Related
I just decided to move to CM12.1 on my Droid Turbo (XT1254) after the 1/27 Snapshot (YOG7DAO3J1) was posted. I am running this with TWRP 2.8.7.0, BHB27 Kernel, and OpenGAPPS 5.1. So far, almost everything has been fantastic and the performance of the device is like night and day compared to the Verizon software.
My problem is that the CM12.1 ROM has my device encrypted to begin with, which is nice but giving me trouble. I can't get into TWRP to install Xposed framework or other .zips via ADB. I have tried the following:
Disabling require password on startup
Changing the password in Android
Changing the password from root ADB shell
Using a pin
Trying "default_password"
Can anyone give me a solution or some advice? Any help is greatly appreciated!
Having same issue with TWRP not recognizing any decryption password given... Any ideas out there? Is TWRP incompatible with Droid Turbo HW Encryption, or ?
P_6 said:
Having same issue with TWRP not recognizing any decryption password given... Any ideas out there? Is TWRP incompatible with Droid Turbo HW Encryption, or ?
Click to expand...
Click to collapse
This thread is kinda old and I assumed nobody really knew what was going on with it either. I ended up just not using the encryption. The first time around mine was encrypted without me knowing, which was the issue. I just wiped all partitions and flashed the ROM again...
I am having a similar issue so i thought i would chime in, despite the older thread. I had a stock ROM that was encrypted and I was able to unlock and root with SunShine fine. Flashed on TWRP 2.8.7 and ran into a "Unable to mount storage. Failed to decrypt data" error. Updated to TWRP 3.0.0 and still have the same issue. Still working through a resolution as the phone is still functional if I just boot normally. When you mentioned you wiped all partitions, what process did you use? If i can just get access to the interal storage I can flash a ROM and be good to go.
Asyt said:
I am having a similar issue so i thought i would chime in, despite the older thread. I had a stock ROM that was encrypted and I was able to unlock and root with SunShine fine. Flashed on TWRP 2.8.7 and ran into a "Unable to mount storage. Failed to decrypt data" error. Updated to TWRP 3.0.0 and still have the same issue. Still working through a resolution as the phone is still functional if I just boot normally. When you mentioned you wiped all partitions, what process did you use? If i can just get access to the interal storage I can flash a ROM and be good to go.
Click to expand...
Click to collapse
So far, the only way I have been able to get encryption working with CM12.1 on the Droid Turbo is to do the folllowing (Note: This assumes you have bootloader unlocked and TWRP installed as your recovery):
Part 0: Make sure you have what you need
1. Stock Droid Turbo Firmware SU4TL for your device
2. The version of CyanogenMod 12.1 that you need. I recommend a Snapshot, but it's up to you.
3. TWRP 3.0.0 or later for your Droid Turbo.
Part 1: Final set up (Yes, we do this first)
1. Download CM12.1 & Download OpenGapps arm for 5.1
2. Wipe device (system, data, cache, internal storage), copy CM12 install zip and opengapps install zip via USB to device.
3. Flash CM12 and OpenGapps in TWRP
4. Set up device how you want it to be (install your apps, set up your accounts, etc).
5. Set whatever lock-screen PIN / Password / Pattern you are going to want on your phone in general!
6. Make a Nandroid backup of your 100% set up phone in TWRP
7. Copy your backup TWRP folder to your PC.
Part 2: Encrypt device and put everything back how we want it.
1. Flash stock Verizon firmware (SU4TL) via Fastboot. Do not flash stock Recovery, but put back TWRP if you did somehow (I use a simple bash script I have attached below).
2. Boot device, go through initial set up, don't download apps (we're going to be wiping the device soon).
3. Make sure your battery is 80%+ charged, and your device is plugged in.
4. Set a password or PIN on your phone.
5. Encrypt your device (this will be fairly fast, as /data is empty, but you should be asked for your encryption password on boot.)
6. Reboot to recovery. TWRP will ask you for your password to decrypt. It should work with no problem.
7. Copy your backed-up TWRP folder with your CM12 install to your device via USB. The TWRP folder goes in the Internal Storage root directory.
8. Still in TWRP (Do not reboot), go to Restore, and select the backup you just copied over. This will replace the stock rom with your CM12 backup.
9. Your CM12 install will be restored, but your device will remain Encrypted.
10. Reboot into CM12. Win.
You will need to decrypt your device every boot with the password that you selected when you initially encrypted your device. Your lock-screen password CAN BE DIFFERENT. That is why I do it this way. I have a fairly long password to decrypt my device on boot-up, but a pattern as my lock screen. That way I can quickly get into my phone during daily use without having to constantly type in a fairly complicated password.
I failed similar times to root my phone with twrp 3.2.xx and 3.1.xx. I used Odin 3 v3.13.1.
Any ideas or thread links for the young padawan?
I appreciate your advice masters :good:
Using Odin Flash TWRP latest from the note 8 TWRP thread here on XDA, one on their site is not latest.
Install magisk manager app from play store.
Download magisk from the app.
Reboot to TWRP and flash the magisk file just downloaded.
Reboot and check magisk manager for root and hide.
Should be good.
Nope. Not working and still ends in a bootloop and it's unable to mount the internal storage.
Something went wrong, so.. my phone is unable to boot the system after that!
The issue is the version of TWRP and Oreo, its not yet compatible on this device, it needs porting over
If you want MAGISK you need to do it all in one hit.
Flash TWRP
Select Read Only Option.
Format Data
Reboot Recovery
Flash the DM Verify Encrypt file
Reboot Recovery, You could be able to flash files wihtout a Data mount error.
Now flash the files you want, i..e MAGISK
Once you have booted the ROM and return back to TWRP you are unable to mount Data.
This can cause various issue when flashing files
Funny you.. How can I format if the internal storage isn't able to mount?
"Select Read Only Option.
Format Data" <-- seems like a contradiction to format a missing
partition.
I think we need to wait until someone will port the twrp for Oreo. cheerio!
Because it needs to be done when you first flash it.
Once you have flash Oreo, Then TWRP, You boot into TWRP and format. You then Flash the DM Verify.
Data is accessible, its empty but accessible, Flashing any files like MAGISK work without any errors.
I have it all working on mine without any issues, I do know if i need to flash any additional files it wont work properly due to Data no longer mountable.
There is a updated version of TWRP that fixes this, but its not been ported over.
Hello Guys! In the past 2 days i wanted to rebrand my phone (Huawei P9 EVA-L09) to the AL10 chinese version with a guide i found in the thread of the HWOTA7 tool. I succesfully flashed it without complications. But then my luck went out and i maybe have softbricked my phone. Here's how it happened.
As i did't like huawei's emui i wanted to load the Base ROM on my phone for flashing my favorite rom, Resurrection Remix. After i flashed my phones RAMDISK with the TWRP version as explained in Tecalotes post (fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img) i went straight in it to flash the img because i didn't know what command i needed to flash it over fastboot. So i tried wiping the Dalvik-/cache, factory reset and then wiping data. Then i went to rebooting my phone into the OS to check if the files are in the right place, but then it just was stuck at the screen (Your device has been unlocked and can't be trusted.) and down below just stands "Your device is booting now". I thought it just could take a while, but even after 10 minutes it did't change a bit, then it automatically reset to the eRecovery. After browsing in some german forums i found out that my phone isn't lost yet After this i booted TWRP again over fastboot and deleted all system files. Then nothing worked anymore. Tried sideloading, it said adb: error: connect failed: closed. or uknowncommand[errno] and then it stopped). I sat there for 6 hours, then my big IQ tried the UPDATE.app extractor and extracted recovery, system, ramdisk and vendor and flashed it. And it worked, it booted in eRecovery again and said "Your OS has mayor errors, do you wan't to download latest version and recovery?". I accepted. It downloaded for 10 minutes, then i repeated the last step of HWOTA7 and again, it worked. Then i could boot in the OS again, and enable ADB Debug and USB debug. After that i booted in TWRP and tried staying at EMIU 8, but again, i couldn't find the files. Then i tried sideload, again a error telling me that sideloading can't be done. Rebooted in OS, again stuck at the screen after the unlocking. I did go to sleep. Now its day 2 and i am writing here with my phone at the side in eRecovery. This time i didnt wipe anything else than data and the cache, also i did a factory reset. I easely can go in the OS again, but then i still would get the false directory without any files and couldnt load OpenGapps and the network fix or the BASE ROM, because i know now that it isnt a problem with base rom. I grately would accept anyone that can help. Also i cant use a SD card because i do not have the money for it right now because i'm in high school. Besides that, I personally think it's a faulty directory because of the TWRP. Also i can't go back to nougat because i can't find the zips. If someone is a expert, hit me up in the DMs here and if i got a fix i write it on this post for everyone that has this problem and i will mention the god that found it!
Many regards!
Since you have followed the re-branding guide by @Tecalote, why didn't you follow also his instructions for going back to stock (Oreo or even Nougat)
https://forum.xda-developers.com/showpost.php?p=77161314&postcount=3
Same things have also been asked in the Open Kirin thread, see e.g.
https://forum.xda-developers.com/showpost.php?p=77589852&postcount=79
Good luck, as long as you have Fastboot and eRecovery, your phone is not dead
Restore your phone and try to be not confused
Bumo Gaming said:
Hello Guys! In the past 2 days i wanted to rebrand my phone (Huawei P9 EVA-L09) to the AL10 chinese version with a guide i found in the thread of the HWOTA7 tool.
As i did't like huawei's emui i wanted to load the Base ROM on my phone for flashing my favorite rom, Resurrection Remix.
After i flashed my phones RAMDISK with the TWRP version as explained in Tecalotes post (fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img) i went straight in it to flash the img because i didn't know what command i needed to flash it over fastboot.
Click to expand...
Click to collapse
Okay, first of all → You should learn to read the instructions carefully. And if you do not understand something, then you should ask first - in the Rebrand Thread - before you do something!
"After i flashed my phones RAMDISK with the TWRP" → which ramdisk to you mean? Since you speak of the "Base ROM", you refer to the renewed post # 2 in the Rebrand Thread. I did not mention anything about flashing a "Ramdisk" there.
Note: ramdisk.img = similar the same than boot.img on Android 7 → and if, it must be flashed to: ramdisk
recovery_ramdisk = on Oreo the place of Recovery on the phone (on Nougat it was: recovery) → and if, it must be flashed to: recovery_ramdisk
In post # 2 I do not offer "ramdisk" for download or to flash.
There are only two recoveries to flash there: 1) P9-EVA-8.0.0-TWRP-v4.img → which must be flashed to: recovery_ramdisk and
2) b528-RECOVERY_RAMDIS.img, which is the EMUI-Stock-Recovery → and must be flashed to the same place: recovery_ramdisk (after flashing the Base ROM for doing the Factory reset)
"After i flashed my phones RAMDISK with the TWRP version as explained in Tecalotes post (fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img) i went straight in it to flash the img because i didn't know what command i needed to flash it over fastboot."
BTW: every Recovery (TWRP, EMUI-Stock-Recovery) can be flashed in Fastboot Mode with: fastboot flash recovery_ramdisk "name-of-the-file".img
→ That means, you flashed already TWRP (P9-EVA-8.0.0-TWRP-v4.img) in Fastboot Mode and you did boot into TWRP → and then?? Which img did you flash then? I did not mention to flash any img immediately after flashing TWRP.
→ After flashing TWRP you should flash either the NetworkPatch.zip or the Base ROM (suitable for your device) and after that you should: Reboot Recovery from TWRP main menu, after TWRP is rebooted you should flash: b528-RECOVERY_RAMDIS.img to: recovery_ramdisk - and NOT TO: ramdisk!!
It is well explained in the Thread.
The next step would be to Reboot Recovery from TWRP main menu into Stock Recovery (which is flashed right now) and perform from EMUI-Stock-Recovery Wipe Cache Partition and Factoryreset....
→ if you flashed b528-recovery_ramdis.img to ramdisk instead to: recovery_ramdisk → then it's clear why your P9 did not boot into the system and was stuck on the Bootscreen!
→ But what I dont understand is: How could you flash recovery_ramdis.img with TWRP if you have no external SD??
I wrote directly under the Download-Link of TWRP a short summary about this TWRP and I told clearly, that this TWRP has currently no access to /data and the internal storage → therefore: nothing can be done without external SD!
So, my question is - from where can you flash anything?
→ It would only possible to flash anything without external SD, if you did "format data" → but that would be a completely wrong step that I have not mentioned anywhere in the instructions.
"Format data" is only required, if you use HuRUpdater, as long TWRP can not decrypt the encrypted data Partiton.
→ But "Format data" can not be used for doing the NetworkPatch or flashing the Base Rom → it requires, that /data is originally encrypted - and NOT formatted.
Bumo Gaming said:
So i tried wiping the Dalvik-/cache, factory reset and then wiping data. Then i went to rebooting my phone into the OS to check if the files are in the right place, but then it just was stuck at the screen (Your device has been unlocked and can't be trusted.) and down below just stands "Your device is booting now". I thought it just could take a while, but even after 10 minutes it did't change a bit, then it automatically reset to the eRecovery.
Click to expand...
Click to collapse
Clear, if you did several things wrong and and not according to the instructions, the phone can not boot and goes and goes after some unsuccessful attempts into eRecovery.
→ But that would not be any problem. Because it is possible on rebranded P9 to EVA-AL10 - to use eRecovery. Just click on "Download latest version and recovery" - then P9 connects to the wifi, get the info package and download and restore your P9 to latest approved Firmware.
"So i tried wiping the Dalvik-/cache, factory reset and then wiping data. " - forget about it → if TWRP has no access to /data - you can not wipe Dalvik and you can not do Factory reset and you can not wipe data with TWRP! → Thats why I advised to do it with Stock EMUI Recovery after the zips are flashed.
Bumo Gaming said:
After browsing in some german forums i found out that my phone isn't lost yet After this i booted TWRP again over fastboot and deleted all system files. Then nothing worked anymore. Tried sideloading, it said adb: error: connect failed: closed. or uknowncommand[errno] and then it stopped). I sat there for 6 hours, then my big IQ tried the UPDATE.app extractor and extracted recovery, system, ramdisk and vendor and flashed it. And it worked, it booted in eRecovery again and said "Your OS has mayor errors, do you wan't to download latest version and recovery?". I accepted.
It downloaded for 10 minutes, then i repeated the last step of HWOTA7 and again, it worked. Then i could boot in the OS again, and enable ADB Debug and USB debug. After that i booted in TWRP and tried staying at EMIU 8, but again, i couldn't find the files. Then i tried sideload, again a error telling me that sideloading can't be done. Rebooted in OS, again stuck at the screen after the unlocking.
Click to expand...
Click to collapse
→ There is a much more simple way to restore your Phone that it can work again properly. I will write at the end.
→ You should not flash any GApps - Open GApps - or whatever, because GApps are not compatible with this firmware and not necessary. All necessary Google core apps and Google services are included in the firmware. Most of them not in the system, but in the data partiton.
→ The NetworkPatch zip as well as the Base Rom are including Playstore and Gboard and all the other Google Apps you need, you can simply install from Playstore.
→ You should not use HWOTA7 on Oreo - it is programmed to work on Android 7 (hwota7) and not on Android 8. It includes TWRP for Android 7 and not for Android 8 - and I already mentioned it in OP.
Bumo Gaming said:
I grately would accept anyone that can help. Also i cant use a SD card because i do not have the money for it right now because i'm in high school. Besides that, I personally think it's a faulty directory because of the TWRP. Also i can't go back to nougat because i can't find the zips. If someone is a expert, hit me up in the DMs here and if i got a fix i write it on this post for everyone that has this problem and i will mention the god that found it! Many regards!
Click to expand...
Click to collapse
→ if you have no money for SD Card or USB OTG, you can go back to a working system (EVA-AL10 as well as make a downgrade to Nougat) - I have it already explained in Post #3 as @zgfg told you - but you will not be able for now to use the NetworkPatch.zip or the Base ROM.zip, because this TWRP can only flash from Micro SD or USB OTG (current version, until decryption of encrypted data is solved)
→ it could be done instead with Root and copy the files from the NetworkPatch.zip to the right places to replace the existent ones. But I made no instruction for it right now.
→ this TWRP has no "faulty directory" and everything is working correctly, except you can not use internal storage for now
→ "everyone that has this problem" - will only have it, if he is quite confused and does not know what he is doing - neither reads instructions properly, nor asks if he does not know
→ if you want to go back to Nougat, read Post #3, it is well explained. The Link EVA-AL10b399Sp17a /Android 7 you can find in Post #2
Using HuRUpdater from internal storage:
1) Flash TWRP for Oreo (not the one from hwota7, which is for Nougat) - flash it in Fastboot Mode with the code in Post #2
2) Boot into TWRP and use: Wipe and right down the Button: format data (for HuRUpdater it is required ) - confirm format data by typing:yes → go back (after) to main menu of TWRP and use: Reboot - but not system - Reboot instead: Recovery
3) Phone reboot again to TWRP and then TWRP is able to see the internal storage (because data is formatted - but note: this practice can not be used for the Base ROM and also not for the NetworkPatch, because it requires original encrypted storage!!)
4) Connect USB cable to P9 and PC - you should see internal storage in Windows Explorer.
If not, go to the Button "Mount" in TWRP and click 1x on "disable MTP" and then "enable MTP" - now you should see the internal storage in Windows Explorer.
6) Make a folder on your internal storage, name it as you like - Copy inside this folder:
a) HuRUpdater 0.4
b) update.zip
c) update_data_public.zip (= renamed, as written in OP)
d) update_all_hw.zip (=renamed, as written in OP)
→ Note: If you use EVA-AL10C00B528 for this operation, you will stay on Oreo, with properly installed Firmware (but without NetworkPatch...)
→ if you use instead EVA-AL10b399Sp17a for this operation, you will downgrade to Nougat, EVA-AL10 and can then use HWOTA7 to rebrand back to your original P9
After you copied the files, disconnect USB from P9.
7) Navigate to the folder you had created on internal storage (with HuRUpdater inside) and flash now ONLY the file: HuRUpdater.
8) The Battery will make some noice - in that moment press shortly VOL- (not Vol+) and HuRUpdater will flash the Firmware (all 3 zip files) from your folder automatically.
9) After it is succesfully flashed, click on the left button to Wipe Dalvik and Cache (it will work now, because of decrypted data) → the go back to the main menu and use again Reboot - But not System! - you choose: Reboot Recovery. This will reboot the Phone into EMUI-Stock-Recovery
10) In Stock Recovery make first Wipe Cache Partition and then Factory Reset → you have a properly working system back.
Can't you borrow an SD card of 4 GB to execute HuRU, I'm not sure could it work from Internal mem
zgfg said:
Can't you borrow an SD card of 4 GB to execute HuRU, I'm not sure could it work from Internal mem
Click to expand...
Click to collapse
SD Card is easier, but HuRUpdater works also from internal storage → and it works also from USB (with OTG cable)
Only problem, TWRP hasn't support for encrypted data yet - but the steps with format data and then copy with PC in Windows Explorer the required files to internal storage, should solve this. ( for this case)
Tecalote said:
Okay, first of all → You should learn to read the instructions carefully. And if you do not understand something, then you should ask first - in the Rebrand Thread - before you do something!
"After i flashed my phones RAMDISK with the TWRP" → which ramdisk to you mean? Since you speak of the "Base ROM", you refer to the renewed post # 2 in the Rebrand Thread. I did not mention anything about flashing a "Ramdisk" there.
Note: ramdisk.img = similar the same than boot.img on Android 7 → and if, it must be flashed to: ramdisk
recovery_ramdisk = on Oreo the place of Recovery on the phone (on Nougat it was: recovery) → and if, it must be flashed to: recovery_ramdisk
In post # 2 I do not offer "ramdisk" for download or to flash.
There are only two recoveries to flash there: 1) P9-EVA-8.0.0-TWRP-v4.img → which must be flashed to: recovery_ramdisk and
2) b528-RECOVERY_RAMDIS.img, which is the EMUI-Stock-Recovery → and must be flashed to the same place: recovery_ramdisk (after flashing the Base ROM for doing the Factory reset)
"After i flashed my phones RAMDISK with the TWRP version as explained in Tecalotes post (fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img) i went straight in it to flash the img because i didn't know what command i needed to flash it over fastboot."
BTW: every Recovery (TWRP, EMUI-Stock-Recovery) can be flashed in Fastboot Mode with: fastboot flash recovery_ramdisk "name-of-the-file".img
→ That means, you flashed already TWRP (P9-EVA-8.0.0-TWRP-v4.img) in Fastboot Mode and you did boot into TWRP → and then?? Which img did you flash then? I did not mention to flash any img immediately after flashing TWRP.
→ After flashing TWRP you should flash either the NetworkPatch.zip or the Base ROM (suitable for your device) and after that you should: Reboot Recovery from TWRP main menu, after TWRP is rebooted you should flash: b528-RECOVERY_RAMDIS.img to: recovery_ramdisk - and NOT TO: ramdisk!!
It is well explained in the Thread.
The next step would be to Reboot Recovery from TWRP main menu into Stock Recovery (which is flashed right now) and perform from EMUI-Stock-Recovery Wipe Cache Partition and Factoryreset....
→ if you flashed b528-recovery_ramdis.img to ramdisk instead to: recovery_ramdisk → then it's clear why your P9 did not boot into the system and was stuck on the Bootscreen!
→ But what I dont understand is: How could you flash recovery_ramdis.img with TWRP if you have no external SD??
I wrote directly under the Download-Link of TWRP a short summary about this TWRP and I told clearly, that this TWRP has currently no access to /data and the internal storage → therefore: nothing can be done without external SD!
So, my question is - from where can you flash anything?
→ It would only possible to flash anything without external SD, if you did "format data" → but that would be a completely wrong step that I have not mentioned anywhere in the instructions.
"Format data" is only required, if you use HuRUpdater, as long TWRP can not decrypt the encrypted data Partiton.
→ But "Format data" can not be used for doing the NetworkPatch or flashing the Base Rom → it requires, that /data is originally encrypted - and NOT formatted.
Clear, if you did several things wrong and and not according to the instructions, the phone can not boot and goes and goes after some unsuccessful attempts into eRecovery.
→ But that would not be any problem. Because it is possible on rebranded P9 to EVA-AL10 - to use eRecovery. Just click on "Download latest version and recovery" - then P9 connects to the wifi, get the info package and download and restore your P9 to latest approved Firmware.
"So i tried wiping the Dalvik-/cache, factory reset and then wiping data. " - forget about it → if TWRP has no access to /data - you can not wipe Dalvik and you can not do Factory reset and you can not wipe data with TWRP! → Thats why I advised to do it with Stock EMUI Recovery after the zips are flashed.
→ There is a much more simple way to restore your Phone that it can work again properly. I will write at the end.
→ You should not flash any GApps - Open GApps - or whatever, because GApps are not compatible with this firmware and not necessary. All necessary Google core apps and Google services are included in the firmware. Most of them not in the system, but in the data partiton.
→ The NetworkPatch zip as well as the Base Rom are including Playstore and Gboard and all the other Google Apps you need, you can simply install from Playstore.
→ You should not use HWOTA7 on Oreo - it is programmed to work on Android 7 (hwota7) and not on Android 8. It includes TWRP for Android 7 and not for Android 8 - and I already mentioned it in OP.
→ if you have no money for SD Card or USB OTG, you can go back to a working system (EVA-AL10 as well as make a downgrade to Nougat) - I have it already explained in Post #3 as @zgfg told you - but you will not be able for now to use the NetworkPatch.zip or the Base ROM.zip, because this TWRP can only flash from Micro SD or USB OTG (current version, until decryption of encrypted data is solved)
→ it could be done instead with Root and copy the files from the NetworkPatch.zip to the right places to replace the existent ones. But I made no instruction for it right now.
→ this TWRP has no "faulty directory" and everything is working correctly, except you can not use internal storage for now
→ "everyone that has this problem" - will only have it, if he is quite confused and does not know what he is doing - neither reads instructions properly, nor asks if he does not know
→ if you want to go back to Nougat, read Post #3, it is well explained. The Link EVA-AL10b399Sp17a /Android 7 you can find in Post #2
Using HuRUpdater from internal storage:
1) Flash TWRP for Oreo (not the one from hwota7, which is for Nougat) - flash it in Fastboot Mode with the code in Post #2
2) Boot into TWRP and use: Wipe and right down the Button: format data (for HuRUpdater it is required ) - confirm format data by typing:yes → go back (after) to main menu of TWRP and use: Reboot - but not system - Reboot instead: Recovery
3) Phone reboot again to TWRP and then TWRP is able to see the internal storage (because data is formatted - but note: this practice can not be used for the Base ROM and also not for the NetworkPatch, because it requires original encrypted storage!!)
4) Connect USB cable to P9 and PC - you should see internal storage in Windows Explorer.
If not, go to the Button "Mount" in TWRP and click 1x on "disable MTP" and then "enable MTP" - now you should see the internal storage in Windows Explorer.
6) Make a folder on your internal storage, name it as you like - Copy inside this folder:
a) HuRUpdater 0.4
b) update.zip
c) update_data_public.zip (= renamed, as written in OP)
d) update_all_hw.zip (=renamed, as written in OP)
→ Note: If you use EVA-AL10C00B528 for this operation, you will stay on Oreo, with properly installed Firmware (but without NetworkPatch...)
→ if you use instead EVA-AL10b399Sp17a for this operation, you will downgrade to Nougat, EVA-AL10 and can then use HWOTA7 to rebrand back to your original P9
After you copied the files, disconnect USB from P9.
7) Navigate to the folder you had created on internal storage (with HuRUpdater inside) and flash now ONLY the file: HuRUpdater.
8) The Battery will make some noice - in that moment press shortly VOL- (not Vol+) and HuRUpdater will flash the Firmware (all 3 zip files) from your folder automatically.
9) After it is succesfully flashed, click on the left button to Wipe Dalvik and Cache (it will work now, because of decrypted data) → the go back to the main menu and use again Reboot - But not System! - you choose: Reboot Recovery. This will reboot the Phone into EMUI-Stock-Recovery
10) In Stock Recovery make first Wipe Cache Partition and then Factory Reset → you have a properly working system back.
Click to expand...
Click to collapse
Thanks for your help for people that may come in this thread with the same problem, fortunally 2 days after this post i totally forgot about it and i allready got a fix that was right in my nose. With Ramdisk i ment the TWRP recovery_ramdisk that you provided for installing the network patch or the BaseRom on the Oreo version of the AL10 Firmware. In the timespan of 2 days i found myself finding a old SD Card in my old broken phone that had 64 GB, so plenty for installing everything. With my foolishness as a beginner at that time i cleared every system partition even if there was no need for it and as i said i had the eRecovery with the install newest version of recovery and EMUI, that for some reason was set on the AL10 8.0.0 patch what still was in beta. I figured it all out after looking in some posts of the thread of the HWOTA7 tool and the post for unofficial update to oreo and just followed everything once again but this time with the SD Card, now my phone is partly stable with the custom rom i installed because of your tutorial. I want to thank you for that and give you my up-most respect for taking the time and helping out people like me that just came to the forums and didn't really understand a thing at first. With that out of the way i will take insperation from you and help others out in this wonderfull community.
BTW: every Recovery (TWRP, EMUI-Stock-Recovery) can be flashed in Fastboot Mode with: fastboot flash recovery_ramdisk "name-of-the-file".img
→ That means, you flashed already TWRP (P9-EVA-8.0.0-TWRP-v4.img) in Fastboot Mode and you did boot into TWRP → and then?? Which img did you flash then? I did not mention to flash any img immediately after flashing TWRP.
→ After flashing TWRP you should flash either the NetworkPatch.zip or the Base ROM (suitable for your device) and after that you should: Reboot Recovery from TWRP main menu, after TWRP is rebooted you should flash: b528-RECOVERY_RAMDIS.img to: recovery_ramdisk - and NOT TO: ramdisk!!
Click to expand...
Click to collapse
I was refering to the TWRP.img i was talking about. I really don't know what i ment by not knowing the command. Also with the ramdisk i got confused between recovery_ramdisk and ramdisk, but i didn't flash the b528 in the wrong kind of ramdisk. Because i was still new to it i didn't know the difference and just called the recovery_ramdisk; ramdisk what may have confused you.
Also with the DATA i've figured out that it can't get accessed by TWRP due to not having encryption. That's where i tried sideloading baserom or network-patch that gave me back the error that it wouldn't install the zip. So i got confused because it worked when i still had the L09 Firmware and flashed RROS 5.8.5 that was on nougat and not on oreo, a big difference now for me after i was looking it up. Thats really the problem i had and fixed allready but i didn't want to leave you without an explanation.
→ You should not flash any GApps - Open GApps - or whatever, because GApps are not compatible with this firmware and not necessary. All necessary Google core apps and Google services are included in the firmware. Most of them not in the system, but in the data partiton.
Click to expand...
Click to collapse
Also also i tried flashing GApps because for some unknown reason the first time i had my os back to the CHINESE firmware that didn't come with the Playstore but rather their own chinese stuff so i got confused and tried getting the Playstore with flashing the OpenGapps what as we know didn't work out that well.
→ "everyone that has this problem" - will only have it, if he is quite confused and does not know what he is doing - neither reads instructions properly, nor asks if he does not know
Click to expand...
Click to collapse
i tried reading the instructions but i misinterpreted them for no reason what-so-ever. Also i had a bit of a problem with xda 'cus i couldn't create a account over my IP because it said i allready created one with this ip today, so i needed to figure out how to find my old account, but it's a whole story for itself. Still i want to thank you for taking out your time for helping people like me.
Many regards
Bumo Gaming said:
Thanks for your help for people that may come in this thread with the same problem, fortunally 2 days after this post i totally forgot about it and i allready got a fix that was right in my nose. With Ramdisk i ment the TWRP recovery_ramdisk that you provided for installing the network patch or the BaseRom on the Oreo version of the AL10 Firmware. In the timespan of 2 days i found myself finding a old SD Card in my old broken phone that had 64 GB, so plenty for installing everything. With my foolishness as a beginner at that time i cleared every system partition even if there was no need for it and as i said i had the eRecovery with the install newest version of recovery and EMUI, that for some reason was set on the AL10 8.0.0 patch what still was in beta. I figured it all out after looking in some posts of the thread of the HWOTA7 tool and the post for unofficial update to oreo and just followed everything once again but this time with the SD Card, now my phone is partly stable with the custom rom i installed because of your tutorial. I want to thank you for that and give you my up-most respect for taking the time and helping out people like me that just came to the forums and didn't really understand a thing at first. With that out of the way i will take insperation from you and help others out in this wonderfull community.
I was refering to the TWRP.img i was talking about. I really don't know what i ment by not knowing the command. Also with the ramdisk i got confused between recovery_ramdisk and ramdisk, but i didn't flash the b528 in the wrong kind of ramdisk. Because i was still new to it i didn't know the difference and just called the recovery_ramdisk; ramdisk what may have confused you.
Also with the DATA i've figured out that it can't get accessed by TWRP due to not having encryption. That's where i tried sideloading baserom or network-patch that gave me back the error that it wouldn't install the zip. So i got confused because it worked when i still had the L09 Firmware and flashed RROS 5.8.5 that was on nougat and not on oreo, a big difference now for me after i was looking it up. Thats really the problem i had and fixed allready but i didn't want to leave you without an explanation.
Also also i tried flashing GApps because for some unknown reason the first time i had my os back to the CHINESE firmware that didn't come with the Playstore but rather their own chinese stuff so i got confused and tried getting the Playstore with flashing the OpenGapps what as we know didn't work out that well.
i tried reading the instructions but i misinterpreted them for no reason what-so-ever. Also i had a bit of a problem with xda 'cus i couldn't create a account over my IP because it said i allready created one with this ip today, so i needed to figure out how to find my old account, but it's a whole story for itself. Still i want to thank you for taking out your time for helping people like me.
Many regards
Click to expand...
Click to collapse
Many thanks for your detailed feedback! :good:
slayernn said:
Plz HELP! History: I did everything from this thread and it worked fine for few monts until last official update, after that sim card was not recognised. I did lots of mistakes after,cant even imagine.. what i did in end is that i changed oem info via hwota to EVA-L09C636 and put again chinese EVA-AL10 oreo.. now my android system have lots of problem, no aps, keyboard was gone (only chinese kb and somehow i managed to put en). Everything is messed. Now problem gets bigger: OEM unlock is grayed in developer options, so i cant unlock bootloader (and in fastboot mode, bootloader and FRP are locked), so there is no way to put TWRP and everything look bricked (( Also dload update always fail at 5% with any room i try... Pls help me, i just want to go back to original nougat, like when i bought and forget chinese brand and oreo... Thanx in advance
droid info app:
Model: EVA-L09 (EVA-L09)
Manufacturer: HUAWEI
Baseband Version: 21.258.09.00.030
RIL Version: android infineon balong-ril 1.0
Build Number: System 8.0.0.046(0EET)
Build Fingerprint: Huawei/generic_a15/generic_a15:8.0.0/OPR6.170623.010/jenkin07111806:user/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: O (8.0.0)
SDK: 26
Click to expand...
Click to collapse
zgfg said:
First and most important for any further analysis, please clearly write on which exact build name/number you are
Can you post a screenshot of Setting/About
Click to expand...
Click to collapse
slayernn said:
Plz HELP! History: I did everything from this thread and it worked fine for few monts until last official update, after that sim card was not recognised. I did lots of mistakes after,cant even imagine..
Click to expand...
Click to collapse
1) It is normally → mobile network and IMEI is lost after OTA Update, but as you can read above - no problem to solve, if you doing the right steps
2) For the next time: First ask here in this Thread: https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849/page93#post77981310
if you face anything you dont know how to do.... before you are doing steps without sence
Where do you live? Because if you live in Germany, I could repair.
If not, we will find a solution - I am just think about it
@slayernn
I moved your issue to this Thread, because it is OT in the main Thread, since your problem is not made by me or my instructions, but because you did several things wrong without asking before.
Here is a Repair Firmware - which can be flashed with dload method (inside is also instructions). I will download in the evening and have a look. Then I can give you further instructions, how to use it. So far I remember, it must be extracted two times....
Huawei P9 EVA-AL10 8.0.0.528(C00) Firmware Android8.0:
https://androidhost.ru/6sl
Tecalote said:
1) It is normally → mobile network and IMEI is lost after OTA Update, but as you can read above - no problem to solve, if you doing the right steps
2) For the next time: First ask here in this Thread: https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849/page93#post77981310
if you face anything you dont know how to do.... before you are doing steps without sence
Where do you live? Because if you live in Germany, I could repair.
If not, we will find a solution - I am just think about it
@slayernn
I moved your issue to this Thread, because it is OT in the main Thread, since your problem is not made by me or my instructions, but because you did several things wrong without asking before.
Here is a Repair Firmware - which can be flashed with dload method (inside is also instructions). I will download in the evening and have a look. Then I can give you further instructions, how to use it. So far I remember, it must be extracted two times....
Huawei P9 EVA-AL10 8.0.0.528(C00) Firmware Android8.0:
https://androidhost.ru/6sl
Click to expand...
Click to collapse
Thanx man and sorry for posting in wrong thread. I'm looking forward! Downloading file right now.
Best regards , ps damn slow download from link (takes 8h to dl) you provide. Is there alternative?
slayernn said:
Thanx man and sorry for posting in wrong thread. I'm looking forward! Downloading file right now.
Best regards , ps damn slow download from link (takes 8h to dl) you provide. Is there alternative?
Click to expand...
Click to collapse
Yes, this is really a slow download, but no - it's the only place where you can get Firmware, which is installable with dload method!
If you create a User on this Site, download is faster, but needs even some hours....
@slayernn
When your Download is ready → you have: Huawei P9 EVA-AL10 8.0.0.528(C00) Firmware Android8.0 EMUI8.0.0 05014GSG androidhost.ru.zip
Rename it to: Huawei P9 EVA-AL10 8.0.0.528.zip
→ unpack/extract zip, then you have the folder: Huawei P9 EVA-AL10 8.0.0.528 - the folder contains:
ReleaseDoc
Software - go inside this folder, there is: SDupdate_Package.tar.gz → unzip/extract it, then you have the folder: SDupdate_Package.tar - this folder contains:
SDupdate_Package.tar - unzip/extract it, then you get finally the folder: SDupdate_Package - and this folder contains, what we need, the folder:
dload
Inside this folder you find the UPDATE.APP - and probably one or two additional folders with another UPDATE.APP (for the location, example: update_EVA-AL10_all_cn.app)
Now you have two possibilites
A)
1) Flash first the UPDATE.APP with dload method → after it is flashed, dont boot to system, press VOL+ during automatically restart to enter EMUI-Recovery
2) reject SD-Card, delete the previous update.app and copy the second update.app (update_EVA-AL10....) into dload folder → rename it to: UPDATE.APP
3) In EMUI-Recovery go to Reboot and during restart press Vol+ and Vol- to force update:
4) now second UPDATE.APP will be flashed → after it is flashed, dont boot to system, press VOL+ during automatically restart to enter EMUI-Recovery
5) delete second Update.app in dload folder and copy the first UPDATE.APP again into dload folder and flash it once again with dload → once you have done this and phone reboot automatically, press again VOL+ to enter EMUI-Recovery
6) Make Wipe Cache and Factoryreset
7) Phone should boot → and be able to enable OEM-Unlock → then a downgrade to Nougat and rebranding would be possible (ask me for the steps, before doing)
B) Second possibility (costs about 15 EUR, but it is easier and probably better)
Buy from DC 15 Credits (=15 EUR) from here: https://www.dc-unlocker.com/buy
Download DCPhoenix Software v63 - extract it and open DCPhoenix, log-in to your Account
In the first field above choose the big, first UPDATE.APP
on Customation field select the second UPDATE.APP (no need to rename for DC)
Flash it → additional you can change oeminfo on second tab....
Wish you success
@slayernn
I answered your PM → forgot to ask: Can you please tell me each exately name of the second two folders (with the two other update.app)
Thx
@slayernn It would be good if you write a summary here with the steps (as far as you remember) - how you managed to restore your P9
Tecalote said:
@slayernn It would be good if you write a summary here with the steps (as far as you remember) - how you managed to restore your P9
Click to expand...
Click to collapse
First of all, thank you Tecalote on all your tutorials and support in every step, without you restoring phone to original stock state would be imposible.
In short, i will explain what problem i had and how it is fixed.
History:
My P9 EVA-L09 was changed to EVA-AL10 and oreo, after few stupid mistakes in a rush, i changed oem info to EVA-L09c63.. and re-update AL-10 files in final step from hwota7. After that i got semi bricked device, oreo with damaged build number, oem info, and most important bootloader/frp was locked and couldnt change oem unlock (it was grayed). After that i tried many different fw/roms via dload method without success until Tecalote suggest downloading Huawei P9 EVA-AL10 8.0.0.528. UPDATE.app of that pack always worked and it was crucial later, but next dload EVA-AL10_all_cn didnt work, so i was at beginning again, with damaged oreo.
What i did later and steps that restore my device to stock nougat:
Next thing i did is taking DC-Phoenix + HCU timed license after which i tried to change oem info, but in dc-phoenix there was no EVA-L09 so i used EVA-L29 and tried some appropriate files to upload. It ended with errors and phone was dead bricked.. cant power on/dload/recovery but dc-phoenix still recognise it in fastboot so then i tried to upload EVA-AL10 8.0.0.528 again and it worked, during period of update device was unlocked and i realised i could use hwota7 tool during that time, just to unlock bootloader with code, so i did and it was successful, was it clever? dont know! What i got now is old oreo with f****d oem info / build etc but unlocked. Next thing i did is to use HCU program and in repair cdma tab, i changed model/vendor/country to EVA-L09/hw/eu! Right after that uploaded EVA-L09_C432B390_Firmware_France_Ger... and update_EVA-L09_C432B390_hw_eu from dc-phoenix and it was successful! Now i got nougat (poor without camera and so) and original EVA-L09 model name. Next, Tecalote send me HWOTA download link and steps to take https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3 and after that, phone was fully restored to original state and everything is working perfecto. It took me 2-3 days of work, many errors.. in a moments i was thinking that device is completely bricked and want it to throw in trash can. Never give up..thats point Best regards!
I would like a help, so I'm trying to install the rom via mi flash, but not installing the rom, it's in 500sec and nothing to complete the installation, luckily I was able to install via TWRP, however when I try to update via Android OTA 10 I get stuck in the bootloop.
need more info.
You installed Twrp I assume over the stock rom?
if so boot into TWRP and format user data. ( note this wipe completely erase the phone. but you have no choice it must be done. if you have files that you want on the phone, see you can access them via Windows explorer and copy them over to your desktop.
Basic Instructions
FORMAT /data partition (Important Never Ever Wipe System Or Persist!)
Copy our ROM to the internal storage or use external USB drive ( must choose which device to install from in twrp)
Install ROM, and anything else depending on rom if needed such as gapps
Reboot to recovery
Reboot to system and setup
tsongming said:
need more info.
You installed Twrp I assume over the stock rom?
if so boot into TWRP and format user data. ( note this wipe completely erase the phone. but you have no choice it must be done. if you have files that you want on the phone, see you can access them via Windows explorer and copy them over to your desktop.
Basic Instructions
FORMAT /data partition (Important Never Ever Wipe System Or Persist!)
Copy our ROM to the internal storage or use external USB drive ( must choose which device to install from in twrp)
Install ROM, and anything else depending on rom if needed such as gapps
Reboot to recovery
Reboot to system and setup
Click to expand...
Click to collapse
Now I managed to install the rom with Android 10 global, but the region is only in China, I can't change it and this one without facial unlocking.
NikolasG. said:
Now I managed to install the rom with Android 10 global, but the region is only in China, I can't change it and this one without facial unlocking.
Click to expand...
Click to collapse
I believe that @Agimax has a flashable mod on his stable page for changing regions, that seems to be a bug with the latest stable version.
Check here, and maybe tried pinging Agimax, if you need assistance.
https://forum.xda-developers.com/mi-8/themes/mods-miui-global-beta-region-free-t3898459/page5
Another option is flashing the latest Xiaomi.EU, which has every available feature some of which have not yet found their way to the stable build.
For the download links check Option 2
https://forum.xda-developers.com/mi-8/how-to/miui-11-xiaomi-eu-rom-released-t3974643
This is a bit late but why not. THIS IS A COMPILATION OF ALL THE OS METHODS YOU NEED FOR THE OP6/6T.
ENJOY my guide
DISCLAIMER:
*I am not responsible for bricked devices, damage to your device*
Sorry for a long list of methods, some work for others and some don't. But I recommend to pick a method and stick to it. Maybe read the part at the top as some have notes about mine or someone else's experience/recommendation. Don't skip steps and follow each step.
If stuck, just ask and I or anyone else will try and help
I am here to post methods for anyone who is interested/need help. I have tested these myself and helped others who may be struggling
Download
The guide has loads of files/ zips/ tools to use/flash/install. But no worries as everything can be downloaded and there are links AT THE BOTTOM OF THIS THREAD (NOT COMMENTS) to where to download:
SDK Platform Tools (Fastboot tools) from Developer Android
TWRP from mauronofrio
Magisk from topjohnwu
Gapps (Google Apps) from NikGapps. I recommend omni for ROMs that don't include Gapps.
Fastboot ROM for OP6 + OP6T from mauronofrio
MSMDownload tools for OP6 + OP6T from Some_Random_Username
IMPORTANT NOTES!
YOU REQUIRE Platform Tools (Fastboot Tools) IN ORDER TO USE THE METHODS IN THIS GUIDE AS TWRP NEEDS TO BE INSTALLED!
YOU NEED TO HAVE A UNLOCKED BOOTLOADER AS WELL!
For GAPPS, u can use the same or a updated version of the package. But has to be the same type u used to install it like (stock, full, Omni, basic, etc). ONLY FLASH/INSTALL IF the RESTORE SCRIPT DIDN'T SHOW UP during a DIRTY FLASH/UPDATE AND ONLY FLASH AFTER REBOOTING TO RECOVERY AFTER FLASHING/INSTALLING A OS/BUILD ZIP FILE!
How to get Platform Tools
These tools are used to install TWRP, to unlock the bootloader of your device and is needed to use the METHODS in this guide.
Download the platform tools.zip of your software platform (Mac, Windows, Linux)
Extract the platform-tools.zip
To use it go into your platform-tools folder
Press shift + right-click and choose command prompt or PowerShell
Connect your device when it's in fastboot mode and done
How to install TWRP
Sadly this Guide is for Windows, but other platforms like Mac or Linux can be found online.
YOU CAN USE THIS METHOD TO INSTALL A NEWER VERSION OF TWRP TOO
You need to have downloaded Platform Tools which the link is attached below.
Transfer the TWRP.img file into the platform-tools folder
Now transfer TWRP.zip into your device's internal storage. (connect -> allow file transfer -> drag and drop files)
If you want root download and transfer magisk.apk and the link is supplied below. Also, RENAME from .apk to .zip
Now we must boot into fastboot mode. (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Now connect your device to a Windows device
Press shift + right-click. Choose command prompt or PowerShell
Enter "fastboot devices" and your device should be displayed if it's connected
Type "fastboot boot twrp" file name (do twrp + press tab) and press enter
Then you should be booted into TWRP
Enter the password and swipe to allow modifications
Press install and find your TWRP.zip file
Swipe to confirm Flash
If you want root do this
Press the back arrow and find your magisk.zip
Swipe to confirm Flash
Reboot to the system and done
Otherwise, just reboot to system. Up to u
Installing a Custom ROM
Install Custom ROM on OP6T from OOS
Make sure u have BACKED UP your device and have the latest OOS installed in both slots. If u do, go to Method 3.
If u have finalize.zip, go to Method 2.
Method 1
If u don't have OOS installed in both slots or finalize.zip, use this method.
Transfer OOS.zip file, TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to Bootloader
Boot TWRP
Flash OOS + TWRP
reboot recovery
Flash OOS + TWRP
Reboot recovery
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Reboot to system
Otherwise, just Format data -> reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 2
If u have finalize.zip, do this method. Using finalize is way quicker as there's less flashing and rebooting.
Transfer OOS.zip file, finalize.zip, TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to Bootloader
Boot to TWRP
Flash OOS + finalize
Boot to Bootloader
Boot to TWRP
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Reboot to system
Otherwise, just Format data -> reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 3
Once you have installed OOS in both slots do this part.
Transfer TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to Bootloader
Boot to TWRP
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Reboot to system
Otherwise, just Format data -> reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Installing Custom Rom not from OOS
You can use finalize method or just flash OOS + TWRP way. The finalize way is there for some who like less flashing and rebooting.
Using the methods in Install Custom ROM on OP6T from OOS
Using the old way, use Method 1
Using finalize.zip, use Method 2
Remember to factory reset (wipe, but no need to wipe internal storage)
Backing Up OOS and Custom ROM
Make sure u have installed the latest TWRP version from mauronofrio
You should use TitaniumBackup or Migrate to back up your apps and contacts.
Also, have a copy of your Internal Storage folders if u have important files.
TWRP Backup backs up your OS like Apps, settings and set up, but not internal storage.
NEVER BACKUP SYSTEM AND VENDOR! ONLY SYSTEM.IMG or VENDOR.IMG IF YOU HAVE TO!
Restoring it makes going back way easier like you have never left
Or you can go manually and try and restore everything, but why do that when you got TWRP?
I do both ways of backing up
Backing up OOS
Boot TWRP recovery
Choose Backup
Choose boot, data. YOU DO NOT NEED TO BACKUP System.img and Vendor.img!
Swipe to backup
Once done, either boot to system or mount
Transfer the whole TWRP folder onto a storage device
Done
Backing up a Custom ROM
Boot TWRP recovery
Choose Backup
Choose boot, data, system.img, vendor.img
Swipe to backup
Once done, either boot to system or mount
Transfer the whole TWRP folder onto a storage device
Done
Restoring OOS and Custom ROM
Restoring OOS TWRP Backup
To restore OOS use either fastboot ROM or MSM. Fastboot is the fastest and easiest way if u have a TWRP backup which there's a method to how to make one in this guide. BUT if you are restoring to go back to stock OOS then use MSM
I use Fastboot ROM restore for that too as we are restoring our data anyways and also for switching/installing a custom ROM. Much easier in my experience.
DOWNLOAD FULL ZIP OF OOS version of your TWRP backup otherwise you could risk doing the whole restore method again OR setup from SCRATCH! IF you aren't restoring a TWRP backup, I recommend either TRANSFER or DOWNLOAD via WiFi or oxygen updater, a UPDATED version of OOS AFTER doing either fastboot ROM or MSM restore methods. As they restore a old version of OOS!
Restoring using Fastboot ROM
Download fastboot ROM of your choice using the link in the Download Link section.
Extract/ un-zip
Boot your device into fastboot mode (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Click flash-all.bat
Restoring using MSM Download Tool
Download latest MSM version of your choice using the link in the Download Link section.
Extract/ un-zip
Click on MSM tool .exe file
Turn off device
HOLD BOTH volume buttons
Connect your phone
Wait for your device to be connected and it should show as green
Click verify to check and press start
Wait till phone reboots
The setup device and u can carrying on restoring your device if u don't want a unlock bootloader or return to what your device was like before.
Go into developer options
Allow OEM unlocking
Reboot to bootloader
Enter "fastboot devices" to check your device is connected
Enter "fastboot oem unlock"
Swipe for yes
Then it will reboot again
continue to the next method
For both fastboot and MSM
Once booted into system, set it up and update to OOS version of your TWRP backup.
Download the full zip using the link in the Download Link section.
Transfer the OOS .zip to internal storage.
Go into settings -> system update -> Update via local upgrade -> find zip file and press install
Do this twice to make sure you have installed that version of OOS in both slots
Boot to bootloader
Boot TWRP
Install TWRP
Reboot recovery
Transfer whole TWRP Folder into internal storage
Restore only boot and data
Swipe to restore
If you have backed up your internal storage folders do this
Reboot to recovery
Transfer all your internal storage folders
Reboot to system and done
Otherwise, just reboot to system. U can update OOS as well if it's outdated. The method is below to update OOS with ROOT. Up to u
RESTORING TWRP BACKUP HAS ISSUES ON THESE ROMs
CrDroid (Method 1 + 2 don't work). Method 3 works (install Gapps if the ROM doesn't have it!)
Restoring a Custom ROM TWRP backup 1
I tried using this method, but it didn't work for me.
You can use this method to switch ROMs too
Boot TWRP Recovery
Flash OOS + Finalize
Boot to bootloader, boot TWRP
Flash TWRP
Reboot Recovery
Transfer twrp backup
Restore System.img, Vendor.img and boot
Boot to system and setup system
Reboot to recovery
Restore data
Reboot system. Done
I had an issue with this method where rebooting system it was from fresh and my data didn't restore. If this happened to you, then do method 2 (Restoring a Custom ROM TWRP Backup 2)
Restoring a Custom ROM TWRP Backup 2
The first method didn't work for me. But this method did
Restore fresh like you're going back to OOS.
Choose one method. Fastboot or MSM method.
I prefer the fastboot method.
Download fastboot ROM using the link in the Download Link section.
Extract/ un-zip
Boot your device into fastboot mode (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Click flash-all.bat
Once booted into system, set it up briefly and DO NOT RESTORE ANYTHING.
Boot to bootloader
Boot TWRP
Install TWRP
Reboot recovery
Transfer whole TWRP Folder into internal storage
Restore everything (System.img, vendor.img, boot.img and data)
Swipe to restore. If data couldn't restore then boot system, setup system, boot TWRP and restore data.
Reboot system. The first reboot might go dodgy and it did for me.
Reboot system and transfer all your internal storage stuff
done
If this did not work still. Then do the 3rd method...
Restoring a Custom ROM TWRP backup 3
If the previous 2 methods has failed for you. Then try this.
Restore fresh like you're going back to OOS.
Choose one method. Fastboot or MSM method.
I prefer the fastboot method.
Download fastboot ROM using the link in the Download Link section.
Extract/ un-zip
Boot your device into fastboot mode (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Click flash-all.bat
Once booted into system, set it up and update to OOS version of your TWRP backup.
Download the full zip using the link in the Download Link section.
Transfer the OOS .zip to internal storage.
Go into settings -> system update -> Update via local upgrade -> find zip file and press install
Do this twice to make sure you have installed that version of OOS in both slots
Transfer TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to bootloader
Boot TWRP
Install TWRP
Reboot to Recovery
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Otherwise, just Format data -> reboot to recovery. Up to u
Reboot Recovery
Transfer twrp backup
Restore data
Reboot system. Done
If it still fails, repeat steps 1 to 15. But restore everything and you should be back on your custom ROM like you never left.
Updating OOS and Custom ROM
Update OOS with Root (Magisk)
Always do a TWRP backup before updating your OS in case
Download the full zip file of the latest OOS, transfer the zip file to internal storage NOT IN ANY FOLDER
Download and transfer twrp.zip file to internal storage
Go into settings, system update, update via local upgrade and choose the file
Wait till the installation has finished. If failed TRY AGAIN!
DO NOT REBOOT!
Go into Magisk Manager, modules
Find the twrp zip file and install TWRP
DO NOT REBOOT!
Go into Magisk Home
Press install
Press install via inactive slot
Reboot system and done
You will reboot into the next slot
You don’t have to repeat the installation to install the latest OOS in the other slot. But you should and I use this method many times and has never let me down.
Updating OOS without root
Go to System Update -> find the update install and reboot.
Or download the zip -> transfer to internal storage -> update via local upgrade -> reboot and done
Update a Custom ROM
Method 1
Always do a TWRP backup before updating your OS in case
Use this method just to update the ROM.
Boot recovery
Flash new version + twrp
Reboot recovery
Flash new version + twrp
If the ROM doesn't have GApps included,
The restore script should show up during the installation of the new ROM.zip
BUT if the restore script DIDN'T pop up do this
Reboot to recovery
Flash Gapps if not included
Reboot to system
Otherwise, reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 2
This method uses finalize.zip
Boot recovery
Flash new version + finalize + twrp
If the ROM doesn't have GApps included,
The restore script should show up during the installation of the new ROM.zip
BUT if the restore script DIDN'T pop up do this
Reboot to recovery
Flash Gapps if not included
Reboot to system
Otherwise, reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Updating vendor
Use Method 1 and 2 for ROMs with Gapps. Use Method 3 for ROMs with no Gapps included.
Method 1
If u haven’t updated your Custom ROM and your Vendor… You can use this method to update both or just the vendor.
Boot recovery
Flash OOS + twrp
Reboot recovery
Flash OOS + twrp
Reboot recovery
Flash Custom ROM + twrp
Reboot recovery
Flash Custom ROM + twrp
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system
Method 2
This method uses finalize.zip
Boot recovery
Flash OOS + finalize + twrp
Reboot recovery
Flash Custom ROM + finalize + twrp
Otherwise, reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system
Method 3
This method is for ROMs with no Gapps included
You can use this method as well for updating to a vendor that has a NEWER ANDROID version like from OOS 10 to OOS 11 vendor.
Boot recovery
Flash OOS + Custom ROM + twrp
Reboot recovery
Flash OOS + Custom ROM + twrp
If u flashed GApps, the restore script should show up during the installation of the ROM.zip
If the GApps script didn't show up do this
Otherwise, skip step 3
Flash Magisk if u want root, otherwise skip step 2
Reboot to recovery
Flash Magisk
Flash Gapps
Reboot to system and done
Download Links:
SDK Platform Tools (Fastboot Tools) Here
OOS versions for OP6 (under Signed Flashable zips) Here
OOS versions for OP6T (under Signed Flashable zips) Here
TWRP for OP6 Here
TWRP for OP6T Here
Magisk Here
NikGapps Here
Stock Fastboot ROM for OP6 Here
Stock Fastboot ROM for OP6T Here
MSMDownloadTool for OP6 Here
MSMDownloadTool for OP6T Here
TitanumBackup App Here
Migrate App Here
Credits:
@mauronofrio For his amazing work on the TWRP recovery and Stock Fastboot ROMs for OP6/6T
@topjohnwu For his work on Magisk
@Nikgapps For their work on creating Gapps
@Some_Random_Username For his Collection of MSMDownloadTool for OP6/6T
@OPTeam For the collection of OOS zips for OP6/6T
@dreamwhite For the method (Method 3) of updating the vendor which works wonders for ROMs with no GApps included
First
Hey Guys,
Need a some expert advice please.
Long story short. I need to replace my OP 6T McLaren's battery as I have serious degradation in battery capacity (73% Serious Loss), meaning the battery is no longer charging to 3700mAh, max charging atm is around 2600mAh, which it drains very quickly. FYI Anything above 80% is the limit for average performance, >90% is best. You can use the OP Diagnostic App 1.0.0.9 to determine your own status. Does not work on all OP devices above 6 btw. Maybe other versions work. Anyway, will be getting OP to change the battery (no real local guys I can trust tbh, all Sammy & Apple guys...) and they want me to Factory Reset the device (complete wipe including internal storage (backed up already to PC)) before sending the device to the OP Repair Center for the obvious reasons of Privacy & Security.
On my device, I have a suite of apps that are no longer available to install with APK specially Signed, but won't be able to re-install (long story & can discuss in a PM more if there is an interest to help on this). These APK will not work any other way, I've tried! This being said, I know that TWRP Nandroids work well & have been doing these backups for yrs and have restored backups with these apps installed and it works! But I have not had to restore any as of late and TWRP Backup has somewhat changed in regards to the partition selections available. See TWRP Options pic below.
When OP returns the device to me, it will mostly likely be on the latest release of 10.3.11 (Hopefully).
Here is the current setup and runs perfectly!
OOS 10.3.11
TWRP: twrp-3.5.2_9-0-fajita
Magisk 23
The last Nandroid done today (No PW for good measure, but secured locally offline), I selected all partitions. Is this the best way to insure I get my full device backup restored?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm guessing that I will have to, Unlock the Bootloader, reinstall TWRP same version the Nandroid was created with in order to restore that backup.
Looking forward to hearing from you guys to make the best decision before proceed with the factory reset.
Thanking you all in advance for your time & assistance!
Cheers!
plepew said:
Hey Guys,
Need a some expert advice please.
Long story short. I need to replace my OP 6T McLaren's battery as I have serious degradation in battery capacity (73% Serious Loss), meaning the battery is no longer charging to 3700mAh, max charging atm is around 2600mAh, which it drains very quickly. FYI Anything above 80% is the limit for average performance, >90% is best. You can use the OP Diagnostic App 1.0.0.9 to determine your own status. Does not work on all OP devices above 6 btw. Maybe other versions work. Anyway, will be getting OP to change the battery (no real local guys I can trust tbh, all Sammy & Apple guys...) and they want me to Factory Reset the device (complete wipe including internal storage (backed up already to PC)) before sending the device to the OP Repair Center for the obvious reasons of Privacy & Security.
On my device, I have a suite of apps that are no longer available to install with APK specially Signed, but won't be able to re-install (long story & can discuss in a PM more if there is an interest to help on this). These APK will not work any other way, I've tried! This being said, I know that TWRP Nandroids work well & have been doing these backups for yrs and have restored backups with these apps installed and it works! But I have not had to restore any as of late and TWRP Backup has somewhat changed in regards to the partition selections available. See TWRP Options pic below.
When OP returns the device to me, it will mostly likely be on the latest release of 10.3.11 (Hopefully).
Here is the current setup and runs perfectly!
OOS 10.3.11
TWRP: twrp-3.5.2_9-0-fajita
Magisk 23
The last Nandroid done today (No PW for good measure, but secured locally offline), I selected all partitions. Is this the best way to insure I get my full device backup restored?
View attachment 5319753
I'm guessing that I will have to, Unlock the Bootloader, reinstall TWRP same version the Nandroid was created with in order to restore that backup.
Looking forward to hearing from you guys to make the best decision before proceed with the factory reset.
Thanking you all in advance for your time & assistance!
Cheers!
Click to expand...
Click to collapse
Idk if u have read Mauronofrio's XDA thread on TWRP backups. BUT NEVER BACKUP OR RESTORE SYSTEM OR VENDOR! From my guide, you don't need to backup vendor.img or system.img or anything else that's not Boot or Data FOR OOS. Make sure you have everything like a copy of everything folder/file in your internal storage before u wipe it.
BUT because you're going to wipe your device. U should have a copy of everything in case but don't backup system or vendor as they're useless and will crash your system if u restore those!
After you've got your device from repair, follow my method to restore OOS TWRP backup on your device and YOU'LL only NEED TO RESTORE BOOT + DATA. Once you have booted back to your system, everything should be there like you never left, but transfer your internal storage stuff as some apps store files in your internal storage. Once that is done, that should be it and it would be like you've never left
If the TWRP backup restore doesn't work let me know, but from my experience with going back to OOS via my TWRP backup I only backed up and restored boot + data for OOS. Custom ROMs are different but isn't the case for you
Extreme_Ninja2099 said:
Idk if u have read Mauronofrio's XDA thread on TWRP backups. BUT NEVER BACKUP OR RESTORE SYSTEM OR VENDOR! From my guide, you don't need to backup vendor.img or system.img or anything else that's not Boot or Data FOR OOS. Make sure you have everything like a copy of everything folder/file in your internal storage before u wipe it.
BUT because you're going to wipe your device. U should have a copy of everything in case but don't backup system or vendor as they're useless and will crash your system if u restore those!
After you've got your device from repair, follow my method to restore OOS TWRP backup on your device and YOU'LL only NEED TO RESTORE BOOT + DATA. Once you have booted back to your system, everything should be there like you never left, but transfer your internal storage stuff as some apps store files in your internal storage. Once that is done, that should be it and it would be like you've never left
If the TWRP backup restore doesn't work let me know, but from my experience with going back to OOS via my TWRP backup I only backed up and restored boot + data for OOS. Custom ROMs are different but isn't the case for you
Click to expand...
Click to collapse
Wow, thanks for the quick reply!
I have not read Mauronofrio thread and will do!
I completely missed the system & vendor piece in your instructions....my bad!
So just to confirm, my backup that I have done with all checked off is good, but only restore Boot & Data with an exact duplicate of the current Internal Storage...right?
Going forward, when creating the Backup, just select Boot & Data and I'm good to go? Or select all Except: System Image(only) & Vendor options (both)?
Also, just so I can understand a bit better, "System" is the actual OOS? Meaning, if I restore Boot & Data on any OOS, all my apps and data will be as I never left, or we should always restore on the OOS that was current at the moment of the Backup (which I have always done in the past).
PS. I may just do the backup again, just to make sure SYSTEM & VENDOR are not there for good measure!
plepew said:
Wow, thanks for the quick reply!
I have not read Mauronofrio thread and will do!
I completely missed the system & vendor piece in your instructions....my bad!
So just to confirm, my backup that I have done with all checked off is good, but only restore Boot & Data with an exact duplicate of the current Internal Storage...right?
Going forward, when creating the Backup, just select Boot & Data and I'm good to go? Or select all Except: System Image(only) & Vendor options (both)?
Also, just so I can understand a bit better, "System" is the actual OOS? Meaning, if I restore Boot & Data on any OOS, all my apps and data will be as I never left, or we should always restore on the OOS that was current at the moment of the Backup (which I have always done in the past).
PS. I may just do the backup again, just to make sure SYSTEM & VENDOR are not there for good measure!
Click to expand...
Click to collapse
First off, I already posted everything you need in my last comment and that's what I usually do. Everything should be there and not like you need to pay or reply to get the extra stuff that you may need. No point in replying asking for more as I'll just be repeating myself over and over.
Just choose boot & data for TWRP backups for OOS specifically going forward and after you got your device from repair. System, vendor doesn't work in my experience and will crash your system. Only backup the .img variant which was stated by the dev (Mauronofrio) for TWRP for OP6/6T devices. Only backup system.img and vendor.img if u need to backup system+vendor, but YOU don't have to for OOS and I said this previously.
JUST DO A BACKUP OF EVERYTHING OTHER THAN SYSTEM AND VENDOR. YOU SHOULD ONLY BACKUP SYSTEM.IMG AND VENDOR.IMG NEVER SYSTEM OR VENDOR.
They never work and will increase the size of your backup and will take even longer to transfer to your storage device from your phone.
YES, to your new question. You should update/ be on the same OOS version as your TWRP backup before u restore data + boot. Restore OOS via fastboot or msm and update to get to the same version of OOS as your TWRP backup. YOU should only do this if your phone is in the wrong version of OOS as your backup after you've got it back from REPAIR.
ALWAYS BE ON THE SAME VERSION OF OOS AS YOUR TWRP BACKUP BEFORE YOU RESTORE YOUR TWRP BACKUP OF OOS!
Maybe take a copy of your wifi passwords, take a google backup in settings, take a copy of sms/call logs and contacts. Other stuff that you may not have stored just in case the TWRP backup fails, but it shouldn't. Good luck
This should be it and there isn't anything else that you'll need
Extreme_Ninja2099 said:
First off, I already posted everything you need in my last comment and that's what I usually do. Everything should be there and not like you need to pay or reply to get the extra stuff that you may need. No point in replying asking for more as I'll just be repeating myself over and over.
Just choose boot & data for TWRP backups for OOS specifically going forward and after you got your device from repair. System, vendor doesn't work in my experience and will crash your system. Only backup the .img variant which was stated by the dev (Mauronofrio) for TWRP for OP6/6T devices. Only backup system.img and vendor.img if u need to backup system+vendor, but YOU don't have to for OOS and I said this previously.
JUST DO A BACKUP OF EVERYTHING OTHER THAN SYSTEM AND VENDOR. YOU SHOULD ONLY BACKUP SYSTEM.IMG AND VENDOR.IMG NEVER SYSTEM OR VENDOR.
They never work and will increase the size of your backup and will take even longer to transfer to your storage device from your phone.
YES, to your new question. You should update/ be on the same OOS version as your TWRP backup before u restore data + boot. Restore OOS via fastboot or msm and update to get to the same version of OOS as your TWRP backup. YOU should only do this if your phone is in the wrong version of OOS as your backup after you've got it back from REPAIR.
ALWAYS BE ON THE SAME VERSION OF OOS AS YOUR TWRP BACKUP BEFORE YOU RESTORE YOUR TWRP BACKUP OF OOS!
Maybe take a copy of your wifi passwords, take a google backup in settings, take a copy of sms/call logs and contacts. Other stuff that you may not have stored just in case the TWRP backup fails, but it shouldn't. Good luck
This should be it and there isn't anything else that you'll need
Click to expand...
Click to collapse
Thank you!!
Hey guys, for some reason I ended up on "Unmodified System Partitions", must have tapped the screen a few times in error while handling the phone I guess.
What should I do?
Unable to go back to TWRP main menu without selecting an option.
I am rooted, on stock OOS and not doing customs ROM at this time...
What should I do?
Select "Keep Read Only"? or Swipe to "Allow Modifications"?
thanking you guys in advance for you help & guidance!
plepew said:
Hey guys, for some reason I ended up on "Unmodified System Partitions", must have tapped the screen a few times in error while handling the phone I guess.
What should I do?
Unable to go back to TWRP main menu without selecting an option.
I am rooted, on stock OOS and not doing customs ROM at this time...
What should I do?
Select "Keep Read Only"? or Swipe to "Allow Modifications"?
View attachment 5320971
thanking you guys in advance for you help & guidance!
Click to expand...
Click to collapse
Swipe to allow modifications. But it seems that your internal storage corrupted. Not sure what you did and how you got into this situation.
After you swiped to allow modifications... If the internal storage files are a messed up, try to switch slots and reboot recovery
Extreme_Ninja2099 said:
Swipe to allow modifications. But it seems that your internal storage corrupted. Not sure what you did and how you got into this situation.
After you swiped to allow modifications... If the internal storage files are a messed up, try to switch slots and reboot recovery
Click to expand...
Click to collapse
I swiped and yeah, the IS was messed up in File Managfer(TWRP).
Selected Reboot then Selected the Slot I remembered I was on : "A"
Rebooted & Boom all good!
Thank you for the help once again! You rock!!
plepew said:
I swiped and yeah, the IS was messed up in File Managfer(TWRP).
Selected Reboot then Selected the Slot I remembered I was on : "A"
Rebooted & Boom all good!
Thank you for the help once again! You rock!!
Click to expand...
Click to collapse
Cool and at least that was a easy fix
Sorry, I'm a total noob, hopefully this is an easy question to answer. Is there any way that I can tell what version of OOS my TWRP Backup contains? I can't remember what version my phone was running when I did the TWRP backup and don't want to mess it up after I restore the phone from MSM. Thanks in advance for your help!
Sorry, I'm a total noob, hopefully this is an easy question to answer. Is there any way that I can tell what version of OOS my TWRP Backup contains? I can't remember what version my phone was running when I did the TWRP backup and don't want to mess it up after I restore the phone from MSM. Thanks in advance for your help!
jas84701 said:
Sorry, I'm a total noob, hopefully this is an easy question to answer. Is there any way that I can tell what version of OOS my TWRP Backup contains? I can't remember what version my phone was running when I did the TWRP backup and don't want to mess it up after I restore the phone from MSM. Thanks in advance for your help!
Click to expand...
Click to collapse
Well u posted this twice which isn't necessary and people will try and reply. But I'm not sure if there is a way to know and as long as u copied the whole TWRP folder for that backup, u should be fine restoring it with a newer version of TWRP. If it really matters to you, then maybe try and find the latest TWRP on the date you did the backup? I think just using a newer TWRP version should be fine
Should I use the same Gapps package I flashed during clean installing when updating custom rom?
Waynenolan92 said:
Should I use the same Gapps package I flashed during clean installing when updating custom rom?
Click to expand...
Click to collapse
U don't have to use the same gapps package. Using a updated one would be better. But, u only have to for ROMs that don't include gapps (vanilla builds) AND the Restore script doesn't show up during installation. Opengapps doesn't have that script but nikgapps does. Using dirty flash/updating a ROM should show the restore script and if it doesn't then just reboot to recovery and flash the updated or same gapps package. This can also be the same for updating the base/vendor (use method 3 in that section of the guide). I hope this helps
Extreme_Ninja2099 said:
U don't have to use the same gapps package. Using a updated one would be better. But, u only have to for ROMs that don't include gapps (vanilla builds) AND the Restore script doesn't show up during installation. Opengapps doesn't have that script but nikgapps does. Using dirty flash/updating a ROM should show the restore script and if it doesn't then just reboot to recovery and flash the updated or same gapps package. This can also be the same for updating the base/vendor (use method 3 in that section of the guide). I hope this help
Click to expand...
Click to collapse
Thanks for your replay)))it's my first using vanilla rom(without Gapps), so I flashed nikigapps Omni package, and my question is: should I always use the same package, or I can go with core package for example?
Waynenolan92 said:
Thanks for your replay)))it's my first using vanilla rom(without Gapps), so I flashed nikigapps Omni package, and my question is: should I always use the same package, or I can go with core package for example?
Click to expand...
Click to collapse
U can... But it doesn't really matter as a updated package works fine and u only need to use it if the nikgapps restore script doesn't show up when updating the ROM or vendor/base (OOS underneath)
I want to CHANGE custom ROMs (havoc to Lineage OS a11 to a12) I have taken TWRP back up of boot+data+system.img+ vendor.img. once I flash the new a12 Lineage plus Nikapps core plus magisk. What steps to restore data? any response is appreciated in advance. Thank you.