Related
It got bricked after trying to update through FLASHER 2.1 The ADB Shell on Sony AIO Tool not work. Option 6 Run Shell does nothing. Tablet gets stuck on the S.O.N.Y logo and I can enter the recovery screen, however no access through the USB to my files, already try the factory reset and still nothing. I would even consider installing the official firmware even if a lose root. I don't have the_hack_recovery.zip or any key. What can I do? I've been looking for solutions for over two days now.
I tried running the signed-nbx03_016-ota-120803071.zip and it didn't work, I'm looking everywhere for the signed-nbx03_001-ota-120803002.zip which should work for me, since my tablet was bought in the U.S. but it isn't available anywhere. I can't access the tablet through the ADB Shell, I press option 6 on the main menu and it does nothing. When I'm in the recovery mode I can see windows asking for drivers for a device named Sony, but none of the adb drivers work. If I go to the Sony logo I have it recognizes the MTP USB device and it looks ok for about 40 sec. and then it puts the yellow exclamation mark. I really need to get this tablet fix,
I'm willing to donate $40.00 through paypal to the person that helps me restore it.
You have to reinstall your firmware and wipe ure tab there is a thread on here that has all firmware from every country
Sent from my LT28i using xda app-developers app
psxpetey said:
You have to reinstall your firmware and wipe ure tab there is a thread on here that has all firmware from every country
Sent from my LT28i using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply, I already tried it with all the U.S. firmwares available in that threat. The one I think should work is the signed-nbx03_001-ota-120803002.zip and I can't find it anywhere.
elwarriorpr said:
It got bricked after trying to update through FLASHER 2.1 The ADB Shell on Sony AIO Tool not work. Option 6 Run Shell does nothing. Tablet gets stuck on the S.O.N.Y logo and I can enter the recovery screen, however no access through the USB to my files, already try the factory reset and still nothing. I would even consider installing the official firmware even if a lose root. I don't have the_hack_recovery.zip or any key. What can I do? I've been looking for solutions for over two days now.
I tried running the signed-nbx03_016-ota-120803071.zip and it didn't work, I'm looking everywhere for the signed-nbx03_001-ota-120803002.zip which should work for me, since my tablet was bought in the U.S. but it isn't available anywhere. I can't access the tablet through the ADB Shell, I press option 6 on the main menu and it does nothing. When I'm in the recovery mode I can see windows asking for drivers for a device named Sony, but none of the adb drivers work. If I go to the Sony logo I have it recognizes the MTP USB device and it looks ok for about 40 sec. and then it puts the yellow exclamation mark. I really need to get this tablet fix,
I'm willing to donate $40.00 through paypal to the person that helps me restore it.
Click to expand...
Click to collapse
I am uploading that file as i type. Since you have done a factory reset..... USB debugging would have reset to default (off) so even if you manage to install the drivers, USB debugging will NOT work.
I had the same (well similar) issue, it was stuck on the boot animation and although it was caused by different things I could not fix it and had to send it to Sony. Good news though, they did not noo I messed with it and repaired it free and IT SHOULD BE BACK TODAY
I feel this file is your only hope. I will reply when I have the link
Stifilz
Edit: Upload complete see here
DEL
stifilz said:
I am uploading that file as i type. Since you have done a factory reset..... USB debugging would have reset to default (off) so even if you manage to install the drivers, USB debugging will NOT work.
I had the same (well similar) issue, it was stuck on the boot animation and although it was caused by different things I could not fix it and had to send it to Sony. Good news though, they did not noo I messed with it and repaired it free and IT SHOULD BE BACK TODAY
I feel this file is your only hope. I will reply when I have the link
Stifilz
Edit: Upload complete see here
Click to expand...
Click to collapse
Thanks for your reply and for uploading the firmware. Unfortunately it didn't work either, I'll have to call sony and see if they can fix it for me. :crying: +Rep for the upload
elwarriorpr said:
Thanks for your reply and for uploading the firmware. Unfortunately it didn't work either, I'll have to call sony and see if they can fix it for me. :crying: +Rep for the upload
Click to expand...
Click to collapse
Sad to hear that. Do a couple of resets before you send in to Sony
elwarriorpr said:
Thanks for your reply and for uploading the firmware. Unfortunately it didn't work either, I'll have to call sony and see if they can fix it for me. :crying: +Rep for the upload
Click to expand...
Click to collapse
Just send to Sony, others have no ideas.
I also bricked it, and Sony restored it through motherboard replacing(free).
---------- Post added at 02:01 AM ---------- Previous post was at 01:57 AM ----------
stifilz said:
I am uploading that file as i type. Since you have done a factory reset..... USB debugging would have reset to default (off) so even if you manage to install the drivers, USB debugging will NOT work.
I had the same (well similar) issue, it was stuck on the boot animation and although it was caused by different things I could not fix it and had to send it to Sony. Good news though, they did not noo I messed with it and repaired it free and IT SHOULD BE BACK TODAY
I feel this file is your only hope. I will reply when I have the link
Stifilz
Edit: Upload complete see here
Click to expand...
Click to collapse
YES, only Sony can fix it.
I also faced the similar trouble one month ago.
And they free for me to replace the motherboard without any inquiries but my device's situations.
When they asked what I did, I said, nothing was done just suddenly can not boot, and force to restore the factory can't be solved the problem in the recovery mode. Okay! They said, just waiting less than 3 days. 3 days later, they sent a text message, and told me to pick up Tablet.
But a little guilt in my heart because I rooted my device and deleted a system file without rescue-backdoor.
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'm just wondering if you can completely Hard Brick a LG G2 to a point, where there is no revive possible.
I can purchase a cheap LG G2 international version, but the seller says that he broke it during flashing a Kernel.
Can you for example revive a phone,that had a Kernel from completely different phone flashed?
Any insight would be greatly appreciated.
Sent from my C6503 using Tapatalk 2
If it's true he only flashed a new kernel then u can restore it. If he messed with the partitions then.... No. If he used a broken usb cable and fried it....
Well ask to try the phone before u by it. Also check if it's stolen
Alright, I gathered some more information from the seller.
He tried updating TWRP, but he followed wrong instructions from some website.
He can´t enter Recovery or Download Mode on the Phone.
The Display is active, but only Backlight.
When he connects the Phone to his Computer, it shows multiple Mass Storages, but the LG Software doesn´t recognize it.
Is this a common problem, that is easy to fix, or should I rather wait for another Deal to come up.
p.s. I asked him for a receipt, and he says that he has one.
E-I-K-E said:
Alright, I gathered some more information from the seller.
He tried updating TWRP, but he followed wrong instructions from some website.
He can´t enter Recovery or Download Mode on the Phone.
The Display is active, but only Backlight.
When he connects the Phone to his Computer, it shows multiple Mass Storages, but the LG Software doesn´t recognize it.
Is this a common problem, that is easy to fix, or should I rather wait for another Deal to come up.
p.s. I asked him for a receipt, and he says that he has one.
Click to expand...
Click to collapse
If the guy was updating through TWRP, he probably have some knowledge on the matter, and the chances that he bricked it for good is high.
When I messed up my G2 a few times, being able to enter in download mode was the hint that the phone was revivable, if him really can't enter the download mode, then it is probably a bigger problem.
But the question is, by buying this possible lemon, how much will you be saving compared to buying a brand new?
If it's showing up like that, if you have a Linux machine you may be able to use dd to flash factory images to the partitions. There is a guide to it somewhere on here. But even if you were successful in flashing those, it really depends on how badly he screwed it up. In particular I really hope he didn't damage or wipe his efs. Or at least has it backed up.
Honestly, I'd point him to the right guides and have him fix it. If he screwed up his efs, or messed the partitions up, or fried something, it's dead and not coming back. If all he did was flash a kernel in twrp and it was actually from this phone and it was just a bad download or flash or something, then you'd probably be okay, but if that were the case you'd get a secure boot error and still be able to enter download mode. Personally, I would not buy a phone that won't boot, especially if the seller isn't even sure what's wrong with it.
Sent from my LG-G2 using Tapatalk
sounds recoverable, if there is a backlight and mass storage comes up that's good, you can dd partitions with linux
no backlight + no recognizable usb device at all = bricked
still, buy at your own risk
It is.. i just did by flashing a broken rom.. sent it to the repair center and they replaced the motherboard
Right, I asked him if the Device shows as qhsusb_bulk in device Manager, and it does.
The only thing that worries me, is that there is no Boot Logo, most of the people in the Linux Fix Thread atleast get a LG Logo and not just Backlight.
I´m really unsure what to do, I can save like 150€ by buying the broken G2, but well . . . I dont know if I can fix it.
Another problem is, that I have not a single clue on how to operate Linux/Ubuntu, and the only real fix requires either of those
E-I-K-E said:
Right, I asked him if the Device shows as qhsusb_bulk in device Manager, and it does.
The only thing that worries me, is that there is no Boot Logo, most of the people in the Linux Fix Thread atleast get a LG Logo and not just Backlight.
I´m really unsure what to do, I can save like 150€ by buying the broken G2, but well . . . I dont know if I can fix it.
Another problem is, that I have not a single clue on how to operate Linux/Ubuntu, and the only real fix requires either of those
Click to expand...
Click to collapse
Just look up a guide on how to install an Ubuntu virtual machine. You should be able to connect your G2 to that virtual if you let it capture the USB port. If you can get it cheap, buy it and try to negotiate so you might have a chance on selling it for higher later on if you can't fix it. To me though, it sounds quite fixable, I would go for it.
E-I-K-E said:
The only thing that worries me, is that there is no Boot Logo, most of the people in the Linux Fix Thread atleast get a LG Logo and not just Backlight.
Click to expand...
Click to collapse
this doesn't really matter, when I was trying to mess with the bootloader and corrupted it a few times I've never had the LG logo, as long as it comes up as storage you can DD it - the only time its a true brick is with no backlight and no usb device
if theres no boot logo you probably need to DD the aboot in
dr87 said:
this doesn't really matter, when I was trying to mess with the bootloader and corrupted it a few times I've never had the LG logo, as long as it comes up as storage you can DD it - the only time its a true brick is with no backlight and no usb device
if theres no boot logo you probably need to DD the aboot in
Click to expand...
Click to collapse
This.. If you have bulk mode, you can fix it!
kewkie said:
It is.. i just did by flashing a broken rom.. sent it to the repair center and they replaced the motherboard
Click to expand...
Click to collapse
That's actually just killing a fly with a sledgehammer. 99.9999% sure you got a softbrick.
Sent from my Moto G using XDA Premium 4 mobile app
Savoca said:
That's actually just killing a fly with a sledgehammer. 99.9999% sure you got a softbrick.
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Tried 3 different laptops
1x windows 8.1 (with ubuntu)
1x window 7 x64
1x windows 7 x86
Reinstalled all drivers, tried everything, but i couldnt get any usb connection.
- Factory reset? Freeze
- Normal boot? Stuck at bootlogo
- Download mode? Stucking at the loading screen
E-I-K-E said:
Alright, I gathered some more information from the seller.
He tried updating TWRP, but he followed wrong instructions from some website.
He can´t enter Recovery or Download Mode on the Phone.
The Display is active, but only Backlight.
Click to expand...
Click to collapse
I had that problem when updating TWRP too. You have to be careful because these recoveries are only made for specific firmware versions. I cant remember how I fixed the issue after only being able to get a backlight on and no image, but I did fix it and my phone works fine. I do think you will need the TWRP files already on the phone to fix though, so you can somehow manage to flash back. They will need to be on the phone since you can push anything via ADB
E-I-K-E said:
Right, I asked him if the Device shows as qhsusb_bulk in device Manager, and it does.
The only thing that worries me, is that there is no Boot Logo, most of the people in the Linux Fix Thread atleast get a LG Logo and not just Backlight.
I´m really unsure what to do, I can save like 150€ by buying the broken G2, but well . . . I dont know if I can fix it.
Another problem is, that I have not a single clue on how to operate Linux/Ubuntu, and the only real fix requires either of those
Click to expand...
Click to collapse
i've been in this bricked situation when i was trying the 4.4.2 update manually...completely bricked, could not get into download mode too...so gave it to the service centre which at first said the main board will have to be changed when recovering through software upgrade failed...next day i got the phone back as they managed to flash the software back on it...
does not end here...i tried to flash optimus g pro 2 rom through twrp and same thing happened again...but was lucky this time as i could enter download mode and flashed kdz to recover...
E-I-K-E said:
I'm just wondering if you can completely Hard Brick a LG G2 to a point, where there is no revive possible.
I can purchase a cheap LG G2 international version, but the seller says that he broke it during flashing a Kernel.
Can you for example revive a phone,that had a Kernel from completely different phone flashed?
Any insight would be greatly appreciated.
Sent from my C6503 using Tapatalk 2
Click to expand...
Click to collapse
And yes i truly believe that our device can be hard bricked like i did mine today.
I tried to compile a custom bootloader for G2 using Qualcom's sources and fraction of LK. But in doing so i left my phone in a quasi-state where it will not connect as a usb device coz it does not pass the bootloader (Although bootloader is working as it should). .
So the only two option remain here for me is
1. To send phone back to LG service center where they'll do idk what.
2. To use JTAG or short the ic (Wonder if it could be done ) i.e manually open the phone and boot into the primary bootloader(Qcom legacy BL).
See that's how you can hard brick ur phone the right way
fizzy177 said:
And yes i truly believe that our device can be hard bricked like i did mine today.
I tried to compile a custom bootloader for G2 using Qualcom's sources and fraction of LK. But in doing so i left my phone in a quasi-state where it will not connect as a usb device coz it does not pass the bootloader (Although bootloader is working as it should). .
So the only two option remain here for me is
1. To send phone back to LG service center where they'll do idk what.
2. To use JTAG or short the ic (Wonder if it could be done ) i.e manually open the phone and boot into the primary bootloader(Qcom legacy BL).
See that's how you can hard brick ur phone the right way
Click to expand...
Click to collapse
Your LK build wouldn't have matched the sbl1, anything other than LG's signed aboot wouldn't work.. /:
Sent from my Nexus 5 using XDA Premium 4 mobile app
Savoca said:
Your LK build wouldn't have matched the sbl1, anything other than LG's signed aboot wouldn't work.. /:
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
But it did work coz our bootloader enfoces the signature check not in the sbl.(Our Primary boot loader)
i'm sure of it because it tries to go to download option but freezes at initial stage.
had it been the case my device would've been detected as qucom_bulk device or so..
---------- Post added at 09:03 AM ---------- Previous post was at 08:58 AM ----------
kewkie said:
Tried 3 different laptops
1x windows 8.1 (with ubuntu)
1x window 7 x64
1x windows 7 x86
Reinstalled all drivers, tried everything, but i couldnt get any usb connection.
- Factory reset? Freeze
- Normal boot? Stuck at bootlogo
- Download mode? Stucking at the loading screen
Click to expand...
Click to collapse
You my dear friend are a victim of a curroupt bootloader seqence(NOT THE CoRRUPT BOOTLOADER) i.e
Your phone would start something like
1- EFI initialization ok
2-Primary Boot Load -ok
3-Vendor Boot Load -ok
4- Error unable to find proper boot sequence- system halted
So ur best options are the one that i've stated just above this thread.
My case. I root and flash custom recovery then apply OTA = medium brick. Download mode was not functioning, only recovery. To make matter worse, I flashed KK stock rom through ADB in recovery = super brick. Then I went to LG service center with poker face asked for reparation. They asked (confirm) whether your phone is rooted or not (they had already know though) and I just said like It is my sister's phone. Then they they open the phone and maybe directly format the sd card with some stuff. My phone is restored again afterward. In my opinion, software modification can always be repaired unless you fry your phone through overclock or overvolt.
ramabg said:
My case. I root and flash custom recovery then apply OTA = medium brick. Download mode was not functioning, only recovery. To make matter worse, I flashed KK stock rom through ADB in recovery = super brick. Then I went to LG service center with poker face asked for reparation. They asked (confirm) whether your phone is rooted or not (they had already know though) and I just said like It is my sister's phone. Then they they open the phone and maybe directly format the sd card with some stuff. My phone is restored again afterward. In my opinion, software modification can always be repaired unless you fry your phone through overclock or overvolt.
Click to expand...
Click to collapse
It's not a brick if it was restored... meh.
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
Title explains it all, although the way I bricked it is honestly the dumbest way to brick a phone. Once upon a time, when cleaning this phone to be ready to sell, I was wiping it to clean it. I wanted to make sure it was all clean for the buyer, so I wiped USB-OTG I believe it's called (literally all storage). I immediately realized what a mistake I had made when I had no ROM, no backups, nothing at all. What is my best bet to go about fixing this now? I can reboot to bootloader and enter fastboot, but it seems like something integral is missing, because my computer no longer recognizes my DNA as a device. I still have TWRP 2.8.0.2 on my device, but I can do nothing with it because I have nothing to flash. I know there is an ADB sideload feature, but I cannot figure that one out either. Someone please help me unbrick this phone :crying:
grimpow said:
Title explains it all, although the way I bricked it is honestly the dumbest way to brick a phone. Once upon a time, when cleaning this phone to be ready to sell, I was wiping it to clean it. I wanted to make sure it was all clean for the buyer, so I wiped USB-OTG I believe it's called (literally all storage). I immediately realized what a mistake I had made when I had no ROM, no backups, nothing at all. What is my best bet to go about fixing this now? I can reboot to bootloader and enter fastboot, but it seems like something integral is missing, because my computer no longer recognizes my DNA as a device. I still have TWRP 2.8.0.2 on my device, but I can do nothing with it because I have nothing to flash. I know there is an ADB sideload feature, but I cannot figure that one out either. Someone please help me unbrick this phone :crying:
Click to expand...
Click to collapse
Boot to recovery
adb push NameOfRom.zip /sdcard
Flash rom
Sent from my HTC6535LVW using Tapatalk
grimpow said:
Title explains it all, although the way I bricked it is honestly the dumbest way to brick a phone. Once upon a time, when cleaning this phone to be ready to sell, I was wiping it to clean it. I wanted to make sure it was all clean for the buyer, so I wiped USB-OTG I believe it's called (literally all storage). I immediately realized what a mistake I had made when I had no ROM, no backups, nothing at all. What is my best bet to go about fixing this now? I can reboot to bootloader and enter fastboot, but it seems like something integral is missing, because my computer no longer recognizes my DNA as a device. I still have TWRP 2.8.0.2 on my device, but I can do nothing with it because I have nothing to flash. I know there is an ADB sideload feature, but I cannot figure that one out either. Someone please help me unbrick this phone :crying:
Click to expand...
Click to collapse
Did you ever get your issue resolved?
santod040 said:
Boot to recovery
adb push NameOfRom.zip /sdcard
Flash rom
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
That was my plan, but the problem is that ever since accidentally wiping everything, my device will not be recognized.
Code:
adb devices
returns that no devices are connected.
strabo231 said:
Did you ever get your issue resolved?
Click to expand...
Click to collapse
Not yet. I'm still stuck trying to get my computer (or any computer for that matter) to recognize my device, but no luck. I'm afraid I've permanently bricked this thing.
grimpow said:
That was my plan, but the problem is that ever since accidentally wiping everything, my device will not be recognized.
Code:
adb devices
returns that no devices are connected.
Not yet. I'm still stuck trying to get my computer (or any computer for that matter) to recognize my device, but no luck. I'm afraid I've permanently bricked this thing.
Click to expand...
Click to collapse
Go into the bootloader and select fastboot. fastboot devices
strabo231 said:
Go into the bootloader and select fastboot. fastboot devices
Click to expand...
Click to collapse
Same problem, won't show up under devices. It's as if I deleted something essential to being recognized as an android device.
grimpow said:
Same problem, won't show up under devices. It's as if I deleted something essential to being recognized as an android device.
Click to expand...
Click to collapse
Kinda doubtful. I do see a usb communication issue though. You say you've tried this on several computers, and I'm assuming they weren't all yours, which leads me to believe that you have been missing drivers. From what you've described I highly doubt the connection issue is stemming from something you deleted off the phone. The DNA is almost impossible to brick to the point of not being able to get it back.
Go here and get HTC Sync. This will ensure that you have all the updated drivers including the proper fastboot drivers. Install the program, and then reboot after installation completes.
http://www.htc.com/us/support/software/htc-sync-manager.aspx
From here you'll want to go in and uninstall it. This will remove the program, which has been known to cause usb connection/communication issues with rooting procedures, but it will leave the drivers behind. Once that completes, restart again. This should fix your fastboot problem. I've had the same problem after reformatting computers and then trying to simply download a driver pack rather than htc sync.
Also be sure to try different usb ports. Sometimes the ones in the front or side will cause problems, but the ones in the back or on the other side work just fine.
If all else fails, mail it to me and i'll fix it for you :good:
Bricked phone, no usb
My dna droid stopped working, loaded htc sync and revoot but still not seen by explorer or adb. Suggestions appreciated.