[Q] Possible to flash update.zip from fastboot? - Kindle Fire Q&A, Help & Troubleshooting

I have a Kindle Fire that I rooted using KFU. FireFireFire and TWRP are both installed. It was working fine for a while, but after I installed the Google Apps and set up the Market account, the Kindle froze. After I turned it off (holding power for ~20 seconds) it would not turn back on for about a half hour. When it finally did turn on, it got through the FireFireFire bootloader screen and went to the regular loading screen, then froze on a black screen (but with the backlight on). I can boot into TWRP, and I have a stock update.zip on the Kindle already, but as soon as I touch Install the recovery freezes (the screen updates to the choose a file menu, but then I cannot select anything or go back).
With all that back story out of the way, I want to try to restore the Kindle Fire to stock and see if the problem persists. Well, I don't want to per se, but it's technically my girlfriend's Kindle Fire and that's what she wants. Since it can get to FireFireFire, I assume I can still use fastboot. I have read up on how to use fastboot to flash a new recovery or do a data wipe, but I was wondering if it is possible to use fastboot to flash the update.zip or update-kindle-6.3.1_D01E_4107720.bin? And if so, what would the command be? The fastboot section of the beginner's guide only mentioned flashing the individual pieces (boot, system, etc..).

It has been asked before if you can fastboot flash a rom to your kindle I dont believe that has been determined very good question so far I have not seen an answer. Im guessing flashing stock would fall under the same category. I would say no because when you fastboot flash its to a specific destination not multiple partitions.

I would boot to TWRP, select Wipe then do Cache, Dalvik Cache, and Factory Reset.
Then if you want the pure stock, then flash this version of Stock 6.3.1(No Bootloader or Recovery).
This will leave FFF and TWRP intact so if you need to get back to them.
If you do want Google play and Super User flash this file.

Tera Tike said:
I would boot to TWRP, select Wipe then do Cache, Dalvik Cache, and Factory Reset.
Then if you want the pure stock, then flash this version of Stock 6.3.1(No Bootloader or Recovery).
This will leave FFF and TWRP intact so if you need to get back to them.
If you do want Google play and Super User flash this file.
Click to expand...
Click to collapse
Thanks for the reply, however as mentioned I cannot do anything in Recovery. If I touch Wipe the same thing happens as with install, it freezes after I complete the first menu change.

I would re-install TWRP then and go from there.

Related

[Q] KF won't boot and is not recognized by KFU or adb

I just got a Kindle today and decided to root it. Here are my exact steps.
Downloaded latest KFU
Ran it, ran input 2 for permanent root
installed TWRP and FireFireFire
made a backup of my current rooted stock ROM
wiped everything
flashed CM9 reloaded ICS ROM
didn't like the ROM, so I went back into recovery
wiped everything
flashed AOKP ROM
reboot
and nothing.. the screen went black
I click the power button and the green light will come on and then everything goes black again
I reinstalled the drivers and got it to boot in recovery. I wiped cache, dalvik, and factory reset. I tried to boot but it won't boot into anything, it just turns off.
I'll try to restore my nandroid and see what that does
Edit: It rebooted into my nandroid of the stock ROM. Was it just a bad AOKP download? Should I run the perm root =, TWRP recovery instal and FireFireFire install on KFU again?
kendallc123 said:
I reinstalled the drivers and got it to boot in recovery. I wiped cache, dalvik, and factory reset. I tried to boot but it won't boot into anything, it just turns off.
I'll try to restore my nandroid and see what that does
Edit: It rebooted into my nandroid of the stock ROM. Was it just a bad AOKP download? Should I run the perm root =, TWRP recovery instal and FireFireFire install on KFU again?
Click to expand...
Click to collapse
I have no idea why your AOKP install failed, but you should check the MD5 sum on those zip files before you flash any new ROM. You don't need to root stock again if you intend to flash a new ROM, but make sure you have TWRP 2.1.1 and FFF 1.4a installed on your device before you try it again. As long as you have those two piece in place, you can get back to recovery and flash something again if anything else should go wrong.
Download a new update zip and give it a try!! check md5 sum first!!
Alright I have never checked an md5sum. I never really knew it was important! I found out how yo do it and what program to use, so I will definitely do that next time! Thanks

kindle fire in boot loop. Howto for restoring with fastboot?

I wanted to get 4.2.2 on my fire2, so I went throught the tutorials to root and install twrp recovery which worked great. I downloaded the CM10.1 sgt7 and gapps for the fire 2 in the dev section and proceeded to reboot into recovery. I wiped the system and flashed the rom and gaps, wiped cache/dalvik and hit reboot.
dreaded kindle fire boot loop. The only thing I can think is that the rom DL was corrupted. It really didn't take long to complete the flash in twrp, probably less than 10 seconds. I really should have checked the md5.
OK, so I get a fastboot cable online and it shows up today. I can't seem to locate a tutorial of how to restore with fastboot though... can someone point me to a link?
Thanks,
-J
miatawnt2b said:
I wanted to get 4.2.2 on my fire2, so I went throught the tutorials to root and install twrp recovery which worked great. I downloaded the CM10.1 sgt7 and gapps for the fire 2 in the dev section and proceeded to reboot into recovery. I wiped the system and flashed the rom and gaps, wiped cache/dalvik and hit reboot.
dreaded kindle fire boot loop. The only thing I can think is that the rom DL was corrupted. It really didn't take long to complete the flash in twrp, probably less than 10 seconds. I really should have checked the md5.
OK, so I get a fastboot cable online and it shows up today. I can't seem to locate a tutorial of how to restore with fastboot though... can someone point me to a link?
Thanks,
-J
Click to expand...
Click to collapse
Can you get into recovery?
Always factory reset when flashing a ROM that is completely different from the one already installed, or you will run into a bootloop.
I was able to get it back. Been running 422 for a few months. I had a bad Roman do from what I can tell. I was not able to get to recovery without restoring with a fastboot cable.

[Q] Performed factory reset, now won't boot

I'm selling my HTC One (stock ROM, unlocked) so I wanted to wipe my data, apps and settings. I performed a factory reset/data wipe in CWM and rebooted and it would get stuck at the Verizon logo. I cleared cache, tried again, and got stuck at "Android is updating, Starting apps" for a good 20 minutes. Now it goes back to the Verizon logo.
Does the factory reset not leave the ROM intact? What can I do now just so it'll boot to a clean slate?
kram12085 said:
I'm selling my HTC One (stock ROM, unlocked) so I wanted to wipe my data, apps and settings. I performed a factory reset/data wipe in CWM and rebooted and it would get stuck at the Verizon logo. I cleared cache, tried again, and got stuck at "Android is updating, Starting apps" for a good 20 minutes. Now it goes back to the Verizon logo.
Does the factory reset not leave the ROM intact? What can I do now just so it'll boot to a clean slate?
Click to expand...
Click to collapse
Download the stock rooted odexed ROM from here: http://forum.xda-developers.com/showthread.php?t=2485319
After you flash it, wipe data and boot up.
Then flash the latest firmware and stock recovery through Fastboot (also that thread), and do another factory wipe using stock recovery.
Your S-Off / Unlocked status will not be affected by this.
NotATreoFan said:
Download the stock rooted odexed ROM from here: http://forum.xda-developers.com/showthread.php?t=2485319
After you flash it, wipe data and boot up.
Then flash the latest firmware and stock recovery through Fastboot (also that thread), and do another factory wipe using stock recovery.
Your S-Off / Unlocked status will not be affected by this.
Click to expand...
Click to collapse
Thanks for your help. Unfortunately, I've been at it for a good 5 hours now and I can't get past the first step.
Using TWRP, I've tried adb push <rom.zip> to /sdcard/, /mnt/sdcard/ and /data/media/ and every time it says it's successful, but the directories show up empty in TWRP. Without a removable SD card, I'm not sure how else I can get the ROM on the phone for flashing. I'm not sure if it's related or not, but everytime I reboot from TWRP, it says my phone isn't rooted. I select "Install" but it occurs again, even though supersu.apk is on the internal storage.
I also tried CWM but couldn't get past "format () expected 5 args, got 4. Installation aborted (Status 7)".
Does anyone have any suggestions on how I can get TWRP to flash the ROM? Thanks.
Try this cmd instead.
Code:
adb push nameofrom.zip /data/media/0/nameofrom.zip
kram12085 said:
Thanks for your help. Unfortunately, I've been at it for a good 5 hours now and I can't get past the first step.
Using TWRP, I've tried adb push <rom.zip> to /sdcard/, /mnt/sdcard/ and /data/media/ and every time it says it's successful, but the directories show up empty in TWRP. Without a removable SD card, I'm not sure how else I can get the ROM on the phone for flashing. I'm not sure if it's related or not, but everytime I reboot from TWRP, it says my phone isn't rooted. I select "Install" but it occurs again, even though supersu.apk is on the internal storage.
I also tried CWM but couldn't get past "format () expected 5 args, got 4. Installation aborted (Status 7)".
Does anyone have any suggestions on how I can get TWRP to flash the ROM? Thanks.
Click to expand...
Click to collapse
I recently returned my phone to stock in order to reset all the firmware and RIL data. Here is how I did it:
Enter recovery TWRP 2.6.3.4 (if you have 2.6.3.3 you may experience issues)
Boot into recovery, then format Data, System, Cache, and Internal Storage (this will leave the phone with NO ROM installed)
Reboot back into recovery. Answer No to the prompt to root your device.
Once back in recovery, Internal Memory will be available again (if you push the ROM before rebooting, it will not be there afterward)
Push the ROM using adb push ROM.zip /sdcard/ROM.zip (this will take 5-7 minutes for a 1.4GB file)
Flash the ROM in TWRP
Reboot when done, phone should boot up corrrectly
Reboot into Fastboot, push firmware.zip package
Reboot into ROM verify connectivity
Reboot into Fastboot, push stock recovery
Reboot into stock recovery, perform a Factory Reset
Boot into ROM
Once you are up and running on the latest 4.4.2 ROM with stock recovery, boot into Fastboot one last time and push TWRP 2.6.3.4. Your S-Off will not be affected and the new owner will be able to flash any ROMs they like.
If all of the above fails, then try using ADB Sideload from the Advanced menu in TWRP.
You guys are a life saver. TWRP 2.6.3.4 did the trick, it just wasn't available on the TWRP site so I didn't install it in the first place. Flashed the ROM and everything back to normal! Thanks for the help!
FWIW, none of the m7 versions of TWRP would load (stuck at "Entering Bootloader" screen). The Sprint version would load, but wouldn't mount the filesystem properly.
kram12085 said:
You guys are a life saver. TWRP 2.6.3.4 did the trick, it just wasn't available on the TWRP site so I didn't install it in the first place. Flashed the ROM and everything back to normal! Thanks for the help!
FWIW, none of the m7 versions of TWRP would load (stuck at "Entering Bootloader" screen). The Sprint version would load, but wouldn't mount the filesystem properly.
Click to expand...
Click to collapse
So what state is the phone in now? Stock w/ HTC recovery, or the Sprint TWRP?
NotATreoFan said:
So what state is the phone in now? Stock w/ HTC recovery, or the Sprint TWRP?
Click to expand...
Click to collapse
The former, stock. The Sprint TWRP loaded but didn't work right. I ended up finding 2.6.3.4 for VZW m7 on an xda thread, it's not on the TWRP site for some reason. That worked great.
kram12085 said:
The former, stock. The Sprint TWRP loaded but didn't work right. I ended up finding 2.6.3.4 for VZW m7 on an xda thread, it's not on the TWRP site for some reason. That worked great.
Click to expand...
Click to collapse
Excellent. Glad to see it all worked out.

[Q] Stuck in TWRP recovery

Ok, so I have a question that either does not exist on Google or that I just don't know how to explain.
My Kindle Fire 2 was flashed a while back with a stock version of Android Jellybean 4.2.2, until today. I made a complete backup of everything inside TWRP and transferred all of those backup files to my laptop. I then flashed a newer version of TWRP, version 2.6.3.1. After that, i flashed the newest version of Cyanogenmod 11, Android 4.4.4.
Anyways, I got to adjusting the settings and told it to allow me to pick between rebooting into recovery or normal mode when i pressed the reboot button on the power menu.
Here is my problem though. At one point, I told Cyanogenmod to reboot me into recovery, and ever since, my Kindle will only let me boot into the TWRP recovery area, regardless of what I tell it to load in the bootloader.
How can I just get it to boot to the normal OS? I've tried reflashing the recovery and reflashing Cyanogenmod onto it. I just don't know what to do because I don't know exactly why this is happening.
I've tried wiping the /data partition too, but to no use. I still am able to wipe internal data partition, however I don't know how it will respond to that. I mean... Isn't that where TWRP is stored? I don't want to lose my recovery partition where I have no way to get back.
If it comes to it, could I replace my recovery partition with Cyanogenmod?
I am still able to use ADB and I'm able to push files. (So far)
Possible solution
mayuri1 said:
Ok, so I have a question that either does not exist on Google or that I just don't know how to explain.
My Kindle Fire 2 was flashed a while back with a stock version of Android Jellybean 4.2.2, until today. I made a complete backup of everything inside TWRP and transferred all of those backup files to my laptop. I then flashed a newer version of TWRP, version 2.6.3.1. After that, i flashed the newest version of Cyanogenmod 11, Android 4.4.4.
Anyways, I got to adjusting the settings and told it to allow me to pick between rebooting into recovery or normal mode when i pressed the reboot button on the power menu.
Here is my problem though. At one point, I told Cyanogenmod to reboot me into recovery, and ever since, my Kindle will only let me boot into the TWRP recovery area, regardless of what I tell it to load in the bootloader.
How can I just get it to boot to the normal OS? I've tried reflashing the recovery and reflashing Cyanogenmod onto it. I just don't know what to do because I don't know exactly why this is happening.
I've tried wiping the /data partition too, but to no use. I still am able to wipe internal data partition, however I don't know how it will respond to that. I mean... Isn't that where TWRP is stored? I don't want to lose my recovery partition where I have no way to get back.
If it comes to it, could I replace my recovery partition with Cyanogenmod?
I am still able to use ADB and I'm able to push files. (So far)
Click to expand...
Click to collapse
I assuming you have a TWRP bootloop problem? Like everytime you reboot it, it shows you the kindel fire logo (organge/white), then to the blue/white logo, and then instead of the normal android ui, it boots into TWRP? If this is the case, have you tried selecting the 'bootmode' option during the kindle fire blue/white logo screen? That was my solution when I had the recovery bootloop problem recently.
rocketfans14 said:
I assuming you have a TWRP bootloop problem? Like everytime you reboot it, it shows you the kindel fire logo (organge/white), then to the blue/white logo, and then instead of the normal android ui, it boots into TWRP? If this is the case, have you tried selecting the 'bootmode' option during the kindle fire blue/white logo screen? That was my solution when I had the recovery bootloop problem recently.
Click to expand...
Click to collapse
I tried telling it to boot normal during that screen. Still goes to TWRP.
Sent from my PantechP8010 using XDA Free mobile app

Unable to Reset - Strange behavior

Hi everyone,
yesterday my beloved galaxy nexus started rebooting continuously. I did not even touched it. The loop is continuing still now without any reason. Usually, in this occasions, I've performed a clean/hard reset (I don't know the correct term), wiping system, data, cache and dalvik partitions, flashing a new rom and bla bla..
The very strage thing today is that I'm not able to do that. I'm using the TWRP custom recovery: if I wipe something or perform a factory reset (standard in twrp) it starts the process, gives me at the end the advice that everything has gone well, it even allows me to flash a new custom rom and gapps but when I reboot, nothing has changed. It reboots in the previous system, nothing erased and again with the reboot loop.
I've just tried also using fastboot interface. Any command I launched performed its task, the phone gives a positive ending but when I reboot again, it's like nothing happened.
Specs: Galaxy Nexus Maguro, GSM version. Actually running a 4.4.4 rom (SlimKat) with its own kernel. A lot of customization (writing/formatting) in the past 2 years.
Thanks in advance for your help!
Did you try CWM recovery?
you can install it using flashify from Google Play...
devil_tear said:
Did you try CWM recovery?
you can install it using flashify from Google Play...
Click to expand...
Click to collapse
My phone reboots in 10 sec after he boots. I can not install flashify and not even flash cwm recovery.
The same here
I'm having the same problem here, it seems that It's not saving any change I try to make, as you've described it says that every task was performed ok but after rebooting it has all my apks, data etc. even afer wiping.
The only thing I can make to keep it ON, is to enter in SAFE MODE, then I can save my pictures and data but I can't flash anything (well I can but it make no change).
FACTS:
-If you start the phone and you activate USB debugging, after rebooting it's not active anymore
-It shutsdown after 10 secons entering in a boot loop (unless you use SAFE MODE, that way you can keep it on)
-If you wipe data, wipe cache, flash boot, flash bootloader, flash system, unlock boot loader, root it, restore, flash stock + unroot (using nexus root toolkit v2.0.5) or use any flash option of fastboot via command line including update, you will get task perfomed ok but nothing is changing; after rebooting It shutsdown after 10 secons entering in a boot loop and all my data including APKs, pictures etc are still in the device.
-You can boot in Download mode, Recovery mode
Phone spec.:
Galaxy Nexus GSM/HSPA+
Android 4.3.0 JWR66Y
Product name: Tuna
Variant: Maguro 16GB
Bootloader Version: PRIMEMD04
Base Band Version: I9250XXLJ1
Lock State - Locked (You can easily unlock it but after reboot it'll be locked again)

Categories

Resources