Related
I rooted my lg on my computer, but I have not connected it since. Everytime I try, it says it does not recognize , that one of the USB devices has malfunctioned. I have installed the lg USB driver 3 different times and still can't get it, I have tried all 5 USB ports I have, same thing. Any ideas
Sent from my LG-E970 using xda app-developers app
I tried restoring to before my first lg driver install, reinstalled driver software, still same error
Sent from my LG-E970 using xda app-developers app
Have you uninstalled the drivers?
If not, with the phone plugged in, go to device manager, find the device, uninstall it, unplug and then replug in your phone.
Yes I did, I'm very computer literate. Turns out a cable can't tell you its bad, the original cable seem to be the problem. Probably why sometimes I get slow charge when plugged into the wall. All may be null and void when I attempt n4 conversion lol , wish me luck!
Sent from my LG-E970 using xda app-developers app
Good luck. I recommend having LGNPST prepped to revert to stock, with the DLLs and the BIN/TOT version of the LG ROM. AFAIK, that's the only way to get back, because of how extensive the N4 conversion is. Reverting with a ZIP ROM in CWM is unlikely to work.
Yah , I think I'm going to give up on trying, between the cable thing, now I can only talk to my phone through adb, fast boot won't seem to work. Plus I can't find a lgnpst guide anywhere for our phone. No idea where to get the DLL I'm supposed to flash with, nor where to get the files to flash back. This is my first lg, I've been a HTC guy, so I know nothing about lgnpst. Thanks though
Sent from my LG-E970 using xda app-developers app
ripbabey said:
Yah , I think I'm going to give up on trying, between the cable thing, now I can only talk to my phone through adb, fast boot won't seem to work. Plus I can't find a lgnpst guide anywhere for our phone. No idea where to get the DLL I'm supposed to flash with, nor where to get the files to flash back. This is my first lg, I've been a HTC guy, so I know nothing about lgnpst. Thanks though
Click to expand...
Click to collapse
The Windows 8 guide works (even if you're in Windows 7):
http://forum.xda-developers.com/showthread.php?t=2013067
Step 5 refers to a folder in a zip file that you get a link to in IRC.
When you go into irc an you !info lgnpst click on other versions and get phantomphreak53's
Click to expand...
Click to collapse
That's the #lg-optimus-g channel on Freenode.
Yes, the DLL refers to "LS970," but it works fine with the E970.
To obtain the files listed in the first four steps, I just Googled them and found Dropbox links.
The TOT/BIN file in question would be this one: http://forum.xda-developers.com/showthread.php?t=1984545
It will take a while to download; the server appears to average 100 KB/s.
As you can seee, it's kind of a pain to set up LGNPST's environment correctly. I recommend taking all of those files and backing them up to a secure location, so that you never need to hunt them down and re-download them again.
The guide also doesn't mention that your phone needs to be in Download Mode to interact with LGNPST. This is achieved by turning the phone off, plugging it into your computer with a USB cable, then holding down the power button and both volume buttons at the same time until the Download Mode indicator shows up on your screen. It may take several attempts; the process appears to have a low tolerance for poor button press timing.
LGNPST will interact with your phone even if Windows no longer recognizes it. I think that's why it remains popular as a last-resort recovery method.
ripbabey said:
Yah , I think I'm going to give up on trying, between the cable thing, now I can only talk to my phone through adb, fast boot won't seem to work. Plus I can't find a lgnpst guide anywhere for our phone. No idea where to get the DLL I'm supposed to flash with, nor where to get the files to flash back. This is my first lg, I've been a HTC guy, so I know nothing about lgnpst. Thanks though
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Everything you need is on Team Nocturnals website where the conversion thread is minus lgnpst and the nexus 4 drivers.
After you flash the n4 conversion, boot in recovery and then install the nexus 4 universal naked drivers (Google it, should be the first xda link.) Then you can use adb to fast boot -w and flash a recovery. Just read a little more and you'll realize its not hard at all. Just make sure everything is prepared. Good luck if you try it. It was very interesting to me. I've gone back to stock and came back to the conversion after the sdcard fix
Sent from my Nexus 4 using xda premium
Right now the problem I am having is getting windows to recognize my phone in boot loader/ fast boot which will prevent me from being able to fastboot -w , I have a thread on here should be titled fast boot and recovery. Posted it last night. I'm trying to make sure everything is ready, but my phone and my PC are just trying to fight me every which way lol. I'm going to try another computer and see if things run smoother, I have rooted and unlocked a bunch of phones for friends and myself on my laptop. Wondering if I'm just having a lot of driver conflicts lol
Its not about what you know , but who you know.
You might need to flash your recovery, and possibly lock your bootloader again. What I have seen over my several rooted phones is that sometimes when unlocking them, the binary code doesn't match up and will not allow the battery, USB port, and even screen to work with the software. Won't matter if you unistall or reinstall the drivers. Hope this help!
Sent from my HTC One V using xda premium
WizzyCreator said:
You might need to flash your recovery, and possibly lock your bootloader again. What I have seen over my several rooted phones is that sometimes when unlocking them, the binary code doesn't match up and will not allow the battery, USB port, and even screen to work with the software. Won't matter if you unistall or reinstall the drivers. Hope this help!
Sent from my HTC One V using xda premium
Click to expand...
Click to collapse
Which software are you describing? I have not lgnpst 'd anything yet, it does notice my phone both with phone on and connection settings to lg software, and in download mode. The problem I am currently stuck on is getting my PC to notice my phone in boot loader so I can't use any fb commands. I can talk to my phone when its on through adb commands no problem.
I dont want to get in trouble, the original problem was I could not get windows to notice my phone at all. I fixed that by trying a different USB cord, apparently my original is failing. If you would like to help me more so I don't get yelled at, please post in my other thread titled fast boot and recovery in the qa thread. I really want to attempt this, its my bday. So it would be a awesome little bday present to my flashaholic self
Its not about what you know , but who you know.
ripbabey said:
Yah , I think I'm going to give up on trying, between the cable thing, now I can only talk to my phone through adb, fast boot won't seem to work. Plus I can't find a lgnpst guide anywhere for our phone. No idea where to get the DLL I'm supposed to flash with, nor where to get the files to flash back. This is my first lg, I've been a HTC guy, so I know nothing about lgnpst. Thanks though
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Man how you using adb ? i wiped system by mistake and now i can access download mode recovery and i tried adb but my pc doesent recocgnize my device installed drivers and stuff and tried all the ports but nothing..so i can't use any tools right now to unbrick,,i can't flash because i have nothing on the internal memory also i'm on e975 i need adb to push a rom onto the sd card please help
I installed the root, then delete important system applications, and got brick device. Inscription appears only when loading "Kindle". Is there any way via fastboot (adb) to flash the stock firmware 13.3.1 (HDX 7")?
Sorry for my bad English.
I have same problem, we hope that you can solve
Have you tried factory reset via adb? It should work. http://forum.xda-developers.com/showthread.php?t=2530623
johnnydowngrief said:
Have you tried factory reset via adb? It should work. http://forum.xda-developers.com/showthread.php?t=2530623
Click to expand...
Click to collapse
does not work because getting stuck on the word "kindle fire" adb does not work for me most of installing the following drivers: http://i.imgur.com/jxq9EKI.png but does not work
sorry for by bad english t.t
This was a big problem with the last gen device. you will not be able unbrick your device until you get a backup of the system img then flash it through fastboot. or you could possibly pull a system image from the update.bin file from amazons kindle software page. I am downloading it now but do not own this device yet so no way of testing it. Also not sure if you can use a factory cable to get into fastboot on this model. anyone know or done this?
onemeila said:
This was a big problem with the last gen device. you will not be able unbrick your device until you get a backup of the system img then flash it through fastboot. or you could possibly pull a system image from the update.bin file from amazons kindle software page. I am downloading it now but do not own this device yet so no way of testing it. Also not sure if you can use a factory cable to get into fastboot on this model. anyone know or done this?
Click to expand...
Click to collapse
I'm bricked as well. The problem was that I got into recovery mode and did factory reset which was a bad idea. It totally killed adb and now I can't get pc to recognize at all. Therefore do no recommend factory reset to others.I have ordered the factory cable from the previous KF HD and will test to see if that works. If so I'll need someone to get a system.img to flash though.
I just talked to an amazon rep and will be sent a replacement. I wonder if they will notice it was rooted.
Does anyone know if an unrooted HDX will brick on factory reset and latest firmware?
Moronig said:
I just talked to an amazon rep and will be sent a replacement. I wonder if they will notice it was rooted.
Does anyone know if an unrooted HDX will brick on factory reset and latest firmware?
Click to expand...
Click to collapse
I will try and recover first as an experiment to also help others having same issues. Otherwise if I can't recover I'll contact Amazon as well.
Sent from my Nexus 5 using Tapatalk
Android Cowboy said:
I will try and recover first as an experiment to also help others having same issues. Otherwise if I can't recover I'll contact Amazon as well.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My brother has the hdx7. Ill see if I can pull a system.img from it when I see him. possibly tom. I'll pm you if I manage to get it done.
onemeila said:
My brother has the hdx7. Ill see if I can pull a system.img from it when I see him. possibly tom. I'll pm you if I manage to get it done.
Click to expand...
Click to collapse
Thanks. I'll work on getting ADB to recognize for now.
Android Cowboy said:
I will try and recover first as an experiment to also help others having same issues. Otherwise if I can't recover I'll contact Amazon as well.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The funny thing is that I deleted all apps I installed in /system/app before trying the factory reset (except superuser.apk and the su binary in /system/xbin. I had installed busybox before, so I'm suspecting that was what caused the problem with the factory reset. A different fdisk or something than the reset script expected... or maybe it does a checksum of some sort on the system partition and bricks it if it's not as expected?
Moronig said:
I just talked to an amazon rep and will be sent a replacement. I wonder if they will notice it was rooted.
Does anyone know if an unrooted HDX will brick on factory reset and latest firmware?
Click to expand...
Click to collapse
Amazon says they won't send me a replacement, so I'll see what else I can try. Let me know if you discover anything.
Moronig said:
Amazon says they won't send me a replacement, so I'll see what else I can try. Let me know if you discover anything.
Click to expand...
Click to collapse
I got one from the Amazon Ads free tablet promotion, and apparently i get no warrenty because it was a "gift". I'll order a factory cable and try poking around in fastboot. Has anyone tried a factory cable yet?
JordanRulz said:
I got one from the Amazon Ads free tablet promotion, and apparently i get no warrenty because it was a "gift". I'll order a factory cable and try poking around in fastboot. Has anyone tried a factory cable yet?
Click to expand...
Click to collapse
I don't think anyone has tried it, I'll try to find a cable I can cut and make one next week. I haven't had much experience with fastboot before, though. Should we be able to flash the /system partition from the latest update image?
Moronig said:
Amazon says they won't send me a replacement, so I'll see what else I can try. Let me know if you discover anything.
Click to expand...
Click to collapse
Why wouldn't they send you a replacement? Did you tell them it bricked while you were trying to root?
Major General said:
Why wouldn't they send you a replacement? Did you tell them it bricked while you were trying to root?
Click to expand...
Click to collapse
No, because I'm in Brazil and they don't sell this model of the Kindle to Brazil. I might try to get them to ship the replacement to my brother in the US.
Moronig said:
I don't think anyone has tried it, I'll try to find a cable I can cut and make one next week. I haven't had much experience with fastboot before, though. Should we be able to flash the /system partition from the latest update image?
Click to expand...
Click to collapse
I have a factory cable that I bought for kindle hd when i bricked that unit but sent the hd back before i ever used it.
I just powered off hdx 7 and plugged in cable but powers on as normal and its charging unit. Mine is rooted with google play not working of course..Is it suppose to boot into fastboot?
davekaz said:
I have a factory cable that I bought for kindle hd when i bricked that unit but sent the hd back before i ever used it.
I just powered off hdx 7 and plugged in cable but powers on as normal and its charging unit. Mine is rooted with google play not working of course..Is it suppose to boot into fastboot?
Click to expand...
Click to collapse
I thought so. Maybe if you hold either volume up, volume down, or both when plugging the cable?
Moronig said:
I thought so. Maybe if you hold either volume up, volume down, or both when plugging the cable?
Click to expand...
Click to collapse
I had wrong cable in sorry..I powered off kindle and plugged correct cable in and windows 7 asked for QHSUSB driver.and kindle stayed off as far as screen is concerned.I hunted down driver http://forum.xda-developers.com/showthread.php?t=1468791 I didnt try fastboot yet as I have a few things to do..Let me know if i could help as android cowboy is in same predicament and would like to help. After unplugged kindle boots up as normal after holding power for awhile
davekaz said:
I had wrong cable in sorry..I powered off kindle and plugged correct cable in and windows 7 asked for QHSUSB driver.and kindle stayed off as far as screen is concerned.I hunted down driver http://forum.xda-developers.com/showthread.php?t=1468791 I didnt try fastboot yet as I have a few things to do..Let me know if i could help as android cowboy is in same predicament and would like to help. After unplugged kindle boots up as normal after holding power for awhile
Click to expand...
Click to collapse
I will have the fastboot cable by tomorrow or Tuesday. Then I can test on my bricked Kindle if it goes into fastboot and if I still have root.
Sent from my Nexus 5 using Tapatalk
I and many others who have changed build.prop or other modifications after root then bricked have found that factory reset is the worst thing to do. It completely removed the PC from recognizing the tablet and ADB no longer works in any manner. Which pretty much means a total brick device. There is no real way to recover at the moment but if you have bricked with root then ADB should still be working. That still leaves some hope to fix the original damage. I have pulled the Amazon bin file and have access to original build.prop and system apk. That might allow some way to reverse the damage. I also have a fastboot cable coming to test if HDX will get into fastboot. For now hold off on any modifications after root since there is no real way to recover. But if you brick definitely don't factory reset.
Android Cowboy said:
I and many others who have changed build.prop or other modifications after root then bricked have found that factory reset is the worst thing to do. It completely removed the PC from recognizing the tablet and ADB no longer works in any manner. Which pretty much means a total brick device. There is no real way to recover at the moment but if you have bricked with root then ADB should still be working. That still leaves some hope to fix the original damage. I have pulled the Amazon bin file and have access to original build.prop and system apk. That might allow some way to reverse the damage. I also have a fastboot cable coming to test if HDX will get into fastboot. For now hold off on any modifications after root since there is no real way to recover. But if you brick definitely don't factory reset.
Click to expand...
Click to collapse
In Fastboot, It would be possible to recover if someone were to pull the system image and post it here on XDA.
r3pwn said:
In Fastboot, It would be possible to recover if someone were to pull the system image and post it here on XDA.
Click to expand...
Click to collapse
Yeah, we are desperate need of system image. I have the fastboot cable coming and new KF HDX being sent. If it's not done I should have it in a couple of days.
Android Cowboy said:
Yeah, we are desperate need of system image. I have the fastboot cable coming and new KF HDX being sent. If it's not done I should have it in a couple of days.
Click to expand...
Click to collapse
Has any progress been made on this? Unfortunately I didn't see your post until it was to late. Any assistance/advice would be much appreciated.
hi android cowboy plz help me
Android Cowboy said:
I and many others who have changed build.prop or other modifications after root then bricked have found that factory reset is the worst thing to do. It completely removed the PC from recognizing the tablet and ADB no longer works in any manner. Which pretty much means a total brick device. There is no real way to recover at the moment but if you have bricked with root then ADB should still be working. That still leaves some hope to fix the original damage. I have pulled the Amazon bin file and have access to original build.prop and system apk. That might allow some way to reverse the damage. I also have a fastboot cable coming to test if HDX will get into fastboot. For now hold off on any modifications after root since there is no real way to recover. But if you brick definitely don't factory reset.
Click to expand...
Click to collapse
My kindle hdx7" is bricked yesterday now only showing kindle fire boot logo so i have connected my laptop use factory.cable but not recognized my device would you help me? Sorry my poor english
bricked as well
cjdfyd2 said:
My kindle hdx7" is bricked yesterday now only showing kindle fire boot logo so i have connected my laptop use factory.cable but not recognized my device would you help me? Sorry my poor english
Click to expand...
Click to collapse
Same here Most likely going to return it which I really would rather not . But I went too far on that new Google play hack and it just booted up to welcome screen for google and never connected to servers and rebooted
after awhile.I did this on stock rom(bad bad) thinking it would be fine. Of course i reset to factory which everyone warned. Now just grey kindle logo and cable( Factory and non) to pc pulls up unrecognized usb that windows stopped from starting Done deal screwed im sure
davekaz said:
Same here Most likely going to return it which I really would rather not . But I went too far on that new Google play hack and it just booted up to welcome screen for google and never connected to servers and rebooted
after awhile.I did this on stock rom(bad bad) thinking it would be fine. Of course i reset to factory which everyone warned. Now just grey kindle logo and cable( Factory and non) to pc pulls up unrecognized usb that windows stopped from starting Done deal screwed im sure
Click to expand...
Click to collapse
I don't think anyone has figured out a recovery from this kind of brick. Safestrap is now the way to go. I had to get a replacement myself.
Sent from my Nexus 7 using Tapatalk
Android Cowboy said:
I don't think anyone has figured out a recovery from this kind of brick. Safestrap is now the way to go. I had to get a replacement myself.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Did the fastboot cable you ordered do anything?
daveman2123 said:
Did the fastboot cable you ordered do anything?
Click to expand...
Click to collapse
No I didn't have much luck with that either.
Sent from my Nexus 7 using Tapatalk
daveman2123 said:
Did the fastboot cable you ordered do anything?
Click to expand...
Click to collapse
it comes up as unrecognized usb device which windows stops
did you your device unbrick succese?
davekaz said:
it comes up as unrecognized usb device which windows stops
Click to expand...
Click to collapse
I had known your device.is.beicked right? Now yor device unbricked?
What happened was I was trying to root my kindle fire HDX with this thread. http://forum.xda-developers.com/showthread.php?t=2689121
I put in "adb reboot bootloader" and it was fine.
After, I put in "fastboot -i 0x1949 flash boot boot.img" and that's where stuff went downhill. Basically my kindle just got stuck at the kindle fire logo, where the kindle is "silver" and the "fire" is orange with the gradient of light going across it.
It was stuck on waiting for device for 10 minutes, so I shut it down by holding the power for 30 seconds and disconnected it.
Ever since then, when I restart the kindle, it just shows the kindle fire shining logo and that's it. I can't do anything else.
I'm very new to this kind of stuff, was doing this with the help of my friend, but now we're both stumped.
Any help would be really helpful. If I could factory reset, I would, so there's a lot of stuff I'm willing to do and part with the info on this kindle. I just want it to be working again.
Thank you for reading this and any help at all would be greatly appreciated!
Edit: Oh, and if it helps, I was running 14.3.2.2 instead of 14.3.2.1.
I didn't think it would make that big of a difference, but I definitely learned my lesson.
uberiyer1 said:
What happened was I was trying to root my kindle fire HDX with this thread. http://forum.xda-developers.com/showthread.php?t=2689121
I put in "adb reboot bootloader" and it was fine.
After, I put in "fastboot -i 0x1949 flash boot boot.img" and that's where stuff went downhill. Basically my kindle just got stuck at the kindle fire logo, where the kindle is "silver" and the "fire" is orange with the gradient of light going across it.
It was stuck on waiting for device for 10 minutes, so I shut it down by holding the power for 30 seconds and disconnected it.
Ever since then, when I restart the kindle, it just shows the kindle fire shining logo and that's it. I can't do anything else.
I'm very new to this kind of stuff, was doing this with the help of my friend, but now we're both stumped.
Any help would be really helpful. If I could factory reset, I would, so there's a lot of stuff I'm willing to do and part with the info on this kindle. I just want it to be working again.
Thank you for reading this and any help at all would be greatly appreciated!
Edit: Oh, and if it helps, I was running 14.3.2.2 instead of 14.3.2.1.
I didn't think it would make that big of a difference, but I definitely learned my lesson.
Click to expand...
Click to collapse
If you can reboot into the bootloader again, it might be worth it to try the same commands, but with the boot.img pulled from 14.3.2.2.
S_transform said:
... but with the boot.img pulled from 14.3.2.2.
Click to expand...
Click to collapse
I don't think this matters... if the HDX 8.9 is anything like the HDX 7, the boot.img file is identical in both the 13.3.2.1 and 13.3.2.2 versions. I did a binary-compare when 13.3.2.2 was released, and they're bit-for-bit identical. FYI.
[Edit] However, there is significant difference in the boot.img between versions 13.3.1.0 and 13.3.2.1. [/Edit]
tl3 said:
I don't think this matters... if the HDX 8.9 is anything like the HDX 7, the boot.img file is identical in both the 13.3.2.1 and 13.3.2.2 versions. I did a binary-compare when 13.3.2.2 was released, and they're bit-for-bit identical. FYI.
[Edit] However, there is significant difference in the boot.img between versions 13.3.1.0 and 13.3.2.1. [/Edit]
Click to expand...
Click to collapse
I was not aware, thanks for the heads up!
No, the root method in my thread unfortunately is non-working. I intended for boot.img to be flashed when the "fastboot" screen is showing. Unfortunately, the hdx does not go into fastboot like its sister device the HD 2013. Reading earlier posts in the thread would show you that it does not work.
But this is puzzling. Did you use a fastboot cable? If not then it was not my root method that bootlooped your device, and you should be able to get a replacement. If you DID use a factory cable, I can help you fix it.
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Mineturtle33 said:
No, the root method in my thread unfortunately is non-working. I intended for boot.img to be flashed when the "fastboot" screen is showing. Unfortunately, the hdx does not go into fastboot like its sister device the HD 2013. Reading earlier posts in the thread would show you that it does not work.
But this is puzzling. Did you use a fastboot cable? If not then it was not my root method that bootlooped your device, and you should be able to get a replacement. If you DID use a factory cable, I can help you fix it.
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Click to expand...
Click to collapse
how can you help fix with a fastboot cable??
jjrizzelcincy said:
how can you help fix with a fastboot cable??
Click to expand...
Click to collapse
Did you use a fastboot cable or not. If you didnt, it wasnot my root method that killed your device, and if you did, it still might not have been. It depends on whether the tablet's "fastboot" screen appeared when you used the cable. If so, i can help you recover it.
So...
•did you use a fastboot cable?
If yes
•did a fastboot screen pop up?
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Mineturtle33 said:
Did you use a fastboot cable or not. If you didnt, it wasnot my root method that killed your device, and if you did, it still might not have been. It depends on whether the tablet's "fastboot" screen appeared when you used the cable. If so, i can help you recover it.
So...
•did you use a fastboot cable?
If yes
•did a fastboot screen pop up?
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Click to expand...
Click to collapse
i am only asking how you might go about fixing his problem to learn something new about the device ,that is why i asked you how you would go about that with a fastboot cable your root method did not brick my device
jjrizzelcincy said:
i am only asking how you might go about fixing his problem to learn something new about the device ,that is why i asked you how you would go about that with a fastboot cable your root method did not brick my device
Click to expand...
Click to collapse
If you want me to fix it you need to answer the questions or I can't help you. I'm doing my best.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
If you want me to fix it you need to answer the questions or I can't help you. I'm doing my best.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
again i did not brick my device
using your root method
my device got bricked by an error in safestrap
i did a wipe data factory reset and this when i went to reflash the rom on the rom slot and it kept saying flash failed and that there were 0 mb on the sdcard i even pushed the rom back to the sdcard from adb but it would not flash and when i went to reboot it gave me a warning saying no os found or something like that so i tried and tried to make another rom slot and tried to restore a backup but it would not let me saying 0mb of storage available
so that's my story and now i dont have adb and im stuck at the gray kindle fire logo with only mtp showing but not fully installing but with a fastboot cable i got QHSUSB_BULK at first but after some booting over and over again i got it into QHSUSB_DLOAD with a driver installed on windows and i can see it connected to Linux as well with an id and everything in lsusb from a terminal that is about where my knowledge ends
but with the right devs we could get this working like the evo 3d and a bunch
of other HTC devices that were fixed that way and even get s-off through that QHSUSB_DLOAD mode but i dont have the knowledge to write something like that up or how to issue the proper commands in Linux or what partitions to write to or even the proper chmod to make so im stuck with a nice little paper weight as of now with no devs on board it's looking a bit grim for me
jjrizzelcincy said:
again i did not brick my device
using your root method
my device got bricked by an error in safestrap
i did a wipe data factory reset and this when i went to reflash the rom on the rom slot and it kept saying flash failed and that there were 0 mb on the sdcard i even pushed the rom back to the sdcard from adb but it would not flash and when i went to reboot it gave me a warning saying no os found or something like that so i tried and tried to make another rom slot and tried to restore a backup but it would not let me saying 0mb of storage available
so that's my story and now i dont have adb and im stuck at the gray kindle fire logo with only mtp showing but not fully installing but with a fastboot cable i got QHSUSB_BULK at first but after some booting over and over again i got it into QHSUSB_DLOAD with a driver installed on windows and i can see it connected to Linux as well with an id and everything in lsusb from a terminal that is about where my knowledge ends
but with the right devs we could get this working like the evo 3d and a bunch
of other HTC devices that were fixed that way and even get s-off through that QHSUSB_DLOAD mode but i dont have the knowledge to write something like that up or how to issue the proper commands in Linux or what partitions to write to or even the proper chmod to make so im stuck with a nice little paper weight as of now with no devs on board it's looking a bit grim for me
Click to expand...
Click to collapse
Oh my god I'm an idiot. I thought you were the op. *facepalm* sorry for the trouble.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
Oh my god I'm an idiot. I thought you were the op. *facepalm* sorry. For the trouble.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
NOPE you are stuck helping me now lol
jjrizzelcincy said:
NOPE you are stuck helping me now lol
Click to expand...
Click to collapse
I'll look into it. But as of now I'm a bit busy. Sorry.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
I'll look into it. But as of now I'm a bit busy. Sorry.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
the only way i see a fix for mine since the fastboot cable did not help me get into fastboot mode is if we some how manage to get some devs over here which seems unlikely at this point but i still have hope one falls on a devs lap sometime soon
So here's what happened.
About a year ago, I rooted my Kindle and flashed the latest CM rom (at the time). Everything worked out great.
Fast forward to a few days ago, I thought it'd be cool to give the KF an update. Total mistake. I wanted to flash CM 11, but before that, I figured it'd be important to install the latest version of TWRP as well, since that was also outdated. I downloaded the most recent img file, flashed it using the Flashify app, and before I knew it, my Kindle Fire was bricked. When I try to power it up now, it gets stuck on the "Kindle Fire" screen. I've tried holding the volume up button to boot into TWRP, to no avail. I can turn the device off, but as soon as I turn it on again, I get the same results.
I've tried using the Kindle Fire Unbrick Utility, but I get a "device not found" message. My computer makes a noise, as if to recognize the KF when it powers on, but within seconds, loses contact.
Any advice?
arthurk62 said:
So here's what happened.
About a year ago, I rooted my Kindle and flashed the latest CM rom (at the time). Everything worked out great.
Fast forward to a few days ago, I thought it'd be cool to give the KF an update. Total mistake. I wanted to flash CM 11, but before that, I figured it'd be important to install the latest version of TWRP as well, since that was also outdated. I downloaded the most recent img file, flashed it using the Flashify app, and before I knew it, my Kindle Fire was bricked. When I try to power it up now, it gets stuck on the "Kindle Fire" screen. I've tried holding the volume up button to boot into TWRP, to no avail. I can turn the device off, but as soon as I turn it on again, I get the same results.
I've tried using the Kindle Fire Unbrick Utility, but I get a "device not found" message. My computer makes a noise, as if to recognize the KF when it powers on, but within seconds, loses contact.
Any advice?
Click to expand...
Click to collapse
Please state your KF type: HD or HDX? Which FW you are on? Seems to me that you have HD version, and if you mistakenly followed instructions from this HDX forum for flashing TWRP ... ouch ...
my speculation is based on following:
About a year ago, I rooted my Kindle and flashed the latest CM rom (at the time). Everything worked out great.
Click to expand...
Click to collapse
About a year ago there was no CM rom for KF HDX - AFAIK.
jeryll said:
Please state your KF type: HD or HDX? Which FW you are on? Seems to me that you have HD version, and if you mistakenly followed instructions from this HDX forum for flashing TWRP ... ouch ...
my speculation is based on following:
About a year ago there was no CM rom for KF HDX - AFAIK.
Click to expand...
Click to collapse
My bad, I totally misread this forum. It's a Kindle Fire HD 8.9".
And I know I just made the mistake here, so it totally undermines what I'm about to say, but I do feel confident that I was paying attention to the model type when downloading the img file for TWRP. Either way, am I screwed?
Also, would you mind directing me to the forum for Kindle Fire HD's? I can't seem to find it on here.
arthurk62 said:
My bad, I totally misread this forum. It's a Kindle Fire HD 8.9".
And I know I just made the mistake here, so it totally undermines what I'm about to say, but I do feel confident that I was paying attention to the model type when downloading the img file for TWRP. Either way, am I screwed?
Also, would you mind directing me to the forum for Kindle Fire HD's? I can't seem to find it on here.
Click to expand...
Click to collapse
Well in case of HDX model you have 100% bad luck and something like this is unrecoverable for user AFAIK, but HD model is maybe recoverable, just ask for help, describe model, which FW you have, what you did, and hope some repair guru can help you ... good luck :good:
Here you go 8.9" Kindle Fire HD Q&A, Help & Troubleshooting
Or Kindle fire HD section
jeryll said:
Well in case of HDX model you have 100% bad luck and something like this is unrecoverable for user AFAIK, but HD model is maybe recoverable, just ask for help, describe model, which FW you have, what you did, and hope some repair guru can help you ... good luck :good:
Here you go 8.9" Kindle Fire HD Q&A, Help & Troubleshooting
Or Kindle fire HD section
Click to expand...
Click to collapse
I have a KFHDX 7 and now my KF is stuck in the grey " kindle fire" screen, I tried to fix it with adb code but my lap does not regonize it
Please help me
tuilakhang said:
I have a KFHDX 7 and now my KF is stuck in the grey " kindle fire" screen, I tried to fix it with adb code but my lap does not regonize it
Please help me
Click to expand...
Click to collapse
I read some of yours previous posts and I think you tryed install CM11 over your nexus 2.0.2 instalation. How did you install CM11 rom - with Safestrap or with TWRP 2.8.x.x?
If you did it with Safestrap, then there is nothing that you can do to repair it, unless you have working adb access to your kindle + root.
jeryll said:
I read some of yours previous posts and I think you tryed install CM11 over your nexus 2.0.2 instalation. How did you install CM11 rom - with Safestrap or with TWRP 2.8.x.x?
If you did it with Safestrap, then there is nothing that you can do to repair it, unless you have working adb access to your kindle + root.
Click to expand...
Click to collapse
Oh, now I get the point, you are right, I did it with Safestrap and don't know anything about TWRP.
Don't worry you must have flashed TWRP for the wrong kindle generation.
Connect your kindle to your pc with the normal cable that is provided with your kindle. Now turn your kindle off and type the following in your cmd
fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
then turn on your device
you should be in fastboot now.
From here follow this thread from step 2
forum.xda-developers.com/showthread.php?t=2128175
and why have you posted the same question twice
skullarc said:
Don't worry you must have flashed TWRP for the wrong kindle generation.
Connect your kindle to your pc with the normal cable that is provided with your kindle. Now turn your kindle off and type the following in your cmd
fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
then turn on your device
you should be in fastboot now.
From here follow this thread from step 2
forum.xda-developers.com/showthread.php?t=2128175
and why have you posted the same question twice
Click to expand...
Click to collapse
First, I sorry for this post cause I don't see anyone reply my thread, so I had searched in forum and see this this guy have the same issue with me.
And I still can't go to the fastboot mode with your advice, cause I can't turn the kindle off when I connect it with my pc, and my cmd just show < waiting for device >
tuilakhang said:
First, I sorry for this post cause I don't see anyone reply my thread, so I had searched in forum and see this this guy have the same issue with me.
And I still can't go to the fastboot mode with your advice, cause I can't turn the kindle off when I connect it with my pc, and my cmd just show < waiting for device >
Click to expand...
Click to collapse
your kindle does not have to be detected by your pc (at least at first) to perform this method you can switch it of then connect the cable and then run the command and then turn your kindle back on
skullarc said:
your kindle does not have to be detected by your pc (at least at first) to perform this method you can switch it of then connect the cable and then run the command and then turn your kindle back on
Click to expand...
Click to collapse
By the way I saw it, its auto turn on when I connect to pc, how can I connect my KF to pc and manual turn it on?
tuilakhang said:
By the way I saw it, its auto turn on when I connect to pc, how can I connect my KF to pc and manual turn it on?
Click to expand...
Click to collapse
then try putting the code first and then connect your kindle while its off
skullarc said:
then try putting the code first and then connect your kindle while its off
Click to expand...
Click to collapse
I tried that way too, but it's show the same result, I think the point is that my pc does not regonize my KF, I had tried to uninstall and install again the driver but it's not work
tuilakhang said:
I tried that way too, but it's show the same result, I think the point is that my pc does not regonize my KF, I had tried to uninstall and install again the driver but it's not work
Click to expand...
Click to collapse
try using this driver(use the first one)
skullarc said:
try using this driver(use the first one)
Click to expand...
Click to collapse
I sorry but how can I install your driver
I try to copy this to the driver folder of amazon in my C disk but its not works too
first right click on mtp usb device > click on update driver software > click on browse my computer for driver software > click on let me pick a list of driver form my computer > click on have disk > browse > select the file android_winusb.inf > Select the first option (before or after this it may ask for permission and say that the driver ins not signed just click ok) > click on next and the driver should be installed.
skullarc said:
first right click on mtp usb device > click on update driver software > click on browse my computer for driver software > click on let me pick a list of driver form my computer > click on have disk > browse > select the file android_winusb.inf > Select the first option (before or after this it may ask for permission and say that the driver ins not signed just click ok) > click on next and the driver should be installed.
Click to expand...
Click to collapse
Seem like its not work with win 64bit
which version of windows are you using ?
window 7 ultimate 64bit
sorry man i have to go now but i will be online again form 2:00 PM IST i will surely help you then
---------- Post added at 05:23 PM ---------- Previous post was at 05:19 PM ----------
tuilakhang said:
window 7 ultimate 64bit
Click to expand...
Click to collapse
try this
modify the android_winusb.inf file with this information. Notice the PID change from 0006 to 0008 on the newer model.