Root for *UNLOCKED* Devices
#61
Posted 23 May 2014 - 06:03 PM
#62
Posted 23 May 2014 - 06:06 PM
Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7
#63
Posted 23 May 2014 - 06:10 PM
That Cwm is your only choice right now.
Sent from my S-Offed One M8
FTFY
Non potest esse nisi unus
#64
Posted 23 May 2014 - 06:18 PM
#66
Posted 27 May 2014 - 06:29 AM
CWM is installed now. I run the file. Reboot into Recovery. Put phone in Sideload Mode.
error: device not found
Every time.
Tried it on another computer, too. Win7 and WinXP.
Copied files to C:\ROOT
Ran the Koush ADB Installer.
Read the instructions 30 times now, at least. I don't think you could make it any easier.
\\EDIT\\ Tried a fresh Download. No joy...
#67
Posted 27 May 2014 - 07:19 AM
It works for many others, so, you'll have to work through it. That's definitely a diver/usb port/usb cable issue of some kind.
Non potest esse nisi unus
#68
Posted 27 May 2014 - 09:25 AM
Are you effing kidding me? Looked at the Cable. Noticed it says LG on it. I have like 6 of these cables.
Grabbed a Moto one.
Tried it again.
error: no device found
*sigh*
Exited Sideload. Tried it once more.
This time Windows popped up and said "New Device Found: Galaxy ADB drive".... First time I've seen that.
Hmmm. Back into Sideload, run RUN.BAT.....
Success.
The. Freaking. Cable....
Wow.
THanks for the help. What have we learned today?
- COPY the CWM IMG file into the directory that gets created when you unzip called "Recovery"
- Use a GD Motorola Cable. Period.
- johnthehillbilly and Rob626 like this
#69
Posted 27 May 2014 - 09:27 AM
And people give me a hard time when I say "use the oem cable that came with the phone....yes it matters". LOL Glad you fixed it.
- ibolski and johnthehillbilly like this
Non potest esse nisi unus
#71
Posted 27 May 2014 - 09:29 AM
Are you effing kidding me? Looked at the Cable. Noticed it says LG on it. I have like 6 of these cables.
Grabbed a Moto one.
Tried it again.
error: no device found
*sigh*
Exited Sideload. Tried it once more.
This time Windows popped up and said "New Device Found: Galaxy ADB drive"....
Hmmm. Back into Sideload, run RUN.BAT.....
Success.
The. Freaking. Cable....
Wow.
THanks for the help. What have we learned today?
- COPY the CWM IMG file into the directory that gets created when you unzip called "Recovery"
- Use a GD Motorola Cable. Period.
I've seen this happen as well. Not all USB cables are made equal. You would THINK they would, but I think it depends on various things, including how much power can it feed to the phone.
My daughters have a blue-tooth speaker that is shower-safe that they use to hook up to their iPhones to listen to music. It comes with what looks like a standard USB cable that has the exact same connector that fits into my USB port of my phone. Hook it up to the PC and nothing. Hook it up to an outlet adapter and nothing. It won't charge.
But, it has no problem charging the blue-tooth speaker. More than likely, it probably doesn't require as much "juice" to charge the speaker, so it probably doesn't send the same amount of voltage through the cable.
I have definitely seen LG cables for older LG phones that I have not work with my Android phones and I would happen to guess it is the same reason as it is with the blue-tooth cable - it doesn't supply enough current to charge, let alone, allow it to connect to a PC and register itself as a device you can adb/fastboot to.
VZW Samsung Galaxy S7 Stock and unrooted running Marshmallow 46A, 32gb Nexus 7 unlocked
#72
Posted 27 May 2014 - 09:43 AM
Decided to take the plunge.. Thank you for the great write-up it was easy to follow and the only tricky was getting into fastboot, but that's explains in a later post. Now time for me to get root back. BTW, I was on 4.4.2 with an unlocked BL before the update script and everything went smoothly!
- SamuriHL likes this
#73
Posted 28 May 2014 - 05:25 AM
started with a fumbled OTA. on my xt926 dead Android, no boot.bricked
finally found this tool, fumbled thru it for 2 days,
almost ready to give up, somehow, some way finally used the universal file, with RDS.
it starts Flashing Yeaa !! , reloaded the new VXZ.
Thank you very much for developing this work !
Love my Maxx phone, ... on GSM ... Tmobile
- SamuriHL, livinginkaos and cmh714 like this
#74
Posted 28 May 2014 - 12:09 PM
I was having problems with this on my unlocked XT926 with the latest KK update. Namely, no many how many times I tried, I always got "<bootloader> Variable not supported!". What finally worked:
1) Installed the latest Moto drivers from Moto themselves (
)-> this was a key, the Koush Universal ADB driver was failing. Whenever I'd connect my phone in ADB mode to my Win7 x64 machine with just that driver, Windows would fail to install a driver.
-> also made sure that I had Developer enabled on my phone (update wiped it) and enabled installing apps from unknown sources
2) I copied the SuperUser update zip to my phone's external SD card.
3) I copied the CWM img file to my C: drive, and renamed it to "recovery.img"
4) I opened a cmd window in windows (Start->in run field type "cmd")
5) In cmd window, typed "cd c:\"
6) In cmd window, typed "adb reboot bootloader"
7) In cmd window, typed "fastboot flash recovery recovery.img"
8) I repeated that a good half dozen times or so, always getting the same "Variable not supported" error but it appeared to copy.
9) In cmd window, typed "fastboot reboot"
-> I think this was also key for some reason, rebooting phone normally once after installing CWM.
-> disconnected phone until it finished booting, then reconnected
10) In cmd window, typed "adb reboot recovery"
11) It finally booted into CWM! Then I just installed ZIP from external SD card like normal.
Hope this helps someone else struggling. I have no idea why that finally worked despite getting the same error message, but it did. I was using a Moto USB cable the whole time, and used the same USB2 port on my laptop the whole time.
- Ofire likes this
#75
Posted 04 June 2014 - 01:59 AM
o) IF you need to have custom recovery installed for you, add your twrp OR cwm recovery img file to the recovery folder. This is ONLY necessary if you don't already have custom recovery flashed to your phone.
Thanks for providing this information. I appreciate it.
I'm working to restore root on a Droid RAZR MAXX HD recently upgraded to 4.4.2
The phone is unlocked and was purchased used.
How do I determine if I have custom recovery on my phone already?
#76
Posted 04 June 2014 - 02:01 AM
Sent from my SM-P600 using Tapatalk
Non potest esse nisi unus
#77
Posted 04 June 2014 - 02:08 AM
Did you install custom recovery? If you didn't then there isn't.
Sent from my SM-P600 using Tapatalk
I didn't but it is possible the prior owner did. It was unlocked when I bought it.
#78
Posted 04 June 2014 - 02:13 AM
Sent from my SM-P600 using Tapatalk
Non potest esse nisi unus
#79
Posted 04 June 2014 - 03:01 AM
Sent from my DROID RAZR HD using Tapatalk
#80
Posted 04 June 2014 - 03:13 AM
Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7
4 user(s) are reading this topic
0 members, 4 guests, 0 anonymous users