I had my Moto G rooted for a few days, borked an attempt to flash to a new rom (Carbon), had to re-flash back to stock. From this point I am no longer able to root my phone. I have tried to flash SuperSU.zip to no avail (worked originally). What happens is after an apparently successful flash of SuperSU and reboot, I get stuck in the unlocked bootloader screen. I've tried SuperSU 2.46, 2.62, 2.79 and all lead to getting stuck in the unlocked bootloader screen. I've had to reflash my stock system each time.
Why would I be able to root once but never again? The first time I did select (in TWRP) to make system files RW instead of read-only, which is what I did originally when it worked. Do I suddenly need to set the system directories as read-only now?
Related
I received an OTA update, however, it is continually failing upon reboot. I discovered that I can't get my RAZR M into recovery.
I would flash TWRP recovery, however, I then would no longer receive OTA updates.
Is it possible that I may have 'locked' myself out of recovery?
My M is rooted; I've been able to get to recovery previously, though do I need to perm unroot my M?
Is it possible to re-flash stock recovery? If so, how?
My phone:
Moto Droid RAZR M
Stock ROM, rooted
Stock recovery
BusyBox 1.21.1
SuperSu
Voodoo OTA Rootkeeper
Having the same issue myself. I have an unlocked bootloader, and My phone is otherwise completely stock 4.1.2. I have 1 ota but when I try to isntall it it fails halfway through the install process in recovery. Now when I try to boot my phone into recovery all i get is an android with a red triangle. On top of that I can't get most fastboot commands to work, such as flashing a new boot image to replace the unlocked boot loader warning. Not really sure what to do any more. Any help would be greatly appreciated. Thanks!
I rooted my motoe lollipop (1st gen),it worked.
Today i got an official update from android and i downloaded it,
but when i installed it i gone to twrp. I rebooted it but it keeps on rebooting every minute
after entering system and goes back to twrp. Plsss help ... i'm stuck:crying:
Goto /cache directory from TWRP file manager, and delete tge content on it, first mount the system on twrp
Tarun1808 said:
I rooted my motoe lollipop (1st gen),it worked.
Today i got an official update from android and i downloaded it,
but when i installed it i gone to twrp. I rebooted it but it keeps on rebooting every minute
after entering system and goes back to twrp. Plsss help ... i'm stuck:crying:
Click to expand...
Click to collapse
OTA can not be installed when the TWRP or ROOT are installed.
They interfere with the installation by modifying the original system, especially TWRP because the OTA is not to flash. Care! Try to install the OTA with installed ROOT and TWRP can brick your Moto E.
Return to Stock 4.4.4. It does not have ROOT or TWRP. This enables the OTA installation usually via stock recovery with no problem.
[[[Sorry for my "bad English". I am a Brazilian and I'm using Google translator (which is horrible). Do not worry, I'm a power user, have tested over 15 custom roms and I've done a lot on my Moto E.]]]
Hello, so I wanted to root my phone. I went throught the process of unlocking my bootloader, after that the phone still booted up to the system.
Then I installed twrp, and at that point, the phone still booted up to the system. I believe my **** up happens on the next part, which is me putting supersu zip in the external sd of the phone, and then installing it through twrp, and now the phone wont go further than the Honor screen I can get to twrp and fastboot, I'm gonna try to install the stock recovery and stuff through abd now...
https://forum.xda-developers.com/honor-7/help/stuck-honor-logo-t3451993
Follow steps given in this thread, it will work.
Next time back up your phone using TWRP.
Also you are probably stuck in bootloop as you installed version of supersu that is not compatible. Use superSU 2.62 and it should work.
Hello, wanting to root my new zenfone I messed up a bit in the bytes.
The situation I'm in now is that system and boot is kinda messed up, the only way to boot into system or recovery is trough fastboot.
The phone is rooted but no wifi and not proper booting (meaning when I boot normally or ">adb reboot recovery",
I'd be stuck in unlocked bootloader message screen and getting fastboot text on top of it after 5 seconds (yea), as opposed to properly boot into whatever I told it to those 5 seconds passed.
but as I said, I can go to fastboot mode and boot from there into recovery or system (fastboot reboot).
Now the thing is, through TWRP when I try to install stock rom, it will fail saying "Failed to mount '/system' (Structure need cleaning).
I'm out of ideas.
What I wan't to do is go back to stock rom(or custom if there is one) basically get the phone to normal working state and retry to get root access properly after understanding it better... this time.
Edit/Solution : Got everything back to stock + root
What I did is that I extracted a stock system.img with UR-Tool Prime v1, from WW-14.1060.1708.70 stock ROM that I got from asus support page. (after flashing system, wifi worked again)
I also took the boot.img that comes along with the zip.
And finally, got stock recovery back by applying "Full Unroot" option from within SuperSu app.
So once you have extracted your system.img from system.new.dat, do the following:
1 - flash boot.img
2 - flash system.img
3 - if you need to, do full unroot option in SuperSu settings
Don't forget to back everything up.
I used Magisk v16 to get root access.
It's a tale as old as time. I have a functioning A3 with TWRP and magisk installed. OTA Jan security update failed. "Installation problem" was all it said. I expected this. I think all my magisk mods are systemless but I did flash a custom kernel in TWRP to get kcal.
Ok I'd gone through this for the December update. I downloaded fastboot ROM and extracted the boot.img. I made sure it was correct. Laurel sprout V10.3.13.0.PFQEUXM. But flashing it with either TWRP or fastboot I got the dreaded error screen on reboot where your options are try again or factory reset. Yes I flashed into the active slot. Even when I chose to factory reset and started fresh, I still got the same error when I tried to update.
I also tried to flash boot+system but also got same corrupted error. I tried using flash_all_except_data_storage but got an antirollback error. I've gone back to a nandroid backup for now but obviously I need to get this sorted out before the Android 10 update.
Any ideas? Thanks
Mi A3 doesn't have anti rollback mechanism as far as I know. If you installed TWRP, you also most probably enabled "allow system modifications" (there is a one time prompt on the first start of TWRP, pretty much everyone just dismisses it without reading). TWRP remembers this setting and for each subsequent boot into TWRP it automatically mounts system as R/W, breaking OTA even if you don't flash anything.
You need to reflash stock fastboot images for boot and system with the same version as you're currently running. If you are getting data corruption error, it usually happens when you flash system image from incorrect region or versions differ too much (you're flashing too old image).
Don't install TWRP (or make sure that you delete its settings first and then do NOT allow system modifications).
As you already performed a factory reset, I'd start from fresh state again - switch to active slot A and reflash whole ROM from fastboot, including data wipe (flash_all.bat if I'm not mistaken, but I don't have it in front of me, so double-check its content that it doesn't lock your bootloader).