49 replies to this topic

[+McKay]

Tried 8 separate guides for unlocking and rooting my Nexus 4 and I ran into the same problems as you, they'd constantly go over some point not mentioned earlier in the tutorial.

[guitmz]

All the android devices are pretty easy to root (just rooted a nexus 10 minutes ago - mannually)... if you dont want to do it like i did, use the toolkits

Nexus 4: http://forum.xda-dev...d.php?t=1995688

Nexus 7: http://forum.xda-dev...d.php?t=1809195

Nexus 10: http://forum.xda-dev...d.php?t=2001868

[+McKay]

guitmz, on 21 November 2012 - 19:38, said:

All the android devices are pretty easy to root (just rooted a nexus 10 minutes ago - mannually)... if you dont want to do it like i did, use the toolkits

Tried the Nexus 4 Toolkit, sat there in the fast boot screen, hit yes to unlock it and it sat there forever saying "waiting for device"

[1WayJonny]

Hello I am the maker of the universal naked drivers so if you need to connect get that first here:
http://forum.xda-dev...08#post28610908

If any users is having issues with the Nexus 7 rooting ti may be cause you hit JB already which has all exploits closed. What you need to do is unlock the boot loader and push root to your system, here's how.

1) Unlock bootloader
2) Boot not flash custom recovery from fastboot
3) mount /System
4) /System is NOW accessible through ADB
5) use ADB to push the SU through command
6) reboot done

If you download my Transformer Prime "Urkels Fresh Start" covers this and if you replace the files and use same commands you will be good to go.

Urkels Fresh Start:
http://forum.xda-dev...d.php?t=1929189

[+McKay]

1WayJonny, on 21 November 2012 - 19:53, said:

Hello I am the maker of the universal naked drivers so if you need to connect get that first here:
http://forum.xda-dev...08#post28610908

If any users is having issues with the Nexus 7 rooting ti may be cause you hit JB already which has all exploits closed. What you need to do is unlock the boot loader and push root to your system, here's how.

1) Unlock bootloader
2) Boot not flash custom recovery from fastboot
3) mount /System
4) /System is NOW accessible through
5) use ADB to push the SU through command
6) reboot done

If you download my Transformer Prime "Urkels Fresh Start" covers this and if you replace the files and use same commands you will be good to go.

Urkels Fresh Start:
http://forum.xda-dev...d.php?t=1929189

Is this just for Nexus 7? Any guides for Nexus 4?

[1WayJonny]

McKay, on 21 November 2012 - 19:59, said:

Is this just for Nexus 7? Any guides for Nexus 4?

Same process on Nexus 4

Unlock
Boot custom recovery
mount /System
and push files to Nexus 4, the nexus 4 does not work with the normal superuser (ChainsDD) and the variant of Chainsfire is used for now. SuperSU

mskip from XDA makes a toolkit which uses my naked drivers, this tookit will automate the process I just mentioned.

http://forum.xda-dev...d.php?t=1995688

[+McKay]

1WayJonny, on 21 November 2012 - 20:17, said:

Same process on Nexus 4

Unlock
Boot custom recovery
mount /System
and push files to Nexus 4, the nexus 4 does not work with the normal superuser (ChainsDD) and the variant of Chainsfire is used for now. SuperSU

I tried that, it just hands indefinately on "waiting for device" when I tell the program to unlock it.

[guitmz]

the process is the same for all google devices... waiting for device is usually related to missing drivers or lack of privileges on windows... on linux it works as it should btw (just run sudo fastboot for the operations)

[1WayJonny]

McKay, on 21 November 2012 - 20:25, said:

I tried that, it just hands indefinately on "waiting for device" when I tell the program to unlock it.

I think I know the issue, first you must uninstall any previous drivers and use mine (which is also the default for the toolkit).

Before you run the toolkit you need to install the driver multiple times, once per fastboot and once per ADB. each mode shows differently in devices manager so you must install it for each mode.

You are 100000% having a driver issue

Please read the red below form my drivers thread:

Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers

[+McKay]

1WayJonny, on 21 November 2012 - 20:32, said:

I think I know the issue, first you must uninstall any previous drivers and use mine (which is also the default for the toolkit).

Before you run the toolkit you need to install the driver multiple times, once per fastboot and once per ADB. each mode shows differently in devices manager so you must install it for each mode.

You are 100000% having a driver issue

Please read the red below form my drivers thread:

Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers

Ok deleted all the drivers, I try to install them from the program but I get this

[1WayJonny]

McKay, on 21 November 2012 - 20:49, said:

Ok deleted all the drivers, I try to install them from the program but I get this

The problem is you are using Windows 8 and need to go to my thread to disable driver enforcement, you are installing drivers through the tool kit which will not give you the error plus needs to run as Admin

If you install them normally through device manager it would have shown this to you. Disable the enforcement and then reinstall the drivers. I would do this manually with my package until you can confirm you got around Windows 8 driver enforcement.

Windows 8 Instructions
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.

[+McKay]

Ok it worked now, thanks!

[1WayJonny]

McKay, on 21 November 2012 - 22:25, said:

Ok it worked now, thanks!

I could tell that was the issue when your screenshot had the windows 8 theme.

Glad to hear! Cheers!

[+Azusa]

Another question is can updating to jellybean un-root cause superuser seems to have stopped working?

[Zumiiiiii]

I lost my root when I installed JB 4.2 OTA. Just 30secs to get root back though.