Related
Way back when, I modified my 4.1.2 tab so I could use the Switchme app. Since it hasn't had a software update since then, I need to unmodify my system, so I did a hard reset but that doesn't seem to unmodify it so I can get it updated. Do I have to flash to a stock ROM, or won't that help either? I've done a hard reset twice now and restoring my Samsung account does seem to work either. Help PLEASE!
Nope it does not.
Stoney60 said:
Way back when, I modified my 4.1.2 tab so I could use the Switchme app. Since it hasn't had a software update since then, I need to unmodify my system, so I did a hard reset but that doesn't seem to unmodify it so I can get it updated. Do I have to flash to a stock ROM, or won't that help either? I've done a hard reset twice now and restoring my Samsung account does seem to work either. Help PLEASE!
Click to expand...
Click to collapse
Factory reset only Clears out use added content apps and Personal Settings. To get back to stop you will ..
1 Download the Correct Latest Version Of Android From Sam-mobile or Samsung For your Device.
2. Download odin for your device
3. Make sure you can access your device from windows or os your using.
4. Follow instructions for getting into download mode and flashing the samsung firmware with odin from your computer.
5 . Reboot the device and Leave it be..
Never flash anything on any Device until you know how to get back.
There are many Threads with step by step details on the above. even many youtube videos..
Good Luck
Hey,
I don't think you have to flash back to a stock ROM in order to upgrade to a different ROM. I was able to upgrade my tab with 4.1.2 (I can't remember what ROM it was) right to GNABO then a few hours later to Carbon, and a few hours later to Hyperdive and I'ts running fine with no issues besides the Aroma freezing, but what else is new...
You shouldn't have to flash back to a stock ROM to flash to a modified ROM, reason being is the modified ROM Flashes over the current ROM on the device, so the original ROM will be deleted anyways. The new ROM contains the updates for you, that's the advantage of androids. I recommend trying a few OS's before you pick the one for you stick with it. If you want to go stock there is a thread somewhere in the DEV section with the stock ROM just do some searching.
Make sure when you install a ROM to ;
Backup your device and make sure to keep a copy of the backup to your pc!
Boot into CWM Recovery or TWRP
Wipe data / factory reset
Wipe cache
Wipe dalvik cache
Install ROM from SD
Good Luck
Hi guys!
I got a G3 yesterday and decided to root it. I installed TWRP and decided to install Cloudy G3.
Immediately on boot, all services stop responding. There's a loop of popups saying things like "System UI has stopped responding." The same with download manager and other things. So I figured the rom didn't install properly. I went to my backup to restore it and TWRP doesn't have it listed. I looked in all directories I could (saved it initially to /sdcard/) but it's not there. The weird part is that when you click the restore button going into the list of your backups, my backup pops up for like a quarter of a second and goes away.
I decided to use TWRP's wipe function to do a system restore. It completed and now my android version is "Cloudy g3 2.5." So... System restore installed the rom? I'm just really confused at all of this. Anybody have any insight to the stuff I've mentioned?
it0ken said:
Hi guys!
I got a G3 yesterday and decided to root it. I installed TWRP and decided to install Cloudy G3.
Immediately on boot, all services stop responding. There's a loop of popups saying things like "System UI has stopped responding." The same with download manager and other things. So I figured the rom didn't install properly. I went to my backup to restore it and TWRP doesn't have it listed. I looked in all directories I could (saved it initially to /sdcard/) but it's not there. The weird part is that when you click the restore button going into the list of your backups, my backup pops up for like a quarter of a second and goes away.
I decided to use TWRP's wipe function to do a system restore. It completed and now my android version is "Cloudy g3 2.5." So... System restore installed the rom? I'm just really confused at all of this. Anybody have any insight to the stuff I've mentioned?
Click to expand...
Click to collapse
Did you use wipe before flashing the rom? If not that's Why you had the issue you didn't wipe. You MUST wipe when flashing a rom.
hyelton said:
Did you use wipe before flashing the rom? If not that's Why you had the issue you didn't wipe. You MUST wipe when flashing a rom.
Click to expand...
Click to collapse
Did not know that, and no I didn't. But I appreciate you letting me know that, probably some volatile information I should've been aware of.
May I ask why the device fixed the CloudyG3 rom when I did wipe it? I thought wiping through TWRP sends the phone back to factory settings, but it just fixed the rom and booted fine.
it0ken said:
Did not know that, and no I didn't. But I appreciate you letting me know that, probably some volatile information I should've been aware of.
May I ask why the device fixed the CloudyG3 rom when I did wipe it? I thought wiping through TWRP sends the phone back to factory settings, but it just fixed the rom and booted fine.
Click to expand...
Click to collapse
Your welcome
It wiped your current install, current rom being cloudy it reset it to factory settings. Doing a wipe won't put you back to stock.
hyelton said:
Your welcome
It wiped your current install, current rom being cloudy it reset it to factory settings. Doing a wipe won't put you back to stock.
Click to expand...
Click to collapse
Ah, so flashing the stock lg firmware would be the only way to send a device back to factory settings? I'm enjoying this learning process for sure.
it0ken said:
Ah, so flashing the stock lg firmware would be the only way to send a device back to factory settings? I'm enjoying this learning process for sure.
Click to expand...
Click to collapse
Correct
My XT1540/rooted/stock 6.0 ROM/ stock recovery now has an update available. I assume I can not accept this system update, even if I un-root my device. I do have a pre-rooted TWRP back up. I can reload that image, but my concern is the best way to get all my apps and data reloaded. I do have TB backups, but I thought that may not be a good option after system update. I am looking for advise how to proceed getting the latest system update and preserving all my current apps and data.
No offense, but did you Google it or search here? There are several tutorials in this device section and other similar Moto devices of the same generation that tell you different ways to do it...
Easy way... boot (not flash) TWPR, backup in TWRP, restore pre-root backup, accept OTA and allow it flash and fully boot, boot TWRP, flash your root of choice that you were using prior (Magisk or SuperSU), reboot and verify operation, then restore data partition backup you did prior to OTA, clear caches, and reboot.
This works 80% of the time... if your data partition is important then make an alternative backup.
acejavelin said:
No offense, but did you Google it or search here? There are several tutorials in this device section and other similar Moto devices of the same generation that tell you different ways to do it...
Easy way... boot (not flash) TWPR, backup in TWRP, restore pre-root backup, accept OTA and allow it flash and fully boot, boot TWRP, flash your root of choice that you were using prior (Magisk or SuperSU), reboot and verify operation, then restore data partition backup you did prior to OTA, clear caches, and reboot.
This works 80% of the time... if your data partition is important then make an alternative backup.
Click to expand...
Click to collapse
Thanks. I have read conflicting information on the use of Titanium Backup, and that was my main reason for my post. My understanding of your reply is that TB would not be a recommended choice to restore apps&data (using either update.zip or batch mode) and that I have an 80% chance of restoring user apps and data by flashing the /data partition from my pre-OTA TWRP backup. And yes, I will make a pre-rooted backup prior to rooting or restoring apps.
I never heard of Magisk and will read more. In the mean time I will stick with SuperSU unless there is strong advise to go with Magisk.
MrTooPhone said:
Thanks. I have read conflicting information on the use of Titanium Backup, and that was my main reason for my post. My understanding of your reply is that TB would not be a recommended choice to restore apps&data (using either update.zip or batch mode) and that I have an 80% chance of restoring user apps and data by flashing the /data partition from my pre-OTA TWRP backup. And yes, I will make a pre-rooted backup prior to rooting or restoring apps.
I never heard of Magisk and will read more. In the mean time I will stick with SuperSU unless there is strong advise to go with Magisk.
Click to expand...
Click to collapse
I dislike TiBU... It is best to reinstall from scratch each time if possible, if not, this is a simple security update to TWRP should suffice.
Magisk is good, and it appears to be the root method most ROMs are going to because with Magisk Hide and a few tweaks that are built in, the device can still pass SafetyNet API checks, and there is no special process for systemless installing (it is the only way it can be done with Magisk). But if you are on SuperSU now and want to restore the data partition, do NOT switch that way... Get clean ROM and flash Magisk then install Magisk Manager. It has it's own community here: https://forum.xda-developers.com/apps/magisk
I am not saying Magisk is superior, but it is quite versatile and most ROMs seem to be switching to it so devices can pass SafetyNet checks.
I was also thinking this would be simple. Pleasant surprise after almost a year and a half to get a security update. So I uninstalled SuperSU (Tried Full Unroot option & it failed, so then just uninstalled the app.....Looks like I may still be rooted), re-installed the stock recovery, and with absolutely no other modifications to this phone, performed the update. So it failed. I thought I was able to do this on my Nexus 4, but that was a while back, and I always did it with a file, not OTA; maybe that was just OS update, who knows. I was just looking for some security peace of mind while waiting for Nougat to become a bit more stable. If I am going to have to go through hoops to do this, then I guess I will just wait; not going to go through this twice. Besides, will it be another year for the next security update; heck, they are already 1 or 2 months behind already.
The answer is what others said, plus you can try flashing OTA updates with flashfire, and don't choose to wipe data.
Rohi09 said:
The answer is what others said, plus you can try flashing OTA updates with flashfire, and don't choose to wipe data.
Click to expand...
Click to collapse
Oh well. On a side note, always grateful for making Nandroid backups before I start playing around with anything though. Things were acting up after haphazardly trying various SuperSU options, so I had to do a restore.
These constant OTA update messages every few minutes that I have to keep canceling are brutal! I might have to install an app to kill them.
Rohi09 said:
The answer is what others said, plus you can try flashing OTA updates with flashfire, and don't choose to wipe data.
Click to expand...
Click to collapse
Are you saying OTA updates can be flashed successfully without unrooting.
MrTooPhone said:
Are you saying OTA updates can be flashed successfully without unrooting.
Click to expand...
Click to collapse
that's the idea, I have never tried it on moto g 2015 though. As far as I know every root solution had its own Uninstaller. which root interface do you use? magisk or supersu?
Rohi09 said:
that's the idea, I have never tried it on moto g 2015 though. As far as I know every root solution had its own Uninstaller. which root interface do you use? magisk or supersu?
Click to expand...
Click to collapse
I have SuperSU. It would be great to flash an OTA over my current system, but I have heard many reports including @pjc123 above where it did not work.
All my searches resulted in suggestions in going back to stock, accept OTA, then use TB or some other similar program to restore saved apps & data. Tomorrow I will try @acejavelin 's above suggested method of flashing the /data partition. If that does not work, I will try TB. I will report my progress.
MrTooPhone said:
I have SuperSU. It would be great to flash an OTA over my current system, but I have heard many reports including @pjc123 above where it did not work.
All my searches resulted in suggestions in going back to stock, accept OTA, then use TB or some other similar program to restore saved apps & data. Tomorrow I will try @acejavelin 's above suggested method of flashing the /data partition. If that does not work, I will try TB. I will report my progress.
Click to expand...
Click to collapse
you can flash unsu zip or magisk Uninstaller and try to install ota via flashfire, won't hurt trying, might save you some time.
acejavelin said:
No offense, but did you Google it or search here? There are several tutorials in this device section and other similar Moto devices of the same generation that tell you different ways to do it...
Easy way... boot (not flash) TWPR, backup in TWRP, restore pre-root backup, accept OTA and allow it flash and fully boot, boot TWRP, flash your root of choice that you were using prior (Magisk or SuperSU), reboot and verify operation, then restore data partition backup you did prior to OTA, clear caches, and reboot.
This works 80% of the time... if your data partition is important then make an alternative backup.
Click to expand...
Click to collapse
Another dumb question, I am in the process of installing OTA. When I loaded the pre-root rom, I did not see any option to clear clear caches. I did see a wipe data and cache option which I understand to be a factory reset. I know I have seen it before but can't find it, so where do I clear cache after restoring data partition?
MrTooPhone said:
Another dumb question, I am in the process of installing OTA. When I loaded the pre-root rom, I did not see any option to clear clear caches. I did see a wipe data and cache option which I understand to be a factory reset. I know I have seen it before but can't find it, so where do I clear cache after restoring data partition?
Click to expand...
Click to collapse
Another simple Google question...
Open TWRP, go to Wipes - Advanced, and select Cache and Dalvik cache (a misnomer today, it should be called ART cache) and swipe to wipe, then reboot.
Thanks to @acejavelin recommendations, I have successfully applied the latest system update to my XT1540. My steps were as follows:
Booted to TWRP (3.0.2-r5.img)
restored original pre-rooted ROM
rebooted, accepted system updates
backed up new pre-rooted ROM
installed SuperSU 2.62-3, rebooted
updated SuperSU to 2.79 via Playstore
restored /data partition from last saved rooted ROM
wiped Dalvik/ART Cache
Reboot system
took a while, a couple of minutes on “Hand stitched by Peter Crawly”, several minutes optimizing apps. The phone booted succesfully then I got an error message the update failed (which I hit OK) But looking at about phone, latest security patch is listed. Phone looks configured (apps, data, configuration) exactly as it was prior to the update.
Rebooted phone, all still seems fine.
Hello, how do I restore original pre-rooted ROM? When I made the backup I got a folder with 6 files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win
system.ext4.win.md5
system.info
None of them seems to be the .img file
bradmoss said:
Hello, how do I restore original pre-rooted ROM? When I made the backup I got a folder with 6 files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win
system.ext4.win.md5
system.info
None of them seems to be the .img file
Click to expand...
Click to collapse
Your are not going to see an img file. Once booted into TWRP, select Restore, navigate and select your original ROM. Those files you have listed are within the restoration directory that you select with TWRP. Just select the directory with TWRP.
Bad news, I could restore pre-TRWP image using that folder and aplied the update.
But now I am in a loop, it tries to install (again) the update and then boots to TWRP
Is there any way out of this loop?
Thanks!
no idea? Am I the sad owner of a bricked phone?
bradmoss said:
no idea? Am I the sad owner of a bricked phone?
Click to expand...
Click to collapse
You could try a factory reset if you're not worried about losing your data. A factory reset solves most of the problems, though I'm a little doubtful because a factory reset won't uninstall the new update (given that it installed in the first place).
bradmoss said:
Bad news, I could restore pre-TRWP image using that folder and aplied the update.
But now I am in a loop, it tries to install (again) the update and then boots to TWRP
Is there any way out of this loop?
Thanks!
Click to expand...
Click to collapse
If it boots to TWRP, sounds like you didn't have a clean pre-root ROM as you did not have stock recovery. Did you try deleting Dalvik and ART cache?
Hello,
I have a rooted Samsung J2 2016. I thought of getting Viper4Android and when I tried to install the drivers it just said drivers installed reboot your phone. I rebooted it 2 times but still it said driver 0.0.0.0 and would ask for permission for updating drivers again. Fed up of this I went to Link2SD app and uninstalled the app. As I had flashed the zip file for Viper, it erased the sound drivers(I think) and I couldnt get any audio through the ear phones so I decided to do a factory reset of the phone by flashing the latest firmware update(This usually removes all apps, TWRP and root from my phone). After I did the factory reset I noticed that all the apps that I had before were still thereconfused I ignored it and plugged in my headphones only to find a complete loss in bass. I tried to tweak the inbuilt equalizer but nothing came out of it. After restarting, bass would enable for a few seconds and then it would disable again. I dont know what to do now. How can I get back my deleted drivers(if they got deleted)?
P.S. I had taken a complete backup but it got erased from the SD card after I formatted it as portable storage( I had it enabled for adoptable storage through root essentials. This might be the reason why the phone didnt factory reset) :crying:
Sorry for the long post. Im a beginner at this. Any help would be appreciated. Thank you
Edit- I tried different earphones and different music players but no success
darshan1504 said:
Hello,
I have a rooted Samsung J2 2016. I thought of getting Viper4Android and when I tried to install the drivers it just said drivers installed reboot your phone. I rebooted it 2 times but still it said driver 0.0.0.0 and would ask for permission for updating drivers again. Fed up of this I went to Link2SD app and uninstalled the app. As I had flashed the zip file for Viper, it erased the sound drivers(I think) and I couldnt get any audio through the ear phones so I decided to do a factory reset of the phone by flashing the latest firmware update(This usually removes all apps, TWRP and root from my phone). After I did the factory reset I noticed that all the apps that I had before were still thereconfused I ignored it and plugged in my headphones only to find a complete loss in bass. I tried to tweak the inbuilt equalizer but nothing came out of it. After restarting, bass would enable for a few seconds and then it would disable again. I dont know what to do now. How can I get back my deleted drivers(if they got deleted)?
P.S. I had taken a complete backup but it got erased from the SD card after I formatted it as portable storage( I had it enabled for adoptable storage through root essentials. This might be the reason why the phone didnt factory reset) :crying:
Sorry for the long post. Im a beginner at this. Any help would be appreciated. Thank you
Edit- I tried different earphones and different music players but no success
Click to expand...
Click to collapse
You probably needed to make sure you had SELinux set to permissive mode, then V4A would probably install the driver and reboot correctly without having to do it again.
You have 2 options:
1) reflash your stock firmware or your custom ROM, whichever one you're using. This will replace what was removed when you flashed V4A zip.
Or
2) enable permissive mode and try V4A again.
Or if you'd like, you can flash your stock or custom ROM just to get things back to a clean start and then try installing V4A again in permissive mode and see if it works right this time.
By the way, when flashing with Odin, it doesn't erase user data unless what you're flashing includes an upgraded/downgraded bootloader. When flashing exactly what you had, it leaves your data intact.
This time, when you flash stock firmware via Odin, boot the device to recovery and factory reset from within recovery, this will wipe user data, then connect to Odin and flash firmware. This should return everything to like it came out of the box.
By the way, in android, the term "factory reset" does not mean flashing stock firmware, that's called "factory restore".
In android, the term factory reset is something completely different, in android, it means wiping user data and leaving only the stock software.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
You probably needed to make sure you had SELinux set to permissive mode, then V4A would probably install the driver and reboot correctly without having to do it again.
You have 2 options:
1) reflash your stock firmware or your custom ROM, whichever one you're using. This will replace what was removed when you flashed V4A zip.
Or
2) enable permissive mode and try V4A again.
Or if you'd like, you can flash your stock or custom ROM just to get things back to a clean start and then try installing V4A again in permissive mode and see if it works right this time.
By the way, when flashing with Odin, it doesn't erase user data unless what you're flashing includes an upgraded/downgraded bootloader. When flashing exactly what you had, it leaves your data intact.
This time, when you flash stock firmware via Odin, boot the device to recovery and factory reset from within recovery, this will wipe user data, then connect to Odin and flash firmware. This should return everything to like it came out of the box.
By the way, in android, the term "factory reset" does not mean flashing stock firmware, that's called "factory restore".
In android, the term factory reset is something completely different, in android, it means wiping user data and leaving only the stock software.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Thank you for replying. The problem is that I am running the stock touchwiz samsung ROM so SELinuxModeChanger doesn't work for me. I would like to go with the second option but I can't find any other method to make it permissive. Can you please help me with this? I dont want to do a factory reset cause talking the phone back to how it is will be a real pain and time consuming. Will just flashing the Viper file again do the job in any way?
Droidriven said:
You probably needed to make sure you had SELinux set to permissive mode, then V4A would probably install the driver and reboot correctly without having to do it again.
You have 2 options:
1) reflash your stock firmware or your custom ROM, whichever one you're using. This will replace what was removed when you flashed V4A zip.
Or
2) enable permissive mode and try V4A again.
Or if you'd like, you can flash your stock or custom ROM just to get things back to a clean start and then try installing V4A again in permissive mode and see if it works right this time.
By the way, when flashing with Odin, it doesn't erase user data unless what you're flashing includes an upgraded/downgraded bootloader. When flashing exactly what you had, it leaves your data intact.
This time, when you flash stock firmware via Odin, boot the device to recovery and factory reset from within recovery, this will wipe user data, then connect to Odin and flash firmware. This should return everything to like it came out of the box.
By the way, in android, the term "factory reset" does not mean flashing stock firmware, that's called "factory restore".
In android, the term factory reset is something completely different, in android, it means wiping user data and leaving only the stock software.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Also sir I found an old complete titanium backup on my laptop. So can it have the original drivers? If yes can I restore them using titanium and how?
I am sorry for asking so many questions but listening to music is what I do most of the times and I am feeling guilty for screwing up something that I like the most and that I can not restore it :crying:
darshan1504 said:
Also sir I found an old complete titanium backup on my laptop. So can it have the original drivers? If yes can I restore them using titanium and how?
I am sorry for asking so many questions but listening to music is what I do most of the times and I am feeling guilty for screwing up something that I like the most and that I can not restore it :crying:
Click to expand...
Click to collapse
What you need wouldn't be in a Titanium Backup file unless you backed up system apps and their data.
If you had a TWRP backup from before you installed V4A then you could use that. Otherwise than that, you'll have to flash stock firmware or at least manually reinstall the stock sound app and it's resources.
Best option to be sure you fix it without having to dig through anything is to flash stock firmware and start over and do it correctly the next time.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
What you need wouldn't be in a Titanium Backup file unless you backed up system apps and their data.
If you had a TWRP backup from before you installed V4A then you could use that. Otherwise than that, you'll have to flash stock firmware or at least manually reinstall the stock sound app and it's resources.
Best option to be sure you fix it without having to dig through anything is to flash stock firmware and start over and do it correctly the next time.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
The titanium backup is a complete system backup. I had chosen the backup all apps and system data option in Titanium and when I went through the backup files, I found the Sound Alive files in it. Those files were different from the ones which I currently have. So this is what I have in the end. If this is useful then fine. Otherwise there's no other option left I guess
darshan1504 said:
The titanium backup is a complete system backup. I had chosen the backup all apps and system data option in Titanium and when I went through the backup files, I found the Sound Alive files in it. Those files were different from the ones which I currently have. So this is what I have in the end. If this is useful then fine. Otherwise there's no other option left I guess
Click to expand...
Click to collapse
No, it's not a complete system backup because Titanium Backup can't do a complete system backup, the only part of system it can backup is system apps and their app data, it doesn't backup anything else from system. TWRP can make a complete system backup but Titanium Backup can't.
If you backed up the system apps themselves then yes, you can restore them but I wouldn't restore any of the app data that goes with those system apps.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
No, it's not a complete system backup because Titanium Backup can't do a complete system backup, the only part of system it can backup is system apps and their app data, it doesn't backup anything else from system. TWRP can make a complete system backup but Titanium Backup can't.
If you backed up the system apps themselves then yes, you can restore them but I wouldn't restore any of the app data that goes with those system apps.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I did a factory reset through TWRP and flashed it again. That did the trick. Thank you for all the help
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: