I failed so hard im not even going to say what i was doing wrong, i want to punch my self in the face lol. Disregard this thread
I was going o install a different rom and in the application settings it said apps were still using up a bunch of space so i flashed the stock rom again, then went into the settings and hit factory reset.
Now when i Boot it up it goes to TWRP menu. I try going into the MOUNT option to put a flashable rom on their but my device doesnt show up on my computer? So KF utility doesnt find it either...
help?
ok, for some reason it wont even show up in device manager as anything. I tried reinstalling the drivers with kindle fure utility but it does nothing..
I am now stuck at the same place as you...
You should use the kindle fire utility to change your bootmode
from Recovery to Normal
Ok, this is how I just fixed mine. Using the KFU, having the KF plugged in to your pc. Now open the KFU and go to the boot mode, hit one to put it in normal boot and it will say waiting on the device, restart the kindle and it will say that it sent the command in a very short window. After that it will still load into twrp, just reboot the system and it should load into the Kindle Fire after twrp has run it normal boot up.
Related
Hi, I have a big problem.
I installed CM7 with TWRP and I rebooted my KF. CM7 was ok.
My second step was to install gapp, so in CM7 I rebooted the KF in recovery mode, but now I have a vicious circle.
In TWRP I press reboot in system mode or in "power off" mode, but in each cases the KF continue to entry in TWRP without I press the power button.
It's impossible to launch android system.
If I use the KF utility, this recognize KF, but if I launch some option, it's stopped to wait for device.
Please help me.
Thank you
(sorry for my english )
a small video.....
on youtube: /watch?v=hUnGTR2DQDY
you need to update divers. I installed the divers with kindle utility and they didn't work. Try searching the threads
Edit.. don't worry I've been here so many times with different things. It seems to be very hard to brick a kindle. Its stuck in boot loop and this has been covered so many times. Hope this helps. If you can't find the right thread let me know and I'll have a look for you.
Sent from my Galaxy Nexus using xda premium
airjump said:
Hi, I have a big problem.
I installed CM7 with TWRP and I rebooted my KF. CM7 was ok.
My second step was to install gapp, so in CM7 I rebooted the KF in recovery mode, but now I have a vicious circle.
In TWRP I press reboot in system mode or in "power off" mode, but in each cases the KF continue to entry in TWRP without I press the power button.
It's impossible to launch android system.
If I use the KF utility, this recognize KF, but if I launch some option, it's stopped to wait for device.
Please help me.
Thank you
(sorry for my english )
Click to expand...
Click to collapse
If you are running windows this is the easiest way to go about fixing any booting problems that you may be having
http://forum.xda-developers.com/showthread.php?t=1428428
If you are not using windows look in my guide and the fix is also in there to do it manually from a command prompt:
My guide http://forum.xda-developers.com/showthread.php?t=1417234
Remember to hit that thanks button if this helped you
Every time I install a new zip, I have to reset the IDME boot to 4000 before I can use the device again in Android. What can I do to prevent this?
I've heard that one way to prevent this (not sure if this is your problem or not) is to only boot to TWRP from firefirefire. IE, if you are running CM7, don't select reboot to recovery, or something like that.
The reason being, there is a bug in TWRP which causes it to not reset the bootmode when you select reboot.
I have always done it this way (saw someone mention it in a post) and have never had the problems of TWRP endless reboots that I keep seeing...
podspi said:
I've heard that one way to prevent this (not sure if this is your problem or not) is to only boot to TWRP from firefirefire. IE, if you are running CM7, don't select reboot to recovery, or something like that.
The reason being, there is a bug in TWRP which causes it to not reset the bootmode when you select reboot.
I have always done it this way (saw someone mention it in a post) and have never had the problems of TWRP endless reboots that I keep seeing...
Click to expand...
Click to collapse
For my one information, what is "firefirefire"? Is that pushing the on button several times to get the TWRP to come up?
ontwowheels said:
For my one information, what is "firefirefire"? Is that pushing the on button several times to get the TWRP to come up?
Click to expand...
Click to collapse
Yes, firefirefire is the yellow triangle.
To clarify the answer to to OP. Always turn POWER OFF before installing a new rom. Don't reboot into TWRP and you won't get stuck in the boot loop.
furtom said:
Yes, firefirefire is the yellow triangle.
To clarify the answer to to OP. Always turn POWER OFF before installing a new rom. Don't reboot into TWRP and you won't get stuck in the boot loop.
Click to expand...
Click to collapse
Thanks....I currently have this and TWRP installed via the KFUtility.
Can also verify I have avoided this by always powering down and not rebooting into recovery. At least with the 4 zips I have flashed.
install clockworkmod touch recovery
twrp never fixed the reboot option.
Sent from my HTC Glacier using xda premium
Fix TWRP boot loop
Turn off Kindle. Plug Kindle into computer. Load fire utility. Choose option 5 for TWRP install, but don't hit enter yet. Turn on Kindle. Once yellow triangle appears, hit enter on keyboard to install TWRP, let it power cycle one or two times. This fixes boot loop.
citizenandroid said:
Turn off Kindle. Plug Kindle into computer. Load fire utility. Choose option 5 for TWRP install, but don't hit enter yet. Turn on Kindle. Once yellow triangle appears, hit enter on keyboard to install TWRP, let it power cycle one or two times. This fixes boot loop.
Click to expand...
Click to collapse
Thank you for this! I've been looking through the forums trying to find something that would work. ADB won't launch for me, something I need to look into, but this worked. Thank! :]
installed MIUI on my KF using TWRP a few days back. went well, played around with it, then decided to go back to stock.
Wiped caches and flashed update.zip (stock rom for KF) and all appeared to have gone well..... BUT..... the battery was/is apparently too low for the device to charge (but wait, it gets better)...
when the device fires up I get the white/orange kf logo animation, then when boots I see the homescreen (without the notification/toolbar at top (just bookshelves,standard icons and bottom row of icons).... as soon as that appears I get forceclose messages for
-android.process.acore
-process.android.providers.calendar
(happens right after the UI starts loading ... if Im quick enough I can get one of the homescreen apps to load, but the device (after just a couple of seconds) just goes back to the white/orange logo animation and starts the boot process all over... whether I click force close or not it just restarts the nasty process).
in the brief time Im able to have it on I cant get the kindle fire utility to recognize it so I can get TWRP back on the device to try to re-flash stock.
probably just a paper weight now Im guessing, so I'll either take over my wifes KF or get a new one, but thought I'd mention my experience here to see if anyone has seen/heard of this before and as a warning to other noobs who know just enough to be dangerous like me!
Thanks all.
Have you tried charging it? Just plug it in with the stock charger and let it sit overnight. Then try the re-flash.
Let it charge, then just flash a new rom.
left plugged in with AC charger all night... the force closes just happen over and over and because it doesnt fully boot (Im guessing) I cant get to point where I can use kf utility to get twrp back on to handle boot. i think trying to flash with such a low battery made the flash go horribly wrong and thats the cause of the force closes??? I wish it had hardware buttons like my galaxy s!
Your device is not bricked alright?
Now that the device is fully charged, just go to KFU, on the option 1 (bootmode), choose recovery (5001).
Then turn off the device completely holding the power button for 15 secs or more.
Then plug it to USB and let the KFU set your device to recovery.
Then it will restart and go directly to TWRP
The fact that it boots at all goes to show you didn't brick it.
A few months ago I couldn't get passed the splash screen.
vbdss said:
Your device is not bricked alright?
Now that the device is fully charged, just go to KFU, on the option 1 (bootmode), choose recovery (5001).
Then turn off the device completely holding the power button for 15 secs or more.
Then plug it to USB and let the KFU set your device to recovery.
Then it will restart and go directly to TWRP
Click to expand...
Click to collapse
Thanks... KFU doesnt recognize the device at all during the 'boot loop-like' process it runs through before the 2 force closes and the eventual automatic reboot..... I followed your steps and it just kept showing waiting for device and the KF goes through the boot > force close > restart process.... its like ground hog day.
Thanks though, I appreciate the response/help.
shobon said:
The fact that it boots at all goes to show you didn't brick it.
A few months ago I couldn't get passed the splash screen.
Click to expand...
Click to collapse
Yeah, I see your point... but the force closes and the fact that it never shows the menus / top notification bar and icons, etc. and that seemingly, the KF os never loads fully keeps me from getting to a point where the windows drivers recognize the device and then allows me to get KFU to work with the device.
sort of stuck but not technically a brick I guess.
There is no such thing like KF never loads fully.
Or it loads or not. FCs is something that happened on the install of the rom
You have TWRP and cant fastboot?
Try to redo the steps to install TWRP and install FFF 1.4a by hashcode
He doesn't have FFF or TWRP anymore, as he flashed Amazon's stock update.zip
Your only solutions are either the USB trick (cracking open the KF's case and shorting specific pins) or getting a factory cable (recommended) to force the KF into fastboot mode, from which you can flash FFF and TWRP, then boot into TWRP and fix the mess.
Sorry, after i went from stock to custom roms, i never tried to go back to stock, didnt know that we lost fff and twrp when doing it.
Thanks, Dasanko, I'll do a search for the cable and see where to buy it and will go that route. Thanks again all.
FastBoot
Something similar happened to me and I did this:
Even though your Kindle Fire isn't recognized by KFU you can run it and select the option #5 (Install Latest FireFireFire).
When you do it'll probably error out attempting to get your device into fastboot but you'll get the prompt "( waiting for device )". Once that happens let your fire loop again and this time the window will be big enough for FireFireFire to be flashed into your device and leave the device in FastBoot...
After FireFireFire gets installed run KFU again to install TWRP and you'll be able to boot into recovery by poking the power button repeatedly in the new boot logo.
Hope that helps! (That's how I un-looped mine)
vbdss said:
Sorry, after i went from stock to custom roms, i never tried to go back to stock, didnt know that we lost fff and twrp when doing it.
Click to expand...
Click to collapse
Np, it's just it doesn't flash just over the system, but also overwrites the recovery and bootloader with their crappy stock ones.
darkjz said:
Something similar happened to me and I did this:
Even though your Kindle Fire isn't recognized by KFU you can run it and select the option #5 (Install Latest FireFireFire).
When you do it'll probably error out attempting to get your device into fastboot but you'll get the prompt "( waiting for device )". Once that happens let your fire loop again and this time the window will be big enough for FireFireFire to be flashed into your device and leave the device in FastBoot...
After FireFireFire gets installed run KFU again to install TWRP and you'll be able to boot into recovery by poking the power button repeatedly in the new boot logo.
Hope that helps! (That's how I un-looped mine)
Click to expand...
Click to collapse
I like this approach and think it MIGHT yield some results (but what do I know- I caused this afterall!).... Im going to let it stay in its little reboot / force close loop and have KFU sitting at FFF (waiting for device).... then if it looks like this works (how will I know exactly? the boot process will change how exactly (what should I look for, basically)) then I will do same with KFU and TWRP installation option do its thing. Thanks.
Something similar happened to me too. I was reverting my CM9 modded Kindle to a stock one. After flashing the 6.3.1 update, I was getting weird FCs whenever I would boot into the stock OS. I finally managed to get to the Factory reset option in the menu and that fixed the issue for me.
Sent from my Amazon Kindle Fire using xda app-developers app
freefaling said:
Something similar happened to me too. I was reverting my CM9 modded Kindle to a stock one. After flashing the 6.3.1 update, I was getting weird FCs whenever I would boot into the stock OS. I finally managed to get to the Factory reset option in the menu and that fixed the issue for me.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Encouraging!.... what exactly did you do to get it to work for you - if you recall... i've just had it spinning through the loop with KFU sitting at waiting for device -- no results though... so seems pointless for me so far.
Little bit of info as to why/what is causing the issues discussed here:
The stock bin backs up data during the restore process and than restores it back along with the ROM (those of you familiar will already see the issue here but I'll continue); problem of course being there that if you restore data from a ROM like CM9 to the gingerbread based/neutered stock OS (or even to CM7 for that matter), it is going to cause all sorts of headaches with force closes and stuff just plain not working.
In short, for those considering trying to return to stock please remember to wipe data before attempting to flash the bin (at least until someone decides there's enough of a demand to make a cleaner return to stock method).
As for the OP, do what was suggested with the factory cable and you should be set; good luck.
Edit: the above posts regarding factory reset might work to as that will delete data but you would have to be able to get to that part of the settings menu, which depending on what's force closing may or may not be possible.
Your exactly right Sblood86 many are slipping on this bannana peel here lately trying to revert back to stock some with even more dire consequences not just a literal shock to it completely changing systems but also how data is rehandled. Could be a better option for some to do full wipes and flash something near stock like modaco to prevent this mishap.
This entire thread is ridiculous.
Hello!
Looks like my Fire HD 10 tablet got kinda bricked...
I can't get into the Recovery Mode to do factory reset.
This is after I've installed TWRP.
The tablet powers on and you can see the Amazon logo, when it disappears instead of going into Recovery it restarts and the Amazon logo pops up again, then goes into Fire logo and stays there forever.
This started happening when I was trying to follow one of the guides where you have to input commands through Linux Terminal.
I run the "sudo ./step-1.sh" command and since then the tablet is not loading all the way up anymore.
Is there a way I could get it to work with some ADB magic or something?
Huge thanks for any help!
Have a great rest of the day!
Is step-1.sh all you did or did you run the other scripts as well?
What was the output of the script?
If you try to enter recovery using the right volume-button and power it doesn't enter recovery?
Hey k4y0z!
My tablet was still operating when I input the command ./step-1.sh, then it turned off and on again to run the script as I've expected it to do.
But this is the point where it never went beyond the Fire logo again.
It did the same thing as when I try to enter Recovery Mode (yes, using the volume and power buttons), that is, showing the Amazon logo then it turns itself off and on to show the Amazon logo again and going to infinite Fire logo.
It looks like it tries to enter Recovery but can't and resets to try and load up normally.
I think the script was trying to enter Recovery too to do its thing but as this mode can't be entered it reset but this time being unable to even load up the system.
I could access Recovery before but not since I've installed TWRP and now the tablet can't access it too.
I recon the only way to fix this is if there's a way to somehow force Factory Reset with some software or a brute ADB command.
Though whenever I try to send a command this way it says <waiting for device> so it probably can't be done without loading up the system first.
I tried to run other scripts but nothing happened, the tablet was not responding to them.
The output of step-1.sh had no errors though I can't remember what it said exactly.
crowbringer said:
Hey k4y0z!
My tablet was still operating when I input the command ./step-1.sh, then it turned off and on again to run the script as I've expected it to do.
But this is the point where it never went beyond the Fire logo again.
It did the same thing as when I try to enter Recovery Mode (yes, using the volume and power buttons), that is, showing the Amazon logo then it turns itself off and on to show the Amazon logo again and going to infinite Fire logo.
It looks like it tries to enter Recovery but can't and resets to try and load up normally.
I think the script was trying to enter Recovery too to do its thing but as this mode can't be entered it reset but this time being unable to even load up the system.
I could access Recovery before but not since I've installed TWRP and now the tablet can't access it too.
I recon the only way to fix this is if there's a way to somehow force Factory Reset with some software or a brute ADB command.
Though whenever I try to send a command this way it says <waiting for device> so it probably can't be done without loading up the system first.
Click to expand...
Click to collapse
step-1.sh doesn't flash TWRP, this only happens in step-2.sh.
In step-1 it resizes userdata and adds two new partitions, recovery stays untouched.
Are you sure recovery worked before step-1? It sounds like it was already broken.
The problem now is, that the userdata is invalid, since it has been resized, that should normally be fixed by doing a factory-reset via recovery, but since your recovery is inaccessible this fails.
You will have to open the device and do the unbrick-procedure: https://forum.xda-developers.com/showpost.php?p=79169423&postcount=2
Hey all, I recently flashed a new rom on my phone, which required me to factory reset my ticwatch I'm order to reconnect.
Upon doing to the first time, everything seems to have gone well, but had trouble connecting to the device. So I ran another factory reset. Since that one, I've been stuck in a boot loop.
I see the "device software can't be checked for corruption" screen for about 20 seconds, and then it vibrates, screen turns off, then I see the same screen again. And so on.
I tried letting the battery go to nothing and trying again, seems to be the same issue. I'm letting it charge and bootloop for now in case maybe I just don't have enough juice to make it through boot.
It is rooted, with custom ROM (followed a guide on this forum somewhere about half a year ago, was running great) and TWRP installed (at least it was, I've been unable to get to the recovery screen since the boot loop started). Cannot see it in adb ever in this process.
Anyone have any other suggestions? I remember the Samsung notes had a special USB tool that would bridge a couple pins to immediately go to recovery, is there a similar option here?
Can you get in usb mode,or fastboot or recovery maybe?There is solution..dont worry.I ghuess adb dont work,but you cant go to fastboot mode and boot twrp image and get in twrp recovery..in twrp recovery you need backup file..If you cant do that,we are going to another solution..
Yeah, I can't - via any combination of button holding - get into any booted mode. No recovery, no fastboot, nothing. If anything, some buttons seem to make it circle boot faster .
nieminen432 said:
Yeah, I can't - via any combination of button holding - get into any booted mode. No recovery, no fastboot, nothing. If anything, some buttons seem to make it circle boot faster .
Click to expand...
Click to collapse
,Yeah tough situation,and when you connect it to pc in that "broken mode" -boot loop and open adb shell on pc ,comand adb devices or fastboot devices,does it show device?When you screwed boot and you have twrp there must be option to get in twrp.One trick more go to manage devices in pc find your device if unknown you right klick on it,update drivers,manually,and then choose android,then android adb install device.
KristijanKG3 said:
,Yeah tough situation,and when you connect it to pc in that "broken mode" -boot loop and open adb shell on pc ,comand adb devices or fastboot devices,does it show device?When you screwed boot and you have twrp there must be option to get in twrp.One trick more go to manage devices in pc find your device if unknown you right klick on it,update drivers,manually,and then choose android,then android adb install device.
Click to expand...
Click to collapse
I tried adb devices, but not fastboot devices, thanks for the idea, I'll give it a go.
nieminen432 said:
I tried adb devices, but not fastboot devices, thanks for the idea, I'll give it a go.
Click to expand...
Click to collapse
Maybe it wont work,but if doesnt,we figure out something..Bootlop is not the end of your device..
No go on either command. Nothing shows up.
I'm half wondering if it's my battery at this point. I think I'm getting a new watch for Christmas anyway, so not a huge loss. But happy to keep trying if anyone else has any ideas.