Database Users

[Q] Stuck at "X" Nexus 7 2013

First I have been to and searched every post and site I can find to turn this thing around, with no success. Sent several emails.
Took a rooted New Nexus 7 that had been restored back because it froze/did not respond. Got a new N7, unlocked bootloader and installed TWRP using Terminal (Mac) booted into recovery (TWRP) it said you are not rooted, install SU by swiping below. I swiped and tried to reboot and it stops at X. I have wiped, reinstalled TWRP and used a One Click Toolkit to Root. no success. Not really sure what I did wrong.....given I have always trusted TWRP.
Anyway... have unlocked bootloader, TWRP installed and cannot get Android File Transfer to recognize device. Welcome help or suggestions.
Thank you in advance.
David

Same thing happened to me. Don't listen to TWRP about SU. You'll need to do it manually for it to be successful. Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=2381582. This won't relock your bootloader. You just need to root it by flashing the SU zip found on one if the "How to root" threads.

natezire71 said:
Same thing happened to me. Don't listen to TWRP about SU. You'll need to do it manually for it to be successful. Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=2381582. This won't relock your bootloader. You just need to root it by flashing the SU zip found on one if the "How to root" threads.
Click to expand...
Click to collapse
Yeah, youre correct, you have to manually flash twrp. I would suggest running the utility to make youre device boot again, then make sure you have the LATEST twrp, then reboot and flash COMPATIBLE SU and you should be golden. Im not sure about macs though but you should deff be goin the right way.

Thank you, I used that site the last time I got into trouble. Do you or anyone know of a Mac site that will get me out of this rut. I won't have access to a PC for a few days and am anxious to set this tablet up.
Thank you for response,
David

dschaap said:
Thank you, I used that site the last time I got into trouble. Do you or anyone know of a Mac site that will get me out of this rut. I won't have access to a PC for a few days and am anxious to set this tablet up.
Thank you for response,
David
Click to expand...
Click to collapse
Give this a try: http://forum.xda-developers.com/showthread.php?t=2395003
I don't have a Mac, so I don't know if this will help. Only thing I could find.

dschaap said:
Thank you, I used that site the last time I got into trouble. Do you or anyone know of a Mac site that will get me out of this rut. I won't have access to a PC for a few days and am anxious to set this tablet up.
Thank you for response,
David
Click to expand...
Click to collapse
If you were able to install using a Mac, then you should have no troubles setting things up again. Avoid toolkits if you can, especially during the early days where things are buggy.
If you put your tablet into fastboot though, you can get started by going ahead and running fastboot -w and then flashing the stock recovery images back on. Sure, you won't have root, but I've found that 1) root doesn't take super nicely unless you're already signed into the tablet anyway, and 2) regardless of 1), once your bootloader is unlocked you might as well get set up and then root afterwards.

Mine did the same thing. What I did to fix was:
1. Go into recovery and format data in the wipe menu.
2. Then factory reset.
3. Restart os.
This was posted by decksy post #11 in tutorial for unlock, recovery, and root thread so if it works thank him.
Sent from my Nexus 7 using xda app-developers app

[Q] [q] after 3 hours,..Unlocked bootloader but continious failure in rooting

Hey,
I decided after a couple of months to finally root my Nexus 4. I followed a manual guide, I didn't want to use a toolkit because I'd figure I'd learn it the proper way. Anyhow, If I go to the bootloader it clearly says it's unlocked. As the guide told me I then went into the clockwerk recovery and installed SuperSu 1.89.
I then proceed to restart my Nexus 4 to then be told that by SuperSu that there are no binaries installed and thus has no root access. It has been driving me nuts and I have spend 3 hours troubleshooting with google searches and experimentation because I hate to just make a thread without researching myself first. what am I missing?
Thanks, a lot.

Alibambam said:
Hey,
I decided after a couple of months to finally root my Nexus 4. I followed a manual guide, I didn't want to use a toolkit because I'd figure I'd learn it the proper way. Anyhow, If I go to the bootloader it clearly says it's unlocked. As the guide told me I then went into the clockwerk recovery and installed SuperSu 1.89.
I then proceed to restart my Nexus 4 to then be told that by SuperSu that there are no binaries installed and thus has no root access. It has been driving me nuts and I have spend 3 hours troubleshooting with google searches and experimentation because I hate to just make a thread without researching myself first. what am I missing?
Thanks, a lot.
Click to expand...
Click to collapse
If you flashed the correct Supersu zip, then it should have also installed binaries. Did you install the zip from Chainfire's site?

Try flashing it again. Sometimes it doesn't seem to stick.
Sent from my Nexus 7 using Tapatalk

Towelroot work??

I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk

Used it installed safestrap and when it reboots get the unlock symbol on the boot screen
Sent from my SM-N900V using XDA Premium 4 mobile app

Works fine on my device. For the unlock symbol, download latest SU and updated binaries. That will go away.
Sent from my SM-N900V using Tapatalk

Definitely works for getting root. Rooted, installed SuperSU, Xposed, SafeStrap all successfully. Now struggling to get a rom to work (tried Eclipse & Hyperdrive). Both say they install successfully via SafeStrap and then hangs on boot up. I've seen one other post on the Eclipse thread for the same problem, so it might be something to keep an eye on.

i can verify that this method works. i just installed superuser and it works flawlessly. the only thing is make sure to download the superuser app from here so you have the updated binaries: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip

re
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??

lazygregg said:
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??
Click to expand...
Click to collapse
Rerun towelroot

re
drewcam888 said:
Rerun towelroot
Click to expand...
Click to collapse
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails

lazygregg said:
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails
Click to expand...
Click to collapse
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.

exaltedgod said:
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.
Click to expand...
Click to collapse
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Sent from my SM-N900V using XDA Premium HD app

Dc4479 said:
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Click to expand...
Click to collapse
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:

exaltedgod said:
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:
Click to expand...
Click to collapse
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.

pmt223 said:
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.
Click to expand...
Click to collapse
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!

emtownsend said:
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!
Click to expand...
Click to collapse
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.

pmt223 said:
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.
Click to expand...
Click to collapse
Ah. Got it. Thanks!
* I successfully used SafeStrap to install HyperROM 8 on slot 1 only, so I had to lose my stock ROM, but I'm OK with that.

cnotes2019 said:
I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
i rooted today with towelroot. i have a verizon note 3 on 4.4.2

Towelroot by: geohot

Just letting everyone know that is does work for this device as well. Not sure if it's been mentioned already or not. If so and it's old news, sorry but didn't see anything posted about here although I didn't look very hard either
On the latest 4.4.4 update. So far so good. Did it's thing in less than 5sec's. Root Check was good, Installed SU from the playstore, said something about the SU Binaries or something, rebooted and bam, that msg doesn't show up anymore and all looks to be good.
Thank you geohot!

Bricking and Boot Loops on Nexus 7 2013 WI-FI
Demmonnixx said:
Just letting everyone know that is does work for this device as well. Not sure if it's been mentioned already or not. If so and it's old news, sorry but didn't see anything posted about here although I didn't look very hard either
On the latest 4.4.4 update. So far so good. Did it's thing in less than 5sec's. Root Check was good, Installed SU from the playstore, said something about the SU Binaries or something, rebooted and bam, that msg doesn't show up anymore and all looks to be good.
Thank you geohot!
Click to expand...
Click to collapse
I actually have encountered problems on two separate Nexus 7 2013 editions both in less the a day of using towelroot. One tablet with a custom kernel bricked and the other tablet while rooted with towelroot is without a custom kernel and whenever encountering a force close will reboot itself and boot loop 20-30 times before eventually booting back into Android 4.4.4. I have no definitive 'proof' that towelroot is causing these errors but I find it all a little too coincidental. I hope your device fairs better then mine.

Not sure I see the point of towelroot on a N7, one just has to flash supersu in twrp.
Edit: I guess if you don't have a pc(really? in this day and age?) or don't wanna wipe? Meh, to each their own.

Captain_FSU said:
I actually have encountered problems on two separate Nexus 7 2013 editions both in less the a day of using towelroot. One tablet with a custom kernel bricked and the other tablet while rooted with towelroot is without a custom kernel and whenever encountering a force close will reboot itself and boot loop 20-30 times before eventually booting back into Android 4.4.4. I have no definitive 'proof' that towelroot is causing these errors but I find it all a little too coincidental. I hope your device fairs better then mine.
Click to expand...
Click to collapse
Haven't had a single issue so far. Did the towel root thing and then unlocked the boot loader then flashed clean ROM and this thing has been amazing so far on all aspects. I would start from scratch fresh and clean and see if that helps anything. Good luck but if u can give a step by step on what u did first through the last step and what version of towel root u used I might be able to help

mdamaged said:
Not sure I see the point of towelroot on a N7, one just has to flash supersu in twrp.
Edit: I guess if you don't have a pc(really? in this day and age?) or don't wanna wipe? Meh, to each their own.
Click to expand...
Click to collapse
1. My computer's a desktop and 100+ miles away
2. Don't want to wipe

I tried the latest towel root on Lollipop and it says "This device is not supported"

I think I goofed... bad. Sm-n900v 5.0 stock

Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice

tbonedude said:
Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice
Click to expand...
Click to collapse
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk

donc113 said:
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply, as of edit 3, I am back on OB6, and cannot seem to get root. Are my chances better with OF1?
Ive tried yemen tools (says 5.0 not found)
I've tried kingo root (says successful, never reboots, and shows "this phone root isnt properly setup" when checking with root checker from joey kilm (think thats his name)
Does it matter my emmc ID is ending with 43100?
https://cdn.discordapp.com/attachments/221482708063223809/378367914388094981/image.png <- image from unlock_n3 after success, emmc checker shows same value AFTER odin ob6 (this held, nothing else did)
Edit: After taking donc's recommendation of OF1, I am now able to run yemen tools. As a side note, I seem to have more bars of service with OF1... coincidence?
Edit2: I HAVE ROOT! on OF1 using yemen tools (downgraded from PL1 to OB6 finally to OB1 and it worked.) Now to re-unlock bootloader. Thanks guys for the support thus far, this is a journey and having qualified accomplices makes this SOOOO much easier.

So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:

tbonedude said:
So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:
Click to expand...
Click to collapse
You're welcome. Just an FYI, the ending of the CID doesn't matter, it's the first 2 numbers that count, and they MUST be 15
I used Flashify (available on Google Play) to load TWRP... worked great (but you must have root and busybox installed to use it to flash TWRP)
Sent from my SM-N900V using Tapatalk