{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lineage-os 18 for Redmi Note 3 pro, ported from Mi Max by @nasim7500
What's working:
----------------
Boot
Bluetooth
Camera / Camcorder
Fingerprint Sensor
FM Radio
GPS
RIL
WiFi
WiFi Hotspot
USB (ADB/MTP)
Video Playback
Touch
Sensors
Bugs:
-------
DT2W (if you need this then install magisk & use any kernel manager app)
Some hidden bug there maybe, not sure
Installation instructions:
---------------------------
Install a compatible Recovery (orangeFox recomended)
Perform a NANDroid backup of your current ROM (Optional)
Wipe system / data / cache partitions
Flash ROM & Gapps then reboot
After boot, again reboot one more time
Optional: Install Magisk for Root.
Special thanks to these guys (For help me)
----------
@MrJarvis698, @trax85, @Jrchintu @Magicxavi
Also This guy for Testting this Rom
-----------------
@JeSsyB007, @H39AR
BUG FIXING FULL CREDIT: OUR GOD (Allah)
NOTE:
We are not responsible for bricked devices, dead sdcard, etc
If you find any other bug you can tell me, I will try to fix but no promises
All mejor bug fixed, now enjoy!!
if you face rendom reboot problem then just format data partition after install this Rom, from twrp thnx to @QantivirusP & @Ardityo
you want selected text feature in normal version? click here
This is my first post in xda so if somthing i wrong then tell me
Still alive poor battery backup then just flash this kernel
chines character kernel have obb bug
SCREENSHOTS:
A11 screen shot - Google Drive
drive.google.com
ROM Download Link:
------------------
lineage-os-18.1_ported_for_kenzo_by-nasim7500 25-8-2021.zip
FlameGApps-11.0-basic-arm64-20210822.zip
[MODED_ROM] lineage-os-18.1_ported_for_kenzo_by-nasim7500 24-8-2021.zip
Changelogs
25/08/2021
Fixed safetynet by default thnx to @Rajat_Prime & @sairam60
Fixed Fingerprint won't wakeup screen
Fixed weak wifi signal
Fixed weak vibration
Fixed poor battery backup again (cause min cpu value set to high) thnx to @trax85
Obb Fixed Big Thnx to @trax85 for compiling new kernel && @alonsoj636 & @Rajat_Prime for give me the Commit file
>>>>> MODE VERSION <<<<<
Gapps included
added selected text feature by default
add Solid explorer to system app thnx to @SkullMax01
1/06/2021
Fixed Camera
Fixed Fingerprint
Fixed FM Radio.
Fixed Heaing Issue
fixed Poor Battery backup
Fixed TWRP Installation error on kenzo device thnx to @nshussain (for findout why this problem)
Rom ported by nasim7500.
Guys if you like my work plz press like button & support to my helper or respect him, thank you..Now Enjoy!!
And Last i Want to say Thank you so much from my heart for All Kenzo dev for your hard & awseome Work...
Nice work bro..
ullas377 said:
Nice work bro..
Click to expand...
Click to collapse
Thank you bro.
nice
I am getting an error:
E1001 failed to update system image.
update process ended with error 1
I tried with the latest TWRP and OrangeFox recovery,
Formated data,
Flash stock boot.img.
Bootloader is unlocked.
Flashed stock Rom using the Mi Flash tool.
Nothing worked.
Other roms like RR and LineageOS 17.1 works fine.
Can anyone please suggest on this? Thanks.
surajbhanmehra68 said:
nice
Click to expand...
Click to collapse
Thanks
surajbhanmehra68 said:
nice
Click to expand...
Click to collapse
Thanks
surajbhanmehra68 said:
nice
Click to expand...
Click to collapse
nshussain said:
I am getting an error:
E1001 failed to update system image.
update process ended with error 1
I tried with the latest TWRP and OrangeFox recovery,
Formated data,
Flash stock boot.img.
Bootloader is unlocked.
Flashed stock Rom using the Mi Flash tool.
Nothing worked.
Other roms like RR and LineageOS 17.1 works fine.
Can anyone please suggest on this? Thanks.
Click to expand...
Click to collapse
1st flash orangefox recovery 2nd boot to orangefox recovery 3rd wipe system,data,catch,vendor 4th format data by type yes from orangefox recovery 5th reboot to recovery 6 try flashing Rom. & Report back here, thank you
nasim7500 said:
1st flash orangefox recovery 2nd boot to orangefox recovery 3rd wipe system,data,catch,vendor 4th format data by type yes from orangefox recovery 5th reboot to recovery 6 try flashing Rom. & Report back here, thank you
Click to expand...
Click to collapse
Thanks but it did not work,
What is your system partition size? mine is 2.5 GB.
I converted system.new.dat.br to img file and the size was 3 GB, maybe that is the issue?
Dnt
nshussain said:
Thanks but it did not work,
What is your system partition size? mine is 2.5 GB.
I converted system.new.dat.br to img file and the size was 3 GB, maybe that is the is
Click to expand...
Click to collapse
nshussain said:
Thanks but it did not work,
What is your system partition size? mine is 2.5 GB.
I converted system.new.dat.br to img file and the size was 3 GB, maybe that is the issue?
Click to expand...
Click to collapse
Don't know but this zip install in my device just fine without any error,,, okay I will update my post letter && fix this issue
I was able to reduce img file size using Ubuntu and flash it. Then resized system partition.
Thank you for Android 11 on Kenzo.
nshussain said:
I was able to reduce img file size using Ubuntu and flash it. Then resized system partition.
Thank you for Android 11 on Kenzo.
Click to expand...
Click to collapse
Could you please tell me that how did you reduced the img size? I'm facing at the same error says
update process ended with error 1.
xykshun said:
Could you please tell me that how did you reduced the img size? I'm facing at the same error says
update process ended with error 1.
Click to expand...
Click to collapse
Install Ubuntu os on a VM, copy img file you converted over there.
On terminal browse to location where you saved img and run commands:
e2fsck -f -y system.img
resize2fs -M system.img
Copy img from Ubuntu to computer and then phone. (I used internet, couldn't understand how to copy directly)
From recovery:
flash system.img to system partition.
Reboot to recovery.
Mount system partition,
Resize system partition.
Install gapps.
Dont forgot to flash boot.img to boot partition as well.
Regards,
removed
nshussain said:
Here is the link for the file I converted.
https://drive.google.com/file/d/1xEwm_cYJvatXSwq0P0WgWL2RhagMJMR-/view?usp=sharing
I think 16 GB Kenzo variant has only 2.5 GB system partition and that's why this issue is coming.
Click to expand...
Click to collapse
Thank you for your detailed instructions. The system.img worked perfectly to boot into the system. LOL
But I can't resize the partition, and I don't know the reason. And obviously it went wrong when I'm trying to flash gapps.
It says that
system available size: 0 KB
/product available size: 0 KB
I know the storage might not be enough, but at least it can't be 0KB.
nshussain said:
I was able to reduce img file size using Ubuntu and flash it. Then resized system partition.
Thank you for Android 11 on Kenzo.
Click to expand...
Click to collapse
your Welcome
nshussain said:
Install Ubuntu os on a VM, copy img file you converted over there.
On terminal browse to location where you saved img and run commands:
e2fsck -f -y system.img
resize2fs -M system.img
Copy img from Ubuntu to computer and then phone. (I used internet, couldn't understand how to copy directly)
From recovery:
flash system.img to system partition.
Reboot to recovery.
Mount system partition,
Resize system partition.
Install gapps.
Dont forgot to flash boot.img to boot partition as well.
Regards,
Click to expand...
Click to collapse
nice job brother
xykshun said:
Thank you for your detailed instructions. The system.img worked perfectly to boot into the system. LOL
But I can't resize the partition, and I don't know the reason. And obviously it went wrong when I'm trying to flash gapps.
It says that
system available size: 0 KB
/product available size: 0 KB
I know the storage might not be enough, but at least it can't be 0KB.
Click to expand...
Click to collapse
Post are updated && issue fixed
Thank you,
for some reason Clash of Clans hangs a lot of times on this Rom, what could be the reason?
Pubg works fine. strange.
Once I flashed this ROM, I launch it into the system, it immediately throws it into Fastboot mode!
At first I tried to flash the latest version with twrp. (I did it all by instrumentation. The effect is the same!)
And then I switched from twrp to ofrp, using the earlier version ofrp. (I did it all by instrumentation. The result is zero!)
My kenzo phone with 2gb RAM.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is only for Honor 8 Pro (DUK)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x.
Intended for usage on stock emui 5.x in combination with unlocked bootloader .
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-duk.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official PHH Superuser Beta 310[/U][/B]
1. download and flash [URL="http://superuser.phh.me/superuser-r310-beta.zip"]official PHH Superuser Beta 310[/URL]
2. install "Phh Superuser" from Google Play
3. Enjoy!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_honor_duk/releases/download/3.1.1-1/twrp-3.1.1-1-duk.img"][U]download twrp-3.1.1-1-duk.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 25. June 2017
Q: which H8 Pro models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
A: Yes you can! (Check FAQ)
Q: Can i install Magisk?
A: No (encrypted /data), Yes (decrypted /data)
Q: Does official SuperSU work?
A: No (encrypted /data), Yes (decrypted /data)
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with fileencryption disabled in fstab
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
XDA:DevDB Information
TWRP, Tool/Utility for the Honor 8 Pro
Contributors
OldDroid, surdu_petru, XePeleato
Source Code: https://github.com/OpenKirin/android_device_honor_duk
Version Information
Status: Beta
Created 2017-06-23
Last Updated 2017-06-25
Reserved
Changelog
Code:
[B]TWRP 3.1.1-1[/B]
* fix twrp on emmc based devices
Man that was fast. Will definitely flash this after I get my H8 Pro.
Sent from my Honor 8 using XDA Labs
Hello,
I tested the package, unfortunately after the flash and first boot impossible to return under android.
If I remember correctly there was a problem of mount point.
To get out I had to flasher the recovery and system partitions of the original rom.
Having to reset my phone I have no log, but if you need anything else do not hesitate.
@ +
Via google translate
blattes86 said:
Hello,
I tested the package, unfortunately after the flash and first boot impossible to return under android.
If I remember correctly there was a problem of mount point.
To get out I had to flasher the recovery and system partitions of the original rom.
Having to reset my phone I have no log, but if you need anything else do not hesitate.
@ +
Via google translate
Click to expand...
Click to collapse
this should work for every h8 pro utilizing emmc storage:
https://drive.google.com/open?id=0BxWP2gF_0Bd_OHBPWDctZmJCanc
It has been tested.
Regards
Can we use Magisk instead? Or the loop issue back in Honor 8 is also here?
OldDroid said:
this should work for every h8 pro utilizing emmc storage:
It has been tested.
Regards
Click to expand...
Click to collapse
I flashed it, it works fine.
Thanks
adriansticoid said:
Can we use Magisk instead? Or the loop issue back in Honor 8 is also here?
Click to expand...
Click to collapse
Magisk 13 works fine.
Just flashed the Magist beta and installed the Magisch Manager 5.
-=MoRpH=- said:
Magisk 13 works fine.
Just flashed the Magist beta and installed the Magisch Manager 5.
Click to expand...
Click to collapse
That's great news. Thanks for confirming. :highfive:
Sent from my Honor 8 using XDA Labs
I flashed emmc version and supersu. For going in twrp I've to clic in the middle of the volume button and the power on.
Interesting, i tried to install it but i'm stuck with installion...i know how to enter fastboot mode with phone plugged to my computer with android sdk on, but the adb files look to be missing when i check with cmd...
Can anyone here give a quick tutorial ? Thanks
New Version (3.1.1-1) available - You can find more infos in OP.
This release fixes partition mounting on emmc 5.1 based devices
Source code is now also up and can be built!
https://github.com/OpenKirin/android_device_honor_duk
Regards
Wow that was faster than I could learn to do it.
Great job. May I ask how you got the important informations to build this?
Did you inject su into the image to gain root and then read all the detailed data through terminal or adb or root file explorer?
Just asking cause i train my brain more and more in my spare time and want to get behind the knowledge base to learn. :good:
First of all thank you for your work, I got the Recovery, root, Magisk, etc. running.
I have 2 Questions:
1. the internal storage when I boot to the recovery looks like enrypted (lots of random named folders). Is it possible to decrypt it for now, since there is currently no custom kernel available?
2. Can I flash the Firmware update to 130b in TWRP? If yes, wich package do I need to choose?
Cheers
Would this work on the Chinese V9 variant?
smouker said:
First of all thank you for your work, I got the Recovery, root, Magisk, etc. running.
I have 2 Questions:
1. the internal storage when I boot to the recovery looks like enrypted (lots of random named folders). Is it possible to decrypt it for now, since there is currently no custom kernel available?
2. Can I flash the Firmware update to 130b in TWRP? If yes, wich package do IP need to choose?
Cheers
Click to expand...
Click to collapse
Format the whole internal storage to remove encryption.
adriansticoid said:
Format the whole internal storage to remove encryption.
Click to expand...
Click to collapse
can I restore Data via TWRP without problems?
adriansticoid said:
Format the whole internal storage to remove encryption.
Click to expand...
Click to collapse
After testing, formatting the whole internal storage does not work.
To restart the partition is new encrypt
smouker said:
can I restore Data via TWRP without problems?
Click to expand...
Click to collapse
Yes it should work. Just make sure that both backup and restore destinations are either both encrypted or both decrypted.
blattes86 said:
After testing, formatting the whole internal storage does not work.
To restart the partition is new encrypt
Click to expand...
Click to collapse
What do you mean to restart the partition is new encrypt?
adriansticoid said:
Yes it should work. Just make sure that both backup and restore destinations are either both encrypted or both decrypted.
What do you mean to restart the partition is new encrypt?
Click to expand...
Click to collapse
sorry for my bad english.
After restart the phone...
TWRP 3.2.1_r12 Moto Z2 Play (albus)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP changelog : Here
Working/Bugs : Need to press power button two times for touch to work
Please do read the installation guide note !
IMPORTANT NOTE :
1. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
2. Encryption is enabled by default
3. If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide :
1. Make sure you have unlocked bootloader
2. Reboot to bootloader
3. fastboot flash recovery twrp-xxxx.img (if you want permanent flash) or
fastboot boot twrp-xxxx.img (if you want temporary boot)
Download Link :Here
Tree : Here
XDA:DevDB Information
TWRP-ALBUS, Tool/Utility for the Moto Z2 Play
Contributors
rahulsnair
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2018-01-03
Last Updated 2018-02-03
I've been using this today to set up my phone fresh. I created a backup, installed stock twrp flashable rom, installed magisk, and magisk module zips all just fine.
Thanks for this.
Trying to set up my new Moto Z2 Play today.
I just unlocked the bootloader, so I'm good there. I wanted to install Magisk and leave it mostly stock. If I was going to just "fastboot boot twrp.img'' (instead of flashing) can I use this TWRP or should I just follow the instructions and use the TWRP version in this other thread?
Is this version more functional?
Would I be able to make a backup if I boot the TWRP instead of flashing?
Can I use the SD Card/internal storage with this version or do I have to still use the OTG cable and a flash drive to hold the DM Verity and Magisk ZIPs?
Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx
JRapsky said:
Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx
Click to expand...
Click to collapse
my experience is, you have to flash TWRP.
I don't think it has the necessary read/write permissions to do a full backup otherwise.
3.1.2_r18 version released. Check download link in OP
hi guys.
I successed to twrp temporary boot.
Successed to full backup (with all check).
Is it safe for permanent flash twrp right now?
p/s: After backup success, I reboot my phone and check TWRP folder but nothing here
so why?
fastboot boot twrp-xxxx.img
freeze at teamwin logo
O flash twrp and its ok
rodacoregio said:
fastboot boot twrp-xxxx.img
freeze at teamwin logo
Click to expand...
Click to collapse
Twrp temporary boot works fine for me.
Some guys said install it can fix your problem.
I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
But Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?
Mark2014 said:
I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?
Click to expand...
Click to collapse
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.
kewlzter said:
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.
Click to expand...
Click to collapse
It show me No command when i reboot to recovery mode by command
adb reboot recovery
was I wrong somethings ?
OS's still boot fine.
Mark2014 said:
It show me No command when i reboot to recovery mode.
was I wrong somethings ?
Click to expand...
Click to collapse
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.
kewlzter said:
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.
Click to expand...
Click to collapse
tks. it works.
I trying format Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM copied in SD card?
Mark2014 said:
tks. it works.
I trying flash Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM in SD card?
Click to expand...
Click to collapse
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.
kewlzter said:
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.
Click to expand...
Click to collapse
Tks. I did a full backup .
tks again.
I will try now.
I make a full backup, so can I restore that backup file after LineageOS?
This works when go command fastboot boot .... ?
I'm having an issue... I've successfully flashed r18, but it cannot seem to mount the data partition. It fails to mount (just hangs for a moment when you check the box next to data), fails to wipe (Could not mount/data and unable to find crypto footer... Failed to mount '/data' (Invalid argument)).
Never mind... I just tried it a 3rd time and it worked. Not sure what's going on there.
**OK** Now, I've flashed the Unofficial LOS and OpenGapps from the thread by OP, following all instructions, and the phone boots to recovery every time I try to boot to system...
Recent success, z2 Play XT1710-06
Just to add to the success stories: A newly-purchased Moto z2 Play, variant XT1710-06 dual SIM, Android 7.1.1, RETLA release channel, build NPSS26.118-19-1-6. My object was to install root only, not (at this time) do any custom ROM flashes.
With this in mind: I used TWRP-3.2.1-0(Albus) after doing the initial bootloader unlock. Quirks noted during install was that I needed to repeat the 'fastboot flash recovery' option 3-4 times to get TWRP to stay put in the 'recovery' partition. Also, as an experiment, I tried renaming the TWRP image to 'recovery.img' (which seems to help).
Once TWRP was in place, I downloaded and installed the most current Magisk (v16). It worked perfectly, the first time, no issues at all (and it even knew to install its management app on its own). Despite my initial leanings, I chose not to try SuperSU due mainly to the developer changes at Chainfire HD (original developer retired, product bought up by some unnamed Chinese group).
Now I get to reinstall all my apps... (sigh). Such is the price of getting the phone we Really Want...
I hope this makes life easier for others.
Keep the peace(es).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DUAL BOOT PATCHER
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary.
Warning: This method requires one time factory reset.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_data-slot.zip file will be created. For example,
Lineage-14.1-oxygen.zip
After patching would create a new
Lineage-14.1-oxygen_data-slot.zip
If you want to root secondary rom, then download Magisk 12.zip given below(Do not use other version, you can update that later from magisk manager app) and patch it like you did with rom
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher.apk from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Secondary: Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
Now Let's Start
1) Boot into recovery
2) Make a backup of /system /data /boot on SD Card (it's important to make it on sd card!)
3) Wipe internal storage (it will erase all of your data including photos, music etc on internal storage. So make sure you moved them or made their backup)
4) Restore your backup and boot to your ROM
5) Install Dual Boot Patcher.
6) Install patched rom as secondary on /system or on /data partition - it's your choice. There is lot of space for 3 roms in /system.
If you want to root secondary ROM and flash patched magiskv12.
7) Select your secondary ROM in ROM list and reboot.
Steps to be followed on Secondary Rom
8) Install Dual Boot Patcher.
9) Install MagiskManager.apk (see attachment)
10) Open Magisk Manager
11) Go to Modules-> press "+" button -> search for Magisk_v15.3.zip -> hold your finger on it -> press "Open". Wait for installation end. Now press close button. Don't restart
12) Open Dual Boot Patcher -> confirm for change current kernel
13) Reboot and voila! You have fully working secondary ROM with Magisk!
FAQ's (FAQ)
Do I need to wipe again for third or next rom?
No, wiping is only required for one time, you can flash as many roms(your device can handle) after that.
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Note:
You must always select 'Data-slots' as installation location for secondary roms on Redmi Note 4x. You can also use 'Extsd-slots' if you want to install on external storage.
If your using MIUI (Multirom, Xiaomi.eu, etc), you may need to enable documents app by going to Settings> Installed Apps before trying to patch any file in DBP.
Don't use official MIUI as primary rom.
If you're not able to boot, your phone vibrates 5 times and then reboot to TWRP after installing secondary rom, it might be that your data partition is encrypted. To fix this follow the instructions below:
First backup all your data including Internal Storage, then boot to TWRP>WIPE>FORMAT DATA then type 'yes' and tap enter. Now reboot and retry DBP.
Source/Credits:
https://dbp.noobdev.io
@chenxiaolong
@bad_request (Thanks for the XDA Post And Guide)
@mario_R (For step by step guide and errors.)
Downloads: https://dbp.noobdev.io/downloads/ and Download latest files
~ Hit Thanks button below if I helped you ~
*Reserved
**Reserved
Already flashed LOS 14.1 and RR as secondary in data slot everything work fine only issue is audio headphone jack not working otherwise cool.
drmuruga said:
Already flashed LOS 14.1 and RR as secondary in data slot everything work fine only issue is audio headphone jack not working otherwise cool.
Click to expand...
Click to collapse
...which is an issue pertaining to the RR custom rom and has nothing to do with this multi boot tool
I just tried last 5 days. When I choose second rom and reboot, it goes into recovery. Can't boot up second rom. Renew primary rom,wipe data and try dbp again and again. But not successed. Now my primary rom is Los 14.1 and trying second rom as miui global dev rom 8.1.11. Please help me.
jbmc83 said:
...which is an issue pertaining to the RR custom rom and has nothing to do with this multi boot tool
Click to expand...
Click to collapse
Yes , this tool working great , my problem is known to roms .
Patch roms and files in data slot not secondary slot in which is only one room can boot as secondary. Data slot for multiple roms flashing. And I never update ramdisk which leads to boot into recovery instead of system .
What's the use of dualboot we have only two ROMs to download.. Lol!
Now we should have at least two stable roms to taste this
nikz106 said:
What's the use of dualboot we have only two ROMs to download.. Lol!
Click to expand...
Click to collapse
not quite correct ^^
we have:
miui stable
miui developer
xiaomi.eu
miui pro
miui globe
lineage os 14.1
resurrection remix
so you could try a total of SEVEN different roms with this tool!
jbmc83 said:
not quite correct ^^
we have:
miui stable
miui developer
xiaomi.eu
miui pro
miui globe
lineage os 14.1
resurrection remix
so you could try a total of SEVEN different roms with this tool!
Click to expand...
Click to collapse
+1 to this.
Mgphyo126 said:
I just tried last 5 days. When I choose second rom and reboot, it goes into recovery. Can't boot up second rom. Renew primary rom,wipe data and try dbp again and again. But not successed. Now my primary rom is Los 14.1 and trying second rom as miui global dev rom 8.1.11. Please help me.
Click to expand...
Click to collapse
Anyone?
mario_R said:
Anyone?
Click to expand...
Click to collapse
Twrp >> wipe >> format data..
And it's ok now. ??
when patching the primary rom (update ramdisk)it reboots to recovery after the vibrations
didn't install any secondery roms -- yet
primary : MIUI globeROM 7.12.21
app version : 9.3.0.r327.gb3914310-snapshot
if it's relevant > i have magisk 15.3 --magisk edits the boot.img > may the issue be related to that ? was i supposed to remove magisk before? magisk in not the problem > i tried with original boot,img with supersu
edit : also i remember formatting the data before flashing this rom .. wil i have to reformat ?! >>>>> seems that miui encrypts the data with every flash !!
edit 2: i skipped ramdisk update for the primary rom and flashed a secondery rom in /system -- so .. is it the format issue ? if i format now will i have to reformat everytime i flash a rom ?? bcoz i clearly remember formatting before installing this primary rom
edit3 : problem solved with formating data again !!
DON'T set lock screen !!
you will end up locked away from your primary rom
----------
in my case the primary was globerom and secondary was lineage os
---------
if you already locked from your rom you can boot twrp and open terminal and write
cd data/system
rm *.key
and reboot
kalawy said:
when patching the primary rom (update ramdisk)it reboots to recovery after the vibrations
didn't install any secondery roms -- yet
primary : MIUI globeROM 7.12.21
app version : 9.3.0.r327.gb3914310-snapshot
if it's relevant > i have magisk 15.3 --magisk edits the boot.img > may the issue be related to that ? was i supposed to remove magisk before? magisk in not the problem > i tried with original boot,img with supersu
edit : also i remember formatting the data before flashing this rom .. wil i have to reformat ?! >>>>> seems that miui encrypts the data with every flash !!
edit 2: i skipped ramdisk update for the primary rom and flashed a secondery rom in /system -- so .. is it the format issue ? if i format now will i have to reformat everytime i flash a rom ?? bcoz i clearly remember formatting before installing this primary rom
edit3 : problem solved with formating data again !!
Click to expand...
Click to collapse
Good that you solved it. But for your knowledge and to any user: updating RAMDISK is not necessary. It's necessary only for "App sharing" feature, but I don't recommend it because it causes sometimes bootloops on secondary ROM. Even even creator of DualBoot patcher said it may be unstable.
Kapil Tapsi said:
If you want to root secondary rom, then download latest magisk and patch it like you did with rom
Click to expand...
Click to collapse
Thanks for mention me in your thread, but remove that line, it will cause bootloop. First you need to patch Magisk_v12.zip and install it, then install latest Magisk_v15.3.zip as a module in MagiskManager. Like I wrote in my guide
mario_R said:
Good that you solved it. But for your knowledge and to any user: updating RAMDISK is not necessary. It's necessary only for "App sharing" feature, but I don't recommend it because it causes sometimes bootloops on secondary ROM. Even even creator of DualBoot patcher said it may be unstable.
Click to expand...
Click to collapse
I figured that out ... the hard way :crying:
mario_R said:
Good that you solved it. But for your knowledge and to any user: updating RAMDISK is not necessary. It's necessary only for "App sharing" feature, but I don't recommend it because it causes sometimes bootloops on secondary ROM. Even even creator of DualBoot patcher said it may be unstable.
Thanks for mention me in your thread, but remove that line, it will cause bootloop. First you need to patch Magisk_v12.zip and install it, then install latest Magisk_v15.3.zip as a module in MagiskManager. Like I wrote in my guide
Click to expand...
Click to collapse
Thanks mario_R for the guide and trick. I did it hassle free as I already had my internal decrypted. But I noticed some people having problem with installation.
it worked and the 2nd rom booted correctly then i added magisk 15.3 and set kernel .. the next boot the phone boots to the primary rom and stuck at bootanimation
when checking from recovery it appears that data partition cant be read and twrp asks for password
i managed to format and restore a backup
but what exactly caused this ??
app share have a high chance of breaking secondery rom
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE: Decrypting data is not currently working. This is my initial release and i'm planning to fix as many bugs i can. When it's stable enough , only then i will push to official
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
/*
* I am not responsible for bricked devices,
* thermonuclear war, or your 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.
*/
Sources: https://github.com/TeamWin
Device tree: https://github.com/Suicide-Squirrel/android_device_huawei_charlotte
Download
Flashing:
Code:
fastboot flash recovery_ramdisk recovery.img
Special thanks to @Dees_Troy for the Huawei Blanc device tree, which this is based on.
XDA:DevDB Information
[RECOVERY][UNOFFICIAL]TWRP:Team Win Recovery Project[P20 PRO], ROM for the Huawei P20 Pro
Contributors
kessaras, steadfasterX
ROM OS Version: 9.x Pie
ROM Firmware Required: v195 or newer
Based On: OMNIROM,TWRP
Version Information
Status: Beta
Created 2019-06-14
Last Updated 2019-06-14
I will use this post to share my work
Sorry for making another TWRP thread, but i've had enough with our current TWRP.
I have enabled logcat and strace.
This is the initial release so keep in mind that it has (probably) currently the same bugs with the official.
The only difference is that you can grab any kind of log and help me improve it and only when it will be stable enough , only then, i will push to the official.
------------------------------------------------------------------------------------------------------
VERSION: recovery-3.3.1-0-b.img | date: 15-06-2019
FIXED:
1. mounts correctly all partitions
2. backup to usb-otg enabled
3. backup all partitions except data (i need to fix decryption)
4. restore fixed.
5. ADB sideload fixed.
6. you can flash a kernel and a recovery .img directly inside TWRP. No more rebooting to bootloader.
NOT TESTED:
1. I don't know about format yet. i haven't tested it because im not ready to format yet.
If anyone is about to format anyway, please after format do:
Code:
adb pull /tmp/recovery.log
and
Code:
adb logcat -b all > logcat.txt
And send me these two logs so that i can fix format and we don't need stock Huawei recovery anymore.
2. Can't flash GAPPS exactly like in the official.
VERSION: recovery-3.3.1-0-c.img | date: 17-06-2019
FIXED:
1. GAPPS flashing fixed. Same goes for any other flashable package.
2. backup data and wipe data are fixed. (not tested restore yet)
NOT FIXED:
1. Even if wipe data and backup data are fixed, and even though we can restore data ! Sadly there are bugs when we wipe data or perform a restore. Until i fix (if i fix it) decryption, please keep using the stock Huawei recovery to format your data and avoid restoring data.
ISSUE: Data partition is fine and it sais that it's 128gb but apps think that we don't have enough "free space". It may just be an issue in vold too in the rom where i tested it.
VERSION: recovery-3.3.1-0-d + e.img | date: 20-06-2019
FIXED:
- minor bug fixes for stability
- added nvme partition which is needed during the decryption
- adb sideload fixed. No need to push and install
NOT FIXED:
- decryption
- format
It's great news man. Looking forward to your further progress! Fully functional twrp is the juice.
Amazing, hope we can have finally fully functional twrp
Thanks
aoryx said:
Amazing, hope we can have finally fully functional twrp
Thanks
Click to expand...
Click to collapse
adb sideload and gapps flashing are fine too.
Format data needs to be fixed and decryption
Legend.
Need to update my ROM, will test this tomorrow. Won't be formatting I hope, but if I do I'll be sure to grab logs..
dladz said:
Need to update my ROM, will test this tomorrow. Won't be formatting I hope, but if I do I'll be sure to grab logs..
Click to expand...
Click to collapse
not yet. gimme some hours. im trying to fix something and then ill share a new build.
i have 2 errors left:
1. linker: Warning: couldn't read "/system/etc/ld.config.txt" for "/sbin/sh" (using default configuration instead): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered
That problem is in bionic.
in bionic/linker/tests/linker_config_test.cpp or in
bionic/linker/ld.config.format.md. But i can't figure it out yet. That will fix the gapps flashing issue with latest TWRP and mine.
What's strange is that it doesn't happen to everyone. So i'm confused.
Me i can't flash any gapps, when others reported to me that they can.
Click to expand...
Click to collapse
We can finally backup data partition. And we can use MTP. And we can restore data. And everything is ok, BUT
i still can't decrypt the internal storage. it's a work in progress.
Click to expand...
Click to collapse
At least wait for 1. otherwise you may need 3.2 official TWRP to flash gapps and it's boring to flash other TWRP every time.
@kessaras
On my P20 Pro i dont have "/system/etc/ld.config.txt" but i have "/system/etc/ld.config.28.txt"
titi66200 said:
@kessaras
On my P20 Pro i dont have "/system/etc/ld.config.txt" but i have "/system/etc/ld.config.28.txt"
Click to expand...
Click to collapse
and mine has no ld.config at all. its beautiful , just beautiful.....
just use it then. if it can flash anything for you, then use it.
ill upload another one now that can also backup data.
For those who cant flash gapps just use twrp 3.2 official.
problem is symlink : system/etc to /etc.
@steadfasterX will help me with that.
EDIT:
VERSION: recovery-3.3.1-0-c.img | date: 17-06-2019
i found a temporary fix until @steadfasterX helps me out. its ok for flashing. system backup is not ok.
kessaras said:
and mine has no ld.config at all. its beautiful , just beautiful.....
just use it then. if it can flash anything for you, then use it.
ill upload another one now that can also backup data.
For those who cant flash gapps just use twrp 3.2 official.
problem is symlink : system/etc to /etc.
@steadfasterX will help me with that.
EDIT:
VERSION: recovery-3.3.1-0-c.img | date: 17-06-2019
i found a temporary fix until @steadfasterX helps me out. its ok for flashing. system backup is not ok.
Click to expand...
Click to collapse
stop working in RL the PR is waiting for you :laugh:
https://github.com/Suicide-Squirrel/android_device_huawei_charlotte/pull/1
as said: needs testing ofc as I do not own that device
.-
- Even though format is successful, TWRP will freeze and on next boot we can't boot or boot to TWRP.
We must format with stock Huawei recovery to fix that. So do not use the format yet in TWRP.
There must be some specific command that huawei uses to format the f2fs data partition. It's impossible to get that from a first boot from EMUI because adb logcat is not allowed until we unlock and enable
developer options. Plus that we can't selectively decrypt and encrypt again like we did a few years ago on older devices.... so i have to test several format command lines randomly until i get the right one.
- When i decrypt i get a fail, without a clear error. Decryption still has a looooong way to the fix and i don't have the time for that to do it daily, so be patient.
Well, at least we have a reliable TWRP now.
kessaras said:
- Even though format is successful, TWRP will freeze and on next boot we can't boot or boot to TWRP.
We must format with stock Huawei recovery to fix that. So do not use the format yet in TWRP.
There must be some specific command that huawei uses to format the f2fs data partition. It's impossible to get that from a first boot from EMUI because adb logcat is not allowed until we unlock and enable
developer options. Plus that we can't selectively decrypt and encrypt again like we did a few years ago on older devices.... so i have to test several format command lines randomly until i get the right one.
- When i decrypt i get a fail, without a clear error. Decryption still has a looooong way to the fix and i don't have the time for that to do it daily, so be patient.
Well, at least we have a reliable TWRP now.
Click to expand...
Click to collapse
Sounds painful, the other twrp does something similar..
Would the chap who made the unofficial one be able to assist?
His threads looked but he's still active .
Feel for you mate, sounds like a massive ballache.
kessaras said:
- Even though format is successful, TWRP will freeze and on next boot we can't boot or boot to TWRP.
We must format with stock Huawei recovery to fix that. So do not use the format yet in TWRP.
There must be some specific command that huawei uses to format the f2fs data partition. It's impossible to get that from a first boot from EMUI because adb logcat is not allowed until we unlock and enable
developer options. Plus that we can't selectively decrypt and encrypt again like we did a few years ago on older devices.... so i have to test several format command lines randomly until i get the right one.
- When i decrypt i get a fail, without a clear error. Decryption still has a looooong way to the fix and i don't have the time for that to do it daily, so be patient.
Well, at least we have a reliable TWRP now.
Click to expand...
Click to collapse
I did wipe system, cache, data and internal memory with success some weeks ago. But I didn't try the Format Data option.
djlukas1983 said:
I did wipe system, cache, data and internal memory with success some weeks ago. But I didn't try the Format Data option.
Click to expand...
Click to collapse
Lukas do not wipe data at an encrypted and non-decrypted partition.
When you will boot again to the rom, the system will think that data is clean so it will attempt to encrypt the already encrypted.
At settings you will see that you have 128gb data partition but you will have only a few mb actually.
wipe data does NOT remove encrption, only a format can remove the encryption.
djlukas1983 said:
I did wipe system, cache, data and internal memory with success some weeks ago. But I didn't try the Format Data option.
Click to expand...
Click to collapse
Did it actually wipe though? If it didn't the ROM may still boot as it would simply be a dirty flash.
Hi,
although I'm on a P20 Lite, does this work with EMUI9.x?
Is it possible to create TWRP also for ANE-LX1?
Does this work with GSI or only Stock ROMs?
Peter
pmatj said:
Hi,
although I'm on a P20 Lite, does this work with EMUI9.x?
Is it possible to create TWRP also for ANE-LX1?
Does this work with GSI or only Stock ROMs?
Peter
Click to expand...
Click to collapse
the only way to know that is to flash it and test it.
what are you afraid of ? if twrp doesn't boot, you can flash back the stock huawei recovery again.
>> the device won't have any issues if twrp is not for that device <<
It should work if it can boot. The only difference is our resolution. So if you see TWRP boot , then it's ok to use it.
* It will probably work because i don't force any specific resolution here.
But if it doesn't , change this to your resolution https://github.com/Suicide-Squirrel...43104c493e172dc469d7838153/BoardConfig.mk#L53
and build TWRP for p20 lite
Hm, ok, my P20Lite boots up, adb is initialized and I can also swipe to start but after 5-10 seconds, the phone just reboots to bootloader, so I cannot do anything useful with it....
I'm currently on EMUI9.1 (so A/B partitioned) and I already faced this behaviour on askuccios TWRP...
pmatj said:
Hm, ok, my P20Lite boots up, adb is initialized and I can also swipe to start but after 5-10 seconds, the phone just reboots to bootloader, so I cannot do anything useful with it....
I'm currently on EMUI9.1 (so A/B partitioned) and I already faced this behaviour on askuccios TWRP...
Click to expand...
Click to collapse
If it's a/b try talking to OnePlus 6/6t recovery.
They have a/b there too and if the dev answers to you then you probably have it
Non-Official Lineage 20.0 for EMUI 9 Huawei (ANE, FIG, POT, VTR, STF)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LeaOS is a project which based on LineageOS 20.1 with Andy Yan's and TrebleDroid GSI patches. I have added my personnals patches for Huawei devices : Encryption, Signal Strengh, Speed Boot, Assisted GPS, NFC, CAST/Miracast, Media App fixes, Camera HDR, SafetyNet etc..)
Changelog :
LeaOS Maarch 2023 version
Move to Android r35 (SPL Maarch)
Add offline charging
Add spoof model to pass safetynet
LeaOS February 2023 version
First release
Pre-requisite :
You must have TWRP installed if you want install patch. and a phone with unlock bootloader
Installation (crypt or uncrypt)
Download the version that corresponds to your Huawei phone model here and extract img file. You can choose with ou without GoogleApps
Flash system image : fastboot flash system <drag system.img here>
Flash twrp image: fastboot flash recovery_ramdisk <drag twrp img here>
Boot into twrp: power + vol+ while NOT connected to pc
Resize system: Wipe > Advanced Wipe > System > Repair or Change File System > Resize File System > Swipe
Wipe cache, dalvik/art cache, internal storage
Wipe data
(option) Install DRM patch for EMUI 9.1 to support DRM : 8-Huawei-FixPreav-AB-v1.3-signed.zip
(option) Install single modem patch for multi-sim device : 11-Huawei-MonoSim-AB-v1.1-signed.zip
reboot to System and set up the phone with Lineage first start assistant.
Enjoy !!!
Source Code:
https://github.com/Iceows
ROM OS Version: Android 13
ROM Kernel: Linux Huawei 4.9.148 or Phenix 4.9.319
ROM Firmware Required: EMUI 9.1
Based On: Lineage 20.0 and TrebleDroid
Credits:
@Frax3r (Testing)
@PHH
@eremitein
@RakinTheGreat (GCam)
@TureX (Kernel)
And all the others who tested my patches and helped me improve this ROM
Support Group
Channel update
Testting on FIG-XXX, will post results
Mafworld said:
Testting on FIG-XXX, will post results
Click to expand...
Click to collapse
How did you manage to install it? I began with EMUI 9.1 .115, unlocked the bootloader flashed the system, flashed twrp, resized system partition, wiped cache, dalvik/art cache, internal storage, installed stock recovery but I can't wipe data. It says reset failed. As far as I remember not wiping data from stock recovery wont work, phone is just stuck in a TWRP loop
EDIT: Well it just booted right in without formatting data. Guess it's fine
Shume said:
How did you manage to install it? I began with EMUI 9.1 .115, unlocked the bootloader flashed the system, flashed twrp, resized system partition, wiped cache, dalvik/art cache, internal storage, installed stock recovery but I can't wipe data. It says reset failed. As far as I remember not wiping data from stock recovery wont work, phone is just stuck in a TWRP loop
EDIT: Well it just booted right in without formatting data. Guess it's fine
Click to expand...
Click to collapse
Not need reset data from stock recovery
AltairFR said:
Not need reset data from stock recovery
Click to expand...
Click to collapse
Well the storage isn't accessible through the file manager, 0 space for images, can't download from browser, and if data is wiped from twrp the device loops into twrp
EDIT: Wiping data from twrp and reflashing the stock recovery took me out of the loop, everything seems to be working now. I'll report bugs if I find any
Shume said:
Well the storage isn't accessible through the file manager, 0 space for images, can't download from browser, and if data is wiped from twrp the device loops into twrp
EDIT: Wiping data from twrp and reflashing the stock recovery took me out of the loop, everything seems to be working now. I'll report bugs if I find any
Click to expand...
Click to collapse
Can you upload stock recovery. It just boots in twrp but it is frozen
acidhell said:
Can you upload stock recovery. It just boots in twrp but it is frozen
Click to expand...
Click to collapse
Its on Haky86's sourceforge
Does anyone know how can I get root access with this custom ROM? I need recovery.img file but I don't know how to get it. Appreciate all the help.
Why you say recovery ? Just enable adb in root mode
When I was on EMUI 9.1 I extracted recovery image from UPDATE.APP so i could root with magisk. I figured I'd do the same now that I am on this custom ROM but yeah, got stuck.
I have many Bluetooth disconnections. In order to make a connection I have to stop Aufio FX, then scan bluetooth device and untick HD audio. After a restart I have to do these steps all over again.
Can I use this on EMUI 12?
I managed to install it on FIG-LX1, but my screen constantly goes blurry for a few seconds and then goes back to being sharp. Any fix for that?
Hello, any bugs/not working?
Everything works fine, I don't have any issue with my P Smart 2018 (FIG-LX1).
However, I lost a huge amount of time to root my phone. And I don't succeed. Does anyone have tutorial/information to help ?
JeyJer said:
Everything works fine, I don't have any issue with my P Smart 2018 (FIG-LX1).
However, I lost a huge amount of time to root my phone. And I don't succeed. Does anyone have tutorial/information to help ?
Click to expand...
Click to collapse
Root with magisk
Skole said:
Does anyone know how can I get root access with this custom ROM? I need recovery.img file but I don't know how to get it. Appreciate all the help.
Click to expand...
Click to collapse
As Skole previously, and according to the official Magisk procedure, I should have the "recovery.img" file to patch with Magisk. Unfortunately, this file is nowhere ?
-----------------------
EDIT: after discussing with @Skole yesterday (thank you again!), I finally got the point. If you want to root your FIG-LX1, you should download the official Huawei's stock ROM and then extract the RECOVERY_RAMDIS.img from it (you can use tools like Huawei Update Extractor to do so).
Then, use Magisk to patch the RECOVERY_RAMDIS.img file. At last, you should flash it in fastboot mode with the command
Bash:
fastboot flash recovery_ramdisk /path/to/magisk_patched.img
Note that the command below doesn't work
Bash:
fastboot flash recovery /path/to/magisk_patched.img
Next, when your phone is off, press Power + Vol+ buttons ; realease them when you see the splash screen Huawei.
You can follow this popular tutorial to root your phone, but keep in mind the advices above
If something went wrong (like me yesterday ), look at the "dload" method to unbrick your phone thanks to EMUI !
Merci beaucoup AltairFR for LeaOS ! You and Skole give my huawei a new life !
Hello, I have been trying to install this with no luck. I have an FIG-LX1 (bootloader & FRP unlocked) with TWRP already installed.
I'm stuck on the second step, where I need to flash the .img file I downloaded. This is the output I get from fastboot flash system LeaOS-20.0-20230331-iceows-google-fig.img: (the same also happens with the image that doesn't have gapps)
Code:
Sending sparse 'system' 1/7 (460796 KB) OKAY [ 13.743s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
Can someone point me in a direction to go? I've been googling for hours with no avail.
(the phone currently cannot boot into any OS. only TWRP I got from this post)
kuylar said:
Hello, I have been trying to install this with no luck. I have an FIG-LX1 (bootloader & FRP unlocked) with TWRP already installed.
I'm stuck on the second step, where I need to flash the .img file I downloaded. This is the output I get from fastboot flash system LeaOS-20.0-20230331-iceows-google-fig.img: (the same also happens with the image that doesn't have gapps)
Code:
Sending sparse 'system' 1/7 (460796 KB) OKAY [ 13.743s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
Can someone point me in a direction to go? I've been googling for hours with no avail.
(the phone currently cannot boot into any OS. only TWRP I got from this post)
Click to expand...
Click to collapse
Your system partition is two small, try to install leao-phh without gapps to see if boot
I think your system partition is too small.
You can use this tool. https://forum.xda-developers.com/t/huawei-partition-kit-enlarge-system-partition.4545993/ made by AltairFR pretty sure.
You will need OS first , you can install this one without google aps. https://forum.xda-developers.com/t/...fig-lx1-leaos-phh-android-13-version.4558685/