Kindle first generation:
- rooted and has twrp v2.3.1.1 working (seemingly) fine.
- copied and verified md5 checksum for all roms
- wiped system clearing previous rom
- performed factory reset creating new partitions
- cleared cache and dalvik
- flashed FIREFIREFIRE bootloader v1.4a(current)
- flashed gedeROM which uses cyanogenmod 9 (26-6-2012 recentish...)
- system reboot
- does not leave the cyanogenmod 9 load screen.... (-_-) [waited 30 minutes each time]
THE PROBLEM
- No matter which rom I verify or flash they all hang at the rom loading screen.
- have tried this same process with several diffrent roms including
-AlienDroidV7.0.zip
-gedeROM-KFire-CM9-26-6-2012.zip
-cm-9-20120711 (snapshot)
-jb-kfire-hashcode-10-10.zip
I have used the same procedure for all roms to no avail. Could there be something wrong with TWRP and that it isnt flashing the roms correctly?
(It returns saying that they were all sucessful)
Any help would be epic
Flash this zip in recovery to revert to the older twrp that one your using is broken http://forum.xda-developers.com/showpost.php?p=30780737&postcount=180 do a full wipe including the system minus the external storage/sdcard reflash your rom and gapps you should be fine.
Thepooch said:
Flash this zip in recovery to revert to the older twrp that one your using is broken http://forum.xda-developers.com/showpost.php?p=30780737&postcount=180 do a full wipe including the system minus the external storage/sdcard reflash your rom and gapps you should be fine.
Click to expand...
Click to collapse
Thanks!!!
I was having the *exact* same problem as the OP and reflashing the old recovery fixed it. Can't believe the current version is broken like this.
Further searching suggests that also checking "use rm -rf" for the formatting method under settings will solve the problem.
That's why I use the oldest. It has less bugs.
THANKS!
Any idea why the current release of TWRP has so many issues?
I am having the same problem as the OP. I rooted my Fire last summer and updated with various builds of the CM10/SGT7 for the Kindle Fire [Linaro] since then without any problems. I've been using the 1127 build and updated to the 1211 version. Now it just hangs at the CyanogenMod animation screen.
I've tried restoring with a backup that was made following the update to 1127, without success. Same with trying to reflash 1127 and even the 1105 builds, which worked well previously.
When I launch KFU on my Windows 7 machine, it sees my Fire intermittently. Mostly, KFU reports the Fire to be offline and unknown boot status.
TWRP is 2.2.2.1 and all the rest is from KFU 0.96
Any suggestions?
Did you wipe system and factory reset before installing?
"That's a special kind of stupid. The kind that makes me laugh."
I have the same problem as TrojanDAd. I was on stock 6.3.1 and rooted using KFU 0.9.6. It installed FFF 1.4a and TWRP 2.2.2.1. I have tried to install different roms from TWRP including Jandycane, Hashcode's latest AOSP JB rom, Hashcode's Unofficial CM10.1 rom, and two roms from twa_priv. Each time I flash a rom I do factory reset, wipe data, flash rom, flash GApps, wipe cache + Dalvik. When I reboot, it hangs at boot logo. I could post logcat if it would help but the errors are different for each rom and there are alot of errors.
soupmagnet said:
Did you wipe system and factory reset before installing?
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
No, I just did a dirty flash. I wiped the cache and Dalvik during the flash, but that was it.
Well crap... in that case, I'll make my own thread.
selyb said:
Well crap... in that case, I'll make my own thread.
Click to expand...
Click to collapse
It turns out that the "Mount Data" and "Mount System" boxes were checked. I unchecked them, wiped everything and then it finally booted to the lock screen.
Thanks to all on the selyb thread!
Related
I'm not sure where to begin. Here are the details:
Kindle was soft-bricked, recovered to stock using a fastboot cable and twrp/fff/stock rom.
Any time anything other than the stock KF rom (by that I mean that I've only tried AOSP roms instead of stock) is loaded, it gets stuck on whatever splash screen comes with the rom.
I usually wait 10-15 minutes to make sure it just isn't some sort of obscenely long first load.
I always flash gapps after I flash the rom, but I'm presuming it isn't the gapps flash that's causing the problem.
Am I missing something? I promise, I really have tried to search around.
Wipe factory/data reset, wipe cache, wipe dalvik, wipe system, flash rom zip, flash gapps zip, reboot then system if prompted. As well what recovery are you using? I suggest twrp 2.2.2.1 .
Thepooch said:
Wipe factory/data reset, wipe cache, wipe dalvik, wipe system, flash rom zip, flash gapps zip, reboot then system if prompted. As well what recovery are you using?
Click to expand...
Click to collapse
I'm using TWRP 2.3.1.1. I think that's the issue. I was just reading the similar thread posted recently, and apparently swapping to TWRP 2.2 will allow me to load an AOSP rom.
princeendo said:
I'm using TWRP 2.3.1.1. I think that's the issue. I was just reading the similar thread posted recently, and apparently swapping to TWRP 2.2 will allow me to load an AOSP rom.
Click to expand...
Click to collapse
try again make sure you wipe if it`s a no go return to 2.2.2.1
Thepooch said:
Your fine just make sure you wipe.
Click to expand...
Click to collapse
I have been wiping. I do a factory reset, then wipe cache and dalvik cache for good measure. Still get stuck.
Did you wipe the system? If that doesnt work restore your backup if you can and use smirkit the return to the older version of twrp http://forum.xda-developers.com/showthread.php?t=1500935 or fastboot flash older version.
Thepooch said:
did you wipe the system?
Click to expand...
Click to collapse
Not recently.
I just now did a system/data/cache/dalvik wipe and flashed AOKP/gapps. 3 minutes later, I'm having the same problem. I figure 3 minutes is enough time for a first-boot.
princeendo said:
Not recently.
I just now did a system/data/cache/dalvik wipe and flashed AOKP/gapps. 3 minutes later, I'm having the same problem. I figure 3 minutes is enough time for a first-boot.
Click to expand...
Click to collapse
sometimes so change your recovery.
Are you using TWRP 2.2.x or earlier?
soupmagnet said:
Are you using TWRP 2.2.x or earlier?
Click to expand...
Click to collapse
No. I came to the conclusion that I probably needed to change. However, on the recommendation given, I tried one more time to do all the wipes and go for it.
Switched to 2.2.2.1 and it worked!
I'm sure it's elsewhere...but why is 2.3 bad for this? And now that it's working, can I switch up to 2.3? What's the deal?
Stick with what you have now.
Twrp 2.3.1.1 formats in a way the Kindle does not like, according to the thread in development.
Sent from my Amazon Kindle Fire using xda app-developers app
Ixthusdan said:
Twrp 2.3.1.1 formats in a way the Kindle does not like, according to the thread in development.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
+1
I have a Samsung Galaxy Nexus GSM and have been trying to install the Paranoid Android flavor custom ROM, I had 2.22 installed not long ago but managed to screw it up when I updated it without clearing my security settings (I had a 4x4 pattern swipe which I couldn't enter with the update which restored it to 3x3 pattern) so I wiped and restored to stock 4.2. I'm now trying to re-install with any custom ROM but it's not working.
Whenever I install a ROM it seems to install ok but when I get to the boot screen it just hangs on the nexus/PA logo.
I've tried with:
Goo Manager
TWRP 2.2
TWRP 2.3
CWM 6.0.1.5
and with
PA 2.22
PA 2.99.1
PA 2.99.5
PA 2.99.6
PA 2.99.7
and I always get the same error, I've tried wiping all options within TWRP and CWM and going from there but that doesn't seem to work, the strange thing for me though is that if I re-install a stock Google ROM it works perfectly fine.
I'm fairly new so please be gentle.
flash the latest twrp and move the rom and gapps to your sdcard then follow this..
1. factory reset
2. wipe system
3. wipe cache
4. wipe dalvik
5. flash rom
6. flash gapps
7. reboot
if it still freezes at boot animation pull battery reboot to recovery wipe cache/dalvik and reboot
Thanks for the suggestion but that didn't work.
Any other suggestions?
When you say TWRP 2.3 do you mean 2.3.2.1? http://teamw.in/project/twrp2/90
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.
zephiK said:
When you say TWRP 2.3 do you mean 2.3.2.1?
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.
Click to expand...
Click to collapse
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).
Using TWRP, wiping cache, dalvik, and system should wipe everything except the sdcard contents. So doing these wipes should make your phone "bare stock" again as you described
Why don't you try downloading another custom ROM or download the same ROM again because maybe it is corrupted or something
osiris231 said:
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).
Click to expand...
Click to collapse
RANT: huh..... seriously? you couldn't have browsed around, searching for this COMMON issue (which usually comes down to user "error"), read the STICKIES, before posting?
first, internal storage = /data/media aka /storage/sdcard0/ aka /sdcard/
Please read all of this
http://forum.xda-developers.com/showthread.php?t=1626895
I am unable to install either hashcode's or twa_priv's cm 11.0. Installing with TWRP results in the blue kindle fire logo.
I have TWRP 2.6.3.1 installed and I did a full wipe (system, data and reset).
I can reinstall CM 10.1 and do a restore, but trying to install 11.0 results in the blue logo.
Any suggestions?
stresser said:
I am unable to install either hashcode's or twa_priv's cm 11.0. Installing with TWRP results in the blue kindle fire logo.
I have TWRP 2.6.3.1 installed and I did a full wipe (system, data and reset).
I can reinstall CM 10.1 and do a restore, but trying to install 11.0 results in the blue logo.
Any suggestions?
Click to expand...
Click to collapse
Did you also wipe Cache and Dalvik? Did you check md5sum on your ROM download?
stresser said:
I am unable to install either hashcode's or twa_priv's cm 11.0. Installing with TWRP results in the blue kindle fire logo.
I have TWRP 2.6.3.1 installed and I did a full wipe (system, data and reset).
I can reinstall CM 10.1 and do a restore, but trying to install 11.0 results in the blue logo.
Any suggestions?
Click to expand...
Click to collapse
Looks like you did a full wipe of everything but SD card. Before flashing the ROM you only need to "swipe" Then after the install you wipe Cache and Dalvik only. Then boot into the system. I would try to install Hashcodes CM 11 first from here http://forum.xda-developers.com/show....php?t=2543481 using the crackflasher mirror. Also check the md5sum of the zip.
If this does not work, it may require you to do a full system restore and go from there.
smirciat said:
Did you also wipe Cache and Dalvik? Did you check md5sum on your ROM download?
Click to expand...
Click to collapse
Yes did and the md5 sum was correct.
LinearEquation said:
Looks like you did a full wipe of everything but SD card. Before flashing the ROM you only need to "swipe" Then after the install you wipe Cache and Dalvik only. Then boot into the system. I would try to install Hashcodes CM 11 first from here http://forum.xda-developers.com/showthread.php?t=2543481 using the crackflasher mirror. Also check the md5sum of the zip.
Click to expand...
Click to collapse
Thanks for the suggestions, I agree I probably deleted everything but the SD card. the crackflasher mirror doesn't seem to work. The md5 sum was correct.
stresser said:
Thanks for the suggestions, I agree I probably deleted everything but the SD card. the crackflasher mirror doesn't seem to work. The md5 sum was correct.
Click to expand...
Click to collapse
This is the third instance of such an occurrence in recent times. Let's try 4.3 JB just to make sure there is nothing else going on (if you want?) Here is the latest release for Hashcodes 4.3 JB for KFHD 8.9 jem http://goo.im/devs/Hashcode/jem/cm10.2/cm-10.2-20131115-UNOFFICIAL-jem.zip Feel like giving that a try? Only "swipe" in TWRP before flashing and then wipe only CACHE and Dalvick after flashing and before booting into system.
If this does not work, it may require you to do a full system restore and go from there.
LinearEquation said:
This is the third instance of such an occurrence in recent times. Let's try 4.3 JB just to make sure there is nothing else going on (if you want?) Here is the latest release for Hashcodes 4.3 JB for KFHD 8.9 jem http://goo.im/devs/Hashcode/jem/cm10.2/cm-10.2-20131115-UNOFFICIAL-jem.zip Feel like giving that a try? Only "swipe" in TWRP before flashing and then wipe only CACHE and Dalvick after flashing and before booting into system.
If this does not work, it may require you to do a full system restore and go from there.
Click to expand...
Click to collapse
The 4.3 JB did not work. Had to do a full system restore to stock, reroot, and then install bootloader and then the cm10.2. One of the ROM updates must have really corrupted my kindle. The fact that some people have had similar problems must mean that there was a corrupt download or something.
Anyway the kindle is working now. Thanks for your help.
stresser said:
The 4.3 JB did not work. Had to do a full system restore to stock, reroot, and then install bootloader and then the cm10.2. One of the ROM updates must have really corrupted my kindle. The fact that some people have had similar problems must mean that there was a corrupt download or something.
Anyway the kindle is working now. Thanks for your help.
Click to expand...
Click to collapse
After installing 10.2 was able to install hashcodes cm 11 without any problems.
I really hope I can find someone to help me get this working.
Kindle fire hd 8.9
Ive been going around in circles for about two days trying to get CM10.2 on this thing. I've done a ton of reading and have reflashed probably a dozen times.
So, firstly I've installed HFFirstAide, used this program to downgrade to firmware 8.2.1. Then I disabled the auto update, turned on adb and allowing 3rd party installations (cant remember the acronym atm).
Then I rooted my device, transferred fireflash11.apk
kfhd8-freedom-boot-8.4.6
dfhd8-twrp-w.6.3.1-recovery
the stack override file
cm-10.2-20131115-UNOFFICIAL-jem.zip
gapps-kk-20131209
I should mention that i performed a md5 check on all of the files and they were fine.
After installing and running fireflash, and plugging the freedom boot and twrp into their slots (yes I checked the boxes as well), I ran the program and rebooted into recovery. Once there I did a backup, wipe of my cache, system, data, and devlik cache (ive also tried just a cache and a devlik wipe, factory reset ect. I've done this about 20 times.)
I then installed the cm zip and rebooted. (doing a wipe on subsequent attempts didn't make a difference).
Every single time I get stuck on the blue kindle fire logo. I can still access twrp and after restoring i get the same freezup. Only thing i can do from here is use kffirstaide to reinstall factory os.
I've tried other firmware zips with the same result. Lastly I tried just installing twrp and did a reboot without flashing a rom (i read somewhere that you could have twrp and amazon os no problem), and it still sticks on that same screen.
What am I doing wrong here?
Finally got it to work on the 22nd try. CM was working great...... and then I installed the gapps.zip file through twrp and it freezes on the blue cyanogenmod screen.... FML.
ABrich said:
Finally got it to work on the 22nd try. CM was working great...... and then I installed the gapps.zip file through twrp and it freezes on the blue cyanogenmod screen.... FML.
Click to expand...
Click to collapse
KK stands for Kitkat. You are using a Jellybean ROM with KitKat Gapps. use these 4.3 Gapps http://goo.im/gapps/gapps-jb-20130813-signed.zip
Oops I had no idea.
Thank you very much, all is good now
I have tried the roms below:
Pac-rom
LiquidSmooth
CyanogenMod 12.1
CyanogenMod 11
And the result is it always gets stuck at boot where the boot animation continues infinitely. I have gave it about 30 minutes to boot.
With LiquidSmooth I was able to run logcat, but CM12.1 I am not able to.
I have tried resetting system, data, caches in twrp and using the reset for new rom in philz.
I have tried flashing with both TWRP and Philz.
I am using the latest Philz and TWRP.
The only thing that has worked for me is samsung stock ROM, but I do not like the stock ROM.
Are there SPH-L900 phones you have to do something different?
Is there a way to get boot logs from CM12?
Am I doing something wrong?
See attachment from LiquidSmooth.
After flashing http://forum.xda-developers.com/showthread.php?t=2086769 everything worked.
GRMrGecko said:
After flashing http://forum.xda-developers.com/showthread.php?t=2086769 everything worked.
Click to expand...
Click to collapse
Hi,
I see that you got it working by using that thread, but what exactly did you flash from it? I had it working with CM12.1 but decided to flash the recovery from CM for my phone and it ruined the installation. Tried re-flashing with the latest nightly to get stuck in the CM infinite boot, returned to stock (that worked fine) flashed TWRP and CWM 6.0.4.3 Touch, re-did everything again with both, but cant go past the infinite boot. This happened the last time too, but it started working out of nowhere so I continued patching until I flashed "cm-12.1-20150828-NIGHTLY-l900-recovery.img". Now it doesn't boot again and redoing what I did the last time is not working (Wiping Cache, Dalvik...)
Thanks
Raziel10000 said:
Hi,
I see that you got it working by using that thread, but what exactly did you flash from it? I had it working with CM12.1 but decided to flash the recovery from CM for my phone and it ruined the installation. Tried re-flashing with the latest nightly to get stuck in the CM infinite boot, returned to stock (that worked fine) flashed TWRP and CWM 6.0.4.3 Touch, re-did everything again with both, but cant go past the infinite boot. This happened the last time too, but it started working out of nowhere so I continued patching until I flashed "cm-12.1-20150828-NIGHTLY-l900-recovery.img". Now it doesn't boot again and redoing what I did the last time is not working (Wiping Cache, Dalvik...)
Thanks
Click to expand...
Click to collapse
Followed this guide from some post I found after reading for 8 hours, LOL. Don't remember who it is from... It's for the Cyanide ROM but worked perfect for CM12.1 latest nightly with the latest GAPPs
1.) revert everything to stock
Using Odin3 v3.09 I first flashed this: L900VPUCNE2_L900SPTCNE2_SPR.zip
2.) Reboot and verify it's not bricked, then use ODIN to flash Philz philz_touch_6.15.4-l900.tar.md5
3.) Reboot into Philz recovery and follow these steps exactly
1. Mounts and Storage
Format / system
Format / cache
Format / data
Format / data and /data /media (/sdcard)
(note this isn't the EXTERNAL sdcard, on to which I had loaded the ROM, Shift and gapps)
2. Power Options > reboot recovery
3. Wipe cache partition
4. Advanced > Wipe dalvik cache
5. Wipe data / factory reset > Wipe data / factory reset
6. Wipe data / factory reset > clean and install new ROM
At one point Philz asked me if I wanted to root and I said yes.
3.) Flash (from the external sdcard) the ROM (Tablet style ROM found in OP "5.0.2-RC-7.1-tablet"), Then flash Shift (Shift-LP-4.3 other versions DID NOT WORK), then flash gapps (GApps-5.0.2-20150315-signed NO OTHER VERSION WOULD FLASH, got Error 20 every time) Here's the
After everything was flashed I rebooted and got stuck at boot animation AGAIN, so I rebooted into recovery and wiped cache. Just cache, not dalvik or user data, rebooted, and it worked.
Installed Netflix from appstore, when I logged in to netflix it asked me to update google play services (I've seen it do this on other devices as well). Updated google play services and went back to Netflix, chose a random show and tapped on it, stuck at "loading" screen. Rebooted phone, tried netflix again and it works.
This was a tough one! But it's working now and I've saved all these files in one place incase it bricks again. Now to install the Note 3/4 style faux-stitched-leather back cover I got off Amazon.
Thanks all!