How to Succesfully flash the may bootloader - Google Pixel XL Guides, News, & Discussion

What you need:
ROM
VENDOR IMAGE
TWRP RC1
Verifiedbootsigner v6.1 BYCHAINFIRE
MAGISK OR SU (NOT TESTED WITH ME)
1. wipe all (system,data,cache)
2.Flash rom (MAKE SURE YOU CHECK WHICH SLOT YOU ARE FLASHING INTO)
3.flash twrp and vendor
4. flash Verifiedbootsigner
5. POWER OFF PHONE
6. boot to bootlaoder and then boot to RECOVERY.
7. REFLASH BOOT SIGNER
8. BOOT TO BOOTLOADER
9. OPEN UP CMD ON COMPUTER AND USE COMMAND BOOT (inactive slot) recover twrp.img
10. once booted into recovery flash twrp rc1 and then reflash bootsigner(force if you have to)
11. Then switch bootslots to the active one which has the rom and boot.
12. NOW FLASH MAGISK AFTER YOU BOOT
The above is my method and how i got around it, i understand i could have made the above abit more cleaner but i am in a rush and wanted to help a few fellows.
If anyone has a more detailed description of the above, please let me know so i can post.
Thanks

asad510 said:
What you need:
ROM
VENDOR IMAGE
TWRP RC1
Verifiedbootsigner v6.1 BYCHAINFIRE
MAGISK OR SU (NOT TESTED WITH ME)
1. wipe all (system,data,cache)
2.Flash rom (MAKE SURE YOU CHECK WHICH SLOT YOU ARE FLASHING INTO)
3.flash twrp and vendor
4. flash Verifiedbootsigner
5. POWER OFF PHONE
6. boot to bootlaoder and then boot to RECOVERY.
7. REFLASH BOOT SIGNER
8. BOOT TO BOOTLOADER
9. OPEN UP CMD ON COMPUTER AND USE COMMAND BOOT (inactive slot) recover twrp.img
10. once booted into recovery flash twrp rc1 and then reflash bootsigner(force if you have to)
11. Then switch bootslots to the active one which has the rom and boot.
12. NOW FLASH MAGISK AFTER YOU BOOT
The above is my method and how i got around it, i understand i could have made the above abit more cleaner but i am in a rush and wanted to help a few fellows.
If anyone has a more detailed description of the above, please let me know so i can post.
Thanks
Click to expand...
Click to collapse
And not a verizon phone

asad510 said:
What you need:
ROM
VENDOR IMAGE
TWRP RC1
Verifiedbootsigner v6.1 BYCHAINFIRE
MAGISK OR SU (NOT TESTED WITH ME)
1. wipe all (system,data,cache)
2.Flash rom (MAKE SURE YOU CHECK WHICH SLOT YOU ARE FLASHING INTO)
3.flash twrp and vendor
4. flash Verifiedbootsigner
5. POWER OFF PHONE
6. boot to bootlaoder and then boot to RECOVERY.
7. REFLASH BOOT SIGNER
8. BOOT TO BOOTLOADER
9. OPEN UP CMD ON COMPUTER AND USE COMMAND BOOT (inactive slot) recover twrp.img
10. once booted into recovery flash twrp rc1 and then reflash bootsigner(force if you have to)
11. Then switch bootslots to the active one which has the rom and boot.
12. NOW FLASH MAGISK AFTER YOU BOOT
The above is my method and how i got around it, i understand i could have made the above abit more cleaner but i am in a rush and wanted to help a few fellows.
If anyone has a more detailed description of the above, please let me know so i can post.
Thanks
Click to expand...
Click to collapse
On step one. After you wipe system, data, and cache, your wiping the system to your active slot.the one your on. So I would say you would want to switch slots right here. So your new rom goes on clean slot.
In my experience so far after your step 5 you will have to fastboot boot TWRP again, because you just flashed a rom now and it's not signed anymore. So TWRP will not boot. Unless you have April bootloader in that slot, if you have may in both slots you will have to fastboot boot twrp. So far this is what I have had to do. I would like to know if someone has figured out how to flash a rom on may bootloader's without having to use fastboot.

mac796 said:
On step one. After you wipe system, data, and cache, your wiping the system to your active slot.the one your on. So I would say you would want to switch slots right here. So your new rom goes on clean slot.
In my experience so far after your step 5 you will have to fastboot boot TWRP again, because you just flashed a rom now and it's not signed anymore. So TWRP will not boot. Unless you have April bootloader in that slot, if you have may in both slots you will have to fastboot boot twrp. So far this is what I have had to do. I would like to know if someone has figured out how to flash a rom on may bootloader's without having to use fastboot.
Click to expand...
Click to collapse
Mac your right mate. I'm not sure you can do it but what I have noticed is that twrp rc1 is needed for may bootloader

Related

fastboot help

I was flashing TWRP
I couldn't boot into system after flashing..
This is what I did:
1. fastboot boot recovery.img
2. Swipe to allow modifications in twrp
3. Flash TWRP installer zip
4. Reboot into partition B
5. Reboot bootloader
6. fastboot boot recovery.img
7. Swipe to allow modifications in twrp
8. Flash TWRP installer zip
9. Then I rebooted into recovery to check if recovery boots and it did.
But afterwards couldn't boot back into system. It was again booting into recovery.
I booted into recovery using fastboot boot, that's why it might won't boot into system. Is there a command to boot into system after above procedure?
Files used: https://m.youtube.com/watch?v=tRcYUMBgvaI
? How to Root Mi A1! Unlock Bootloader, TWRP Recovery ... - YouTube
By Dhananjay Bhosale
Kindly also suggest source of files you used, if you know another working method.
I have the same problem. Meanwhile, flash the stock fastboot images.
Why do you want to have TWRP installed? I am following these steps each month (fastboot ROM was always out sooner than my OTA) without any issues.
1. flash stock ROM via fastboot
2. fastboot boot twrp-3.1.1.img and don't allow system modifications or you won't be able to apply OTA
3. install magisk 15.1
4. reboot to system
If first boot takes more than 2-3 minutes, hold power off button until phones restarts, second start will take the usual time.
I also don't allow any modifications from TWRP, and just boot to TWRP when I need to. I do not install TWRP.
Sounds like you'll have to do a miflash of the rom, then try not installing TWRP and not allowing any modifications in TWRP to system. Just use TWRP to flash Magisk.

* * * [Pixel 2 XL] - UPDATE Monthly Factory Image / UPGRADE To New OS * * *

WHO IS THIS GUIDE FOR:
Anyone updating factory images within the same OS version (10 to 10)
Anyone upgrading from one OS to another (9x to Android 10)
Below is a QUICK REFERENCE guide for those who have done this before, and a DETAILED STEP BY STEP guide for the first or second timer who needs each and every step outlined. Links to all required files are also provided (make sure you are selecting the latest version)
UPDATE TO THE LATEST FACTORY IMAGE . . . UPGRADE TO THE NEXT OS. . .
PREP WORK:
* Unlocked bootloader. (*performing critical_unlock only required with bootloader versions PRIOR to TMZ20a) read it here.
* Latest SDK Platform Tools found here.
* USB 2.0 & 3.0 cables available (trust me)
* Remove screen lock security before starting
* Remove all substratum overlays
*Download and extract the latest Taimen factory image (place the second extracted folder in Platform Tools folder)
CLEAN FLASH (wipe everything) or DIRTY FLASH (keep data)
Decide now whether you want a fresh OS that will restore your device to factory setup OR if you want to flash the latest factory image but keep your data.
For a clean flash: leave the FLASH-ALL file intact, change nothing.
To retain your data: EDIT the FLASH-ALL file and REMOVE the -w near the end of the script. Save the file and reopen it to ensure the -w has been removed,
When UPGRADING from one OS to another I reco a CLEAN FLASH (leave the -w intact)
Place these files on your sdcard (either before dirty flash or from PC after clean install):
* Latest TWRP.ZIP
* Your preferred customer kernel zip, I use ElementalX kernel
* Magisk uninstall instructions In the event you need to manually uninstall and reinstall MM
* Latest Magisk.zip
* Latest Magisk Manager APK
NOTE: On Android 10, when flashing TWRP Installer, kernels, magisk , etc. in TWRP, ignore the warning "FAILED TO MOUNT '/system' (invalid argument) this is a known issue with TWRP + 10 but affects nothing :good:
QUICK REFERENCE GUIDE for updating/upgrading Pixel 2 XL:
Once you verify 'fastboot devices' on command prompt
Type flash-all to install factory image (allow it to install, and boot into system)
Hold vol down and power button to boot into bootloader
Fastboot into twrp 3.3.0-0.IMG
Flash the twrp installer 3.3.0-0.ZIP,
Flash custom kernel, I use flar2's ElementalX Kernel. SELECT THE CORRECT 9X OR ANDROID 10 KERNEL
Let the system boot up to verify.
Reboot back into twrp and flash latest magisk
Reboot to system
Profit
DETAILED STEP BY STEP GUIDE for updating monthly factory images, or upgrading to the next OS (ie: 9x to 10x)
I reco a CLEAN FLASH (leave the -w intact) when jumping from one OS to a new one (not necessary when doing monthly factory updates within the same OS version)
Requirements:
*Unlocked bootloader and Critical_unlock* completed. (*critical_unlock required with bootloader versions PRIOR to TMZ20a) read it here.
*Latest SDK PlatformTools found here
*USB 2.0 & 3.0 cables available (trust me)
These files on your sdcard:
* Latest TWRP.ZIP
* Your preferred Custom Kernel, I use Elemental X Kernel
* Magisk uninstall instructions In the event you need to manually uninstall and reinstall MM
* Latest Magisk.zip
* Latest Magisk Manager APK
These files in your Platform Tools Folder:
* Latest factory image (MAKE SURE YOU DL THE CORRECT DEVICE IMAGE :good: )
* Latest TWRP.IMG
1. Make backup, move to PC (because you never know)
2. Disable all security; patterns, pins, etc.
3. In Developer Options, make sure USB DEBUGGING is on
4. Connect device to PC, verify fastboot is working type; fastboot devices (should see your device's serial number)
5. Fastboot latest factory image (To KEEP internal storage intact, edit and remove -w in "flash-all.bat" file and SAVE, to wipe entire device, leave flash-all unedited)
Type: FLASH-ALL (hit enter) Allow the OS to reboot and settle for a minute *REMEMBER LEAVING THE -W INTACT WILL WIPE YOUR DEVICE*
6. Reboot into BOOTLOADER, in CMD screen Type: fastboot boot <twrpxxx.img name> to boot into Latest TWRP.IMG
7. Once in TWRP, install Latest TWRP.ZIP from sdcard
8. Reboot back into Recovery
9. Install compatible custom kernel, I use flar2's ElementalX Kernel.
10. Reboot back into Recovery
11. Reboot into System, allow OS to settle for a few minutes
12. Boot into Recovery
13. Install Latest Magisk.zip
14. Reboot into System
15. Profit
Troubleshooting Tips & Other Information
Click here for * * * BASIC FASTBOOT/ADB TROUBLE SHOOTING FOR THE 2XL * * *
If you get stuck at the G screen, or bootloop into TWRP, try these steps:
-Perform a hard reboot (long press the power button) or
-Get back to TWRP (whether by booting into it from fastboot, or rebooting into bootloader -long press power & vol down- then boot into recovery) and reinstall the Magisk Uninstaller in TWRP a few times.
- If you are bootlooping into TWRP with Magisk installed, READ THIS!
- Safety Net message in Magisk "The Response Is Invalid" is a known issue[/URL] ... Be patient
View attachment 4572738
Make sure you have all the correct and/or latest versions of SDK Tools, factory image, TWRP.img and TWRP.zip, and Magisk
Note: as a matter of superstition, I reboot back into recovery each time after installing TWRP, cust kernel, and magisk, prior to booting into system. It is NOT required, but it works
Again, HUGE thanks to @Badger50 for his invaluable input
Az Biker said:
A lot of users have had success upgrading from Oreo to Pie and there are several tutorial / guide posts located in different threads, so I figured I'd centralize instructions in a Quick Reference Thread, that includes all needed file links and an easy to follow step by step.
Please feel free to make any suggestions to simplify or make this more accurate.
Requirements:
*Unlocked bootloader and Critical_unlock completed.
*Latest SDK Tools found here
*USB 2.0 & 3.0 cables available (trust me)
These files on your sdcard:
* TWRP 3.2.2-0.ZIP
*Flash kernel 3.0
* magisk uninstaller
*magisk zip 1674
* MM 5.8.3 APK
These files in your Platform Tools Folder:
* 9.0 factory image
*TWRP 3.2.2-0.IMG
1. Make backup, move to PC (because you never know)
2. Disable all security; patterns, pins, etc.
3. In Developer Options, make sure USB DEBUGGING is on
4. Verify fastboot is working type; fastboot devices (should see your device's serial number)
5. Fastboot 9.0 factory image(To KEEP internal storage intact, remove -w in "flash-all.bat" file and SAVE, to wipe entire device, leave flash-all unedited)
6. Type: fastboot boot <twrpxxx.img name> to boot into TWRP 3.2.2-0.IMG
7. Once in TWRP, install TWRP.ZIP on sdcard
8. Reboot back into Recovery, and install the magisk uninstaller in twrp,
9. Reboot back into Recovery and install Flash kernel 3.0
10. Reboot back into Recovery
11. Reboot into System, allow OS to settle for a few minutes
12. Install MM 5.8.3 APK
13. Reboot into Recovery
14. Install magisk zip 1674,
15. Reboot back into Recovery
16. Reboot into System
17. Profit
Note: as a matter of superstition, I reboot back into recovery each time after installing TWRP, cust kernel, and magisk, prior to booting into system. It is NOT required, but it works
Thanks to @Badger50 for figuring out the right steps in this process!
Click to expand...
Click to collapse
Well done my brother!! :good::good:
Badger50 said:
Well done my brother!! :good::good:
Click to expand...
Click to collapse
I use unlock bootloader normal.
I was done follow your step but it's boot stuck google logo after flash magisk(16.74).
newyesor said:
I use unlock bootloader normal.
I was done follow your step but it's boot stuck google logo after flash magisk(16.74).
Click to expand...
Click to collapse
Sometimes it takes 5 minutes or so on first boot. If it doesn't work, do a hard restart a few times. If that doesn't work, flash magisk again in twrp.
You use unlock bootloader normal??
Badger50 said:
Sometimes it takes 5 minutes or so on first boot. If it doesn't work, do a hard restart a few times. If that doesn't work, flash magisk again in twrp.
You use unlock bootloader normal??
Click to expand...
Click to collapse
I use normal unlock bootloader.
I wait devices boot around 5 minutes and it 's reboot in to twrp recovery.
newyesor said:
I use normal unlock bootloader.
I wait devices boot around 5 minutes and it 's reboot in to twrp recovery.
Click to expand...
Click to collapse
So your bootloader _critical partition isn't unlocked?? Which can't be right either since you've been able to boot fastboot the update to P. Guess I just don't know what your trying to say.
Badger50 said:
So your bootloader _critical partition isn't unlocked?? Which can't be right either since you've been able to boot fastboot the update to P. Guess I just don't know what your trying to say.
Click to expand...
Click to collapse
I use this command for flash unlock bootloader.
fastboot flashing unlock
newyesor said:
I use this command for flash unlock bootloader.
fastboot flashing unlock
Click to expand...
Click to collapse
Have you ever ran fastboot flashing unlock_critical..?
Have you actually booted into the 9.0.OS yet?
Badger50 said:
Have you ever ran fastboot flashing unlock_critical..?
Have you actually booted into the 9.0.OS yet?
Click to expand...
Click to collapse
I have never ran fastboot flashing unlock_critical.
Yes,My devices is base on android P and I was booted into the 9.0.OS.
newyesor said:
I use this command for flash unlock bootloader.
fastboot flashing unlock
Click to expand...
Click to collapse
If you flashed the factory image with no issues, then you must have completed critical_unlock as well, otherwise the new bootloader shouldn't have taken (as far as I understand).
I'd start from scratch again, and make sure you follow the process exactly. Many users have used this with no issue, so maybe you missed something? The first time I flashed the factory image to my 6P (my backup) I totally skipped flashing the boot.img, and wondered why it wouldn't boot
Kudos, just what I needed to update!
newyesor said:
I have never ran fastboot flashing unlock_critical.
Yes,My devices is base on android P and I was booted into the 9.0.OS.
Click to expand...
Click to collapse
Have you flashed the magisk uninstaller as well? Why are you showing magisk 16.0?
Badger50 said:
Have you flashed the magisk uninstaller as well? Why are you showing magisk 16.0?
Click to expand...
Click to collapse
Yes,i was flashed the magisk uninstaller as well.
I try to root with magisk on my devices.
I try to flash patch boot for root without twrp but it's not work.
I try to flash magisk follow you but it's not work.
Is flashing the kernel mandatory?
newyesor said:
Yes,i was flashed the magisk uninstaller as well.
I try to root with magisk on my devices.
I try to flash patch boot for root without twrp but it's not work.
I try to flash magisk follow you but it's not work.
Click to expand...
Click to collapse
Something just seems fishy to me. I've never heard of anyone not unlocking _critical, and being able to fastboot the factory image. However, it seems that you have somehow. All I can suggest is to fastboot the 9.0 again to both slots, and let it boot up each time.
Then fastboot into twrp, flash the installer zip, and let it boot up. Then go back to twrp, flash magisk uninstaller zip, then flash custom kernel, and let it boot up. Then go back to twrp, and flash magisk 1674 again.
If none of that works, I'd unlock _critical, which will wipe your phone, and then start over.
aznriceballman said:
Is flashing the kernel mandatory?
Click to expand...
Click to collapse
Not mandatory, but it keeps TWRP touch screen working among other things...
Just wanted to say thanks for this!
I didn't have time to update from DP5 yesterday, but I guess that was a good thing because now there's this guide, and it worked perfectly. Upgraded from DP5/flash 2.44 and who knows what Magisk version to all the latest and greatest in no time at all.
Thanks!
Badger50 said:
Something just seems fishy to me. I've never heard of anyone not unlocking _critical, and being able to fastboot the factory image. However, it seems that you have somehow. All I can suggest is to fastboot the 9.0 again to both slots, and let it boot up each time.
Then fastboot into twrp, flash the installer zip, and let it boot up. Then go back to twrp, flash magisk uninstaller zip, then flash custom kernel, and let it boot up. Then go back to twrp, and flash magisk 1674 again.
If none of that works, I'd unlock _critical, which will wipe your phone, and then start over.
Click to expand...
Click to collapse
im having an issue, i followed all instructions and got booted up an everything but when i flash twrp img it stays stuck on the twrp logo, flashed the one mentioned in o.p and the newest as well to remove any doubts, but no go. Any suggestions?
shooterlgk said:
im having an issue, i followed all instructions and got booted up an everything but when i flash twrp img it stays stuck on the twrp logo, flashed the one mentioned in o.p and the newest as well to remove any doubts, but no go. Any suggestions?
Click to expand...
Click to collapse
Do you have screen lock disabled?
Badger50 said:
Do you have screen lock disabled?
Click to expand...
Click to collapse
Yes sir

Flashable Recovery?

Hello, I know our great device does not have a recovery partition, so we need to use fastboot to boot TWRP. But muy question is, is there no way to boot into TWRP without a computer? Maybe a terminal command from Android itself, or a little script that we can run when needed? This might be a noob question, but I'm sure many here could profit from a positive answer.
Thanks
Angelelz said:
Hello, I know our great device does not have a recovery partition, so we need to use fastboot to boot TWRP. But muy question is, is there no way to boot into TWRP without a computer? Maybe a terminal command from Android itself, or a little script that we can run when needed? This might be a noob question, but I'm sure many here could profit from a positive answer.
Thanks
Click to expand...
Click to collapse
Assuming youre rooted... Ive used the reboot app on my phone. I have a 1926-7 Moto G6 Plus. It will boot to fastboot, fast reboot, recovery, reboot system etc. Look around xda and see if someone has a good reboot app or else use GP. I actually had twrp flashed permanently to my phone but it would not back up so I have to redo it. Also the phones data was encrypted and I didnt know how to fix it. I hope that you are able to find something that works for you
You can boot into TWRP via terminal command without using a computer. Use the 'dd' command ( 'dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.backup.img' ) to take a backup of your boot.img. Than use 'dd' to overwrite boot with twrp and reboot to recovery (dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/boot)
Later to boot your phone as normal you only have to install your boot.img backup via TWRP.
now we can install a TWRP 3.3.0 ONLY ON DECRYPTED ROMS (the lastest Havoc, Resurrection Remix, AEX, Decendant, PixyOS are unencripted by default) for flashing magisk modules or mods but it will be overwrite when we flash/update our custom/stock rom:
https://drive.google.com/open?id=1CqzvBiEfk9xucXG8UemNZMhBxDCeSV0i
How to install it:
Put the donwloaded TWRP on your plataform tools folder and in your internal/sd storage.
Boot the same TWRP (fastboot boot TWRP.img)
Go to ADVANCED and select Install Ramdisk Recovery
Check backup boot box( in case something goes wrong just restore your boot partition)
Swipe and wait until finish.
Reboot
If every reboot finishes in twrp booting just flash magisk and youll be able to boot into system.

[GUIDE] Official Stock Android 10 flashing , Rooting with magisk and TWRP

In this guide i will go over how to flash stock android 10 if you are unlocked after flashing installing magisk and disabling force encryption :-
THIS GUIDE HAS BEEN TWEAKED AND UPDATED FOR PIXEL EXPERIENCE TOO
HTML:
Your warranty is now void.
We are not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about mods
included in these GUIDES before using them! YOU are choosing to
make these modifications.
THIS GUIDE IS ONLY FOR THOSE WHO HAVE UNLOCKED THEIR BOOTLOADER
Moving from Custom ROM to Stock 10 :- OR Flashing PE 10
First downlaod Stock 10 CLICK HERE OR Pe 10
Reboot to twrp
Wipe everything expect internal storage
Flash ROM Zip
>Now if You Want to be Encrypted you can skip to Formatting Data Step This is for whom you don't want to format and want to be decrypted
>Change Slot and Reboot To Bootloader
>Boot To Official TWRP Image
>Now Flash FBE Disabler (Normally Or Via ADB Sideload ) and Reboot
Now You have to Format Your Data (IMPORTANT IF YOU CHOOSE TO BEING ENCRYPTED)
Change Slot
Now Reboot
IMPORTANT DON'T TRY TO FLASH TWRP INSTALLER JUST AFTER FLAHING THE STOCK ROM OR ELSE YOU WILL NOT BE ABLE TO BOOT ROM IN PE YOU CAN FLASH TWRP INSTALLER BUT IT TWRP WON'T BOOT AS OUR TWRP ISN'T YET READY FOR FBE
IF YOU ARE ALREADY ON STOCK(ENCRYPTED) AND WANT TO INSTALL MAGISK OR WANT TO DECRYPT SO CAN USE TWRP AGAIN
Once you have installed Stock 10 via TWRP in a rush and later you find out nothing is working there no TWRP no magisk and thus you can't move to custom ROM now , well check this out now
STEPS TO ONLY INSTALL MAGISK WITHOUT ANY DECRYPTION
Downlaod pathced boot image from link CLICK HERE
Reboot to Fastboot
Now type this code
HTML:
fastboot flash boot magisk_patched.img
After Success message reboot normally
Now Install Magisk Manager (apk)
YOU ARE ROOTED !
STEPS TO INSTALL MAGISK REMOVE DECRYPTION AND USE TWRP (For Stock and Pixel Experience Both)
IN ORDER TO SWITCH TO OTHER CUSTOM ROMs WHICH AREN'T FORCE-ENCRYPTED YOU HAVE TO DECRYPT FIRST !
IF YOU ARE ALREADY MOVING TO A ENCRYPTED ROM THEN YOU DON'T HAVE TO DECRYPT .
Reboot to Fastboot
Now type this code
HTML:
fastboot -w
This will earse all your data and decrypt
Now wait don't reboot
Now downlaod TWRP image and place it in you platform folder
Now boot to TWRP using this code
HTML:
fastboot boot twrp.img
As soon as you are in twrp flash force encrypt disabler
After Flashing Disabler Flash Magisk and reboot
NOW YOU ARE ON STOCK WITH NO ENCRYPTION AND MAGISK INSTALLED!
IF JUST IN CASE YOU WANT TO MOVE TO CUSTOM ROMs JUST AFTER FORMAT DATA AND BOOTING TWRP STEP FLASH YOUR DESIRED ROM
RECOMMENDED TWRP :- XDA HERE
THANKS Zacktg5 for Zip
HIT THANKS:cyclops:
I followed "STEPS TO ONLY INSTALL MAGISK WITHOUT ANY DECRYPTION" and got a bootloop
Thank you man!
Coming from a custom ROM (PE 10), is it possible to flash the stock 10 using fastboot, or this will cause issues?
can't install miui_JASMINEGlobal_V11.0.4.0.QDIMIXM_545aa0d958_10.0.zip
Step 1/2
Error applying update: 7 (ErrorCode :: kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Error installing zip file /sdcard/miui_JASMINEGlobal_V11.0.4.0.QDIMIXM_545aa0d958_10.0.zip
---------- Post added at 03:19 PM ---------- Previous post was at 03:18 PM ----------
Zedsdeadbaby said:
I followed "STEPS TO ONLY INSTALL MAGISK WITHOUT ANY DECRYPTION" and got a bootloop
Click to expand...
Click to collapse
you can install miui_JASMINEGlobal_V11.0.4.0.QDIMIXM_545aa0d958_10.0.zip ?
why I got error ?
link to Universal DM-Verity, ForceEncrypt, Disk Quota Disablers in case someone asks: http://zackptg5.com/android.php#disverfe
XDA: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Great
Antusuprik said:
can't install miui_JASMINEGlobal_V11.0.4.0.QDIMIXM_545aa0d958_10.0.zip
Step 1/2
Error applying update: 7 (ErrorCode :: kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Error installing zip file /sdcard/miui_JASMINEGlobal_V11.0.4.0.QDIMIXM_545aa0d958_10.0.zip
---------- Post added at 03:19 PM ---------- Previous post was at 03:18 PM ----------
you can install miui_JASMINEGlobal_V11.0.4.0.QDIMIXM_545aa0d958_10.0.zip ?
why I got error ?
Click to expand...
Click to collapse
use some other twrp
I have flashed Android 10 ZIP in TWRP in slot A. After that i changed to slot B and restart to TWRP. In slot B i flashed Encryption Disabler zip and Magisk zip in order.
Same product, less steps
blackman01 said:
Downlaod pathced boot image from link CLICK HERE
HIT THANKS:cyclops:
Click to expand...
Click to collapse
Is this a December patched boot IMG?
d3rt0xx said:
I have flashed Android 10 ZIP in TWRP in slot A. After that i changed to slot B and restart to TWRP. In slot B i flashed Encryption Disabler zip and Magisk zip in order.
Same product, less steps
Click to expand...
Click to collapse
Just the Android 10 ZIP or with the twrp zip? Didn't you lose twrp if you didn't flash the twrp zip?
Thufailb said:
Just the Android 10 ZIP or with the twrp zip? Didn't you lose twrp if you didn't flash the twrp zip?
Click to expand...
Click to collapse
Without TRWP installer. I reboot to bootloader after every single step and boot TWRP.img manually with fastboot boot TWRP.img
So stock recovery is preset
Step by step:
- Boot twrp.img in fastboot from PC "fastboot boot twrp.img"
- Delete all partitions and be sure active boot slot is "A"
- Reboot to Bootloader, NOT Recovery
- Boot twrp.img in fastboot from PC "fastboot boot twrp.img" again
- Install Android 10 zip
- Change active boot slot to "B"
- Reboot to Bootloader, NOT Recovery again
- Boot twrp.img in fastboot from PC "fastboot boot twrp.img" again
- Flash Encryption Disabler zip
- Flash Magisk zip in order
- Reboot! Profit!
Fresh Android 10, decrypted and rooted with stock recovery :good:
Which recovery did you use tho?
Also does that recovery boot from stock android 9???
Please help,asap.
Guys, I have mi a2 on official pie and arb4. How to update?
Rupamxx said:
Which recovery did you use tho?
Also does that recovery boot from stock android 9???
Please help,asap.
Click to expand...
Click to collapse
Recent twrp.
Twrp boots from every version
d3rt0xx said:
Without TRWP installer. I reboot to bootloader after every single step and boot TWRP.img manually with fastboot boot TWRP.img
So stock recovery is preset
Step by step:
- Boot twrp.img in fastboot from PC "fastboot boot twrp.img"
- Delete all partitions and be sure active boot slot is "A"
- Reboot to Bootloader, NOT Recovery
- Boot twrp.img in fastboot from PC "fastboot boot twrp.img" again
- Install Android 10 zip
- Change active boot slot to "B"
- Reboot to Bootloader, NOT Recovery again
- Boot twrp.img in fastboot from PC "fastboot boot twrp.img" again
- Flash Encryption Disabler zip
- Flash Magisk zip in order
- Reboot! Profit!
Fresh Android 10, decrypted and rooted with stock recovery :good:
Click to expand...
Click to collapse
Hi, very helpful guide.
But how do you get OTA update when there's a new one? Can you provide the steps to get OTA and then get back to root. Thanks in advance.
disaster_peace said:
Hi, very helpful guide.
But how do you get OTA update when there's a new one? Can you provide the steps to get OTA and then get back to root. Thanks in advance.
Click to expand...
Click to collapse
Easy!
Just install normally via updater.
But before you restart your phone, install TWRP Retention Script via Magisk Manager to change active boot slot
can i skip installing magisk in this guide to get my banking apps working??
Sivakumar$ said:
can i skip installing magisk in this guide to get my banking apps working??
Click to expand...
Click to collapse
Yes, if you only install official OTA, banking apps work. Why not? Its official and unrooted
But decryption Script will useless without root i think
Im on derp fest Q rom now i want to go to stock 10 i cannot find any latest fastboot file and there is some issues with the mi flash tool as some users were reporting getting dev error
I'm tried using two versions of TWRP(3.2.3-0 and 3.3.1-0) and got two different errors:
• No digest file found (3.2.3-0)
• Error 7 (3.3.1-0)
What should I do? I don't have any ROM's installed

All Custom ROM installations fail the same way.

I am trying to get a custon ROM to work on my Oneplus 8 Pro (instantnoodlep)
ROMs I tried installing:
Cherish OS 3.9.5
Nameless-AOSP_instantnoodlep-12.1-20220708-0935-Official
What I do:
1. Download recovery provided with the ROM
2. Reboot to bootloader and flash recovery
'fastboot flash recovery recovery.img'
'fastboot reboot recovery'
3. Select apply update/apply from ADB
4. Connect device to PC
5. Sideload rom.zip
'adb sideload rom.zip'
6 Do Factory reset/format data from recovery
7. Restart to system
What happens:
Phone goes to fastboot and stays there.
When I try
fastboot reboot system
or
fastboot reboot recovery
I also land in fastboot again.
The only way to get out of fastboot again is fastboot boot recovery.img, which boots into recovery. When I then reboot into system, my old OOS11 boots up.
Because this is independent of the Custon ROM, there might be another issue. But which one?
You made sure you have latest OOS11 on BOTH slots?
xtcislove said:
You made sure you have latest OOS11 on BOTH slots?
Click to expand...
Click to collapse
Thanks for the response! How do i check that? Both slots of what?
Infraviored said:
Thanks for the response! How do i check that? Both slots of what?
Click to expand...
Click to collapse
When you're booted in OOS 11 just do a local install of the same OOS version that you're on. That will install OOS to the other slot, meaning you'll have the same OOS version on both slots and "should" be able to flash a custom rom.
Infraviored said:
I am trying to get a custon ROM to work on my Oneplus 8 Pro (instantnoodlep)
ROMs I tried installing:
Cherish OS 3.9.5
Nameless-AOSP_instantnoodlep-12.1-20220708-0935-Official
What I do:
1. Download recovery provided with the ROM
2. Reboot to bootloader and flash recovery
'fastboot flash recovery recovery.img'
'fastboot reboot recovery'
3. Select apply update/apply from ADB
4. Connect device to PC
5. Sideload rom.zip
'adb sideload rom.zip'
6 Do Factory reset/format data from recovery
7. Restart to system
What happens:
Phone goes to fastboot and stays there.
When I try
fastboot reboot system
or
fastboot reboot recovery
I also land in fastboot again.
The only way to get out of fastboot again is fastboot boot recovery.img, which boots into recovery. When I then reboot into system, my old OOS11 boots up.
Because this is independent of the Custon ROM, there might be another issue. But which one?
Click to expand...
Click to collapse
U don't need the command fastboot reboot recovery. U can just use the volume buttons to select recovery and press power button to boot to recovery
Nimueh said:
When you're booted in OOS 11 just do a local install of the same OOS version that you're on. That will install OOS to the other slot, meaning you'll have the same OOS version on both slots and "should" be able to flash a custom rom.
Click to expand...
Click to collapse
Another way to set your phone up for a custom rom can be found here. https://wiki.lineageos.org/devices/instantnoodlep/install
Just make sure your booting from a good 00S11 install when you do this.
I had a heck of a time with this two days ago. OP pushed c33, A12 on my phone. It took forever to corrupt both a and b enough to get twrp recovery installed and working to install A11 again. I had to load the recovery on both slots, a and b and I used twrp install to install the OTA to slot a. Right now I have nothing on slot b other that twrp recovery.
king_xerxes said:
I had a heck of a time with this two days ago. OP pushed c33, A12 on my phone. It took forever to corrupt both a and b enough to get twrp recovery installed and working to install A11 again. I had to load the recovery on both slots, a and b and I used twrp install to install the OTA to slot a. Right now I have nothing on slot b other that twrp recovery.
Click to expand...
Click to collapse
Sorted it out by this. Thank you!

Categories

Resources