I have had my G2 since march and recently tried some flashing and such. I'm not new to flashing and ROMs and recoveries in general but I'm running into some problems.
I was having issues with lag in the stock odexed KitKat rom so i tried restoring my backup from my ZVA before I flashed anything. Upon restoring, when I boot, I get a LG boot animation, not the sprint spark animation. I tried the Team D3rp ROM that is ZVA based and I'm currently stuck on the stock android boot animation. I even made sure to flash the correct radios.
I'd really appreciate some help with this because as of right now my phone is useless and I have no idea what I should do.
I think this is some error with the boot partition or boot script and I have never messed with that stuff other than flashing ROMs with the boot scripts built in. I get no errors when flashing and the logs read that boot.imgs and partitions are being flashed successfully and I have tried flashing a few different kernels such as furnace kernel and dormianx kernel. I'm sure they are the right kernels for my model (ls980) as the download says they are and they all flash successfully.
Thanks for any help.
I think I fixed the problem by wiping the data partition....
Related
well i am a little lost... i tried to update the kernel to the newest version of savaged zen. But got stuck on the white screen, so i went back and wiped both catches again, then i got to the boot animation and now thats looping.. okay so i made a backup before starting but now after wiping everything and restoring the backup is boot looping too. Any suggestions?
Try another kernel. I am using the BCblend kernel from november, it's awesome and very stable. Once you get it booted, go into your advanced wifi settings and set your sleep policy to never.
well... my backup boot loops too... wouldnt the backup have the old kernel?
It's possible your phone doesn't like that kernel either, mine didn't. How long were you running it before flashing the new kernel? I would try at least a couple more kernels and if you still can't get it booted then wipe and start over. What version of MIUI are you running?
In my opinion...if you have a good working kernel do not change it. From what ive seen every custom rom is based off a stock rom that comes with a kernel. Usually only custom kernels that match the rom version work well. So it could be the rom and the kernel dont work well together. One thing is nobody seems to list which kernel version is from which rom. So its hard to tell. Also I think your pri version will mess with compatability also. Basically newest rom versions should work with newest kernels. But if your on an older rom...the older kernels will probably work better. And usually kernels come out (it seems) before rom versions. Like new miui kernel supports 4g, but the rom does not support it yet. Also nandroid? backups should have the kernel also. Not sure bout miui backup. But wiping and installing it fresh usually works well. If not you know the deal..wipe everything..then flash the rom..and start over So.....find a good one...keep it=no issues
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
chirantan.f said:
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
Click to expand...
Click to collapse
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
i would also like to note here that i tried installing AOSP based ROMs also, and AOKP didnt work, got stuck at nexus like boot animation forever, but when i tried installing CM10.1.2 (which is what i was running when i tried to get back to TW based ROM) it worked perfectly, so for now i am back to CM, but i would really get back to flashing different ROMs and trying them out. just makes me wonder if CM is the reason i am not able to install anything else, just a thought...
has anybody else tried going to any other ROMs from CM 10.1.2?
your help is appreciated!
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
Click to expand...
Click to collapse
thanks for your reply, but i have tried doing that, i also wipe data and system along with cache and dalvik before installing any new ROM.
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
Click to expand...
Click to collapse
i have latest recovery , TWRP 2.6.0.0 and i have given more than an hour to boot up and still nothing. i have been flashing ROMs like an addict since i got this phone last year, but when CM 10.1 stable was released i stayed on it till today, but now i cannot install any other ROM, i can odin to stock 4.1.1 ROM or install cm 10.1.2 which i did just now, but no other ROM, either TW based on AOSP based is working...which is very weird for me.
Were you able to fix this issue at all? I am facing the same issue, in my case, the phone was encrypted on stock TW. I roooted and put in CM 10.1.2 and now when I try installing Dandroid, the install itself would work but I am struck at the "type password to unlock the screen". If I reflash CM10.1.2, I can login fine. Any pointers?
So I switched to AOSP ROMs and now I wanted to go back to a Sense ROM but every time I flash one it boot loops. I've tried wiping the memory before and after flashing but the ROM won't stay stable. I've tried ARHD as well as Sinless. Even GPE ROMs aren't stable anymore. Is there something I'm missing? Any help will be greatly appreciated.
Try to adb erase cache, than install recovery again. Or try a different recovery (in particular TWRP seem to cause some ROM flashing issues for some folks, so try CWM).
And its a bootloop (phone restarts over and over) and not just frozen on the splash screen, right? Because with any 2.2x based ROM (including current ARHD) long boot time (like 5-10 minutes) is a common issue if you haven't updated firmware.
redpoint73 said:
Try to adb erase cache, than install recovery again. Or try a different recovery (in particular TWRP seem to cause some ROM flashing issues for some folks, so try CWM).
And its a bootloop (phone restarts over and over) and not just frozen on the splash screen, right? Because with any 2.2x based ROM (including current ARHD) long boot time (like 5-10 minutes) is a common issue if you haven't updated firmware.
Click to expand...
Click to collapse
ARHD did the strangest thing. Right after flashing the ROM, the screen dimmed and went black and did nothing. I thought that it froze or something, so I rebooted the phone by holding power and up. The ROM never booted, so I tried Sinless Sense ROM. It did boot but the boot loops happened. My phone isn't S-Off if that helps. Also, when I boot into the bootloader, it says "RADIO-INVALID_VER_INFO" and "OpenDSP-INVALID_VER_INFO" To correect that I tried flashing a T-Moblie radio, but that didn't work. I'm not sure if the problems are related.
I will try the steps you reccommend when I get off work.
No radio info in hboot is a known issue (reported by others). But I don't think in itself, its anything to worry about.
If you haven't updated your firmware to 2.22 you should do that. Or dig up the latest ROM version for your firmware.
redpoint73 said:
No radio info in hboot is a known issue (reported by others). But I don't think in itself, its anything to worry about.
Click to expand...
Click to collapse
I got it to work somhow lol. I just flashed ARHD again and this time just let it sit for a while. The ROM booted up with no problem and is stable. I will still erase the cache and try CWM recovery. Thanks a lot for your support! Next stop is S-OFF!!
I tried flashing a nightly of CM12 on my M919 after no problems for almost 2 weeks. After flashing, my phone was stuck in boot with the CM logo. I tried flashing previous versions of the rom wiping and clearing each time. All I got was the CM logo. I finally decided to start from scratch and reinstalled stock(4.4.4) with ODIN 3.07. Phone booted right up. Rooted the phone with CF-Auto-Root (KTU84P.M919UVUFNH7) with no problems. Ran it for the day to make sure no issues. After feeling comfortable, I downloaded and tried flashing CM11 Snapshot M12 since it's based off 4.4.4. Boot loop again. I tried CM12 with the same results. I'm using CWMR 6.0.4.7. I've tried newer versions of both CWMR and TWRP(I don't remember what versions they were). I'd like to go back to using 5.0, if possible. I'm not sure if I've missed a step in rooting, since it's been so long that I rooted/flashed this phone. Right now it's running stock 4.4.4/M919UVUFNK2 and rooted. Any suggestions as to what I could try?
That nightly may have borked some files causing a problem, the nightlies are usually full of warnings about possibly causing boot loops or lockups and always recommend a nandroid b/u before flashing.
A nightly is a way of trying something out on other people's phones to see if it works well enough to add it as an update to the regular rom build.
If your that desperate for a nightly you need to follow the thread for a couple of days and see how others do with it.
If all you see is "I flashed the nightly and boot loops all over the place, don't bother, otherwise you find yourself in this thread.
Try a factory reset and flashing again,
also get a newer CWM recovery 6051 (if not mistaken) but stay away from the nightlies.
If you really need a reliable phone that works all the time and doesn't windup dead, just keep your stock rooted rom. And lollipop will be here soon as an update, probably by mid-march, the you'll have all the lollipops you want.
Pp.
Hi! First off i i have latest multirom/twrp installed. haveing issuses with twrp rebooting when flashing everything without a aroma installer...cant flash kernals, boot screens, mods ect.,( unless its flashed through aroma). I can not flash kernals, mods, ect on my main rom. The host roms in multirom do not have these isues, and can flash kernals,,,,ect no problem. When trying to flash anything that is NOT throgh aroma on the host rom, TWRP resets. My main rom works flawless otherwise. To guess, i must have a corrupt partion. I wouldnt mind flshing a rooted stock ru to fix the partion, but im afraid after backing up all my roms, ill lose all my hard work. Has anyone ever had this issue, and what would be the safest way to get everything back to norm. Devs, your input would be much appreciated.. Im not at all sure what path i should take....