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.
Related
QI am running rooted stock 4.1.1 with TWRP 2.4.3.0. Recently I have encountered a situation where Chrome sends the unit into a spontaneous reboot. Apparently, going into settings-->apps also produces a reboot. Otherwise the unit functions nominally and rooted apps run with appropriate root permission. If I use the stock browser, I can even access the web.
In an effort to try to clean things up, I decided to restore a nandroid, and discovered, much to my chagrin, that even though TWRP reports the nandroid has been restored, nothing whatsoever has changed. (Interestingly, the "data" portion takes 0 seconds, obviously suggesting that it isn't restoring the data partition at all). The unit is precisely as it was before I rebooted. In fact, even when I wipe cache, dalvik, system AND data, even factory reset, a reboot gets me precisely the exact same system as beforehand, even if I don't restore any nandroid. I am unlocked, with firmware 10.4.2.20. I even tried to flash the newest TWRP (2.6.0.0) and fastboot reported that it took, only to boot to recovery and see I'm still staring at 2.4.3.0.
It's as though the unit has write protected itself.
Update: Tried again with blob instead of img file which worked. Factory reset then flashed surdu_petru's deodexed stock and problems vanished.
So, my previous post was a bit too optimistic. I've managed to get TWRP onto my phone, but when I went to actually load a custom ROM into it, I found that it couldn't read anything from my sdcard.
I'm having what appears to be a common problem: when I boot into Recovery, TWRP asks for a password. When I cannot provide it (because I have no idea what it is), TWRP is unable to access the data partition. Apparently, the partition is encrypted and I have no way to de-crypt it.
I've found dozens of other posts by users having this problem and the solution everyone is giving is to fully wipe the data partition and start over. But I *can't* wipe the data partition, because TWRP can't access it and fails almost immediately. I have tried a multitude of options, including:
* Installing old versions of TWRP - same behavior; asks for a password, fails to wipe/format the data partition.
* Installing ClockWork's recovery - same thing; fails to format/wipe the data partition
* Flashing back to stock recovery, using that to format my data partition; this worked fine but as soon as I put TWRP back, the problem came back.
On my last attempt, I used the stock recovery to completely wipe the data partition, and made absolutely sure that it never booted into anything but Download or Recovery modes after that. I was hoping that would prevent the stock software from ever re-encrypting the data, but somehow, when I booted TWRP, it still can't read my partitions. Note that my phone itself is not "encrypted" as far as the Settings application is concerned, but apparently Android is doing something behind the scenes anyway. There doesn't seem to be any option in the stock settings to turn off this encryption.
Is there any hope for getting a custom ROM onto this phone?
Thanks for the help!
Any solution? I'm running into the same issue where TWRP is asking for a password.
Hi,
I have tested the liquidremix rom which is great, but I still wanted to go back to my stock OSS
So I started TWRP, hit restore, everything seem to work fine, but when I reboot the system I'm stuck at the boot animation.
When I reboot the device to TWRP and check the file manager or my backup folder there are only cryptic and weird letters...
How do I restore my backup properly ?
Try to go back to TWRP 3.2.1.0 i think that that works
everything is gone, you will have to restore with the brick tool, happened to me last week and still not sure why, apparently backing up with TWRP you only need to ticket DATA and that's it.
You need to do two things whenever you restore with TWRP. First is factory reset in TWRP before the restore (that will wipe data). Second is restore system, boot, and data ONLY.
The weird file names and cryptic letters is from the encryption from the old rom. I strongly recommend that you invest in an OTG flash drive so you can store TWRP backups on it. Then you can properly wipe the phone. On the plus side this has happened to me before and I never needed anything special like the unbrick tool to get my TWRP backup up and running smoothly.
and there is a better twrp than twrp. The official is by Dees Troy and the un-official one by Joe Moss Jr. is here. https://forum.xda-developers.com/oneplus-6/development/recovery-twrp-3-2-2-0-touch-recovery-t3813317
Joe's big improvement is a usable 'mtp', ie. access that thumb drive.
Also puts the vibration back in to the key press.
First if you r seeing weired letters in twrp like xdjdhdhdhd folders. Then go to fastboot mode flash newest twrp. Img then ij recovery first flash your liquid remix furst, then flash twrp installer zip niw reboot to recovery.
Now factory reset your phone.
Now if you have oos backup. Then restore everything except system.
And then restore system alone at last now reboot it will work.
your gonna need the flashable oos 5.1x which is one here
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
fastboot to twrp
abd push the stock.zip to the phone <-assuming you know this.
and flash it from twrp.
reboot
fastboot twrp again and flash twrp.
this is where decryption comes in handy
Restoring backups with twrp will fail almost all the time. I've yet to do a successful restore and I've tried every method. You're gonna have to flash back to stock OOS and start over.
If anyone has successfully restored more than one backup then I would start a new thread with the exact method you used.
That worked.
I still wonder why not to restore system.
If I take a nandroid backup should one backup
system or system image, data or data image ?
I was trying a new rom the Resurection Remix V6.2.0 Android 8.1.0. i wanted to go back to my TWRP Backup of OOS 5.11 . I wiped data/cache/System . Tried to restore rom . it restored successfully but i didnt do wipe data thing. when i tried to reboot twrp blu, the recovery was lost. then i had to fastboot boot reovery. and lot of wierd folders were created on my phone internal memory. All data lost.
i had to flash the full 5.11 stock zip via twrp. tried to reboot again lost in bootloop. Switched back to stock recovery and make a factory reset then it booted.
switched off the phone back to Blu spark TWRP. again wipe data cache and system. Then restore the TWRP Backup previously double saved on a usb drive. This Time it restored successfully and booted as well fine.
i think i should have made a factory reset or format data before restoring from A Lineage OS Rom OS to OOS TWRP Backup
thats what made the whole internal drive mess and to be formatted as well
My Question is it only important to format data and then restore twrp or also backup and make restore of system.img of OOS backup as well
Hi all,
I have A6000 with OOS 9.0.5. I installed magisk and TWRP with this guide. I did a full backup, however I cannot restore it. I get error 255 on tarExtractFork(). I use official TWRP 3.3.0. After failed restore I can still boot to (now freshly wiped after attempted restore) system. Even backups of this clean system cannot be restored.
For the record, I don't have a second profile, no "999" user id, I didn't change slots, I removed screen lock before making backup. I still have this problem even if I backup just data, with all other options unticked.
Any help? I come from a device, which didn't have any problems with backup/restore so this is a bummer for me. But I'm sure that users of OP6 can do backups and restores.
Thanks!
For anyone that also has the same problem:
This helped me. I have a feeling that flashing just data through fastboot could be enough, but I didn't have an occasion to check it, as even subsequent restores worked.
I used this to flash device in fastboot mode.
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