Fire Stick Gen 2 in bootloop after failed update - Fire TV Q&A, Help & Troubleshooting

Good day community,
My Stick Gen 2 tried to do an update and somehow got bricked. The stick boots up to "installing new updates" then goes into a bootloop.
I tried the unbrick/root solution but the stick does not boot into fastboot, but instead tries to install updates again.
Is there a way to cancel this update step and just flash a stock rom?
Your help is much appreciated!
Regards
Phaisto

Phaisto said:
Good day community,
My Stick Gen 2 tried to do an update and somehow got bricked. The stick boots up to "installing new updates" then goes into a bootloop.
I tried the unbrick/root solution but the stick does not boot into fastboot, but instead tries to install updates again.
Is there a way to cancel this update step and just flash a stock rom?
Your help is much appreciated!
Regards
Phaisto
Click to expand...
Click to collapse
If you have done the unlock/root thing, you can boot to twrp recovery with the boot-recovery script... take a look in the unlock thread.
In TWRP you can flash the latest prerooted rom for your 'tank' device (or a stock update.bin renamed to zip, if you have one), wipe cache and dalvic cache.
Before you reboot, you could delete the ota update file, it's on sdcard... you can google the path. Then reboot.

Sus_i said:
If you have done the unlock/root thing, you can boot to twrp recovery with the boot-recovery script... take a look in the unlock thread.
In TWRP you can flash the latest prerooted rom for your 'tank' device (or a stock update.bin renamed to zip, if you have one), wipe cache and dalvic cache.
Before you reboot, you could delete the ota update file, it's on sdcard... you can google the path. Then reboot.
Click to expand...
Click to collapse
Hi, thanks for your quick reply!
Unfortunately the unlock doesn't run through, it does not boot into the fastboot mode, so I can not run fastboot-step, and therefore I do not have twrp...
Is there an other option to send a "kill-order" to stop the installing? Maybe during bootrom step?
Adb is not available....

Phaisto said:
Hi, thanks for your quick reply!
Unfortunately the unlock doesn't run through, it does not boot into the fastboot mode, so I can not run fastboot-step, and therefore I do not have twrp...
Is there an other option to send a "kill-order" to stop the installing? Maybe during bootrom step?
Adb is not available....
Click to expand...
Click to collapse
Is the ota really looping?
You see the update screen?
You may test the first script again. Start it, then plug the stick in without any short...
Then report back, please

Sus_i said:
Is the ota really looping?
You see the update screen?
You may test the first script again. Start it, then plug the stick in without any short...
Then report back, please
Click to expand...
Click to collapse
Yes, I see the update screen, the bootrom-step goes through until the script says "reboot to fastboot". When I put sudo bash fastboot- step.sh, it's just waiting for device and the update loops again...
https://photos.app.goo.gl/cnz3JEwhQL1G4Gbp7
https://photos.app.goo.gl/SNK9c7Ly43a3NuVx6
If I plug the stick in without short, the bootrom-step is waiting for device...

Phaisto said:
Yes, I see the update screen, the bootrom-step goes through until the script says "reboot to fastboot". When I put sudo bash fastboot- step.sh, it's just waiting for device and the update loops again...
https://photos.app.goo.gl/cnz3JEwhQL1G4Gbp7
https://photos.app.goo.gl/SNK9c7Ly43a3NuVx6
If I plug the stick in without short, the bootrom-step is waiting for device...
Click to expand...
Click to collapse
ok, don't know, maybe @k4y0z can tell you what to do...
Edit: I suppose you have disabled modemmanager and installed the required packages, i.e python3 python3-serial adb-tools-adb adb-tools-fastboot ??

Sus_i said:
ok, don't know, maybe @k4y0z can tell you what to do...
Edit: I suppose you have disabled modemmanager and installed the required packages, i.e python3 python3-serial adb-tools-adb adb-tools-fastboot ??
Click to expand...
Click to collapse
Yes, all the packages are installed as in the unlock threat, I copy/pasted the inputs. Modemmanager was removed as well.

Phaisto said:
Yes, all the packages are installed as in the unlock threat, I copy/pasted the inputs. Modemmanager was removed as well.
Click to expand...
Click to collapse
Ok, I've seen that behavior somewhere months ago, but I can't remember what causes that.
Unfortunately you can't delete the update package without adb... and you need twrp to flash a new system.
Your best bet is to do the unlock, flash a prerooted rom, flash magisk.zip, wipe cache and dalvic, and then delete that update package with adb shell:
Code:
rm -f /sdcard/Android/data/com.amazon.device.software.ota/files/*.bin
or twrp file manager, if you have an otg cable and a mouse.

Sus_i said:
Ok, I've seen that behavior somewhere months ago, but I can't remember what causes that.
Unfortunately you can't delete the update package without adb... and you need twrp to flash a new system.
Your best bet is to do the unlock, flash a prerooted rom, flash magisk.zip, wipe cache and dalvic, and then delete that update package with adb shell:
or twrp file manager, if you have an otg cable and a mouse.
Click to expand...
Click to collapse
That was exactly my plan for unlocking the stick in the hope of deleting that pesky update file. But I can not manage to get the twrp installed. As far I can understand it is installed with the fastboot-step script. But to execute this script I need the stick to enter fastboot, somehow the update is blocking that. Is there a way to modify the bootrom-step script to delete it, or wipe something?

Phaisto said:
That was exactly my plan for unlocking the stick in the hope of deleting that pesky update file. But I can not manage to get the twrp installed. As far I can understand it is installed with the fastboot-step script. But to execute this script I need the stick to enter fastboot, somehow the update is blocking that. Is there a way to modify the bootrom-step script to delete it, or wipe something?
Click to expand...
Click to collapse
No. You can't improve the scripts
Usually that whole unlock thing is done in 5 minutes, including booting linux and disassemble the stick
Something must be wrong on your side.

Sus_i said:
No. You can't improve the scripts
Usually that whole unlock thing is done in 5 minutes, including booting linux and disassemble the stick
Something must be wrong on your side.
Click to expand...
Click to collapse
I meant, if there is a possibility to add a function to the script to delete the update.
And yes, I know that the scripts are very good, and I also realize that the issue is with my stick not the script....

Phaisto said:
I meant, if there is a possibility to add a function to the script to delete the update.
And yes, I know that the scripts are very good, and I also realize that the issue is with my stick not the script....
Click to expand...
Click to collapse
Why you run the scripts with bash instead of dash?
Have you downloaded and extracted the amonet.zip with windows?
You may test this out...
Plug your stick into a hdmi port. Run the boot-fastboot script with:
sudo ./boot-fastboot.sh
then power the stick with your laptop.
If you see on your TV down in the left corner a hacked fastboot message together with the amz. logo, it worked.
You can then try a fastboot devices...

Sus_i said:
Why you run the scripts with bash instead of dash?
Have you downloaded and extracted the amonet.zip with windows?
You may test this out...
Plug your stick into a hdmi port. Run the boot-fastboot script with:
sudo ./boot-fastboot.sh
then power the stick with your laptop.
If you see on your TV down in the left corner a hacked fastboot message together with the amz. logo, it worked.
You can then try a fastboot devices...
Click to expand...
Click to collapse
I have downloaded the zip- files with Ubuntu and extracted as well. I used bash, as I saw it in the posts as a possible fix to problems, but my Linux knowledge is limited so I just used it without thinking about it....
I just tried your suggestions, but no luck. The stick stays on the Amazon logo and doesn't go into the update cycle ( maybe small victory?).
I tried to redo the bootrom step, after it finished, took the USB off, run boot-fastboot followed by fastboot-step, but as you can see, still stuck in waiting for device....
https://photos.app.goo.gl/BAL9V2sQhjowTq498
https://photos.app.goo.gl/iL5D3meE6LgNjdDW8
Any ideas?
Update: the device shows up on adb now, but unfortunately it is unauthorized.... Any chance to fix this?

Phaisto said:
I just tried your suggestions, but no luck. The stick stays on the Amazon logo and doesn't go into the update cycle ( maybe small victory?).
Click to expand...
Click to collapse
probably it goes into fastboot, but maybe not the unlocked hacked one
Phaisto said:
I tried to redo the bootrom step, after it finished, took the USB off, run boot-fastboot followed by fastboot-step, but as you can see, still stuck in waiting for device....
Any ideas?
Click to expand...
Click to collapse
have you tried to run: fastboot devices
behind the boot-fastboot script?
Phaisto said:
Update: the device shows up on adb now, but unfortunately it is unauthorized.... Any chance to fix this?
Click to expand...
Click to collapse
With TWRP shell you can authorize ADB access, like you can see in this link.
But without TWRP this won't work.

Sus_i said:
probably it goes into fastboot, but maybe not the unlocked hacked one
have you tried to run: fastboot devices
behind the boot-fastboot script?
With TWRP shell you can authorize ADB access, like you can see in this link.
But without TWRP this won't work.
Click to expand...
Click to collapse
No luck with fastboot devices:
https://photos.app.goo.gl/bd4Qrjr6si9b9gZm9
How come the script doesn't let the stick boot into hacked fastboot mode?
Anyone an idea?

Phaisto said:
No luck with fastboot devices:
https://photos.app.goo.gl/bd4Qrjr6si9b9gZm9
How come the script doesn't let the stick boot into hacked fastboot mode?
Anyone an idea?
Click to expand...
Click to collapse
I had trouble running the boot-fastboot script with ubuntu, debian worked as expected.
I would try also an other usb port/cable/hub.
Since amz. can't patch the exploit, there isn't a reason why it should not work.

Sus_i said:
I had trouble running the boot-fastboot script with ubuntu, debian worked as expected.
I would try also an other usb port/cable/hub.
Since amz. can't patch the exploit, there isn't a reason why it should not work.
Click to expand...
Click to collapse
Debian did not work either, same result....
Changing cable, same result....
I suspect, the bootrom-step script can't write the hacked fastboot...
Does anyone have an other idea how to fix this stick?
Amazon took the lazy way out and just offered 15% discount.... On a device their update broke....

Related

BRICKED Galaxy Nexus - please help me restore/advice

Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
This ISN'T Resolved. I get errors when attempting to fastboot the stock image
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
If anybody has any ideas please let me know, I really don't know what to do at this point.
grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Okay your bootloader is unlocked which is good, but your MAC doesn't see your phone in bootloader mode?
grnmons said:
Plan B is to use a PC which I can only access later in the week.
Click to expand...
Click to collapse
Can you bootcamp or use a virtual machine?
grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Wrong section..but
I would def use a PC and use Odin ! Make your life easier...it takes like 3-5 Mins..takes it to stock!
Sent from my Galaxy Nexus using xda premium
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Sent from my Galaxy Nexus using Tapatalk
Please uninstall and reinstall your phones drivers. Your just soft bricked is all. Once your computer sees the device you should be good.
sent from the Almighty One himself....
borgey said:
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Click to expand...
Click to collapse
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
grnmons said:
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
Click to expand...
Click to collapse
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
zephiK said:
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Thanks. Can you confirm that these are the steps?
1) Download the latest stock image( i will leave finding that image to you since this post can become outdated)
2) Unzip the files, and place the images into the adb-fastboot folder you created on your desktop above.
3) Open a terminal and use the following commands:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
4) Wait for bootloader to reboot on phone.
5) Then, in terminal use the following commands:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
~/Desktop/adb-fastboot/fastboot flash system ~/Desktop/adb-fastboot/system.img
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery.img
~/Desktop/adb-fastboot/fastboot flash userdata ~/Desktop/adb-fastboot/userdata.img
~/Desktop/adb-fastboot/fastboot erase cache
~/Desktop/adb-fastboot/fastboot oem lock
6) Reboot to System, and you should be returned to Stock and Unrooted
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
anybody have any other suggestions to this? or a follow up?
It should be easy to fix. You do not seem to have the correct driver installed.
Sent from my Galaxy Nexus using xda premium
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
grnmons said:
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
Click to expand...
Click to collapse
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
ogdobber said:
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
Click to expand...
Click to collapse
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
grnmons said:
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
Click to expand...
Click to collapse
download the gnex-su.zip and put in in the root of your sd card. then in recovery select "-install zip from sdcard" then "-choose zip from sdcard" then select the gnex-su.zip. this will give you root and install the superuser app
not to get ahead (previous post), but after your computer recognizes the phone you need to flash clockwork recovery
you need to open a terminal in the platform-tools folder of the sdk (also put the recovery.img there) and then
Code:
fastboot flash recovery name-of-recovery.img
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Just got your last post, I'm unfamiliar with SDK but I've since put the recovery file in there, not sure how to flash recovery. I have tried flashing recovery through terminal and surprisingly it says "-bash: fastboot: command not found"
grnmons said:
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Click to expand...
Click to collapse
that is for the nexus s
check your pm
ogdobber said:
that is for the nexus s
check your pm
Click to expand...
Click to collapse
If you are still having problems ...like I said before ...use Odin......since the simple process of fastboot is not working properly for you.Odin makes things so Much easier
Sent from my Galaxy Nexus using xda premium

[Q] Recovering Verizon Galaxy Nexus

Hey all, I got a new Galaxy Nexus today and went about rooting it. Apparently something didn't happen correctly and now I'm caught in the kernel boot screen ("Google" with unlocked lock) loop. I'm surprised by this because I've rooted another and haven't had a problem. I've tried running `fastboot flash system ~/Downloads/aokp_toro_jb-build-1.zip` and that hasn't helped the boot loop.
Did you get a custom recovery (cwm.. twrp) loaded ... what steps did you perform to root and what was the last step before the looping?
pepp67 said:
Did you get a custom recovery (cwm.. twrp) loaded ... what steps did you perform to root and what was the last step before the looping?
Click to expand...
Click to collapse
First I flashed 'recovery-clockwork-touch-6.0.1.0-toro' with `fastboot flash recovery recovery-clockwork-touch-6.0.1.0-toro.img`. Then I ran `fastboot oem unlock` and tried `adb push ~/Downloads/su.zip /sdcard/Downloads` and kept getting the error:
"ERROR: could not get pipeline properties"
But then it would give me file transfer job output.
I have tried using CWM recovery for flashing `su.zip` and a new system image (AOKP), but whenever I try to do anything that interacts with the file system or sdcard I get this output:
`Couldn't open directory.
Couldn't open directory.
No files found.`
Actually, now that I think about it I didn't turn USB Debugging on before I tried everything, would that be what wasn't allowing me to access the pipeline properties?
read this, before you mess up for real.
Sent from my i9250
bk201doesntexist said:
read this, before you mess up for real.
Sent from my i9250
Click to expand...
Click to collapse
I followed all of those instructions and I'm still caught in the boot loop. I did notice though that the `userdata.img` and `boot.img` weren't included in the .tgz that I downloaded for my toro.
JustLikeThat said:
First I flashed 'recovery-clockwork-touch-6.0.1.0-toro' with `fastboot flash recovery recovery-clockwork-touch-6.0.1.0-toro.img`. Then I ran `fastboot oem unlock` and tried `adb push ~/Downloads/su.zip /sdcard/Downloads` and kept getting the error:
"ERROR: could not get pipeline properties"
But then it would give me file transfer job output.
I have tried using CWM recovery for flashing `su.zip` and a new system image (AOKP), but whenever I try to do anything that interacts with the file system or sdcard I get this output:
`Couldn't open directory.
Couldn't open directory.
No files found.`
Actually, now that I think about it I didn't turn USB Debugging on before I tried everything, would that be what wasn't allowing me to access the pipeline properties?
Click to expand...
Click to collapse
yeah its most likely the fact you didnt have usb debuggin on
JustLikeThat said:
First I flashed 'recovery-clockwork-touch-6.0.1.0-toro' with `fastboot flash recovery recovery-clockwork-touch-6.0.1.0-toro.img`. Then I ran `fastboot oem unlock` and tried `adb push ~/Downloads/su.zip /sdcard/Downloads` and kept getting the error:
"ERROR: could not get pipeline properties"
But then it would give me file transfer job output.
I have tried using CWM recovery for flashing `su.zip` and a new system image (AOKP), but whenever I try to do anything that interacts with the file system or sdcard I get this output:
`Couldn't open directory.
Couldn't open directory.
No files found.`
Actually, now that I think about it I didn't turn USB Debugging on before I tried everything, would that be what wasn't allowing me to access the pipeline properties?
Click to expand...
Click to collapse
in parts:
JustLikeThat said:
First I flashed 'recovery-clockwork-touch-6.0.1.0-toro' with `fastboot flash recovery recovery-clockwork-touch-6.0.1.0-toro.img`. Then I ran `fastboot oem unlock`
Click to expand...
Click to collapse
first you unlock, then you flash a custom recovery...
JustLikeThat said:
and tried `adb push ~/Downloads/su.zip /sdcard/Downloads` and kept getting the error:
"ERROR: could not get pipeline properties"
But then it would give me file transfer job output.
Click to expand...
Click to collapse
do you see your device's SN under 'adb devices' output?
JustLikeThat said:
I have tried using CWM recovery for flashing `su.zip` and a new system image (AOKP), but whenever I try to do anything that interacts with the file system or sdcard I get this output:
`Couldn't open directory.
Couldn't open directory.
No files found.`
Click to expand...
Click to collapse
what cwm version are you using?
JustLikeThat said:
Actually, now that I think about it I didn't turn USB Debugging on before I tried everything, would that be what wasn't allowing me to access the pipeline properties?
Click to expand...
Click to collapse
unrelated, in recovery at least. a custom recovery would be meaningless without adb support. inside android itself, yes, of course, if usb debugging is not on, you can't use adb.
JustLikeThat said:
I've tried running `fastboot flash system ~/Downloads/aokp_toro_jb-build-1.zip` and that hasn't helped the boot loop.
Click to expand...
Click to collapse
of course it didn't work, that zip is probably packed for CWM/TWRP! you don't know what you're doing man, just read, read it again, read it one more time, and again re-read the thread that I posted, that will lead you unlock bootloader and get your device back to JB STOCK (!) through fastboot, since google-provided stock fastboot images are available for toro (you're SURE you have a toro, right? as in, Verizon Galaxy Nexus, right? just checking).
THEN you can flash a custom recovery, and a custom rom.
Well I found the correct stock image and just decided to start from square 1.
Sorry for the vague question and ignorance. I was honestly incredibly stoned when I wrote it and was doing this, attributing to the facts that I rushed everything, assumed I knew more about what I was doing than I did and didn't verify the md5's of the downloaded files. Thanks for being so thorough @bk201doesntexist, I'll be more careful round 2.
JustLikeThat said:
Well I found the correct stock image and just decided to start from square 1.
Sorry for the vague question and ignorance. I was honestly incredibly stoned when I wrote it and was doing this, attributing to the facts that I rushed everything, assumed I knew more about what I was doing than I did and didn't verify the md5's of the downloaded files. Thanks for being so thorough @bk201doesntexist, I'll be more careful round 2.
Click to expand...
Click to collapse
thanks. you got it, hash check is one of the best ways to check a file is good to go. although i'm not by any means a cryptography expert, i suggest you use sha256sum instead, safer than md5sum (i don't think we have found how to fully mitm or fully collision a sha-1 hash, let alone a sha-2 family hash). just something for everyone to think about, md5sum will suffice if you not all that worried.
also, remember that if some image is broken (corrupted), you'll never be able to flash it through fastboot.

[Q] twrp fails doing anything, no os(?)

Ive been working on this kindle fire for the last 2-3 days.Here's what I know I can do:
I can issue commands in fastboot mode
I can issue commands in adb mode
I can even mount the kindle to my PC as a SDcard (when I give it the command in adb)
I checked the partitions and they seem to be stock, (ext4 on data, cache ect.) I ran the oem command anyways just to make sure.
However it appears nothing within TWRP actually works. Wiping anything just comes back with a failed message (right after verifying file systems), trying to load a ROM will act like it doing something (200mb file done in 2seconds) but really doesnt. Im not really sure where to go from here, it just appears that there is nothing on the kindle, no OS or otherwise, and I cant seem to find a way to load one.
Thanks in advance!
Which version of TWRP are you using?
Thepooch said:
Which version of TWRP are you using?
Click to expand...
Click to collapse
2.2.1, I believe its the latest version.
You have some kind of mounting issue use soupkit http://forum.xda-developers.com/showthread.php?t=1850038 .
Thepooch said:
You have some kind of mounting issue use soupkit http://forum.xda-developers.com/showthread.php?t=1850038 .
Click to expand...
Click to collapse
That did the trick, kindle back up and running. Thanks a ton!

Attempted to root, maybe bricked, can I recover?

Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
enjoyingsilence said:
Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
Click to expand...
Click to collapse
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
monster1612 said:
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
Click to expand...
Click to collapse
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
enjoyingsilence said:
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
Click to expand...
Click to collapse
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
monster1612 said:
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
Click to expand...
Click to collapse
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
enjoyingsilence said:
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
Click to expand...
Click to collapse
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
monster1612 said:
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
Click to expand...
Click to collapse
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
enjoyingsilence said:
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
Click to expand...
Click to collapse
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
monster1612 said:
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
Click to expand...
Click to collapse
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
enjoyingsilence said:
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
Click to expand...
Click to collapse
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
monster1612 said:
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
Click to expand...
Click to collapse
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
edit: Found the latest CM ROM and Gapps files. Just need options for full recovery back to FireOS if needed in the end.
enjoyingsilence said:
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
Click to expand...
Click to collapse
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
monster1612 said:
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
Click to expand...
Click to collapse
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
enjoyingsilence said:
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
Click to expand...
Click to collapse
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
enjoyingsilence said:
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
Click to expand...
Click to collapse
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
monster1612 said:
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
Click to expand...
Click to collapse
Thanks. I was able to update twrp and get the 23rd of Dec's nightly CM12 build installed. It didn't seem to work properly though, and gapps wouldn't install. So I've resigned to the fact that I need to put the original OS back on it. After updating twrp, this doesn't seem possible. When I connect it to the computer, all I'm getting is error: device offline when typing adb shell. This is in linux and windows.
I tried connecting it and mounting the usb storage, then dragging over the fireos images, but after installation it went into this reboot loop due to a corrupt something or other... Now, I can't get cm or the original os back on it.
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
enjoyingsilence said:
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
Click to expand...
Click to collapse
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
monster1612 said:
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
Click to expand...
Click to collapse
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
enjoyingsilence said:
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
Click to expand...
Click to collapse
Do you have adb installed system-wide? If you do, try cd'ing to the directory where you placed the boot, recovery, and system images and then running those commands again. If you don't, then move the files to the folder where the adb and fastboot executables are located and run the commands in that folder.

Developer Options Off and no OS. only TWRP.

Hello I have an urgent request. My phone isn't working currently because I tried to switch kernels but ended up flashing the wrong boot.img and was stuck on boot. With g logo.
Now whenever I try to boot system it goes to TWRP. due to bank of America app not allowing developer options, I had it turned off but I know USB debugging was on. When I used Tool All in one, it did recognize my phone but typing adb devices on command prompt doesn't show anything. Please help!!!
Flash magisk
@trizzv: There should be two ways for you to resolve your issue. The first and arguably the least painful is to change your slot and reboot, which you can do in the reboot menu of TWRP. The second is to download the latest full OTA image from Google and flash it through TWRP. And yes, flashing the OTA through TWRP will work, although you will end up losing TWRP and will need to reinstall it after fully booting the system.
@akellar: His boot.img is the wrong one. Flashing Magisk won't help here, based upon what trizzv has said.
Flash flactory image if all else fails. Don't panic. I got into a similar situation.
Strephon Alkhalikoi said:
@trizzv: There should be two ways for you to resolve your issue. The first and arguably the least painful is to change your slot and reboot, which you can do in the reboot menu of TWRP. The second is to download the latest full OTA image from Google and flash it through TWRP. And yes, flashing the OTA through TWRP will work, although you will end up losing TWRP and will need to reinstall it after fully booting the system.
@akellar: His boot.img is the wrong one. Flashing Magisk won't help here, based upon what trizzv has said.
Click to expand...
Click to collapse
I can't drag any files to my phone and right now it doesn't have anything-- magisk, TWRP file, or boot.img
azpatterson3 said:
Flash flactory image if all else fails. Don't panic. I got into a similar situation.
Click to expand...
Click to collapse
What would be the steps? Fastboot? Tried that but I couldn't get it to work
trizzv said:
What would be the steps? Fastboot? Tried that but I couldn't get it to work
Click to expand...
Click to collapse
https://developers.google.com/android/images
If for some reason it won't write and ends with an error. Open the flash script and remove the "-w" on the last line before it says "update"
I wonder, since you can boot into TWRP, if sideloading an OTA image won't fix your boot partition -- as I understand it, OTA's would overwrite and essentially reinstall/reinitialize the boot partition... If others concur or you decide you wish to try this route, say so and I could lay out steps to take...
But, if anything, reboot into Bootloader (can be done from TWRP), open up a command prompt (elevated, or powershell if you're more familiar with), have it directed at your platform-tools folder (or whatever folder you have adb.exe and fastboot.exe), and input the commands
Code:
fastboot --version
and
Code:
adb devices
*to load emulator and such...
if, after all of this, those two commands return info without an error, that should establish that you would be good to go in re-flashing the boot partition (as well as the system, vendor, modem, etc.) without losing any data and, at the very least, confirm that you have fastboot working...
do these and get back to us/me and can take steps from there towards repairing your pixel...
use Deuces Bootloop-Recovery & Flashing Script and just follow instruction :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
simplepinoi177 said:
I wonder, since you can boot into TWRP, if sideloading an OTA image won't fix your boot partition -- as I understand it, OTA's would overwrite and essentially reinstall/reinitialize the boot partition... If others concur or you decide you wish to try this route, say so and I could lay out steps to take...
But, if anything, reboot into Bootloader (can be done from TWRP), open up a command prompt (elevated, or powershell if you're more familiar with), have it directed at your platform-tools folder (or whatever folder you have adb.exe and fastboot.exe), and input the commands and *to load emulator and such...
if, after all of this, those two commands return info without an error, that should establish that you would be good to go in re-flashing the boot partition (as well as the system, vendor, modem, etc.) without losing any data and, at the very least, confirm that you have fastboot working...
do these and get back to us/me and can take steps from there towards repairing your pixel...
Click to expand...
Click to collapse
Please let me know what the steps are. Will try it today.
trizzv said:
Please let me know what the steps are. Will try it today.
Click to expand...
Click to collapse
...the suggestion @goti(0) actually gave is rather simpler, but do require pretty much the same steps (downloading factory image, extracting, placing the files in correct place, etc.)...
What did the commands return when you entered them? I am not reluctant to give you the steps, rather I gave you those commands to narrow down where your issues might be; if your fastboot and emulator aren't set up properly, giving you further steps might carry you down a less-stable and "skewed" path because things would be "based" at it's source incorrectly...
Let us/me know what those commands return and I'll get those steps to ya right away!
goti(0) said:
use Deuces Bootloop-Recovery & Flashing Script and just follow instruction :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
THIS WORKED!!!!! THANK YOU so much for the suggestion.
trizzv said:
THIS WORKED!!!!! THANK YOU so much for the suggestion.
Click to expand...
Click to collapse
it was a great suggestion...I'm glad it worked out for you! :victory:
Also you can just reflash corrupt boot.img the original for what image you have. You can load on flash drive through your type c .
There's a lot of ways to fix your stuff

Categories

Resources