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
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
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!
Is there anything I can do?
So I installed the 12/10 Nightly of CM10 and I am stuck on this ROM. After about an hour all my application force close including Trebuchet. When I reboot into recovery, TWRP 2.3.1.1, I try to restore one of my backed up ROMs. It looks as though everything goes fine on the restore, but when I reboot system, I am still on the 12/10 Nightly of CM10.
I have tried re-installing TWRP, I have tried installing a new different ROM, I have tried re-rooting using odin, I have tried un-rooting using odin, I have tried installing CWM in a zip form and pushing it by command prompts and I am just about out of all options. I have also tried to install super su and uninstall and re-install superuser, thinking it might be that and no luck there either. I am not sure what to do.
Please help if you can.
Face_Melter said:
Is there anything I can do?
So I installed the 12/10 Nightly of CM10 and I am stuck on this ROM. After about an hour all my application force close including Trebuchet. When I reboot into recovery, TWRP 2.3.1.1, I try to restore one of my backed up ROMs. It looks as though everything goes fine on the restore, but when I reboot system, I am still on the 12/10 Nightly of CM10.
I have tried re-installing TWRP, I have tried installing a new different ROM, I have tried re-rooting using odin, I have tried un-rooting using odin, I have tried installing CWM in a zip form and pushing it by command prompts and I am just about out of all options. I have also tried to install super su and uninstall and re-install superuser, thinking it might be that and no luck there either. I am not sure what to do.
Please help if you can.
Click to expand...
Click to collapse
You shouldn't have too, but try formatting system before flashing.
And of course wipe cache and dalvik.
Best of luck,
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Brandon168 said:
You shouldn't have too, but try formatting system before flashing.
And of course wipe cache and dalvik.
Best of luck,
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Yeah I always wipe cache/dalvik, wipe system and factory reset before installing anything new.
try pulling the battery? try twrp 2.2.2.0? i had problems restoring w/ twrp 2.3.1.1. where i didn't have problems with a rom before but after restoring that same rom, i would run into rr and sod.
which cwm did you try to install? did you try sk8erwitskil's cwm? install over twrp, reboot recovery, and then install from there? if not, maybe try a different sdcard?
Face_Melter said:
Yeah I always wipe cache/dalvik, wipe system and factory reset before installing anything new.
Click to expand...
Click to collapse
I always do this. Wipe factory then system then cache then dalvik in that order and never had issue. I also went back to twrp2.2.20
merrygocow said:
try pulling the battery? try twrp 2.2.2.0? i had problems restoring w/ twrp 2.3.1.1. where i didn't have problems with a rom before but after restoring that same rom, i would run into rr and sod.
which cwm did you try to install? did you try sk8erwitskil's cwm? install over twrp, reboot recovery, and then install from there? if not, maybe try a different sdcard?
Click to expand...
Click to collapse
I have tried all versions of CWM and I have tried going back to twrp 2.2.2.0 and everytime I reboot I am still on 2.3.1.1. No matter what I do I still stuck on CM10 and twrp 2.3.1.1.
What could have happened? It seems as though nothing will flash properly.
This sounds like what happened to my 32GB SanDisk card; it turned read-only. Have you tried flashing a ROM? Maybe with CWM.
Sent from my Samsung SGH-T989 running CM10 by TeamChopsticks.
So I have read around to see what could be wrong. It sounds as though my phone is not writing to the nand. Is there anyway to fix that or no?
Have you tried restoring to stock Rom via Odin or flashing from a app that does it for you?
~~~~~~~~~~~~~~~~~~~~~
Samsung galaxy s2
Rom: Jedi knight 6
kernel: Jedi kernel 2
~~~~~~~~~~~~~~~~~~~~~
And you thought celebrities weren't smart! =P
Okay, I searched before posting. Here is my steps.
I was on SKYNOTE 8.2 and wanted to go back to stock and see what At&t's update was about.
Once back to stock, I rooted my phone and have been on this setup for about 2 weeks.
I was in the original thread and saw the new 4.2.2 Collective AoCP / CM10.1 ROM.
I wanted to try it out.
Using TWRP's latest, followed all instructions and when rebooting it still has stock root ROM.
What am I doing wrong?
I thought it was TWRP so I went to an earlier ver, still no change.
I've tried 4 times now to flash this 4.2.2 Rom and nothing.
Factory Reset
Wiped Dalvik
Install Zip
Install gapps
It says to wipe cache and data again
then boot up
It boots up alright, right into my old phone.
Any input I can get is appreciated guys !!!! Thanks.
Copy the ROM to your device (some storage folder)
Boot directly to TWRP
Manually install the ROM and the appropriate GAPPS
(watch the script window and see what it says.. look for errors)
Clear caches and dalvik
reboot
LuckyColdJohnson said:
Okay, I searched before posting. Here is my steps.
I was on SKYNOTE 8.2 and wanted to go back to stock and see what At&t's update was about.
Once back to stock, I rooted my phone and have been on this setup for about 2 weeks.
I was in the original thread and saw the new 4.2.2 Collective AoCP / CM10.1 ROM.
I wanted to try it out.
Using TWRP's latest, followed all instructions and when rebooting it still has stock root ROM.
What am I doing wrong?
I thought it was TWRP so I went to an earlier ver, still no change.
I've tried 4 times now to flash this 4.2.2 Rom and nothing.
Factory Reset
Wiped Dalvik
Install Zip
Install gapps
It says to wipe cache and data again
then boot up
It boots up alright, right into my old phone.
Any input I can get is appreciated guys !!!! Thanks.
Click to expand...
Click to collapse
Try wiping cache/delvik cache, then factory reset twice, then system wipe twice, Install .zip, Install GApps, then wipe cache/delvik again(don't wipe data after .zip is installed. That's how I always do it and it works great.
I think its my recovery Twrp. I changed something.
adam_wingert said:
Try wiping cache/delvik cache, then factory reset twice, then system wipe twice, Install .zip, Install GApps, then wipe cache/delvik again(don't wipe data after .zip is installed. That's how I always do it and it works great.
Click to expand...
Click to collapse
I have tried everything. Its got to be the recovery. No matter what I do in twrp, nothing changes. It says updating partitions and stimulating actions
. It also says successful. After updating to the newest twrp it started this. I changed something. ##[email protected] went into settings and reset....nothing. What if I flashed CWM and then went back to TWRP.
LuckyColdJohnson said:
I have tried everything. Its got to be the recovery. No matter what I do in twrp, nothing changes. It says updating partitions and stimulating actions
. It also says successful. After updating to the newest twrp it started this. I changed something. ##[email protected] went into settings and reset....nothing. What if I flashed CWM and then went back to TWRP.
Click to expand...
Click to collapse
Try cf auto root to reinstall stock then reinstall twrp through odin
Sent from my GT-N7105 using xda premium
What have I done ?
Android The Greek said:
Try cf auto root to reinstall stock then reinstall twrp through odin
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Okay guys....This has made me sick to my stomach.....I have tried all the different methods. I even soft bricked my phone today using CWM.
Kies wouldnt even fix my phone.
I had to download stock firmware and flash via Odin to get back.
Installed TWRP
Rooted
Went into recovery and wiped everything again
Installed the custom ROM
Rebooted
TWRP didnt do anything even though it says it did.
My phone boots up like normal with Att logo and works but no Custom Rom and no wipes.
What is this? Im going to try other things but wow, this is crazy.
On my SD card I have alot of stuff. I also have a folder named TWRP, it has a back up in there. I wonder if I should remove that?
IDK,,,,,Stuck with Stock root for now. Help If you can. Never had this issue before. What a day
LuckyColdJohnson said:
Okay guys....This has made me sick to my stomach.....I have tried all the different methods. I even soft bricked my phone today using CWM.
Kies wouldnt even fix my phone.
I had to download stock firmware and flash via Odin to get back.
Installed TWRP
Rooted
Went into recovery and wiped everything again
Installed the custom ROM
Rebooted
TWRP didnt do anything even though it says it did.
My phone boots up like normal with Att logo and works but no Custom Rom and no wipes.
What is this? Im going to try other things but wow, this is crazy.
On my SD card I have alot of stuff. I also have a folder named TWRP, it has a back up in there. I wonder if I should remove that?
IDK,,,,,Stuck with Stock root for now. Help If you can. Never had this issue before. What a day
Click to expand...
Click to collapse
Might as well try everything. wipe your sd card in twrp,if that doesn't work reformat through android when booted. Then copy the custom rom over and try again. Only other thing I can think to try is to check that all partitions that are needed are mounted, or try CWM instead.
Also, how did you install TWRP? Through the app? that is the best way to do it, I have had problems flashing twrp through CWM or through the computer. If you aren't already, use goomanager to install it. TWRP has instructions on their website
I figured it out!!!!!!!
Doggydude said:
Might as well try everything. wipe your sd card in twrp,if that doesn't work reformat through android when booted. Then copy the custom rom over and try again. Only other thing I can think to try is to check that all partitions that are needed are mounted, or try CWM instead.
Also, how did you install TWRP? Through the app? that is the best way to do it, I have had problems flashing twrp through CWM or through the computer. If you aren't already, use goomanager to install it. TWRP has instructions on their website
Click to expand...
Click to collapse
It was the settings in TWRP. One of the boxes was checked. Sim actions for theming. I unchecked that and was on my way. Rocking The Collective AoCP now !!!!! Yes.....Thanks to all of you for your input. I'm going back to each and will hit thanks right now! Thanks again XDA members.
Lucky
I'm glad things worked out... isn't it amazing how attached we get to our toys
Sent from my GT-N7105 using Tapatalk 2
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.