Hello, For the past two days i've been trying to get a custom ROM to work on my t999. I've tried 5 different ROMs on my t999 and none seem to work with 3 not booting and the other 2 that have major issues that they shouldn't. Before I get int the problems here's the ROM's i've tried.
-Cm 13. based on 6.0.1. - Boots with a broken setup screen that doesn't respond to touch
-Slim 6 based on 6.0.1. - Boots to black screen, only image that is shown is the power off button when you hold the power button
-LN 14.1- Based on 7.1.2. - Stuck on starting screen then follows with system process isn't responding
-Cm 14.1 based on 7.1.2. - Stuck on starting screen then follows with system process isn't responding
-Meeko based on android 7.1. - Stuck on starting screen then follows with system process isn't responding
I've installed 3 different TWRP versions from newest to old and none of them will make any differences with the ROMs i'm trying to install.
They all successfully flash and do show booting screens, but most never get passed them and the only one with a successful boot was CM 13 with the broken setup screen. I've restored the phone to its stock OS and tried several times along with trying while rooted and while not rooted. The one thing I haven't tried was trying to install the ROM while the phone was on stock i always flash with some version of TWRP but I don't think that would make an issue.
If anyone has any suggestions please let me know i'm getting desperate lol.
Related
So here is the problem, I try and install a new ROM with TWRP and it goes through with no problems. Once I go to restart it, the problem begins. My Note keeps getting stuck when it gets to the updating andriod apps screen after the initial (first) reboot after install. I have tried this with two different roms and can not get it to work. An outlying problem that i also have is that when it is off for long periods of time when I turn it on it gets stuck in system boot mode (boot animation). I have no idea what is going on. Can someone please help.
Current Setup:
NOTE 2
TWRP
MACK Allstar 5.0 Rom
Only one .bak on the system update.
Everything else is APK based
The setup: Galaxy S3 (d2att SGH-I747) running Slim Kat 4.4.4. Bootloader is I747UCUFNJ1 and the recovery is TWRP v2.8.6.0. The phone already rooted with a custom ROM on it. At one point in the past, somebody had tried to install CyanogenMod, but I don't know what they did.
The issue: When I boot my phone, if flashes a "Samsung" logo briefly, then the SlimKat logo, then the SlimKat boot animation in that order. But, when I boot the phone into recovery, it flashes the "Samsung" logo, then a logo that says "Samsung Galaxy SIII" with the cyanogen guy logo below it, then the TWRP splash screen. I am not running Cyanogenmod and am wondering why the second logo appears and how to get rid of it. This has not affect on the performance of the phone, but is something I would like to figure out to better understand how the phone works. Before you tell me to Google this, I have spent countless hours researching this issue and have found only one thread on another forum that mentions this problem with no replies. I cannot find anything about boot logos for recovery, how they get there, how they are changed, where they reside. Keep in mind, I am NOT talking about the system logo or the system boot animation.
What I have tried: When I got the phone, it was on MJB bootloader and have have since upgraded it using Odin and instructions/files from enewman17 and postings on this site. I have flashed his stock rooted ROMS (both MJB and NJ1). I have installed several custom Roms (Cyanogen, SlimKat, Stock_rooted), several recoveries using both the app and Odin (CWM, TWRP, and philz_touch), and at least one Kernel (Majestic 1.0.9). This boot logo remains. The only success I had in getting it to disappear was by flashing progressively older TWRPs and it took back until 2.5.0.0 before it dissapeared. TWRP 2.5.0.0 doesn't even use a logo, so it was probably still there, just not used. The phone works great with everything I have done, it is just this logo that remains.
Any thoughts or suggestions?
Here is what I believe you are encountering. If I am not mistaken Slimroms uses pretty much the stock CM kernel but they have replaced the splash screen to be of Slimroms design. However when you boot into recovery I'm guessing there is a different splash screen that is accessed which is still what cyanogenmod put in the kernel.
Could be wrong but I believe that is the case.
Possibly, but I think I have ruled that scenario out. I have flashed a different kernel and a stock ROM but the CM recovery boot logo remains.
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
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.