Database Info

[Q] First time rooting.

Couldn't find a very clear tutorial anywhere, just a number of different threads saying different things lol. Anyways, need to know how to root my Droid Charge. Also need to know how to install CyanogenMod after.
I know rooting will void my warranty but I heard from a few people that if I unroot the phone, the warranty will be put back in place. Is this true?
If I somehow manage to brick my phone, I can always unbrick in most cases, correct?
Phone Info:
Hardware version - i510.06
Firmware version - 2.3.6
Kernel version - 2.6.35.7-EP4
Build number - SCH-I510.EP4
Not sure what information is important, but I believe it was mainly the kernel and Android version lol.
EDIT: Never mind about Cyanogen, I just want the best/fastest ROM I can get.

First things first. It's very difficult to hard brick this phone. I had to do a warranty return before and it is easy to go back to stock. If you get a soft brick, you can follow this thread and get it back to stock: http://forum.xda-developers.com/showthread.php?t=1111486
Next thing, you can't install CyanogenMod on this phone. We don't have any AOSP rom on this phone. All we have is repackaged stock roms.
As for how to root, it really depends on what you want. Do you just want root, or do you want a rom?

For right now, I just want to root. I've found out how to do that, kinda. I'm stuck now.
I'm trying to install imoseyon's kernel through CWM but I used the backup option before I installed the kernel. So now when I boot into recovery it oly gives me the optinos to "reboot system now", " apply update from sdcard", "wipe data/factory reset", and "wipe cache partition". I tried to apply update from sdcard and when I selected my kernel zip, it gives me back this:
"
-- Install /mnt/sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.

You need to reflash CWM.
CWM does not survive a reboot unless you're on a custom kernel, or root and remove the updater script. You have to flash CWM and immediately boot into it. If you let it boot up fully on the stock kernel, it will overwrite CWM with the stock recovery, so you'll have to flash it again, and immediately boot in and flash.

Will I keep the backup I made? Or should I just not worry about the backup and use Titanium?

It will keep the backup. It does the backup to SD, and the only folder on SD that CWM will touch in a wipe is .android_secure.

It worked. All rooted, thank you. Any suggestions for themes, apps to get, or ROMs?

ratchetlock2 said:
It worked. All rooted, thank you. Any suggestions for themes, apps to get, or ROMs?
Click to expand...
Click to collapse
The two most are using are TweakStock and Infinity. I strayed but came back to
TweakStock. Dont think it has a true theme available yet but you could atleast do something like Go launcher or something. With Ifininity there is a theme available. Read about both in the Dev section then decide.

Will do. Any OCable kernels yet? Saw someone post on here that there wasn't any yet.

ratchetlock2 said:
Will do. Any OCable kernels yet? Saw someone post on here that there wasn't any yet.
Click to expand...
Click to collapse
No custom kernels at all, other than repackaged stock kernels, but Tegrak Overclock works with any GB kernel. The free version only lets you change clock speeds. The pay version lets you change voltages as well, and lets you apply at boot.

Uh oh, got stuck in an infinite reboot loop. Tried turning my phone on only to come up to the first Samsung post screen, goes to black eventually for a little bit, then goes right back to the Samsung screen. How do I fix it? Can't find a solid answer.
I went into CWM and tried to restore a backup but it said it was missing the MD5 file or something; can't remember what exactly the error was with the restore. I'll try reflashing CWM soon.

Now I can't do anything... Can't put phone in DL mode, recovery, nothing. Won't even say it's charging.
I'm still under warranty, I'm considering bringing it in and saying I need a replacement because I know they won't be able to fix this on the spot.
EDIT: Got into DL mode luckily and I'm getting into DL mode smoothly now. But I still can't power on or get into recovery...
EDIT2: Using this thread to try and fix my problem. http://forum.xda-developers.com/showthread.php?t=1111486
{
"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"
}
Are these the right settings?
Trying to odin this file: http://forum.xda-developers.com/showthread.php?t=1172182
EDIT3: What a headache... Fully back to stock now. Going to try and restore everything that I backed up onto my SD card.

Are you leaving in the battery while flashing?
Sent from my SCH-I510 using xda premium

Nope.
numberfix

ratchetlock2 said:
Nope.
numberfix
Click to expand...
Click to collapse
There's your problem. Once you're in download mode and detected by Odin, pop the battery back in.
Sent from my SCH-I510 using xda premium

Xperia bootloop upgrading to 5.1.1 (FTF D2303 Generic UK 18.6.A.0.182)?

The last thing I remember flashing was Clockword Mod 11 last year, ever since then I have been running Firmware build 18.3.1.C.1.15. Upon seeing an update for my phone for Firmware build 18.3.1.C.1.17 I attemted to download it and kept getting the message "Cannot Verify" so after trying this out on PC Companion and relocking my bootloader I was still running into problems. So the simplest thing I could think of is to use Flashtool and flash the latest ftf from there (Firmware 18.6.A.0.182 - obtained from XperiFirm), at first I didnt think it was a problem to not wipe USER_DATA as I just thought of it as an upgrade, if that failed I persumed I would have to wipe everything (this didnt matter much anyway). So I went ahead and flashed the rom however when I went to boot my mobile I got a bootloop "Android is optimising apps xxx of xxx" this went on forever untill I cut the power using a pin. So I tried it again this time wiping everything and still the same problem :crying: . Then I came across people on the forums to use the older FlashTool verison 0.9.18.6 since the new FSC feature can cause probelms, this time I tried it again however I used the older Firmware 18.6.A.0.172 just to be failsafe. Still the same problem. Right then I was thinking Emma would save my phone so I went and applied the 4.4.4 Firmware 18.3.1.C.1.15 service (Which I had to begin with) but for some reason this seemed to have little effect despite trying it twice and reciving a "Sucessful Flash" message. Now I am left very confused as it is still booting in the lollipop style (optimising apps loop) even though I flashed a KitKat rom. I have been left without my phone all day because of this, any help would be STRONGLY APPRICIATED! . Thanks for your time

#1 Open your bootloader again
#2 Install TWRP (See 5.1.1 root topic for installation/guide)
#3 Open TWRP Wipe all data
#4 Reboot into recovery
#5 Flash any custom rom like Cyanogenmod through TWRP
Post results please this is fixable It's seems It's a soft brick which is an easy fix
What i think is you had corrupt data/left over data and after you relocked bootloader something went wrong after flashing. Though flashing should wipe all data let's see

Re-flash ftf wiping data and caches, you must do this if going from 4.4.4 to 5.1 and From 5.1 to 4.4.4 due to changes in runtime from dalvik to art and other changes.

How to get near enough stock?
Thanks for your replies, when I flashed the ftf's I did tick all the boxes under 'Wipe' on FlashTool, when that failed so did emma. I can try flashing CWM however the main purpose of this was for me to upgrade to Lollipop as I wanted a near enough stock experiance (Considering Z5 Rom) with root. When I tried CWM before there were a few things that I just coulnt get used to. Is there any way that I could use recovery to flash a stock rom with the lastest Lollipop releese or Z5 experiance as I have backups on PCC that I have to restore (Important contacts, media etc...) and I dont really want to use a CWM based rom . I wouldnt mind to flash Z5 however I dont know if this is possiable could you guys comfirm this? Thanks for your time .

[Update] TWRP recovery is working!
I have followed this thread to update my Recovery - TWRP 2.8.7.0 .
Many Thanks to @linuxct for the straight forward instructions and @ARandomIndian for putting me in the correct direction :highfive: .
Im just unsure if I can flash Z5 Experiance Rom now. Is it possiable despite my android being messed? I have already wiped data, is it okay to just go and flash? .

Zane Finch said:
I have followed this thread to update my Recovery - TWRP 2.8.7.0 .
Many Thanks to @linuxct for the straight forward instructions and @ARandomIndian for putting me in the correct direction :highfive: .
Im just unsure if I can flash Z5 Experiance Rom now. Is it possiable despite my android being messed? I have already wiped data, is it okay to just go and flash? .
Click to expand...
Click to collapse
Don't worry you're android is not messed up, let's do this to fix it back to regular :-
Before starting i highly recommend you charge your phone to have atleast 50+% battery and use the official cable provided also make sure the cable is firmly inplace,
#1 Enter Recovery, wipe all data
#2 Download Stock 5.1.1 i think you like that so get that (Make sure it is for your D2303 or whatever your model is)
#3 Install latest flashtools with latest patch (Or later versions if you don't want to risk it)
#4 Go to the location of flashtools (installation directory) for me it is C:\Flashtool\drivers Open the exe file there, select the 2 Flashmode and Fastboot drivers install them.
#5 Flash the ftf using flashtools
Post results

Somehow...
Using TWRP I wiped Dalvik Cache, Cache, System and Data. Using the same 18.6.A.0.182 Customization UK FTF from yesterday I flashed my phone but somehow I am stuck with the same bootloop again?! "Android is optimising Apps XXX of XXX" I really dont understand this. . Thanks for your help .

Zane Finch said:
Using TWRP I wiped Dalvik Cache, Cache, System and Data. Using the same 18.6.A.0.182 Customization UK FTF from yesterday I flashed my phone but somehow I am stuck with the same bootloop again?! "Android is optimising Apps XXX of XXX" I really dont understand this. . Thanks for your help .
Click to expand...
Click to collapse
Hey man Android is optimizing means everything is working just fine it takes about 30+ minutes sometime,
Just leave it charging for atleast 2 hours and see what the progression is and post results please, thank you

Optimising
ARandomIndian said:
Hey man Android is optimizing means everything is working just fine it takes about 30+ minutes sometime,
Just leave it charging for atleast 2 hours and see what the progression is and post results please, thank you
Click to expand...
Click to collapse
Yes but this does not seem normal, the first boot always freezes on the wave animation. It then restarts by itsself and optimises upto so many for example 64 of 200 and then freezes and restarts with a different ammount like 90 of 194. This didnt seem normal to me, is this okay?
Edit: I have left it running for almost 40 min now. Every time just before it seems to freeze and reboot it never reaches the end of the ammount say 60 of 200. I'm becoming very doubtful that it is going to work . But I just remembered a while back that I flashed a custom boot img to get recovery and root in my last working state. Maybe this has somthing to do with it?
Really need my phone working now :| If anyone can help please do! Thanks!

Zane Finch said:
Yes but this does not seem normal, the first boot always freezes on the wave animation. It then restarts by itsself and optimises upto so many for example 64 of 200 and then freezes and restarts with a different ammount like 90 of 194. This didnt seem normal to me, is this okay?
Edit: I have left it running for almost 40 min now. Every time just before it seems to freeze and reboot it never reaches the end of the ammount say 60 of 200. I'm becoming very doubtful that it is going to work . But I just remembered a while back that I flashed a custom boot img to get recovery and root in my last working state. Maybe this has somthing to do with it?
Really need my phone working now :| If anyone can help please do! Thanks!
Click to expand...
Click to collapse
Hi okay, try flashing the Z5 style rom please then we'll move forward I think you've a corrupted ftf
Please redownload latest Z5 style rom make sure it's not interrupted during download. Restart router if needed for stability before download

ARandomIndian said:
Hi okay, try flashing the Z5 style rom please then we'll move forward I think you've a corrupted ftf
Please redownload latest Z5 style rom make sure it's not interrupted during download. Restart router if needed for stability before download
Click to expand...
Click to collapse
I tried flashing the Z5 experiance rom, I followed the instructions on the rom page (Used TWRP). However this time when it booted it did not say "Optimising Android" but it still did boot loop after the wave animation. I also tried flashing the older firmware but that did the same loop again, I also have been looking for alternative ftf's online becuase I also had the suspicion of a corroupted ftf however there are no Customized UK roms availble. I really am stuck now, my phone seems to be more messed up than I thought. . Any more Ideas?

If your bootloader is unlocked did you update it before flashing anything? If not this is why

Zane Finch said:
I tried flashing the Z5 experiance rom, I followed the instructions on the rom page (Used TWRP). However this time when it booted it did not say "Optimising Android" but it still did boot loop after the wave animation. I also tried flashing the older firmware but that did the same loop again, I also have been looking for alternative ftf's online becuase I also had the suspicion of a corroupted ftf however there are no Customized UK roms availble. I really am stuck now, my phone seems to be more messed up than I thought. . Any more Ideas?
Click to expand...
Click to collapse
You updated your bootloader before flashing right? If not do that like Andy said,
Also i would give you my Nandroid but It's the D2305.

[email protected] said:
If your bootloader is unlocked did you update it before flashing anything? If not this is why
Click to expand...
Click to collapse
ARandomIndian said:
You updated your bootloader before flashing right? If not do that like Andy said,
Also i would give you my Nandroid but It's the D2305.
Click to expand...
Click to collapse
Okay, you mean the same one I flashed to be able to update my bootloader to TWRP? I'll give it a shot! Thanks!

Zane Finch said:
Okay, you mean the same one I flashed to be able to update my bootloader to TWRP? I'll give it a shot! Thanks!
Click to expand...
Click to collapse
Okay nice post the results

ARandomIndian said:
Okay nice post the results
Click to expand...
Click to collapse
I flashed that very bootloder before I flashed the Lollipop ftf I booted my phone and the same thing happend, so I tried it again this time flashing afterwards an still booting with the same damn screen . Was I definatly using the correct bootloader or am I missing out anything when flashing? My phones rebooted like 5 times now for the 'optimisation' and its getting nowhere .
Shall I fire up my classic Nokia 5230 with custom Symbian to record a video so you guys can see what happens when it boots?

Did you wipe user data and cache when flashing the ftf

[email protected] said:
Did you wipe user data and cache when flashing the ftf
Click to expand...
Click to collapse
Yes, everything in the 'Wipe' section was ticked, infact before I flashed it again I also wiped Dalvik, cache, data and system in TWRP.

So I just flashed CWM 12.1 and its all running fine for some reason the Wifi doesnt work but atleast I can use this untill we find what the problem is. Do you guys know why my WiFi isnt working? But more importantly why does CWM work and stock rom doesnt?!
Edit: The reason the WiFi isnt working has to be a problem with the kernal as far as I can see, this also suggests that the kernal could be incompatable with Lollipop as it wasnt designed to support it? Correct me if im wrong but if this is the case where can I download the official latest kernal? If someone could confirm this by checking my kernal version above that would be great! Thanks!
I previously updated my kernal here the one that says [new]. If you look at post #8 you will see that this kernal has a problem with WiFi in CWM "As I suspected, in kernel modules there's no WiFi module (wlan.ko), I think that that's the reason why WiFi is not working.
{
"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"
}

Okay flash this version of Cyanogen http://forum.xda-developers.com/xperia-m2/orig-development/rom-cyanogenmod-12-developement-t2971213 choose the latest one
We'll see what the issue can be any ideas @linuxtt
---------- Post added at 03:18 PM ---------- Previous post was at 03:14 PM ----------
Zane Finch said:
So I just flashed CWM 12.1 and its all running fine for some reason the Wifi doesnt work but atleast I can use this untill we find what the problem is. Do you guys know why my WiFi isnt working? But more importantly why does CWM work and stock rom doesnt?!
Edit: The reason the WiFi isnt working has to be a problem with the kernal as far as I can see, this also suggests that the kernal could be incompatable with Lollipop as it wasnt designed to support it? Correct me if im wrong but if this is the case where can I download the official latest kernal? If someone could confirm this by checking my kernal version above that would be great! Thanks!
I previously updated my kernal here the one that says [new]. If you look at post #8 you will see that this kernal has a problem with WiFi in CWM "As I suspected, in kernel modules there's no WiFi module (wlan.ko), I think that that's the reason why WiFi is not working.
Click to expand...
Click to collapse
Okay can you please flash another FTF? First try a new 5.1.1 ftf from another source for your model and then try older versions like Kitkat and post results please

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.

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