FORUMS

Analysis & Opinion

Top Forum Discussions

Cannot root or unlock bootloader 4.4.4

13 posts
Thanks Meter: 3
 
By Ahmed_iAM, Junior Member on 26th June 2014, 03:03 PM
Post Reply Subscribe to Thread Email Thread
I've tried to unlock the bootloader and root this phone for the past 5 hours with no success. Is the 4.4.4 not supported by the current tools? I don't suppose any of the drivers have changed from the 4.4.3 to this. Running windows 8.1. Also have Ubuntu 14.10
The Following User Says Thank You to Ahmed_iAM For This Useful Post: [ View ]
 
 
26th June 2014, 03:06 PM |#2  
Member
Flag Chicago
Thanks Meter: 96
 
Donate to Me
More
Quote:
Originally Posted by Ahmed_iAM

I've tried to unlock the bootloader and root this phone for the past 5 hours with no success. Is the 4.4.4 not supported by the current tools? I don't suppose any of the drivers have changed from the 4.4.3 to this. Running windows 8.1. Also have Ubuntu 14.10

Why don't you just do it manually? Its good learning experience and extremely easy/straightforward to do on Nexus devices. Plenty of guides.

EDIT: I assume you meant you were using scripts given you said tools. I guess I should clarify. You do mean those toolkits are what you are using? Or are you saying that fastboot isn't working?
26th June 2014, 03:06 PM |#3  
Ti2's Avatar
Senior Member
Flag Texel
Thanks Meter: 316
 
More
Quote:
Originally Posted by Ahmed_iAM

I've tried to unlock the bootloader and root this phone for the past 5 hours with no success. Is the 4.4.4 not supported by the current tools? I don't suppose any of the drivers have changed from the 4.4.3 to this. Running windows 8.1. Also have Ubuntu 14.10

What about unlocking it manually (fastboot oem unlock) & flashing recovery + SuperSU?

Beter than the tools (assuming you mean toolkits) anywayz.

Sent from my Nexus 10 using Tapatalk
26th June 2014, 03:08 PM |#4  
Ahmed_iAM's Avatar
OP Junior Member
Thanks Meter: 3
 
More
I'll try it manually. If that doesn't work I'll come back. I usually unlock the bootloader then root. That is the best way right or does it not matter?
26th June 2014, 03:08 PM |#5  
Member
Flag Chicago
Thanks Meter: 96
 
Donate to Me
More
Quote:
Originally Posted by Ahmed_iAM

I'll try it manually. If that doesn't work I'll come back. I usually unlock the bootloader then root. That is the best way right or does it not matter?

Unlocking the bootloader wipes the device, so yes, do that first.
27th June 2014, 02:19 AM |#6  
Ahmed_iAM's Avatar
OP Junior Member
Thanks Meter: 3
 
More
Worked. But Android L erased the root like I thought I would and also removed the custom recovery. I do like the features. Buggy with sum apps but it's good for the most part.
27th June 2014, 02:37 AM |#7  
jd1639's Avatar
XDA: ASSIST
Recognized Contributor
Minnetonka, MN
Thanks Meter: 4,922
 
Donate to Me
More
Quote:
Originally Posted by Ahmed_iAM

Worked. But Android L erased the root like I thought I would and also removed the custom recovery. I do like the features. Buggy with sum apps but it's good for the most part.

Glad you did it the manual way. Flashing the entire factory image will always remove root and put on the stock recovery. Extract the zip file in the factory image and see what's in there. You can flash all those individually.

Sent from my Nexus 5 using XDA Free mobile app
27th June 2014, 04:27 AM |#8  
Ahmed_iAM's Avatar
OP Junior Member
Thanks Meter: 3
 
More
The issue came up again. I Dont know which driver it is. I did the recovery, rooting and flashing from a windows 7 VM and it worked perfectly. It just happens when I use 8.1 it does not work at all. I installed LG's drivers, googles, the SDK, the slimes SDK and a couple others. Seems to make no difference. Any ideas? I'd prefer not having to use a VM to do this root and flashing process.

Main issue is when I do the adb or fastboot devices command, the nexus 5 is not recognized but the system does see it as an android boot loader.
Last edited by Ahmed_iAM; 27th June 2014 at 04:33 AM.
27th June 2014, 06:42 AM |#9  
gfaughn's Avatar
Member
Thanks Meter: 5
 
More
I seem to be having the same issue, I can get the phone to reboot into fastboot through ADB, but "fastboot oem unlock" does not work, states "waiting for device", even tried CF auto root and it displays the same thing, "waiting for device". any suggestions?
27th June 2014, 09:13 AM |#10  
danarama's Avatar
Senior Member
Flag Oxenhope, West Yorkshire, UK
Thanks Meter: 19,162
 
More
Quote:
Originally Posted by gfaughn

I seem to be having the same issue, I can get the phone to reboot into fastboot through ADB, but "fastboot oem unlock" does not work, states "waiting for device", even tried CF auto root and it displays the same thing, "waiting for device". any suggestions?

Reboot your computer. Boot your phone into bootloader using volume down and power. Then connect the USB and see if "fastboot devices" reports anything
28th June 2014, 06:29 AM |#11  
Ahmed_iAM's Avatar
OP Junior Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by gfaughn

I seem to be having the same issue, I can get the phone to reboot into fastboot through ADB, but "fastboot oem unlock" does not work, states "waiting for device", even tried CF auto root and it displays the same thing, "waiting for device". any suggestions?

If it's windows 8/8.1 it needs some driver verification. To turn it off go to charms>setting>advance start up> restart now>trouble shoot> adv options>windows start up options>restart>press F7 or "disable driver signature enforcement">reboot

Should work

Read More
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes