So recently, I downgraded to 13.3.1.0, and installed Safestrap (not the one for later versions). However, after restarting and adding a ROM slot, it wouldn't let me do anything with stock.
I restored stock, but still nothing.
The odd thing is, whenever I press the power button, it will still make noise.
I can access fastboot, Safestrap, and the default recovery.
What do I do?
Bump, need help ASAP
Alex311360 said:
So recently, I downgraded to 13.3.1.0, and installed Safestrap (not the one for later versions). However, after restarting and adding a ROM slot, it wouldn't let me do anything with stock.
I restored stock, but still nothing.
The odd thing is, whenever I press the power button, it will still make noise.
I can access fastboot, Safestrap, and the default recovery.
What do I do?
Click to expand...
Click to collapse
If you can enter safestrap recovery, check if you can establish adb access:
so enter safestrap and connect kindle to your pc or laptop. Then start cmd window or terminal if you using linux, and try:
adb devices
it should return:
list of devices attached
xxxxxxxxx recovery
if you can achieve that your kindle in safestrap recovery is recognized by win/linux, you can try this:
1. Download this 13.3.1.0 (Kindle HDX 7") update - pure amazon FireOS so OTA updates enabled - do not connect to wifi/register your kindle if you want root and use of custom recovery after flashing this
A. Now, since I am not expert for adb installing pushing repairing etc., read this thread [HOWTO] Unbrick your device
B. If that for whatever reason wont work, you can try sideload update-kindle-13.3.1.0_user_310079820.bin (rename .bin to .zip before sideloading) through safestrap recovery, but because Safestrap is only TWRP "based", I cant guarantee that this will work either (it should, but this is one way ticket, your working safestrap recovery will be destroyed in the process of update and if things dont go as they should, your kindle is bricked for good):
0. connect kindle to pc/laptop
1. enter Safestrap, tap Advanced -> ADB Sideload -> Swipe slider to start Sideload
2. on pc/laptop open cmd/terminal, type adb devices, you should see:
List of devices attached
XXXXXXXXXXXXXXXX sideload
3. type adb sideload update-kindle-13.3.1.0_user_310079820.zip
4. You will see a progress bar in the command prompt indicating that the Zip file is being copied to the device. Once the file is transferred, the Zip is automatically installed on your device.
OK fingers crossed, I hope something will work, but things can go wrong, so it is up to you if you try this or not ...
On a scale of 1 to worse, what happens if ADB sideload refuses to work? It just freezes at starting and does nothing afterwards, and I have to cancel.
Alex311360 said:
On a scale of 1 to worse, what happens if ADB sideload refuses to work? It just freezes at starting and does nothing afterwards, and I have to cancel.
Click to expand...
Click to collapse
You can also try to unlock your bootloader (since you have compatible FW) and proceed to flash cuber signed recovery (TWRP 2.8.5.0) through fastboot and then from TWRP you can do necessary steps to recover your kindle quite easily - if you are familiar with TWRP flashing...
Regarding sideloading I honestly dont know how it will react - never try it - it was developed exactly for quick system recovery, but you must be flashing 100% working rom ...
Personaly I would go for bootloader unlock and then flash TWRP 2.8.5.0 from which sideloading feature (If you want use that) must working... :good:
Do you require a factory fastboot cable for that?
Alex311360 said:
Do you require a factory fastboot cable for that?
Click to expand...
Click to collapse
No, standart USB cable is enough.
Can you give me a link on how to do this? I know I'm sounding very noobish, but I'm a tad new to this.
Alex311360 said:
Can you give me a link on how to do this? I know I'm sounding very noobish, but I'm a tad new to this.
Click to expand...
Click to collapse
Sure, here is original post from dpeddi.
... and here is how to for windows ... :good:
Hey, sorry it's taken me so long to reply. Was busy with school.
For some reason it won't connect to the device in fastboot, it just says "waiting for device", even the Kindle says "Ready." and does nothing.
What do I do?
Alex311360 said:
Hey, sorry it's taken me so long to reply. Was busy with school.
For some reason it won't connect to the device in fastboot, it just says "waiting for device", even the Kindle says "Ready." and does nothing.
What do I do?
Click to expand...
Click to collapse
If your OS is Windows 7, you can try install these drivers and then try again.
jeryll said:
If your OS is Windows 7, you can try install these drivers and then try again.
Click to expand...
Click to collapse
Still no dice. Doing fastboot devices or adb devices brings up nothing.
Please note I have done the following things:
- did a kindle fire system restore with safestrap restore still installed
- adb sideload doesn't work in safestrap
- fastboot drivers used installed does nothing
Still stuck.
Alex311360 said:
Still no dice. Doing fastboot devices or adb devices brings up nothing.
Please note I have done the following things:
- did a kindle fire system restore with safestrap restore still installed
- adb sideload doesn't work in safestrap
- fastboot drivers used installed does nothing
Still stuck.
Click to expand...
Click to collapse
On which FW you were before downgrading to 13.3.1.0?
Weird thing with windows and these drivers is it sometimes command fastboot -i 0x1949 devices does nothing, while actually direct commands like
fastboot -i 0x1949 getvar product
fastboot -i 0x1949 getvar version
fastboot -i 0x1949 getvar kernel
works as expected...
Anyway to restore system on your kindle you need working connection between kindle and PC/laptop, so you can use adb commands to restore your system, or after bootloader unlock, you can use fastboot commands to flash required/missing components. I have tested while in safestrap kindle is recognizable by adb devices, if you can achieve that, you can continue with how to unbrick thread I posted before.
You can also learn how to install/use Linux, where adb and fastboot device recognition/commands works 100%...
I must leave for work now ...
So, some kind of miracle happened, and I found the source of the problem.
Upon trying to update to 13.3.2.4, it reboots the phone instead of installing it. I try booting into Safestrap, and it does Open Recovery Script, causing it to boot to a black screen upon booting to the actual thing.
I don't know how to fix Open Recovery Script doing that, but all I had to do to get it back to normal was reflash the 13.3.1.0 amazon OS onto stock.
Related
Hi xda,
I was unlocking and installing AOKP ROM this week and I've hit a problem that I can't get past. I apologise that this seems like so many other questions already posted, but I haven't found a solution in the threads I've read. I also apologise that I write verbose explanations; I just want to be as clear as possible.
My new TF201 was on ASUS firmware .21 so I used bpear's viperMod/Wolf849-based tool to downgrade to ASUS firmware WW .15.
I then used bpear's tool to root it after downgrading, and then unlocked the bootloader using ASUS' tool. Before anyone asks why I bothered to root if I was going to unlock, I didn't entirely understand what was required to flash a custom ROM on the TP; the process was much simpler on my HTC Desire.
After unlocking the TF201 I used bpear's tool to flash CWM. I downloaded AOKP (aokp_tf201_build-38.zip) and put it on the internal space - I don't have an SD card in it. I rebooted the device into CWM and wiped Dalvik cache, reset factory settings, then went to "Install from zip" and selected the AOKP zip. It ended successfully (i.e: no errors, all messages on the screen appeared normal), so I reboot the device.
And after rebooting it hangs at the splashscreen. I tried to reflash AOKP but there was no change, so I rebooted into the bootloader menu and, without thinking about the consequences, selected to wipe the device. Now I can't reflash AOKP because I wiped the device, and I can't restore a nandroid backup because I didn't take one before flashing AOKP.
I rebooted to the bootloader and selected Fastboot mode while the device was connected to my computer (Windows 7 x64). In Windows, I can see in the taskbar that a device is recognised as "fastboot", and drivers are installed successfully, so I type in the command 'fastboot devices' which simply returns a new line. I reboot into CWM and try to use adb to connect to the device, but there is no device detected in Windows and the command 'adb devices' indicates there is nothing found.
At this point I'm unsure what step to take next. Any tips would be useful.
The command "adb devices" will not show your device unless it's booted, so what you're seeing is normal. You may want to try pushing a ROM to your TFP via adb fastboot.
cam30era said:
The command "adb devices" will not show your device unless it's booted, so what you're seeing is normal. You may want to try pushing a ROM to your TFP via adb fastboot.
Click to expand...
Click to collapse
there is no 'adb fastboot' command
@OP, you have to reinstall/point windows again (while in recovery) to the drivers manually. it's the same drivers, yes.
Hi xda,
I got everything sorted a couple of days after this thread was started.
I followed the same procedure described in the OP, with two changes:
1. I swapped AOKP for Virtuous Prime.
2. I installed the Universal Naked Drivers .
My TF201 is functioning very well on Virtuous Prime ROM. I am pleasantly surprised with the battery life but sufficiently annoyed with the wireless that I set up an AP at the other end of the apartment just for the TF201.
cam30era said:
The command "adb devices" will not show your device unless it's booted, so what you're seeing is normal. You may want to try pushing a ROM to your TFP via adb fastboot.
Click to expand...
Click to collapse
While I was searching for a solution, I read on several sites that it was possible to push files to the tablet while in recovery mode/CWM. An example is this thread. I have to wonder: am I misunderstanding the steps being provided, or is the information being provided is incorrect or incomplete?
With regards to fastboot, I did mention in the OP that fastboot wasn't functional.
Cheers.
Droid DNA with Supercharged Hatka DNA got stuck in bootloop after running fine for over a year (ROM flashed last February)
I have a *fairly* recent backup if I could get it to boot to recovery, but I would prefer not to considering the 20ish Litecoins walleted on the device. I will be willing to give a whole Litecoin to whoever can fix my problem
Esploded said:
Droid DNA with Supercharged Hatka DNA got stuck in bootloop after running fine for over a year (ROM flashed last February)
I have a *fairly* recent backup if I could get it to boot to recovery, but I would prefer not to considering the 20ish Litecoins walleted on the device. I will be willing to give a whole Litecoin to whoever can fix my problem
Click to expand...
Click to collapse
Do you have adb? If you do the command is adb reboot recovery. Need to know more it just cycles? If so then try to push both power button and and both volumes until it has lights flashing at the bottom and reboots dont let go until it reboots. Other then that I am not sure. I tried to boot to recovery the manual way and it doesnt work. Which is why i Always use that to reboot recovery. Wait, I figured it out. Hold down volume power dont let go until bootloader comes up then let go of both. use volume down and select recovery and bam!
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Esploded said:
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Click to expand...
Click to collapse
Ok so if you have fastboot you should be able to use fastboot to flash recovery. If you are going to use a backup then you would need to have the same recovery image you used for the original. My suggestion is go to twrp and get the image. make sure you are plugged in at bootloader and fastboot is selected. IT should say fastboot usb if you are connected correctly on the top. I am assuming you have fastboot? If not my suggestion is to get minimal adb and fastboot it is the easiest. after you have installed run this command.
fastboot devices
it should come up with your device number if it doesnt then you need fastboot drivers. If it does then take the recovery.img you downloaded and place it in the same folder as your fastboot and adb folder. I suggest changing name to make it easier, I usually just change it to recovery.img instead of whatever it downloaded as. Then enter this command
fastboot flash recovery recovery.img
It should say sending and complete then enter this command
fastboot reboot recovery
bam you are in recovery!
jhr5474 said:
Ok so if you have fastboot you should be able to use fastboot to flash recovery. If you are going to use a backup then you would need to have the same recovery image you used for the original. My suggestion is go to twrp and get the image. make sure you are plugged in at bootloader and fastboot is selected. IT should say fastboot usb if you are connected correctly on the top. I am assuming you have fastboot? If not my suggestion is to get minimal adb and fastboot it is the easiest. after you have installed run this command.
fastboot devices
it should come up with your device number if it doesnt then you need fastboot drivers. If it does then take the recovery.img you downloaded and place it in the same folder as your fastboot and adb folder. I suggest changing name to make it easier, I usually just change it to recovery.img instead of whatever it downloaded as. Then enter this command
fastboot flash recovery recovery.img
It should say sending and complete then enter this command
fastboot reboot recovery
bam you are in recovery!
Click to expand...
Click to collapse
I'll give the fastboot utility a shot, hopefully it works. Thank you
Esploded said:
I'll give the fastboot utility a shot, hopefully it works. Thank you
Click to expand...
Click to collapse
IT is a lifesaver and so is adb once you learn how to use them you will be freed from lots of problems! Good luck.
jhr5474 said:
IT is a lifesaver and so is adb once you learn how to use them you will be freed from lots of problems! Good luck.
Click to expand...
Click to collapse
ADB tool is no help, computer will not recognize my phone even with all the HTC drivers installed. I'm at my wit's end, starting to believe something in the phone's hardware is messed up because nothing is working
Esploded said:
ADB tool is no help, computer will not recognize my phone even with all the HTC drivers installed. I'm at my wit's end, starting to believe something in the phone's hardware is messed up because nothing is working
Click to expand...
Click to collapse
Which adb drivers did you install and you need the fastboot drivers also. I have never found a phone that would not accept a fastboot command what OS are you on?
jhr5474 said:
Which adb drivers did you install and you need the fastboot drivers also. I have never found a phone that would not accept a fastboot command what OS are you on?
Click to expand...
Click to collapse
I only installed the HTC Sync and the ADB utility, I didn't know about ADB drivers. I'm on Windows 7
Esploded said:
I only installed the HTC Sync and the ADB utility, I didn't know about ADB drivers. I'm on Windows 7
Click to expand...
Click to collapse
All this stuff has been asked and answered a hundred times... Look here
http://forum.xda-developers.com/showthread.php?t=2131284
Get your ADB and Fastboot working. You will be fine.
sdamark said:
All this stuff has been asked and answered a hundred times... Look here
http://forum.xda-developers.com/showthread.php?t=2131284
Get your ADB and Fastboot working. You will be fine.
Click to expand...
Click to collapse
ADB and fastboot don't help, since it won't connect to any computer. I'm starting to think this is a hardware issue
I figured out what caused this. About a month ago, I was deleting unnecessary files, and it had been a year since I'd flashed my custom ROM so I forgot what the process involved. I accidentally deleted the 'sdcard' folder, and the phone became a ticking time bomb for it to stop working. I bricked it didn't I?
Esploded said:
I figured out what caused this. About a month ago, I was deleting unnecessary files, and it had been a year since I'd flashed my custom ROM so I forgot what the process involved. I accidentally deleted the 'sdcard' folder, and the phone became a ticking time bomb for it to stop working. I bricked it didn't I?
Click to expand...
Click to collapse
No, If you have twrp use adb push and push a rom to your phone and then flash it and your fine.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Esploded said:
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Click to expand...
Click to collapse
If you can get into your rom, go to settings..power and at the bottom disable fastboot
Esploded said:
ADB and fastboot don't help, since it won't connect to any computer. I'm starting to think this is a hardware issue
Click to expand...
Click to collapse
1. Charge your phone (about 24 hours).
2. Let him rest (about 24 hours) without turning on.
3. Connect device to PC with original wire (Win7 preferred).
There is possibility that your BB will recognize phone.
I'm in the middle of restoring an HTC One M7 Sprint phone to stock from CM11. Since I don't have S-Off, I tried using the minimal package from HTC1Guru, the Reset Download. I have TWRP Recovery, so I copied the Reset Download utility to the phone and ran it. That went ok, except the screen was unresponsive and I had to use a mouse. So, I tried to get an OTA (after relocking the bootloader) to get all current stock. A few minutes into the install of the OTA, it just locked up and there I sat, with the White HTC screen and nothing happening.
So I've tried several things. But a side effect of this condition is I could NOT run ADB. Now I do have a USB connection and it works; In Fastboot if I issue the FASTBOOT DEVICES command I get the device id back. But I could not get ADB to work at all, even though the cable is connected and all that (since Fastboot works). Oh, and ADB worked before this locked up. ADB Devices returns no devices. BUT (it gets weirder) I went back to Fastboot and flashed TWRP REcovery again, and if I enter RECOVERY, I can issue ADB Commands from recovery fine. But outside of recovery, I can't. And, more importantly, PROGRAMS CAN'T DETECT ADB. I tried Rumrunner's program to turn S-OFF, and I tried the ARUWizard RUU utility from Viperboy, and both said to check the USB cable, that ADB could not be found. But I went right to it, booted recovery, and there was ADB!
So, what could cause ADB to be present if I'm booted to recovery, but not from bootloader screen? since right now I can boot to REcovery but not to the ROM, I'm totally dead in the water.
Steve
Steve Thomas said:
So, what could cause ADB to be present if I'm booted to recovery, but not from bootloader screen?
Click to expand...
Click to collapse
ADB never works in the bootloader (that's why you have fastboot to talk to it). ADB talks to the ADB daemon, which is running when a ROM or a recovery is booted.
_that said:
ADB never works in the bootloader (that's why you have fastboot to talk to it). ADB talks to the ADB daemon, which is running when a ROM or a recovery is booted.
Click to expand...
Click to collapse
I thought I must be doing something wrong running ADB with the phone in Recovery since Rumrunner keeps failing with "No ADB Connection". But maybe it's something else.
Thanks!
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
wbexpress said:
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
Click to expand...
Click to collapse
If you have a T-Mobile device you are able to root etc. Make sure you have usb debugging enabled, and tick enable oem unlock in developer options. I presume you have a driver issue. Just go ahead and reinstall the drivers and try again.
markbencze said:
If you have a T-Mobile device you are able to root etc. Make sure you have usb debugging enabled, and tick enable oem unlock in developer options. I presume you have a driver issue. Just go ahead and reinstall the drivers and try again.
Click to expand...
Click to collapse
Hi Mark. Which drivers? I have literally tried to use 5 or 6 different ways of installing drivers: device manager/Nexus Root Toolkit/the full Android SDK/KlicKit/adb setup 1.4.3 and maybe two others. Do you know a source that I am missing? Why would my phone out of all of the thousands sold NOT have proper drivers installed? This makes no sense. Weird thing is I can get to the bootloader screen using the adb reboot bootloader command.
wbexpress said:
Hi Mark. Which drivers? I have literally tried to use 5 or 6 different ways of installing drivers: device manager/Nexus Root Toolkit/the full Android SDK/KlicKit/adb setup 1.4.3 and maybe two others. Do you know a source that I am missing? Why would my phone out of all of the thousands sold NOT have proper drivers installed? This makes no sense. Weird thing is I can get to the bootloader screen using the adb reboot bootloader command.
Click to expand...
Click to collapse
Can I ask what commands your running when you're rebooted into boot loader/fastboot?
I'd say to try the LG drivers first and if not go with the Samsung ones. They're relatively universal.
Im also having problems. Ive installed every driver from samsung lg google and universal drivers and still nothing. I can get adb to reconize the device and reboot my device. I type in fastboot oem unlock and it stays on waiting on device
markbencze said:
Can I ask what commands your running when you're rebooted into boot loader/fastboot?
I'd say to try the LG drivers first and if not go with the Samsung ones. They're relatively universal.
Click to expand...
Click to collapse
Sure. Usually I am able to get into the bootloader(if adb devices recognized what's going on) where I get the LG logo and the words on the top left say "Welcome to Fastboot Mode". I put in adb reboot bootloader, which does get me there. Then, I put in fastboot oem unlock and that's when it hangs on waiting for device.
dillonorden said:
Im also having problems. Ive installed every driver from samsung lg google and universal drivers and still nothing. I can get adb to reconize the device and reboot my device. I type in fastboot oem unlock and it stays on waiting on device
Click to expand...
Click to collapse
Exactly. I guess the "misery loves company" thing is operative here. If you do figure it out, PM me, I will do the same.
what does it say when you type "fastboot devices"?
I am 100% certain you have either a driver issue which you should look into in your device/driver manager on your pc. there's likely something broken (common problem). Or you do not have usb debugging/enable oem unlock checked. I'm leaning towards a driver issue. It is also possible that if what you say is true and have installed too many drivers that something is conflicting.
markbencze said:
what does it say when you type "fastboot devices"?
I am 100% certain you have either a driver issue which you should look into in your device/driver manager on your pc. there's likely something broken (common problem). Or you do not have usb debugging/enable oem unlock checked. I'm leaning towards a driver issue. It is also possible that if what you say is true and have installed too many drivers that something is conflicting.
Click to expand...
Click to collapse
Progress!!! I was able to use Tech Know to unlock the bootloader. Now, if I can get the phone to behave enough to install twrp and root I will be good. But, KlicKit is not doing it, still hanging. And, when I type fastboot devices it just opens up another prompt and sits.
Edit: And, I am able to use fastboot reboot to reboot from the bootloader, but I get an error message when I try KlicKit, but it goes away too quickly to read what it says. OK, so now that I have an unlocked bootloader, do you have a recommendation of what method to use to install twrp and to root. (I have renamed the twrp file to "twrp.img" and I have both SU 2.46 and 2.52 on my external sd).
wbexpress said:
Progress!!! I was able to use Tech Know to unlock the bootloader. Now, if I can get the phone to behave enough to install twrp and root I will be good. But, KlicKit is not doing it, still hanging. And, when I type fastboot devices it just opens up another prompt and sits.
Edit: And, I am able to use fastboot reboot to reboot from the bootloader, but I get an error message when I try KlicKit, but it goes away too quickly to read what it says. OK, so now that I have an unlocked bootloader, do you have a recommendation of what method to use to install twrp and to root. (I have renamed the twrp file to "twrp.img" and I have both SU 2.46 and 2.52 on my external sd).
Click to expand...
Click to collapse
Just follow the instructions in the "how to root..." thread. it goes step by step and I believe there is a video tutorial as well. You'll need to do a quick search for this.
wbexpress said:
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
Click to expand...
Click to collapse
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
duecebravo said:
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
Click to expand...
Click to collapse
Hi Duece, thanks for that. I am ok up to where I actually try to root, meaning, I am fine with getting into the bootloader. When I type "fastboot devices" it does give me the model # and the word fastboot next to it. The bootloader is now definitely unlocked. It's the next steps (twrp/root) that I get stuck. When I use KlicKit, it does do something for a second and then it just closes. Have you successfully installed twrp and rooted? That's where I'm jammed up. Thanks...
Edit: although I have the twrp.img file on my ext sd, and I renamed it "twrp.img" and typed that command in when in the bootloader, but it says "error: cannot open twrp.img".
wbexpress said:
Hi Duece, thanks for that. I am ok up to where I actually try to root, meaning, I am fine with getting into the bootloader. When I type "fastboot devices" it does give me the model # and the word fastboot next to it. The bootloader is now definitely unlocked. It's the next steps (twrp/root) that I get stuck. When I use KlicKit, it does do something for a second and then it just closes. Have you successfully installed twrp and rooted? That's where I'm jammed up. Thanks...
Edit: although I have the twrp.img file on my ext sd, and I renamed it "twrp.img" and typed that command in when in the bootloader, but it says "error: cannot open twrp.img".
Click to expand...
Click to collapse
put the twrp.img in the same folder with fastboot, flash recovery by using
Code:
fastboot flash recovery twrp.img
After twrp flash ,shutdown/ restart to factory rest mode and go for 2x "yes". if entering TWRP fine, then flash a supersu 4.52 zip from sd
I am using 2.8.x twrp working fine
jkyoho said:
put the twrp.img in the same folder with fastboot, flash recovery by using
Code:
fastboot flash recovery twrp.img
After twrp flash ,shutdown/ restart to factory rest mode and go for 2x "yes". if entering TWRP fine, then flash a supersu 4.52 zip from sd
I am using 2.8.x twrp working fine
Click to expand...
Click to collapse
Aah, that would make sense. However, I did a search in Root Explorer and nothing came back with "fastboot". Do you know where the most likely place would be?
wbexpress said:
Aah, that would make sense. However, I did a search in Root Explorer and nothing came back with "fastboot". Do you know where the most likely place would be?
Click to expand...
Click to collapse
So which step did you go through?
Do you have your twrp recovery working now?
fastboot is a platform tool from google. You should have it downloaded to computer(Win) and use it with CMD(command prompt)
https://www.youtube.com/watch?v=PPLwFGxLQA4
This is a good sample of how ppl unlcok BL and root v10
duecebravo said:
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
Click to expand...
Click to collapse
Lorddyyy ive been trying this crap all day i have the same driver issue but it won't let me select the one i want it just says there are no drivers available in this folder! GRRRRR
---------- Post added at 08:37 PM ---------- Previous post was at 08:00 PM ----------
omg i think i got it! http://forum.xda-developers.com/lg-v10/help/phone-adb-fastboot-t3247732 went here and did what duece said above but choose choose from a list!> then i hit select all devices> the box said populating but i just clicked install from disk and changed it to the unzipped file folder that had the driver in it until i found this file android_winusb and selected it!> then low abd behold the box populated with the driver info and it became a samsung adb device! finalllyyyyyy!!!!!!!!!!! i'm so happy Ive been trying to root this damn thing all day!
jkyoho said:
So which step did you go through?
Do you have your twrp recovery working now?
fastboot is a platform tool from google. You should have it downloaded to computer(Win) and use it with CMD(command prompt)
https://www.youtube.com/watch?v=PPLwFGxLQA4
This is a good sample of how ppl unlcok BL and root v10
Click to expand...
Click to collapse
No good. typed adb reboot bootloader, it went right there. Then typed fastboot flash recovery twrp-2.8.7.1-h901.img, it gives an error message: cannot flash twrp-2.8.7.1-h901.img. Typed fastboot reboot, went right back. The video's great, but if the commands don't take, it 's moot. If anybody figured this out (same issue), please let me know how. This is taking forever.
wbexpress said:
No good. typed adb reboot bootloader, it went right there. Then typed fastboot flash recovery twrp-2.8.7.1-h901.img, it gives an error message: cannot flash twrp-2.8.7.1-h901.img. Typed fastboot reboot, went right back. The video's great, but if the commands don't take, it 's moot. If anybody figured this out (same issue), please let me know how. This is taking forever.
Click to expand...
Click to collapse
are you sure your bootloader unlocked? and the code you typing match the recovery file name?
jkyoho said:
are you sure your bootloader unlocked? and the code you typing match the recovery file name?
Click to expand...
Click to collapse
Positive. The code I am putting in is twrp-2.8.7.1-h901.img. That's what most things I've read say to do. The other thing I have been thinking about is that KlicKit is supposed to have everything pre-loaded, and even it won't do it. KlicKit gets me into fastboot, then something really quick happens and the command prompt screen closes. What driver system do you use? I've installed a number of them, then deleted them as well, just to try to make sure there are no conflicts. However, I now have two devices in device manager: "android device.lge mobile adb interface" and "portable devices/v10. Does one need to go, maybe?
Power off your phone , hold volumn down and connect usb to PC.
Do you see "LOCK STATE - UNLOCKED" ?
if yes, type "fastboot.exe flash recovery twrp-2.8.7.1-h901.img "
Hey guys - while trying to unlock the bootloader on my HDX 7, I flashed the older aboot per instructions and now cant get the HDX to boot. It shows a backlit black screen when attempting to boot, IT IS recognized by the computer, and I have ADB composite drivers installed, so thats what it is seen as in device manager. I can't see the system mounted as a file folder, however, I can get it to semi-respond to fastboot commands. fastboot devices lists the serial number, fastboot reboot will reboot it back to the backlit screen, fastboot -w did its thing and wiped it, fastboot flash boot boot.img seems to flash the boot.img, but it still will not boot. Also, NO adb commands are working, and it is not seen when adb shell or adb devices is executed. Am I totally F*cked, or is there hope that I can somehow flash a recovery via fastboot and get a system img flashed? any help or thoughts would be great.
sunapeelakers said:
Hey guys - while trying to unlock the bootloader on my HDX 7, I flashed the older aboot per instructions and now cant get the HDX to boot. It shows a backlit black screen when attempting to boot, IT IS recognized by the computer, and I have ADB composite drivers installed, so thats what it is seen as in device manager. I can't see the system mounted as a file folder, however, I can get it to semi-respond to fastboot commands. fastboot devices lists the serial number, fastboot reboot will reboot it back to the backlit screen, fastboot -w did its thing and wiped it, fastboot flash boot boot.img seems to flash the boot.img, but it still will not boot. Also, NO adb commands are working, and it is not seen when adb shell or adb devices is executed. Am I totally F*cked, or is there hope that I can somehow flash a recovery via fastboot and get a system img flashed? any help or thoughts would be great.
Click to expand...
Click to collapse
Barring a hardware problem your device is likely recoverable. Sounds like you may have flashed the wrong aboot; verify you're using the appropriate image. Aboot-13 is for the 7" (Thor); aboot-14 for the 8.9" (Apollo).
If that's not the issue you will need to coax the device into 'bulk mode' and rebuild from there. Not hugely difficult if comfortable with Android devices and working at the command prompt. There are random posts describing the process in the unlock thread. I'm not in a position to post links ATM so you'll have to do some digging. Read carefully; details and sequence of operations matter.
Davey126 said:
Barring a hardware problem your device is likely recoverable. Sounds like you may have flashed the wrong aboot; verify you're using the appropriate image. Aboot-13 is for the 7" (Thor); aboot-14 for the 8.9" (Apollo).
If that's not the issue you will need to coax the device into 'bulk mode' and rebuild from there. Not hugely difficult if comfortable with Android devices and working at the command prompt. There are random posts describing the process in the unlock thread. I'm not in a position to post links ATM so you'll have to do some digging. Read carefully; details and sequence of operations matter.
Click to expand...
Click to collapse
I flashed aboot 13, but the device never booted after I flashed that and twrp. I figured I could get into twrp since I had flashed it one step previous, but I cant. So i wiped it using fastboot -w thinking I could get rid of the aboot file, then flashed twrp again using fastboot flash recovery recovery.img, it ran through its thing and seemed to flash successfully, but I still cant boot to anything but a blank black screen. no logos or anything. It does respond to all the fastboot commands, of which I only know enough to be dangerous. I've tried changing the drivers around to get adb working to no avail. It seems to be stuck in fastboot mode, even when i fastboot reboot and quickly unplug it. Just not sure where to go from here - it had 4.5.5.2 on it before all of this.
sunapeelakers said:
I flashed aboot 13, but the device never booted after I flashed that and twrp. I figured I could get into twrp since I had flashed it one step previous, but I cant. So i wiped it using fastboot -w thinking I could get rid of the aboot file, then flashed twrp again using fastboot flash recovery recovery.img, it ran through its thing and seemed to flash successfully, but I still cant boot to anything but a blank black screen. no logos or anything. It does respond to all the fastboot commands, of which I only know enough to be dangerous. I've tried changing the drivers around to get adb working to no avail. It seems to be stuck in fastboot mode, even when i fastboot reboot and quickly unplug it. Just not sure where to go from here - it had 4.5.5.2 on it before all of this.
Click to expand...
Click to collapse
Bulk mode and rebuild.
Davey126 said:
Bulk mode and rebuild.
Click to expand...
Click to collapse
Ok, I executed fastboot -i 0x1949 erase aboot and seemingly put the HDX into bulk mode - I can now see a bunch of disk drives on the computer, and it is now recognized as "other devices" "QHSUSB_BULK" in device manager. I still am unable to execute adb commands at this time.
sunapeelakers said:
Ok, I executed fastboot -i 0x1949 erase aboot and seemingly put the HDX into bulk mode - I can now see a bunch of disk drives on the computer, and it is now recognized as "other devices" "QHSUSB_BULK" in device manager. I still am unable to execute adb commands at this time.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post71430759
Davey126 said:
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post71430759
Click to expand...
Click to collapse
ok sick, I was able to execute those commands for aboot and twrp 3.1.1.1 and get the HDX booted into TWRP. now my issue is that I have nothing to install to get a system image going. Any suggestions on something safe?
Got slimrom installed and running 7.1.2 - awesome! Thanks so much for the help!