Hi guys, can somebody help me? I received the stagefright update this morning and after downloading it and rebooting, the phone stopped working. It shows the logo animation for a few seconds then the screen goes black. It's a rooted and unlocked phone so i don't know if thats the cause. Also, i can access the recovery mode pressing power and down. Other than that nothing.
If you were rooted and updated ya..the rooting may be the reason
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Jaydeep123 said:
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Click to expand...
Click to collapse
I always forget how peacefull people with knowledge can be. Thanks mate, will do that.
But, just for curiosity: rooted phones tends to have problems after updates?
Yes It may get error or Somthing Else Thats Why I prefer if a update is avaiable flash back to stock and then proceed
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
reinaldojr said:
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
Click to expand...
Click to collapse
Mod will move or merge.
Sent from my MotoG3 using XDA Free mobile app
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
hp420 said:
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
Click to expand...
Click to collapse
Hello HP429; reflashin full factory image would effectively wipe phone
sunandoghosh said:
Hello HP429; reflashin full factory image would effectively wipe phone
Click to expand...
Click to collapse
Not if you only flash the system, boot and recovery image files
Recover the factory
I did the update and as mentioned previously on the thread stales after the logo. (bootloader is unlocked)
I can not find my oem backup. I tried twrp on recovery and was able to backup other stuff. Is there a way to generate the OEM so that i can flash or any other roms that are compatible with Moto G 3rd generation?
Try wiping cache, dalvik cache and data with TWRP. Don't use stock recovery for the data wipe or you will lose all the files stored on your internal partition, as well.
Related
Hi,
I tried to modify the build.prop file of my LG Optimus 2X to simply disable the animation during the boot. It didn't really worked well because my cellphone is now looping during the boot. I think I saved the build.prop on my sdcard but now I don't know what to do...! I tried to hard reset and wipe date, but it's still no booting. I have clockwork mod instal.
Thank you!
EjasRus said:
Hi,
I tried to modify the build.prop file of my LG Optimus 2X to simply disable the animation during the boot. It didn't really worked well because my cellphone is now looping during the boot. I think I saved the build.prop on my sdcard but now I don't know what to do...! I tried to hard reset and wipe date, but it's still no booting. I have clockwork mod instal.
Thank you!
Click to expand...
Click to collapse
Well, first, I'd like to ask if you have a CWM backup of your system before you edited your build.prop? I assume that since you can wipe the data, you can reach CWM. If you can and have a backup, try recovering that backup and see if that works. If you do not, then you can always try to find an RUU (ROM update utility) that should return your phone to an unrooted, stock ROM. I don't know of any other options, all I can say now is become best friends with that search bar up there.
Hope you manage to get your phone back. :fingers-crossed:
revert to stock, oh just reflash whatever custom ROM you have been using (if you have any), you should be able to mount SD card from CWM and copy your ROM in there and flash away. I am under the assumption that since you were doing your DIY mods there, you should have knowledge of flashing back to stock or Custom Roms of choice. Good luck.
TekGadgt said:
Well, first, I'd like to ask if you have a CWM backup of your system before you edited your build.prop? I assume that since you can wipe the data, you can reach CWM. If you can and have a backup, try recovering that backup and see if that works. If you do not, then you can always try to find an RUU (ROM update utility) that should return your phone to an unrooted, stock ROM. I don't know of any other options, all I can say now is become best friends with that search bar up there.
Hope you manage to get your phone back. :fingers-crossed:
Click to expand...
Click to collapse
No I don't have a CWM backup :S Do you know where I could get a RUU for my phone?
EjasRus said:
No I don't have a CWM backup :S Do you know where I could get a RUU for my phone?
Click to expand...
Click to collapse
Here's a start. http://forum.xda-developers.com/showthread.php?t=1035041
The search bar on top is very useful if that doesn't help...
Foreverme89 said:
The search bar on top is very useful if that doesn't help...
Click to expand...
Click to collapse
That it is. Half of the time when helping people out, that is my starting point I'm really new to this, but know my way around a search engine and how to read
Boot into recovery, wipe cache and dalvik cache, and flash the same ROM you were already using
Sent from my MB508 using xda premium
do a full wipe or flash with the original rom
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps
xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
You can always flash the factory images here: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You can flash any ROM and that should fix your issue
You will not lose your unlocked bootloader unless you flash the stock one which is in the factory images
Your bootloader will not relock unless you lock it yourself using fastboot. Flashing roms or factory images won't lock it by themselves.
And even if it somehow did, one fastboot command and you're unlocked again.
And as far as root goes....it takes 5 minutes to reroot.
So just flash whatever factory image you need and then custom recovery, and you're done. Maybe need to download superSU from play store after.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
justinisloco said:
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps
Click to expand...
Click to collapse
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?
xfranchize said:
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?
Click to expand...
Click to collapse
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
vin4yak said:
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.
xfranchize said:
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.
Click to expand...
Click to collapse
Maybe your flashing a bad version of GApps since the force closes are on google Calander?
Are you using a 4.4.2 GApps?
Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk
xfranchize said:
Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.
gee2012 said:
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.
Click to expand...
Click to collapse
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?
xfranchize said:
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?
Click to expand...
Click to collapse
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.
gee2012 said:
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.
Click to expand...
Click to collapse
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk
xfranchize said:
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).
gee2012 said:
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).
Click to expand...
Click to collapse
Okay ill give it a shot, thanks alot. Ill update here if im successful.
Sent from my Nexus 5 using Tapatalk
Hi! I just installed a new Custom ROM for my phone. After 5 minutes I wanted to create a backup. So I started ROM Manager. I entered the name, and hit OK. The phone booted into a crashed recovery mode. So I took the battery out and rebooted the phone. It didn't boot into my Custom ROM. It booted into recovery. So I am stuck inside the recovery mode and can't boot normally.
Phone: Samsung Galaxy Mini (GT-S5570)
Recovery: CWM Recovery
Custom ROM: CyanogenMod
Hello,
If you can boot into the recovery, do a factory reset and flash back the custom rom. And then reboot the device, once you rebooted the device will boot into system. And then you're done!
Good luck!
HashyCode. :good:
It still puts me into recovery
HashyCode said:
Hello,
If you can boot into the recovery, do a factory reset and flash back the custom rom. And then reboot the device, once you rebooted the device will boot into system. And then you're done!
Good luck!
HashyCode. :good:
Click to expand...
Click to collapse
I tried it. I wiped /system, /data, /cache and I did a factory reset. Flashed it back but it still puts me into recovery.
xdcsaba said:
I tried it. I wiped /system, /data, /cache and I did a factory reset. Flashed it back but it still puts me into recovery.
Click to expand...
Click to collapse
Flash the original firmware back. And try from the start
HashyCode
It still doesn't work
HashyCode said:
Flash the original firmware back. And try from the start
HashyCode
Click to expand...
Click to collapse
Tried it. Does not work.
xdcsaba said:
Tried it. Does not work.
Click to expand...
Click to collapse
Visit here and try one of them
HashyCode.
Hi, i would like help you with this problem as I myself have experienced it. The things that you should have done are:
1. Always make the backup early on before installing the Custom ROM.
2. When installing a Custom ROM, make sure you have not replaced core system apps
3. Make sure your there are complete symlinks in your ROM otherwise it be hard bricked. Ouch.
4. Before installing a Custom ROM, make sure they are from experts, like CyanogenMOD, and sure your device is supported for updates.
5.[Most Important] The only things to wipe when installing a ROM are : 1. Cache 2. Dalvik Cache 3. User Data, never ever ever ever WIPE your system folder with root access on it. This will always ensure that you will reboot into recovery, and it will be annoying to root your device w/o ADB USB Debugging on.
6. Make sure that there are no system apps missing on your Custom ROM, check for the legibility of the Custom apps installed. Are they pirated perhaps?
7.[Very Important]Always watch a video tutorial for it's errors, and search how to Unbrick your device first before proceeding with an installation.
So that if any problem arises, you will be sure to restore it to it's Stock experience.
8.[Absolutely Important]Make sure that your software counterparts on the PC are compatible and functioning well first before you proceed.
Now tell, me which of the following did you not do?
And if this really helped you a lot, please like. For the sake of those who did their research.
HashyCode said:
Hello,
If you can boot into the recovery, do a factory reset and flash back the custom rom. And then reboot the device, once you rebooted the device will boot into system. And then you're done!
Good luck!
HashyCode. :good:
Click to expand...
Click to collapse
ive already done factory reset like 5 times i still am not able to flash it to custom rom stock condition im going to try using a laptop with windows 7 to see if i can do that way because its not working on the latest windows 8
Kinnngzzzz
Try fastboot?
Hi,
No one seems to have suggested using a program called fastboot. It involves just installing some essential software on a PC, then running the program "Fastboot" along with the desired options.
I strongly suggest trying this: http://forum.xda-developers.com/showthread.php?t=2277112
I am always flashing ROMs and then trying to tweak them and end up messing up the bootloaders, or somehow breaking the system. And then i try using CWM or TWRP and still there remain issues. However, fastboot has always done the job for me.
Hope this helps.
Someone help me with my problem please ??
Use Fastboot!!!
kinnngzzzz said:
Someone help me with my problem please ??
Click to expand...
Click to collapse
kinnngzzzz, you too should use Fastboot! See my post right before yours...
So again, see this link: http://forum.xda-developers.com/showthread.php?t=2277112
I say if fastboot can't get it fixed, nothing will. :victory:
kinnngzzzz said:
Someone help me with my problem please ??
Click to expand...
Click to collapse
As you said that you're going to try with windows 7. Did you tried it? And please! Visit the link which youniqueg33k provided.
HashyCode.
Ok guys I'm stumped on this one. I got the OTA notification for 5.1 yesterday on my XT1034 and so I decided to preempt any issues I might have and just flash everything back to stock 5.0.2 in order to install the update.
I was able to flash everything fine then went to reboot, got the unlocked bootloader screen and...... nothing. It just stayed on the unlocked bootloader screen. I figured I did something wrong so I reset back to fastboot mode, tried again and sure enough I missed sparsechunk 3. So I tried again, restarted, and.... same thing.
OK then, reset again and reboot into recovery mode. It booted to the Motorola splash screen, ok this is different..... nope still not loading. Reset again and try flashing a custom recovery.
CWM, flashed ok, reset again, Moto splash
TWRP, flashed ok, reset, Moto splash
Philz, flashed, reset, splash
OK.. so I'm clearly doing something wrong. Did some research and tried:
- formatting the cache and userdata partitions
> cache formatted fine, userdata refused to format, not supported for filesystem type 'raw'
- tried flashing again without erasing the partitions
> flashed fine, no change in booting
- tried flashing back to 4.4.4
> flashed fine, no change in booting
- tried flashing all the custom recoveries with 4.4.4, no change
- I found a thread where someone else had a somewhat similar issue, and apparently resolved by unlocking their bootloader
> mines already unlocked, but sure it can't hurt, tried again, but nothing since it's already unlocked
I looked for anyone that had a stock 5.1 image other than the OTA, but couldn't find anything. I gave up on trying stock and looked at some custom roms, but all of them just start with, unlock your bootloader, load a custom recovery and flash the update zip file.
Soooo I'm stumped. I've tried just about everything I can think of. I made backups of everything so I'm not worried about the data I just want a working phone again. I refuse to accept that it's borked at this point since I can still get to fastboot.
OK so, no clue what changed, but I was finally able to boot into recovery, Philz
I wiped and reformatted everything and tried flashing 5.0.2 again
rebooted and it still hung on the bootloader unlocked screen
I'll try flashing Philz again and updating through there
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
tapman said:
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
Click to expand...
Click to collapse
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Umer520 said:
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Click to expand...
Click to collapse
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
moralesnery said:
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Click to expand...
Click to collapse
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
tapman said:
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
Click to expand...
Click to collapse
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
tapman said:
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
Click to expand...
Click to collapse
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Umer520 said:
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Click to expand...
Click to collapse
Yeah unlocking your bl doesn't affect ota's
moralesnery said:
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
Click to expand...
Click to collapse
I think at least in part what my issue was, was that the partition formatting got borked. If you can boot to a custom recovery you can wipe and reformat them. Then you should be able to reflash it normally.
I was just so tired of dealing with my phone at that point so I only tried once and gave up with stock, but I'm pretty sure that's what I need to do to fix it.
Just figured I'd give the heads up if you factory reset with a patched boot, for root or otherwise, it bootloops the phone twice and then goes to recovery. Flashing back stock boot img fixes it.
So don't be stupid like me and reset settings while rooted lol.
thank you for providing us this info, do u just have to go through the whole process again to TWRP/Root?
would it work, if u installed the stock unmodded boot image via twrp, do the factory reset/or clean install full OS zip, then install TWRPFix & Root all in the same session?
Bradl79 said:
thank you for providing us this info, do u just have to go through the whole process again to TWRP/Root?
would it work, if u installed the stock unmodded boot image via twrp, do the factory reset/or clean install full OS zip, then install TWRPFix & Root all in the same session?
Click to expand...
Click to collapse
I would imagine so, I haven't tried that yet. TWRP broke wifi for me, so I went back to stock recovery for now, maybe I did something wrong, but I'm gonna hold out until theres an official TWRP.
Chris123NT said:
I would imagine so, I haven't tried that yet. TWRP broke wifi for me, so I went back to stock recovery for now, maybe I did something wrong, but I'm gonna hold out until theres an official TWRP.
Click to expand...
Click to collapse
Did u follow post 70 step by step and used the files provided? Also when I did mine I deleted any security I had first.
Bradl79 said:
Did u follow post 70 step by step and used the files provided? Also when I did mine I deleted any security I had first.
Click to expand...
Click to collapse
Yeah, I did, so I dunno what happened, but when I booted into the OS after all the steps WiFi was boned.
If you have TWIRP why would you factory reset?
Why not just format /data?
Or does that also cause boot loops
virtyx said:
If you have TWIRP why would you factory reset?
Why not just format /data?
Or does that also cause boot loops
Click to expand...
Click to collapse
u don't want to format data, u want to wipe data, Format will erase sdcard. That is what the factory reset does anyway is wipe the caches and data.
Bradl79 said:
u don't want to format data, u want to wipe data, Format will erase sdcard. That is what the factory reset does anyway is wipe the caches and data.
Click to expand...
Click to collapse
if youre going to factory reset might aswell format data in twrp
i just thought maybe formatting data in twrp wouldnt cause the bootloop
virtyx said:
if youre going to factory reset might aswell format data in twrp
i just thought maybe formatting data in twrp wouldnt cause the bootloop
Click to expand...
Click to collapse
I could be wrong but I believe the OP might be talking about the root files and not twrp. Prior to twrp release, factory reset was the only option. As it happen to me also, after rooting device.
Plus Oneplus did not include a rom install zip in the stock recovery.
Damn, this AB partition setup really makes things a hassle
Bumping because other people are getting tripped up by this. Something in the factory reset process is not compatible with any sort of mods.
This happened to me as well. Not sure how I recovered, as I flashed via fast boot a bunch of image files. Is the boot image in the image files the latest stock boot image for 5.1.5?
For those of us rooted and no TWRP can someone link the stock boot.img?
Nevermind I found them on the ota page by titokhan
Bradl79 said:
Did u follow post 70 step by step and used the files provided? Also when I did mine I deleted any security I had first.
Click to expand...
Click to collapse
That could be what's causing it, I did wonder about that.
Chris123NT said:
That could be what's causing it, I did wonder about that.
Click to expand...
Click to collapse
try it and let us know
So before factory reset we need to make sure to reflash stock boot.img that will unroot the phone and only then do a factory reset..
So factory reset with twrp is working or not?
Anyone know where I might be able to get the stock boot.img? My phone is now toast and the referred thread should carry a health warning
Sorry for the noob question but does factory reset delete the media partition too?
itsadme said:
Sorry for the noob question but does factory reset delete the media partition too?
Click to expand...
Click to collapse
No, it does not.
this happened to me too. I was thinking of flashing the latest OxygenOS 5.1.11 with a clean install and I am rooted with TWRP. So what I did was reboot to recovery, wiped data, flashed OOS, then TWRP, reboot recovery and then flashed magisk. Then it got stuck in a TWRP bootloop.
Good thing I had a nandroid so i restored it and tried again.
This time I did the above steps but didn't wipe data. I booted successfully to 5.1.11 and i tried Factory Reset inside OxygenOS. Phone rebooted to TWRP and no data wipe was done. I did the Wipe Data within TWRP, same thing happened... bootloop to TWRP.
Nandroid restored again.
3rd attempt to dirty flash 5.1.11 but this time i didn't flash TWRP nor magisk and just rebooted system. I was back to stock. Then I tried factory reset again within OOS, it was successful so i had to do the whole TWRP and Magisk install again, and restored my apps via Titanium.
Moral of the story is (at least for me), Factory Reset within OOS or Wipe Data in TWRP both doesn't work. If i need to do a clean install, flash OOS then factory reset after rebooting to system, and then go through the whole TWRP and Magisk install process from scratch. Pain in arse really...:crying: