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.

Xiaomi Redmi 4 (prada; Standard Edition) - All info in one thread

{
"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"
}
Redmi 4 is a mid-end device released by Xiaomi (along with 4A, 4 Prime) in November 2016. The device itself is very similar to Redmi 3S in every aspect, expect it has a few improvement to some components. (For example the Wi-Fi, where 5GHz connection is now possible)
Device specs: http://www.gsmarena.com/xiaomi_redmi_4-8419.php
Available official ROMs: http://en.miui.com/download-318.html
Rooting only possible via official unlock (There is no known method for unofficial unlock)
No official Global ROM was released yet.
Redmi 4 subthread in XDA: https://forum.xda-developers.com/t/xiaomi-redmi-4
TWRP for Redmi 4: https://forum.xda-developers.com/an...fficial-twrp-recovery-xiaomi-redmi-4-t3594052
If something is bothering you feel free to express your thoughts.

Any news for the global rom for Redmi 4 prada??

VE511 said:
Any news for the global rom for Redmi 4 prada??
Click to expand...
Click to collapse
Unfortunately no
There is a Global ROM available from the official MIUI site, but it has in-calling bugs, and is not released officially.

Redmi 4 just got it's very own subforum!!
https://forum.xda-developers.com/t/xiaomi-redmi-4

Can somebody please give his QCN file from Redmi 4? I need to fix my baseband and IMEI... Thank you.

Clean android....
Hello, i'm new user on this forums. I have very big problem with my device.
I got second model of Redmi 4, first one had malfunction of SIM module (after instaling CM 13), and device wasnt detecting SIM's at all (what more interesting SD cards was detected) on both slots. After service i got brand new Redmi 4, installed CyanogenMod 13 as only properly working OS* and starting to have the same issue.
*So now let me explain why i threat CM 13 as only working OS - it uses battery as it should. On every MIUI (which seems to not be official) including MIUI 9 my battery just drain. For example with 1-2 hours of daily usage on CM my battery can keep 7-14 days, which is perfect resoult, while on MIUI even unused device is keeping max 4 days, and battery usage says Android OS and android (process names) eat 40 % of battery (sometimes up to 56%). I'm installing OS by full wipe, so its not the case of files remaining from older OS.
NOW final question to all specialists here - from where can i get CELAN ANDROID MARSHMALOW or NOUGAT for my model (Redmi 4 prada)? Installation as i understand properly is the same as in case of ROM right (TWRP) or maybe flash?
Please answear, i'm looking over internet 2 months right now, and spending all my free time after job on unsuccessfull searching for help.

Hello,
After I flashed my phone to MIUI 9 (can't remember which one - so many I tried), I got the success message on MiFlashTool, but my phone didn't restart. It was dead.
I mananged to revive it but I had lost many sensors, like wi-fi, bluetooth, etc. I managed to fix those and then I was getting an error about IMEI (can't ID the device) or something like that. Basically my IMEI was gone. I found a fix for that. The phone can now detect the SIM card.
My issue is that it can't connect to the GSM network of my carrier.
I double checked the APN settings - they are good. When I dial *#*#4636#*#* I see the 'turn radio on' button but it doesn't do anything.
Switching back and forth between different versions of MIUI did not help. I tried flashing the NON HLOS bin file via command prompt, I got the okay message, but it didn't fix the problem. I tried flashing the 3 modem files via TWRP, again, it didn't fix my problem.
They talk about restoring EFS on a thread, but I don't know how to do that or if that will help. I don't have the back up files anyways for EFS.
Can anyone help?
Currently I am on CyanogenMod 13 (OS 6.0.1).
Thanks
Andrei

camilleisfunky said:
Hello,
After I flashed my phone to MIUI 9 (can't remember which one - so many I tried), I got the success message on MiFlashTool, but my phone didn't restart. It was dead.
I mananged to revive it but I had lost many sensors, like wi-fi, bluetooth, etc. I managed to fix those and then I was getting an error about IMEI (can't ID the device) or something like that. Basically my IMEI was gone. I found a fix for that. The phone can now detect the SIM card.
My issue is that it can't connect to the GSM network of my carrier.
I double checked the APN settings - they are good. When I dial *#*#4636#*#* I see the 'turn radio on' button but it doesn't do anything.
Switching back and forth between different versions of MIUI did not help. I tried flashing the NON HLOS bin file via command prompt, I got the okay message, but it didn't fix the problem. I tried flashing the 3 modem files via TWRP, again, it didn't fix my problem.
They talk about restoring EFS on a thread, but I don't know how to do that or if that will help. I don't have the back up files anyways for EFS.
Can anyone help?
Currently I am on CyanogenMod 13 (OS 6.0.1).
Thanks
Andrei
Click to expand...
Click to collapse
I'll transfer cash via paypal to whomever walks me through the process. Thanks

camilleisfunky said:
Hello,
After I flashed my phone to MIUI 9 (can't remember which one - so many I tried), I got the success message on MiFlashTool, but my phone didn't restart. It was dead.
I mananged to revive it but I had lost many sensors, like wi-fi, bluetooth, etc. I managed to fix those and then I was getting an error about IMEI (can't ID the device) or something like that. Basically my IMEI was gone. I found a fix for that. The phone can now detect the SIM card.
My issue is that it can't connect to the GSM network of my carrier.
I double checked the APN settings - they are good. When I dial *#*#4636#*#* I see the 'turn radio on' button but it doesn't do anything.
Switching back and forth between different versions of MIUI did not help. I tried flashing the NON HLOS bin file via command prompt, I got the okay message, but it didn't fix the problem. I tried flashing the 3 modem files via TWRP, again, it didn't fix my problem.
They talk about restoring EFS on a thread, but I don't know how to do that or if that will help. I don't have the back up files anyways for EFS.
Can anyone help?
Currently I am on CyanogenMod 13 (OS 6.0.1).
Thanks
Andrei
Click to expand...
Click to collapse
Wow, you really mess up bro...
Let's see... First I advise you to flash the official fastboot ROM from the official forum and see if boot normaly.
If not, you can try unbrick the phone by 'test points'.

Hey
Thanks. The phone boots normally, everything works except for the radio. All commands for the radio can't be changed. If I do *#*#4636 phone information, I see my SIM Card, it shows my carrier (Rogers). WHen I click the 3 little buttons to select the band it shows unknown and lists a few options, including the one I think it the one I need (GSM 850/1900 - i'm in Canada). When I select that band it shows unsuccessful....What can it be?

camilleisfunky said:
Hey
Thanks. The phone boots normally, everything works except for the radio. All commands for the radio can't be changed. If I do *#*#4636 phone information, I see my SIM Card, it shows my carrier (Rogers). WHen I click the 3 little buttons to select the band it shows unknown and lists a few options, including the one I think it the one I need (GSM 850/1900 - i'm in Canada). When I select that band it shows unsuccessful....What can it be?
Click to expand...
Click to collapse
I must admit that is out of my league.. Sorry
You saying the radio is turned off and can't receive calls? You don't have signal?
In the 'Phone Information', in the button of the page, there is a option that say 'Turn Radio On/OFF', try it.
But... You say you have some modem files, right? If is the same I used when I change to a custom ROM, maybe can help. Try flashing that files in TWRP.
---------- Post added at 01:18 AM ---------- Previous post was at 12:58 AM ----------
DracoXXI said:
I must admit that is out of my league.. Sorry
You saying the radio is turned off and can't receive calls? You don't have signal?
In the 'Phone Information', in the button of the page, there is a option that say 'Turn Radio On/OFF', try it.
But... You say you have some modem files, right? If is the same I used when I change to a custom ROM, maybe can help. Try flashing that files in TWRP.
Click to expand...
Click to collapse
Sorry, I remember now one thing...
Which fastboot ROM you use? China Stable or Dev?
Try use the Dev ROM and in Miflashtool, select 'Clean All' option.
Hope this work

DracoXXI said:
I must admit that is out of my league.. Sorry
You saying the radio is turned off and can't receive calls? You don't have signal?
In the 'Phone Information', in the button of the page, there is a option that say 'Turn Radio On/OFF', try it.
But... You say you have some modem files, right? If is the same I used when I change to a custom ROM, maybe can help. Try flashing that files in TWRP.
---------- Post added at 01:18 AM ---------- Previous post was at 12:58 AM ----------
Sorry, I remember now one thing...
Which fastboot ROM you use? China Stable or Dev?
Try use the Dev ROM and in Miflashtool, select 'Clean All' option.
Hope this work
Click to expand...
Click to collapse
Thanks. I tried all those things many times before. My radio functionality is faulty. I cannot enable the radio.

camilleisfunky said:
Thanks. I tried all those things many times before. My radio functionality is faulty. I cannot enable the radio.
Click to expand...
Click to collapse
Then only by test points, don't see any other options.. At least for now..

What is the benefit of using test points vs fastboot?
Thanks

camilleisfunky said:
What is the benefit of using test points vs fastboot?
Thanks
Click to expand...
Click to collapse
Well... The test points is more for when the phone is really mess up, phone don't boot, not enter the 'fastboot', etc... normally know as 'hard brick'. It's the "ultimate" recovery.
In the PM I send to you, there is a link to a post in the official forum explaining where, and 'how to' do.
But... If you are not comfortable doing that, then, don't do.
Anyway... I can't help you more, sorry
Try asking in the official forum for help. They are more active than here.

"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.

[ROM][11.0][OFFICIAL][OOSCAM][OnePlus 7 Pro][11.0_r20] Evolution X | Emerald

{
"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"
}
Evolution X 5.2 for the OnePlus 7 Pro [guacamole]
Code:
/*
* Your warranty is void. Or vaild, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modificiations, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
Living, Breaking, Keep Evolving.
Pixel UI, customization and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@peaktogoo (Now RealAkito)
Reach us on Twitter! @EvolutionXROM
What are our features?
- Just flash and check "The Evolver"
single tap gesture doesn't work, WFD doesn't work and No Verizon Network Support
DO NOT FLASH GAPPS, ALREADY INCLUDED
DO NOT FLASH GAPPS, ALREADY INCLUDED
First Time Install / Clean Flash
1. Have latest OOS 10.x flashed to both slots!!
2. Download the proper flashable ZIP for your device
3. Reboot to Recovery
4. Wipe Data/Cache/System
5. Format Data (Required)
6. Flash the ROM
7. Reboot to System
8. Reboot to Recovery (Optional)
9. Flash Magisk (Optional)
10. Reboot to System and #KeepEvolving
Update / Dirty Flash
1. Reboot to Recovery
2. Download the proper flashable ZIP for your device
3. Reboot to Recovery (Optional)
4. Flash Magisk (Optional)
5. Flash the ROM
6. Reboot to System and #KeepEvolving
Light Screenshots / Dark Screenshots / Download
Donate to me! / Official Chat / Device Support
​
Android OS version: 11.0_r20
Security patch level: December 2020
Build Author: Justin Crawford
Source Code: https://github.com/Evolution-X
Kernel Source Code: https://github.com/Justasic/kernel_oneplus_sm8150
ROM Developer: joeyhuab
Thanks: npv12, spookcity138, chandu dyavanapelli, madgeniusgamer

Reserved

Screenshots by Android 10 ????

I have Evolution X android 10. And it's amazing it has so many features and modification Love it. Does EvoX 11 have all of these features and even more? keep up the good job

Wait, this has OOS cam AND is Android 11? SICK! Does normal Magisk Beta work or do we need that modded Magisk that's been floating around?

@justasic What version of the camera program?

Just a heads up, not sure if my phone is just weird, but the first wipe instructions (step 4), resulted in my device only being able to boot to bootloader and resulting in " FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" if i try to flash or do anything on CMD/fastboot now. Not sure if it's bricked or if this will happen to you, and it's obviously not a ROM issue, but just mentioning it just incase anyone is following the exact steps.

Nice ROM,so smooth,,dualboot with MSM xtended rom,
Video with OOS Cam crash,,even with shortcut,,

Parkourkid93 said:
Just a heads up, not sure if my phone is just weird, but the first wipe instructions (step 4), resulted in my device only being able to boot to bootloader and resulting in " FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" if i try to flash or do anything on CMD/fastboot now. Not sure if it's bricked or if this will happen to you, and it's obviously not a ROM issue, but just mentioning it just incase anyone is following the exact steps.
Click to expand...
Click to collapse
Dont wipe system,,just do format data

muphetz said:
Dont wipe system,,just do format data
Click to expand...
Click to collapse
Too late, I already learned the hard way bro. I'm pretty sure it was bricked since I couldn't even get into recovery, just kept booting back to the bootloader. I unbricked it and i'm & running now though. Great rom so far, I noticed the initial UI lag that seems to be common on every A11 roms I tried for the oneplus 7, but it goes away once you refresh the screen, so no big deal. A major issue for me though is that Google FI doesn't seem to activate. When I try to it just tells me "Unfortunately your Google FI service can't be activated because your account currently isn't authorized for service". Which sounds like it's an issue with my account, but when I log into fi via my desktop, nothing seems out of the ordinary, I even randomly used the sim on a t-mobile sim locked iPhone, downloaded FI and it activated without an issue. I'm gonna go back to stock & see if it happens there. Will report back in a few.
To everyone else, don't let this discourage you from trying this rom out. Like i mentioned before, great rom so far & I appreciate the upload, I loved Evolution on Pixel 3. Just need my service lol

Parkourkid93 said:
Too late, I already learned the hard way bro. I'm pretty sure it was bricked since I couldn't even get into recovery, just kept booting back to the bootloader. I unbricked it and i'm & running now though. Great rom so far, I noticed the initial UI lag that seems to be common on every A11 roms I tried for the oneplus 7, but it goes away once you refresh the screen, so no big deal. A major issue for me though is that Google FI doesn't seem to activate. When I try to it just tells me "Unfortunately your Google FI service can't be activated because your account currently isn't authorized for service". Which sounds like it's an issue with my account, but when I log into fi via my desktop, nothing seems out of the ordinary, I even randomly used the sim on a t-mobile sim locked iPhone, downloaded FI and it activated without an issue. I'm gonna go back to stock & see if it happens there. Will report back in a few.
To everyone else, don't let this discourage you from trying this rom out. Like i mentioned before, great rom so far & I appreciate the upload, I loved Evolution on Pixel 3. Just need my service lol
Click to expand...
Click to collapse
MSMTool will save your life on this, also I recommend not using Step 4. Skip to Step 5. Wiping will erase OOS off the phone.

SaintZ93 said:
MSMTool will save your life on this, also I recommend not using Step 4. Skip to Step 5. Wiping will erase OOS off the phone.
Click to expand...
Click to collapse
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.

Parkourkid93 said:
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.
Click to expand...
Click to collapse
My question would be, what type of OP7P do you have. The one from OnePlus or the one from T-Mobile? If TMO then there is a different MSMTool you will need to use.

SaintZ93 said:
My question would be, what type of OP7P do you have. The one from OnePlus or the one from T-Mobile? If TMO then there is a different MSMTool you will need to use.
Click to expand...
Click to collapse
Good question, I bought it off of Amazon like a year ago though, so I don't have a 100% answer on that. Since I've gotten the device, I was able to OEM unlock, flash twrp, magisk etc. off the rip. I even dual simmed it with Google FI & Mint together without any issues and I use the global stock .zip from the OnePlus site everytime I update. If there's a way to check for sure, deff lemme know & I'll get back at you. Message me though since this isn't really ROM related & I don't want to clutter up the thread.

Set up works fine, getting an unusal issue where the framerate is locked at 30fps, anyone else having this issue?
*Edit* Typical, I reboot to install magisk, and now it is working fine. Nevermind me!

H4X0R46 said:
Wait, this has OOS cam AND is Android 11? SICK! Does normal Magisk Beta work or do we need that modded Magisk that's been floating around?
Click to expand...
Click to collapse
You can use magisk v21.2 or the modded one, it seems the fastboot issues were fixed in v21.2.

Eagle-no1 said:
@justasic What version of the camera program?
Click to expand...
Click to collapse
OOScam version 3.8.114, I didn't focus a lot on getting camera working quite yet which is why it still has some crashes, should be getting fixed as best I can in the next few updates.

ImjustSaiyan92 said:
Set up works fine, getting an unusal issue where the framerate is locked at 30fps, anyone else having this issue?
*Edit* Typical, I reboot to install magisk, and now it is working fine. Nevermind me!
Click to expand...
Click to collapse
This framerate issue is because I am forcing 90hz from the kernel (since automatic 90hz needs some work still), just lock the device and unlock it and it will go away.

Parkourkid93 said:
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.
Click to expand...
Click to collapse
hmm I only had to use msmtool once in my experience, generally as long as you're able to get to fastboot and you've already oem unlocked, you can go back to oos usually by fastboot booting a recovery image and flashing from there. I have not heard of Google FI before so I will look into this, we just merged our January security patch so I'll be making a new release soon and it might be related to that. I've not had any issues with wiping system on my device and I keep it there in case others are looking to come from other roms. Wiping vendor would cause issues though which is why I have flashing oos there but you're welcome to skip the wiping system step as I don't believe it will cause problems since the rom flashes over system anyway.

Done all the steps. Cant connect to my home wifi, I enter password and nothing happens. Any ideas? Wifi worked before on android 11

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..