Does hard reset uninstall the custom recovery being installed? Just wanted to revert it back to original like a newly bought phone. Also wanted to locked to bootloader. Wanted to do these things because it went buggy when I started experimenting to root my phone thus it was all failures. Hoping for a informative or maybe a step by step guide reply to this. Thankyou
If you mean factory reset, that will not return you to the stock ROM. All a factory reset does is wipe user data.
Or if you're talking about the WIPE section in TWRP, if you select "system" it will just wipe the OS, and not leave anything in its place. Meaning you will no longer be able to boot into OS.
You should make a TWRP backup of the stock ROM before rooting. That way, you can easily restore to the stock unrooted ROM.
Otherwise, there are guides in this (M8s) section about how to return to the stock ROM.
Related
This may be a stupid question so please don't flame me for it but it's a simple and quick one.
If i do a factory restore on a rooted stock ROM for the Incredible, will i LOSE root and have to re-root??
If you do a Factory Reset, wipe, etc from recovery, you will not lose root, but will have to re-enter your accounts and the like when you re-boot. If you flash an original ruu, you will lose root and have to re-root.
If I am wrong on this, someone please correct me.
What if i do the factory restore from within the ROM itself instead of doing it from recovery?
Any difference there?
Predtechhacker said:
What if i do the factory restore from within the ROM itself instead of doing it from recovery?
Any difference there?
Click to expand...
Click to collapse
No, as said above, if you flash RUU back to stock, it puts the factory image on your phone. If you do a factory restore, it wipes all data from your phone and you need to reinstall everything. It will not change a custom rom back to a stock rom.
Excellent. Thanks man!
Damn, he's quick to respond. Ditto.
Last week i was running stock 1.26 with unlocked bootloader and rooted and i tried to flash a battery mod from a custom rom. After flashing, my device was stuck on the htc screen.
To recover from this, i relocked the bootloader and ran the appropriate ruu for my device.
I am now running 1.28 and the ruu for this is not yet available. What are my options to recover from a situation as above.
1/ Nandroid? I have never used this before (never needed to). Is this a backup that i can store on my phone to use to restore my device in this situation?
2/ Would storing a 1.28 custom rom on my device storage to flash suffice for this situation?
3/ Is there any simpler way to recover my device?
Any advice would be much appreciated.
Do a complete nandroid, tis backs up everything on your phone do it when it's fully working and all set up saves having to set it up again, so any time you have a boot loop issue, go into CWM and just restore your backup after doing a factory reset, wiping data cache and dalvik cache.
I have been playing around with the nexus 7 installing apps and adding a different recovery.
I would now like to perform one final wipe of the device, reset it, and then make my pristine backup. I'm currently using Clockworkmod recovery. What is the best way to return the 7 back to stock?
Should I just reset/erase using Clockworkmod recovery? Also, will I need to delete my old Clockworkmod backup if I do not want it anymore?
Any advice would be much appreciated.
Rick
C5Longhorn said:
I have been playing around with the nexus 7 installing apps and adding a different recovery.
I would now like to perform one final wipe of the device, reset it, and then make my pristine backup. I'm currently using Clockworkmod recovery. What is the best way to return the 7 back to stock?
Should I just reset/erase using Clockworkmod recovery? Also, will I need to delete my old Clockworkmod backup if I do not want it anymore?
Any advice would be much appreciated.
Rick
Click to expand...
Click to collapse
reset from recovery only resets the user data and depending on recovery, also the virtual sdcard.
It doesn't touch the /system files. You might have installed tweaks to the system. You might have installed root, changes to the slimport resolution, USB-OTG like stickmount may have made changes to debuggerd. None of these get reset with the reset from recovery.
The factory image blasts a factory image back onto the device, bootloader, recovery, kernel, rom, resets user data, etc.
So in your case if you really want to get back to stock before making a pristine backup, factory image is the better choice.
sfhub said:
reset from recovery only resets the user data and depending on recovery, also the virtual sdcard.
It doesn't touch the /system files. You might have installed tweaks to the system. You might have installed root, changes to the slimport resolution, USB-OTG like stickmount may have made changes to debuggerd. None of these get reset with the reset from recovery.
The factory image blasts a factory image back onto the device, bootloader, recovery, kernel, rom, resets user data, etc.
So in your case if you really want to get back to stock before making a pristine backup, factory image is the better choice.
Click to expand...
Click to collapse
Thanks, the new image is exactly what I want to do. I'm still a little confused about the relationship between the recovery and the image though. If I flash the image again, will I lose my custom recovery and just return to the stock recovery? Is it just like a computer that the image is going to configure the tablet exactly back to the stock image or will I still have the Clockworkmod recovery? I know I can easily reflash the Clockworkmod recovery so not a big deal.
Thanks again for the help.
Rick
C5Longhorn said:
Thanks, the new image is exactly what I want to do. I'm still a little confused about the relationship between the recovery and the image though. If I flash the image again, will I lose my custom recovery and just return to the stock recovery? Is it just like a computer that the image is going to configure the tablet exactly back to the stock image or will I still have the Clockworkmod recovery? I know I can easily reflash the Clockworkmod recovery so not a big deal.
Thanks again for the help.
Rick
Click to expand...
Click to collapse
Factory image flashes stock
1) bootloader
2) radio (for deb/LTE)
3) recovery
4) boot/kernel
5) system/ROM
6) wipes user data / virtual sdcard
7) wipes cache
So your custom recovery would be replaced with stock recovery.
sfhub said:
Factory image flashes stock
1) bootloader
2) radio (for deb/LTE)
3) recovery
4) boot/kernel
5) system/ROM
6) wipes user data / virtual sdcard
7) wipes cache
So your custom recovery would be replaced with stock recovery.
Click to expand...
Click to collapse
Great, thanks. This is exactly what I'm going to do.
Edit: Check this whole first post, because I have made some additional entries concerning failures and potential cures to things. I will update when my current encryption test is complete.
For the short version see the tldr at the bottom.
I have been trying different combinations of things all day in my last ditch attempt to get encryption working without needing to flash my original firmware back on from odin, since I hate the thought of how long it takes and what could go wrong.
The secret that I have worked out today is I install TWRP, wipe everything out, factory reset, wipe etc. Then install the rom, in my case it was my TWRP backup of my original firmware installed and then later CM11 M12, then immediately after flashing, reboot to download mode and flash the stock recovery image (I had to get a guide and use my linux VPS to turn the extracted recovery.img into a .tar.md5 and use that for flashing my original recovery. Then boot to recovery (now the genuine original recovery) and perform a factory reset. Then boot the phone up and the encryption works. Right now CM11 is at 38% encryption! Just before I started this off, I also had 100% success with encryption using my TWRP backup of a stock firmware install, using this same method. Once it is encrypted I will flash TWRP back on here as I did before and it should be good.
My theory (I am too burned out to test it at this point, I just want my phone working...) is that the issue is not whether you have TWRP installed, but whether the final factory reset (before booting up phone for usage) is performed by an official recovery or a third party recovery. So I bet it would work if you perform the factory reset and then immediately flash TWRP back on there and then boot up and perform the encryption.
Plus, in theory since I am using CM11 encryption, TWRP should be able to access /data which means I can keep this encryption and flash what ever rom I want using TWRP and upon booting it "should" just work. I tested this once before when I lucked out and got encryption working on some rom (I forget now which it was) but I was able to do a wipe with TWRP and install a different rom and the encryption still worked, still booted up fine.
Do you have any thoughts on this topic? Maybe I am reinventing the wheel...? I have not seen any of this referenced in any of the text or video guides I have been checking out. So I thought I would share this just in case. It might work for other samsung phones too.
STAND BY. The encryption did not work and I am trying a slight modification that is also proceeding. I am 19% on encrypting CM10.2. This time I did the usual TWRP wipes and then once wiped, Immediate flash of the original stock recovery (no OS install yet), then perform a factory reset and then flash TWRP again. Then I installed CM10.2 and skipped through the setup wizard and went straight to setting up encryption. Where usually it fails, it is actually performing the encryption. I have hopes that since the factory reset from the stock firmware's recovery was performed BEFORE the OS install, that it should... should work this time. I have a feeling the prior one failed because of doing a factory reset from one rom's recovery on a different rom's OS. So doing the factory reset before the OS install might be what will make it work. I will update soon.
Edit: It worked flawlessly... Booted up, authenticated, everything is fine. I am now running the same test with CM11 (M12) Also, I am not sure if this will work, but once I performed the final factory reset via the stock recovery (before re-flashing TWRP to begin OS install) I made a backup. My hope is that instead of reflashing and re-flashing back and forth, that the backup I made will have everything ready as if I had done a stock recovery based factory reset. If I decide to ditch CM11 I will test this theory out. I should also mention that the last test I mentioned with CM10.2 worked even though TWRP was presently still installed. So the presence of the stock recovery is not required, rather it is the factory reset from a stock rom being the final step required before the OS ROM install process.
Edit: There seems to be an issue with CM11. Twice now it has failed to work on CM11. I will try CM12 next, using my backup of a freshly official factory reset. If it fails I will do the whole process on 12 and see if it works and report back.
Edit: CM12 encryption by using the TWRP backup of a freshly factory reset (via stock recovery) failed. I am in the process of waiting for the first initial boot and setup wizard to complete of my second attempt at CM12 encryption via the full final step of actual stock recovery factory reset before CM12 installation via TWRP that is flashed after the stock recovery factory reset. I will update if this works. If it works and boots up correctly while encrypted, then it means a TWRP of a stock recovery factory reset is not adequate to replicate a true factory reset and the developers of TWRP should be made aware of this so they can enhance their own factory reset feature to allow encryption to work. If it doesn't work then there is something definitely wrong with CM11 and CM12 since both the stock firmware and CM10.2 encrypt using this full factory reset method. Stay tuned, wizard just came on screen...
Edit: Ok, weird... this time the encryption process has begun, whereas using my TWRP backup that was made after doing the stock factory reset did not get to this point, although the percentage counter started from 100% and counting... Right now the encryption is at 146% completed. That is very odd... I will report back if the encryption process actually ends up with a successfully booting phone or not, since CM11 failed at the booting phase. Before I save this edit, ne thing I am noticing is the progress percentage is going up rather fast compared to any other ROM. Right now it is at 177% and right now it is 179%, now it is 183% and I type fast... Stay tuned.
Edit: The encryption process worked and rebooted, asked for authentication and came up, however upon unlocking verious apps like CM bug reporter and whisper and others crash sometimes resulting in a OS loading screen and a fresh unlock needing to be performed.
tldr: When installing ANY rom, you need to wipe the file systems with TWRP or other similar recovery, then flash your stock firmware's recovery image (not the whole firmware, just the recovery, which means you need to extract the recovery.img from your flash file using 7zip and then follow these instructions: http://www.w0lfdroid.com/2013/04/android-how-to-convert-img-recovery-to.html to create a .tar.md5 file that odin can use to flash your recovery rom. (load odin, click AP or PDA and set your recovery tar.md5 and untick the two boxes that are always on by default. I use Odin v3.09). Then after you have wiped the file systems with TWRP (format data, then wipe the other mount points) then with your stock recovery perform a factory reset. Then flash TWRP or what ever custom recovery you use and just install your ROM, no other formatting or anything else, just install (not restore). Then the encryption will work, assuming there are no bugs in the rom that prevent it working on your handset, as seen on my handset with CM11 and the weird bugs with apps crashing on CM12.
So my recommendation is that the developer(s) of TWRP change the way they perform the factory reset, to emulate the actual process that a stock recovery uses, so that you do not need to keep reflashing your recovery images over and over when you need a fresh install.
Notes: CM11 M12 fails to boot, post successful encryption process, while CM12 nightly (18th March 2015) has bugs with apps crashing after successful bootup post encryption.
I have verified all this twice since. It is the stock recovery factory format that is needed before you install your ROM. I hope this helps the other people that I have seen having encryption problems.
Hey everyone. My phone has been running like crap lately and I have thought about doing a factory reset. I just had a few questions. If I did a factory reset I'm pretty sure I lose root, but what about the custom recovery?
Also, this is what I had in mind to do - but would you mind checking to see if it would be my best route please? I am going to install a custom rom on it. But just wanted to do a factory reset / install stock firmware first before I did it.
Download and install stock firmware. 10B I believe is what it is.
Root it again and put the bumped recovery back on it.
Install CM12 or another rom.
Is that pretty much what I should do?
Thanks!
mikewelch5 said:
Hey everyone. My phone has been running like crap lately and I have thought about doing a factory reset. I just had a few questions. If I did a factory reset I'm pretty sure I lose root, but what about the custom recovery?
Also, this is what I had in mind to do - but would you mind checking to see if it would be my best route please? I am going to install a custom rom on it. But just wanted to do a factory reset / install stock firmware first before I did it.
Download and install stock firmware. 10B I believe is what it is.
Root it again and put the bumped recovery back on it.
Install CM12 or another rom.
Is that pretty much what I should do?
Thanks!
Click to expand...
Click to collapse
If you do a factory reset (with the kdz tool, its the best way if you want to reinstall the stock firmware), you lose everything (root, recovery, etc..) because it will flash the phone completely.
I recommend you to take a look at this for all the thing that you need to do: http://forum.xda-developers.com/showthread.php?t=2785089
And make sure you never do a factory reset from within Android w/ a custom recovery like TWRP installed, otherwise your phone will end up in a continuous boot loop. There's no reason for you to go back to stock anyway, as you're planning on reinstalling CM12 or installing a different ROM. You'll be doing a factory reset (wiping System, Data, Cache, and Dalvik) from within TWRP before flashing anyway, so there's no need to go back to stock beforehand.
mikewelch5 said:
Hey everyone. My phone has been running like crap lately and I have thought about doing a factory reset. I just had a few questions. If I did a factory reset I'm pretty sure I lose root, but what about the custom recovery?
Also, this is what I had in mind to do - but would you mind checking to see if it would be my best route please? I am going to install a custom rom on it. But just wanted to do a factory reset / install stock firmware first before I did it.
Download and install stock firmware. 10B I believe is what it is.
Root it again and put the bumped recovery back on it.
Install CM12 or another rom.
Is that pretty much what I should do?
Thanks!
Click to expand...
Click to collapse
If you flash your phone with kdz, yes, like the guy above said you will lose both root and recovery. What I'm curious about is reason you want to do it? You already have custom recovery so if you want to do factory reset (that is wiping data and cache partitions) why not do it manually there?
And what is the point of it? As you said you will flash CM12 or another ROM, so that will basically do a factory reset, you will wipe all (system, data, cache) to install your new ROM...
Of course before flashing or wiping system partition with TWRP I recommend doing a backup just in case.
Thanks for the info everyone. The reason I wanted to do a clean factory install instead of just putting on CM12 is because if I didn't like it, I could just go back to a stock, rooted KK.
Like I said it has been acting up lately, so maybe a clean install of factory can help it. That way, if I don't like CM I can just restore my clean copy.
Where as now, if I didn't like CM I would have to restore my messed up backup.
But I will probably flash back to stock firmware, root it again and put a custom recovery on it again. Make a backup of that, then play around with some ROMS.
But once again, I appreciate the help!