Develop Bugs

4.1.1 aosp install problems

hi, i have been having problems installing hashcodes port of jellybean. I made a nandroid backup, did a factory restore, flashed the rom. and when it reboots the screen goes to fire fire fire bootloader, then a black screen. Then the screen flashes, and the kindle reboots back to bootloader. I have tried redownloading the JB rom, restored back to stock and tried again, and tried immediately installing Gapps after flashing the rom. Any help would be greatly appreciated. Thanks in advance.
p.s. im on 6.3.1

Josepho1997 said:
Wipe the cache and dalvik's cache too. You could also redownload it.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
it wipes cache when you do the factory restore, but i wiped again just for good measure, and tried wiping dalvik too. same thing. i have CWM touch as my recovery and the latest fire fire fire bootloader if that helps any. im wondering if trying with TWRP as the recovery might have any better luck, although i dont know why it would.

Yeah put twrp on use smirkis scripts to replace cwmr with twrp and try again also when going from one system to another always wipe system before flashing rom and jb gapps right after

I believe hash code said not to use cwm anymore, so give twrp a try. I've had no problem flashing any of hashcods or lithiums jb roms. I'm on the newest build of twrp.
Sent from my Kindle Fire using xda app-developers app

waffull said:
I believe hash code said not to use cwm anymore, so give twrp a try. I've had no problem flashing any of hashcods or lithiums jb roms. I'm on the newest build of twrp.
Sent from my Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Ok, installed twrp, wiped everything, and selected both the rom and the gaps zip. Twrp finishes, I reboot and it does the same thing as before.

Never mind, finally got it working. Thanks for all the help

Sheesh and never once hit the thanks button lol j/k

[Q] Custom Roms Stuck at Splash Screen

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

[Q] roms do not make it past cyanogen mod screen

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!

[Q] Boot Fail after Custom ROM

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

Boot loop issue :( please help

Ok, so i was using the cyanogenmod nightlys just fine until i decided to want to try other roms (Pac-man, exodus, etc.) when i loaded the first i used clockwork recovery and it seemed to go smoothly and installed the Gapps, and BAM boot loop, i can still access the recovery menu and the Odin mode menus with the boot sequence, ive successfully side-loaded other roms and Gapps and nothing seems to work, everything just gives me the boot loop, Any help is much appreciated.
Edit: forgot to mention, sometimes it loads the rom but only for a few seconds and reboots again

Assume you did clean flash? Wiping data, cache, dalvik cache.
Also twrp recovery works a little better flashing lollipop roms.

madbat99 said:
Assume you did clean flash? Wiping data, cache, dalvik cache.
Also twrp recovery works a little better flashing lollipop roms.
Click to expand...
Click to collapse
yes, i did a clean flash, do you think it could be as simple as using twrp?

Could even be the gapps you're using. If you're using a very recent build of a rom, make sure you're using new gapps. Try open gapps.
It's also sometimes necessary to wipe internal storage.

madbat99 said:
Could even be the gapps you're using. If you're using a very recent build of a rom, make sure you're using new gapps. Try open gapps.
It's also sometimes necessary to wipe internal storage.
Click to expand...
Click to collapse
ive tried different versions of gapps but ill give open another shot, whats the best way to wipe the internal storage?

Shadow00f said:
ive tried different versions of gapps but ill give open another shot, whats the best way to wipe the internal storage?
Click to expand...
Click to collapse
In twrp. Wipe/advanced wipe/ internal storage. Make sure you have anything you need from internal backed up.