Edit - just an FYI for complete transparency. I have moved from the Pixel 3a XL to the Pixel 6. I no longer own my Pixel 3a XL. While I've been told (thanks @AndDiSa) that the root process for Android 12 is the same as it historically has been, I no longer can test things myself. (The root process for the Pixel 6 is different and more complicated than this phone). If you run into any problems or issues, please post in this thread and someone will hopefully be able to answer them.
I'm assuming you understand how to use ADB on your computer. If you need assistance with installing or using ADB, please refer to this XDA article for more information. However, here are some common issues that people have with ADB if it doesn't work initially for you. 1) Check the Android System Notification that appears in your phone's notifications after you plug in your USB cord. Your phone probably defaults to "No data transfer" and you need to change it to "file transfer" to allow the phone to connect. 2) Make sure you have USB debugging turned on in the Settings/System (advanced)/Developer options. 3) If this is your first time using this phone/computer combination, you will have to accept the connection when it pops up on your phone.
You also need an unlocked bootloader to complete these steps. If you need assistance with unlocking your bootloader, here is decent set of instructions. Those instructions are based on the Pixel 3 phone, but the steps are the same for the 3a devices.
Here are the official Magisk installation instructions. I will walk through them to help everyone understand them. Please note that while TWRP does work with Android 9 (Pie), it does not work currently with Android 10 or 11. If you are still on Pie for some reason you can choose either installation option, but if you have moved to a later Android version, you must use the "Boot Image Patching" installation method.
Custom Recovery Installation Method - (available for Android Version 9/Pie only because TWRP does not work currently with the Android 10/11)
This is the easier installation method IMHO, but it does require using TWRP. If you don't know how to get TWRP for the Pixel 3a, please refer to the official TWRP for Pixel 3a thread
Step 1 - Download and install the Magisk manager app on your phone. (link to the latest stable version can be found here).
Step 2 - Using the Magisk manager app, select "Install Magisk" and select the "Download Zip Only" option. This simply downloads the installation zip to your phone's download folder. It doesn't attempt to install anything.
Step 3 - Boot into TWRP - (because TWRP is not permanent on the stock Pie OS, we must follow these instructions each time we want to boot into TWRP).
Step 3a - Download the latest TWRP image for the 3a to your computer (not your phone) from the official TWRP for 3a thread.Step 3b - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".Step 3c - Boot your phone into the bootloader (type the command "adb reboot bootloader").Step 3d - Boot into TWRP using this command, "fastboot boot twrp-3.x.x-x.img" (where "twrp-3.x.x-x.img" = whatever the name of the TWRP download is). Please note you are not using the "flash" command as we are not permanently installing TWRP.Step 4 - Once the device boots into TWRP, select "Install" and then find the Magisk.zip download from step 2. Swipe to confirm the installation
Step 5 - After the installation is complete, simply reboot system.
Step 6 - Enjoy your rooted phone and install any Magisk modules that appeal to you
Step 7 - Be sure to turn off the "Automatic System Updates" setting found in Developer settings (Settings /System (advanced) /Developer Options). This will prevent the phone from automatically installing an OTA update and instead allow you to follow the steps listed under the "Taking an OTA Update" section below
The Boot Image Patching Installation method - (the only method currently available under Android 10, 11 or 12, but it also works with Pie).
Use this method if you are on Android 10 or 11 or you are on Android 9/Pie but you don't want to or can't use TWRP.
Step 1 - Obtain a stock boot.img file for the OS version/update that you are currently on. The easiest method is probably to download the applicable full stock image directly from Google. Unzip the files and unzip the second folder and you should find the boot.img file inside.
Step 2 - Copy the stock boot.img file to your phone's storage - probably to /sdcard or to /sdcard/downloads
Step 3 - Download and install the Magisk manager app on your phone. (link to the latest version can be found here). If you are early in the Android 12 cycle, you probably need to use a Canary build of Magisk.
Step 4 - Using the Magisk manager app, press "Install --> Install --> Select and Patch a File" - select the stock boot.img file that you put on your phone in step 2.
Step 5 - Magisk will modify the stock boot.img file and create a patched boot image file. It will save this modified file at "sdcard/Download/magisk_patched.img"
Step 6 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 7 - Copy the patched boot image from your device to your PC and the adb folder. If you can’t find the file on your phone via MTP or Windows Explorer, you can pull the file by typing the command "adb pull /sdcard/Download/magisk_patched.img" - Please note, I would suggest double checking the "file modified date" prior to moving the file. Be sure to only move the file if it was last modified on the date you are doing this. I've had a strange situation before where the newly modified file didn't immediately show up and the file showed a modified date of the previous month. If you flash an old version, your phone will bootloop.
Step 8 - Boot your phone into the bootloader (type the command "adb reboot bootloader").
Step 9 - Flash the patched boot image to your device using this command, "fastboot flash boot magisk_patched.img"
Step 10 - Reboot (using command "fastboot reboot").
Step 11 - Enjoy your rooted phone and install any Magisk modules that appeal to you
Step 12 - Be sure to turn off the "Automatic System Updates" setting found in Developer settings (Settings /System (advanced) /Developer Options). This will prevent the phone from automatically installing an OTA update and instead allow you to follow the steps listed next.......
Taking an OTA update in the future (if you used this method to install Magisk).
Taking OTA updates is very easy with the Pixel devices because of their A/B partition system. It allows us to uninstall Magisk, take the OTA update, and reinstall Magisk - all from the phone and all without rebooting during the process. Here are the offical Magisk OTA instructions. I will go through the steps to help explain them.
Step 1 - In the Magisk manager app: Click “Uninstall” then “restore images”. DO NOT REBOOT or press the reboot button.
Step 2 - Download and install OTA (in your phone's Settings/System/System Update). DO NOT REBOOT or press the reboot button.
Step 3 - Open the Magisk manager app and click “Install” next to Magisk (usually it says "Magisk is up to date") then “Install to second/inactive slot (After OTA)”
Step 4 - Press the Reboot button in Magisk.
That should be all it takes to install an OTA and keep root.
Please note, we are getting reports that users are getting notifications that an OTA update has been installed even when they have "Automatic Updates" turned off. If this happens to you, don't reboot the phone which is suppose to be the final step in the update process. Instead, follow the above instructions on taking an OTA update, but start in step 3. In other words, you shouldn't have to uninstall Magisk because the update has already been installed. All you need to do is install Magisk to the "second/inactive slot (After OTA)”. After completing that step, you can reboot your phone to complete the update process. Be sure to post your experiences in this thread to let us know if this process works or not.
Just remember that many custom parts (like kernels and Magisk modules) may need to be updated to any new OTA version. Please be sure to check out the forums for each custom kernel or module that you may want to install to ensure it has been updated to the lastest OS version. Don't assume anything or you may find yourself in a bootloop.
If you find yourself in a bootloop after upgrading an already rooted phone
If you find yourself in a bootloop after updating to a new OS version and flashing the magisk_modified boot.img again, it is likely due to an installed Magisk module not being compatible with the new update. To uninstall all Magisk modules to fix the bootloop, follow these steps:
Step 1 - Connect your phone to the computer you use ADB on.
Step 2 - In ADB type the command "adb wait-for-device shell magisk --remove-modules"
Step 3 - Start your phone again or wait for it to go through another bootloop cycle.
Step 4 - as soon as ADB is available (which occurs even during a bootloop) the command will activate, the modules will be removed, and the phone will reboot.
If the normal OTA method isn't working - sideload the OTA update
Taking an OTA update should be as easy as the above instructions. However there is another option available to install an OTA update called sideloading. Sometimes the update doesn't appear on the phone in a timely manner and you may want to manually install the update. Other times the OTA update seems to fail for some reason. In the end, you may decide to sideload the OTA instead of trying get it via the update feature on the phone. Surprisingly, it's actually faster to install the update via sideloading than it will be to take the OTA normally. I'll walk through the sideloading steps.....
Optional Step 1 - Uninstall Magisk (so that it restores the stock boot.img). If you find yourself unable to boot into recovery, you will have to restore the stock boot.img. I've run into this issue on a couple Android 10 images, but most do not require this step.
Step 2 - Download to your computer the correct OTA image from here
Step 3 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 4 - Boot your phone into recovery (type the command "adb reboot recovery").
Step 5 - The phone will have a green android robot with a red sign over it's open access panel. Press the power button and then the volume up button while still holding down the power button.
Step 6 - Select "Apply update from ADB" using the volume buttons to highlight the choice and the power button to select it to enter the sideload mode.
Step 7 - Using your computer, type "adb sideload ota_file.zip" where ota_file.zip is the name of the OTA file you downloaded in step 2.
Step 8 - Once the update finishes, reboot the phone to complete the update process. (See note below about initial boot times).
Step 9 - To obtain root again, please use one of the two root methods listed above
Please note, while the initial boot is usually pretty quick, it can take longer. I've occasionally seen the process take upwards of 20 minutes and longer. I think part of the reason it can take so long is that sometimes it optimizes the apps during this boot process. The more apps you have, the longer the process may take. When you take an regular OTA update, the phone will change to a screen where is specifically tells you it is optimizing the apps and counts up as the apps are optimized to give you status updates. When you use the side-load method, it all happens with just the regular boot animation running and without any status updates. Because of this, it is easy to assume something has gone wrong with the boot process while in fact the phone is working through the process normally. If it isn't boot looping (showing the initial power screen before moving back to the boot animation), everything is fine and you just need be patient and let the phone complete the process.
My rant about using these "Pre-patched Boot image" files
I started this thread during a period of time where there was a another thread on this forum started by pbanj that showed users how to root their phone by using some pre-patched boot image files. This method is not the generally accepted method and while it works, there are major shortcomings with it (see explanation below). Because it was the only root thread available at the time and he only showed the "pre-patched boot image" method, many people blindly followed his directions only to be confused when it came time to update the software on their phones. I wrote this thread in an effort to show people the official Magisk installation method. Pbanj has since updated his thread and it now includes the preferred method as well. With his edits, the two threads are sharing the same information now, although Pbanj thread still offers people the "pre-patched boot image" method (which I don't recommend people using).
EDIT - Yet another thread pushing a pre-patched root method has been started. It suffers the same issues as listed below.
Shortcomings with using the "pre-patched boot image" method.
As I already mentioned, there is a huge shortcoming with using the "pre-patched boot image" method described in the other root thread. Because he provides a pre-patched boot.img file, you skip some normal installation steps. In the end you have the exact same patched file (which is why his method works), but you cripple the system when it comes to taking any future OTA. That's because the first step in taking an OTA update is having Magisk reflash the stock boot.img effectively uninstalling itself. This step fails if you used his pre-patched boot image method because you skip the step where Magisk creates the backup of the stock boot.img that it needs to uninstall itself.
I already used the "pre-patched boot image" method to gain root. What can I do?
First, let me clarify and say that there is nothing wrong with your phone or root privileges. Your phone will work exactly as expected and root and Magisk will work exactly as expected. That being said, in the near future you will want to update your phone to the latest Android update and this is where the "pre-patched boot image" method is much more cumbersome. The best option is to simply undo his root method and re-root using the method described above. To do this, flash the correct stock boot.img file to your boot partition and then follow the steps above to reinstall Magisk. Jbanj has confirmed this method will work. The other option is just wait until you need to take an update and then sideload the OTA update following the instructions above. This will remove root and you can then follow one of the two methods to obtain root as outlined in this thread.
Notes
- Please be sure you are on the latest adb and drivers which can be found here.
- You do not need to keep the stock boot.img file (from step 2 of the Boot Image Patching method) on your phone after completing these steps. Magisk saves the stock boot.img backup at /root/data in a file with the name "stock_boot_XXXXXXXXXXXX.img.gz"
Thanks to.......
@ZVNexus for getting TWRP working on the 3a and 3a XL phones
@topjohnwu for making Magisk what it is today
Made it to step 7/8, went to reboot, and entered bootloop. Not sure exactly what happened, gonna fix this and give it another go.
EDIT: Should I be flashing in fastboot or recovery mode?
EDIT 2: Working! Thanks!
You know there are more ways to skin a cat, right? This is another method to acquire root. I don't think you need to bash the work that pbanj has done. He provides modified boot.img and also offers help on getting it working. I think acting like your method is the only acceptable way to gain root is extremely pompous and arrogant.
Sent from my Pixel 3a using Tapatalk
jmtjr278 said:
You know there are more ways to skin a cat, right? This is another method to acquire root. I don't think you need to bash the work that pbanj has done. He provides modified boot.img and also offers help on getting it working. I think acting like your method is the only acceptable way to gain root is extremely pompous and arrogant.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
I don't think that this method is the only way to get root, nor is this "my method". It is however the method spelled out by the Magisk developers and it is the only method that uses Magisk strengths when trying to take an OTA update.. I'll simply leave it at that......
sic0048 said:
I don't think that this method is the only way to get root, nor is this "my method". It is however the method spelled out by the Magisk developers and it is the only method that uses Magisk strengths when trying to take an OTA update.. I'll simply leave it at that......
Click to expand...
Click to collapse
Sure. It's the way I do it also. But show some class and don't call out other, helpful members in this fashion and crap all over what they do. I have seen your posts and know your a helpful members also, let's respect each other and be classy.
Sent from my Pixel 3a using Tapatalk
@sic0048
Thank you. I got to admit it was pretty tense for a while. Thanks to you I made it. Had to do a sideload, had to do some stupid things but I made it. Now, I got through all the steps and I have two items; Having done this transition can I now do the magisk-uninstall-restore images for all future OTAs and is step 9 performing the magisk install process a second time?
Bankuu said:
Made it to step 7/8, went to reboot, and entered bootloop. Not sure exactly what happened, gonna fix this and give it another go.
EDIT: Should I be flashing in fastboot or recovery mode?
EDIT 2: Working! Thanks!
Click to expand...
Click to collapse
I've edited the steps and added a few more going into greater detail to try and make it even clearer for users. Let me know if you have any suggestions.
alliance1975 said:
@sic0048
Thank you. I got to admit it was pretty tense for a while. Thanks to you I made it. Had to do a sideload, had to do some stupid things but I made it. Now, I got through all the steps and I have two items; Having done this transition can I now do the magisk-uninstall-restore images for all future OTAs and is step 9 performing the magisk install process a second time?
Click to expand...
Click to collapse
You should be able to use the normal Magisk OTA update instructions for future updates.
I've updated the thread and I think the "step 9" you listed isn't the same anymore, but I think I understand your question. Actually I think my original instructions were inaccurate as far as that step. I've always gone back into Magisk after flashing the modified boot.img and I thought I hit install to install the Magisk framework (if that is the correct term). But after reading some other guides, I think my memory is incorrect and you don't really have to install anything after the flashing portion of the steps.
Once you reboot after flashing, that should be all you have to do. I'll uninstall Magisk here in a while and walk through the steps myself to ensure this is correct howeve.
The OP should be made a sticky.
Cool guide. Can the method be applied to Q beta 4 ?
MPAI said:
Cool guide. Can the method be applied to Q beta 4 ?
Click to expand...
Click to collapse
No root for Android q on our devices yet afaik.
Sent from my Pixel 3a using Tapatalk
@sic0048
Should we keep the stock boot image copied to the phone storage in step 2? Is this where Magisk will look for it to do an image restore?
alliance1975 said:
@sic0048
Should we keep the stock boot image copied to the phone storage in step 2? Is this where Magisk will look for it to do an image restore?
Click to expand...
Click to collapse
You do not need to keep the stock boot image that was copied over in step 2. Magisk saves the backup of the boot.img at /root/data. It will have the name "stock_boot_XXXXXXXXXXXXXXXXXXX.img.gz"
sic0048 said:
You do not need to keep the stock boot image that was copied over in step 2. Magisk saves the backup of the boot.img at /root/data. It will have the name "stock_boot_XXXXXXXXXXXXXXXXXXX.img.gz"
Click to expand...
Click to collapse
Thanks sic0048. You put up with my dumb questions and helped make my pixel 3a a great phone.
Respect.
Edited - now that jbanj has confirmed we can simply flash the stock boot.img file to the boot partition and start over, the post I originally had here is pointless.
Alliance's question got me to thinking.....
Since Magisk saves the stock boot.img backup at /root/data in a file named "stock_boot_XXXXXXXXXXXX.img.gz" I wonder if we can't simply share a backup file with someone that used jbanj "modified boot image" method and have them copy it to that location. I suspect Magisk will then allow the normal OTA update prceedures to work.
I can share the backup file that I have, but it is for the 3a XL model, Android version 9 (Pie) and the June 5, 2019 security update. That means it will be next month before there will be another OTA update pushed out.
If someone is still on the OEM March update and rooted using the normal directions and is willing to share their backup file, we might be able to try it sooner.
Unfortunately I don't know if Magisk modifies the backup to be some sort of unique file. I doubt it, but I don't know for sure. Of course worse case scenario is that it doesn't work and the person has to flash the OTA manually - which is no different than what they would have to do anyway. So there really isn't much risk in trying this.
MPAI said:
Cool guide. Can the method be applied to Q beta 4 ?
Click to expand...
Click to collapse
Wondering the same thing. I know the OTA is rolling out again today IIRC. But I also read something about root not being available on Q yet, so not sure how that would work out.
Bankuu said:
Wondering the same thing. I know the OTA is rolling out again today IIRC. But I also read something about root not being available on Q yet, so not sure how that would work out.
Click to expand...
Click to collapse
Google has changed the file structure in the Q beta 4 release and root is not possible at this time. This is true across all devices (not just the Pixel 3a). I know John Wu (the Magisk developer) is working on a solution and I would expect to see results before Android 10 is released, but only time will tell.
However, at this time there is no root on the Q beta 4. If you need root, you will have to stick to Pie for now.
@sic0048 I've updated my thread
I'm getting weird behavior here that I've been able to replicate.
Bottom line, if you use the Magisk patch method, upon flashing that boot image, your phone will auto-play music every single time it boots up. That's incredibly annoying.
Uninstall and go back to stock boot.img, and it goes away. Flash again, it's right back.
Guess I'll just wait for TWRP instead of going through those steps again, lol.
Related
TWRP (Team Win Recovery Project) replaces a device's stock recovery and provides, among other options, the ability to install img (image) and zip files. TWRP for the Fire HDs was developed by JMZ and is described here.
How to install TWRP
These steps are for a first-time install on a rooted Fire HD running OS 4.5.3 with stock bootloader and recovery.
At this time, 4.5.3 bootloader is required. You're welcome to try to get it onto a different OS, but you need the 4.5.3 bootloaders and I'm not getting into that. So, if you're running a different OS, have messed with partitions or done something that requires a TWRP reinstall (other than reinstalling 4.5.3 and rerooting), you risk being unable to boot recovery or bootloop/brick.
OK, that doesn't sound so "newbie-friendly" but this really is a simple process that should always go smoothly on a "clean" OS 4.5.3.
You can easily install TWRP with either TWRP Manager (also by JMZ) or Flashify from the Play Store.
If you don't have Play Store access:
- Flashify - v 1.9.1 from APKMirror
- TWRP Manager - Download from JMZSoftwareFor installing TWRP, the only difference between the two is that TWRP Manager auto-downloads the correct TWRP version while Flashify requires you download it yourself.
[EDIT 8/16/2015] At this time, TWRP Manager doesn't seem to be working. Use Flashify, instructions below. Steps for TWRP Manager are at bottom of post.
Install TWRP with Flashify
Download JMZ's ariel TWRP image (https://www.androidfilehost.com/?fid=24052804347756852) to the Fire's download folder.
Install and run Flashify (download link above) and give it superuser access when prompted. It probably will also prompt to apply loki patch for Kitkat. Say yes.
Tap Recovery Image and then Choose a File.
Navigate to download folder, tap the TWRP file, and when Flashify asks if you are sure, tap Yup!
If install succeeds ("Flash Complete"): (a) Tap Reboot now. (b) When back in Fire OS, boot to recovery (below) and confirm you're in TWRP. Note: If tablet bootloops, post the problem in one of the bootloop threads.
If install fails (error messages displayed), first take a screenshot. If you can determine the problem, fix it and try again or try TWRP Manager. If you don't understand the error or can't resolve it, post in a "TWRP install failure" thread.
How to Boot to Recovery
Manual: (a) Power off tablet. (b) Hold down power and volume-up buttons at same time until you see "Amazon," then release. (If you just boot back into Fire, you didn't power off first or didn't hold buttons long enough.)
adb command from computer: adb reboot recovery
- If you see TWRP, great! Check it out and then press Reboot and System to go back to OS.
- If you get stock recovery screen ("reboot" and "factory reset"), TWRP didn't install. Reboot should be highlighted. (If it's not, use volume-up or -down to select it.) Press the power button to click reboot and when back in Fire OS, try the other app.
[EDIT 1] For simplicity, install TWRP Manager on the Fire and follow these steps.
Install TWRP with TWRP Manager
Install and run TWRP Manager and give it superuser access when prompted. It will also prompt to apply patch for Kitkat. Say yes.
Tap top-left of screen for slide-out menu and select Install TWRP.
Confirm Device Name shows "ariel" and then tap Install Recovery. [download begins]
At warning screen, tap yes.
If install succeeds ("Flash Successful"): (a) Go to slide-out menu and choose Reboot Options and then Reboot Device. (b) When back in Fire OS, boot to recovery (above) and confirm you're in TWRP.
Note: If tablet bootloops, post the problem in one of the bootloop threads.
If install fails (error messages displayed), take a screenshot in case you need to post the problem and then look at comments here for a solution. If you can determine the problem, fix it and try again or try Flashify. If you don't understand the error or can't resolve it, post in a "TWRP install failure" thread.
After step 5 a) only puts on the screen "Kindle Fire" and I can not make the "Power and Volume up buttons reboot".
Could you help me please?
Po069 said:
After step 5 a) only puts on the screen "Kindle Fire" and I can not make the "Power and Volume up buttons reboot".
Could you help me please?
Click to expand...
Click to collapse
I'm sorry I can't help you. This guide is for the 2014 Fire HD tablets. The Kindle Fires are ealier models. Look here to figure out which tablet you have and then post the problem in the forum for your tablet:http://forum.xda-developers.com/kindle-fire/help/index-amazon-kindle-fire-t3205350
DoLooper said:
I'm sorry I can't help you. This guide is for the 2014 Fire HD tablets. The Kindle Fires are ealier models. Look here to figure out which tablet you have and then post the problem in the forum for your tablet:http://forum.xda-developers.com/kindle-fire/help/index-amazon-kindle-fire-t3205350
Click to expand...
Click to collapse
Thank you very much for your answer.
Kind regards.
Sorry if this is a stupid question, but if I update the Fire OS after successfully rooting/installing TWRP will I mess up anything?
I rooted everything and installed TWRP succesfully on my Fire HD 6 running 4.5.3 (it was fresh out of the box and I didn't allow any OTA updates). If I update the OS now will it brick it or mess up TWRP in any way?
Also, ultimately I'm just trying to get Google Apps on my HD 6 (it'd be nice if I could get lollipop on it but I bricked the last HD 6 I had so I'm starting with the low-hanging fruit haha). However, I can't really find a guide to do this starting from 4.5.3 Fire OS... Could you point a noob anywhere to either a) install GApps or b) get lollipop installed?
I was trying to follow this tutorial but it's not really noobie-friendly and I think it's meant to start from 5.0.n which is why I'm asking if I can update without screwing anything up.
Thanks for your help!
SpaceBananas said:
Sorry if this is a stupid question, but if I update the Fire OS after successfully rooting/installing TWRP will I mess up anything?
I rooted everything and installed TWRP succesfully on my Fire HD 6 running 4.5.3 (it was fresh out of the box and I didn't allow any OTA updates). If I update the OS now will it brick it or mess up TWRP in any way?
Also, ultimately I'm just trying to get Google Apps on my HD 6 (it'd be nice if I could get lollipop on it but I bricked the last HD 6 I had so I'm starting with the low-hanging fruit haha). However, I can't really find a guide to do this starting from 4.5.3 Fire OS... Could you point a noob anywhere to either a) install GApps or b) get lollipop installed?
I was trying to follow this tutorial but it's not really noobie-friendly and I think it's meant to start from 5.0.n which is why I'm asking if I can update without screwing anything up.
Click to expand...
Click to collapse
If you update now without following that guide you will lose root and TWRP. You may not be able to root with Kingroot and you won't have the "friendly" bootloaders that can boot TWRP. Don't do it.
I'll have to get back to you about updating. Maybe bibikalka will jump in. Look around for a KitKat version of pico-uni Gapps, which you could install in TWRP now. There will be link in an old guide for OS 4.
SpaceBananas said:
I rooted everything and installed TWRP succesfully on my Fire HD 6 running 4.5.3 (it was fresh out of the box and I didn't allow any OTA updates).
. . .
Also, ultimately I'm just trying to get Google Apps on my HD 6 (it'd be nice if I could get lollipop on it but I bricked the last HD 6 I had so I'm starting with the low-hanging fruit haha). However, I can't really find a guide to do this starting from 4.5.3 Fire OS... Could you point a noob anywhere to either a) install GApps or b) get lollipop installed?
I was trying to follow this tutorial but it's not really noobie-friendly and I think it's meant to start from 5.0.n which is why I'm asking if I can update without screwing anything up.
Click to expand...
Click to collapse
OK, I looked at the guide again. @bibikalka may have a preferred route, but here's what I suggest: Pretend nothing else is there except steps 1) through 3) and just carefully follow those steps.
Download all the files to the pc first. Get the 5.1.1 update (only because we know it's rootable with Kingroot) and rename the extension from bin to zip. Skip Xposed (step 1-7). Do get 5.2.0_stock_recovery_uboot.zip (step 1-10). Copy or move all the files to the downloads folder on device. (This is the long way and you can download directly to device if you prefer. I just find it easier to download and double check that you have all the right files from the pc.)
Hold Power and volume+ to get into TWRP, then carefully do all the sub-steps under 1) except for step 7. (From what you say, I just don't think you need Xposed.) Just be sure you have the correct file at each step and you'll be fine.
DoLooper said:
OK, I looked at the guide again. @bibikalka may have a preferred route, but here's what I suggest: Pretend nothing else is there except steps 1) through 3) and just carefully follow those steps.
Download all the files to the pc first. Get the 5.1.1 update (only because we know it's rootable with Kingroot) and rename the extension from bin to zip. Skip Xposed (step 1-7). Do get 5.2.0_stock_recovery_uboot.zip (step 1-10). Copy or move all the files to the downloads folder on device. (This is the long way and you can download directly to device if you prefer. I just find it easier to download and double check that you have all the right files from the pc.)
Hold Power and volume+ to get into TWRP, then carefully do all the sub-steps under 1) except for step 7. (From what you say, I just don't think you need Xposed.) Just be sure you have the correct file at each step and you'll be fine.
Click to expand...
Click to collapse
Any point in using 5.1.1 ? Since SuperSu gets flashed during the update, it does not care which FireOS version it is. Nobody will be running Kingroot since SuperSu is already there
bibikalka said:
Any point in using 5.1.1 ? Since SuperSu gets flashed during the update, it does not care which FireOS version it is. Nobody will be running Kingroot since SuperSu is already there
Click to expand...
Click to collapse
No, 5.1.2 is fine. It was just a cya suggestion in case user missed a step and somehow lost root--but OF COURSE no steps will be missed.
TWRP failed to install, now have no recovery
So I'll start by saying I'm an idiot. I wasn't paying attention to which version OS is required and tried to install TWRP using Flashify. It went through the motions and did its reboot, and now I'm stuck with absolutely no recovery at all. I've tried searching these forums for a "TWRP installation failed" thread and have had no luck, at least not for the Fire HD 6 device. Really need help here, I have absolutely no way to get into recovery to flash anything back at all.
So I wanted to create a thread dedicated to performing this function. I know as someone who does this quite often, I like to have all my ducks in a row to ensure everything works perfectly. I'm not big on fragging my phone and then frantically trying to find a way to undo all the chaos. I do a lot of research and ask a lot of questions before doing anything.
On that note I would like to first thank all the amazing people on here, whether they be developers or just experienced Tech Guru's, everyone is always a big help. I take absolutely no credit for any of the awesomeness that can be found on XDA, I'm just creating a thread that I hope will help folks find everything in one place for this function. So here we go, I'm going to explain the way I did it, which is the way I have been doing stuff like this for years. I have a preferred method as it has always resulted in perfect flashes and no bricks, not even soft bricks. So I feel it works pretty well.
Just so it is understood, this is for the Moto X Pure, which has been bootloader unlocked and has TWRP and root installed. Also it should be noted that you need to have Developer Options enabled and USB Debugging enabled. You should also be familiar with the ADB process, to some extent, maybe you have at least heard of it.
Steps to follow:
1. Use Titanium Backup and backup all your User Apps, NOT SYSTEM APP's, system apps will not restore across updates and will most often corrupt your new install.
2. Make a Nandroid backup using TWRP, I backed up system, boot, data, and EFS, but I don't think EFS is necessary.
3. Make sure you have the Motorola Drivers installed, get them from here http://www.motorola.com/getmdmwin
4. Get Shawn5162's Restore to Stock Tool, I know others have said it's not necessary to perform a complete restore, but this is part of my process that I have always done, and it's always worked. Get it here by using one of the mirror's created by patt2k in post 6, and don't forget to thank him for the mirrors http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
5. Unzip Shawn5162's zip to a folder on your desktop, and before you move onto the next step, make sure you have backed up everything valuable on your phone, such as pictures, messages, etc..., because everything is going to be erased in the next step, except for the stuff on your MicroSD. I'm so anal, I even remove the MicroSD before flashing. Connect your phone to your computer using a USB and make sure you have USB debugging enabled under Developer Options.
6. Inside the folder you created run the FLASH-ALL.bat, which will reboot your device to the bootloader and begin the restore to stock flash. This will remove root and TWRP, but will not remove the fact you have an unlocked bootloader. Your phone will reboot when complete and should boot back into your system within a short period of time.
7. Once you are rebooted, you may need to do a little setup before you get the message that a System Update is available. DO NOT waste your time installing any apps, wait until you have full root on MM before doing any of that. Once the Update message appears, accept it and download the MM update file, then install it once it is finished downloading and asks if you want to install.
8. The update takes about 20 - 25 minutes so be patient. Once complete your phone will once again boot back to system, now you have MM in it's complete unrooted greatness.
9. Now go into settings, about phone, and tap on build number a bunch of times to enable Developer Options. Then go into developer options and enable USB Debugging.
10. Next download a bunch of stuff from the following links, if you desire to install TWRP and regain root.
TWRP 2.8.7.1 here https://dl.twrp.me/clark/twrp-2.8.7.1-clark.img
Modified Boot Image from here, required to perform systemless root , not sure about the Cowboy hat dude, but click on him, it will download the file.
SuperSU 2.52 from here https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip?retrieve_file=1
11. Next copy the modified boot file and SuperSU file directly to your internal or external SD on your phone, either works fine, although I prefer my External SD.
12. Next copy the TWRP file you downloaded into the same folder you made for Shawn5162's files. This folder has all the adb and fastboot files you need to perform the TWRP flash. Now hold shift and right click and choose open a command window here. Then ensure your device is detected by running the command adb devices, it should show your phones S/N and the word device. If it doesn't, you may need to look at your phone and respond to the prompt about allowing your computer to have access to adb. Try the command again after that. Then run the command adb reboot bootloader, which should reboot your phone to bootloader fastboot mode.
13. Once it fastboot mode run fastboot devices just to make sure your device is still detected, then run the command fastboot flash recovery twrp-2.8.7.1-clark.img. That will flash TWRP to your recovery partition. Then type the command fastboot reboot twrp-2.8.7.1-clark.img or use the volume rocker to toggle to recovery then select the power key to boot to it. Make sure you choose the slider at the bottom to allow modification. Once on the main screen you can choose reboot and then select recovery. This makes sure that you have booted to TWRP at least once, and ensures by rebooting to it, you can get back to it.
14. Now perform a Nandroid Backup, using the TWRP Backup option, of your completely stock MM system, data, boot, and EFS partitions. Enable compression if you like and store it to your External SD if you have one. This allows you to have an unrooted backup on your SD, which is good for future updates. After the Nandroid is complete now flash the modified boot image zip using the TWRP Install feature, and when it's complete, then flash the SuperSU zip file. After I always perform the option to erase Dalvik and Cache, I just think it is a good thing to do, it's probably placebo, but I do it anyhow.
15. Go back to TWRP Home and choose reboot and select system. Your device will reboot and you now have a fully updated and rooted Moto X Pure on MM.
Thanks go out to all the folks who have contributed to the many threads that contain this information. Special thanks to Shawn5162, DaMadOne, Chainfire, and Hashbang173 for their awesomeness. Hope this helps folks that are concerned about performing these procedures. I can say that it worked perfectly for me with no issues at all, but of course I take no responsibility if it doesn't work for you and causes your device to fail. Again these are similar steps I have taken in the past with other devices and I have never had a single brick, so hopefully it works for others as well.
Enjoy!!
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
I think I am in way over my head. I am receiving my phone Friday and was looking to unlock to root but from the looks of it, I will not be able to do that.
I've never unlocked & rooted a phone before. So all that looks like the bible to an uneducated man "me".
superkev72 said:
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
Click to expand...
Click to collapse
If I'm not mistaken it will download to your phone but not be able to be installed because of an error
Is there no way to upgrade from LP to MM without a wipe?
superkev72 said:
Is there no way to upgrade from LP to MM without a wipe?
Click to expand...
Click to collapse
Yeah, if you rooted already, you must reflash the original boot.img. Then update, and then restore your root. Read here:
http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380
At the bottom of the post, you get the original file you need and it is mentioned here:
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
K?
Why would you want to update without a wipe? You must like sluggish performance
i have no wifi after this
No WIFI either
I ended up with no WIFI after following these steps also.
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
skimaniaz said:
I ended up with no WIFI after following these steps also.
Click to expand...
Click to collapse
Same here. Anybody got a fix?
So the last three posts complain of no wifi yet people keep using this method?
The modified boot zip breaks the wifi. You can root by flashing superSU 2.62, I think, or any SuperSU zip that is specifically systemless.
ilovemeow said:
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
Click to expand...
Click to collapse
Not true.
lafester said:
Not true.
Click to expand...
Click to collapse
coz i tried before, it fail in first 2 flash steps
Are you unlocked?
ilovemeow said:
coz i tried before, it fail in first 2 flash steps
Click to expand...
Click to collapse
The partition always fails. Just ignore it. You should be able to downgrade the bootloader. I have been able to so I don't know why you would be having issues with that unless your bootloader is locked/re-locked.
Sent from my XT1575 using XDA Labs
So is this safe or not?
lafester said:
Are you unlocked?
Click to expand...
Click to collapse
yup, it's unlocked, but currently fine for using android M at this moment
Hi everyone!
This is my second guide, but it was the first one written. Like I said in my first guide on how to systemlessly root your Pixel XL, I started writing these for myself so that I can keep straight all the things I like to do. I like simple, concise instructions that written clearly in way that anyone could understand. I've decided to start sharing these with the community!
This guide will teach you to manually flash Google's updates, like monthly security patches or version updates (like Oreo) to your Pixel XL while keeping your apps, settings, and data. It's a very simple and easy process. This guide assumes you know what the ADB/Fastboot and what flashing to your device means.
Pre-requisites:
1) The current ADB/Fastboot Platform Tools
2) A Pixel XL with an unlocked bootloader. This is essential, as a locked bootloader will not allow you to flash anything to your device
3) You should also be fully stock, meaning that you are not running a custom ROM (like PureNexus) and that you are not running a custom Kernel (like Franco or ElementalX)
4) OPTIONAL: Have a file structure for your device on your PC that makes sense to you - for Oreo updates, I use C:\Users\groov\Pixel XL\Oreo\ where I unzip the image and rename the folder to the month of the update, like August 2017 Stock. For the Platform Tools, I use C:\Users\groov\Pixel XL\platform-tools. I copy the necessary files into this folder for flashing.
STEPS:
1) Download the latest stock image
2) Unzip the stock image zip into your designated folder OR just unzip it right into platform-tools
3) Right click ‘flash-all.bat’ and click ‘edit’. You can use any text editor, like Notepad or Notepad++ (I like Notepad++ better because of the font highlighting and better tabbing)
4) Remove the ‘-w’ from near the end of the file; save the file
5) Put the device into bootloader mode (adb reboot bootloader OR power+volume down). Make sure the phone is connected to computer.
6) Double click ‘flash-all.bat’. The update will flash (this takes 5-10 minutes) and the phone will boot with the update installed and all data/settings preserved.
Please note that when you flash the update, it will seem at a few points like it is hanging; it is not. The process will clearly inform you when it is finished, and you will also get visual confirmation in the form of your device booting to system.
I have used this method twice so far - once to go back to 7.1.2 August Stock when I got into a TWRP bootloop trying to root (although I did not keep my data), and then to update to Oreo on Monday (I kept my data then). It worked successfully both times. This method will work for the regular Pixel as well (presuming you download the correct image).
This will obviously only work until Google stops supporting the first gen Pixels, but thankfully we have a long time until then
Please feel free to ask me any questions you might have. I will answer to the best of my ability, and if I don't know something I'll do my best to redirect you.
Good luck and happy flashing!
You can flash with locked bootloader if you download OTA image from same link just select "Full OTA Images" on left menu.
It will automatically preserve all the data, just follow instructions on the page.
I just used this method to update to the latest update. I'm still getting prompted on my phone to install the OTA. How can I stop the OTA update prompts?
[DEPRECATED] no longer working on due to real life issues. [DEPRECATED]
Please feel free to use my post and work on it yourselves, sorry.
Nexus 5x BLOD fix (OPM2.171019.029)
I recently purchased a Nexus 5x from ebay; it had the BLOD issue and, after many days I managed to fix it.
So I have decided to update the boot image to the 'latest' android factory image; this will allow people who have applied the patch to use a later version of Android or a custom ROM.
A huge thanks to @XCnathan32 for the original fix!
The steps below will wipe all data from your device!
For Rooting Information and Google Pay fix, see 2nd post.
Changelog
02/05/2018 - Updated method and added custom ROM method.
01/05/2018 - Updated TWRP from version 3.1.1.0 to 3.2.1-0.
What does this do?
There are two versions;
The first process will install the 'newest' stock version of Android onto your device; it will then install a custom recovery, and finally flash the updated boot.img file.
The boot.img has been modified slightly to only use 4 out of the 6 cores on the processor, this fixes the overheating issue with the Nexus 5x devices.
The other version is similar except using a custom version of Lineage OS.
Instructions
For detailed instructions and more info please visit the original thread.
Please make sure to have all of the downloaded file ready.
First Method - Stock Image
1. Boot into fastboot mode.
2. Extract factory image zip file and go into its directory.
3. With the phone in fastboot mode and connected the computer, open 'flash-all.bat'.
3a. Let the process finish; the device will reboot.
4. Go back into fastboot mode.
4a. [optional] you may wish to flash a custom recovery. If so move into the directory where you have the custom image downloaded. follow step 6a and type in
Code:
fastboot flash recovery [filename].img
5. Now move into the directory in which you downloaded the boot.img file.
6. Once inside; shift-right-click in the file manager and select 'open in powershell' or 'open in cmd'
7. Once the command window has opened: type in
Code:
fastboot flash boot boot.img
8. Now reboot the device!
Second Method - Custom ROM
1. Boot the device into fastboot mode
2. Download the ROM [linked below].
3. Download the GAPPS package [linked below].
4. Download Magisk [linked below].
5. Download the stock factory image; this is important as it contains the newest version of the bootloader, radio and vendor images, which is needed for Lineage to work [linked below].
6. Extract the stock factory image and go into it’s directory.
6a. There should be a file called ‘flash-all.bat’ - double-click to run it (Make sure phone is plugged in and in fastboot mode!).
6b. Let the process finish; the device should reboot.
7. Once the device has rebooted, again make sure it’s in fastboot mode.
8. Now download the custom version of TWRP; go into it’s directory then shift-right-click and select ‘open with cmd’ or ‘open with powershell’.
9. Then type the following:
Code:
fastboot flash recovery [filename].img
10. Once that process has finished (it should only take a sec), boot into recovery mode by selecting it via the volume up & down keys; the using the power button to select.
11. Once in recovery;
11a. Copy and paste the ROM zip archive, Magisk and the GAPPS package to the phone. You should be able to view your phone in the file explorer. If not please install the adb & fastboot drivers.
11b. Once done; go to ‘Install’ -> the select the zip file you transfered. It will now ask you to confirm, drag the bar across to accept the flash.
12. The ROM will now be flashing; leave it until it is done!
13. Once that process has finished; go back into the install section.
13a. Now you need to flash the GAPPS package.
14. Once the GAPPS has finished flashing; you now need to flash Magisk. This allows you to root your device and use services like Google Pay.
15. Now reboot!
If all is good then the device will reboot. You should see a boot animation (This can take up to 30 mins, so please wait!), after you should now see the android setup process.
Downloads
The fixed boot image can be downloaded from here.
The factory image: please make sure the version you are downloading matches the updated boot images'. It can be found here.
Modified Lineage OS ROM (boot image updated to the fix); it can be found here.
Magisk -> here.
GAPPS -> here. (Download for ARM64).
A fixed version of TWRP created by @XCnathan32 and updated by me to work with the 4-core boot image. Download Here.
Disclaimer
I will not be held responsible for anyone that decides to proceed with the steps listed above. If there are any issues please post them below with as much detail as you can. I will try my best to answer them, but I do have real-life stuff to deal with.
The original mod was not created myself! I have simply updated it.
Rooting info & Google pay fix
Rooting info & Google Pay fixFlashing Magisk after ROM will allow you to have root privileges and will also allow you to use
Magisk: it's HERE
My phone has bootloader locked. Is it needed?
lollazzo said:
My phone has bootloader locked. Is it needed?
Click to expand...
Click to collapse
Unfortunately, it is required so that you can flash the images. If you can't turn the device on then try the steps linked below;
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Goto the "*If your phone is bootloader locked/OEM locked:" section, I had the same issue and freezing my phone for 15 mins worked great.
Might work for you to
could you please fix the link to the Modified Lineage OS ROM.
thank you
deoneR said:
could you please fix the link to the Modified Lineage OS ROM.
thank you
Click to expand...
Click to collapse
Fixed it sorry for the wait; was busy with college etc.
if i do all your steps for the second method i always get a reboot to TWRP after ~ 3mins
what am i doing wrong?
deoneR said:
if i do all your steps for the second method i always get a reboot to TWRP after ~ 3mins
what am i doing wrong?
Click to expand...
Click to collapse
Try following method #1 first, then If you want; flash the custom ROM etc.
The custom ROM I provided works for me so I'm not 100% sure why it's not working. Trying the first method may help :|
lollazzo said:
My phone has bootloader locked. Is it needed?
Click to expand...
Click to collapse
Freezing did not worked for me , I put mine the oven and heated it to about 60 Grad Celsius.
That even gave me enough time to back up my data .
however, is back to live because of this tread.
Thanks.
This is the clear and simple instructions that always make things work first try! Thank you so much!
For June 5th security update I managed to work with those instructions, works perfect with making my own 4 core boot image and recovery.
http://aurelio.net/articles/nexus-5x-bootloop-fix.html
First fix that actually brought my phone back to life
Wow, amazing job, thank you very much! I tried many other methods to fix my device, and some allowed me to boot back into my phone, but I encountered errors like my wifi died etc. So I thought it was the end for my device and it turned into a very expensive USB flash drive lol. I don't know how your fix differs from the other ones on xda ( I used the first method), but it worked for me. So thanks again!
Something happened to my phone today. Its running 8.1 Pixel rom with the bload fix applied. All of a sudden my phone turned off today after running fine from so many months with blod fix. Now it doesn't boot. Google logo and turns off. Not even recovery is working (TWRP 4 core, patched). Can anyone suggest what's wrong?
Dragon's Fedora said:
Nexus 5x BLOD fix (OPM2.171019.029)
I recently purchased a Nexus 5x from ebay; it had the BLOD issue and, after many days I managed to fix it.
So I have decided to update the boot image to the 'latest' android factory image; this will allow people who have applied the patch to use a later version of Android or a custom ROM.
A huge thanks to @XCnathan32 for the original fix!
The steps below will wipe all data from your device!
For Rooting Information and Google Pay fix, see 2nd post.
Changelog
02/05/2018 - Updated method and added custom ROM method.
01/05/2018 - Updated TWRP from version 3.1.1.0 to 3.2.1-0.
What does this do?
There are two versions;
The first process will install the 'newest' stock version of Android onto your device; it will then install a custom recovery, and finally flash the updated boot.img file.
The boot.img has been modified slightly to only use 4 out of the 6 cores on the processor, this fixes the overheating issue with the Nexus 5x devices.
The other version is similar except using a custom version of Lineage OS.
Instructions
For detailed instructions and more info please visit the original thread.
Please make sure to have all of the downloaded file ready.
First Method - Stock Image
1. Boot into fastboot mode.
2. Extract factory image zip file and go into its directory.
3. With the phone in fastboot mode and connected the computer, open 'flash-all.bat'.
3a. Let the process finish; the device will reboot.
4. Go back into fastboot mode.
4a. [optional] you may wish to flash a custom recovery. If so move into the directory where you have the custom image downloaded. follow step 6a and type in
Code:
fastboot flash recovery [filename].img
5. Now move into the directory in which you downloaded the boot.img file.
6. Once inside; shift-right-click in the file manager and select 'open in powershell' or 'open in cmd'
7. Once the command window has opened: type in
Code:
fastboot flash boot boot.img
8. Now reboot the device!
Second Method - Custom ROM
1. Boot the device into fastboot mode
2. Download the ROM [linked below].
3. Download the GAPPS package [linked below].
4. Download Magisk [linked below].
5. Download the stock factory image; this is important as it contains the newest version of the bootloader, radio and vendor images, which is needed for Lineage to work [linked below].
6. Extract the stock factory image and go into it’s directory.
6a. There should be a file called ‘flash-all.bat’ - double-click to run it (Make sure phone is plugged in and in fastboot mode!).
6b. Let the process finish; the device should reboot.
7. Once the device has rebooted, again make sure it’s in fastboot mode.
8. Now download the custom version of TWRP; go into it’s directory then shift-right-click and select ‘open with cmd’ or ‘open with powershell’.
9. Then type the following:
Code:
fastboot flash recovery [filename].img
10. Once that process has finished (it should only take a sec), boot into recovery mode by selecting it via the volume up & down keys; the using the power button to select.
11. Once in recovery;
11a. Copy and paste the ROM zip archive, Magisk and the GAPPS package to the phone. You should be able to view your phone in the file explorer. If not please install the adb & fastboot drivers.
11b. Once done; go to ‘Install’ -> the select the zip file you transfered. It will now ask you to confirm, drag the bar across to accept the flash.
12. The ROM will now be flashing; leave it until it is done!
13. Once that process has finished; go back into the install section.
13a. Now you need to flash the GAPPS package.
14. Once the GAPPS has finished flashing; you now need to flash Magisk. This allows you to root your device and use services like Google Pay.
15. Now reboot!
If all is good then the device will reboot. You should see a boot animation (This can take up to 30 mins, so please wait!), after you should now see the android setup process.
Downloads
The fixed boot image can be downloaded from here.
The factory image: please make sure the version you are downloading matches the updated boot images'. It can be found here.
Modified Lineage OS ROM (boot image updated to the fix); it can be found here.
Magisk -> here.
GAPPS -> here. (Download for ARM64).
A fixed version of TWRP created by @XCnathan32 and updated by me to work with the 4-core boot image. Download Here.
Disclaimer
I will not be held responsible for anyone that decides to proceed with the steps listed above. If there are any issues please post them below with as much detail as you can. I will try my best to answer them, but I do have real-life stuff to deal with.
The original mod was not created myself! I have simply updated it.
Click to expand...
Click to collapse
With the second method, I flash all the files separately, and when I reboot it, the bootagement of Lineage OS started, but it got stuck, how do I fix it?
Dragon's Fedora said:
Nexus 5x BLOD fix (OPM2.171019.029)I recently purchased a Nexus 5x from ebay; it had the BLOD issue and, after many days I managed to fix it.
So I have decided to update the boot image to the 'latest' android factory image; this will allow people who have applied the patch to use a later version of Android or a custom ROM.
Click to expand...
Click to collapse
Good job! Works great for me and my similarly acquired device. Easy to read and follow write up too!
For others who may have done something weird like myself during the flash all process. The only issue I had initially was getting a boot and recovery sig not verified error message (or something like that). Worked around it by extracting the zipped image-bullhead-opm file and copying my fastboot files within the folder then fastboot flashing recovery, system and vendor manually. Then everything per steps explained worked as described. This is probably a common, well known error and fix to the BLOD Nexus 5X owners but I've just had this crazy device 2 days.
Thanks again!
Used 2nd method and worked perfectly.
Phone has been on non-the-less for a solid 3 hours and battery is stable (had really bad battery drain before, and the system was locking up and freezing and unresponsive as well 2-3 weeks before the BLOD.
I had also previously tried to flash a few other newer 8.1 roms after getting this BLOD, however phone crashed several times during installation and returned to BLOD and was unable to return to TWRP/recovery.
Glad the phone is back to life. Thanks a bunch for the modified rom, TWRP link, and guide!
On a side note, do you feel it is safe to try to flash other vendor images + roms + kernels now... or will the device go back to BLOD. From what I understood this is hardware issue, not software? @Dragon's Fedora
only4dank said:
Used 2nd method and worked perfectly.
Phone has been on non-the-less for a solid 3 hours and battery is stable (had really bad battery drain before, and the system was locking up and freezing and unresponsive as well 2-3 weeks before the BLOD.
I had also previously tried to flash a few other newer 8.1 roms after getting this BLOD, however phone crashed several times during installation and returned to BLOD and was unable to return to TWRP/recovery.
Glad the phone is back to life. Thanks a bunch for the modified rom, TWRP link, and guide!
On a side note, do you feel it is safe to try to flash other vendor images + roms + kernels now... or will the device go back to BLOD. From what I understood this is hardware issue, not software? @Dragon's Fedora
Click to expand...
Click to collapse
Whilst the issue is caused by the hardware; it's actually the software that causes the BLOD. The phone tries to use the 6 cores, but when it detects two of them failing it reboots the device. You can try use other; newer vendor images BUT you must make sure to change the boot.img file within the vendor zip folder.
Whilst the issue is caused by the hardware; it's actually the software that causes the BLOD. The phone tries to use the 6 cores, but when it detects two of them failing it reboots the device. You can try use other; newer vendor images BUT you must make sure to change the boot.img file within the vendor zip folder.
Dragon's Fedora said:
Whilst the issue is caused by the hardware; it's actually the software that causes the BLOD. The phone tries to use the 6 cores, but when it detects two of them failing it reboots the device. You can try use other; newer vendor images BUT you must make sure to change the boot.img file within the vendor zip folder.
Click to expand...
Click to collapse
there is a modified rom that is not stock to boot with the 4 cores, and flashed this boot and the recovery fixed and my nexus is restarted every 5 seconds I would appreciate your help and read many post and I think there is no solution
only4dank said:
Used 2nd method and worked perfectly.
Phone has been on non-the-less for a solid 3 hours and battery is stable (had really bad battery drain before, and the system was locking up and freezing and unresponsive as well 2-3 weeks before the BLOD.
I had also previously tried to flash a few other newer 8.1 roms after getting this BLOD, however phone crashed several times during installation and returned to BLOD and was unable to return to TWRP/recovery.
Glad the phone is back to life. Thanks a bunch for the modified rom, TWRP link, and guide!
On a side note, do you feel it is safe to try to flash other vendor images + roms + kernels now... or will the device go back to BLOD. From what I understood this is hardware issue, not software? @Dragon's Fedora
Click to expand...
Click to collapse
Which version of gapps did you use?
Hey all, just wanted to try and combine the bits and pieces of the "how to update OTA for rooted/BL unlocked" phones into one place as a quick run down for myself (and others who might have the same question) for the OTA:
Grab OTA update manually
Uninstall Edge Sense Mod from Magisk
Plug in phone into PC
adb reboot recovery
adb fastboot flash "stock boot.img"
adb sideload "OTA file name"
Reboot to bootloader using the volume and power button
adb fastboot flash "patched image to inactive slot (no idea how yet, sorry! Will add command)"
Reboot phone
Go back into Magisk and install manager for root
Re-install Edge Sense Mod within Magisk
*Optional*Re-apply Magisk Hide
Please let me know if there's any steps I'm missing or how it could be made easier for others to understand and if there's credit(s) missing (10+ hr shift and running on strong tea only 11 hr shift arguing with doctors to actually provide care instead of leeching insurance, and insurance to pay the damn medical claims instead of baton passing them to patients).
Disclaimer:
I'm no developer, just a common user that wants to make it a bit more convenient for other Pixel 3a owners to OTA update while rooted/BL unlocked. If it didn't work, or you encountered error(s), let me know and I can link them in so others can learn.
Disclaimer 2:
The above step(s) is assuming you've used pbanj's method for getting Magisk. Apparently I should add this as there's the "conventional" and "unconventional" method for Magisk. Had no idea since there was no guide available informing people otherwise at the time of making this step-by-step guide.
Credits:
pbanj for Pixel 3a root and Magisk images saving a MASSIVE some time, and its thread for the above steps.
googlephoneFKLenAsh for details of what I was missing in my initial steps.
sic0048 for making the root confusion apparent, and making a modified boot image method (the pbanj Magisk) here and his guide for rooting here.
Wdenton said:
Hey all, just wanted to try and combine the bits and pieces of the "how to update OTA for rooted/BL unlocked" phones into one place as a quick run down for myself (and others who might have the same question) for the OTA:
Grab OTA update manually
Uninstall Edge Sense Mod from Magisk
Plug in phone into PC
adb reboot recovery
adb sideload "OTA file name"
Reboot to bootloader using the volume and power button
fastboot flash "patched image"
Reboot phone
Go back into Magisk and install manager for root
Re-install Edge Sense Mod within Magisk
*Optional*Re-apply Magisk Hide
Please let me know if there's any steps I'm missing or how it could be made easier for others to understand and if there's credit(s) missing (10+ hr shift and running on strong tea only).
Disclaimer:
I'm no developer, just a common user that wants to make it a bit more convenient for other Pixel 3a owners to OTA update while rooted/BL unlocked.
Credits:
pbanj for Pixel 3a root and Magisk images saving a MASSIVE amount of time, and its thread for the above steps.
Click to expand...
Click to collapse
Before step 5, you need to fastboot flash stock boot.img before doing "adb sideload ota file".
I think step 7 should specify flashing patched image to inactive slot, (a or b), so as to be on the new active slot after a reboot, (step 8).
---------- Post added at 08:33 AM ---------- Previous post was at 08:28 AM ----------
googlephoneFKLenAsh said:
Before step 5, you need to fastboot flash stock boot.img before doing "adb sideload ota file".
Click to expand...
Click to collapse
I followed the op procedure and it worked without flashing the stock boot image. To what slot would you flash the stock image, active slot or inactive slot? Can it be flashed to old slot after step 8 reboot? Would there be any benefit?
I'm not sure why people insist that using the "modified" boot images make the update process faster or easier..... I assure you it does not.
Here is the update process if you install Magisk the normal way......
- Magisk: Click “Uninstall” → “restore images” → NO REBOOT
- Download and install OTA → NO REBOOT
- Clear all apps from recents (probably not even needed, but better to be safe than sorry).
- Magisk: Click “Install” → “Install to second/inactive slot (After OTA)”
- Reboot
That's all......... and it's all done from the phone. No computer or ADB is required for updates.
Tell me how that is harder than your method or how your method saves "a MASSIVE amount of time"?????
Look, I'll be the first to admit that using the modified boot images does make the initial root process easier and faster - by a few steps and about 2 minutes of time. But you will pay for it when it comes time to update your phone.
sic0048 said:
I'm not sure why people insist that using the "modified" boot images make the update process faster or easier..... I assure you it does not.
Here is the update process if you install Magisk the normal way......
- Magisk: Click “Uninstall” → “restore images” → NO REBOOT
- Download and install OTA → NO REBOOT
- Clear all apps from recents (probably not even needed, but better to be safe than sorry).
- Magisk: Click “Install” → “Install to second/inactive slot (After OTA)”
- Reboot
That's all......... and it's all done from the phone. No computer or ADB is required for updates.
Tell me how that is harder than your method or how your method saves "a MASSIVE amount of time"?????
Look, I'll be the first to admit that using the modified boot images does make the initial root process easier and faster - by a few steps and about 2 minutes of time. But you will pay for it when it comes time to update your phone.
Click to expand...
Click to collapse
Forgive me sic0048. You helped me in another post but I feared doing the initial step, magisk-uninstall-restore images. My reading of these forums indicates there is no stock image to restore since it was overwritten by the patched image during the initial root process. It is the transition from using patched images to doing a normal Magisk install that I lack knowledge of.
alliance1975 said:
Forgive me sic0048. You helped me in another post but I feared doing the initial step, magisk-uninstall-restore images. My reading of these forums indicates there is no stock image to restore since it was overwritten by the patched image during the initial root process. It is the transition from using patched images to doing a normal Magisk install that I lack knowledge of.
Click to expand...
Click to collapse
Great point, difference between downloading a patched boot image vs patching yourself is not clear as to how it affects the OTA update...
alliance1975 said:
Forgive me sic0048. You helped me in another post but I feared doing the initial step, magisk-uninstall-restore images. My reading of these forums indicates there is no stock image to restore since it was overwritten by the patched image during the initial root process. It is the transition from using patched images to doing a normal Magisk install that I lack knowledge of.
Click to expand...
Click to collapse
I totally understand the confusion......
If you use normal Magisk installation method where you let Magisk modify the stock boot.img file, then the OTA update method that I described above should work. Because you let Magisk modify the stock boot image, it will be able to use the stock image in the first step - Magisk: Click “Uninstall” → “restore images” → NO REBOOT
If you used the "modified boot image" method, you were able to skip the step where you let Magisk modify the stock boot image. This saves time initially, but it comes back to bit you during an OTA update because Magisk is unable to use the stock image to uninstall itself. You are correct that the normal Magisk "How to Take an OTA Update" instructions will fail if you used the modified boot image to gain root initially.
I guess I didn't realize that you had used the "modified boot image" method. Here is my recommendation to all those that have used the modified boot image method - start over.........
- use the Magisk manager app to Uninstall Magisk using the "Complete Uninstall" method.
- Pull the stock boot.img from the applicable factory image (whatever OS version/update you are currently on). Downloads are available here https://developers.google.com/android/images
- Using your computer, flash the stock boot.img file by using the command "fastboot flash boot boot.img"
- Reinstall Magisk using the "normal" method....
- Put the stock boot.img file on your phone's root SD card location
- Use the Magisk manager app to modify the stock boot.img
- move the magisk_modified boot image to your computer
- flash the magisk_modified boot image to the boot partition using the command "fastboot flash boot <patched_boot.img file name>"
- reboot
Then follow the instructions I gave for the normal OTA update process listed a couple posts above.
---------- Post added at 02:25 PM ---------- Previous post was at 02:14 PM ----------
duh1 said:
Unless I'm misunderstanding the process, seems like Magisk is missing a checkbox to backup the unpatched boot image prior to creating a patched image, for future OTA updates...
Click to expand...
Click to collapse
Magisk isn't missing this option, it's just that the method suggested by pbanj in this thread bypasses the normal method. It's not an issue with Magisk, it's an issue with the root method being suggested.
What I really need to do is create another "How to Root" thread and list the normal and recommended method. The confusion comes from people coming to this site and reading pbanj's thread and thinking that is the correct way to root. It is not the correct way to root.
alliance1975 said:
I think step 7 should specify flashing patched image to inactive slot, (a or b), so as to be on the new active slot after a reboot, (step 8).
---------- Post added at 08:33 AM ----------
I followed the op procedure and it worked without flashing the stock boot image. To what slot would you flash the stock image, active slot or inactive slot? Can it be flashed to old slot after step 8 reboot? Would there be any benefit?
Click to expand...
Click to collapse
Normally you would flash the stock boot image to the active slot to unroot the phone prior to installing the OTA.
Confused as to why flashing stock boot is no longer necessary. If this works as stated, it would appear the OTA is no longer patching the phone's boot and system partitions as had been done in the past. So perhaps the OTA now installs full boot and system images?
duh1 said:
Normally you would flash the stock boot image to the active slot to unroot the phone prior to installing the OTA.
Confused as to why flashing stock boot is no longer necessary. If this works as stated, it would appear the OTA is no longer patching the phone's boot and system partitions as had been done in the past. So perhaps the OTA now installs full boot and system images.
If that is indeed the case we should be able to just install the OTA normally through the system update button without having to uninstall Magisk and get rid of root first. Then as the Magisk tutorial states cancel the reboot go into the Magisk manager and reroot. Has anyone tried this on a rooted phone?
Click to expand...
Click to collapse
I had read, but have not confirmed myself, that the OTA images did include the boot and system img. However I just checked and the factory image for the June update on Bonito is 1.6gb while the "full OTA" image is only 1.1gb. So the two images are not identical. It's not like you saving a bunch of time by not uninstalling Magisk first and I don't think I would skip this simple step with the hope it would work. I'll continue to follow the recommended procedure that the Magisk developer has come up with and I would recommend to others that they do the same.
sic0048 said:
I had read, but have not confirmed myself, that the OTA images did include the boot and system img. However I just checked and the factory image for the June update on Bonito is 1.6gb while the "full OTA" image is only 1.1gb. So the two images are not identical. It's not like you saving a bunch of time by not uninstalling Magisk first and I don't think I would skip this simple step with the hope it would work. I'll continue to follow the recommended procedure that the Magisk developer has come up with and I would recommend to others that they do the same.
Click to expand...
Click to collapse
It's smaller as the OTA only contains the partitions that have changed such as system and boot. The other partitions are probably cloned over from the active slot to the inactive slot.
As I mentioned previously, the Magisk tutorial does not account for not having a backup of the stock boot image when you download the patched boot, so to remove boot prior to installing the OTA, you must manually flash the stock boot.
googlephoneFKLenAsh said:
Before step 5, you need to fastboot flash stock boot.img before doing "adb sideload ota file".
Click to expand...
Click to collapse
alliance1975 said:
I think step 7 should specify flashing patched image to inactive slot, (a or b), so as to be on the new active slot after a reboot, (step 8).
---------- Post added at 08:33 AM ---------- Previous post was at 08:28 AM ----------
I followed the op procedure and it worked without flashing the stock boot image. To what slot would you flash the stock image, active slot or inactive slot? Can it be flashed to old slot after step 8 reboot? Would there be any benefit?
Click to expand...
Click to collapse
Before step 5, flash stock boot.img to slot a (or just use getvar to get the current active slot. It should be slot a before first ota). If you don't flash stock boot img, you will get error message "E: Failed to verify package compatibility".
I think you didn't get this message because you actually restored stock boot.img when you uninstalled magisk. For those who rooted their phone by flashing patched boot.img, magisk doesn't know the location of stock boot.img.
Then in step 7, flash patched boot.img to slot b (after ota, the active changes to slot b. If there is new ota in the future, just use getvar to find out the active slot)
sic0048 said:
I'm not sure why people insist that using the "modified" boot images make the update process faster or easier..... I assure you it does not.
Here is the update process if you install Magisk the normal way......
- Magisk: Click “Uninstall” → “restore images” → NO REBOOT
- Download and install OTA → NO REBOOT
- Clear all apps from recents (probably not even needed, but better to be safe than sorry).
- Magisk: Click “Install” → “Install to second/inactive slot (After OTA)”
- Reboot
That's all......... and it's all done from the phone. No computer or ADB is required for updates.
Tell me how that is harder than your method or how your method saves "a MASSIVE amount of time"?????
Look, I'll be the first to admit that using the modified boot images does make the initial root process easier and faster - by a few steps and about 2 minutes of time. But you will pay for it when it comes time to update your phone.
Click to expand...
Click to collapse
sic0048 said:
I totally understand the confusion......
If you use normal Magisk installation method where you let Magisk modify the stock boot.img file, then the OTA update method that I described above should work. Because you let Magisk modify the stock boot image, it will be able to use the stock image in the first step - Magisk: Click “Uninstall” → “restore images” → NO REBOOT
If you used the "modified boot image" method, you were able to skip the step where you let Magisk modify the stock boot image. This saves time initially, but it comes back to bit you during an OTA update because Magisk is unable to use the stock image to uninstall itself. You are correct that the normal Magisk "How to Take an OTA Update" instructions will fail if you used the modified boot image to gain root initially.
I guess I didn't realize that you had used the "modified boot image" method. Here is my recommendation to all those that have used the modified boot image method - start over.........
- use the Magisk manager app to Uninstall Magisk using the "Complete Uninstall" method.
- Pull the stock boot.img from the applicable factory image (whatever OS version/update you are currently on). Downloads are available here https://developers.google.com/android/images
- Using your computer, flash the stock boot.img file by using the command "fastboot flash boot boot.img"
- Reinstall Magisk using the "normal" method....
- Put the stock boot.img file on your phone's root SD card location
- Use the Magisk manager app to modify the stock boot.img
- move the magisk_modified boot image to your computer
- flash the magisk_modified boot image to the boot partition using the command "fastboot flash boot <patched_boot.img file name>"
- reboot
Then follow the instructions I gave for the normal OTA update process listed a couple posts above.
---------- Post added at 02:25 PM ---------- Previous post was at 02:14 PM ----------
Magisk isn't missing this option, it's just that the method suggested by pbanj in this thread bypasses the normal method. It's not an issue with Magisk, it's an issue with the root method being suggested.
What I really need to do is create another "How to Root" thread and list the normal and recommended method. The confusion comes from people coming to this site and reading pbanj's thread and thinking that is the correct way to root. It is not the correct way to root.
Click to expand...
Click to collapse
googlephoneFKLenAsh said:
Before step 5, flash stock boot.img to slot a (or just use getvar to get the current active slot. It should be slot a before first ota). If you don't flash stock boot img, you will get error message "E: Failed to verify package compatibility".
I think you didn't get this message because you actually restored stock boot.img when you uninstalled magisk. For those who rooted their phone by flashing patched boot.img, magisk doesn't know the location of stock boot.img.
Then in step 7, flash patched boot.img to slot b (after ota, the active changes to slot b. If there is new ota in the future, just use getvar to find out the active slot)
Click to expand...
Click to collapse
googlephoneFKLenAsh said:
Before step 5, you need to fastboot flash stock boot.img before doing "adb sideload ota file".
Click to expand...
Click to collapse
Thanks to all, was not expecting this much reply in this short amount of time, at all.
I made this step by step guide because no dedicated thread really was readily accessible in one place. Hopefully this inspires others to make guides.
googlephoneFKLenAsh said:
Before step 5, flash stock boot.img to slot a (or just use getvar to get the current active slot. It should be slot a before first ota). If you don't flash stock boot img, you will get error message "E: Failed to verify package compatibility".
I think you didn't get this message because you actually restored stock boot.img when you uninstalled magisk. For those who rooted their phone by flashing patched boot.img, magisk doesn't know the location of stock boot.img.
Click to expand...
Click to collapse
How else could the phone have been rooted besides flashing a patched boot image on a device without a custom recovery, such that Magisk on his device knows where to find the stock boot image?
duh1 said:
How else could the phone have been rooted besides flashing a patched boot image on a device without a custom recovery, such that Magisk on his device knows where to find the stock boot image?
Click to expand...
Click to collapse
Learn how to read a few posts in this thread.
Root method 1: install magisk, patch the stock boot image, then flash the patched boot image to gain root. Magisk knows where the stock boot image is. In this case, just follow the instructions to take ota: uninstall magisk to restore stock boot image and take ota, then reroot.
Root method 2: flash patched boot image provided by someone in the forum, then install magisk to get root. In this case Magisk doesn't have a backuped stock boot image. So the regular instructions of uninstalling Magisk to restore stock boot image doesn't work and you need to manually flash stock boot image to take ota.
googlephoneFKLenAsh said:
Learn how to read a few posts in this thread.
Root method 1: install magisk, patch the stock boot image, then flash the patched boot image to gain root. Magisk knows where the stock boot image is. In this case, just follow the instructions to take ota: uninstall magisk to restore stock boot image and take ota, then reroot.
Root method 2: flash patched boot image provided by someone in the forum, then install magisk to get root. In this case Magisk doesn't have a backuped stock boot image. So the regular instructions of uninstalling Magisk to restore stock boot image doesn't work and you need to manually flash stock boot image to take ota.
Click to expand...
Click to collapse
Difference is downloading the patched image vs patching it yourself. Wasn't clear how that created the issue. Well written, thx for pointing it out.
So if anyone patches the new version boot image before uninstalling Magisk, they'll get an error. Likewise, patching the current boot image in the manager will allow the uninstall to work correctly...
googlephoneFKLenAsh said:
Learn how to read a few posts in this thread.
Root method 1: install magisk, patch the stock boot image, then flash the patched boot image to gain root. Magisk knows where the stock boot image is. In this case, just follow the instructions to take ota: uninstall magisk to restore stock boot image and take ota, then reroot.
Root method 2: flash patched boot image provided by someone in the forum, then install magisk to get root. In this case Magisk doesn't have a backuped stock boot image. So the regular instructions of uninstalling Magisk to restore stock boot image doesn't work and you need to manually flash stock boot image to take ota.
Click to expand...
Click to collapse
you dont need to restore stock to update. the restore is only needed if you want the phone to handle the update. if you sideload the ota in adb it updates fine then you can just flash the new patched boot image. also fun little fact, even if you use the pre-patched images you can still use magisk's internal update method. you just have to do one simple thing....... grab the stock boot.img for your current update, and tell magisk to patch it, it will create the stock backup and then you can just use the magisk update method. i've been meaning to add that to my thread but i've been busy and having some health problems so i haven't been on here in a few days.
pbanj said:
you dont need to restore stock to update. the restore is only needed if you want the phone to handle the update. if you sideload the ota in adb it updates fine then you can just flash the new patched boot image. also fun little fact, even if you use the pre-patched images you can still use magisk's internal update method. you just have to do one simple thing....... grab the stock boot.img for your current update, and tell magisk to patch it, it will create the stock backup and then you can just use the magisk update method. i've been meaning to add that to my thread but i've been busy and having some health problems so i haven't been on here in a few days.
Click to expand...
Click to collapse
Sorry for the health issues. Take care and get well soon.
Thank you for this post. I was getting confused about the ADB sideload of OTA (which, iirc, didn't work on unlocked BL on my last phone), which you said does work on the 3a. My last phone was the N5X and despite Magisk being available, I stayed with SuperSu (which worked for me as well as suhide and FlashFire). The dual slot is new to me; I think my MOTO Z3 Play has that (I'm not unlocking that one atm) so it really doesn't matter.
If I fastboot flashed the patched boot.img to slot_b, then the next time I flash any boot.img, I will have to direct it to slot_a [fastboot flash boot_a boot.img]? I guess I'll learn as I go along. Next, I'll take current stock boot.img and tell magisk to patch it.
ritchea said:
Sorry for the health issues. Take care and get well soon.
Thank you for this post. I was getting confused about the ADB sideload of OTA (which, iirc, didn't work on unlocked BL on my last phone), which you said does work on the 3a. My last phone was the N5X and despite Magisk being available, I stayed with SuperSu (which worked for me as well as suhide and FlashFire). The dual slot is new to me; I think my MOTO Z3 Play has that (I'm not unlocking that one atm) so it really doesn't matter.
If I fastboot flashed the patched boot.img to slot_b, then the next time I flash any boot.img, I will have to direct it to slot_a [fastboot flash boot_a boot.img]? I guess I'll learn as I go along. Next, I'll take current stock boot.img and tell magisk to patch it.
Click to expand...
Click to collapse
ya pretty much. every time the phone updates the active slot changes. I'm currently updating my root thread so everything is clearer and in one place.
pbanj said:
you dont need to restore stock to update. the restore is only needed if you want the phone to handle the update. if you sideload the ota in adb it updates fine then you can just flash the new patched boot image. also fun little fact, even if you use the pre-patched images you can still use magisk's internal update method. you just have to do one simple thing....... grab the stock boot.img for your current update, and tell magisk to patch it, it will create the stock backup and then you can just use the magisk update method. i've been meaning to add that to my thread but i've been busy and having some health problems so i haven't been on here in a few days.
Click to expand...
Click to collapse
Just to be sure, sideloading bypasses the OTA package compatibility verification that would give an error during normal update if it detects wrong boot version?
duh1 said:
Just to be sure, sideloading bypasses the OTA package compatibility verification that would give an error during normal update if it detects wrong boot version?
Click to expand...
Click to collapse
correct. i had no issue with it, and i friend is the one who told me about it as that's how she installs her updates even though she could use the magisk method