tl;dr: Updated to 7.1.1 OTA then installed twrp 3.1.1-0 had it apply what I assume is the F2FS kernel fix, now phone won't boot into system
Yesterday I was trying to update my rooted phone from MM to the latest software. I did this by reverting everything back to stock using this guide and that worked without a problem. Once it was back to stock I upgraded all the way up to the most recent OTA from Motorola (7.0.1 I believe), and then I upgraded up to the most recent 7.1.1 OTA manually using this guide. After all the updating I then flashed twrp 3.1.1-0 and booted into it. This is where things went wrong, after booting into twrp for the first time I asked me if I'd like to like to apply what I'm assuming is a kernel with the F2FS fix, I didn't think much about it and accepted it. In retrospect this was a very bad idea seeing as the F2FS fix for 7.1.1 hasn't been released yet. Now whenever I try to boot into the system the bootloader warning screen shows "ID: bad key" and won't boot. I can still get into the bootloader for fastboot and the twrp recovery but I don't know what to do from here in order to fix it. If anyone could help me fix this I'd really appreciate it!
f2fs fix is Kernel. You need an original boot.img of your currently installed firmware version and flash that to uninstall f2fs. Then it should work.
My advice in general:
Before doing any updates: do a full Nandroid backup.
Before modifying boot partition (f2fs fix, install Magisk or SuperSU or phh superuser) do a backup of at least boot.img. it may be a good idea to do a system backup (system boot recovery logo oem). Will help for OTA updates.
Before modifying recovery, back it up.
Before doing any modifications, save your data (data partition, but careful: /data/media is excluded here! You need that additional).
I hope I'll learn to keep all this in mind too without getting out of patience
I just spent the last day going through your exact issues. Pm me if you need instructions and files. I can look up exactly what firmwares and fastboot commands I used to get back to normal.
Related
I have a One M8 DevEd which I have just upgraded to Marshmallow (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4). After the ugrade I flashed TWRP 2.8.7.0. I rebooted into TWRP. It asked me if I wanted to leave the System R/O and I said NO.
I then Installed Beta-SuperSU2.65 by flashing the Zip from TWRP Install. It flashed fine. It asked me if I wanted to install SU to rootbefore rebooting and I said NO as I had read that it can get the phone stuck in boot loop.
However, when I did reboot, it got stuck in boot mode...
I reflashed the RUU and tried again, this time I said yes to the question in TWRP to install SU to root the phone at reboot, and I got stuck as well.
Am I missing a step? Any suggestion? Thanks!
TheEarman said:
I have a One M8 DevEd which I have just upgraded to Marshmallow (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4). After the ugrade I flashed TWRP 2.8.7.0. I rebooted into TWRP. It asked me if I wanted to leave the System R/O and I said NO.
I then Installed Beta-SuperSU2.65 by flashing the Zip from TWRP Install. It flashed fine. It asked me if I wanted to install SU to rootbefore rebooting and I said NO as I had read that it can get the phone stuck in boot loop.
However, when I did reboot, it got stuck in boot mode...
I reflashed the RUU and tried again, this time I said yes to the question in TWRP to install SU to root the phone at reboot, and I got stuck as well.
Am I missing a step? Any suggestion? Thanks!
Click to expand...
Click to collapse
Rooting in MM includes flashing modified boot.img (modified kernel). I guess that's what you are missing. There is the modified boot.img for root in MM dev edition thread or I can recommend you the flar2 elementalX 6.0.2 kernel that I am using right now and is far better on battery life/performance vs the stock one. Cheers!
Thanks. I had read something about a modified boot.img but thought it was only for the GPE version. I'll give it a try. Thanks for the help!
TheEarman said:
Thanks. I had read something about a modified boot.img but thought it was only for the GPE version. I'll give it a try. Thanks for the help!
Click to expand...
Click to collapse
let us know what the outcome is. Been looking for a thread on rooting unlocked/dev edition and was unable to find any
TheEarman said:
I have a One M8 DevEd which I have just upgraded to Marshmallow (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4). After the ugrade I flashed TWRP 2.8.7.0. I rebooted into TWRP. It asked me if I wanted to leave the System R/O and I said NO.
I then Installed Beta-SuperSU2.65 by flashing the Zip from TWRP Install. It flashed fine. It asked me if I wanted to install SU to rootbefore rebooting and I said NO as I had read that it can get the phone stuck in boot loop.
However, when I did reboot, it got stuck in boot mode...
I reflashed the RUU and tried again, this time I said yes to the question in TWRP to install SU to root the phone at reboot, and I got stuck as well.
Am I missing a step? Any suggestion? Thanks!
Click to expand...
Click to collapse
I was able to root properly, with proper binaries, by using the method described here (I was missing the boot.img flashing step, as indicated by High_voltage): http://forum.xda-developers.com/htc-one-m8/development/kernel-unlocked-developer-edition-t3262823. Problem solved. Thanks!
This isn't a bad question, as the newer 2.6x SU betas can alter the boot image of some devices during the ZIP install. I was actually about to ask whether or not that included the M8's boot image, but it would appear the answer is no.
jshamlet said:
This isn't a bad question, as the newer 2.6x SU betas can alter the boot image of some devices during the ZIP install. I was actually about to ask whether or not that included the M8's boot image, but it would appear the answer is no.
Click to expand...
Click to collapse
I was running 2.64 and now I'm running SuperSU 2.65 and about to test 2.66 later on stock boot.img for MM (I'm on stock MM 6.12.709.4 ROM)
There is no need for a patched boot.img
SuperSU will detect boot.img
If it is stock boot.img, it will install root in systemless mode
If it is a patched boot.img, it will install root in system mode
The point is I have no problem to root a stock MM ROM with 2.64 and later versions
ckpv5 said:
I was running 2.64 and now I'm running SuperSU 2.65 and about to test 2.66 later on stock boot.img for MM (I'm on stock MM 6.12.709.4 ROM)
There is no need for a patched boot.img
SuperSU will detect boot.img
If it is stock boot.img, it will install root in systemless mode
If it is a patched boot.img, it will install root in system mode
The point is I have no problem to root a stock MM ROM with 2.64 and later versions
Click to expand...
Click to collapse
The posts i've read point to the possibility of getting stuck in a bootloop or worst case bricking the device if its attempted without a modified boot. While those were for the gpe version i shouldn't think it matters.
Your suggesting its possible without modifying the boot.img? If so are there any repercussions vs using a patched boot.img?
ShinAkira00 said:
The posts i've read point to the possibility of getting stuck in a bootloop or worst case bricking the device if its attempted without a modified boot.
Click to expand...
Click to collapse
You should always do a TWRP backup before making major system changes, including root. Doing a TWRP backup mean you can simply revert to your backup if you run into such issues.
A bootloop or no boot (into OS) are always possibilities when modding the phone. I doubt a real brick is possible just by attenting root. If you read this somewhere, my guess is the person just meant a bootloop or no boot, not a true brick (which by definition is not recovery except by opening the phone).
redpoint73 said:
You should always do a TWRP backup before making major system changes, including root. Doing a TWRP backup mean you can simply revert to your backup if you run into such issues.
A bootloop or no boot (into OS) are always possibilities when modding the phone. I doubt a real brick is possible just by attenting root. If you read this somewhere, my guess is the person just meant a bootloop or no boot, not a true brick (which by definition is not recovery except by opening the phone).
Click to expand...
Click to collapse
cool, thanks for clarifying.
Hi,
I've just bought a Nexus 5X and wanted to root it with systemless method for being able to get OTA in futur.
I've booted to TWRP to flash SuperSU zip but I've made the mistake to use the slider when TWRP ask if I want to keep the system as read only.
Is there an easy way to revert back without the reflashing the rom ?
And is there a way to boot to TWRP from android (if i keep the. .img on my phone) ?
Thank you
Sebacestmoi said:
Hi,
I've just bought a Nexus 5X and wanted to root it with systemless method for being able to get OTA in futur.
I've booted to TWRP to flash SuperSU zip but I've made the mistake to use the slider when TWRP ask if I want to keep the system as read only.
Is there an easy way to revert back without the reflashing the rom ?
And is there a way to boot to TWRP from android (if i keep the. .img on my phone) ?
Thank you
Click to expand...
Click to collapse
If you had TWRP touch your /system in R/W mode even if it made no changes, the system partition is tainted (there is meta-data that changed)
The only practical way to get back to untainted /system is to flash the stock system.img. The flashing is simple, but it might take a little time to download the factory image and extract the system.img.
I usually keep twrp in the recovery partition, probably chainfire has something to boot twrp directly. I do know that if you boot twrp over usb there is a problem where it doesn't accept your pin/pattern/pass to decrypt the user partition. I don't know if it suffers the same problem through other booting methods.
BTW even with systemless root, you cannot flash the differential OTA you receive over the air directly. You need to restore the stock boot.img before flashing the OTA.
The FULL OTA you get from the factory image website, on the other hand, can flash over anything, regardless of whether you have boot, system, or vendor modified.
Thank you for the clear answer
Sebacestmoi said:
Hi,
I've just bought a Nexus 5X and wanted to root it with systemless method for being able to get OTA in futur.
I've booted to TWRP to flash SuperSU zip but I've made the mistake to use the slider when TWRP ask if I want to keep the system as read only.
Is there an easy way to revert back without the reflashing the rom ?
And is there a way to boot to TWRP from android (if i keep the. .img on my phone) ?
Thank you
Click to expand...
Click to collapse
The command
Code:
[I]fastboot boot <img file name>[/I]
will boot twrp from your computer with out having to install it.
Im running stock ROM 7.1.1 with Latest ElementalX Kernel and latest Magisk + MagiskSU. Also Running latest TWRP 3.1
I haven't updated yet. so I have the march patch, and this recent patch im behind on my 5x. I thought maybe i could just accept the OTA and just reflash magisk and the elementalX kernel afterwards. Oh, and likely would have to do TWRP as well. But accepting the update clicking to restart and install just rebooted me into TWRP. Flashfire doesn't work yet either been waiting a month on that. I get that failure during "uncrypting" error.
I'm slightly new back on the modding scene, until recently have been out of it for years. I did recently make a mistake with an audio mode and had to download the full image and use fastboot to throw that back on my device. Anyway with 7.1.2 out i really do want to update so i need to do it manually, and hopefully without losing my data. (or having to restore it from a backup if possible anyway)
I'd read somewhere that you can download the full images and extract the updated images you need and flash them to your device then your respective addons root kernel ect.. There seems to be lots of way to go about it, but little clear on how to do this so that's what brings me here to this post. What's the best way to manually update (add security patches) if im running Magisk and magiskSU.
Thanks in Advance.
https://elementalx.org/how-to-install-android-monthly-security-updates/
After you flash the /system /boot /vendor (I would also do bootloader and radio), reboot into TWRP and install kernel & Magisk.
So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!
If you don't want to wipe just update through factory image, just open the factory zip, open flash-all file and remove "-w" from last line, then execute it (update without wipe)
But I suggest to flash the stock factory image with the "-w" to make a clean install, flashing major release like 7.x -> 8.x is always better wipe to avoid potential issues.
But yes, you can first give a try without wipe and only if you find bugs try wiping. Your choice.
simply flash the OTA, then re-root
xraystyle said:
So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!
Click to expand...
Click to collapse
Use full unroot in supersu. Then take ota. Then root again after upgrading to O
Thanks for the help everyone, you pointed be in the right direction.
In the event that it might help someone else, here's what I ended up doing:
1. I downloaded the OTA, booted into the TWRP I had currently installed, and then sideloaded the OTA.
2. I used ADB to push the newest TWRP flashable zip, the latest SuperSU, and the latest SU-Hide to /sdcard on the device.
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
4. Finally, I rebooted to recovery on the phone (latest TWRP now instead of stock), and flashed SuperSU and SU-Hide.
I'm now stock, rooted, on O. No wipe necessary, kept all my apps and data. So far the OS itself has been entirely stable. I had an issue or two with a few apps after the upgrade, but those were fixed with a quick re-install. Except for Better Terminal Emulator Pro, seems it doesn't want to work on Oreo and it's no longer under active development. It's fine though, there's other terminal emulators out there.
Thanks again for the help!
xraystyle said:
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
Click to expand...
Click to collapse
Which version of TWRP do you have TWRP working with Oreo 8.0?
I can boot into the modded TWRP 3.1 (fastboot boot twrp-3-1-pixel-bootable-mod.img) but AFAIK there is no working flashable recovery for 8.0 yet.
quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.
gordonlw said:
quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.
Click to expand...
Click to collapse
That's how I did it. I don't use suhide.
Does the -w in the .bat file format or wipe the data? I want a clean clean , o-fresh in the morning feeling kind of wipe
toknitup420 said:
That's how I did it. I don't use suhide.
Click to expand...
Click to collapse
Thanks! What I ended up doing:
Decided to try and unroot and take the ota. super-su full unroot would not work. so I fastbooted to the mod twrp and flashed UPDATE-unSU. I then took the ota. then fastbooted to mod twrp and flashed super-su. worked perfect!
I hope that someone here can help me rescue to rescue my data.
I was on the AOSiP build from september and than decided to encrypt my device. That worked perfectly. Now I wanted to install the latest update. The internal updater didn't work (just booted into TWRP recovery without further action, so I moved the update file to microsd and than updated manually by flashing the zip file via TWRP). Prior to the whole action, I updated TWRP through the app to the latest version.
Now my phone doesn't boot anymore, it is stuck in the AOSiP boot animation. Reverting to a previous TWRP version (3.2.3.2) didn't help, also flashing the september build again didn't help.
In TWRP I was unable to decrypt data, because TWRP keeps asking me for a password (but I don't remember putting a password in the first place). Therefor I switched from TWRP to OrangeFox recovery. Here decryption worked, put still after flashing the phone doesn't boot.
Anyone that has further ideas how to fix this without loosing all my data? Any help appreciated!
Have you tried installing another kernel?
kotobodj said:
Have you tried installing another kernel?
Click to expand...
Click to collapse
No, but as my system was running before without problems I don't expect the kernel to be the problem .. Or why would that make sense?
SOLVED: I noticed that flashing the update manually didn't automatically flash Gapps right afterwards. So flashing the Gapps helped and the phone now boots normally!