Database Info

updating from software crash - cyangoen mod

got a samsung galaxy captivate i897
bought it rooted running cyanogen mod & miui
was fine for about a year then the software kept crashing (everything was force closing)
in the this time i didnt do anything that would have caused this issue. i didnt update anything the only thing i did was install or uninstall apps. so i dont know why it occured. i dont even know if it happened as a result of having been rooted (if something became unstable - i wouldnt have thought so since it worked for a year with no problems)
anyways i now have new phone since that one become unreliable but i'm now looking at how i could fix the issue so i can use it as a spare phone if needs be.
it runs cyanogen mod android version 2.3.7 and i'd be looking at how i could go about updating to ice cream sandwich or jellybean, whichever has a stable build.
how would i go about doing this? (in simple terms - i'm a noob!)

neonflash said:
got a samsung galaxy captivate i897
bought it rooted running cyanogen mod & miui
was fine for about a year then the software kept crashing (everything was force closing)
in the this time i didnt do anything that would have caused this issue. i didnt update anything the only thing i did was install or uninstall apps. so i dont know why it occured. i dont even know if it happened as a result of having been rooted (if something became unstable - i wouldnt have thought so since it worked for a year with no problems)
anyways i now have new phone since that one become unreliable but i'm now looking at how i could fix the issue so i can use it as a spare phone if needs be.
it runs cyanogen mod android version 2.3.7 and i'd be looking at how i could go about updating to ice cream sandwich or jellybean, whichever has a stable build.
how would i go about doing this? (in simple terms - i'm a noob!)
Click to expand...
Click to collapse
Im glad you asked for ICS or Jellybean, CM 11 (Kitkat) is terrible looking. if you still know how to flash roms, we should probably figure out what version of CWM you have. other than that, if you have CWM 5.x.x.x or higher you can go ahead and download the top version here first http://download.cyanogenmod.org/?device=captivatemtd&type=stable and This Gapps for CM 10.2 http://goo.im/gapps/gapps-jb-20130813-signed.zip and put them both on your External micro SD card. boot into CWM and flash CM 10.2 first and then the Gapps after.

Trozzul said:
Im glad you asked for ICS or Jellybean, CM 11 (Kitkat) is terrible looking. if you still know how to flash roms, we should probably figure out what version of CWM you have. other than that, if you have CWM 5.x.x.x or higher you can go ahead and download the top version here first http://download.cyanogenmod.org/?device=captivatemtd&type=stable and This Gapps for CM 10.2 http://goo.im/gapps/gapps-jb-20130813-signed.zip and put them both on your External micro SD card. boot into CWM and flash CM 10.2 first and then the Gapps after.
Click to expand...
Click to collapse
problem is i dont know how to flash!
yeah sorry i'm a total noob
if there's step by step instructions though that'd be great

neonflash said:
problem is i dont know how to flash!
yeah sorry i'm a total noob
if there's step by step instructions though that'd be great
Click to expand...
Click to collapse
so do you at least know how to boot into Recovery? i haven't touched my Captivate in awhile but i imagine that its (turn off your phone first) hold volume up first then power button until the Samsung logo apears and tell me all the information thats on the screen. when your done you can use the volume buttons to navigate to reboot phone.

vol up & down and power yep :]
here's the options:
reboot system now
apply update from sd card
wipe data/factory reset
insall zip from sd card
backup and restore
counts and storage
advance
power off
go back
i selected reeboot now & have been left with a hat like this on screen :/ (dunno if that's good or bad!)
{
"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's just the hat nothing else and has been like that for about 30mins......
phone's ****ed isnt it ?
optop of the options it say cwm based recovery v5.0.2.7

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.

S7 battery life issues on Oreo, Nougat, Stock, Superman etc.

Hello all,
Whilst there are many posts like this about battery issues, I thought I'd make my own because I've already tried all the approaches I can think of and I'd like to avoid any unnecessary confusion between posters.
I have less than 3 hours screen-on time on my Samsung S7 SM-G930F (international model) and horrific standby time, meaning I'll run out of battery before the end of the day even if I don't touch the phone at all. When I first got the phone, I got 4-6 hours screen on time and I see no reason why this should have changed so drastically. This is a somewhat recent occurrence, over the last 2-6 months (I believe it was gradual, so I can't quite pick out the time it started happening).
{
"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"
}
So far, I have tried:
Factory reset
Uninstalling all unnecessary (non-core) apps
replacing the battery
draining and recharging the battery fully
underclocking the processor
a multitude of different stock ROMs, both Nougat and Oreo
a few different Kernels
At best, playing around with these options has net me maybe a 5-15% improvement overall, much less than the 70-100% improvement I need to get back to what I had during early Nougat / late Marshmallow days.
Bar literally just getting a new phone, I would appreciate any advice you can give me.
EDIT: System2 log:

Was the flashing of different ROM's via TWRP or Odin?

Beanvee7 said:
Was the flashing of different ROM's via TWRP or Odin?
Click to expand...
Click to collapse
TWRP

I'd recommend making a full backup in TWRP, saving it to your PC, then doing a full Odin flash using all 4 firmware files. It's the only method that ensures a complete fresh start.
It will mean you have to install TWRP again, but then you can at least be sure that you've cleaned out literally everything.

Beanvee7 said:
I'd recommend making a full backup in TWRP, saving it to your PC, then doing a full Odin flash using all 4 firmware files. It's the only method that ensures a complete fresh start.
It will mean you have to install TWRP again, but then you can at least be sure that you've cleaned out literally everything.
Click to expand...
Click to collapse
I formatted internal storage via TWRP more than once though. I would have thought that would have fixed it.

I've added a System2 log for extra information in the OP

Well if you're leaving behind a modified bootable custom recovery, the device isn't clean, and could still have corrupted, fragmented, or badly partitioned boot files that affect all subsequent installs.
A full Odin flash is the closest thing to an out of the box system, it fixes almost all software bugs and issues. I can't guarantee it will fix your issue, but it's the only thing you've not done.

Beanvee7 said:
Well if you're leaving behind a modified bootable custom recovery, the device isn't clean, and could still have corrupted, fragmented, or badly partitioned boot files that affect all subsequent installs.
A full Odin flash is the closest thing to an out of the box system, it fixes almost all software bugs and issues. I can't guarantee it will fix your issue, but it's the only thing you've not done.
Click to expand...
Click to collapse
Ok. Thanks a lot. I'll try it and report back in a few days.
I'll probably need to get the latest files from Sammobile (more like Sam-slow-bile).

samfirm tool still works for obtaining the latest firmware files, and I get max speed using it on my internet (100mbs down)
For older versions you might have more luck with updato.com, for me I get almost full speed if I use a download manager, but it does have a bit of a slow start period.

hey bro i have the same issue in oreo so its not worth downgrading to 7.0 ? .... these samsung have the most lowest battery life from all phones ... god btw what is that app your using ?

dengiz-islam said:
hey bro i have the same issue in oreo so its not worth downgrading to 7.0 ? .... these samsung have the most lowest battery life from all phones ... god btw what is that app your using ?
Click to expand...
Click to collapse
Change battery in Samsung service

Finnishman said:
Change battery in Samsung service
Click to expand...
Click to collapse
Hey, I was about to open a new topic, but maybe you could answer me here I was about to change the battery I installed an app called AccuBattery when I go to health it shows that my battery health is 48% and the estimated capacity 1.429mAh is the battery dead? I don't know if those are also acurate stats what you think? when I calculated how much I lose me with apps and stuff it exactly comes out like 1.400mAh huh? ...

Colors/screen messed up after flashing LineageOSMicroG (HELP)

So I unlocked, rooted, and flashed my first android and ran into this problem. I bought another G7 Power and ran into the exact same problem.
The screen/colors are all messed up.
{
"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 trying to retrace my steps to determine where I went wrong.
So first I try to check if the bootloader is properly unlocked. Here I run into problems.
First I tried dialing *#*#7378423#*#* but soon as I dial the last "#" the screen just goes blanc. So that didn't work
Second I tried "fastboot oem device-info" in ADB & Fastboot
So that didn't work either.
How can I determine if the bootloader is properly unlocked?

For a temporary fix,
go into the 'Display' menu in settings,
under 'Advanced' click on 'Colors' and select a different color scheme.
You can also go back to the original after that if so desired.
This fixes it for me until the next reboot.
Didn't happen with LOS 17.1, started seeing this when I went to LOS 18.1

Sigster said:
For a temporary fix,
go into the 'Display' menu in settings,
under 'Advanced' click on 'Colors' and select a different color scheme.
You can also go back to the original after that if so desired.
This fixes it for me until the next reboot.
Didn't happen with LOS 17.1, started seeing this when I went to LOS 18.1
Click to expand...
Click to collapse
This seems to have fixed it for me. I was seriously starting to doubt myself lol
Thanks allot

Same problem here. Color switch does not help.

I have the same problem.
Rocc69 said:
So I unlocked, rooted, and flashed my first android and ran into this problem. I bought another G7 Power and ran into the exact same problem.
The screen/colors are all messed up.
View attachment 5292047
Click to expand...
Click to collapse
I also found this problem. However, the remedy given as 'settings -> Display -> Advanced -> Colours -> Cycle between the Natural, Boosted and Saturated options fixed it for me until I rebooted the phone. Makes me wonder if there are some lines of coding that could be looked at with the controls of these options. Hope one of you clever guys can find a solution. Otherwise - Android 11 is working fine. Running LineageOS18.1. Thanks in advance. Ron

Looks like the problem was fixed with the LineageOS update on 10th May 2021.

Same here, no more color problems. But now I lost my modem. No cellular connection, SIM not recognized.
Edit:
Installed 2021-05-15 update OTA and cellular network came back.
Guess it could either be that the 2021-05-08 release was bad (or something went wrong during OTA)
or maybe one of my slots (a or b) has bad modem info and I will lose network with every other update.
We'll see.

As of the LineageOS18.1 May 15th 2021 update, I lost control of my SIM, the system saying that the SIM could not be found. A hard reset did not fix this either so I started afresh with boot into TWRP and wiped everything, then re-installed the first LineageOS18.1 I had downloaded to my sdcard. Voila! the system then found my SIM card again, but then when I allowed the system to upgrade to the 15th May 2021 release my SIM detection failed again! I have the wifi connection but am stumped as to what to do next. My contract is due for renewal in June 2021 so I think I'll buy a second hand Samsung instead. Any further advice anyone?

gulliverxc said:
As of the LineageOS18.1 May 15th 2021 update, I lost control of my SIM, the system saying that the SIM could not be found. A hard reset did not fix this either so I started afresh with boot into TWRP and wiped everything, then re-installed the first LineageOS18.1 I had downloaded to my sdcard. Voila! the system then found my SIM card again, but then when I allowed the system to upgrade to the 15th May 2021 release my SIM detection failed again! I have the wifi connection but am stumped as to what to do next. My contract is due for renewal in June 2021 so I think I'll buy a second hand Samsung instead. Any further advice anyone?
Click to expand...
Click to collapse
Similar to what I wrote in the comment before yours. My phone is a XT1955-5
Was on May 1st release. Lost SIM with the May 8th. Came back with the May 15th.
So it shouldn't be the May 15th release itself.
Based on what I read in a Reddit comment it could be that the modem code in one of my/our slots is bad.
I will try and confirm that by waiting for the next 2 releases to be out. Should then be such that when I install the next release I would lose SIM and with the second release get it back.
If that's the case I'll see if I can fix that without a wipe, phone is too important right now. If not I'll just live with it and only install 2 updates right after each other.

I had the same problem, somehow it works now with the new 20210515 and the old 20210508.
I suspect it has something to do with slot_a/slot_b and the respective modem bin, see my posts
here: https://forum.xda-developers.com/t/gps-not-working.4261437/
I have a XT1955-4, EU. My recollection of what I did is:
1. Flash 18.1 20210501. Modem and GPS does not work
2. Flashed modem from the original stock image like described here:https://forum.xda-developers.com/t/...nbrick-your-moto.3042687/page-6#post-80052655
3. GPS/Modem works
4. Updated to 20210508. Modem gone again.
5. Tried to flash the modem stuff again, nothing works
6. Discovered that I had forgotten to do the copypartitons part from the installation.
7. Flashed 20210501 to slot_a again, reflashed modem stuff
8. copypartions (apparently over to slot_b) / everything works like in 3
9. update to 20210508 (apparetnly to slot_b). Modem/GPS works
10. Update to 20210515, Modem/GPS works. (Microphone issue though)
Hope this helps anybody. I guess all this flasjhing could brick the phone, but it worked for me.

This issue with the messed up colours has showed up for a friend of mine as of November 2021. It is a G7 Power Dual SIM 4MB 64GB version running LineageOS 18.1
I haven't got the phone with me at this moment, but I'm happy to go to the LineageOS18.1 thread and include a logcat when I can.

Further device details to add from my comment yesterday. The Moto G7 Power is an XT1955-7
It's running the official vanilla build of LOS by @SyberHexen @erfanoabdi @npjohnson from here
The colour glitches usually appear a minute or two after reboot and after locking then unlocking the screen. Worth mentioning is I can't reproduce this screen glitch in bootloader and recovery modes.
I'm interested in the technical reason for this glitch because the image artifacts are interesting.
Attached are some photos of the phone.
sliding the RGB adjusters appear to behave normally.
Here's a picture of how a rainbow coloured wallpaper image appears when the glitch is present
Here's the original image as it should appear
The workaround solution from comment number 3 in this thread works for this device.

gulliverxc said:
Looks like the problem was fixed with the LineageOS update on 10th May 2021.
Click to expand...
Click to collapse
Nope it wasn't fixed. I have the newest update and its still there. My screen colors are " flickering" as I type this.

The problem is still there on the G7 Power that I just flashed with lineage-18.1-20220312-nightly-ocean-signed.
I also get the flickering. The fix from post 3 seems to fix it till next reboot.

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