yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] rodem77:
Hi Wugfresh, I repost here my situation, at the moment I've unloked my Nexus S with your tool but I can't root. Thankyou in advance. If you need I can give you more information or do some test to better understand where the problem is.

Thanyou

Hi, thankyou for your work, I'm trying to root my Nexus S i9023 with android 4.1.1 (stock OTA update) with your tool. I've installed driver and unlocked my device, I activated USB debug again but later when I click on "root" button, my phone reboot into temporary TWRP, your tool display "waiting for your device to finish booting back up" and nothing else happens. I can manually use TWRP and I can reboot my device but I can't find any SU application. I've also tried to install it manually from market to be sure that I'm not rooted and the application said me that I've no SU privileges. What I can try to solve this problem?

When I'm in temporary TWRP, in terminal commands I can read this:

finding update package...

opening update package...

E: can't open /sdcard/!readytoflash/root_files_cw

(no such file or directory)

verify filesystem

verify partition size

E: error installing zip file /sdcard/!readytoflash/root_files_cw

I tested option 1, 2 and 3 for driver installation (all with success in final driver installation test) and tested the tool on 2 different PC one with win 7 64 bit and one with win 7 32 bit with the same final result.

I readed also this post: http://xdaforums.com/show....php?t=1007782

with these indications:

1 - Download Android SDK

2 - Unzip & launch "SDK Manager.exe"

3 - Cancel the first popup & go to "Available packages" > "Third party Add-ons" > "Google Inc."

4 - Select "Google USB Driver package" & click "Install Selected"

5 - Once you're finished go to your SDK installation "extras\google\usb_driver" dir

6 - (MOD EDIT: Ignore this step for i9020A models) Open "android_winusb.inf" and add the following lines to both "[Google.NTx86]" and "[Google.NTamd64]" sections :

;

;Google Nexus S GT-i9023

%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20

I've tried to add these two lines in the file that I found in your driver tool folder (but maybe that I made some mistake) and i've tried to install again the driver with option 3 but all stop in temporary TWRP like before. At the moment I've no more ideas...

New Information: Reading an Italian forum I found another person with my phone model (nexus s 9023) and with my same issue. To solve, he manually copied superSU in his telephon internal memory and later used temporary TWRP to flash superSU. In the next days I will try this solution but if you have some ideas or if you need more information about my issue please let me know.

Thankyou
[Nexus 7 Android Development] oliwatts:
Hi WugFresh

Thanks for your advice. :highfive: After a bit more tinkering I discovered the unit had a changing problem, something to do with the USB connector. The N7 charged over USB but mains power using the ASUS adapter didn't work. Other mains adapters also failed. :eek:

First such issue i've seen and the first fault unit taken back to CarPhoneWarehouse. So a replacement unit is on its way :o (Good show CarPhoneWarehouse, surprisingly helpful service). I don't believe I plugged anything I shouldn't in to the N7 so a genuine mystery.

Hopefully i won't bother you again :)
[Nexus 7 Android Development] arkhan11:
Follow the guide for the Nexus 7 in my signature. :)

---------- Post added at 10:05 AM ---------- Previous post was at 09:57 AM ----------

It seems everything looks ok. You should receive the update. If you didn't get it could be because of previous custom ROM you've installed. If you can't get the update (any reason) flash any aosp rom, it's like have pure android updated before any Google ota.
[Nexus 7 Android Development] guih:
Sorry if this is a dumb question, but do we really need to uninstall all previous drives in order to root? I ask cause it would be a bit annoying to have to install past drivers again after rooting.
[Nexus 7 Android Development] rodem77:
No you don't need, its only a precaution to avoid problem during the process, follow the driver guide make you sure to have your phone/tablet correctly installed on your PC. If you want you can skip the driver installation and just follow the step 3 of driver procedure and click on "full driver test" to check if the toolkit can correctly see your phone/tablet. If not, follow the complete installation guide is the best solution.
[Nexus 7 Android Development] guih:
Awesome thanks dude!

Sent from my LTEVO
[Nexus 7 Android Development] vimesUK:
Thanks for this toolkit. I have just bought a C9O version tablet and unlocked and rooted, with custom recovery in a few minutes. All done and working fine :)

I have just donated $5 to you - sorry it isn't much, but I do not have much either.!
[Nexus 7 Android Development] gulo101:
Hi

I installed Root Toolkit 1.5.3 today to get my nexus 7 tablet rooted. I did the backup first, then unlocked and rooted my tablet.

The problem is that I am unable to restore it now. Every time it gets to com.disney.WMW (I believe it's the game Where's my water) it gets stuck for a while and then quits with message "restore ended"

Unfortunately this is one of the first few programs in the restore file so vast majority of my programs are NOT restored. I tried multiple time and it always dies at the same spot.

Any ideas?

thanks
[Nexus 7 Android Development] WugFresh:
I am not sure what the best course of action would be in your circumstance as I am not aware of a method for unpacking those ab files. Maybe try downloading that "Where's my water" app first, running it once, rebooting, airplane mode.. and then try again. This is just a troubleshooting idea... not sure why it would work.. but maybe having the app already on there would get you past that hurdle.

{{ WugFresh }}
[Nexus 7 Android Development] a1exus:
mbp:nakasi-jro03d alexus$ fastboot devices
mbp:nakasi-jro03d alexus$

my options are:

* Start -> Booting failed

* Restart bootloader -> restarts bootloader and I'm back where I started it

* Recovery mode - nothing happens

any ideas please?
[Nexus 7 Android Development] gulo101:
yeah, I tried that too, same thing. it always stops at the same spot, wish there was some way to skip that app
[Nexus 7 Android Development] Pariah3000:
I can finally post my thanks (stupid post minimums).

This tool kit has been indispensable. I used it to root my Nexus 7 and a couple times to recover it after a bit of failed shenanigans. Thank you for all the hard work WugFresh!
[Nexus 7 Android Development] Doritos Bandito:
Verizon finally pushed the official jelly bean update through JRO03O but that one isn't listed as one of the choices. So which one would be alright to choose?
[Nexus 7 Android Development] WugFresh:
I noticed that last night. I am working on v1.5.4 with that for sometime next week. For now choose "Any Build" in the pull down. By next week the toolkit should have official support as well as some other small fixes.

I also have an interesting plan for v1.6 that in theory should make the toolkit support all android devices with unlockable bootloaders that can utilize fastboot, without me updating the toolkit per device. :) I hope I can make my idea into a reality.. some of it is already coded at this stage. Stay tuned.

{{ WugFresh }}
[Nexus 7 Android Development] landstander:
The latest update to Titanium Backup, released just yesterday, can supposedly restore items from ADB backups... including encrypted backups. I believe that you need to purchase the Titanium Backup Pro Key, however, in order to enable this feature.

Disclaimer: Both of my Nexus devices have been rooted for quite some time, so I haven't had any need to test this new capability personally.
[Nexus 7 Android Development] WugFresh:
Sweet. Thanks for the info. I actually have TitaniumBackupPro, it's a great app. I will try it out next time I get a chance.

{{ WugFresh }}
[Nexus 7 Android Development] MeOminG:
As I never posted anything before on XDA, I have to thank you this way.

THANKS!
[Nexus 7 Android Development] emylia777:
hi WugFresh, 1st of all, thanks for the nice and simplest toolkit for us to root our beloved N7.

But I'd like to report the low success rate in rooting the JRO03S build. It made the N7 randomly stucked in bootloader mode. This was done on a successfully-installed PDAnet driver and 'Any Build' was chosen on the toolkit. Just want you to know, perhaps there's another workaround for this.

I, on the other hand, however managed to get my JRO03S build rooted with ur toolkit despite it being few times stucked in bootloader. Changing the USB ports did the trick. It's weird I know but that did the trick. Perhaps this info would let you improve this great toolkit in your future versions. :victory:
[Nexus 7 Android Development] arkhan11:
my N7 is a C90 model and came with JRO03S out of the box. I did not used the manual root guide (because of some issues in sdk setup) neither the easy tool from WugFresh. I merged both solutions using the tool to install driver, then continuing with the manual guide which is the same for any Android release. I wrote a pdf you can download from my signature.

The reason it stucks on bootloader during the procedure is a bug in the N7 bootloader. More details in the pdf.

Thanks to WugFresh for the tool :)
[Nexus 7 Android Development] raywaldo:
USB 3.0 ports

If you were using a USB 3.0 port, that may have been the problem.

I have experienced several issues with some devices linking via any of the 3.0 ports on my laptop. The same devices work great with my (ONLY) 2.0 port.
[Nexus 7 Android Development] arkhan11:
That's REALLY interesting. It could be the cause. I don't have any usb 3.0 port on my computers.

The reason could be in usb 3.0 standard specification. I'll do some searching. If I have new, I'll post here :)
[Nexus 7 Android Development] old_fart:
.

Its never good to make 'broad' statements. Maybe it would be important to talk about a specific brand or the 'chipset' used. . More data plz, Ray.

.

The ccleaner folks, Piriform have a nice tool, speccy.
[Nexus 7 Android Development] raywaldo:
generalized statements

You are correct about the need for more specific data. However, the occasions when it happened, I was more focused on fixing the issue than with recording the data so I did not keep good notes. Remember, I am a couple years older than you - and probably more forgetful.:D

However, I believe that it is better to mention the POSSIBILITY (note that I did not make any definite statements) of the problem than it is to ignore the possibility. Now, others may also be observant of the possible issues and someone (like arkhan11 above) may discover whether it really is an issue.

Who knows, maybe a noob with a problem may try changing ports and fix their problem! :cool:
[Nexus 7 Android Development] SharpIS03:
This toolkit rocks! Really easy to follow with the popups, really quick too! I ordered my Nexus 7 in Japan, C90 with build JRO03S. Used the "Any Build" option. Thanks a lot!
[Nexus 7 Android Development] arkhan11:
Ok, as I promised here's what I found.

debug was a specific made for serial ports and, as USB is a serial port. it works on ANY usb 2.0 port.

it seems you cannot use this feature in 3.0 ports if your pc has at least one USB 2.0 port (it means not native usb 3.0 controller). It could be related to the need of speed increasing within the 3.0 standard. IIRC, it was difficult to make the usb 3.0 standard retro-compatible with 2.0.

I've also found that "Debugging over a USB 3.0 connection requires the following hardware:

A USB 3.0 debug cable. This is an A-A crossover cable that has only the USB 3.0 lines and no Vbus.

USB 3.0 host controllers on the host and target computers."

(as written here http://social.msdn.microsoft.com/Forums/en-US/wdk/thread/74a03abb-ef5f-4e2a-8f27-e2282d56a986)

and that windows 7 CANNOT debug over usb 3.0 ports, that feature will be added in windows 8, as written here (http://msdn.microsoft.com/en-us/library/windows/hardware/ff551063(v=vs.85).aspx):

"New for Windows 8

We have added support for debugging over a network connection or a USB 3.0 connection"

Anyway it depends ALSO on the controller (www.ti.com/analog/docs/microsite.tsp?sectionId=590&tabId=2276&micrositeId=11)

So, let's summarize:

1) you need debug support on your usb 3.0 controller (if your PC has at least one 2.0 port, connect it there. it won't work on 3.0 ones)

2) there are no PCs with only usb 3.0 ports (neither ultrabooks) so where's the problem?

3) if you like windows, you have to wait windows 8 as windows 7 doesn't support debug over usb 3.0 as above (again use 2.0 ports, it's not bad!)

3) if you like linux... don't know! I love Linux but let's talk about it when there'll be only 3.0 ports around

4) if you got the latest macbook air/pro/retina, it's another story (2012 released have only 3.0 ports)

:)

Sorry if it is not a full-detailed explanation but I'm not an electronic engineering. Anyway, it gives us an idea why in described scenarios it does not work.

sources

http://stackoverflow.com/questions/9663719/usb-debugging-on-galaxy-nexus-causes-windows-7-to-freeze

http://pete.akeo.ie/2011/08/do-necrenesas-upd720200-based-usb-30.html

http://www.coreboot.org/EHCI_Debug_Port#Finding_the_USB_debug_port

http://www.google.it/url?sa=t&rct=j...sg=AFQjCNHFwNGEy8a58wmB5xAqhRnKPcB97A&cad=rja

http://channel9.msdn.com/Events/BUILD/BUILD2011/HW-258P
[Nexus 7 Android Development] raywaldo:
USB 3.0 ports

-------------------------------------------

​

---------------------------

That is some VERY IMPRESSIVE researching!! Thank you!!! :highfive:

----------------------------------------------------------------------

​
[Nexus 7 Android Development] arkhan11:
I hope it will be useful for other people now I sorted it out.

If you think it's good, feel free to share the link to this post when it's necessary :)
[Nexus 7 Android Development] raywaldo:
I posted a link on my website http://raywaldo.com
[Nexus 7 Android Development] arkhan11:
:)

Nice website, nice articles.
[Nexus 7 Android Development] demandarin:
need help with nagging issue trying to revert back to stock.

Do you know of a solution was ever found to people getting stuck in various places trying to revert back to stock? I have a 2nd nexus 7 that got borked ssomehow trying to revert back to stock. I can bring up bootloader/fastboot screen. When I run the flash stock/unroot and can't boot up option, it runs. It'll seem to do everything right initially. Then towards the end it'll get stuck on sending boot.img or system img. IVE tried basically everything. Uninstalled drivers, re-installed them, different cables, different PC ports, different toolkits, etc.. I even tried manual method through ADB. No matter which method I try, they all get stuck on same part. Its crazy how it'll go fine for majority of process then get stuck. There are several others who had exact same issue. I know I had proper drivers installed. Also have the Android SDK with all platform tools installed. I was especially disappointed when even manual adb method got stuck on same part. I heard some people got it to work by using another computer bit that's not an option for me atm as i don't have another PC. Any insight as to what may be happening? I know, at least Initially, adb commands being pushed are working. As it'll reboot tablet or show signature match on top of nexus screen. But whenever it gets down to end topart where its sending extracted files(tTHST program extracts itself) it gets stuck on various portions. I know they say sending system.img can take a while but mines gets stuck. Never finishes no matter how long I leave it. Things like flashing stock recovery and stuff work as the nexus 7 takes it.

I must have a really bad soft brick..lol my only hope it seems is THST as least bootloader screen shows and my nexus 7 intiallu takes commands.

One other quick question. I eventually got frustrated with it and relocked it with adb command. Another piece of evidence showing adb and drivers working correctly. I was going to send it in to Google but haven't yet. Since my tablet is in the state its in(stuck on google screen. Never boots up. Likely do to previous wiping trying to revert back to stock with vsrious tools), could I use your tool to unlock it again(would it work)? Or what adb command do I type to unlock my nexus 7 again?I know how to use ADB bit don't know/memorized all the various commands yet. I need it unlocked to try to revert back to stock again,correct? im ready to give it another shot at trying to solve this problem. I gave up for a few weeks..lol
[Nexus 7 Android Development] WugFresh:
Manually boot your device into bootloader mode by holding down both volume buttons and the power button to boot up. Use the toolkits advanced utilities "Launch CMD Prompt" button, then type the following cmd:

fastboot oem unlock

That will prompt you with the standard unlock screen, use the power button to select "Yes", this will wipe your device (factory reset) and boot up (or not, depending on how screwed up your device is).

Then re-flash stock again using the "can't boot up" option in the toolkit. Try letting the toolkit automatically download it instead this time, if you tried that already, then try re-downloading the factory image yourself from google.

As an alternate solution, you can also use the advance utilities "Flash to partition" buttons, and individually flash the system.img and boot.img to their corresponding partitions (i.e system img to System, boot.img to Boot). Those individual img files are contained within the factory image package. The toolkit automatically extracts it and flashes those.. but you could easily extract the package yourself with a program like 7zip and then flash those img files individually. Good luck, let me know how it works out for you.

{{ WugFresh }}
[Nexus 7 Android Development] demandarin:
Appreciate it. I will likely try this out this weekend. Ill make sure to let you know how it goes. Thanks!
[Nexus 7 Android Development] ZuperMario:
Model Type ??

Hello,

my nexus is JB4.1.1 - "I9250XXLF1" - kernel "3.0.31-g6fb96c9" - build "JRO03C"

I dont understand what type of device i have to choose starting Nexus Root Toolkit software.... can you help me? Thanks

---------- Post added at 09:48 PM ---------- Previous post was at 09:29 PM ----------

yakju maguro 4.1.1 thanks :)
[Nexus 7 Android Development] Gigabitex2:
If your device isn't listed I think you just choose "any device" in the list.
[Nexus 7 Android Development] demandarin:
Well I unlocked with command. Then I ran your tool again like you said. It got stuck on sending recovery. So I tried your advanced utilities flash to partition. I extracted all needed files from stock and used the bootloader grouper you already had in there(or may have been from me).

-Flashed boot.img to boot. Said flashing then it rebooted my device.

-manually put it in fastboot mode then flashed bootloader-grouper.img to bootloader. Said flashing then rebooted my device. My device said signature match on the screen.

-put it in fastboot mode again and flashed recovery.img to recovery partition. Said flashing then rebooted device.

-fastboot again. Then flashed system.img to system. Said Flashing system img and has been on that same part for about last 20mins. Or so. I'm just leaving it like that to see if maybe my computer so slow its taking an extremely long time to flash that part. I never made it to the last step of flashing userdata.img to userdata partition.

I flashed each partition in order how it is in your tool. Top to bottom. Or is there a particular order in which I should've done it. I'm puzzled as to why fastboot commands and flashing certain parts work but gets stuck especially on system.img. when I unlocked it again it did say various parts were wiped.

Since other parts except for system.img flashed, I will likely stop it. Then flash userdata.img. then try system.img again. I shouldn't have to reflash other partitions since it "LOOKED" like my nexus 7 took those flashes.

Any other ideas?

Update: since it was hanging on flashing system.img for over 20mins., I stopped it. Then I reflashed each partition over again except this time I left flashing system.img for last. It took boot, bootloader, recovery, and userdata(which is next biggest file,101mb or so, after System.img.) it flashed userdata.img partition pretty fast. Now I'm trying to flash system.img again. So far 3mins. And still onflashing system.img. iI will leave it for a while and cross my fingers it takes it. Now 5mins. On system.img..lol. I'm determined to get this nexus 7 running again ;)
[Nexus 7 Android Development] WugFresh:
Anyway you could access another computer? Regarding the order, it shouldn't matter. Top to bottom is how I would have done it. For whatever reason the system.img doesn't seem to flashing successfully for you. I am not entirely sure why. I would try another computer. If that doesn't work, maybe try setting up a linux machine, with Ubuntu or something and use the linux sdk fastboot. If you need help setting up a Linux machine or doing it manually, I would be happy to help you or point you to some good resources.

{{ WugFresh }}
[Nexus 7 Android Development] demandarin:
I updated that post. Its still hanging on system.img again for last 12-13mins. Or so. I will stop it. Then unplug my device and cable. Then ill reconnect and try to flash system.img off the bat. Maybe even another port.

If no luck still then ill have to access another PC to try. Might take some time before I can though. Yeah..been like 16mins. And still hanging, time to try what I just said..lol
[Nexus 7 Android Development] WugFresh:
You could also try flashing a ROM. That might be a good course of action. You can use the flash zips button in the toolkit or put a ROM on your sdcard and boot into temp custom recovery. If you flash a ROM and then you are able to boot up, then try reflashing stock.

{{ WugFresh }}
[Nexus 7 Android Development] demandarin:
I was wondering the same thing. Good idea. Which folder would I put the rom in for your toolkit to flash it? I think I knlow but want to be sure.
[Nexus 7 Android Development] WugFresh:
The toolkit will handle everything if you use the "file is on my computer" option. It doesn't matter what folder, the toolkit will push it to your phone and flash it automatically.

{{ WugFresh }}
[Nexus 7 Android Development] demandarin:
I tried :( its not recognizing my device through adb. So the pop up appears saying adb device wasn't found. I'm only being recognized through fastboot.

I did try to boot into temp. Custom recovery. It worked and twrp appeared. But I have nothing installed on device itself to flash. So I figured I try to push a rom from my PC to /sdcard. Wouldn't work because once again adb device wasn't found. At least it booted up twrp though..lol. my restore backup must've been erased. I looked for THST also. I'm kinda stumped now. Commands using adb won't work as its not being recognized. Only being recognized through fastboot. I wish there was a fastboot way to push or flash the rom. Or hold up..lol. can I fastboot flash the rom zip? Fingers crossed..lol even on stock recovery?

Me being able to temp. Boot into twrp gives hope. Now I just need a way to push the rom onto device. I noticed my /sdcard folder is empty also. Any Backdoor tricks to flash custom rom through fastboot or push file, througgh fastboot, to my nexus?

I also saw in twrp, when i tried to reboot through it, it said I have no OS installed. Is there supposed to be a folder that says "\datadata"? I saw that there through twrp. If that helps. It might explain why adb not working and only fastboot. For adb to work, debug option needs to be checked off in developers options, correct? Well I'm pretty sure its not and since I have no OS installed, according to twrp, I won't be able to enable debugging mode unless there's another way.

Do you think using fastboot command to erase all those partitions then format them would help? I used fastboot to format system partition and it worked. Then tried flashing system.img again. Waiting game again..lol