Related
It seems no matter how much this topic gets discussed, people still use old methods and they either fail, or they break something like WiFi, Mobile Data, infinite bootloop, or getting stuck on the boot logo... THIS DOESN'T HAVE TO HAPPEN and it IS repairable, usually without reflashing the entire image. The problem comes from using an old method, outdated SuperSU, or incorrect method. This guide will help you correct most issues, or help you to flash root correctly the FIRST time.
I have written rooting guides for multiple Moto device, and I have owned many Moto devices as well, so I have some idea what I am saying and I have tested these methods extensively, they work.
------------------------
This guide covers ALL Moto X 2015 models that can be bootloader unlocked and have TWRP available, it doesn't matter if it is the XT1575 or XT1572, the method is identical (untested on Chinese XT1570, but it should work). In fact, this method will work on all 2015 and 2016 series Moto phones running Marshmallow, including the Moto E, X, G3, G4, and Z with the appropriate TWRP image.
Please read completely and make sure you understand each step and how to do it, if you don't get something search the thread or ask an open question, no offense, but do not PM me with a question because you think it is too stupid to ask in public (we all started as noobs), or because you want me to hold your hand and do it for you, I will politely tell you no and ask you to post in the thread.
If you are coming here because you followed an old guide where you used a special boot.img file and now you have no service (WiFi and/or mobile data) and you don't have a TWRP backup to restore first, well, the RIGHT way to fix it is to reflash the current stock firmware image and start over... why? Because the various "help" people give to have you flash the radio files that match the kernel (ie. boot image) that was patched for the old style root method, has now put you in a mismatched firmware environment and could potentially brick on the next OTA. If you are in this situation and don't know for to properly fix it... go to the FAQ section in post #3 below (WIP-incomplete).
If came are coming here to root the first time, or you just thought you could flash SuperSU and reboot and now stuck in either a bootloop or stuck on the boot logo... Your in luck, read on, because we can fix that in a jiffy!
tl;dr version for advanced users: Skip to "How to do it" section to root, or "Do the prep" section to fix a bad root.
I am writing this tutorial because there are still lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto X P/S, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover the details of rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread.
Prerequisites:
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: Performing this prerequisite will give you all the tools (fastboot) and drivers needed to continue, and wipe your device, meaning erase all your information and programs. Make sure to backup any important data first. This step will also permanently void your warranty once an unlock code has been issued by Moto, it doesn't matter if you even use it, your warranty is done.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See the official TWRP pages for clark here. I will NOT teach you how to use TWRP in this thread, if you are going to root you need to understand that your self, but if you get in a real bind I may knudge you in the right direction. I will tell you that there are two modes, flashed or booted, the later is much better if you plan to take an OTA later as long as you don't do something stupid like flash Xposed.
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device, you can always fine the latest stable version here: https://download.chainfire.eu/supersu/ As of this posting update UPDATE-SuperSU-v2.82-20170528234214.zip (version 2.82) is the current stable version and it has been tested and verified to work.
NOTE: Unless otherwise stated, do not use a beta version for rooting Moto devices. SuperSU versions with even numbers are stable versions, while odd numbered versions are beta editions.
4) Reboot and start TWRP recovery, the method you use to do this doesn't matter (boot or flash).
5) Backup your device with TWRP to your SD card, even if you just unlocked and the phone is as blank as a printed page from a 1988 HP DeskJet printer with it's original cartridges still installed, backup... You will always have a good point to return to if the worst happens.
Do the prep:
Note that the hidden Do the prep section is ONLY for repairing a bad flash, SuperSU has been updated and as of version 2.79 the hidden section should no longer be needed for general purpose root on a working device, you just flash SuperSU. If you flashed an older version and are bootlooped, perform this section and continue.
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, when you have your backups and are ready to root, first go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press ENTER (there is no confirmation returned). You can verify this worked correctly by entering 'cat /data/.supersu' in the terminal and see if it returns "SYSTEMLESS=true", if not, you did it wrong, try the echo command again. Now press exit/back and press the HOME key.
After you have successfully entered the command in the TWRP Terminal you may continue
How to do it:
Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
Again, this is somewhat dated information and only applies to fixing a bootlooping device when improperly rooted.
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
If you need assistance, we need detailed information about what what's going on and what you have tried to do... Please provide details including:
1) Device model number and Android version
2) TWRP version
3) SuperSU version
4) Output of 'cat /data/.supersu' from TWRP terminal
And a copy of recovery.log if possible, and any other pertinent information you can think of. Without specific information there is nothing that I can do to assist you and request for help may be ignored.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
NOTE: I no longer own this device, but will help where I can and will keep this thread open to assist users where ever possible, but I no longer have a device to test/verify things with.
Alternate Method #1
Some users have noted that the above method doesn't seem to work, we don't know why as it seems inconsistent but we can't pin it down specifically to user error, certain model number or build, or anything else, as it works 98% of the time...
But if the above method fails, the alternative is to download and copy to SD card or internal storage SuperSU 2.62-3 ßeta version available here and flash it through TWRP like normal.
Reserved - FAQ (oops, guess I already did that)
I'm so glad I found this thread! I've been procrastenating fixing my phone because of all the crappy methods. This one very easy to follow!
But still can't manage to get my WiFi working
I don't get it. But somehow my nandroid backup failed too, because it's only some 2.X MB big and I don't seem to recover anything....
So I guess I'll have to keep trying..
FYI:
1) Moto X Style 6.0
2) TWRP 3.0.2-0
3) Tried both 2.78 and 2.62. Currently running 2.62
4) SYSTEMLESS=true
Jorinde123 said:
I'm so glad I found this thread! I've been procrastenating fixing my phone because of all the crappy methods. This one very easy to follow!
But still can't manage to get my WiFi working
I don't get it. But somehow my nandroid backup failed too, because it's only some 2.X MB big and I don't seem to recover anything....
So I guess I'll have to keep trying..
FYI:
1) Moto X Style 6.0
2) TWRP 3.0.2-0
3) Tried both 2.78 and 2.62. Currently running 2.62
4) SYSTEMLESS=true
Click to expand...
Click to collapse
Find the latest rom image for the version you have installed, and flash the radios with fastboot.
acejavelin said:
Find the latest rom image for the version you have installed, and flash the radios with fastboot.
Click to expand...
Click to collapse
Thanks for your quick reply. Tried that, didn't work.. The ROM i'm currently running is MPH24.49-18 btw... I'm now trying it the hard way, just reverting everything step by step. But the first step (flashing gpt.bin) is already giving me the preflash error. This is going to be a lot harder than I thought and it's been too long since I've been flashing these things.
Used to flash my Moto Milestone and my Sony X10, can you imagine.
Jorinde123 said:
Thanks for your quick reply. Tried that, didn't work.. The ROM i'm currently running is MPH24.49-18 btw... I'm now trying it the hard way, just reverting everything step by step. But the first step (flashing gpt.bin) is already giving me the preflash error. This is going to be a lot harder than I thought and it's been too long since I've been flashing these things.
Used to flash my Moto Milestone and my Sony X10, can you imagine.
Click to expand...
Click to collapse
Because you are not on 49-18, if you were on the latest OTA for 6.0 you were on 49-18-4. Pre-flash validation failure confirms your using the wrong version. Look in my sig for the return to stock thread, there are links to current roms and discussion of the 'preflash validation error'.
Wasn't systemless method only intended for not altering the system partition in such way not to break compatibility with Android Pay and such apps that don't allow root?
Maybe I got it wrong when I first saw the appearance on the scene of systemless root. From what you are saying the auto detect it's supposed to detect with which method the device is compatible (not only detects if system was already modified? let's say like by TWRP).
I wasn't able to flash SuperSu newest stable versions either, all ended up stuck at boot, except for the 2.62 version (updatable later through playstore and binaries thorugh app via normal update). Honestly I haven't tried systemless as for me I through it was a waste (as said I through it wasn't meant for other purpose).
ATM I'm using CM's own root, but I will report as soon as I will try SU again. I never had problems with modem/wifi with SU, only that it didn't boot on newer stable builds.
Got the Moto X Pure a few days ago. It came with 6.0. This procedure works. Thank you!
ban.codrut said:
Wasn't systemless method only intended for not altering the system partition in such way not to break compatibility with Android Pay and such apps that don't allow root?
Maybe I got it wrong when I first saw the appearance on the scene of systemless root. From what you are saying the auto detect it's supposed to detect with which method the device is compatible (not only detects if system was already modified? let's say like by TWRP).
I wasn't able to flash SuperSu newest stable versions either, all ended up stuck at boot, except for the 2.62 version (updatable later through playstore and binaries thorugh app via normal update). Honestly I haven't tried systemless as for me I through it was a waste (as said I through it wasn't meant for other purpose).
ATM I'm using CM's own root, but I will report as soon as I will try SU again. I never had problems with modem/wifi with SU, only that it didn't boot on newer stable builds.
Click to expand...
Click to collapse
No, although that was one thing we thought we would gain (which we didn't), Systemless root is to get around Marshmallow security. Root is detected by SafetyNet API, and it detects pretty much any system modification, systemless or not
Currently Using TWRP 3.0.2.0 . Just unlocked bootloader and haven't done anything else . Recovery flash went well during the initial process of unlocking . Now Im trying to make a backup of the stock Rom , everytime I try to make one I keep getting failed at the end of the process ? Is this a known bug ? I have been doing google searches for the past hour and still unable to find anything to indicate anyone else is having this problem . Unless I didn't use the correct terms while searching . Any help would be appreciated
SouthernEvo said:
Currently Using TWRP 3.0.2.0 . Just unlocked bootloader and haven't done anything else . Recovery flash went well during the initial process of unlocking . Now Im trying to make a backup of the stock Rom , everytime I try to make one I keep getting failed at the end of the process ? Is this a known bug ? I have been doing google searches for the past hour and still unable to find anything to indicate anyone else is having this problem . Unless I didn't use the correct terms while searching . Any help would be appreciated
Click to expand...
Click to collapse
It is not a known issue... Where are you storing the backup, internal storage or SD card?
acejavelin said:
It is not a known issue... Where are you storing the backup, internal storage or SD card?
Click to expand...
Click to collapse
Was backing up to the SD Card . Been messing with it and now its working for some weird reason . I appreciate your quick response though
I used windroid to unlock the bootloader and install twrp( don't reboot system but rather boot into recovery to make twrp stick) , from there I just flashed supersu and I was good to go. Many methods out there but this worked for me.
Thank you so much for this guide. I have to say, as a new Motorola user coming from Samsung phones exclusively, this whole process made me feel like a real noob again.
I made the switch from iOS to Android back when the Galaxy S2 came out because I grew tired of the jailbreak cat and mouse games on the iPhones and iPads. Learning to root and flash ROMs on all my subsequent Samsung devices was fairly simple and very enjoyable. This Moto X Pure though was a real tasker for me. I honestly never knew about the extra steps you had to take to unlock, twrp and root this phone. I really wish manufactures would help us make this much easier.
Anyway, thank you again for your help. I'll be seeing y'all around the forums as a new MXPE user!
acejavelin said:
No, although that was one thing we thought we would gain (which we didn't), Systemless root is to get around Marshmallow security. Root is detected by SafetyNet API, and it detects pretty much any system modification, systemless or not
Click to expand...
Click to collapse
Thank you for clarifying a misconception I had on systemless root
(I intentioned to reply to you earlier, but the mad busy week made me forget about my intent )
I'm going to try right now the latest stable with systemless method (rather than flashing the older version) on a full wiped clean stock to see if it works. (Even tho I see lots of feedbacks here inspiring me to believe it would)
In what order?
acejavelin said:
It seems no matter how much this topic gets discussed, people still use old methods and they either fail, or they break something like WiFi, Mobile Data, infinite bootloop, or getting stuck on the boot logo... THIS DOESN'T HAVE TO HAPPEN and it IS repairable, usually without reflashing the entire image. The problem comes from using an old method, outdated SuperSU, or incorrect method. This guide will help you correct most issues, or help you to flash root correctly the FIRST time.
I have written rooting guides for multiple Moto device, and I have owned many Moto devices as well, so I have some idea what I am saying and I have tested these methods extensively, they work.
------------------------
This guide covers ALL Moto X 2015 models that can be bootloader unlocked and have TWRP available, it doesn't matter if it is the XT1575 or XT1572, the method is identical (untested on Chinese XT1570, but it should work). In fact, this method will work on all 2015 and 2016 series Moto phones running Marshmallow, including the Moto E, X, G3, G4, and Z with the appropriate TWRP image.
Please read completely and make sure you understand each step and how to do it, if you don't get something search the thread or ask an open question, no offense, but do not PM me with a question because you think it is too stupid to ask in public (we all started as noobs), or because you want me to hold your hand and do it for you, I will politely tell you no and ask you to post in the thread.
If you are coming here because you followed an old guide where you used a special boot.img file and now you have no service (WiFi and/or mobile data) and you don't have a TWRP backup to restore first, well, the RIGHT way to fix it is to reflash the current stock firmware image and start over... why? Because the various "help" people give to have you flash the radio files that match the kernel (ie. boot image) that was patched for the old style root method, has now put you in a mismatched firmware environment and could potentially brick on the next OTA. If you are in this situation and don't know for to properly fix it... go to the FAQ section in post #3 below (WIP-incomplete).
If came are coming here to root the first time, or you just thought you could flash SuperSU and reboot and now stuck in either a bootloop or stuck on the boot logo... Your in luck, read on, because we can fix that in a jiffy!
tl;dr version for advanced users: Skip to "How to do it" section
I am writing this tutorial because there are still lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto X P/S, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover the details of rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread.
Prerequisites:
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: Performing this prerequisite will give you all the tools (fastboot) and drivers needed to continue, and wipe your device, meaning erase all your information and programs. Make sure to backup any important data first. This step will also permanently void your warranty once an unlock code has been issued by Moto, it doesn't matter if you even use it, your warranty is done.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See the official TWRP pages for clark here. I will NOT teach you how to use TWRP in this thread, if you are going to root you need to understand that your self, but if you get in a real bind I may knudge you in the right direction. I will tell you that there are two modes, flashed or booted, the later is much better if you plan to take an OTA later as long as you don't do something stupid like flash Xposed.
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device, you can always fine the latest stable version here: https://download.chainfire.eu/supersu/ As of this posting SR4-SuperSU-v2.78-SR4-20161115184928.zip is the current stable version and it has been tested and verified to work.
NOTE: Unless otherwise stated, do not use a beta version for rooting Moto devices. SuperSU versions with even numbers are stable versions, while odd numbered versions are beta editions.
4) Reboot and start TWRP recovery, the method you use to do this doesn't matter (boot or flash).
5) Backup your device with TWRP to your SD card, even if you just unlocked and the phone is as blank as a printed page from a 1988 HP DeskJet printer with it's original cartridges still installed, backup... You will always have a good point to return to if the worst happens.
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. You can verify this worked correctly by entering 'cat /data/.supersu' and see if it returns "SYSTEMLESS=true", if not, you did it wrong, try the echo command again.
Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
If you need assistance, we need detailed information about what what's going on and what you have tried to do... Please provide details including:
1) Device model number and Android version
2) TWRP version
3) SuperSU version
4) Output of 'cat /data/.supersu' from TWRP terminal
And a copy of recovery.log if possible, and any other pertinent information you can think of. Without specific information there is nothing that I can do to assist you and request for help may be ignored.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Click to expand...
Click to collapse
I really appreciate the help, but I have one question. Do I flash SuperSu and then type the command into the terminal, or do I type the terminal command first?
Thanks again for your help,
Matt
Iglooian said:
I really appreciate the help, but I have one question. Do I flash SuperSu and then type the command into the terminal, or do I type the terminal command first?
Thanks again for your help,
Matt
Click to expand...
Click to collapse
First, a little etiquette lesson, please don't quote long posts (especially the first post) for no reason, at the very least edit it down to only show the relevant parts so people don't have to scroll through a long meaningless quote.
And to answer your question, you enter the terminal command first, then install SuperSU, that is how it is ordered in the first post instructions. If you read the entire first post, it explains what the command does, and logic therefore lets you know it must be done first.
acejavelin said:
First, a little etiquette lesson, please don't quote long posts (especially the first post) for no reason, at the very least edit it down to only show the relevant parts so people don't have to scroll through a long meaningless quote.
And to answer your question, you enter the terminal command first, then install SuperSU, that is how it is ordered in the first post instructions. If you read the entire first post, it explains what the command does, and logic therefore lets you know it must be done first.
Click to expand...
Click to collapse
Actually, it was unclear what order I was supposed to do it in; we call that a clarifying question, but thanks anyway.
Iglooian said:
Actually, it was unclear what order I was supposed to do it in; we call that a clarifying question, but thanks anyway.
Click to expand...
Click to collapse
Fair enough... I will edit the "How to do it" section to make it more clear.
So I did the whole unlock bootloader flashed a custom rom, flashed twrp and did the verify boot image. And it worked flawlessly. I then decided to root the phone using supersu and verified again. it worked. I decided to do Magisk and now nothing I can do works. I flashed magisk did the verify, and it booted but said it was rooted but magisk was not installed. So I went back into recovery and flashed my custom rom again, twrp, magisk, then verify and now all it does it reboot a couple times till it gets to the google logo then it reboots into recovery. What can I do to fix this?
@KingAroan I've been there several times. Do you know how to revert to a stock image?
Here's the link to download a stock image.
Are you using linux or Windows? Either way keep in mind USB3 (blue plugs) are prone to issues unless you know how to work around them.
Thanks. I went back to stock to fix it, just upset because i didn't get to backup anything haha. Didn't know about blue plug USB causing issue's. I'll stick with the 2.0 plugs thanks for the information.
KingAroan said:
Thanks. I went back to stock to fix it, just upset because i didn't get to backup anything haha. Didn't know about blue plug USB causing issue's. I'll stick with the 2.0 plugs thanks for the information.
Click to expand...
Click to collapse
Ok, now I'm feeling kind of bad. I hoped you would reply before doing stuff!!! But I know the urgency. if you remove the "-w" from the "fastboot" lines in the script(s) then it won't actually format your internal storage. Sorry man. But I'm glad you got it working again.
As a general rule - when messing with SuperSU and Magisk and stuff like that, ya always want to read the install instructions carefully to figure out if you can install it at your current system state, or if you need a "new system state" (like a fresh install).
If you setup a fresh install properly you won't actually have to wipe all your data. I know it's tricky. Hopefully you have original copies of everything on your phone. If not, let me know and I'll show you some good methods for backing up your data. I might have to ask more questions for your setup though. Some backup solutions require root. Some don't.
Glad I could help, though I wish it was under better circumstances
It's fine I flashed stock the same night. I appreciate the information. I am backing up myself information with titanium backup and storing it on my Google drive for safety just in case I mess up another flash. I think I messed up by trying to flash magisk v12 and then I found the pixel version separately... So it was my mistake.
KingAroan said:
It's fine I flashed stock the same night. I appreciate the information. I am backing up myself information with titanium backup and storing it on my Google drive for safety just in case I mess up another flash. I think I messed up by trying to flash magisk v12 and then I found the pixel version separately... So it was my mistake.
Click to expand...
Click to collapse
Sir, I understand all too well.
Let me know if I can help in the future. I'm generally well versed on the Windows side, and getting much more well versed on the Linux side.
There is generally a specific order to do stuff in, with any kind of tinkering. And with Pixel and it's crazy partitions, all the more so.
Yeah the pixel order is crazy especially with having to sign the boot images.
I never thought that this would happen, especially after 6 years of being an ardent flashaholic but here I am like another noob requesting for guidance.
So it started a few days back when the Flashaholic in me wanted something to divert my mind from the monotonicity of a good ROM.I was using "[8.1.x][WEEKLIES] CarbonROM | cr-6.1 [bacon]" Rom on my 3 year old bacon happily when I decided to try "Crdroid ROM for OnePlus ONE crdroid-4.6".
As mentioned in the instructions I followed the steps to each word i.e. wipe,flash rom and then gapps (using modded twrp-3.2.1-K2-bacon.)and the ROM booted fine.I setup it as usual post boot however I faced few reboots which made me doubt myself so i thought of reflashing the same ROM again but the butter fingers got the best of me and while selecting partitions to WIPE( I guess) I selected some incorrect partition and after the flash my phone went into bootloop..
I tried to boot into recovery but I wasnt able to so but I knew I could boot into recovery using Fastboot so I reflashed the recovery while in fastboot mode and ran fastboot boot TWRP.img as I wasnt able to boot into recovery with VolumeDown+Power.I tried to fetch the nandroid backup but to my astonishment it was gone and my /data partition was wiped clean.I blame myself as I must have done something wrong as I was panicked.
Since then(last sunday)my phone has been in bootloop and doesnt start in recovery unless I boot recovery from fastboot. I have spent countless hours to fix it and the things I have tried already are mentioned below
1)Flash Stock rom (CM11,CM12,CM13)
2)Erase and flash persist.img
3)Flashed CM13 snapshot or bacon_firmware_update_2015_05-15_DI.3.0.c6-00241.zip followed by RR 5.8.5 ,RR 6.0 ,Carbon rom 6.1 and c-droid 4.6
4)Flashed coloros and then stock rom(CM11,CM12,CM13) or RR 5.8.5 ,RR 6.0 ,Carbon rom 6.1 and c-droid 4.6
I have gone through this awesome guide ultimate-answer-to-bacon-flavored- by @Timmmmaaahh ,other noob friendly guides indexes , compilations ,threads on softbrick and hardbrick topics and used almost every tool created for one plus one.
I have ruled out below
1)Volume button not working as I can boot into fastboot fine using VolumeUp+Power button
2)Battery not working as my phone can stay in fastboot for pretty much a day with 50% battery or bootloops throughtout the day
I am really out of my depth and I am trying to find where I had kept my nandroid backup on Laptop/Drive but I dont think even that can help me now.I have lost a lot of precious and Important data due to my panicking and wouldnt want to lose my phone so any help and guidance would be really appreciated.
Hopefully I am posting in the correct place and havent breached any XDA rules!Aplogies in advance if I have
you are sure, that you have flash thr TWRP and not only load TWRP via sideload into the ram?
please post the command, which you have send to the phone
So I use below command to install the twrp from fasboot
fasboot flash recovery <path/twrp file>
Also I've tried to flash twrp in recovery from twrp by selecting image file option but it doesn't boot into recovery ever
I've tried twrp 2.7,2.8,3.0,3.1 and 3.2 as well on every rom that I've flasher given the compatibility.
to boot into recovery as it's not accessible I use below command
Fastboor boot <path/twrp file>
Stupid thing it seems but try different micro usb cable
vedanth123456 said:
So I use below command to install the twrp from fasboot
fasboot flash recovery <path/twrp file>
Also I've tried to flash twrp in recovery from twrp by selecting image file option but it doesn't boot into recovery ever
I've tried twrp 2.7,2.8,3.0,3.1 and 3.2 as well on every rom that I've flasher given the compatibility.
to boot into recovery as it's not accessible I use below command
Fastboor boot <path/twrp file>
Click to expand...
Click to collapse
Okay, let's optimize your environment first. Make sure the path to your adb is c:\adb (don't flash stuff like "c:\users\dinky doodle\my awesome downloads\android shizzle\recovery manizzle"). Use the amazing 15 seconds adb installer and let it install the drivers as well. @kallum7 makes a good point, do try that.
Use the TWRP recommended in my guide and follow the clean flash steps (including CM13 step again).
More importantly: check md5 hashes on all your downloads. You really want to avoid flashing a corrupted recovery download. Only continue flashing ROMs once you have a stable TWRP installation going. If it's not properly booting to TWRP, do not bother flashing anything else.
When successfully booted in TWRP, make sure MTP is enabled under mount and connect it to your PC. Browse for possible backups via your computer. If you can't find any, you've probably wiped internal memory. If you didn't make a copy to your computer, the data is most likely gone forever (sorry).
Panicking is indeed a bad idea, we've all been there and it's an excellent learning process (you'll appreciate your failures later, lol). It's better to work step by step slowly, make sure you read everything thoroughly. When in doubt, just post here and we'll follow up. We'll get there, don't worry.
---------- Post added at 08:51 AM ---------- Previous post was at 08:47 AM ----------
Oh and rename the recovery file to recovery.img and place it in your adb folder to avoid any complications. Less = more!
Because I had bricked my phone a few months ago and I changed my USB cable and it worked perfect
kallum7 said:
Stupid thing it seems but try different micro usb cable
Click to expand...
Click to collapse
Thanks mate..I did try that but it didn't endure fruitful results
Timmmmaaahh said:
Okay, let's optimize your environment first. Make sure the path to your adb is c:\adb (don't flash stuff like "c:\users\dinky doodle\my awesome downloads\android shizzle\recovery manizzle"). Use the amazing 15 seconds adb installer and let it install the drivers as well. @kallum7 makes a good point, do try that.
Use the TWRP recommended in my guide and follow the clean flash steps (including CM13 step again).
More importantly: check md5 hashes on all your downloads. You really want to avoid flashing a corrupted recovery download. Only continue flashing ROMs once you have a stable TWRP installation going. If it's not properly booting to TWRP, do not bother flashing anything else.
When successfully booted in TWRP, make sure MTP is enabled under mount and connect it to your PC. Browse for possible backups via your computer. If you can't find any, you've probably wiped internal memory. If you didn't make a copy to your computer, the data is most likely gone forever (sorry).
Panicking is indeed a bad idea, we've all been there and it's an excellent learning process (you'll appreciate your failures later, lol). It's better to work step by step slowly, make sure you read everything thoroughly. When in doubt, just post here and we'll follow up. We'll get there, don't worry.
---------- Post added at 08:51 AM ---------- Previous post was at 08:47 AM ----------
Oh and rename the recovery file to recovery.img and place it in your adb folder to avoid any complications. Less = more!
Click to expand...
Click to collapse
Hi mate,So I pulled an all nighter yesterday and was somehow magically able to boot in TWRP.I don't remember what I did but I booted into TWRP 2.8.7.0 and the first thing I did was check if any nandroid backup was there but I was disappointed to see my /data with free 55326 MB also no backups on my drive.All my data is gone and I can't curse myself enough for that,moving on so I did manage to gather my sense and flashed TWRP 3.2.1-K2 and flashed RR-O-v6.1.0 but the phone goes into boot loop again and again.
Since then my phone is displaying some weird behavior so if I unplug my device and start my phone the phone won't boot and wont go past oneplus one splashscreen so I thought my battery is gone but if I can go in fastboot mode or TWRP mode while being plugged in and unplug my device but my phone wont die,it'll be in the respective mode for ages.
I do have a clean setup (K:\oneplus\adb\) that's how I stayed away from this mess since ages but I guess I got too cocky.
I have religiously followed your thread and it has helped me a lot so once I am home I will check the TWRP part again and get back with the results.
Once again..thanks for your guidance.
vedanth123456 said:
Hi mate,So I pulled an all nighter yesterday and was somehow magically able to boot in TWRP.I don't remember what I did but I booted into TWRP 2.8.7.0 and the first thing I did was check if any nandroid backup was there but I was disappointed to see my /data with free 55326 MB also no backups on my drive.All my data is gone and I can't curse myself enough for that,moving on so I did manage to gather my sense and flashed TWRP 3.2.1-K2 and flashed RR-O-v6.1.0 but the phone goes into boot loop again and again.
Since then my phone is displaying some weird behavior so if I unplug my device and start my phone the phone won't boot and wont go past oneplus one splashscreen so I thought my battery is gone but if I can go in fastboot mode or TWRP mode while being plugged in and unplug my device but my phone wont die,it'll be in the respective mode for ages.
I do have a clean setup (K:\oneplus\adb\) that's how I stayed away from this mess since ages but I guess I got too cocky.
I have religiously followed your thread and it has helped me a lot so once I am home I will check the TWRP part again and get back with the results.
Once again..thanks for your guidance.
Click to expand...
Click to collapse
This is weird I just restarted my phone to see if it magically starts but it went into bootloop(displaying splashscreen not boot logo) in contrast to earlier when it died instantly when not plugged in also I can't boot into my recovery now!
Once I am plugged in and the phone is on bootloop and if I hold the volumedown+Powerkey it boots into TWRP properly..
This is just weird and I havent seen this behavious in the past three years of using my old lovely bacon
Try using the color os toolkit https://steemit.com/oneplus/@delusionalgenius/how-to-unbrick-oneplus-one-bacon and even though it says do not use if it is soft bricked use it this helped me
Sorry for getting back rather late (again). I'm in the middle of organizing an event and it's leaving very little XDA time. Anyway...
Isn't a hardbrick tutorial kinda agressive? I mean, I've used it before, and it's excellent, but then my device was actually hardbricked. I'd rather go for the 'back to stock' method first, setting the system back to CM13, which is a much better base for further flashing compared to ColorOS.
@vedanth123456 if you didn't take any action yet then I suggest following this thread (skip step 4!!).
The deal is to flash all images from fastboot. This will – naturally – wipe every single partition on your device!
I suggest doing the fastboot flashing manually (copy paste each command one by one) to avoid your device getting its bootloader locked. You DO NOT want to lock the bootloader on a OnePlus One if you ever wish to unlock it again.
When you successfully booted CM13, go though its initial setup, [disable recovery protection in system or developer settings] (it's been so long since I've experienced this process that I'm not sure if this option was present in CM13; if you can't find it, don't mind), get back to fastboot mode and flash K2 TWRP. First thing to do at this point: create a full nandroid backup of your working CM13 setup and copy it externally. ROM flashing should now be successful. If not, I'm afraid your hardware is failing. Do try several ROMs.
Don't forget to check those md5 hashes!
By the way, your /data is supposed to be empty after a factory reset. /data merely contains settings and app data (user added information). Backups and user media go to the /sdcard partition, which is known as internal memory. If I may suggest a ROM, go for CrDroid. It's more stable compared to RR, it's still actively developed and it has similar features.
Timmmmaaahh said:
Sorry for getting back rather late (again). I'm in the middle of organizing an event and it's leaving very little XDA time. Anyway...
Isn't a hardbrick tutorial kinda agressive? I mean, I've used it before, and it's excellent, but then my device was actually hardbricked. I'd rather go for the 'back to stock' method first, setting the system back to CM13, which is a much better base for further flashing compared to ColorOS.
@vedanth123456 if you didn't take any action yet then I suggest following this thread (skip step 4!!).
The deal is to flash all images from fastboot. This will – naturally – wipe every single partition on your device!
I suggest doing the fastboot flashing manually (copy paste each command one by one) to avoid your device getting its bootloader locked. You DO NOT want to lock the bootloader on a OnePlus One if you ever wish to unlock it again.
When you successfully booted CM13, go though its initial setup, [disable recovery protection in system or developer settings] (it's been so long since I've experienced this process that I'm not sure if this option was present in CM13; if you can't find it, don't mind), get back to fastboot mode and flash K2 TWRP. First thing to do at this point: create a full nandroid backup of your working CM13 setup and copy it externally. ROM flashing should now be successful. If not, I'm afraid your hardware is failing. Do try several ROMs.
Don't forget to check those md5 hashes!
By the way, your /data is supposed to be empty after a factory reset. /data merely contains settings and app data (user added information). Backups and user media go to the /sdcard partition, which is known as internal memory. If I may suggest a ROM, go for CrDroid. It's more stable compared to RR, it's still actively developed and it has similar features.
Click to expand...
Click to collapse
Hi mate
Apologies for not acknowledging your message and not replying back earlier. I've been traveling using a spare phone and things just aren't the same on it.
To give u an update, I tried the steps mentioned in the link (which I had tried previously as well) but the phone didn't boot. Same bootlooping and issue with the twrp.
So I went through other forums and links and finally found an exe that worked.!!!!!! So the exe seems to be an modified version of the one mentioned in the hard brick method and has been created by someone else (NOT ME!!)
My phone after many moons has booted and its on the good old cyanogen CM 11.0 XNPH44S. I've tried numerous roms on this bad boy but there is some beauty in the simplicity of the good old roms.
My phone battery is charging pretty slowly and wifi is not turning on so I'm still tensed but the fact that it booted is a small victory. I would want to upgrade to a stable rom once my phone is charged and not displaying erratic behavior so I'll wait for a day and see how it works but I'll want to upgrade to a slightly latest rom probably not a battery hogging one.
I believe I'll have to first install an old twrp followed by nandroid backup(save on every goddammed devices I own), then some CM snapshot and finally the rom but please can you confirm and suggest.
vedanth123456 said:
Hi mate
Apologies for not acknowledging your message and not replying back earlier. I've been traveling using a spare phone and things just aren't the same on it.
To give u an update, I tried the steps mentioned in the link (which I had tried previously as well) but the phone didn't boot. Same bootlooping and issue with the twrp.
So I went through other forums and links and finally found an exe that worked.!!!!!! So the exe seems to be an modified version of the one mentioned in the hard brick method and has been created by someone else (NOT ME!!)
My phone after many moons has booted and its on the good old cyanogen CM 11.0 XNPH44S. I've tried numerous roms on this bad boy but there is some beauty in the simplicity of the good old roms.
My phone battery is charging pretty slowly and wifi is not turning on so I'm still tensed but the fact that it booted is a small victory. I would want to upgrade to a stable rom once my phone is charged and not displaying erratic behavior so I'll wait for a day and see how it works but I'll want to upgrade to a slightly latest rom probably not a battery hogging one.
I believe I'll have to first install an old twrp followed by nandroid backup(save on every goddammed devices I own), then some CM snapshot and finally the rom but please can you confirm and suggest.
Click to expand...
Click to collapse
Heya!
Well, this is legacy material so I kinda forgot what TWRP worked best for the older ROMs (2.8?). The latest TWRP should be backwards compatible and support CM11 so you can give that a whirl first. You're just making a backup (no write actions) and TWRP's are easily replaced with other version so there ain't much to lose. Anyway, glad you got it running! I'd still go with the CM13 flash before moving to one of the modern ones. If you encounter more bootloops, that same exe should recover it for ya. By the way, can you PM me a link to that exe? Who knows, it might come in handy one day.
As a stable up-to-date ROM I can really suggest crDroid. I've been using it myself for a few weeks now. @chineel is a talented and devoted dev.
Timmmmaaahh said:
Heya!
Well, this is legacy material so I kinda forgot what TWRP worked best for the older ROMs (2.8?). The latest TWRP should be backwards compatible and support CM11 so you can give that a whirl first. You're just making a backup (no write actions) and TWRP's are easily replaced with other version so there ain't much to lose. Anyway, glad you got it running! I'd still go with the CM13 flash before moving to one of the modern ones. If you encounter more bootloops, that same exe should recover it for ya. By the way, can you PM me a link to that exe? Who knows, it might come in handy one day.
As a stable up-to-date ROM I can really suggest crDroid. I've been using it myself for a few weeks now. @chineel is a talented and devoted dev.
Click to expand...
Click to collapse
Try bacon root toolkit you can perform most of the things very easily.
chineel said:
Try bacon root toolkit you can perform most of the things very easily.
Click to expand...
Click to collapse
Hey man, thanks for pinching in. I'm personally not a fan of these toolkits as one can accidentally lock the bootloader and I prefer manual style because it's educational and you see more of what's going on. It's like I preferred DOS over Windows 3.11 back in the day. That's pretty much the same, right?... ?
Timmmmaaahh said:
Heya!
Well, this is legacy material so I kinda forgot what TWRP worked best for the older ROMs (2.8?). The latest TWRP should be backwards compatible and support CM11 so you can give that a whirl first. You're just making a backup (no write actions) and TWRP's are easily replaced with other version so there ain't much to lose. Anyway, glad you got it running! I'd still go with the CM13 flash before moving to one of the modern ones. If you encounter more bootloops, that same exe should recover it for ya. By the way, can you PM me a link to that exe? Who knows, it might come in handy one day.
As a stable up-to-date ROM I can really suggest crDroid. I've been using it myself for a few weeks now. @chineel is a talented and devoted dev.
Click to expand...
Click to collapse
Hi Mate,
My perils seem not to end.So after the last update I tried to start my phone and it started but as soon as I removed the power cord the phone switched off.
I realized that the issue was with the battery so I got it replaced in one of the OnePlus Authorized service center.
The new battery with only one month warranty started just fine and I could see the phone hold power without the charger attached.So I reached home and did the below
1)Flash Twrp
2)Flash CM 13 snapshot
3)Flash cdroid and gapps
4)Reboot phone
Everything seems to work as expected other than the goddamn network and the wifi.My phone has no IMEI and ofcourse I have no EFS backup stored cause of my previous fiasco.
Any ideas mate,I see forums where itts told to install color os and then cm11 and then something but I dont want to risk anything anymore .
Any advice ?
vedanth123456 said:
Hi Mate,
My perils seem not to end.So after the last update I tried to start my phone and it started but as soon as I removed the power cord the phone switched off.
I realized that the issue was with the battery so I got it replaced in one of the OnePlus Authorized service center.
The new battery with only one month warranty started just fine and I could see the phone hold power without the charger attached.So I reached home and did the below
1)Flash Twrp
2)Flash CM 13 snapshot
3)Flash cdroid and gapps
4)Reboot phone
Everything seems to work as expected other than the goddamn network and the wifi.My phone has no IMEI and ofcourse I have no EFS backup stored cause of my previous fiasco.
Any ideas mate,I see forums where itts told to install color os and then cm11 and then something but I dont want to risk anything anymore .
Any advice ?
Click to expand...
Click to collapse
you are going to have to use the colour os toolkit to get the imei info back there is nothing else you can do
---------- Post added at 05:34 PM ---------- Previous post was at 05:20 PM ----------
vedanth123456 said:
Hi Mate,
My perils seem not to end.So after the last update I tried to start my phone and it started but as soon as I removed the power cord the phone switched off.
I realized that the issue was with the battery so I got it replaced in one of the OnePlus Authorized service center.
The new battery with only one month warranty started just fine and I could see the phone hold power without the charger attached.So I reached home and did the below
1)Flash Twrp
2)Flash CM 13 snapshot
3)Flash cdroid and gapps
4)Reboot phone
Everything seems to work as expected other than the goddamn network and the wifi.My phone has no IMEI and ofcourse I have no EFS backup stored cause of my previous fiasco.
Any ideas mate,I see forums where itts told to install color os and then cm11 and then something but I dont want to risk anything anymore .
Any advice ?
Click to expand...
Click to collapse
you are going to have to use the colour os toolkit to get the imei info back there is nothing else you can do
kallum7 said:
you are going to have to use the colour os toolkit to get the imei info back there is nothing else you can do
---------- Post added at 05:34 PM ---------- Previous post was at 05:20 PM ----------
you are going to have to use the colour os toolkit to get the imei info back there is nothing else you can do
Click to expand...
Click to collapse
Mate ,can you please help me with the link ?
I know I can google it but I just dont want to take chances anymore
vedanth123456 said:
Hi Mate,
My perils seem not to end.So after the last update I tried to start my phone and it started but as soon as I removed the power cord the phone switched off.
I realized that the issue was with the battery so I got it replaced in one of the OnePlus Authorized service center.
The new battery with only one month warranty started just fine and I could see the phone hold power without the charger attached.So I reached home and did the below
1)Flash Twrp
2)Flash CM 13 snapshot
3)Flash cdroid and gapps
4)Reboot phone
Everything seems to work as expected other than the goddamn network and the wifi.My phone has no IMEI and ofcourse I have no EFS backup stored cause of my previous fiasco.
Any ideas mate,I see forums where itts told to install color os and then cm11 and then something but I dont want to risk anything anymore .
Any advice ?
Click to expand...
Click to collapse
I'd hate to say I told you so ?
Don't worry too much. The cool thing about flashing with Android is that there's always other ways to get to a working system. Plus, having a fizzled up system is how you'll learn the most about how this all works. You'll be a pro in no time. I personally got seriously into troubleshooting with a hard bricked OPO that had a wasted flash chip. Believe me when I say that's a whole other world of pain.
One question: did you wipe system/data/caches between the CM13 and the crDroid flash? That's kind of important. It would also be useful to mention the versions of everything.
I have no first person experience with broken EFS partitions but according to what I've read you'll indeed have to get ColorOS running. You could try wiping everything again and flash CM13 to see if that boots fine (with working connectivity) but I'm afraid you'll have to go through the whole works: wipe all, flash or fastboot flash ColorOS, get it running (verify IMEI), flash TWRP and backup EFS (MAKE AN EXTERNAL COPY), wipe all again, flash CM13, get it running, wipe all again, flash crDroid + Gapps, wipe caches and boot to a (hopefully) working system. If EFS broke again you can simply restore the backup made earlier instead of starting over.
Mind that when I say wipe all, it doesn't have to include internal memory or you'll be wiping backups you might need later on.
Alright, here goes your 27th attempt. Good luck! ?
mate here is the link https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 even though it says do not use on soft brick devices in your case you are going to have to
With every update until this one, I was able to keep root (download update, local upgrade via settings, install update, install magisk to inactive slot, reboot and done) but it did not work with this latest one. I tried mauro's toolkit but it didn't work either. What are my options to get root now? Thanks in advance!
https://forum.xda-developers.com/oneplus-8/how-to/guide-magisk-oxygenos-11-beta-1-global-t4160833
Flash the patched img!
I'm a ****ing genius. Managed to bootloop/temp brick my phone. MSM tool saved my ass but it took a usb 2.0 slot and lots of tries to get into edl mode. I am getting tired of fighting for root and it's such a jarring and unpleasant experience to suddenly lose root.
t-mizzle said:
I'm a ****ing genius. Managed to bootloop/temp brick my phone. MSM tool saved my ass but it took a usb 2.0 slot and lots of tries to get into edl mode. I am getting tired of fighting for root and it's such a jarring and unpleasant experience to suddenly lose root.
Click to expand...
Click to collapse
I feel you mate, when my phone arrived I immediately managed to brick it, but it's just part of the game. To be honest I found the unbricking and rooting pretty easy on OP8, I'm quite sure when the next OTA arrives you just have to follow the same method (installing magisk to inactive slot then reboot) just like in OOS10.
Recovered, tried again, same outcome. Patched image installed correctly according to the command prompt but actually resulted in a boot loop. Will hold off from Android 11 for now.
Are you flashing the right img? What's your ROM build version? I bet you flash a wrong img for your ROM. In the above mentioned thread there are only imgs for EU, global and Indian ROMs, if you using some kind of US specific ROM then tell me and I can make you a patched img.
https://oneplus.gadgethacks.com/how...factory-images-for-any-oneplus-phone-0249751/
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
==> DOWNLOAD LATEST SDK PLATFORM TOOLS HERE: https://developer.android.com/studio/releases/platform-tools
==> Official Factory Image / OTA - Downloads / Flashing Guide Here (recommend reading): https://developers.google.com/android/images
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: twitter dot com /topjohnwu/status/1272136975022084097?s=19 (until I figure out how to stop new XDA from forcing the URL to embed a giant twitter posting in the middle of the post...)
ALL FILES BELOW ARE FOR "RQ3A.210605.005, Jun 2021"!
Magisk v23.0 Patched Boot Image: https://www.androidfilehost.com/?fid=14943124697586345554
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=14943124697586345555
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=14943124697586345553
----------------------------------------------
-------------UPDATE PROCESS BELOW-------------
----------------------------------------------
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RQ2A.210505.002, May 2021". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rq2a.210505.002-factory-dtbo.img: https://www.androidfilehost.com/?fid=2188818919693794180
coral-rq2a.210505.002-factory-boot.img: https://www.androidfilehost.com/?fid=2188818919693794183
June 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq3a.210605.005-4e7b2427.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
*. make sure installed Magisk (Manager) app version is equal to or greater than the Magisk pre-patched version boot image provided
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-rq2a.210505.002-factory-boot.img
3. fastboot flash dtbo coral-rq2a.210505.002-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rq3a.210605.005-4e7b2427.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rq2a.210605.005-magisk_patched-23000.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdX/LSposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
-------------------------------------------------
-------------------TROUBLESHOOTING-------------------
-------------------------------------------------
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
Since Magisk v21.x, Core Only mode has been replaced by using Android's built-in Safe Mode. Booting into Safe Mode should essentially boot you back into your system but with all modules disabled (as well as Magisk Hide). Keep in mind that even after you reboot, modules will remain disabled, unless you re-enable them first. Also remember to re-enable Magisk Hide if you had it enabled before.
Please see @Didgeridoohan's guide for more details: https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Core_Only_Mode
It's also worth mentioning, his guide is extremely well-made and contains a lot of useful information that could benefit all Magisk users and modders. I highly recommend looking through it anyway!
Quick note - apologies for going radio silent towards the middle / end of last month. Things are really starting to get busy in life, and all of the "big ticket" life changes are all converging on us at once! Went on a ~1500mi road trip to visit family for the first time in a long time... with a toddler :O
Also just bought our first house... closing is happening soon... starting new jobs... I have knee surgery coming up in a few weeks during all this and moving and stuff... and all while raising a toddler who is going to be 2 years old at the end of the year!
Anyway, I added the notes and a link regarding latest platform SDK tools. Thanks to everyone who recommended that before. Hopefully it helps prevent or leads people to solve silly issues due to using outdated SDK tools.
Besides that, like I said things are getting extremely busy and I'm finding it a bit tougher to keep up with XDA stuff. Fortunately, according to the downloads counters on AFH, it seems like plenty of people are still finding these guides useful, so I'm glad I could help in that respect.
If you are helped by these guides, I would appreciate if you could express your thanks by hitting the thanks button. Apologies if I'm not around as much for the next several weeks, but I hope you all have a great summer! =)
@i5lee8bit, I appreciate your posts dude!
You're a Gravity Box user, right? Any problem with June update or all smooth? I know Google did a feature drop this month.
Ghisy said:
@i5lee8bit, I appreciate your posts dude!
You're a Gravity Box user, right? Any problem with June update or all smooth? I know Google did a feature drop this month.
Click to expand...
Click to collapse
No problems noted yet, at least for the particular mods I happen to use in the GB arsenal. =)
Pretty much all the mods I use are for functionality and almost never for cosmetics. A few randomly off the top of my head being remapping navbar keys, adding left / right cursor keys to navbar, volume key cursor controls, statusbar quicksettings lockdown, advanced reboot menu. These all seem to work without issue so far. I also flashed Kirisakura 7.4.3 and it seems to be working well so far too.
I say go ahead and OTA. Working nicely here. =)
Also in case you didn't know, C released an update to GB (v 11.0.3) just a few days ago, so make sure you grab that too if you haven't already.
i5lee8bit said:
Quick note - apologies for going radio silent towards the middle / end of last month. Things are really starting to get busy in life, and all of the "big ticket" life changes are all converging on us at once! Went on a ~1500mi road trip to visit family for the first time in a long time... with a toddler :O
Also just bought our first house... closing is happening soon... starting new jobs... I have knee surgery coming up in a few weeks during all this and moving and stuff... and all while raising a toddler who is going to be 2 years old at the end of the year!
Anyway, I added the notes and a link regarding latest platform SDK tools. Thanks to everyone who recommended that before. Hopefully it helps prevent or leads people to solve silly issues due to using outdated SDK tools.
Besides that, like I said things are getting extremely busy and I'm finding it a bit tougher to keep up with XDA stuff. Fortunately, according to the downloads counters on AFH, it seems like plenty of people are still finding these guides useful, so I'm glad I could help in that respect.
If you are helped by these guides, I would appreciate if you could express your thanks by hitting the thanks button. Apologies if I'm not around as much for the next several weeks, but I hope you all have a great summer! =)
Click to expand...
Click to collapse
Always thanks to you bro. These guides have been a godsend, and have made stuff so much easier. Now, I can breeze through the whole process in less than 10 mins. Much appreciated.
There is a small mistake in the guide.
The uploaded magisk file is called
fastboot flash boot coral-rq3a.210605.005-magisk_patched-23000.img
The guide however wants a
fastboot flash boot coral-rq2a.210605.005-magisk_patched-23000.img
Ergo copying the guide won't work. The file name must either be changed or the text from the guide must be changed.
I changed the file name and it worked without an issue. Thanks again for your awesome guide. Updating a rooted phone has never been that easy.
I did the June update and can no longer get back to root(blackout after boot animation)...
I tried safe mode, removing modules with adb, uninstalling Magisk via TWRP, but the situation remained the same...
Is this because of my environment?
By the way, it boots normally with stock boot.img.
Hey all.
Been running with the June updates for a week or so now. So far, so good.
GPay has even been working... until today, that is.
No longer passing Safetynet (neither basic, nor ctsProfile).
Anyone else passing Safetynet?
EDIT: Got things working again by switching from EdXposed to LSposed
Cememer said:
I did the June update and can no longer get back to root(blackout after boot animation)...
I tried safe mode, removing modules with adb, uninstalling Magisk via TWRP, but the situation remained the same...
Is this because of my environment?
By the way, it boots normally with stock boot.img.
Click to expand...
Click to collapse
Resolved. Probably because I did not uninstall magisk properly before updating.
I temporarily turned off the passcode, which gave me a grace period and could uninstall magisk from the app.