Hey there,
I use a LGG4 international version (H815). It is rooted and runs AICP Rom (MM 6.0.1). Xposed is not installed. It runs latest SUPERXE kernel.
While browsing the web it randomly got a blackscreen and an error message (some kind of log whats happening) showed up. It said that the kernel crashed. Rebooting did nothing, even while it booted the same error screen shows up, but this time with a green background. I booted to twrp and wiped everything, reinstalled the kernel and the system. And again, the same green error screen. I tried again and i could actually use the rom (Latest Genesys rom) for some minutes, then i got a random reboot. Even twrp hanged itself up and/or rebooted. Now I dont have any system installed and cant boot to twrp because the green error screen (see attached pic) shows up after the twrp boot screen. Is my phone ****ed?
Oh, and my external SD somehow died, cant recover it from windows or any other phone. So maybe the storage of the phone itself is damaged too?
Please help!
Thanks in advance
Aicp =/= stock rom.
Pfeffernuss said:
Aicp =/= stock rom.
Click to expand...
Click to collapse
I know, that's why I switched back to a stock based rom. And I tried too with completely LG stock rom, same issue.
Related
Hello,
I have a great problem with my Motorola. I installed battery icon mod without reading for which phone it's made and used it. Now I can't use my phone, because it's stopping at this logo before system. I had Cyanogenmod 7 (last nightly before RC), but when I destroyed it by this application first thing I did was wipe. After it nothing has changed, so I tried again and I flashed it with normal 2.2 Nordic but - as I "predicted" - nothing has changed again, but this time system was stopping at Android logo, not Cyanogenmod logo. I tried to flash again - nothing. The device can be charged (there appears this battery).
What should I do?
zielonek430 said:
Hello,
I have a great problem with my Motorola. I installed battery icon mod without reading for which phone it's made and used it. Now I can't use my phone, because it's stopping at this logo before system. I had Cyanogenmod 7 (last nightly before RC), but when I destroyed it by this application first thing I did was wipe. After it nothing has changed, so I tried again and I flashed it with normal 2.2 Nordic but - as I "predicted" - nothing has changed again, but this time system was stopping at Android logo, not Cyanogenmod logo. I tried to flash again - nothing. The device can be charged (there appears this battery).
What should I do?
Click to expand...
Click to collapse
Go into the stock recovery and wipe data. Then re-flash the sbf.
I did it already, but I forgot, that I can do wipe after flashing the device I thought about it and did it - everything is working. Sorry for useless thread.
Regards.
I wanted to ask at the same time. What if i can't enter stock recovery. My phone's rooted , slightly overclocked , and i can't download any apps , i can't do factory reset , and even when i'm trying to enter it , the android pic would appear with that "danger - triangle". What should be done?
sLvW said:
I wanted to ask at the same time. What if i can't enter stock recovery. My phone's rooted , slightly overclocked , and i can't download any apps , i can't do factory reset , and even when i'm trying to enter it , the android pic would appear with that "danger - triangle". What should be done?
Click to expand...
Click to collapse
The triangle IS the stock recovery! when you see the triangle with the little android dude, hit both up and down volume at the same time. This will bring up a menu that will allow you to do a factory wipe.
And another question. I've installed custom recovery , and it said that install was succsesful , but when I apply recovery boot , it just reboots my phone , or lefts screen blacked out, at which case i have to turn on my phone by removing and applying battery.
sLvW said:
And another question. I've installed custom recovery , and it said that install was succsesful , but when I apply recovery boot , it just reboots my phone , or lefts screen blacked out, at which case i have to turn on my phone by removing and applying battery.
Click to expand...
Click to collapse
Not sure I understand the questions, but I'll take a stab at it anyway:
Since we have a locked bl, the custom recovery does not overwrite the stock recovery.
As far as I know, the only way to get in to custom recovery, is to push the vol down when the blue light goes on during the boot cycle.
sLvW said:
And another question. I've installed custom recovery , and it said that install was succsesful , but when I apply recovery boot , it just reboots my phone , or lefts screen blacked out, at which case i have to turn on my phone by removing and applying battery.
Click to expand...
Click to collapse
If it was a first reboot after installing Custom Recovery than USB Debbug should be off...
Hi All,
Got a problem with my HOX. Rooted, and was running Franco kernel and PKMN ROM. Had a few issues so flashed back to stock kernel, wiped and reinstalled ROM.
Now I've got a problem; boots up, get a sense lock screen, then when I unlock I just get a white screen with HTC logo on that doesn't go away.
Help!
I've reflashed stock boot.img in fastboot, I've done a fastboot erase cache and still have same issue.
EDIT:
Well, got it to boot. Going thru setup now and it's INCREDIBLY SLOW. It's like it's underclocked to 100mhz or something. It's completely unusable - hitting "Next" in the Android setup menu takes 30 secs to process etc... This is kind of what was starting to happen before I wiped and reflashed - could it be I have corrupt storage or something?
landwomble said:
Hi All,
Got a problem with my HOX. Rooted, and was running Franco kernel and PKMN ROM. Had a few issues so flashed back to stock kernel, wiped and reinstalled ROM.
Now I've got a problem; boots up, get a sense lock screen, then when I unlock I just get a white screen with HTC logo on that doesn't go away.
Help!
I've reflashed stock boot.img in fastboot, I've done a fastboot erase cache and still have same issue.
EDIT:
Well, got it to boot. Going thru setup now and it's INCREDIBLY SLOW. It's like it's underclocked to 100mhz or something. It's completely unusable - hitting "Next" in the Android setup menu takes 30 secs to process etc... This is kind of what was starting to happen before I wiped and reflashed - could it be I have corrupt storage or something?
Click to expand...
Click to collapse
Did you remember to install kernel modules AFTER you installed your ROM? Roms come with their own kernels and the kernel modules are already installed under /system/lib. So unless you flash the kernel modules after the ROM, ROMs kernel modules get installed instead.
Yes, I did. Got it working now though - not sure what it was but mounted USB storage and got windows to scan the storage - then re-downloaded the ROM and flashed again. Weird....!
Greetings,
I am running Zoe Rom 6.0, I had problems with proximity sensor, the screen wouldnt light up after receiving calls, so I got into hidden menu and ran mt device test, after that phone turned its screen off and blue and red dot started to blink, I thought that is a device test procedure, but actually its just stuck like that.
I can enter TWRP recovery and download mode, but I am at work right now. I wiped clean several times and restored from backup but "Boot certification verify" error on every boot still persists..
I even flashed 7.1 ROM from SD card from TWRP and same outcome.
Why doesnt the error go away after clean flash? or clean restore?
Is there a way to fix this?
thanks for help in advance.
kaLuta said:
Greetings,
I am running Zoe Rom 6.0, I had problems with proximity sensor, the screen wouldnt light up after receiving calls, so I got into hidden menu and ran mt device test, after that phone turned its screen off and blue and red dot started to blink, I thought that is a device test procedure, but actually its just stuck like that.
I can enter TWRP recovery and download mode, but I am at work right now. I wiped clean several times and restored from backup but "Boot certification verify" error on every boot still persists..
I even flashed 7.1 ROM from SD card from TWRP and same outcome.
Why doesnt the error go away after clean flash? or clean restore?
Is there a way to fix this?
thanks for help in advance.
Click to expand...
Click to collapse
Hello,
Try installing Mr.Bump (click on it to download it) and you will be ok.
Greetings.
Sotiris02 said:
Hello,
Try installing Mr.Bump (click on it to download it) and you will be ok.
Greetings.
Click to expand...
Click to collapse
Too bad you havent replied before, 30 min before your post I flashed kdz with lg up tool. Started everything from zero, dont know if I lose recovery this way?
Big thanks anynways Cheers
Hello,
I have a LG G3 D855 with unlocked bootloader and TWRP 3.0.2-0 and it had a relatively recent build of the official LineageOS ROM.
Everything was running fine, until suddenly, during a phone call, it shut down, and since then,each time I try to turn on the device, the LG logo appears for 20 seconds, disappears for 2 seconds, and then appears again, over and over again. I can still access the recovery thou.
So I have tried wiping everything, including system, data, and caches, repairing file systems, reinstalling the newest version of lineageOS, (my SD card slot doesn't work so i had to push the ROM file to the data partition using adb and installing it from there). I also tried using a different battery, and the same problem persists.
I am kinda hopeless now so I would appreciate any help I can get.
Many thanks.
I have the exact same problem. It started when I upgraded to latest TWRP. Flashing back to the normal TWRP didn't solve the problem and the boot looping is persistent now and TWRP is inaccessible.
I flashed to stock rom using LG flash tool 2014 and no matter what I try it still loops indefinitely with the new OS installed.
I was on AEX and tried a new roms (Pixys, Evolution, Pixel Experience etc) and none of them booted the android.
Tried to restore AEX and even that is not booting. Phone keeps rebooting in loop without booting to any os including the restored backup.
Evolution and pixel after a clean installation says "no os".
Phone stays in start mode and does not move beyond this point.
Phone boots to twrp recovery.
Any idea what is wrong? Have corrupted the phone that it can't be used?
Is there a way out?
Quick solution would be highly appreciated.
Thanks
Anyone has a solution/suggestion for this?Deperate now since there is no alternate phone.
Thanks again
The phone boots recovery and adb commands work whereas fastboot commands don't work. I am able to flash vendor2factory and rom successfully with no error but the phone still not boot android but vibrates and goes back start screen and if i don't press any keys it restarts again after showing the ZUK logo.
I hope i have been able to explain the situation. I am still not able to boot the android despite trying more than one rom.
Anyone has any clues? Thanks
ramadurair said:
I was on AEX and tried a new roms (Pixys, Evolution, Pixel Experience etc) and none of them booted the android.
Tried to restore AEX and even that is not booting. Phone keeps rebooting in loop without booting to any os including the restored backup.
Evolution and pixel after a clean installation says "no os".
Phone stays in start mode and does not move beyond this point.
Phone boots to twrp recovery.
Any idea what is wrong? Have corrupted the phone that it can't be used?
Is there a way out?
Quick solution would be highly appreciated.
Thanks
Click to expand...
Click to collapse
I am having the same problem. I was in pixel experience and i flashed latest pixel experiences august security patch, it showed no os but it booted. But there were several bugs in the rom, i thought it was roms problem and then i tried to flash evolution, it again showed no os after flashing and then i got stuck at evolution x boot logo. So, i tried to qfil zui but to no avail, the flashing process won't even start the qpst tool just freezes after pressing the download button. Then in the twrp i noticed that battery percentage is different at different times sometimes it shows correct value but somes it won't so i thought that the problem might be from twrp and then i flashed new twrp but again same problem. Then i flashed arrow os 10.0 without gapps, it booted successfully then i flashed gapps. After sometime i tried to flash evolution x but got stuck at boot logo again. Finally i flashed arrows os again it booted successfully (i flashed rom and gapps separetly)
So, FINALLY THE TEMPORARY SOLUTION IS TO FLASH ARROW OS IT WILL BOOT SUCCESSFULLY BUT THEN AGAIN OTHER ROMS WON'T BOOT. IF I FIND ANY SOLUTION I WILL POST HERE
muralee krishna said:
I am having the same problem. I was in pixel experience and i flashed latest pixel experiences august security patch, it showed no os but it booted. But there were several bugs in the rom, i thought it was roms problem and then i tried to flash evolution, it again showed no os after flashing and then i got stuck at evolution x boot logo. So, i tried to qfil zui but to no avail, the flashing process won't even start the qpst tool just freezes after pressing the download button. Then in the twrp i noticed that battery percentage is different at different times sometimes it shows correct value but somes it won't so i thought that the problem might be from twrp and then i flashed new twrp but again same problem. Then i flashed arrow os 10.0 without gapps, it booted successfully then i flashed gapps. After sometime i tried to flash evolution x but got stuck at boot logo again. Finally i flashed arrows os again it booted successfully (i flashed rom and gapps separetly)
So, FINALLY THE TEMPORARY SOLUTION IS TO FLASH ARROW OS IT WILL BOOT SUCCESSFULLY BUT THEN AGAIN OTHER ROMS WON'T BOOT. IF I FIND ANY SOLUTION I WILL POST HERE
Click to expand...
Click to collapse
Now the phone is not even booting into recovery after i did a qfil install on zui rom. Looping into start screen only.
ramadurair said:
Now the phone is not even booting into recovery after i did a qfil install on zui rom. Looping into start screen only.
Click to expand...
Click to collapse
When you qfil, the recovery will be lost i think. But since you cannot enable usb debugging i think you wont be able to flash twrp.
---------- Post added at 07:26 AM ---------- Previous post was at 07:19 AM ----------
ramadurair said:
Now the phone is not even booting into recovery after i did a qfil install on zui rom. Looping into start screen only.
Click to expand...
Click to collapse
I think the problem is our phone is not able to boot big rom i.e. roms of size close to 1gb or more than 1gb since arrow os without gapps is only 600mb my phone is able to boot. If you are able to find the solution or get your phone repaired at any cell repair centre please let me know
bro is your phone working now