Hi i was about to update my phone and setting it to factory in order to update it to Oxygenos last version since i still using oxygen2 (andoid 5) etc...
I was about to do a twrp backup however i do no thave enought space so i've read on internet that with twrp 3.1+ you can backup directly on pc. I've tryed to update twrp however its not working and not starting the recovery partition. I've read that : (3.0.2-1 and above for OxygenOS 3.x and above) (3.0.2-0 and below for OxygenOS 2.x and below) however i need the updated version to backup directly on pc what can i do? some advice? i've looked for a modified version of twrp 3.1 for oxygenos2 but i did not find it :S
Before you do this, update TWRP via these instructions
https://wiki.lineageos.org/devices/oneplus2/install
skip down to this line "Installing a custom recovery using fastboot" as you do not need to unlock the bootloader as it is already unlocked since you have TWRP already.
Do not make a TWRP backup, It will not be of any use once you move to OxygenOS 3.6.1 since the backup will be of Nouget (android 5). The best way to upgrade would be to follow the steps here http://downloads.oneplus.net/oneplus-2/oneplus_2_oxygenos_3.6.1/
Once you get to step 4, click the "View Instructions for TWRP Recovery" link then you can either dirty flash or clean flash the zip. I would recommend clean flashing, as in do the factory reset as mentioned in the second paragraph under step 4. However, do not directly flash the rom afterward, use the reboot option in TWRP to reboot into recovery then flash the zip.
NOTE: If you want to use Magisk to pass SafetyNet and have root, download the Magisk zip and flash after flashing the rom, or queue it to it flashes right after the OOS rom.
afterward let the phone boot up then do the setup. Once you have completed setup, enable developer settings and enable advanced reboot. use reboot into recovery to boot into TWRP
Now go ahead and make a TWRP Backup, This backup will be your Go-To backup if you want to go back to factory OOS 3.6.1 with the setup completed and Magisk already installed.
Not able to backup
The problem is that the last version of TWRP working on oxygenos2 is 3.0.2-1 and you can not make the backup directly on computer, i've traied toupdate twrp and it does not lounch however with that version of twrp (3.0.2) or before it works that was the point if there was any modified twrp for oxygenos2 and with twrp version 3.1 or higher.
TWRP v3.x.x doesn't work with oxygen 2.
There's no way to boot TWRP v3 without installing oxygen 3.
If you need to backup your files (pictures, videos, WhatsApp messages etc.) you don't need TWRP because it backups only your system and your apps.
So simply attach your phone to your PC and copy all your files.
If you need a copy of your system then you need to free some space on your phone and do a backup with TWRP v2
Related
Hi
Trying to flash TWRP but no ADB & Fastboot directory under Windows 10 program files/x86?!? Also should GApps go here? 32bit? What if SD card & internal storage is merged? End result is Lineage OS...
Could anyone link a good guide?
Which adb/fastboot utility did you install? If you install Minimal ADB 1.4.2, on my computer it's present under C:\Program Files (x86)\Minimal ADB and Fastboot. For 1.4.2: https://www.androidfilehost.com/?fid=745425885120698566
If you're trying to flash TWRP (ensure you've got either TWRP 3.0.2 or a more recent version, 3.1.1 for example, and that it's for athene devices), you could follow this guide: https://forum.xda-developers.com/showpost.php?p=67031805&postcount=3 Also, double check you've unlocked your bootloader before attempting any of this: https://forum.xda-developers.com/showpost.php?p=67031801&postcount=2 Bear in mind unlocking your bootloader will wipe your device and void your warranty.
Once you've flashed TWRP, then reboot straight to recovery - this is to ensure TWRP is not overwritten by the stock recovery. Once you've booted to the recovery, then TWRP should stick and you may reboot as normal.
EDIT - instead of flashing TWRP, you may wish to boot to TWRP (and look at step 4 below):
Copy the TWRP image file to your adb folder.
Boot into the bootloader and connect your device to your computer.
Open your adb client and verify your device is communicating by executing 'fastboot devices' without the quotes. You should get a response with your device's serial number.
To boot in TWRP, execute in the adb terminal 'fastboot boot <name of TWRP image>' without the quotes. E.g if your TWRP is twrp-3.1.1-athene_shreps.img, then the command you'd use is 'fastboot boot twrp-3.1.1-athene_shreps.img' (without quotes).
Afterwards, you'll be able to flash LineageOS and GApps. The main instructions for flashing a custom ROM are usually listed in the first post of each custom ROM (here's the link for the official LineageOS: https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101)
If you have your SD card and internal storage merged, then unless you can save the encryption key from your stock, your SD card will be wiped/inaccessible. SD cards mounted as portable storage appear to operate okay under both custom and stock ROMs. Thus, back up your SD card to your computer. You may wish to re-format your SD card as portable storage (and from what I've read on the Lenovo Motorola forums, that might help your SD card last longer, as it's not being subjected to encryption as it would be with adoptable storage).
1)You'll be flashing the LineageOS and GApps (can use either OpenGApps or BeanGApps) zips using TWRP. You need 7.1 arm Gapps (32 bit).
2)Download LineageOS and GApps to your device. Do not unzip them.
3)Reboot to TWRP recovery. Tap the Backup option on the main menu.
4)Back up your device in TWRP (make a note this is your stock backup). If you want this backup to be OTA friendly for stock updates, then do not 'swipe to allow modifications'. Back up the stock ROM, verify you've got the backup then reboot to TWRP, and then 'swipe to allow modifications'.
5)Go back to the main menu, and tap the 'Wipe'.
6)Under 'Advanced Wipe', select Dalvik/ART cache, system, data and cache. Double check these are the only ones you have ticked.
6a)Swipe to wipe.
7)Go back to the TWRP main menu.
8)Tap Install and locate your LineageOS and GApps zips.
9)Flash LineageOS first and then GApps.
10)Reboot to LineageOS.
If your device screen goes to sleep whilst in TWRP, press on the volume keys to wake up your device.
If you wish to revert back to near stock, you can flash your TWRP backup of your stock ROM (though this will revert any messages to the point when your backup was taken, you may wish to use Titanium Backup or MyPhoneExplorer to backup). If you decide to revert completely to stock, then if you were on the June 2017 stock update, please only flash the June 2017 or later stock firmwares: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
@echo92 if he would decide to flash back to a clean StockRom (by fastboot) in order to start with a complete unmodified System (stock boot, stock kernel & stock recovery) wouldn't it be better not to "flash" but just to "boot" once into TWRP and take a backup of the clean StockRom in order to save the stockrecovery too? So he could simply restore his clean stock if he wants to take a future OTA.
If he "flashes" TRWP permanently onto StockR he would backup Stock with modified recovery and might wonder, why he couldn't install an OTA.
Please correct me, if I'm wrong.
bullfinch110 said:
@echo92 if he would decide to flash back to a clean StockRom (by fastboot) in order to start with a complete unmodified System (stock boot, stock kernel & stock recovery) wouldn't it be better not to "flash" but just to "boot" once into TWRP and take a backup of the clean StockRom in order to save the stockrecovery too? So he could simply restore his clean stock if he wants to take a future OTA.
If he "flashes" TRWP permanently onto StockR he would backup Stock with modified recovery and might wonder, why he couldn't install an OTA.
Please correct me, if I'm wrong.
Click to expand...
Click to collapse
Oh definitely, that's an option, booting into TWRP and backing up the stock ROM. As I understand it, you have to back up your device without allowing TWRP to modify your system partition. If the backup is taken after that, I recently read that enabling that will cause an OTA to fail (since the type of OTA monitors if the system was ever mounted as read/write), even if the backup you took had no other changes.
It honestly depends on how much flashing the opening poster is planning on doing, if it's simply just LineageOS and OpenGApps, then might be worth booting into TWRP. However, to keep updated then you'd have to perform the updates when you've got a PC available (to be able to boot into TWRP), in which case the inconvenience of booting into TWRP with a PC might outweigh the downside of a custom recovery. For custom ROMs, we might have a similar issue ironically, where a user downloads an update for custom ROMs and cannot flash the update because they do not have TWRP on their device (albeit this issue is easier to fix). I concur that simply booting into TWRP may be more suitable for new users and those that do not realise the requirements/downsides of having a custom recovery. I'll add in the option of booting to TWRP in the previous post As the saying goes, with great power comes great responsibility.
Also, if the user flashes other files (e.g. a custom logo.bin to hide the bootloader warning), then the OTA would fail anyway, and custom logos aren't backed up by TWRP. For a logo.bin though, that can be easily replaced by a stock logo.bin (from the appropriate stock ROM) flashable in fastboot or in TWRP.
If the xda pros would establish a new status, like "Recognized Explainer", you were the first who 'd deserve it.
Thx!!!
I have successfully installed Lineage Flo (2013) on a Nexus 7! This practice (fell at every hurdle) & your post should bring the matter to a swift finish.
Many thx.
Last working state :
1. Android O version WW-15.0410.1803.55
2. Bootloader unofficial unlocked
3. Rooted with magisk
Reason for flashing :
Update to latest Oreo then re-root but flashing failed due to magisk not being uninstalled first
Current state :
1. Able to enter fastboot
2. Twrp is intact
3. Magisk uninstalled using twrp
Actions already taken :
1. Uninstall magisk via TWRP
2. Re-flash WW-15.0410.1803.55 via TWRP
3. Wipe dalvik/cache
4. Factory reset via twrp swipe
Still stuck in bootloop
I'm thinking of flashing Oreo stock recovery prior to reflash Oreo firmware via Asus flash tool. Found Oreo stock recovery image from 15.04.10.1711.6. Is this usable? (Edit : found suitable version and bunch of other versions, big thanks to Iceboy91 on following thread : https://forum.xda-developers.com/zenfone-3/help/request-stock-recovery-boot-img-stock-t3763381 )
But before I do anything even more stupid, I need your advise on correct next moves, guys.
Flash raw oreo via Asus flash tool and all will be fine.
[email protected] said:
Flash raw oreo via Asus flash tool and all will be fine.
Click to expand...
Click to collapse
Will Asus FT run properly on TWRP i/o stock recovery? Last time I did it booted to TWRP and I can't proceed. Kindly confirm if it's possible and I'll give it another try. I am left with another option which is flashing corresponding stock recovery and boot image.
To save your time from trial and error recovering from similar problem, here's what I do.
Issues :
1. Flashing raw on stock with TWRP stuck on eternal 'unzip image'
2. Flashing raw on stock ROM with stock recovery and wipe data OFF was successfull but could not enter system (stuck on Asus logo with circling progress).
Also unable to enter stock recovery at this point.
Steps taken to recover from bootloop :
1. Flash corresponding recovery and boot image to replace TWRP (BE CAREFUL WITH SOFTWARE VERSION)
2. Firstly, flash basic Oreo RAW firmware which can only boot to fastboot found on this post : https://forum.xda-developers.com/zenfone-3/how-to/updated-unlock-relock-bootloader-t3749456
3. Flash full RAW Oreo firmware found on the very same post mentioned on #2, but with WIPE DATA SELECTED.
Note : Step 2 might be skippable, up to you to try
Hey ,
If you wanna upgrade to latest Oreo update, just follow these steps (most of the users did not report any kind of bootloop)
1) Flash stock recovery
2) Sideload the latest firmware .zip
3) Reboot and flash TWRP & Magisk
Link for stock recovery/boot images by @shakalaca :
https://mega.nz/#F!lw02CLpA!hpetR2-Sec1F__gHPNRE9Q!E09B3BbA
If anything happens, RAW firmware is there for you
Note: Do not remove/uninstall Magisk via TWRP. Flashing latest update will remove Magisk automatically.
Thanks for the tip, my problem has been solved, but better solution is certainly welcomed. Will do when caught in the same situation.
Here is what I do:
Skip automatic update and do it manually through TWRP.
First flash update then reinstall latest magisk in order within TWRP.
Reboot.
sanctitude888 said:
Will Asus FT run properly on TWRP i/o stock recovery? Last time I did it booted to TWRP and I can't proceed. Kindly confirm if it's possible and I'll give it another try. I am left with another option which is flashing corresponding stock recovery and boot image.
Click to expand...
Click to collapse
AFT just needs working fastboot.
Flashing raw via aft will restore all stuff to stock state.
Twrp will be replaced by stock recovery too.
I wouldn't recommend flashing stock zip via twrp.
Another way to get back to. Stock is to replace twrp by stock recovery (after wiping data, cache, system). Then flash boot.img and finally use update via SD card option from the newly installed stock recovery.
Also you can take twrp backup of stock rom (system, data, boot) and restore whenever you want to go to stock (after wiping system, data and cache).
All methods tried and tested.
Hey guys.
Just updated to 9.0.13 last night and today I saw that my root was gone.
I was rooted with Magisk, and did the same as usual. Uninstalled Magisk, downloaded and install the update from System, and after that I Installed Magisk on the second partition (after OTA update) just like in the tutorial..
Any solutions to regain root without wiping the phone ? I already fuc*d it up last month and lost everything .
Regards,
Switiz
In my case it installs magisk after updating and everything worked fine. Reinstall it from the TWRP and it should work.
I don't have twrp installed. is there any possibility to install it without pc ?
p.s I don't have a recovery. every time I try to go to recovery, I have a menu with 3 languages ( 2 Chinese and English ) and the only options are Wipe data and cache and reboot
Switiz said:
I don't have twrp installed. is there any possibility to install it without pc ?
p.s I don't have a recovery. every time I try to go to recovery, I have a menu with 3 languages ( 2 Chinese and English ) and the only options are Wipe data and cache and reboot
Click to expand...
Click to collapse
How did you get root without flashing magisk inside of twrp? And if you did the update that came thru your phone that's why you lost root.. from what I read it's best to always flash full stock. No partial updates
You updated incorrectly. So now you have the stock recovery. You will need a PC to fix it. It's not a big deal, you're just starting over. You will need to boot the TWRP image again, flash the TWRP installer. Then flash magisk. BEFORE you do anything, back up all your data.
Follow this guide here. <-- Use this to reinstall TWRP and Magisk.
Use this guide to update from now on. <-- Download update files here. Dirty flash them, follow the TWRP instructions. I don't even uninstall Magisk personally, but go ahead if you want, as the official instructions say to. No data loss. No losing root. Do not use the OTA update (unless you are stock), do not use Magisk to update (Magisk works, it just seems to mess people up), etc.
Thank you. I will try when I get home.
I update using the tutorial from the page you provided :/.
"Update Process for Rooted Users
1. Magisk Manager > Tap "Uninstall" > Tap "Restore Images" (DO NOT REBOOT)
2. Now Run the System update to download and install the full OTA zip (DO NOT REBOOT)
3. Close all background apps
4. Open Magisk > Tap "Install" > Tap "install" again > Tap "Install to Inactive/Second Slot (After OTA)"
5. Finally tap Reboot after Magisk installation is complete."
It's not the first time. I don't know why this time it didn't worked..
After booting in twrp and installing Magisk, after reboot, I still don't have root :|
https://imgur.com/a/hjGwQkR
Try this
https://forum.xda-developers.com/on...t-oneplus-6t-using-oneplus-6t-rooter-t3864238
OhioYJ said:
You updated incorrectly. So now you have the stock recovery. You will need a PC to fix it. It's not a big deal, you're just starting over. You will need to boot the TWRP image again, flash the TWRP installer. Then flash magisk. BEFORE you do anything, back up all your data.
Follow this guide here. <-- Use this to reinstall TWRP and Magisk.
Use this guide to update from now on. <-- Download update files here. Dirty flash them, follow the TWRP instructions. I don't even uninstall Magisk personally, but go ahead if you want, as the official instructions say to. No data loss. No losing root. Do not use the OTA update (unless you are stock), do not use Magisk to update (Magisk works, it just seems to mess people up), etc.
Click to expand...
Click to collapse
Thanks for this link.
Not sure if you've managed to fix this issue, but I've never used to the uninstaller. I boot into TWRP and flash the full system image and then reboot back into TWRP and flash Magisk onto the active partition. If you don't reboot inbetween then you end up flashing Magisk to the current (old) partition rather than the new upgraded partition.
Hello, I have a T-Mobile 6T which thanks to the XDA thread about bypassing T-mobile, is running the international firmware so I didn't have to kiss their butt trying to unlock the bootloader. Yesterday I decided to try the Resurrection Remix rom since it is unclear whether the Lineage 16 rom supports the in-display fingerprint reader, and I am too busy at work and too lazy to read the entire thread to see if it does.
I followed the instructions and updated my OxyOS to the latest .15 release via TWRP which I also updated to the latest version via OTG using a USB drive because I was unable to unencrypt using the older Blu-Spark TWRP version I had installed. After the OxyOS update (on both partitions) I flashed TWRP again, rebooted to recovery and installed Pico Gapps.
I found the Resurrection Remix rom to be very buggy and I hate the way the in-display biometric works (very slow and I don't like the paw print used as fingerprint placement). Anyway I started installing apps and after 4 apps installed, it says there is no space left in storage.
Nothing will update, and when I try to check storage with any file explorer it says "access denied" or just won't load. I've tried everything. Wiped the data and did factory reset, then flashed stock rom again and same issue. What am I doing wrong?
That looks like a messed up flash. And is pretty common. Considering that A/B is still new and everyone has his own method of flashing. So assuming you can make it back to latest Stock OOS (9.0.15 right now). If you dunno how to then simple reboot to recovery, flash OOS ZIP and then TWRP. Again Reboot to Recovery from within TWRP (Reboot -> Recovery) and again flash OOS ZIP and TWRP Installer. For TWRP I recommend you to grab the latest one (3.3.1-6 as of now). Once flashed, Format Data (Wipe -> Format Data -> YES) and Reboot. Wait for it to boot up. Now you should be on Stable Stock OOS with TWRP Installed.
Now Download ROM of your Choice (RR, LOS, Bootleggers, whatever). You will also need the latest TWRP Installer (same as above) and Gapps (Nano/ Stock Recommended) and Magisk if you want to Root. Reboot to Recovery, flash ROM ZIP and TWRP Installer ZIP. Wait for it to Finish. Reboot to Recovery. Once in TWRP, again flash ROM and TWRP Installer. Once done, again. Reboot to Recovery from Within TWRP. (Read above on how to). Now, flash Gapps. Magisk if you want to Root. Once done, again do a Format Data. Reboot and be patient for ROM to boot. And then tell me wether this works or Not. Good Luck.
hey guys, so i used twrp to flash a OTA then flashed twrp again and rebooted and when i went to flash magisk i was just shown a list of all random numbers/letters. i booted into bootloader flashed twrp img, booted into recovery and all my files were there once again but i still cant get into the OS, can anyone please help?
why is flashing so complicated these days? even the recovery works different. the last time i rooted (4 years ago maybe) you could use twrp to make a backup and it was done simple as that (i did this on the oneplus 6t about 4 weeks ago and got the issue with my storage just being a list of numbers and letters and had to find a way to fully wipe and re install OOS) and the same for flashing, i could just flash something and it was fine, no issues.
Do you have an OTG adapter and pendrive? You can copy the full OTA zip, TWRP zip and Magisk zip on to that and flash from TWRP using that. Your internal storage is encrypted and you won't be able to access it until you can reboot OOS fully. If that didn't work, you may have to do a factory reset/wipe (including internal data) to get the phone to boot again. You will obviously lose any unbacked data.
Which version of TWRP are you using? Which version of OOS are you using? Most likely you just don't have the correct version, and you updated to the latest version OOS with the new security patch and it no longer can decrypt it.
Have you tried TWRP 3.3.1-7 from here? If you boot the .img file from fastboot, can you decrypt your data?
Most likely you just need to flash Magisk, and you will be fine. For updates, it's always as you did, flash the full OTA update, TWRP installer, reboot to recovery, Magisk. It is recommended to uninstall Magisk, however I usually don't do that personally. Official Instructions here. You just have to make sure you are using the correct version of TWRP, otherwise you can run into encryption issues, as you found out when there are updates.
OhioYJ said:
Which version of TWRP are you using? Which version of OOS are you using? Most likely you just don't have the correct version, and you updated to the latest version OOS with the new security patch and it no longer can decrypt it.
Have you tried TWRP 3.3.1-7 from here? If you boot the .img file from fastboot, can you decrypt your data?
Most likely you just need to flash Magisk, and you will be fine. For updates, it's always as you did, flash the full OTA update, TWRP installer, reboot to recovery, Magisk. It is recommended to uninstall Magisk, however I usually don't do that personally. Official Instructions here. You just have to make sure you are using the correct version of TWRP, otherwise you can run into encryption issues, as you found out when there are updates.
Click to expand...
Click to collapse
Latest twrp and latest full OOS OTA. If I fastboot the twrp. Img I can see all my data again. I've fixed it now, I flashed the twrp. Img in fastboot then rebooted system and it worked