Issue:
If your kindle fire is black brick after flashing firmware.The KF can not show any content.
for this case, the boot-loader is broken. It must be re-flashed again.
the usbboot must under linux environment such as ubuntu OS.
solution:
you can use usbboot tools with MOTO factory cable. below is the command.
SORRY, FOR this thing, I mistake the cable mode.The cable is KINDLE FIRE FACTORY CABLE. The cable mode is OTG
Code:
usbboot aboot.bin u-boot.bin
after flashing bootloader, the KF will boot up.
If you want to get the usbboot, please see the attachment.
updated post infomation:
The OMAP 4430 can boot from usb otg port.so,I think the usbboot programm can be used under normal usb cable or otg mode cable. but someone told me it must short one pin to the ground for booting.but I don't think so.
so, I just want to get one really black brick(no bootloader at all or bootloader broken). It's not battery empty case.because the battery is empty, the system is unstable.And you can find most problem. such as always restarting, always show fire logo or fastboot command can not operate.If you have battery empty case, please charge your battery use the normal cable.The charging period is about six hours.The charger must be 950ma charging current.Most problem can be solved!
If you have bootloader failed case,you can verify it. Really power off your KINDLE FIRE at first. second step is run the usbboot programm under ubuntu.and then plug in the normal usb cable or OTG MODE cable(USB ID pin short to ground) not factory cable.
additionally, I think most case it belong battery voltage is too low.Most interesting case is battery issue.If you KF battery voltage is less than 3.5v or less. using the factory cable just force power on and enter fastboot mode.NO other special function. If you KF battery voltage is 0v,then the PC usb port can support 5v 500ma MAX.The current can not support power on with the LCD. but The PCBA can be boot up without LCD by the usb port current.so, you must use the normal cable to charge you kindle fire at first.The second step is use factory cable to fix your kindle fire.it's important.
How to make an Ubuntu bootable USB stick
xiaohewu said:
you can use usbboot tools with MOTO factory cable. below is the command.
Code:
usbboot aboot.bin u-boot.bin
after flashing bootloader, the KF will boot up.
If you want to get the usbboot, please see the attachment.
Click to expand...
Click to collapse
You mean no short-trick? Correct me if I'm wrong but AFAIK, MOTO factory cable is just an ordinary one, and it only works if you have a valid bootloader.
linktohack said:
You mean no short-trick? Correct me if I'm wrong but AFAIK, MOTO factory cable is just an ordinary one, and it only works if you have a valid bootloader.
Click to expand...
Click to collapse
if the OMAP 4430 can not boot, You must be short the boot up pin to ground. you can use the moto factory cable to usbboot the correct bootloader.bin(flash it).Maybe normal cable do this,but i did not verify this things. I just use the factory cable to usbboot the bootloader.bin(flash it).
ur bootloader wasn't messes up, cuz a factory cable would not work unless ur bootloader was okay.
usbboot only works with shorting it with rear cover removed.
Sent from my HTC Glacier using xda premium
Did you try other factory cable? it's OTG mode. The Kindle fire boot under OTG mode.
smirkis said:
ur bootloader wasn't messes up, cuz a factory cable would not work unless ur bootloader was okay.
usbboot only works with shorting it with rear cover removed.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Thanks，I made a mistake.The topic name should kindle fire factory cable otg mode.How can i change it or delete？
xiaohewu said:
Did you try other factory cable? it's OTG mode. The Kindle fire boot under OTG mode.
Click to expand...
Click to collapse
Do you mean a REGULAR OTG Cable or a SPECIAL Kindle Fire OTG Cable with special pinout?
I have KF with broken bootloader, please tell me how to make this cable (if it a special cable)
so ur saying u can run usbboot with an otg cable?
Sent from my HTC Glacier using xda premium
The OMAP 4430 can boot from usb otg port.so,I think the usbboot programm can be used under normal usb cable or otg mode cable. but someone told me it must short one pin to the ground for booting.but I don't think so.
so, I just want to get one really black brick(no bootloader at all or bootloader broken). It's not battery empty case.because the battery is empty, the system is unstable.And you can find most problem. such as always restarting, always show fire logo or fastboot command can not operate.If you have battery empty case, please charge your battery use the normal cable.The charging period is about six hours.The charger must be 950ma charging current.Most problem can be solved!
If you have bootloader failed case,you can verify it. Really power off your KINDLE FIRE at first. second step is run the usbboot programm under ubuntu.and then plug in the normal usb cable or OTG MODE cable(USB ID pin short to ground) not factory cable.
additionally, I think most case it belong battery voltage is too low.Most interesting case is battery issue.If you KF battery voltage is less than 3.5v or less. using the factory cable just force power on and enter fastboot mode.NO other special function. If you KF battery voltage is 0v,then the PC usb port can support 5v 500ma MAX.The current can not support power on with the LCD. but The PCBA can be boot up without LCD by the usb port current.so, you must use the normal cable to charge you kindle fire at first.The second step is use factory cable to fix your kindle fire.it's important.
Related
I am able to get into bootloader. however, the problem is that whenever the USB cable is plugged in, the buttons don't navigate through the options. whenever the USB cable is NOT plugged in (and reboot bootloader) the button work just fine.
I don't have a recovery currently installed.
the issue is not with drivers on the computer or the usb cable...
happens while USB plugged in windows, linux or simply just plugged into a wall outlet to charge.
I need to get into fastboot but i'm having this issue with the bootloader (corrupted?).
any help would be appreciated.
bootloader version 3.34
nexus 7 (grouper)
It should work with the original cable, but other cables may or may not work. If you are using the original, try a different usb cable. Also, try other usb ports or another computer.
I was having an incredibly hard time flashing an image via fastboot, until I realized that my USB 3.1 GEN1 type A to type C cable didn't work well when plugged into a USB 3.0 port. I suppose it might have something to do with the N5X only supporting USB 2.0 or maybe it's a funky cable. I thought that I had indeed broken my phone on day 1.
At any rate, once I plugged it into a USB 2.0 port, fastboot is working just fine. I hope this saves someone from panic, crying, and the inevitable rage quiting.
I tried rooting and something failed and now my shield won't boot. I have downloaded the factory image from NVidia for the 16gb version I have, my question is how do I flash this though? Thank you
enigma7820 said:
I tried rooting and something failed and now my shield won't boot. I have downloaded the factory image from NVidia for the 16gb version I have, my question is how do I flash this though? Thank you
Click to expand...
Click to collapse
Have you opened Shield TV to see if there is header for serial console port? Nvidia Jetson TK1 and TX1 all have serial console port, you may be able to see boot loader messages from serial console.
Factory reset
enigma7820 said:
I tried rooting and something failed and now my shield won't boot. I have downloaded the factory image from NVidia for the 16gb version I have, my question is how do I flash this though? Thank you
Click to expand...
Click to collapse
When this happens, all you have to do is either plug it into a computer or certain android devices via otg cable ( for example: the original Shield). Disconnect the power on the Shield TV. Wait about 10 seconds or so. Plug the power back in. As soon as the light has been on for about 2 seconds, hold down the power button until the bootloader screen comes up. The stupid thing is that even if you don't need to get anything from anywhere else, your Shield TV still has to have another device plugged into it's micro usb port otg style in order to get to bootloader/recovery/forced recovery/factory reset and so on
Nixin Victis said:
When this happens, all you have to do is either plug it into a computer or certain android devices via otg cable ( for example: the original Shield). Disconnect the power on the Shield TV. Wait about 10 seconds or so. Plug the power back in. As soon as the light has been on for about 2 seconds, hold down the power button until the bootloader screen comes up. The stupid thing is that even if you don't need to get anything from anywhere else, your Shield TV still has to have another device plugged into it's micro usb port otg style in order to get to bootloader/recovery/forced recovery/factory reset and so on
Click to expand...
Click to collapse
This is very important hint for bootloader/recovery. I was wondering why I could not get to bootloader anymore when tried to dual boot Android and Linux, I forgot to plug the OTG cable to a PC.
Got myself a google LG Nexus 4.
Connecting via USB - 2 different cables, 2 computers, 3 different operating systems (archlinux, debian, windows vista ) - i get nothing (*).
the phone does not acknowledge that it is connected to a computer, but it charges ok.
the computers do not recognize the phone in any way, not even in dmesg (or device manager in windows).
i have tried changing options inside the phone (debugging on/off, mtp/ptp...), even a full factory reset, and going into recovery and wiping cache/dalvik cache. - nothing.
wiggling the cable and such does not help.
i even replaced the usb connector, no change whatsoever.
so something tells me that it is not a hardware problem.
the phone has been upgraded to android 5.0 (before i became the owner).
my endless searches show that nobody knows what's going on, it might be hardware fatigue, it might be related to the upgrade to 5.x, it might be a firmware problem...
any helpful pointers, including downgrading & softbricking the system would be helpful (i just want to install ubuntu phone onto it).
(*) my other android phone connects ok with both cables, to all machines and operating systems.
With the phone in fastboot or recovery mode, is it recognized?
The fact that the usb port has been changed could indicate a problem with the motherboard connector.
Go into device manager with your phone connected and uninstall the drivers. Then install "universal adb driver"(google it it's from Koush) with your phone NOT connected.
audit13 said:
With the phone in fastboot or recovery mode, is it recognized?
Click to expand...
Click to collapse
i tried adb, the device list is empty.
booting into recovery, replugging the usb cable, i still get nothing. it's like there's nothing to communicate to, both from the computer's and the phone's point of view.
i will have to play with fastboot (i gather it works only while the phone is booted into recovery?), but i doubt it'll change anything.
The fact that the usb port has been changed could indicate a problem with the motherboard connector.
Click to expand...
Click to collapse
do you mean the connector from the usb port, that flat cable snap-on thingy (far right on this image)?
is it realistic to try to fix that?
PS:
meanwhile the battery drained completely and i had a "Red light of death" which i managed to fix like this. i think it will take a while to recharge properly.
Adb commands will work with the phone booted into the rom. Use fastboot commands with the phone in fastboot mode.
Yes, the flat part at the it her end of the USB cable is what connects to the motherboard and is not worth fixing if that is causing the charging problem.
With a red LED, just connect it to a 2.0 amp charger using the original charging cable and let it charge for a few hours.
thanks again.
next thing i realized that the volume rocker isn't working (anymore?).
so i can't boot into recovery.
i don't know how, but once i managed to get into recovery, but couldn't make any choices in there.
anyhow, that sort of cinches it: i'm done with this phone. project failed.
(nevermind, it was a cheap ebay shot)
ubuntu phone will have to wait.
So long story short, I followed the initial tutorial to root the Fire HD 8 2018 (https://forum.xda-developers.com/hd8-hd10/general/tut-root-hd82018-via-magisk-t3906554/) after getting the mtk-su temp root. I made sure all the codes were correct before powering off my tablet, and everything seemed to be going smoothly until I ran the code on LInux to go into BootRom mode.
That was when the code was stuck on "Waiting for bootrom...". I connected my device to my PC, but the code didn't change at all. The USB also wasn't being recognized by the computer and was randomly being connected and disconnected. I'm not really sure what to do next as nobody else on the thread seemed to have my problem. I am a newbie, so please bare with me .
If anyone does have the solution, I'd be extremely grateful. Thanks in advance!
Is your tablet bricked as required by the guide? Or does it boot/show Amazon or fire logo?
If it is properly bricked, you could try a different USB port or cable.
If all else fails, your best bet is to follow the instructions in the original unlock/debrick thread:
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
Can you use the transferrable micro USB Cable?
I had the same issue with mine. I was getting the device showing in linux as a "mediatek" phone. When I plugged it, it would randomly connect and disconnect. finally it got recognized, and I ran into the BOOT0 broken issue mentioned elsewhere. I commented the != in the main.py first method to ==, and it flashed twrp correctly.
To avoid stuck in Waiting for bootrom...
Make sure your Fire tablet is shut down
Disable or uninstall the ModemManager
Use the transferrable micro USB cable
To short CLK to GND point using conductive objects. Do Not use the diode, capacitor or resistor to short the test point
USB access is enabled in VirtualBox settings