[Q] After installing ROM - gets stuck on Boot animation - Kindle Fire Q&A, Help & Troubleshooting

I posted the following in the AOKP Rom thread as that was the first one I tried, but the issue also occured after restoring from backup and installing CM10.1 ROM as well....
Ok, so Installed KFU and using it, I installed TWRP 2.5.0.0 & FFF, I downloaded the ROM and gapps, Used TWRP to Wipe Delv/chache/system, Installed ROM & then gapps, rebooted. The Kindle booted into the boot animation and I was under the impression it takes 10-15 mins for it to carry out the updates while this boot animation is going on (But there is no idication of what exactly is happening). An hour later the boot animation is still going with no indication of when it will actually boot into Android. So I'm thnking this has not worked. Can someone please guide me as to what to do now?
Thanks

Well i would say that the first issue would be that you said you wiped Cache, delvik, and system? Try going into TWRP and wipe /data also. That should do the trick!

tobiascuypers said:
Well i would say that the first issue would be that you said you wiped Cache, delvik, and system? Try going into TWRP and wipe /data also. That should do the trick!
Click to expand...
Click to collapse
Are you saying to start again or just go into TWRP then Wipe Data and the just reboot?

Go into TWRP and wipe data, cache, and delvik and system then reflash the ROM and Gapps
Sent from my SGH-I777 using Tapatalk 4 Beta

tobiascuypers said:
Go into TWRP and wipe data, cache, and delvik and system then reflash the ROM and Gapps
Sent from my SGH-I777 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hallelujah !!!
That worked. Thanks so much tobiascuypers !!!
Either I was blind or it was never mentioned but I did not see anywhere that said to wipe data. I'm now running CM10.1 ROM on Kindle Fire :good: Not sure if I want to mess with now by tring to install AOKP if there is any real benefit to doing so.
Thanks again !!!

jbl0ggs said:
Hallelujah !!!
That work. Thanks so much tobiascuypers !!!
Either I was blind or it was never mentioned but I did not see anywhere that said to wipe data. I'm now running CM10.1 ROM on Kindle Fire :good: Not sure if I want to mess with now by tring to install AOKP if there is any real benefit to doing so.
Thanks again !!!
Click to expand...
Click to collapse
When installing a new ROM, except from different CM10.1 variants, it is always recommended wipe data. Also. Here is a thanks button too(;
Sent from my SGH-I777 using Tapatalk 4 Beta

great job
tobiascuypers said:
When installing a new ROM, except from different CM10.1 variants, it is always recommended wipe data. Also. Here is a thanks button too(;
Sent from my SGH-I777 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Could not have said it better myself
---------- Post added at 05:05 PM ---------- Previous post was at 04:51 PM ----------
Darknesso666 said:
Could not have said it better myself
Click to expand...
Click to collapse
Also remember before you go and install any custom rom or root you phone make sure you do all your research first. To all the noobs out there. Before you root your phone understand you forfeit your warranty by doing so. make sure the root is for your make model of said phone. And after root has been done remember to FLASH (clockwork mod). After that then choose which rom you want and make sure its compatibly sound with your device. I run AOKP and love it.

Similar issue
Hello,
I am running into the a very similar situation. I am running 6.3.2
First I ran KFU 0.9.9, this installed FFF with no problem. KFU downloaded "most recent twrp" and installed it (but does not work, freezes at teamwin logo). and it had trouble installing su.
After looking around for ways to root kindle fire 6.3. without using KFU. I found a tutorial on the following website Eputor.com.
and ran these comands using cmd
1. adb push fbmode /data/local/fbmode
2. adb shell chmod 755 /data/local/fbmode
3. adb shell /data/local/fbmode
4. adb reboot
after booting into Fastboot mode, I use the following commands
1. fastboot -i 0x1949 flash bootloader u-boot.bin
2. fastboot -i 0x1949 flash recovery twrp.img
3. fastboot -i 0x1949 oem idme bootmode 4000
4. fastboot -i 0x1949 reboot
after booting into recover I use the following commands:
1. adb shell mount system
2. adb push su /system/xbin/su
3. adb shell chown 0.0 /system/xbin/su
4. adb shell chmod 06755 /system/xbin/su
After installing SU and gapps I believe I have accessed root because when I install 3rd party apps SU asks for permission to grant permission.
I have had to manually flash twrp 2.4 because every time I flash a newer twrp and boot into twrp, twrp gets stuck at at the teamwin logo then reboots with no access to recovery, only the teamwin logo. Ive flashed every twrp version from 2.6 going down the list of twrp downloads provided by the website that the twrp website provide but i am only able to get twrp to work on twrp 2.4.0.0. (sorry, I would provide the link but can't because I have not have 10 posts yet.)
after flashing twrp 2.4, I flashed 3 different roms
1st rom - I wiped cache, dalvik cache, factory rest and then flashed jb-4.2.2-kfire-hashcode-2013-02-12.
wiped cache again after install was complete, then flashed gapps and after that , wiped cache again.
after rebooting, I get stuck on a the boot animation. It then freezes for a few minutes then it reboots back into FFF then loops back same boot animation loop.
2nd rom - I then proceed to wiped cache, dalvik cache, factory rest and then flash Cm - 10.1 - 20130724 - 1413 - otter-sgt7.zip, wiped cache again after install was complete, then flashed gapps and after that , wiped cache again and reboot.
After rebooting, I get stuck on a the boot animation very similar to the previous rom, it boots up to the boot animation, but the difference is that the boot animation is off centered and cut off. It then freezes for a few minutes then it reboots back into FFF then loops back same boot animation loop.
3rd rom -I do the exact same with Pac_otter_4.3-build.1.RC_20130824- 144117.zip and the exact same thing happens boot loop with off centered boot logo. then reboots into fff and off centered boot logo.
I cant find a rom that will work. I really hope this is enough information, I hope someone out there can help me.
In this thread, it was advised to wipe data. in twrp 2.4.0.0, the wipe options are cache, dalvik cache, factory reset, system, external storage, and android secure. Is it nececary to wipe external storage, system and android secure? I have only wiped cache, dalvik cache, factory reset, system. Please advise.

It [email protected]!
tobiascuypers said:
Go into TWRP and wipe data, cache, and delvik and system then reflash the ROM and Gapps
Sent from my SGH-I777 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you!!!
Your advice worked.

Related

How to "un-brick" from Recovery

Using "CWM-based Recovery v5.0.2.7 FULL".
I can't get my device to boot. I'm running the previous version of Energy's ROM (not most recent). However, I can get into recovery and fastboot easily.
All I have tried is to factory reset, wipe caches, and re-install Energy, but it still will not boot. It's gotten close - can see the splashscreen, but no further.
Battery is at 100.
What do I need to do get this baby going again!
P.S. The original problem is that I let the battery drain too low for it to fully boot.
Always read the OP for the ROM before you flash...
http://forum.xda-developers.com/showthread.php?t=1528024
NRGZ28 said:
...
How to Flash this ROM:
- Root your device
- Install TWRP custom recovery
- Install the downloaded ROM .zip found in post #3
- Make sure to do a Factory Reset / Wipe before installing ROM
Click to expand...
Click to collapse
The 3.0 Kernel discussions also mention the the symptoms you will encounter if you do not follow instructions...
http://forum.xda-developers.com/showthread.php?t=1591869
Hashcode said:
PLEASE use TWRP to flash this ROM. You will probably bootloop if you don't. If you experience a really long boot animation, double check your recovery (change if necessary) and try it again.
Click to expand...
Click to collapse
Oddly enough I used TWRP to flash. Somehow it reverted me back to CWM. I don't have a clue.
It's currently trying very hard to boot. Once I get there what should be my first steps?
If it doesn't boot, should I try and push TWRP through fastboot?
Edit: pushed TWRP (latest). Wiped and reinstalled. Still won't get past boot animation.
Can I transfer a new ROM file using fastboot or will I need to use 'fastboot update' to install a different ROM?
Should I try reverting to stock image?

Help needed asap

I installed CM10 and GApps from here, http://forum.xda-developers.com/showthread.php?t=1778010, as I normally boot to recovery and wipe data, clear cache and davlik, install rom , install gapps, clear cache and davlik again and reboot. I get this screen now after Kindle Fire 1.4a boot screen. I can turn off and go back to recovery just fine, but I cannot get any ROM, new CM10 or Hashcode 4.1.1 previous to boot at all? Any help is greatly appreciated. I have Kindle Fire 1.4a and CWM Recovery 5.0.2.7. Please see attached image of screen as I see it with colored triangles flipping on my screen.
Your Question Does Not Belong Here.
Go Back To CM9 And Wipe Everything, Then Wipe Everything Again And Try CM10.
lkbeck said:
I installed CM10 and GApps from here, http://forum.xda-developers.com/showthread.php?t=1778010, as I normally boot to recovery and wipe data, clear cache and davlik, install rom , install gapps, clear cache and davlik again and reboot. I get this screen now after Kindle Fire 1.4a boot screen. I can turn off and go back to recovery just fine, but I cannot get any ROM, new CM10 or Hashcode 4.1.1 previous to boot at all? Any help is greatly appreciated. I have Kindle Fire 1.4a and CWM Recovery 5.0.2.7. Please see attached image of screen as I see it with colored triangles flipping on my screen.
Click to expand...
Click to collapse
As the previous person said wrong forum however what you are seeing is the boot animation. Have you actually just let it boot?
Sent from my Galaxy Nexus using Tapatalk 2
lkbeck said:
I installed CM10 and GApps from here, http://forum.xda-developers.com/showthread.php?t=1778010, as I normally boot to recovery and wipe data, clear cache and davlik, install rom , install gapps, clear cache and davlik again and reboot. I get this screen now after Kindle Fire 1.4a boot screen. I can turn off and go back to recovery just fine, but I cannot get any ROM, new CM10 or Hashcode 4.1.1 previous to boot at all? Any help is greatly appreciated. I have Kindle Fire 1.4a and CWM Recovery 5.0.2.7. Please see attached image of screen as I see it with colored triangles flipping on my screen.
Click to expand...
Click to collapse
Also switch your recovery to twrp cwm can brick the kindle flashing a ROM that that uses 3.0 kernel
Sent from my Galaxy Nexus using xda premium
lkbeck said:
I installed CM10 and GApps from here, http://forum.xda-developers.com/showthread.php?t=1778010, as I normally boot to recovery and wipe data, clear cache and davlik, install rom , install gapps, clear cache and davlik again and reboot. I get this screen now after Kindle Fire 1.4a boot screen. I can turn off and go back to recovery just fine, but I cannot get any ROM, new CM10 or Hashcode 4.1.1 previous to boot at all? Any help is greatly appreciated. I have Kindle Fire 1.4a and CWM Recovery 5.0.2.7. Please see attached image of screen as I see it with colored triangles flipping on my screen.
Click to expand...
Click to collapse
Don't use CWMR! I suggest you get TWRP asap.

TWRP 2.6 now asking for password

I installed elemental x kernel and all was fine went back into recovery and twrp is asking for a password and i cannot mount anything when i boot the system i all kinds of FC's now...
I fixed it by reformatting data then restarting recovery
Sent from my Nexus 7 using Tapatalk 4
unobtainiumdroid said:
I fixed it by reformatting data then restarting recovery
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
were you able to restore after that?
I had to adbpush the ROM through
Sent from my Nexus 7 using Tapatalk 4
i cannot restore data....
Many people have had this problem.
When you're asked for a password, hit cancel. Then go to Wipe and Factory Reset. If that doesn't work, then restart your recovery. If that still doesn't work then try reflashing TWRP again.
When you do the fastboot oem unlock, you should do it using stock recovery and let it reboot and wipe data.
Then boot back into bootloader to install twrp.
Don't do both at the same time.
sfhub said:
When you do the fastboot oem unlock, you should do it using stock recovery and let it reboot and wipe data.
Then boot back into bootloader to install twrp.
Don't do both at the same time.
Click to expand...
Click to collapse
I did... was running fine a few days and all of sudden this happened. Wiping data did but i still could not restore data from backup i had to reset and restore from titanium.
When TWRP does this to me I reboot into system then with goomanager I reinstall TWRP. It seems that some changes in the system cause this. AOSP Browser appears to do this to me or the kernel as those are the only thing I have on that modifies the system. Need more testing
Blackwidowman said:
When TWRP does this to me I reboot into system then with goomanager I reinstall TWRP. It seems that some changes in the system cause this. AOSP Browser appears to do this to me or the kernel as those are the only thing I have on that modifies the system. Need more testing
Click to expand...
Click to collapse
Happened to me after the kernel.
Sent from my Nexus 7 using Tapatalk 4
I have the kernel and also have aosp browser and twrp is fine so far.
Sent from my Nexus 7 using XDA Premium HD app
Hi, I have the same problem and I can't boot my tablet in normal mode, it remains frozen on start animation screen. I started unlocking bootloader with no problems and the problem started after i install the TWRP 2.6.3.0. I'm on Android 4.3.1 (JLS36I). I can't wipe or mount /data, I can't enter in ADB Sideload mode.
I tried to fix it installing TWRP again and I also installed CWM but with the same result.
I was trying to find the original recovery image but with no success.
Any idea about how to get out of this mess?
Thanks!
pvitruvian said:
Hi, I have the same problem and I can't boot my tablet in normal mode, it remains frozen on start animation screen. I started unlocking bootloader with no problems and the problem started after i install the TWRP 2.6.3.0. I'm on Android 4.3.1 (JLS36I). I can't wipe or mount /data, I can't enter in ADB Sideload mode.
I tried to fix it installing TWRP again and I also installed CWM but with the same result.
I was trying to find the original recovery image but with no success.
Any idea about how to get out of this mess?
Thanks!
Click to expand...
Click to collapse
If it is frozen on X then your /data is messed up. Do a wipe data factory reset from recovery.
If it is frozen on Google, then your /system is messed up, to a nowipe factory image restore.
It is doubtful TWRP caused this problem. Most likely your tablet corrupted /data and it only showed up after a reboot.
sfhub said:
If it is frozen on X then your /data is messed up. Do a wipe data factory reset from recovery.
If it is frozen on Google, then your /system is messed up, to a nowipe factory image restore.
d
It is doubtful TWRP caused this problem. Most likely your tablet corrupted /data and it only showed up after a reboot.
Click to expand...
Click to collapse
It was frozen on X but I couldn't wipe it because it didn't mount /data, all the wipe commands failed.
Now I could fix the problem. What I did was to connect an external drive through USB-OTG and I installed the SuperSu zip (the step where I was stuck), after that I could format data and perform a Factory Reset. After the first complete boot, the TWRP stopped to ask password and everything seems to be OK.
Thanks!

[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.

Help Fixing issue tab pro 8.4

Hello, I decided to root my device using Odin. I followed steps from a video and successfully rooted and installed twrp with flashify. When I booted to twrp I did a swipe without backup. I proceeded to install CM11 nightly with the gapps zip. Everything went well during installation and the device rebooted. I saw the cm mod logo upon reboot but I get error setup wizard failed after boot. I cant access the tablet or anything. All I see is the blue CM wallpaper and no apps. Upon further investigation, it turns out I flashed the wrong gapps zip? I tried rebooting to twrp recovery to reflash gapps. But problem is that I cant access twrp recovery only the stock recovery. It gives me limited options...update from adb, update from external, wipe data, wipe cache... Is there anyway to fix this? I installed adb and fastboot but when I install rom using adb sideload, i get signature failures all the time. I tried fastboot but apparently there is only download mode (which i used when rooting with odin). My device isnt recognized with fastboot devices command only adb devices. Can anyone help? I am new to this stuff.
Hi,
I will have your thread moved to your device section.
Good luck!
Try to wipe cache, then flash TWRP again by Odin.
If you can get TWRP up and running, you should be able to do the default wipe (cache, Dalvik, and user data) and flash CM11 and gapps again.
I think I had the same issue with CM11 not booting since I flashed the wrong gapps. But flash the right gapps, and you should be ok.

Categories

Resources