[TWRP][FIGO][EMUI-9.x] TWRP 3.5.2 for Huawei P Smart 2018 - Huawei P Smart ROMs, Kernels, Recoveries, & Other

Hi folks
this is TWRP 3.3.1-0 for our beloved Huawei P Smart 2018 based on EMUI 9.x firmware.
Bugs
ADB is "unauthorized".
MTP (it is a common bug, I test Charlotte TWRP on our phone looks like doesn't work even on official version) so use sideload.
Changes
08/10/2019
Initial build.
twrp-3.3.1-0-v1-emui9-figo.img
12/06/2020
Fix rebooting issue.
twrp-3.4.0.0-v1-hi6250-emui9.img
17/05/2021
Fix mostly everything.
twrp-3.5.2-v1-figo-emui9.img
01/06/2021
Bringup EMUI8 support too.
Everything should works as expected.
twrp-3.5.2-v1-figo-emui8.img
https://sourceforge.net/projects/haky86/files/HuaweiPSmart2018/TWRP/twrp-3.5.2-v1-figo-emui8.img/download
XDA:DevDB Information
TWRP Recovery for P Smart 2018, ROM for the Huawei P Smart
Contributors
haky 86
Source Code: https://github.com/hak86/android_device_huawei_figo-twrp
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui-9.x
Based On: LineageOS/AOSP
Version Information
Status: Alpha
Stable Release Date: 2019-10-08
Beta Release Date: 2019-10-08
Created 2019-10-08
Last Updated 2019-10-08

reserved

Internal storage appears as random characters in TWRP and rom, why is that?

Linux Lounge said:
Internal storage appears as random characters in TWRP and rom, why is that?
Click to expand...
Click to collapse
bugy encryption.

12/06/2020
Fix rebooting issue.
twrp-3.4.0-hi6250-emui9.x-haky86.img

haky 86 said:
12/06/2020
Fix rebooting issue.
twrp-3.4.0-hi6250-emui9.x-haky86.img
Click to expand...
Click to collapse
Uuum is it 2020-06-12 or 2020-06-21

Hawaii_Beach said:
Uuum is it 2020-06-12 or 2020-06-21
Click to expand...
Click to collapse
it's june, my fault lol.

@haky 86
Got a problem with my phone hanging on the TWRP startup screen (I was trying to load the latest lineageos and it went tits up!)
error is FAILED (remote: 'partition length get error') when I perform 'fastboot flash recovery'
I also tried 'fastboot flash recovery_ramdisk' and that writes successfully BUT when rebooting still gets stuck on TWRP screen
Any ideas?
Thanks!

punteruk said:
@haky 86
Got a problem with my phone hanging on the TWRP startup screen (I was trying to load the latest lineageos and it went tits up!)
error is FAILED (remote: 'partition length get error') when I perform 'fastboot flash recovery'
I also tried 'fastboot flash recovery_ramdisk' and that writes successfully BUT when rebooting still gets stuck on TWRP screen
Any ideas?
Thanks!
Click to expand...
Click to collapse
did you wipe data with twrp? if yes do a factory reset using stock recovery.

haky 86 said:
did you wipe data with twrp? if yes do a factory reset using stock recovery.
Click to expand...
Click to collapse
yes , looks like I accidentally wiped everything with twrp
I can't get into emui erecovery now for stock recovery....
I can get into 'FASTBOOT&RESCUE MODE' and tried to format cache and userdata in case that helped but this is the error
fastboot format cache
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(it shows Phone unlocked and FRP unlock)
Any more ideas gratefully received thanks!

punteruk said:
@haky 86
Got a problem with my phone hanging on the TWRP startup screen (I was trying to load the latest lineageos and it went tits up!)
error is FAILED (remote: 'partition length get error') when I perform 'fastboot flash recovery'
I also tried 'fastboot flash recovery_ramdisk' and that writes successfully BUT when rebooting still gets stuck on TWRP screen
Any ideas?
Thanks!
Click to expand...
Click to collapse
1: u can break the loop by clicking (volume up + volume down + power button)
ignore the error and select reboot system
2: or u can flash the official emui recovery by (fastboot flash recovery_ramdisk RECOVERY.img)
official recovery for emui 9 : i cant post outside links before 10 posts ...

Sabri.Gharbi said:
1: u can break the loop by clicking (volume up + volume down + power button)
ignore the error and select reboot system
2: or u can flash the official emui recovery by (fastboot flash recovery_ramdisk RECOVERY.img)
official recovery for emui 9 : i cant post outside links before 10 posts ...
Click to expand...
Click to collapse
re 1 tried all sorts of methods including letting the phone battery completely run out.....none work......dunno if it is because I can't actually power off the phone
re 2 I've tried flashing haky's recovery here https://sourceforge.net/projects/figo/files/stock_images/9.1_stock_rec.img/ and that doesn't work either
Edit: I can get the phone to do this but it never goes into erecovery

problem flashing
Hello,
I'm trying to install TWRP, and when I reboot into bootloader, I get this screen (phone is connected to PC with cable, ignore the message):
Then, I try to flash the TWRP image, but I get this error:
Code:
$ fastboot flash recovery twrp-3.4.0.0-v1-hi6250-emui9.img
target reported max download size of 471859200 bytes
sending 'recovery' (13308 KB)...
OKAY [ 0.379s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.385s
Is this because of FRP? I've been searching how to bypass/disable it, but haven't found any working method yet.
What do I need to do?

ilvidel said:
Hello,
I'm trying to install TWRP, and when I reboot into bootloader, I get this screen (phone is connected to PC with cable, ignore the message):
Then, I try to flash the TWRP image, but I get this error:
Code:
$ fastboot flash recovery twrp-3.4.0.0-v1-hi6250-emui9.img
target reported max download size of 471859200 bytes
sending 'recovery' (13308 KB)...
OKAY [ 0.379s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.385s
Is this because of FRP? I've been searching how to bypass/disable it, but haven't found any working method yet.
What do I need to do?
Click to expand...
Click to collapse
unlock your bootloader device first.

Hi I've found a couple of issues with the recovery:
- Backing up the partition "Data (excl storage)" results in a "createTarFork() process ended with ERROR: 255" error
- Updating official FIGO lineage 16 firmware with inbuilt updater from 2020-09-25 to 2020-10-02 made my device not bootable anymore, had to restore it back to EMUI firmware :/ Is it because something with erasing data is broken?
- The "install image" button doesn't allow you to flash recovery_ramdisk, so we can't update TWRP via TWRP.
- In "Wipe" there's three partitions all named "Storage", I'm assuming they have some other real name
Cheers for your work haky it's really appreciated! Without your and I_am_Gelber's endless hours put developing for this phone it would be garbage in my opinion, no one here taking it for granted! Also would it possible for this twrp to become official?
By the way MTP works perfect for me

Hawaii_Beach said:
Hi I've found a couple of issues with the recovery:
- Backing up the partition "Data (excl storage)" results in a "createTarFork() process ended with ERROR: 255" error
- Updating official FIGO lineage 16 firmware with inbuilt updater from 2020-09-25 to 2020-10-02 made my device not bootable anymore, had to restore it back to EMUI firmware :/ Is it because something with erasing data is broken?
- The "install image" button doesn't allow you to flash recovery_ramdisk, so we can't update TWRP via TWRP.
- In "Wipe" there's three partitions all named "Storage", I'm assuming they have some other real name
Cheers for your work haky it's really appreciated! Without your and I_am_Gelber's endless hours put developing for this phone it would be garbage in my opinion, no one here taking it for granted! Also would it possible for this twrp to become official?
By the way MTP works perfect for me
Click to expand...
Click to collapse
I'd but I give my fig-lx1 to nephew temporary

haky 86 said:
Hi folks
this is TWRP 3.3.1-0 for our beloved Huawei P Smart 2018 based on EMUI 9.x firmware.
Bugs
ADB is "unauthorized".
MTP (it is a common bug, I test Charlotte TWRP on our phone looks like doesn't work even on official version) so use sideload.
Changes
08/10/2019
Initial build.
twrp-3.3.1-0-v1-emui9-figo.img
12/06/2020
Fix rebooting issue.
twrp-3.4.0.0-v1-hi6250-emui9.img
Downloads
https://sourceforge.net/projects/huawei-p-smart-2018/files/EMUI-9.x/TWRP/
XDA:DevDB Information
TWRP Recovery for P Smart 2018, ROM for the Huawei P Smart
Contributors
haky 86
Source Code: https://github.com/hak86/android_device_huawei_figo-twrp
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui-9.x
Based On: LineageOS/AOSP
Version Information
Status: Alpha
Stable Release Date: 2019-10-08
Beta Release Date: 2019-10-08
Created 2019-10-08
Last Updated 2019-10-08
Click to expand...
Click to collapse
stock rom also used?

fatih4261 said:
stock rom also used?
Click to expand...
Click to collapse
not really, don't quote the main post thanks.

Hello,
i am currently trying to move from PHHusson's AOSP 8 to lineage 16 on a FIG-LX1, and i need to install TWRP for that.
However the TWRP website does not propose a compatible version for this phone (though the Lineage installation guide seems to imply there should be one), and the links on this post seem dead.
Is it discontinued ?
If not, where can i find a TWRP version compatible with emui 9.X to support LineageOS 16 ROM ?
Thanks in advance,
a potato

SingingPotato said:
Hello,
i am currently trying to move from PHHusson's AOSP 8 to lineage 16 on a FIG-LX1, and i need to install TWRP for that.
However the TWRP website does not propose a compatible version for this phone (though the Lineage installation guide seems to imply there should be one), and the links on this post seem dead.
Is it discontinued ?
If not, where can i find a TWRP version compatible with emui 9.X to support LineageOS 16 ROM ?
Thanks in advance,
a potato
Click to expand...
Click to collapse
Hi,
Sadly I'm in a similar position, but coming from stock. Any TWRP that I have found has brought problems, and the lineage instruction #4 'format data' is where the process fails for me, not to mention getting garbage for a file structure if I ignore it and wipe data instead - lineage does install and boot but with wifi issues for me :-(
I'm guessing that the issue is I'm coming from EMUI 9.1. I haven't tried a roll back to 8 as the device works ok on stock, but only patched to 1 April 2020 - some irony in the patch date!?
Sadly I'd say the device is less well supported on the forums, TWRP, etc than I'd hoped it would be, probably due to the manufacturer removing the bootloader unlock program.
Sorry I can't be more positive.

Related

Redmi 4X: TWRP, LineageOS, Gapps (Cannot update ROM) (nightly) *error*

Hi everyone,
I'm new here though but am a Xiaomi user from the beggining of Xiaomi into devices with Redmi Note 3G Enhanced.
Currently, I own a Redmi 4X and I would like your expert lights please. I've flashed the latest twrp from twrp.me for my santoni device. Then flashed the latest build from LineageOS Official source + Gapps before booting up for first time. Everything was working perfectly until I decided to flash the latest update of LineageOS as I've seen in my updater it was released. So, I downloaded it through the updater and tried to flash it...
I came up with this "Failed to unmount /system (device or resource busy)" after that re-booted to LineageOS and everything was messed up with Google Services & Apps etc. Then I went back to twrp recovery and tried to flash again the rom but I was still getting that message so I understood something am doing wrong. Also santoni has dm-verity enabled which I know something about but just an info. I really wanna stick with LineageOS on my Redmi 4X forever but I'm afraid to flash it again. I've flashed MIUI 10 Beta by fastboot but now I wanna go back to LineageOS forever (addicted).
My only problem is: After successfuly flashing LineageOS and Gapps, I cannot apply (flash) updates to update the ROM to the latest nightly build due to this error above.
Kind regards,
peryson
Try with different recovery. For example with this
Harukey said:
Try with different recovery. For example with this
Click to expand...
Click to collapse
Instead of trying an unofficial recovery, do I have an option to unmount system manually before flashing through Official TWRP?
peryson said:
Instead of trying an unofficial recovery, do I have an option to unmount system manually before flashing through Official TWRP?
Click to expand...
Click to collapse
You can download latest Lineage OS build and dirty flash it (without any wipes) (so you can unmout system parition). And I don't see any issue in using unoffical twrp.
I also have experienced same error once during upgrade "failed to unmount /system"
Eventually I wiped everything and did clean flash from scratch. This is really annoying issue and demonstrates that upgrade system is not 100% reliable for some reason.
I'm not sure however is it Lineage or twrp issue.

[TOOL/UTILITY][TWRP][3.3][RECOVERY] TWRP 3.3.1-0 TeamWin Recovery Project 9/2

[RECOVERY] TWRP 3.3.1-0 - TeamWin Recovery Project
Hello, I am releasing an official version of TWRP I have been working on for the last 6 weeks. If you download the patched fastboot image as described in the device installation page, you can use TWRP to repack the non-fastboot image for a permanent installation. Currently encryption is supported in the fastboot version and the permanently installed version. Thanks for your patience waiting for official support.
I was kindly given the device from Asus, and will not be blind supporting this device.
X01WD Device Config: https://github.com/TeamWin/android_device_asus_X01WD
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://twrp.me
Reserved 1
Reserved 2
Amazing news! I'm expecting to receive my Zenfone 6 30 edition tomorrow, so the timing couldn't be more perfect.
Is it working with LOS 16 encryption?
Yes. I merged in the good work from Peter Cai for wrapped key support. First it will try a non wrapped key. If that fails it will try a wrapped key. I tested both LOS and Omni.
bigbiff said:
Yes. I merged in the good work from Peter Cai for wrapped key support. First it will try a non wrapped key. If that fails it will try a wrapped key. I tested both LOS and Omni.
Click to expand...
Click to collapse
stuck on Trying Decryption for several minutes after fastboot boot twrp-installer-fastboot-3.3.1-0-I01WD.img
I can boot twrp without password and flash persistent version. Maybe it will work then?
Nope. Cannot boot recovery after flashing. Only LOS booting.
Here is my experience:
Lineage for me is really broken, after a while if I reboot my phone I eventually get stuck in a bootloop, I always customise many settings and haven't narrowed done what the issue is. I was hoping this official TWRP would help with this (constantly reinstalling everything was getting really annoying) but it didn't seem to change much.
Flashing the first IMG (the second download) is the IMG file that works otherwise I bootloop. The flash seems to not in into as many mounting errors as the previous mod and flashing lineageos works but only through ADB sideload or you will again bootloop. This is an improvement because before side loading was not possible.
After flashing the twrp installer zip thus successfully passes but never installs correctly and every time I went through an install I would be taken to lineageOS recovery. From here side loading twrp doesn't work but side loading magisk and mindthegapps is fine with no errors that would occur before.
Booting lineage for the first time didn't open the factory wipe error screen as well.
TLDR; TWRP doesn't stick on the phone but I haven't had a reboot leading to an eventual bootloop so far. So far a partial success
Are you on the most recent firmware? Did you install the image in the download link through the fastboot installer version of TWRP through the repack recovery ramdisk option of TWRP?
Grom8 said:
Here is my experience:
Lineage for me is really broken, after a while if I reboot my phone I eventually get stuck in a bootloop, I always customise many settings and haven't narrowed done what the issue is. I was hoping this official TWRP would help with this (constantly reinstalling everything was getting really annoying) but it didn't seem to change much.
Flashing the first IMG (the second download) is the IMG file that works otherwise I bootloop. The flash seems to not in into as many mounting errors as the previous mod and flashing lineageos works but only through ADB sideload or you will again bootloop. This is an improvement because before side loading was not possible.
After flashing the twrp installer zip thus successfully passes but never installs correctly and every time I went through an install I would be taken to lineageOS recovery. From here side loading twrp doesn't work but side loading magisk and mindthegapps is fine with no errors that would occur before.
Booting lineage for the first time didn't open the factory wipe error screen as well.
TLDR; TWRP doesn't stick on the phone but I haven't had a reboot leading to an eventual bootloop so far. So far a partial success
Click to expand...
Click to collapse
no way to decrypt
Hi,
sorry for bothering, I'm on Stock Rom -189 ( Asus ZF6 8/256 ), I tried fastboot boot twrp-installer-fastboot-3.3.1-0-I01WD.img after entering my personal "PATTERN" the TWRP stucks on " Updating partition details... " ... see the image
I can't extract a "recovery log" for the STATE of the system ( no MTP )
digitalpixel
encryption destroyed
Hi,
I tried to boot my Rom but nothing happen ... Stuck on the Zenfone logo .. no OS
Very Sad :crying:
digitalpixel
So i tried to flash the zip:
I am on the latest omnirom 2019-08-31 with unofficial twrp 3.3.1-19 from mauronofrio. I flashed omnirom coming from stock 191 if it matters.
Twrp 3.3.1-19 successfully decrypts.
I flashed twrp-installer-3.3.1-0-I01WD.zip and magisk.zip from twrp 3.3.1-19 > reboot to recovery. Enter decryption pin > trying decryption. Thats where i am stuck after waiting a few minutes.
Forcing a reboot with vol down + power recovery starts again. I can not boot system.
After a few minutes of waiting nothing happens after "using secdis" in the recovery.log.
Rebooting into bootloader and fastbooting twrp 3.3.1-19 and installing it works as does booting to system after.
HELP
Hi,
there is a way to retrive the data partition ?? I have important personal document not BU over there :crying::crying::crying:
digitalpixel
digitalpixel said:
Hi,
there is a way to retrive the data partition ?? I have important personal document not BU over there :crying::crying::crying:
digitalpixel
Click to expand...
Click to collapse
Depending on where in data you file is stored you can try "adb pull /path/to/you/file.txt".
Adb works even while twrp is stuck during decryption.
If that does not work try booting into bootloader > fastboot boot twrp3.3.1-19 image from mauronofrio. In twrp 3.3.1-19 flash the twrp3.3.1-19 installer.zip and magisk.zip. Reboot system. That worked for me on omnirom.
isthisadagger said:
So i tried to flash the zip:
I am on the latest omnirom 2019-08-31 with unofficial twrp 3.3.1-19 from mauronofrio. I flashed omnirom coming from stock 191 if it matters.
Twrp 3.3.1-19 successfully decrypts.
I flashed twrp-installer-3.3.1-0-I01WD.zip and magisk.zip from twrp 3.3.1-19 > reboot to recovery. Enter decryption pin > trying decryption. Thats where i am stuck after waiting a few minutes.
Forcing a reboot with vol down + power recovery starts again. I can not boot system.
After a few minutes of waiting nothing happens after "using secdis" in the recovery.log.
Rebooting into bootloader and fastbooting twrp 3.3.1-19 and installing it works as does booting to system after.
Click to expand...
Click to collapse
Hi isthisadagger,
no way I can't decrypt , I think I LOOSE ALL ...
What happens when you install 3.3.1-19 and
1. Try to boot to system?
2. Boot to recovery and enter you password to decrypt?
isthisadagger said:
What happens when you install 3.3.1-19 and
1. Try to boot to system?
2. Boot to recovery and enter you password to decrypt?
Click to expand...
Click to collapse
I tried like you said, no way to decrypt data partition in TWRP -19 and no way to boot to system
---------- Post added at 07:50 PM ---------- Previous post was at 07:43 PM ----------
isthisadagger said:
What happens when you install 3.3.1-19 and
1. Try to boot to system?
2. Boot to recovery and enter you password to decrypt?
Click to expand...
Click to collapse
I think the custom roms have the ability " I suppose " to restore the Key ... the stock NO
I hope some one didn't mess with "wrappedkey and non-wrappedkey"
digitalpixel
digitalpixel said:
Hi,
I tried to boot my Rom but nothing happen ... Stuck on the Zenfone logo .. no OS
Very Sad :crying:
digitalpixel
Click to expand...
Click to collapse
Re-reading thread
isthisadagger said:
So i tried to flash the zip:
I am on the latest omnirom 2019-08-31 with unofficial twrp 3.3.1-19 from mauronofrio. I flashed omnirom coming from stock 191 if it matters.
Twrp 3.3.1-19 successfully decrypts.
I flashed twrp-installer-3.3.1-0-I01WD.zip and magisk.zip from twrp 3.3.1-19 > reboot to recovery. Enter decryption pin > trying decryption. Thats where i am stuck after waiting a few minutes.
Forcing a reboot with vol down + power recovery starts again. I can not boot system.
After a few minutes of waiting nothing happens after "using secdis" in the recovery.log.
Rebooting into bootloader and fastbooting twrp 3.3.1-19 and installing it works as does booting to system after.
Click to expand...
Click to collapse
What zip are you flashing? I am only supporting flashing the recovery image through the fastboot installer and using TWRP's repacking tools.
digitalpixel said:
I tried like you said, no way to decrypt data partition in TWRP -19 and no way to boot to system
---------- Post added at 07:50 PM ---------- Previous post was at 07:43 PM ----------
I think the custom roms have the ability " I suppose " to restore the Key ... the stock NO
I hope some one didn't mess with "wrappedkey and non-wrappedkey"
digitalpixel
Click to expand...
Click to collapse
TWRP only updates the key in memory and it shouldn't overwrite the local data key. If it's unable to decrypt normally, it will attempt to use a wrapped key in memory.

[Unofficial] [SODP] Lineage 15.1 for Xperia XZ [EOL]

Lineage 15.1 for Xperia XZ
Based on SODP
By Sjll
This is a stable and performance version​
Download Link: AndroidFileHost
Choose the file named "kagura"
OEM download : Link
How to flash:
1. Wipe Data and flash in twrp
2. Flash oem with SW_binaries_for_Xperia_Android_8.1.6.4_r1_v17_tone.zip
3. Boot and Enjoy.
Feature: Performance, Stable, Gcam support.
Gcam recommend: MGC_6.1.009_MI8_A8.1+_V0_2.apk
For dual model
Add this in build.prop
Code:
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,1
Source code: Github
XDA:DevDB Information
Lineage 15.1 for the Sony Xperia XZ
Contributors
Sjll
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Created 2020-03-26
Last Updated 2020-3-26
2. Flash oem in SW
Hello
I am brand new here so I am not sure if I should post a question here or some place else? I started working on installing Lineage OS to my Xperia XZ about 10 days ago with no results. Than I found this thread today after installing Lineage OS on Realme 3 Pro.
Can you explain to me what I am suppose to do here?
2. Flash oem in SW_binaries_for_Xperia_Android_8.1.6.4_r1_v17_tone .zip
Kind Regards
T
toxypoxy said:
Hello
I am brand new here so I am not sure if I should post a question here or some place else? I started working on installing Lineage OS to my Xperia XZ about 10 days ago with no results. Than I found this thread today after installing Lineage OS on Realme 3 Pro.
Can you explain to me what I am suppose to do here?
2. Flash oem in SW_binaries_for_Xperia_Android_8.1.6.4_r1_v17_tone .zip
Kind Regards
T
Click to expand...
Click to collapse
1. Backup all your staff.
2. Unlock Bootloader on Sony Xperia XZ
3. fastboot flash recovery twrp-kagura-oem-to-vendor.img---------> https://sx.ix5.org/files/builds/kagura/misc/twrp-kagura-oem-to-vendor.img ....Use this TWRP , it will solve your " Failed to mount ´/oem´ " problem!
4. fastboot flash oem SW_binaries_for_Xperia_Android_8.1.6.4_r1_v17_tone .img
5. In TWRP --> flash --->zip rom.
6. reboot.
7. Optional (you can install Magisk https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip) to uninstall Magisk --> https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-uninstaller-20200323.zip
İf you have never done such thing before! Research for more info.
Thanks to Sjll.
toxypoxy said:
Hello
I am brand new here so I am not sure if I should post a question here or some place else? I started working on installing Lineage OS to my Xperia XZ about 10 days ago with no results. Than I found this thread today after installing Lineage OS on Realme 3 Pro.
Can you explain to me what I am suppose to do here?
2. Flash oem in SW_binaries_for_Xperia_Android_8.1.6.4_r1_v17_tone .zip
Kind Regards
T
Click to expand...
Click to collapse
elm_bacchus said:
1. Backup all your staff.
2. Unlock Bootloader on Sony Xperia XZ
3. fastboot flash recovery twrp-3.3.1-0-kagura.img
4. fastboot flash oem SW_binaries_for_Xperia_Android_8.1.6.4_r1_v17_tone .zip
5. In TWRP --> flash --->zip rom.
6. reboot.
7. İf you have never done such thing before! Research for more info.
Click to expand...
Click to collapse
Unzip it,you need to flash IMG in this zip file.
Sjll said:
Lineage 15.1 for Xperia XZ
Based on SODP​By Sjll
This is a stable and performance version
Download Link: AndroidFileHost
Choose the file named "kagura"
OEM download : Link
How to flash:
1. Wipe Data and flash in twrp
2. Flash oem with SW_binaries_for_Xperia_Android_8.1.6.4_r1_v17_tone.zip
3. Boot and Enjoy.
Feature: Performance, Stable, Gcam support.
Source code: Github
XDA:DevDB Information
Lineage 15.1 for the Sony Xperia XZ
Contributors
Sjll
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Created 2020-03-26
Last Updated 2020-3-26
Click to expand...
Click to collapse
Good project can you up until lineages 16.0 for XZ?
Do I have to first install Oreo base firmware ROM. Latest .192?
Working on it
Sjll said:
Unzip it,you need to flash IMG in this zip file.
Click to expand...
Click to collapse
Hello and thank you and elm_bacchus for quick reply
So this is the status:
1. Backup all your staff. FINISHED
2. Unlock Bootloader on Sony Xperia XZ FINISHED
3. fastboot flash recovery twrp-3.3.1-0-kagura.img FINISHED
4. fastboot flash oem SW_binaries_for_Xperia_Android_8.1.6.4_r1_v17_tone .zip FINISHED But after I did this I always get this message in TWRP : Failed to mount ´/oem´ (Invalid argument) in red letters. TWRP still continues to work but always this message. :silly:
5. In TWRP --> flash --->zip rom. I am assuming this is the file I should Unzip? And flash IMG in TWRP? or ...
6. reboot. Seen SONY logo enough times for today :laugh:
7. İf you have never done such thing before! Research for more info.
---End Quote---
Unzip it,you need to flash IMG in this zip file
Thanks
T
delete
wich gapps is recomended? or there is a specific one that works?
caqo71 said:
Do I have to first install Oreo base firmware ROM. Latest .192?
Click to expand...
Click to collapse
Yup.
seyrarms said:
Good project can you up until lineages 16.0 for XZ?
Click to expand...
Click to collapse
Need time.
toxypoxy said:
Hello and thank you and elm_bacchus for quick reply
So this is the status:
1. Backup all your staff. FINISHED
2. Unlock Bootloader on Sony Xperia XZ FINISHED
3. fastboot flash recovery twrp-3.3.1-0-kagura.img FINISHED
4. fastboot flash oem SW_binaries_for_Xperia_Android_8.1.6.4_r1_v17_tone .zip FINISHED But after I did this I always get this message in TWRP : Failed to mount ´/oem´ (Invalid argument) in red letters. TWRP still continues to work but always this message. :silly:
5. In TWRP --> flash --->zip rom. I am assuming this is the file I should Unzip? And flash IMG in TWRP? or ...
6. reboot. Seen SONY logo enough times for today :laugh:
7. İf you have never done such thing before! Research for more info.
---End Quote---
Unzip it,you need to flash IMG in this zip file
Thanks
T
Click to expand...
Click to collapse
You need to upgrade to latest Oreo FW, the flash oem.img via fastboot or twrp, format data, flash lineage zip in twrp.
Sjll said:
Yup.
Need time.
You need to upgrade to latest Oreo FW, the flash oem.img via fastboot or twrp, format data, flash lineage zip in twrp.
Click to expand...
Click to collapse
Thanks you my hope
SONY Xperia XZ
Quote:
Originally Posted by Sjll
You need to upgrade to latest Oreo FW, the flash oem.img via fastboot or twrp, format data, flash lineage zip in twrp.[/QUOTE]
Thank you and elm_bacchus again for the help
Well well this all went well, most of my time went in to trying to flash the wrong TWRP for XZ but after that, it worked in my second attempt :good:
After flashing the SW binaries and format data I got this message again in TWRP : Failed to mount ´/oem in red letters. But I just continued flashing the ROM in TWRP and it worked like a charm.
Kind regards
T
@Sjll:
It seems that this build doesn't support ExFat on External SDCards, am I right ?
And:
What TWRP-Version do you recommend ? The lastest offical 3.3.1-0 doesn't mount /data, so every time I enter TWRP I have to format data ...
Thanks for this. I followed the instructions and it worked.
I forgot that my SDcard was encrypted and lost my photos but hey ho.
@Sjll is there a git repository for this ROM ?
2faraway2 said:
@Sjll:
It seems that this build doesn't support ExFat on External SDCards, am I right ?
And:
What TWRP-Version do you recommend ? The lastest offical 3.3.1-0 doesn't mount /data, so every time I enter TWRP I have to format data ...
Click to expand...
Click to collapse
Hello
I used twrp-3.3.1-0-kagura and it worked for me.
Regards
T
How about front camera? Does it work properly?
dawidcx3 said:
How about front camera? Does it work properly?
Click to expand...
Click to collapse
It works for me on the F8331 device.
XZs build (keyaki)?
By chance is there a choice for 15.1 for Keyaki? It is stated to choose Kagura, are there other choices for the XZ variants? Would like to update to 8.1, 9, or 10 binaries and read the build instructions from source for Lineage but am wondering if all I need are the kernel binaries to complie Lineage (15.1, 16, 17, 17.1) for the XZS. There is practically nothing for the XZS and it would be helpful to know how to provide other roms for it as well. Any assistance will be greatly appreciated.
Does anyone know what the latest Android security update supported is on this ROM?
Some bugs
Hello, I've been using as my daily for a week now and I've noticed some bugs
1) the camera works but it's bad not even close to stock. The picture is dark and dim.
2) sometimes the wifi doesn't open or close no matter how much you try only restarting the phone helps.
3)sometimes the phone doesn't charge even when it's showing charging.
I hope these bugs can be solved asap because I love this rom its stable, smooth and fast with good battery life. Thanks.

GUIDE How to Instal GSI ROM- Havoc-OS-v4.X-Official Android 11 On Redmi 8

Here I bring to you the official Havoc-os 4.X ROM Android 11 and fully functional on Redmi 8
The intention of this post is to make a step-by-step tutorial on the installation of this excellent GSI ROM on Redmi 8 and give assistance in the installation process
All the development credits for this wonderful ROM go to the Havoc team
@Ruturaj Kadam
@jhenrique09
@SKULSHADY
Remember I am not a developer, if you are presenting any bugs let us know and you can contact the Havoc team on Telegram
I am not responsible for any damage caused to your device by not following the steps or negligence at the time of this process, All the steps were carried out and tested on my personal device and are confirmed, My device Redmi 8 3/32, the version that i tested Havoc-OS-v4.5-20210208-Official-arm64-ab.img.xz
Bugs
videos recorded with the default camera do not play
Update: Install the NGCam_7.4.104-v1.8-fix.apk Once the application is installed open it take a photo close the application, this will create a folder in the SD called Gcam, inside the Gcam folder create a folder and call it Config7 and inside this place the XML file Redmi 8 GCam 7.4.104.314953318 G_Modder.xml restart the application and you're done
the only bugs that have is slow motion record not work for now
Automatic brightness does not work
Update: to fix the automatic brightness on your device, after installing the ROM, put in the folder SYSTEM-OVERLAY the treble-overlay-xiaomi-redmi 8.apk and set the permission for the apk on 644 ( use root explorer ) and reboot ..... problem solved
the necessary files are at the end of the tutorial
Steps
Note: I did the installation coming from Mui 12.EU, and there was no problem in the installation process or in the boot process
If you come from Miui12 .EU or any other GSI Rom go to step 4, if you come from the Rom stock follow the this steps
1- First make a backup of all the necessary information in case something goes wrong you can easily recover, Charge the battery at least 80%
All your data will be deleted during the process
2- Unlock the Bootloader if you have not already done it or do not know how to, follow this post: http://en.miui.com/unlock/
3- Install a custon recovery, if you dont know how to, follow this post: https://c.mi.com/thread-2850424-1-0.html
4- Make wipe only to Cache, Dalvik, System, Data and Internal SD
5- Format data,( if it doesn't format the data you will have bootloop) then Reboot into Recovery
6- Copy all the files to the phone (Havoc-OS-v4.X-20200522-Official-arm64-ab.img you can find it by unpacking the zip), Magisk,Magisk Path Fix, Permisiver, Certification Patch.zip, opengapp (recommended nano or pico)
7- Install system image to system partition (on TWRP go to install-Install image-System) .
8- Flash Permisiver v5 (on TWRP go to install selec permisver_v5.zip)
9- Resize system partition to flash opengapps (on TWRP go to Wipe-Advanced Wipe-Select System on the list-Repair or Change File System-Resize)
To Root
once you have installed an resized the system
10- Flash the Magisk path fix (on TWRP go to install selec MagiskA11_PATH_fix.zip)
11- Flash Magisk (on TWRP go to install selec Magisk-v23.0.zip)
12- Flash Opengapps
1-Flash Certification Patch
1 - Make a wipe to Cache and Dalvik
1- Reboot
The boot process takes 5 to 10 minutes the first boot, in case of any problem in any of the stages you can reinstall Miui version fastboot with Mi flash tool and start again
Download link Rom image:
arm64-ab • Havoc-OS
Havoc-OS Downloads
download.havoc-os.com
OpenGapss Android 11: https://sourceforge.net/projects/opengapps/files/arm64/test/20210130/
Magisk:
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com
Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer
letouvetpierre said:
Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer
Click to expand...
Click to collapse
Don't mind it, I haven't read all the article....
letouvetpierre said:
Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer
Click to expand...
Click to collapse
You can place it in either of the two, as long as you can access the storage where you placed them from the recovery
D
letouvetpierre said:
Don't mind it, I haven't read all the article....
Click to expand...
Click to collapse
Dont worry
Darth Inferno said:
You can place it in either of the two, as long as you can access the storage where you placed them from the recovery
Click to expand...
Click to collapse
Okay thanks I think I will try this in the few days. Thanks for your guide !
Hey ! Do we need to flash a vbmeta image for Havocon boot ?
Is there any bugs when you install Havoc with TWRP ? 'cuz i'm a little bit experimented with TWRP but i'm shy with GSI...
Thanks for the answer
UPDATE :
I bricked my phone. When i arrived to the step 5 and i rebooted into fastboot (i would reboot into recovery...)
So, what can I do ? I installed MiFlashTool to unbrick my phone, if it can...
I tried to reboot from fastboot to twrp and this is what happened :
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.141s]
booting...
FAILED (remote: unknown reason)
finished. total time: 2.771s
Thanks...
letouvetpierre said:
UPDATE :
I bricked my phone. When i arrived to the step 5 and i rebooted into fastboot (i would reboot into recovery...)
So, what can I do ? I installed MiFlashTool to unbrick my phone, if it can...
I tried to reboot from fastboot to twrp and this is what happened :
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.141s]
booting...
FAILED (remote: unknown reason)
finished. total time: 2.771s
Thanks...
Click to expand...
Click to collapse
Hi, I need to know some things to help you, what ROM did you have before flashing Havoc? do you have the bootloader unlocked? When did you use My flashtool, what method did you use?
letouvetpierre said:
Hey ! Do we need to flash a vbmeta image for Havocon boot ?
Is there any bugs when you install Havoc with TWRP ? 'cuz i'm a little bit experimented with TWRP but i'm shy with GSI...
Thanks for the answer
Click to expand...
Click to collapse
In my particular case it was not necessary to flash vbmmeta as I comment in the OP I come from Miui12.eu, but it is necessary to avoid problems whatever the ROM you have before installing Havoc is to have the latest version of TWRP and have configured a lock pattern security in ROM access and in the flashing process I didn´t have problems
Hey!
I was on the stock ROM when i started to flash HavocOs.
I unbricked my phone with the MIUnlockTool V2 and my phone's still alive.
I booted on TWRP with fastboot boot TWRP.img 'cuz I can't boot to TWRP with volume up and power...
How can I flash HavocOs in the good way ?
I have Redmi 8 3/32 like you...
letouvetpierre said:
Hey!
I was on the stock ROM when i started to flash HavocOs.
I unbricked my phone with the MIUnlockTool V2 and my phone's still alive.
I booted on TWRP with fastboot boot TWRP.img 'cuz I can't boot to TWRP with volume up and power...
How can I flash HavocOs in the good way ?
I have Redmi 8 3/32 like you...
Click to expand...
Click to collapse
Ok the first thing is that you have the bootloader unlocked, if it is that way regardless of the stock version of the rom you have when installing twrp you must install magisk to ensure that the Recovery remains fixed in this link is a tutorial on how to install it, that tutorial was made by me and approved by Xiaomi https://c.mi.com/thread-2850424-1-0.html ,
install the latest version of TWRP and as it says in the tutorial then flash magisk, once you have everything ready install miui 12.eu do not do many settings except create a blocking pattern when starting the rom this is used by TWRP to be able to decrypt the internal memory
All ready do the steps as indicated in this tutorial (If you come from Miui12 .EU or any other GSI Rom go to step 4)
If for some reason you have a problem, use MI flashtool to return to the stock rom, but make sure to use the snapdragon method, select MIflash and when opening the screen at the bottom select clean all, this will prevent you from blocking the bootloader and you can start again without problems (note when selecting clean all at the end it will give you an error for not being able to block the bootloader and the device will restart, do not worry it will restart normally without problems)
Darth Inferno said:
Ok the first thing is that you have the bootloader unlocked, if it is that way regardless of the stock version of the rom you have when installing twrp you must install magisk to ensure that the Recovery remains fixed in this link is a tutorial on how to install it, that tutorial was made by me and approved by Xiaomi https://c.mi.com/thread-2850424-1-0.html ,
install the latest version of TWRP and as it says in the tutorial then flash magisk, once you have everything ready install miui 12.eu do not do many settings except create a blocking pattern when starting the rom this is used by TWRP to be able to decrypt the internal memory
All ready do the steps as indicated in this tutorial (If you come from Miui12 .EU or any other GSI Rom go to step 4)
If for some reason you have a problem, use MI flashtool to return to the stock rom, but make sure to use the snapdragon method, select MIflash and when opening the screen at the bottom select clean all, this will prevent you from blocking the bootloader and you can start again without problems (note when selecting clean all at the end it will give you an error for not being able to block the bootloader and the device will restart, do not worry it will restart normally without problems)
Click to expand...
Click to collapse
Hey!
I thought about something this afternoon : if I flash HavocOS with adb and fastboot, we also haven't any problems with TWRP installation ! But the problem is that I haven't found any wiki to do that and i won't transform my phone to a beta tester....
Thanks a lot for your help but I think i will wait until a custom rom of LineageOs or HavocOs...
Hi . I am currently running havoc is 3.12 on my device I tried multiple times to flash this ROM without any success. Is not installing open gapps a problem ? Anyways when I flash this rom without flashing the certification patch I get a no os installed warning before rebooting from orange fox recovery but when I flash the certification I no longer get this message. Etherway I am getting stuck on a bootloop . How can I solve this issue? I did all the steps correctly wiping the correct partitions and formating data . Edit I wiped cache and dalvik after the bootloop without any success .
Dragonnuu said:
Hi . I am currently running havoc is 3.12 on my device I tried multiple times to flash this ROM without any success. Is not installing open gapps a problem ? Anyways when I flash this rom without flashing the certification patch I get a no os installed warning before rebooting from orange fox recovery but when I flash the certification I no longer get this message. Etherway I am getting stuck on a bootloop . How can I solve this issue? I did all the steps correctly wiping the correct partitions and formating data . Edit I wiped cache and dalvik after the bootloop without any success .
Click to expand...
Click to collapse
Hey !
I had the same bug before installing the v3.12 version.
I think it goes from the Permissiver v5. I think we should flash it to have the Havoc v4.
I'll test later if I have the time to do this and I'll inform you about the possibilities.
Hope I can help.
letouvetpierre said:
Hey !
I had the same bug before installing the v3.12 version.
I think it goes from the Permissiver v5. I think we should flash it to have the Havoc v4.
I'll test later if I have the time to do this and I'll inform you about the possibilities.
Hope I can hel
Click to expand...
Click to collapse
Thanks for replying and trying to help but last night I managed to get havoc 4.1 is installed by flashing lineage first (using another guide from this category). I will try again to get havoc 4.1 working without flashing lineage as soon as posible because I am curious .
Used online available guides bit still not able to install magisk on Hovoc 4.1
Anyone succeeded?
mwaseem851 said:
Used online available guides bit still not able to install magisk on Hovoc 4.1
Anyone succeeded?
Click to expand...
Click to collapse
Magisk doesn't work on Android 11
letouvetpierre said:
Magisk doesn't work on Android 11
Click to expand...
Click to collapse
Finally managed to flash Magisk on Havoc 4.1 with the help of youtuberking (telegram and YouTube).
How: just flash Magisk path fix before magisk and it's good to go.

Question Error in 'failed to check sparse crc')

Hi all
I got a Global version of Note 10 Pro.
I tried to flash a custom rom with custom recovery. I installed Teamwin Recovery and then flashed Arrow OS but it didnt boot. I waited for 30 mins.
Then I wiped everything from Teamwin recovery, copied the rom over again and flashed but now it is showing some mount issue.
I then downloaded the official rom from Xiaomi and tried to flash that from Fastboot but getting Error in 'failed to check sparse crc')
Any idea how to fix this issue?
thanks
you find a way around this?
dying4004 said:
Hi all
I got a Global version of Note 10 Pro.
I tried to flash a custom rom with custom recovery. I installed Teamwin Recovery and then flashed Arrow OS but it didnt boot. I waited for 30 mins.
Then I wiped everything from Teamwin recovery, copied the rom over again and flashed but now it is showing some mount issue.
I then downloaded the official rom from Xiaomi and tried to flash that from Fastboot but getting Error in 'failed to check sparse crc')
Any idea how to fix this issue?
thanks
Click to expand...
Click to collapse
Enddo said:
you find a way around this?
Click to expand...
Click to collapse
Did you've tried
Twrp format data with yes
Flash ROM
Again Twrp format data with yes
Reboot with ignoring shown failures.. Wait until system booted
for future reference, I ended up having to download an older version of the firmware. even redownloading the copy of the MIUI firmware I was trying ( in case of corruption or something) didn't fix the issue
I had to download the previous version of MIUI (to the one I was trying to flash) and then I could update to the latest via the built-in OTA updater
no idea what is causing the check sparse error (both command line and miflashtool were giving)

Categories

Resources