Recommended Posts

Rooting a Nexus device should be the simplest thing to root. I know you've looked at a few guides, have you tried this one? Using Toolkits can actually make things more complicated so this one is a bit more manual.

Essentially you need to unlock your bootloader (assuming you haven't already) and then you can flash a custom recovery and root.

Hope that helps

did you read the link??

the second paragraph says

You DO NOT need to be on a stock rom to run this and it will NOT erase your data. But it is recommended when you get into CWM recovery for obvious reasons.

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-developers.com/showthread.php?t=1995688

Nexus 7: http://forum.xda-developers.com/showthread.php?t=1809195

Nexus 10: http://forum.xda-developers.com/showthread.php?t=2001868

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"

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

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?

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-developers.com/showthread.php?t=1995688

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.

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)

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

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

VIA5x.png

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

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.
[/CODE]

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

if you're on the stock rom and you updated OTA then yes it will remove the root if you don't have one of the root keeper apps installed on your android

Here's a dumb question. Hwo do I fully back up my Nexis 7? Plug it in and just drag everything to a folder on my PC?

are you already rooted? if so just boot into CWM and make a backup from there

Do is rooting even worth it? I'm not even sure I understand the concept. Is it like Jailbreaking on iOS? I'm only even looking into it because I wanted to try the Saxaxxis app and apparently it needs the device to be rooted.

Does rooting void your warranty?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Payday TWO!! Is 13 years old man I feel old - I remember trying it out and if I did not know I would say 5-6 years ago or something
    • Payday 2 engine upgrade adds 64-bit and DX11 support, drastically shrinks install size by Pulasthi Ariyasinghe Payday 2, the most popular entry in the heisting game franchise, is getting a surprising update after all these years. This is slated to be a complete engine upgrade that will enhance almost every aspect of the 13-year-old title, targeting performance, loading times, file size, rendering backend, and more. Developer Sidetrack Games is planning a beta to test out the new version ahead of the full public launch. The development team today revealed that the long-awaited upgrade to the 64-bit architecture is happening with this Diesel 3.0 engine update. By letting the game use more ram than 4GB, it is said to improve stability and compatibility on most hardware. It should also help modders in the long term with implementing larger changes too. "While many of the changes are made on the backend and not everything will be visible to you guys because it is a massive rewrite of the entire codebase, there will be a lot of things that you can look forward to," Sidetrack explained. Payday 2 will also hop over from DirectX 9 to 11. Instead of visual improvements, this is slated to reduce the amount of VRAM used by the title, letting more lower-end hardware access the title and run it better. Since these changes would require a complete redownload of the game anyway, Sidetrack says it has revamped "the game's packaging and bundling system." This should reduce the installation size from 86GB to 32GB. "So, now it's time to finally move the game to your SSDs," added the studio. The Payday 2 Diesel Engine 3.0 update is entering open beta on June 30 for Steam users. No console release plans were announced today. Sidetrack Games says it has been working on this complete rewrite of the codebase for the last nine months. While these changes should break most mods, the studio encouraged modders to use the beta period to repair their creations with support from the development team.
  • Recent Achievements

    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
    • First Post
      Kolakid60 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      440
    2. 2
      +Edouard
      195
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      FloatingFatMan
      71
    5. 5
      Steven P.
      68
  • Tell a friend

    Love Neowin? Tell a friend!