me and a buddy both have Fires and we both have rooted using this Guide.
After rooting we both have similar results. Well in fact all elements are the same except the bootloader screen, he has the Blue fire loader while I have the Yellow Triangle...
What's the difference?
josuave83 said:
me and a buddy both have Fires and we both have rooted using this Guide.
After rooting we both have similar results. Well in fact all elements are the same except the bootloader screen, he has the Blue fire loader while I have the Yellow Triangle...
What's the difference?
Click to expand...
Click to collapse
Short answer: 0.2
Long answer:
http://forum.xda-developers.com/showthread.php?t=1369405
http://forum.xda-developers.com/showthread.php?t=1632375
Related
So is it possible to flash a new splash screen over the Default yellow triangle from FFF?
using
Code:
fastboot flash splash splash.img
yields nothing.
am i missing something? or is it not possible to change FFF's splash?
Thanks!
fallingcowdude said:
So is it possible to flash a new splash screen over the Default yellow triangle from FFF?
using
Code:
fastboot flash splash splash.img
yields nothing.
am i missing something? or is it not possible to change FFF's splash?
Thanks!
Click to expand...
Click to collapse
Yeah don't mess with it you will seriously brick your kindle and have a fancy little hockey puck
---------- Post added at 01:39 PM ---------- Previous post was at 01:36 PM ----------
If you wish to replace your bootloader use this method http://forum.xda-developers.com/showthread.php?t=1500935
Hmmm. You still dident answer my question. I realize that I could brick my KF...At least tell me what partition the bootloaders stored in.
Sent from my Amazon Kindle Fire using xda app-developers app
Hmmm you didn't listen doing this to your bootloader can cause a permanent brick end of story if you wish to continue speak to those who build the bootloaders
Just a side note hashcodes new bootloader has a lovely new splash screen no more yellow triangle check it out
Wow. You're not too bright. Are you? Let me break this down for you.
1. I couldn't care less if I bricked my KF
That was hard. Wasn't it?
If you don't have the answer, don't post.
Sent from my Amazon Kindle Fire using xda app-developers app
Wow if intelligence is an indication why are you asking?..:silly:
You don't give up... do you?
thanks for soupmagnet.
now, kindlefire begin to work!
but, i have question still
why DON'T WORK my device?
bootloader is bad? or my mistake?
past post : http://forum.xda-developers.com/showthread.php?t=1857140
No, if the device turns on, you're in good shape. I'm guessing you are stuck at a big yellow triangle, correct?
soupmagnet said:
No, if the device turns on, you're in good shape. I'm guessing you are stuck at a big yellow triangle, correct?
Click to expand...
Click to collapse
stuck mean brick?
Does the device power on now? If yes, do you see a yellow triangle?
Or
Did the device power on, only until reboot, then it has no power again?
Hopefully that is easier to translate.
soupmagnet said:
Does the device power on now? If yes, do you see a yellow triangle?
Or
Did the device power on, only until reboot, then it has no power again?
Hopefully that is easier to translate.
Click to expand...
Click to collapse
now my devices is normalcy
but i want know, reason brick my kindle in past.
understand?
my english skill is very very bad..
i think.. undelivered post meaning..
The reason was a bad bootloader flash. Always check MD5. Even then, sometimes it just happens.
soupmagnet said:
The reason was a bad bootloader flash. Always check MD5. Even then, sometimes it just happens.
Click to expand...
Click to collapse
i understand
always thanks for help!
Well I got tired of modifying my stock Kindle OS and getting wierd results so I tried a Second Time to Install CM10 on my KFHD 8.9 (FW 8.1.4) Followed this guide: http://forum.xda-developers.com/showthread.php?t=2100963 Got to step 4 and at this point the damn thing hard bricked. No fast boot, No Safe boot, No boot at all just a black screen. How come everyone else can seem to get it right but me? Anyway I have already recieved 1 replacement device from Amazon, and I am quite poor and cannot afford expensive tools or another system. So My question here is 2 fold. Is there any fix for this? and if so what is the safest way to attempt TWRP and CM10? Thanks and hope to hear from somebody.
JonnyLawless said:
Well I got tired of modifying my stock Kindle OS and getting wierd results so I tried a Second Time to Install CM10 on my KFHD 8.9 (FW 8.1.4) Followed this guide: http://forum.xda-developers.com/showthread.php?t=2100963 Got to step 4 and at this point the damn thing hard bricked. No fast boot, No Safe boot, No boot at all just a black screen. How come everyone else can seem to get it right but me? Anyway I have already recieved 1 replacement device from Amazon, and I am quite poor and cannot afford expensive tools or another system. So My question here is 2 fold. Is there any fix for this? and if so what is the safest way to attempt TWRP and CM10? Thanks and hope to hear from somebody.
Click to expand...
Click to collapse
Unfortunately that Kindle is more than likely done for good. What you flashed was for a Kindle Fire 2 to your Kindle Fire HD 8.9.
I'm really interested in changing the boot (OEM) logo that appears before the boot animation - the giant Google logo with the padlock at the bottom of the screen.
From what I can understand, the boot logo is part of the bootloader, making it harder to change... Are there any projects going/does anyone know how to change this logo for the Nexus 7 (2013)'s bootloader?
I'm running CM11 4.4.2 (snapshot M7).
Thanks everyone
TheTechnoToast said:
I'm really interested in changing the boot (OEM) logo that appears before the boot animation - the giant Google logo with the padlock at the bottom of the screen.
From what I can understand, the boot logo is part of the bootloader, making it harder to change... Are there any projects going/does anyone know how to change this logo for the Nexus 7 (2013)'s bootloader?
I'm running CM11 4.4.2 (snapshot M7).
Thanks everyone
Click to expand...
Click to collapse
Check this out in the Nexus 5 forums: http://forum.xda-developers.com/google-nexus-5/themes-apps/tool-change-boot-logo-images-t2763698. I flashed one of these on my Nexus 5, and I now have the Red Bull Racing logo where it used to say "Google" and "Powered by Android" where it used to show the unlocked padlock. It's pretty sweet. I'm not entirely sure how to make one for the N7, but with a little reading, you may be able to make your own.
charesa39 said:
Check this out in the Nexus 5 forums: http://forum.xda-developers.com/google-nexus-5/themes-apps/tool-change-boot-logo-images-t2763698. I flashed one of these on my Nexus 5, and I now have the Red Bull Racing logo where it used to say "Google" and "Powered by Android" where it used to show the unlocked padlock. It's pretty sweet. I'm not entirely sure how to make one for the N7, but with a little reading, you may be able to make your own.
Click to expand...
Click to collapse
Thanks, I'll take a good look at this.
TheTechnoToast said:
Thanks, I'll take a good look at this.
Click to expand...
Click to collapse
Did it work for Nexus 7?
rajiv0909 said:
Did it work for Nexus 7?
Click to expand...
Click to collapse
Afraid not... It's been a while since I looked at this, but from what I remember I think it involved replacing my entire bootloader. Plus it can't recognize custom recoveries and well, I'd rather modify TWRP than modify the stock one.
Hi
My fire stick stuck at start at the amazon logo. Nothing helps.
Before throwing it away I was thinking of opening it up if there was a way to i don't know short circuit something to force it to boot into recovery or if there was any way to recover it from the grave.
Thanks for the suggestions in advance.
It is the model LY73PR
gabor.czinege said:
Hi
My fire stick stuck at start at the amazon logo. Nothing helps.
Before throwing it away I was thinking of opening it up if there was a way to i don't know short circuit something to force it to boot into recovery or if there was any way to recover it from the grave.
Thanks for the suggestions in advance.
It is the model LY73PR
Click to expand...
Click to collapse
Unbrick:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 2nd gen (tank)
Read this whole guide before starting. This is for the 2nd gen Fire TV Stick (tank) Current relase: amonet-tank-v1.2.2.zip NOTE: Recent reports indicate a change that disables brom DL-mode The change seems to have been introduced with devices...
forum.xda-developers.com
Sus_i said:
Unbrick:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 2nd gen (tank)
Read this whole guide before starting. This is for the 2nd gen Fire TV Stick (tank) Current relase: amonet-tank-v1.2.2.zip NOTE: Recent reports indicate a change that disables brom DL-mode The change seems to have been introduced with devices...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks that's what i was looking for. Though the process runs through until point 5. Wait for the script to finish.
But the device still stuck at amazon logo unfortunately. Trash it is?
gabor.czinege said:
Thanks that's what i was looking for. Though the process runs through until point 5. Wait for the script to finish.
But the device still stuck at amazon logo unfortunately. Trash it is?
Click to expand...
Click to collapse
I thought since I'm at the point where it accepts stuff like handshake2.py stuff can't i somehow reset it to factory defaults via command line? Clear cache? Force it to load to recovery? (though i don't have a powered otg yet but I'd get one if I'd get to recovery)
gabor.czinege said:
I thought since I'm at the point where it accepts stuff like handshake2.py stuff can't i somehow reset it to factory defaults via command line? Clear cache? Force it to load to recovery? (though i don't have a powered otg yet but I'd get one if I'd get to recovery)
Click to expand...
Click to collapse
There is only one unbrick solution, see the link above.
Take a look at which step the script stalls and/or if you get an error message, search for it in the thread.