Develop Bugs

[ROM][UNOFFICIAL][LineageOS][19.1][dragon] -> 2023-01-11 (DISCONTINUED)

{
"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"
}
LineageOS 19.1​
Android 12
lineage-19.1-20230111-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- Camera is not working yet.
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Chrome browser starts slowly.
- As it looks like Widevine L1 has been revoked by end of August 2020.
- Maybe more issues ..
Installation:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions !
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (25.2)
6. Wipe CACHE and DAVLIK
7. Reboot into system
Enjoy 12
Android 11
lineage-18.1-20220216-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Chrome browser starts slowly.
- Camera/Video may stops working after some time in use.
- As it looks like Widevine L1 has been revoked by end of August 2020.
Fresh Installation / Upgrade from any other ROM:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !)
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (21.x)
6. Wipe CACHE and DAVLIK
7. Reboot into system
Upgrade from previous lineage-18.x builds:
1. Boot into TWRP
2. Install ROM.zip
3. Re-Install Magisk 21.x
4. Wipe CACHE and DAVLIK
5. Reboot into system
Enjoy 11
Android 10
lineage-17.1-20201211-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Camera/Video may stops working after some time in use.
- As it looks like Widevine L1 has been revoked by end of August 2020.
system-as-root (SAR)
For gapps installation issues and more information ..
Pls read first .. https://forum.xda-developers.com/showpost.php?p=80693701&postcount=1350
Fresh Installation / Upgrade from any other ROM:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !)
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (20.x+)
6. Wipe CACHE and DAVLIK
7. Reboot into system
Upgrade from previous lineage-17.1 builds:
1. Boot into TWRP
2. Install ROM.zip
3. Wipe CACHE and DAVLIK
4. Reboot into system
- The ROM does contain it's own vendor.img ! (If you go back to Oreo, pls reinstall stock vendor.img)
Enjoy TEN
Android Pie
lineage-16.0-20191017-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- Encryption seems not to work - and has not been tested. -> Pls do not encrypt your data partition yet !
- Keymaster -> If you set Pattern, PIN or Password the Screen unlock may not work correctly.
Workaround for Pattern: On fresh boot you will need to wait a bit longer before you enter credentials.
The waiting time is required on fresh boot only, the following unlocks are working normally.
In case of problems pls use Update.ZIP_TWRP_flashable_pattern_pin_remover_V2.zip to remove pattern/pin or password.
Installation:
1. Boot into TWRP (latest available version)
2. Wipe system, cache, dalvik and data partitions ! ( If you have encrypted /data partition - pls "format" /data via TWRP first ! )
3. Install lineage-16.0-201Yxxyy-UNOFFICIAL-dragon.zip
4. Install Opengapps
5. install Magisk.zip (tested with 18.x)
6. Reboot into system ..
- The ROM does contain it's own vendor.img ! (If you go back to Oreo, pls reinstall stock vendor.img)
And big thanks to @NYCHitman1 (Dirty Unicorn) !
Without his work the Android Pie project would not have been possible !
I have uploaded the last official Lineage Oreo build to androidfilehost.com ..
lineage-15.1-20200221-nightly-dragon-signed.zip - -> DISCONTINUED
SOURCES:
https://github.com/followmsi/manifests/tree/dragon-lineage-18.1
DOWNLOADS:
https://drive.google.com/drive/fold...oaU1iazg?resourcekey=0-4krcBcSF3tnMFvgcP4kMvw
https://androidfilehost.com/?w=files&flid=289293
Enjoy LineageOS on your Pixel C .. [/B]

RESERVED

Here you are ..

TWRP loop for me. Installs with no errors but won't boot into the os
I did a dirty (coming from AOSP 7.1.2) and then clean install. Haven't factory refreshed yet.
Tried wiping again and flashing back to aosp and having the same issue.
Any thoughts?
edit: now trying to pull some data off my tablet to do a full wipe, i dont NEED to do this, but would like to...but twrp wont recognize MTP on my system (win 10) ... problems problems today

minieod said:
TWRP loop for me. Installs with no errors but won't boot into the os
I did a dirty (coming from AOSP 7.1.2) and then clean install. Haven't factory refreshed yet.
Tried wiping again and flashing back to aosp and having the same issue.
Any thoughts?
edit: now trying to pull some data off my tablet to do a full wipe, i dont NEED to do this, but would like to...but twrp wont recognize MTP on my system (win 10) ... problems problems today
Click to expand...
Click to collapse
Did you format system ?
Pls do as first step.
If you boot loop install boot.img via fastboot.
No problems here.. it's quite fast !
Also dirty installation .. kept all my settings.
EDIT:
Mtp should work .. correct driver in Windows ?
We are using abd and mtp at the same time.
A Windows driver is on the share as well ..

Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip
Based on LineageOMS sources ...
https://github.com/LineageOMS
Enjoy

followmsi said:
Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip
Based on LineageOMS sources ...
https://github.com/LineageOMS
Enjoy [/QUOT
Is the nav bar laid out like stock
Click to expand...
Click to collapse

followmsi said:
Did you format system ?
Pls do as first step.
If you boot loop install boot.img via fastboot.
No problems here.. it's quite fast !
Also dirty installation .. kept all my settings.
EDIT:
Mtp should work .. correct driver in Windows ?
We are using abd and mtp at the same time.
A Windows driver is on the share as well ..
Click to expand...
Click to collapse
Hey follow
Yep did all of that. Formatted system, flashed boot.img, and no issues with mtp prior to the boot loops.
I went ahead and did a complete userdata reset and am sampling the O DP1 now ..I'm sure it'll work fine when (if) I come back to 7.x

Officialness
Thanks for building this. Hoping to try it out this weekend.
I'm hoping you intend to submit this build officially to LineageOS, so we continue to get updated builds. As you probably remember Cyanogen didn't accept the Pixel C. Hopefully with LineageOS things are better.

gaufres said:
Thanks for building this. Hoping to try it out this weekend.
I'm hoping you intend to submit this build officially to LineageOS, so we continue to get updated builds. As you probably remember Cyanogen didn't accept the Pixel C. Hopefully with LineageOS things are better.
Click to expand...
Click to collapse
You are not the first asking me this question ..
Here some more information ..
https://wiki.lineageos.org/submitting_device.html
Who is the maintainer ? .. me
- Changing vendor stuff .. monthly
- Applying kernel patches .. monthly
- Applying possible device tree patches and changes .. monthly
- Etc.
Here is the manifest for LOS ..
https://github.com/followmsi/manifests/tree/dragon-lineageos-cm-14.1
Also for the people who like to build their own verison
- As you may see we are removing 2 LOS repos today, due to build errors.
- This needs to be fixed on code level first - commited on LOS github.
- The stock google vendor.img needs to be integrated into the LOS Installer
Still not clear how this is done for "official" lineageos .. also from legal point of view.
Actually I need to get information here ... How is this done for other ROMs having a dedicated vendor.img ?
- The missing integrated kernel building was impemented a few minutes before
https://github.com/followmsi/androi...mmit/316a7e0e87b191bcf11b8de55778ddec83fac2f8
https://github.com/followmsi/android_kernel_tegra/commit/3e3e24c41db74693efc2fc74efaf6286b1c06013
You see there a few issues left ..
The ROM works perfectly but its not ready to be official yet.
Don't want to force and push a go live now .. No need to rush !
Hope you have a better understanding now ..
Cheers

Reuben_skelz92 said:
followmsi said:
Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip
Based on LineageOMS sources ...
https://github.com/LineageOMS
Enjoy [/QUOT
Is the nav bar laid out like stock
Click to expand...
Click to collapse
No !
The OMS version is the same like lineageOS but including OMS - to be ready to install substratum .. etc.
Made a version for Nexus 10 as well .. it seems to work fine.
Just have installed the ROM .. works fine - but did no special customizations or anything else.
Hope this helps ..
Click to expand...
Click to collapse

Debugging bootloop
followmsi said:
Did you format system ?
Pls do as first step.
If you boot loop install boot.img via fastboot.
Click to expand...
Click to collapse
Unfortunately this is also bootlooping for me. I've tried the steps above.
How can I help debug this? I was not able to use logcat. Does logcat work for you?

gaufres said:
Unfortunately this is also bootlooping for me. I've tried the steps above.
How can I help debug this? I was not able to use logcat. Does logcat work for you?
Click to expand...
Click to collapse
You did flash boot.img via fastboot ?
The ROM installation had no errors ?
What version of bootloader are you using .. .50 for 7.1.2 ?
Do you see the LOS logo (boot animation) when you boot-loop ?
Are you able to make a md5 hash ..Or similar to compare ?
File corrupt ?
Pls post a hash value to compare .. maybe onedrive is the problem.
Was not the first time a file was corrupted.
I am testing several ROMs and kernels in the last days .. no problems at all.
EDIT:
Which version of TWRP ?
EDIT2:
For your understanding.. logcat will start a short time after Android is booting.(boot animation)
But if you not pass the boot.img we have another issue. (Google logo)

Re: Debugging bootloop
followmsi said:
You did flash boot.img via fastboot ?
Click to expand...
Click to collapse
Yes. No errors.
followmsi said:
The ROM installation had no errors ?
Click to expand...
Click to collapse
None.
followmsi said:
What version of bootloader are you using .. .50 for 7.1.2 ?
Click to expand...
Click to collapse
I think so. Version 7900.50.0 from n2g47d.
followmsi said:
Do you see the LOS logo (boot animation) when you boot-loop ?
Click to expand...
Click to collapse
It doesn't get that far.
I see the unlocked bootloader warning. After thirty seconds it beeps, as expected. Then white "Google" text is then displayed for two or three seconds.
But after that it reboots into TWRP (blank screen, then unlocked bootloader warning, then beep, then white "Google" text, then TWRP).
followmsi said:
Are you able to make a md5 hash ..Or similar to compare ?
Click to expand...
Click to collapse
The update zip I'm installing from TWRP is lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip, which I downloaded from OneDrive. It has SHA256 hash
Code:
d124b4048f096317f593fa5dbf313ceaebbddd4352f0422276a86fd5f6707902
The boot.img I'm flashing with fastboot comes from the above zip. So it might be redundant for me to say the boot.img has SHA256 hash
Code:
cde8c7376d2d8d9d35ea5558473a669f91a27b0489f21b7a3cdb79af4a4ba931
followmsi said:
Pls post a hash value to compare .. maybe onedrive is the problem.
Was not the first time a file was corrupted.
Click to expand...
Click to collapse
I'm kinda hoping that is the problem, because otherwise this will be a pain to debug!
followmsi said:
I am testing several ROMs and kernels in the last days .. no problems at all.
Click to expand...
Click to collapse
Good. Weird.
followmsi said:
Which version of TWRP ?
Click to expand...
Click to collapse
Your build of 3.1.0-0.
followmsi said:
For your understanding.. logcat will start a short time after Android is booting.(boot animation)
But if you not pass the boot.img we have another issue. (Google logo)
Click to expand...
Click to collapse
Thanks for the explanation. So it might be boot.img given the boot sequence I described above?

I always get the TWRP bootloop if I boot before installing SuperSU. That happened with DU and with this.
I also had some issues with the setup wizard crashing. It was skipping the step of connecting wifi, and then it would crash when I tried to enter a Google account (which wouldn't have worked anyway without wifi.) I tried different gapps, same result. Finally I managed to swipe open settings and connect to wifi and now I'm set.
Now that I've got it running (OMS variant) it's great.

gaufres said:
Yes. No errors.
None.
I think so. Version 7900.50.0 from n2g47d.
It doesn't get that far.
I see the unlocked bootloader warning. After thirty seconds it beeps, as expected. Then white "Google" text is then displayed for two or three seconds.
But after that it reboots into TWRP (blank screen, then unlocked bootloader warning, then beep, then white "Google" text, then TWRP).
The update zip I'm installing from TWRP is lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip, which I downloaded from OneDrive. It has SHA256 hash
Code:
d124b4048f096317f593fa5dbf313ceaebbddd4352f0422276a86fd5f6707902
The boot.img I'm flashing with fastboot comes from the above zip. So it might be redundant for me to say the boot.img has SHA256 hash
Code:
cde8c7376d2d8d9d35ea5558473a669f91a27b0489f21b7a3cdb79af4a4ba931
I'm kinda hoping that is the problem, because otherwise this will be a pain to debug!
Good. Weird.
Your build of 3.1.0-0.
Thanks for the explanation. So it might be boot.img given the boot sequence I described above?
Click to expand...
Click to collapse
[HashChecker]
[File]/storage/emulated/0/download/lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip
[MD5]C79F1066186FF36C55643E264B3647E2
[SHA1]4DDD0A811FE22359D745335AA563023E95E808D3
[SHA256]D124B4048F096317F593FA5DBF313CEAEBBDDD4352F0422276A86FD5F6707902
At least the sha256 matches
Good bootloader
Good TWRP version ..
Do you install supersu at last step of your installation procedure ?
After you did install the ROM in TWRP, pls install supersu.zip (2.79 -sr3) as last step.
It will boot twice for the first time .. but then it should boot normally.

badwiring said:
I always get the TWRP bootloop if I boot before installing SuperSU. That happened with DU and with this.
I also had some issues with the setup wizard crashing. It was skipping the step of connecting wifi, and then it would crash when I tried to enter a Google account (which wouldn't have worked anyway without wifi.) I tried different gapps, same result. Finally I managed to swipe open settings and connect to wifi and now I'm set.
Now that I've got it running (OMS variant) it's great.
Click to expand...
Click to collapse
The SetupWizard is related to gapps .. the beans version seems to run perfectly.
Opengapps seems still to have issues on certain devices.
Will check supersu topic ..
Thanks for the feedback !

badwiring said:
I always get the TWRP bootloop if I boot before installing SuperSU.
Click to expand...
Click to collapse
followmsi said:
Do you install supersu at last step of your installation procedure ?
Click to expand...
Click to collapse
Thanks both. That's it.
No su: bootloops.
Lineage extras su: bootloops
SuperSU: boots OK
Magisk: boots OK

gaufres said:
Thanks both. That's it.
No su: bootloops.
Lineage extras su: bootloops
SuperSU: boots OK
Magisk: boots OK
Click to expand...
Click to collapse
Cool !
Found the issues as well ..
It's related to DM-verity .. even some config is missing.
Or the overwrite of build_fingerprint is related.
Need to investigate ..
Both supersu and magisk are removing the DM-verity checks in ramdisk.(boot.img)
As I always install supersu, I never realized.
Just compiling a new version .. changed the sources.
https://github.com/followmsi/androi...mmit/aae5804e75f4133ec82253cf6b2afbe39e46a56a
Removing DM-verity from fstab .. should solve this issue, also without supersu.
At later stage we can enable again, if it's working fine.
Thanks for your help testing ..
Cheers

New release ..
lineage-14.1-20170421-UNOFFICIAL-dragon-followmsi.zip
Changes:
- Integrated kernel compiling - using DU branch
- disabled DM-verity -> should fix proper booting even without supersu/magisk.
- General LineageOS changes -> fresh repo sync from today .. https://download.lineageos.org/
Installation:
1. Boot into TWRP
3. Install lineage-14.1-20170421-UNOFFICIAL-dragon-followmsi.zip
4. install SuperSU-v2.79-201612051815.zip (optional)
6. Reboot into system ..
- The ROM installer will keep your existing gapps installation.
- If you had SuperSu installed before you need to install it again - as we overwrite the boot.img completely.
A new OMS version will come later ..
Enjoy ..

[Recovery] [Unofficial] [MI 8] TWRP 3.3.1-1031

I'm not the Author, the author is wzsx150 from LR.TEAM
WZSX’s TWRP is well-known as the Chinese version of TWRP due to the language default is in Chinese. However, you can switch to English within TWRP user settings it's easily. switched. You can follow the instructions on this link to change the language to English: https://miui.blog/any-devices/lr-tea...inese-english/
Xiaomi 8's LR.Team customized version of Twrp
Automatically decrypts data, Includes root functionality, clear the power-on password, multi-function restart.
Disclaimer: I have installed it and for me it works fine. However, it is not guaranteed to work for you especially if you currently have encryption. Use at your own risk
If you need help flashing TWRP : Follow instructions here: https://miui.blog/mi-8/flash-twrp-root-mi-8/
Downloads
Latest
Version for Miui 11 Android 10/Q : https://www.androidfilehost.com/?fid...26312261636230
MD5: 2f5f2e7dc8f32b5a999828c9370b7de2
Version for Miui 10 or 11 Android 9/P : https://www.androidfilehost.com/?fid...26312261636232
MD5: 4681f9bd6367f934218da71fd528e39b
Old Versions
TWRP-3.2.3.1-FireDance-Edition (English) ( img)
TWRP 3.2.3-1208 (English) ( zip - img )
TWRP 3.2.3-1110 (English) ( zip - img )
TWRP 3.2.3-1110 ( zip - fastboot - img )
TWRP 3.2.3-0918 (zip - fastboot - img)
TWRP 3.2.3-0908 (zip - fastboot - img)
TWRP 3.2.2-0703 (zip - fastboot - img)
TWRP 3.2.2-0611 (zip - fastboot - img)
TWRP 3.2.2-0609 (zip - fastboot - img)
Changelog (Google Translated)
2018.11.10 update Contents:
1. Update the new rom that supports the official Android 9.
2. Update and optimize some functions
3. Increase the option to restart after the automatic upgrade is completed. In the twrp setting, the default is automatic restart. Uncheck the box and you can not restart. After the automatic upgrade, some operations are performed to prevent twrp from being overwritten, etc.
4. Update the built-in root to magisk 17.1, and fix the problem that the module cannot be brushed. Other features are also updated and optimized
5. After the new version of the system root, restarting the system requires manual installation of the magisk app, the official system problem, this can only be so
. 6. If Kami may need the root system or remove the dm check operation.
7. Prevent the functions covered by the official rec: root system, signature boot, remove dm check, cancel forced encryption, etc.
2018.9.8 update:
1. Support the official Android 9.0 system, including automatic decryption data
2. About data decryption, this may not be particularly stable now, sometimes need to reboot into the system and then restart Twrp can be decrypted.
If the new version of twrp is not supported, you can try to use the old version of
2018.8.6 update:
1. Update twrp 3.2.3 source code
2. Built-in magisk16.7, temporarily build this version first
3. Optimize data decryption problem, fix some problems
4 Support the new version of miui10 data decryption
5. Decrypt the plaintext display input password, easy to check whether the password input is correct
6. Update to try to repair the decryption data scheme, set the lock screen password to the machine, enter twrp need to enter the lock screen Password, otherwise you cannot temporarily decrypt data.
7. After brushing in twrp, the first time you enter twrp may restart once. This is normal. If you restart repeatedly, or you can't decrypt data, please give me feedback on Weibo.
8. Regarding data decryption, this may not be particularly stable now. Sometimes you need to reboot into the system and restart into twrp to decrypt.
If the new version of twrp is not supported, you can try to use the old version of

Thanks. I was already using the EN version you posted in the Dogsly(that may be wrong) thread.
Great job

arifqur said:
Thanks. I was already using the EN version you posted in the Dogsly(that may be wrong) thread.
Great job
Click to expand...
Click to collapse
@gulp79 is to thank for the English version

mikefallen said:
@gulp79 is to thank for the English version
Click to expand...
Click to collapse
if you want to add to op, this is the img version of TWRP-3.2.3-1110-XIAOMI8-EN-wzsx150
(with a minor modifications of prop.default, and also with chinese language, in previous version chinese was removed, btw english is set as default).
https://mega.nz/#!MwQn3IgR!UmuuBk1OScPrHi_HUO1zA_Da0df3nexfrrWGEBGjJPg

gulp79 said:
if you want to add to op, this is the img version of TWRP-3.2.3-1110-XIAOMI8-EN-wzsx150
(with a minor modifications of prop.default, and also with chinese language, in previous version chinese was removed, btw english is set as default).
https://mega.nz/fm/M4oDgLxA
Click to expand...
Click to collapse
that link doesn't seem to work for me, just redirects to the home page of mega

mikefallen said:
that link doesn't seem to work for me, just redirects to the home page of mega
Click to expand...
Click to collapse
try this
https://mega.nz/#!MwQn3IgR!UmuuBk1OScPrHi_HUO1zA_Da0df3nexfrrWGEBGjJPg

gulp79 said:
try this
https://mega.nz/#!MwQn3IgR!UmuuBk1OScPrHi_HUO1zA_Da0df3nexfrrWGEBGjJPg
Click to expand...
Click to collapse
yup added to OP Thanks!

Help!!!
It works for mi 8 miui 10.0.3.0 global?, i cant figure out how install the eu rom, in the twrp show me only folders encrypted :C, somebody knows how ?

Looks like you will have to format Dara partition in recovery by typing yes

So, boot the img and then flash the zip for TWRP to stick permanently?

Can't use gapps Aroma installer using twrp .. any ideas ?

could this twrp support amora installer
could this twrp support amora installer?

On my MI 8, i restored a previous backup made with twrp, now the device does not accept my 4-digit password so I can't login to my phone!
please help!

cyaneo said:
On my MI 8, i restored a previous backup made with twrp, now the device does not accept my 4-digit password so I can't login to my phone!
please help!
Click to expand...
Click to collapse
in twrp go to file manager, data, system and delete locksettings file. reboot and you're good to go again

Hi!
Help me, please!
I can't exit from recovery mode on MI8

cyaneo said:
On my MI 8, i restored a previous backup made with twrp, now the device does not accept my 4-digit password so I can't login to my phone!
please help!
Click to expand...
Click to collapse
Go into recovery mode, format internal memory.
---------- Post added at 06:24 AM ---------- Previous post was at 06:22 AM ----------
Coolesha said:
Hi!
Help me, please!
I can't exit from recovery mode on MI8
Click to expand...
Click to collapse
You need to format your device.

bahuy2003 said:
Go into recovery mode, format internal memory.
Click to expand...
Click to collapse
ok, but doesn't this delete all my settings & personal files (aka reset to default)?
Thank you!

cyaneo said:
ok, but doesn't this delete all my settings & personal files (aka reset to default)?
Thank you!
Click to expand...
Click to collapse
If you device can't reboot, you can flash eu or global rom, format again and reboot system.

bahuy2003 said:
If you device can't reboot, you can flash eu or global rom, format again and reboot system.
Click to expand...
Click to collapse
Hu? never wrote it doesn't reboot etc. - It reboots, everything seems to be OK - I "just" can't login after restore a backup....
so, again: does "format internal memory" reset my phone, delete setting or personal files? If so, how does this solve the problem? After a fresh EU ROM install, everything works fine like a new install does.

cyaneo said:
Hu? never wrote it doesn't reboot etc. - It reboots, everything seems to be OK - I "just" can't login after restore a backup....
so, again: does "format internal memory" reset my phone, delete setting or personal files? If so, how does this solve the problem? After a fresh EU ROM install, everything works fine like a new install does.
Click to expand...
Click to collapse
Flash this zip in TWRP and your login password would be deleted, which by the way gets jumbled up after a restore.

[CLOSED][OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7.2 | Daredevil |

{
"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 - Iam Not Responsible for bricked devices
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
Note - download twrp according to your phone security patch
1 . Download twrp-3.4.0-0-DDV_sprout_sprout.img copy in one folder
2. connect phone to pc boot your phone to bootloader mode
3. open cmd in that folder
4. type fastboot devices
5. type fastboot flash boot twrp-3.4.0-0-DDV_sprout.img
6. now get back to phone select recovery mode and now your phone boots in to twrp
7. now flash magisk or what ever your wish and press reboot system
bugs- none
well still you people can flash magisk.zip using sideload
just download magisk.zip & and click on sideload in twrp and open cmd and type adb sideload magisk.zip and after completion reboot system
Download Android 9 Twrp-3.3.1-0 From Here
Download Android 10 Twrp-3.4.0-0 From Here
​For More Information About Status Official Click Here​
​Join Nokia 7.2 Community​
​
XDA:DevDB Information
TWRP 3.4.0-0 , for the Nokia 7.2
Contributors
Raghu varma
My build script: https://github.com/RaghuVarma331/scripts
Source Code: https://github.com/omnirom/android_bootable_recovery
Device Source Code: https://github.com/TeamWin/android_device_nokia_DDV_sprout.git
Version Information
Status: beta
Created 2019-11-07
Last Updated 2020-06-25

Thanx.
Thanx for the effort and hope this phone will have good Custom
ROMs too

nuwanmw1988 said:
Thanx for the effort and hope this phone will have good Custom
ROMs too
Click to expand...
Click to collapse
Soon roms will be out

Does anyone have a stock recovery.img? In case that i will install OTA.

pinh3ad said:
Does anyone have a stock recovery.img? In case that i will install OTA.
Click to expand...
Click to collapse
Nokia 7.2 is an A/B system, not sure where you would get a recovery.img
Additionally, coming from 00WW_1_200 (September update), WiFi module fails after flashing TWRP, and it seems you have to reflash original kernel/boot.img to get the WiFi back. It would be helpful if someone is willing/able to provide it.

KohGeek said:
Nokia 7.2 is an A/B system, not sure where you would get a recovery.img
Additionally, coming from 00WW_1_200 (September update), WiFi module fails after flashing TWRP, and it seems you have to reflash original kernel/boot.img to get the WiFi back. It would be helpful if someone is willing/able to provide it.
Click to expand...
Click to collapse
The reason behind this we need a proper kernel sources from hmd Nokia . For that reason i used prebuilt kernel from stock rom and that rom is based on August so here August kernel & wifi modules signed with different keys and September kernel & wifi modules signed with different keys so here August kernel and September wifi modules signatures are different that's why wifi got broken

Hi Guys,
i'm having a problem, I' able to fastboot flash boot twrp-3.3.1-0-DDV_sprout-9.0-20191119.img but when I restart it, i still not having twrp booting and now, the wireless module is not booting
Anyone to help?
D:\userdata\...\Desktop\Nokia 7.2> fastboot flash boot "D:\userdata\...\Desktop\Nokia 7.2\twrp-3.3.1-PL2.img"
target reported max download size of 536870912 bytes
sending 'boot' (38736 KB)...
OKAY [ 0.849s]
writing 'boot'...
OKAY [ 0.246s]
finished. total time: 1.101s
D:\userdata\...\Desktop\Nokia 7.2> fastboot reboot
rebooting...
finished. total time: 0.002s

JoSoFer said:
Hi Guys,
i'm having a problem, I' able to fastboot flash boot twrp-3.3.1-0-DDV_sprout-9.0-20191119.img but when I restart it, i still not having twrp booting and now, the wireless module is not booting
Anyone to help?
D:\userdata\...\Desktop\Nokia 7.2> fastboot flash boot "D:\userdata\...\Desktop\Nokia 7.2\twrp-3.3.1-PL2.img"
target reported max download size of 536870912 bytes
sending 'boot' (38736 KB)...
OKAY [ 0.849s]
writing 'boot'...
OKAY [ 0.246s]
finished. total time: 1.101s
D:\userdata\...\Desktop\Nokia 7.2> fastboot reboot
rebooting...
finished. total time: 0.002s
Click to expand...
Click to collapse
You have to flash twrp According to your security patch
For example September security patch download from 2019-09-19
For example August security patch download from
2019-08-19
And also if you want to boot back to twrp after flashing twrp and rebooting in to system
Just power off your phone and reboot to download mode and press reboot to recovery now you will boot in to twrp.
If you know what exactly you are doing you won't get confused just follow steps
If you still can't able to boot then you are unlucky because all of the people who viewed this thread successfully booted as well

Hi, I tried to flash this TWRP 2 times, and in all cases the touch does not work. Nokia 7.2 TA-1196. Any ideas how to fix this?

Which TWRP to Flash?
i have model TA-1193 on november 5 security patch, os version is 00ww_1_200_SP01.
was able to successfully un lock bootloader today. Which TWRP should i flash? there are multiple images in https://sourceforge.net/projects/ddv-sprout/files/TWRP/PIE/2019-11-05/\
tried Flashing all the recoveries from the folder, wifi doesnt work.! any help how to fix it?

I wiped my SD card, now instead of 256GB it shows as 16MB, any ideas? Crap, now when i boot into Recovery, i just get a dead robot and 'No Command".

Why do the instructions here say to flash it to the boot partition, but the instructions on the twrp site say to flash it to the recovery partition? IMO recovery makes more sense but I'm no expert.
Which one is correct?
Code:
fastboot flash boot twrp.img
or
Code:
fastboot flash recovery twrp.img
I've had bat luck flashing things to boot in the past so want to make sure.
----- EDIT -----
Nvm my silly question. I've been out of the loop for a while and didn't realise there isn't even a recovery partition anymore. I've now flashed TWRP, boots up fine. No issues with anything on the stock rom afterwards.
However, my question now is how to get TWRP to work with the internal storage? I wanted to make a somewhat stock backup before rooting and the internal storage is full of jibberish folders and files. (See attached image)

CGarz said:
Why do the instructions here say to flash it to the boot partition, but the instructions on the twrp site say to flash it to the recovery partition? IMO recovery makes more sense but I'm no expert.
Which one is correct?
Code:
fastboot flash boot twrp.img
or
Code:
fastboot flash recovery twrp.img
I've had bat luck flashing things to boot in the past so want to make sure.
----- EDIT -----
Nvm my silly question. I've been out of the loop for a while and didn't realise there isn't even a recovery partition anymore. I've now flashed TWRP, boots up fine. No issues with anything on the stock rom afterwards.
However, my question now is how to get TWRP to work with the internal storage? I wanted to make a somewhat stock backup before rooting and the internal storage is full of jibberish folders and files. (See attached image)
Click to expand...
Click to collapse
Well even I appreciate the work of this guy, you have to be careful. 1st - if you on Nokia 7.2 keep in mind that all his stuff based not on Nokia 7.2 sources because Nokia not released any souses yet. 2nd - he warned about it if read carefully. 3rd - all his ROMs for Nokia 7.2 have same trouble as LineageOS and treble. I prefer stay on stock with MicroG, at least all stuff works. 4th - for internal access from twrp you have flash DisableForceEncryption_Treble. Don't use Disable_Dm-Verity_ForceEncrypt_10.20.2019 it has bugs and not works. Just look for same name as I give Disable_Forse_Encryption_Treble. Careful with, it removes encryption but leaves verity in tact. Read all warning about using it, google in help. After reboot in twrp you would read internal and data. Hope that helps. Also check version twrp that he uploading, they base on security patch and I guess it have to match your system. But I'm using fine 11/28 on august security patch.
O, and one more thing - don't relay completely on twrp backups, they not working in 100%, just try restore before. Good luck.

Thanks for the tips boomo15. I ended up installing the Lineage OS rom though.
WiFi works now, data is decrypted and the other system UI crashing bug I had has gone as well. Very pleased with the phone now.
NFC and DDTW don't work and cam quality is poor but even with those issues Lineage is still preferable to me.

CGarz said:
Thanks for the tips boomo15. I ended up installing the Lineage OS rom though.
WiFi works now, data is decrypted and the other system UI crashing bug I had has gone as well. Very pleased with the phone now.
NFC and DDTW don't work and cam quality is poor but even with those issues Lineage is still preferable to me.
Click to expand...
Click to collapse
As I told before stock works best for me, but last week I install AOSP phh_treble version for Pie 123. Since 109 a lot off better.All works smooth and fine, detects my sim card w/o problems (got 1 sim not dual). Replaced camera (crashed all time) with ported by Balu GCam works fine for me. Got one issue - can send sms but can't receive. Tried fix myself but no luck, so asked for help on AOSP treble tread. Hope somebody know what's going on. Don't use NFC can't tell if it works or not.

boomo15 said:
As I told before stock works best for me, but last week I install AOSP phh_treble version for Pie 123. Since 109 a lot off better.All works smooth and fine, detects my sim card w/o problems (got 1 sim not dual). Replaced camera (crashed all time) with ported by Balu GCam works fine for me. Got one issue - can send sms but can't receive. Tried fix myself but no luck, so asked for help on AOSP treble tread. Hope somebody know what's going on. Don't use NFC can't tell if it works or not.
Click to expand...
Click to collapse
That' strange about SMS. Did you set your APN correctly? Or does your carrier auto set it like mine does?
Also for NFC could you see if you have the option for it in settings? It should be around WiFi, Bluetooth, etc.

Hi,
I was trying to install the TWRP recovery but when I saw people in a other XDA forum everyone crying about there WiFi that wont work.
So I was wondering can I install the TWRP recovery without those problems.
Here some info about my phone:
Nokia 7.2 TA-1196
Android version: 9
Security patch level: December 5, 2019
Some help would be appreciated.

VictorAcid said:
Hi,
I was trying to install the TWRP recovery but when I saw people in a other XDA forum everyone crying about there WiFi that wont work.
So I was wondering can I install the TWRP recovery without those problems.
Here some info about my phone:
Nokia 7.2 TA-1196
Android version: 9
Security patch level: December 5, 2019
Some help would be appreciated.
Click to expand...
Click to collapse
Not sure about your version, I got Nokia 7.2 TA-1178 no any problems on stock. The problem that I experienced with was when I used Disable_Dm-Verity_ForceEncrypt_10. - bootloop. For root I used Magisk versions from 19.3-20.2 w/o any problems. Read couple treads above what I used to disable encryption. Also I use w/o problems Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip - it do all job remove encryption and verity if you interested. Also not all backups that I made using TWRP posted here worked.
---------- Post added at 05:31 PM ---------- Previous post was at 05:23 PM ----------
CGarz said:
That' strange about SMS. Did you set your APN correctly? Or does your carrier auto set it like mine does?
Also for NFC could you see if you have the option for it in settings? It should be around WiFi, Bluetooth, etc.
Click to expand...
Click to collapse
Sorry I can't tell you anything about NFC. As I told before can't receive SMS and this I my business phone not playing toy I return back on stock. For me root and removing not wanted stuff enough. Bad that not all my TWRP backups working, have to always format data. Right now I do adb backup.

boomo15 said:
Not sure about your version, I got Nokia 7.2 TA-1178 no any problems on stock. The problem that I experienced with was when I used Disable_Dm-Verity_ForceEncrypt_10. - bootloop. For root I used Magisk versions from 19.3-20.2 w/o any problems. Read couple treads above what I used to disable encryption. Also I use w/o problems Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip - it do all job remove encryption and verity if you interested. Also not all backups that I made using TWRP posted here worked.
---------- Post added at 05:31 PM ---------- Previous post was at 05:23 PM ----------
Sorry I can't tell you anything about NFC. As I told before can't receive SMS and this I my business phone not playing toy I return back on stock. For me root and removing not wanted stuff enough. Bad that not all my TWRP backups working, have to always format data. Right now I do adb backup.
Click to expand...
Click to collapse
Okay lets not try it this is my main phone :/

I tried to build TWRP myself using your device tree and the latest stock kernel that I extracted from the OTA. The result was a working wifi module, but whenever I set a device unlock PIN, entering the correct PIN doesn't unlock the device. It just says "Wrong PIN". Do you have any thoughts about what could be happening? I'm at a loss.

[HONOR 6x EMUI 8.X Oreo] Installing EMUI 8.X on Honor 6X EMUI 5.X and RAM extend via SD Card

My problem is that I can't run correctly LineageOS on Honor 6x, and I didn't know how to run it properly, and I still don't know how to do it because I got bootloop, even if I factory reset...
=> For future people who still want to know how I switch Honor 6x on EMUI 5.X to EMUI 8.X, I write just below the full step and problems that I met during this process (But I think there is already some thread that talk about this.
________________________________________________________________________________________________________
Installing EMUI 8.X Oreo from scratch on a Honor 6x running with the EMUI 5.X Nougat
First of all, I have to thanks @Djiban that help me for the first step ✌
So, many Custom ROM/AOSP ROM for Honor 6x required an EMUI 8.X base.
And to update your Honor 6x to EMUI 8.X, you MUST DEBRAND your phone to BLN L22 India version of the OS
1/ Requirements (Search on Google for installation and how to use, or ask in this thread below)
Spoiler: 1/ Requirements
- You can choose between those 2 methods (Advise you to take the Huawei MultiTool):
Have ADB and Fastboot tools on Computer: ||__Minimal ADB__|| (also present with Android Studio, Unity3D with Android build support)
For Unity3D, if you had add the Android Build Support, the adb and fastboot tools should be here : C:\Program Files\Unity\Hub\Editor\20XX.X.X\Editor\Data\PlaybackEngines\AndroidPlayer\SDK\platform-tools (Replace 20XX.X.X with your version of Unity 3D)
You can ALSO use ||__Huawei MultiTool v8 __||, that get on more an interface(Great Noob Friendly tools).
I advise you to set the 2 tools inside the Windows 10 environment variable to easily use adb and fastboot command on command prompt. Type adb devices on the console tools of your computer, if it's correctly referenced you will see something like the screenshot:​
{
"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"
}
- Unlock the bootloader of your phone ! (you can use ||__DC unlocker__|| to get the bootloader code for 4€, or if someone know to get the number with a simple batch file code ? It would be awesome) (Huawei don't get you anymore the bootloader code, even with the paid service)
To make DC-UNLOCKER detect your phone :​
In your phone Settings -> About Phone -> Press 7 times the Build Number => To unlock Developpers Options; then go to Settings -> Developpers Options => Enable USB debugging
Install HiSuite from Huawei to get all the drivers needed to detect your Huawei/Honor phone on your computer
You have to type in dial pad(the default phone app) *#*#2846579#*#* then go to ProjectMenu -> Background Settings -> USB Ports Settings -> [U]Manufacture Mode[/U]. You have to redo this if you disconnected your phone, because it will set by default the HiSuite Port !
Once you get the code :​
In your phone Settings -> Developpers Options => Enable Unlocking OEM
Connect your phone to your computer and allow the debugging mode, and choose MTP mode(transfert files, not charging only)
With Huawei Multi-Tool, press Quick Actions(top right of the UI) -> Reboot to Fastboot mode (OS-FB) OR
Open the console (search cmd on windows), and type adb reboot bootloader
Open the console (search cmd on windows), and type fasboot oem unlock YOURCODE
If all good, type in the cmd : fastboot reboot
- MUST install TWRP Recovery 3.1.1 (Other versions will not work for EMUI 5.X Android Nougat) :
Use Huawei MultiTool : In Recovery Tab, it will normally propose you the EMUI5 twrp image or the 3.1.x version. Press Flash Recovery_ramdisk (require you to enable/allow USB debugging on your phone)
You can also choose an image from your download (see link below for twrp 3.1.1)
Or with the cmd
Boot into fastboot : adb reboot bootloader
Install TWRP : fastboot flash recovery twrp-3.1.1-0-berlin.img
||__All TWRP version for Honor 6x[berlin]__||
||__twrp-3.1.1-0-berlin.img__||
- Advise you also to make a backup with HiSuite to save your data, and a TWRP backup to recover your system in case.
- To reboot into TWRP Recovery mode, press Volume + and Power buttons. Or use Huawei MultiTool v8 Quick Actions or type into the cmd : adb reboot recovery
2/ Debrand to BLN-L22
Spoiler: 2/ Debrand to BLN-L22
- See if you already got the BLN-L22 or not : Honor6x -> Settings -> About phone -> Build number
If yes, you can skip this step
View attachment 5233545
- Here is the tutorial made by @shashank1320 to debrand to BLN-L22 (work for BLN and BLL models as I know): ||__LINK__||
(Careful, the 3 links on the firmware finder database may take 1-3 hours to download, they didn't get a good server speed, same as the step 3) And you may need to flash OEMInfo.zip via TWRP !
- Here is some issues that I encounterd and solved, the Huawei MultiTool ZIP is there also : ||__LINK__||
Kentoto2021 said:
OKKK after one all day (9:30AM to 10:30PM) I finally get it !!!!!!! THANK YOU for your advice you saved my phone if I can say Djiban A look of my new version phone below, very happy !!! Now I have to find how to get Emui 8.X on my Honor 6.X without broken my phone
I really thought that my phone was broken because I didn't backup my OEM info with the Huawei MultiTool and ended into a bootanimation loop even restoring my phone with TWRP.
______________________________________________________________________________________
For those who is doing this awesome tutorial : https://forum.xda-developers.com/t/...ln-l22-successful-case-noob-friendly.3679402/ I attach here to my message the Huawei MultiTool v7 that I found on this forum too (but can't find the link in my browser history ) :
For this tool, don't connect to internet when you launch it to avoid auto update, you can enable it after the question about proxy or when you see the main menu. The only bad thing that it's not in english, but the screenshot in the tutorial show you what is what
For the OEM info zip, if you get "sbin/su not found" when restauring int the MultiTool , try also to install it with the traditional way in TWRP via the button Install -> Install ZIP
At the step where you have done the dload method with the update.zip, you will be get stuck in the bootanimation or black screen, it says that you have to shutdown the phone and that's a bit complicated with Honor 6x, you can only reboot whatever you done and adb acess from computer is off (don't activate the bootloader, it can reject the new update you just put in the dload folder !!!)
What I have done is going to Huawei eRecovery mode by pressing and maintaining Power button and Volume +, then choose wipe cache then wipe data/factory reset (it will erase all your data that you have on your last system !). By that, the phone will reboot and get you into the EMUI 5.X and the menu too set your phone, and by that you can rename the folder dload-data to dload through computer as mentionned in the tutorial, then SHUTDOWN your phone and redo the dload activation (Volume + and - and power button pressing)
And that's it ! Some tips to avoid future people stuck for hours and panic because nothing is working and the phone seems to be good for bin
Click to expand...
Click to collapse
WARNING : Once you update the OEM info of your phone, the Huawei eRecovery won't find update to factory reset the entire firmware ! So if the Huawei eRecovery tell you that the system is broken and you have to reset your phone (can't avoid that if it tells you that I think), after that the bootloader will be locked, then you can't go to TWRP recovery or start the OS.
DON'T PANIC, go into fasboot/bootloader by shutting down your phone(if can't, just reboot and do the following steps before the phone vibrates when reboot !) : Hold AND Keep VOLUME - , then plug the USB cable
Then on your computer, unlock the bootloader as you already done with the command : fastboot oem unlock THEBOOTLOADERCODE (The bootloader code will be the same whatever your firmware version is, it's unique for your phone harware)
3/ Update to EMUI 8.X BLN-L22HNC675 [Android 8.0]
Spoiler: 3/ Update to EMUI 8.X BLN-L22HNC675 [Android 8.0]
Here is the firmware finder database same as the previous step if you want to pick other version of your firmware
Online firmware database ⋆ TEAM MT Developers
< PREVIOUS FIND MODEL NEXT > Дата изменения Полное название Файлы обновления Размер Тип G g v f 2021.11.09 MED-LGRP2-OVS 10.1.0.195 filelist 0 OTA 1458 104 519745 3 2021.11.08 patch01 filelist 0 OTA 1458 104 525603 1 2021.11.08 TAS-LGRP1-CHN 11.0.0.170 filelist 0 OTA 1458 104 525098 1 2021.11.08...
pro-teammt.ru
- Here is the tutorial also made by the same author at the step 2 : ||__LINK__||
- Some UPDATE Links about this tutorial:
The HwOTA8 tools : ||__LINK__||
Make sure to keep HWOTA8_BLN folder inside HWOTA_BLN_Eng folder
HWOTA_BLN_Eng should be put inside the Tools folder of Huawei Multi-Tool v8
Make sure the path don't contain SPACE such as C:/Program Files
They are new update of the BLN-L22HNC675 (B520)
The newest one is : BLN-L22HNC675CUSTC675D2B520 (8.0.0.520) update on 2018.11.29
Search BLN-L22HNC675CUSTC675D here
You can upload the 3 zip on my pCloud (it's faster): ||__LINK__||
WARNING : On the first boot, wait 3-4 mins. The reboot to the EMUI 8.X can take some times
If after some minutes, nothing happen and you still on the blue Honor bootloop, try to wipe cache AND factory reset the phone via Huawei eRecovery or via TWRP (don't format data, only at the last resort but I think you have to reinstall the firware through HwOTA8 again). Have to be patient, it takes me 6-8 mins to reboot after wiping cache and data at the 2nd attempt.
- After successfully installed EMUI 8.X :
It's possible that you can't access TWRP, you have to reinstall TWRP Recovery through Huawei Multi-Tool (same step at the step 1/ Requirementsabove).
The tool will automaticcaly detect your device and propose you the BLN_TWRP_EMUI8.zip (press Flash Recovery_ramdisk with your phone open in android and allow the debugging connection - see 1/ Requirements for more informations.
Or you can download TWRP 3.2.X-0 (version 3.2.X only ! Other versions may not work, I didn't try it)
With this version, you will encounter some issue with TWRP. You can't wipe chache, or mount/unmount data for example, so some installtion through TWRP may not work, like for OpenGAPPS who maybe can't be installed when you want to try other Custom ROM like LineageOS. If you know how to install OpenKirin(LineageOS) on Honor 6x EMUI 8.X, feel free to share in this thread !
4/ Extend your RAM via SD Card
Spoiler: 4/ Extend your RAM via SD Card
If you succeed all those steps, you may right now see that your device maybe a little buggy, particularly when you open severals android application.
- For me, I used AParted available on the Play Store : ||__LINK__||
- This app require a rooted phone of course : Install Magisk ||__LINK__|| through TWRP Installation (Reboot to TWRP -> Install -> Install ZIP) or use SuperSU propose by Huawei MultiTool button installation
A PDF/Tutorial are available on the app inside, showing you the step to do with screenshot
WARNING : Save your data of your SD card before continue
You may not see big difference by increasing the RAM memory, it will just allow you to open more apps at the same times without crashing or lag
Summary of steps :
Tab CREATE -> press ADD 2 times (or more if you already have some partitions)
Set Part 1 as fat32 and give him his total storage
Set Part 2 as swap and give him his storage (will be for the RAM) (For me, I choose 2Go)
Click APPLY
Go to Tab TOOLS
Select Part 2 - FS: swap
Choose Swap in the drop down menu next to the button Apply
Press Apply
Watch a video (advertising if yo uconnected to internet)
Cancel the installation of AMemoryBoost
Click ON and OK to enable Swap Partition
Now you will saw the current RAM and the Swap memory
I wish my post can be helpful and I wish you can enjoy your new phone !!!
I can't wait to see new thread about an AOSP 11 on the honor 11 !

let us know which ROM you did try to install, and how you did solve. thx

Kentoto2021 said:
=> For future people who still want to know how I switch Honor 6x on EMUI 5.X to EMUI 8.X, I write just below the full step and problems that I met during this process (But I think there is already some thread that talk about this.
Click to expand...
Click to collapse
Below?

Kentoto2021 said:
I wish my post can be helpful and I wish you can enjoy your new phone !!!
I can't wait to see new thread about an AOSP 11 on the honor 11 !
Click to expand...
Click to collapse
thanks for this excellent and very complete guide. Hop too that @DarkJoker360 AOSP 11 system.img from Huawei P8 Lite forum will work as it did for march and July AOSP 10!!! I'll give i a try next week for sure :

After a succesfull debrand to BLN-L22 with the very fast way, I'm following your guide to step to EMUI 8, first of all thanks for providing files from your pcloud !!

Kentoto2021 said:
HWOTA_BLN_Eng should be put inside the Tools folder of Huawei Multi-Tool v8
Click to expand...
Click to collapse
You did use multi tool V8 to update to EMUI 8 ? Can see any signe of that in the guide you did follow . I guess it just replace the adb fastboot command .
All went fine for me, I'm now on very last EMUI 8 stock ROM for BLN-L22! thx
But of course TWRP flash is now an issue:
all TWRP recovery versions I fastbooted flash (3.1.1, 3.2.3, 3.5.0, all for bacon) sent me the same message error in fastboot: "FAILED (remote: partition lentgh get error)" . Apparently not EMUI 8 version .....

Oh nice wonderful !!! Happy it helps
I used the Multi Tools for the 3 step because it contains the adb and fastboot tools. But if you have it with the minimal adb software it will work also.
And if you set the adb folder to the windows 10 variable path system, I think you can put the HwOTA almost anywhere in the computer disk.
Yep indeed the twrp not work properly...
And still all my attempt to upgrade my OS with another method without the 3 zip (update, public, data) is not working

There is a workaround for custom recovery, I'll try it seriously and post back here

Kentoto2021 said:
Oh nice wonderful !!! Happy it helps
I used the Multi Tools for the 3 step because it contains the adb and fastboot tools. But if you have it with the minimal adb software it will work also.
And if you set the adb folder to the windows 10 variable path system, I think you can put the HwOTA almost anywhere in the computer disk.
Yep indeed the twrp not work properly...
And still all my attempt to upgrade my OS with another method without the 3 zip (update, public, data) is not working
Click to expand...
Click to collapse
U can try elite twrp,it worked perfectly fine for me

MAK7246 said:
U can try elite twrp,it worked perfectly fine for me
Click to expand...
Click to collapse
You mean this one:
[TWRP][3.2.1-0][EMUI5.X and AOSP][Decryption Support] For Honor 6X by HassanMirza01
Elite TWRP Project For Honor 6X DONOT COPY MY WORK, Ask for Permissions or Gather it yourself,,, This ROM is only for Firmwares based on EMUI 5.X only... /* * Your warranty is now void. * * We are not responsible for bricked devices...
forum.xda-developers.com
"for EMUI 5 only" on EMUI 8 ?

Djiban said:
You mean this one:
[TWRP][3.2.1-0][EMUI5.X and AOSP][Decryption Support] For Honor 6X by HassanMirza01
Elite TWRP Project For Honor 6X DONOT COPY MY WORK, Ask for Permissions or Gather it yourself,,, This ROM is only for Firmwares based on EMUI 5.X only... /* * Your warranty is now void. * * We are not responsible for bricked devices...
forum.xda-developers.com
"for EMUI 5 only" on EMUI 8 ?
Click to expand...
Click to collapse
Yep that is working fine!

MAK7246 said:
Yep that is working fine!
Click to expand...
Click to collapse
thanks, I'll use it for making a nandroid backup. Right afterward I'll install TWRP recovery from pretoriano80 (https://mega.nz/#!LLhBXSzY!3runNNoW9z1tOHSu-heIUhyy-4u8XHvc8rZMsn547so ou https://eu.dl.twrp.me/prague/) because I plan to try ton install @DarkJoker360 AOSP 11 for P8Lite.

Djiban said:
thanks, I'll use it for making a nandroid backup. Right afterward I'll install TWRP recovery from pretoriano80 (https://mega.nz/#!LLhBXSzY!3runNNoW9z1tOHSu-heIUhyy-4u8XHvc8rZMsn547so ou https://eu.dl.twrp.me/prague/) because I plan to try ton install @DarkJoker360 AOSP 11 for P8Lite.
Click to expand...
Click to collapse
Let me know if u are successful!

[Fluid OS][Android 11] Guide to install Fluid OS on Huawei Honor 6X

POST - v3
(This number will increase every time the post is updated.)​What's new in v3?
Added procedure in a new spoiler to install the base EMUI 8 for hi6250 devices as using the EMUI 8 we get with our device is causing some errors and bugs. Thanks to @Kentoto2021 and @VarianWrynn for testing and reporting this problem.
Spoiler: Version Changelog
What's new in v2?
Updated the thread with newly found bugs in "What isn't working" section.
Made small changes to thread.
What's new in v1?
Took a lot of time to collect the infinity stones.
Took even longer to make Mr. Thanos snap this thread to existence.
What's new in v0?
LoL Who knows?
This ROM is none of my work. I just tested it and provided appropriate procedure and fixes to errors(Found nothing yet).
Thanks a ton to @Hami_Do for making this possible. Original Post : link.
Thanks to Huawei for making their phones nearly unbrickable .
Thanks again to Huawei for making more than one device with hi6250 chipset.
Thanks a lot to @Djiban for helping me and testing different procedures, fixes and ROMs.
Follow this thread only if you know what you're doing. I'm not responsibe for any damage or thermonuclear wars .
Read the post completely and understand it before doing anything ATLEAST FOR THE SAKE OF MANKIND .
This thread is best viewed in PC and is Noob Friendly.​
Spoiler: Requirements
Requirements:
Huawei Honor 6X (Unlocked Bootloader. If not, follow this post (using PotatoNV) or YouTube video.
EMUI 8 (If not, you could follow this guide, direct file : link).
GSI from link.
TWRP from attachments or link or any other TWRP recovery compatible with Honor 6X EMUI 8.
Gapps(Optional, I used pico OpenGapps).
stock recovery (available in attachments).
Time.
PC.
ADB and Fastboot.
Patience.
Human Brain.
ALL IN ONE GUIDE : Check it out here. It contains every thing in detail all the way from bricked device -> EMUI 2 -> EMUI 5 -> EMUI 8 -> AOSP 10. Thanks to @lmaohelp for his effort and describing everything in detail.
Useful Information :
What is OpenGapps? Check it out at OpenGapps.org!
What is ARM64? it is a 64 bit operating system/platform.
What isn't working :
Usb Notification (Options will be greyed out. To transfer files, go to Developer Options > Default USB configuration > set it to File Transfer).
Dual sim is buggy. Single sim works perfectly. Thanks to @Loopeez for reporting it.
What's Working :
Everything.
*Tell me if something isn't working.
***If you have a bricked device/messed up somewhere during the process and unable to figure out what to do, follow this guide by @lmaohelp .***
Spoiler: Installing base EMUI 8 for hi6250 devices.
This was already described in a separate thread which describes the process to get back to EMUI 8 from custom ROMs. You can find it here.
Just follow the procedure in that thread. You need not even flash the frp unlock thing. After that, follow the process described in this thread.
It's recommended to be on original EMUI 8 before installing base EMUI 8 for hi6250. Follow the process linked in requirements to install EMUI 8 first then follow this spoiler.
Procedure :
Make sure your device is running stock EMUI 8.
Extract downloaded image using some xz extractor(7zip can also do this), copy it to pc.
Reboot your device to TWRP.
Format the data partition {Wipe > Format data > type "yes"}
Flash fstab.hi6250b.zip from attachments
Check if your device is detected by adb using
Code:
adb devices
.
Move the img file using adb to device
Code:
adb push -p *img-name*.img /sdcard/
(the img file must be in adb directory).
(Optional, only if you want gapps) Move Gapps in the same manner
Code:
adb push -p *gapps-name*.zip /sdcard/
(the zip file must be in adb directory).
Install img as system image {Install > Install Image > Select > Choose system image > Swipe➡}.
(Optional, only if you want gapps) Unmount and Remount system partition as writable. Go to wipe > advanced wipe > Choose system > resize > Swipe➡.
Flash gapps.
Flash stock recovery. Push it with adb using
Code:
adb push -p stock_recovery_ramdisk.img /sdcard/
and flash it with twrp as "Recovery" after choosing install image.
Disconnect your device from PC and reboot to recovery(stock one).
Clear cache partition and perform a factory reset(You'll get an error during factory reset but you have to do it) (your device will bootloop if wiped with twrp itself).
Reboot, Cross your fingers and wait.
>Booting is quite different in android 11 ROMs on our device. You'll see the "Your device has been unlocked" screen for more time than usual. Then, you'll see the boot animation (for very short time on subsequent boots) and the device will boot to ROM. So, be patient. (This isn't the case with ROMs upto android 10)
>Face Unlock is working perfectly
Spoiler: Additionals
Additionals:
>Its better to charge your device to atleast 70% before doing anything as you'll have ample of time to recover it if you messed up something. If not, you can still charge your device in eRecovery mode and twrp but i found some issues like heating up and slow charging.
>Don't forget to set ringtone, notification and other sounds from settings after booting.
Spoiler: Updates
Updates :
Nothing yet...
Happy Flashing !
{
"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"
}

RESERVED​

Thx for keep looking for the best andorid 11 rom for Honor 6X. Installed it, no issue so far, testing it as a 2nd daily device. Let you know...
Below is my installation procedure using a microsdcard, quite the same as post #1 apart of that.
- on a micro SD card, download:
https://forum.xda-developers.com/attachments/twrp-img.5326857/
https://sourceforge.net/projects/darkjoker360-developements/files/Huawei/fstab.hi6250b.zip/download
https://forum.xda-developers.com/attachments/stock_recovery_ramdisk-img.5321325
FluidOS-1.1-Rum-R-Hi6250-emui8.img extracted with 7zip from https://mega.nz/#!jWQWEJ7Z!cd2S5oy2g8IdUuw5PfQEkSadslojBpFgB6ltUNOpc-w
OPTIONAL: pico gapps from https://sourceforge.net/projects/opengapps/files/arm64/test/20210110/
- insert the micro SD card in your usb debugging enabled Honor 6X (with EMUI 8 or custom rom installed over EMUI8), and connect it to a PC with adb & fastboot
- in adb, "adb reboot bootloader"
- in fastboot, "fastboot flash recovery_ramdisk TWRP.img"
- in fastboot, "fastboot reboot"
- after reboot completed, "adb reboot recovery"
- disconnect the honor 6x from the PC
- in TWRP recovery, Format the data partition {Wipe > Format data > type "yes"}
- in TWRP recovery, flash fstab.hi6250b.zip
- in TWRP Recovery, flash FluidOS-1.1-Rum-R-Hi6250-emui8.img {Install > Install Image > Select > Choose system image > Swipe}
- OPTIONNAL IF GAPPS WANTED: in TWRP recovery, Mount system partition (Mount > check system and unckeck read only OR reboot in recovery).And
resize system (Go to wipe > advanced wipe > Choose system > repair > resize). Then install open_gapps-arm64-11.0-pico-XXXXXXX.zip.
- in TWRP Recovery Flash STOCK_RECOVERY_RAMDISK.img {Install > Install Image > Select > Choose recovery image > Swipe}
- in TWRP recovery, reboot to recovery (even if TWRP says no OS installed)
- in Stock recovery, wipe cache and factory reset (error is normal)
- in Stock recovery, reboot and wait
Click to expand...
Click to collapse

Rom is very nice so far , no issue yet!!!!

Djiban said:
Rom is very nice so far , no issue yet!!!!
Click to expand...
Click to collapse
Same with me.

Hello, do you know how can I factory reset in the Huawei ERecovery step at the end ?
I try to do it so but it keep reboot my phone to TWRP recovery, it's like I can't wipe data/factory reset my phone from the stock recovery.
Maybe TWRP is bloking it ? Should I disable something in the TWRP settings ?
Between thanks for yours work !

Kentoto2021 said:
Hello, do you know how can I factory reset in the Huawei ERecovery step at the end ?
I try to do it so but it keep reboot my phone to TWRP recovery, it's like I can't wipe data/factory reset my phone from the stock recovery.
Maybe TWRP is bloking it ? Should I disable something in the TWRP settings ?
Between thanks for yours work !
Click to expand...
Click to collapse
Your mistake is that your using stock erecovery.
You have to use stock recovery. Meaning flashing the stock recovery provided in post 1 over the twrp recovery :
- in TWRP Recovery Flash STOCK_RECOVERY_RAMDISK.img {Install > Install Image > Select > Choose recovery image > Swipe}
- in TWRP recovery, reboot to recovery (even if TWRP says no OS installed)
- in Stock recovery, wipe cache and factory reset (error is normal)
- in Stock recovery, reboot and wait

Yep thanks, I forget to choose Recovery when I flash the stock recovery ramdisk, so my twrp install it on the last choice that it's system image
To resolve my problem I reinstall my previous system (EMUI 8 for honor 6x) and this time I wipe the david cache, system, cache ... after format the data partition
And I didn't install any OpenGAPPS and it works fine !
A little empty, but I will try without Google services to see if it sweet to me, it saved a lot of battery so that's nice !
Again, I thank you all of you for your amazing work thank you very much my honor 6x can still live haha
Edit : no it's too painfull without google services haha

Kentoto2021 said:
Yep thanks, I forget to choose Recovery when I flash the stock recovery ramdisk, so my twrp install it on the last choice that it's system image
To resolve my problem I reinstall my previous system (EMUI 8 for honor 6x) and this time I wipe the david cache, system, cache ... after format the data partition
And I didn't install any OpenGAPPS and it works fine !
A little empty, but I will try without Google services to see if it sweet to me, it saved a lot of battery so that's nice !
Again, I thank you all of you for your amazing work thank you very much my honor 6x can still live haha
Click to expand...
Click to collapse
Perform a factory reset after flashing gapps too.
Flashing gapps without factory reset crashed chromium based browsers on AOSP 10. This might not be the case with this rom but better do it.

Kentoto2021 said:
Yep thanks, I forget to choose Recovery when I flash the stock recovery ramdisk, so my twrp install it on the last choice that it's system image
To resolve my problem I reinstall my previous system (EMUI 8 for honor 6x) and this time I wipe the david cache, system, cache ... after format the data partition
And I didn't install any OpenGAPPS and it works fine !
A little empty, but I will try without Google services to see if it sweet to me, it saved a lot of battery so that's nice !
Again, I thank you all of you for your amazing work thank you very much my honor 6x can still live haha
Edit : no it's too painfull without google services haha
Click to expand...
Click to collapse
Android without Google services is more and more easy.
Aurora market is a good choice.
I have also some workaround for'GPS localisation and so....

Nevertheless, gapps working fine for me, no device lag cause of it ! All services active and working

Djiban said:
Nvertheless, gapps working fine for me, no device lag cause of it ! All services active and working
Click to expand...
Click to collapse
Same with me. And the power menu controls are just AWESOME.

Dang, I cannot go past installing Huawei USB COM driver to unlock my device (

jottect said:
Dang, I cannot go past installing Huawei USB COM driver to unlock my device (
Click to expand...
Click to collapse
? Didn't get you... Did you mean bootloader unlock? If yes, follow @lmaohelp 's guide mentioned in post 1. He described it very clearly.

Venkata Lochan Nune said:
? Didn't get you... Did you mean bootloader unlock? If yes, follow @lmaohelp 's guide mentioned in post 1. He described it very clearly.
Click to expand...
Click to collapse
Yes, it's clear, read the posts, watched YT video, but one of the steps is installing Huawei USB COM driver to replace the SER driver, and I already tried on 2 computers, Windows 10 (updated) fails to install that driver, and without it, PotatoNV won't 'see' the device.

Venkata Lochan Nune said:
Same with me. And the power menu controls are just AWESOME.
View attachment 5337621
Click to expand...
Click to collapse
Oooh how did you get that ?
I only have this :
Is it Gapps ? I use the nano one

Kentoto2021 said:
Is it Gapps ? I use the nano one
Click to expand...
Click to collapse
Nope, there's an app on play store called "power menu controls" download that. And the other, you could use Tasker(also an app from play store) to create your custom controls like the ones I did for screen rotation.

jottect said:
Yes, it's clear, read the posts, watched YT video, but one of the steps is installing Huawei USB COM driver to replace the SER driver, and I already tried on 2 computers, Windows 10 (updated) fails to install that driver, and without it, PotatoNV won't 'see' the device.
Click to expand...
Click to collapse
what's the procedure you followed to install drivers?
Unzip the attached file, and choose "DriverSetup.exe" and that's it. uninstall these drivers after installing the rom using "DriverUninstall.exe" for mtp to work. The process will ask for reboot in some language(i think Chinese) after uninstalling but it isn't needed.
*These are also the fastboot drivers(but the name in attachments is testpoint drivers).

Kentoto2021 said:
Edit : no it's too painfull without google services haha
Click to expand...
Click to collapse
Indeed! I once tried using AOSP 10 with floss services and without Google ones but yeah it didn't last even a day... lol I flashed gapps within 5 hrs.

Venkata Lochan Nune said:
what's the procedure you followed to install drivers?
Unzip the attached file, and choose "DriverSetup.exe" and that's it. uninstall these drivers after installing the rom using "DriverUninstall.exe" for mtp to work. The process will ask for reboot in some language(i think Chinese) after uninstalling but it isn't needed.
*These are also the fastboot drivers(but the name in attachments is testpoint drivers).
Click to expand...
Click to collapse
Thanks a million! It worked., I just unlocked the bootloader, I did not have these drivers.
Now onto next steps... may take a while, I'm old and slow
Well, did not go too far... when trying to flash twrp (as per this guide:
), I'm getting an error:
fastboot flash recovery_ramdisk twrp.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24466 KB)...
OKAY [ 0.642s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished.
Ideas?
P.S. I also tried
fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (24466 KB)...
OKAY [ 0.642s]
writing 'recovery'...
FAILED (remote: image verification error)