[Q] Bootloop / no adb / no fastboot

[Lemonilla]

So I was being stupid and I moved a system file... Which not surprisingly crashed it. When I rebooted, It started to flash the "Kindle Fire" logo for about 30-45 seconds before becoming a red triangle and telling me I should do a system restore, which did nothing.

I searched around and found that I needed to get into fastboot to flash my backed up copy of the partitions back on to undo what I did. So I ordered a cable off ebay, which arrived from china yesterday. Sadly, when I plug my kindle into my computer via this cable it does nothing. When I run any fastboot commands, they hang at "< waiting for device >".

Is there anything that I can do that might help? I plan on soldering my own cable tomorrow to see if that's the problem.

Additional information:
- OS: Windows 7
- Kindle Fire 2
- I changed a file in "/system/framework/framework-res.apk"
- Used Kindle FirstAide to make backups
- adb drivers don't show up in device manager

 

[stunts513]

You didn't see any devices with a yellow triangle next to them when the kindle is in fastboot mode? On wait your kindle never shows the fastboot logo?

Sent from my Amazon Kindle Fire HD using Tapatalk

 

[Lemonilla]

You didn't see any devices with a yellow triangle next to them when the kindle is in fastboot mode? On wait your kindle never shows the fastboot logo?

Sent from my Amazon Kindle Fire HD using Tapatalk

It never showed fastboot logo despite being plugged in with a factory cable. And no, the triangle was red.

 

[stunts513]

It never showed fastboot logo despite being plugged in with a factory cable. And no, the triangle was red.

sounds like a bad fastboot cable. i have heard horror stories of people buying them and then using them and having the usb port fried on the kindle, so i guess yours was the lucky side of a bad fastboot cable. Lately i think people have been going for this nice adapter i think hashcode mentioned in his post by blackhat or something, it goes between the microusb plugs on the kindle and cable. Feel free to make one though, thats usually pretty easy to do.

 

[Lemonilla]

Feel free to make one though, thats usually pretty easy to do.

One would think so. I managed to break the connection wire (the little one that goes into the micro_usb). Then while trying to solder to the broken stub, I wedged some molten solder to cross between ping 3 and 5's wires. I think I'll open up the one I bought for a second try. If that doesn't work I'll look into buying one of the adapters.

 

[Lemonilla]

So I finally found time to try making a new one with the Chinese one that they sent. You were right about it being a bad cable. I took it apart and it was missing pin 5 altogether. Where would you recommend buying one from? I saw a neat little adapter head somewhere, but don't want to buy another one that doesn't work. I've been looking at this one: shop. teamblackhat .info (won't let me post the link )

 

[stunts513]

If that's the one I'm thinking it is, its the same one hashcode mentions in his 2nd bootloader + twrp installation tutorial, I recommend it.

Sent from my Amazon Kindle Fire HD using Tapatalk

 

[Lemonilla]

If that's the one I'm thinking it is, its the same one hashcode mentions in his 2nd bootloader + twrp installation tutorial, I recommend it.

Sent from my Amazon Kindle Fire HD using Tapatalk

So it came in the mail, and it works. It flashes everything but system.img, which I believe it says is too large to flash. The problem is that I believe this is the partition that is messed up. Do you know how to bypass this?

C:\Users\Lemonilla\Documents\System Files\Backups\KindleBackup1>fastboot -i 0x19
49 flash system system.img
target reported max download size of 486539264 bytes
Invalid sparse file format at header magi
sending sparse 'system' (463367 KB)...
OKAY [ 10.661s]
writing 'system'...
FAILED (remote: : Sparsed Write)
finished. total time: 10.716s

 

[stunts513]

I'm guessing the system.img is just corrupt, I see it happen on occasion and it causes this error, try redownloading the system.img using kffa but I think kffa's links are down for its system images. Hopefully this situation isn't the same as a situation I'm having with someone else's kindle that is reporting that issue when it shouldn't be unless I make the actual partition smaller.

Sent from my Amazon Tate using Tapatalk

 

[Lemonilla]

It worked, now all I have to do is get it to find my router. Thanks a ton!


EDIT: For some reason it is not letting me enable Wi-Fi. Is this common, I can't find anything on it.

 

[stunts513]

Oh boy... Check to see if you can enable bluetooth

Sent from my Amazon Tate using Tapatalk

 

[Lemonilla]

Oh boy... Check to see if you can enable bluetooth

Sent from my Amazon Tate using Tapatalk

I managed to fix it. I re-flashed the system and downloaded the boot and launcher from kffa and flashed those over my backups as well and that seemed to fix it. Thank you so much for your help!

 

[stunts513]

OK glad to hear that that fixed it, I was worried it might be the boot0block, but thankfully it was not.

Sent from my Amazon Tate using Tapatalk

 

[Lemonilla]

It might have been, that is one of the one's that I flashed with kffa's files.

 

[stunts513]

The boot0block isn't flashed by kffa because its unique to every device, its basically the nvram with your serial number, WiFi mac address, Bluetooth mac address and such in it. You probably saw it flashing the bootimg (kernel + intramfs).

Sent from my Amazon Tate using Tapatalk