yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] pokey9000:
Yes, it does, but it would take some soldering and more than shorting just one pin. Also we haven't identified all the boot mode pins.
[Kindle Fire Android Development] pokey9000:
Not silly, I've tried to get usbboot to work on Windows when I developed a Nook Color version, but the Windows USB stack sucks. If it were to work, it would piggyback on either libusb or the Google USB driver, either of which have 32 and 64 bit versions. Windows gurus are welcome to lend a hand.
[Kindle Fire Android Development] mikbe.tk:
Stuck on Kindle...

I have the 6.2.1 update so tried this.

I followed the instructions but when I `fastboot reboot` the screen goes black. When I power it down manually and then turn it back on it hangs on the initial Kindle boot screen, it never gets to the animated Kindle boot screen.

# ./usbboot aboot.bin u-boot.bin; fastboot flash boot 6_2_1rootboot.img
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
< waiting for device >
sending 'boot' (3234 KB)...
OKAY [ 0.814s]
writing 'boot'...
OKAY [ 1.155s]
finished. total time: 1.969s
MintBookPro kindle # fastboot reboot
rebooting...

finished. total time: 0.001s
#

I noticed the fastboot command didn't have ./ in front of it so tried that with the same results, it just hung on the Kindle boot screen.

Out of curiosity I tried the TWRP image and that worked so I was able to install the full rooted 6.2.1 (not just the boot image) from TWRP and now I have 6.2.1 rooted.

So I don't think there was anything wrong with your app, that seemed to work fine, but the plain 6.2.1 boot image seems not to work. Which isn't your issue but anyone that tries this needs to be aware of it.
[Kindle Fire Android Development] kfuller:
Great work pokey9000! Very interesting what you are doing.

A couple of questions if you can spare the time.

1) What bootmode is it that shorting the pin enables?

2) As I have a factory cable, would this do the same without popping the case?

Also, and this is off topic and possibly already asked and answered, but I'm curious of your thoughts of the possibility to just select boot from usb on power up from the device, maybe through a utility such as TWRP or some other. Seems that if that could be done, one could greatly increase the size of storage, effectively circumventing the current internal storage limitation. And since the usb is removable and rewritable, you could revert to an earlier version archived on a pc if any updates get pushed that break something.
[Kindle Fire Android Development] pokey9000:
Corrected my directions to hard power off. Reason is that the boot mode gets detected on cold reset, and the reboot warm resets and so doesn't detect the new bootmode. I suppose we could add something to override the boot mode when you call reboot if it detects that USB is the boot device. Code is already there to do something similar with bootmode 4003.

My bad, fixed.

Don't know about this, these directions were created w/o a Fire in my possession. I'll make a note in the OP to try the TWRP method.
[Kindle Fire Android Development] pokey9000:
Thanks. This bootmode isn't the same as you set with "idme". This boot mode (called SYS_BOOT) tells the CPU what kind of device to boot from. Stock bootmode is SYS_BOOT[5:0]=0b110110 which equates to MMC2(1)->USB->UART->MMC1. That is, it will try to find a valid bootloader on internal flash, then try USB, UART, and (nonexistant) second eMMC/SD slot. This must be for factory programming, where the Fire is assembled with a blank flash, and the first boot allows them to do a USB boot to shoehorn in the flash contents.

In correction to what I said earlier, this SYS_BOOT is one bit away from having USB boot first, then MMC2(1) boot last. If we could identify SYS_BOOT[5] and short it low permanently (remove/replace a resistor) then this would boot up just like the Nooks, where USB is tried before the internal flash. So it still needs soldering, but only a little once we find the correct signal.

The factory cable doesn't do the same thing. Amazon's version of the bootloader is rigged to look for the fastboot cable's presence. If it sees the ID pin tied to 5V, it will go into fastboot mode.

Since the fastboot cable behavior is in the bootloader, and Amazon can update the bootloader with an update (and has in 6.2 and 6.2.1), they can potentially lock out the fastboot cable method. I very much doubt this will happen since I think Amazon uses the fastboot cable for in-factory software updates and diagnostics.

The fastboot cable is definitely safer as long as you don't try to format everything or flash any untested bootloaders.

USB in this case has the Fire acting as a USB device to a host PC. It won't boot off of a thumb drive or whatever. It would be great if that were the case...
[Kindle Fire Android Development] iDylan1357:
thanks so much man. I was switching between CM7 and Stock for a while, but I think I'm sticking with CM7 for now on, til ICS alpha of course ;)
[Kindle Fire Android Development] kfuller:
I appreciate the reply. Its tough to stay current and these days seems most everything is software. I hesitate to ask questions here as I'm not code level, though I have surface knowledge due to management of a custom integration project with linux and asterisk at work. My forte and training is more on the hardware side, so no problem with SMD (other than needing magnification and hands less steady as I've gotten older ). Sounds like you have that covered but if I can help let me know.

Your original post and your reply both have piqued my curiosity. Ubuntu 11.10 on a stick is sweet by the way! Makes me wonder why windows at all. And, this may be the answer to finally de-bricking my Fire - just as soon as I get all the presents wrapped :).

As for needing a usb host, check out this link: http://www.talkandroid.com/73692-an...oid-2-3-squeezed-onto-usb-stick/#.TvUHXXqQJIw

Thanks again and have a merry Christmas.
[Kindle Fire Android Development] pokey9000:
Thanks, I'm all set on the SMD front. I've got access to some nice rework equipment at work if I need it. It looks like each signal to strap the CPU into a different boot mode is flanked by pads for either pullup or pulldown, so to change the value you just move the resistor (or wire jumper) from one side to the other.

If only it were that easy... The stage of the boot that's being controlled by shorting the pin is managed by software permanently baked into the CPU. We get a selection of boot sources (various flash, external SD card, USB device mode, serial) but we can't add a new one after the fact. Because this is hardcoded into the CPU, Amazon can't take this boot & install scheme from us unless they start making Fires with the relevant signals buried in the PCB.

The hardware is there to do USB host, but it's not really possible to boot from it.
[Kindle Fire Android Development] mrpaint:
Sorry for replying to this old thread but I couldn't find a more relevant thread so please bear with me (and help me!).

So today I stupidly flashed .zip as the bootloader so the KF has become a brick. I remove the back cover wanting to try the shorting trick but there no usbboot for Mac OSX so I cloned your repo and pulled this commit (https://github.com/cfriedt/omap4boot/commit/7e6ccff81be0171c651595ce5c69b9571f3a133a) and successfully compiled for darwin. Then I tried

./usbboot aboot.bin u-boot.bin

usbboot and aboot.bin is my compiled version

u-boot.bin is the one in this thread's first post .zip package

This is the output

waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...

I also noticed the power led flashed green once. Then I tried fastboot to no avail... Can you help? I did the shorting trick for 5 times and it all ended up the same way.

Thank you.
[Kindle Fire Android Development] pokey9000:
Use the usbboot you compiled with my aboot. aboot contains device specific memory and I/O setup.
[Kindle Fire Android Development] bsoplinger:
If you get this working with the help suggested, would you please post the Mac OSX usbboot you're created? Then I won't need to get Linux working to try to fix my bricked Kindle.

Sent from my Sprint Evo View 4G (PG41200) using Xparent Purple Tapatalk 2
[Kindle Fire Android Development] mrpaint:
Thank you for your reply. I have been away for the last few days so I couldn't response earlier.

Anyway, I tried with your aboot.bin and got the same "sending image to target" message. After that, I tried "fastboot boot twrp-blaze-2.0.0RC0.img" to no avail (I have fastboot in my PATH). The power led shines for 1 seconds (when the usbboot connects to it I think) before turning off...

Do you have any idea?

---------- Post added at 04:52 PM ---------- Previous post was at 04:42 PM ----------

It doesn't work for me yet but you can get my compiled version here

https://github.com/downloads/daohoangson/omap4boot/usbboot

Good luck.
[Kindle Fire Android Development] bsoplinger:
If you get that MacOS port working I'll be all over it.

But until then, can this be done with a live CD vs. a full blown Linux install?

Sent from my Sprint Evo View 4G (PG41200) using Xparent Purple Tapatalk 2
[Kindle Fire Android Development] smirkis:
u can do it with a thumb drive install.
[Kindle Fire Android Development] lovejoy777:
i tried allsorts and now find it easy i've done it so many times. lol

follow the steps exactly

download pendrive installer

follow instructions to install livecd onto pendrive (i tried this so much with my ubuntu desktop, it did not work)

extract the fk script to the pen drive

boot pc of usbpen

make sure your kindle is off (hold power for 30 seconds)

make sure usb A (big end) plugged into pc

make sure usb b (small end) is not plugged into kindle)

open terminal and type

sudo /cdrom/fk and press enter.

select option from list ie. usb_fix press tab

then press enter

it should say waiting for omap device

short out pin and frame and keep it shorted as you plug in your kindle (i found i had to hold the pin shorted all the time it was running script).

hope this is usefull

steve
[Kindle Fire Android Development] westlandnick:
So I also made the mistake of flashing the firefirefire as a zip and bricked my kf. I have a adb to kindle working ubuntu computer, I have tried shorting the pin several times and I'm getting nothing... In my terminal I have:

nick@ftp:~/rekindle$ sudo ./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp.img

[sudo] password for nick:

?

waiting for OMAP44xx device...

^C< waiting for device >

When I short the pin and plug it in I get nothing... I've tried holding the pin for several seconds after plugged in.. I'm getting nothing. After I bricked the KF I left it sitting for about a week. Is it possible I drained the battery? Will it not charge when its bricked? I plugged it in for a few hours, tried again, still nothing.

Any suggestions??

---Edit---

I finally got the usb-shorting trick to work with the fire kit, For anyone else in this situation just keep trying. I probably shorted mine at least 50 times before it finally worked.
[Kindle Fire Android Development] assasukasse:
insted of opening the difficult case what about drilling a small hole that allows a tool to get tru and short?

Does anyone have a case open to take precise measurements?
[Kindle Fire Android Development] soupmagnet:
Bad idea. It's too easy to create an ESD and ruin some component. Then you would have to deal with dust, dirt, and possibly even moisture getting in. It's best to just open the case.

Oh, and use a safety pin for the short ;)
[Kindle Fire Android Development] Sblood86:
Just thought I'd mention (in case someone hasn't) guitar picks are particularly helpful when opening cases.
[Kindle Fire Android Development] piercedfreak:
ok, so i finally got it to work, but cant seem to install anything. twrp is installed via fastboot, and the kindle is in recovery, so fastboot will not work, and when i try to install a rom via the booted twrp it fails. what should i do?
[Kindle Fire Android Development] sd_shadow:
Think you just need a fastboot cable, and a pc with drivers installed properly

Or use soupkit on a linux system
[Kindle Fire Android Development] poshat:
Same problem with Huawei U9500 (omap4440)

Have same problem with Huawei Ascend D1 (U9500) - OMAP4440 SoC. I lost bootloader, can't boot and flash firmware. May be somebody advice me something about way to repair bootloader? I tried find "short the point" on motherboard (look in attach), but didn't find it.
[Kindle Fire Android Development] maheboi:
Is there anyway to do this with the kindle fire 2? i dont have the fastboot cable and im trying to short it into fastboot with this method. i already had twrp installed, just acidentally wiped internal storage and im now in boot loop with no adb connection.
[Kindle Fire Android Development] koop1955:
You would be better off asking on the Kindle Fire 2 forums: http://xdaforums.com/kindle-fire-hd/fire-2-development
[Kindle Fire Android Development] chris8428:
Thank you

I know this is an old thread, but the procedure worked perfectly. And on the first try. Thank you guys for saving my Kindle.

Chris
[Kindle Fire Android Development] Bashirjan:
Amazone kindle fire hd7, Stuck in bootloop and the screen (Teamwin) blinking with every 5 seconds) but not entering on twrp recovery mode. please help
[Kindle Fire Android Development] nito510:
unbricking my hdx 8.9

Hi there,

anyone still active in this thread?

I would like to fix my fire hdx 8.9. It is hard bricked, no fastboot, no adb, only kindle logo when powering up. :(

So I am trying to flash it the hard way.

I opened it successfully but now I am stuck, cannot find any point to start with. Is anyone here familiar with this piece of hardware?

Where to put a flashing cable? Where to shorten some pins?

Many thanks in advance for your help!

nito
[Kindle Fire Android Development] chevycam94:
As far as the shorting trick with that test point, I have been trying for about an hour. It does nothing. Doesn't even power on. I have to pull the battery connector and replug it just to be able to get it to turn on again.

The top of my CPU says "ELPIDA". There is a smaller TI chip next to it (not near the test point used for this trick.

UPDATE: Nah, it's dead. Time to send it off in the trash. If anything, the constant attempt at doing the USB shorting trick killed it. I honestly didn't have a lot of faith in that method anyway. There was very little information about it, and very few reports that it actually worked. I got this for free, so I'm not out anything here. BUT, now I know never to buy one of these. The fact that I could NOT get fastboot to work in ANY operating system with this KF was the first knife in the back. My Google Pixel 3, always works flawlessly. A Kindle? Not a chance. Time to move on.
[Xoom Q&A, Help & Troubleshooting] custroid:
***Deleted***
[Xoom Q&A, Help & Troubleshooting] okantomi:
You have to have a micro sdcard in your Xoom when you flash the recovery image file from fastboot. There's no other way with the R4c recovery v. 3.2.0.0. That file needs to be in the folder on your pc with fastboot in it, that you are operating the command window from.
[Xoom Q&A, Help & Troubleshooting] zone23:
Kinda wish there were more threads like this one.. LOL
[Samsung Galaxy Nexus] Superguy:
Just a quick question.

My volume rocker seems to be a little over active. Like when I'm in CWM, when I'm moving to a selection, sometimes one click will move it like 2 or 3. It's pretty random when it does it, but it happens enough to be annoying. I have to be really deliberate about clicking to make it advance one option.

Is this common on other GNex (LTE), or is this just an issue with mine?

Thanks!

Super
[Samsung Galaxy Nexus] johantheolive:
If it's just in CWM then nothing to worry about. CWM is quirky like that.
[Samsung Galaxy Nexus] zipzoomeroo:
How do I get Voice Actions to come up? I've tried long pressing the mic in the home screen widget and everything else I can think of, but I can't get Voice Actions to come up. What am I doing wrong, and is there any way to remap Voice Actions to a long-press of the home button?
[Samsung Galaxy Nexus] jhuynh:
Don't you just press the mic and it comes up?
[Samsung Galaxy Nexus] zipzoomeroo:
I tried that but it doesn't seem to do all the voice actions from there. I couldn't get the "text" one to work.
[Samsung Galaxy Nexus] peadarog:
Are you American? Some of the voice actions will only work if you set your language to English (US)...
[Samsung Galaxy Nexus] zipzoomeroo:
I am American. Good idea, though.

I can hit the mic on the search bar and do a voice search, but it doesn't seem to work for all Voice Actions.
[Samsung Galaxy Nexus] neok44:
idk just worked for me. i said Text Carolyn (my gf) and it worked just fine.

*edit* also just tried call home, and that worked too.

also works a lot better than my nexus one. i had to fight with that damned phone to understand the difference between Carolyn and Caroline Country Club.
[Samsung Galaxy Nexus] zipzoomeroo:
I guess I'll just have to try it out some more. Thank you.
[Samsung Galaxy Nexus] irspam:
I didn't know you could say "text (person)" on the Galaxy Nexus... How do you do that? Lol...

Edit*** Nevermind, found it! :)
[Samsung Galaxy Nexus] neok44:
lol glad you found it. voice search has a lot of voice actions built in. call, text, navigate, and a few more.
[Verizon Droid Charge] coreysr:
I was wondering if someone could enlighten me on if a recalibration is necessary in this situation. I installed InfinityROM then calibrated with two complete discharge & on recharge. After that I was messing around with some themes, didn't like the result and then refresh infinity. I know I should of reinstalled it on a full battery but I didn't. Now since I'm not changing ROMs , just reinstalling the old theme, does that require a recalibration?

Sent from InfinityROM using xda premium
[Verizon Droid Charge] >DARKMAN<:
I beleive that if you flash a theme it does still wipe battery stats, so you could recalibrate, i usually don't bother because over time it will recalibrate itself in my experience.
[Verizon Droid Charge] fortesquieu:
As far as I know, flashing themes don't require battery calibration, but changing ROMs do.
[Verizon Droid Charge] JihadSquad:
I am pretty sure that the battery stats file is somewhere in the /system or /data partition. That means that it will only get cleared if your theme overwrites this file, which it shouldn't.
[Verizon Droid Charge] kvswim:
No. Files you flash will explicitly tell you if a recalibration will be necessary. Also, your battery level does not matter when flashing as long as it doesn't die in the process. I've flashed ROMs with 10% battery remaining without any negative consequences.
[Verizon Droid Charge] coreysr:
Thanks alot guys.

Sent from InfinityROM using XDA Premium.
[XPERIA X8 Q&A, Help & Troubleshooting] be_born:
I've been told that the nAa kernel is among the fastest... If you run the latest version of MiniCM on top of it you should have good performance. But i won't flash my kernel any time soon, i run MiniCM 2.0.7 on stock kernel now, i bricked the phone twice trying to install the nAa kernel. Cheers!
[XPERIA X8 Q&A, Help & Troubleshooting] joe200:
Try naa kernel it has the most features of all kernel currently for x8.
[Nook Touch General] el34han:
Like to tune my N2E with sysctl. Created /system/etc/sysctl.conf and load it manually with "sysctl -p" OK.

The problem is the effect is lost after reboot. If I can put "sysctl -p" in a rc file or any file that can be edited and run at boot time that should solve my problem.

Thank you.
[Nook Touch General] eded333:
This file runs at boot, try editing it:

/system/bin/clrbootcount.sh
[Nook Touch General] el34han:
Thank you. I will give it a try.
[Nook Touch General] el34han:
After checking clrbootcount.sh I found the file of my choice to invoke sysctl. Which is /data/boot_complete_hook.sh. It is invoked by clrbootcount.sh at boot time. Because /data/boot_complete_hook.sh is located in a writable partition it is easy to modify.

My NST is running much fast now. Switching between applications is about 3 to 5 times faster. Openning a book is another 3 to 5 times faster.

Thank you for the help.

BTW, This makes me wonder why can't B&N do this?
[Nook Touch General] mali100:
Could you please post your conf-file?
[LG Thrill 4G] joax11:
Hi,

Is there anyway to enable delivery reports for this phone?

Thanks!
[HTC Inspire 4G] MikeIsCore:
i usually never have any trouble with the WiFi on my phone, but for some reason the wifi is seriously failing the last couple days. I'm connecting to the same wifi network my computer is on and the computer is running very fast. Is it possible to mess with the wifi adapter?
[HTC Inspire 4G] MMM-BACONSTRIPS:
Have you taken off your battery cover lately? I believe the wifi connections are back there and if you have taken off the battery cover, they might not touching all the way giving spotty wifi...
[HTC Inspire 4G] MikeIsCore:
Yep tried that. Everything is connecting tight.

I dropped the phone the day I started having the issue but it was only about a foot long drop, and the bottom of the phone hit the ground first.

Could that be affecting anything? I dropped my iPhone 3GS more times than i've dropped my Inspire and i never had trouble with the wifi in that. Not trying to knock the Inspire because i couldnt stand anything about the iPhone when i had it.
[HTC Inspire 4G] jpcdeux:
Don't be careless and drop phones! That deserves any wifi issues lol
[HTC Inspire 4G] MMM-BACONSTRIPS:
Tough to tell ya know. Each drop will do something different, I mean I've dropped my phone from my balcony and no problems...I'm going to make a bold assumption that you're rooted? If you are, reflash the ROM and see if that will help.
[HTC Inspire 4G] MikeIsCore:
Re-flashing will completely wipe the phone correct? I haven't devled into the world of flashing and re-flashing roms. I've only rooted, flashed CM7, and updated the nighties as they were available.
[HTC Inspire 4G] zelendel:
To be honest I would do a nand back up and flash a Non CM based rom and see if it helps.
[HTC Inspire 4G] MikeIsCore:
I went into Recovery and didnt see anything that said Nand back up but i did see an option for Backup / Restore which I went into and created a backup.

Is there more to a nand backup?
[HTC Inspire 4G] zelendel:
No that is a nand backup. It backs up your whole rom.
[HTC Inspire 4G] willwalk93:
I usually stick to sense ROMs, but this should be universal. once I had that problem and flashed a new kernel and it was better than ever. Might want to give that a shot if your reflash doesn't work or you don't want to reflash.
[HTC Inspire 4G] jpcdeux:
He dropped his phone. I doubt that suddenly made a kernel or rom act up.
[HTC Inspire 4G] willwalk93:
Ok I'll give you that. I have also dropped mine. I'm just throwing out possible options for him. Possibly his battery jarred and a config file in his kernel controlling his wifi power corrupted. or something got moved and is interfering with the wifi signal but his computer antenna is strong enough compensate. Yes highly unlikely, I know. Like I said, just trying to expend all possible options. Sorry if that came off as rude or disrespectful to your senior member status, it was not intended in that manor.
[HTC Inspire 4G] jpcdeux:
Not rude at all.

Just mildly comical when people are so careless as to repeatedly drop phones and then wonder why things go wrong and think software is going to help it. If you drop your phone REPEATEDLY you kind of have it coming. Well see him next asking glass replacement help hahaha.
[HTC Inspire 4G] ehupp:
Have you tried releasing the ip address and re negotiating a connection?
[HTC Inspire 4G] willwalk93:
Haha good point... And mine is in the otterbox so... I mean the worst I have done was dropped it in the blender. Is that too bad to fix? Jk

As for releasing and renewing... Good point there, and he may also need a router reboot if DHCP is Hung.