I unlocked my firestick 2 using the instructions here and everything worked fine. I then decided to install Lineage OS using the instructions here . It got stuck on "patching system image unconditionally" and I made the mistake of rebooting.
It is now stuck on the white amazon logo and does not show up in ADB. Any help will be appreciated!
The_Treasurer said:
I unlocked my firestick 2 using the instructions here and everything worked fine. I then decided to install Lineage OS using the instructions here . It got stuck on "patching system image unconditionally" and I made the mistake of rebooting.
It is now stuck on the white amazon logo and does not show up in ADB. Any help will be appreciated!
Click to expand...
Click to collapse
See post #3 here, you need to get back into recovery. FWIW - i think mine took a really long time to install 12.1. Make sure you wipe per the instructions...
https://forum.xda-developers.com/fire-tv/development/unlock-fire-tv-stick-2nd-gen-tank-t3907002
Michajin said:
See post #3 here, you need to get back into recovery. FWIW - i think mine took a really long time to install 12.1. Make sure you wipe per the instructions...
https://forum.xda-developers.com/fire-tv/development/unlock-fire-tv-stick-2nd-gen-tank-t3907002
Click to expand...
Click to collapse
I tried the commands for when you are stuck in a boot loop; "sudo ./boot-fastboot.sh" and "sudo ./boot-recovery.sh". They both execute but nothing happens. Still stuck on the white amazon logo
The_Treasurer said:
I tried the commands for when you are stuck in a boot loop; "sudo ./boot-fastboot.sh" and "sudo ./boot-recovery.sh". They both execute but nothing happens. Still stuck on the white amazon logo
Click to expand...
Click to collapse
Start the script boot-recovery.sh, then Plug the stick in. The script should say "waiting on preloader" then run, when the device is pluggedin, if the script is completing and you are not booting into recovery, then you might have corrupted something when you unplugged. You may have to open the device and start the exploit over.
Michajin said:
Start the script boot-recovery.sh, then Plug the stick in. The script should say "waiting on preloader" then run, when the device is pluggedin, if the script is completing and you are not booting into recovery, then you might have corrupted something when you unplugged. You may have to open the device and start the exploit over.
Click to expand...
Click to collapse
I had to start the exploit over, and it worked. Thanks so much!!
Related
O.k. Let me explain the best I can!
So this makes the 2nd Kindle Fire 2 to do the same thing to me.
First off I have read and re-read all the threads front to back that deal with KF2 devices. NOTHING HAS WORKED.
My problem...
http://www.youtube.com/watch?v=C_YWq0h1-9s
This all deals with my 2nd Kindle. The first one has been shipped back to Amazon for exchange.
However the steps are the same. (There is only two guides after all)
So I started by rooting the stock 10.2.3 KF2 using Bin4ry's Root Method.
I then used http://forum.xda-developers.com/showthread.php?t=2106463 to install TWRP.
After rebooting into TWRP I proceeded to wipe the required areas and install http://forum.xda-developers.com/showthread.php?t=2105077
All files Installed with NO ISSUES!
Rebooted into the "streched out CW 10.1 logo". That's when it seemed to get stuck! 45 Mins nothing.
Ok so lets redo this I think to myself.
Reboot into TWRP wipe ALL data areas EXCEPT my SDCard (Roms are stored there need them to install OS duh!) and proceed to install again.
Reboot..... an LOOP.. LOOP .. LOOP
2 different Kindles doing same loop.
Fastboot. Does not work. I have 2 Kindles with 2 different cables and 100+ computers to try it on. All from XP/7/8 to MAC/Ubuntu.
Sadly none are helping me enter fastboot. To me it seems to be GONE! Is that even possible?
Can anyone help?
Just view the Youtube link to know where I am currently!
You may have to wipe SD
nFxus said:
O.k. Let me explain the best I can!
So this makes the 2nd Kindle Fire 2 to do the same thing to me.
First off I have read and re-read all the threads front to back that deal with KF2 devices. NOTHING HAS WORKED.
My problem...
[YOUTUBE="http://www.youtube.com/watch?v=Pt5-d6VH4xQ"][/YOUTUBE]
This all deals with my 2nd Kindle. The first one has been shipped back to Amazon for exchange.
However the steps are the same. (There is only two guides after all)
So I started by rooting the stock 10.2.3 KF2 using Bin4ry's Root Method.
I then used http://forum.xda-developers.com/showthread.php?t=2106463 to install TWRP.
After rebooting into TWRP I proceeded to wipe the required areas and install http://forum.xda-developers.com/showthread.php?t=2105077
All files Installed with NO ISSUES!
Rebooted into the "streched out CW 10.1 logo". That's when it seemed to get stuck! 45 Mins nothing.
Ok so lets redo this I think to myself.
Reboot into TWRP wipe ALL data areas EXCEPT my SDCard (Roms are stored there need them to install OS duh!) and proceed to install again.
Reboot..... an LOOP.. LOOP .. LOOP
2 different Kindles doing same loop.
Fastboot. Does not work. I have 2 Kindles with 2 different cables and 100+ computers to try it on. All from XP/7/8 to MAC/Ubuntu.
Sadly none are helping me enter fastboot. To me it seems to be GONE! Is that even possible?
Can anyone help?
Just view the Youtube link to know where I am currently!
Click to expand...
Click to collapse
Hi,
I got stuck in a boot loop 12 days ago. Never got to Cynaogen screen. I wiped all data, including my ROM and Gapps. WHOOPS.
I could boot into TWRP, and that was it. I was optimistic... CAN YOU GET INTO TWRP?
But, I could not get any computer to recognize it. I tried my Win Xp, Mac OSX: 10.6.7 and Xubuntu...
Finally I got ADB running by following this tutorial: http://desire.giesecke.tk/tutorial-adb-on-xubuntu/?wpmp_switcher=desktop
Be sure to change the Vendor ID to 1949, and use your machine's text editor. I have leafpad.
It took about 30 minutes to get ADB working
I wiped then sideloaded and flashed (install from zip) CM10
Then I rebooted
Then I flashed Gapps.
Hope this helps. Wiping the device can be a critical step.
GOOD LUCK. I was relieved when the CM splash screen ended.
nFxus said:
....
Rebooted into the "streched out CW 10.1 logo". That's when it seemed to get stuck! 45 Mins nothing.
Ok so lets redo this I think to myself.
Reboot into TWRP wipe ALL data areas EXCEPT my SDCard (Roms are stored there need them to install OS duh!) and proceed to install again.
Reboot..... an LOOP.. LOOP .. LOOP
2 different Kindles doing same loop.
Fastboot. Does not work. I have 2 Kindles with 2 different cables and 100+ computers to try it on. All from XP/7/8 to MAC/Ubuntu.
Sadly none are helping me enter fastboot. To me it seems to be GONE! Is that even possible?
Can anyone help?
Just view the Youtube link to know where I am currently!
Click to expand...
Click to collapse
It sounds like a bad download. Have you tried re downloading the ROM again? Check the MD5 code on your download against the code on the website.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
MD5 Check out just fine.
chronicfathead said:
It sounds like a bad download. Have you tried re downloading the ROM again? Check the MD5 code on your download against the code on the website.
Click to expand...
Click to collapse
Yeah thats not the issue. The md5's checkout just fine. Thanks though. :good:
I did what you proposed.
yudanjah said:
I could boot into TWRP, and that was it. I was optimistic... CAN YOU GET INTO TWRP?
Click to expand...
Click to collapse
Sadly no!
Finally I got ADB running by following this tutorial: http:/ /desire.giesecke.tk/tutorial-adb-on-xubuntu/?wpmp_switcher=desktop
Be sure to change the Vendor ID to 1949, and use your machine's text editor. I have leafpad.
Click to expand...
Click to collapse
As you can see in my new Youtube Video the KF2 is Alive but Dead!
youtube.com/watch?v=C_YWq0h1-9s
I think my 1st gen KF is stuck trying to boot to recovery. I was trying to restore back to stock from CM10.1. Downloaded the Amazon update 6.2.1 bin file, renamed it to update.zip, booted into TWRP recovery, tried to flash and it failed (several times). After some research, I found that the fix for this was to downgrade TWRP to v2.2.2.1 (I was on 2.6.0.0 or something like that). I tried several methods for doing that and it wouldn't take, even though it looked like flashing the TWRP v2.2.2.1 finished successfully. So finally I found a method (thanks to XDA's wonderful developers) to install CWM. Finally was able to get it to boot into CWM recovery, tried flashing the update.zip again, and all went through successfully. However, when I rebooted it was stuck at the Kindle Fire logo screen. Tried rebooting several times...nothing. AFter more research, found that the bootmode was incorrectly set so I tried to change the bootmode to recovery (which failed miserably)...now I'm stuck on the Kindle Fire logo screen. Seems like it is trying to boot to stock recovery but can't get there. Now none of my computers will recognize it at all. Is there anything I can do to unbrick this? I've tried just about every method I can get my hands on but without the computer recognizing it, not sure what else I can do.
Any help would be GREATLY appreciated. This is my 8-year old son's Kindle!
Thanks,
caseym
caseym said:
I think my 1st gen KF is stuck trying to boot to recovery. I was trying to restore back to stock from CM10.1. Downloaded the Amazon update 6.2.1 bin file, renamed it to update.zip, booted into TWRP recovery, tried to flash and it failed (several times). After some research, I found that the fix for this was to downgrade TWRP to v2.2.2.1 (I was on 2.6.0.0 or something like that). I tried several methods for doing that and it wouldn't take, even though it looked like flashing the TWRP v2.2.2.1 finished successfully. So finally I found a method (thanks to XDA's wonderful developers) to install CWM. Finally was able to get it to boot into CWM recovery, tried flashing the update.zip again, and all went through successfully. However, when I rebooted it was stuck at the Kindle Fire logo screen. Tried rebooting several times...nothing. AFter more research, found that the bootmode was incorrectly set so I tried to change the bootmode to recovery (which failed miserably)...now I'm stuck on the Kindle Fire logo screen. Seems like it is trying to boot to stock recovery but can't get there. Now none of my computers will recognize it at all. Is there anything I can do to unbrick this? I've tried just about every method I can get my hands on but without the computer recognizing it, not sure what else I can do.
Any help would be GREATLY appreciated. This is my 8-year old son's Kindle!
Thanks,
caseym
Click to expand...
Click to collapse
I'm having exactly the same issue on my Kindle Fire. I just recently got it from a friend; it seemed to be bricked, but the friend stated that he had never tried modifying the stock OS. I was able to use KFU to install the most up-to-date version of TWRP, but not FFF; I wanted to get it to stock before doing any additional hacking. That version of TWRP booted without any issues.
As OP mentioned, the most up-to-date version of TWRP has issues with installing the current version of the Amazon software. So, I tried downloading a copy of TWRP 2.2.2.1 (attached) and used KFU to install it, by extracting recovery.img, renaming it to twrp.img, and dropping it in KFU's /recovery/ folder.
Since then, I've seen the same symptoms as OP. The Fire boots to the Kindle Fire bootscreen, with no animation. It's not detected at all by any computer I attach it to. Windows doesn't chime or show it in Device Manager and KFU and adb don't see it. I also tried setting up FireKit, but none of the tools in that package are able to see it.
I'm going to test to see if this persists after depleting the battery for a while. I do not have a fastboot cable to test with, but I'm open to opening the case if you guys think that'll help get it back up and running.
Update; I was able to use the shorting trick to put it into OMAP boot mode and install FFF and TWRP, as well as reset the boot mode using Firekit. Firekit also installs TWRP 2.0, which is able to restore the stock Kindle Fire firmware.
haikuginger said:
Update; I was able to use the shorting trick to put it into OMAP boot mode and install FFF and TWRP, as well as reset the boot mode using Firekit. Firekit also installs TWRP 2.0, which is able to restore the stock Kindle Fire firmware.
Click to expand...
Click to collapse
OK...can you explain what you mean by the "shorting trick"? The battery on mine has been dead for about a day and a half. I had the case open the other day but didn't really do anything. What do I need to do?
Thanks,
caseym
caseym said:
OK...can you explain what you mean by the "shorting trick"? The battery on mine has been dead for about a day and a half. I had the case open the other day but didn't really do anything. What do I need to do?
Thanks,
caseym
Click to expand...
Click to collapse
First, get the Kindle charged. Then, boot to Ubuntu and set up FireKit (link above). Then, with the back cover off, hook the Kindle up to the computer. It'll power up, but hold down the power button to shut it off immediately.
Once you've done that, run the "usb_install_fff_twrp" script from Terminal. It'll say that its waiting for an OMAP device. Here's where the shorting comes in. Short the pad circled in the picture in this post to the metal frame around the CPU:
http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51
Then, keeping it shorted, press the power button.
Firekit should see the device over USB now, and write the appropriate settings. Once booted to TWRP, you should be able to install the stock firmware from /sdcard/.
It might take a couple tries, but keep trying. I used a continuity tester with an LED in it to make sure I had shorted that pad correctly.
haikuginger said:
First, get the Kindle charged. Then, boot to Ubuntu and set up FireKit (link above). Then, with the back cover off, hook the Kindle up to the computer. It'll power up, but hold down the power button to shut it off immediately.
Once you've done that, run the "usb_install_fff_twrp" script from Terminal. It'll say that its waiting for an OMAP device. Here's where the shorting comes in. Short the pad circled in the picture in this post to the metal frame around the CPU:
http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51
Then, keeping it shorted, press the power button.
Firekit should see the device over USB now, and write the appropriate settings. Once booted to TWRP, you should be able to install the stock firmware from /sdcard/.
It might take a couple tries, but keep trying. I used a continuity tester with an LED in it to make sure I had shorted that pad correctly.
Click to expand...
Click to collapse
Well it worked the first time. I was able to get it to boot and the FireKit utility installed TWRP and I was able to flash the stock rom. After doing that, I disconnected the USB cable and the KIndle immediately shut off and I can't get it to turn back on. What did I do wrong?! Is it fried or something?
--
caseym
caseym said:
Well it worked the first time. I was able to get it to boot and the FireKit utility installed TWRP and I was able to flash the stock rom. After doing that, I disconnected the USB cable and the KIndle immediately shut off and I can't get it to turn back on. What did I do wrong?! Is it fried or something?
--
caseym
Click to expand...
Click to collapse
I'm afraid I've got nothing for you at this point. Hopefully someone more knowledgeable than I can sound off.
A very good friend of mine donated me his Kindle Fire; because he doesn't like it, and OS from Amazon in particular.
I've tried to root the kindle following this: http://forum.xda-developers.com/showthread.php?t=2074565; but the process always went with errors, reporting that some files do not exist. I am using NixOS at the moment and I haven't seen Windows since 2000, so please don't send me to Windows-only rooting.
After that, I tried to install 2nd bootloader/recovery, following the guide: http://forum.xda-developers.com/showthread.php?t=2100963; but something went wrong. I got blue fire logo, but it never booted and was stuck on the "loading" screen. I let the battery go flat; then charged from the wall charger and booted into normal mode - that went OK.
I am wondering if I have chosen wrong files or made a device identification error?
I know the kindle was bought from Amazon in November 2012 on promotional offer. The device information is the following: system version 10.4.6_user_4620220. Serial number D026 A0A0 2464 01LW.
Lilybet said:
A very good friend of mine donated me his Kindle Fire; because he doesn't like it, and OS from Amazon in particular.
I've tried to root the kindle following this: http://forum.xda-developers.com/showthread.php?t=2074565; but the process always went with errors, reporting that some files do not exist. I am using NixOS at the moment and I haven't seen Windows since 2000, so please don't send me to Windows-only rooting.
After that, I tried to install 2nd bootloader/recovery, following the guide: http://forum.xda-developers.com/showthread.php?t=2100963; but something went wrong. I got blue fire logo, but it never booted and was stuck on the "loading" screen. I let the battery go flat; then charged from the wall charger and booted into normal mode - that went OK.
I am wondering if I have chosen wrong files or made a device identification error?
I know the kindle was bought from Amazon in November 2012 on promotional offer. The device information is the following: system version 10.4.6_user_4620220. Serial number D026 A0A0 2464 01LW.
Click to expand...
Click to collapse
thats definately a kf2, if it got stuck on the blue logo then maybe you either didnt tell it to go into recovery or you forgot to flash a custom recovery. as long as you have the blue logo i believe you can get into fastboot without a fastboot cable and flash a custom recovery. Or try boting into it with the key combo for kf2 that i don't know of offhand.
stunts513 said:
thats definately a kf2, if it got stuck on the blue logo then maybe you either didnt tell it to go into recovery or you forgot to flash a custom recovery. as long as you have the blue logo i believe you can get into fastboot without a fastboot cable and flash a custom recovery. Or try boting into it with the key combo for kf2 that i don't know of offhand.
Click to expand...
Click to collapse
Thanks. Perhaps I made a mistake falshing recovery. Fixed now, TWRP works OK.
Now I am stuck with getting a working combination of ROM + GAPPS: Tried
1) cm-10.2-20131102-SNAPSHOT-M1-otter2.zip + gapps-jb-20130813-signed.zip --- get "unfortunately com.android.phone stopped".
2) cm-10.2-20131102-SNAPSHOT-M1-otter2.zip + gapps-jb-20130301-signed.zip --- get "unfortunately, android keyboard (AOSP) stopped" Clear data + clear cashe do not solve the problem.
3) cannot flash any cm-11 from download.cyanogenmod.org/?device=otter2&type=snapshot : get message set_metadata_recursive: some changes failed. E: Error executing updater binary in zip 'sdcard/cm-11*/ Error flashing zip 'cm-11-*'.
Something is telling me that TWRP v2.6.3.0 is not compatible with CM11 and Android KK. Is it correct?
Thus I need a working combination of CM10.? and JB GAPPS.
Tried this one early morning today: http://forum.xda-developers.com/showthread.php?t=2146030
Flashing was OK, but cannot boot afterwards: get a screen with rotating/flying triangles, nothing else.
Alright, the only combination with CM 10.2 that works at this moment for me is JB 4.3 with CM10.2/SGT7:
http://forum.xda-developers.com/showthread.php?t=2416561&nocache=1
The other threads seem to have links incompatible roms/gapps due to updates...
I followed the extra steps on this guide: http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ to try and get the downgrade to proceed. But it didn't work.
This is my first Fire TV wouldn’t allow the downgrade update to run. So I followed the extra steps, but it didn’t work. I get a “No space left on device” error. http://imgur.com/76wW5n8
And when I tried recovery reboot, it just sits on the white amazon logo now. I can boot normally with no problem though. Just getting to recovery seems to be an issue now.
Any ideas? It’s a brand new FireTV so there shouldn’t be anything filling up the space. And I deleted the update.zip from /cache before attempting it.
modstore said:
I followed the extra steps on this guide: http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ to try and get the downgrade to proceed. But it didn't work.
This is my first Fire TV wouldn’t allow the downgrade update to run. So I followed the extra steps, but it didn’t work. I get a “No space left on device” error. http://imgur.com/76wW5n8
And when I tried recovery reboot, it just sits on the white amazon logo now. I can boot normally with no problem though. Just getting to recovery seems to be an issue now.
Any ideas? It’s a brand new FireTV so there shouldn’t be anything filling up the space. And I deleted the update.zip from /cache before attempting it.
Click to expand...
Click to collapse
Never mind, I downloaded the full rom rather than recovery image, thanks to rbox for alerting me to this :S
modstore said:
Never mind, I downloaded the full rom rather than recovery image, thanks to rbox for alerting me to this :S
Click to expand...
Click to collapse
I am stuck on the exact same error. Had to follow additional steps. Could you please describe what you meant by 'downloading a full rom instead of recovery'? Thanks
hello i recently rooted and installed cm11 on my FP, i just did a clean system partition flash, then flashed pa_gapps. now screen is stuck at black screen with amazon logo. what should i do? i did get the phone to connect to the pc, i got it working using the stock usb cord phone came with. now the phone not connecting to pc anymore.
what can i do to return the phone to factory setting? or at least to get the cm11 running.
azheng said:
hello i recently rooted and installed cm11 on my FP, i just did a clean system partition flash, then flashed pa_gapps. now screen is stuck at black screen with amazon logo. what should i do? i did get the phone to connect to the pc, i got it working using the stock usb cord phone came with. now the phone not connecting to pc anymore.
what can i do to return the phone to factory setting? or at least to get the cm11 running.
Click to expand...
Click to collapse
You mentioned clean partition flash and pa gapps but you didn't say you flash the cm11 zip. I assume you did? If not there's no os. Twrp will notify if the os isn't there but not sure about safestrap. I'd assume you need to flash it in fastboot now unless there's a button combo that can be utilized.
I'd take this to the cm11 thread. ggow might be able to assist.
KLit75 said:
You mentioned clean partition flash and pa gapps but you didn't say you flash the cm11 zip. I assume you did? If not there's no os. Twrp will notify if the os isn't there but not sure about safestrap. I'd assume you need to flash it in fastboot now unless there's a button combo that can be utilized.
I'd take this to the cm11 thread. ggow might be able to assist.
Click to expand...
Click to collapse
well problem is i cant even get into safestrap recovery right now. when i hard reset the phone, try to boot it. its stuck at amazon screen. good thing right now is when i plug the phone in the pc, it makes connection. maybe i can sideload a os using the pc?
azheng said:
well problem is i cant even get into safestrap recovery right now. when i hard reset the phone, try to boot it. its stuck at amazon screen. good thing right now is when i plug the phone in the pc, it makes connection. maybe i can sideload a os using the pc?
Click to expand...
Click to collapse
That probably IS a good thing. But if there's no OS installed I'd think it would automatically boot to recovery? I've only owned this phone a short time and before last week never used safestrap. Normally I'd either try to boot recovery with a button combo (haven't needed to on this phone.) Or connect via adb and use the command "adb reboot recovery".
I'd say you have a better chance or at least a quicker response if you head over to ggow's thread. Good luck
KLit75 said:
That probably IS a good thing. But if there's no OS installed I'd think it would automatically boot to recovery? I've only owned this phone a short time and before last week never used safestrap. Normally I'd either try to boot recovery with a button combo (haven't needed to on this phone.) Or connect via adb and use the command "adb reboot recovery".
I'd say you have a better chance or at least a quicker response if you head over to ggow's thread. Good luck
Click to expand...
Click to collapse
thanks for the help, i think recovery went bye bye along with the OS lol
Hi,
any update on this thread? I've been stuck also. I had safestrap. I supposed to flash a cleamsystempartion but I accidentally restart it without flashing new rom and now i am stuck in Fire Phone Logo. I still can access the stock recovery tho. Please help :crying::crying::crying:
try to flash your phone back to stock rom
any solution to this problem? I am stuck with same problem.
siddharth_bhal said:
any solution to this problem? I am stuck with same problem.
Click to expand...
Click to collapse
same problem here: can't start safe stripe and stuck at Amazon. tried to start the phone pressing volume up and power button, see if you can get into the build-in recovery. if it works, you can wipe the data and then use ADB sideload to flash in official rom (should be a bin file, i tried 4.6.1 version) and bring back your phone .
fire phone keep rebooting
my fire phone is keep rebooting with amazon logo up to 5 minutes and suddenly turned of i want to know the problem and how to fix it so please help me.
Have any of you guys tried the instructions in this thread: https://forum.xda-developers.com/fire-phone/general/reverting-fire-phone-to-stock-t3288890
I have bricked Fire phone quite a few times and everytime I followed his instructions and the lifehacker instructions that he linked to install adb and ADB sideloaded 4.6.6.1. without any problems.
My fire keeps rebooting and gets stuck with the amazon logo on it pls i need ur help urgently
Bahdtyga said:
My fire keeps rebooting and gets stuck with the amazon logo on it pls i need ur help urgently
Click to expand...
Click to collapse
U need a new fire phone, talk with amazon from your country or region or the seller from where you got fire phone!