So I've been trying to root my thunderbolt for about a week with no success.
At first I used the method here: http://forum.xda-developers.com/showthread.php?t=1005292
It has continually failed on step 2, tried on different computer also. No luck.
I gave up on rooting it for a few days/
Since the first step went through I am downgraded, running 1.03.605. It's got quite a few bugs and when I try to software update from the phone nothing is found. All I really wanted was to get it to the current firmware to fix connectivity bugs but after searching high and low I still have no idea how to/if it is possible.
I assumed I may have to just root it at this point, so I gave the manual root on theMikMik a shot. While setting up my ABD everything runs smooth until I try to enter commands into abd. I get permissions denied, every time. I've tried looking for an answer to this with no luck. Guide I used found here: http://www.themikmik.com/forums/viewtopic.php?f=66&t=256
So my main question, is there any way to get the latest firmware onto my phone without rooting? I've tried downloading an update, naming it update.zip then updating from bootloader with no luck.
If not, what the hell am I doing wrong that is denying me permission in ABD. I've turned anti-virus off, rebooted etc.
assuming adb is properly set up (drivers working), you've checked Debugging and unchecked Fastboot (under setting->apps->dev), plugged the phone into your computer, and typing "adb devices" acknowledges your phone is connected, and you are in fact on the downgrade as you said you were. Make sure PG05IMG.zip is removed from your sdcard then...
Go here and start at step 5: http://forum.xda-developers.com/showthread.php?t=996616
You were getting permission denied errors with those adb commands on mikmik because you are not rooted yet hence the "rooted evo" under requirements.
Edit:
While that may should work, I believe you could start from the beginning with Step 1 using the link I just posted as well. Just don't flash the old firmware (1.0.3.605 that you currently have) after you go through that for any reason (see: http://forum.xda-developers.com/showthread.php?t=1008824).
Absolute_Zero said:
assuming adb is properly set up (drivers working), you've checked Debugging and unchecked Fastboot (under setting->apps->dev), plugged the phone into your computer, and typing "adb devices" acknowledges your phone is connected, and you are in fact on the downgrade as you said you were. Make sure PG05IMG.zip is removed from your sdcard then...
Go here and start at step 5: http://forum.xda-developers.com/showthread.php?t=996616
You were getting permission denied errors with those adb commands on mikmik because you are not rooted yet hence the "rooted evo" under requirements.
Click to expand...
Click to collapse
*Facepalm*
So I tried what you said from that guide, step 5 failed for me. So I tried from the beginning...still failed.
So, I decided to record it and hopefully you can tell me what I'm doing wrong.
Link: http://www.youtube.com/watch?v=o2AFZEIVIio
Figured that'd be a better way to get the help I need with less reading on your part.
Sorry, I was commuting home from work.
According to the output of "adb shell" you're either already rooted or psneuter has already been run since boot. (note the "#" output instead of "$").
There's no reason to run psneuter to gain permroot again. So once you see that pound sign, start from a two steps down where it says "/data/local/busybox md5sum /data/local/misc.img". IOW, skip that particular "/data/local/psneuter" step.
And I would highly recommend that if you are going to copy/paste, only copy one line at a time to prevent errors.
Off to grab dinner. I'll check back later when I can but hopefully you will be good from here on out.
Edit:
I'm perfectly happy with walking you through it (and I believe you should be fine after this post anyway) but if you still wanted to use that easyroot method that you started with you might want to read this if you haven't http://bit.ly/qsvOkN. I didn't use that easyroot method but it looks like if a step fails, people just run it again until it works. /shrug
I like adb and people should know how to use it anyway.
Related
I have an LG Enlighten (Verizon Wireless), not an LG Optimus Slider (Virgin Mobile), running Android 2.3.4 (Gingerbread). I am in desperate need of a root solution. I have searched the online forums to no avail. I have put the phone up for sale for fear that this device may never be rooted. I am calling on XDA Developers to produce a working root before I ultimately rid myself of this thing. To add, I tried running Android SDK (adb). No go. The instructions threw me even after trying them repeatedly on several different occasions. It could be that my laptop
has no internet access, but I'm not entirely sure.
I really enjoy this phone and have customized it to the point of
exhaustion. All I'm waiting for now is ROOT! Please help ASAP...
Have you attempted to root it? Have you tried Superoneclick, z4root, and/or Gingerbreak?
Re: Have you tried to root it?
Yes, I have. Unfortunately, with no success. Results are as follows:
Z4Root - The end result is my phone takes me back to the previous screen (internet, home, games, music, etc.). It begins the rooting process... acquiring shell root. Then it just sticks for approximately 30 seconds and then closes. I have repeated the process on several occasions in the event that something unusual happened the first time around. But the result is always the same.
Gingerbreak - This app just ultimately hangs, endlessly. Approximately two hours worth before I just quit in frustration. But all online forums claim it should take no more than 15 minutes tops. I should also note that I read Z4Root and Gingerbreak will not work on rooting Android 2.3.4 due to the patching of an exploit. However, I did not update my phone to this firmware. It came preinstalled. And I have not found a procedure for downgrading (sbf'ing) an LG Enlighten.
SuperOneClick - This is the one I'm currently trying still. I can't recall the website, but in addition to SOC, it also requires the use of adb from Android SDK. The problem I'm coming across is the laptop I'm using to perform this action is without internet access (which I've tried feverishly to restore to no avail). And I'm thinking this is what the issue may be, but I'm not entirely sure. The only access I have to the internet currently is on my phone. However, I make a weekly trip to the college library (no restrictions on installing, downloading, etc.). So maybe I can try something there.
For the past month, I've been doing extensive research online trying to find any and all information in regards to resolving this matter. A few sites have blamed Verizon for crippling their Android devices from performing certain functions. For instance, this particular device has no "boot into recovery mode" (which I confirmed with a Verizon tech support person). Had it, I easily could've updated with the .zip file from my SD card (which I've now deleted since it's rendered useless).
I did read today that the next version of SuperOneClick v2.3 (to come out at a later date) will include the option for the forced inclusion of adb debugging/android files which could be the solution to my problems. Possibly.
I apologize if this reply post seems a little long-winded. But I wanted to provide you with all the information I have available in order to better recieve instruction as how to proceed forward. I will continue to try the SuperOneClick in hopes that I will acquire root. But if not, I will rely on the expertise of those in the XDA community.
Thanks,
Centim6
Rooting LG Enlighten
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
centim said:
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
Click to expand...
Click to collapse
Hi, I too have an LG Enlighten from Verizon wireless. I was just wondering how your root process went? Did the phone work well afterwards? Also do you by any chance have a link to or at least remember the name of the video you watched which helped you to get your phone rooted.
thanks in advance, Angel
centim said:
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
Click to expand...
Click to collapse
Can you link to the video?
Sparky42 said:
Can you link to the video?
Click to expand...
Click to collapse
seeing as there is no link, I would say no.
secondly, the video posted and my own research indicates that root was possible only if it was v. 2.3.3. There isn't anything available for 2.3.4.
I have rooted my LG Enlighten which was on Gingerbread 2.3.4. I made a tutorial over at phandroids forums since xda does not let me post links to outside sources. Just google Lg Enlighten root and you will find it in the first or second link. Enjoy.
PS: If you do not believe me I made a video of my phone rooted on youtube. My user name there is the same as xda and I posted pictures at the end of my tutorial. Gingerbread 2.3.4 is fully exploitable on the LG Enlighten.
fsdfgasgfisd said:
I have rooted my LG Enlighten which was on Gingerbread 2.3.4. I made a tutorial over at phandroids forums since xda does not let me post links to outside sources. Just google Lg Enlighten root and you will find it in the first or second link. Enjoy.
PS: If you do not believe me I made a video of my phone rooted on youtube. My user name there is the same as xda and I posted pictures at the end of my tutorial. Gingerbread 2.3.4 is fully exploitable on the LG Enlighten.
Click to expand...
Click to collapse
I think it would a great idea to include which firmware you used this on. I kbow for a fact that it fails on v4 and v5.
And its not that I don't believe you (I do btw) its just the lack of specifics are going to excite someone and they'll leave you a nasty message cause they thought it would work. So, just a heads up:
Android version:
Firmware version:
Sent from my LG-VS700 using xda premium
I can confirm that the new VS700ZV5 update crippled the ability of this phone to root. I just tried the gingebreak and it didnt work. Any way around this?
Same here, android 2.3.4; firmware VS700ZV5.
I haven't been able to get root to work with SoC....
Any chance someone will figure a way around this update?
please reply to root on you tube PLEASE!
centim said:
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
Click to expand...
Click to collapse
Extremely frustrated and hoping you will share this link. I to have tried everything to root my Enlighten to no avail and would appreciate your help more than I can explain! Please! Thank you and congats!
I had my phone rooted, then verizon put out an update, and now I can't root it. I think we're screwed until sombody figures out a new method.
Model: LGVS700
Firmware: VS700ZV5
im not sure if this will help but here, i found this claiming to be able to root the phone.
First, you need the file hboot_2.xx_soff-V8.9.zip, download it.
Unzip it into c:evoroot on your pc.
Second, put your LG Enlighten into development mode by
going to Settings->Applications->Development and turn USB
debugging on.
Third, connect your LG Enlighten to your computer and set
your USB to Just charge.
Fourth, if you get errors with drivers, install their HTC drivers.
(You can also install HTC Sync, but it is bulky!)
Fifth, open up a command prompt by typing cmd.
Sixth, type the following commands: (Or copy and paste,
easier!)
Code:
cd evoroot
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip
adb push root/flash_image /data/local/
adb -d install -r root/z4root.apk
Seventh, go to your phone and launch Z4Root app. Then select
temp root and wait until its done.
Eighth,go back to command prompt and type:
Code:
adb shell
su
If you get a pound(#) sign, that means you have temp root,
which just gives you temporary root so we can now install
permanent root.
ninth, go back to command prompt and type the following:
Code:
chmod 0755 /data/local/flash_image
./data/local/flash_image misc /sdcard/mtd-eng.img
sync
And reboot to bootloader mode by typing:
Code:
reboot bootloader
When bootloader mode starts up, it will look for PC36IMG.zip
and after about 3 minutes ask you if you want to install
PC36IMG.zip.
Say Yes by hitting the volume up button, it should now install
the new zip file, should take about 10 minutes. Go grabs some
coffee and come back.
Eleventh, reboot when its done by hitting the volume up
button.
It will reboot into the OS and we dont want that so takes the
battery out and puts it back in it. Then go back to the
bootloader by hitting the power button while holding down
the volume down button.
Choose Bootloader and wait until you get the triangle sign and
type:
Code:
adb push recovery /
adb shell busybox Cinstall /sbin
adb shell nohup /sbin/recovery
&
Go back to your LG Enlighten and you should see green
menus.
Choose install zip from sd card and choose unrevoked-
forever.zip
After that installs, Choose MS-USB
Go to your computer and delete PC36IMG.zip, then rename
PC36IMG-MR.zip to PC36IMG.zip.
Then power off your LG Enlighten, power back on by pressing
Power Button while holding down the Volume Down button,
this should get you back into bootloader mode.
Simply wait and when it asks to install the update, hit the
Volume Up button.
then reboot your LG Enlighten, your device should now be
rooted with Recovery menu then you can flash new ROMs for
LG Enlighten.
LG Enlighten root
I have lg enlighten running 2.3.4 and it is rooted with super user and rom toolbox working. I used POOT.APK which can be found on google. It worked well and everything went smooth. It is a simple and easy to use application. (You can use either SU or SSU)
any way to update it to ics? i have one
Hi, I just purchased the new LG myTouch (all myTouches are now made by LG) from tmobile and I have been trying to root it with no luck. I have been trying to use superoneclick but it always gets to step 7 and stops working. I made sure my SD card is unmounted, the phone has USB debugging turned on, I have tried the pdanet method, and I tried unplugging and replugging the USB cord but it always stops on step 7. The phone has android 2.3.4 but I have seen other threads where people with 2.3.4 got their phones rooted so why can't I? Any ideas?
Sorry if I'm posting this in the wrong place but there is no forum dedicated to this phone. I'm guessing because it just came out this month.
i just got the Q for my girl, i was wondering the same, just to remove the bloat. can someone please point me to the right direction?
Just checking in to see if anyone has found any answers.
Network24 said:
Hi, I just purchased the new LG myTouch (all myTouches are now made by LG) from tmobile and I have been trying to root it with no luck. I have been trying to use superoneclick but it always gets to step 7 and stops working. I made sure my SD card is unmounted, the phone has USB debugging turned on, I have tried the pdanet method, and I tried unplugging and replugging the USB cord but it always stops on step 7. The phone has android 2.3.4 but I have seen other threads where people with 2.3.4 got their phones rooted so why can't I? Any ideas?
Sorry if I'm posting this in the wrong place but there is no forum dedicated to this phone. I'm guessing because it just came out this month.
Click to expand...
Click to collapse
where can i find these threads? can you point me to it... maybe i can try and find something, or do something different and help out with solving it.
EDIT: did these threads say for the MTQ or was it just a thread for a random 2.3.4 device?
The threads I saw were just for a random 2.3.4 device. I saw another thread on xda with someone trying to root this phone but just like this thread no one is answering.
Has anyone found any methods to root this phone?
Success!
After several attempts to root via SuperOneClick 2.2, I tried something totally random from another LG rooting thread that seems to have worked. Install ADB, then do:
WINDOWS> adb shell
$ echo 1 > /data/local/lge_adb.conf
$ exit
Then run SuperOneClick 2.2 and it should root properly.
I will have to give this a try on one of my Windows PC's. Linux and SuperOneClick are not playing nice together right now.
+1
Good Job Man....Worked for me. Have root and superuser.
Ditto! Root, & Superuser
== Instructions that worked for me ==
- Download myTouch Q drivers (Search "mytouch Q usb drivers" - Can't post links yet! XD )
- Check that adb recognizes device: C:\> adb devices
- Follow eamondaly's instructions:
WINDOWS> adb shell
$ echo 1 > /data/local/lge_adb.conf
$ exit
Click to expand...
Click to collapse
- Run SuperOneClick v2.2
- Wait for phone to reboot (SuperOneClick seems to be paused)
- Reset USB debugging (mine was turned off after reboot)
- Wait for SuperOneClick to finish.
- Enjoy rooted phone
Thanks
Okay thanks for the root methods greatly appreciated but now I am starting to get into developing anyone can teach me how to make a system dump to try and make my own roms I am a fast learner ort at least point me in right direction thanks again
Im not shure if im doing something wrong, i had better luck rooting an xperia play, a Droid X, and a htc mytouch, but this lg mytouch wont go for me. I tryed runing adb, i know how to use, was doing a little programming with it and eclipse. Anyhow, typed everything in and this is what my cmd shell looked like...
C:\ADB>adb shell
$ echo 1> /data/local/lge_adb.conf
echo 1> /data/local/lge_adb.conf
$ exit
exit
Then i tryed running superoneclick , tryed root and shell root, neither seem to work, it goes threw some and then hangs. my phone disconnects and reconects, thats it though. i checked in terminal, typed su, access is denied. i tryed it with debugging on and off, sd mounted and not.
Any ideas or tips. im using windows vista.
DMOYER said:
Im not shure if im doing something wrong, i had better luck rooting an xperia play, a Droid X, and a htc mytouch, but this lg mytouch wont go for me. I tryed runing adb, i know how to use, was doing a little programming with it and eclipse. Anyhow, typed everything in and this is what my cmd shell looked like...
C:\ADB>adb shell
$ echo 1> /data/local/lge_adb.conf
echo 1> /data/local/lge_adb.conf
$ exit
exit
Then i tryed running superoneclick , tryed root and shell root, neither seem to work, it goes threw some and then hangs. my phone disconnects and reconects, thats it though. i checked in terminal, typed su, access is denied. i tryed it with debugging on and off, sd mounted and not.
Any ideas or tips. im using windows vista.
Click to expand...
Click to collapse
you are running under admin right I know silly question but had to as lol
Thanks eamondaly
I just want to thank eamondaly for this method. I just ran superoneclick 2.3.1 and it worked perfectly. I don't know if it was your method that worked or if superoneclick 2.3.1 fixed it but all that matters is my phone is now rooted. Thanks.
Thanks a lot for the root method, I've been waiting patiently for this. Now can we get to making mods for this phone now?
Edit: Anyone having trouble sending/receiving MMS messages? I cant seem to send or receive them.
I was having an issue with receiving MMS on both my wife's and my phone. Ditching the stock messaging client and downloading Handcent resolved it for both.
Switching MMS apps didn't work. Tried a number of countless APN setups. I just decided to unroot and factory reset. Everything is working again.
titanium pro back up image
hey all,
Im sure this is a random spot for this but, since we dont have a home yet.
Im looking for a stock back up image (Titanium backup pro)with all apps and system settings. I think I may have cleared out a system file or two when cleaning out all the Tmo bloat.
Any help or other suggestions would be great.
I found another way to root easily. http://www.unlockroot.com download, install and click root. I had issues with superoneclick and the adb method but this gave me full root with superuser and now I am happy that all the t-mobile crapware is gone
I'm trying to root my T-Mobile MyTouch Q and not having any luck. It's Android 2.3.6, but I tried running "echo 1 > /data/local/lge_adb.conf" and I get a permission denied error. I tried SuperOneClick version 2.2 and 2.3.3. SuperOneClick gets to step 7 than hangs and nothing happens. It says waiting for device. I also tried Unlock Root and it fails to get shell root. I searched all over google and the xda forums, but all say to run that command then run SuperOneClick and that hasn't worked for me. Anyone have any ideas?
Hello all!
I'm trying to root my HTC Legend using Chirag's manual.
I somehow managed to complete all steps until step 4 (that is, flashing the rooted rom), but now i'm stuck.
I but the phone in fastboot mode, plug it to my computer, and the phone says "fastboot USB". When i run 'step1-windows.bat', nothing happens, i get the message:
"Legend Root Step 1
Erasing cache and rebooting in RUU mode...
<waiting for device>"
And that is all. Any ideas? It would be pretty lousy to go through all those steps, including downloading and losing all apps not to be able to finish the very last step...
--edit--
I do have superuser "app" in the drawer of my legend. Don't know if it's important...
Ok, so my PC doesn't see the legend when in FASTBOOT mode, "adb devices" returns an empty list. When the phone is on, and normal, i see it with adb services.
Okay, made it past step one. I turned off HTCSync, and the PdaNet, which i installed earlier (i was that desperate). Nothing seemed to work. I then entered FASTBOOT mode, plugged it into the PC, and then in control panel went to 'devices', found 'Android 1.0 devices' and installed the drivers automatically. The moment i did that, step one started to work, and finished in about couple of minutes.
Just in case someone else gets this problem, this is the solution.
Now starting step 2, i hope it will succeed.
--edit--
Yesss!!! It worked like a charm, i now (finally) have rooted 2.1 with sense
Sorry for talking to myself, but i wanted to share the solution, i usually get pissed when someone solves his problems and doesn't share
Nah Your all right with me, its good to see you managed to get it fixed on your own. I think all the guides need to be updated with that information regarding the need for android 1.0 drivers as it seams to be THE most common issue when not being able to get through the rooting steps.
Enjoy and have fun!
Sent from my HTC Legend using XDA App
So, I was sort of thinking that at least rooting and OTA blocking with the handy hdx toolkit would be easy but I don't get the impression that it is working. My Firmware is 13.3.2.3.2 and I used towelroot via the toolkit. This is what I see when I root. (aren't allowed to post links/images yet so it's only a non-clickable link to the image, sorry)
i.imgur.com/GLtVd1R.jpg
As you can see, there are some error messages. It also asks me to select 'make it rain' but there is nothing on my device to actually select and it continues on without my input. It then says 'please wait until device reboots' but my device continues to be entirely unimpressed and doesn't reboot, not even a bit. In short, while the root *appears* to be doing something, I don't think it actually does because it can't find the stuff it needs. On the next screen it checks if the rooting worked but it only gets me another error message saying /system/bin/sh: su: not found
help, please?
You can download and install towelroot manually.
As for OTA updates, you can rename /system/etc/security/otacerts.zip to anything else (i.e. otacerts.zip.bak); that should block them.
I couldn't leave well enough alone despite @EncryptedCurse excellent advice and managed to troubleshoot it and get it working in the toolkit after all. In case someone has similar troubles (Error 2 and Error 3 are what I got at different times) here's how I got it working (in Windows 7):
-In the device manager I uninstalled the adb driver (with adb enabled the kindle is listed twice in the device manager, you should unistall the drivers of the one that *isn't* listed under portable devices) and restarted the computer. Edit: On second thought: I'm not sure if that uninstall worked. I think I needed to use uninstaller.exe in C:\Program Files (x86)\Amazon.com\Kindle Fire\Drivers to really remove the driver.
-Then I disabled ADB in the kindle. I also shut down my antivirus (not sure if it made a difference but some people have reported interference). Then I used the toolkit to install adb drivers again (in the instructions there it says to have adb enabled while doing this but if you get error messages while rooting try it this way.).
-Now I rebooted the computer again (this is important), checked that antivirus was still activated, checked that Bluestacks was *also* still shut down (having it or another emulator open leads to a complete different error message, I have learned ) and tried rooting with the toolkit again. It worked with no troubles.
Last time I checked it was a chore to unlock the bootloader is that still the case these days? Its why I haven't yet done it on my HDX 8.9" running 14.3.2.4_user_324002120
Montisaquadeis said:
Last time I checked it was a chore to unlock the bootloader is that still the case these days? Its why I haven't yet done it on my HDX 8.9" running 14.3.2.4_user_324002120
Click to expand...
Click to collapse
Wow - that's an old build! If you have used adb, have a host PC or laptop, can install device drivers and are comfortable following directions unlocking is relatively easy. At present the task remains a largely manual affair. However, the rewards are rich with a nice suite of custom ROMs including several Nougat based options. It will be like having a new device!
I have both a laptop and desktop both are running Windows 10
Montisaquadeis said:
I have both a laptop and desktop both are running Windows 10
Click to expand...
Click to collapse
Assume the device is rooted given OTA updates appear blocked. If accurate read and execute step #2 only (skip #1) from this post. The links in that post are dead; you can download the files from here. Be sure to grab the Apollo variants of both files. Life gets ugly fast if you run with the Thor variants.
The above procedure will NOT unlock the bootloader but will put into place the necessary prerequisites for doing so.
Davey126 said:
Assume the device is rooted given OTA updates appear blocked. If accurate read and execute step #2 only (skip #1) from this post. The links in that post are dead; you can download the files from here. Be sure to grab the Apollo variants of both files. Life gets ugly fast if you run with the Thor variants.
The above procedure will NOT unlock the bootloader but will put into place the necessary prerequisites for doing so.
Click to expand...
Click to collapse
The thread on TWRP says it requires an unlocked bootloader. So wouldn't that cause issues since I am NOT unlocked yet?
Montisaquadeis said:
The thread on TWRP says it requires an unlocked bootloader. So wouldn't that cause issues since I am NOT unlocked yet?
Click to expand...
Click to collapse
Nope - TWRP can be flashed on a locked device with a vulnerable bootloader. Having access to a custom recovery can be a huge benefit should something go wrong during subsequent steps.
I understand why the OP included that caveat. Makes sense if you don't have someone guiding you through the unlock procedure.
Davey126 said:
Nope - TWRP can be flashed on a locked device with a vulnerable bootloader. Having access to a custom recovery can be a huge benefit should something go wrong during subsequent steps.
I understand why the OP included that caveat. Makes sense if you don't have someone guiding you through the unlock procedure.
Click to expand...
Click to collapse
Hows the 1-click bootloader unlock working these days?
AKA
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
It was linked to in the post you linked to.
Ok so far I have done both TWRP which is indeed working and aboot and that is it.
Montisaquadeis said:
Hows the 1-click bootloader unlock working these days?
AKA
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
It was linked to in the post you linked to.
Ok so far I have done both TWRP which is indeed working and aboot and that is it.
Click to expand...
Click to collapse
Congrats! You have gotten through the riskiest part of unlocking the bootloader. From this point forward there is little you can do to hurt your HDX aside from sustained contact with a blow torch or direct engagement with an A1 Abrams battle tank (bit of an overreach but you get the point).
Unfortunately, 1-Click is still not ready for prime time. The author has the best of intentions but a severe lack of bandwidth to complete.
That said, manual unlocking is relatively easy:
1) Download/install this package on one of your Windows machines which scores drivers that have proven reliable with every HDX device I (and others) have encountered. Yep, seems illogical but it works better than all of the other alternatives (drivers) that have been bounced around for the past 4 years. You can remove the package after unlocking your device.
2) Install Minimal ADB and Fastboot (here) on the same machine
3) Verify you can launch the ADB/Fastboot command window via the icon that should have been added to your Windows desktop.
4) Boot into TWRP and tether your device using a reliable USB cable. You should receive some audible/visual feedback from Windows that it recognizes the device.
5) Launch the minimal ADB/Fastboot window, type "adb devices" and press <return>. Response should be the device identifier followed by the word 'device'. If successful type "adb reboot bootloader" followed by <return>. After a few moments the device will boot into fastboot. Type "fastboot devices" and press <return>. If successful response should be similar that noted above. Finally, type "fastboot reboot" to boot into FireOS. If any of the previous commands fail simply untether and long press power button (8-20 sec) to turn off your device. It can then be restarted in the usual fashion.
If you have difficulty with any of the items in step #5 please detail your observations and I will help you through remedial steps. Otherwise, bounce back and we will go through the remaining few steps to complete the unlock process.
Sorry for parceling this out in small chunks. Experience has taught this is the best approach rather than penning a long novel in a single post.
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Is what came up when I went to do adb reboot bootloader.
Montisaquadeis said:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Is what came up when I went to do adb reboot bootloader.
Click to expand...
Click to collapse
Hum - something seems wrong. That command should not have failed if the previous "adb devices" returned the expected response. Let's take a different approach to the fastboot connectivity test:
- untether device
- boot into TWRP
- tap 'reboot' followed by 'bootloader'
- you may be prompted for a confirmation swipe; go ahead and do that
You should now see a gray "Kindle fire" logo followed by the word "fastboot" in brackets. Retether device; hopefully a ready prompt will appear. If so continue with fastboot connectivity test as documented in previous post.
If a ready prompt does not appear or the test fails you'll need to use Windows device manager to identify your device and update the device driver to "Mot Composite ADB Interface". This can be a tedious process if you haven't gone through it before. Bounce back if you need assistance.
Ok fastboot devices is not bringing anything up so it doesn't seem to have worked.
Oh in Device Manager its coming up as Kindle Fire HDX under both Universal Serial Bus devices and Portable Devices.
basically
adb devices brings up the device id but it says unautherized to the right of the id.
Montisaquadeis said:
Ok fastboot devices is not bringing anything up so it doesn't seem to have worked.
Oh in Device Manager its coming up as Kindle Fire HDX under both Universal Serial Bus devices and Portable Devices.
basically
adb devices brings up the device id but it says unautherized to the right of the id.
Click to expand...
Click to collapse
Boot into FireOS, tether and respond to any prompts. Hopefully one asks you to approve the connection to your Windows box (be sure to check the 'always' box if presented). Then repeat adb connectivity test.
Note: You may have to enable adb under developer options in settings. Might find this article helpful (found it on a quick Google search; haven't verified contents but seems to be ok; I haven't used FireOS v4 in a couple years).
Note #2: I'm happy to keep going but don't want to you to feel obligated/stressed by the barriers being thrown up. Feel free to bail at any time.
Davey126 said:
Boot into FireOS, tether and respond to any prompts. Hopefully one asks you to approve the connection to your Windows box (be sure to check the 'always' box if presented). Then repeat adb connectivity test.
Note: You may have to enable adb under developer options in settings. Might find this article helpful (found it on a quick Google search; haven't verified contents but seems to be ok; I haven't used FireOS v4 in a couple years).
Note #2: I'm happy to keep going but don't want to you to feel obligated/stressed by the barriers being thrown up. Feel free to bail at any time.
Click to expand...
Click to collapse
Ok FireOS comes up with device next to the id while TWRP says unautherized so I have no idea what is going on here personally.
Montisaquadeis said:
Ok FireOS comes up with device next to the id while TWRP says unautherized so I have no idea what is going on here personally.
Click to expand...
Click to collapse
Not going to worry about it now as it doesn't reflect an immediate barrier. You have established/verified ADB communications (good!) but still need to verify fastboot communication.
Path forward:
- Boot back into TWRP and then reboot to the bootloader/fastboot (there are more direct methods but the TWRP->Fastboot two step is the easiest for now). As before there should be a 'fastboot' in brackets but no 'ready' prompt.
- Tether device; if ready appears you're good! More likely nothing will happen. At that point you need to launch Windows device manager and change the device driver used to communicate with the HDX as detailed in a previous post. In short, locate the device (most likely shown with a yellow explanation mark); right click -> update driver; select 'Browse my computer...'; select 'Let me pick...'; locate and select 'Mot Composite ADB Interface'. If you still do not get a ready prompt after performing the above repeat the first two steps until device is retethered. Hopefully that will do it.
- Once you have a ready prompt issue the command 'Fastboot devices' to verify fastboot communications are possible. Then reboot your device.
I realize the above seems kludgy and obviously frustrating. It is without a doubt the most difficult part of unlocking the device. Once fastboot communications have been verified it's all down hill.
Davey126 said:
Not going to worry about it now as it doesn't reflect an immediate barrier. You have established/verified ADB communications (good!) but still need to verify fastboot communication.
Path forward:
- Boot back into TWRP and then reboot to the bootloader/fastboot (there are more direct methods but the TWRP->Fastboot two step is the easiest for now). As before there should be a 'fastboot' in brackets but no 'ready' prompt.
- Tether device; if ready appears you're good! More likely nothing will happen. At that point you need to launch Windows device manager and change the device driver used to communicate with the HDX as detailed in a previous post. In short, locate the device (most likely shown with a yellow explanation mark); right click -> update driver; select 'Browse my computer...'; select 'Let me pick...'; locate and select 'Mot Composite ADB Interface'. If you still do not get a ready prompt after performing the above repeat the first two steps until device is retethered. Hopefully that will do it.
- Once you have a ready prompt issue the command 'Fastboot devices' to verify fastboot communications are possible. Then reboot your device.
I realize the above seems kludgy and obviously frustrating. It is without a doubt the most difficult part of unlocking the device. Once fastboot communications have been verified it's all down hill.
Click to expand...
Click to collapse
As I said Kindle Fire HDX is listed TWICE in Device Manager when tryinng to do the fastboot. Its listed under both Portable Devices and Universal Serial Bus devices and neither have a yellow exclamation mark so I havw no clue which one to change over to the other driver. Ontop of that its 11pm here so I will check back tomorrow.
Montisaquadeis said:
As I said Kindle Fire HDX is listed TWICE in Device Manager when tryinng to do the fastboot. Its listed under both Portable Devices and Universal Serial Bus devices and neither have a yellow exclamation mark so I havw no clue which one to change over to the other driver. Ontop of that its 11pm here so I will check back tomorrow.
Click to expand...
Click to collapse
You want to work the entry listed under Portable Devices. I'm in the same timezone; also winding down for the evening.
Hi Davey, I'm responding in this thread as you requested yesterday.
Before I start trying to install TWRP, does it matter that I have Safestrap currently installed? Or should it be removed first? @Yousucks2 said the following in my other thread:
"But check first first which recovery are you install, replace Safetrap with TWRP without unlocked bootloader , will brick your device"
Also, I am running a custom Rom of kindle fire for thor. I was on kit Kat 4.4 but felt like trying out Amazon again. Not sure if that matters at all in this process.
leeismyname said:
Hi Davey, I'm responding in this thread as you requested yesterday.
Before I start trying to install TWRP, does it matter that I have Safestrap currently installed? Or should it be removed first? @Yousucks2 said the following in my other thread:
"But check first first which recovery are you install, replace Safetrap with TWRP without unlocked bootloader , will brick your device"
Also, I am running a custom Rom of kindle fire for thor. I was on kit Kat 4.4 but felt like trying out Amazon again. Not sure if that matters at all in this process.
Click to expand...
Click to collapse
Reasonable questions; responses:
- SafeStrap v4 and TWRP can coexist on the same device; no need to uninstall the former which is not a true recovery (it lives in the system partition and will be wiped out when you install a custom ROM)
- No issue running FireOS while navigating the bootloader unlock procedure
As previously noted be sure to use the Thor builds on your HDX 7. Recovering from an inadvertent Apollo flash make passing a kidney stone look appealing.
Ok I have changed the driver over to MOT composite ADB device V2 since I had 2 listed aka Version 2 and version 1.3. I now have the ready prompt and when I do fastboot devices I get the device id and fastboot to the right. So I tlooks like I am good to go with fastboot now
Montisaquadeis said:
Ok I have changed the driver over to MOT composite ADB device V2 since I had 2 listed aka Version 2 and version 1.3. I now have the ready prompt and when I do fastboot devices I get the device id and fastboot to the right. So I tlooks like I am good to go with fastboot now
Click to expand...
Click to collapse
Excellent! Next steps:
- Complete the 3rd bullet in the prerequisite section of this post. Pay careful attention to where the extracted batch file resides; move as needed. Most likely the directory will be "C:\Program Files (x86)\Minimal ADB and Fastboot" but you will need to confirm. Obviously referring to the Win 10 box.
- Perform steps #1 and #3 in the "Code generation and unlock" section. When complete it is quite possible the bootloader will be fully unlocked. However, if the procedure stalls we will have to take one more (easy) step to complete the procedure.
IMPORTANT: Step 2 in the "Code generation and unlock" section has already been performed (as directed earlier in this thread)! No need to repeat as this is the riskiest part of the unlock procedure.
Bounce back when complete. There are a couple clean-up steps that should be done before flashing a custom ROM. I can also provide guidance on which ROM to install if you don't already have one in mind.