I installed a ROM the other day and when it booted backup it now shows a screen that says Custom with a lock underneath it. How do I get rid of this screen as it seems to make my device boot up slower. I had this happen to my Galaxy S3 also and I fixed it by returning everything to stock but I really don't want to do that. Any suggestions?
bvm1228 said:
I installed a ROM the other day and when it booted backup it now shows a screen that says Custom with a lock underneath it. How do I get rid of this screen as it seems to make my device boot up slower. I had this happen to my Galaxy S3 also and I fixed it by returning everything to stock but I really don't want to do that. Any suggestions?
Click to expand...
Click to collapse
There is a module for xposed framwork called wanam xposed that module has option in the security hacks section to fake system status to offical which will return the original galaxy s4 boot screen after a reboot or two. Its a quick fix without having to return everything to stock.
Ok thanks. I will try it out
Does Xposed work on Cyanogenmod based builds?
Hello, I have been having issues with my LG G2 (VS980) rebooting randomly after the screen shuts off for a lock. It sometimes does it when I let the screen turn off from inactivity, or when I turn the screen of with the power button, only to be unable to turn it back on. It happens randomly, and with no way for me to replicate it. It has happened on 4 different ROMS:
CyanogenMod 10.2 (cm-10.2.0-vs980),
PAC-MAN (pac_vs980_4.3.Build-1_20131128-135105),
Carbon (CARBON-JB-UNOFFICIAL-20131024-1220-vs980), and
AOKP (aokp_vs980_jb-mr2_unofficial_2013-12-01)
I have also tried Custom G2 Kernel (vs980-custom-05-cm), as well as the stock kernel with no success.
I've wiped Dalvik-Cache and Cache multiple times, as well as full wipes when flashing another rom, and the only time that I have had no problems was when I was running the stock ROM.
Here are a few logcat dumps of what may of happened when it crashed: (just add a 'h' to beginning, cannot post links due to being a new user)
ttp://pastebin.com/5WHJAgyK
ttp://pastebin.com/pSfZpxmZ
ttp://pastebin.com/AudKWyWe
All of the crashes happen around line 3800.
Any help would be appreciated!
EDIT: I have also tried using no lockscreen and using one, and I have no widgets at all on the lockscreen or the homescreen.
I had the same problem with my Verizon G2... every single ROM was way too unstable and I couldn't get widgets to work on half of them.. plus I was having messages popping up saying that I wasn't rooted when trying to delete apps..... so I say forget the ROMs.. stock with debloading Lol..
Sent from my VS980 4G using Tapatalk
So I just updated Magisk from v11 to v12 and my phone is totally douched up. After rebooting there's an "Unable to use fingerprints" message at the bottom of the screen, the touch screen is janky and my unlock pattern no longer works. The screen goes to sleep randomly too and then comes on without being touched. On the off occasson that the unlock pattern DOES work, the screen loads with no icons, just the page dots and status bar with my wallpaper and nav buttons. Uninstalled Magisk and got the same. Rebooted after uninstall, same thing. I guess I'll be reflashing the ROM, but this is a huge pain in the ass.
Same happened to me on ls997 but i dirty flashed my rom. It fixed the issue without losing anything. Not sure witch carrier you have or witch rom.
Well VS995 and H918 seem safe to update magisk on. Ive seen multiple people have 0 issues with it. Maybe a bad download? Never had that happen while updating magisk :|
Sounds more like a system issue. Id try reflashing your rom and see if that works
Hello,
when having installed a custom Rom on Oneplus 5 and in the Initial setup-wizard I want to restroe a cloud-backup, the Screen just goes white.
No matter which gapps I use.
Any help?
Any help?
Not exactly help but that crap never really worked for me except back in Nexus 5x times.
But due to custom ROM it is possible that the corresponding service was disabled so you get a blank screen
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Hi:
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
I'm in the same situation. I think these screens are not 100% compatible so it seems a hardware issue.
Maybe using vendor partition but i'm so stucked as you.
My phone can't hotboot any official recovery although i can boot flashed recovery only if i boot slot a not slot b.
Stock roms boot always using slot a but tried Lineage (thats uses slot b) and got always black screen.
I'll keep reading and trying to solve it.
Regards.
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
Have you made any progress?
gsausalito said:
Have you made any progress?
Click to expand...
Click to collapse
Thanks for your interest but I've made no progress and actually given up on it. I'm sure the issue could be resolved by buying a new, more compatible screen but I'm not going to put any more money into the phone.
As far as the software solution goes, I've tried almost every combination of ROM + Kernel i can think of but the only thing that works is the stock ROM.
I'm going to close this thread as I don't think it's much use to anyone.
Regards
Sorry for posting here, but i am in the same and i noticed that flashing canting 4.9 kernel gives display for like 8 seconds after screen turns off. May it be a kernel config issue? if anyone in this forum could answer this i could try and change it. Also flashing stock kernel on custom rom solves the problem but makes other thing fail
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Hello Mi A1 friends.
So yesterday I decided to change my crack LCD screen and to my surprise the phone boots into Xiaomi Logo and then after that its just a black screen. Message and other notifcation sounds still come in which means that the phone mange to boot into home screen, just with nothing to display. At the time of changing screen, I am on stock kernel and Pixel Experience 10.
Gonna flash back to stock pie(9) rom and see how it goes from there.
Deezio said:
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Click to expand...
Click to collapse
Sry for reply to an old post, but how did you do it? How did you flash kernel when you can't enter twrp because of screen issues? I have exact the same problem, where stock rom works but everything else cause blank screen. Also can't boot to twrp - probably the same reason.