Database Users

[Q] Updating nexus 7 to 4.1.2 using OTA

Hello,
I've got a Nexus 7 that is rooted, has stock ROM and has CWM recovery (flashed using ROM manager i think). I wanted to update my nexus 7 to 4.1.2 due to the lag bug, but i'm now confused on how to do it after reading a few threads.
I have a few n00b questions:
1. Preferebly, i'd like to update OTA. Will an OTA update notification come up, even though i have CWM recovery? and if it does, will I be able to update using OTA without any problems caused by CWM?
2. How to I keep root access with OTA rootkeeper? Do I install it before I update android? and what if I have SuperSU (not pro version) installed?
3. If I can't update OTA, do I install OTA rootkeeper, install update.zip using CWM recovery and restore root?
I'd really appreciate if anyone could help me out. Thanks.

If you have superSU you can put it in survival mode and it will stick. But I have pro version, not sure if you need that. If you have custom recovery (cwm or twrp) you will need to either go back to stock recovery and OTA, or download and flash the update yourself.
Rootbrain

I received the OTA notification and tried to take it, but it failed because I had renamed the stock browser .apk and .odex files to use the GNex browser that works with flash. After renaming them both back, I copied the OTA from /cache to root and installed it in CWM recovery (choosing 'reboot into recovery' from Rom Manager). I kept CWM recovery and kept root with no problems.

Groid said:
I received the OTA notification and tried to take it, but it failed because I had renamed the stock browser .apk and .odex files to use the GNex browser that works with flash. After renaming them both back, I copied the OTA from /cache to root and installed it in CWM recovery (choosing 'reboot into recovery' from Rom Manager). I kept CWM recovery and kept root with no problems.
Click to expand...
Click to collapse
How did you keep root?
I have superSU installed and it's not the pro version (so no survival mode). Can I use OTA rootkeeper with it?

Is there a guide somewhere that spells out how we can update a rooted Nexus 7 to 4.12? I used the Wugfresh app to root. I'd ask in that topic, but don't have enough posts, yet, to have permission. I realize that there is a lot of info about this here, but some of it is, to me, something of a noob, contradictory and I'm not really sure what I need to do.
I tried doing an OTA update with SuperSU trying to protect root, but it wouldn't install, maybe because I'd used Wugfresh's kit. I’m not sure.
Any help or pointers would be appreciated.

v9s said:
How did you keep root?
I have superSU installed and it's not the pro version (so no survival mode). Can I use OTA rootkeeper with it?
Click to expand...
Click to collapse
I also have Supersu (not pro) and I did install Voodoo OTA Rootkeeper and ran it before installing the OTA. Sorry, should have mentioned that. After the OTA installed, I got an option in CWM to 'flash stock recovery' on reboot. I chose 'no' to keep my CWM recovery. Then I got a prompt to try and regain root, to which I said 'yes'. I booted into the new 4.1.2 and still had root and still had the ability to 'reboot into recovery' from Rom Manager. I feel quite lucky given the threads in which people have had lots of problems, even resorting to loading an older bootloader, modifying scripts, etc. Mine went smooth as silk and my N7 is running great.

Groid said:
I also have Supersu (not pro) and I did install Voodoo OTA Rootkeeper and ran it before installing the OTA. Sorry, should have mentioned that. After the OTA installed, I got an option in CWM to 'flash stock recovery' on reboot. I chose 'no' to keep my CWM recovery. Then I got a prompt to try and regain root, to which I said 'yes'. I booted into the new 4.1.2 and still had root and still had the ability to 'reboot into recovery' from Rom Manager. I feel quite lucky given the threads in which people have had lots of problems, even resorting to loading an older bootloader, modifying scripts, etc. Mine went smooth as silk and my N7 is running great.
Click to expand...
Click to collapse
I've had less luck. I tried to keep root, but the OTA wouldn't install. So I downloaded the .zip and installed it. That got me to 4.1.2, but I can't get root back for reasons that are unclear to me. I go through the process and get what seems like the right feedback, but it's not working for whatever reason. I'm not rooted anymore.
I may have to go back to stock and start over again.

Other posters have said to use the toolkit again to root and install a recovery. Supposedly it works just as well after the update. Is that the process you are using? Did you use stock or a custom recovery? I originally unlocked, rooted, and installed cwm recovery with Wug's rootkit, so I figure it's not the problem.

Groid said:
I also have Supersu (not pro) and I did install Voodoo OTA Rootkeeper and ran it before installing the OTA. Sorry, should have mentioned that. After the OTA installed, I got an option in CWM to 'flash stock recovery' on reboot. I chose 'no' to keep my CWM recovery. Then I got a prompt to try and regain root, to which I said 'yes'. I booted into the new 4.1.2 and still had root and still had the ability to 'reboot into recovery' from Rom Manager. I feel quite lucky given the threads in which people have had lots of problems, even resorting to loading an older bootloader, modifying scripts, etc. Mine went smooth as silk and my N7 is running great.
Click to expand...
Click to collapse
Thanks!
I did exactly what you did before reading your reply and my update process went the same way.

Groid said:
I also have Supersu (not pro) and I did install Voodoo OTA Rootkeeper and ran it before installing the OTA. Sorry, should have mentioned that. After the OTA installed, I got an option in CWM to 'flash stock recovery' on reboot. I chose 'no' to keep my CWM recovery. Then I got a prompt to try and regain root, to which I said 'yes'. I booted into the new 4.1.2 and still had root and still had the ability to 'reboot into recovery' from Rom Manager. I feel quite lucky given the threads in which people have had lots of problems, even resorting to loading an older bootloader, modifying scripts, etc. Mine went smooth as silk and my N7 is running great.
Click to expand...
Click to collapse
Thank you! I followed what you said and it installed perfectly.

Groid said:
Other posters have said to use the toolkit again to root and install a recovery. Supposedly it works just as well after the update. Is that the process you are using? Did you use stock or a custom recovery? I originally unlocked, rooted, and installed cwm recovery with Wug's rootkit, so I figure it's not the problem.
Click to expand...
Click to collapse
Long story short, I couldn't get root. It turns out that some people are having the identical problems that I had, others have had smooth sailing. I ended up going back to 4.1.1. At some point, when things become a little clearer, I'll try this process again.

maigre said:
Long story short, I couldn't get root. It turns out that some people are having the identical problems that I had, others have had smooth sailing. I ended up going back to 4.1.1. At some point, when things become a little clearer, I'll try this process again.
Click to expand...
Click to collapse
I cannot get root or flash a recovery. I am not used to Google device's, I manually updated to 4.1.2, so not really sure how to go back to 4.1.1. It has been a week and I have only just realised, so not real important, but I would like to get twrp back
Sent from my Nexus 7 using Tapatalk 2

Tricky103 said:
I cannot get root or flash a recovery. I am not used to Google device's, I manually updated to 4.1.2, so not really sure how to go back to 4.1.1. It has been a week and I have only just realised, so not real important, but I would like to get twrp back
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Long story short, you could try replacing the 3.41 bootloader that installed with the OTA 4.1.2 with the 3.34 bootloaded from 4.1.1.
Do this with device connected to PC, USB debugging on:
adb reboot bootloader
fastboot flash bootloader bootloader-grouper-3.34.img from the naksi-jro03d-factory-e102ba72.tgz (factory image)
fastboot flash recovery openrecovery-twrp-2.3.0.0-grouper.img (CWM recovery should work too)
fastboot reboot-bootloader
TWRP recovery should start .
flash CWM-SuperSU-v0.96.zip to regain root
update busybox binaries in SuperSU and Busybox free app.
Worked for me.

Groid said:
I received the OTA notification and tried to take it, but it failed because I had renamed the stock browser .apk and .odex files to use the GNex browser that works with flash. After renaming them both back, I copied the OTA from /cache to root and installed it in CWM recovery (choosing 'reboot into recovery' from Rom Manager). I kept CWM recovery and kept root with no problems.
Click to expand...
Click to collapse
I did this installing stock browser, what did you rename it back too. its been so long i forgot what i did. thanks

I have unlocked and rooted my N7 using the Nexus Root Toolkit but I can't remember which version and the desktop has since been formatted.
I have also patched the wallet.apk, modified build.prop (for home screen rotation before 4.1.2)
I got a notification to update the system and thus, went to install Voodoo OTA Root Keeper, protected the root and install the OTA update.
In the bootup screen, I saw the exclamation mark with the android robot but the tablet still managed to boot up.
After the tablet boots up, the settings shows it is still in 4.1.1 but when I do a system check, it mentioned that I'm on the latest.
Can someone advise on how should I go around this?
Thanks!!!

Groid said:
I also have Supersu (not pro) and I did install Voodoo OTA Rootkeeper and ran it before installing the OTA. Sorry, should have mentioned that. After the OTA installed, I got an option in CWM to 'flash stock recovery' on reboot. I chose 'no' to keep my CWM recovery. Then I got a prompt to try and regain root, to which I said 'yes'. I booted into the new 4.1.2 and still had root and still had the ability to 'reboot into recovery' from Rom Manager. I feel quite lucky given the threads in which people have had lots of problems, even resorting to loading an older bootloader, modifying scripts, etc. Mine went smooth as silk and my N7 is running great.
Click to expand...
Click to collapse
This works well, thanks

I am having the same problems as many of you. I rooted my Nexus a while ago and got a prompt for the update today. Here is the error that I am getting. Any ideas which route I should take?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Never mind I think that I just found my answer...
http://forum.xda-developers.com/showthread.php?t=1764794

[Q] SuperSU can't detect su binary after reboot

I rooted my phone with Kingroot, and ran this script to replace the Kinguser with SuperSU: http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html?m=1
After launching SuperSU it updates the binary and everything works fine until I reboot my phone. Now when I launch SuperSU it says no su binary installed. Using es file explorer I can see the su is in /system/xbin where it should be but SuperSU can't see it.
After rerooting with Kingroot and doing the same process over SuperSU will once again work fine until I reboot my phone. Anyone know what's going on and how I can get SuperSU to work properly?

Anyone?
I tried flashing the SuperSU.zip, but when I launch the app it fails to update the binary. I've also tried installing ChainsDD Superuser but it also fails to update the binary. I've even tried manually copying, setting permissions, and symlinking the files found in the SuperSU.zip, but it still fails to update.
I don't like using Kingroot because apps like Titanium Backup and Lucky Patcher don't work with it's su binary. Has anyone encountered this before? Why won't SuperSU update? And when it does update why can't it survive past a reboot? This is stressful ha. Any help is very much appreciated.
By the way I'm using a Cricket Galaxy S4 (SGH-I337Z). It's a weird model that few people seem to know about (I337ZTUUBOA1). The only root method that works on it is Kingroot otherwise I would have just rooted it some other way.

I had an idea wile reading your post could u try flashing TWRP for ur phone then rooting with the built in installer might be worth a try but u might need to Un root or flash back to what ever firmware ur using to remove root so that TWRP sees that ur not rooted

xstokerx said:
I had an idea wile reading your post could u try flashing TWRP for ur phone then rooting with the built in installer might be worth a try but u might need to Un root or flash back to what ever firmware ur using to remove root so that TWRP sees that ur not rooted
Click to expand...
Click to collapse
I've got twrp flashed. How do I use the built in root installer??

When u boot into system from TWRP it will ask you if u want to root the system but it only asks if TWRP can't detect root.

xstokerx said:
When u boot into system from TWRP it will ask you if u want to root the system but it only asks if TWRP can't detect root.
Click to expand...
Click to collapse
I unrooted and rerooted with twrp. It installed su binary, but when I install SuperSU and launch it it still gives the no binary installed error

Nihilian said:
I unrooted and rerooted with twrp. It installed su binary, but when I install SuperSU and launch it it still gives the no binary installed error
Click to expand...
Click to collapse
Try rooting with kingroot, then uninstall king user by going into king user and unrooting. Once that is done, download the newest version of SuperSU.zip (update-supersuv2.46.zip I think is newest) then copy to phone storage, reboot to twrp and then flash the SuperSU zip. Reboot and profit!
Hope this helps!
Sent from my A0001 using XDA Free mobile app

Nihilian said:
I unrooted and rerooted with twrp. It installed su binary, but when I install SuperSU and launch it it still gives the no binary installed error
Click to expand...
Click to collapse
Sorry to hear was worth a shot I can't think of any thing else right now :crying:

Klown80 said:
Try rooting with kingroot, then uninstall king user by going into king user and unrooting. Once that is done, download the newest version of SuperSU.zip (update-supersuv2.46.zip I think is newest) then copy to phone storage, reboot to twrp and then flash the SuperSU zip. Reboot and profit!
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Still no luck I think it's an issue with the SuperSU app. Something during a reboot causes it to break for some reason. I really hope it can be fixed :/

Well only thing I can think of is odin to stock and start over or find a nice custom rom that works with your phone that comes pre rooted if there are any.......

xstokerx said:
Well only thing I can think of is odin to stock and start over or find a nice custom rom that works with your phone that comes pre rooted if there are any.......
Click to expand...
Click to collapse
Finally found a working custom rom and everything is working. Thanks

Nihilian said:
Finally found a working custom rom and everything is working. Thanks
Click to expand...
Click to collapse
Awsome to hear u found something that works for u and ur welcome ?

I don't wanna open new topic coz I have similar problem.....
I have huawei g630, rooted and unlocked bootloader, but no cwm.... and supersu gives me this messages.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and when I click on that phone restarts and nothing happens..... when I cancel that this is msg.....
what could be the problem?

jabre said:
I don't wanna open new topic coz I have similar problem.....
I have huawei g630, rooted and unlocked bootloader, but no cwm.... and supersu gives me this messages.....
and when I click on that phone restarts and nothing happens..... when I cancel that this is msg.....
what could be the problem?
Click to expand...
Click to collapse
I'm sorry but I probly can't help I know nothing about your phone this is the att/Canadian s4 forum how did u get your phone rooted? U can try unrooting and rooting with a different method or retry with same method

Everything stock, suddenly stuck on Boot loop after reboot.

Short version: Nexus 4 is stuck on bootloop but it's as good as new with the stock ROM and everything.
Long version: My nexus 4 has stock kernel, stock ROM of Lollipop that was updated when google rolled it out few months back. I did have my bootloader unlocked via Nexus Root Toolkit few months back while i still had KitKat, but apart from that, i have NEVER ROOTED, NEVER INSTALLED A CUSTOM RECOVERY, NEVER CHANGED KERNEL, NEVER INSTALLED ANY OTHER CUSTOM ROMs. The only tampering i did was unlock the bootloader and never bothered anything else. But suddenly, my phone got stock on bootloop last night. I powered it off normally, full charged the phone, and when i turned it on, it got stuck ever since. It did happen once when the phone updated to lollipop for the first time, but a simple restart solved it that time. I have tried wiping cache, factory resetting and wiping cache again, but no luck so far.
All posts related to stuck bootloop in XDA are because of tampering the phone, installing a custom ROM, going back to stock etc. I didn't find a relevant post if this happens while still in stock with never tampered phone. If there is a post like that, please kindly redirect me there. I am left without a clue here with very less experience outside stock stuff.
PLEASE HELP !

cart00nist said:
Short version: Nexus 4 is stuck on bootloop but it's as good as new with the stock ROM and everything.
Long version: My nexus 4 has stock kernel, stock ROM of Lollipop that was updated when google rolled it out few months back. I did have my bootloader unlocked via Nexus Root Toolkit few months back while i still had KitKat, but apart from that, i have NEVER ROOTED, NEVER INSTALLED A CUSTOM RECOVERY, NEVER CHANGED KERNEL, NEVER INSTALLED ANY OTHER CUSTOM ROMs. The only tampering i did was unlock the bootloader and never bothered anything else. But suddenly, my phone got stock on bootloop last night. I powered it off normally, full charged the phone, and when i turned it on, it got stuck ever since. It did happen once when the phone updated to lollipop for the first time, but a simple restart solved it that time. I have tried wiping cache, factory resetting and wiping cache again, but no luck so far.
All posts related to stuck bootloop in XDA are because of tampering the phone, installing a custom ROM, going back to stock etc. I didn't find a relevant post if this happens while still in stock with never tampered phone. If there is a post like that, please kindly redirect me there. I am left without a clue here with very less experience outside stock stuff.
PLEASE HELP !
Click to expand...
Click to collapse
Did it just spontaneously reboot and go into a bootloop? Will it boot into the Bootloader? If so, you might try reflashing the image files directly and see if that fixes it. You can do that using Wug's NRT and selecting the Soft-Brick option under Stock + Unroot.
Hopefully that works. If not, it could be a hardware failure, but exhaust software side fixes first.

ariesgodofwar said:
Did it just spontaneously reboot and go into a bootloop? Will it boot into the Bootloader? If so, you might try reflashing the image files directly and see if that fixes it. You can do that using Wug's NRT and selecting the Soft-Brick option under Stock + Unroot.
Hopefully that works. If not, it could be a hardware failure, but exhaust software side fixes first.
Click to expand...
Click to collapse
No, i turned it off myself. Then charged the battery to 100% and then turned it back on. It got in the bootloop ever since. After u suggested, i downloaded the stock ROM and tried flashing it using Wug's NRT selecting the soft-brick option. Everything went smoothly but I am still stuck with the bootloop. If it's a hardware problem, i'm as good as screwed. There is no LG Service Center in Nepal!

cart00nist said:
No, i turned it off myself. Then charged the battery to 100% and then turned it back on. It got in the bootloop ever since. After u suggested, i downloaded the stock ROM and tried flashing it using Wug's NRT selecting the soft-brick option. Everything went smoothly but I am still stuck with the bootloop. If it's a hardware problem, i'm as good as screwed. There is no LG Service Center in Nepal!
Click to expand...
Click to collapse
How long did you wait after booting it after flashing the stock ROM? It can sometimes take a while to boot the first time.

theminikiller said:
How long did you wait after booting it after flashing the stock ROM? It can sometimes take a while to boot the first time.
Click to expand...
Click to collapse
About 10 minutes.
In another note, I don't have custom recovery or root access. But i found that i can install a custom ROm i.e. cyanogenmod using Nexus Root Toolkit. Will i run to any known problem if i do that?

cart00nist said:
About 10 minutes.
Click to expand...
Click to collapse
I would suggest you try again and wait maybe a little over half an hour to see if it boots then.

theminikiller said:
I would suggest you try again and wait maybe a little over half an hour to see if it boots then.
Click to expand...
Click to collapse
Ok, will try again.
In another note, I don't have custom recovery or root access. But i found that i can install a custom ROm i.e. cyanogenmod using Nexus Root Toolkit. Will i run to any known problem if i do that?

cart00nist said:
Ok, will try again.
In another note, I don't have custom recovery or root access. But i found that i can install a custom ROm i.e. cyanogenmod using Nexus Root Toolkit. Will i run to any known problem if i do that?
Click to expand...
Click to collapse
You shouldn't, just make sure it's for the same android version.

theminikiller said:
You shouldn't, just make sure it's for the same android version.
Click to expand...
Click to collapse
I flashed it again and It's been exactly half an hour but it's still stuck with the same four colorful dots rotating screen. Could it be because of the ROM build? I saw that there is a previous build of the same lollipop 5.1.1 in google's link.. Should i try flashing that instead?

cart00nist said:
I flashed it again and It's been exactly half an hour but it's still stuck with the same four colorful dots rotating screen. Could it be because of the ROM build? I saw that there is a previous build of the same lollipop 5.1.1 in google's link.. Should i try flashing that instead?
Click to expand...
Click to collapse
You could, you could also try flashing a custom recovery and then installing a custom ROM to see if that helps.

theminikiller said:
You could, you could also try flashing a custom recovery and then installing a custom ROM to see if that helps.
Click to expand...
Click to collapse
How do i flash a custom recovery from fastboot mode? Since i cannot go to the homescreen and turn on USB debugging, i cannot root the device. The NRT only has root+custom recovery together in a single button. Since i only need the custom revovery and that also i need to install it by staying in the fastboot mode, how do i do it? This is the only phone i have and i cannot afford another phone anytime soon. Thankyou so so much for helping me

cart00nist said:
How do i flash a custom recovery from fastboot mode? Since i cannot go to the homescreen and turn on USB debugging, i cannot root the device. The NRT only has root+custom recovery together in a single button. Since i only need the custom revovery and that also i need to install it by staying in the fastboot mode, how do i do it? This is the only phone i have and i cannot afford another phone anytime soon. Thankyou so so much for helping me
Click to expand...
Click to collapse
Try following this guide: http://forum.xda-developers.com/showthread.php?t=2018179
Your bootloader is already unlocked so you can ignore that part of the guide. Follow the instructions to install adb and fastboot. Then instead of using adb commands to boot into the bootloader do it by first powering off your phone, then power it on while holding the volume down button.
When you are there follow the instructions to flash a recovery image, but instead of using CWM as is suggested there use TWRP instead from this link: http://forum.xda-developers.com/showthread.php?t=2002326 there will be a link in the post to their webpage where you can download the image file. The reason I recommend TWRP over CWM is that CWM is discontinued and haven't been updated in a while.
Then use the same command as in the guide to flash the recovery image, just use the TWRP image file instead. You can ignore the root part since custom Rom's come pre-rooted. Then to flash a custom ROM follow the guide to boot into recovery. Once there you should be able to copy files from your computer and to your phone.
To then install a custom ROM find a ROM you want to try, some stable ones right now are XenonHD and Chroma. Download the zip file from their thread, download a GApps package. There is usually a link to one in the ROM threads. Then copy those two files to your phone.
Then in recovery choose to do a factory reset. Then choose to install first the ROM zip and then the GApps zip, and then wipe cache. You should then try to boot it up normally.
Let's hope that works, but ask if something is unclear. ☺

theminikiller said:
Try following this guide: http://forum.xda-developers.com/showthread.php?t=2018179
Your bootloader is already unlocked so you can ignore that part of the guide. Follow the instructions to install adb and fastboot. Then instead of using adb commands to boot into the bootloader do it by first powering off your phone, then power it on while holding the volume down button.
When you are there follow the instructions to flash a recovery image, but instead of using CWM as is suggested there use TWRP instead from this link: http://forum.xda-developers.com/showthread.php?t=2002326 there will be a link in the post to their webpage where you can download the image file. The reason I recommend TWRP over CWM is that CWM is discontinued and haven't been updated in a while.
Then use the same command as in the guide to flash the recovery image, just use the TWRP image file instead. You can ignore the root part since custom Rom's come pre-rooted. Then to flash a custom ROM follow the guide to boot into recovery. Once there you should be able to copy files from your computer and to your phone.
To then install a custom ROM find a ROM you want to try, some stable ones right now are XenonHD and Chroma. Download the zip file from their thread, download a GApps package. There is usually a link to one in the ROM threads. Then copy those two files to your phone.
Then in recovery choose to do a factory reset. Then choose to install first the ROM zip and then the GApps zip, and then wipe cache. You should then try to boot it up normally.
Let's hope that works, but ask if something is unclear.
Click to expand...
Click to collapse
Installed TWRP, and then installed XenonHD. Everything went ultra smooth. Again got stuck in the same boot screen. Tried factory reset, doesn't work! I'm screwed!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

cart00nist said:
Installed TWRP, and then installed XenonHD. Everything went ultra smooth. Again got stuck in the same boot screen. Tried factory reset, doesn't work! I'm screwed!
Click to expand...
Click to collapse
I'm afraid that the only suggestion I have left is to try flashing a factory image manually instead of using the toolkit. This is a guide on how to do it: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/

theminikiller said:
I'm afraid that the only suggestion I have left is to try flashing a factory image manually instead of using the toolkit. This is a guide on how to do it: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Click to expand...
Click to collapse
Haha. I was out for a while and my stupid brother flashed a Droid ROM of about 900MB. I don't know what he was thinking. I cannot even scold him because he his my cousin. lol
Now the phone doesn't even turn on. It probably is on because when i connect it to the PC, the new hardware is detected and the driver is also probably installed, because the windows doesn't say the driver installation was failed. But i cannot see anything on the screen. I am about to throw my phone in the trashcan. lol I feel so stupid. Do you have any last suggestion for me?

cart00nist said:
Haha. I was out for a while and my stupid brother flashed a Droid ROM of about 900MB. I don't know what he was thinking. I cannot even scold him because he his my cousin. lol
Now the phone doesn't even turn on. It probably is on because when i connect it to the PC, the new hardware is detected and the driver is also probably installed, because the windows doesn't say the driver installation was failed. But i cannot see anything on the screen. I am about to throw my phone in the trashcan. lol I feel so stupid. Do you have any last suggestion for me?
Click to expand...
Click to collapse
Do you get any feedback if you use the command "fastboot devices"?

theminikiller said:
Do you get any feedback if you use the command "fastboot devices"?
Click to expand...
Click to collapse
Oh rite i forgot to tell you. i did fastboot devices and so far it doesn't show up the serial number of my phone.

cart00nist said:
Oh rite i forgot to tell you. i did fastboot devices and so far it doesn't show up the serial number of my phone.
Click to expand...
Click to collapse
In that case I unfortunately don't have any more ideas, sorry. I wish you luck with your phone tho, maybe some other member here at xda has any other ideas.

How to keep permanent root?

So I have converted my Note for to developer and have an unlocked bootloader and installed TWRP through Odin. I have tried a few times to gain root by installing SuperSU through TWRP, but it just manages to keep looping my phone after it installs. Is there a way to install SuperSU without doing it through TWRP as I think that's the problem?
Also I wouldn't be able to install a ROM until I gain root correct?
Thank you for all of your help

adriel161 said:
So I have converted my Note for to developer and have an unlocked bootloader and installed TWRP through Odin. I have tried a few times to gain root by installing SuperSU through TWRP, but it just manages to keep looping my phone after it installs. Is there a way to install SuperSU without doing it through TWRP as I think that's the problem?
Also I wouldn't be able to install a ROM until I gain root correct?
Thank you for all of your help
Click to expand...
Click to collapse
install a prerooted rom of your choice through twrp recocery.. they will come pre rooted..
if not i have a feeling youre not using the correct supersu zip to root the device..
have you flashed cf auto root?
Sent from my SM-G925V using XDA-Developers mobile app

Flash a prerooted rom or flash the Emotion-TW-5.1.1-nightly-r21 kernal + BETA-SuperSU-v2.71-20160331103524

elliwigy said:
install a prerooted rom of your choice through twrp recocery.. they will come pre rooted..
if not i have a feeling youre not using the correct supersu zip to root the device..
have you flashed cf auto root?
Sent from my SM-G925V using XDA-Developers mobile app
Click to expand...
Click to collapse
So yea.I don't mean to hijack this thread or anything, but I'm having thebsane issue. I've converted to Dev edition, installed TWRP, and am currently running CM 13. However, whenever I try to use an app that requires root, it says that I don't have root.
I've tried flashing the latest Super SU in recovery, downloading Super SU from the play store, and I've tried flashing the Emotion kernel (when i try to flash that, my screen goes black and I'm returned to my recovery home)
What pre rooted ROMs are out?
And are my issues rooting because I flashed a 6.0,1 ROM before getting permanent root?

refusedchaos said:
Flash a prerooted rom or flash the Emotion-TW-5.1.1-nightly-r21 kernal + BETA-SuperSU-v2.71-20160331103524
Click to expand...
Click to collapse
Cool, thanks got it to work!
Now my only issue is that once I was rooted and everything I wanted to flash CM13.
I shut down my phone and went into TWRP, I restored and the tried to install CM13+Gapps and it just went into a black screen and started over. I rebooted, but now I'm in a boot loop.
So I am going to start over and regain root, but do you know if I did something incorrectly? How would I go about it? Thank you.

shusuke028 said:
So yea.I don't mean to hijack this thread or anything, but I'm having thebsane issue. I've converted to Dev edition, installed TWRP, and am currently running CM 13. However, whenever I try to use an app that requires root, it says that I don't have root.
I've tried flashing the latest Super SU in recovery, downloading Super SU from the play store, and I've tried flashing the Emotion kernel (when i try to flash that, my screen goes black and I'm returned to my recovery home)
What pre rooted ROMs are out?
And are my issues rooting because I flashed a 6.0,1 ROM before getting permanent root?
Click to expand...
Click to collapse
Settings-/developer options/ enable root
Sent from my SM-N920F using XDA-Developers mobile app

adriel161 said:
Cool, thanks got it to work!
Now my only issue is that once I was rooted and everything I wanted to flash CM13.
I shut down my phone and went into TWRP, I restored and the tried to install CM13+Gapps and it just went into a black screen and started over. I rebooted, but now I'm in a boot loop.
So I am going to start over and regain root, but do you know if I did something incorrectly? How would I go about it? Thank you.
Click to expand...
Click to collapse
Hmm im not sure (i'm running stock + Emotion kernel). But if you want to go CM13, you dont need to flash the Emotion kernel.
EDIT: you did a full factory reset (via recovery) before you flashed CM13 right?

refusedchaos said:
Hmm im not sure (i'm running stock + Emotion kernel). But if you want to go CM13, you dont need to flash the Emotion kernel.
EDIT: you did a full factory reset (via recovery) before you flashed CM13 right?
Click to expand...
Click to collapse
Yes I did, but I had the Emotion Kernal installed. That's probably why, I'm going to attempt right now to flash SuperSu then CM13.

[/COLOR]
shusuke028 said:
So yea.I don't mean to hijack this thread or anything, but I'm having thebsane issue. I've converted to Dev edition, installed TWRP, and am currently running CM 13. However, whenever I try to use an app that requires root, it says that I don't have root.
I've tried flashing the latest Super SU in recovery, downloading Super SU from the play store, and I've tried flashing the Emotion kernel (when i try to flash that, my screen goes black and I'm returned to my recovery home)
What pre rooted ROMs are out?
And are my issues rooting because I flashed a 6.0,1 ROM before getting permanent root?
Click to expand...
Click to collapse
Cm13 is pre-rooted, root is embedded in the rom, superSu isn't needed, you can turn it on in developer settings.

adriel161 said:
Yes I did, but I had the Emotion Kernal installed. That's probably why, I'm going to attempt right now to flash SuperSu then CM13.
Click to expand...
Click to collapse
Yea, try with stock kernal. I don't think you need to flash SS when flashing CM13 though

For me, when I try to flash CM13 through TWRP it'll get to saying "MTP Enabled" in the terminal window, then black screens for a few seconds, and reboots to TWRP. It also doesn't flash CM13, and I'm at a loss for what to do

Orange Offizier said:
For me, when I try to flash CM13 through TWRP it'll get to saying "MTP" in the terminal window, then black screens for a few seconds, and reboots to TWRP. It also doesn't flash CM13, and I'm at a loss for what to do
Click to expand...
Click to collapse
Which version of TWRP do you have? And did you make sure it was a vzw build?

Reminon said:
Which version of TWRP do you have? And did you make sure it was a vzw build?
Click to expand...
Click to collapse
I have TWRP 3.0.2, and it is a vzw build

moto x pure 6.0 mm ( root )

Tried everything flashing every supersu via twrp and just gets stuck at the moto logo. Tried systemless root and did the same thing. So thinking it was my kernel and flashed elementalx moto kernel ( frankenclark ) then tried to flash supersu once again with the same fail and noticed with that kernel I lost my wifi connection but ran it anyways but failed. After much forum browsing and that supersu just isn't for the MXPE I even went as far as kingroot to achieve root then slap supersu to keep root like I did with my kindle fire. I'm pretty lost for words here. I'm previously running resurection remix and works flawless but I do really like the original setup. Ps tried the stock rooted roms and they was a lil off and kept trying to ota update but failed because my bootloader is unlocked so I had to uninstall it. Just looking to root the original rom so I can keep all the moto apps. Looking forward to hearing the ideas. Thanks in advance.

Wow... So I assume you flashed back to pure stock?
Rooting is not difficult, there is only 2 ways to do it, either flash SuperSU 2.62-3 beta or the latest stable version with the "echo" command for systemless installations. Look at this thread (note the pictures in the OP are of my XT1575, I fudged a little) but the method is identical. If it doesn't work, no offense, but your not doing something right.

I have both pure stock in a restore and resurection remix in a restore which is pretty much my daily because the active display drives me nuts. And supersu 2.6.2 I haven't tried yet but the SR supersu I've flashed via twrp with the stock kernel and ( frankenclark ) kernel and it responded the same stuck at moto. I've flashed it via windroid toolkit also it shows it's installing without any failure but on boot up she says no way. And I've updated the toolkit to it's newest version and still ends up stuck at moto. I'm sure I'll figure it out and get it. And no offense on doing something wrong it's been known to happen. Some lg double tap to wake the screen would be nice over the active display.

fastjohnson said:
I have both pure stock in a restore and resurection remix in a restore which is pretty much my daily because the active display drives me nuts. And supersu 2.6.2 I haven't tried yet but the SR supersu I've flashed via twrp with the stock kernel and ( frankenclark ) kernel and it responded the same stuck at moto. I've flashed it via windroid toolkit also it shows it's installing without any failure but on boot up she says no way. And I've updated the toolkit to it's newest version and still ends up stuck at moto. I'm sure I'll figure it out and get it. And no offense on doing something wrong it's been known to happen. Some lg double tap to wake the screen would be nice over the active display.
Click to expand...
Click to collapse
It sounds like the install script for SuperSU is not doing a systemless install...
So you are flashing stock, booting at least once (this is required), the open TWRP and allow changes to system (In mounts make sure Mount System Read-Only is NOT checked), go to Advanced - Terminal and enter "echo SYSTEMLESS=true>>/data/.supersu" and press enter, then go to Install and select the SuperSU zip file and install it. It should clearly say it is doing a system-less install, patching boot image, etc. as shown in the first post of the link I shared a couple posts previous.

OK I tried this info word for word and tried multiple times and its still gets stuck on the moto logo, I don't get it.

I don't know... it's a puzzler.

2.62-3 and stop using toolkits.

lafester said:
2.62-3 and stop using toolkits.
Click to expand...
Click to collapse
I'm using twrp to obtain the root like specified. But I'll try adb commands and see if the version you mentioned will do it. I appreciate the help.

fastjohnson said:
I'm using twrp to obtain the root like specified. But I'll try adb commands and see if the version you mentioned will do it. I appreciate the help.
Click to expand...
Click to collapse
Well that worked perfectly the first try I used those terminal commands with that version SuperSU it rooted and booted right up like normal and started asking the SuperSU adb shell permission banners. Perfect guys maybe this thread will help some other poor soul to get root. Awesome advice that works. Thank you.

fastjohnson said:
Well that worked perfectly the first try I used those terminal commands with that version SuperSU it rooted and booted right up like normal and started asking the SuperSU adb shell permission banners. Perfect guys maybe this thread will help some other poor soul to get root. Awesome advice that works. Thank you.
Click to expand...
Click to collapse
Yeah, glad it's working... Did you read through the link I posted earlier? The 2.62-3 method was clearly described in the second post under Alternative Methods.

acejavelin said:
Yeah, glad it's working... Did you read through the link I posted earlier? The 2.62-3 method was clearly described in the second post under Alternative Methods.
Click to expand...
Click to collapse
No actually I didn't see it, lol probably would have helped made me not look dumb. Buy who am I kidding you guys love flexing you rooting muscles..

Deleted.