I have just successfully rooted my kindle and downloaded several different roms to play with.
In TWRP, I made a backup of my rooted stock ROM.
With any new ROM that I flash, when I try to boot, I get stuck on that ROM's bootsplash.
I've tried with the latested jandycane, CM10+SGT7, and MIUI...all the same problem. I wait 30 minutes to an hour for each, but none boot all the way.
In TWRP, I have no problem restoring the rooted stock ROM, so the KF isn't bricked, I just can't use any new ROMs.
Any suggestions on what the problem might be?
EDIT: I'm using TWRP 2.3.1. I know there are formatting issues, so in settings, I use the "use rm -rf" option.
Are you remembering to wipe system and factory reset before flashing the ROMs?
Related
Hey guys, I am afraid I have quite a problem.
I have flashed roms before (latest one was Defrost 1.8), but then got stuck into a bootloop. I then re-rooted my desire, and now I cannot flash any non-stuck ROMs. They all install just fine, but then get stuck on the green HTC screen.
Any Ideas what I Could do? I did factory reset, Cache Wipe, Dalvik Wipe... and tried flashing again. It just gets stuck in the first HTC screen, with the screen turned on at maximum brightness...
Any ideas???'
Thanks
Wipe and reflash a stock HTC ROM
Root it
Then reflash upto Defrost 1.8 again
See if that makes any Diff and post up and update
I have done that before, provided using MODACOs update.zip Stock rom does count.
I started from that again. You think I should unroot and root again?
I just wiped, and plugged into USB mode, entered Recovery, and installed update.zip provided (Stock but rooted sense 2.1 rom)
BTW. Tanks a lot for your help
If your on Stock but a rooted ROM try making a nandroid backup so you can flash to that quickly again and then have a shot with a Cooked ROM, if it fails nandroid covers
I have done that multiple times, this is exactly when I get stuck on that green boot screen, with nothing happening anymore. (I have waited over 15 minutes...)
I always have to go back to recovery, and nandroid restore to my 2.1....
Have you updated the Radio or anything recently??
Nope.... Nothing fancy really. I had fixed the permissions through Rom Manager... that's about it....
I rooted my wifes Kindle Fire and verified I had root on original ROM. Installed FireFireFire and CWM.
Made a backup of ROM in CWM, did factory reset, formatted cache/dalvik cache and flashed "Jandycane" ROM with GApps. When KF got to boot animation; device would freeze and reboot. So I redownloaded ROM and GApps and tried once more; again stuck with bootloop.
Restoring backup of original ROM and all is good.
I've tried several other JB ROMS and same problem with all of them so I know I'm missing something....just cant figure it out.
Any help would be greatly appreciated!
which clockwork mod upgrade with this to the newest or change to twrp http://forum.xda-developers.com/showthread.php?t=1500935
Loading TWRP 2.2.0 seems to have resolved the problem.
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
Hi,
I was frustrated with the delay in T-Mobile's release of KitKat for the GSIII, so I decided to root my phone last night in order to try flashing CM11 on it. Rooted my phone with Towelroot, installed ROM Manager and CWM, and created backups on Kies and through CWM. Then I proceeded to do data wipe/factory reset, cache wipe, and /system format. Tried to flash CM11, but got a status 7 error.
I freaked out, so I decided to restore everything from the backup I'd created. Restoration seemed like a success, but now I get the error "Unfortunately, the process com.google.process.gapps has stopped" in an endless loop, and it prevents me and any apps from doing anything. I tried clearing dalvik cache in recovery, but the problem still persists. Read on a few threads that I should flash to stock firmware via Odin, but I'm currently on a macbook, so I can't install it.
tl;dr - Prepped to flash CM11, reached status 7 error, got freaked out, and did restore via CWM, only to get infinite loop of gapp crashes. No access to Odin or PC. Not hard bricked or soft bricked, but essentially useless phone. Help? );
if you can still get to recovery, download latest gapps and flash that
Did you factory reset before or after you restored your back up?
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Try to factory reset again
vvnn said:
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Click to expand...
Click to collapse
If I'm not mistaken, there is some device ID that will change each time you flash a new rom. It may be something to do with this ID not matching the one in the restored data. Purely a guess but seems logical to me.
Anyway, factory resetting will most likely solve this for you, but I wanted to add that except in certain circumstances, you shouldn't ever manually format /system. (and one format on any partition is sufficient. There shouldn't be any need to format multiple times). If you format /system, you are wiping the O/S off of your device. Then what happens if you have problems flashing a rom, or firmware? I've seen it happen many times and I often end up spending a couple of days working with them just to get the thing to boot up again!
When you flash a rom, the first thing it does is format /system. So there is just no need to do this manually. At least if the rom fails to flash (such as failing the assert checks), youll still have something to boot into. Hope this helps in the future!
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.
Hey. So, my dad had a n5120 and it randomly just fell into an infinite bootloop. It had a version of Cyanogen Mod on it. No big deal, I thought. I flashed another ROM from the forums here and same thing. Bootloop. I've been flashing ROMs and messing around with Android for a little while now so I did the basic troubleshooting, wiped cache partition, dalvik cache and factory reset. Still boot looped. I tried installing several ROMs, to no avail (all flashed successfully, but bootlooped). I flashed the stock firmware (recovery, system etc.) with Odin, but still no luck!
I am now stumped. Can anyone help?
nanokiwi said:
Hey. So, my dad had a n5120 and it randomly just fell into an infinite bootloop. It had a version of Cyanogen Mod on it. No big deal, I thought. I flashed another ROM from the forums here and same thing. Bootloop. I've been flashing ROMs and messing around with Android for a little while now so I did the basic troubleshooting, wiped cache partition, dalvik cache and factory reset. Still boot looped. I tried installing several ROMs, to no avail (all flashed successfully, but bootlooped). I flashed the stock firmware (recovery, system etc.) with Odin, but still no luck!
I am now stumped. Can anyone help?
Click to expand...
Click to collapse
You are simply having wrong bootloader issue if I make a quess...I would check it out civato's ROM and follow the instruction.
basically, flash n5120 with odin, and then flash civato's n5120 flexburst room and see if it resolves your issue...