Database Info

Display broken after root

Hi all
I'm having a strange problem with the display after rooting my Galaxy S7. The screen has stripes, is flickering and having weird colors, see image below. The touch functionality is still working.
As it was happening just after the rooting (using CF-Auto-Root), I'm still having the hope that it is a software issue and can be fixed somehow.
What I did:
- the first thing on the brand new device (unknown firmware) was rooting the device using CF-Auto-Root. This was working well.
- I installed Titanium Backup to get rid of the bloatware. Possibly I've deleted too much, after the reboot the device was hanging on the boot logo (bootloop?)
- I've downloaded latest firmware (G930FXXU1APD1 [DBT]) and installed it via ODIN
- Device was again working and everything was looking fine
- I've tryed to root again using CF-Auto-Root with the same file I did it with the shipped firmware. After one of these restarts during root, the problem started.
Except the weird screen, everything looks good so far. I've also tried to flash G930FXXU1APD1 again, but no change. Even on boot logo, in recovery and download mode, the screen looks like that. possibly something with the display driver?
I hope there is another way to fix it than bringing it back to the shop and hope that they will not refuse the repair because of knox flag (the firmware is shown as official).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(I'm aware of the risks that rooting brings, but I have the hope that all modifications or problems can be reverted by flashing something fresh, as long as the recovery is accessible [which is]).
Any help is appreciated.

This looks bad. Hope you can fix it!

I seriously doubt that this was caused by rooting or flashing the firmware. You've got a faulty screen.

This has nothing to do with rooting.
This is clearly a Hardware defect. Root is only a Software modification.
Gesendet von meinem SM-G930F mit Tapatalk

Have seen many people with this faulty screen. This should be a hardware issue. Get it replaced
Sent from my Silver Titanium Galaxy S7 Edge

BigMani said:
Hi all
I'm having a strange problem with the display after rooting my Galaxy S7. The screen has stripes, is flickering and having weird colors, see image below. The touch functionality is still working.
As it was happening just after the rooting (using CF-Auto-Root), I'm still having the hope that it is a software issue and can be fixed somehow.
What I did:
- the first thing on the brand new device (unknown firmware) was rooting the device using CF-Auto-Root. This was working well.
- I installed Titanium Backup to get rid of the bloatware. Possibly I've deleted too much, after the reboot the device was hanging on the boot logo (bootloop?)
- I've downloaded latest firmware (G930FXXU1APD1 [DBT]) and installed it via ODIN
- Device was again working and everything was looking fine
- I've tryed to root again using CF-Auto-Root with the same file I did it with the shipped firmware. After one of these restarts during root, the problem started.
Except the weird screen, everything looks good so far. I've also tried to flash G930FXXU1APD1 again, but no change. Even on boot logo, in recovery and download mode, the screen looks like that. possibly something with the display driver?
I hope there is another way to fix it than bringing it back to the shop and hope that they will not refuse the repair because of knox flag (the firmware is shown as official).
(I'm aware of the risks that rooting brings, but I have the hope that all modifications or problems can be reverted by flashing something fresh, as long as the recovery is accessible [which is]).
Any help is appreciated.
Click to expand...
Click to collapse
I agree with what other said. This has nothing to do with rooting. Somehow the bad display showed off it's real colors coincidentally after you root. Only way is to approach Samsung ASAP for warraty repair. Not sure whether they will check the device is in 'modifed' state (rooted) or in 'official' state for any such serious hardware issues. But you gotta say a lie about when this issue popped up. That's it. If you're lucky you will get the LCD replaced.

Hi all
many thanks for all your feedback. under the condition that we believe it is a hardware issue, I can keep my decision about doing the rooting, on the other side I will never understand why it was happing exactly at that moment.
However it seems that I had extremly luck. Today I went to the shop where I've ordered it online and they informed be about the DOA (Dead-On-Arrival) warranty, which is only possible within 7 days after purchase - today was day 7
they did just replace the device with a brand new one, they even didn't had to send it to Samsung before giving me a replacement. I was walking out with a new device :angel: :angel:
To finish here, I tried now exactly the same process as on saturday: first flashed latest firmware G930FXXU1APD1 and then I applied CF-auto-root. You can't imagine how nervous I was during these few reboots and hoping that the same problem does not reappear again (I could not go a second time to the shop with the same issue...). but this time all went well. latest firmware, rooted and now also debloated a bit.
again thanks to all of you.

Please help me! Freshly softbricked SGS7, SM-G930W8, No OS Installed

I have tried goddamn near everything and lurked everywhere.
This is just me trying to fix a huge mistake. I got this phone yesterday, everything was fine. I just wanted to install a custom recovery so I could back up the phone.
I flashed TWRP with Odin, I may have done it wrong or something... But I'm pretty sure I followed some directions. Odin did it in a snap, my device rebooted into TWRP... but then, I just barely noticed the "No OS installed!" message.
I have attempted, in no particular order:
- Using Kies 3 to initialize my device. It will download to 100% and then stick on 0% going to install the OS. Tells me the device is not supported.
- I then tried SmartSwitch because someone told me that's what you need for Android 4.3+. Same exact thing.
- Tried flashing my stock firmware, both 6.0.1 that it came with and the 7.0 that was available before it was bricked, with Odin 13.2 (I also tried others)
What's interesting here is when I add in the AP, BL, CP and HOME_CSC and press start, I get Odin's log to fail just after cm.bin - every time.
Here is a screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
At that point, I am no longer able to re-attempt until I restart and re-enter DL mode, and a black-backgrounded red text appears on the Download Mode screen, that says:
SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1
My device is the Canadian version, in the XAC region.
I have downloaded and attempted flashing firmwares G930W8VLU2BQB6_G930W8OYA2BQB6_XAC and G930W8VLU1APG1_G930W8OYA1APG1_XAC.
Both give the exact same errors and so I don't think the firmwares I got are the issue. I just have no idea what it could be, since the only problem with my phone is there's no OS installed.
Actually, I do have a problem with TWRP, as well.
TWRP is unable to do much. It cannot mount /data (among others), and those folders are all still there as I can adb push files to the device, and I attempted pushing the actual firmware to the /data folder and I could see the progress by pressing Install in TWRP and then looking in the /data folder... but that was the only file that told me "No space left on device" once it 100% completed, when there's obviously ~30GB.
The first error TWRP gives is that it cannot find the crypto footer.
Am I screwed here? Is this a harder softbrick? What am I missing? Please reply quickly, working by tomorrow would be very ideal.
Thanks in advance!

The last time I tried to flash stock - I got errors in Odin. Disconnected phone, restarted download mode and tried again. Don't know why but it took four tries before flashing complete - good luck
Sent from my SM-G930W8 using Tapatalk

bill_in_mtl said:
The last time I tried to flash stock - I got errors in Odin. Disconnected phone, restarted download mode and tried again. Don't know why but it took four tries before flashing complete - good luck
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
I tried many more than four times. Should I be using CSC rather than HOME_CSC, just to wipe everything and maybe that'll work?
You say you got 'errors' in Odin, but it's always different for a different cause. You didn't get an error before cm.bin, did you?
EDIT: Attempting CSC rather than HOME_CSC for both v7 and v6 firmwares.
UPDATE: Ugh... I guess it's not the same every time. Using CSC with the Marshmallow md5s, I got Odin to err earlier this time, before even getting to cm.bin!:
UPDATE2: I have just tried flashing Nougat with Odin, using CSC instead of HOME_CSC, and IT'S WORKING??? WTF. Got past recovery, now going through system... Perhaps I posted too soon? Sorry for wasting anyone's time. I will update this thread if it doesn't work.
I'd say this thread isn't worth deletion because I think somebody could come by, take this information and help themselves with it.

I had similar issue - error would be different with every attempt until finally it just flashed and passed. Glad you got it working .
sent from SGH-1337M using Tapatalk

Yeah, that's the thing though... With this one, I got the same error no matter how many times I tried one specific way.
I suppose just never attempted the 7.0 firmware with CSC instead of HOME_CSC. Thanks anyway

"No SIM card - 31000" - Galaxy S5 G9000P

Recently I have flashed my S5-G9000P for the first time with the Resurrection OS RR-O-v6.0.0-20180405-klte-Official.
After working alright for the first day or so, texts would not send. Then, at the top of my screen it says "No SIM card - 31000". I don't really know much about modding phones, so here is what I tried so far:
- Resetting the phone
- Removing the SIM card then reinserting, then resetting the phone again
- Resetting my mobile data options
So far these above options haven't helped the problem. I have looked at similar threads to this and none seem to have the same problem based on their descriptions.
Thanks for your time.
Phone - G9000P Galaxy S5
Android Version - 8.1.0
Kernel version (if that's important) - 3.4.113-lineageos-g592be94 (gcc version 4.9.x 20150123 (prerelease) (GCC) ) [email protected] #1 Thu Apr 5 13:41:19 CEST 2018
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Mine did that out of nowhere also. Saying no sim card was inserted or some junk. I have never flashed custom kernels so maybe that is an issue. I tried reflashing my custom rom I was running at the time (the one in my sig at the moment) and nothing. I ended up reflashing the stock firmware in odin then booting straight to recovery and reinstalling my rom and that seemed to fix it. That happened twice and thats how I got it fixed.
I have since flashed the latest stock sprint firmware and then installed LineageOS 16 and it has not happened since but I have been having a ton of other issues with the phone, on both custom sprint roms, and LineageOS so pretty sure my phone is on its way out. Might have to do a motherboard replacement. Hope not though.
Good luck and report back.

Well I can State the Facts... has happened here tooooo..... on LineageOS 16 and 15.1. The only fix that I have done, which may help, is Rebooting the Phone.
Yep, tat was the only thing I actually have done, When and IF it happens.
Same thing though, "NO SIM Card" " Corrupt Sim Card" and I Tink there was another one too. All if which, (Knowing that it was running correctly, prior this) I just rebooted. maybe once, maybe like 3-4 times. before it actually goes away.
Now, knowing the phone was running correctly is the Key , I believe. IF your in the process of Flashing, yep, maybe restart that. However, if its running right an all, no reason to do any flashing. why--- Well, was built in the First run batch of them. the phone is rather good and all, cant even see me spending over a $1,000.00 for a new phone, that's Ficking Nutz !!! I am sure, they did built it to last a life time, but what is it, a cell phone built in 2012. Before my warranty was over, I rooted, and got rid of all thre Samsung crap. Ran smooth. Been Flashing ever since.....

E.4.113-LineageOS-g592be94 mobile data not working
Hippie459MN said:
Mine did that out of nowhere also. Saying no sim card was inserted or some junk. I have never flashed custom kernels so maybe that is an issue. I tried reflashing my custom rom I was running at the time (the one in my sig at the moment) and nothing. I ended up reflashing the stock firmware in odin then booting straight to recovery and reinstalling my rom and that seemed to fix it. That happened twice and thats how I got it fixed.
I have since flashed the latest stock sprint firmware and then installed LineageOS 16 and it has not happened since but I have been having a ton of other issues with the phone, on both custom sprint roms, and LineageOS so pretty sure my phone is on its way out. Might have to do a motherboard replacement. Hope not though.
Good luck and report back.
Click to expand...
Click to collapse
You have in your signature a new rom, does that rom is working ok? The only thing that is driving me nuts is that I can’t have my data usage, I installed RR-O-v6.0.0-20180405-klte-Official on my gsm900M what do you suggest!?
Edited, i found it! just needed to edit the APN settings! i google them for my case that is Mexico, and now i have mobile data!!

Im still running lineageOS. I just havent updated my signature yet. I am going to be getting a new phone in the next week or so though. Pretty sure the motherboard (Internal storage) is taking a dump on me. Phone will work great sometimes for 2 weeks then apps start crashing like mad and only way to fix is to uninstall and reinstall and only way to fix it is to do a full wipe and reinstall the rom. Sometimes it will even start messing up within an hour or two. Things like google play services, the stock dialer, and bluetooth will randomly crash. I have tried just about everything. Different roms, going to stock software, nothing works. And when it tries to do do a backup in TWRP, it always fails in the data partition and always at different points saying it cant read the data partition or some junk. I forgot but I am giving up on it. I have another S5 but wont have it for another week or two.

Question Hard brick

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you ever get this glitchy screen there's a high chance that your device is going to get hard bricked soon. The glitches usually get accompanied by system reboots or reboots to fastboot.
We still haven't determined what exactly leads to a brick. All reports so far have been from users on stock MIUI 12.5.x or MIUI 12.5.x based custom ROMs, either with locked or unlocked bootloader. But yesterday we had the first case of a brick on AOSP too. It's probably MIUI 12.5.x firmware's fault so we suggest you to use MIUI 12.0.x if you want to use MIUI and use only 12.0.x firmware if you're an AOSP/CAF custom ROM user.
Also, make sure to take a backup of your internal storage and your apps as soon as possible if you ever encounter these graphical glitches. You'd better take backups regularly either way just to be safe.
In case you get a hard brick, you have to visit a service center to get your motherboard replaced. Do anyone faced this problem?

irmas5 said:
View attachment 5446589
If you ever get this glitchy screen there's a high chance that your device is going to get hard bricked soon. The glitches usually get accompanied by system reboots or reboots to fastboot.
We still haven't determined what exactly leads to a brick. All reports so far have been from users on stock MIUI 12.5.x or MIUI 12.5.x based custom ROMs, either with locked or unlocked bootloader. But yesterday we had the first case of a brick on AOSP too. It's probably MIUI 12.5.x firmware's fault so we suggest you to use MIUI 12.0.x if you want to use MIUI and use only 12.0.x firmware if you're an AOSP/CAF custom ROM user.
Also, make sure to take a backup of your internal storage and your apps as soon as possible if you ever encounter these graphical glitches. You'd better take backups regularly either way just to be safe.
In case you get a hard brick, you have to visit a service center to get your motherboard replaced. Do anyone faced this problem?
Click to expand...
Click to collapse
That's not a hard brick ... you screwed up your GPU/Motherboard (overheating / fake fast charger, water ... etc)
Hard Brick = bootloader relocked with a modified partition / modified firmware = Black Screen ALWAYS
you better go to a service center ... before now !!!
don't waste you time with flashing ...

I've been following this on telegram & youtube, my personal opinion is it is a hardware issue, the frequency of it happening on 12.5.x is because most people have upgraded to 12.5.x, if everyone now downgrade to 12.0.x as a 'precaution', we'll probably see reports on 12.0.x, we'll know soon enough...

No. Mine fine now. Yesterday and today started some flickering, but uninstal magisk. Fully unrooted and disappeared flickering. Just curious.

gringo80 said:
That's not a hard brick ... you screwed up your GPU/Motherboard (overheating / fake fast charger, water ... etc)
Hard Brick = bootloader relocked with a modified partition / modified firmware = Black Screen ALWAYS
you better go to a service center ... before now !!!
don't waste you time with flashing ...
Click to expand...
Click to collapse
this has been happening on all units, randomly. Do you know of any way that it can be fixed without the service centre's help?

meechyy said:
this has been happening on all units, randomly. Do you know of any way that it can be fixed without the service centre's help?
Click to expand...
Click to collapse
this is hardware issue
bricking is related to software

Lu5ck said:
this is hardware issue
bricking is related to software
Click to expand...
Click to collapse
can anything be done?

meechyy said:
can anything be done?
Click to expand...
Click to collapse
No, you send to xiaomi to service to replace the hardware.
Software fix can't cross dimension to reality.

I would expect more attention after months, if this issue were as severe, as it seems. Perhaps these were indeed hardware related issues, that weren't related to the software in any way, at all.

Question Massive system storage use on Stock OnePlus 9 5G

Hey everyone. I've been looking through Forum posts everywhere and can't seem to see anything recent concerning this issue that actually solves it.
My system data is taking up an extremely abnormal amount of space. So much so that I have to routinely prune my already limited photo, video, and file storage or my device runs out of space to store temp and application files. Has anyone found a decent way to fix this outside of starting from scratch?
I have a stock OnePlus 9 5G running Android 12 (LE2115_11C.48), tho it had been an ongoing issue since before Android 12...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

It seems like a known issue that has no resolution but factory reset and switch to a non-OOS ROM.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
There is some suggestion that it's dump files being constantly created.

Hmmm... Do you know if root is possible without factory reset? I bet I could find the problem files pretty quick if I could get access to those files.

dallen.baldwin said:
Hmmm... Do you know if root is possible without factory reset? I bet I could find the problem files pretty quick if I could get access to those files.
Click to expand...
Click to collapse
Not that I'm aware of. Temp root exploits are closed pretty quickly once discovered and the act of unlocking the bootloader causing the phone to be wiped is a security mechanism since having an unlocked bootloader could potentially give way to an easier method of extracting your data off of the device.

until support arrives, there's no choice but to reset and reinstall OS.
the problem with the other option of using a custom OS is kinda scary.
because installing/using a custom OS is no longer as straight forward as previous like in oneplus 3t.

jmadiaga said:
until support arrives, there's no choice but to reset and reinstall OS.
the problem with the other option of using a custom OS is kinda scary.
because installing/using a custom OS is no longer as straight forward as previous like in oneplus 3t.
Click to expand...
Click to collapse
What's scary about it? It's really not that bad as long as you read the instructions. I have flashed this thing 3 or 4 times now and it's no worse than any other phone I have ever had.

That's good to know. I previously had a Xiaomi Mi Mix 3 (may it rest in peace) and ran several custom ROMs on it before its untimely demise. I imagine the process on this device is equally nerve wracking the first couple of times and totally normal afterwards.
Any suggestions while we're on the topic?

dallen.baldwin said:
That's good to know. I previously had a Xiaomi Mi Mix 3 (may it rest in peace) and ran several custom ROMs on it before its untimely demise. I imagine the process on this device is equally nerve wracking the first couple of times and totally normal afterwards.
Any suggestions while we're on the topic?
Click to expand...
Click to collapse
If you can type fastboot commands into command prompt, it's really not that difficult. I actually often found flashing with TWRP to be more irritating because of weird errors and sometimes it would refuse to factory reset and make a really big mess for me.
Now you just download the ROM and the recommended recovery, flash the recovery, boot to recovery, flash ROM, and you're done. Obviously read each ROM's instructions though because some like StagOS require you to do other stuff (you have to flash a partition file with that one).
I personally recommend StagOS. The only thing I found wrong with it was that it didn't support Verizon (no signal with a Verizon network SIM) but the dev is working on that and the fingerprint sensor icon wasn't lined up properly which apparently not everyone had that problem. I have tried a few others and had different issues with each of them. Derpfest is pretty good too but sometimes my apps act like I have never run them and I had a weird crash when swiping down on the status bar earlier. I plan to go back to StagOS. In fact, I am going to just go ahead and do that right now.
If you want to save yourself some annoyance, if the phone doesn't have OOS 12 on it when you get it, don't flash it to OOS 12 or you'll have to downgrade it to make sure you have a firmware match.

Dang.. I thi k I already went to OOS 12 since I'm on Android 12

dallen.baldwin said:
Dang.. I thi k I already went to OOS 12 since I'm on Android 12
Click to expand...
Click to collapse
Yep, you definitely did. The easiest way to get back to being ready IMO is to run the global MSM tool to get back to OOS 11, then when that's done, unlock the bootloader (make sure you do it in this order, I had my phone refuse to boot twice when I unlocked the bootloader after installing 11.2.10.10), then when the phone has booted back up, install 11.2.10.10 OTA for global (it's in the pinned update post), then you're ready for custom ROMs.

EtherealRemnant said:
Yep, you definitely did. The easiest way to get back to being ready IMO is to run the global MSM tool to get back to OOS 11, then when that's done, unlock the bootloader (make sure you do it in this order, I had my phone refuse to boot twice when I unlocked the bootloader after installing 11.2.10.10), then when the phone has booted back up, install 11.2.10.10 OTA for global (it's in the pinned update post), then you're ready for custom ROMs.
Click to expand...
Click to collapse
When you go back to os 11 you will experience duplicate media storage issue.. I just flashed os13 stable currently shows 7GB of data on ' others ' , don't know if will continue grow..keep my eye peeled..