• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root How long does rooting take?

N

nickademus420

Lurker
I am using the Nexus Root Toolkit v1.8.0, and it is stuck on booting modified boot.img to enable running privileged commands.
Been there over 30 minutes.
Is this normal?
Should I retry and do something different?
I chose Root and checkmarked custom recovery.
 
Are you sure it's not waiting for you to confirm something either on the tablet or in the toolkit?
 
nickademus420 said:
I am using the Nexus Root Toolkit v1.8.0, and it is stuck on booting modified boot.img to enable running privileged commands.
Been there over 30 minutes.
Is this normal?
Should I retry and do something different?
I chose Root and checkmarked custom recovery.
Click to expand...

You need to make sure your device setting in Wug's NRT is properly set to the version and build of android your device is currently running.

ibb4EHIxvkMKkC.png


This setting is vital and probably the only thing you can screw up, make sure you set it properly. If by chance NRT pushes the wrong modified boot image to your device you will get everything you described, but it is not fatal.

Press and hold the power button on your nexus until it shuts down.

Once it reboots go into settings/about device. Write the device and build down.

Set the proper device and build in NRT.

Try again and it should work.
 
Glad it worked out, Thank you for reporting back what the solution was as it will help people in the future that has the same issue and stumbles across this thread via a search of the forums or even Google.
 
I have the same problem . Have checked the version and build number. Lock status unlocked. Bootloader version Flo-04.02
Any idea what I can do?
 
khun wim said:
I have the same problem . Have checked the version and build number. Lock status unlocked. Bootloader version Flo-04.02
Any idea what I can do?
Click to expand...

What is happening exactly? What are you doing step by step and where/when/what point is the device hanging?

Also, what is your exact device?
 
exact device: Nexus 7, Android: 4.4.3, Kernel version:3.4.0 go3485a6 Build nummer: KTU84L,
4.4.3 en build nunmer zijn veranderd omdat ik gisteren, na het probleem, een update heb gedaan.
Ik heb Nexus Root Toolkit 1.8.3 gedownload en geinstalleerd. Toen een back up gemaakt, de nexus unlocked (krijg open slot te zien bij opstarten, Drivers gedeinstalleerd volgens initial set up, toen root aanwijzingen gevolgd. Daar ontstond het probleem dat ik beschreef.

exact device: Nexus 7, Android 4.4.3, Kernel version: 3.4.0, go3485a6, Build number: KTU84L (
After this reported problem I updated the Nexus to 4.4.3, I had installed Nexus Root Toolkit 1.8.3, made a back up, unlocked the device (at start up I see an open lock.) Installed drivers according to initial set up and than followed the root procedures. There a encountered the problem I described.
 
heb na update modified boot rasor 4.4.3 geinstalleerd en nu blijkt dat hij wel root.
tenminste kreeg ik gefeliciteerd. Hoe kan ik vaststellen dat het device geroot is? Ik heb alle aanwijzingen van Supersu etc, gevolgd en uitgevoerd.
 
Hey folks!

I came across this thread last night while searching for a solution for a very similar issue.

After farting around for hours trying different things I finally noticed the following line in Step 3 of the Full Driver Installation Guide:

Step 3: Choose a driver solution (if the reccomended dosen't work try #4)
Click to expand...

I went ahead with Driver Solution #4 - RAW Drivers. I had to jump through some security hoops as I'm using Windows 8.1 (possibly the problem all along) but once I had that completed, BAM! Root completed quickly and without issue!

Anyway! I just thought I'd follow up in the hopes of helping others. The moral of the story is, READ THE INSTRUCTIONS! :) I'm terrible for that. I skim and miss important stuff like this.
 
khun wim said:
heb na update modified boot rasor 4.4.3 geinstalleerd en nu blijkt dat hij wel root.
tenminste kreeg ik gefeliciteerd. Hoe kan ik vaststellen dat het device geroot is? Ik heb alle aanwijzingen van Supersu etc, gevolgd en uitgevoerd.
Click to expand...

Forgot your translator.
 
Sorry, I am dutch, live in Thailand but this moment in the netherlands. Sometimes I do not realise what language I am using.
After update to 4.4.3 I installed the modified boot rason 4.4.3. and now the device has rooted. at least I get the message: congratulations. How can I find out the device did root indeed? I followed all the instructions from the very nice and accurate application.

@clearnew: I did the same, first #1 but this did not work. Than #4, this did work but the system did not root yet.
 
khun wim said:
Sorry, I am dutch, live in Thailand but this moment in the netherlands. Sometimes I do not realise what language I am using.
After update to 4.4.3 I installed the modified boot rason 4.4.3. and now the device has rooted. at least I get the message: congratulations. How can I find out the device did root indeed? I followed all the instructions from the very nice and accurate application.

@clearnew: I did the same, first #1 but this did not work. Than #4, this did work but the system did not root yet.
Click to expand...

Look to see if you have the app super su. If you do open it and let it update. Also look for app busybox. If you used a toolkit, it should have told you to do that after rooting if it was successful.
 
khun wim said:
Yes, I do have Super Su and busy box. So, the device must be rooted.

thank you
Click to expand...

You're welcome. Also open busybox app and wait for it to finish gathering components. Change location at the top to system/xbin, then tap install. Choose normal install not smart install.
 
You must log in or register to reply here.
Back
Top Bottom