Database Info

Any way to encrypt /data/data and /sdcard on Xiaomi EU ROM?

Hello,
Xiaomi EU ROM is running decrypted, that's a security breach...
Is there a way to use Xiaomi EU ROM, based on Miui 10, in a encrypted phone?
Thanks

I tried but no success. The only method to enable encryption is miflash official rom. For me it works perfectly in Los. Apparently xiaomi Eu removed encryption from vendor.

And there is no way to add the files to the vendor partition?

I am using the EU ROM for months encrypted (FBE).
It's a little complicated to get there (and to stay), but it can be done.
1. You need to come from an encrypted MIUI Rom
2. Enter TWRP, enter your decryption code.
Important note: NEVER format in TWRP, otherwise you'll have to start from MIUI again (which means flashing with MiFlash).
4. Dirty flash EU Rom. Do NOT reboot.
5. After flashing the ROM, go to the main menu in TWRP and mount the Vendor partition.
6. Install the attached Zip file with TWRP (copy to phone before starting the whole procedure steps)
7. Reboot
As I said I followed this procedure for the last months, running EU and still encrypted.
You have to do ALL the steps 2-7) again EVERYTIME you flash a new EU Rom.

Hello,
Thanks for the answer. I will try it, but...
1) After flash this, I can wipe device (not format) from TWRP?
2) Is also /sdcard encrypted or only /data/data?
3) I can't install Global MIUI from TWRP if I will return to Global?
4) I assume that I can install Magisk after 6 and before 7
Thanks
hoehm72 said:
I am using the EU ROM for months encrypted (FBE).
It's a little complicated to get there (and to stay), but it can be done.
1. You need to come from an encrypted MIUI Rom
2. Enter TWRP, enter your decryption code.
Important note: NEVER format in TWRP, otherwise you'll have to start from MIUI again (which means flashing with MiFlash).
4. Dirty flash EU Rom. Do NOT reboot.
5. After flashing the ROM, go to the main menu in TWRP and mount the Vendor partition.
6. Install the attached Zip file with TWRP (copy to phone before starting the whole procedure steps)
7. Reboot
As I said I followed this procedure for the last months, running EU and still encrypted.
You have to do ALL the steps 2-7) again EVERYTIME you flash a new EU Rom.
Click to expand...
Click to collapse

I reply my questions:
After flash EU ROM and the ZIP that @hoehm72 in the previous posts, the EU ROM is working fine.
You can wipe the device from TWRP and also return to Global version (you need to backup your /cust partition before flash EU for first time and restore /cust before flash Global ROM).
Also, /sdcard and /data/data remains encrypted in EU, like in Global.
Thanks mate!
EDIT: If you forgot to flash the zip file after flash EU ROM the phone will enter in a bootloop. No problem, you only need to enter TWRP then:
* mount vendor
* edit /vendor/etc/fstab.qcomm
then update "encryptable" by "fileencryption" then reboot...

Thank you, it worked for me too!

Hello how can I know if my rom is encrypted ?

If your device is rooted...
enter TWRP and, when TWRP asks for password click on cancel button.
Next, click on advanced -> file manager then navigate to /sdcard
If when you are on /sdcard (and also on /data/data) the file manager displays correctly the filenames you aren't encrypted and any can access to the files if has access to your device.
Bradco said:
Hello how can I know if my rom is encrypted ?
Click to expand...
Click to collapse

Bradco said:
Hello how can I know if my rom is encrypted ?
Click to expand...
Click to collapse
You can find it in settings-passwords&security- data privacy(or data security, I don't know in english) -encryption

The most secure mode to check it is to check over twrp, like I've explained.
Some roms, like eu, says encrypted but really aren't
Seosam said:
You can find it in settings-passwords&security- data privacy(or data security, I don't know in english) -encryption
Click to expand...
Click to collapse

This is what i posted some thime ago in xiaomi.eu forum.
I downloaded miui_MIMIX2SGlobal_V10.3.2.0.PDGMIXM_7e27e6e0d5_9.0.zip and xiaomi.eu_multi_MIMix2S_V10.3.1.0.PDGCNXM_v10-9.zip
than i extracted these folder and three files from global rom:
firmware-update
vendor.transfer.list
vendor.new.dat.br
vendor.patch.dat
than i deleted those three files and folder from xiaomi.eu rom
than i repacked xiaomi.eu rom with three vendor files from global rom (i used winrar, just drag and drop )
than i installed .zip on my phone
I managed to encrypt the latest (9.7.11) version too. You need to use vendor files from china beta (9.7.11). If you use older files your wifi wont work.

A less painful solution is to extract missing files from china rom
The file lists that should be added/replaced from china miui rom (about 3 MB, tested on Mi6 10.4.2.0, eu/cn):
Ps., some of below files are not necessary, but I am not sure which one did the trick.
/system/vendor/etc/gps.conf
/system/vendor/etc/mixer_paths_overlay_dynamic.xml
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/izat.conf
/system/vendor/etc/wifi/WCNSS_qcom_cfg.ini
/system/vendor/etc/fstab.qcom
/system/vendor/app/TrustZoneAccessService/TrustZoneAccessService.apk
/system/vendor/app/TrustZoneAccessService/oat/arm64/TrustZoneAccessService.odex
/system/vendor/app/TrustZoneAccessService/oat/arm64/TrustZoneAccessService.vdex
/system/vendor/app/ConnectionSecurityService/oat/arm64/ConnectionSecurityService.odex
/system/vendor/app/ConnectionSecurityService/oat/arm64/ConnectionSecurityService.vdex
/system/vendor/app/PowerOffAlarm/oat/arm64/PowerOffAlarm.vdex
/system/vendor/app/PowerOffAlarm/oat/arm64/PowerOffAlarm.odex
/system/vendor/app/PowerOffAlarm/PowerOffAlarm.apk
/system/vendor/app/SSGTelemetryService/oat/arm64/SSGTelemetryService.odex
/system/vendor/app/SSGTelemetryService/oat/arm64/SSGTelemetryService.vdex
/system/vendor/app/TimeService/oat/arm64/TimeService.odex
/system/vendor/app/TimeService/oat/arm64/TimeService.vdex
/system/vendor/app/TimeService/TimeService.apk
/system/vendor/lib/mediadrm/libdrmclearkeyplugin.so
/system/vendor/lib/mediadrm/libwvdrmengine.so
/system/vendor/lib/libmmcamera_imx386_semco.so
Obviously, in android 9 based miui 10, xiaomi.eu has removed encryption files from vendor, not just modified "fstab.qcomm".
On Mi6 10.4.2.0, I successfully encrypted /sdcard/ with above files.

In fact, you only need to replace fstab.qcomm at vendor/etc from the one included at eu miui from the one at stock rom.
This file as a size if 2KB
watert said:
Sorry, but I will add the file lists that should be added/replaced from china miui rom in hours later (about 3 MB).
Click to expand...
Click to collapse

Modification of "vendor/etc/fstab.qcomm" worked on android 8 based xiaomi.eu's miui, but not for android 9 based xiaomi.eu's miui -- at least for MI6.
If you only modify fstab.qcomm, but do not copy files which actually did the encryption job, encryption is fake (although it showed encrypted on "setting"). Check this by : goto twrp, click 'cancel' when it asks for gesture, then you would find you can still access files on /sdcard/ (without encryption).
bartito said:
In fact, you only need to replace fstab.qcomm at vendor/etc from the one included at eu miui from the one at stock rom.
This file as a size if 2KB
Click to expand...
Click to collapse

I have only modified fstab file and my device is encrypted (see screenshot).
The only that you need to do it not to do a format data under twrp after install EU ROM.
This is due the phone encryption will be done in global ROM. EU is not capable to do it even with the modified fstab, 9nly that can do is to manage a previously encrypted partition.
watert said:
Modification of "vendor/etc/fstab.qcomm" worked on android 8 based xiaomi.eu's miui, but not for android 9 based xiaomi.eu's miui.
If you only modify fstab.qcomm, but do not copy files which actually did the encryption job, encryption is fake (although it showed encrypted on "setting"). Check this by : goto twrp, click 'cancel' when it asks for gesture, then you would find you can still access files on /sdcard/ (without encryption).
Click to expand...
Click to collapse

Yes, that is one way. but I'd like to format/wipe everything in twrp before flashing.
If data partition was formated, I think ~3 MB files from china rom are necessary for encryption.
bartito said:
I have only modified fstab file and my device is encrypted (see screenshot).
The only that you need to do it not to do a format data under twrp after install EU ROM.
This is due the phone encryption will be done in global ROM. EU is not capable to do it even with the modified fstab, 9nly that can do is to manage a previously encrypted partition.
Click to expand...
Click to collapse

Please, post the files when possible. I will check. Thanks
watert said:
Yes, that is one way. but I'd like to format/wipe everything in twrp before flashing.
If data partition was formated, I think ~3 MB files from china rom are necessary for encryption.
Click to expand...
Click to collapse

hoehm72 said:
I am using the EU ROM for months encrypted (FBE).
It's a little complicated to get there (and to stay), but it can be done.
1. You need to come from an encrypted MIUI Rom
2. Enter TWRP, enter your decryption code.
Important note: NEVER format in TWRP, otherwise you'll have to start from MIUI again (which means flashing with MiFlash).
4. Dirty flash EU Rom. Do NOT reboot.
5. After flashing the ROM, go to the main menu in TWRP and mount the Vendor partition.
6. Install the attached Zip file with TWRP (copy to phone before starting the whole procedure steps)
7. Reboot
As I said I followed this procedure for the last months, running EU and still encrypted.
You have to do ALL the steps 2-7) again EVERYTIME you flash a new EU Rom.
Click to expand...
Click to collapse
For me this works with actual miui eu.
I checked it in TWRP too.
But maybe you need these 3MB when you do a clean start, without official miui first.

Seosam said:
For me this works with actual miui eu.
I checked it in TWRP too.
But maybe you need these 3MB when you do a clean start, without official miui first.
Click to expand...
Click to collapse
absolutely agree

[TWRP] TWRP 3.4-0-0 For Blu G90 G0310WW [MT6765][Android 10]

First released twrp for BLU G90 phone.
Whats working:
Adb
Mtp
USb-OTG
MicroSD
Flash Image
Mount System , Vendor, product (contents of SUPER).... mount allows reading the partitions, but was not able to write to them
Back-Up/Restore to/from usb (or micro sdcard).... Due to size of super.img needed to format card ext4
Logcat
Screenshot
Known bug:
**Solved with new tree file**--data decryption is not working, so not able to read or backup internal storage.--
Built with Minimum Manifest _branch 10.0 :
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
Kernel source :
https://github.com/mrmazakblu/Blu_G90_G0310WW_stock_kernal
Device Tree :
New
GitHub - mrmazakblu/device_PBRP_BLU_G90_G0310WW at TWRP
Contribute to mrmazakblu/device_PBRP_BLU_G90_G0310WW development by creating an account on GitHub.
github.com
Download :
Releases · mrmazakblu/device_PBRP_BLU_G90_G0310WW
Contribute to mrmazakblu/device_PBRP_BLU_G90_G0310WW development by creating an account on GitHub.
github.com
Old
https://github.com/mrmazakblu/device_TWRP_BLU_G90_G0310WW
Download : https://github.com/mrmazakblu/device_TWRP_BLU_G90_G0310WW/releases

ADB Sideload is also broken.

Shananiganeer said:
ADB Sideload is also broken.
Click to expand...
Click to collapse
Most likely due to no able to read/ write to /data there is no place to temp store the zip.
Working on alternative options at the moment, as I am having trouble getting build correct to make decrypt.
Alternative is a modified /vendor.img, so device is not encrypted. But this of course is less secure.

I reformatted /data so it was unencrypted, but still couldn't use adb sideload. I was able to use adb push to put files onto the phone, but that didn't end up mattering as without rw to /system I can't install gapps XD. I'll have some time this weekend to take a look at things and try and help debug the decryption.

Appearently, this build is only missing data decryption.
Spoke with TWRP maintainer, they said this is working as intended. Super.img partitions are not currently meant to be mounted as r/w.
After I asked about flashing GApps, I was informed that there might be changes to TWRP source to allow mounting as r/w sometime sooner or later.

mrmazak said:
Appearently, this build is only missing data decryption.
Spoke with TWRP maintainer, they said this is working as intended. Super.img partitions are not currently meant to be mounted as r/w.
After I asked about flashing GApps, I was informed that there might be changes to TWRP source to allow mounting as r/w sometime sooner or later.
Click to expand...
Click to collapse
so it may seem we are waiting on how to affectively be able to modify the dynamic partitions before we can see a fully successful root. I am fairly new to these things so might be looking at it wrong.

Ivisibl3 said:
so it may seem we are waiting on how to affectively be able to modify the dynamic partitions before we can see a fully successful root. I am fairly new to these things so might be looking at it wrong.
Click to expand...
Click to collapse
To modify it "live" yes maybe.
You can modify the extracted system, as I did , using linux mount, and flash the system back modified, just like a gsi rom.
But for root, can't say.

On the latest build, was able to mount /system r/w. And successfully change the contents of it.
The patches in twrp source is not finished yet, so normal zip installs are not coded. But using adb shell (or TWRP terminal ) seem to be working.
This New build to be uploaded on github device source, as release "test build 9"

I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)

johnsag49 said:
I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)
Click to expand...
Click to collapse
Well, the first thing I'm concerned with here is , I'm not sure if THIS TWRP will work on the g90 pro.
But it might be possible. I was able to mount system as r/w on my g90 in TWRP.
You would need to fastboot flash --disable-verity vbmeta and vbmeta_system to prevent red state bootloader lockout.

Ok I've found one potential bug and have a question you may be able to answer. With your build of TWRP I cannot access fastbootd. Running adb/fastboot reboot fastboot just puts me back into recovery. To change images I've been doing the following:
1. Enter bootloader and flash stock recovery you provided in your other G90 thread
2. Enter fastbootd and flash the image
3. Re-enter bootloader and flash twrp
The question I have is, how can the super partition be increased? I tried to flash the LOSQ build with gapps, but the image is > half the size of the super partition. I want to take 1GB away from the userdata partition and add it to the super partition instead. Do I mount the stock super.img in Linux and modify it to be 5GB, adjust the partitions on the eMMC so the new img will fit, flash the new super.img from bootloader, and then go into fastbootd and flash LOSQ? Where does modifying BoardConfig.mk with the new size fit in? If you don't know or don't wanna bother answering that's cool, I've been doing some digging trying to get to the bottom and I'm just not understanding how to adjust the new dynamic partition scheme.

Shananiganeer said:
Ok I've found one potential bug and have a question you may be able to answer. With your build of TWRP I cannot access fastbootd. Running adb/fastboot reboot fastboot just puts me back into recovery. To change images I've been doing the following:
1. Enter bootloader and flash stock recovery you provided in your other G90 thread
2. Enter fastbootd and flash the image
3. Re-enter bootloader and flash twrp
The question I have is, how can the super partition be increased? I tried to flash the LOSQ build with gapps, but the image is > half the size of the super partition. I want to take 1GB away from the userdata partition and add it to the super partition instead. Do I mount the stock super.img in Linux and modify it to be 5GB, adjust the partitions on the eMMC so the new img will fit, flash the new super.img from bootloader, and then go into fastbootd and flash LOSQ? Where does modifying BoardConfig.mk with the new size fit in? If you don't know or don't wanna bother answering that's cool, I've been doing some digging trying to get to the bottom and I'm just not understanding how to adjust the new dynamic partition scheme.
Click to expand...
Click to collapse
The stock /product partition is not needed in non stock roms. Google gsi flashing guide tells show to delete logical partition product.
Code:
fastboot delete-logical-partition product
This is probably what is needed.
Don't know about your plan to increase stock super.img. no idea about why you mention boardconfig.mk

This TWRP is before the patch for TWRP fastbootd, so it is not included. I have resynced source, and will see if new build works, or not. If it does will post new release.

I mentioned BoardConfig.mk because the size of the super partition is listed there, but you were totally right about the product partition and I was able to flash LOSQ+gapps after deleting it. Thanks for the assist, and your work on porting TWRP to this awesome device! Will continue to keep an eye on your work as TWRP finalizes their support for Android 10.

Will this work for the G90 Pro? My guess is not but figured I'd ask

KryptekKnight said:
Will this work for the G90 Pro? My guess is not but figured I'd ask
Click to expand...
Click to collapse
I assume not. But if you send device stock recovery, I can try to bring it up. But cannot test it, I don't have the device.

mrmazak said:
I assume not. But if you send device stock recovery, I can try to bring it up. But cannot test it, I don't have the device.
Click to expand...
Click to collapse
Would you be able to compile a Gcam pretty for this phone? I would be willing to supply you with whatever is within my means to provide

KryptekKnight said:
Would you be able to compile a Gcam pretty for this phone? I would be willing to supply you with whatever is within my means to provide
Click to expand...
Click to collapse
I have no idea about gcam

johnsag49 said:
I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)
Click to expand...
Click to collapse
Sorry OP.....
I need to get 01 post of your topic to report on custom recoveries on the G90 Pro.
For new users, you should know about the Android 10 permission structure.
In TWRP or PBRP, through the File Manager, it is not possible to copy files to the superpartition. But you can copy files from the superpartition to the internal SD card.
Therefore, to modify files from the super partition, it will be necessary to extract the super partition and extract system-product-vendor to then carry out the modifications and repackage.
Using Havocv3.11 the volume issue dissapears...........

Well all, thanks to @lopestom , we may soon have a new device tree to build recovery from , and data decryption is working on first test img. New recovery would be pbrp instead of twrp.

Problems after Magisk update - can only enter download mode and recovery

Hey there,
I am currently struggeling with my Samsung Galaxy S7 (Exynos) device, running on superman rom (Android 8).
What happened?
For root I´m using Magisk Manager and for banking apps I have Magisk hide running. Then the program told me that there is an update (Magisk App) available. So, as always and recommended, I choosed "Direct Install" but that failed for some reason. OK I thought´, no problem. Later I wanted to reboot my phone but it didn´t. The screen says "Downloading.... Do not turn off device!". I only can enter "Download Mode" and "Recovery Mode via TWRP".
What I tried so far:
1) Wipe cache/dalvik --> not successful
2) Tried to do a factory reset via twrp --> not successful
3) Tried to flash BL via Odin --> not successful
At this time I realised that the same problem occured to my Galaxy Tablet SM-T580. So I came to the point that I did something wrong with updating magisk on both devides.
What I also tried next:
4) Tried to delete magisk modules via twrp --> not successful
5) Tried to uninstall magisk through twrp by downloading the latest Magisk app and rename it to "uninstall.zip" as recommended in installation guide --> Not successful because of Error installing zip file: Unsupported /Unknown image format (unpacking image format)
What can I do next?
Can anyone please help me, since I have two bricked devices now????

A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.

Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
Mohamedkam000 said:
A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
Click to expand...
Click to collapse
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Mohamedkam000 said:
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.
Click to expand...
Click to collapse
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.

capitarider said:
Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.
Click to expand...
Click to collapse
Glad your tablet revived again.
Magisk creates a backup of the boot.img found just before flashing magisk, it is compressed in gzip format, so you need to pull it, extract it, and push it back to the phone, then flash it.
The file is usually in /data/stock_boot_${SHA1}.img.gz
You can extract it using the built-in terminal of TWRP, if PC is not accessible at the moment by writing and executing the following command:
gunzip {stock-boot-name}.gz
Replace {stock-boot-name} with your backed-up boot name (without the curleybrackets), or you can use the following command:
gunzip *.gz
That'll extract the gzip archive, and the boot.img will be in /data of which you can navigate to it and flash it.
There's another guaranteed method, if you have the file of the ROM you're using right now, you can just open it (it's just a zip archive) and search for the boot.img of your specific phone model and flash it.
Another guaranteed method will be by flashing a custom kernel compatible with your current ROM, like Moro AiO kernel, of which has a wide support for ROMs starting from Oreo, and up to Q, AOSP, or stock-based, just in one file.
Moro's thread: Moro Kernel

you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot

aIecxs said:
you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot
Click to expand...
Click to collapse
Doesn't seem like he's encrypted, he found the boot backup of his tablet in /data so he has probably searched for a similar file on his S7, but since it is compressed, he won't find it solely.
Also he would've told us that his /data is empty or something.

start from scratch with older magisk, current 22 has bug
https://github.com/topjohnwu/Magisk/issues/4008

Thank you for your help.
I had a n old twrp backup on another external hard drive. I extracted the boot file and repached it with 7zip to boot.img and flashed through twrp. That also didn´t work for various times. TWRP always said "failed".
In the end I didn´t manage it to bring my phone back to live. Anyway, I decided to flash the latest LineageOS (Android 11) and now its running smooth again.
Thanks again.

Try using sp flash tools flashing the boot.img

General Official OnePlus 9 Oxygen to Color and back

hi everyone
I got the official firmware
How to install?
1.Download firmware
2.Put the file in the phone directory
3. Open system update, select local update
Warning！
1.Please backup your data！
2.imei cannot be recognized correctly
##Back to oxygen os can be restored
##The official said the later ota repair
3.Flashing into coloros will generate a new partition
my_product
my_engineering
my_stock
my_heytap
my_company
my_carrier
my_region
my_preload
my_manifest
After you return to oxygen os，You can use fastboot to clear these partitions
For example
fastboot resize-logical-partition my_product 0
Download link：
click me

jizzboss said:
hi everyone
I got the official firmware
How to install?
1.Download firmware
2.Put the file in the phone directory
3. Open system update, select local update
Warning！
1.Please backup your data！
2.imei cannot be recognized correctly
##Back to oxygen os can be restored
##The official said the later ota repair
3.Flashing into coloros will generate a new partition
my_product
my_engineering
my_stock
my_heytap
my_company
my_carrier
my_region
my_preload
my_manifest
After you return to oxygen os，You can use fastboot to clear these partitions
For example
fastboot resize-logical-partition my_product 0
Download link：
click me
Click to expand...
Click to collapse
Done, from ColorOS to OxygenOS.

Reported

Hi,
I have an OnePlus 9, bought in China, with ColorOs.
Followed the instructions, downloaded the file, copied it to the mobile directory, and it worked perfectly. I just had to update the ColorOS first.
After that I manage to recover all my apps and information from my OnePlus 6.
Just perfect!
Thank you

lilz23 said:
Hi,
I have an OnePlus 9, bought in China, with ColorOs.
Followed the instructions, downloaded the file, copied it to the mobile directory, and it worked perfectly. I just had to update the ColorOS first.
After that I manage to recover all my apps and information from my OnePlus 6.
Just perfect!
Thank you
Click to expand...
Click to collapse
Could you tell me if it support the 4G band 66 and 71 after change to Oxygen OS? Thanks.

jizzboss said:
hi everyone
I got the official firmware
How to install?
1.Download firmware
2.Put the file in the phone directory
3. Open system update, select local update
Warning！
1.Please backup your data！
2.imei cannot be recognized correctly
##Back to oxygen os can be restored
##The official said the later ota repair
3.Flashing into coloros will generate a new partition
my_product
my_engineering
my_stock
my_heytap
my_company
my_carrier
my_region
my_preload
my_manifest
After you return to oxygen os，You can use fastboot to clear these partitions
For example
fastboot resize-logical-partition my_product 0
Download link：
click me
Click to expand...
Click to collapse
Hello just to be clear i have China vatiant (ColorOS) after flashing OxygenOS i have to fastboot clear all the above partitions? ot just
fastboot resize-logical-partition my_product 0?
Please Kindly explain better

dailystudio said:
Done, from ColorOS to OxygenOS.
Click to expand...
Click to collapse
hello can you explain how you get back imei number .. fastboot what partitions i dont want to messup my device i want to install oxygen with any issues please

Does threre exist any other way to change the imei? Because it is written on the device (sticker) and did not match. And I have unfortunately no backup
Problem solved with the next european update the real IMEI were back

Hi guys i think i'll buy the OnePlus 9 but it's a Chinese version (the one without wireless charging)
AFAIK the phone itself does support Hungarian bands so calls, 4G etc. won't be an issue (correct me if i'm wrong please) but it comes with ColorOS by default. I'd like to change it to OxygenOS but i don't know if this method will work or not, and if yes, do i loose/break something by doing it? For ex. loosing IMEI, not be able to call, system crashes etc...
Thank you!

AxelM said:
Does threre exist any other way to change the imei? Because it is written on the device (sticker) and did not match. And I have unfortunately no backup
Problem solved with the next european update the real IMEI were back
Click to expand...
Click to collapse
please share link with firmware that you user to fix imei

I used the Idian firmware (11.2.1.1 (210309)) from this post: https://forum.xda-developers.com/t/oneplus-9-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254579/ to reset the phone
and than I installed this European Version within the updater 11.2.3.3: OnePlus9Oxygen_22.E.06_GLO_0060_2104020539
Than it was fine for me...

I have a OnePlus 8 on oxygen os 12. I have a partition called my_heytap that has the YouTube app. I have an older version of YouTube for the use of YouTube Vanced root. For some reason this partition keeps updating YouTube after I reboot.
Can I use your fastboot command
fastboot resize-logical-partition my_partition name 0
to get rid of those my_ partitions? Are those partitions below necessary?
my_product
my_engineering
my_stock
my_heytap
my_company
my_carrier
my_region
my_preload
my_manifest

jizzboss said:
hi everyone
I got the official firmware
How to install?
1.Download firmware
2.Put the file in the phone directory
3. Open system update, select local update
Warning！
1.Please backup your data！
2.imei cannot be recognized correctly
##Back to oxygen os can be restored
##The official said the later ota repair
3.Flashing into coloros will generate a new partition
my_product
my_engineering
my_stock
my_heytap
my_company
my_carrier
my_region
my_preload
my_manifest
After you return to oxygen os，You can use fastboot to clear these partitions
For example
fastboot resize-logical-partition my_product 0
Download link：
click me
Click to expand...
Click to collapse
I have a OP8 on OOS 12.1 C.33 and I want to get rid of those partitions. The command fastboot resize-logical-partition my_heytap 0 is giving me an error of Unkown Command. Why not use the command fastboot delete-logical-partition my_heytap? Why didn't the command of resize logical partition failed?
Edit: I guess I figured it out. Vanced manager needs to be installed for the mount script to work.

[GSI][Android 10] Install AOSP 10 on Huawei Honor 6X.

POST - v14
(This number will increase every time the post is updated.)​What's new in v14?
Corrected some simple mistakes in procedure.​Modified overall post for better UX.​
​
Spoiler: Version Changelog
What's new in v13?
Modified Gapps part in requirements to make it more clear.​Added useful information section. for Pro Noobs and Ultra Noobs like me.​​What's new in v12?
Added User Contributions and feedback section.​Added Miscellaneous recommendations section.​Modified some steps in installation procedure to make it even more noob friendly.​Linked @lmaohelp's thread.​Decreased size of text in procedure.​​​
​
This ROM is based on Android 10 GSI builds of @phhusson (Thanks a ton to him).
Thanks to @Hami_Do for his hi6250 patches.
Thanks to Huawei for making their phones nearly unbrickable .
Thanks to @Djiban for his ideas on improving the thread.
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.
Note that I was using flux substratum theme in the screenshots. Hence, icons and colors may vary on your device.​
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 (download system-quack-arm64-aonly-vanilla.img.xz, you could try others but arm64, a-only is must).
TWRP from attchments or link or any other TWRP recovery compatible with Honor 6X EMUI 8.
Gapps(Optional, I used nano OpenGapps, NikGapps gave an error during installing, You can also try others. You can directly try the img with gapps instead of vanilla but i prefer nano gapps over vanilla).
stock recovery.
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 (mentioned in this post). Thanks to @lmaohelp for his effort and describing everything in detail.
Useful Information :
What on the Earth is meant by Vanilla android? -> it is the stock / pure version of android without Google apps and services.​
What is OpenGapps? Check it out at OpenGapps.org!​
What is Nano (not the mathematical 10^-9) Gapps? It is a version of Gapps with Minimal installation which means only the core part of gapps is installed with very little major apps. They can be installed later.​
What is ARM64? it is a 64 bit operating system/platform.
What on the moon is AOSP? It stands for android open source project which is the purest form of android.
NOTE : My device bootlooped whenever I tried installing Magisk. So, better stick with the PHH-SuperUser that you get out-of-the-box with the system image.
NOTE : Skip every step with gapps if you are already using img with gapps.
What isn't working :
VoLTE (can't be fixed as per my knowledge), Camera (FIXED NOW | trying to find a fix, replacing libcamxxx could help), Flashlight (FIXED NOW | also trying to find a fix, fixing camera may fix this too).
CAMERA AND TORCH HAVE BEEN FIXED. Thanks to @Hami_Do (flash the attched patch file whenever you are bored, LOL)
What's Working :
Everything except the ones mentioned above VoLTE.
*Tell me if something else 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 .***​Procedure :
Make sure your device is running EMUI 8.​
Extract downloaded image using some xz extractor(7zip can also do this), copy it to pc.​
Reboot your device to TWRP recovery.​
Format the data partition {Wipe > Format data > type "yes"}​
(Optional) In TWRP, choose wipe > advanced wipe > select system, data, cache and DALVIK and format them.​
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 nano gapps over vanilla) 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 nano gapps over vanilla) Unmount and Remount system partition. Go to wipe > advanced wipe > Choose system > resize. Flash gapps.​
Flash stock recovery(also available in attachments) with twrp in the same way. 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.​
>If you flashed gapps over vanilla, the first boot would take about 5 mins. else, it would be very fast. Subsequent boots on both are quite fast.
>Sometimes, I observed that flashing gapps from internal storage caused bootloop(this is because of corrupt zip), in such case get back to EMUI 8, repeat the process by flashing gapps from micro sd.
*you'll get a warning that something wrong with your device every time you boot it. IGNORE IT.
Spoiler: Additionals
Additionals:
> If you messed up somewhere during installation, you can always recover your device by following this guide.
> If you have the update.zip file from the above mentioned EMUI 8 folder directly, you could just directly flash it after wiping data, system and cache(use adb push or microsd to transfer update.zip to device).
>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 :
I was able to install magisk by flashing unSU zip from @Hami_Do 's thread on hi6250 manual fixes and then flashing phh's magisk after deleting phh-su from /system/bin/ but sadly, I wasn't able to use quickswitch for other launchers as it needs magisk version of 20.4 (min.) but phh's magisk is 19.3 and substratum theme engine is not working (due to some error). So, I'm sticking with the root that comes out of the box and I recommend you to do the same. EXTRAS : The Phone and Messaging apps that came out of the box with the GSI stopped working after installing magisk. So, you are installing magisk, just replace these system apps from LineageOS ones or delete them and install the google phone and messaging from play store.
During multiple tests (installing, modifying and testing the GSI for its stability in multiple ways), I found that you need not always go back to stock EMUI 8 if you messed up something. This works without error but if you have some time, getting back to stock EMUI 8 is still recommended before installing some other ROM/GSI.
Try not to touch the finger print sensor when you are at the setup after first boot. This is making the finger print sensor not recognisable until next reboot.
User Feedback and Contributions :
Thanks to @OrionThyHunter for his feedback and some fixes :
Using the Greenify app will stop the finger print sensor from working. FIX : Disable "Alternative Screen Off Mode".
Thanks to @[email protected] for finding out he following issues :
Adaptive Brightness Doesn't work. Flash the attachment in this post to fix it.
To pass SafetyNet, follow this post.
Miscellaneous Recommendations :
Use Google Camera Go app for photos. Its much better than the GSI's stock one.
​
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"
}

thank you it worked, now waiting for volte and camera fix on next update.... please update soon.... waiting waiting waiting........

[email protected] said:
thank you it worked, now waiting for volte and camera fix on next update.... please update soon.... waiting waiting waiting........
Click to expand...
Click to collapse
I think VoLTE can't be fixed.
For camera, you have to replace each file in /system/lib/ starting with libcam(libcamxyz...) from stock emui 8 and check each possible combination with subsequent reboots. I'm a little bit busy right now as I'm working on AOSP 11(as I believe it'll run without much problems because it has been tested on other hi6250 devices) with @Djiban. You could just do this on your own. If you find any working combination, please post it in this thread.

[email protected] said:
thank you it worked, now waiting for volte and camera fix on next update.... please update soon.... waiting waiting waiting........
Click to expand...
Click to collapse
Finally, Fixed it dude(camera and torch) by replacing libraries! Found a patch that does the same thing. Updated the Original post.
Tried a lot to fix VoLTE but didn't work... will try again later.
CHECK IT OUT!
#endyourwait LOL!

Hi again, I got this installed using TWRP, and I still have TWRP installed because I don't have the stock recovery. The system boots but it is giving me an error saying encryption unsuccessful, with a button saying "erase all data" which does nothing, and I am unable to do anything.
I was having this error when I first installed EMUI 8 from EMUI 5 as well, but at least the button took me to eRecovery, where the factory reset would fail at 5-6%. Currently if I go into eRecovery and click factory reset, it just reboots and takes me to TWRP again. Also, when I go into eRecovery it asks me to reformat the partition because it is "corrupted", which somehow changes the file system for /data to f2fs, and causes the phone to be stuck on the android boot animation. When I change /data back to ext4 I am able to boot back to the screen of encryption unsuccessful.
How do I fix this issue and be able to use the phone? Attached is a screenshot of the error message the OS is giving me.

lmaohelp said:
Hi again, I got this installed using TWRP, and I still have TWRP installed because I don't have the stock recovery. The system boots but it is giving me an error saying encryption unsuccessful, with a button saying "erase all data" which does nothing, and I am unable to do anything.
I was having this error when I first installed EMUI 8 from EMUI 5 as well, but at least the button took me to eRecovery, where the factory reset would fail at 5-6%. Currently if I go into eRecovery and click factory reset, it just reboots and takes me to TWRP again. Also, when I go into eRecovery it asks me to reformat the partition because it is "corrupted", which somehow changes the file system for /data to f2fs, and causes the phone to be stuck on the android boot animation. When I change /data back to ext4 I am able to boot back to the screen of encryption unsuccessful.
How do I fix this issue and be able to use the phone? Attached is a screenshot of the error message the OS is giving me.
Click to expand...
Click to collapse
Did you flash stock recovery after flashing system image?
Get back to emui 8(if you have update.zip, you could directly flash it with twrp). Repeat the process. Flash stock recovery. Perform a factory reset. And boot it to the system for the first time. You could then flash twrp with fastboot.
***Do not do a factory reset with twrp! Its causing errors.***

Apparently it could be a faulty EMMC chip according to this website, which makes sense since TWRP is not able to mount the internal storage partition or the Dalvik / ART cache, and eRecovery is not able to reset the phone, which is a characteristic of EMMC failure, according to this website. I had to unplug the battery countless times when I was tinkering with the phone, because my power button is broken, and it definitely would've contributed to this failure according to what I have read. Well, guess I'm done with this phone lol
EDIT: Well I'm starting from scratch again but everything is installing fine so I guess nothing is wrong currently? Huawei factory reset even worked

Venkata Lochan Nune said:
Did you flash stock recovery after flashing system image?
Get back to emui 8(if you have update.zip, you could directly flash it with twrp). Repeat the process. Flash stock recovery. Perform a factory reset. And boot it to the system for the first time. You could then flash twrp with fastboot.
***Do not do a factory reset with twrp! Its causing errors.***
Click to expand...
Click to collapse
No, I don't know where to find the stock recovery file, where can I find it?
I managed to boot into EMUI 8 just fine since I did not have a password on the EMUI 5 OS before installing lol. Now I just need the stock recovery you are talking about so I can follow your steps.

do you mean, you testing ASOP 11 on honor 6x ? if yes wow......

[email protected] said:
do you mean, you testing ASOP 11 on honor 6x ? if yes wow......
Click to expand...
Click to collapse
Nope, not now. @Djiban is quite busy and for me to work, I'm not having a spare device. He'll do it when he's got free time.
I didn't find much noticeable differences between AOSP 10 and 11 execpt some ui improvements and under-the-hood improvements. So, I'll skip AOSP 11 and directly will work with AOSP 12 on future. I liked the new things introduced in android 12. So, I'll definitely work on it.

lmaohelp said:
No, I don't know where to find the stock recovery file, where can I find it?
I managed to boot into EMUI 8 just fine since I did not have a password on the EMUI 5 OS before installing lol. Now I just need the stock recovery you are talking about so I can follow your steps.
Click to expand...
Click to collapse
Do you have the update.zip file?
Or wait I'll attach one in few hours...

lmaohelp said:
Apparently it could be a faulty EMMC chip according to this website, which makes sense since TWRP is not able to mount the internal storage partition or the Dalvik / ART cache, and eRecovery is not able to reset the phone, which is a characteristic of EMMC failure, according to this website. I had to unplug the battery countless times when I was tinkering with the phone, because my power button is broken, and it definitely would've contributed to this failure according to what I have read. Well, guess I'm done with this phone lol
EDIT: Well I'm starting from scratch again but everything is installing fine so I guess nothing is wrong currently? Huawei factory reset even worked
Click to expand...
Click to collapse
This is because twrp on our phone doesn't support encryption-decryption things. So, they can only mount internal storage when you perform a complete data format by typing "yes".

Venkata Lochan Nune said:
Do you have the update.zip file?
Or wait I'll attach one in few hours...
Click to expand...
Click to collapse
I do, but I'm unfamiliar with how to get the recovery.img from the zip file. If you can tell me how to extract it or attach one that would be great!

lmaohelp said:
I do, but I'm unfamiliar with how to get the recovery.img from the zip file. If you can tell me how to extract it or attach one that would be great!
Click to expand...
Click to collapse
Actually, flashing it should replace twrp with stock one didn't it?
You can extract it with 7zip. It worked for me.

Venkata Lochan Nune said:
Actuall, flashing it should replace twrp with stock one didn't it?
You can extract it with 7zip. It worked for me
Click to expand...
Click to collapse
What do you mean by flashing it, the update file? I updated from EMUI 5 to EMUI 8 using a update.zip file and HWOTA method so I am not sure if that is the same thing as just flashing the update.zip file. Also, just extracting the files doesn't produce anything useful. I used a firmware extractor from this thread, which comes up with the files shown in the screenshot. Now I'm not sure which file is the stock recovery image. I also tried flashing Magisk for root access and using Flashify to backup the stock recovery image, but the app would just freeze, I'm not sure why.

lmaohelp said:
What do you mean by flashing it, the update file? I updated from EMUI 5 to EMUI 8 using a update.zip file and HWOTA method so I am not sure if that is the same thing as just flashing the update.zip file. Also, just extracting the files doesn't produce anything useful. I used a firmware extractor from this thread, which comes up with the files shown in the screenshot. Now I'm not sure which file is the stock recovery image. I also tried flashing Magisk for root access and using Flashify to backup the stock recovery image, but the app would just freeze, I'm not sure why.
Click to expand...
Click to collapse
Well you could directly flash update.zip with twrp.
Wail I'll attach it in a while. Just turned on my PC to search for it and this bloody "working on updates" came up.

lmaohelp said:
What do you mean by flashing it, the update file? I updated from EMUI 5 to EMUI 8 using a update.zip file and HWOTA method so I am not sure if that is the same thing as just flashing the update.zip file. Also, just extracting the files doesn't produce anything useful. I used a firmware extractor from this thread, which comes up with the files shown in the screenshot. Now I'm not sure which file is the stock recovery image. I also tried flashing Magisk for root access and using Flashify to backup the stock recovery image, but the app would just freeze, I'm not sure why.
Click to expand...
Click to collapse
Yeah I've faced the same problem with flashify and ofcourse other similar apps. The problem I usually get is that system partition isn't writable. After changing it to r/w, I get an error that boot image not found. (This doesn't happen in flashify, it just freezes). Not sure what the problem is maybe, huawei's anti modding measures...

This might be the stock recovery(its in between some 10 other recoveries so, not sure). Try it and inform me
EDIT : THIS IS NOT THE RIGHT ONE. STOCK RECOVERY WAS ATTACHED IN POST #1.

Venkata Lochan Nune said:
This might be the stock recovery(its in between some 10 other recoveries so, not sure). Try it and inform me.
Click to expand...
Click to collapse
I don't think that is the correct file, as I flashed it and "adb reboot recovery" just causes it to be stuck on the "your phone is unlocked" screen, and so does clicking the factory reset option in eRecovery. I tried extracting the RECOVERY_RAMDIS(K).img file and flashing it, which worked, and successfully failed (lol) to reset the phone.
EDIT: I got into the OS successfully. It is unexpectedly smooth, good job!

lmaohelp said:
I don't think that is the correct file, as I flashed it and "adb reboot recovery" just causes it to be stuck on the "your phone is unlocked" screen, and so does clicking the factory reset option in eRecovery. I tried extracting the RECOVERY_RAMDIS(K).img file and flashing it, which worked, and successfully failed (lol) to reset the phone.
EDIT: I got into the OS successfully. It is unexpectedly smooth, good job!
Click to expand...
Click to collapse
So you liked it?
And hey, attach the stock recovery for future reference if someone needs it.
Use the camera patch to fix cam and flashlight issues. It just replaces the libraries. Flash any emui 8 compatible twrp with fastboot. Take a migrate backup in case.
Google Camera GO app works like a charm and is better than the stock one so I recommended using it.
Enjoy your phone!