So I'm in an interesting situation that I'll try and describe and hopefully get some help. I just switched my N7 over to f2fs with slimkat. Then supersu wouldn't update binaries. I enabled development options and granted root to adb and apps. Restarted to update binaries through TWRP. After the update I'm stuck in a Google boot loop. What can I do. I can't get back into TWRP but I can get to the bootloader. Any help would be great!
waywardsojourner said:
So I'm in an interesting situation that I'll try and describe and hopefully get some help. I just switched my N7 over to f2fs with slimkat. Then supersu wouldn't update binaries. I enabled development options and granted root to adb and apps. Restarted to update binaries through TWRP. After the update I'm stuck in a Google boot loop. What can I do. I can't get back into TWRP but I can get to the bootloader. Any help would be great!
Click to expand...
Click to collapse
What's stopping you accessing twrp from your bootloader? Is it not booting into it?
Sent from my Desire S using Tapatalk
It actually would go to the TWRP logo then go straight back to the Google screen.
I managed a fix for those wondering. I wiped using fastboot and now I've installed Mahdi and I'm doing much better.
Related
I tried updating to the new 4.2 ota, I installed stock ROM then booted then back to recovery to install 4.2 update. I lost root as expected, however my ota root keeper says the is not root backup file even though I ran it before doing all that. Not sure what happened.
On top of that I can't reboot into recovery without going through boot loader. It seems as though the update removed my custom recovery too.
I could easily fix all this if I were home, but I am at work today...no adb access. Is there a way to fix root and recovery without a computer?
Sent from my Nexus 7 using Tapatalk 2
GatorsUF said:
I tried updating to the new 4.2 ota, I installed stock ROM then booted then back to recovery to install 4.2 update. I lost root as expected, however my ota root keeper says the is not root backup file even though I ran it before doing all that. Not sure what happened.
On top of that I can't reboot into recovery without going through boot loader. It seems as though the update removed my custom recovery too.
I could easily fix all this if I were home, but I am at work today...no adb access. Is there a way to fix root and recovery without a computer?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
To enable ADB to go:
Settings-> About Tablet-> Click Build Number for Easter Egg Multiple times! BOOM!
I am not sure if there's a way of rooting without PC and custom recovery.
hello guys,
I had 4.4.1 rom+kernel stock, rooted and custom recovery, after the OTA to 4.4.2 lost my root and recovery.
tried re-root with wug's but it gets stuck on "pushing root file to you device".
got superSU application but cant remove it because its system application.
Is there a way to root it?
thanks.
Same here except i had cwm touch latest. It seems i have lost my recovery too. If i try and boot into the recovery menu i get the open hood android with a red triangle.
No custom kernel only custom recovery.
Sent from my Nexus 7 (2012)
I lost my custom recovery too. But I just reflashed it (adb reboot bootloader, then flashed a downloaded custom recovery via fastboot), and then reflashed SuperSU as well.
Sent from my Nexus 4 using XDA Premium 4 mobile app
I'm having the same problem. Root undone, and recovery went back to stock. Custom recovery doesn't stick after reboot.
santoshgs said:
I'm having the same problem. Root undone, and recovery went back to stock. Custom recovery doesn't stick after reboot.
Click to expand...
Click to collapse
I was in the same situation after my OTA of 4.4.2
I had nexus root toolkit, tried to put in twrp with it failed.
Then updated to the latest nrt and then I could flash the latest twrp, havent tried cwm.
and eventually got the root back using nrt
7thAkash said:
I was in the same situation after my OTA of 4.4.2
I had nexus root toolkit, tried to put in twrp with it failed.
Then updated to the latest nrt and then I could flash the latest twrp, havent tried cwm.
and eventually got the root back using nrt
Click to expand...
Click to collapse
Ah, glad that it worked! ^_^
santoshgs said:
I'm having the same problem. Root undone, and recovery went back to stock. Custom recovery doesn't stick after reboot.
Click to expand...
Click to collapse
Found the solution to my problem. Used CF Auto Root instead of manually flashing SuperSU again. Cheers guys!
http://download.chainfire.eu/363/CF...merhead-hammerhead-nexus5.zip?retrieve_file=1
Same thing happened to me. just use fastboot to flash CWM, then before you reboot go into the recovery. then next time you reboot it will still be there. For some reason if I flash the recovery then reboot without entering recovery it will loose the recovery.
Once you have the recovery back, just flash the SuperSU binary through CWM.
Also, IMHO, dont use toolkits... you dont really know whats going on when you use those. Learn to use ADB & fastboot. They are really simple to use and you will be better able to help yourself when you have problems in the future.
Hey, today Supersu wanted to update from the play store so i updated it, and once it was done it asked to restart the phone like usual, i restarted and when it was done booting supersu said the phone was no longer rooted. Not exactly sure what to do to fix this, i am on the unlocked V20 (US996) i am not running any rom, just stock and root. Hopefully you guys can help me get root back on my phone, thank you.
If you have TWRP installed , try to flash a supersu zip file for the update or one from a rom in the development thread . I just updated myself but didn't reboot yet.
I think the Playstore update screws it up.
You need to search the update .zip and flash it in recovery.
SuperSU 2.80 and 2.81 are both broken. Flash 2.79 SR3 in TWRP and root will be back. Worked for me anyway.
P.S. Don't re-update through the Play Store until they fix the issue, just stay with 2.79 SR3 for now.
Bubba Fett said:
If you have TWRP installed , try to flash a supersu zip file for the update or one from a rom in the development thread . I just updated myself but didn't reboot yet.
Click to expand...
Click to collapse
I downloaded the supersu zip from chainfire's site supersu 2.46. Flashed it and then rebooted, however the boot never ended, it doesn't seem to be bootlooping it just gets to the final boot animation and sits on that, waited 10 minutes and it still never made it to the home screen, trying to figure out how to get into twrp from here.
Okay, i found this thread https://forum.xda-developers.com/v20/how-to/booting-recovery-t3488099/page2 which states that pressing the power and volume down button in a certain way will take me to a white screen asking me to reset my phone and that if i have twrp installed (Which i do) it will take me to twrp saying yes, should i do this to get to twrp and then flash Supersu 2.79 as jeston suggested? And should i wipe dalvik/cache after flashing?
Okay i fixed it, entered the bootloader by doing the power and volume button factory reset thing i found and then flashed supersu 2.79, then wiped the dalvik/cache and rebooted, it bootlooped once but it started after that and is working perfectly! Thank you all for your help!
Good to see you're sorted now.
meccano300 said:
Hey, today Supersu wanted to update from the play store so i updated it, and once it was done it asked to restart the phone like usual, i restarted and when it was done booting supersu said the phone was no longer rooted. Not exactly sure what to do to fix this, i am on the unlocked V20 (US996) i am not running any rom, just stock and root. Hopefully you guys can help me get root back on my phone, thank you.
Click to expand...
Click to collapse
I had the same problem. Lost root after allowing supersu to update from playstore.
Just flashed supersu2.79.zip in twrp and was rooted again.
I lost root after updating SuperSU. I don't think it was from the Play Store, it was a SuperSU notification that kept bugging so I let it do it's thing and then lost root after rebooting. I do not have TWRP because I have a locked bootloader (Samsung on Verizon). How do I get it back?
So I just got my Nexus 6p today and I've tried rooting this thing but it just kept making me stuck on the google logo. I successfully unlocked the bootloader and installed TWRP but everytime I installed from ZIP SuperSU or Magisk it would keep getting me stuck on the google logo. I've tried this several times because I could still go to bootloader. I've flashed the stock image a couple of times and reinstalled TWRP but I just can't get it to root.
Edit: I have flashed to stock and I'm on 6.0. I haven't tried reinstalling TWRP but the bootloader is unlocked and everything else is stock.
Edit 2: I just flashed TWRP and now I'm stuck on the google logo. Wtf is this??
nemesis101x said:
So I just got my Nexus 6p today and I've tried rooting this thing but it just kept making me stuck on the google logo. I successfully unlocked the bootloader and installed TWRP but everytime I installed from ZIP SuperSU or Magisk it would keep getting me stuck on the google logo. I've tried this several times because I could still go to bootloader. I've flashed the stock image a couple of times and reinstalled TWRP but I just can't get it to root.
Edit: I have flashed to stock and I'm on 6.0. I haven't tried reinstalling TWRP but the bootloader is unlocked and everything else is stock.
Edit 2: I just flashed TWRP and now I'm stuck on the google logo. Wtf is this??
Click to expand...
Click to collapse
Could be because you are on older version of Android. Did you make sure you are on the correct bootloader? Anyways I found with stock you must complete the initial setup then you can go back and root later. I've had success with Magisk 16.0 on nougat and Oreo so don't see why it wouldn't work on marshmallow.
Exodusche said:
Could be because you are on older version of Android. Did you make sure you are on the correct bootloader? Anyways I found with stock you must complete the initial setup then you can go back and root later. I've had success with Magisk 16.0 on nougat and Oreo so don't see why it wouldn't work on marshmallow.
Click to expand...
Click to collapse
What is a 'correct bootloader' anyway? I am on the latest bootloader and flashed latest factory images and still bootlooping, can't even make it to recovery mode (flashed 4-cores TWRP after I flashed stock).
Gamool said:
What is a 'correct bootloader' anyway? I am on the latest bootloader and flashed latest factory images and still bootlooping, can't even make it to recovery mode (flashed 4-cores TWRP after I flashed stock).
Click to expand...
Click to collapse
Ok sorry you said 6.0 in comment that's why I asked about bootloader. Also thought was just the root giving you a hard time not the dreaded bootloop that some 6Ps get.
I've messed everything up and now I'm devastated!
My S8 stucks at the very first screen (where it says: SAMSUNG GALAXY S8 - powered by android). It doesn't boot further this very specific screen. I have tried to update Magisk and Magisk Manager but only Magisk Manager seems to get updated successfully while the app suddenly says that the latest version of Magisk Manager required Magisk V19.XX hence I've tried to install it via TWRP. According to log screen, I've managed to install magisk via TWRP but after booting up, I opened Magisk Manager where it now says that Magisk isn't installed. I therefore boot into TWRP and tried to fix it since some apps of mine that required root access wasn't working anymore. So, I thought I must have lost root access. I once again boot into recovery, I uninstalled magisk and install an older version of magisk and magisk manager and also the no_verity patch. After that my Galaxy S8 won't boot up. It just stucks at the very first screen. My S8 (international version) is still on Nougat stock samsung firmware and I can enter TWRP but the phone remains freeze and stubbornly refused to boot up.
I'm quite devastated and I hope you guys can help me fix this issue!
Thank you!
Hi, well sorry if I am stating the obvious but I would format and install one of the many custom roms available...
tosmaniac said:
Hi, well sorry if I am stating the obvious but I would format and install one of the many custom roms available...
Click to expand...
Click to collapse
Are there any solutions other than flashing a custom rom? Meanwhile, I have managed to flash Android 9 via ODIN and have TWRP installed but it won't boot up and stucks at the very first booting screens.
Any help would be appreciated!
Thanks!
cocolish said:
Are there any solutions other than flashing a custom rom? Meanwhile, I have managed to flash Android 9 via ODIN and have TWRP installed but it won't boot up and stucks at the very first booting screens.
Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
Have you tried just flashing stock rom only to see if it boots up. You may have to do a clean install.
Problem sounds like you haven't decrypted phone and flashed no verity zip file.
You won't need to flash a custom rom to fix this.
As for magisk have a look through this very helpful guide for installs and troubleshooting.
https://www.didgeridoohan.com/magisk/HomePage
I've managed to solve this issue by myself. But still, thank you so much! It's the thought that counts ? And yes, I've figured out that I haven't decrypt my S8. But everything is absolutely fine now and I feel extremely relieved. It took me 1 day to fix this major issue and I've encountered lots of difficulties while trying to fix this like bootloops, system won't boot up and managed to stuck at the very first booting screen again and the phone boot past the first booting screen and stucks at the second booting screen, and also bootloader error and stuffs like where realization hit me that I can't restore my nandroid backup while still on Nougat because after restoring it won't boot up. I therefore managed to flash Android 9 and twrp. My S8 is now on Android Pie with custom recovery and rooted (via Magisk).