So I was trying to change my son's Fire 2 over to the new Kit Kat OS, and as I was downloading the necessary files to my computer, I thought I would wipe everything, since he had managed to pretty much fill it with junk, (he's 8). I have TWRP, (2.3.3.0) installed, and used that to wipe everything, including the internal storage and the format data wipe. I have done this with my Fire 1 with no issues, but this time I ran into a problem. TWRP works fine, but now windows won't recognize the tablet. When I go to mount the usb storage to copy the os files over, windows 7 cant load the device drives, and in my device manager it shows the Amazon Kindle fire 2 with the yellow exclamation mark next to it, saying that the drivers for this device are not installed. I have the SDK installed, and I have gone through and re installed the device drivers several times, and also uninstalled the kindle from the device list in manager. Nothing is working. I have attempted fastboot, but when I do try, it gets stuck at the "press the button menu" for TWRP, and after running the fastboot -i 0x1949 getvar product command, it tells me it sees an Otter2-Prod-04.
Does anybody have any ideas or suggestions on how I can get into the usb storage so I can load the OS info? Thanks for any help.
Dead?
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?
xanthian23 said:
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?
Click to expand...
Click to collapse
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen
mindmajick said:
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen
Click to expand...
Click to collapse
I have the standard cheap Kf2, no HD, just the upgrade from the first from last year, (2012), they were selling around Christmas last year. I have tried getting it to start back up, but with no success. I don't even understand why it shut down like that. I hadn't done anything to it other than reboot, which I had done successfully several times before. As for the fastboot, I may be incorrect. I ran the adb command: fastboot -i 0x1949 getvar product in CMD, and then plugged the kindle in and booted up. It showed it was an otter4 or something like that, which I thought meant it was in fastboot. At that time I was using my S4 usb cable. I'm sure I can sort out ho to sideload a rom via adb if I can ever get it started back up again. I had thought about opening it up and unplugging the battery and then re-plugging it back it to try to reset it, but I doubt it will help. Would getting a fastboot cable possibly make it start back up? If anyone has any suggestions on how I can get this thing started up again I would greatly appreciate it. I fell like crap for bricking my kids kindle, he's 8, so it's really important to him. It'll take me several months to save up to buy another one, so if I can get it running again, that would be awesome.
Here's a bit of an oddity, and maybe this spells some hope for me yet. So I plug the KF2 into the computer with the factory cable, hold down the power button for twenty seconds, let go, and then hit the power button again, for about a second, and windows makes the usb device plugged in sound, followed by a usb rejected or not recognized sound. It repeats this over and over for about thirty seconds or so and then stops. So there is something going on with the kindle, and its not flat out dead, or at least it seems. Is this a good sign? Does this help anyone to figure out what I might need to do?
So just to be sure that I was using a fastboot cable, even though I believe that my samsung s4 cable is fastboot capable, and I'm pretty sure I am using the factory cable, (it's not marked so I can't be 100% sure), I built my own fastboot cable, via instructions on how to do so on xda. (found HERE) It's doing the same thing with windows making the usb device inserted / recognized sound, followed by the usb device error sound. I'm guessing that this is a bad thing, am I correct?
One more bit of information to add to the list. I attempted to do the fastboot mode again,and decided to watch my device manager. Whenever windows chimes off that it detects a usb device, something called OMAP 4430 pops up for about a second before disappearing when the error sound comes on. I'm going to try and get a driver for that, just to see what happens. Maybe it'll help. I doubt it, but you never know until you try...
This just keeps getting weirder and weirder. So I installed the omap driver for windows and android, and now windows recognizes the device, but only for about a second. It just keeps cycling through the usb connected sound, recognizing the omap device, and then the usb disconnected sound, as though the device were being plugged in and then unplugged about every second for roughly thirty seconds. I'm starting to think there is something seriously wrong, which bites. If anyone has any suggestions, I'm all ears.
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
OK, I have both a tf - micro sd card usb card reader, and a full sd card usb card reader. I'll have to go digging for them in the morning, but I think I can find them. I'm also really good with a soldering iron, (used to be a vcr / tv repair technician), It took me roughly two minutes to do the homemade factory cable. So I am game, especially since at this point I really have nothing to loose by trying. Would you mind posting a link to where the tutorial is? I'm going to go looking for it, but just in case I can't find it, a link would help. And thank you so much for this suggestion!
OK, I found the tutorial on how to wire everything up and what's needed. I'll have to go get some small wire and a better tip for my iron, but aside form that, the wiring and soldering seems simple enough. My problem is going to be dealing with linux. I know Windows backwards and forwards, but I have a pretty limited knowledge of linux, aside from a few things we did in school to cover general PC repair. I can get it up an running, which I will do tomorrow, but I may need some help sorting out what to do with it once I have the board lined up and ready to roll, which will have to wait till next week when I get back from a work trip. Do you know if kurohyou offers repairs? If it's not too expensive, I would be willing to pay for the fix.
He might repair it, he just made a solderless repair tool to repair them. But like I said I'm more than willing to help with the Linux side, I'm a PC tech myself and use Linux primarily, you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
... you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Click to expand...
Click to collapse
Yeah, I've ran a live usb version of unbuntu a few times, and in the past I have had the full version on my system, but I rarely ever used it, so I got rid of it. I have an extra 600 gig's of space just sitting around on my laptop, so I will install a full version, and get off my lazy rear and start learning linux. This should be a good first lesson. I can't do any of this until next week though, so I will be pm'ing you once I've gotten everythig hooked up and ready to go. Thanks again for the help.
I had a question about the repair though. I went through the discussion, and I may have just missed it, but did he ever figure out how to get the OS up and running? From what I could tell, he was still working on it, and hadn't managed to get a working rom loaded. I probably just either missed it, or didn't understand one of the post's.
So I tried to migrate from CM to Lineage (which ive already done on my N5) and while formating my data due to encryption, my tablet is completely F'd in the A.
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank.
I ended up deleting all of the partitions but now i cant even see the device at all.
Since i cant get anyhting on the display and since i cant even get to fastboot, i have a feeling in screwed and need to go get a new board for it now... or just a new tablet i guess, but i rly liked my & and id hate to be w/o it over something stupid like this...
Can anybody else at least confirm or possibly have another idea?
I dont even get the charging animation with it off either...
carnagex420x said:
So I tried to migrate from CM to Lineage (which ive already done on my N5) and while formating my data due to encryption, my tablet is completely F'd in the A.
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank.
I ended up deleting all of the partitions but now i cant even see the device at all.
Since i cant get anyhting on the display and since i cant even get to fastboot, i have a feeling in screwed and need to go get a new board for it now... or just a new tablet i guess, but i rly liked my & and id hate to be w/o it over something stupid like this...
Can anybody else at least confirm or possibly have another idea?
I dont even get the charging animation with it off either...
Click to expand...
Click to collapse
Do you have ADB set up? if not, now may be a good time and through ADB try download a factory image.
carnagex420x said:
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank. I ended up deleting all of the partitions but now i cant even see the device at all.
Click to expand...
Click to collapse
Connect it to a PC again and check the USB mode your N7 is in.
If it is, or if you can make it work in, USB mode 9006 then follow this post. The linked N7 image is from my 32GB Hynix but you can use it to restore boot on any eMMC and adjust it later. While you do not see the partitions anymore, you may be able to access the device to restore the image.
If it is USB mode 9008 then your only recovery option is JTAG or hardware programming of the eMMC chip.
Good luck, it is still fixable :good:
the device still appears completly lifeless however i am able to get the device to show up as
Code:
Bus 002 Device 064: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
but im not sure how to go about getting fastboot yet, i get that i can dd an image to it i guess but im pretty sure i only have the 16GB not the 32, wjich i cant seem to find.
After playing with it for a couple hours and reading the entire Unbricking thread, the spot im stuck at now is the 9008-9006 mode switch. I have the QPST software and drivers working right and i get the NAK error but i follow the directions and cant get it into 9006 mode...
LineageOS update of May 24 2017 bricked my Nexus 7 2013 also.
Can't even use the Nexus Root Toolkit to recover. Always get stuck in the Google symbol.
Can enter into recovery, but it takes 15 minutes. And the directory structure showed is all empty.
Rebooting it show some errors saying that the partition table is empty.
"OEM Device Info" of NRT shows that the equipment is now locked also.
Have no idea of what to do. Can't even install the SO again.
There is a thread on "general" that seems to deal with related problems:
https://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495
ramon.hugo said:
LineageOS update of May 24 2017 bricked my Nexus 7 2013 also.
Can't even use the Nexus Root Toolkit to recover. Always get stuck in the Google symbol.
Can enter into recovery, but it takes 15 minutes. And the directory structure showed is all empty.
Rebooting it show some errors saying that the partition table is empty.
"OEM Device Info" of NRT shows that the equipment is now locked also.
Have no idea of what to do. Can't even install the SO again.
There is a thread on "general" that seems to deal with related problems:
https://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495
Click to expand...
Click to collapse
When you can boot into recovery you are good to go. Use a pendrive and an otg cable and flashthe rom from pendrive.
Already tried that ... Also impossible.
Try this way,
Connect to Computer
Use NRT then pess root, your Device will restart in TWRT then you can put the file in and reinstall.
You may be running into flash wear issues. This device is about 4 years old at this point, a similar thing started happening to the 2012 models. Don't blame the ROM, blame the NAND chip in your tablet.
I have a busted USB port so prefer to recharge via wireless. Sometimes wireless charging keeps disconnect and reconnecting if it's on so I need to shut it off.
I did that and now it just hangs at the Google screen as well.
If I hold Vol down I dont get twrp but the general bootloader. Any choice seems to just reboot it.
I think I'm screwed as well.
Prior to this my pc doesnt detect via USB at all, just charges it.
Hello and thank You for reading this!
I will get straight into it, I have a Nexus 5X (h791) in a what I would like to refer to as a semi-conscious state.
What I would like to do is to unbrick it and furthermore install a custom rom and I sincerely hope you all can help me with that.
So I have tried to unbrick my phone with LGUP (https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740) after I have not been successful with fastboot.
While following the guide I have noticed that my phone was not able to get into fastboot-mode anymore, still it was recognised by my PC as a qualcomm usb bulk device within the category of "other devices". I have already dealt with a similar issue in the past which was about getting the port right of a LG G3 marked as a unit within "ports" but with my LG G3 I was lucky to get it into a working state of download mode.
I have already tried to disable driver signature enforcement and re-installed everything as well but it did not work out yet. Also, my device seems to be alive as I can hear a steady noise when holding my ear next to the speakers. But still I cannot turn it off without fully draining the battery as it does not react to any buttons pressed except when I plug it into my PC with vol up.
tldr; I think my phone is recognised falsely (as qc bulk device rather than N5X) by my pc because i can't get into fastboot-mode properly. Any help or experience?
Please let me know if You have any more questions and thank You in advance
Bricked my phone as well with LGUP... Piece of trash software. Only shows up as qualcomm and does not react at all. I guess it is hard bricked and only way to fix it is with qualcomm software. Trying to find someone to help with it but out of luck: https://forum.xda-developers.com/nexus-5x/help/qualcomm-hs-usb-qdloader-9008-t3754397
hansschnee said:
Hello and thank You for reading this!
I will get straight into it, I have a Nexus 5X (h791) in a what I would like to refer to as a semi-conscious state.
What I would like to do is to unbrick it and furthermore install a custom rom and I sincerely hope you all can help me with that.
So I have tried to unbrick my phone with LGUP (https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740) after I have not been successful with fastboot.
While following the guide I have noticed that my phone was not able to get into fastboot-mode anymore, still it was recognised by my PC as a qualcomm usb bulk device within the category of "other devices". I have already dealt with a similar issue in the past which was about getting the port right of a LG G3 marked as a unit within "ports" but with my LG G3 I was lucky to get it into a working state of download mode.
I have already tried to disable driver signature enforcement and re-installed everything as well but it did not work out yet. Also, my device seems to be alive as I can hear a steady noise when holding my ear next to the speakers. But still I cannot turn it off without fully draining the battery as it does not react to any buttons pressed except when I plug it into my PC with vol up.
tldr; I think my phone is recognised falsely (as qc bulk device rather than N5X) by my pc because i can't get into fastboot-mode properly. Any help or experience?
Please let me know if You have any more questions and thank You in advance
Click to expand...
Click to collapse
Hello, and thanks in advance for for everyone's help (and patience if my post exasperates). This is my 4th OP phone and i've come to rely on MSM heavily as i tend to overflash ROMs etc. Although i've had issues (always evenutally resolved) in the past with getting MSM to restore, this is the first time i feel truly stymied. While playing around with TWRP i ended up having one of the A/B slots seemingly unrecoverable. Even during MSM it would get stuck on DSP.img. I eventually got fastboot to manually write that partition and i thought all was well. However during a flash of a custom ROM the phone crashed (i think t was an external event rather than related to my previous issues) in any event since that point the phone seems to be hard bricked. I can't get to the bootloader or the screen to come on at all. When plugged into Win 10 it is recognized and i can QDLoader 9008 to show up in the device manager. It even starts to work on MSM showing as connected when hitting enum. However after the initial "firehose download" it times out after 18-20 seconds. By unplug/replug etc i can sometimes get it go a bit father but then it stops at Param preload and will go no further.
Thoughts? Questions or detail i missed to help you help me?
re install the driver from device manager try dif port and cable.............
make sure no av shutting it down and good luck!
let me stress try a DIFFERENT PORT AND A DIFFERENT CABLE dunno how many times i can say that even if you got 3 cables go get a new one to rule it out also press hold power up 30 sec before you press hold to get in firehose
Install this on your pc Here. Add your device, use 8 PRO since 9 Pro isn't listed. Choose boot to EDL, and run MSM once your phone in EDL
Click the box to use lite firehose, then enum until it says connected, then start.
You said windows recognized it and so did msm
But I still gotta ask
Did you do the driver verification removal on the windows 10?
Also is it the right msm version/oos?
Use the original USB calbe, better if its a USB C TO A not to C as the C controllers on pcs are kind of weird with these kinda situations.
If you are using the same windows and drivers that worked on your old phones (Haven't formatted or uninstalled the drivers since) then nothing to be done here, but you have try to installing them with windows driver signature turned off. (Qualcomm drivers and oneplus drivers)
make sure the phone booted to EDL too.
These will solve 99% of msmtools problems usually.
try this
hello
Id like to have access to internal storage, connecting via USB doesnt work
phone fell and is dead, I only have a red led (not blinking)
do you know about any software that could grant me access to the phone?
thanks a lot
A data recovery specialist -might- be able to access it.
If you can repair the damage.
Otherwise the outlook is rather bleak.
thanks!
It's possible a connector was knocked off, so at least open it up and survey the damage before writing it off. Likewise if a daughter board like the jack port pcb was damaged a repair would be fairly easy and inexpensive.
thanks again, I'll try to find someone with the right hardware to check all this
dave_id said:
hello
Id like to have access to internal storage, connecting via USB doesnt work
phone fell and is dead, I only have a red led (not blinking)
do you know about any software that could grant me access to the phone?
thanks a lot
Click to expand...
Click to collapse
Hmmm, have you tried to put the device in edl mode? If yer not familiar with that, it's qualcomm's emergency download mode. There are lots of references to it in the 'guides' forum as it's used to root the device.
essentially, put it in edl mode, connect to pc and use qfil utility to save 'user data' partition. Mount that user data image, get what you need from it.
I don't have a device connected to edl / qfil in front of me, so the user data partition may not be in the partition list (don't remember), but there are some other utilities that might get it, that come with qfil. If not, use bkerler python edl utilities (find on github), I know for sure they can pull user data partition (it's very very big though, many many gigs).
cheers