Kindle Fire HD 7 - Switches on then immediately off. - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Hi All,
My kindle fire hd 7 (Model number X43Z60) has I think gone completely caput.
Here are the symptoms:
When I plug it into the power supply (including connecting it to the computer) the kindle fire logo comes on and then it disappears (no 'ping' noises on windows to show it's connected).
So I spent most of today building a factory cable and succed and now can get it into fastboot mode, BUT this time the kindle logo comes on and then the fastboot logo and then it dies switches of again.
However I DO get the windows ping noise this time and windows does detect something. But it then switches off and disconnects from the PC.
Fortunately I have enough time to be able to flash boot.img and recovery.img (they are about 8kb so very small), but not enough time to flash system.img using the KFHD_SRTv1.3.5 tool.
Also just now I have managed to get usb id of the device that it comes up as, it comes up under device manager as Android ADB Interface with a usb id of 1949:0007
How can I fix this kindle? Why does it simply switch off after a few moments?

rash.m2k said:
Hi All,
My kindle fire hd 7 (Model number X43Z60) has I think gone completely caput.
Here are the symptoms:
When I plug it into the power supply (including connecting it to the computer) the kindle fire logo comes on and then it disappears (no 'ping' noises on windows to show it's connected).
So I spent most of today building a factory cable and succed and now can get it into fastboot mode, BUT this time the kindle logo comes on and then the fastboot logo and then it dies switches of again.
However I DO get the windows ping noise this time and windows does detect something. But it then switches off and disconnects from the PC.
Fortunately I have enough time to be able to flash boot.img and recovery.img (they are about 8kb so very small), but not enough time to flash system.img using the KFHD_SRTv1.3.5 tool.
Also just now I have managed to get usb id of the device that it comes up as, it comes up under device manager as Android ADB Interface with a usb id of 1949:0007
How can I fix this kindle? Why does it simply switch off after a few moments?
Click to expand...
Click to collapse
Seems you're looping. I would get another fastboot cord and make sure that's not the issue. A fastboot cord is suppose to keep the tablet energized. If it does not, then IO would inspect the USB port on the tablet for a loose soldier joint.

LinearEquation said:
Seems you're looping. I would get another fastboot cord and make sure that's not the issue. A fastboot cord is suppose to keep the tablet energized. If it does not, then IO would inspect the USB port on the tablet for a loose soldier joint.
Click to expand...
Click to collapse
I didn't have a 1k ohm resistor - do I actually need that between vcc and pin 4? I'll double check the cable now.

rash.m2k said:
I didn't have a 1k ohm resistor - do I actually need that between vcc and pin 4? I'll double check the cable now.
Click to expand...
Click to collapse
I didn't use one. http://forum.xda-developers.com/showthread.php?t=2207122 You may be dropping the voltage to much. Test the voltage output, should be 5 volts (think)

LinearEquation said:
I didn't use one. http://forum.xda-developers.com/showthread.php?t=2207122 You may be dropping the voltage to much. Test the voltage output, should be 5 volts (think)
Click to expand...
Click to collapse
Voltage appears fine, drops to 4.8 once the screen is on then jumps to about 5.05 - 5.20

rash.m2k said:
Voltage appears fine, drops to 4.8 once the screen is on then jumps to about 5.05 - 5.20
Click to expand...
Click to collapse
The Kindle should stay powered in fastboot as long as the voltage is present. If not, then there may be an issue with the USB port or something with the software.

LinearEquation said:
The Kindle should stay powered in fastboot as long as the voltage is present. If not, then there may be an issue with the USB port or something with the software.
Click to expand...
Click to collapse
I just removed all the connectors on the mobo once I removed the battery one and plugged in the charger it appears to power on (not fully) but I get a android recovery screen asking me to reboot or reset to defaults.
I think I just need to flash the system.img and then it should be fine.
One more question - why are there TWO system.img files in the KFHD_SRTv1.3.5.zip file from this thread:
http://forum.xda-developers.com/showthread.php?t=1951254

rash.m2k said:
I just removed all the connectors on the mobo once I removed the battery one and plugged in the charger it appears to power on (not fully) but I get a android recovery screen asking me to reboot or reset to defaults.
I think I just need to flash the system.img and then it should be fine.
One more question - why are there TWO system.img files in the KFHD_SRTv1.3.5.zip file from this thread:
http://forum.xda-developers.com/showthread.php?t=1951254
Click to expand...
Click to collapse
mobo? remove battery? You are using Kindle Fire HD 7 right?

LinearEquation said:
mobo? remove battery? You are using Kindle Fire HD 7 right?
Click to expand...
Click to collapse
Yes - I cracked the case open!
Anyway it's now fixed! The cable was a bit dodgy too one of the pins was being pushed back when I plugged it into the micro usb port!
Thanks for your help dude
For anyone else that sees this I basically following the following steps:
flashed boot.img
flashed recovery.img
flashed system.img
Using fastboot -i xxxxxx boot/recovery/system etc

fg
:laugh::laugh::laugh::laugh:

rash.m2k said:
Yes - I cracked the case open!
Anyway it's now fixed! The cable was a bit dodgy too one of the pins was being pushed back when I plugged it into the micro usb port!
Thanks for your help dude
For anyone else that sees this I basically following the following steps:
flashed boot.img
flashed recovery.img
flashed system.img
Using fastboot -i xxxxxx boot/recovery/system etc
Click to expand...
Click to collapse
Good to see it working. Yea, that happened when I slapped my first cord together too. Worked great until I plugged it in lol.

Related

fastboot screen when powered up

My kindle is rooted but I noticed when it's off and I connect charger into it it starts up then goes into fastboot screen......I have to shut off disconnect and boot up without cord being plugged in. Need to fix this.....any help is appreciated
You using a factory lead, by mistake?
When I do this happens
From box 13......
What do u mean factory lead?
south956 said:
What do u mean factory lead?
Click to expand...
Click to collapse
It's a cable that forces the Kindle into fastboot mode everytime when you power it on with it attached, that's it's purpose & can't be used for charging.
Some of them look just like a normal cable, I got one the other day & it doesn't look like the quality of the official Amazon cable but most unsuspecting users would just think it's a 3rd-party charging/data cable.
Gilly10 said:
It's a cable that forces the Kindle into fastboot mode everytime when you power it on with it attached, that's it's purpose & can't be used for charging.
Some of them look just like a normal cable, I got one the other day & it doesn't look like the quality of the official Amazon cable but most unsuspecting users would just think it's a 3rd-party charging/data cable.
Click to expand...
Click to collapse
Damn ok thanks it was an old Huawei charging cable

factory cable does not work

i connect kindle fire hd 7 and computer with a factory cable.
but it does not work.
I think maybe the bootloader is broken.
i tried to charge it , but no reaction.
Please help me.
thank you.
gogolovedell said:
i connect kindle fire hd 7 and computer with a factory cable.
but it does not work.
I think maybe the bootloader is broken.
i tried to charge it , but no reaction.
Please help me.
thank you.
Click to expand...
Click to collapse
I have almost the same problem, my Kindle loads "Kindle Fire" logo and does not go into fastboot by factory cable. It does not appear in the devices in w7x64 (adb drivers is installed).
I found a reason why didn't work fastboot - bad quality of cable. Try to make new.
You can check your wire,
Pin 1 should go to pin 4..
For a fast boot cable that's 5 volts to pin four
For an on the go cable I believe pin 4 goes to ground pin 5
I have to wonder if these poor cables we are hearing about are otg cables
Sent from my GT-P3110 using xda app-developers app

[Q] One more charging problem with Nexus 7?

Hello! After some experiments with POGO contacts on my Nexus 7 3G I have the following situation:
1. The normal USB-charging can not properly start. The battery state in the Settings menu eventually changes from Charging to Discharging and back, the battery level goes down as it is indeed discharging. If the tab is off, then the charging animation is not shown completely in an infinite loop.
2. No any connection can be established with a computer using USB cable. Windows 7 machines just ignore this connection without any traces. Windows XP machines repeatedly show warnings about a non-recognized usb device although all drivers were preinstalled.
3. If I put a USB-OTG cable into the tab (even if the cable is empty from other side) android shows that the battery is charging. Neththertheless, the tab in this state correctly recognizes flash drives as it did previously.
4. The POGO charging contacts are alive. The charging is normal. Moreover, this charging alllows to normally connect the tab to computer via USB cable.
I used the last feature to return to the stock ROM and to lock the bootloader, so the device is ready to go to service. But are there some chance to fix the problem by my own?
Thank you!
potzil said:
Hello! After some experiments with POGO contacts on my Nexus 7 3G I have the following situation:
1. The normal USB-charging can not properly start.
Click to expand...
Click to collapse
You'll have to say what you broke.. Did you hook the pins up wrong?
Yes,
khaytsus said:
You'll have to say what you broke.. Did you hook the pins up wrong?
Click to expand...
Click to collapse
It seems, yes, but it is very easy way to break:laugh:
No excuses for breaking it, I did not hook it up the wrong way for my GNex................
Beamed from my Maguro.

[Q] Amazon kindle stuck at logo even with fastboot usb cable

I have an Amazon Kindle Fire HD 7 inch tablet. I tried to install cm10 and it would only boot about every four tries so I decided to go back to the Amazon OS. After I flashed it back with the srt tool, it now only boots with kindle fire logo for about four seconds and blinks the logo again in a bootloop. I bought a usb fastboot cable. I bout the n2a cable that was recommended in the forum but it still boots the same thing while plugged in. Am I out of options? Thanks in advance.
I forgot to mention it's the kindle 2012 version.
daprospecta said:
I forgot to mention it's the kindle 2012 version.
Click to expand...
Click to collapse
Hold the power button for 30 seconds until it powers off. Now plug the Factbook cord into the tablet and now you USB port. The tablet should energize into Factbook mode automatically.
Sent From Kindle Fire HD 7 running CM 11 4.4.2
LinearEquation said:
Hold the power button for 30 seconds until it powers off. Now plug the Factbook cord into the tablet and now you USB port. The tablet should energize into Factbook mode automatically.
Sent From Kindle Fire HD 7 running CM 11 4.4.2
Click to expand...
Click to collapse
Thanks for the reply. That's what I've tried to no avail. I've even removed the back and unplugged the battery to make sure it was off. It turns on to the kindle fire logo even still. I have the motorola/kindle fire fast boot cable. I would purchase scoprn's cable but I don't want to waste my money if it's not the cable. The fast boot cable I bought was used by others users in this forum successfully. It's weird though, everyone seems to suggest that if it boots and is showing something then it's not bricked. I just don't what my options are at this point.
daprospecta said:
Thanks for the reply. That's what I've tried to no avail. I've even removed the back and unplugged the battery to make sure it was off. It turns on to the kindle fire logo even still. I have the motorola/kindle fire fast boot cable. I would purchase scoprn's cable but I don't want to waste my money if it's not the cable. The fast boot cable I bought was used by others users in this forum successfully. It's weird though, everyone seems to suggest that if it boots and is showing something then it's not bricked. I just don't what my options are at this point.
Click to expand...
Click to collapse
I recomend the adapter by blackhat i think hashcode has posted in his 2nd bootloader thread, goes in between a normal cable and the plug on the kindle.
stunts513 said:
I recomend the adapter by blackhat i think hashcode has posted in his 2nd bootloader thread, goes in between a normal cable and the plug on the kindle.
Click to expand...
Click to collapse
Thanks for the suggestion. That's the one I purchased over the weekend. Hope it works.

Not recognising USB connection

Hi Folks,
Have a 7th Gen Fire7, which is currently not recognising that it is connected to a PC or charger via USB. Multiple cables, PCs, and chargers tried. Also power banks. It's definitely a problem at the device end of the wire.
At start-up, if connected to a computer the PC recognises the device in preloader mode briefly, but as soon as the bootloader or OS starts, nothing. No change if I enable ADB mode on the device (either in the OS or TWRP).
Left it connected to power overnight and charge level didn't drop, but didn't increase either.
Current state: TRWP + Stock 5.6.4.0 - factory reset.
What led me here?
- Was working normally in 5.6.4.0
- Decided to try the Fire7 tool to remove some Amazon apps and reduce load/improve performance.
- Attempted rollback to 5.4, not realising this would brick a 5.6.4.x device
- Subsequently, in a preloader loop
- Used the 'short trick' and Linux scripts to load the hacked preloader, then fastboot a bootloader, the ADB sideload an OS (5.4)
- Relieved, and out of time for fiddling, decided to put it back to stock 5.6 (as noticed the Kids side was a better experience, and my boy will be using it in a week for a flight)
- Grabbed the .bin file from Amazon and flashed using TWRP (expected to lose that bootloader, but didn't)
That's when I noticed that it was no longer charging or communicating with a PC.
Since, I've been through various upgrades and downgrades, resets, wipes, etc, all to no avail.
I don't think it's hardware - I can't have damaged anything through the short process as else the fastboot/ADB piece wouldn't have worked after.
I note that it can't be powered off whilst plugged in anymore. It will immediately start up again.
All and any advice you can offer would be greatly appreciated, as I'm not entirely certain where to go from here.
Many thanks.
Regards,
Gavin.
gicarey said:
Hi Folks,
Have a 7th Gen Fire7, which is currently not recognising that it is connected to a PC or charger via USB. Multiple cables, PCs, and chargers tried. Also power banks. It's definitely a problem at the device end of the wire.
At start-up, if connected to a computer the PC recognises the device in preloader mode briefly, but as soon as the bootloader or OS starts, nothing. No change if I enable ADB mode on the device (either in the OS or TWRP).
Left it connected to power overnight and charge level didn't drop, but didn't increase either.
Current state: TRWP + Stock 5.6.4.0 - factory reset.
What led me here?
- Was working normally in 5.6.4.0
- Decided to try the Fire7 tool to remove some Amazon apps and reduce load/improve performance.
- Attempted rollback to 5.4, not realising this would brick a 5.6.4.x device
- Subsequently, in a preloader loop
- Used the 'short trick' and Linux scripts to load the hacked preloader, then fastboot a bootloader, the ADB sideload an OS (5.4)
- Relieved, and out of time for fiddling, decided to put it back to stock 5.6 (as noticed the Kids side was a better experience, and my boy will be using it in a week for a flight)
- Grabbed the .bin file from Amazon and flashed using TWRP (expected to lose that bootloader, but didn't)
That's when I noticed that it was no longer charging or communicating with a PC.
Since, I've been through various upgrades and downgrades, resets, wipes, etc, all to no avail.
I don't think it's hardware - I can't have damaged anything through the short process as else the fastboot/ADB piece wouldn't have worked after.
I note that it can't be powered off whilst plugged in anymore. It will immediately start up again.
All and any advice you can offer would be greatly appreciated, as I'm not entirely certain where to go from here.
Many thanks.
Regards,
Gavin.
Click to expand...
Click to collapse
Can you help to solve/troubleshoot the problem from USB connection on your Fire tablet:
-> Make sure you check the microUSB port for damages.
-> Make sure the USB voltage/current is 5V/1000mA (5.1V/2100mA is recommended).
-> If the USB cable is broken. Ues an another USB cable or buy a new one.
-> Try to use an USB voltmeter/ammeter or didn't have. Use a multimeter.
-> Make sure the USB cable wiring is correct polarity. See attached image on this post.
>> Can you help to solve/troubleshoot the problem from USB connection on your Fire tablet:
Thanks for replying. Yes, can confirm everything is fine on the supply-to-Kindle side of things (and, indeed, with the port on the Kindle). Specific answers below.
-> Make sure you check the microUSB port for damages.
Port definitely fine, opened the device to check, all solder points to the board are solid, pins undamaged, no fluff/etc
-> Make sure the USB voltage/current is 5V/1000mA (5.1V/2100mA is recommended).
Yep, charger output is fine. Multiple chargers used, this device has previous worked on this charger/cable, and another fire continues to do so
-> If the USB cable is broken. Ues an another USB cable or buy a new one.
Tried multiple known-good cables.
-> Try to use an USB voltmeter/ammeter or didn't have. Use a multimeter.
Voltage output is fine and stable, as is the current.
-> Make sure the USB cable wiring is correct polarity. See attached image on this post.
Yes, wiring is correct.
Looks to be a similar problem (and chain) to the ones experienced here: https://forum.xda-developers.com/showpost.php?p=78943209&postcount=200

Categories

Resources