I recently rooted my phone on 7.1.2, then I got a boot loop in twrp and somehow I went back on to when I was on the beta O firmware when supersu working. If I unenroll will I get back in a boot loop or will I just loose root and be back to "normal'
Related
I managed to upgrade my Nexus 7 2013 LTE from KitKat to Marshmallow using factory images yesterday and took some notes. All apps and settings kept (or at least I haven't noticed any issues other than no Xposed) and rooted. I figured someone might find this useful.
So, short version: upgrading directly from 4.4.4 to 6.0 with factory images didn't work without wiping data and where's the fun in that? So I took a longer route and went 4.4.4->5.02->5.1.1->6.0.0. It's possible I could've gone from 5.0.2 to 6.0 or 4.4.4 to 5.1.1 directly but I'm not going to try and see if that's the case. Enjoying Marshmallow now.
Basically, I did the same thing for all three update steps:
Unpacked factory image, rebooted to bootloader, flashed bootloader, radio, system.img, boot.img, cache.img. I rebooted to bootloader after flashing bootloader and again after flashing radio, same thing the flashall.bat does. Don't know if it matters.
Booted to TWRP recovery, flashed supersu zip and renamed /system/recovery-from-boot.p to keep TWRP.
Booted system and grew some gray hairs while the boot animation went on and on until it finally got to the long "optimizing apps" phase.
For 6.0 I flashed a modified kernel and supersu beta 2.52.
So, enjoying Marshmallow now. No issues so far. Root cloak detectors seem to be becoming a plague and I've only used an Xposed module for that.
I am at a loss.
I am crazy and like to restore to stock whenever there is a security update or anything like that just so I can remember how to flash recovery, boot images, etc.
So I had the **18-3 with the Feb update and was rooted with SuperSU ( don't recall which ) and TWRP 3.0.0-1 I believe.
When I got the notification for the new security update I promptly unrooted, and flashed the stock 24.49-18-4 / 24.221.4 firmware and am able to boot.
I have installed the latest TWRP and can boot to it, and reboot to system all I want.
I have done this process twice now because the first time I tried to install SuperSU (2.76??) after all this I got stuck on the moto logo and could not boot.
Other threads have mentioned you cannot root with SuperSu on 6.0, or something to that effect.
So I am not unrooted (I believe) on 24.49-18-4 and want to root to be able to get SuperSU and the rest of my root apps up and running.
What do I do from here?
Fixed: http://forum.xda-developers.com/moto-x-style/help/rooting-stock-xt1575-marshmallow-6-0-t3353812
Su 2.62-3 for root & boot up normal then flash over Su 2.76
Done.
Just installed Nougat stock ROM for my S7 Edge with ODIN, and trying to root.
I installed TWRP latest version 3.01 and immediately after installed supersu 2.79 SR3 from TWRP.
At first I could not boot the phone because it kept saying I used the wrong PIN code for boot. I reflashed stock rom and was able to boot again (same PIN) - disabled PIN on boot, and reflashed TWRP and supersu, but it keeps hanging at the Samsung Logo.
Flashing stock rom solves it, but I still want to root it..
What am I doing wrong?
currently there is no reliable root for nouget roms. It is being worked on.
Cosmic Blue said:
currently there is no reliable root for nouget roms. It is being worked on.
Click to expand...
Click to collapse
Thanks for replying.
In this case - even if the goal is to root - it seems the problem is with TWRP.. Even if I do not root, but just install TWRP, the neverending bootlogo shows up..
Nougat OS has been changed that all the old rooting and twrp need to be updated.
It will be a while till developers can modify the os to allow changes.
Have posted the same question in the TWRP S7 thread that I did not see before posting this one - sorry
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.
After a painful rooting process, I finally achieved root with Magisk 19.1 and unlocked bootloader. I decided to load Super V20 ROM this morning but it has never finished the boot process. It's sticking on the Verizon boot animation. As far as the stock phone, I had version VS99510B and Android 7.0, running TWRP 3.2.1-0. When I went through the options in the Aroma loader for Super ROM, I don't think I chose anything crazy. I selected Magisk & MK2000 kernel (though, that didn't have any effect on the static screen; I was told it would).
After the first load attempt, I went back into TWRP, triple-wiped everything and reflashed again. Same effect. It just won't move past the Verizon boot animation. What could be the issue? Is there anything I can fix here or do I need to reload all the stock software? If that is the case, do I need to go back to 10B or would a newer version work better? I do intend to load a custom ROM at some point but I just want to get this phone functioning again.
Right now, I do have access to recovery (TWRP 3.2.1-0) so all is not lost. Got any help?
Thanks all.
LG V20 VS995, attempting Super V20 4.1 (8.2.18), Magisk 19.1, TWRP 3.2.1-0