[bootloader][05-26] FFF 1.4A bugfixes + new look + recovery boot [.zip file size]
- Thread starter Hashcode
- Start date
Does it have a fastboot countdown like in earlier versions of fff?
PS: just flashed this after a pretty scary brick and all is well again
EDIT: nvm I just got the chance to check it and it does work.
Sent from my Amazon Kindle Fire using XDA
I don't even think its necessary anymore but its great to have at startup for easy use.
Sent from my GT-P1000 using xda premium
Last edited:
I expect it'll happen sooner or later. I don't think it is the highest priority at the moment so don't hold your breath
Sent from my fax machine
This is being worked on. But it not an obvious fix. So its taking a while.
Lately ive been testing a new clockwork recovery.. and its working great, except that it doesnt power off correctly, so im hesitant to put it out just yet.
And im rewriting the charger driver.
Sent from my DROID4 using Tapatalk 2
Just updated my bootloader thanks for the hard work 
Sent from my Amazon Kindle Fire using Tapatalk 2
Sent from my Amazon Kindle Fire using Tapatalk 2
Little Question.
I there im a huge fan of you're work, but i have a question. How do you install a bootloader for the first time? Do you get TWRP and flash it? Thanks in advance.
I there im a huge fan of you're work, but i have a question. How do you install a bootloader for the first time? Do you get TWRP and flash it? Thanks in advance.
You need to unzip the file and use fastboot to flash the bin file included in the zip file. Use the following command:
fastboot flash bootloader <file.bin>
The file name should match the extracted file from zip downloaded.
Sent from my Amazon Kindle Fire using Tapatalk 2
The whole point of making it in a .zip format to be flashed in recovery is to avoid any possibility of installing it incorrectly and thereby hard-bricking one's device. Plus it automatically performs checksum to prevent it from installing a corrupt file.
Always flash in recovery when possible.
Last edited:
Hi gannon, good to hear your voice again, hows life after android central? Ok done with off topic conversations
sent from my Nokia 5110
So just to be absolutely clear (which you can never be to careful when flashing a bootloader on anything) From TWRP all i have to do is flash
Rombot mirror:
http://bit.ly/J5izIt
and it doesnt matter what version of FFF bootloader im on already(Obviously im still on the one with the gian yellow sign with an "!" on it?)
Rombot mirror:
http://bit.ly/J5izIt
and it doesnt matter what version of FFF bootloader im on already(Obviously im still on the one with the gian yellow sign with an "!" on it?)
Appreciate it, just wanted to make sure!
I don't blame you, we would rather you ask to clarify, then to be another "I bricked my kindle" thread
sent from my Nokia 5110
Looks good
I definitely like the new improvements you have made to the bootloader, it was driving me crazy to not be able to get hardly any feedback on what was happening. However, I'm still having the same problem I did with the FFF before this.
I cannot for the life of me get it to boot into recovery by just using the bootloader. I end up having to use fbmode, then reflashing the whole recovery.img to get it to boot into twrp (when I set the idme bootmode it refuses to work, which brings me to the next point.)
After I get it into recovery and flash what I need to, then it is a pain to get it to boot normally. So the "reset bootmode" option on here still hasn't worked for me, it repeatedly boots back into recovery. Even after I set the idme bootmode back to 4000.
I'm very puzzled as to why I'm having such difficulty, and I haven't found anything related to the problem...I usually spend all my time on here searching for answers (hence the low post count.) So I'm sorry for such a long post, but I have three different kindle's that I need to fix, and I just haven't figured it out yet...
Edit: I have tried the instructions from the twrp site (http://www.teamw.in/project/twrp2/79):
"If your device is always booting TWRP run: adb shell "idme bootmode 4000"
If you still can't get out of booting TWRP, first run: adb shell "idme bootmode 4002"
reboot your device, then run: adb shell "idme bootmode 4000"
reboot again and you should be out of your bootloop"
to no avail. This is a strange problem.
Thanks in advance for any help
Edit Again:
So, I have turned this post into a little story here and I apologize. But I seem to have found the solution. Somewhere along the lines, I had typed the wrong command in...see, I was going off of memory, and not really thinking. (My drive for figuring stuff out by myself has its own consequences.) So, I ran:
fastboot flash boot (recovery).img
and uh...well as you can imagine that made a mess of things. So, after a long time of wondering what I did wrong, I reflashed the recovery using "fastboot flash RECOVERY recovery.img" and then had to extract the boot.img from the rom and flash that to the boot partition again, and THEN reset the bootmode and now I think everything is FINALLY working.
So, there's an entertaining story for your day, I doubt anybody will be looking for this post as a solution to their problem (so I won't get any thanks lol) Anyways, I figured it wasn't a problem with your bootloader, I appreciate the great work Hashcode! Keep it up.
I definitely like the new improvements you have made to the bootloader, it was driving me crazy to not be able to get hardly any feedback on what was happening. However, I'm still having the same problem I did with the FFF before this.
I cannot for the life of me get it to boot into recovery by just using the bootloader. I end up having to use fbmode, then reflashing the whole recovery.img to get it to boot into twrp (when I set the idme bootmode it refuses to work, which brings me to the next point.)
After I get it into recovery and flash what I need to, then it is a pain to get it to boot normally. So the "reset bootmode" option on here still hasn't worked for me, it repeatedly boots back into recovery. Even after I set the idme bootmode back to 4000.
I'm very puzzled as to why I'm having such difficulty, and I haven't found anything related to the problem...I usually spend all my time on here searching for answers (hence the low post count.) So I'm sorry for such a long post, but I have three different kindle's that I need to fix, and I just haven't figured it out yet...
Edit: I have tried the instructions from the twrp site (http://www.teamw.in/project/twrp2/79):
"If your device is always booting TWRP run: adb shell "idme bootmode 4000"
If you still can't get out of booting TWRP, first run: adb shell "idme bootmode 4002"
reboot your device, then run: adb shell "idme bootmode 4000"
reboot again and you should be out of your bootloop"
to no avail. This is a strange problem.
Thanks in advance for any help
Edit Again:
So, I have turned this post into a little story here and I apologize. But I seem to have found the solution. Somewhere along the lines, I had typed the wrong command in...see, I was going off of memory, and not really thinking. (My drive for figuring stuff out by myself has its own consequences.) So, I ran:
fastboot flash boot (recovery).img
and uh...well as you can imagine that made a mess of things. So, after a long time of wondering what I did wrong, I reflashed the recovery using "fastboot flash RECOVERY recovery.img" and then had to extract the boot.img from the rom and flash that to the boot partition again, and THEN reset the bootmode and now I think everything is FINALLY working.
So, there's an entertaining story for your day, I doubt anybody will be looking for this post as a solution to their problem (so I won't get any thanks lol) Anyways, I figured it wasn't a problem with your bootloader, I appreciate the great work Hashcode! Keep it up.
Last edited:
I definitely like the new improvements you have made to the bootloader, it was driving me crazy to not be able to get hardly any feedback on what was happening. However, I'm still having the same problem I did with the FFF before this.
I cannot for the life of me get it to boot into recovery by just using the bootloader. I end up having to use fbmode, then reflashing the whole recovery.img to get it to boot into twrp (when I set the idme bootmode it refuses to work, which brings me to the next point.)
After I get it into recovery and flash what I need to, then it is a pain to get it to boot normally. So the "reset bootmode" option on here still hasn't worked for me, it repeatedly boots back into recovery. Even after I set the idme bootmode back to 4000.
I'm very puzzled as to why I'm having such difficulty, and I haven't found anything related to the problem...I usually spend all my time on here searching for answers (hence the low post count.) So I'm sorry for such a long post, but I have three different kindle's that I need to fix, and I just haven't figured it out yet...
Edit: I have tried the instructions from the twrp site (http://www.teamw.in/project/twrp2/79):
"If your device is always booting TWRP run: adb shell "idme bootmode 4000"
If you still can't get out of booting TWRP, first run: adb shell "idme bootmode 4002"
reboot your device, then run: adb shell "idme bootmode 4000"
reboot again and you should be out of your bootloop"
to no avail. This is a strange problem.
Thanks in advance for any help
Edit Again:
So, I have turned this post into a little story here and I apologize. But I seem to have found the solution. Somewhere along the lines, I had typed the wrong command in...see, I was going off of memory, and not really thinking. (My drive for figuring stuff out by myself has its own consequences.) So, I ran:
fastboot flash boot (recovery).img
and uh...well as you can imagine that made a mess of things. So, after a long time of wondering what I did wrong, I reflashed the recovery using "fastboot flash RECOVERY recovery.img" and then had to extract the boot.img from the rom and flash that to the boot partition again, and THEN reset the bootmode and now I think everything is FINALLY working.
So, there's an entertaining story for your day, I doubt anybody will be looking for this post as a solution to their problem (so I won't get any thanks lol) Anyways, I figured it wasn't a problem with your bootloader, I appreciate the great work Hashcode! Keep it up.
Yeah be careful, you almost flashed your recovery on your boot partition, that's no fun to fix. Ask lovejoy.
sent from my Nokia 5110
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
151NEW BOOTLOADER INSTALL METHOD: FLASH.ZIP. SAFER. USE IN RECOVERY JUST LIKE ANY OTHER ROM .ZIP
This is an UPDATED version of FIREFIREFIRE by Pokey9000
CREDITS and THANKS GO TO:
- Pokey9000: For getting this going. Hard to dev at all w/o a way of getting to recovery.
- eldarerathis: Menu code was used from the Extended FIREFIREFIRE github
- Icemank121: All splash/menu screens
Version 1.5 of FIREFIREFIRE changes:
- [1.5] Better handling for lower power / charging screen
- [1.4a] Reprioritized the different boot options so that regardless of idme bootmode, the options chosen from the menu would be used first.
- [1.4] Support for a single boot directly to Recovery for applying ROM updates, etc via "Reboot Recovery" menu in Android. Works with any recovery that is installed. All existing ROM devs need to update their BoardConfig.mk to support this by adding the following:
TARGET_RECOVERY_PRE_COMMAND := "idme postmode 1;"
Your builds will need to also have a working "idme" binary and the "libidme.so" lib for the reboot recovery option to work.
Both of these are in the prebuilts of the device tree on github:
https://github.com/KFire-Android/android_device_amazon_otter/tree/cm-11.0/prebuilt
- Fixed Charging Mode which will pause the boot process and let the device charge if the current capacity is under 3%. If you connect it to the stock charger, the boot can proceed.[/B]
- Added a Boot Menu which is accessed by pressing the power button after a the initial splash screen is displayed. You then press the menu button again to navigate through each option. If you wait after an option is highlighted, it will automatically be selected after a few seconds.:
- Normal: Standard boot into your installed ROM
- Recovery: Boot to recovery
- Reset Boot Mode: This is a normal bootup but resets "idme bootmode" to 4000 for those that are stuck and can't access idme for whatever reason.
NOTES:
Currently the handling of the power button is a bit sloppy, takes 1-2 presses for it to register each press to navigate through the menu.
Download the recovery-flashable .zip file here:
http://goo.im/devs/hashcode/otter/bootloader/flash-zip
v1.5 md5sum: 4e9d277a31a2a26d33156edf5abbf0e4
v1.4a md5sum: 419c53b922c963082454b14b7de75a90
Apply this flash.zip from recovery just like any other ROM or kernel .zip file. This is by far the safest way to upgrade your bootloader. It does a sha1sum check on the file before applying.
GitHub source (forked from Pokey9000's original) here:
https://github.com/KFire-Android/kf_u-boot119
This is being worked on. But it not an obvious fix. So its taking a while.
Lately ive been testing a new clockwork recovery.. and its working great, except that it doesnt power off correctly, so im hesitant to put it out just yet.
And im rewriting the charger driver.
Sent from my DROID4 using Tapatalk 27While I applaud the move to have the bootloader flashed through recovery, distributing it as a zip file has had an unintended, but somewhat foreseeable side effect. There's a certain group of users who do not care to read warnings or follow directions, so they charge ahead and flash the zip file with fastboot. No matter how big and prominent you make the directions, there will always be those who need to be protected from themselves and doing harm to their device.
I swear... even if you warned people in big, red neon lights that flashing something will make the device blow up, they'd still come back the next day and ask if a factory cable will fix it. I've come to believe that posting directions and warnings is just not enough. There's another thread today from a user who flashed the zip archive and I'm sure that won't be the last if there's no guardrail in place to keep them from going over the cliff. That's my long-winded prelude to my suggested fix...
Hashcode... could you place an extraneous pad file inside the distribution so the zip archive exceeds the 256KB mark in size? Fastboot will do a sanity check and compare the size of the file to the size of the partition. If the file is too big, it will balk and stop the flash procedure. Like this...
Code:$ fastboot flash bootloader fff-u-boot_v1.4b.zip sending 'bootloader' (273 KB)... OKAY [ 0.086s] writing 'bootloader'... FAILED (remote: image too large for partition) finished. total time: 0.093s
That should effectively stop people from shooting themselves in the foot.
