Problem flashing ROM ***SOLVED*** - Kindle Fire General

I've got lots of experience flashing on my Samsung Fascinate but flashing on my daughter's kindle fire is proving to be difficult for me. I've got TWRP installed, gotten into recovery and tried flashing a couple different roms. I get the same errors everytime: No md5 file for /sdcard/...(which ever rom I'm trying) then finding and opening update, installing update, then E:Cannot load volume /misc. When I try to reboot it just continues to go back into recovery. I'm not sure it's actually installing the rom though. What am I doing wrong?

Toddw said:
I've got lots of experience flashing on my Samsung Fascinate but flashing on my daughter's kindle fire is proving to be difficult for me. I've got TWRP installed, gotten into recovery and tried flashing a couple different roms. I get the same errors everytime: No md5 file for /sdcard/...(which ever rom I'm trying) then finding and opening update, installing update, then E:Cannot load volume /misc. When I try to reboot it just continues to go back into recovery. I'm not sure it's actually installing the rom though. What am I doing wrong?
Click to expand...
Click to collapse
Those errors aren't really errors and are normal, you should be able to press reboot, then system, it will take a few minutes to completely boot up once the logos start doing their thing.

airmaxx23 said:
Those errors aren't really errors and are normal, you should be able to press reboot, then system, it will take a few minutes to completely boot up once the logos start doing their thing.
Click to expand...
Click to collapse
I read that those responses are normal but I wasn't sure. When I hit reboot it turns off then back on to the yellow triangle. I leave it alone and it goes back into recovery without me hitting the power button. Thanks for the speedy response by the way.

Toddw said:
When I hit reboot it turns off then back on to the yellow triangle. I leave it alone and it goes back into recovery without me hitting the power button.
Click to expand...
Click to collapse
You'll have to set bootmode to normal using KFU. It's probably stuck on FastBoot mode.

KFU? Elaborate if you can please. I'm new to Kindle Fire flashing.
Sent from my SCH-I500 using xda premium

KFU stands for Kindle Fire Utility.
I strongly suggest that you read this thread: http://forum.xda-developers.com/showthread.php?t=1552547
It's good and informative.

Oh, KFU, Kindle Fire Utility. Didn't make the correlation. I've got that. I'll read the article. I'll take all the learning I can get. Thanks

Got it. I was making it harder than it was. Thanks for the help.

You are welcome
Please edit the topic and add something like [SOLVED] in the title.

Related

Booting into clockwork recovery

I don't know how I did it, but everyone else is trying to boot into Clockwork Recovery mode successfully...and the whole pull the battery mode doesn't work 100% of the time...buuuut...I CANT STOP!
I can't stop booting into Clockwork. Every time I turn my phone on, it boots into the Clockwork Recovery, without fault. I've rebooted almost 30 times now and every time its done the same thing. Once it reboots into recovery, it will allow me to reboot the phone and then it boots normally. I really want to fix it, its annoying. The phone still works without any issues, its just really annoying that I have to sit there and watch it boot up to get it to the actual phone.
I don't want to unroot and start over with it all because I've made so many small changes to the phone and made it my own.
Sooo, pleeeeeeeeeease anyone with any info or fixes; let me know!
Mine did that too so I flashed the SBF and started over from scratch. I am afraid to try the D2 Bootstrap again for that reason. For now I can live with it. Did you find a fix yet?
How does this work?
When your device boots up, there is a init.rc script in your boot image that runs various components found in /system. The Droid X recovery bootstrap mimics the "logwrapper" binary. The hijacker then looks for "/data/.recovery_mode", and if it finds it, it unmounts /system to prevent android from starting. It then starts up recovery instead.
That's from Koush's site. Have you tried to delete the .recover_mode file if it clears it up? If you do try may you please post back?
Worked for me! Thanks for that!
Apparently it only happens randomly to some people. My roommate has a Droid2 and his never did it....weird.
kwheel596 said:
Worked for me! Thanks for that!
Apparently it only happens randomly to some people. My roommate has a Droid2 and his never did it....weird.
Click to expand...
Click to collapse
Glad it worked. It happened to me too and I just used the sbf file to restore everything. Did you use any mount adb commands before you had that problem?
To be honest I have no idea, I've had android phones for a while so I was just flying through the commands and don't remember what was typed
Unable to remove "ClockworkMod Recovery"
[/QUOTE]That's from Koush's site. Have you tried to delete the .recover_mode file if it clears it up? If you do try may you please post back?[/QUOTE]
So, I looked throughout my sd card, and have been unable to find any ".recover_mode" file.. I still get the ClockworkMod Recover screen EVERY time I reboot my device.. I have rooted and unrooted multiple times to try and figure out this problem, as well as searched through this website for answers.. I am not finding any.. HELP!?
Ultimately, I would like to just restore my phone to factory so I can pass it on to a friend..
Thanks in advance for everyone's help!
Chenoaem
Im not able to get into recovery at all... even after flashing recovery using rom manager... and the koush flash doesn't work either. When I try to boot into recovery, it just shows the yellow triangle and the ! and the android icon.....what can i do to get around this? The device is rooted using z4root..... thx!
enkrypt3d said:
Im not able to get into recovery at all... even after flashing recovery using rom manager... and the koush flash doesn't work either. When I try to boot into recovery, it just shows the yellow triangle and the ! and the android icon.....what can i do to get around this? The device is rooted using z4root..... thx!
Click to expand...
Click to collapse
nevermind... forgot to hit the search key! doh!

Help! Droid 2 stuck in boot loop.(solved.)

Ok, so I was playing around with the new Root Tools app and made a few, what I thought were safe, tweeks to the system and rebooted the phone. It gets past the M screen, runs the boot animation and then starts the boot animation again. No way out except to pull the battery.
How can I get it out of this endless bootloop? If I have to factory reset and start again from scratch, so be it. I would just like to know how.
I've tried holding down different button combinations on boot but haven't come up with the right sequence I guess.
I've also tried pulling the battery as the animation starts, then putting it back in and rebooting which is supposed to call up the recovery mode, but it doesn't. I'm not sure what to try next? I wish these things had a reset button
It's a Droid 2 Rooted with the stock rom running Froyo 2.2. I have the Bootstrap recovery loaded and did a backup with the clockwork recovery. I also have, and use, Titanium Backup Pro for Root.
After bootlooping pull the battery and put it back in. Then plug the droid 2 in with the cable either wall or USB will work. Then turn it on and it should get you recovery. The phone has to be completely off when you plug it in though.
Sent from my DROID2 using XDA App
EDIT: I tested it and USB won't work (at least for me) better off just using the wall plug.
Thanks, but that not working either. When I plug in the cable after the battery pull it starts up automatically and goes to the battery charge screen. I then shut it off and start it back up with no battery but plugged in and it goes right back into the boot loop after the M screen.
The batter charge screen is what you want. Just press the power button after you get the charge screen and you'll be booted into clockwork.
But in order to factory reset from a bootloop you have to flash an .sbf theres a few different tutorials. One in Windows, Another in linux/mac, and another in linux but for windows machines through an Ubuntu livecd(that I made).
Oh, OK I thought it was going to go right into recovery mode. Good to know.
I finally figured out how to get into the stock recovery and bootloader, so I tried to run the stock restore but after it wiped the data, it couldn't find the recovery file! So then I read in another post about using RSDlight 4.9 to do an sdf restore so I used that method. Of course while it was flashing I did come across your Ubuntu method and that does look like it would be a simpler process. I'm going make one of those CD's to have for next time.
Anyway, I was able to get it back to stock. It looks like most of my stuff is still on the SD card, so that's a bonus! I'll have to re-root before I can restore everything via Titanium, but that's going to be tomorrow's project. As for now just happy to to have my phone back. Especially before the wife (who has been telling me for weeks to stop F'in with it) found out .
I really appreciate that you took the time to help, thanks again!
No problem.
Could you change your Thread title to include [SOLVED]. Thanks
Can you please explain to me how you fixed this problem? I am currently having this problem now.
Please do not open/post in multiple threads for the same issue. This is a waste of time as we can see you have an open thread. Please reply to my response in your original thread for further assistance. (http://forum.xda-developers.com/showthread.php?t=824254)
newk8600 said:
Could you change your Thread title to include [SOLVED]. Thanks
Click to expand...
Click to collapse
Ok, your wish is my command! ;-)
Sent from my DROID2 using XDA App
Can I close this?
Yes. This issue has been resolved.
theecho said:
Yes. This issue has been resolved.
Click to expand...
Click to collapse
Ok, thanks

[SOLVED] Bricked?

SOLVED I have done something very very stupid. I tried flashing a galaxy nexus kernel to my kindle fire. I've been flashing roms/kernals all day to my G-nex and for some reason i was thinking i was on my gnex and i just flashed it in rom manager on my kindle fire (DUMB). Now my KF will only boot into TWRP. I have adb working on my computer if someone could just help me figure this whole shinanigans out.
I was on cm7 when i flashed it. then i tried flashing cm9. it looks like it flashed it right but it wont boot up. it just goes straight to twrp.
bb-gun said:
I was on cm7 when i flashed it. then i tried flashing cm9. it looks like it flashed it right but it wont boot up. it just goes straight to twrp.
Click to expand...
Click to collapse
Did you select reboot into recovery at any point? From reading other threads, it seems like people get stuck in TWRP due to bootmode settings after choosing that option.
*EDIT* I'm guessing if you used ROM Manager the app defaulted to booting into recovery in order to install the kernel.
ghost_og said:
Did you select reboot into recovery at any point? From reading other threads, it seems like people get stuck in TWRP due to bootmode settings after choosing that option.
*EDIT* I'm guessing if you used ROM Manager the app defaulted to booting into recovery in order to install the kernel.
Click to expand...
Click to collapse
Yeah. I even knew i wasn't supposed to do that. I was half awake when i did it. Is there any way to recover it?
bb-gun said:
Yeah. I even knew i wasn't supposed to do that. I was half awake when i did it. Is there any way to recover it?
Click to expand...
Click to collapse
Pretty sure. Search the dev forum for how to switch boot modes. I think the Kindle Fire Utility thread would be a good place to start.
if you allready have twrp it should be no problem:
http://forum.xda-developers.com/showthread.php?p=20714780#post20714780
do from the status where you are - means you don't need the twrp installation
Thank you soooooooo much. It worked. It took forever to boot up but it finally did.
glad to help ...
Should change the subject of the topic (edit first post) to [Solved]
They really need to take that reboot to recovery option out lol.
bb-gun said:
Thank you soooooooo much. It worked. It took forever to boot up but it finally did.
Click to expand...
Click to collapse
How much is forever? Mine is 10+ minutes.

TWRP/FireFireFire gone?

Well, I used KFU months ago to root, install TWRP, and install GAPPS to my fire. Worked great. Got the yellow triangle on bootup and could hit the power button to enter recovery. I have not rebooted my kindle in forever, its always on. Well I finally decided I would make a backup of the stock rom and try flashing CM7. I shut down the kindle and then turned it back on, and my yellow triangle screen is nowhere to be found? It just boots up like normal. Where did my FireFireFire go? Was there an update that broke it? I don't have a clue how to go about this now, I have no idea if the TWRP is still installed and theres just no way to get to it, or if I should just try reinstalling the recovery using KFU. Has anyone else had this problem?
insanespain said:
Well, I used KFU months ago to root, install TWRP, and install GAPPS to my fire. Worked great. Got the yellow triangle on bootup and could hit the power button to enter recovery. I have not rebooted my kindle in forever, its always on. Well I finally decided I would make a backup of the stock rom and try flashing CM7. I shut down the kindle and then turned it back on, and my yellow triangle screen is nowhere to be found? It just boots up like normal. Where did my FireFireFire go? Was there an update that broke it? I don't have a clue how to go about this now, I have no idea if the TWRP is still installed and theres just no way to get to it, or if I should just try reinstalling the recovery using KFU. Has anyone else had this problem?
Click to expand...
Click to collapse
When you get an Amazon OTA update of the Kindle Fire software, it will overwrite both the bootloader and recovery with the stock versions. I'm guessing that's what happened to your device. You'll have to repeat the process with KFU to get them installed again.
Thanks for the reply. I guess I will just use KFU and try to reinstall the recovery. I just haven't been keeping up on the kindle forum and wanted to make sure that I wasn't missing something.
Sent from my XT862 using Tapatalk

Constantly rebooting...

Hello, this is my first post here and I have searched for a similar post or issue but have been unsuccessful finding anything.
Please forgive me if I have posted in the wrong area, missed a solution somewhere and/or have not explained anything correctly/clearly.
My Nexus 7 (2012) (I installed Cyanogen on it (and updated it once) through their installer and it has run perfectly for months) started rebooting randomly one morning. I turn it on and it seems to be normal, then it will suddenly reboot. The time between reboots varies ranging from 30 seconds to a few minutes. I can not install or update any apps and any settings changed are reset back to what they were previously upon reboot. I have tried a factory reset and while it appears to wipe everything (all caches and data) when I reboot it is the same as before the reset (I also receive this message (after all other processes are complete) during the data wipe "E: unknown volume "/sdcard/.android_secure" "). I am able to turn on developer options but then the random reboot occurs and it is turned off. I have plugged it to my computer and see it listed, but can not access anything on it.
My intention is to wipe it using my computer (fastboot?) but I am at a standstill due to the rebooting and being unable to turn on developer options.
Any ideas or suggestions would be greatly appreciated.
Have you tried flashing another ROM in recovery? Perhaps try to see if you can access the filesystem while in recovery or if the bootloader brings anything up on your computer.
kcipopnevets said:
Have you tried flashing another ROM in recovery? Perhaps try to see if you can access the filesystem while in recovery or if the bootloader brings anything up on your computer.
Click to expand...
Click to collapse
Thanks for the reply. Sorry for my delay in replying. I've been rather frustrated with this.
I flashed the official image (downloaded from the google site) using fastboot and it seemed to work as all messages said complete but when I rebooted, it was back to it's current state. I am at a loss. I also tried adb sideloading but that just hangs when it gets to installing. It does not reboot randomly when it is in recovery.
pdn190 said:
Thanks for the reply. Sorry for my delay in replying. I've been rather frustrated with this.
I flashed the official image (downloaded from the google site) using fastboot and it seemed to work as all messages said complete but when I rebooted, it was back to it's current state. I am at a loss. I also tried adb sideloading but that just hangs when it gets to installing. It does not reboot randomly when it is in recovery.
Click to expand...
Click to collapse
No worries!
So CyanogenMod is still installed? Oh my. Has anything at all changed? If you still have custom recovery installed, why not try a near stock ROM?
kcipopnevets said:
No worries!
So CyanogenMod is still installed? Oh my. Has anything at all changed? If you still have custom recovery installed, why not try a near stock ROM?
Click to expand...
Click to collapse
Yes. No matter what I do, when I reboot it's still Cyanogen. Being a semi-novice at this, I didn't backup the stock ROM I had before installing Cyanogen. It feels like a virus, but I pretty much installed the exact same apps on both my phone and tablet and the phone has been fine.
I used this image(nakasi kot49h). Should I try a earlier version?
Thank you.
pdn190 said:
Yes. No matter what I do, when I reboot it's still Cyanogen. Being a semi-novice at this, I didn't backup the stock ROM I had before installing Cyanogen. It feels like a virus, but I pretty much installed the exact same apps on both my phone and tablet and the phone has been fine.
I used this image(nakasi kot49h). Should I try a earlier version?
Thank you.
Click to expand...
Click to collapse
You can always try. Also make sure you check md5 before flashing, that may explain why stock didn't flash correctly.
And I still can't get anything to work. Most recently I tried using wugfresh and EVERYTHING works except when it writes bootloader.img at the start. I feel like I am close but then it reboots back to cyanogen. lol

Categories

Resources