Related
[GUIDE] NOOB-Friendly STEP-BY-STEP Instructions to Install Monthly OTA updates on Rooted Essential PH-1
Introduction: I know there are many threads already posted that answer how to install OTA on rooted devices but unfortunately they get lost in massive threads that are often not NOOB friendly. I do not claim to be an expert but I have spent a long time reading threads and found the method I will detail below the easiest for me to follow on a monthly basis. I will do my best to give credit where credit is due to the original authors but my apologies in advance if I miss anything.
Just to start the prerequisites I have are a Windows 10 PC, Essential PH-1, with Stock OS and stock unlocked Bootloader. I have tried using TWRP in the past but I found this method simpler. I don't know whether my instructions will work for you or not if you already have TWRP installed but I can let one of the experts respond and I will be happy to update the guide based on feedback.
Part 1 - Downloads
Start by downloading the following items and storing them locally on your PC if you don't have them already
Download the latest OTA Monthly build from here: https://www.essential.com/developer/current-builds Note: Just check off that you are looking for "Current Builds" and click "Submit Form" and then click "Download (OTA)" link beneath the newest release you want.
Download the newest stock boot image here from bmg1001's google drive Credit:bmg1001
(FIRST TIME ONLY) Download and install the Windows driver (if you don't already have on your computer) from here: https://storage.googleapis.com/essential-static/Essential-PH1-WindowsDrivers.exe
(FIRST TIME ONLY) Download ADB tool (if you don't have already on your computer) from here: https://developer.android.com/studio/releases/platform-tools.html This link is directly from Essentials site here in their "Before Sideloading" section it is the link entitled "You'll need the latest ADB tool"
To continue you must have developer options USB Debugging enabled which I presume was already done previously if your phone is rooted but if not you must do so before proceeding.
To Enable Developer Options: Settings App> System> About Phone> Scroll Down to Bottom and tap 7 times on the "Build Number"
To Enable USB Debugging: Settings App> Developer Options> USB Debugging (Set to Enabled)
Part 2 - Sideload the OTA Update
DISCLAIMER: This method if done properly should not wipe any of your data, however I take no responsibility and it is always advisable to back up your data before proceeding with any updates if you wish. I will be honest that I have now done this several times and never had any issues.
Unzip the ADB tool (link above in downloads section is for "platform-tools") and save it to a folder easily accesible on your computer (for this demonstration I will use "C:\platform-tools")
Copy the OTA update file to your ADB folder i.e. "C:\platform-tools" and rename it "OTAupdate.zip" (it is not necessary to rename it, just makes this simpler for the guide)
Verify the checksum of the image. I use hashtab which allows you to right click on any file and click properties and see the hashes as a tab in the properties menu. The SHA-256 is listed right under the OTA download link just copy and paste it in to the hashtab to verify
Remove your PIN / Password before sideloading by going to Settings> Security & Location> Screen Lock> Set it to None (this probably isn't necessary I just do it as a precaution)
Plug Essential Phone into computer and make sure that it says USB Debugging Enabled
Open the folder "C:\platform-tools" in Windows File Explorer and hold shift and right click in the window and you select the option "Open Powershell window here" from the context menu (works in Windows 10 can't speak for earlier Windows versions). If you don't see it the first time Shift+right click on a different part of the empty white window and you should see it appear.
Verify your device is properly connected by typing
Code:
adb devices
and you should see your device listed
Type
Code:
adb reboot recovery
Note:If you're unable to use ADB to reboot into recovery, you can use the key combination for your device. While device is off to boot into Recovery mode, press and hold Volume-Up button while pushing Power button to boot.
Your device is now in Recovery mode. An Android logo with red exclamation mark should appear on screen. Hold the Power button, then press the Volume-Up button one time. When the menu appears, select Apply update from ADB.
Run the following command:
Code:
adb devices
Then check that your device shows up with “sideload” next to its name
Run the following command:
Code:
adb sideload OTAupdate.zip
where OTAupdate.zip is the name of the file you downloaded and verified
Once the update finishes, select Reboot system now to reboot your phone
At this point you should have a stock updated essential device but without root. The remainder of this guide will use Magisk to restore your device to root.
Part 3 - Re-root your Device with Magisk
Copy newest boot image from here that you downloaded earlier to a folder directly on your phone. I personally put it in my "Download" folder on my phone so I can find it easily
Open Magisk Manager and click Install>Install>Patch Boot Image
Select the boot image from step 1 and then let Magisk proceed in creating a patched image file
Copy the file "magisk_patched.img" file that Magisk just created from your device back to the computer and put it in the ADB folder "C:\platform-tools"
Plug in phone and open powershell same as before (shift+ right click> Open Powershell window here)
Type
Code:
adb reboot bootloader
to reboot your phone into fastboot
Confirm your phone is in fastboot by typing
Code:
fastboot devices
Then check that your device shows up with “fastboot” next to its name
Execute the command
Code:
fastboot flash boot magisk_patched.img
Restart your phone and you are done! Don't forget to put your phone PIN/Password back if you disabled security in the earlier step.
You should now have a successfully updated phone with full ROOT access with Magisk. I know that this guide seems like a lot of steps but it really goes very quickly, I just tried to be detailed and NOOB-Friendly.
Hope this helps all of my fellow XDA members!! Please share any and all feedback. Thanks!
Full credit goes to this thread for helping me with everything: [GUIDE] Rooting your Essential PH-1
The way I do *updates* is different (not the initial TWRP/ root).
I use the same Essential developer link as in part 1-1. I also have a copy of twrp-installer-mata-3.2.3-0 zip file on my device.
Boot to TWRP, and do a complete nandroid.
Then install the OTA file just like it's any other zip and when it's done, install the twrp-installer-mata-3.2.3-0 zip file. You can simply put them both into the flash queue before starting the flash.
This TWRP installer will install to both slots ensuring that the inactive slot has it installed. Wipe dalvik and then reboot to system which will be in the opposite slot from the one you started at.
The OTA will always flash to the inactive slot and the bootloader will switch to the slot the OTA was flashed to.
The initial boot takes a few minutes. Once I verify the ROM boots correctly, then I reboot to TWRP and flash Magisk. This ensures that Magisk get installed to the same slot that is now active.
I agree it's safer to remove screen pin, so far I have gotten away with never remembering to do that [emoji16]
If the flash fails, the bootloader should just switch you back to the original slot. I would expect that to boot fine, with one exception... The bootloader was changed between 8.1.1 and 9.0. So if you are going between major versions, the original slot will bootloop after the update.
One more note, a pet peeve of mine; when referencing a post that is older, make sure that you review the forums for changes. TWRP might have a required newer release, the methods that once worked may no longer work. If you are not sure or comfortable recovering, then don't be an early adopter. [emoji6]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
The way I do *updates* is different (not the initial TWRP/ root).
I use the same Essential developer link as in part 1-1. I also have a copy of twrp-installer-mata-3.2.3-0 zip file on my device.
Boot to TWRP, and do a complete nandroid.
Then install the OTA file just like it's any other zip and when it's done, install the twrp-installer-mata-3.2.3-0 zip file. You can simply put them both into the flash queue before starting the flash.
This TWRP installer will install to both slots ensuring that the inactive slot has it installed. Wipe dalvik and then reboot to system which will be in the opposite slot from the one you started at.
The OTA will always flash to the inactive slot and the bootloader will switch to the slot the OTA was flashed to.
The initial boot takes a few minutes. Once I verify the ROM boots correctly, then I reboot to TWRP and flash Magisk. This ensures that Magisk get installed to the same slot that is now active.
I agree it's safer to remove screen pin, so far I have gotten away with never remembering to do that [emoji16]
If the flash fails, the bootloader should just switch you back to the original slot. I would expect that to boot fine, with one exception... The bootloader was changed between 8.1.1 and 9.0. So if you are going between major versions, the original slot will bootloop after the update.
One more note, a pet peeve of mine; when referencing a post that is older, make sure that you review the forums for changes. TWRP might have a required newer release, the methods that once worked may no longer work. If you are not sure or comfortable recovering, then don't be an early adopter. [emoji6]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
you know i just finished writing my own guide to do it after i had trouble with the sticky posts. for me, magisk couldnt find the stock boot so i had to pretty much redo it. i did most things with back-to-stock and fastboot. but now i really wanna try your method through twrp. i been using the patched_twrp_magisk_stock.img images which have twrp and magisk in the same image. using your method, in twrp, could i flash the ota, the patched_twrp_magisk_stock.img, switch slots in twrp, flash patched_twrp_magisk_stock.img again, then switch back to the original slot and reboot system? thanks!
this thread has the patched_twrp_magisk_stock.img images
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
@andypiznti
There's no need to manually switch slots. And no reason to flash the TWRP *installer* file twice. The first time it runs, it patches both slots.
IMHO, trying to control slots is what gets people into trouble.
I do pay attention to what slot I'm on before I start though. In TWRP, if you go to the reboot menu, it will tell you. But the way I flash, I stay on the slot I started with. The OTA will always flash to the opposite slot - which should be the inactive slot. Flashing the TWRP *installer* file just once, patches both slots.
Just wipe dalvik (and cache but there is no cache partition so it will error - just ignore the error) then reboot to system like we've done after custom ROMs for years.
The next boot, the bootloader knows to switch to the slot with the newest OS.
After a successful boot, when you return to TWRP, you'll see the slot is the opposite one from when you started. But you didn't need to do any slot switching.
Don't force things. Let the slots take care of themselves.
I also think, there is less likely to be trouble with Magisk and the boot.img, if you boot fully after an update, before returning to recovery to flash Magisk. Remember that both TWRP and Magisk are making changes to the boot.img.
Final thought, unless I seriously misunderstand Magisk, if you rooted using an all-in-one boot.img you won't have a back up of the "stock" boot.img to restore, making the Magisk uninstaller useless. The backup made when installing Magisk is stored on the data partition, not the boot partition. This is why the instructions in BTS tell you to flash the stock boot.img and provide a copy of it.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
The beauty of my method in the OP is you don't need to worry at all about the correct "slots" like you have to with TWRP...
ktmom said:
@andypiznti
I also think, there is less likely to be trouble with Magisk and the boot.img, if you boot fully after an update, before returning to recovery to flash Magisk. Remember that both TWRP and Magisk are making changes to the boot.img.
Final thought, unless I seriously misunderstand Magisk, if you rooted using an all-in-one boot.img you won't have a back up of the "stock" boot.img to restore, making the Magisk uninstaller useless. The backup made when installing Magisk is stored on the data partition, not the boot partition. This is why the instructions in BTS tell you to flash the stock boot.img and provide a copy of it.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
ok that answers a lot. thanks! the guide i made for myself had me flashing the stock image with bts. i was curious about the full boot after an update, i was thinking the same thing in that it might cause problems with magisk, but i also thought twrp would cause problems too. the reason i mentioned switching slots and flashing is the all-in-one img only flashes to one slot at a time, i believe.
heres my guide for reference, its kinda long. but these were the exact steps i followed and was successful. had to flash the img twice, kept rebooting into recovery if i didnt.
Applying OTA for Essential Phone when Magisk doesn't have stock boot
Boot to recovery with Magisk
Back up at least system and boot
Boot to bootloader with TWRP
Extract back to stock (BTS) for CURRENT INSTALLED VERSION, not the update BTS version
Once in bootloader, connect phone->old phone plug, SSD plug
Run flashallnowipe.bat, once bootloader reboots, select Start, unplug phone
Uninstall Magisk like a regular app
Do OTA->settings->advanced->system update
after reboot->reboot while holding volume down until in download/fastboot mode
***REMEMBER!! Flash on the opposite slot of the current slot
***so if im on slot a, flash slot b.
make sure to extract Essential_ADB_and_FASTBOOT.zip in BTS folder then->cmd-here.exe
fastboot getvar current-slot
***
fastboot flash boot_a dec_patched_twrp_magisk_stock.img
fastboot flash boot_b dec_patched_twrp_magisk_stock.img
***Switch to other slot
fastboot --set-active=a
fastboot --set-active=b
***Just to double check, REMEMBER!! Flash on the opposite slot of the current slot
fastboot getvar current-slot
***
fastboot flash boot_a dec_patched_twrp_magisk_stock.img
fastboot flash boot_b dec_patched_twrp_magisk_stock.img
***Switch back to orig slot
fastboot --set-active=a
fastboot --set-active=b
On the phone fastboot menu, select Start, unplug phone
Manager asks if you wanna install it, no, it downloads the wrong one, maybe works now?
Install Magisk Manager->https://github.com/ianmacd/MagiskBuilds
IT HAS TO BE THIS APK, Download any apk version from above github, install
when you open Manager, then download the newest apk, dont update image
Manager and Image update daily, ignore till next month OTA
Click to expand...
Click to collapse
hssxda said:
The beauty of my method in the OP is you don't need to worry at all about the correct "slots" like you have to with TWRP...
Click to expand...
Click to collapse
I don't know what more I could do to make the point it's not necessary to worry about slots in TWRP.
@andypiznti. The all-in-one is Fastboot flashed to either slot one at a time. All of this makes life harder than it needs to be.
My post was suggesting an alternative. Use the OTA, no Fastboot, no PC just have the TWRP installer file I linked so you don't lose TWRP.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
I don't know what more I could do to make the point it's not necessary to work about slots in TWRP.
Click to expand...
Click to collapse
Well, all of your posts describing your method contains the word "slot" multiple times so it is obviously a relevant concern otherwise you wouldn't have mentioned it. My post did not contain the word even once...
I see no need to use TWRP. What advantage does it have?
ktmom said:
I don't know what more I could do to make the point it's not necessary to worry about slots in TWRP.
@andypiznti. The all-in-one is Fastboot flashed to either slot one at a time. All of this makes life harder than it needs to be.
My post was suggesting an alternative. Use the OTA, no Fastboot, no PC just have the TWRP installer file I linked so you don't lose TWRP.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
oh yes, definitely doing that next time. thanks!! i found this post thats exactly your method in a little less words.
https://forum.xda-developers.com/es...1-1-nmj20d-t3701681/post78194778#post78194778
Jeebus...
We didn't like the other 15 goddamn threads with the same topic...
XDA is cancer
what works for me at the time to flash the patched image was
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
note: i am on pie
thanks for the guide.
Really helped lots, thank you.
January update is out, who might like to patch boot.img with TWRP and Magisk?
kma_29 said:
January update is out, who might like to patch boot.img with TWRP and Magisk?
Click to expand...
Click to collapse
Go to the stock room thread
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
OP, if you want to avoid having to sideload the whole OTA, you can have it done directly by your phone by flashing the stock boot image for the current version that you are one and then updating from the settings (or notification). Then just continue with flashing the rooted boot image for the new update. I feel like that is safer than both TWRP and sideloading the full OTA (in reference to keeping data safe).
https://forum.xda-developers.com/showpost.php?p=76828139&postcount=1264
morphius88 said:
OP, if you want to avoid having to sideload the whole OTA, you can have it done directly by your phone by flashing the stock boot image for the current version that you are one and then updating from the settings (or notification). Then just continue with flashing the rooted boot image for the new update. I feel like that is safer than both TWRP and sideloading the full OTA (in reference to keeping data safe).
https://forum.xda-developers.com/showpost.php?p=76828139&postcount=1264
Click to expand...
Click to collapse
Thanks
@bmg1001 are you still providing the stock boot images on your google drive. I am looking for the Feb stock boot image or can someone tell me how to get it. I tried extracting from the Feb OTA but did not see it listed in that zip
jionny said:
@bmg1001 are you still providing the stock boot images on your google drive. I am looking for the Feb stock boot image or can someone tell me how to get it. I tried extracting from the Feb OTA but did not see it listed in that zip
Click to expand...
Click to collapse
Yep, I have it in the same Google Drive folder where the other month's images are posted.
bmg1001 said:
Yep, I have it in the same Google Drive folder where the other month's images are posted.
Click to expand...
Click to collapse
Sorry chalk that up to me not paying attention. I was looking for it after Jan but its actually the first one listed. Thanks!
bmg1001 said:
Yep, I have it in the same Google Drive folder where the other month's images are posted.
Click to expand...
Click to collapse
Hi one more thing, this is my third time updating and rooting via this method. The last two times worked flawlessly however this time I did update the OTA but when I try to reroot and go to adb devices I see my phone listed then when I reboot recovery it does however when I try fastboot devices my phone does not show and nothing happens, any help will be appreciated
Found this while trolling through the Chinese forums, none of this is my work, I have translated the instructions as best I can.
Disclaimers; I have not tried this, it may brick the global rom, the custom recovery is likely only in Chinese language.
You need:
Boot Loader unlock code (currently probably not possible to get)
Huawei USB drivers
Recovery image (attached)
Magisk package (attached)
files: https://mega.nz/#!PM0EmYLA!384hZjmJ9ExNc7Q8rSqssHunWSO7AxQ3GA4qet6RX4E
Extract files to a folder, open command prompt and change into this folder.
Unlock bootloader (BL unlock will clear the phone data, please do a backup)
- Obtain an official unlock code
- double-click to open the "Huawei Toolbox.exe"
- click "unlock bootloader "
- enter the unlock code in the pop up window , click OK, and wait for the phone to unlock complete restart.
Flash the third-party recovery
- Turn off the phone and connect the computer. Press and hold the “Volume Down” button and “Power button” until the phone displays the android page and release your finger.
- open command prompt and run:
fastboot flash recovery_ramdisk twrp.img
- after seeing the two OKAY feedback from the command line, the flash is successful.
Enter recovery to flash root image (this step will clear all data of the mobile phone including memory card, please make a backup in advance)
- long press “Volume Up” and “Power” ", until you see the a twrp logo, release the keys and wait to enter recovery mode
- After entering recovery, click the second item “Clear”, click “Format Data Partition” in the lower left corner, slide the slider to enter the clear, wait for the progress bar to complete
- Return to the recovery homepage, click on the last item "Advanced", select the last item "Remove data forced encryption", slide the slider to release, wait for completion
Copy the root package to the phone
- In Command Prompt type or copy the following commands
adb push magisk-installer.zip /sdcard
adb push magisk.apk /sdcard
Install Image
- Whilst still in recovery mode, click the first item to install the magisk-installer.zip package from the sdcard , slide the slider to install, wait for the flash to complete, and restart the phone
- After reboot is complete, click “File Manager”, select the apk file “magisk.apk” just copied from the memory card when install is finished, open the magisk app and click “No, thank you” in the pop-up window
- Return to the command line tool, type the code to execute, and wait for the phone to automatically restart
Fastboot reboot recovery
- after the restart, open "magisk", it should show that the installation is complete, that is, ROOT is achieved.
Anything in that forum on how to manually update phone?
technotika said:
Anything in that forum on how to manually update phone?
Click to expand...
Click to collapse
That is actually what I was looking for
But none, problem is the v20 (china version) seems to get OTA way before us, they all got v143 2 weeks ago.
I did find the menu to do it, but it only supports if the image is stored on an sdcard, and when I click it it says no sdcard found. so its impossible.
Tried same with similar results. One day eh? ?
İ have V20 chinese version. İ want to root but could not find a way. Can you share the chinese forum maybe i can find how to unlock bootloader
greenblueye said:
İ have V20 chinese version. İ want to root but could not find a way. Can you share the chinese forum maybe i can find how to unlock bootloader
Click to expand...
Click to collapse
If you read what I wrote in the first post you would see you cannot root without a bootloader unlock code.
Tested! Work bootloader code on Russia services (Cost 20USD)
belam00r said:
Tested! Work bootloader code on Russia services (Cost 20USD)
Click to expand...
Click to collapse
Nice! Did unlocking bootloader factory reset your device?
Yes of course. All new Huawei and Honor do a reset after unlocking
i get bootloader unlock code from funkiehuwai for 20$
any one tried this instructions and have success?
I just wonder comments below will work?
*adb push magisk-installer.zip /sdcard
*adb push magisk.apk /sdcard
because there is no sd card support for view20?
when i opened huawei-toolbox.exe its in chinese and im afraid to continue other instructions
Did anyone use TWRP and which version?
Did the View 20 Boot correctly?
I read in a Forum, that with the view 20 doesn´t boot correctyl with TWRP. The reason should bei the Storage...
Best regards
Unlocked Bootloader
belam00r said:
Tested! Work bootloader code on Russia services (Cost 20USD)
Click to expand...
Click to collapse
Does that mean you rooted you device (with the files from above) or you just unlocked the bootloader?
I was able to unlock my bootloader with a code from funkyhuawei (about 18 €, site seems to be down currently). I did not use the unlock tool above, mainly because its chinese
- Enabled "USB debugging" and "OEM unlock" in developer settings
- Connected phone to PC, opened adb and used "adb reboot bootloader"
- Unlocked via "fastboot oem unlock *16digit code*"
This worked out fine. However, as far as i understand it magisk is installed over twrp (recovery_ramdisk), removing twrp but granting you root. This makes me kind of nervous since twrp has been a nice safety net on several occasions. This is why I stopped after unlocking the bootloader. Maybe someone has more experience on this? Why is there so little interest in rooting this phone?
Regards
root achieved
I don't know if nobody's interested or nobody wants to try rooting this phone. However, I just went ahead and tried it. I used this guide: https://topjohnwu.github.io/Magisk/install.html#emui-9 (posted in https://forum.xda-developers.com/honor-view-20/help/root-t3900266). https://androidhost.ru/search.html is were I got the firmware from (posted in https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). I downloaded the 9.0.1.137 firmware, since this corresponds to the one currently installed on my phone.
In summary:
I extracted recovery_ramdis.img from the update.app with the huawei extractor. In order to see this image file, I had to uncheck "verify header checksum" under settings->extract.
I then transferred this file to my phone (download folder), downloaded newest magisk manager and installed it. I then pushed INSTALL next to magisk (which was not installed of course), Install again and then Patch boot image file. Choose your transferred recovery_ramdis.img and go ahead. Transfer patched file (now called patched_boot.img) back to PC.
For the next step, bootloader has to be unlocked already! Turn on "Enable OEM unlock" and "USB debugging" in the developer options and reboot to fastboot. Open ADB as usual and connect cable to phone. Type "fastboot flash recovery_ramdisk *path to patched_boot.img*" and wait for success.
A few things to keep in mind:
-Had a bootloop with the newest version of the viper4android module!
-The root was done without custom recovery, therefore a magisk module leading to a bootloop requires you to factory reset and do everything again if you want root to work (at least i couldn't get it to work again by reflashing orginial recovery_ramdis.img followed by patched_boot.img).
-For rooting to work you have to boot phone to recovery (in this case resulting in a "normal boot"). This means pressing volume up and holding it when booting the phone. For restart you could use an app which lets you boot to recovery automatically.
-While the above my sound annoying, permanently gives you the chance to boot you phone unrooted. This is nice, especially when you have a bootloop due to a magisk module (which I had).
-According to the first link, you could install a custom recovery into the second recovery partition of Huawei/Honor devices (erecovery_ramdis). there is no official twrp available for Honor View 20 at the moment.
-After unlocking my bootloader (see post above) I had "device not verified" in google play store. After rooting, my device is verified again
Regards
garris_bibop said:
I don't know if nobody's interested or nobody wants to try rooting this phone. However, I just went ahead and tried it. I used this guide: https://topjohnwu.github.io/Magisk/install.html#emui-9 (posted in https://forum.xda-developers.com/honor-view-20/help/root-t3900266). https://androidhost.ru/search.html is were I got the firmware from (posted in https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). I downloaded the 9.0.1.137 firmware, since this corresponds to the one currently installed on my phone.
In summary:
I extracted recovery_ramdis.img from the update.app with the huawei extractor. In order to see this image file, I had to uncheck "verify header checksum" under settings->extract.
I then transferred this file to my phone (download folder), downloaded newest magisk manager and installed it. I then pushed INSTALL next to magisk (which was not installed of course), Install again and then Patch boot image file. Choose your transferred recovery_ramdis.img and go ahead. Transfer patched file (now called patched_boot.img) back to PC.
For the next step, bootloader has to be unlocked already! Turn on "Enable OEM unlock" and "USB debugging" in the developer options and reboot to fastboot. Open ADB as usual and connect cable to phone. Type "fastboot flash recovery_ramdisk *path to patched_boot.img*" and wait for success.
A few things to keep in mind:
-Had a bootloop with the newest version of the viper4android module!
-The root was done without custom recovery, therefore a magisk module leading to a bootloop requires you to factory reset and do everything again if you want root to work (at least i couldn't get it to work again by reflashing orginial recovery_ramdis.img followed by patched_boot.img).
-For rooting to work you have to boot phone to recovery (in this case resulting in a "normal boot"). This means pressing volume up and holding it when booting the phone. For restart you could use an app which lets you boot to recovery automatically.
-While the above my sound annoying, permanently gives you the chance to boot you phone unrooted. This is nice, especially when you have a bootloop due to a magisk module (which I had).
-According to the first link, you could install a custom recovery into the second recovery partition of Huawei/Honor devices (erecovery_ramdis). there is no official twrp available for Honor View 20 at the moment.
-After unlocking my bootloader (see post above) I had "device not verified" in google play store. After rooting, my device is verified again
Regards
Click to expand...
Click to collapse
Well done good job:good:
İ have chinese version PCT-AL10 9.0.1.144 right now. Do you think i can use the same way? İ wonder from which version to extract recovery_ramdis.img
I have my view20 rooted
Thanks for the instructions.
greenblueye said:
I have my view20 rooted
Thanks for the instructions.
Click to expand...
Click to collapse
You're welcome Be careful with sound improvement modules in Magisk! Had another bootloop with the Zirene module...
Which firmware did you get the recovery_ramdisk from in the end?
garris_bibop said:
You're welcome Be careful with sound improvement modules in Magisk! Had another bootloop with the Zirene module...
Which firmware did you get the recovery_ramdisk from in the end?
Click to expand...
Click to collapse
I get recovery-ramdisk from firmware PCT-AL10 9.0.1.129 . my phone is on version 9.0.1.144 but it worked:good:
After root i can not auto update software. 9.0.1.166 version is seen on ota but after download it says update is unsuccessful. Do you have any suggestion?
I think thats to be expected when rooted. Go for manual update I guess (https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). Personally I wouldn't bother with every update unless theres interesting new features and/or security updates. just to be on the safe side I would reflash the original recovery_ramdisk before updating! And backup your data!
NM Card
Hello !
Unless I'm mistaken, the View20 must be able to use nano sd cards (NM Card)
I'm pleased to report I've successfully done systemless root with MAGISK on the Ulefone Armor 11 5G. Turns out the process is nearly identical to the Armor 10.
Most of the information I found on this thread
First of all you need to unlock the bootloader, you can found how to do it on my previous post. Unlocking the bootloader will erase all of your data and will probably void your garanties.
I'm not responsable of any damage your phone can receive doing this procedure.
After unlocking the bootloader, everytime you switch on the phone there will be a message informing you that the bootloader is unlocked and so the phone not safe anymore.
Assuming you have done it without problem you need:
- The latest SDK Platform Tools to download Adb and Fastboot. Remember that are command line software, so the run only through command prompt
- The latest version of Magisk, in this moment is the 22.1.
- The USB driver, but you should already have downloaded it to unlock bootloader
- The latest ROM version, that you can download from Ulefone Site, here the UE and Not-UE version
- A copy of vbmeta_null.img as found here. VERY IMPORTANT
Let's start rooting your phone.
- Extract boot.img from the ROM and copy it on your phone in a directory you can easily remember (i.e. Download, Bluetooth...)
- Download or copy Magisk on the phone and install it. If it ask to install from unknown source accept it.
- Open Magisk app and choose Install Magisk NOT the App. When prompted for the method, choose "Select and patch a file". It will ask you to indicate where you have stored the copy of boot.img that you have previously stored on the phone. It will produce a file magisk_patched_xxxxx.img where xxxxx is a casual number.
- Copy magisk_patched_xxxxx.img on your PC, I will suggest the same location of Adb
- Now you have to reboot in bootloader mode by opening command prompt in adb location and run:
adb reboot bootloader
Click to expand...
Click to collapse
- When done verify the connection with the phone:
fastboot devices
Click to expand...
Click to collapse
If you have received a positive answer we can go further otherwise check that you have the right driver installed.
- Let's assume you have received a positive answer. Now you have to disable the safety check of the boot.img otherwise you will have a bootloop:
fastboot flash vbmeta vbmeta_null.img
Click to expand...
Click to collapse
If you receive a positive answer we can go to next step
- Install patched Boot Image:
fastboot flash boot magisk_patched_xxxxx.img
Click to expand...
Click to collapse
naturally, replace the X's with whatever string of characters Magisk supplied
- Assuming everything went good you can reboot your phone:
fastboot reboot
Click to expand...
Click to collapse
Done now your phone should be now rooted.
Enjoy.
Have fun
Thanks for this, I was missing the vbmeta_null.img and was getting a boot cycle. Works perfectly.
Harlock1978 said:
I'm pleased to report I've successfully done systemless root with MAGISK on the Ulefone Armor 11 5G. Turns out the process is nearly identical to the Armor 10.
Most of the information I found on this thread
First of all you need to unlock the bootloader, you can found how to do it on my previous post. Unlocking the bootloader will erase all of your data and will probably void your garanties.
I'm not responsable of any damage your phone can receive doing this procedure.
After unlocking the bootloader, everytime you switch on the phone there will be a message informing you that the bootloader is unlocked and so the phone not safe anymore.
Assuming you have done it without problem you need:
- The latest SDK Platform Tools to download Adb and Fastboot. Remember that are command line software, so the run only through command prompt
- The latest version of Magisk, in this moment is the 22.1.
- The USB driver, but you should already have downloaded it to unlock bootloader
- The latest ROM version, that you can download from Ulefone Site, here the UE and Not-UE version
- A copy of vbmeta_null.img as found here. VERY IMPORTANT
Let's start rooting your phone.
- Extract boot.img from the ROM and copy it on your phone in a directory you can easily remember (i.e. Download, Bluetooth...)
- Download or copy Magisk on the phone and install it. If it ask to install from unknown source accept it.
- Open Magisk app and choose Install Magisk NOT the App. When prompted for the method, choose "Select and patch a file". It will ask you to indicate where you have stored the copy of boot.img that you have previously stored on the phone. It will produce a file magisk_patched_xxxxx.img where xxxxx is a casual number.
- Copy magisk_patched_xxxxx.img on your PC, I will suggest the same location of Adb
- Now you have to reboot in bootloader mode by opening command prompt in adb location and run:
- When done verify the connection with the phone:
If you have received a positive answer we can go further otherwise check that you have the right driver installed.
- Let's assume you have received a positive answer. Now you have to disable the safety check of the boot.img otherwise you will have a bootloop:
If you receive a positive answer we can go to next step
- Install patched Boot Image:
naturally, replace the X's with whatever string of characters Magisk supplied
- Assuming everything went good you can reboot your phone:
Done now your phone should be now rooted.
Enjoy.
Have fun
Click to expand...
Click to collapse
it works for me ... thanks!!!!
They will release an update with Android 11 for Armor 11 this summer, should i wait for that or is it just to root on? Sincerly the n00b
morwlin said:
They will release an update with Android 11 for Armor 11 this summer, should i wait for that or is it just to root on? Sincerly the n00b
Click to expand...
Click to collapse
Did you update to android11. What are your findings? Android 11 good? bugs?
So let's say I tried the steps above and I somehow ended in a boot loop. For reference, I removed the OS and had TWRP Recovery installed. I restarted while on TWRP Recovery from the phone and I been stuck on Boot Loop since. For whatever reason, for the life of me, I can't remove the battery or figure out how to enter Recovery Mode (I tried so many combinations).
Anyone know how to get into Recovery Mode or find a way to get out of this boot loop? =(
PS: These were the last steps I did:
1) adb reboot-fastboot
2) --- Reboot to bootloader
3) fastboot flash vbmeta vbmeta_null.img
4) fastboot flash recovery recovery.img (The TWRP img)
5) fastboot flashing unlock
6) - Reboot from TWRP on phone after browsing around
dummiedroid said:
So let's say I tried the steps above and I somehow ended in a boot loop. For reference, I removed the OS and had TWRP Recovery installed. I restarted while on TWRP Recovery from the phone and I been stuck on Boot Loop since. For whatever reason, for the life of me, I can't remove the battery or figure out how to enter Recovery Mode (I tried so many combinations).
Anyone know how to get into Recovery Mode or find a way to get out of this boot loop? =(
PS: These were the last steps I did:
1) adb reboot-fastboot
2) --- Reboot to bootloader
3) fastboot flash vbmeta vbmeta_null.img
4) fastboot flash recovery recovery.img (The TWRP img)
5) fastboot flashing unlock
6) - Reboot from TWRP on phone after browsing around
Click to expand...
Click to collapse
Well since this post, I just basically let my phone battery die. With a clear mind, and some help from here (https://forum.xda-developers.com/t/...h-stock-unlock-boot-loader-root-twrp.4297803/) I was able to save the phone (yay!).
I got the ROM and MPD from here: https://www.ulefone.com/support/software-download.html which lead me to their drive for Ulefone Armor 11 5G here: https://drive.google.com/drive/folders/12N1nQVACM4noSO4klyrOk0-sfEnTWMRN
1) Download ROM, SP_MDT_AFterSale_20.32.rar and PDF (RAR and PDF in the "Upgrade tools and USB driver" folder)
2) Follow the steps on the PDF which basically said to scan the port, add the scatter file then start the update. (Read full PDF before trying it)
Hopefully if anyone is frustrated out there, this helps. (I know I was not thinking rationally... lol)
PS: The drive said it might brick your phone with Android 11 but mine worked with Android 11. No issues. So good luck!
Harlock1978 said:
I'm pleased to report I've successfully done systemless root with MAGISK on the Ulefone Armor 11 5G. Turns out the process is nearly identical to the Armor 10.
Most of the information I found on this thread
First of all you need to unlock the bootloader, you can found how to do it on my previous post. Unlocking the bootloader will erase all of your data and will probably void your garanties.
I'm not responsable of any damage your phone can receive doing this procedure.
After unlocking the bootloader, everytime you switch on the phone there will be a message informing you that the bootloader is unlocked and so the phone not safe anymore.
Assuming you have done it without problem you need:
- The latest SDK Platform Tools to download Adb and Fastboot. Remember that are command line software, so the run only through command prompt
- The latest version of Magisk, in this moment is the 22.1.
- The USB driver, but you should already have downloaded it to unlock bootloader
- The latest ROM version, that you can download from Ulefone Site, here the UE and Not-UE version
- A copy of vbmeta_null.img as found here. VERY IMPORTANT
Let's start rooting your phone.
- Extract boot.img from the ROM and copy it on your phone in a directory you can easily remember (i.e. Download, Bluetooth...)
- Download or copy Magisk on the phone and install it. If it ask to install from unknown source accept it.
- Open Magisk app and choose Install Magisk NOT the App. When prompted for the method, choose "Select and patch a file". It will ask you to indicate where you have stored the copy of boot.img that you have previously stored on the phone. It will produce a file magisk_patched_xxxxx.img where xxxxx is a casual number.
- Copy magisk_patched_xxxxx.img on your PC, I will suggest the same location of Adb
- Now you have to reboot in bootloader mode by opening command prompt in adb location and run:
- When done verify the connection with the phone:
If you have received a positive answer we can go further otherwise check that you have the right driver installed.
- Let's assume you have received a positive answer. Now you have to disable the safety check of the boot.img otherwise you will have a bootloop:
If you receive a positive answer we can go to next step
- Install patched Boot Image:
naturally, replace the X's with whatever string of characters Magisk supplied
- Assuming everything went good you can reboot your phone:
Done now your phone should be now rooted.
Enjoy.
Have fun
Click to expand...
Click to collapse
Hi, does the VBmeta work for all models? I am trying to root my Ulefone Power Armor 13.
It should, because iy's an empty file.
Harlock1978 said:
It should, because iy's an empty file.
Click to expand...
Click to collapse
Just tried it and it works great! Any idea anyone where I can get TWRP for Ulefone Armor 13? This phone has the recovery in the boot partition
Will this work with Android 11?
I forgot to update my progress. Works great on R (11) so far. Lots of modules seem to be updated too. I am considering using a custom ROM and finally disconnecting from GMS though I would like to retain the customised camera app for,the night vision. I will find a thread that might have a way to do this though if anyone here can help me or point me to the right place, would be much abliged. Also, any ROM recommendations, that are working best?
Lenovo Tab P11 (2021г.) - Обсуждение - 4PDA
Lenovo Tab P11 (2021г.) - Обсуждение, Планшет, 11"
4pda.to
Translator from Russian: https://www.deepl.com/translator
Basically
1. Enable OEM Unlock in Developers Settings
2. (Your host PC should have LMSA installed) Open command window, and go to where ADB is
3. Turn your tablet off. Press and hold volume down and power buttons to enter bootloader
4. Enter the following in command window
Code:
fastboot flashing unlock
. Answer yes to unlock bootloader
warning: your tablet is wiped during the process!!![/B]
5. Reboot
To root, patch boot with Magisk
You can use LMSA to download matching ROM, and use rescue to update ROM if necessary. You can get needed boot at c:/program data/LMSA/download/romfiles/
Copy boot.img to your phone and use Magisk to patch, and copy patched_boot.img back to host computer.
Turn your tablet off and enter bootloader
Switch to fastbootd
Code:
fastboot reboot fastboot
Flash the patched boot
Code:
fastboot flash boot
Press spacebar once and drag and drop the patched boot onto command window, and press enter
Reboot
does this work with Lenovo Pad Pro 2021 (SD870) ?
Thanks for the guide, I've successfully unlocked the bootloader and rooted with Magisk.
I also installed the unofficial TWRP from here: https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j606f/
However I didn't flash the provided vbmeta.img and everything still seems to be working fine, including booting into TWRP.
Anyone know if not flashing it may cause issues to appear?
The reason I didn't flash it is because someone else on another thread here said they got stuck in a boot loop after flashing it and that after restoring they decided not to flash it and everything worked fine, which seems to be my experience too, but maybe there are implications I'm not aware of with not flashing it.
I had this issue too, I had to run the command:
Code:
fastboot flashing unlock
aurelienlux said:
Thanks for the guide, I've successfully unlocked the bootloader and rooted with Magisk.
I also installed the unofficial TWRP from here: https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j606f/
However I didn't flash the provided vbmeta.img and everything still seems to be working fine, including booting into TWRP.
Anyone know if not flashing it may cause issues to appear?
The reason I didn't flash it is because someone else on another thread here said they got stuck in a boot loop after flashing it and that after restoring they decided not to flash it and everything worked fine, which seems to be my experience too, but maybe there are implications I'm not aware of with not flashing it.
Click to expand...
Click to collapse
I flashed vbmeta.img and now I can't boot into system/fastboot/recovery. Do you know how to restore ? I also tried LMSA, device cannot be detected.
cyatsl said:
I flashed vbmeta.img and now I can't boot into system/fastboot/recovery. Do you know how to restore ? I also tried LMSA, device cannot be detected.
Click to expand...
Click to collapse
DO IT ON YOUR OWEN RISK! I HAVE NOT TESTED ON A LENOVO TAB P11 YET!
These are the steps for rooting a Lenovo Tab M8 FHD!
I think essential are the points 19 to 21, to flash the boot.img ONCE AGAIN after vbmeta.img.
It discribes ... this part is key, otherwise you'll bootloop!
Fully charge tablet
Turn tablet on
Skip as much of the initial setup process as possible, however you MUST be connected to the WiFi in order to allow unlocking of your bootloader (Start -> More/Accept -> no wifi/Set-Up Offline -> skip setting current time set -> Choose reporting options / Hit Accept -> Skip Pin -> Skip Lenovo ID -> Lenovo User Experience Program (choose if you want to skip or not) -> Choose navigation etc) Get to the home screen
Swipe down from top of screen and open Settings
Developer Tools (enable dev tools if you don't yet have access) -> Enable USB Debugging
Developer Tools -> Enable OEM Unlocking (again, if you're not on WiFi, it may not allow you to do this)
Connect tablet usb and usb to computer (Click "allow" when the usb debugging popup comes up)
./adb devices (Make sure the computer can see the tablet)
./adb reboot bootloader
./fastboot devices (Make sure the computer can see the tablet)
./fastboot flashing unlock then press volume-up on the device
./fastboot reboot`
On the Lenovo loading splash screen, you should now get the Orange State alert that the device is unlocked. It may take a bit to reboot as you've just wiped all data again and it must do initial setup
Device boots up normally. Now you can do real setup steps if you like, or you can ignore everything like in Step 3 above.
Enable USB Debugging again (Step 4-5)
Grab the boot.img and vbmeta.img from the LMSA TB_8505FS_S300025_201015_BMP update. Copy the boot.img to the tablet, taking note of the location (e.g., ./adb push boot.img /sdcard/)
Install latest version of Magisk Manager (doesn't need to be the Canary version, can be the regular version) and patch the boot image.
Clicked on "Install" on the righthand top in magisk manager
Clicked on "Next" Righthand top.
Selected "Select and Patch a File".
picked the boot.img file I had copied in step 1. Take note of the location of the patched image (magisk_patched.img), and copy it to your PC.
Reboot into bootloader again (./adb reboot bootloader)
Flashed the magisk patched boot.img ./fastboot flash boot path/to/magisk_patched.img
Flash the VB meta with the disable-verification flag ./fastboot --disable-verification flash vbmeta path/to/vbmeta.img
Flashed the magisk patched boot.img AGAIN!!!!!! (this part is key, otherwise you'll bootloop) ./fastboot flash boot path/to/magisk_patched.img
Reboot, you should now be rooted (can confirm in Magisk Manager) ./fastboot reboot
Is it ok/safe to flash this to TB-J606L?
It is the same model but with sim card and 4G.
Sometimes WiFi vs 4G models have the same software and detect differences on startup and sometimes not... Not sure about this model. I would prefer to not (soft)brick it.
Hi there. First time boot-unlocker needing help. I also have the P11 TB-J606F and would like to root it. I believe I need to do this first. I cannot seem to get any response from the tablet when doing this. In "regular tablet" mode I can connect and do ADB-commands, but in this "bootloader" mode I cannot seem to connect. I just get "Waiting for any device"
Could it be a driver issue? In device manager there is an Android device with an exclamation mark? I have no clue how to update this? Automatic doesn't work and I can't seem to find any drivers that work. I am not sure if this indeed is the problem, but you know - help needed, please.
skodkassen said:
Hi there. First time boot-unlocker needing help. I also have the P11 TB-J606F and would like to root it. I believe I need to do this first. I cannot seem to get any response from the tablet when doing this. In "regular tablet" mode I can connect and do ADB-commands, but in this "bootloader" mode I cannot seem to connect. I just get "Waiting for any device"
Could it be a driver issue? In device manager there is an Android device with an exclamation mark? I have no clue how to update this? Automatic doesn't work and I can't seem to find any drivers that work. I am not sure if this indeed is the problem, but you know - help needed, please.
Click to expand...
Click to collapse
Not sure if it helps. I had a similar issue with my Lenovo Tab M8 FHD.
The big issue was to get the android driver for win10, fastboot was not working. I found it under win10 update >> optional updates >>driver updates >> there was a medi.... as installable update. Afterthem fastboot was working fine.
sc00ter98 said:
Not sure if it helps. I had a similar issue with my Lenovo Tab M8 FHD.
The big issue was to get the android driver for win10, fastboot was not working. I found it under win10 update >> optional updates >>driver updates >> there was a medi.... as installable update. Afterthem fastboot was working fine.
Click to expand...
Click to collapse
And thus my problems were solved. It took me a few hours going nowhere and thanks to you everything is now cool
sc00ter98 said:
Not sure if it helps. I had a similar issue with my Lenovo Tab M8 FHD.
The big issue was to get the android driver for win10, fastboot was not working. I found it under win10 update >> optional updates >>driver updates >> there was a medi.... as installable update. Afterthem fastboot was working fine.
Click to expand...
Click to collapse
Solution
Download and install LMSA and use Motorola ADB driver Device Manager
You should see P11 with no driver. Update driver > Let me choose > Android ADB > choose Motorola ADB driver
aurelienlux said:
Thanks for the guide, I've successfully unlocked the bootloader and rooted with Magisk.
I also installed the unofficial TWRP from here: https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j606f/
However I didn't flash the provided vbmeta.img and everything still seems to be working fine, including booting into TWRP.
Anyone know if not flashing it may cause issues to appear?
The reason I didn't flash it is because someone else on another thread here said they got stuck in a boot loop after flashing it and that after restoring they decided not to flash it and everything worked fine, which seems to be my experience too, but maybe there are implications I'm not aware of with not flashing it.
Click to expand...
Click to collapse
Be aware: The link above is not the right TWRP for the P11 Pro. I lost two days an bricked my tablet to find out that. The TWRP for P11 Pro is at https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j706f/
37_ said:
does this work with Lenovo Pad Pro 2021 (SD870) ?
Click to expand...
Click to collapse
Did you try it ? I think this method can work on Pad Pro 2021 SD870
mingkee said:
Basically
1. Enable OEM Unlock in Developers Settings
2. (Your host PC should have LMSA installed) Open command window, and go to where ADB is
3. Turn your tablet off. Press and hold volume down and power buttons to enter bootloader
4. Enter the following in command window
Code:
fastboot flashing unlock
. Answer yes to unlock bootloader
warning: your tablet is wiped during the process!!![/B]
5. Reboot
Click to expand...
Click to collapse
does work with me . it repeat the same error:
C:ladb>adb reboot bootloader
error: device '(null)' not found
Two questions:
1. Did anyone lose their Widevine level when unlocking, installing Magisk and/or rooting? I currently have L1 and would hate to lose that (to L3).
2. Is it possible to use the TWRP version for the TB-J706F for the TB-J716F as well? Basically, they are very similar devices, but the screen (90 Hz OLED) and processor (Snapdragon 870 instead of Snapdragon 730G) are different, but I don't know what is relevant for TWRP. Otherwise, could I also root without TWRP?
Thanks in advance!
HANN1860BAL said:
Two questions:
1. Did anyone lose their Widevine level when unlocking, installing Magisk and/or rooting? I currently have L1 and would hate to lose that (to L3).
2. Is it possible to use the TWRP version for the TB-J706F for the TB-J716F as well? Basically, they are very similar devices, but the screen (90 Hz OLED) and processor (Snapdragon 870 instead of Snapdragon 730G) are different, but I don't know what is relevant for TWRP. Otherwise, could I also root without TWRP?
Thanks in advance!
Click to expand...
Click to collapse
1. Yes you will lose L1 when unlock bootloader
2. No , TWRP with very different hardware so don't hope so much .
I see there is no reason to root TB-J716F now, current firmware is stable and smooth
luizkun said:
1. Yes you will lose L1 when unlock bootloader
2. No , TWRP with very different hardware so don't hope so much .
I see there is no reason to root TB-J716F now, current firmware is stable and smooth
Click to expand...
Click to collapse
Thanks for the fast reply!
Is it possible to lock bootloader after rooting again and gaining L1 back with keeping device rooted?
That's true, but I want to use some rooted apps, like Titanium Backup and AdAway ;-)
HANN1860BAL said:
Thanks for the fast reply!
Is it possible to lock bootloader after rooting again and gaining L1 back with keeping device rooted?
That's true, but I want to use some rooted apps, like Titanium Backup and AdAway ;-)
Click to expand...
Click to collapse
you can root after unlock bootloade by patching boot.img from stock rom (by magisk ) and install magisk without TWRP
Rooting the Pixel 6a is just about as easy as any other factory unlocked pixel, but because so many people have had issues with unlocking their bootloaders, I figured I'd post my exact personal steps I took when a Pixel 6a came into my tech shop to be rooted, and I discovered the current bug with Rooting
What You'll Need:
- June 2022 Firmware OTA Update Installed at least: Do this on device. Do Not download the OTA update from google's firmware website.
- ADB/Fastboot/Google Drivers for Windows: I use this to install- ADB 15sec Installer
- Magisk Manager APK: Github - Magisk Github Releases
- Firmware Matching Currently Installed: Google FW page - Google Official Firmware Downloads - you need this for the boot.img file
- A Windows Computer
- A USB-C cable to connect to your phone to the computer
OEM Unlock Bug
With early units sold by Google, they're shipping with a bug where OEM Unlock stays grayed out. Here's the only way I got around this issue
1.) Log out of any Google Account on the device
2.) Connect to Wifi, check for updates without your sim card in the device. There is a bug where it will potentially download the update for your carrier sim
3.) At minimum, you should get the June 2022 security patch update. Run the update and remember which update it is for when you download the firmware to get boot.img
4.) When the update is finished, Factory Reset your device either from settings or Android recovery
5.) Go through Android setup without sim card in, and don't connect to wifi, finish setup without logging into a google account or anything
6.) When setup is done, connect to wifi and put your sim back in.
7.) Pay attention in your notifications for "Preparing your Device" notification.
8.) When that notification pops up, enable Developer options (tap build number a bunch of times)
9.) OEM Unlock should be possible to enable now. Also enable USB Debugging
Pre-Root Setup
1.) Install Magisk Manager from Github
2.) Use 7zip (or any other ZIP opening program) to extract the boot.img from your firmware download from google
-- the boot.img is inside another zip file that's in the download from google. very easy to get
3.) Put the Boot.img on your phones internal storage
4.) Open Magisk Manager, and select your Boot.img from internal storage. Patch the boot.img to make it a rooted boot.img
5.) With your phone connected to the computer, move the magisk_patched.img from sdcard/downloads to your computer
6.) If USB debugging is properly enabled, now you can open CMD and reboot to bootloader with
Code:
adb reboot bootloader
Unlocking the bootloader
1.) With the device connected, OEM Unlock enabled, and booted to bootloader, you can unlock the bootloader with the following command
Code:
fastboot flashing unlock
-- If nothing changes on your phone screen, use Device Manager to make sure the device is recognized via google drivers: vid here on that - Quick Fastboot Drivers Install Tutorial
2.) On your phone, use the volume keys to select Unlock Bootloader, then hit the power button, device should reboot back to bootloader
3.) flash the boot partition with the magisk patched boot.img
Code:
fastboot flash boot magisk_patched.img
4.) Now you can reboot back into your device and you should be rooted!
Code:
fastboot reboot
Congrats! Now you're bootloader unlocked and rooted! GrapheneOS is already available if you want a degoogled rom, haven't seen another rom pop up yet
all done from there
updating your device when rooted
I do not have a pixel 6a specifically for this right now to confirm this will work, but on every other device with OTA's, this has been my process.
1.) Download your OTA using the system update part of Settings
2.) When it pops up and is ready to restart to finish installing the update, DO NOT CLICK RESTART IN SETTINGS/SYSTEM UPDATE
3.) Go to Magisk Manager, and select Install next to Magisk
4.) Select "Install to Inactive Slot (After OTA)
5.) When its done patching the boot partition, hit restart in Magisk
Your OTA Update is now rooted
To save time and effort here is the magisk patched boot.img for June 2022 patch level, Carrier Unlocked 6a from the Google Store. Make SURE you are on build SD2A.220601.003 before flashing!
To get the `OEM Unlock` option in Developer Options to work, it's simpler to just manually flash 12.1.0 (SD2A.220601.004, Jun 2022, Verizon, Verizon MVNOs) and then wipe.
Even though it's label as Verizon, it should work for all carriers.
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
jejemc said:
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
Click to expand...
Click to collapse
Correct, though I would probably fastboot boot first just to make sure it boots up ok. When it does you can reboot to recovery and flash it.
these instructions sound like "the usual process", but for the 6a isn’t there something to patch regarding vbmeta as well?
(never had a phone that "needed" this, but in my understanding it "should" be necessary with the 6a? won’t have time to try out myself before the weekend, just asking ..)
ctfrommn said:
Correct, though I would probably fastboot boot first just to make sure it boots up ok. When it does you can reboot to recovery and flash it.
Click to expand...
Click to collapse
here it is and does and works perfectly well thank you for everything.
Im starting work on my custom kernel now so hopefully MVK for Bluejay will be ready in the coming days/weeks.
Zaxx32 said:
To save time and effort here is the magisk patched boot.img for June 2022 patch level, Carrier Unlocked 6a from the Google Store. Make SURE you are on build SD2A.220601.003 before flashing!
Click to expand...
Click to collapse
As this thread ages, not everyone will have the June 2022 update. That's why I suggested/put the steps in to do it themselves with matching firmware to what their device is on.
benji said:
To get the `OEM Unlock` option in Developer Options to work, it's simpler to just manually flash 12.1.0 (SD2A.220601.004, Jun 2022, Verizon, Verizon MVNOs) and then wipe.
Even though it's label as Verizon, it should work for all carriers.
Click to expand...
Click to collapse
This DID NOT work for me. That's why I wrote this up the way I did.
jejemc said:
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
Click to expand...
Click to collapse
If you're bootloader is already unlocked, you just have to flash the patched magisk boot img, correct. I wrote this up for those having issue with not having the ability even if it is an unlocked from google device
frank93 said:
these instructions sound like "the usual process", but for the 6a isn’t there something to patch regarding vbmeta as well?
(never had a phone that "needed" this, but in my understanding it "should" be necessary with the 6a? won’t have time to try out myself before the weekend, just asking ..)
Click to expand...
Click to collapse
Correct, these are basically the usual steps. There's nothing regarding vbmeta flashing in this case of just rooting stock firmware. You only need to do that with ROMs (GSI's mainly)
KaptinBoxxi said:
3.) flash the boot partition with the magisk patched boot.img
Code:
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
Just a heads up. As already told by ctfrommn, it's always a better approach to first boot the magisk patched boot file. And if everything works well and good, you could then Direct Install it via Magisk.
Although directly flashing should also work, but its always better to be on the safer side.
KaptinBoxxi said:
Correct, these are basically the usual steps. There's nothing regarding vbmeta flashing in this case of just rooting stock firmware. You only need to do that with ROMs (GSI's mainly)
Click to expand...
Click to collapse
I followed your steps to a T. Still can't unlock. I'm convinced there is a fault with my device itself at this point.
stormcrank said:
I followed your steps to a T. Still can't unlock. I'm convinced there is a fault with my device itself at this point.
Click to expand...
Click to collapse
they will warranty replace if it for sure fails still. Its a silly situation, but mistakes happen
binary**# said:
Just a heads up. As already told by ctfrommn, it's always a better approach to first boot the magisk patched boot file. And if everything works well and good, you could then Direct Install it via Magisk.
Although directly flashing should also work, but its always better to be on the safer side.
Click to expand...
Click to collapse
I may not be very active on XDA, but have been rooting and rom'ing devices since the palm pre, first android phone was the droid x. I've never heard of this step, its never been needed. Its an extra pointless step that is just tethered root. You don't need to do it. As long as you don't download a random Boot.img, like the one for some reason attached to a reply on this thread and get it yourself from the firmware matching your device OR flashing Magisk via TWRP/Lineage Recovery with adb sideload, there's no reason to fastboot boot the boot.img.
You may have never run into an issue flashing a boot image but I've built thousands of roms and kernels and have learned the hard way more than once to measure twice, cut once.
That said, as long as you're simply patching a stock boot.img it's likely not an issue.
Followed all steps, on SD2A.220601.003SD2A.220601.003. OEM unlock still greyed
Nice work, Kaptinboxxi. Everything worked fine. How should we handle updates after rooting? Will a security patch break root? If so, what is the best process to root it again?
Voxilli said:
Nice work, Kaptinboxxi. Everything worked fine. How should we handle updates after rooting? Will a security patch break root? If so, what is the best process to root it again?
Click to expand...
Click to collapse
Yes, each update will require reflashing a patched kernel for the new build.
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root. This has been a bit of a hit and miss for some people on the Pixel 6 series, though. The misses may be in large part be due to people having modified their partitions or not restoring the necessary images while being on a custom kernel.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Lughnasadh said:
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
Good call...I guess I've never messed with that as I flash so many kernels anyway.
Lughnasadh said:
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root. This has been a bit of a hit and miss for some people on the Pixel 6 series, though. The misses may be in large part be due to people having modified their partitions or not restoring the necessary images while being on a custom kernel.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
That's what I've done with my OnePlus 7T for the last three years. Any repercussions for doing it this way versus patching the kernel?