I've just finished setting up my T-Mobile 7T with the global v. 11.0.0.2 firmware and Magisk 23. I'm really like a more versatile recovery, and I'm not keen on the experimental version of TWRP that's currently available. Is there any reason to think that the recovery from the 7T build of LineageOS 18.1 would cause problems?
Should work fine though lossyx twrp oos11 is very good also, decrypting oos11 data and backing up oos11 data fine (on AFH 7/28/21)
This? https://forum.xda-developers.com/t/...l-teamwin-recovery-project-7t-7t-pro.4299171/
Yes, specifically https://androidfilehost.com/?fid=7161016148664790680
Ok, so the developer said that backups are unreliable with OOS, which is what I have and the main reason I want a recovery. On closer look, LOS recovery doesn't seem to support this either. Do you know of one that does?
Quoted oos recovery allows oos backup reliably. Restoring needs 2 steps: 1st restore all but data; reboot, skip google setup, remove lock screen in security section, reboot back into twrp; then restore data, reboot twice (1st time has no nav bar, 2nd time nav bar appears)
HueyT said:
Quoted oos recovery allows oos backup reliably. Restoring needs 2 steps: 1st restore all but data; reboot, skip google setup, remove lock screen in security section, reboot back into twrp; then restore data, reboot twice (1st time has no nav bar, 2nd time nav bar appears)
Click to expand...
Click to collapse
I don't quite understand. Are you saying that the stock OxygenOS recovery does backups?
No TWRP on Android File Host as above
Related
hello all,
I have a rooted OP3 running the latest TWRP recovery. Using these instructions I am trying to upgrade to 3.2.8 from 3.2.7. There are no errors displayed during OOS or SuperSU install steps.
But when the phone reboots - it stays stuck at the boot animation. This happens across several attempts. I do not have xposed installed, if it helps. Repeating the above steps with a 3.2.7 image works without issues.
Is there any way I can figure out where the 3.2.8 reboot is getting stuck at? I *do not* want to do a fresh install.
Any thoughts/ Suggestions? I have already posted at the above thread and thought I'd try my luck here too.
EDIT: Can a MOD please move this to Q&A forum. Just realized I posted to Guides, News & Discussion.
backup all your data and install 3.2.8 with the official procedure
Sacob said:
backup all your data and install 3.2.8 with the official procedure
Click to expand...
Click to collapse
That's my last option. But that's as good as starting from scratch. In which case, I might as well postpone until Nougat arrives on the OP3
tropicanapure said:
That's my last option. But that's as good as starting from scratch. In which case, I might as well postpone until Nougat arrives on the OP3
Click to expand...
Click to collapse
and wait without a phone?
Flash the new Beta 10. i'm currently using it with root and it works great
Not sure what you mean - without a phone. I was able to roll back to 3.2.7 with zero issues
I was mulling over installing the Beta - but I understand Nougat is due in Jan? Also, is there a process to move to b10 without losing data?
Sacob said:
and wait without a phone?
Flash the new Beta 10. i'm currently using it with root and it works great
Click to expand...
Click to collapse
tropicanapure said:
Not sure what you mean - without a phone. I was able to roll back to 3.2.7 with zero issues
I was mulling over installing the Beta - but I understand Nougat is due in Jan? Also, is there a process to move to b10 without losing data?
Click to expand...
Click to collapse
i got the impression that your phone wasn't booting xD
well, every time i flash those betas (9 and 10) TWRP asks me for a PIN that doesn't exists and to solve that i need wipe everything... so i wouldn't count on that
tropicanapure said:
hello all,
I have a rooted OP3 running the latest TWRP recovery. Using these instructions I am trying to upgrade to 3.2.8 from 3.2.7. There are no errors displayed during OOS or SuperSU install steps.
But when the phone reboots - it stays stuck at the boot animation. This happens across several attempts. I do not have xposed installed, if it helps. Repeating the above steps with a 3.2.7 image works without issues.
Is there any way I can figure out where the 3.2.8 reboot is getting stuck at? I *do not* want to do a fresh install.
Any thoughts/ Suggestions? I have already posted at the above thread and thought I'd try my luck here too.
EDIT: Can a MOD please move this to Q&A forum. Just realized I posted to Guides, News & Discussion.
Click to expand...
Click to collapse
Did you download the full 3.2.8 zip from http://downloads.oneplus.net? I did. And to my surprise, it erases the whole userdata partition, including TWRP backups and downloaded files (including SuperSU zip). So big warning if you try with that zip. I assume that this zip is intended for those reverting from Nougat Beta, to go back from F2FS to EXT4.
My solution was to restore an old TWRP backup that was saved on my PC and then reflash a modified full 3.2.8 zip where the last line in the update script was removed: the one that erases userdata partition. So before flashing full 3.2.8 zip from http://downloads.oneplus.net I recommend you to remove the last line in the update script.
No, I downloaded the Full ZIP from this official thread on the OP3 forums. I was aware of that line though. And from previous experience - the first thing I do when I make a TWRP backup is to move it off the phone. That and I purchased Titanium Backup long time ago. I use it to back up stuff surgically and sync it up to Dropbox every night. The app also seems to have the ability to make a recovery-flashable "update.zip" - something I have yet to try.
Appreciate the heads-up though.
ptblad said:
Did you download the full 3.2.8 zip from http://downloads.oneplus.net? I did. And to my surprise, it erases the whole userdata partition, including TWRP backups and downloaded files (including SuperSU zip). So big warning if you try with that zip. I assume that this zip is intended for those reverting from Nougat Beta, to go back from F2FS to EXT4.
My solution was to restore an old TWRP backup that was saved on my PC and then reflash a modified full 3.2.8 zip where the last line in the update script was removed: the one that erases userdata partition. So before flashing full 3.2.8 zip from http://downloads.oneplus.net I recommend you to remove the last line in the update script.
Click to expand...
Click to collapse
tropicanapure said:
No, I downloaded the Full ZIP from this official thread on the OP3 forums. I was aware of that line though. And from previous experience - the first thing I do when I make a TWRP backup is to move it off the phone. That and I purchased Titanium Backup long time ago. I use it to back up stuff surgically and sync it up to Dropbox every night. The app also seems to have the ability to make a recovery-flashable "update.zip" - something I have yet to try.
Appreciate the heads-up though.
Click to expand...
Click to collapse
OK. I also use TB, and from now on I use cloud storage :laugh:
After the full modified 3.2.8 zip I successfully flashed official SuperSU 2.79, Xposed v87 and Bluspark r25 kernel. I use F2FS on data partition. It boots and runs fine!
The only thing I'm a bit concerned about is that it stays on the bootlogo (OnePlus logo, Powered by Android) for about 25 secs before the bootanimation begins when booting to system. Much faster before. When booting to recovery (TWRP 28, Bluspark) the time on bootlogo is normal (short). Any thoughts on that?
I wish I had, man. You went a number of steps ahead when your phone went past the boot animation
As a afterthought - try looking through your logs.
ptblad said:
OK. I also use TB, and from now on I use cloud storage :laugh:
After the full modified 3.2.8 zip I successfully flashed official SuperSU 2.79, Xposed v87 and Bluspark r25 kernel. I use F2FS on data partition. It boots and runs fine!
The only thing I'm a bit concerned about is that it stays on the bootlogo (OnePlus logo, Powered by Android) for about 25 secs before the bootanimation begins when booting to system. Much faster before. When booting to recovery (TWRP 28, Bluspark) the time on bootlogo is normal (short). Any thoughts on that?
Click to expand...
Click to collapse
I got my op3 phone loaded up with twrp version 3.0.2-1 but many errors occurred after I flashed this version.
Current problems on my phone right now:
-"The dm-verity is not started in enforcing mode" occurs every time I turn on the phone.
-Twrp won't read any of my files inside the "sdcard" folder wether it's just regular folder, .zip files, and even .img files.
-It also looks like only 1 version works of twrp works on my phone right now since any twrp versions after 3.1.0 causes the twrp program to froze and doesn't completely move past welcome screen of twrp.
I believe I had the same problem. Contact OnePlus on their support page. In a chat support window, tell the operater about your problem, and ask for an appointment with a level 2 technician. They should schedule you an appointment with a technician who should be able to wipe your phone no matter what state/condition it's in. They fixed my phone in a matter of minutes. But PLEASE, try to remember to be respectful and co-operative, it usually gets you better service no matter who you are dealing with.
For dm - verity problem, it's not a problem tough... Just a security breach as seen by Google.
BTW here is the fix...It's easy , follow the thread :
https://forum.xda-developers.com/oneplus-3/how-to/fix-easy-method-removing-dm-verity-t3544339
Can't comment on twrp as I'm on the 3.0.2-1, haven't tried 3.1. Hope it helps, Thanks!
Use TWRP 3.0.4-1. 3.0.2 can't decrypt internal storage, at least not on mine it couldn't.
Also if you have f2fs file system, TWRP takes a loooooong time to boot. Just wait, even though it seems hung. Takes several minutes. If you have ext4, it's quick. Use the app 'Diskinfo' to check
I had TWRP 3.1 and it would not do OTA of lineage, it would wipe the device when I tried and would not restore backed ROMs, stay away from TWRP 3.1. So, i went back to 3.0.4.1 via fastboot. My suggestion is flash the stock recovery from Oxygen 3.8 marshmallow (this can be found in the archived OnePlus 3 tool kit on XDA) and then sideload the stock marshmallow Oxygen 3.2.8 (download from OnePlus support page) and start all over.
mremghz said:
I had TWRP 3.1 and it would not do OTA of lineage, it would wipe the device when I tried and would not restore backed ROMs, stay away from TWRP 3.1. So, i went back to 3.0.4.1 via fastboot. My suggestion is flash the stock recovery from Oxygen 3.8 marshmallow (this can be found in the archived OnePlus 3 tool kit on XDA) and then sideload the stock marshmallow Oxygen 3.2.8 (download from OnePlus support page) and start all over.
Click to expand...
Click to collapse
That doesn't make sense..
The latest recovery works fine here, atleast the official one. If you are in F2fs and encrypted keep in mind it takes a long long time since F2fs is really bad at this.. Depending in how full your internal storage is it can take up to 10 minutesm
Twrp 3.0.4.1 or
3.1.0 x v.26 blu_spark.
To get OTA you need to be stock, only Oos official stuff.
I do have my oneplus 3 formatted as f2fs, but it is not encrypted. I don't know what happened to it when I tried to do an update with lineage os it basically factory reset the phone (and no I didn't wipe anything but the cache) and it would not install any zips from my internal sd card. I had to go back to fastboot and reflash TWRP 3.0.4.1 recovery. Then I wiped the device and reinstalled lineage, now it works perfectly fine.
They are lineage nighty OTA updates.
Hello fellow XDA members and flashaholic people! This is a guide about flashing sGSI or GSI (semi-GSI) Android Pie images on VINCE.
This guide is for VINCE only! Please don't try it on WHYRED it may work or it may not.
First you need to treble enabled custom recovery. I suggest OrangeFox V8.1 https://forum.xda-developers.com/redmi-note-5/development/official-orangefox-recovery-project-t3807479
You can either flash it via TWRP or extract zip and flash recovery img by fastboot method.
Second you need treble enabled custom Oreo ROM, I suggest Cardinal-AOSP as it's vendor.img works flawlessly. https://forum.xda-developers.com/redmi-note-5/development/rom-cardinalaosp-t3774232
And third step includes the GSI image. You can find several GSI's here; https://forum.xda-developers.com/project-treble/trebleenabled-device-development
After downloading .zip file from any ROM you wanted extract it to get its system image and move it into the either internal storage or SD card. [SYSTEM IMAGE ONLY NEEDED]
I tried Pixel Experience 9.20 and Havoc OS 9.18 builds both booted without issues.
Please note that you need GApps package for ROM's (Except PixelExperience) you can find them here; https://opengapps.org/ Suggested package is Nano one. But if you want more you can go for bigger packages. I always use Mini version of it.
Steps to get Pie working on our device:
1. Reboot to custom recovery (if you have) flash OrangeFox R8.1 treble-enabled recovery. [If you have already have OrangeFox Recovery skip this step]
2. Touch Wipe and wipe /system /data /cache /dalvik and format /data
3. Flash cardinal-aosp ROM to your device You do not need to install GApps as we are going to use Pie anyway.
4. After flashing reboot to system it will directly go into launcher without setting stuff up. Reboot your device to recovery again.
5. Touch install, touch install image and flash the system image you've extracted. Wait for it to complete.
5.1 If you installed other than Pixel Experience please install proper GApps right after. [IF GAPPS WONT INSTALL BOOT THE DEVICE INTO SYSTEM FIRST AND WHEN BOOT COMPLETED PLEASE REBOOT RECOVERY AND FLASH GAPPS IT WILL WORK] After GApps installed go to wipe and do a factory reset in recovery. Reboot the device into system.
6. After you set up your device there is several optional operations you can do;
6.1 Root: You can use Magisk v17.1 or above to get root access. [Flash via recovery, if Magisk app wont appear in app menu you can install it from apkmirror safely]
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
PLEASE KEEP IN MIND I DO NOT DEVELOPING ABOVE GSI IMAGES OR HELPING TO DEVELOP. IF YOU HAVE ANY BUGS TO REPORT PLEASE REPORT IN PROPER FORUM POST. I CAN HELP ABOUT INSTALLATION ONLY.
Ah, and there is few screenshots i'll share (Pixel Experience 9.0):
Don't need to flash p lag fix, volte fix and other stuff?
Ritik17 said:
Don't need to flash p lag fix, volte fix and other stuff?
Click to expand...
Click to collapse
Since i did not have any problems about lag or freeze dont need to flash it. Though im not sure about VoLTE but it seems broken for me too. I still wait for official or unofficial Pie ports (which even redmi 2 and 3 got)
bdogan1912 said:
Since i did not have any problems about lag or freeze dont need to flash it. Though im not sure about VoLTE but it seems broken for me too. I still wait for official or unofficial Pie ports (which even redmi 2 and 3 got)
Click to expand...
Click to collapse
Any other bug or issue that you've found in the ROM? Camera problems? Bluetooth or Wifi's MAC changing or reverting to 00:00:00...? Battery drains, memory leaks, crashes? GPS problems? anything?
moralesnery said:
Any other bug or issue that you've found in the ROM? Camera problems? Bluetooth or Wifi's MAC changing or reverting to 00:00:00...? Battery drains, memory leaks, crashes? GPS problems? anything?
Click to expand...
Click to collapse
In few hours of usage i did not encountered very-serious level bugs. Battery was fine and didn't seemed like to draining. Bluetooth and WiFi had no issues for me either. Only VoLTE doesnt works and as may you know thats global issue on it. Did not faced any mem-leaks or running out of memory problems, with freshest install it used up to 1.3 GB mem and with some apps like social ones it went up to 1.6 to 1.9 GB but ROM was overall butter smooth without single lag or freeze. No FCs either, GPS works i guess it was enabled by default on fresh install as usual but since im not using the GPS that much i did not tested it fully though.
As you can guess those are still experimental/beta builds could have issues that i did not encounter. But overall was very fine for me. I'd keep it but it kinda messed "about phone" settings as it goes manufacturer and model both goes by unknown or phh-treble. It's very natural since i installed as GSI image but still bothered me.
Almost forgot; In Havoc OS settings goes direct crash if you touch battery in settings. PE works fine but it has problems with Dark theme beign not applied correctly. Also i did not used or tried substratum or its themes.
Thank you for your instructions. I wanted to install a GSI 9.0 ROM since Pie came out, but other threads with instructions were too complex or convoluted that I thought it was harder.
I would like to make some clarifications on your steps:
* I used the unofficial PixelExperience 9.0 GSI image, as you said. It feels and behaves almost exactly as the official PixelExperience build for our device, but with nicer interface. The image is HERE. Just as a sidenote, the System image comes with DPI = 360, things look a bit too big. To make it look like MIUI or the official PixelExperience build for vince, a dpi of 390 should be set (this can be done from settings > System > Developer Settings > Minimal Width, under the "draw" section).
1. Reboot to custom recovery (if you have) flash OrangeFox R8.1 treble-enabled recovery. [If you have already have OrangeFox Recovery skip this step]
2. Touch Wipe and wipe /system /data /cache /dalvik and format /data
* At this step, I had to make "Format Data", and only then reboot to recovery again, and make the wipes to all other partitions. Without rebooting the wipes weren't possible (it was showing errors while trying to mount partitions). VENDOR PARTITION SHOULD NOT BE WIPED
3. Flash cardinal-aosp ROM to your device You do not need to install GApps as we are going to use Pie anyway.
4. After flashing reboot to system it will directly go into launcher without setting stuff up. Reboot your device to recovery again.
At this point, you must check that the hardware works correctly. Touch, screen, audio, BT, wifi, RIL, LTE or whatever you use. If something doesn't work at this point, it won't work after installing the GSI image.
5. Touch install, touch install image and flash the system image you've extracted. Wait for it to complete.
* In OrangeFox, at this point before flashing the GSI's .img file, the recovery asks for the type of image. For noobs and careful people, "System Image" must be selected before proceeding.
5.1 If you installed other than Pixel Experience please install proper GApps right after. [IF GAPPS WONT INSTALL BOOT THE DEVICE INTO SYSTEM FIRST AND WHEN BOOT COMPLETED PLEASE REBOOT RECOVERY AND FLASH GAPPS IT WILL WORK] After GApps installed go to wipe and do a factory reset in recovery. Reboot the device into system.
6. After you set up your device there is several optional operations you can do;
6.1 Root: You can use Magisk v17.1 or above to get root access. [Flash via recovery, if Magisk app wont appear in app menu you can install it from apkmirror safely]
* When installing Magisk through recovery, the framework will be installed, but the APK won't appear in the app list. It must be downloaded separately from https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.0/MagiskManager-v6.0.0.apk
The following modules are working without issues in my setup:
* Youtube Vanced
* Google Product Sans font
* MagiskHide Props Config
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
Cast and mirror screen are broken. After choosing a screen to share the phone's screen to, SystemUI will crash. Apps with cast capabilites won't detect Chromecast devices (the cast button won't appear).
Thank you for your help
moralesnery said:
The following modules are working without issues in my setup:
* Youtube Vanced
* Google Product Sans font
* MagiskHide Props Config
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
Thank you for your help
Click to expand...
Click to collapse
I don't know what is "MagiskHide Props Config" but is MagiskHide working normally for you?
I'm currently using the Pie "V4 zip" from this thread but MagiskHide isn't working. If it is working normally for you I will try to flash in your way then.
And can I flash 9.0 GSI image over any 8.x roms? Or it must be PE or Havoc?
Can't Show the Image File
After extracting the Hovac OS GSI file (a link that given) can not show Image file it shows file different files in different formats.
GizPrime said:
After extracting the Hovac OS GSI file (a link that given) can not show Image file it shows file different files in different formats.
Click to expand...
Click to collapse
This is the correct link, you don't downloaded gsi file (I did the same thing, currently running Havoc 9 ):
https://sourceforge.net/projects/havoc-os/files/arm64aonly/
sadly i can't flash pie rom because my phone is encrypted. i will try this someday, once i backup my files and do the full format (including internal storage)
i want to try PE pie
Biggest thanks to you as i was in dilemma to try the PE 9.0.
However, the stock camera is so dark so i installed Camera2API, resulting the camera app FC, installed the crashfix Gcam apk i found somewhere in this thread not so long ago to no avail, the camera is still broken. Anyone having the issue ?
TIPS: I tried both Dark Ages and Genom Kernel, the brightness is crazy, i think its the late display driver provided within it: the brightness level is scaled incorrectly, with the 50% on MIUI is 0% in PE, and 50% in PE is equal to 100% of MIUI (the max brightness is at 50% and sliding all over to the right does nothing); clean flashed the whole thing and not using custom-installed kernel at all.
HungNgocPhat said:
I don't know what is "MagiskHide Props Config" but is MagiskHide working normally for you?
I'm currently using the Pie "V4 zip" from this thread but MagiskHide isn't working. If it is working normally for you I will try to flash in your way then.
And can I flash 9.0 GSI image over any 8.x roms? Or it must be PE or Havoc?
Click to expand...
Click to collapse
MagiskHide Props Config" its a module that replaces the ROM's fingerprint with a certified one. This way you get ctsProfile: true and basicIntegrity: true, thus passing SafetyNet. This combined with MagiskHide allows me to use some apps that rely on SafetyNet.
After flashing the Treble-enabling ROM (Cardinal OS) you can install GSI system images based on Oreo or Pie.
Is hotspot working in PIE GSI?
dahrel22 said:
sadly i can't flash pie rom because my phone is encrypted. i will try this someday, once i backup my files and do the full format (including internal storage)
i want to try PE pie
Click to expand...
Click to collapse
If you use orange fox recovery you can wipe encripted partitions and flash custom roms, try it!
Wyneg said:
If you use orange fox recovery you can wipe encripted partitions and flash custom roms, try it!
Click to expand...
Click to collapse
seems like i need to do a format data in recovery. but right now i cant afford to loose all my files in internal storage. once i back up all my file then i will do the format data.
i wish there is some way to decrypt my storage without formatting
btw, i got my storage encrypted because i flashed miui stable rom
it's work but hotspot doesn't work
in cadinal i already check it's work but in gsi have a problem
And.. what If I installed a Treble ROM and I want to go back to stock MIUI, or a non-treble ROM? What should I wipe before going back?
moralesnery said:
And.. what If I installed a Treble ROM and I want to go back to stock MIUI, or a non-treble ROM? What should I wipe before going back?
Click to expand...
Click to collapse
If you do same wipes what you did to flash GSI it's totally ok
expextors said:
it's work but hotspot doesn't work
in cadinal i already check it's work but in gsi have a problem
Click to expand...
Click to collapse
Weird cause hotspot is working fine for me. My kids phone is able to connect without any problems.
soyti2x said:
Weird cause hotspot is working fine for me. My kids phone is able to connect without any problems.
Click to expand...
Click to collapse
i tried on havoc it doesn't work what your gsi you used ? i can't open hotspot because always off when turn on
Hello Everyone,
I am currently on OOS_OB12 on my 5T. And I have root + Blu_Spark TWRP running. How do I update to Pie without losing data ? I have the treble update, but still on Oreo. I searched a lot and found mixed information, some say I need to go to a specific version first and then to latest., Some say I just dirty flash and flash magisk on top of that. Clean flashing is not an option as I have a lot of data I can't lose, So please help me out here.
TIA
hgaaditya said:
Hello Everyone,
I am currently on OOS_OB12 on my 5T. And I have root + Blu_Spark TWRP running. How do I update to Pie without losing data ? I have the treble update, but still on Oreo. I searched a lot and found mixed information, some say I need to go to a specific version first and then to latest., Some say I just dirty flash and flash magisk on top of that. Clean flashing is not an option as I have a lot of data I can't lose, So please help me out here.
TIA
Click to expand...
Click to collapse
Yeah the treble thing is a bit confusing. I don't remember which one it is for open beta. But the safe way to do it is to install 5.1.3 which installs without problem. Then take an update to 5.1.4. then you can freely update to any pie version without losing data. The problem is that I don't remember the Open Beta equivalent versions for these firmwares.
But like best is that you make a TWRP backup of the data RN before doing anything. OOS is quite picky on what conditions it wants to boot under.
Sent from my OnePlus 5T using XDA Labs
Go to Settings and check for available system update. It will get you the one you need to flash to get Treble. That's how I upgraded from 4.7.4. Downloaded 5.1.3 from Software Upgrade, flashed and booted up, checked update again, received 5.1.4 then 5.1.7 because Pie wasn't out for my country yet.
I checked my 'System Updates ' and it is showing me Open Beta 23 . Does that mean I'm good to upgrade directly to the latest version.?
Update I followed the steps here And everything works as expected. no need to clean flash :
https://forum.xda-developers.com/oneplus-5t/how-to/soon-oxygenos-beta-1-android-o-oneplus-t3726074
[Dirty Flash] For Users with an Unlocked Bootloader and TWRP Recovery coming from H2OS Oreo/Pie, Stable OOS Oreo/Pie, OOS OB Oreo/Pie:
Download the full ROM zip from the downloads section above
Transfer the zip to the root of your device's internal storage
Only needed if you are coming from Oreo: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
Reboot to TWRP recovery (make sure you're using siankatabg's TWRP if you're on Oreo or codework's TWRP/blu_spark TWRP if you're on Pie) and take a nandroid backup of your existing ROM
Flash Magisk Uninstaller (recommended)
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
Flash the latest stable Magisk in case you want to root
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
If you were decrypted earlier, flash Disable DM-Verity and ForceEncrypt 2.0 (OP5-5T-Treble).zip from here
Reboot
Closing thread.
[RESOLVED] Updating from OOS_OB12(Oreo) to OOS_OB23(Pie)
Closing thread
I got Lineage 17 w/ Magisk root running now neat and great and I want to perform a full NANDroid Backup.
After some research it seems crucial to have a custom recovery like TWRP for that. There is the online nandroid thing - but I would need CWM or anything like this to restore?!
So my question is
a) is there another custom recovery (compatible with Pixel 3a XL w/ lineage 17 based on android 10) I can install and perform Nandroid backup with?
b) any other solution to perform this backup and restore? I heard there are cmd commands for that as well , but I'm a noobie not so sure to do that.
of course there are several apps out there to backup data.. but I don't trust ''any'' app to get root permission. In F Droid I couldn't find what I was looking for. Suggestion?
thank you for help!
It is unsafe to perform backups while booted into Android, as files may be changed/added/removed while the backup is taking place.
This is why it tends to be a feature of custom recoveries.
Titanium Backup is good. It doesn't support split APKs like YouTube but the data restore works flawlessly. This is an old utility app so you can trust it with root. You can find Titanium Backup on the play store, it is the one with the star and "root required".
If you want to perform full backups of your PHONE you will want TWRP. If you want to perform full backups of your APPS then you will want to use an app like Titanium Backup (however Titanium Backup is not updated for split APKs, like I said above), which will allow you to transfer your backups to a new phone and fully restore all apps & data (as long as both phones have root).
Sure problem is I want to perform a full backup of my phone, but TWRP ist not available. What are my options?
dadu1257 said:
Sure problem is I want to perform a full backup of my phone, but TWRP ist not available. What are my options?
Click to expand...
Click to collapse
Does TWRP for Pixel 3a XL not work for you? All you have to do is download the "twrp-installer-3.4.0-0-bonito.zip", install it as a Magisk module, then direct install Magisk again, then reboot into recovery and you'll have TWRP.
When accepting OTAs, you will want to use the "TWRP A/B retention script" before you install Magisk to the inactive slot. The script is available as part of the Magisk modules repository, so you should be able to install it directly from within Magisk Manager.
TWRP doesnt work for me, see here what user 41rw4lk wrote, too..
Is there a tutorial on how to install twrp as a masgisk module?
Also, how else can I perform a backup img for my phone?
thank you
dadu1257 said:
TWRP doesnt work for me, see here what user 41rw4lk wrote, too..
Is there a tutorial on how to install twrp as a masgisk module?
Also, how else can I perform a backup img for my phone?
thank you
Click to expand...
Click to collapse
https://puu.sh/GWiul/2611f0cdf4.mp4 - video showing how to install TWRP
Edit: https://puu.sh/GWiAe/6f620419c8.mp4 is more compatible and smaller. same video
.....
LoganDark said:
https://puu.sh/GWiul/2611f0cdf4.mp4 - video showing how to install TWRP
Edit: https://puu.sh/GWiAe/6f620419c8.mp4 is more compatible and smaller. same video
Click to expand...
Click to collapse
Benn trying to get this to work for a little bit now and no luck at all....
Let me start by saying i an NOT running LOS so that might be the whole issue...
I have tried with pure stock and stock with ex kernel
Same results for each
1) TWRP loads as the recovery and can be booted into, BUT the rom is now soft bricked and wont boot at all
2) Even when in twrp I cannot flash anything, cannot see sdcard and cannot backup data partition (the data partition shows as 0 space)
Perhaps the LOS kernel or rom adds something thats missing in my two setups?
The sample video is for another phone. My recolection is that twrp and pixels on android 10 or 11 wont work. Lineageos 17.1 is android 10 based. I think it worked on that other phone as it was not a pixel.
Can anyone confirm or deny if this works in any configuration of android 10 or 11 on our phones?
adm1jtg said:
Benn trying to get this to work for a little bit now and no luck at all....
Let me start by saying i an NOT running LOS so that might be the whole issue...
I have tried with pure stock and stock with ex kernel
Same results for each
1) TWRP loads as the recovery and can be booted into, BUT the rom is now soft bricked and wont boot at all
2) Even when in twrp I cannot flash anything, cannot see sdcard and cannot backup data partition (the data partition shows as 0 space)
Perhaps the LOS kernel or rom adds something thats missing in my two setups?
The sample video is for another phone. My recolection is that twrp and pixels on android 10 or 11 wont work. Lineageos 17.1 is android 10 based. I think it worked on that other phone as it was not a pixel.
Can anyone confirm or deny if this works in any configuration of android 10 or 11 on our phones?
Click to expand...
Click to collapse
Huh, that's weird... I apologize, I'm not very good at supporting devices I don't own. I'm not running Lineage either, I'm running stock plus mods.
It's possible that it doesn't work on your phone for whatever reason. There are a couple ways to install TWRP nowadays, check them out maybe? I promise TWRP is what you want for backups.
LoganDark said:
Huh, that's weird... I apologize, I'm not very good at supporting devices I don't own. I'm not running Lineage either, I'm running stock plus mods.
It's possible that it doesn't work on your phone for whatever reason. There are a couple ways to install TWRP nowadays, check them out maybe? I promise TWRP is what you want for backups.
Click to expand...
Click to collapse
Agreed but twrp simply doesnt work on our phones, or even any pixel 3 or above. It can't read the partitions correctly. Just trying to keep people from soft bricking their phone. Something about andriod 10 and 11 and the phones a/b partition configuration
adm1jtg said:
Agreed but twrp simply doesnt work on our phones, or even any pixel 3 or above. It can't read the partitions correctly.
Click to expand...
Click to collapse
Where did you hear this? I'll admit, I haven't heard about TWRP not working on Pixels, but it's relevant and it would be good to know if I ever help another Pixel user in the future.
adm1jtg said:
Something about andriod 10 and 11 and the phones a/b partition configuration
Click to expand...
Click to collapse
That's interesting, because my OnePlus 7 Pro runs Android 10 with an A/B configuration and TWRP works just fine. Haven't found a single feature that didn't work. Flashing custom ROMs, changing boot slots, etc. all work fine. So it can't be the A/B configuration.
LoganDark said:
Where did you hear this? I'll admit, I haven't heard about TWRP not working on Pixels, but it's relevant and it would be good to know if I ever help another Pixel user in the future.
That's interesting, because my OnePlus 7 Pro runs Android 10 with an A/B configuration and TWRP works just fine. Haven't found a single feature that didn't work. Flashing custom ROMs, changing boot slots, etc. all work fine. So it can't be the A/B configuration.
Click to expand...
Click to collapse
You can read through this:
[CLOSED]TWRP 3.3.1-1 for Pixel 3A XL [OFFICIAL]
Team Win Recovery Project 3.x, or TWRP3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
And this:
tips for preserving twrp from Pie to Q
hi i'm not an expert so sorry maybe for foolish question but coudn't find a clear answer yet.. i'm still on pie and twrp 3.3.1.1; i'd like to upgade to ten but preserving twrp (maybe upgrading to 3.4.0 if necessary) which are the steps to keep...
forum.xda-developers.com
No method I have tried results in anything but an unusable twrp or a boot loop. Cant even fastboot boot current version. All about dynamic partitions and lzma compression as I guess the partition isnt big enough. But bottom line is I have yet to find anyone including myself who can get twrp to in any way shape or form be usable on our phones for android 10 or newer.
this is what command prompt gives with fastboot boot
Sending 'boot.img' (65536 KB) OKAY [ 1.509s]
Booting FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
This is likely due to the kernels I use likely not having lzma. Checking into it.
fastboot: error: Command failed
LoganDark said:
If you want to perform full backups of your PHONE you will want TWRP
Click to expand...
Click to collapse
I'm not sure how reliable is that. I just did a backup of Lineage 17 in TWRP, System and Data, restored it a few hours later through OTG and it got stuck on a google boot screen... Now I installed the LOS 17 ROM again (which I had in internal storage) but restored only Data (excl. storage).
It boots up now, but most apps are corrupted - if I open them they crash ('App ... keeps stopping').
I wouldn't count on it. TWRP nandroid backup is very unreliable.