As the title says, I flash an image, don't even get to boot screen, just goes black after bootloader warning then reboots, occuring on havok 2 , and a few more (can't remember the ones I tested) anyone else have this issue?
Came from a fresh reinstall of B368, to get rid of custom kernel, so I can't see any issues there.
Related
Hi folks,
I'd appreciate some assistance in identifying the problem with my sm-p605. The color balance (RGB) on it went all bonkers. Red was alright, but the green and blue were almost completely faded. When I booted into download mode the colors were right, so I figured it's gotta be a software problem. I tried re-installing the firmware, first through Kies, but it got disconnected in the process, so I found stock firmware on sammobile and flashed it with Odin with a PASS. After that, the device would get stuck in a boot loop with "recovery booting....." written in the top left corner whether I tried to boot it normally or in recovery mode. But the download mode still worked so I tried flashing a custom recovery. I don't know if a device needs to be priorly rooted for that, but I flashed CF Auto Root and TWRP both with a PASS. After that, the device still wouldn't boot into recovery mode. It would say "recovery is not seandroid enforced". I tried several supposedly compatible versions of the recovery with the same result. But now it does boot normally into the OS except none of the things I flashed stuck. It's still the same non altered system it was before I did anything with it, even though I re-installed stock firmware twice now, second time even with Kies. So what's going on?
I took a screenshot of the app drawer after all this, and the colors are alright when viewed on a computer screen, so it might be a hardware issue after all, although I don't have a definite conclusion since capturing and displaying aren't the same part of the OS. There are other issues with it being non responsive when I'm trying to wake it up. I still want a fresh ROM so I can know for sure and I'm not able to install one, be it custom or stock. Any ideas?
I'll try to be clearer. Current ROM I have is stock 4.4.2, but it's barely usable, so I wan't a fresh one. I cannot get into recovery mode. If I flash stock firmware, I cannot boot into either the OS or recovery. If I flash custom recovery on top of that I still can't boot into it, but I can boot into the OS, which reverts itself like I never flashed fresh stock. So I'm stuck with what seems to be a corrupt OS with no way of installing a new one. Is there something I can try?
If you can flash a custom recovery. Boot into it and try factory reset. Either that or try a custom ROM if any are available (font have tablet)
Sent from my LG-D850 using XDA Free mobile app
Factory reset was the first thing I tried, I wish it had been that simple. I can flash a custom recovery, but I can't boot into it. The only thing it acomplishes is breaking the bootloop from stock recovery, so I can boot back into the OS, which stays the same no matter if I flashed new stock (it boots up already user configured). To install custom ROM I need custom recovery, unless there are some methods of installing that don't require flashing from storage.
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!
Hello,
I am quite new to the community, did some flashing some time earlier on Xperia SP successfully but now I am struggling with Xperia Z1c (Amami) with new Pie releases.
I have been trying to flash my Z1C to Android 9, and all I can see is as those roms are working fine, but whatever I do, I end up with unusable phone.
When I tried clean flash (wipe Cache/Dalvik/System/data) and flash even the rom only (no gapps or any other module) I end up with a black screen after the splash screen is gone. When I flash also Gapps, I get the screen where I can pick the language and afterwards it says I shoudl wait a few moments and it literary goes forever, with 1 change that after 1-2 mins screen goes dark and from time to time it lights up with lockscreen or the screen to unlock SIM, but the touchscreen does not respond and also HW buttons are not working, shutting it down via vol up plus power.
I also tried to go dirty and use older oreo builds (Recovery Remix and AICP Roms) to go to Pie successors, but then I end up in a similar loop, where it says Android system is starting (this is when the touchscreen works) and then the screen goes dark and once it lights up, the touchscreen is not responding like in case of clean flash.
I am using TWRP 3.2.3 recovery plus AICP and RR roms. in both cases 8.1 roms work like a charm, but I am missing the security patches.
Is there anybody who could suggest if I am doing anything wrong, or just its my phone?
EDIT: happens the same on Lineage OS as well... quite desperate as I am not able to gather any info what could be going wrong
Thank you in advance.
https://forum.xda-developers.com/so...om-lineage-os-16-0-xperia-z1-compact-t3886233
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
So, this is more for interest than anything else, but here's the scenario.
A friends 5T did a sudden shutdown. He picked up the phone, unlocked the screen and opened WhatsApp. An error message flashed on the screen - too fast to read - and the phone shut down immediately. He tried to restart, but it was stuck at the boot logo (circle with rotating dots).
We had a go at trying to get it back up again and did the following. I should note that both recovery and fastboot were available, however the bootloader was locked.
1) Booted into recover and sideloaded the latest OnePlus ROM - Stuck at boot logo
2) Got hold of unbrick tool and flashed with latest version (seems to be Android 8.1) - Stuck at boot logo
We were about to give up assuming a hardware issue when on a whim I tried the old unbrick for Android 7. Amazingly the phone booted. I quickly enabled bootloader unlock and unlocked the bootloader. We then flashed TWRP and tried to flash a custom ROM (Bliss in this case) - followed all the instructions to the T and got stuck at the (Bliss) boot logo (very cool boot logo by the way).
We then flashed a rollback version of Android 7 designed for folks coming back from one of the early beta 8 versions. This booted again, although it replaced TWRP as expected. We then sideloaded the latest version of 7 we could find (seems to be 7.11).
So here's the question. The only thing not working on the phone is the Wi-Fi. It does not switch on and shows a MAC address of 02:00:00:00:00:00 which indicates an issue. So I'm assuming something to do with the Wi-Fi has died on the mainboard. However, Bluetooth still works, SIM cards still work. I can use the phone normally with a mobile data.
So, what would stop anything above version 7.11 from booting if just the Wi-Fi is broken? Is there some link to this that was added in Android 8. It would great to update to 8 or 9 and still be able to use the phone, as everything else seems to work.
P.S. I have noticed that the camera takes about 10 seconds for the image to appear after the app opens, then works fine after that. Related maybe?
Anyway, was just wondering if anyone knows the inner workings and can shed some light on this one.