Database Info

Honor 8: Nougat (Android 7.x) B360 - TWRP and Root HOW TO

I'd like to create a new thread on installing TWRP and rooting Android Nougat (7.x) on version B360 of the Honor 8. All the threads I see are people frantically trying to restore their phone to their previous glory. To keep people from asking "will this work on yada yada model, *I* have a FRD-L04 which is the 32gb unlocked SINGLE SIM variant sold locally at Best Buy here in the states and I'm pretty sure the FRD-L09 is the international DUAL SIM version with 64GB and I believe firmware for both of these are different? If not, please correct me. The process should be the same for all variants, but the files used will be different.
I want to update this OP and keep it as up to date as possible. If we can get 3 or more people to confirm a certain process works in this thread, I will update it with the proper links to all tools/files/versions of TWRP and SuperSU as well as firmware that's needed. I think I currently count eleven different threads all over the place on this and would be nice to have it centralized. Let's help out and get this phone going with a working root on Nougat!!!
Here are the questions I propose:
1. What is the actual steps to root the Honor 8 running a FULL STOCK version of B360 (Android 7.x)?
A. Unlock Bootloader (This process should be the same as always)
B. Flash TWRP (Which version?) This should be a simple flash with fastboot
C. Flash SuperSU (Which version?) This should be a simple flash with TWRP
D. What are the current issues with this process? (encryption issues, formatting, unable to access the Data partition, etc)
E. How to revert back (and when I say back, I mean ANY working state of Nougat (Android 6.x) or Marshmallow(Android 7.x))
F. How to install extras (Xposed for example, etc)
If I can have answered the questions above, I will clean it up and move it over to the guide section. As it stands now we have no guide. We just need clarification on what works, what doesn't and the process.
Also, PLEASE be kind to those who don't speak English as their primary language. The Honor 8 is an international phone and I see many people getting angry because they don't understand or don't follow instructions correctly because the OP didn't clearly state what they did. Let's help each other out!
Here's an example step by step for unlocking the bootloader below. This is what I'd like to do for each of the questions above.
A: Unlocking the bootloader (UNDERSTAND THAT BY UNLOCKING THE BOOTLOADER ALL YOUR DATA ON THE PHONE WILL BE ERASED AS IF YOU'RE PULLING IT OUT OF THE BOX FOR THE FIRST TIME)
1. Go to Huawei's EMUI site and log in. If you need to create a new account, do so. Link here: http://www.emui.com/en/plugin/hwdownload/download
2. Click on the DOWNLOAD link at the top of the site.
3. Underneath the search field you will see a green link that says "Unlock Bootloader". Click it and follow the instructions. You will be asked to enter in several pieces of information about your phone.
4. Once you've filled out all the information, you will receive your unlock code at the bottom of the screen. Write this down and save it. This number will NEVER change.
5. On your Honor 8, go to Settings > About and tap on the Build Number seven times until you unlock the Developer Settings.
6. In Developer Settings, check Enable OEM Unlock.
7. Scroll down a bit more and check USB Debugging.
8. Go to Huawei's site and download their HiSuite and install it. This installs the OFFICIAL Honor 8 USB driver. Link here: http://consumer.huawei.com/minisite/HiSuite_en/index.html Once the app is installed, you can unselect start with Windows under settings.
9. Plug in your Honor 8 with the provided USB cable. Give it about 45 seconds to install the driver and recognize it. You may need to go to your phone and tap on "Allow File Access". You will be presented with a question asking if you'd always like to trust the computer you just connected to. Select yes, if this is your primary computer you will be working with.
10. Now download the most up to date ADB drivers. A Google employee has created one link to get that and make it easy. Link here: https://developer.android.com/studio/releases/platform-tools.html
11. Open the zip file you just downloaded and create a folder on your computer easy to get to (I recommend c:\ADB) and paste those files there so they are extracted.
12. Now open the folder up in Windows Explorer if you closed it and hold down the Shift key and RIGHT click in the open area and click "Open command window here"
13. Type adb devices and hit enter. You should see a device ID as a response in the window.
14. Type adb reboot bootloader and hit enter. Give it a couple of seconds and the phone will load the bootloader.
15. Now type fastboot devices and hit enter. You should see your device ID appear again.
16. LAST CHANCE before it wipes everything and unlocks the booloader!!! Type fastboot oem unlock XXXXXXXXXX (where XXXXXXXXXX is the unlock code you received on step 4) and hit enter. It will ask if you're sure. Once this is done, the phone will wipe your data, unlock the phone and reboot. Your Honor 8's bootloader is now unlocked.
B. Flash TWRP (Which version?) This should be a simple flash with fastboot. This is already discussed in another post, but I will put here for reference.
1. Grab a working copy of TWRP for the Honor 8 here: https://forum.xda-developers.com/showpost.php?p=70893767&postcount=408
2. Download TWRP into the same folder you used in step A above (where you're keeping all your files)
2. Navigate in Windows Explorer to this location and hold down the Shift key and RIGHT click in the open area and click "Open command window here"
3. Type adb devices and hit enter. You should see a device ID as a response in the window.
4. Type adb reboot bootloader and hit enter. Give it a couple of seconds and the phone will load the bootloader.
5. Now type fastboot devices and hit enter. You should see your device ID appear again.
6. Type fastboot flash recovery frd-twrp.img and hit enter.
7. Once this is complete, unplug your phone.
8. Hold Volume UP and Power at the same time. Release ONLY the Power button after the blue Honor logo appears.
9. You now are booted into TWRP and it's been successfully flashed.
C. Flash SuperSU (Which version?) This should be a simple flash with TWRP. This is a crazy process because of the encryption on the Data partition. Below is the exact steps I can confirm works from the help of others on here.
1. Boot into TWRP
2. Once there, when asked to keep system read only? - swipe to allow modifications
3. Tap Install
4. Tap Select Storage - Select your SD card
5. Select the supersu file "SuperSU-v2.79-201612051815-EMUI5.0.zip"
6. Swipe to confirm flash
7. Ignore the multiple errors: "Failed to mount '/data' (Invalid argument)
8. Go back to the main menu
9. Select Reboot to Recovery
10. When asked to keep system read only? - swiped to allow modifications (again)
11. Tap Wipe
12. Tap Format Data
13. Type YES then hit enter
14. It will format data using make_ext4fs..
15. When finished, tap Reboot System
16. Reboot back into TWRP
17. Swipe to allow modifications (You can check the box to never show this again)
18. Tap Install
19. Select storage
20. Select your SD card
21. Select the supersu file "SuperSU-v2.79-201612051815-EMUI5.0.zip"
22. Swipe to confirm flash
23. You should see NO ERRORS now when installing SuperSU
24. Wipe cache/dalvik
25. Swipe to wipe
26. Reboot system
Once here, you can download root checker and it will verify you have root access - BUT.. see section D below!
D. What are the current issues with this process? (encryption issues, formatting, unable to access the Data partition, etc)
Some applications like Root Checker will verify that you have root. Other applications will even prompt you (like any of the basic quick reboot apps that easily let you back into recovery) but other major apps like BusyBox and Viper4Audio (when asking to load the driver) will simply fail upon installation. I'm not sure why, since you have R/W access to both the system and the newly unencrypted data partition. I'm really hoping someone can help with this one!
E. How to revert back (and when I say back, I mean ANY working state of Nougat (Android 6.x) or Marshmallow(Android 7.x))
F. How to install extras (Xposed for example, etc)

I know and have done A, B, and C, but as for the rest I'm not too sure about those.

Maybe in the wrong section but thank you.

joesee said:
14. It will format data using make_ext4fs..
Click to expand...
Click to collapse
The Honor 8 defaults file system for /data is F2FS. Do you see any performance changes going back to EXT4? Is it possible to keep F2FS?

joesee said:
15. When finished, tap Reboot System
Click to expand...
Click to collapse
When I wipe then reboot I get stuck in the bootup screen
EDIT； Nevermind I just didn't wait long enough for my phone to boot up

KevinN206 said:
The Honor 8 defaults file system for /data is F2FS. Do you see any performance changes going back to EXT4? Is it possible to keep F2FS?
Click to expand...
Click to collapse
Yes, but twrp read it as ext file, i tested both format f2fs and ext4, i dont feel any different between those 2.
Yes, you can changed the data format to f2fs with twrp but if you reverted back to MM, its requred to changed the data to ext4 format, if not, you'll get bootloop. (dont know if its twrp bugs or not)
Worst scenario, you'll lost all stock recoveries and everything.
I've been there... Lol

faizalotai said:
Yes, but twrp read it as ext file, i tested both format f2fs and ext4, i dont feel any different between those 2.
Yes, you can changed the data format to f2fs with twrp but if you reverted back to MM, its requred to changed the data to ext4 format, if not, you'll get bootloop. (dont know if its twrp bugs or not)
Worst scenario, you'll lost all stock recoveries and everything.
I've been there... Lol
Click to expand...
Click to collapse
Are you saying I can format /data with F2FS to remove the encryption? I am assuming TWRP does not support the encryption yet. Bootlop sux but most important stuffs on my phone is stored on the SD card anyway so it's not too bad to start over.
Maybe it's just me but it seems encryption adds a bit of risks when playing around with rooting. Has there been a scenario where you *can't* recover from bootloop permanently?

KevinN206 said:
Are you saying I can format /data with F2FS to remove the encryption? I am assuming TWRP does not support the encryption yet. Bootlop sux but most important stuffs on my phone is stored on the SD card anyway so it's not too bad to start over.
Maybe it's just me but it seems encryption adds a bit of risks when playing around with rooting. Has there been a scenario where you *can't* recover from bootloop permanently?
Click to expand...
Click to collapse
So far, i've experienced with bootloop and no recoveries available,
As long as you have fastboot mode and bootloader key, you're safe.

faizalotai said:
So far, i've experienced with bootloop and no recoveries available,
As long as you have fastboot mode and bootloader key, you're safe.
Click to expand...
Click to collapse
I am afraid of running into this issue from a fellow xda. The person still doesn't have a solution. https://forum.xda-developers.com/mate-8/help/encrypted-data-mount-t3537645

I'm running into issues with Bluetooth activation, and previously NFC, which i fixed by reflashing the hw_update package, but still no Bluetooth.
I've followed each and every single step on this guide, and BT was working perfectly before.
Any ideas where this may be coming from ?
Still, thanks or the guide

For the SuperSU instructions, you don't have to reformat /data. Yes, TWRP won't be able to access it, but you really only need that for making full system backups. You can access everything in /system/ and then ADB push to /data/ after boot, or fastboot flash an image to /data/ from bootloader. It's not ideal, but it saves you from having to wipe out your configuration.
I'll echo the above poster, as long as you're bootloader unlocked and can issue fastboot commands I'm not sure you're truly bricked. Worst case scenario you ought to be able to flash individual partition images to recover, I unpacked the Nougat update zip to extract the partition images and I've been using those when my tinkering results in a bootloop -- corrupted boot and corrupted recovery I fixed easily.

Hello. Im coming from general topic on Honor 8 rooting but my issue is related to Android MM.
So i had stock EMUI 4.1 (Android 6.0) which i unlocked, flashed TWRP and SuperSU.
Today EMUI 5 (Android 7 ) update came by air so i installed it. After update - no TWPR neither SuperSU.
I enabled Developer options and saw "Enable OEM unlock" switch in OFF state and grayed out (impossible to switch ON).
So now i cannot flash TWPR as fastboot gives error "Command not allowed".
During boot phone says that it is unlocked, FRP lock. Otherwise it boots and works fine but no root.
Any solution possible?
Thank you.

Telperion said:
For the SuperSU instructions, you don't have to reformat /data. Yes, TWRP won't be able to access it, but you really only need that for making full system backups. You can access everything in /system/ and then ADB push to /data/ after boot, or fastboot flash an image to /data/ from bootloader. It's not ideal, but it saves you from having to wipe out your configuration.
I'll echo the above poster, as long as you're bootloader unlocked and can issue fastboot commands I'm not sure you're truly bricked. Worst case scenario you ought to be able to flash individual partition images to recover, I unpacked the Nougat update zip to extract the partition images and I've been using those when my tinkering results in a bootloop -- corrupted boot and corrupted recovery I fixed easily.
Click to expand...
Click to collapse
can u please tell more or make a step by step tutorial on rooting? I'm stuck in rooting, when I format data and boot agai into recovery and flash su It still ends with error 1, dnt know which error it is..

I have FRD-L09 C432B360 Honor 8 (Sweden) with EMUI 5.0, i have TWRP 3.1.0.0, unlocked bootloader
I could not root my phone since it uppdated to nougat (EMUI 5.0)
I tried everything what i could find on the net, but nothing worked yet, any suggestions ?
thanks

Is there any way to do this without rooting?
I recently got my phone and I didn't get the update. I am still running on EMUI 4.1

ajmdrh said:
I have FRD-L09 C432B360 Honor 8 (Sweden) with EMUI 5.0, i have TWRP 3.1.0.0, unlocked bootloader
I could not root my phone since it uppdated to nougat (EMUI 5.0)
I tried everything what i could find on the net, but nothing worked yet, any suggestions ?
thanks
Click to expand...
Click to collapse
Update to latest TWRP and try again

Shehzaan said:
I recently got my phone and I didn't get the update. I am still running on EMUI 4.1
Click to expand...
Click to collapse
Indian version?? Frd-l02?

venugopalu007 said:
Indian version?? Frd-l02?
Click to expand...
Click to collapse
Nope, it is FRD-L09C636B130. I think this is the Middle East version.

Shehzaan said:
Nope, it is FRD-L09C636B130. I think this is the Middle East version.
Click to expand...
Click to collapse
Yes, it is middle east variant

PalakMi said:
Yes, it is middle east variant
Click to expand...
Click to collapse
Do you have any idea how can I get EMUI 5.0 without rooting?

Swipe Elite max : Unlock Bootloader,Unofficial TWRP, Rooting and Stock reflash.

IMPORTANT UPDATE : I have observed that when mounting system R/w device restarts. It means that even after rooting successfully, system is blocking the app. So rooting will not be complete as of now,till further corrections. Rest of the operations are normal, quick reboot apps work properly. and device works normally. So please bear with me.
Freinds , this thread is basically for what the title suggests. After a long time I was able to do it.
I'll update as required, so be patient. and keep watching.
1. Unlock Bootloader
a. Boot device in bootloader from adb in cmd terminal. (To go in fastboot mode, press power and volume down button ).
Please enter these commands, one at a time.
Code:
adb devices
(this will show your device)
adb reboot-bootloader
( device will reboot to bootloader). Then enter this...
fastboot devices
(this will show your device)
fastboot oem unlock-go
( If it shows already unlocked, go to twrp flash. If it is not, It will ask for erasing data, so backup all your data. This will unlock your bootloader.)
2. Flash TWRP
In fastboot mode: continue.......
Code:
fastboot flash recovery twrp.img
(Flash the image I have provided)
You can also try
fastboot boot twrp.img
( to try this image file, if you are scared of bricking the phone.)
3. Flash patched boot.
Code:
fastboot flash boot boot.img
(Flash the image I have provided. This is necessary as otherwise the su zip may not work )
4. Rooting
Please copy the SuperSu zip file to your micro sd card. Now boot to Twrp recovery. My advice is to backup of your system and boot. Then wipe data, dalvik-cache,cache, Internal storage. (Sometimes, format option is required.)
Now flash this zip.
If there are errors anywhere, please tell me and I shall try to correct them.
Updates :
1. Twrp stable added on 8/6/2018
2. Twrp_3.1.0.1 added on 11/6/2018, Removed Old Twrp link.
3. Twrp_3.1.0.1 Link updated on 13.6.2018.
4. Twrp_3.1.0.1 Link updated on 9.7.2019. Removed Old Twrp 3.1.0.1 link.
Downloads
1. Twrp_Stable_3.0.2.0.img: Link
2. TWRP_3.1.0.1_unofficial_SwipeEliteMax : https://drive.google.com/open?id=1n-DfHwC4_WRn_Jlr5FosOb6lW827M5ho
Remember first thing before rooting, do a backup of system and boot.img. Rest is your choice.
2. SuperSu zip: http://www.supersu.com/download Or you can download from anywhere on the net.
3. Patched Boot : Link

Stock Reflash and subsequent Update:
1. Stock Version V12 Reflash :
Remember , boot takes 5-10 mins to come on. So don't panic when device doesn't boot.
If the need arises due to any reason device hangs in logo, first restore only boot which you backed up. If still no change, restore system also.
But if you want to flash stock version , then read ahead.
The FOTA zip did not work for me from adb sideload. So I will recommend the QFIL download.
1. Download Stock Rom and Qualcomm downloader from here
Extract the zip. Install the drivers.
2. QFIL install : Download and install Qualcomm downloader.
It should look like the image in attachments
1. If it shows Flat Build / Meta Build, choose Flat Build.
2. Click "browse" and select "prog_emmc_firehose_8937_lite.mbn" , in the Extracted Stock rom folder
3. Click Load XML and select "rawprogram_unsparse.xml" in the Extracted Stock rom folder.
4. Click Load Patch and select "patch0.xml" in the Extracted Stock rom folder.
5. Click Download. If device is in adb mode, no problem, it will go in download mode automatically.
If it is not, just connect and shutdown device . While it is shutting down, it will connect automatically andf flash will begin.
Do not disconnect while process is on. Be patient.
2. Update to V15 :
After Stock reflash, the update to V15 comes immediately after connecting to internet.
Just incase someone wants to flash it offline , here is the process and file.
1. Recovery Method : Place gobi zip in adb folder . Go to stock recovery. Press Volume up and Power button. Once in recovery, choose "update from adb" .
Enter the following command in cmd console :
Code:
adb sideload update-gobi.zip.
Downloads : Update zip for Version Update from V12 to V15. Link

Yogesh1969 said:
Freinds , this thread is basically for what the title suggests. After a long time I was able to do it.
I'll update as required, so be patient. and keep watching.
1. Unlock Bootloader
a. Boot device in bootloader from adb in cmd terminal, Please enter these commands, one at a time.
2. Flash TWRP
In fastboot mode: continue.......
You can also try
3. Flash patched boot.
4. Rooting
Please copy the SuperSu zip file to your micro sd card.
My advice is to backup your data, then wipe data, dalvik-cache,cache, Internal storage. Sometimes, format option is required.
Now boot to Twrp recovery and flash this zip.
If there are errors anywhere, please tell me and I shall try to correct them.
Downloads
1. TWRP : https://drive.google.com/open?id=0BztfiMqkQrCaQVA4T01pRmlmYXc
Remember first thing before rooting, do a backup of system and boot. Rest is your schoice.
2. SuperSu zip: http://www.supersu.com/download
3. Boot : https://drive.google.com/open?id=19StfSorHM8T89uX07epstCWIUnMsITjz
Click to expand...
Click to collapse
Thanks for help bro. But the tarp zip file u shared needs a password to be opened.

Sorry
partha_h said:
Thanks for help bro. But the tarp zip file u shared needs a password to be opened.
Click to expand...
Click to collapse
Sorry Parth. I linked a wrong image . I now have updated the link. please check and tell me. Dont' hurry in any process. Take care.

Yogesh1969 said:
Sorry Parth. I linked a wrong image . I now have updated the link. please check and tell me. Dont' hurry in any process. Take care.
Click to expand...
Click to collapse
Thanks
Rooted my device successfully. Solved the twrp data decrypt password issue. Mounted super su via usb and my device is successfully rooted.
Thanks again
Now it's time to search for custom roms. Suggest me any ROM u recommend

partha_h said:
Thanks
Rooted my device successfully. Solved the twrp data decrypt password issue. Mounted super su via usb and my device is successfully rooted.
Thanks again
Now it's time to search for custom roms. Suggest me any ROM u recommend
Click to expand...
Click to collapse
Glad to hear that. I don't have any information about specific roms for swipe but we may have to port any aosp or lineage roms for our chipset (msm8937). Once I'm free, I'll get to search that. ....

partha_h said:
Thanks
Now it's time to search for custom roms. Suggest me any ROM u recommend
Click to expand...
Click to collapse
I have ported an AOSP for Redmi 3s. But it has flaws,(wifi, etc.) will take time. Also, I have removed all unwanted apps from the stock. So it is now smaller.

Sorry repeated msg

Yogesh1969 said:
I have ported an AOSP for Redmi 3s. But it has flaws,(wifi, etc.) will take time. Also, I have removed all unwanted apps from the stock. So it is now smaller.
Click to expand...
Click to collapse
Pls share if there is any . Thanks

partha_h said:
Pls share if there is any . Thanks
Click to expand...
Click to collapse
Actually, AOSP and lineage Os ,both are ported successfully. But there are some flaws. Time is a major factor.
Also, I think Our Rom is better than these roms. From twrp I removed all useless apps. So memory has increased a bit.
So, i think instead of marshmallow I should try Nougat or Oreo if possible. Of course time is an enemy . Just hope.

Yogesh1969 said:
Actually, AOSP and lineage Os ,both are ported successfully. But there are some flaws. Time is a major factor.
Also, I think Our Rom is better than these roms. From twrp I removed all useless apps. So memory has increased a bit.
So, i think instead of marshmallow I should try Nougat or Oreo if possible. Of course time is an enemy . Just hope.
Click to expand...
Click to collapse
Hi. U r doing great. Android 7 or 8 would be gud option. Keep up the good work. Thanks

Some one plz send build.prop file of swipe elite max
Some one plz send build.prop file of swipe elite max

Your build.prop attached.
Sachin2015 said:
Some one plz send build.prop file of swipe elite max
Click to expand...
Click to collapse
Is something wrong with your phone or just experimenting ?
Anyways, there are two build.prop files in the system folder, so attached both. good luck.

Yogesh1969 said:
Is something wrong with your phone or just experimenting ?
Anyways, there are two build.prop files in the system folder, so attached both. good luck.
Click to expand...
Click to collapse
Thanx Dude.
How to enable VoLTE for airtel user in this phone ?
How to write imei on this phone ?
and can u send a updated baseband file for this ?

Sachin2015 said:
Thanx Dude.
How to enable VoLTE for airtel user in this phone ?
How to write imei on this phone ?
and can u send a updated baseband file for this ?
Click to expand...
Click to collapse
Hi. This is a very late reply . Sorry for that.
To enable volte, you have to go to
Settings>More>Cellular networks.
Here, you have to enable/On Enhanced 4G Lte mode.
But, you have to remember, few things. Our phone has only one 4g and one 2g slot. You can use any slot for 4g. The other will automatically turn to 2g. This happens when you choose data for that sim.
Another problem you will face if you have the other sim of JIO. It works only in 4g. So if you awnt volte /4g on Airtel and other sim is Jio, you will have no network on Jio as it does not work in 2g/3g.
For Imei , just google SN / IMEI writing softwares from the net. But mind you enter the right IMEIs, as you mind land in trouble if non-matching one is written.
What base band file do you want ? The firmware folder ?

Yogesh1969 said:
Hi. This is a very late reply . Sorry for that.
To enable volte, you have to go to
Settings>More>Cellular networks.
Here, you have to enable/On Enhanced 4G Lte mode.
But, you have to remember, few things. Our phone has only one 4g and one 2g slot. You can use any slot for 4g. The other will automatically turn to 2g. This happens when you choose data for that sim.
Another problem you will face if you have the other sim of JIO. It works only in 4g. So if you awnt volte /4g on Airtel and other sim is Jio, you will have no network on Jio as it does not work in 2g/3g.
For Imei , just google SN / IMEI writing softwares from the net. But mind you enter the right IMEIs, as you mind land in trouble if non-matching one is written.
What base band file do you want ? The firmware folder ?
Click to expand...
Click to collapse
not showing any network..need the modem files

Sachin2015 said:
not showing any network..need the modem files
Click to expand...
Click to collapse
Did you get the files ? If you want the firmware folder, im attaching here.

[guide] Blu Vivo XL4 | | Vivo Xi || Vivo Xi+

The BLU VIVO XL4 has arived.
Sorry this guide is not for very new users, it relies on certain amount of prior knowledge.
**NOTE**
Unlocking Bootloader WILL set warranty flag to "NO"
Make the read-back backup, BEFORE unlocking, so there is a possibility to restore warranty to "yes"
Getting SPFlash Tool to work on BLU VIVO XL4
I used sp flash tool version 5.18.28
Needs custom DA file and Auth file. Both have been found from a near clone device.
Open flash tool select the DA file and Auth file from the link below.
add the scatter file from archive. There is a preloader file in the archive also. This is needed for spflash tool to open the Auth file.
Stock Rom and Auth file
Then follow the guide found on youtube.
Not planning to go into too much detail about the actual pulling of the firmware, as there is already
a fantastic guide with step-by-step photos and also a video.
Just the basics
Pull stock rom with spflash tool once just from the "boot region" to get the preloader file.
Process that file with the Wwr_MTK tool to get partition table information.
And one more time pull as one large binary file from the "user region" then split it into
individual images using the tool called "Wwr_MTK" it can be found on other site(Hovatek). I cannot put a
link as it is against forum rules (no advertising other forums)
But there is a youtube video that describes the process. And gives link for download of the tool.
**NOTE-1**
The Wwr_MTK tool did not have the correct chip (mt6762 In fact the "family class" for the chip is mt6765) as an option. Because of this you will need to add it to the tool before using it. Open the downloaded zip.( I used "WwR_MTK_2.40_Eng" ). Open "Template.ini" with text editing software, in the section labeled "CPU" add "MT6765 2" , keep same format as the rest of the file. Save the changes and close Template.ini.
Now when you run the tool, you will be able to create the scatter file as you split the rom into files.
**NOTE-2**
The tool connects to internet and downloads fresh the files and scripts when you start it. There is a 30 second ad screen displayed. If you block internet to the tool, then the add screen turns into 2 minute wait screen. I am not suggesting that you hack the tool to by-pass it, just letting you know what to expect.
IT IS HIGHLY RECOMMENDED TO MAKE YOUR OWN FULL BACKUP BEFORE PERFORMING THESE STEPS
AFTER YOU HAVE MADE FULL BACKUPS
Now to start modifying
DOWNLOAD
UNLOCK BOOTLOADER
unlocking bootloader is no more complicated then then enabling OEM unlock toggle in dev options menu.
Then performing Command in terminal. Just like so many android devices.
Unlock Bootloader
1. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select more "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
2. Open cmd or power shell terminal
3. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
4.Once the phone has finished loading into fastboot mode type this command
Code:
fastboot oem unlock
I also did --MIGHT be an optional step
Code:
fastboot flashing unlock
Do not think both were needed.
After each command when phone was rebooted,
it took extra time to open. But did not show the normal recovery screen while
it did the factory reset. But a reset did happen both times,
as I had the setup wizard each time.
Even after unlocking bootloader, doing a "fastboot boot *xyz.img" (boot or recovery test images)
Phone would only cycle to off then do a full reboot. Doing "fastboot flash boot boot.img" does flash the boot.
And "fastboot flash recovery recovery.img" does flash the recovery.
TWRP
1. Download TWRP From Link above
2. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
3. Open cmd or power shell terminal
4. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
5. Now give the command to flash twrp, assuming you downloaded the file to default download folder
Code:
fastboot flash recovery %userprofile%\downloads\TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img
5. Reboot to twrp. Needed to boot directly to twrp, or stock recovery will be re-flashed by phone.
Code:
fastboot oem reboot-recovery
Once inside twrp It is asking for password to unlock (decrypt)***automatic decrypt not work on this device as of YET***
this is supposed to be same password used to unlock phone.
Because this twrp does not work with encryption, every time you reboot you will have to select language, if changed from default.
To get recovery to be functional, you need to make phone patched for both "DM-Verity" and "Force-encryption"
I do this with
"Universal Disabler"
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
There is similar utiliy built into this Recovery image.
to use the built in option , Select ADVANCED, Then RM Forceencrypt
This will flash the lazypatcher with options set to remove encryption both in boot.img and /vender/*fstab : remove dm-verity.
--OR-- manually do the following steps
Steps
1. Download Zip from Link above.
2. Open TWRP
3. Open Wipe menu
4. Select format /data
5. Key in "YES" and swipe
6. Return to Home Page of TWRP
7. Choose reboot menu then recovery
8. Recovery should now have access to Internal memory (temp for now)
9. Use abd push to put the zip file downloaded above to internal memory
Code:
adb push %userprofile%\downloads\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip /sdcard/
10. Select install menu , and install the Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip
Do not rename the file. It installs and makes the patch base on the file name.
If you want to have root also, then flash Magisk at this point.
Now the dm-verity and force encryption are off. You can flash gsi custom rom, if you desire. At the moment, I have only been able to boot the phone with working cell data and calls on the PHH-Phusion --vanilla builds. Do not know why the gapps versions do not allow rill to function.
As of the writing of this I have put up V4 of the TWRP port. This version uses the correct mount points for this phone, not the ones from the source of the port. Also corrected the device name in default.prop, to match device name. Build fingerprint has been left as is. Fixed the micro sdcard name and OTG names. Added mipe to the "misc" /"para" partition to escape a factory reset recovery loop that [uu]could[/u] happen under certain situations.
And my prefered ported recovery from LRTeam TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img.
DOWNLOADS
Files
1. Sp Flash tool (v 5.18.28 or newer) https://androidmtk.com/smart-phone-flash-tool
2. stock XL4 ROM, DA file, TWRP all in shared folder https://androidfilehost.com/?w=files&flid=287088
3. stock Xi+ ROM, TWRP in shared folder https://androidfilehost.com/?w=files&flid=287703
4. Unviversal DM-Patch disable tool thread
5. Youtube Guide Video to use backup image splitter tool "WWR_MTK" https://www.youtube.com/watch?v=GMAytZ56hac
Kernel sources have been published 12-12-2018, by BLU
I have them synced to GitHub while I make test builds.
https://github.com/mrmazakblu/BLU-VIVO-XL4-kernel
Default defconfig should be arch/arm64/config/k62mv1_64_bsp_defconfig. Based off of build description in "getprop"
Built kernel has not been able to be booted yet.
TWRP is first ported and provided thanks to @Voinea12
.

placeholder not really welcomed here on XDA
just pm a moderator or report this thread when you`re ready to upload something, until then, thread closed

After seeing that the Blu vivo xl4 requires an "auth file" in order to flash with spflash tool, I asked BLU to supply the file.
They responded with a big fat NO.
.......
.......
THE NEXT DAY THE FILE WAS POSTED ON A DIFFERENT THREAD.
SO THERE HELP WAS NO LONGER NEEDED.

Just made successfull readback on preloader. and currently reading full rom.
will post link when done.
here is auth file and DA file I used.
pulled firmware is here.
there are more images in complete firmware, but the ones included should be enough , as long as you NEVER do format all from spflash tool.
STOCK ROM

So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Working version is available now

Thread was opened.

mrmazak said:
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Click to expand...
Click to collapse
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?

psychofad said:
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
Click to expand...
Click to collapse
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?

mrmazak said:
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
Click to expand...
Click to collapse
No, I got the readback of the EMMC_USER just fine and ran it through the WwR MTK tool and it gave me the hex address to use for the full rom readback, t then told me
Code:
The file size is smaller than the start position of the LK (uboot). To determine the type of processor and memory, it is necessary to read the full firmware in the SP Flash Tool, specify the parameters for reading: Start address: 0x0, Lenght: 0x1D1EC00000.
So I entered those two addresses as EMMC_USER readback. If my phone is off and I just connect it to the usb without holding any keys it gives me another error.....and I'm an idiot. just figured it out as I was looking at logs, apparently I must have changed the usb speed in sp flash which changes it's pid causing it to try and read from another port. It's downloading now

Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ

******EDIT*****
Most of the following problems did not repeat in same way when I tried to repeat the install process.
Main issue was with simcard. But exact process to get installed and working is still not known.
-- install after already having rooted, encryption removed stock, seems to work.
-- fresh full stock rom, full encryption, then gsi seems to not work sim card.
PHH-treble gsi images do boot this device. I do not have a bug list as yet.
working:WITH encryption removed:
1. wifi
2. camera
3. fingerprint- unlock
4. music
5. video
NOT working :WITH encyyption removed:
1. cell signal
2. cell data
3. phone
4. sms
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
working:WITH encryption enabled
1. phone
2. sms
NOT working:WITH encryption enabled
1.. everything else
EDIT
Much of the force closing problems were from a corrupted external sdcard. When I removed the card , the force close messages did not come.
Getting 4G data connection was not stable. after a full reset and rom re-install I was not able to get data connection, and only able to have connection to make calls when set to 3G connection only.
some bugs in vendor I assume will need some help solving this.
EDIT 2
Finally got around to trying again. his time I started with vanilla version of phh-treble gsi.
4G data and sms, calls in out all work. Camera , video both work.
WiFi tethering did not work.
Setup that worked :
force encryption removed with universal dm-verity patcher, ( bothboot.img and vendor partitions both edited).
magisk patched boot

Would this work on Blu Vivo XI since same chipset?

sinkoo1979 said:
Would this work on Blu Vivo XI since same chipset?
Click to expand...
Click to collapse
It should. I have been working with few users with Xi+ it works for them. And another user of Xi provided a twrp port, but no details on if this read-back worked. It must have, I suppose it must have.
Please do try to do the readback for your self, and share the files. will help with twrp if I can

Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.

mrmazak said:
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
Click to expand...
Click to collapse
Can any of this be done without a computer

Decaphyz said:
Can any of this be done without a computer
Click to expand...
Click to collapse
No, you need fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.

mrmazak said:
No, need you fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
Click to expand...
Click to collapse
Oof

mrmazak said:
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
Click to expand...
Click to collapse
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site

IndifferentBear said:
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
Click to expand...
Click to collapse
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition

mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
thanks dude! can you give me the command to run in terminal to do it? ill try that first, then ill try flashing stock recovery!
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
but i was required to wipe the sys, data, cache, and dalvik/art to have a clean install.
---------- Post added at 03:33 AM ---------- Previous post was at 02:47 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
YO! Oaky so basic laly when i flashed that misc recovery IT BOOTED!!!!! thank you soo much dude, your the best!

Ulefone Power 5 twrp + root + project treble

Hello everyone, lets root your ulefone power 5 and if you want: flash another rom. I'm kinda new here so don't mind if I'm telling things in a stupid way.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Ok, first of all, massive shout out to @gamr13 and @Dukino and @CarelMinnaar for providing some of the files.
Original threat: https://forum.xda-developers.com/android/help/ulefone-power-5-twrp-root-t3848501/
Link to the website I copied and translated the guide from: https://www.chinahandys.net/android-9-auf-dem-ulefone-power-5-anleitung/
Code:
If you are using any custom rom on your phone, I strongly
recommend reflashing your whole phone with the original
firmware provided by ulefone. I'll add the link.
I assume you know how to flash, otherwise search on youtube or
request it and I'll add a guide.
Most files you may need and worked in my case:
MediaFire
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
More files in the spoiler below.
Let's begin!
First of all, make sure your phone is recognized by your pc and use a good cable. (the original one broke pretty quickly in my case)
Next, go to system and search for 'build number'.
Tap it untill it says: you are now developer.
Go to developer options and enable: OEM unlocking. Then power your phone off.
Next, download the fastboot and adb zip file I provided. If you already use adb and fastboot, download the recovery zip and you know how it works.
Extract the 'android' folder and put it on the root of your system disk (mostly /C).
Next, go to your command prompt and type: cd \android
Now you start your phone in bootloader. Press and hold volume up and power and let your phone cycle untill you enter bootloader.
Select 'fastboot'.
Plug your phone into your pc and type in the command prompt: fastboot devices
Now you should see the serial number of one device (in my case it was something like ABCD1234567890). If not, install some fastboot drivers and use device manager to select the fastboot driver for your phone.
Then, type: fastboot oem-unlock
Select Yes on your phone and let it reboot.
Re-enter fastboot on your phone.
To be sure: fastboot devices
Flash your recovery using: fastboot flash recovery TWRP_3.2.3_Ulefone_Power_5_AND_5S.img
Then, you need (maybe not but just do it) to reboot straight into bootloader. So press volume up and power untill it shows the bootloader, and then select recovery.
Now your phone may be encrypted or something like that. Select 'Wipe' and accept.
Next, put your gsi (A only, arm64), gapps and/or your decrypt file on your sdcard and flash it!
Known bugs:
- VoLTE - I needed to use a simcard from a different provider to get calling working.
- Hotspot
- Seems sticky to 2.4G?
- MTP not working in recovery
- When waking up your device you may encounter some weird behaviour. Just wait a second and it's gone.
Spoiler: The old guide
Files:
https://mega.nz/#!N2hijYAB!0LLshTYgW...SUfOKpV5BELo4A (seems to be down and dated)
or
http://www.mediafire.com/folder/55lxwzgdd938t/ulefone_power_5
or
https://drive.google.com/drive/folders/1totRbNzS1RBeSO66WW2O0hG2kPGbGERl?usp=sharing
So, the method.
1.) In the files above you will find a file ulefone power 5 twrp root. Extract it and find the map called SP_Flash_Tool. Open this and run the flash_tool.exe. Please download the firmware.zip and the flashtool.zip and extract them. Put the decrypt.zip on your sdcard. (in some cases you need also the 'MT65xx_USB_VCOM_DRIVERS.zip' to install properly)
2.) Once opened the flashtool.exe, go into the options menu, click the connection tag and make sure USB is selected. make sure its set to Full speed and auto detect.
3.) Browse through the map sp flashtool and use the MTK_AllInOne_DA.bin file as the DA file (may be selected by default).
4.) Select the scatter file found in the firmware folder with all the .img files. Its called: MT6763_Android_scatter.txt
5.) While unplugged, hold the volume up and power button to load the phone into it's bootloader mode.
(if your phone is bricked in any screen skip this step) Turn your phone totally off.
6.) Set the SP flash tool to download only and press the download button to start the download.
7.) Plug your phone in and as expected, nothing will happen.
8.) Now, hold the volume up and power button continuously. Keep holding it until the SP Flash tool starts start downloading and the bottom bar loads things. Be sure you immediately loose the buttons, otherwise it soft-bricks itself so you have to start the download again.
9.) Be patient and wait until you get the green check mark, then unplug your phone.
10.) Boot directly back into bootloader. (vol. up and power, hold it untill you get the fastboot screen. Sometimes it takes up to 4 reboots), select and boot recovery.
11.) Now it's all for you! Put something on your sdcard and flash it. Mine seems to be broken so I used an usb stick, wich is working fine. MTP is not working in the recovery.
12.) CarelMinnaar published the new decrypt file, wich I thrust more than the previous russian one. Put it on your sdcard, do a full wipe and install. This should ban the forced encryption.
12.)
A.) For root: flash the magisk .zip file from the files above or search on the internet for the right one.
Thanks to @gamr13
1. Reboot to TWRP
2. MAKE A FULL BACKUP (every partition checked)
3. Mount System and Vendor
4. Go back to the main screen
5. Advanced > File Manager
6. Go to Vendor
7. Go to the "lib" folder
8. tap libdirect-coredump.so and Copy File
9. Go to /system/lib
10. paste the file in here
11. Go to /vendor/lib64
12. Copy libdirect-coredump.so
13. Paste in /system/lib64
14. Install Magisk
15. Reboot
16. Go to Magisk > Download > Search for "SafetyPatch" by hackintosh5
17. Reboot and enjoy
Click to expand...
Click to collapse
B.) 1. For another rom: search overhere for a system.img Download the A only variant. I'll keep you updated below. I am not using this phone frequently anymore, so updates may come later. @gamr13 will keep you updated
2. Wipe cache, dalvik cache, data and System.
3. Select flash .img and flash the .img at your System.
4. Flash magisk or other mods.
5. There may be some bugs. Sms was not working on the phh treble for me. The launcher crashed also.
13.) Boot up
14.) Enjoy! Feel free to ask anything.
Got some pm's asking what to do if stuck on boot/recovery, this video explains the return to stock process. In short: start spflashtool, select the scatter file in the stock firmware, select download only, firmware upgrade or download and format. Plug your cable in. Then click start, and press vol. up and power until you hear the 'new device found' sound on your pc and let it go. Then just reboot.
Feel free to use his files or mine. Doesn't really matter.

Working gsi images
These gsi images are tested on this phone:
Android 8.1
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
bugs: sometimes the screen flickers when powering on. (once or twice per month)
Android 9
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
bugs: a bit laggy. It takes up to 30 seconds to wake up from just screen off. Maybe a bug with the sleep state. When you use your phone frequently you don't suffer from this.
Thanks to @gamr13 :
Alright boys, yet another stride made today.
I've done some extensive testing on some Generic System Images for the Ulefone Power 5. This GSI seems to be the most stable I've used so far and best of all, it has root built-in (of course, it's LineageOS).
This is the only one I've gotten to work with ViPER4Android and root. Quick note that this still does have the screen flicker on the lock screen, but it's not as bad in this ROM compared to others I've tried.
Android Q GSIs currently do not work on the Ulefone Power 5, I've tried and fought hard with 'em but nothing. So, Pie it is for now.
Note: Magisk DOES NOT work. Please do not flash it on this ROM or you will break root access and need to reflash the system image.
First things first:
https://sourceforge.net/projects/andyyan-gsi/files/
1) Download the A-ONLY ROM.(avN): https://sourceforge.net/projects/an...309-UNOFFICIAL-treble_arm_avN.img.xz/download
2) Make a backup of your stock ROM as it is, just in case in TWRP.
3) WIPE System, Data, Cache and Dalvic in the Advanced Wipe section of TWRP.
4) Flash the image as a System Image in TWRP.
5) Flash Open Gapps
7) Reboot into ROM
8) Enable Developer Options and enable root for apps and adb
9) Download ViPER4Android 2.5.0.4 (This is critical as the newest release will not work)
10) Install the driver
11) On every reboot you will have to go into V4A and go to Settings > Turn on developer mode > Disable SELinux
12) Enjoy Android Pie with ViPER4Android on your Ulefone Power 5.
Click to expand...
Click to collapse
Android 11
Havoc os
[11][OFFICIAL] Havoc-OS 4.1 [ARM64/ARM/A64][A/AB/AB-VNDKLITE][GApps/Vanilla]
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy... General...
forum.xda-developers.com
Not the quickest, but looks nice with the pixel inspired interface. No extra bugs found.

Handy thread!
I can’t get Magisk working though on any GSIs. I don’t ever get a prompt to allow root access to an app or even with it set to automatically grant, nothing happens and apps don’t detect it, yet, Magisk is installed and Magisk Modules install and work no problem.
Weird issue.

oes20 said:
These gsi images are tested on this phone:
Android 8.1
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
bugs: sometimes the screen flickers when powering on. (once or twice per month)
Android 9
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
bugs: a bit laggy. It takes up to 30 seconds to wake up from just screen off. Maybe a bug with the sleep state. When you use your phone frequently you don't suffer from this.
Click to expand...
Click to collapse
Does Magisk work for you on these GSIs?

gamr13 said:
Does Magisk work for you on these GSIs?
Click to expand...
Click to collapse
It works on (i guess) the android 8 gsi. I do not recommend magisk, as it messes with your /vendor partition. That partition can not be factory reset other than re-flashing the whole recovery/system/vendor/radio etc. Magisk is also not optimized for this device. Tweaks like viper4androidfx won't work. I don't use my phone anymore at this moment, so any tips, tricks or new information is always welcome to ensure that everybody can get the same good experience

oes20 said:
It works on (i guess) the android 8 gsi. I do not recommend magisk, as it messes with your /vendor partition. That partition can not be factory reset other than re-flashing the whole recovery/system/vendor/radio etc. Magisk is also not optimized for this device. Tweaks like viper4androidfx won't work. I don't use my phone anymore at this moment, so any tips, tricks or new information is always welcome to ensure that everybody can get the same good experience
Click to expand...
Click to collapse
That reply gave me serious doubt that you know a single thing about what you're doing. If it touches /vendor, you flash stock vendor.img in fastboot mode, ez pz. Not that it matters at all since nothing will get messed up at all. Magisk works perfectly fine on stock ROM. V4A works on stock, but when I use any GSI then no apps that require root work at all.

gamr13 said:
Handy thread!
I can’t get Magisk working though on any GSIs. I don’t ever get a prompt to allow root access to an app or even with it set to automatically grant, nothing happens and apps don’t detect it, yet, Magisk is installed and Magisk Modules install and work no problem.
Weird issue.
Click to expand...
Click to collapse
It is a problem, I know. We can't do anything than reporting these problems to the Magisk team and hope for help. In my case, Magisk worked for root, but not for the modules. I got also knocked out of Snapchat because of Magisk. Just one of those little things that are part of our development hobby

gamr13 said:
That reply gave me serious doubt that you know a single thing about what you're doing. If it touches /vendor, you flash stock vendor.img in fastboot mode, ez pz. Not that it matters at all since nothing will get messed up at all. Magisk works perfectly fine on stock ROM. V4A works on stock, but when I use any GSI then no apps that require root work at all.
Click to expand...
Click to collapse
In my case I got root acces working in Magisk. I apologize for that part about the vendor. You are right about that. I am trying my best to share my experience. I am no expert in anything.

Alright boys, yet another stride made today.
I've done some extensive testing on some Generic System Images for the Ulefone Power 5. This GSI seems to be the most stable I've used so far and best of all, it has root built-in (of course, it's LineageOS).
This is the only one I've gotten to work with ViPER4Android and root. Quick note that this still does have the screen flicker on the lock screen, but it's not as bad in this ROM compared to others I've tried.
Android Q GSIs currently do not work on the Ulefone Power 5, I've tried and fought hard with 'em but nothing. So, Pie it is for now.
Note: Magisk DOES NOT work. Please do not flash it on this ROM or you will break root access and need to reflash the system image.
First things first:
https://sourceforge.net/projects/andyyan-gsi/files/
1) Download the A-ONLY ROM.(avN): https://sourceforge.net/projects/an...7-UNOFFICIAL-treble_arm64_avN.img.xz/download
2) Make a backup of your stock ROM as it is, just in case in TWRP.
3) WIPE System, Data, Cache and Dalvic in the Advanced Wipe section of TWRP.
4) Flash the image as a System Image in TWRP.
5) Flash Open Gapps
7) Reboot into ROM
8) Enable Developer Options and enable root for apps and adb
9) Download ViPER4Android 2.5.0.4 (This is critical as the newest release will not work)
10) Install the driver
11) On every reboot you will have to go into V4A and go to Settings > Turn on developer mode > Disable SELinux
12) Enjoy Android Pie with ViPER4Android on your Ulefone Power 5.

Android 10 and TWRP...
Me. I tested 10 different roms of Android 10 and none works correctly .. I always stay on the Android logo that lights up in a loop. if you find information and manipulations or roms that work and are stable, send me the link or download. Thank you. And if you also find a new TWRP custom 3.3.0 or 3.3.1, put the download here. Thanks ?

gamr13 said:
Alright boys, yet another stride made today.
I've done some extensive testing on some Generic System Images for the Ulefone Power 5. This GSI seems to be the most stable I've used so far and best of all, it has root built-in (of course, it's LineageOS).
This is the only one I've gotten to work with ViPER4Android and root. Quick note that this still does have the screen flicker on the lock screen, but it's not as bad in this ROM compared to others I've tried.
Android Q GSIs currently do not work on the Ulefone Power 5, I've tried and fought hard with 'em but nothing. So, Pie it is for now.
Note: Magisk DOES NOT work. Please do not flash it on this ROM or you will break root access and need to reflash the system image.
First things first:
https://sourceforge.net/projects/andyyan-gsi/files/
1) Download the A-ONLY ROM.(avN): https://sourceforge.net/projects/an...7-UNOFFICIAL-treble_arm64_avN.img.xz/download
2) Make a backup of your stock ROM as it is, just in case in TWRP.
3) WIPE System, Data, Cache and Dalvic in the Advanced Wipe section of TWRP.
4) Flash the image as a System Image in TWRP.
5) Flash Open Gapps
7) Reboot into ROM
8) Enable Developer Options and enable root for apps and adb
9) Download ViPER4Android 2.5.0.4 (This is critical as the newest release will not work)
10) Install the driver
11) On every reboot you will have to go into V4A and go to Settings > Turn on developer mode > Disable SELinux
12) Enjoy Android Pie with ViPER4Android on your Ulefone Power 5.
Click to expand...
Click to collapse
8 Days later and I can confirm the ROM has been really stable with no issues other than the lock screen flicker which rarely happens, especially compared to other ROMs. Battery life has had a significant increase even when putting the phone under heavy usage (Call of Duty: Mobile and other games). Performance has shown a decent increase compared to the stock ROM. All in all, very impressed with the substantial improvements the GSI has brought over the stock Oreo firmware that came with this phone.

Can not install ANDROID 10 AOSP v201 !
Hello, I tested all versions of Android 10 phhusson and none works ..
phhusson offers to do this manually but I do not understand where to put it and how to run it!
phhusson: "need to manually setprop ro.skia.ignore_swizzle true"
If you have a solution to my problem, tell me here because I'm tired of Android 9 .. I'd like to upgrade to the latest version and not bother with this Android 9 .. Thanks ​

Android 10 GSIs currently do not work with the Ulefone Power 5.

gamr13 said:
8 Days later and I can confirm the ROM has been really stable with no issues other than the lock screen flicker which rarely happens, especially compared to other ROMs. Battery life has had a significant increase even when putting the phone under heavy usage (Call of Duty: Mobile and other games). Performance has shown a decent increase compared to the stock ROM. All in all, very impressed with the substantial improvements the GSI has brought over the stock Oreo firmware that came with this phone.
Click to expand...
Click to collapse
Tried to install the .xz gsi-image in TWRP but that doesn't work. Can anybody tell me how to install this image, because in TWRP you can only choose between .zip and .img install. Thanks in advance!

fernseher said:
Tried to install the .xz gsi-image in TWRP but that doesn't work. Can anybody tell me how to install this image, because in TWRP you can only choose between .zip and .img install. Thanks in advance!
Click to expand...
Click to collapse
You have to extract the file and then you will have an .img
Extract it with Winrar or 7ZIP

PetroChina said:
You have to extract the file and then you will have an .img
Extract it with Winrar or 7ZIP
Click to expand...
Click to collapse
This!

A guy was able to install Android 10 with another TWRP
I will soon receive the recovery on Facebook,
I am impatient for me and for all of you who tries to
install Android 10 without success, I hope to have it this week!
I'll let you know about Ulefone Power_5's friends <3
https://1drv.ms/u/s!AidaoCKFpLudgeJAwtAZTJlaLIV2EQ?e=6N3RaD​

PetroChina said:
I will soon receive the recovery on Facebook,
I am impatient for me and for all of you who tries to
install Android 10 without success, I hope to have it this week!
I'll let you know about Ulefone Power_5's friends <3
https://1drv.ms/u/s!AidaoCKFpLudgeJAwtAZTJlaLIV2EQ?e=6N3RaD​
Click to expand...
Click to collapse
Great! Let us know what bugs it has (if any) and especially for TWRP if it has the screen flicker!

gamr13 said:
Great! Let us know what bugs it has (if any) and especially for TWRP if it has the screen flicker!
Click to expand...
Click to collapse
I will tell you everything, I must first test it personally and after the upload on Mediafire.
In my opinion, I hope that the scienceillements of the TWRP will not be there ​

I have the files but I can not install it because it did not explain very well the steps ..
http://www.mediafire.com/file/eqzhwznxxr9qlsf/TWRP_3.3.1_UlefoneP5.img/file
http://www.mediafire.com/file/1sf9mi9qlcv5ari/no_encryption_mod.zip/file
He told me this and I do not understand much and it is not clear enough... : no encryption mod first before install latest twrp if your phone doesnt boot from old twrp to twrp 3.3.1​

How To Guide [GUIDE][UNLOCK][ROOT] How to unlock bootloader, flash ArrowOS v11.0 ROM and root Xiaomi Poco X3 Pro

If you've recently purchased a Xiaomi Poco X3 Pro, but were on the fence about using it until an AOSP ROM became available then you're in luck. Kudos to @kubersharma for his contribution by providing us the first official AOSP release, ArrowOS v11.0 [vayu].
Now, throughout this guide, I have linked the page or post based on information I gathered to put this guide together in order to credit that person instead of having to name drop them individually. These are fully detailed instructions to make it easier for newbs.
I've spent the better part of my day figuring all of this stuff out so hopefully you won't go through the trouble I did. PLEASE DO NOT PM ME FOR HELP. REPLY TO THIS GUIDE BELOW, THANKS. NOW LET'S BEGIN!!!
UNLOCK BOOTLOADER
1. Unlock the bootloader with Xiaomi Unlocker tool.
a. Be aware this process will factory reset the device before proceeding.
b. Download the Mi Unlock app onto your PC. Extract the contents within the zip file into an empty folder then run the app.
c. Register for Xiaomi account and sign in with your Mi Account.
d. Your Mi Account must be added to your Mi Settings
Sign into your Mi Account on the device.
Go to Settings –> About Phone –> tap on MIUI version (For POCO) until it says Developer options is enabled.
Back out of About Phone, Additional Settings –> Developer options –> Mi Unlock status.
Agree, then "Add account and device".
e. Shut down your phone manually, and hold Vol down + Power button to enter Fastboot mode.
Download and install the latest Xiaomi USB Drivers or here (or Google's latest USB drivers for Windows if all else fails) for your PC.
Connect the device to the computer via USB cable, and confirm that your phone shows up recognized as "Android Bootloader Interface" (in Device Manager), and click "Unlock" in the Unlock app.
NOTE: If Windows does not recognize the device due to it automatically installing the wrong "Kedacom Device Driver" then you will have to manually install the drivers for "Android ADB Interface/Android Bootloader Interface".
f. After your first initial unlock attempt, you MUST wait 168 hours before unlock process can fully complete.
Wiping the device or removing the Mi account from the device could result in the timer being reset.
g. After the waiting period expires, click "Unlock" in the Unlock app. You will notice the phone will restart followed by subsequent different screens during the phone's boot sequence including the "POCO" screen which now displays an "open lock icon" at the top, indicating your bootloader unlock attempt and will eventually end up on a "This device is locked" screen where you have to confirm you are the device owner by entering your Mi Account password to "activate this device"; connect to your WiFi prior to doing so if the device lacks an active sim card.
FLASH CUSTOM RECOVERY, DECRYPTION DISABLER, & ROM THEN ROOT
2. Download the Official ArrowOS v11.0-vayu fastboot ROM for POCO X3 Pro [direct link here].
a. NOTE: ArrowOS requires MIUI V12.0.4.0 firmware so it recommended to downgrade to this version before flashing ArrowOS otherwise the ROM may not boot.
b. Choose the GApps build type which "includes Play services and now some AOSP apps have been replaced with GApps... All GApps packages and other[sic] files [were] extracted from original firmware images for Pixel4XL (coral)."
3. [OPTIONAL] Download the latest version of Encryption Disabler then copy it along with the fastboot ROM into a folder named 'TWRP' on the root of your microSD.
4. Ensure USB Debugging is already enabled on your device (in Settings –> Additional Settings –> Developer options).
5. Remove any screen unlock (i.e., fingerprint, PIN, pattern or password) in MIUI.
6. Power off device and put it in Fastboot mode (Vol down + Power button).
7. Download the latest SDK Platform Tools from Google for adb compatibility and create a folder called "adb" in the root of the "C:\" drive.
a. Extract the files adb, AdbWinApi.dll, AdbWinUsbApi.dll, and fastboot into the folder.
b. Ensure the latest USB drivers are installed for your PC, connect the device to the computer via USB cable, and confirm that your phone shows up recognized as "Android Bootloader Interface".
c. Launch "Command Prompt" on your PC and run the command:
cd C:/adb
To show a list of devices (including your phone) connected to your PC, enter the command:
fastboot devices
8. Download the unofficial Pbrb (test3) recovery file (PitchBlack Recovery Project 3.1.0 unofficial) by Alex Besida and copy it into the ADB install folder and rename it to "recovery.img".
9. Flash custom recovery file in CMD, run commands:
fastboot flash recovery "recovery.img"
fastboot boot recovery.img
10. Your device should automatically boot into custom recovery. At this point, the microSD will become accessible from recovery or the PC, but the device's internal storage will not be which makes using a microSD card much more imperative for this process since the recovery is in early access development.
a. Go to Wipe –> Format Data, type "yes" to perform data wipe; Back out to the main menu.
b. Go to Install –> Navigate to the TWRP folder on the microSD (via "external_sd").
Select "Arrow-v11.0-vayu-OFFICIAL-20210424-GAPPS.zip" and flash the ROM, but do not change any of the checkboxes that show up before doing so.
Format data (not wipe) before rebooting into the new ROM.
NOTE: At most it takes around 1 minute to boot back up.
11. [OPTIONAL] Power off the device and boot back into recovery.
a. Go to Install –> Navigate to the TWRP folder on the microSD.
Select " Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip" and flash it, but do not change any of the checkboxes that show up before doing so.
NOTE: This will disable forced encryption of data partition for better performance and internal SD + Data mounting in TWRP. It's not needed for the ROM to work, but due to disabling encryption it compromises security.
Reboot into the new ROM.
12. After going through the phone's boot sequence, you'll be presented with the initial phone setup process onscreen where you can begin recovering your data.
13. Go to Settings –> About phone –>tap on Build number until it says Developer options is enabled.
a. Back out to Settings –> System –> to access Developer options –> Enable USB Debugging.
14. Installing Magisk via custom recovery will fail in the background, resulting in an unresponsive "POCO" screen which is caused by installer scripts not being able to properly detect the correct device info or the recovery environment does not meet its expectation. In this case, you will need to use the Patch Image method as it is guaranteed to work 100% of the time. Installing Magisk through custom recoveries on modern devices is no longer recommended due to this reason.
a. Pull down the Notification Bar from the top of the screen and change "Charging this device via USB" to "File Transfer".
b. Open " Arrow-v11.0-vayu-OFFICIAL-20210424-GAPPS.zip " and copy "boot.img" to the phone's internal storage.
c. Download the latest version of Magisk (Magisk v22.1) and copy it to the phone's internal storage and use the native "Files" app to install the apk.
NOTE: Magisk binaries (ZIP) are now included within Magisk Manager APK file. Now you don’t have to download it separately. You can install the .apk file or rename its extension to .zip then flash it through custom recovery / TWRP.
d. Launch Magisk from the app drawer and go to "Install" under Magisk –> "Select and Patch a File," select the "boot.img" you copied internally –> "LET'S GO".
e. Copy the generated patched file to the ADB folder and flash it via fastboot by running the following commands:
cd C:/adb
fastboot flash boot boot.img
f. Reboot into the new ROM and voila!
fastboot reboot
g. Use an app such as Root Checker or BusyBox Checker (from the Play Store) to confirm root status.
h. To bypass/restore SafetyNet validation, open the Magisk app, go to Settings (cogwheel icon) and enable MagiskHide.

SIDENOTES:
These are either my comments or other user's comments that may be considered helpful as it relates to ArrowOS
Picture guide unlock bootloader, flash custom ROMs & root Xiaomi Poco X3 Pro (Credits to @pl1992aw)
Using TWRP to install OTA Updates
Installing OTA updates
Stability of 'PitchBlack Recovery Project' Recovery
How to verify SafetyNet status
Feel feel to let me know of other threads or comments that are also related to installing ArrowOS.

Excellent guide
My suggestions in terms of improvements:
- 7-day waiting time before unlocking: I would mention that wiping the device or removing the Mi account from the device could result in the timer being reset;
- DFE/Encryption Disabler: it's optional, not needed for the ROM to work and thanks to disabling encryption it compromises security;
- Firmware: Arrow OS requires MIUI V12.0.4.0 firmware, so before flashing Arrow OS it's recommended to downgrade MIUI to this version, otherwise the ROM might not boot
In the future, once more custom ROMs come out, it should be easy to turn this guide into general flashing instructions instead and not just for Arrow OS, which would be a great resource to have here

kamild_ said:
Excellent guide
My suggestions in terms of improvements:
- 7-day waiting time before unlocking: I would mention that wiping the device or removing the Mi account from the device could result in the timer being reset;
- DFE/Encryption Disabler: it's optional, not needed for the ROM to work and thanks to disabling encryption it compromises security;
- Firmware: Arrow OS requires MIUI V12.0.4.0 firmware, so before flashing Arrow OS it's recommended to downgrade MIUI to this version, otherwise the ROM might not boot
In the future, once more custom ROMs come out, it should be easy to turn this guide into general flashing instructions instead and not just for Arrow OS, which would be a great resource to have here
Click to expand...
Click to collapse
Fair enough, thanks for the suggestions. I can add them in.

Thanks for this detailed guide! I'm currently on MIUI 12.0.2 - do you know if I have to update to 12.0.4 first or if I can follow your guide directly?

Aulig said:
Thanks for this detailed guide! I'm currently on MIUI 12.0.2 - do you know if I have to update to 12.0.4 first or if I can follow your guide directly?
Click to expand...
Click to collapse
Yes, you have to update to MIUI 12.0.4.0 before flashing.

How stable is the PBRP Beta? Great Guide btw

DeblaGaming said:
How stable is the PBRP Beta? Great Guide btw
Click to expand...
Click to collapse
More stable than other unofficial custom recoveries such as OrangeFox, especially when it comes to functionality. Based on my experience using OrangeFox, it failed to flash anything that was already present on my microSD, but PBRP worked OOB w/ no issues first time, and allowed me to copy over files onto the microSD while the device was in recovery while simultaneously being connected to my PC. Thanks btw.

AusVGM said:
Yes, you have to update to MIUI 12.0.4.0 before flashing.
Click to expand...
Click to collapse
Thank you, I did that now and then followed the guide (without disabling encryption as that's an important feature to me). Super easy to follow even though I haven't been modding a lot these past years. Worked perfectly, thanks @urbanman2004
Tip: make sure to check safetynet with an app and not magisk, as described in the thread linked regarding magisk hide

Aulig said:
Thank you, I did that now and then followed the guide (without disabling encryption as that's an important feature to me). Super easy to follow even though I haven't been modding a lot these past years. Worked perfectly, thanks @urbanman2004
Tip: make sure to check safetynet with an app and not magisk, as described in the thread linked regarding magisk hide
Click to expand...
Click to collapse
Thanks for the compliment... I didn't feel the need to include how someone could check their device's SafetyNet status, but the app I use is called SafetyNet Helper Sample in the Play Store.

Very detailed instruction thumbs up...
My questions
1. For miui requirement the MIUI V12.0.4.0 , is it free or need specific version like chinese or europe or asia or america for more clearly
2. In future when twrp or custom recovery available , can we just flash the rom via recovery as simple as that. Like other phone

bla.tiga said:
Very detailed instruction thumbs up...
My questions
1. For miui requirement the MIUI V12.0.4.0 , is it free or need specific version like chinese or europe or asia or america for more clearly
2. In future when twrp or custom recovery available , can we just flash the rom via recovery as simple as that. Like other phone
Click to expand...
Click to collapse
Thanks for the compliment. To answer your questions:
1) Any version of MIUI V12.0.4.0 will do.
2) To flash future OTA updates (ROMs), it will require flashing the "compatible recovery" (vayu ArrowOS Recovery) in fastboot mode, rebooting the device then followed by installing the OTA update once it becomes available and letting it flash automatically.

hello all,
I have flashed vanilla version of ArrowOS, and magisk...
could somebody help me with installing microG for VANILLA build ROM? I'm new to microG stuff, so I don't really know from where should I install, what version etc.
some apps are not running as they require Google play services

I have asked this question elsewhere but maybe somebody here has some experience. Is it possible to install ArrowOS OTA with another TWRP than from ArrowOS ?
I'm asking because this AOS TWRP is very limited in functionality.

as400l said:
I have asked this question elsewhere but maybe somebody here has some experience. Is it possible to install ArrowOS OTA with another TWRP than from ArrowOS ?
I'm asking because this AOS TWRP is very limited in functionality.
Click to expand...
Click to collapse
Best that your question be taken up w/ the devs.

as400l said:
I have asked this question elsewhere but maybe somebody here has some experience. Is it possible to install ArrowOS OTA with another TWRP than from ArrowOS ?
I'm asking because this AOS TWRP is very limited in functionality.
Click to expand...
Click to collapse
So I have some breaking news:
I can confirm that the latest unofficial alpha version of TWRP (TWRP-3.5.1-vayu-Nebrassy-1) is capable of decrypting and reading internal storage. Due to this advancement, I can also confirm that ArrowOS OTA updates will officially work using TWRP. There is NO NEED TO USE ANY OTHER CUSTOM RECOVERY BESIDES TWRP.

Hi everyone, i have one dubt in unlock bootloader process...
When phone wipe /data partition???, after or before wait the time to unlock???

Let's remain on topic and avoid bickering.

My bootloader unlocks in 4 days and I am planning to change the room using your guide. I have a doubt, I am a beginner. can I do step 8 with TWRP instead of Pbrb (test3)? Would the steps be the same with the change?

@newbrn of course. Pitch Black is literally a dark themed TWRP with some tweaks.