Hi everyone!
Yesterday after entering boot loops after trying to install the Xposed module from Magisk, I reinstalled the latest Oxygen OS zip via TWRP's "Wipe / Swipe to Factory Reset". When the phone booted in "hello, new user" mode, I saw there were still files from before under sdcard/, so, to be sure, I also tried to do a Factory reset from within OOS Settings / System. When the phone booted in "hello, new user" mode, I noticed there were still files from before under sdcard.
I re-flashed Magisk, installed a few things, did a backup via TWRP. Worked on setting up the phone for two more hours (didn't install any Magisk module, only software from the Play store), rebooted the phone to check everything was okay… boot loop!
Using the backup, I was able to reset the phone to the state of before wasting these two hours… But these boot loops seem so fickle, so random, that I wonder if I'm missing something with the factory reset, if maybe there is a more brutal reset that would erase all trace of activity after the state where the phone was after unlocking the bootloader.
Is there a way to do a more complete "factory reset" than what I've done? I see that Magisk has an "Advanced Wipe", if I checked all the box would that do it? Or is that a bad idea because some important OOS recovery files would vanish. Which "Advanced Wipe" options should I check? If I follow that procedure, will I be able to reinstall TWRP and Magisk via ADB?
Really needing some expert insight, I feel very lost!
Thanks in advance!
who ah way said:
Hi everyone!
Yesterday after entering boot loops after trying to install the Xposed module from Magisk, I reinstalled the latest Oxygen OS zip via TWRP's "Wipe / Swipe to Factory Reset". When the phone booted in "hello, new user" mode, I saw there were still files from before under sdcard/, so, to be sure, I also tried to do a Factory reset from within OOS Settings / System. When the phone booted in "hello, new user" mode, I noticed there were still files from before under sdcard.
I re-flashed Magisk, installed a few things, did a backup via TWRP. Worked on setting up the phone for two more hours (didn't install any Magisk module, only software from the Play store), rebooted the phone to check everything was okay… boot loop!
Using the backup, I was able to reset the phone to the state of before wasting these two hours… But these boot loops seem so fickle, so random, that I wonder if I'm missing something with the factory reset, if maybe there is a more brutal reset that would erase all trace of activity after the state where the phone was after unlocking the bootloader.
Is there a way to do a more complete "factory reset" than what I've done? I see that Magisk has an "Advanced Wipe", if I checked all the box would that do it? Or is that a bad idea because some important OOS recovery files would vanish. Which "Advanced Wipe" options should I check? If I follow that procedure, will I be able to reinstall TWRP and Magisk via ADB?
Really needing some expert insight, I feel very lost!
Thanks in advance!
Click to expand...
Click to collapse
Hello, format internal storage within twrp deletes everything off your /sdcard but does not touch system, data, vendor for example.
You're still able to use fastboot/adb cause you do not delete the bootloader:good:
strongst said:
Hello, format internal storage within twrp deletes everything off your /sdcard but does not touch system, data, vendor for example.
You're still able to use fastboot/adb cause you do not delete the bootloader:good:
Click to expand...
Click to collapse
Thank you for your reply!
Just to be sure I understand, are you suggesting that a strong way of getting a good Factory Reset would be:
TWRP / Wipe
[ ] Dalvik / ART Cache
[ ] System
[ ] Vendor
[ ] Data
[x] Internal Storage
[ ] USB Storage
then (if TWRP is gone):
adb devices
adb reboot bootloader
fastboot boot twrp-3.3.1-52-guacamole-unified.img
In TWRP, install twrp-3.3.1-52-guacamole-unified-installer.zip
In TWRP, install OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
Do the phone's "Welcome, user" setup
Flash Magisk
Does that sound right?
who ah way said:
Thank you for your reply!
Just to be sure I understand, are you suggesting that a strong way of getting a good Factory Reset would be:
TWRP / Wipe
[ ] Dalvik / ART Cache
[ ] System
[ ] Vendor
[ ] Data
[x] Internal Storage
[ ] USB Storage
then (if TWRP is gone):
adb devices
adb reboot bootloader
fastboot boot twrp-3.3.1-52-guacamole-unified.img
In TWRP, install twrp-3.3.1-52-guacamole-unified-installer.zip
In TWRP, install OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
Do the phone's "Welcome, user" setup
Flash Magisk
Does that sound right?
Click to expand...
Click to collapse
Generally the factory reset does all too need(from android settings). Why theres something left of your device I don't know.
But I meant format internal storage, not wipe internal storage.
So reboot to twrp - wipe - format and follow the instructions reading the hints.
Again: that does not wipe your twrp, system, system data only the internal storage like music, photos etc.
For installation, it's OK what you wrote
Thank you very much, @strongst.
If I understand, that "Format" option that you suggested is what gets rid of all the personal files. Then to Factory Reset, I can either flash via TWRP, or use adb.
At the moment I am thinking that like you suggested the phone is actually okay after the standard Factory Reset — and that the earlier boot loop was created by one specific piece of "bad software". So I am reinstalling things little by little, and doing TWRP backups after every 15 minutes of set-up. That way if the phone enters a boot loop, I will be able to restore and to narrow it down, and check on the forum if others have the same problem. Does this make sense to you?
Wishing you a great week!
who ah way said:
Thank you very much, @strongst.
If I understand, that "Format" option that you suggested is what gets rid of all the personal files. Then to Factory Reset, I can either flash via TWRP, or use adb.
At the moment I am thinking that like you suggested the phone is actually okay after the standard Factory Reset — and that the earlier boot loop was created by one specific piece of "bad software". So I am reinstalling things little by little, and doing TWRP backups after every 15 minutes of set-up. That way if the phone enters a boot loop, I will be able to restore and to narrow it down, and check on the forum if others have the same problem. Does this make sense to you?
Wishing you a great week!
Click to expand...
Click to collapse
It's a good way to break a potential boot loop issue down, time consuming, but worth the effort in case it boot loops
Related
SuperMan-Rom V1.8.1 Aroma - AP will not boot (integrity verification failed)
On My S7 edge, thought I'd give it another go at trying to root since this rom claims to be almost stock with an option to get rid of all the samsung rubbish (like s-voice) that you don't use ever.
Followed all the steps to root, ON STOCK OS, entered developer mode, allowed OEM, allowed USB debugging, turn off verify installs by USB abd. Now It seems the phone is prepped and ready to go.
Flashed TWRP with latest ODIN 3.11, made a backup of stock OS, back in download mode and flashed required bootloader and modem (BL and CP), boot again into recovery to flash AP (SuperMan-Rom_SM-G93XF_V1.8.1.zip). Went through all the process and it seems fine until 1st boot.
***Every try is showing "Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."***
Have I Done something wrong to be showing this error every time????
I had the same error message. The cause was that my device was encrypted. TWRP can't handle encryption on the S7 yet. Reboot into TWRP and look at the logs. If it says it couldn't mount /data, then this is probably the same issue I had.
To fix it, I restored the backup OS from TWRP, made a backup of all apps and data to external SD using Titanium Backup and wiped the encrypted partition in TWRP (which removes the encryption and all data). There may be better ways, but this one worked for me.
@Davebnly You need to take backup of the Internal Storage data and then do a wipe using TWRP, Since TWRP cannot handle the Samsung's Encryption the only way to bypass this is by formatting again. This is already mentioned in the Official TWRP Installation post here.
I have this same error after flashing a custom ROM. I did not take a backup of the old stock ROM as it's a new phone and I didn't think I needed to!
Can anyone tell me, if I flash the stock ROM will it let me into the device again?
Is there anyway to wipe the encrypted drive without installing stock ROM?
*UPDATE: I just logged into recovery and did a factory reset and it loaded the custom ROM. Not as lengthy a solution as I expected!
Do these exact steps, Do not miss.
1. Reboot to recovery.
2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes"
3.Go to Reboot and Reboot back to recovery.
4.Download DM Verify Disabler https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ , Get the latest.
5.Copy in to the phone and flash it.
6.Go to Reboot and Reboot back to recovery.
7.Now Flash any rom as you wish.
8.Make Sure to Wipe Dalvik, Cache after.
Enjoy!!
Shameera_N said:
Do these exact steps, Do not miss.
Click to expand...
Click to collapse
Man, you just saved my life!
Thanks you very much.
Shameera_N said:
Do these exact steps, Do not miss.
1. Reboot to recovery.
2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes"
3.Go to Reboot and Reboot back to recovery.
4.Download DM Verify Disabler , Get the latest.
5.Copy in to the phone and flash it.
6.Go to Reboot and Reboot back to recovery.
7.Now Flash any rom as you wish.
8.Make Sure to Wipe Dalvik, Cache after.
Enjoy!!
Click to expand...
Click to collapse
Hi, I'm sorry but what does all that mean? Reboot to recovery??? The only option on my phone is the button to RESET DEVICE and I have two weeks worth of photos and videos that I have not backed up yet! Please help!!! FYI, I have the same exact message telling me to erase all my data because I need to reset my device. Nooo, I am so scared right now.
About two weeks ago just before CyanogenMod's announcement of its closure I updated my Moto G2015 (1GB) to the latest nightly, which was CM14.1 released on the 25th of December, with its corresponding GAPPS version also released on the 25th of December (ARM, android 7.1, Full)
Yesterday the 7th of January my Google Apps decided that they didn't want to open, at first I thought it was just updating and since my battery was low I plugged in my device, I later realised that my device randomly went to a boot loop and stayed there. I grew impatient so I restarted the phone and went to the Recovery Mode (To Re-Flash the ROM), but to my annoyance the recovery (TWRP) just stayed on the 'Teamwin' logo forever, it would randomly go black then return to that logo. infuriated I turned on my phone and went to backup/reset and clicked 'factory reset'. it annoyingly booted me into recovery to reset the device, which of course I couldn't do.
Now the simple answer would have been for me to go and wipe the cache and data from 'google play services' and or 'launcher3' but I did, either it always shows 'calculating' preventing me from clicking 'manage space' or clearing 'cache' or when it did finally show, after I did click the button for the cache and or data to be cleared it would say 'calculating', and a quick check would discover that nothing was actually cleared.
Kind Regards, and Thank You to any help recieved,
NotSoGreat
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
acejavelin said:
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
Click to expand...
Click to collapse
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
NotSoGreat said:
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
Click to expand...
Click to collapse
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
I'll try now.
acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
Right, so I reinstalled and flashed the latest version TWRP, when I opened into it, it took about 1 minute before it opened up, it ran a quick operation that I just glimpsed, it looked like it was wiping cache and user data, my phone was rebooted and I was right, my phone had been reset for the second time today (I'm almost a pro at reinstalling all my apps). I rebooted into the recovery and Look and Behold, it was working.
Thanks slot for your help and time.
Okay, I'm not sure if this entirely the right place. Have updated to Viper 2.1.0. Rebooted my phone, as I do each morning. It came up with needing to to enter a decryption key, ie; my password. Did said & it failed saying that data is corrupt. TWRP can no longer read the data portion either. Therefore can't wipe it in TWRP.
Is there a way to format or wipe the data partition through either fastboot or adb?
Factory reset but your data will be gone.
Random Pinenut Joy said:
Okay, I'm not sure if this entirely the right place. Have updated to Viper 2.1.0. Rebooted my phone, as I do each morning. It came up with needing to to enter a decryption key, ie; my password. Did said & it failed saying that data is corrupt. TWRP can no longer read the data portion either. Therefore can't wipe it in TWRP.
Is there a way to format or wipe the data partition through either fastboot or adb?
Click to expand...
Click to collapse
Try this, Venom helped with it a while ago and it worked, you will just have to re activate smart lock in google setting.
TWRP-Advanced-File Browser.
Navigate to /data/system and delete the locksettings.db.
I got my phone back from HTC after repair my phone screen and they wiped my custom rom and recovery but still have unlocked bootloader and restore oreo 8.0.
I managed to re-install twrp and tried to install a customed rom and experienced the same "decryption unsuccessful". But there is no lockingsettiings.db in the folder.
I will later try this method and report.... been a frustrating day....
=https://forum.xda-developers.com/showpost.php?p=59685278&postcount=3
hey all. recently i tried to use hwota 8 to go from emui 8 china to emui 8 india. during the processs where it askd for bootloader unlock code (i used change location) it failed (remote password wrong). so i disconnected and manually booted to fastboot and unlocked my bootloader. but now the device wont boot, its stuck on your device is booting screen. i cant enter fastboot, erecovery or bootloader, however when i connect it to my pc sound plays. please help me anyone i am worried i cant also use dload
@Ramesh006 can you help me out?
Fixed. A while ago actually. Posting so that anyone in the same situation can ask
Good idea is writing Solution whitout waiting another in same condition...
Fixed. A while ago actually. Posting so that anyone in the same situation can ask
Click to expand...
Click to collapse
I have the same situation . what Solution ????
When you say same do you mean exactly same like no fastboot, recovery etc. And did it happen after HWOTA 8. Please tell me exactly what happened so I can guide you better
MadDog.76 said:
Good idea is writing Solution whitout waiting another in same condition...
Click to expand...
Click to collapse
+1
Oh well. If you want guide then sure. Here you go.
First of all let your battery drain completely. Once battery is dead. Plug your phone into charging and as soon as it shows three options boot screen quickly press Volume Up to boot into recovery. It will boot TWRP. Only if you tried via HWOTA 8. Read OP to know complete story. Now once in TWRP keep your phone on charging and don't let it shutdown. In TWRP go to Wipe and Format Data. Do it one to two times. Now go to Advanced Wipe and individually select each of the following one by one.
Cache
Dalvik Cache
Data
Internal
System.
First select repair file system and then after it repair wipe it individually. Then do a collective wipe. One or two Swipe to factory reset. After this cleansing flash firmware for Oreo of the build you were trying to go-to via Hurupdater. Search for it and follow exact guide. After that select Reboot Phone and when it's powering on, you should get three options menu. Press Volume Up to enter erecovery. This time you will boot normal recovery. Factory reset and then Format cache. Reboot system. First boot will take time. Be patient.
After you reboot you will notice several apps missing and themes not working as well as pinkish wallpaper instead of purple one. To fix flash any Oreo Compatible TWRP or the TWRP form Elemental ROM thread. Go-to wipe and format data. Then advanced wipe and select Data Internal System Cache and Dalvik. Wipe and then reflash Firmware via Hurupdater. After it finishes, reboot system and then reboot into stock recovery. Perform factory reset and then format cache. Reboot.
Installed Lineage 18.1 OS, TWRP 3.6.0_11-0 and Magisk, booted system, added PIN and fingerprints, all was good. Booted back into TWRP and made a full backup of all partitions. Tried a test restore of Super and Data partitions. Upon reboot, I get the lineage splash/boot screen, then "phone is starting" forever. From reading around, this is due to the system trying to access encrypted data. Questions: 1) I'd like to be able to use TWRP for two things: a) restoring to a new device should this one break, and b) reverting back to previously backed up state of operation on the same device. What partitions should I be restoring for each of these? 2) Is there a fix or proper method to make restorable backups using TWRP?
Exactly the same situation. And have exactly the same questions.
Had the same problem, wiped data, repaired data file system, rebooted into system to disable the pin. Then restored my TWRP data backup again, now it boots into system, just had to reboot twice because the gestures and staturbar didn't work first. Now I just have to tweak some little details again to get it how it was.
Didn't solve my main problem though, SMS not working. Wiped and repaired data again, now it works. Welp, guess I have to set it all up again from here.