Hi everyone,
i have a problem with my rooted LG G3 855. After flashing Cloudy 2.5 i want go back to a cm based rom. After installing any CM based rom, my phone messed up. The "Uprade in Progress" message appears. After that my phone reboots and the initializing progess begin again. Anybody else faces this problem? Any solutions? I tried different roms. Nothing works. Only backups of older roms seems to be stable. Dont know what happened. I always did a clean install.
Related
Guys need help.
My device is E988 and I love AOSP ROMs. I have had reboot issue from past month, before that everything used to be fine. To my bad luck now every AOSP ROM I install reboots randomly. And specially sometimes when I text phone freezes and reboots causing text msg to fail and also sometimes on incoming calls. I have been using cm11 official builds n tried every other AOSP ROMs. Same problem. But everything is fine on stock and stock based ROMs. Flashed .kdz and then rooted and installed AOSP based rom and again kernel panics. Is this just me or any other e988 users experiencing this issue? I have flashed all kinds on e988 modems too. If anyone interested to look into this issue I'll be glad to provide logcat.
Edit: fixed by installing slimkat and flashing E988 modem thrice!
I too am having this issue. Everything I install is in reboot loop.
Fixed
Fixed.. See op for details.
Hey bro, can you provide the correct verion of e988 modem?
i need the modem but unfortunately i can't find this on the internet
Hello all,
I just recently noticed the RC3 for CyanogenMod, and tried to flash it, I failed with the status code 7, and disregarded it, and went back to my old CyanFox ROM. Weirdly, i started to not be able to connect to AT&T and get no service for minutes at a time, about every 10 minutes. I flashed LiquidSmooth, same problem, flashed CarbonROM, same problem. i flashed the most recent modem baseband, but the problem persists. I cannot seem to find a solution to this, so is there anything that would hopefully help?
Status 7 can be due to using an outdated recovery to flash KK ROMs. I suggest updating your recovery, wiping, and re-flashing.
hi guys,
my problem is a little difficult to describe.
After flashing a custom ROM (RR, CM, Vanir, Slim, LiquidSmooth...) KitKat or Lollipop , everything seems to work normal, but after unlocking display the brightness is about 5-10%, It is very difficult to see something on the display. The only way is to reboot into recovery and restore a nandroid.
This issue appears with installed mods just like xposed modules and other stuff, BUT it also appears without them (completely fresh install - ROM and GAPPS).
Curiously no problem with stock ROMs like KitSlim, Dstriker, PrivacyGuard and RockZ1K.
This is very ANNOYING!
Anybody the same issue or an idea how to solve it???
Thx for your help.
Hi
I am trying install AOSP roms for my s3 boost phone. The install seems to go just fine. However when The phone boots It just stays at The splash screen of the rom. I am also trying 5.0 and 5.1 variant kernals and TWRP. Nothing happens. I am trying different rom versions too and same results. Any ideas and suggestions?
Hi, Ive not long had my m9. When i got it it updated straight away and got the charging bug.
Since then I have s-off'd and tried various roms with not too much luck.
I now have a bug that occurs when i flash a new rom. This has happened when i flashed 3 different roms. Leedroid, Viper and android revolution. the rom flashes ok, then starts to boot, and builds art. It then finishes building art and starts to complete the boot process, and then it reboots and tries to build art again.
I flash back to my stock backup and everything is fine again. (apart from the damned charging bug)
Has anyone else experienced something similar?? am i missing something??
Go in twrp and make factory reset
just tried that, didnt work
Did you update your firmware? if you're still on 1.x firmware, those 2.x roms will reboot.
yeah. have tried matching roms to firmware and still get the same result. trying viper one currently. in a massive bootloop again. It boots enough to say "nfc service has stopped working" and thats what made me think it might be firmware, but it seems to make no difference.
cant even adb whilst its booting.. getting waiting for device.
What version of twrp are you using?
2.8.6.1
philicibine said:
2.8.6.1
Click to expand...
Click to collapse
Update to 2.8.7.0 and see if it continues.
I've solved this, and my charging issue. Finally!!
I decided to flash the earliest ruu I could find and then let it do all of the ota updates itself.
I then rerooted, flashed updated firmware and am now running leedroid.
Thanks for the help guys.