[Q] Stock 4.2.2. refusing to ADB to then root

[nigelhealy]

I had a windows 7 PC perfectly working in booting a Nexus 7 to flash and root etc, it did a Nexus 4 last week.

There is some problem with drivers and 4.2.2. specifically. My story was it was 4.1.2. rooted and it was refusing to OTA update but I wasn't bothered due to the bugs/performance in 4.1.1 so I waited til 4.2.2. came along. The N7 refused to take OTA 4.2.2. I got the Android icon with the Red icon out its belly and it would boot back as 4.1.2 every time.

So using Nexus Rootkit I did a "stock flash+unroot" to 4.2.1 and then let it did a OTA to 4.2.2 and that worked so I have a stock 4.2.2 but not it won't root, it would do that ADB bootloader type stuff. I've tried updating driving umpteen times but it like it simply won't obey ADB type commands? I'm not a rooting expert I just used the toolkit and howtos.

So stuck.

In hindsight as it WAS doing ADB at 4.2.1 I should have rooted and then otarootkeeper then OTA to 4.2.2. but I didn't know 4.2.2 rooting fails.

Any ideas?

 

[maxambro]

same for me!!!
Help...

 

[nikon120]

Well, the OTA for 4.2.2 would fail every time because of version diffs in the files. You had to be on 4.2.1 to accept the OTA.

1. Out of curiosity, did you remember to re-enable USB debugging?
2. Did you update you SDK for 4.2.2?

If you still have issues after enabling debugging, then try the Universal Naked driver. It was the only one to work on my Win7 box. Also, make sure only 1 instance of ADB is running.

At least you don't have a super weird issue like me where flashing stock recovery refuses to stick, but TWRP flashes with no problem.

Sent from my Nexus 7 using Tapatalk 2

 

[nigelhealy]

can root a stock 4.2.2 - it works!

I fixed it!

I'd been trying toolkit all of its options and none worked. So I followed this guide which contains an error which is irrelevant.

http://m.ibtimes.co.uk/root-nexus7-official-android422-jdq39-jellybean-ota-434720.html

Do its step 1. It downloads the Google USB drivers - THEY WORK. This is the problem with other guides they point to drivers which don't work.

Ignore its step 2 because you find step 1 includes fastboot so you don't need to get it separate. I lost a lot of time on that one problem because the link to that shared file fastboot.zip won't download so I hunted and found another and when I was going to copy to the required destination in step 2 I found the fastboot file alreadt there! So ignore step 2

Step 3. Now I downloaded it on the Nexus 7 itself and mine was in /sdcard/Downloads or you can copy on the PC and then copy it over to the N7 via USB cable.

Step 4. Press and hold power off you get option select power off.

Step 5. At the step 1 you'll see WHERE it is installing the SDK to, you need to go to that folder in this step 5 as described.

Step 6. As describe, press vol down and power button together and keep them hold. Then a menu screen shows mine had been unlocked from before. Now dont't touch the N7. Go to Windows machine.

Step 7. My Windows Pc doesn't have command prompt option inside a folder so I opened command prompt and CD down to where step 1 was.

Step 8. Type that command. Mine simply worked fperfectly first time. It had a copying type command which looked happy.

Step 9. Back on the N7 hit the vol up button til you see a "recovery" type word on screen.

Step 10 and 11 as described.

Step 12. Now is the next area where howto guide is wrong / misleading, I had on my screen some gibberish folders and an "update.zip" not the supersu zip from step 3. Initially I tried the update.zip and it went crazy but fortunately a hard power-off got me fixed so then next time I looked around for the supersu zip. So of the stuff on-scren where was like 0/ type folder so I selected that THEN I could see the sdcard/download folder I could go down to and then select the zip file. The /sdcard folder isn't showing firstly you have to go /0 and then you see it.

Step 13 do it.

Then get it booted and then go into Supersu app and run it and then make sure you install voodoo root keeper app and select it to preserve root.

So I've got a vanilla 4.2.2. with root and so far it all works. Features which kept me on 4.1.2 like PPP-widget simply work.

Phew.

I've spent about 15 hours on this trying to eliminate my own dumbness as the cause.

I think basically the ADB drivers in the Toolkits are bumb, ignore them they don't work I think the Android SDK with its Google USB drivers are the ones which work with 4.2.2 I guess the Toolkits need to be updated.

 

[nigelhealy]

Well, the OTA for 4.2.2 would fail every time because of version diffs in the files. You had to be on 4.2.1 to accept the OTA.

1. Out of curiosity, did you remember to re-enable USB debugging?
2. Did you update you SDK for 4.2.2?

If you still have issues after enabling debugging, then try the Universal Naked driver. It was the only one to work on my Win7 box. Also, make sure only 1 instance of ADB is running.

At least you don't have a super weird issue like me where flashing stock recovery refuses to stick, but TWRP flashes with no problem.

Sent from my Nexus 7 using Tapatalk 2

The problem seems to be drivers. The N7 stock 4.2.2 simply refuses to respond to Root Toolkit its drivers are simply not working, the N7 is ignoring to get into fastboot. I figured it out see my later post.

I think 4.2.2. is too new for toolkits and people's 4.2.2. rooting guides are buggy and relate to old old instructioned since outdated and in error. By trial+error I figured it.

 

[nigelhealy]

Well, the OTA for 4.2.2 would fail every time because of version diffs in the files. You had to be on 4.2.1 to accept the OTA.

1. Out of curiosity, did you remember to re-enable USB debugging?
2. Did you update you SDK for 4.2.2?

If you still have issues after enabling debugging, then try the Universal Naked driver. It was the only one to work on my Win7 box. Also, make sure only 1 instance of ADB is running.

At least you don't have a super weird issue like me where flashing stock recovery refuses to stick, but TWRP flashes with no problem.

Sent from my Nexus 7 using Tapatalk 2

Addtional my N7 did OTA receive the 4.1.2 to 4.2.2 update I even went into the /cache and the file name had version names to match so OTA was thinking itself capable. I think in some unlock / root past event I'd something screwed something up and OTA simply weren't working full stop. I did though manage to use Toolkit to get to stock 4.2.1 and then the drivers in the toolkit then don't work with 4.2.2, that's the broken bit. If you use Android SDK Google USB drivers, they work and you have to use command prompt fastboot as in the HOWTO I just posted to get it all working.

Toolkit drives broken with 4.2.2.

 

[simms22]

dont use a root toolkit. do it the right way, there arent any issue.

fastboot oem unlock, fastboot flash a recovery, flash the su binaries or a custom rom, reboot. thats it.

 

[jtrosky]

FYI - I've found that to use the toolkit (the 4.0.0 toolkit is what I used), you need to replace the adb-toolkit.exe (or whatever adb.exe is called in your toolkit) with the adb.exe that comes in the SDK (after you've updated your SDK, of course).

Otherwise, ADB shows as "offline" in the toolkit menu.

Hope that helps someone...

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

 

[nigelhealy]

The issue is what you typed is gibberish to most including me.

Sent from my Nexus 7 using xda app-developers app