Develop Bugs

[Q] Am I bricked?

I'm not sure where to go from here, I rooted my Nexus, installed CWM, and everything was fine. Until my dumbass decided to reboot to recovery from ROM manager, didn't think it would hurt anything. Now, whenever I try to load recovery from my bootloader, the android pops up with the swirling ball for a second, then comes up an android laying down with a red triangle with an ! in it.
I tried factory reset, started from step 1, locked the bootloader and unlocked and rooted again. If I flash CWM, it will work the first time, but anytime after that my little hazardous android symbol pops up again unless I flash CWM again. I'm new to all this obviously, so any help would be very greatly appreciated. Thanks.

I would recommend just flashing a factory .img threw adb. That should do it.
Send, Finally From Lte Galaxy Nexus

I agree. This link helped me do it for mine just a few mins ago.
LTE Instructions:
https://plus.google.com/107538503004482952974/posts/K8wozE8zhzq
GSM Instructions:
http://forum.xda-developers.com/showthread.php?t=1373995

irb123 said:
I'm not sure where to go from here, I rooted my Nexus, installed CWM, and everything was fine. Until my dumbass decided to reboot to recovery from ROM manager, didn't think it would hurt anything. Now, whenever I try to load recovery from my bootloader, the android pops up with the swirling ball for a second, then comes up an android laying down with a red triangle with an ! in it.
I tried factory reset, started from step 1, locked the bootloader and unlocked and rooted again. If I flash CWM, it will work the first time, but anytime after that my little hazardous android symbol pops up again unless I flash CWM again. I'm new to all this obviously, so any help would be very greatly appreciated. Thanks.
Click to expand...
Click to collapse
You're not bricked. Flash CWM and then use Root Explorer or another file browser and navigate to /system and delete reboot-from-recovery.p
You will now be able to boot into recovery.

Awesome thanks for the replies you guys are great. The ordeal ended up causing my phone to reject the sim card for some reason...just got back from Verizon. I'm trying the file manager route first but it's telling the file is read only?
Sent from my Galaxy Nexus using XDA App

Nevermind...hit the r/w...like I said...noob. Checking recovery now thanks again...
Sent from my Galaxy Nexus using XDA App

Andrew C said:
You're not bricked. Flash CWM and then use Root Explorer or another file browser and navigate to /system and delete reboot-from-recovery.p
You will now be able to boot into recovery.
Click to expand...
Click to collapse
What if I don't have the reboot-from-recovery.p file in my /system folder?

ironcx said:
What if I don't have the reboot-from-recovery.p file in my /system folder?
Click to expand...
Click to collapse
Follow the instructions for How to install CWM in this post. Once you've done that, you'll be able to find the reboot-from-recovery.p in /system. Just delete it and you'll be good.

[Q] Big Help Needed - framework-res.apk renamed

Please help. Via advice to remove main google account I renamed framework-res.apk to framework-res.apk.bak. Phone is stuck on white dinc screen. cWm is unresponsive. any help is greatly appreciated. phone is/was rooted droid incredible running 2.3.4 (I believe). Thanks!

Framework res apk is the heart of the operating system. You can't rename it. You will need to boot into recovery and either recover a back up, or flash complete rom. If you can't get into boot loader, you will need to flash factory RUU from bootloader.

reply
I can boot into fast boot/hboot screen with skateboard guys down at bottom, when i try to go into recovery i get to cwm 5.0.2.0 screen menu, but hitting options hangs at the black hat orange ring screen. I can hit power and go back to menu..
I am not sure what the ruu thing is/how it works or where to get it - thoughts?

Check pvillecomp.com for resources. it's got a lot of useful recovery stuff for the incredible. The page you may be interested in is the stock images page where you can flash the gingerbread RUU or froyo RUU. it won't turn S-OFF to S-ON fortunately.

Thanks, will check it out
Thanks! I'll head over there and take a look. as a noob, one of my issues is that none of the cwm menu options works and computer not recognizing phone. hoping this site will help me/teach me how to get files I need to load from computer to phone and loaded by phone. wish me luck
tiny4579 said:
Check pvillecomp.com for resources. it's got a lot of useful recovery stuff for the incredible. The page you may be interested in is the stock images page where you can flash the gingerbread RUU or froyo RUU. it won't turn S-OFF to S-ON fortunately.
Click to expand...
Click to collapse

Back in Biz, but lost root
JCatman said:
Thanks! I'll head over there and take a look. as a noob, one of my issues is that none of the cwm menu options works and computer not recognizing phone. hoping this site will help me/teach me how to get files I need to load from computer to phone and loaded by phone. wish me luck
Click to expand...
Click to collapse
Yeah - reinstalled ruu, now I'm up and running which is a big deal. Looks like I lost root tho, and I'm on 4.06. Am I screwed or is there a root if I'm @4.06? I was at 4.06 with root/s-off before.

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A

JCatman said:
Yeah - reinstalled ruu, now I'm up and running which is a big deal. Looks like I lost root tho, and I'm on 4.06. Am I screwed or is there a root if I'm @4.06? I was at 4.06 with root/s-off before.
Click to expand...
Click to collapse
You should be able to just flash the latest cwm and either a custom ROM with root or an su flashable zip. I recommend the custom ROM as it has busybox. And if you had s-off you'll still have s-off as the ruu doesn't remove root.
Sent from my Galaxy Nexus using Tapatalk 2

Back in Biz, but lost root
tiny4579 said:
You should be able to just flash the latest cwm and either a custom ROM with root or an su flashable zip. I recommend the custom ROM as it has busybox. And if you had s-off you'll still have s-off as the ruu doesn't remove root.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I ran root checker and it said I don't have root permissions. here is where it gets fuzzy for me. what custom ROM is recommended and where do I get it? I gather I would download the file to root of SD and flash in recovery? Thanks again!

Renamed framework-res.apk.dak!! Phone not at all working!!
hey!!
i have a micromax A60!!
Android 2.1 update 1!!
i was trying to delete the google account so i checked a video on the internet which said go to "Root Explorer / system / framework select write only" and after that to rename one file "framework-res.apk to framework-res.apk.bak" Instead of bak i by mistake typed dak!!
and now my phone is stuck its not even starting so that i could restore the factory settings neither i can connect it to the pc..
Even hard reset is not working i can only see the micromax logo thats it!!
what to do plz help!!

Shasha_Daredevil said:
hey!!
i have a micromax A60!!
Android 2.1 update 1!!
i was trying to delete the google account so i checked a video on the internet which said go to "Root Explorer / system / framework select write only" and after that to rename one file "framework-res.apk to framework-res.apk.bak" Instead of bak i by mistake typed dak!!
and now my phone is stuck its not even starting so that i could restore the factory settings neither i can connect it to the pc..
Even hard reset is not working i can only see the micromax logo thats it!!
what to do plz help!!
Click to expand...
Click to collapse
OK, I'll try but this is not really the right forum. I've not heard of this phone before but if you can adb in you can probably fix it. The phone might also have a way of flashing it so it can be reverted to stock. Factory reset won't help here. Is there a way to even get in recovery?
Here's how you'd try to fix it:
1. Download and setup adb on your computer.
2. Open a command window and type adb devices, you should get some device name returned.
3. Then type the following:
Code:
adb shell
busybox mount -o remount,rw /system
cp /system/framework-res.apk.dak /system/framework-res.apk
chmod 644 /system/framework/framework-res.apk
4. Reboot
If step 2 or 3 fails try the micromax forums. I just wanted to try to assist because you searched for the related issue and ended up here. Also, that advice given was bad advice to rename a critical system file.
And OP, were you able to get your root issue fixed? Ice Cream Sense, Stock+ and Touch of Blue are good stock-ish ROMs.

Bootloader Relocks Automaticly

I'm having an issue with my friend's GN,
He suffers from random reboots which automatically restore the phone information to a specific date in the past.
I tried the toolkit, manual root and unlock but no luck.
the bootloader itself relocks itself right after i try the "fastboot reboot-bootloader" command.
I cant flash CWM permanently.
Can this be the recovery partition kicking in? I tried renaming it and I didn't get an error.
I managed to root the device, but then I cant install any programs from the Market, I was trying to get Root Explorer to work to ensure that the recovery is renamed or removed.
Whenever I flash the bootloader to primela03 it goes back primekk15.

Is this a GSM GNex (i9250)?

i9250

To me it sound like you actually never unlocked the bootloader in the first place..
Edit: To be more constructive... I have no idea what "the toolkit" does or how it works.
To unlock your bootloader you boot into it and run "fastboot oem unlock". That's the whole process. I personally don't see the value of a toolkit obscuring that process.
Unlocking your bootloader will cause your phone to factory reset and wipe everything on it. Have you done this? Have your phone asked you to confirm this? Did you click the volume-rockers to "yes" and then confirm with the power-button? And then, did the phone get wiped?
If you cannot answer "yes" to every question asked above, you have not unlocked the bootloader. End of story.

When you boot the phone up there should also be an unlocked lock icon under the Google logo at the bottom of the screen.

This is a wacky situation,
I tried using GNex toolkit 6 (http://forum.xda-developers.com/showthread.php?t=1392310) and it never worked.
"fastboot oem unlock" unlocks the device, but the as soon as I try "fastboot reboot-bootloader" it goes back to it's locked state.
I tried flashing another bootloader right after I unlocked it, but it reverted to the old one after rebooting.

BlindWolf8 said:
When you boot the phone up there should also be an unlocked lock icon under the Google logo at the bottom of the screen.
Click to expand...
Click to collapse
Did that, but as soon as I reboot the lock icon goes away.

aGoGo said:
Did that, but as soon as I reboot the lock icon goes away.
Click to expand...
Click to collapse
Strange

There is a file that will put the stock recovery back when you reboot. I'm not sure what else that file does but maybe that's your problem?
Going from memory, I think the process is unlock via fast boot, flash clockwork recovery, boot into recovery, flash super user, I also removed that recovery file at this stage via adb even though other directions have you do it later with root explorer. And that was it. If you do it the way others wrote it up (using root explorer) you'll have to reflash the recovery again.
Sent from my Galaxy Nexus using Tapatalk 2

DeezNotes said:
There is a file that will put the stock recovery back when you reboot. I'm not sure what else that file does but maybe that's your problem?
Going from memory, I think the process is unlock via fast boot, flash clockwork recovery, boot into recovery, flash super user, I also removed that recovery file at this stage via adb even though other directions have you do it later with root explorer. And that was it. If you do it the way others wrote it up (using root explorer) you'll have to reflash the recovery again.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer, ROM Manager via adb
5- in root explorer I deleted recovery-from-boot.p from /system and it came back then tried "adb shell rm /system/recovery-from-boot.p" and it's gone.
6- Tried downloading CWM from ROM manager and the phone reboots whenever it starts download and goes back to stock
rebooted and the damn thing still living in the past!!! even the recovery file is back!

aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer via adb
5- deleted recovery-from-boot.p from /system
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
You have to go back in and re-apply the recovery. That file "recovery-from-boot.p" is like a "reset" file that puts the stock recovery back during the boot process. I suspect it may be re-locking your bootloader too, but this is just a guess.
After you do step 5, repeat steps 1 and 2.

aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer via adb
5- deleted recovery-from-boot.p from /system
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
When you "Unlock the recovery," do you mean you flash a custom recovery or do you mean you unlock the *bootloader*? It's not the same thing.

aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer, ROM Manager via adb
5- in root explorer I deleted recovery-from-boot.p from /system and it came back then tried "adb shell rm /system/recovery-from-boot.p" and it's gone.
6- Tried downloading CWM from ROM manager and the phone reboots whenever it starts download and goes back to stock
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
O_O
the only thing I can think of is a hardware problem is causing the device to do a hard reset every time you boot.

j.go said:
When you "Unlock the recovery," do you mean you flash a custom recovery or do you mean you unlock the *bootloader*? It's not the same thing.
Click to expand...
Click to collapse
I unlock and then flash or sometimes reboot another boot image.

DeezNotes said:
You have to go back in and re-apply the recovery. That file "recovery-from-boot.p" is like a "reset" file that puts the stock recovery back during the boot process. I suspect it may be re-locking your bootloader too, but this is just a guess.
After you do step 5, repeat steps 1 and 2.
Click to expand...
Click to collapse
Did that, the moment I reboot, everything goes back to normal :s
I'm also unable to wipe from the normal system settings, the phone reboots when we try that.
can it be related to this issue? http://www.galaxynexusforum.com/forum/rescue-squad/4093-data-not-wiping-cant-return-stock-3.html

If you have problems doing data wipe/factory reset, it's quite possible that storage is corrupted/failing. It may be whats causing all the random reboots and reverting to old info. Best to bring to a samsung center and make that warranty claim.

I'm not sure what you're doing wrong... but its something.
You shouldn't have to flash another boot loader. I'm not sure what you would gain from that with the phone being a nexus?
Flashing another recovery is necessary for flashing different roms, kernels, mods, root, etc.
If you are indeed flashing a different boot loader, may i ask why?
Sent from my Galaxy Nexus using Tapatalk 2

Don't just delete the file recovery-from-boot.p, as there's one more file that can do bad things. It's called "install-recovery.sh" and is to be found within /system/etc

Theshawty said:
Don't just delete the file recovery-from-boot.p, as there's one more file that can do bad things. It's called "install-recovery.sh" and is to be found within /system/etc
Click to expand...
Click to collapse
Actually, don't delete either file.
Don't touch recovery-from-boot.p at all, and rename the sh.
If you want to be able to install otas in the future, renaming the patch file will break the MD5 check. The file is harmless if the sh file is out of commission.

DeezNotes said:
I'm not sure what you're doing wrong... but its something.
You shouldn't have to flash another boot loader. I'm not sure what you would gain from that with the phone being a nexus?
Flashing another recovery is necessary for flashing different roms, kernels, mods, root, etc.
If you are indeed flashing a different boot loader, may i ask why?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm trying another loader because nothing else works, the phone is stock and running 4.0.2. auto update causes it to crash and reboot.

cant go into recovery mode with custom rom

i ve recently rooted my phone, it was on 4.0.2; everything works perfectly fine.
i just wanted to try jelly bean and when i tried to install it, after selecting whether to erase cache and backing up, phone rebooted and when it opened up i got this screen with a droid laying down on the ground with an exclamation mark on it.
whenever i try to restore my phone with clockwork or galaxy nexus root toolkit, i get stuck on that screen.
if i plug the battery out and start my phone, it openes up without any problems.
what did i do wrong?

kallshak said:
i ve recently rooted my phone, it was on 4.0.2; everything works perfectly fine.
i just wanted to try jelly bean and when i tried to install it, after selecting whether to erase cache and backing up, phone rebooted and when it opened up i got this screen with a droid laying down on the ground with an exclamation mark on it.
whenever i try to restore my phone with clockwork or galaxy nexus root toolkit, i get stuck on that screen.
if i plug the battery out and start my phone, it openes up without any problems.
what did i do wrong?
Click to expand...
Click to collapse
similar problem even i had but in my case when the screen with android excamn mark use to come it had some thing to do with enable/ disable when i press power button it use to show to cwm screen and last two line says recovery mode disabled etc and if i wait it says its enables after it says enables button use to work just try that not very sure in your case myte work

actually i couldn't fully understand what you meant

no one knows anything about this problem?

Using Root explorer, go into system/ and after you do Mount R/W, rename the file recover-from-boot.p to recover-from-boot.p.bak or delete it.
Then go into Rom Manager and Flash CMR and reboot into recovery.
From then on, you will never see that red triangle again when you boot into recovery, neither do you have to flash CMR everytime you have to boot into recovery.
Hope this helped.

rename (or delete) this file: /system/etc/install-recovery.sh.
This will prevent the ROM from overwriting CWM with the stock recovery. If you want to have the stock recovery so that future updates will install automatically, leave the ROM as is.

brealorg said:
rename (or delete) this file: /system/etc/install-recovery.sh.
This will prevent the ROM from overwriting CWM with the stock recovery. If you want to have the stock recovery so that future updates will install automatically, leave the ROM as is.
Click to expand...
Click to collapse
so if i rename or delete this file, in future i cant get stock updates then?

kallshak said:
so if i rename or delete this file, in future i cant get stock updates then?
Click to expand...
Click to collapse
considering you're wanting to overwrite the stock recovery with CWM, you wouldnt anyways.

another question, is this action reversible?
i mean, if i ever want to bring my phone back to unrooted and stock state?
i ve tried to look it up with search but couldnt find the answer

you didnt search very hard then.
http://forum.xda-developers.com/showthread.php?t=1626895

might've missed some key words on search. thx for your help

[Q] Restore TWRP nandroid from PC

I'm a newbie and I am in trouble. I have a rooted Nexus 7 2013 and I have a TWRP Nandroid backup which I had copied to my WIndows PC.
Now my Nexus 7 crashed and won't go beyond the X on bootup. The Nandroid and Titanium backups are on my windows PC.
How do I restore the Nexus 7 to working status by restoring from the Nandroid backup and data I have copied to the PC?
Please help. Thanks.

Guys, someone please help.
I don't know how to get out of this mess. I'm still stuck on X.
I can power off the Nexus 7 and power to the recovery screen where I find Teamwin's menu.
I restored (several times) the nandroid backups I found on this menu (they were all done after the last reset) but rebooting then just gets me back to the X screen and no further.
I have a good nandroid backup on my PC but no way to get it into the tablet so TWRP can restore from it. Is there a way to transfer a file to or from the tablet when it will not boot completely?
The advanced screen of the Teamwin recovery menu lets me access a file manager. Is there any way I can use it to move files on or off the tablet to "anything" else?
The last time the boot froze on the X screen, I was able to go to the recovery screen with the android on his back and an X and from there to a reset. But this time I cannot get there and the recovery screen gets me to the Teamwin recovery menu. This has a wipe option. Will this reset the Nexus if selected. Will it remove root? I don't want to go through rooting it all over again.
Essentially I just want to do 2 things:
a) extract data from the stuck Nexus 7
b) reset and restore the nandroid backup I have on my pc.
Please help.......

Bill235 said:
Guys, someone please help.
I don't know how to get out of this mess. I'm still stuck on X.
I can power off the Nexus 7 and power to the recovery screen where I find Teamwin's menu.
I restored (several times) the nandroid backups I found on this menu (they were all done after the last reset) but rebooting then just gets me back to the X screen and no further.
I have a good nandroid backup on my PC but no way to get it into the tablet so TWRP can restore from it. Is there a way to transfer a file to or from the tablet when it will not boot completely?
The advanced screen of the Teamwin recovery menu lets me access a file manager. Is there any way I can use it to move files on or off the tablet to "anything" else?
The last time the boot froze on the X screen, I was able to go to the recovery screen with the android on his back and an X and from there to a reset. But this time I cannot get there and the recovery screen gets me to the Teamwin recovery menu. This has a wipe option. Will this reset the Nexus if selected. Will it remove root? I don't want to go through rooting it all over again.
Essentially I just want to do 2 things:
a) extract data from the stuck Nexus 7
b) reset and restore the nandroid backup I have on my pc.
Please help.......
Click to expand...
Click to collapse
Just choose the wipe option in twrp.
That should allow you to start android.
Then copy your backup from PC to virtual sdcard, reboot to twrp, and restore.
You can copy files while in recovery but it is more involved so I would try this first.

sfhub said:
Just choose the wipe option in twrp.
That should allow you to start android.
Then copy your backup from PC to virtual sdcard, reboot to twrp, and restore.
You can copy files while in recovery but it is more involved so I would try this first.
Click to expand...
Click to collapse
But will it remove the root I worked so hard to get?

If you worked hard to get root on a Nexus device you did something wrong. It should be as simple as unlocking the bootloader (already done), flashing a custom recovery (already done), and flashing the SuperSU ZIP file (this is the only step you'd need to repeat).
That said, doing a factory reset should not remove root. Even if it does, it would be restored when you restored your rooted Nandroid.

raptir said:
If you worked hard to get root on a Nexus device you did something wrong. It should be as simple as unlocking the bootloader (already done), flashing a custom recovery (already done), and flashing the SuperSU ZIP file (this is the only step you'd need to repeat).
That said, doing a factory reset should not remove root. Even if it does, it would be restored when you restored your rooted Nandroid.
Click to expand...
Click to collapse
Easy for an expert. I'm a newbie. I used the WUGfresh toolkit and it took multiple frustratng attempts and forever for it to finally download the correct adb drivers that would recognize the Nexus 7. Then all went smoothly.
But back to the present. I'm all fine now (till the next time the Nexus 7 crashes on me). For other newbies like me who run into this problem and need simple instructions here is what I did.
The first time this crash with the boot stuck on the X screen happened, going to the recovery screen (Power button + Volume up simultaneously) showed me the android on his back with a red triangle. Pressing power button and briefly volume up gave me the option to reset the tablet without removing root. Because I was traveling and did not have my TWRP backups with me (they were on my laptop 1,000 miles away) this removed all my data and I had to re-install all my apps and everything again.
The second time this happened, the recovery screen took me to the TWRP recovery screen. TWRP recovery had apparently survived the crash. I needed to save my data before reseting the tablet again. By trial and error I discovered that the TWRP menu has under the Advanced Tab a file manager. also discovered that if you connect a flash device to the tablet's usb port the TWRP file manager could read and write to it (!!!) in a folder called usb-otg (but not to my windows laptop). I copied what I wanted to save to the flash drive. Then I used the "wipe" tool to return the tablet to android.
I installed a free app, Recovery Manager, to reinstall TWRP recovery. Copied my previous TWRP nandroid backup to the tablet and restored everything as it was.
Easy as pie if you know how. I hope this helps some other befuddled user.
sfhub and raptir: Do you know what can be done to prevent this from happening again? Could Google Play being conected to in Europe after it was used to being to conected to in the US cause the problem? Both times the crashes happened shortly after I used the tablet in Europe and the the second time after I used it for the first time in the US.

Bill235 said:
sfhub and raptir: Do you know what can be done to prevent this from happening again? Could Google Play being conected to in Europe after it was used to being to conected to in the US cause the problem? Both times the crashes happened shortly after I used the tablet in Europe and the the second time after I used it for the first time in the US.
Click to expand...
Click to collapse
I can't say for sure what is happening in your case, but in my experience getting stuck on X means your user data got corrupted. The cases I've seen fall into 2 categories:
1) faulty EMMC flash memory. Sometimes if you wipe a couple of times the bad blocks get locked out and you don't see the problem anymore. Other times, they keep coming back. In the latter case, return/exchange/rma the unit
2) android crashes (random reboot) and unfinished writes are not completed corrupting the user data. They put in code in the latest ROM to mitigate this so if you think you are suffering from this type of corruption, install the latest ROM if you haven't done so already.

Thank you for the excellent and clear reply. I'll hope the 2 wipes I did may have gotten rid of my bad blocks.
I'll update to the latest stock rom too.
Thank you.

Bill235 said:
Thank you for the excellent and clear reply. I'll hope the 2 wipes I did may have gotten rid of my bad blocks.
I'll update to the latest stock rom too.
Thank you.
Click to expand...
Click to collapse
The updating part got me in trouble.......
I accepted the system update and am now running android 4.3 but lost root.
So I went back to the WUGfresh Nexus Root kit. Updated everything, am now on version 1.7.3 of the toolkit, followed all the instructions (uninstalled and re-installed driveers) and got stuck on the same problem I had the first time I tried rooting: the adb : step3 of the full driver test. adb device not found .
I did reboot twice, am using the oem asus cable, etc. What a pain!!
Unfortunately I am dependant on the toolkit because I do not know enough to root manually.
Suggestions? Thanks.

Bill235 said:
The updating part got me in trouble.......
I accepted the system update and am now running android 4.3 but lost root.
So I went back to the WUGfresh Nexus Root kit. Updated everything, am now on version 1.7.3 of the toolkit, followed all the instructions (uninstalled and re-installed driveers) and got stuck on the same problem I had the first time I tried rooting: the adb : step3 of the full driver test. adb device not found .
I did reboot twice, am using the oem asus cable, etc. What a pain!!
Unfortunately I am dependant on the toolkit because I do not know enough to root manually.
Suggestions? Thanks.
Click to expand...
Click to collapse
So you're stock 4.3 now? Rooting manually isn't hard bud, setting up the toolkit is harder IMO.
You just need to download and install the Android SDK. Then download a custom recovery .img file, and a SuperSU flashable zip. Put the SuperSu flashable zip on your /sdcard. You'll then boot into the bootloader, open a command prompt and change directories to your Android SDK (Ex. mine is at C:\sdk\platform-tools) and run the command: fastboot flash <name of recovery file>.img
Then reboot into recovery, flash the SuperSU zip, reboot, done. You're rooted. There are plenty of How To's stickied in the General Forums for the N7 here.

RMarkwald said:
So you're stock 4.3 now? Rooting manually isn't hard bud, setting up the toolkit is harder IMO.
You just need to download and install the Android SDK. Then download a custom recovery .img file, and a SuperSU flashable zip. Put the SuperSu flashable zip on your /sdcard. You'll then boot into the bootloader, open a command prompt and change directories to your Android SDK (Ex. mine is at C:\sdk\platform-tools) and run the command: fastboot flash <name of recovery file>.img
Then reboot into recovery, flash the SuperSU zip, reboot, done. You're rooted. There are plenty of How To's stickied in the General Forums for the N7 here.
Click to expand...
Click to collapse
Will look into your suggestions later because I am rooted again. It was the adb drivers again. The universal ones just would not work for me. The Samsung signed drivers on the other hand worked smoothly and then the toolkit ran smoothly and I am rooted. But it wiped out my TWRP recovery so I will re-install that next.
Thanks for the help.
About your advice, than you. But as a newbie I need clearer instructions. "download and install the Android SDK". Where? to the pc or the tablet? etc.
I need to learn more so I don't keep getting into these ridiculous binds!

Bill235 said:
Will look into your suggestions later because I am rooted again. It was the adb drivers again. The universal ones just would not work for me. The Samsung signed drivers on the other hand worked smoothly and then the toolkit ran smoothly and I am rooted. But it wiped out my TWRP recovery so I will re-install that next.
Thanks for the help.
About your advice, than you. But as a newbie I need clearer instructions. "download and install the Android SDK". Where? to the pc or the tablet? etc.
I need to learn more so I don't keep getting into these ridiculous binds!
Click to expand...
Click to collapse
Review the General forum for the N7 2013 here, as there are threads stickied to the top of that forum which has write-ups and video how to's that'll explain it all. I suggest to review those FIRST before you try doing things just so you can get a picture of what's going on. It may seem like a lot, but once you do it, it really is not.
The Android SDK is installed on your computer.