Solution: In my research, I found people were having problems with TWRP format and were told to enable the option "Use rm -rf" instead of format. This was preventing /data from being formatted properly and it was not mounting properly during boot so I kept getting stuck at the boot animation on any rom. Now I'm successfully using TWRP v2.3.3.1 with default options.
Original Post:
Yesterday I rooted my KF with stock 6.3.1 using KFU 0.9.6. It seemed to go well and I now have FFF v1.4a and TWRP v2.2.2.1.
I have used TWRP to install a handful of roms and every one of them gets stuck at the boot logo. I have enabled the option in TWRP to "use rm -rf". Each time I have installed a rom I have done the following
Wipe>Factory Reset
Wipe>System
Install Rom.zip
Install GApps
Wipe Cache/Dalvik Cache
I have tried the following roms (plus a couple others):
[ROM] [JB 4.2.1] CM10.1/SGT7 for the Kindle Fire
[ROM-AOSP] [NEW] Stock Jelly Bean 4.2.1_r1 for the Kindle Fire [12-18 DEEP SLEEP FIX]
[ROM/KERNEL] UNOFFICIAL CM10.1 + 3.x Kernel for Kindle Fire [12/16 SLEEP-FIX]
[ROM][AOSP][10/10/2012] Jelly Bean Tablet Edition aka Project Jandycane
Attached are some logcat logs. cm-10.1-20121216-UNOFFICIAL-otter printed nothing to logcat. Jandycane didn't install since if failed the checksum check.
At the blue Kindle Fire logo, hold the power button to pull up the boot options and select "reset boot mode".
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
At the blue Kindle Fire logo, hold the power button to pull up the boot options and select "reset boot mode".
Click to expand...
Click to collapse
Sorry if I said it wrong. I'm stuck at the boot animation. I'll try this when I get home.
Make sure you have no checks in the boxes of system and data under twrps mount option if so uncheck them then select reboot system. As well might I suggest a better wipe order: factory reset, cache, dalvik, system, flash ROM zip, flash proper OS specific gapps zip then select reboot system.
selyb said:
Sorry if I said it wrong. I'm stuck at the boot animation. I'll try this when I get home.
Click to expand...
Click to collapse
Well, that's a different story.
Two things usually cause this...not wiping the necessary partitions or using the wrong recovery (CWM, TWRP 2.3)
I would double check to make sure the examples listed above are not an issue. Otherwise, pull your recovery.log while booted into recovery to see what's going on.
Code:
adb pull /tmp/recovery.log
"That's a special kind of stupid. The kind that makes me laugh."
Thepooch said:
Make sure you have no checks in the boxes of system and data under twrps mount option if so uncheck them then select reboot system. As well might I suggest a better wipe order: factory reset, cache, dalvik, system, flash ROM zip, flash proper OS specific gapps zip then select reboot system.
Click to expand...
Click to collapse
Those boxes were not checked. I actually thought of this before, but I just double checked. Wipe order didn't seem to make any difference.
soupmagnet said:
Well, that's a different story.
Two things usually cause this...not wiping the necessary partitions or using the wrong recovery (CWM, TWRP 2.3)
I would double check to make sure the examples listed above are not an issue. Otherwise, pull your recovery.log while booted into recovery to see what's going on.
Click to expand...
Click to collapse
Edit: Recovery.log attached.
Edit2: Also, I forgot to mention that before I flashed anything, I backed up the stock /system. I have successfully restored this and booted back to the stock UI. It is only custom roms that get stuck.
selyb said:
Those boxes were not checked. I actually thought of this before, but I just double checked. Wipe order didn't seem to make any difference.
Edit: Recovery.log attached.
Click to expand...
Click to collapse
Get on recovery, download the latest twrp, flash it, reboot to recovery, delete system, cache, dalvik, and Factory reset. Then install the ROM ad you are good to go.
Sent from my Nexus 7 using XDA Premium HD app
firered365 said:
Get on recovery, download the latest twrp, flash it, reboot to recovery, delete system, cache, dalvik, and Factory reset. Then install the ROM ad you are good to go.
Click to expand...
Click to collapse
I'm getting the same result. I looked at my logcat and it looks like /data isn't being mounted during boot.
Yeah you will need to use soupkit to fix your data mounting issue. First try resetting twrp defaults use format instead of rm -rf .
Thepooch said:
Yeah you will need to use soupkit to fix your data mounting issue. First try resetting twrp defaults use format instead of rm -rf .
Click to expand...
Click to collapse
That did it
I just had to uncheck the "use rm -rf" option, do factory reset, wipe system, then install the rom. Thx much guys
Related
I now cannot get into an operating system. The device loads FFF 1.4a says "booting" goes blank for a little while then comes back to the 1.4a screen and says "booting" again and loads up TWRP. This is how I got to this point:
I recently decided to go from an older CM7 rom to a new jb one.
Because I had an older version of FFF and had a CWM recovery, I downloaded the new version of FFF (1.4a) and the newest version of TWRP (2.2.0) (flashable zip file) as well as the new jellybean rom and jb gapps. I checked all md5s prior to doing anything.
I booted into recovery and created a backup in CWM. I then cleared cache and Davlic cache and installed FFF 1.4a. I then rebooted to CM7. After loading CM7, I rebooted into recovery, cleared cache and davlic cache and installed TWRP 2.2.0. I then rebooted into CM7, rebooted into recovery. I then cleared cache, davlic cache, factory reset, and wiped system. I then installed CM10 and jb gapps and attempted to reboot to system, but have not ever been able to get there.
I have tried installing the CM7 rom I had before, no difference, CM9 rom, no difference. I tried to use a recovery file I had, still no good.
Adb does not seem to behaving properly as well. I can't seem to be able to get the device into fastboot mode for one. In TWRP I can see the device as the following:
4B8E000600000001 recovery
when I try to change the bootmode, this is how it behaves:
adb shell
~ # <-[6n idme bootmode 4002
/sbin/sh: idme: not found
KFU also seems to not be much help at changing the bootmode. I have tried older version as sited elsewhere (0.9, 0.3), but these fair no better.
Also, In my haste and desire to get this working I thought,"maybe there is some conflict with the sd card", so I wiped that only to realize while wiping that I never backed up my recovery files, "doh!".
Also, I have full battery.
I am a noob, so I could have done anything wrong. Any help would be appreciated.
When you get to the bootloader screen select boot normal in the boot menu by quickly depressing your power button a few times if it does not boot normal then flash the bootloader again in recovery http://forum.xda-developers.com/showthread.php?t=1632375 also you will have to mount your sdcard in twrp to do so make sure there are no checks in the boxes of system and data then mount transfer 1.4a bootloader a new ROM and gapps then unmount flash bootloader reboot it get back to twrp wipe factory reset wipe cache wipe dalvik wipe system flash ROM flash gapps select reboot if prompted select system see where your at after that
http://forum.xda-developers.com/showpost.php?p=29186989&postcount=157
Thanks
Thepooch said:
When you get to the bootloader screen select boot normal in the boot menu by quickly depressing your power button a few times if it does not boot normal then flash the bootloader again in recovery http://forum.xda-developers.com/showthread.php?t=1632375 also you will have to mount your sdcard in twrp to do so make sure there are no checks in the boxes of system and data then mount transfer 1.4a bootloader a new ROM and gapps then unmount flash bootloader reboot it get back to twrp wipe factory reset wipe cache wipe dalvik wipe system flash ROM flash gapps select reboot if prompted select system see where your at after that
Click to expand...
Click to collapse
Thanks, I will try this when I get a chance.
Thanks
kinfauns said:
http://forum.xda-developers.com/showpost.php?p=29186989&postcount=157
Click to expand...
Click to collapse
Thanks for this as well, did not see this information anywhere else.
fixed
Yep, it was a bad FFF flash. All good now. Thanks for the help.
I really, REALLY have tried going through the threads and tried to figure this out on my own but I'm just stuck. A while back I got stuck in the boot loop (I guess). It was after a few factory resets. It had been rooted. Now, I can get into twrp but once there I can't seem to find any of the files that I need to flash to get it going again. When I launch the KFU it says the device is "online" and device manager reads "Android Composite ADB Interface". I'm sorry if this isn't enough info but can someone give me a push in the right direction? :silly:
Still vague bro but hey you have twrp do you have fff? If you have those things select mount in twrp transfer ROM zip and a gapps zip to your sdcard but don't place them inside a folder... leave them in the open this is considered the root of your sdcard then select unmount go to install see if you can navigate to the files you put on the kindle if so select wipe, wipe factory reset, wipe cache wipe dalvik, wipe system, select install tap on the ROM zip flash it when done use the back button upper right... flash gapps then select reboot and system if prompted let it boot.. I suggest this ROM or a cm7 flavored variety.. http://forum.xda-developers.com/showthread.php?t=1778010
fff is the kindle logo with the blue (fire) lettering, right? v1.4a in the upper right corner. Let's me go into normal, recovery and reset boot mode? The only option that let's me make any progress is the recovery option and that loads me into twrp. The "mount" option in twrp gives me 4 choices, mount system, mount data, unmount cache, and unmount sdCard. Mount system and mount data are unchecked. And if I click the "mount usb storage" button it takes me to a screen that says "USB Storage Mounted -- Be sure to safely remove your device from your computer before unmounting!" and there's an "unmount" button underneath. That's all I'm seeing. I'm not trying to be vague. I just don't know what specifically is the relevant info to give. But thanks for helping out those who can't help themselves
Ok plug to your computer select mount make sure there are no checks in the boxes of data and system then hit the big button this will mount your sdcard transfer zips select unmount follow my instructions above...
hey man, it worked!:victory: But I'm sure you knew it would. So, is it a bad idea or is it even possible at this point to revert to the factory reset? You know, have it be totally stock? And is it just tricky or dangerous to do factory resets a few times? I like using just the stock kindle version. The kindle app is just a little funky. Or it was the last time I used it. But obviously I love the google suite. I hadn't made a back-up the last time because it was just as easy to download a few of the things at a time from the cloud. So, making a back up would be a good habit and help in a situation like this? Do you know of any good threads re: backups? And superuser is something I don't know anything about but how does it work and where should I learn more about that? Mega MEGA thanks again dude! :highfive:
Yeah if you want the best of both worlds go with rooted stock all the wipes I suggested after backing up first then flash this http://forum.xda-developers.com/showthread.php?t=1439916 the standard version not the altrom thats for dualboot your miles from that
What's the process to get to rooted stock? I just made a back up
akaFoxMulder said:
What's the process to get to rooted stock? I just made a back up
Click to expand...
Click to collapse
just put this on your sdcard wipe every thing but your external storage and flash it http://loadbalancing.modaco.com/dow...gned-MD5-569fe6550cfcfba68dabc3d088324a46.zip your external storage is your sd card you dont wanna wipe that
its nothing but rooted stock with playstore and it wont wipe out your recovery and fff in the process
when installing the modaco custom rom, what boxes do I want to have checked? Zip file sig is checked by default and Force MD5 check on all zips is unchecked. Good?
akaFoxMulder said:
when installing the modaco custom rom, what boxes do I want to have checked? Zip file sig is checked by default and Force MD5 check on all zips is unchecked. Good?
Click to expand...
Click to collapse
Just leave them all unchecked
thanks again for all your help thePooch. I've tried installing the rom a couple of times and it either freezes or I've got the following message.
Writing Data - Writing System - Writing Boot then E:Error in /sdcard/Gr9.2-altrom-update-.....
(Status 0)
*Verifying filesystems...
*verifying partition sizes...
Error flashing zip ‘/sdcard/Gr9.2xxx
do I need to just stay with the cm10 rom at this point? what other kind of fun stuff can I do to get this working:fingers-crossed:
I believe Thepooch told you earlier NOT to download the altrom. Check your download and try again.
no doubt. Funny how this stuff works the way that it's supposed to
soupmagnet said:
I believe Thepooch told you earlier NOT to download the altrom. Check your download and try again.
Click to expand...
Click to collapse
Thanks soupmagnet yes the altrom version will fail everytime because it needs extra partitions to work which do not and very likely will not ever exist on your device.... Intructions well it helps if they are read I gave very clear ones and I definatly said not to use the altrom........
ありがとうございました。 I think I'm done.
your welcome
Just out of the blue my Kindle just boots into recovery every time. I use TWRP and I've tried restoring multiple backups, I've tried wiping everything. Even factory reset won't do anything. I've also tried reflashing the ROM I have on it (CM9).
Any suggestions?
DO you have firefirefire?
No. Do I need it?
wizky911 said:
No. Do I need it?
Click to expand...
Click to collapse
Read:
http://forum.xda-developers.com/showthread.php?p=20455567
Sent from an Amazon Gindle Fireoid
Generally that can be cause by two main things a broken system or altered bootmode. Which twrp are you using, how and what order are you wiping, after you flash a rom what are you selecting as a reboot option, system, recovery or bootloader and lastly what rom are you flashing? Another reason other than the two main ones is some kind of mounting problem.
guitarman2010 said:
Read:
http://forum.xda-developers.com/showthread.php?p=20455567
Sent from an Amazon Gindle Fireoid
Click to expand...
Click to collapse
nothing in that utility works. the kindle goes straight to recovery. can anyone suggest anything else?
Im waiting for answers as well.
Thepooch said:
Generally that can be cause by two main things a broken system or altered bootmode. Which twrp are you using, how and what order are you wiping, after you flash a rom what are you selecting as a reboot option, system, recovery or bootloader and lastly what rom are you flashing? Another reason other than the two main ones is some kind of mounting problem.
Click to expand...
Click to collapse
I have TWRP v2.0. I factory reset, then wipe cache, then dalvik. It's been running CM9 reloaded for months, but I have 3 other ROMs on it to flash, while I was testing each one. but now none of them will flash. I unchecked check MD5 Sums and Signatures, the installation will say complete, then i wipe caches and reboot system, and I just get booted back into recovery
wizky911 said:
I have TWRP v2.0. I factory reset, then wipe cache, then dalvik. It's been running CM9 reloaded for months, but I have 3 other ROMs on it to flash, while I was testing each one. but now none of them will flash. I unchecked check MD5 Sums and Signatures, the installation will say complete, then i wipe caches and reboot system, and I just get booted back into recovery
Click to expand...
Click to collapse
I always have had trouble with roms that have gapps baked in. First go to mount in twrp make sure there are no checks in the boxes of system and data if so uncheck them , cache and sdcard should be checked by default select the big mount button after you have connected to pc. Transfer this rom zip http://forum.xda-developers.com/showthread.php?t=1778010 and the 20121011 jb gapps to your sdcard if it will mount http://wiki.rootzwiki.com/Google_Apps#Jelly_Bean_.28Android_4.1.x.29 unmount then unplug your kindle wipe factory reset, wipe cache,wipe dalvik, and wipe the system. Flash rom zip flash gapps zip then select reboot and system if prompted. If you get the same result or twrp throws a bunch of errors then soupkit is what you need because of some kind of mounting issue.http://forum.xda-developers.com/showthread.php?t=1850038 As well if you don`t have have the bootloader with the white kindle blue fire simply flash that in recovery from here only http://forum.xda-developers.com/showthread.php?t=1632375. Your recovery is way out of date flash this in recovery after you get the rest sorted and you are running again http://forum.xda-developers.com/showpost.php?p=30780737&postcount=180 this is the latest working version.
Edit: sidenote all these files are intended to be flashed as zips do not extract!
Thepooch said:
I always have had trouble with roms that have gapps baked in. First go to mount in twrp make sure there are no checks in the boxes of system and data if so uncheck them , cache and sdcard should be checked by default select the big mount button after you have connected to pc. Transfer this rom zip http://forum.xda-developers.com/showthread.php?t=1778010 and the 20121011 jb gapps to your sdcard if it will mount http://wiki.rootzwiki.com/Google_Apps#Jelly_Bean_.28Android_4.1.x.29 unmount then unplug your kindle wipe factory reset, wipe cache,wipe dalvik, and wipe the system. Flash rom zip flash gapps zip then select reboot and system if prompted. If you get the same result or twrp throws a bunch of errors then soupkit is what you need because of some kind of mounting issue.http://forum.xda-developers.com/showthread.php?t=1850038 As well if you don`t have have the bootloader with the white kindle blue fire simply flash that in recovery from here only http://forum.xda-developers.com/showthread.php?t=1632375. Your recovery is way out of date flash this in recovery after you get the rest sorted and you are running again http://forum.xda-developers.com/showpost.php?p=30780737&postcount=180 this is the latest working version.
Edit: sidenote all these files are intended to be flashed as zips do not extract!
Click to expand...
Click to collapse
I'm gonna try it
Good luck.
No luck.
Sent from my SPH-L710 using xda app-developers app
wizky911 said:
No luck.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Alright, try to pay attention...
If you installed FireFireFire1.4 (blue & white Kindle Fire logo) as you were instructed to previously, you can use the boot menu to reset your bootmode to normal (more information can be found in the FFF1.4 thread btw). Just hold the power button at startup until the boot menu appears, and select "reset boot mode".
Otherwise, you need to use either adb or fastboot to manually change your bootmode to 4000.
I tried to install Paranoid Android and GAPPS. It get force closing on setup so I booted back into recovery to try to fix it and now there is no OS. I can boot into Recovery and Fastboot only
so you wiped system in recovery?
why dont you provide us with EVERYTHING you did to cause this?
did you do a factory reset before installing PA? that would have prevented the force closes.
if all you can do is boot into recovery, then just do a factory reset and reflash your rom...its pretty simple
I had a similar issue and it was caused by not using the correct gapps package. Correct gapps for PA 4.2 http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.2-20130209.zip
I put it on a flashdrive and used an OTG cable to connect, then used "external SD" in TWRP.
Pirateghost said:
so you wiped system in recovery?
why dont you provide us with EVERYTHING you did to cause this?
did you do a factory reset before installing PA? that would have prevented the force closes.
if all you can do is boot into recovery, then just do a factory reset and reflash your rom...its pretty simple
Click to expand...
Click to collapse
I forgot which app I used to download the new image and GAPPS. I figured ig GAPPS was the issue i could wipe, so from Team Win Recovery Console I did a wipe of Cache, Dalvik Cache. I* *may* have also chosen to wipe System and Format data but I can't remember right now.
So I can boot into the recovery console but nothing else. If I try to boot it sits on the white Google logo until I pull the battery
ElevyNJ said:
I forgot which app I used to download the new image and GAPPS. I figured ig GAPPS was the issue i could wipe, so from Team Win Recovery Console I did a wipe of Cache, Dalvik Cache. I* *may* have also chosen to wipe System and Format data but I can't remember right now.
So I can boot into the recovery console but nothing else. If I try to boot it sits on the white Google logo until I pull the battery
Click to expand...
Click to collapse
you definitely wiped /system.
go back to stock from the return to stock thread in general. it's stickied.
ElevyNJ said:
I forgot which app I used to download the new image and GAPPS. I figured ig GAPPS was the issue i could wipe, so from Team Win Recovery Console I did a wipe of Cache, Dalvik Cache. I* *may* have also chosen to wipe System and Format data but I can't remember right now.
So I can boot into the recovery console but nothing else. If I try to boot it sits on the white Google logo until I pull the battery
Click to expand...
Click to collapse
if you selected wipe DATA, then your SDCARD is gone...you need to adb push your rom zip back to the sdcard and flash it. if you wiped system, then you have no OS installed any more...
Zepius said:
you definitely wiped /system.
go back to stock from the return to stock thread in general. it's stickied.
Click to expand...
Click to collapse
I assume it's also the link in your sig and must be done from a PC. I won't have access to a PC until tonight but I do have access to a MAC this afternoon
Pirateghost said:
if you selected wipe DATA, then your SDCARD is gone...you need to adb push your rom zip back to the sdcard and flash it. if you wiped system, then you have no OS installed any more...
Click to expand...
Click to collapse
Thanks.
ElevyNJ said:
I assume it's also the link in your sig and must be done from a PC. I won't have access to a PC until tonight but I do have access to a MAC this afternoon
Click to expand...
Click to collapse
yes, but for a mac just change fastboot to ./fastboot in the terminal window. instructions are still the same.
Zepius said:
yes, but for a mac just change fastboot to ./fastboot in the terminal window. instructions are still the same.
Click to expand...
Click to collapse
I'm at the screen with the android laying on it's back and the panel open. When I do ./adb devices it says list of devices attached but doesn't show anything.
I'm following the guide from http://forum.xda-developers.com/showthread.php?t=1917237
ElevyNJ said:
I'm at the screen with the android laying on it's back and the panel open. When I do ./adb devices it says list of devices attached but doesn't show anything.
I'm following the guide from http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Because your phone is in fast boot.
063_XOBX said:
Because your phone is in fast boot.
Click to expand...
Click to collapse
Sorry I'm being dense today
Ok phone is up and running again or shall I say limping. The 3G/4G indicator just shows bars.
Hi all,
My AFT wouldn't boot this AM. Booted to TWRP and tried a wipe cache but got an error with cache not present, went into advance wipe and fixed this.
Installed latest pre-rooted rom. No errors rebooted but wouldnt boot.
Installed previous version 5.2.4.0 firetv goes into a boot loop (white amazon logo then back to Twrp screen)
Also tried installing the unbrick image again no joys.
Any ideas?
thanks
I've had this issue before, make sure system is mounted and if it boots up factory reset from settings but make sure you have access to a pre rooted rom on either USB or ext xd
bamemanxxa3416 said:
I've had this issue before, make sure system is mounted and if it boots up factory reset from settings but make sure you have access to a pre rooted rom on either USB or ext xd
Click to expand...
Click to collapse
When I go into TWRP recovery and check whats mounted everything appears to be mounted.
When I do an advanced cache wipe or normal wipe. Messages respond success no errors Just will not boot.
This all started because I turned on the AFT and it was dead and would only boot to twrp and when checked the cache was in error tried the usual wipe/advance wipe still errors. the did a change system and redid the ext4 this brought back a "clean system" no more errors on installing due to cache and everything looked good. Just still no boot.