Hi,
My moto one Action with stock firmware is stack at the Android One boot screen.
Is there a way to reset the system without loosing apps and data?
The recovery mode is not having the option to wipe the cache…
Flashing firmwares usually don't wipe data, unless it was triggered by a file, or an option. I doubt it'll be of help even if you have TWRP installed, cause the data partition may be encrypted.
If you have bootloader unlocked, you can use TWRP to take a backup of your files/apps.
Related
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.
Hello all,
My S3 currently has TWRP 2.7.0.1 recovery and CM11 installed. It was also previously encrypted.
Recently the gapps on my S3 have completely stopped working. New accounts cannot be added and the programs immediately crash upon starting. Deleting the app-data for these has had no effect.
While I can decrypt the phone for regular use, I cannot do the same in recovery to reinstall gapps. Consequentially, it appears that the best option would be to wipe out everything to get rid of the encryption. Unfortunately, it seems that you cannot flash a new ROM over an encrypted partition via recovery. I have reached the conclusion that Odin should be used to reformat everything.
Is this a correct understanding? And how would I go about doing this safely?
First, backup everything you can. Then try a factory reset. If this doesnt help, choose format data from recovery. (Formatting /data will wipe the internal sd card).
If all else fails, then go for the odin flash. From what I have seen though the factory reset or format should be sufficient.
Be very careful using Odin of you have a 4.3 or newer bootloader. You don't want to flash an incorrect modern or bootloader which can brick your phone.
Very true, always be careful of this. I dont usually mention it for Odin flashes though because Odin will recognize the versions and will refuse to flash. Its usually flashing via recovery that is the most dangerous in my experience. (But I have seen odin flashes go bad too, its kind of rare, but always be careful with what youre doing.)
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.
I jacked up my phone by disabling the wrong system app in an attempt to increase performance and now it wont boot past the Boost Mobile logo.
i cannot boot into safe mode, but I can get into recovery.
tried wiping the cache, no dice.
tried some phone recovery software from FonePaw, didn't help.
I am pretty certain I jacked up the Boost Launcher system app and it is now disabled which is preventing the phone from booting fully.
Is there a way to fix this without losing the data? most photos are already backed up to the cloud, but there is some that I would lose by doing a factory reset. Is there a way to extract the data from the device and then do a reset?
Berserker333 said:
I jacked up my phone by disabling the wrong system app in an attempt to increase performance and now it wont boot past the Boost Mobile logo.
i cannot boot into safe mode, but I can get into recovery.
tried wiping the cache, no dice.
tried some phone recovery software from FonePaw, didn't help.
I am pretty certain I jacked up the Boost Launcher system app and it is now disabled which is preventing the phone from booting fully.
Is there a way to fix this without losing the data? most photos are already backed up to the cloud, but there is some that I would lose by doing a factory reset. Is there a way to extract the data from the device and then do a reset?
Click to expand...
Click to collapse
Flash twrp recovery then do factory reset from twrp you will not lose any data in internal or external memory.
Not sure though it will fix the bootloop issue cuz if you deletet some system app factory reset won't bring it back you have to flash stock rom from odin.
I've been having issues with my phone so i decided to do a full wipe and factory reset. After restoring with my google account, i boot into twrp and put in my pattern, and it says it cannot decrypt data. booting into android shows my data decrypted. tested both on Android Pie and Q with the same result. Any ideas as to why this would happen? even with a full wipe?
you have to remove the twrp pin code has problem with the code always gives it as an error
YoshiFan501 said:
I've been having issues with my phone so i decided to do a full wipe and factory reset. After restoring with my google account, i boot into twrp and put in my pattern, and it says it cannot decrypt data. booting into android shows my data decrypted. tested both on Android Pie and Q with the same result. Any ideas as to why this would happen? even with a full wipe?
Click to expand...
Click to collapse
It's been a problem since May, just remove your screen lock pin in security before using TWRP.
Only way around this is flash-all April factory image, boot up then dirty update with the OTA in TWRP.
Don't think it's worth the hassle