Related
[How To Root] Huawei P smart - Android 8 - EMUI 8.0.0
The Rooting was tested by me on this device:
Model: FIG-LX1
Board: FIG-L31
Build No.: 8.0.0.128(C432)
EMUI 8 - Android 8
"free device"
Whether the following instructions are based on provider-branding is applicable, I could not test
and therefore advise against it.
Warning: Rooting will void the device warranty. Be careful with the newly acquired root rights.
I recommend this only to users who are fit in handling a custom recovery.
This TWRP is not yet perfect and should be used with caution.
Make sure to backup all data on the SD card. (PC, stick, or HD)
Create a backup with the Huawei Backup App.
Make sure the bootloader is open.
OEM and FRP unlocked,
in the device settings, OEM unlock and USB debugging enabled.
The stock kernel is mandatory.
This is flashed in fast boot mode/ bootloader:
If the device is unroot, it does not need to be done.
fastboot flash kernel kernel.img
(KERNEL.img.header must also be in the adb folder.)
This steps must be followed exactly:
Factoryreset in recovery.
Flashing TWRP in the bootloader: fastboot flash recovery_ramdisk FIGO.img
Boot to TWRP and change the file system of the external SD card:
Wipe> Advanced Wipe> Micro SD card> Repair or Change File System> Change File System> FAT:
Execute with "Swipe to Change".
This change deletes all data on the SD card.
Switch to the Mount menu and unmount all partitions. (remove all hooks)
On the internal and external memory.
Then create a backup:
Backup> Select Storage> Micro SD card> select all partitions,
except cache. Then reboot the device into the system and copy the Magisk Zip to the SD card.
Then install in TWRP: Install> Select Storage> Micro SD card> Magisk-v16(1600).zip> Swipe to confirm Flash.
Is there an error message, installing this Zip via MagiskManager App.
Reboot and if not available, install the MagiskManager App and check the root.
The routing is now complete.
Install Magisk modules only with the app; never with TWRP.
Important:
Never wipe the cache or perform a factoryreset.
[*]Please do not experiment with Xposed. This leads to the bootloop and the Firmware must be completely reinstalled.
[*]Please with each backup, make sure to unmount all partitions again. (internal and external)
Update via Firmwarefinder:
Start Firmwarefinder App and select the appropriate update.
Then on GET AN UPDATE THROUGH DNA.
Then on WITHOUT IMEI.
Availability is displayed.
Now click on REGISTER UPDATE and the registration is displayed.
Then click IN-APP PROXY.
Now activate DNS in the router, enter 81.177.139.39 as addresses and save.
Now go to the WLAN settings on the phone, touch and hold the active connection.
Then change to Network in the menu.
Under Proxy-manual, enter localhost and port 8080 as host names for extended options.
Now only set the IP setting to DHCP. Now start the eRecovery.
Vol.+ and Power with PC connection
There on "Download latest version and recovery".
Then click on "Download and recovery" and register there under Select WIFI.
Now the update is displayed and can be started.
When rebooting, the device lands in the bootloop,
execute a factoryreset in the recovery.
After the update reboot and all changed WLAN settings, also in the router
and reboot it again. If you don't, it'll be over by the time
next OTA update is displayed again and again, since the authorization remains in memory.
Themes-Fix, How to Unbrick, FRP-Unlocking and Bootloader Unlocking I described here. Or follow this thread.
https://www.android-hilfe.de/forum/...t-how-to-root-twrp-root-anleitung.866625.html
It is easy to translate with: https://www.deepl.com/translator
All downloads are here: http://www.mediafire.com/folder/7qdu5je08caya/FIGO
Attention: Changing the oem.info can
cause the phone to lock. OEM/FRP=LOCK
Thread Update 2017-03-28:
A new TWRP is now available. It is version 3.2.1-0.
Original Chinese developer version.
Instructions:
First perform the Huawei data backup.
Flash TWRP per Adb as usual.
Then switch from Chinese to English.
Then assign write and read rights by removing the hook in wipe menu.
Now for security, create a backup without data.
Then Format Data.
Create a new full backup including data. This is possible now that the
formatting is the size of Data = 0.
Now reboot the device and set it up completely new.
Now there is a new and configured data partition.
Then turn OEM and USB back on and boot to TWRP.
Then create a new full backup.
TWRP is now fully functional. Only the MTP mode does not work.
http://www.mediafire.com/file/icpfjhw9eysjlao/FIGO321.img
Good luck!
My special thanks for this original Chinese TWRP for free use,
goes to: "weibo.com/xinkid520", FIRE Team(Developer) and "Team Win Recovery Project".
Despite careful elaboration, I cannot guarantee that the execution of this manual will not cause any damage to the device or operating system and therefore I do not assume any liability for any damage or malfunction of the hardware and software! If you are still unsure, follow these steps: Follow the instructions only if you or your device is subject to any conditions (model number, Android version, etc.). Read the instructions carefully and completely, look up unknown terms. Check downloaded files for viruses. Make a backup of important settings and data. Do not follow the instructions if you do not know what you are doing.
These warnings must be logical. Please process my comments correctly.
Many thanks to: funkyhuawei.club, Jrummy, Chainfire, Stephen (Stericson) +
Jmz Software, TWRP, osmOsis,Topjohnwu and Huawei Technologies Co., Ltd 华为技术有限公司
it's alive!!! FIGO-LX1C10B120
Men I love you!!!
Thank you monster!!!! [emoji8]
thanks !! are we getting a Huawei P smart forum here soon ??
Themes
I cannot apply themes after Root ?
Hello,
could you also provide the vendor.img?
Would be really nice.
Thx in advance
@enjac
Forum habe ich beantragt.
I have applied for a new forum.
@JahSound77
Flash the cust.img. Then it works.
@Destroyer706
Vendor kannst Du nicht mit adb flashen.
You cannot flash Vendor with adb.
Hey, guys, I got a brick. Can someone save/extract the "kernel. img"
from the 122. Or can someone from the sources compose a kernel. img? I don't have a linux pc.
:crying:
I know I can't flash with adb, but fastboot. I made some changes and want to role back easily.
I try to provide you the kernel img
Themes
I followed your instructions.... fastboot flash cust cust. img
But no luck, after reboot... still can't apply themes from the store .
Destroyer706 said:
I know I can't flash with adb, but fastboot. I made some changes and want to role back easily.
I try to provide you the kernel img
Click to expand...
Click to collapse
I uploaded it now. :good:
https://mega.nz/#F!EplhBBzS!UUgXBRC9DRaExP9HY57FKQ
JahSound77 said:
I followed your instructions.... fastboot flash cust cust. img
But no luck, after reboot... still can't apply themes from the store .
Click to expand...
Click to collapse
You must be logged in to the google account and huawei id. Outside Asia. If it doesn't work, wait one or two days. It'll probably work then. It was like that with me.
Thx. I am already compiling the kernel from source
Destroyer706 said:
Thx. I am already compiling the kernel from source
Click to expand...
Click to collapse
This has never happened to me before. I have always been able to rely on TWRP backups. But without.....
ChinHon said:
This has never happened to me before. I have always been able to rely on TWRP backups. But without.....
Click to expand...
Click to collapse
The thing, I didn't think about, is, I don't know how to repack the image.gz after compiling to flashable boot.img as I don't have a existing boot.img.
Maybe you can advice me.
Can you upload oeminfo file for FIG-LX1 8.0.0.122 (C432) please?
I would like to rebrand my Chinese version (FIG-AL10).
Destroyer706 said:
The thing, I didn't think about, is, I don't know how to repack the image.gz after compiling to flashable boot.img as I don't have a existing boot.img.
Maybe you can advice me.
Click to expand...
Click to collapse
There is no boot. img in the 121 firmware anymore. Only the kernel. img. I flashed that. So I have the bootloop and need the img from 122, so I thought you might be able to extract it from your device.
steveleg said:
Can you upload oeminfo file for FIG-LX1 8.0.0.122 (C432) please?
I would like to rebrand my Chinese version (FIG-AL10).
Click to expand...
Click to collapse
Not included in the UPDATE. APP anymore.
See filelist:
Here is the extracted kernel.img. Hope it helps.
https://mega.nz/#!auo2TAaC!7009dtrK8-uBR39s9fNFf2xCQkEzR1EXURSLBabkuk8
steveleg said:
Can you upload oeminfo file for FIG-LX1 8.0.0.122 (C432) please?
I would like to rebrand my Chinese version (FIG-AL10).
Click to expand...
Click to collapse
I found another update in the net. Here the oeminfo as a self-extracting archive.
https://mega.nz/#!5gcygYLL!Wdlvg5jUo2hv6L7DBtAVT1-0z_WRmSBLuBin7iUGjig
Destroyer706 said:
Here is the extracted kernel.img. Hope it helps.
https://mega.nz/#!auo2TAaC!7009dtrK8-uBR39s9fNFf2xCQkEzR1EXURSLBabkuk8
Click to expand...
Click to collapse
Hey bro, FIGO's alive again. Thanks a million. You're the best.
:good::good:
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!
A/A & Welcome,
READ THE FULL GUIDE OR YOU CAN LAND IN TROUBLE
Ain't gonna work on pie official
AND DO PRESS THE THANKS BUTTON
Disclaimer
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or anything that happens to your device
INTRO
This is a full guide for unlock/relock, install TWRP, Root your device and backup/restore stock OS. Each and every step is explained thoroughly with pictures and videos.
I have ASUS Zenfone Max Pro M1 (6GB variant) (X00TD) (ZB601KL), so I can’t test for other variants. Please report back issues, corrections, omissions, etc., though the guide should work for all devices.
THINGS TO KNOW (IMPORTANT)
~Every text written in double quotes “” means the same written without the quotes.
e.g.:- “abcd” means abcd
“zxcv” means zxcv
They (“”) help to separate usual text from the other text (like a command, file name, etc.)
~If you have not enabled file name extensions then you will see files without their extension and vice versa
e.g.:- “filename”, “mypicture” in 1st case
“filename.extension”, “mypicture.png” in 2nd case, respectively.
~Boot Partition or Bootloader:-This is the partition that enables the phone to boot. Without this partition, the device will not be able to boot.
~Recovery Partition:-Recovery partition lets you boots the device into a recovery mode to perform recovery tasks.
~TWRP: - stands for TeamWin Recovery Project. It is a custom touch recovery that is GUI based.
~Flashing: - simplest: - installing
~Fastboot Partition: - lets us reflash partitions. (On device)
~Fastboot: - is an executable used to reflash partitions. It comes with the Android SDK. (On PC)
~Rooting: - an Android phone lets owner edit system files. Thus enabling various tweaks and use of apps that require root access.
~Device driver: - determines how PC will communicate with a device.
~Unlocking/Relocking:-With a locked Bootloader, booting into custom things is not allowed is not. Unlocking lets us do so.
~Reboot: - Switching ON AND OFF (in simple terms)
Requirements
MIND, PC, USB Cable, Internet, Fully charged PC (Windows OS), and obviously Asus Zenfone Max Pro M1
The Real Steps From Here
FOLLOWING THIS GUIDE YOU WILL PROBABLY LOSE ALL THE DATA ON YOUR PHONE SO MAKE A BACKUP FIRST (Don’t worry it’s in guide too)
STEP 1. Downloading all the necessary files
a. Here are 2 zip file with everything you will probably need following the guide :-
basic zip
extension zip
. I have tested the procedures using these files only so maybe other versions might not work. A “guide.doc” with the same text as in here (on XDA) is also present. It will be of great help if you don’t have internet connection in PC.
The basic zip file contains minium files needed.
The extension zip file contains the TWRP recovery(then one used in the guide),guide.docx ,and the videos used here too.
Copy the twrp file to unlock folder of extracted folder.
b. Extract the zip file above.
First download the zip file and Copy to PC
Then Right Click on it
Then click “Extract All”
Uncheck “Show extracted files…”
Click on “Extract”
The folder “zip” will be extracted
Done
This “zip” folder will be called extracted folder in the guide video link to extract zip
To download most up to date version of the files go to links present at last
STEP 2. BACKUP
a. Use an apk backup tool to backup app installers
VIDEO TO BACKUP APP INSTALLERS
b. Some APPS like Whatsapp, etc. have backup to drive function use that
VIDEO TO BACKUP WHATSAPP CHATS
c. Backup SMS AND Call Logs
VIDEO TO BACKUP CALL LOGS AND MESSAGES
d. Copy each and every file from you internal storage to PC.
Video to backup each file to pc
DONE
Step 3. UNLOCKING BOOTLOADER(Data will be wiped)
2 options:-
A. Official Method (NOT TESTED): -
In extracted folder go to “unlock” folder then “Official” folder. Install the “UnlockTool_9.1.0.3_180621_fulldpi_signed_ZB601KL.apk” in Asus and follow the steps from there.
B. Unofficial Method (Tested):-
a. Installing Drivers
Connect phone using USB cable to PC
Right click on This Pc
Go to “Manage” > “Device Manager” Or Just search for “Computer Management”/“Device Manager”
A list will appear.
Find your device (best way to do so is by disconnecting/connecting the device and notice the changes accordingly in the list)
Now right click on it>”Update Driver Software”>“Browse my computer for driver software”
Now either enter path of the driver folder or click on browse and navigate to the driver path from there.
Press Next OR
“Let me pick …”>and select the driver
video to install driver
The drivers have been installed
b. Booting into FASTBOOT
Switch Off the Phone
Hold the Volume UP and Power ON Button Simultaneously
Device buttons labbled image
You will see this on your phone
image of FASTBOOT screen
c. Unlocking Bootloader
Now connect phone using USB cable to PC
Look for the “unlock” folder in the extracted folder.
Open it
Find “unlock.cmd” or “unlock” file
(Or “unlock no erase.cmd” to keep data {not tested})
Open it
Done
d. You will see some messages in yellow/brown/white colour on your phone
You will most probably see “encrypting your device”, “warning Bootloader unlocked” messages, let phone do its work and don’t interrupt it, and keep cable connected. Phone might reboot too. The phone will at last boot into stock OS and you will see the device setup screen.
image of the warning message
e. Now if you wanted TO ONLY UNLOCK BOOTLOADER THEN THE JOB IS DONE, long press power button. If you want to root or flash TWRP then continue (Tested method to root requires TWRP flashing or you can try the untested method to root only)
Step4. Installing/Flashing TWRP
TESTED METHOD
a. Connect phone using USB cable to PC
b. Don’t setup your device just now because possibilities are you might lose the data again
c. Boot into fastboot mode
d. Open the “unlock” folder in the extracted folder.
Now Two Different ways to opt for from here:-
i. THE LAZY METHOD (Tested)
a. Open “flash_recovery.bat” or “flash_recovery” in the “unlock” folder of the extracted folder.
b. You can flash the tested or any other recovery using this script.
c. Follow the steps from the script
video of how to use the script
d.Then go to step of Flashing ZIPS of The Manual Method
e. Done
OR
ii. The Manual Method (Tested)
a. Keeping Shift Key pressed, right click {with mouse} in the blank white space of the “unlock” folder’s explorer window.
b. From the menu select “open command window here”
c. A CMD window will be opened
open cmd video
d. Now type “fastboot devices”
e. See if your device is connected. You will see something like this
f. Now type “fastboot flash recovery twrp-3.2.3-0-X00TD-20181024.img”
If you want to flash any other recovery instead of “twrp-3.2.3-0-X00TD-20181024.img” write the file name of your recovery file. Make sure it’s in “unlock folder”. Though this recovery is the only tested one (by me).
g. Now keeping the phone connected to PC, boot into TWRP/Recovery by pressing the Volume Down and Power ON Button Simultaneously.
h. The usual warnings, messages and recovery boot screen will flash:-
warning image
twrp flash screen image
i. It may take some time to load so wait for at least 2 minutes.
j. Now if touch is not working press power button 2 times (on and off the screen)
video showing how to enable touch in twrp
k. If it shows “Swipe to Unlock” do so. If it shows “Swipe to Allow Modifications” then wait and continue reading …
swipe to allow image
swipe to unlock
l. “Swipe to Allow Modifications” means you allow TWRP to modify system. This will make sure TWRP remains in the phone and not just vanish after a reboot but it also means you will have to flash some other files to be able to boot into stock rom back.
m.
2 ways from here:-
i. Now after swiping, Decrypt Screen will appear just press cancel.
decrypt screen image
OR
ii. If you have data on the device then enter pin/password or try default_password.
If you had kept pattern then either go back and change it or try this:-
1 2 3
4 5 6
7 8 9
these no’s correspond to pattern dots.
Say you kept pattern “third row left to right” then the password is 789 .
If all these fail then you will have to lose your data.
n. As we don’t have any precious data in our phone we will (or you are compromising)
Press “Wipe”
Press “Format Data”
TYPE “yes”
Press “tick” or “enter key”
Done
wipe data video
>Flashing ZIPS
o. Now Copy these 2 files
i. “decrypt.zip” or “decrypt”
ii. “Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip” or “Disable_Dm-Verity_ForceEncrypt_12.16.2018”
From extracted folder to your phones internal storage.
p. Go to Install>select the zip>swipe to flash (flash dm_verity… then decrypt…)
If you don’t see your device storage connected then try reconnecting using USB cable and also check if MTP is enabled.
enable mtp video
>Done
Want to root? Then continue…
or >
Now reboot to system Go to Reboot>System
video to show how to rebbot to system in twrp
Step 5. Rooting
We will be using Magisk to root you can use any other method but this is the only tested method.
a. Copy “Magisk-v18.0.zip” or “Magisk-v18.0” to your phones internal storage from extracted folder.
b. Go to Install>select Magisk…>swipe to flash
Done
c. Now reboot to system Go to Reboot>System
reboot video
e. To use Magisk properly you may need to download latest apk. (Link at last)
Step 6. Relock (NOT TESTED)
a. Connect phone using USB cable to PC
b. Boot into fastboot mode
c. Open “Relock” folder from extracted folder
d. Open “relock.cmd” or “relock” file
Done
Step 7. RESTORING
a. First setup the Device again
b. Copy each and every file back to the phone storage
c. Now to restore messages see the restoring part of this video here
d. WhatsApp messages will be automatically restored after you install the app with same number as before.
Tips
After rooting don’t just go on and flash a custom rom. Take a backup first (of all partitions) using TWRP and keep it safe somewhere so you won’t need to find unbrick tutorials later. Plus you will have your most stable and tailored rom with you.
Also don’t just go on and flash xyz mod. Research and then Flash.
Magisk is our best friend. It lets you do modifications without hurting the system. The Magisk modules are most safe mods as they can be reverted back easily.
And don’t just go on and debloat stock OS. In Magisk there is a module called Debloater use that. You can easily revert back if anything goes wrong.
Other good Magisk modules: - Energized, Systemizer, MidnightCore & Advanced Charging Controller (acc) but do read their XDA guides first.
Sources/Credits:-
Dm_Verity.zip Official XDA:-
link
Original unlocking XDA:-
link
Magisk XDA:-
link
Original Decrypt Data XDA:-
link
TWRP Used XDA:-
link
Credits to the authors of the above guides
Plus sorry for bad editing of videos. I am facing some problems. Will try to post better videos.
I thank all the members who have made the previous guides for their hard work. This guide by no means disrespects their hard work. This guide is just an Addition instead of an Alternative.
Read the full guide
Press the thanks button
Re edited the guide.
Added link of apps used in YouTube videos.
Not working for pie official
Deleted cruddy comments. Good job.
Good initiative but not so good noob guide. Please format it for better organization and better understanding.
malikmiran19 said:
2. BACKUP
>Use an apk backup tool to backup app installers
howto video
Click to expand...
Click to collapse
Appreciate the effort . I have a suggestion. It would be helpful to put the name or link of the app that you used to back up apks.(some apk extractor lite ig). I'll provide the one I found anyway. https://www.apkmirror.com/apk/ankit.../apk-extractor-lite-2-8-android-apk-download/
camaroamarelo said:
Good initiative but not so good noob guide. Please format it for better organization and better understanding.
Click to expand...
Click to collapse
Did so
GliderZ said:
Appreciate the effort . I have a suggestion. It would be helpful to put the name or link of the app that you used to back up apks.(some apk extractor lite ig). I'll provide the one I found anyway. https://www.apkmirror.com/apk/ankit.../apk-extractor-lite-2-8-android-apk-download/
Click to expand...
Click to collapse
Added apk links in YouTube videos
Anyone tried unlocking without erasing data?
TheDarkKnight said:
Anyone tried unlocking without erasing data?
Click to expand...
Click to collapse
nyimak
fuzuy said:
nyimak
Click to expand...
Click to collapse
What?
TheDarkKnight said:
What?
Click to expand...
Click to collapse
it means im interested in your question and im following it
I want to unlock bootloader, flash TWRP and flash a custom ROM (Cerberus OS).
I have rooted and flashed TWRP before in my previous device but I'm not familiar with unlocking and Custom ROM.
Do I have to follow all hese steps for what I want to do or I must skip decrypt/encrypt and Magisk?
dharsouparno1 said:
I want to unlock bootloader, flash TWRP and Custom ROM.
Click to expand...
Click to collapse
U can flash twrp then flash ROM and probably flash magisk for root tooo
malikmiran19 said:
U can flash twrp then flash ROM and probably flash magisk for root tooo
Click to expand...
Click to collapse
Thanks for the help.
I'm running into some problems while installing the driver software on my Windows 10 laptop. It shows Error 10 this device cannot start.
I tried to uninstall and reinstall the drivers, rebooted my pc on every step, tried to install while connected to my phone, but nothing seems to work.
I've installed the Pie Beta for Asus Zenfone Max Pro M1 (not sure if this is causing it)
Is there a solution to this problem?
I am currently on Beta Pie...will these methods work for bootloader unlocking and TWRP, custom rom flash ???? I just wanna use PE/Havoc OS rom...no other tweaks or root
thanks its working
I updated to pie beta and I think this guide is not working for that, because when flashing twrp. I'm getting 'request download size is more than allowed size' and I tried every way possible to solve it. But no luck Hope you can help me with it, or maybe it'll work after stable version?
---------- Post added at 04:15 AM ---------- Previous post was at 04:11 AM ----------
utsavdey said:
I am currently on Beta Pie...will these methods work for bootloader unlocking and TWRP, custom rom flash ???? I just wanna use PE/Havoc OS rom...no other tweaks or root
Click to expand...
Click to collapse
It's not working for me. I also updated to pie beta few days back.
Is this method working on pie stable build
Anyone tried this method on the stable pie build 056?
Installing Lineage
Few quick things.
LOS 18.1 is now official so the guide will now just be covering that.
I also want to address a common question, you can use Windows for this process. I prefer Linux, and Fastboot just works in Linux without driver issues. If you have Fastboot and ADB working in Windows already feel free to use that if you want.
Frequently asked Questions:
This looks like a lot of work, is there an easier way to install? Try the LOS Wiki Method.
Using TWRP 3.5.2_9-01. Start off Fresh. Install OOS using the Fastboot ROM.
Start off with a fresh install of OOS. You need the latest version of OOS 10. I typically use a the fastboot ROMs for this as it will do both slots for me at once. (Alternatively you can use TWRP and install the ZIPs and do it twice to get it on both slots, or my least favorite, the MSM Tool if you want. Doesn't matter how OOS ends up on both slots, as long as it ends up on both slots.)
I use Linux, and honestly I feel like it's easier and more reliable for fastboot and ADB so that's what I'm including here in these steps. It's easy to boot from a USB.
To create a bootable Linux flash drive you can use Unetbootin, which you can download for free here (Your other option would be to burn the ISO straight to a DVD and skip the unetbootin step):
https://unetbootin.github.io/
For Linux, I'm using Linux Mint Cinnamon, You can download for free here:
https://www.linuxmint.com/download.php
Then run unetbootin (yours will look a little different, I'm running it in Linux):
{
"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"
}
Point it to the Linux ISO, and tell it where an empty flash drive is. It will erase everything on the flash drive. Afterwards you can load whatever you want on the flash drive. However be aware when booting Linux from this drive you can't access what is on the drive (at least not by normal methods).
After this has successfully completed, reboot the PC, and boot from the USB drive. Your PC will boot into Linux (turning off the PC and removing the USB drive will make it boot up like normal again).
Next we need to install fastboot and adb. You need to open up the "start menu" and open the "synaptic package manager". You can find this stuff in the menus, however the easiest way to get to these items is to just start typing the name of the item. See below:
Search fastboot, click the boxes, choose install. Then search for ADB, click the boxes, choose install and then click apply. It's that easy it will download everything that's needed and install.
Time to open up a terminal:
Just to make sure we don't run into any problems we need to update adb and fastboot. In the terminal run these commands to update fastboot and adb (this is downloading them directly from Google).
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip \platform-tools-latest-linux.zip
sudo cp platform-tools/adb /usr/bin/adb
sudo cp platform-tools/fastboot /usr/bin/fastboot
You will also need the appropriate fastboot ROM. Fastboot ROMs available in this thread. The catch being that thread is no longer updated. So we will need to make our own fastboot rom. To do this we need two things:
1. The stock rom zip (OP Site).
2. Payload dumper. I've yet to get the one from the GitHub link to work, so I've been using the one from this Article. Direct Download Link
You need to extract the payload.bin file from the stock rom zip. Extract the payload_dumper files as well, and place everything in the same folder. Payload_dumper requires python3. Open up Synaptic again, search for python3.6 and install it. Now open a terminal so we can extract the images from the payload.bin.
Navigate to the location of payload_dumper and your payload.bin file. In my case my commands are:
cd Desktop <-- switches to the Desktop folder
cd payload_dumper <-- switches to the payload_dumper folder on the Desktop
python3 payload_dumper.py payload.bin <-- runs the payload_dumper "program" and extract the images from the payload.bin
Now would be a good time to back everything up. The phone will get wiped. Extract the fastboot images to a folder that is easy to find. I would recommend the Desktop.
Now it's time to flash all those images we just extracted using payload dumper. Place the phone in fastboot mode. You can do this using the advanced reboot menu, ADB, or the key combinations (all key combos listed below for reference):
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
You can flash the images one by one or use a script. My script is available here. Flashing the fastboot ROM should look something like this:
That image explained:
cd Desktop <-- Switched the directory to the Desktop the default directory when you open up the terminal is the /home directory.
cd flash <-- I put my fastboot images in a folder called flash. This stuff is case sensitive. My folder was all lowercase.
sudo fastboot devices <-- Is just checking to see if my PC can see my phone, and making sure it's in fastboot. Sudo is necessary for this distro, as both fastboot and ADB must be run as root.
sudo sh FlashThese.sh <-- Tells the terminal to run my script, since the script contains fastboot commands it must be run as root.
At the end you should get something like this:
Then just choose start form Fastboot (If you were previously on a custom ROM go straight to recovery and wipe everything). Not booting and getting dumped off at the OnePlus recovery screen is nothing to worry about. Choose your language of choice, Wipe data and cache, Erase everything (Music, pics, etc), This can not be undone, continue. After that the phone will boot. Once booted enable developer options, advanced reboot, and reboot to fastboot.
2. Installing TWRP.
First step is to boot the correct TWRP image. Grab the current TWRP from the official site. You need both files, the img file, and the installer. Once again from the terminal:
The image explained:
cd Desktop <-- Switched the directory to the Desktop the default directory when you open up the terminal is the /home directory.
sudo fastboot devices <-- Is just checking to see if my PC can see my phone, and making sure it's in fastboot. Sudo is necessary for this distro, as both fastboot and ADB must be run as root.
sudo fastboot boot twrp-3.5.2_9-0-fajita.img * <-- Sends that TWRP image to the phone to be booted temporarily. Only boot this, never run the command "flash".
Once in TWRP the phone should show up as a media device so you can copy files to it. Copy the TWRP installer over to it. Choose Install from the TWRP menu and navigate to where you placed the TWRP installer. Press on it, and swipe to confirm flash. When it is done hit the back button until you are back out to the main menu.
From the main menu choose reboot, and choose Recovery:
The first time you try and reboot the official version of TWRP it will ask you if you want to install the TWRP app. Do NOT install the app. In the settings you can disable this prompt. Your other option is just uncheck both boxes at the screen you see below when you get to it, and then click the button that says do not install. Do use the slider. At that point the phone will reboot as to recovery as you selected.
Now that you are back in TWRP that is now installed, time to wipe the phone. From the main menu choose Wipe. Swipe the factory reset slider at the bottom. Then hit back. Next hit Format Data. Type Yes to Continue. Hit back to continue. Keep hitting back till you get to the main menu.
Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. So go back into the reboot menu, choose reboot to recovery again (swipe to allow modifications if it asks). You must do this after formatting data.
3. Install Lineage
Links:
Lineage 18.1 XDA Thread
Official 6T Lineage Downloads
The phone should still be in TWRP at this point. You now need to copy Lineage to the phone. From TWRP's main menu choose install. Then navigate to your ROM .zip location and click on it. Then swipe to confirm flash.
Lineage will replace TWRP, so you need to reflash TWRP as well. Run the TWRP installer again. If it's not on the phone, just copy it over again real quick. On A/B devices ROMs get flashed to the opposite slot. Things like Gapps, Magisk, etc get flashed to the current slot. We need Lineage on both slots, so it must be flash again. Flashing it twice only needs to be done the first time as we need to get rid of OOS. For updates it just gets flashed once. After the TWRP installer has run, back out to the main menu, and choose reboot, then recovery:
Once back in TWRP flash Lineage again. From TWRP's main menu choose install. Then navigate to your ROM .zip location and click on it. Then swipe to confirm flash.
Now run the TWRP installer again. Back out to the main menu, and reboot to recovery.
4.Optional, Gapps
Links:
NikGapps <-- For Lineage 18.1 (Use the R Folders for Android 11. I recommend the "Core" version. I also tested Basic though if you want that level of Gapps. I strongly recommend you grab setup wizard out of the R Addons Folder, I used the regular setup wizard, not the pixel one.)
MindTheGapps <-- It's worth mentioning here Lineage recommends MindTheGapps for 18.1. Take your pick. I personally use NikGapps as I can use a "leaner" Gapps package.
Now that your phone is back in TWRP for the last time before booting up Lineage, it's time to install Gapps if you want them. This step is optional. Same as the other steps here, go to install, choose your OpenGapps package, Then navigate to your .zip location and click on it. Then swipe to confirm flash.
5. Very Optional, Magisk
These steps are very optional. However this is how I, root, pass safety net, and get a various apps to appear in the Play store.
Flash Magisk in TWRP. For Magisk 23, you now have to rename the Magisk.apk to Magisk.zip. Then flash it in TWRP. If you wanted to uninstall it, you rename it to uninstall.zip. If you already had an older version of Magisk installed, make sure you do not have it hidden / nenamed when installing Magisk 23 for the first time. Restore the original package before installing 23.
Magisk <-- Flash this right after Gapps.
These items are add-ons are flashed in Magisk after the first boot (Don't flash these in TWRP anymore):
MagiskHide Props Config
Busybox
To flash modules in Magisk press the puzzle piece icon. Then choose install from storage. Now just choose your addons. After flashing the icons it will have a reboot icon at the bottom. You can reboot or you can press back and flash another. After you are done reboot.
You will also need a Terminal Emulator. I personally use:
Terminal Emulator for Android
Once all these are installed the first step is setup Magisk. Under Magisk go to settings:
In version 20.4+ Magisk Hide is no longer on by default. So make sure the Magisk Hide, Hide Magisk from various forms of detection switch is flipped. Then press Hide Magisk Manager. This will bring up a box for you to choose a random name for the Magisk Manager, type whatever you want here. You can leave it Manager if you wish, but I typically change this.
Now open Magisk again. It will ask you to download it again, click ok, then manually open the app again as it says. Now we need to open Magisk hide. This is now under the shield icon, then click the arrow at the top:
These are the apps you don't want to know that you have root. Less is better. You can cause instability problems by just choosing everything. My general rule of thumb is, Google, steaming video, music, and payment apps get selected. In my experience if I come across an app that needs it and I didn't select it, I just clear cache and/or data and re-open the app and it works. There are some big multiplayer apps that ban hardware / people, so do your research (don't ask me, I don't play those games).
Next time to change the device fingerprint using MagiskHide Props Config Module. We do this using the terminal emulator. In the terminal emulator, type "su" to gain root privileges. Then type props to run the module:
Now it's just following the menus. Choose option 1 - Edit device finger print. (type 1, hit enter)
After this you will see a menu of devices. It doesn't matter what device you pick really. If you want apps / Google to think you have a OPPO or Samsung pick one of those Fingerprints. However there's a bit more to passing Safety-net than that. Since Google has changed how things work not all those fingerprints that used to work will work now. Also now you may get an error when you turn on the phone because of the security dates. The OP6T Android 10 fingerprint has no issues at this point, so use that if you want:
After choosing the fingerprint you want, it will ask you if you want to reboot. Choose yes. After rebooting, you may need to clear the cache from the play store for some apps to appear in it. You should now pass safety net. Check this in Magisk:
6. Very Optional, Ad Blocking with a Host File.
You can block many things with a hosts file, most popular would be ads. I've been use StevenBlack's host file which is a compilation of several hosts files. This is located on Github:
https://github.com/StevenBlack/hosts (Scroll down you'll see the options of what you can block)
Direct link to the hosts file I use. This will block Adware / Malware.
Unfortunately for quite some time now on this device you can no longer just use a root browser to swap the hosts file. The easiest way is to use TWRP.
First we have to make the hosts file. The hosts file must use unix / linux line endings. If you are using linux, don't worry about this, just create the file. If you are using Windows, the easiest thing to do is use Notepad++ (Free).
Notepad++ Downloads
Next one other caveat. The hosts file is quite large. I've never had much luck copy and pasting it from any other browser than Firefox (Windows or Linux), but however you get it into Notepad++ is not a big deal.
Once in you have the hosts file into Notepad++ go to Edit, EOL Conversion, and Choose Unix (LF).
Now save the file as "hosts" no ending. This does mean under file type you will need to change it to All File types *.*. Move this hosts file to your phone. Then reboot to recovery. From the main TWRP menu, choose mount. Then mount system:
Hit the back button and go to the advanced menu. Choose File Manager:
You will find your hosts file under /sdcard, wherever you placed it. In my case I placed it in a folder called ROMs. Once you locate it, press and hold it for a moment, and relase. Then choose copy file:
At this point you need to tell TWRP where you want to paste the hosts file. It belongs in the /etc folder. The only hic-cup here is depending on what you were doing in TWRP this could be (on this device) /system/etc or /system/system/etc (you will see similar folders to the image below if you are in the right place). Once you are there, press "paste?" button in the lower right corner:
After this just swipe to confirm:
You can now reboot the device, and your hosts file should now be in place. Your ad block should now be active for all apps as it's global for all connections.
7. Reboot to system.
Updating Lineage
1. Flash Lineage.
Reboot to recovery. You can use the advanced reboot menu, or Volume Down + Power while turning the phone on. Don't wipe anything. From TWRP's main menu choose install. Then navigate to your ROM .zip location and click on it. Then swipe to confirm flash.
Lineage will replace TWRP, so you need to reflash TWRP as well. Run the TWRP installer again. After the TWRP installer has run, back out to the main menu, and choose reboot, then recovery:
2. Optional, Gapps (if you installed them once you must continue to install them or do a clean install)
Links:
NikGapps
Now that your phone is back in TWRP for the last time before booting up Lineage, it's time to install Gapps if you want them. This step is optional. Same as the other steps here, go to install, choose your OpenGapps package, Then navigate to your .zip location and click on it. Then swipe to confirm flash.
3. Reboot to system.
Last updatedSince I don't want people to have to wonder if these instructions are current, I am going to periodically test and update this post with my results. Please note I'm testing with a 6T, TMobile 6Ts are different. You can generally assume previous versions of LOS and OOS were also tested, but if you are unsure feel free to ask in this thread.
Last tested with:
OOS 10.3.7 and LOS 17.1 12-31 with TWRP 3.4.0-2
OOS 10.3.11 and LOS 18.1 05-27 with TWRP 3.5.2_9-0
This method has also been tested with:
OOS 10.3.3 and Omnirom 5-24 MicroG and Omnirom 5-24.
Cliff Notes
*TWRP 3.5.0_9-0+ Must be used with LOS 18 / 18.1
- Backup everything to the PC, so you will need to copy all your data over.
- Sync all your accounts, etc.
- In TWRP format data. Reboot recovery (This step wipes the device, make sure you backed everything up!)
- Factory Reset. (This is the slider at the bottom, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else)
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage (This is only the first time, to get the AOSP rom on both slots, only do this for the first install)
- Flash TWRP Installer (This is only the first time, to get the AOSP rom on both slots, only do this for the first install)
- Reboot to Recovery (This is only the first time, to get the AOSP rom on both slots, only do this for the first install)
- Flash Gapps (Optional)
- Flash Magisk (Optional) (Remember for ver 22 the Magisk.apk gets renamed to Magisk.zip, can also be renamed to uninstall.zip for uninstalling)
- Reboot to System.
- Then you should be able to setup the device, copy everything back over. Restore your data.
After this you should be able to update Lineage as normal.
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Optional, but if you flashed them once you have to keep flashing them.)
- Flash Magisk. (Optional)
- Reboot to system.
- No loss of data, or anything.
Thanks for the guide, able to flash los 17.1 successfully.
How to go back to OOS?
Does anyone have a guide on how to go back to OOS after flashing Lineage according to Lineage's instructions?
fordjonathan said:
Does anyone have a guide on how to go back to OOS after flashing Lineage according to Lineage's instructions?
Click to expand...
Click to collapse
Back up your data, use Step 1 of these instructions. That will put OOS back on your phone.
MSM Tool, always my least favorite option, but always an option.
MSM Tools for Regular 6T (TMobile uses a different one)
installed 17.1!
OhioYJ said:
Installing Lineage...
Click to expand...
Click to collapse
Massive thanks for your instructions!
- at first, I tried upgrading from LOS 16.0 to LOS 17.1. I followed the instructions on the wiki, but it landed me in the qualcomm crashdump mode.
- after that I ran into your instructions, and tried to follow your update guide, but it didn't help (not very surprising I guess, but I haven't had much to lose at this point ).
- after that, I just followed your fresh install guide (i.e. flashing the fastboot room and starting from scratch), followed every step and it worked!
I wonder if it's worth updating lineage OS wiki and pointing to your instructions? There is bunch of people in this thread, who also bricked the phone into crashdump, so perhaps it could help to prevent it for someone else.
Updating to LOS 17.1 ?
Dasseem said:
Thanks for the guide, able to flash los 17.1 successfully.
Click to expand...
Click to collapse
Initially I had problems with updating LOS, so I returned to Stock. As more people attempted to install LOS, and this fine Original Poster "Ohio" offered such excellent, and detailed instructions, I have been running LOS 16 since February.
However, I have not updated it, since I have had Zero Issues.
But to clarify, you used this method to update to LOS 17.1 ?
- coming from LOS 16 - without first returning to a fast-boot ROM ?
Did you up-date GApps accordingly during this Flash ?
Thank You, in advance, for any assistance!
:good:
barguybrady said:
But to clarify, you used this method to update to LOS 17.1 ?
- coming from LOS 16 - without first returning to a fast-boot ROM ?
Click to expand...
Click to collapse
Hi, I updated my previous reply to make it a bit more clear!
Yep, I was on LOS 16. Haven't had any issues, but figured why not update if I'll have to do it eventually
So I downloaded 17.1 and used the wiki instructions, which messed the phone up
Ended up flashing fastboot rom and starting from scratch, flashed gapps and magisk according to OhioYJ's instruction and it worked.
Flashing method
barguybrady said:
But to clarify, you used this method to update to LOS 17.1 ?
- coming from LOS 16 - without first returning to a fast-boot ROM ?
Did you up-date GApps accordingly during this Flash ?
Thank You, in advance, for any assistance!
:good:
Click to expand...
Click to collapse
I was using carbon ROM previously, had to move to OOS latest for flashing the lineage 17.1, believe it needs to be done if you are coming from pie, people know better correct me if I am wrong here.
As Karlicoss mentioned, it's better to follow the method posted by Ohio.
OhioYJ said:
Cliff Notes Versions
Installing Lineage
- Install fastboot ROM boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the image of TWRP.
- Run the TWRP installer, reboot to recovery
- You backed everything up right?
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery.
- Install Gapps if you want them.
- Install Magisk if you use Magisk. Do not install modules or other add ons at this point. Boot once and go through the setup and everything, then install your add-ons.
- Be aware the phone may restart once, then Lineage will start up and all will be good.
Updating Lineage
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean install)
- Flash Magisk. (Optional If you use it)
- Reboot to system.
- No loss of data, or anything.
- No need to flash anything twice etc.
Click to expand...
Click to collapse
Updating failed for me, as it shows everything encripted once I reboot the second time to recovery on slot B...
badpanda said:
Updating failed for me, as it shows everything encripted once I reboot the second time to recovery on slot B...
Click to expand...
Click to collapse
Usually this means you didnt format data, or you are using an old version of TWRP. Did you do a clean install?
I just tried it on my phone, was running 4-12 build, using 3.3.1-32 TWRP, updated to the 4-14 build, using 4-14 Gapps (nano), everything went smoothly here.
OhioYJ said:
Usually this means you didnt format data, or you are using an old version of TWRP. Did you do a clean install?
I just tried it on my phone, was running 4-12 build, using 3.3.1-32 TWRP, updated to the 4-14 build, using 4-14 Gapps (nano), everything went smoothly here.
Click to expand...
Click to collapse
No, no clean install. Just wanted to update to today's newest build os.
bump...
Thanks a lot for your guide. Very helpfull.
I'm using it with /e/ rom.
installing android 10 roms
I followed exactly as it was written. Same issues arose for me. After the phone is off then turned on no LTE. It makes phone calls and also text stuff. HOWEVER when you take out and reinsert sim LTE is enable. What is the problom?????????
sickpoppy said:
I followed exactly as it was written. Same issues arose for me. After the phone is off then turned on no LTE. It makes phone calls and also text stuff. HOWEVER when you take out and reinsert sim LTE is enable. What is the problom?????????
Click to expand...
Click to collapse
Just cycling airplane mode doesnt work? This isn't a TMobile 6T is it? You are in Sim slot 1? You maybe better asking in the LOS thread, and provide log it not working and then it working when you reinsert it. Im not quite sure whats going on there.
OhioYJ said:
Usually this means you didnt format data, or you are using an old version of TWRP. Did you do a clean install?
I just tried it on my phone, was running 4-12 build, using 3.3.1-32 TWRP, updated to the 4-14 build, using 4-14 Gapps (nano), everything went smoothly here.
Click to expand...
Click to collapse
So this means you do have to always format data for every single update??
---------- Post added at 09:07 PM ---------- Previous post was at 09:05 PM ----------
sickpoppy said:
I followed exactly as it was written. Same issues arose for me. After the phone is off then turned on no LTE. It makes phone calls and also text stuff. HOWEVER when you take out and reinsert sim LTE is enable. What is the problom?????????
Click to expand...
Click to collapse
Change your sim card to the other slot...
---------- Post added at 09:11 PM ---------- Previous post was at 09:07 PM ----------
@OhioYJ So for an update you boot to recovery flash LOS latest version then flash twrp again and then reboot to recovery second time then format data to possibly decript encrypted system and, transfer files both gapps and magisk to device and then install gapps and magisk, lastly just reboot to system?
reply
yes it is a tmobile but it was flashed to global. TWRP is the version you are using. downloaded the lastest ROM. Weird it finds LTE at first then like I said when then phone shuts off LTE doesnt work til I take sim out.
badpanda said:
So this means you do have to always format data for every single update??
Click to expand...
Click to collapse
No that would be ridiculous. Not necessary at all. You have something else going on, but I dont know what. My update procedure is exactly as listed on the OP, on two 6Ts, two different carriers.
sickpoppy said:
yes it is a tmobile but it was flashed to global. TWRP is the version you are using. downloaded the lastest ROM. Weird it finds LTE at first then like I said when then phone shuts off LTE doesnt work til I take sim out.
Click to expand...
Click to collapse
A TMobile "converted" to global does not equal a global 6T. Logs posted in the LOS thread, may help out other TMobile users? The TMobile 6Ts introduce all sorts of quirks, and Im afraid I dont have any experience with them, so hopefully another TMobile user will be able to help.
Well, I found this in a Telegram group (which I know I can't share the link) and when performing all possible tests, it works perfectly with my 4/128 spes.
And as we would all say, I am not responsible for any damage and loss of data caused to your device. I only share the information "as is" and the tests performed by myself on my personal device. Everything is at your own risk.
So, let's start with the post:
New Developer on this version:
@jabieff
Previous Developer
@dblenk9 - Telegram
2022/11/06 Update Changelog:
Synced latest TWRP 12.1 source
Fixed Android 13 ROM flashing issue (source side)
Changelog in the previous version by @dblenk9
Sync with latest TWRP
Update kernel to MIUI V13.0.4.0.SGCMIXM
Update blobs to MIUI V13.0.4.0.SGCMIXM
MTP fixed
Decrypt works
Features I tried and didn't have any problems
Flashing and decrypt data from A13 ROMs
Flashing and decrypt data from A12.1(A12L) ROMs
Flashing and decrypt data from MIUI-based ROMs (custom and Stock) with A12
Flashing Magisk
MTP fully functional
ADB sideload
Install recovery ramdisk and "Flash current TWRP" from Advanced menu
DO NOT USE WITH ANDROID 11 ROMS!!!
Bugs I've found so far
If you perform a format data, the internal memory will not be recognized in MTP mode of TWRP, which will not be displayed in Windows file explorer
SOLUTION: Boot into the OS at least once so that the internal memory is rebuilt and made available again in MTP mode
Sometimes, when checking the option "Automatically reflash TWRP after installing the ROM", it does nothing when it finishes installing the ROM
SOLUTION: The option seems to be somewhat bugged, so before restarting always reinstall TWRP with the methods that I will explain below
When flashing some ROMs, "Failed to mount *partition*" errors come out when you finish installing
SOLUTION: In some ROMs you may get errors when mounting some partitions, commonly "system_ext", "product" and "vendor".
If the installation process ended without any problem and without showing any error code, that's fine, you can restart without problems, This bug has been in all unofficial TWRP for this device
Steps to install
Make sure you have the bootloader unlocked before you start. There are many guides on the internet for that.
Tutorial for Windows only because zero knowledge for Mac and Linux
From PC:
Download the latest platform-tools from the Android developer site and extract the zip in an easily accessible folder
Download the TWRP image file from here, or from the post attachments
SHA256: 8F25AC88628E6D7BC5E29D8572CF4ACA3499B7D626685654B3C4548323B8D591
Restart your device to fastboot mode
Method 1:
Using this adb command if you have USB debugging active on your device
Code:
adb reboot bootloader
Method 2:
- Turn off your device
- After it has completely turned off, press and hold Vol - and the Power button at the same time until the word "FASTBOOT" with orange letters comes out
Method 3:
- Turn off yout device
- Press and hold Vol - button
- Connect the USB cable (previously connected to the PC) to the device and press and hold the button until the word "FASTBOOT" with orange letters comes out
Connect your device to the PC
Open a cmd window in the folder where you extracted the binaries from the zip from step 1
Easy method: Open the folder, and without leaving it, type "cmd" in the address bar of the file explorer and press enter. Command promt will open a window directly in the folder location
Verify that your device is recognized by fastboot using this command
Code:
fastboot devices
If your device has been detected (a serial number followed by the word fastboot), you can continue. Otherwise, check if the drivers are installed correctly, although if you used Mi Unlock and were able to unlock the device correctly on the PC you are using, you should not have problems with that.
- Because this device uses A/B partitions, there is no recovery partition as such, but it is integrated into the "boot" partition. So, first we must boot using the TWRP image.
Type this command in the cmd window, but don't press Enter yet, just type it and leave a space at the end
Code:
fastboot boot_
Don't write the "_". This only indicates the space you should leave at the end.
This is how it should look when you write it:
fastboot boot
Now, drag the image file (twrp-3.7.0.img) to the command window and drop it above the window. This will make you copy your exact location for convenience.
- The result should be this:
Code:
fastboot boot "C:\location\to\your\file\twrp-3.7.0.img"
Quotation marks are only added if the entire location has spaces.
Otherwise, it is displayed without quotation marks.
Press Enter and wait a few seconds. The MI logo will come out, and then the TWRP logo.
DONE! You've started perfectly in TWRP
From the device
NOTE: Only use these steps if you want to have TWRP installed semi-permanently
I said "semi-permanent" because when flashing any ROM, and knowing that the "recovery" is integrated into the "boot" partition, it will be lost after leaving TWRP, so you can follow these steps if you want to avoid loss of TWRP.
If you have easy access to a PC, you can be fine with the boot method. If you don't have easy access to a PC, you can follow these steps.
Method 1
While in the TWRP menu, tap the Advanced button
Now tap on the option "Flash current TWRP"
"Swipe to confirm" and the TWRP installation process will begin
Method 2
While in the TWRP menu, tap the Advanced button
Copy the TWRP image file to the internal memory or SD card from the PC. MTP mode is enabled by default
You can use a USB OTG too
Now tap on the option "Install recovery ramdisk"
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storages
"Swipe to confirm" and the TWRP installation process will begin
Method 3
While in the TWRP menu, tap the Install button
Copy the TWRP image file to the internal memory or SD card from the PC. MTP mode is enabled by default.
You can use a USB OTG too
Tap on the option "Install image"
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storage
In the new menu, select "Install recovery ramdisk" and then "Swipe to confirm Flash"
Remember that with the three methods mentioned above you will lose root access (Magisk), so do not forget to flash it again. These steps are also valid to update TWRP if you already had it previously installed.
Conclusion
I did everything I could but I couldn't find the source code for this TWRP, so I'm sorry for that.
05/05/2023
POST
- Link to GDrive fixed
11/11/2022
POST:
- Reverted to previous version as @jabieff TWRP is unable to flash MIUI ROMs due to dynamic partitioning error.
07/11/2022
POST
- Added info about Android 11
- Updated to latest TWRP and new developer
19-10-2022
POST:
- Fixed typo and A11 ROMs info added
Hello and thanks for this tutorial. I tried it on my new red minote 11 and unlike on 3.6.1 TWRP my pin code can't unlock encryption.
It returns :
Code:
Failed to decrypt user 0
Is there a way to solve yhis issue ?
Rom version : MUI global 13013 Stable RGKEUXM
Android version: 11 RKQ1.211001.001
Thanks !
essor-13 said:
Hello and thanks for this tutorial. I tried it on my new red minote 11 and unlike on 3.6.1 TWRP my pin code can't unlock encryption.
It returns :
Code:
Failed to decrypt user 0
Is there a way to solve yhis issue ?
Rom version : MUI global 13013 Stable RGKEUXM
Android version: 11 RKQ1.211001.001
Thanks !
Click to expand...
Click to collapse
I think this version of TWRP works only with MIUI13 A12. You're on A11 version of MIUI13.
essor-13 said:
Hello and thanks for this tutorial. I tried it on my new red minote 11 and unlike on 3.6.1 TWRP my pin code can't unlock encryption.
It returns :
Code:
Failed to decrypt user 0
Is there a way to solve yhis issue ?
Rom version : MUI global 13013 Stable RGKEUXM
Android version: 11 RKQ1.211001.001
Thanks !
Click to expand...
Click to collapse
This recovery is not compatible with Android 11 ROMs. If you need one for A11 specifically, use version 3.6.1
NeoSDAP said:
This recovery is not compatible with Android 11 ROMs. If you need one for A11 specifically, use version 3.6.1
Click to expand...
Click to collapse
Thanks for the answer. I'm a bit confused about this (I'm really not an expert, far from that). My previous phone was a antic galaxy S7 that passed awaysome days ago. With that phone (at the end I was on LOS 19 I think) there was no encryption issue, I installed the TWRP on a Oreo android version ans I never had android version compatibility issues (let say that is TWRP version x was compatible with android version y is was also compatible with android version y-1). It seems to be different with my new redmi note 11.
I also had a backup / restore issue (TWRP 3.6.1) : I did enter the TWRP by unlocking with my pin code, did the backup (data, system and also data+system in case of) and I wanted to restore the data backup (I tried to debloat the ROM via adb but I made some mistakes so I decided to restore the backup data + system) and the TWRP showed a warning : "pin must be desactivated before restoring". I tried to ignore the message (I made enough mistakes to be enable to reach the phone's login), the restore operation failed with an "error 255". So I reconfigured the phone, desactivated the login pin, went to TWRP, made the restore (no pin warning) but hen the phone didn't boot correctly (hanged 15 min on the MI startup logo with the three dots on the bottom, but nothing else happens).
I obviously did the backup / restore operation the wrong way. On my S7 it was very easy : I make a full backup, data+system, then I restore it when needed, and no issue at all). So What is the correct way to backup / restore a full system + data with TWRP without having to do a factory reset and then try to restore Titanium backup (which cannot restore correctly all the apps, some need to be resintalled). This solution works, but it is much longer and annoying than restoring a TWRP/nandroid backup.
Thanks !
@NeoSDAP You could add sth like 'only for A12/A13'-roms to the title and add a highlighted note, that You need 3.6.1 for A11 roms to the OP.
essor-13 said:
Thanks for the answer. I'm a bit confused about this (I'm really not an expert, far from that). My previous phone was a antic galaxy S7 that passed awaysome days ago. With that phone (at the end I was on LOS 19 I think) there was no encryption issue, I installed the TWRP on a Oreo android version ans I never had android version compatibility issues (let say that is TWRP version x was compatible with android version y is was also compatible with android version y-1). It seems to be different with my new redmi note 11.
I also had a backup / restore issue (TWRP 3.6.1) : I did enter the TWRP by unlocking with my pin code, did the backup (data, system and also data+system in case of) and I wanted to restore the data backup (I tried to debloat the ROM via adb but I made some mistakes so I decided to restore the backup data + system) and the TWRP showed a warning : "pin must be desactivated before restoring". I tried to ignore the message (I made enough mistakes to be enable to reach the phone's login), the restore operation failed with an "error 255". So I reconfigured the phone, desactivated the login pin, went to TWRP, made the restore (no pin warning) but hen the phone didn't boot correctly (hanged 15 min on the MI startup logo with the three dots on the bottom, but nothing else happens).
I obviously did the backup / restore operation the wrong way. On my S7 it was very easy : I make a full backup, data+system, then I restore it when needed, and no issue at all). So What is the correct way to backup / restore a full system + data with TWRP without having to do a factory reset and then try to restore Titanium backup (which cannot restore correctly all the apps, some need to be resintalled). This solution works, but it is much longer and annoying than restoring a TWRP/nandroid backup.
Thanks !
Click to expand...
Click to collapse
Because this device uses a different partition scheme (A/B partitions and, apparently, dynamic partitions) it is not necessary to make nandroid backups, since the partitions change size depending on the ROM you install.
If you want to keep everything in order:
- Keep a copy of TWRP and the zip of the ROM you are using to avoid problems in the future.
- If you want a backup of the info on your phone, I recommend you install Magisk and use Swift Backup. It's in the Play Store.
gentano said:
@NeoSDAP You could add sth like 'only for A12/A13'-roms to the title and add a highlighted note, that You need 3.6.1 for A11 roms to the OP.
Click to expand...
Click to collapse
Thanks for the correction. I have already modified the title
NeoSDAP said:
Thanks for the correction. I have already modified the title
Click to expand...
Click to collapse
Can you please tell me if it's possible to flash twrp via magisk app for root access and for installing twrp itself, actually I've updated my rn11 and insalled October security patch but my custom recovery along with root is overwritten
sarib said:
Can you please tell me if it's possible to flash twrp via magisk app for root access and for installing twrp itself, actually I've updated my rn11 and insalled October security patch but my custom recovery along with root is overwritten
Click to expand...
Click to collapse
Nope. You need a PC to install the recovery. Something that can also work is to use a phone rooted with Magisk and the ADB and fastboot module
NeoSDAP said:
Because this device uses a different partition scheme (A/B partitions and, apparently, dynamic partitions) it is not necessary to make nandroid backups, since the partitions change size depending on the ROM you install.
If you want to keep everything in order:
- Keep a copy of TWRP and the zip of the ROM you are using to avoid problems in the future.
- If you want a backup of the info on your phone, I recommend you install Magisk and use Swift Backup. It's in the Play Store.
Click to expand...
Click to collapse
Thanks a lot for those infos. I understand a bit better now.
By any chance do you know a rom (debloated) that works flawlessly (camera, wifi, NFC, BT, etc) with the redmi note 11 ? I had LOS on my S7, that was fine because it made the device last longer, but it wasn't withoutt issues.
am I doing something wrong
Thank.
{
"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"
}
Appl1 said:
War mache ich falsch? Hat jemand eine Idee?
Thank.
View attachment 5779933
Click to expand...
Click to collapse
According to the rules, English is required.
Boot to a different version from TWRP. The v3.62 will help, then flash the v3.7.0 through TWRP. It happens, probably, because some custom recoveries, doesn't allow this version to boot to.
SubwayChamp said:
Gemäß den Regeln ist Englisch erforderlich.
Booten Sie mit einer anderen Version von TWRP. Die v3.62 wird helfen, dann die v3.7.0 über TWRP flashen. Es passiert wahrscheinlich, weil einige benutzerdefinierte Wiederherstellungen es dieser Version nicht erlauben, zu booten.
Click to expand...
Click to collapse
danke werde ich im laufe des tages ausprobieren. Ich habe auf Englisch geschrieben. Verzeihung
Appl1 said:
am I doing something wrong
Thank.
View attachment 5779933
Click to expand...
Click to collapse
Do you have unlocked bootloader?
Appl1 said:
danke werde ich im laufe des tages ausprobieren. Ich habe auf Englisch geschrieben. Verzeihung
Click to expand...
Click to collapse
Thanks for the edit of your first post and the switch to English. However, if you check you post above it's again only in German. Did you check your browser's settings if it automatically translates to German even if you wrote in English?
Regards
Oswald Boelcke
Senior Moderator
sarib said:
Can you please tell me if it's possible to flash twrp via magisk app for root access and for installing twrp itself, actually I've updated my rn11 and insalled October security patch but my custom recovery along with root is overwritten
Click to expand...
Click to collapse
Same ****.. I bought my phone in July... then rooted it... then all these useless security patches for me used to unroot my phone - remove TWRP and the root while have magick app installed. One time tried to reroot and ****ed up so had to reflash again the stock rom (I was with the stock rom before) just lost some data (not a big deal... all apps with their non cloud savable data, settings and etc LOL)
So I am still wondering how to avoid this and properly update without losing the root.
Also when Xiaomi will stop releasing **** small updates every month?
Flammable98 said:
Same ****.. I bought my phone in July... then rooted it... then all these useless security patches for me used to unroot my phone - remove TWRP and the root while have magick app installed. One time tried to reroot and ****ed up so had to reflash again the stock rom (I was with the stock rom before) just lost some data (not a big deal... all apps with their non cloud savable data, settings and etc LOL)
So I am still wondering how to avoid this and properly update without losing the root.
Also when Xiaomi will stop releasing **** small updates every month?
Click to expand...
Click to collapse
There´s not such a thing; "...properly update without losing the root", any major update causes the loss of root, because of boot partition, but, if the update is only about security policies, then you shouldn´t lost root. Rooting this device can always be done, flashing the Magisk zip over the ROM.
Anyway, you can choose, not to update automatically, so, this is up to you, get it or not.
Flammable98 said:
Same ****.. I bought my phone in July... then rooted it... then all these useless security patches for me used to unroot my phone - remove TWRP and the root while have magick app installed. One time tried to reroot and ****ed up so had to reflash again the stock rom (I was with the stock rom before) just lost some data (not a big deal... all apps with their non cloud savable data, settings and etc LOL)
So I am still wondering how to avoid this and properly update without losing the root.
Also when Xiaomi will stop releasing **** small updates every month?
Click to expand...
Click to collapse
There's a new update "November patch" and I'm now thinking what I should do