help after flashing superSU, phone will not start. 7.0 - Nexus 6P Q&A, Help & Troubleshooting

hello everyone.. i just updated to 7.0 using ADB. that went smooth. rebooted into the system played with 7.0 for a bit . then i notice i didnt have root any more. i read that we needed to install twrp 3.0.2.3 for 7.0. so i installed twrp 3.0.2.3 with ADB. then i flash superSU v2.78 stable. now my phone stays in the colorfull circles screen. its been that way for 45mins. i am at a lost. what is the next step i should take??

As far as I know there's no TWRP 3.0.2-3 for angler. You should only download from TWRP.
Current version (3.0.2-2) here: https://dl.twrp.me/angler/twrp-3.0.2-2-angler.img.html
Flash current version with fastboot.

Pig Vomit said:
As far as I know there's no TWRP 3.0.2-3 for angler. You should only download from TWRP.
Current version (3.0.2-2) here: https://dl.twrp.me/angler/twrp-3.0.2-2-angler.img.html
Flash current version with fastboot.
Click to expand...
Click to collapse
3023 is a fixed unofficial version

Pig Vomit said:
As far as I know there's no TWRP 3.0.2-3 for angler. You should only download from TWRP.
Current version (3.0.2-2) here: https://dl.twrp.me/angler/twrp-3.0.2-2-angler.img.html
Flash current version with fastboot.
Click to expand...
Click to collapse
Gee, hard to see how bad info gets around. -2 is buggy on large backups. Unofficial -3 is the version to use.
Sent from my Nexus 6P using Tapatalk

ok .. some help please..

Lw00d said:
ok .. some help please..
Click to expand...
Click to collapse
Did you try flashing boot and system again?

istperson said:
Did you try flashing boot and system again?
Click to expand...
Click to collapse
no i have not.. i will try now

This couldn't be a problem with the unofficial TWRP could it? Always some risk involved when trying such new and relatively untested software

ok i updated to the new 7.0.0 (NBD91K) . everything went smooth.. booted up system send some text. bc phone would not boot up.. then i go to flash superUS v2.78 SR3. i thougt maybe that will help. im using twrp 3.0.2-3. i flash> wipe cache/dalvik > reboot. phone will not boot up..
is there another way i could flash superSU. other then twrp.. ????
EDIT:: im going to try installing 7.0.0 (NRD90U) .. see if superSU works

no that didnt work either.

Seems like a familiar issue as in the WETA ROM thread. Can you use cf-auto root instead of flashing SuperSU?

Related

i337m gets auto-unrooted everytime I do system update of nightly version

As the subject mentioned, It gets auto-unrooted. So, every nightly update, I always do CF-Auto-Root to root it again.
The problem is my TWRP recovery gets wiped, and I still have to install new TWRP recovery again.
Is there any other easier rooting method which doesnt erase my TWRP recovery other than CFroot method?
khunkami said:
As the subject mentioned, It gets auto-unrooted. So, every nightly update, I always do CF-Auto-Root to root it again.
The problem is my TWRP recovery gets wiped, and I still have to install new TWRP recovery again.
Is there any other easier rooting method which doesnt erase my TWRP recovery other than CFroot method?
Click to expand...
Click to collapse
OK, that's REALLY strange... TWRP shouldn't be getting clobbered unless the way you're installing it is causing weird issues.
Have you tried flashing TWRP using heimdall/odin/JOdin? It sounds like you're using some sort of root app to flash it on-device???
As to losing root - SuperSU->Settings->Install backup script is the workaround until we integrate SuperSU into omni.
Entropy512 said:
OK, that's REALLY strange... TWRP shouldn't be getting clobbered unless the way you're installing it is causing weird issues.
Have you tried flashing TWRP using heimdall/odin/JOdin? It sounds like you're using some sort of root app to flash it on-device???
As to losing root - SuperSU->Settings->Install backup script is the workaround until we integrate SuperSU into omni.
Click to expand...
Click to collapse
I installed TWRP recovery through Goomanager, install script on the phone.
Is that why my TWRP recovery keeps getting removed everytime I do system update?
khunkami said:
I installed TWRP recovery through Goomanager, install script on the phone.
Is that why my TWRP recovery keeps getting removed everytime I do system update?
Click to expand...
Click to collapse
Possibly, goomanager might be doing something weird like doing a fakeflash. I'm not sure.
If you install a TWRP image using heimdall or odin it should persist - the dd method listed in http://teamw.in/project/twrp2/124 should work too. (i337 is the AT&T/Rogers Note2, right?)
Omni shouldn't be flashing recovery on this device (Omni only changes recovery on devices that can't change kernel without changing recovery - like the I9100/I777/N7000 and many Sonys), but even if it is, it should be flashing a TWRP build...
Entropy512 said:
Possibly, goomanager might be doing something weird like doing a fakeflash. I'm not sure.
Click to expand...
Click to collapse
I've seen / had the issue to with GooManager. Indeed it is doing a "fakeflash", if you go into recovery from GooManager you will get into the recovery but after that. If you do it on boot you won't get there. No matter what, unless you do a manual install for the recovery..
Hope this helped,
Gertlily said:
I've seen / had the issue to with GooManager. Indeed it is doing a "fakeflash", if you go into recovery from GooManager you will get into the recovery but after that. If you do it on boot you won't get there. No matter what, unless you do a manual install for the recovery..
Hope this helped,
Click to expand...
Click to collapse
I am just curious. Why does Omni Rom unroot the device after system-update?
khunkami said:
I am just curious. Why does Omni Rom unroot the device after system-update?
Click to expand...
Click to collapse
It is not only the issue on OmniROM but on (almost) every ROM, I've had the same on cyanogen and Samsung Stock.. So flashing it yourself is better.. Hope this bug will get fixed somewhere in the future.
Bye,
Sent from my Nexus 7 using Tapatalk
khunkami said:
I am just curious. Why does Omni Rom unroot the device after system-update?
Click to expand...
Click to collapse
It's because Omni doesn't have root yet. It's on the to do list. The easiest way is to install SuperSU to system, then install the back up script. That way you'll keep root through updates.
khunkami said:
As the subject mentioned, It gets auto-unrooted. So, every nightly update, I always do CF-Auto-Root to root it again.
The problem is my TWRP recovery gets wiped, and I still have to install new TWRP recovery again.
Is there any other easier rooting method which doesnt erase my TWRP recovery other than CFroot method?
Click to expand...
Click to collapse
I know very little about anything, and I was experiencing this same thing. CF-Auto-Root reinstalls stock recovery which overwrites TWRP during the rooting process. Each time I update a nightly and then run CF-Auto-Root to re-root it. After that I use mobile ODIN to reinstall TWRP recovery and all is good.
AKdballs said:
I know very little about anything, and I was experiencing this same thing. CF-Auto-Root reinstalls stock recovery which overwrites TWRP during the rooting process. Each time I update a nightly and then run CF-Auto-Root to re-root it. After that I use mobile ODIN to reinstall TWRP recovery and all is good.
Click to expand...
Click to collapse
You shouldn't be using CF-Auto-Root if you have a custom recovery (which you need in order to install Omni). Just flash SuperSU in recovery.
I knew something wasn't quite right but I did it that way because it works. I have downloaded su onto the SD card, as well as the latest nightly build of Omni. Can I install the new nightly with TWRP, and add su as a second zip to install at the same time? Or should I flash them separately?
Sent from my SGH-I337M using xda app-developers app

Need the OEM Marshmallow system images for the OG Shield.

Long story short, I messed up and soft bricked my OG Shield, and I need someone to upload the OEM Image files.
I would also like it if someone would provide download links to a semi stable version of TWRP and a SuperSU binary for 6.0.
Crayman122 said:
Long story short, I messed up and soft bricked my OG Shield, and I need someone to upload the OEM Image files.
I would also like it if someone would provide download links to a semi stable version of TWRP and a SuperSU binary for 6.0.
Click to expand...
Click to collapse
+1 but i think we will have to wait for nvidia to release them.
I'm trayng to downgrade using lollipop recovery image 3.1.1. installation looks ok but tablet get stuck at nvida logo.
lupick said:
I'm trayng to downgrade using lollipop recovery image 3.1.1. installation looks ok but tablet get stuck at nvida logo.
Click to expand...
Click to collapse
Wrong boot image. Need to flash lollipop boot Image
lupick said:
I'm trayng to downgrade using lollipop recovery image 3.1.1. installation looks ok but tablet get stuck at nvida logo.
Click to expand...
Click to collapse
same. got this after flashing supersu
FIXED!!! Found a download link to the update.zip burried in some other forum. Now I just need someone to provide a link to a working SuperSU and xposed framework for OG ST
I had the same problem, I got out of bootloop by flashing the 4.0 update and SuperSU in two steps:
1st flash update zip, clear caches and reboot
2nd flash SuperSU 2.67 and reboot
Of course you will need the experimental twrp for marshmallow
Hope it works for you like it did for me.
Good luck!
Crayman122 said:
FIXED!!! Found a download link to the update.zip burried in some other forum. Now I just need someone to provide a link to a working SuperSU and xposed framework for OG ST
Click to expand...
Click to collapse
Did you flash it through fastboot?
sshep1986 said:
Did you flash it through fastboot?
Click to expand...
Click to collapse
No. I flashed the file through twrp unstable. I didn't flash twrp as recovery, but you can use this to boot twrp without flashing and it still works fine:
Code:
fastboot boot <twrp recovery for shield>.img
Here is the link for the TWRP Recovery. It's a little bit unstable, but it still works ok-ish. UI is REALLY glitchy, that's why I didn't flash, but core functionality is still there.
Crayman122 said:
No. I flashed the file through twrp unstable. I didn't flash twrp as recovery, but you can use this to boot twrp without flashing and it still works fine:
Code:
fastboot boot <twrp recovery for shield>.img
Here is the link for the TWRP Recovery. It's a little bit unstable, but it still works ok-ish. UI is REALLY glitchy, that's why I didn't flash, but core functionality is still there.
Click to expand...
Click to collapse
Thankyou very much. Appreciate the reply. Unfortunately mine hangs on the booting downloaded image. Still got my spare Shield to use for now. I will have to wait for the release of the factory image. Hopefully wont take forever. Cheers
lowsum said:
i had the same problem, i got out of bootloop by flashing the 4.0 update and supersu in two steps:
1st flash update zip, clear caches and reboot
2nd flash supersu 2.67 and reboot
of course you will need the experimental twrp for marshmallow
hope it works for you like it did for me.
Good luck!
Click to expand...
Click to collapse
thank you so much!!!! You saved me from the hell of stock android!!!

Wrongly installed TWRP 3.0. 2-0

I was running on an older version of TWRP. Also I had uprooted my phone recently due to battery heating and media server issue. I flashed the new zip file but did not clear cache after flashing instead directly booted into system. System boots perfectly but cannot load recovery as it gets stuck on splash screen( Lenovo logo). Please do help me.
Flash it back to older twrp version using fastboot.
Guys, hi
There is one more new problem. I tried to update the OTA update but got stuck at boot screen. It's not responding after the Lenovo logo. I think the issue is not having any recovery(custom nor stock). How to fix this issue? Please help me to
# Reset stock recovery or TWRP 3.0.2-0
# Update the OTA update( I badly want this as I saw that Resurrection Remix requires the device to presently run on stock Lollipop to update. I soo badly want to use CM13
Iamjomy said:
I was running on an older version of TWRP. Also I had uprooted my phone recently due to battery heating and media server issue. I flashed the new zip file but did not clear cache after flashing instead directly booted into system. System boots perfectly but cannot load recovery as it gets stuck on splash screen( Lenovo logo). Please do help me.
Click to expand...
Click to collapse
Use cwm ...its working 100% sure
ANDROiDCO said:
Flash it back to older twrp version using fastboot.
Click to expand...
Click to collapse
Thank you. But can you please tell how to do this via the flash boot. I haven't tried yet in a PC. I installed the older TWRP and now tried flashing the new version using my phone. Wouldn't I get stuck because none of the recoveries(custom and stock) are opening
can you boot into the system? if Yes then use rashr app and flash twrp's img file from the storage.. and reboot to recovery and u don't need to update to stock lollipop you can directly flash cm12.1 by ed300 and after booting into system once you can install any lollipop or marshmallow rom with the help of recovery. i advice you to not to do update as u r a root user.
varun4495 said:
can you boot into the system? if Yes then use rashr app and flash twrp's img file from the storage.. and reboot to recovery and u don't need to update to stock lollipop you can directly flash cm12.1 by ed300 and after booting into system once you can install any lollipop or marshmallow rom with the help of recovery. i advice you to not to do update as u r a root user.
Click to expand...
Click to collapse
Thank you bro. Yes I can boot into system. Actually I'm not root user anymore. I had heating issues with the battery earlier. After rooting media server started draining battery. So i uninstalled SuperSU.
Iamjomy said:
Thank you bro. Yes I can boot into system. Actually I'm not root user anymore. I had heating issues with the battery earlier. After rooting media server started draining battery. So i uninstalled SuperSU.
Click to expand...
Click to collapse
You first hv to root for the installation of recovery.. First root ur phone then install stock recovery.. Using flashify or rashr.
If you can boot into system, then you can use adb sideload to flash zips(recovery or rom).
For detailed info, google it or go to http://www.droidviews.com/sideload-roms-mods-using-adb-sideload/
If it doesn't work, root your phone and then install flashfire. Then use it to flash recovery.
varun4495 said:
You first hv to root for the installation of recovery.. First root ur phone then install stock recovery.. Using flashify or rashr.
Click to expand...
Click to collapse
Thanks bro. Is it bad to root using iRoot or KingRoot? Or should I do it using ADB?
@Iamjomy if you have pc then go for adb otherwise go for the latest version of kingoroot.. I rooted with kingroot.. No problem in that.. You can find that apk by searching on google.. !!
varun4495 said:
@Iamjomy if you have pc then go for adb otherwise go for the latest version of kingoroot.. I rooted with kingroot.. No problem in that.. You can find that apk by searching on google.. !!
Click to expand...
Click to collapse
Hello,
Thank you soo much. I flashed TWRP 2.8 using Flashify and it works. Actually I wanted to do a factory reset to solve "Unfortunately the process com.android.phone has stopped" issue. It wasn't allowing me to turn on my mobile data. I couldn't reset the phone too as a recovery was missing. Now the issue is fixed and I'm happy with it. Can I flash the TWRP 3.0.2-0 similarly using Flashify? Also please do suggest some good ROMS bro. Im still on the KitKat version( S040_150805)
Iamjomy said:
Hello,
Thank you soo much. I flashed TWRP 2.8 using Flashify and it works. Actually I wanted to do a factory reset to solve "Unfortunately the process com.android.phone has stopped" issue. It wasn't allowing me to turn on my mobile data. I couldn't reset the phone too as a recovery was missing. Now the issue is fixed and I'm happy with it. Can I flash the TWRP 3.0.2-0 similarly using Flashify? Also please do suggest some good ROMS bro. Im still on the KitKat version( S040_150805)
Click to expand...
Click to collapse
Recovery version are depended on the different andtoid versions.. 3.0.2 is for the LP and MM.. If u use custom roms then u can use that.. I dnt suggest you to use that as u r on the lollipop.. And the best roms are.. CM12.1, RR5.7.3, MOKEE, XOSP.. press thanks if i helped you. !!

Root on Android 7.1 beta

Hey guys, so I installed twrp and formatted data, rebooted, installed super su (sr version), and now my phone is decrypted and rooted on 7.1.1 Just passing this along if anyone needs it
Xdevillived666 said:
Hey guys, so I installed twrp and formatted data, rebooted, installed super su (sr version), and now my phone is decrypted and rooted on 7.1.1 Just passing this along if anyone needs it
Click to expand...
Click to collapse
Screenshots guys
I can confirm CF-Autoroot works without flaws!
I used the Nexus Root Toolkit and that worked a charm, got recovery and root installed easily.
What recovery are you guys using? latest 3.0.2-3?
Krenol said:
What recovery are you guys using? latest 3.0.2-3?
Click to expand...
Click to collapse
I'm using 3.0.2-1 but I have heard people say 3.0.2-2 works as well. Hope that helps
does formatting the data is really needed? I tried to flash twrp with everything on stock (encrypted), it works on first boot of twrp but whenever I boot to system then try to boot to twrp, it gives 'No Command' and I have to reflash twrp again :silly:
RonnellTapawan said:
does formatting the data is really needed? I tried to flash twrp with everything on stock (encrypted), it works on first boot of twrp but whenever I boot to system then try to boot to twrp, it gives 'No Command' and I have to reflash twrp again :silly:
Click to expand...
Click to collapse
It would seem so. Until I decrypted, I wasn't able to keep it permanently installed.
I can also say that Nexus Root Toolkit worked for me. That's a great app - I suggest using it and helping the developer!
Razeer123 said:
I can also say that Nexus Root Toolkit worked for me. That's a great app - I suggest using it and helping the developer!
Click to expand...
Click to collapse
Yeah, it is nice . I just like doing it myself ,though I used the app to flash stock recovery and get the ota.... Speaking of the ota , does anyone else have "android 7.1.1" under about phone ???
I rooted at first with PHH suhide and the only thing I couldn't do was change system files, as expected. Flashed back to stock, updated to dev preview again (clean slate) and installed magisk v8 and root. Everything is working fine and dandy.
Xdevillived666 said:
Yeah, it is nice . I just like doing it myself ,though I used the app to flash stock recovery and get the ota.... Speaking of the ota , does anyone else have "android 7.1.1" under about phone ???
Click to expand...
Click to collapse
Yeah, I think everyone have this number. I suppose the x.x.1 means Security Patch number, but I'm not sure.
I'm new to the beta program. What happens if I root and install a custom recovery in this beta version 7.1.1? I assume that I will no longer be able to get future incremental OTA beta updates?
ToothTooth said:
I'm new to the beta program. What happens if I root and install a custom recovery in this beta version 7.1.1? I assume that I will no longer be able to get future incremental OTA beta updates?
Click to expand...
Click to collapse
You can. Just before installing , reinstall stock recovery and then install ota or use flash fire
Have any of you been able to use SuHide?
Im just getting a constant bootlogo and no further.
Morning all
Just checking in to say I've been running this 7.1.1 preview for over 24 hours, without so much as a slight hiccup. It's very smooth and fluid. I haven't bothered rooting or anything yet as the phone runs beautifully as is, but no doubt I will tinker when I get back from a short break. Only disappointing thing is android pay not working due to unlocked bootloader
Anyone has no-force decrypt boot img, coz seems like device is encrypted, as Im stuck with TWRP(3.0.2-1) logo
odunke01 said:
Have any of you been able to use SuHide?
Im just getting a constant bootlogo and no further.
Click to expand...
Click to collapse
My bad, didnt wait long enough.
Problem is though that we cant seem to keep changes to the /system file on the preview
https://www.reddit.com/r/Android/comments/58npsl/71_appears_to_aggressively_fix_errors_to_the/
odunke01 said:
My bad, didnt wait long enough.
Problem is though that we cant seem to keep changes to the /system file on the preview
https://www.reddit.com/r/Android/comments/58npsl/71_appears_to_aggressively_fix_errors_to_the/
Click to expand...
Click to collapse
What are you using su hide for?
It was for pokemon go.
Although I have reverted to PN on 7.0 as I was having other issues. Root (edit:and recovery) wasn't holding after reboot and my hosts file kept disappearing.
I also missed the night light.

new info about nougat twrp

found this info from this source
http://androiding.how/huawei-mate-8-nougat-root-twrp/
Thank you for the info; I was waiting for this.
Any idea where is the developer's thread or site; androiding.how didn't provide the link.
As far as I know this was for honor 8. @LastStandingDroid built for honor 8 nougat. It currently cannot flash SuperSU anyway
Thank you! I have just found LastStandingDriod thread.
I have tried this TWRP. You can boot into TWRP, touch is fine. But it cannot flash supersu into system. Got a reboot when I tried to do that.
insideccw said:
I have tried this TWRP. You can boot into TWRP, touch is fine. But it cannot flash supersu into system. Got a reboot when I tried to do that.
Click to expand...
Click to collapse
Did you try SR3 SuperSU?
insideccw said:
I have tried this TWRP. You can boot into TWRP, touch is fine. But it cannot flash supersu into system. Got a reboot when I tried to do that.
Click to expand...
Click to collapse
To me I spend exactly the same thing, twrp is fine, but the root no.
To wait for someone to do it and tell us how
thanks for the info.
tried it...
can boot to recovery... but cant do anything else

Categories

Resources