Database Info

[Q] Will a phone Reset make me lose Root?

I'm having an issue with an app and I've tried everything I can think of to troubleshoot it, Uninstall/re-install. Turn phone off/on, restart phone.
I was thinking of trying a reset on my phone, but it's currently rooted/unlocked.
Will doing the reset under settings give me any issues?
Any help is greatly appreciated.
Thank you

If you have a custom recovery installed like twrp or cwm you can do a full wipe from there and it will essentially do the same thing.
sent from my VenomOne M8

No it wont.

I also have the same question. Did you do the reset? Lose root? What happened?
Sent from my HTC One

Roque13 said:
If you have a custom recovery installed like twrp or cwm you can do a full wipe from there and it will essentially do the same thing.
Click to expand...
Click to collapse
x_V.I.P.3.l2_x said:
No it wont.
Click to expand...
Click to collapse
Yes it will. And if you think it won't a little more elaborate post would be helpful...... ?????
I would not do a factory restore from Settings with a custom recovery installed. I have never tried this on the M8 but on the Transformer tablets that can get you into a nasty "forced reboot to recovery" loop.
If it's an app causing the problem, just do a Factory Wipe in recovery. In TWRP the Factory Wipe will wipe all your apps and their data (not your personal files in data/media though) and also cache and dalvik. Not sure how CWM handles that option....
Read the recovery log while it's running or save the log from the Advanced option and check afterwards which partitions the recovery wiped.
For good measure re-flash the rom and you should be good to go.

[HELP!] Not booting after stagefright update!

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.

Soft brick after restoring backup with TWRP

Ok... As you can see from this thread,
https://forum.xda-developers.com/on...en-restore-t3804734/post76832485#post76832485
I soft bricked my phone after trying to restore a backup in official TWRP.
I followed this tutorial https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
And jumped over to this tutorial https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558 per this post in the tutorial https://forum.xda-developers.com/showpost.php?p=76564290&postcount=5 note that this post points to another way of getting TWRP. The link I went to is how to install OFFICIAL TWRP.
And jumped back to the original tutorial for the rest. I'm scared to death now to try and test the restore functionality in TWRP. Has anyone successfully restored a backup? If so, what steps did they take to get the backup and what steps did they take restoring backup? What partitions did the check.mark during backup and what partitions did they check mark during restore? And do you need to do anything with changing the a/b slots????
Edited to add correct link to install official TWRP.

vinnievegas said:
Ok... As you can see from this thread,
https://forum.xda-developers.com/on...en-restore-t3804734/post76832485#post76832485
I soft bricked my phone after trying to restore a backup in official TWRP.
I followed this tutorial https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
And jumped over to this tutorial per this post in the tutorial https://forum.xda-developers.com/showpost.php?p=76564290&postcount=5
And jumped back to the original tutorial for the rest. I'm scared to death now to try and test the restore functionality in TWRP. Has anyone successfully restored a backup? If so, what steps did they take to get the backup and what steps did they take restoring backup? What partitions did the check.mark during backup and what partitions did they check mark during restore? And do you need to do anything with changing the a/b slots????
Click to expand...
Click to collapse
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.

mikex8593 said:
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
Click to expand...
Click to collapse
I'll try this and if this works and is in deed the process we need to follow until TWRP can just do what it's supposed to, then shouldn't this stuff be in the tutorials or have the OPs actually pulled this off like it's supposed to be?

vinnievegas said:
I'll try this and if this works and is in deed the process we need to follow until TWRP can just do what it's supposed to, then shouldn't this stuff be in the tutorials or have the OPs actually pulled this off like it's supposed to be?
Click to expand...
Click to collapse
Just too lazy to make an official thread, I guess. It will work.

mikex8593 said:
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
Click to expand...
Click to collapse
mikex8593 said:
Just too lazy to make an official thread, I guess. It will work.
Click to expand...
Click to collapse
So to be clear, I get the roms from here under signed flashable zips?
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244

vinnievegas said:
So to be clear, I get the roms from here under signed flashable zips?
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Click to expand...
Click to collapse
Yep. You can use the method with any of those zips.

I restored boot, system and data and ended in twrp loop. Flashing magisk revived it.
Sent from my ONEPLUS A6003 using Tapatalk

tdamocles said:
I restored boot, system and data and ended in twrp loop. Flashing magisk revived it.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Did you do it like he instructed above?
Flash rom
Flash TWRP
Restore boot, system, and data
Reboot?

vinnievegas said:
Did you do it like he instructed above?
Flash rom
Flash TWRP
Restore boot, system, and data
Reboot?
Click to expand...
Click to collapse
To tell you the truth I didn't even see the other post and was trying to get the renovate magisk module working in the process. It was the first time for me trying to restore a twrp backup because I borked something in the renovate magisk install. Like I said, I tried restoring boot, system and data and ended in a bootloop twrp situation. I figured what the heck, let's try flashing magisk root again and see what happens, and voila it work.

Yes me too twrp on oneplus 6 are buggy when I had restore all system part my Phone enter in bootloop [emoji58]
Actual Device : OnePlus 6 Past Devices : Galaxy S6, Xperia Z2, Huawei P7, Nokia 620

mikex8593 said:
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
Click to expand...
Click to collapse
Ok. Worked like a charm. Thank you so much. I tested all this without any lock screen security. Now I'm wondering if this procedure works with backups with lock screen security.

mikex8593 said:
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
Click to expand...
Click to collapse
black_file said:
Yes me too twrp on oneplus 6 are buggy when I had restore all system part my Phone enter in bootloop [emoji58]
Actual Device : OnePlus 6 Past Devices : Galaxy S6, Xperia Z2, Huawei P7, Nokia 620
Click to expand...
Click to collapse
tdamocles said:
To tell you the truth I didn't even see the other post and was trying to get the renovate magisk module working in the process. It was the first time for me trying to restore a twrp backup because I borked something in the renovate magisk install. Like I said, I tried restoring boot, system and data and ended in a bootloop twrp situation. I figured what the heck, let's try flashing magisk root again and see what happens, and voila it work.
Click to expand...
Click to collapse
Ok. Just tried what tdamocles did. But I've been wiping before restore. I then just restore and select system, boot, and data. I did not reflash TWRP. Rebooted and everything was good. Still had root and didn't need to reflash magisk. Was also able to reboot back into TWRP, so there was no need to reflash TWRP. But.... I think that is due to not flashing the stock room first. I'm assuming that if you reflash stock that you will indeed have to reflash TWRP. So, conclusion... If you restore system, boot, and data then no need to reflash TWRP and in my case no need to reflash magisk. Again, this is without lock screen security. My next test will be with lock screen security unless someone posts a negative result before I do.

vinnievegas said:
Ok. Just tried what tdamocles did. But I've been wiping before restore. I then just restore and select system, boot, and data. I did not reflash TWRP. Rebooted and everything was good. Still had root and didn't need to reflash magisk. Was also able to reboot back into TWRP, so there was no need to reflash TWRP. But.... I think that is due to not flashing the stock room first. I'm assuming that if you reflash stock that you will indeed have to reflash TWRP. So, conclusion... If you restore system, boot, and data then no need to reflash TWRP and in my case no need to reflash magisk. Again, this is without lock screen security. My next test will be with lock screen security unless someone posts a negative result before I do.
Click to expand...
Click to collapse
You will not be able to get past encrption if you decrypt in TWRP and restore. It essentially forgets encryption key.

mikex8593 said:
You will not be able to get past encrption if you decrypt in TWRP and restore. It essentially forgets encryption key.
Click to expand...
Click to collapse
Update...
Just performed a backup with lock screen security and was able to restore the backup choosing system, boot, and data. No reflashing of TWRP or magisk. Not sure if needed but I've been performing basic wipe before all my restores. Still able to boot back into TWRP and still had root.

mikex8593 said:
You will not be able to get past encrption if you decrypt in TWRP and restore. It essentially forgets encryption key.
Click to expand...
Click to collapse
Check my post above. I edited it to quote you.

I must also note that I'm using official TWRP. I edited my first post to reflect the link I used when jumping out if the tutorial and back.

vinnievegas said:
Update...
Just performed a backup with lock screen security and was able to restore the backup choosing system, boot, and data. No reflashing of TWRP or magisk. Not sure if needed but I've been performing basic wipe before all my restores. Still able to boot back into TWRP and still had root.
Click to expand...
Click to collapse
Nice.

I have restored from twrp a couple times now with no problem.. I did get the message saying can't mount system or something like that, ok I went into the mount options and mounted system after that the restore worked perfectly and I could boot back into the rom and back into twrp after.

Restored mine yesterday too, all files checked when backup, deleted lockscreen settings before, few bootloops at the beginning, until phone changed slot, then booted into system. Cheers!

primus19 said:
Restored mine yesterday too, all files checked when backup, deleted lockscreen settings before, few bootloops at the beginning, until phone changed slot, then booted into system. Cheers!
Click to expand...
Click to collapse
Not necessary to check all partitions. This only results in a huge nandroid file.

How to perform a clean install?

How to do a clean install(no rom installed just recovery)? I want to format everything and flash my rom thru otg. Shud I wipe everything when I boot to recovery?

I think internal storage is the correct option then though it also removes all media on the device. Otherwise clear system, data, cache, bootloader, dalvik. Then install the rom from external source.

Should I flash from fastboot the recovery(twrp)? It might get wiped once the wipe everything.

I have same doubts....

Mord0rr said:
I have same doubts....
Click to expand...
Click to collapse
So do I... You necro'd a 8 month old thread...

I tried to go through few thereds however I was unable to find an answer.
I'm still on 5.11 oreo a d official TWRP. I would like to update to newest pie, however I would go for clean flash.
How should I do it?
I already backed up all app+ data using titanium.
Should I just go to TWRP
1. Factory default
2. Wipe all
3. Wipe system. Data, davlik and cache
4 flash latest pie and don't reboot
5 reboot to twrp
6 flash twrp
7 reboot to TWRP and flash magisk
It it right?
Thank you

netgar said:
I tried to go through few thereds however I was unable to find an answer.
I'm still on 5.11 oreo a d official TWRP. I would like to update to newest pie, however I would go for clean flash.
How should I do it?
I already backed up all app+ data using titanium.
Should I just go to TWRP
1. Factory default
2. Wipe all
3. Wipe system. Data, davlik and cache
4 flash latest pie and don't reboot
5 reboot to twrp
6 flash twrp
7 reboot to TWRP and flash magisk
It it right?
Thank you
Click to expand...
Click to collapse
Swap 5 and 6

Flashing this phone looks like sorcery....
Miss all days we could go to TWRP, erase all **** and then just flash rom. Period.
Now, doing this can even brick the dam phone.
It sucks!
EDIT*
Did Nuke 9.0.5 and install fresh 9.0.3.:angel:

Mord0rr said:
Flashing this phone looks like sorcery....
Miss all days we could go to TWRP, erase all **** and then just flash rom. Period.
Now, doing this can even brick the dam phone.
It sucks!
EDIT*
Did Nuke 9.0.5 and install fresh 9.0.3.:angel:
Click to expand...
Click to collapse
That also happened to me. I do not know how to go to another custom ROM from another custom ROM without going to MsmDownloadToolV4 to unbrick my device. Actually i did unbrick my device twice already because of trying various custom ROM.
Also, is there a way to just restore from recovery then flash another custom ROM. Then if we want to change custom ROM again we can just restore from recovery again then flash another custom ROM?
Please help us guys. Thanks.

Has anyone been able to boot a TWRP restore on this phone?

I break my system a lot (currently testing which of my favorite Xposed modules work with Pie) . I've had to set up from scratch like 6 times in the past week. Every TWRP restore results in a boot loop, both custom and stock. Has anyone made it work and, if so, how? It surprises me that our TWRP is official if it can't restore a backup.

Encrypted?

arkansawdave74 said:
I break my system a lot (currently testing which of my favorite Xposed modules work with Pie) . I've had to set up from scratch like 6 times in the past week. Every TWRP restore results in a boot loop, both custom and stock. Has anyone made it work and, if so, how? It surprises me that our TWRP is official if it can't restore a backup.
Click to expand...
Click to collapse
I'm having the same problem. This is my first a/b device and everything I thought I knew after flashing ROMs for years just doesn't seem to work on this architecture. Like you said twrp backup restore always results in a bootloop. Also any full custom ROMs I've tried appear to overwrite twrp and install its own recovery. Even gsi's don't boot and then twrp freezes and back to stock I go. This thing has me stumped.

Skippy12359 said:
I'm having the same problem. This is my first a/b device and everything I thought I knew after flashing ROMs for years just doesn't seem to work on this architecture. Like you said twrp backup restore always results in a bootloop. Also any full custom ROMs I've tried appear to overwrite twrp and install its own recovery. Even gsi's don't boot and then twrp freezes and back to stock I go. This thing has me stumped.
Click to expand...
Click to collapse
I noticed when installing RR that it actually needs that Lineage recovery to factory reset after the install. A TWRP factory reset wouldn't help it, and it wouldn"t boot after the install. Funny how they try so hard to stop us tinkerers, then steal all our cool ideas for their stock ROMs. I see Linux phones in my future.

I wonder if a factory reset with that Lineage recovery would help after a TWRP restore? Next time I may try that.

Damn! I just got it. I'm typing this on a restored crDroid Official. The boot.img is in ramdisk, so only backup system and data. Yay!

WoKoschekk said:
Encrypted?
Click to expand...
Click to collapse
Just saw this. No. I had flashed dm-verity. Good thinking.

arkansawdave74 said:
Damn! I just got it. I'm typing this on a restored crDroid Official. The boot.img is in ramdisk, so only backup system and data. Yay!
Click to expand...
Click to collapse
So your saying because recovery is in the boot image that we need only to backup system and data and then a restore of same will not go into a bootloop? That would mean the problem has been backing up and then restoring the boot image. System as root and no recovery partition is just hard to grasp at this point. For me restoring data in a backup of stock results in twrp error 255.

Skippy12359 said:
So your saying because recovery is in the boot image that we need only to backup system and data and then a restore of same will not go into a bootloop? That would mean the problem has been backing up and then restoring the boot image. System as root and no recovery partition is just hard to grasp at this point. For me restoring data in a backup of stock results in twrp error 255.
Click to expand...
Click to collapse
I spoke too soon. This was the 1st time I'd flashed dm-verity on the install. That's why it worked. It won't work if /data is encrypted. I just made a backup with boot as well and it restored fine.

arkansawdave74 said:
I spoke too soon. This was the 1st time I'd flashed dm-verity on the install. That's why it worked. It won't work if /data is encrypted. I just made a backup with boot as well and it restored fine.
Click to expand...
Click to collapse
Which version of dm- verify are you using and what steps did you take to get crdroid to boot?

Skippy12359 said:
Which version of dm- verify are you using and what steps did you take to get crdroid to boot?
Click to expand...
Click to collapse
I'm not sure where I got it Or else I would link you. But this is the one I'm using this one. I flashed it after formatting /data and also after installing the ROM. One of those is proper, but I couldn't remember. I think it's supposed to be after you install, but before 1st boot.
https://www.mediafire.com/download/uxldj5okanllfza

arkansawdave74 said:
I'm not sure where I got it Or else I would link you. But this is the one I'm using this one. I flashed it after formatting /data and also after installing the ROM. One of those is proper, but I couldn't remember. I think it's supposed to be after you install, but before 1st boot.
https://www.mediafire.com/download/uxldj5okanllfza
Click to expand...
Click to collapse
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.

Skippy12359 said:
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.
Click to expand...
Click to collapse
Yup. I've restored it twice and made another with boot included and it booted as well. I hope it works with RR too, but I've got a helluva headache. I may stop messing with it for now.

Oh, I had wiped dalvic (actually ART), system, and data. I don't think boot was an option during wipe.

You know, I've only had one device before thar force encrypted, and back then, TWRP couldn't decrypt /data except by formatting. Now it can. That's why I didn't suspect it was an encryption issue.

I was still using a Galaxy S5 with crDroid 7.1.2 built by me until last week. It died, may it rest in peace.

Skippy12359 said:
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.
Click to expand...
Click to collapse
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.

arkansawdave74 said:
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.
Click to expand...
Click to collapse
My goal was to have twrp backup of stock pie which is really great in my opinion and also be able to flash Q gsi's like I do on my Moto g6. So far any backup restore of stock just bootloops and any gsi just hangs at boot logo or boots back to recovery.

arkansawdave74 said:
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.
Click to expand...
Click to collapse
It does appear to be an encryption issue with a stock rom TWRP backup restore not booting. Formatting data in TWRP and rebooting always results in a bootloop. Until I can format data to remove encryption and get it to boot and the security setting says it's not encrypted, I don't think a backup will ever boot. Out of ideas at this point.

Skippy12359 said:
It does appear to be an encryption issue with a stock rom TWRP backup restore not booting. Formatting data in TWRP and rebooting always results in a bootloop. Until I can format data to remove encryption and get it to boot and the security setting says it's not encrypted, I don't think a backup will ever boot. Out of ideas at this point.
Click to expand...
Click to collapse
For stock, I wonder if you could boot TWRP after all those fastboot commands and flash dm-verity before booting stock. You may be able to keep stock from encrypting. I don't know for sure though.