Hi guys
I have the chinese version with global rom.
Successfully installed TWRP and crDroid 10.0 rom but the google first time setup kept freezing (everything else worked perfect) so I decided to reflash the rom.
When I reflashed the rom it keeps getting stuck on the crDroid boot screen, have left it overnight and same.
Tried reflashing vbmeta, firmware and then crDroid with various wipes but same result.
I would appreciate any advice.
Mubs
Related
I was having boot loop while installing cm 12.1 i could boot if i unplug the battery and leave te phone for half an hour. When booted the phone has no problems. But the problem is while booting. It gave me constant bootloops. So i decided to do a complete factory rom change. So i flashed fastboot rom vi mi flash tool. Still the problem persists te phone is looping with a blue flash at the top.
A bit too late, sorry, but I think I have had some minor issues after flashing a fastboot rom few times.. I think it can be solved by entering MiRecovery, cleaning cache and then rebooting from recovery to system. If the system is not booting up in 5 minutes, it's not fixed. On the other side, maybe you haven't done it right or something is wrong with your file. I recommend doing it again with v45 Miui5 fastboot Rom. That one always works for me.
Anyone to help ??
Only way to make it booting is installing rr rom. With beast v5 kernel. That too with multiple reboots while android upgrading progress
I tried miui5 and i have twrp. I think this is happening by improper kernel configuration.
As i told earlier i can use phone awesomely by installing RR rom with beast v5 kernel.
Hello so I flashed cm13 way back in January. Recently the last few nightlies have really messed my phone up. Randomly crashing and got worse before it now bootloops for no reason. I booted up in twrp and read to wipe everything and flash latest nightly again. Did that except now twrp starts the flash before it boots onto the LG screen. It stays like that and I have to remove the battery. Basically it starts to flash before stopping the flash and booting the phone after a few seconds. Phone will only boot into twrp but same thing again. I feel like I have wiped the system so surely flashing the nightly will work. At the moment I have no phone and really not happy. Can someone help? Bit of a noob to this.
Best solution for you is to flash a stock rom using LG Flashtool. You can never go wrong, after that you can root and flash any rom of your choice. Avoid flashing cm nightly, try the stable versions.
Hey there,
I recently tried to upgrade to Nougat 7.1 by flashing Lineage 14.1 (latest Nightly) or Resurrection Remix 5.8.0 / 5.9.2 via TWRP 3.1.0-2. But somehow I can't get the system to work.
At first I went from Fulmics 6.9 to Lineage. TWRP -> Factory Reset -> Flash ROM -> Flash GAPPS 7.1 Pico -> [1st attempt Reset Cache + Dalvik] / [2nd attempt: Factory Reset] -> Reboot. Same procedure for RR 5.8.
After flashing the boot animation appears for a while and then, finally, the screen turns black, then reboot. When the screen is black I can still push the power button and hear the wakeon sound. But the screen is still empty. At some point I managed to get to the first step of system configuration (language selection) just by waiting one or two minutes. But on the next step the screen tuns black again and eventually freezes. Sometimes I can even see the status bar and change the volume bars for example, but the installation process somehow cannot initialize properly. Most of the time the system just turns black, freezes and then reboots sooner or later. I tried different builds of RR (5.8.0 of 2016 and 2017 as well as the newer 5.8.2) and Lineage (13.0 / 14.1) but the issue is always the same.
On my first attemps - coming from Fumlics 6.9 - I even had problems with the modem. But after switching between 30B and 21C flashing ROMs (7.1 in particular) went mostly fine.
In the meantime I have even performed a full reset via LGUP / LG Flash Tool 2014 to D85521C_00_1204.kdz, Android 5.0 LP with Baseband 13.2-00002 (modem 21c). After rooting with Kingroot, applying TWRP with AutoRec and upgrading to the latest version (3.1.0-2) I tried the whole thing again.
Flashing Nougat RR / Lineage, Gapps, then Factory Reset and Reboot. The issue is still the same... blackscreen, freeze, reboot. Also flashing MR_Bump.zip after the Nougat / Gapps makes no difference. When applying the .zip via TWRP, the system suddenly shuts down and reboots, then the same Nougat bootloop as mentioned before.
Interestingly it isn't even possible to flash back to Fulmics 6.6 after trying a 7.1 Nougat version. When flashing the system just shuts down, then reboots. The ROM won't install. Other MM ROMs have problems after trying to flash Nougat, as well. For most of them I get the same bootloop / freeze phenomenon.
So the only chance is to completely reset back to LP 5.0 via LGUP / Flash Tool 2014 again...
I am not really sure what is going wrong with the system. But generally speaking LP and upgrading to MM and its variants appears to work fine.
Only trying to flash Nougat leads to perpetual bootloops with any ROMs.
Is there any chance to make Nougat run on my D855?
Anything else I could try to fix the issues mentioned above?
Would be grateful for any help!
Edit:
After installing another 6.0 Marshmallow yesterday I oncemore tried flashing two other Nougat ROMs. The first one was AICP, the second crDroid. When flashing in TWRP I noticed that there was a basband incompatibility again. The ROMs required the 21c, which was already installed (by the lastest MM 6.0) but still marked as unsupported. After that I tried flashing Step-hans 21c in the first place and finally got the two ROMs to install. However, after the unconditional flashing procedure I always got two lines of an "Unknown Command [log]" error...
AICP just gave me the black screen after the boot animation again, but suprisingly crDoid booted without any issue. At least I could make it run normally for one or two minutes. Entering the menus, pushing buttons, opening apps just worked fine for that short period. And then the screen finally faded to black again. I could still use the power button and see the display powering on and off. But the screen itself was still black. Maybe my device has problems with running Nougats system UI...?
Any idea? :'(
Did you wipe the system partition before flashing?
Thanks for the response.
Yes, I did
One month has passed and the issue unfortunately still persists.
I have tried to flash an older Lineage version (v13.0 with MM) the other day and realized that even that one had troubles with my phone.
The UI was very slow and finally crashed to a black screen. In some cases only (pices of) the top bar were visible after the UI crashed. So basically the same as with the newer Nougat builds. I also noticed that at some point the screen toggled between full brightness and a yellow mode with lower brightness (reading mode?).
Could those issues be realted to the kernel?
In some rare cases I can get the newer builds to run for maybe 3 or 4 minutes until the UI finally crashes / the screen turns black. I can then push the power button and hear the wake up effect, but the screen remains black. The nougat builds were also running very slow in those few minutes whilst maxing out the temperature of the cpu.
Any further ideas?
Would be glad for any advice!
Edit:
Stock LP and MM with 21C and 30B still work perfectly, and even very smooth.
But as soon as I try to upgrade to another MM such as Mokee or Lineage 13 or the newer Nougat builds, the screen turns black when setting up the device.
It looks like only Stock-based ROMs (Nimax MM or Fulmics MM) appear to work at the moment!
This a bit of a long short story, so please bear with me for a while.
I first unblocked my Lenovo K5 Vibe Plus a6020a46 (India) in 2017 and using TWRP I had flashed the AEX Oreo v5.7 ROM. It was a great change and everything else was working fine for a long time.
Fast forward to 2020, I felt the phone was slowing down so I clean flashed AEX Pie v6.7 using TWRP, the ROM worked slick but after some time weird problems started to rise. Here's the chronology of what happened:
1. While using some apps the phone used to freeze, then shutdown. A restart would solve the problem for a while. But the lag used to remain.
2. The same problem repeated after a while but this time the phone went into bootloop.
3. I wiped cache, tried other solutions but nothing worked out so I reflashed the same ROM after a clean wipe. Phone worked fine for a week but then slowed down and finally crashed (This happened 2 times.)
4. After a week it was different, this time the boot animation would get stuck, then the phone would crash. So I reflashed again but when I booted up the phone there was no SIM service, no iMEi, No Wifi, No IP, Bluetooth.
5. I thought this AEX Pie ROM to be a problem so I flashed Arrow OS, Paranoid OS, AEX Oreo version, AEX 10 version but the problem remained: The phone would boot, boot animation stuck, and the phone would crash. This loop is where I am now.
I followed THIS GUIDE and tried reverting back to Official Stock ROM using QFIL. The flash was successful but the phone wouldn't bootup and went into a restart loop.
Here are some more important details:
1. The recovery mode is working fine. I can flash and wipe but I sometimes get the error of "Unable to mount" on Data, System and Cache partition which is solved with a format.
2. I can also get into Fastboot mode, EDL mode for QFIL flash.
3. I can also view all files and folders from TWRP Filemanager.
TLDR; Phone keeps crashing on boot, reverting to stock ROM also leads to restart loop, the phone shows no SIM, Wifi, iMEi, IP, etc. Tried wipe, clean flash, format which is successful but the problem remains. HELP!
"4. After a week it was different, this time the boot animation would get stuck, then the phone would crash. So I reflashed again but when I booted up the phone there was no SIM service, no iMEi, No Wifi, No IP, Bluetooth."
This is caused by bad ROM flashing ( when your flash wasn't entirely successful). You can fix this by reflashing. This could also happen if you downgraded, so go back to the version uou were on and see if this did it. You can fix IMEI with root if you want, I saw a thread for another phone: https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147 see if this could help.
"Animation Stuck"
This could be a problem with the ROM and data/cache, try factory resetting. Otherwise, it is also a problem with the ROM
In any case, I would redownload and reflash Stock ROM again and see if it still happens.
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