Flashtool showing "No partition delivery included" when flashing. What to do? - Sony Xperia XA2 Questions & Answers

Flashtool showing "No partition delivery included" when flashing. What to do?
Hi,
A while back I unlocked my XA2, thus disabling OTAs. I have discovered that there's a new firmware for my phone and I have downloaded the firmware using Xperifirm. After downloading the firmare, I created a bundle using Flashtool. So far, so good. However, I'm reluctant to flash my device because Flashtool displays the following message:
View attachment 4692407
What should I do? I have not found a FTF-download for the newest firmware for my device.

Ok, I figured this one out by myself. I took the following steps:
1. Downloaded Xperifirm (downloaded from XDA) and FlashTool
2. Set up Xperifirm to not download OTAs (though I'm uncertain that this i necessary)
3. Found my device and downloaded the firmware from Xperifirm
3a. If Xperifim has problems unpacking the files, just cd to the download directory and unzip each FILE_* into *.sin-files
3b. After extracting the FILE_*s, you should create a boot-subdirectory and extract boot.zip to that directory.
4. Open FlashTool and create a bundle.
4a. To create the bundle, you need to point to the directory where all sin-files are located.
4b. When setting the version, make sure the version starts with 50.1.. This is important, if not the FlashTool cannot find the necessary setup-script.
4c. FlashTool will ask if you would like to include a device specific script. Click yes.
5. When the bundle is created, flash it.
5a. If FlashTool asks "No partition delivery included. [snip] Do you want to continue?", click yes.
5b. If FlashTool asks to use the device specific script. Click yes.
5c. If FlashTook asks "The following files is not in FSC script: [snip]. Do you want to continue?", click yes.
6. Do as flashtool says, power down and unplug the device, hold voulme down and plug the USB cable to the phone.
6a. Wait for FlashTool to do its job and finish flashing.
7. Reboot the phone.
8. (optional) Boot recovery and root
8a. Boot into recovery (adb reboot bootloader AND fastboot boot twrp-recovery.img)
8b. Install Magisk if needed
If these steps are successfully applied, you should have a updated Android version on your phone

??

Related

[Q] relock bootloader for Xperia s

I want to relock my bootloader for official jelly bean update on PC.........please help me
ishu87scorpion said:
I want to relock my bootloader for official jelly bean update on PC.........please help me
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1527159
Please don't create a new thread.. Search first and then read.. Read and read more..
The link provided for Xperia-S_Relock_bootloader.ftf is dead. If someone has the file and would be so kind as to mirror it it would be awesome. I would have posted on the original thread, but it's in the developer section and I am not allowed to post there. I have tried google search to find an alternative and I have come across one file with the same name, I flashed it with Flashtool and now my Xperia S won't boot, I can get into flashmode and fastboot but that's it.
queloo said:
The link provided for Xperia-S_Relock_bootloader.ftf is dead. If someone has the file and would be so kind as to mirror it it would be awesome. I would have posted on the original thread, but it's in the developer section and I am not allowed to post there. I have tried google search to find an alternative and I have come across one file with the same name, I flashed it with Flashtool and now my Xperia S won't boot, I can get into flashmode and fastboot but that's it.
Click to expand...
Click to collapse
I have also faced the same problem and finally got the solution............
1. Just download the flash tool from here............
http://androxyde.github.io/index.html?1367093576000
2. Download latest Firmware from here..........
http://forum.xda-developers.com/showpost.php?p=24844165&postcount=2
3. And follow this steps...........
>DO NOT CONNECT YOUR PHONE
>First you need to have FLASH TOOL installed from above 1 no. link
Now run FLASHTOOL.
>From FLASHTOOL home, select the flash/lightning bolt button
>Select FLASH MODE
>Select your stock firmware file (.ftf file wich downloaded from 2 no. link)
>WIPE: everything
>If available EXCLUDE: TA. (this option is not available for all stock.ftf files, if it's there just exclude it)
>Now click START button
>After FLASHTOOL prepares files, you should get this screen (or similar depending on version of FLASHTOOL)
>Now connect your phone with Volume key down (-). Flash mode and green LED will blink.
> Now flashing will start.............
>After all activity will done than start your phone and enjoy......
If u need any assistance just post here............
ishu87scorpion said:
I have also faced the same problem and finally got the solution............
1. Just download the flash tool from here............
http://androxyde.github.io/index.html?1367093576000
2. Download latest Firmware from here..........
http://forum.xda-developers.com/showpost.php?p=24844165&postcount=2
3. And follow this steps...........
>DO NOT CONNECT YOUR PHONE
>First you need to have FLASH TOOL installed from above 1 no. link
Now run FLASHTOOL.
>From FLASHTOOL home, select the flash/lightning bolt button
>Select FLASH MODE
>Select your stock firmware file (.ftf file wich downloaded from 2 no. link)
>WIPE: everything
>If available EXCLUDE: TA. (this option is not available for all stock.ftf files, if it's there just exclude it)
>Now click START button
>After FLASHTOOL prepares files, you should get this screen (or similar depending on version of FLASHTOOL)
>Now connect your phone with Volume key down (-). Flash mode and green LED will blink.
> Now flashing will start.............
>After all activity will done than start your phone and enjoy......
If u need any assistance just post here............
Click to expand...
Click to collapse
Thank you very much. This worked. I didn't know flashing a stock .ftf firmware would re-lock my bootloader. It did I flashed LT26i_6.1.A.2.50_1257-5499_WORLD and after that was able to upgrade through PC-companion without any problems. Thank you for the help.
ishu87scorpion said:
I have also faced the same problem and finally got the solution............
1. Just download the flash tool from here............
http://androxyde.github.io/index.html?1367093576000
2. Download latest Firmware from here..........
http://forum.xda-developers.com/showpost.php?p=24844165&postcount=2
3. And follow this steps...........
>DO NOT CONNECT YOUR PHONE
>First you need to have FLASH TOOL installed from above 1 no. link
Now run FLASHTOOL.
>From FLASHTOOL home, select the flash/lightning bolt button
>Select FLASH MODE
>Select your stock firmware file (.ftf file wich downloaded from 2 no. link)
>WIPE: everything
>If available EXCLUDE: TA. (this option is not available for all stock.ftf files, if it's there just exclude it)
>Now click START button
>After FLASHTOOL prepares files, you should get this screen (or similar depending on version of FLASHTOOL)
>Now connect your phone with Volume key down (-). Flash mode and green LED will blink.
> Now flashing will start.............
>After all activity will done than start your phone and enjoy......
If u need any assistance just post here............
Click to expand...
Click to collapse
i flashed LT26i_6.2.B.0.200_WORLD.ftf firmware but i am not able to upgrade through PC-companion or directly from the phone
please help

[Guide] [XAS] [UPDATED] Xperia Unlocking BL, flashing ROMs/kernels BPaul's 5.1.1

This is a guide for XPERIA ACRO S (other xperia users can also refer needed information)
[Below procedure looks lendy, but you'll just need max 30 minutes if you have every downloaded file.]
I make this guide for noobs as there weren't such guide (even for my first time of flashing ROM I didn't get any such guide, so I decided to make one)
This Guide is especially for flashing BPaul's 5.1.1 ROMs (B3||B2||B1)
To Flash Different Versions Of BPaul's ROM follow Respective Guide:
Beta1 threads POST #13
Beta2 same thread
Beta3 threads POST #40
So here I'm giving detail process to install Bpaul's 5.1.1 with every links needed.
we are going to take below steps;
1. unlocking Bootloader
2. flashing kernel with recoveries
3. backing up stock ROM
4. installing BPaul's 5.1.1
Special Thanks;
@BPaul (for awesome ROM)
@cobrato (for stock kernel)
@jajb (for gapps)
NOTE: I'AM NOT RESPONSIBLE IF YOU DAMAGED YOUR PHONE BY CROSS FLASHING OTHER ROMS,KERNELS ETC. BELOW PROCESS IS SUCCESSFULLY CARRIED ON XPERIA ACRO S. AS NOOBS CAN MAKE MANY MISTAKES, I'AM NOT RESPONSIBLE FOR YOUR DAMAGE.
-DO AT YOUR OWN RISK-
Click to expand...
Click to collapse
-Here we START-
Note: Before Unlocking Bootloader, I suggest you to Backup your TA Partition. (Trim Area) IF in future something goes wrong with network signal related issues or bootloader issue, you could restore this backup. TA Partition can be backed-up ONLY before unlocking bootloader. To backup TA follow this "Guide" and after you could below steps. Also your phone needs to be Rooted to backup TA, if your phone isn't rooted, follow this "Guide"
*_UNLOCKING BOOTLOADER_*
(unlocking bootloader will erase everything on your phone, i suggest you to take backup of your data)
First check weather you can unlock your bootloader. To do so type *#*#7378423#*#* in dialer and find bootloader unlocked status.
IF bootloader unlock allowed = YES (you can unlock)
IF bootloader unlock allowed = NO (you can't unlock)
IF bootloader unlocked = YES (already unlocked)
Then you need to take unlocking code from official Sony website (link below)
LINK1 Unlocking Bootloader
after clicking on above link, on the page just scroll down
1.select your device
2.provide your IMEI
3.you'll get unlock code (save it properly)
Next you need to download minimal adb and fastboot (link below)
LINK1 Miniamal ADB and Fastboot
install it to your computer.
Now we have to connect phone in fastboot mode, follow below steps
1.Turn on usb debugging mode.
(setting > developer option > usb debugging)
2.Turn Off your Xperia Acro S
3.Press and Hold volume up button and then connect usb to computer.
(If you see Blue LED of phone, then everything is going right)
(Let your computer install essential fastboot drivers)
[If blue LED disappears after some seconds and phone starts charging, that means your PC isn't installing fastboot drivers. In such situation REFER Q&A thread POST #4 ]
Now open minimal adb and fastboot (we installed previously)
Type below command
-fastboot devices
-fastboot -i 0x0fce oem unlock 0x(your unlock code without this brackets)
-fastboot reboot
DONE
(Now you have successfully unlocked your bootloader)
[ To check that if you have succeeded in unlocking bootloader type *#*#7378423#*#* in dialer and find bootloader unlock status.
ALSO you'll notice that your phone is factory resetted]
*_FLASHING KERNEL WITH RECOVERY'S_*
As you have STOCK ROM, you need to flash STOCK KERNEL with recoveries (link below)
LINK1 Stock Kernel
-The above kernel cantain CWM as well as TWRP
After opening above link, download respective kernel
Save the above downloaded kernel to fastboot folder on your computer.
-Get into fastboot mode and connect to computer.
(Press and Hold volume up button and then connect usb to computer).
Now open minimal adb and fastboot (we installed previosly)
Type below command
-fastboot devices
-fastboot flash boot kernel_62B196_acroS.elf
-fastboot reboot
DONE
(Now you have successfully flashed kernel with recovery)
*_BACKINGUP STOCK ROM_*
As you have successfully flashed kernel with recoverys, its easy to take a full backup of your system.
To enter into recovery follow below steps
1.To get into CWM reboot your phone, press volume up key for few times when the magenta LED appears.
(To navigate use volume buttons, for selecting use power button)
2.To get into TWRP reboot your phone and tap the screen for few times when the magenta LED appears.
3.Select Backup.
(let the process finish)
I SUGGEST TO TAKE BACKUP FROM BOTH RECOVERY'S
DONE
(Now you have successfully Backed-up your ROM)
Flashing BPaul's Beta2 ROM works ONLY IF YOUR PHONE HAS Beta1 ROM installed. If you don't have Beta1 installed, first of all install it. . If your phone has Beta 1, ignore this and carry on.
*_FLASHING ROM BPaul's 5.1.1_Beta 2 over Beta 1*
For Flashing This ROM your phone (Xperia Acro S) needs to be rooted if your not rooted, follow this "Guide" Also USB Debugging in developers option should be enabled.
A] Download ROM BPaul's 5.1.1 Beta 2 (link below)
LINK1 BPaul's B2
C] Download below minimal GApps for 5.1.1 and copy it to your sdcard/ext_sdcard(link below)
LINK1 GApps for 5.1.1
1.Download fota kernel with cwm recovery (link below)
LINK1 Fota Kernel
2.Copy above downloaded kernel + rom to internal storage of your phone
3.Open minimal adb and fastboot
Type below command;
-adb shell
-su
(confirm popup su request from your phone)
-dd if=/sdcard/hikari-fota_CWM.img of=/dev/block/mmcblk0p11
Now you need to enter into recovery. To do so, restart your phone in recovery mode.
1.Wipe system + factory reset
2.Install zip from sdcard/ext_sdcard
(select beta-hikari...... rom)
3.Wipe cache + dalvic cache
4.Again install zip from sdcard/ext_sdcard
(select 5.1.1 gapps)
5.Again wipe cache+ dalvic cache
6.Reboot
For the first time it can take a looooong time to boot up. So just don't worry.
DONE
(You have successfully installed BPaul's 5.1.1)
OPTIONAL:
For rooting this ROM, just download SuperSU, save it to your phone and install it manually with recovery. (link below)
LINK1 SuperSU
If you found above post easy and helpful, you could donate/buy me a cup of COFFEE or even a BEER!
(I'll be there for you as a online support any time), just click HERE!
(You need to have a PayPal account, If you don't have, then click HERE and just create one individual account, it's simple)
Regards,
hitman-xda
Very good tutorial. Thank you.
BPaul said:
Very good tutorial. Thank you.
Click to expand...
Click to collapse
Its because of you BPaul, thanx for making an awesome ROM and still caring for acro s
I can't open CWM after flash system.img
Please help
dzi-benk said:
I can't open CWM after flash system.img
Please help
Click to expand...
Click to collapse
Did you copied the recovery into internal memory and typed the command successfully??
hitman-xda said:
Did you copied the recovery into internal memory and typed the command successfully??
Click to expand...
Click to collapse
Yes, I have copied recovery (CWM.img and TWRP.img) and always fail in the process command, what should i do ?
dzi-benk said:
Yes, I have copied recovery (CWM.img and TWRP.img) and always fail in the process command, what should i do ?
Click to expand...
Click to collapse
You just need to copy one of them.
Do not keep it in any folder and correctly write the command or just copy and paste.
Let me know if you fail again.
And post a picture of the error.
PS: Make sure you write cwm command if you copied cwm recovery and twrp command for twrp recovery.
Regards,
hitman-xda
hitman-xda said:
You just need to copy one of them.
Do not keep it in any folder and correctly write the command or just copy and paste.
Let me know if you fail again.
And post a picture of the error.
PS: Make sure you write cwm command if you copied cwm recovery and twrp command for twrp recovery.
Regards,
hitman-xda
Click to expand...
Click to collapse
This :
{
"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"
}
dzi-benk said:
This :
Click to expand...
Click to collapse
Copy twrp into your internal memory and DO NO WRITE the command which is marked into below picture.
https://drive.google.com/file/d/0BzKXheD4UND6NjdDOGpVcTY2WDA/edit?usp=docslist_api
Regards,
hitman-xda
hitman-xda said:
Copy twrp into your internal memory and DO NO WRITE the command which is marked into below picture.
https://drive.google.com/file/d/0BzKXheD4UND6NjdDOGpVcTY2WDA/edit?usp=docslist_api
Regards,
hitman-xda
Click to expand...
Click to collapse
Wow, thanks bro finally i can try lolipop for my Acro S
How about to root? I install SuperSU from app store and when i want to update it's so loong and failed
dzi-benk said:
Wow, thanks bro finally i can try lolipop for my Acro S
How about to root? I install SuperSU from app store and when i want to update it's so loong and failed
Click to expand...
Click to collapse
Did you followed every step of the Guide? (you must be)
The last step of the Guide is about rooting 5.1
Just installing superSU from play store doesn't root your phone.
BTW You could just press thumbs up button, instead writing thanks
Regards,
hitman-xda
hitman-xda said:
You could just press thumbs up button, instead writing thanks
Just installing superSU from play store doesn't root your phone.
Are you on stock ROM? OR lollipop? OR any other.
Regards,
hitman-xda
Click to expand...
Click to collapse
Finally, i'm download from Here and push from CWM it's work Once more thanks for your help. Nice to meet you
Regards,
dzi-benk
BPaul's Beta1 Flashing Guide
(As B2 version is flashable over B1, i created this guide for newer users who are facing ERROR7)
The process is little bit different compaired to B2 flashing process.
--PHONE NEEDS TO BE ROOTED AND USB DEBUGGING ENABLED.--
*_Downloads_*
1. ROM http://d-h.st/yt2G
2. Kernel http://d-h.st/nJXM
3. Flashtool (install it) http://d-h.st/Kb8
(After installing, goto installation folder and then drivers, install it. Select xperia acro s, fastboot driver while installing)
4. Min ADB and Fastboot (install it) https://drive.google.com/file/d/0B1S0LCuXCnnmOWhnUk1ZWVdQakE/view?pli=1
5. SuperSU http://download.chainfire.eu/supersu
*_FLASHING B1_*
1. UNZIP downloaded ROM to a folder. (You'll see 2imgs and 2recoverys)
2. Copy TWRP to your internal memory of phone.
3. Now open Min ADB and Fastboot and type below command.
-adb shell
-su
-dd if=/sdcard/twrp.img
of=/dev/block/mmcblk0p11
4. Open Flashtoool.
5. Click flash button.
6. Select fastboot mode .
7. Remove USB, Reboot phone to fastboot mode. (Power off phone, push vol up key and connect USB )
--FOLLOW BELOW STEPS CAREFULLY--
8. Setect SYSTEM to flash and open system.img from the extracted folder. (wait minimum 6 mins)
9. Select Kernel to flash and open downloaded kernel boot_07_05_15.img (wait for a min)
10. Reboot device into system.
DONE!
Your phone will take a long time to boot up for the first time, so just dont worry.
Also for Flashing Beta2 version your phone needs to be rooted. For that copy downloaded SuperSU to your phone and install it manually through your recovery.
NOW YOU CAN FLASH B2 VERSION WITHOUT ANY ERROR.
Regards,
hitman-xda
hitman-xda said:
BPaul's Beta1 Flashing Guide
(As B2 version is flashable over B1, i created this guide for newer users who are facing ERROR7)
The process is little bit different compaired to B2 flashing process.
--PHONE NEEDS TO BE ROOTED AND USB DEBUGGING ENABLED.--
*_Downloads_*
1. ROM http://d-h.st/yt2G
2. Kernel http://d-h.st/nJXM
3. Flashtool (install it) http://d-h.st/Kb8
(After installing, goto installation folder and then drivers, install it. Select xperia acro s, fastboot driver while installing)
4. Min ADB and Fastboot (install it) https://drive.google.com/file/d/0B1S0LCuXCnnmOWhnUk1ZWVdQakE/view?pli=1
5. SuperSU http://download.chainfire.eu/supersu
*_FLASHING B1_*
1. UNZIP downloaded ROM to a folder. (You'll see 2imgs and 2recoverys)
2. Copy TWRP to your internal memory of phone.
3. Now open Min ADB and Fastboot and type below command.
-adb shell
-su
-dd if=/sdcard/twrp.img
of=/dev/block/mmcblk0p11
4. Open Flashtoool.
5. Click flash button.
6. Select fastboot mode .
7. Remove USB, Reboot phone to fastboot mode. (Power off phone, push vol up key and connect USB )
--FOLLOW BELOW STEPS CAREFULLY--
8. Setect SYSTEM to flash and open system.img from the extracted folder. (wait minimum 6 mins)
9. Select Kernel to flash and open downloaded kernel boot_07_05_15.img (wait for a min)
10. Reboot device into system.
DONE!
Your phone will take a long time to boot up for the first time, so just dont worry.
Also for Flashing Beta2 version your phone needs to be rooted. For that copy downloaded SuperSU to your phone and install it manually through your recovery.
NOW YOU CAN FLASH B2 VERSION WITHOUT ANY ERROR.
Regards,
hitman-xda
Click to expand...
Click to collapse
Is it true that I have to root the phone (JB) with DooMLorDs kit.
PhantomSuppressor said:
Is it true that I have to root the phone (JB) with DooMLorDs kit.
Click to expand...
Click to collapse
There are many ways available for rooting Acro S.
For Me, 'towelroot' was the easiest way to root my phone. After that, you can manually download SuperSU app from play store.
Even You can try it
http://towelroot.com/
Regards,
hitman-xda
hitman-xda said:
There are many ways available for rooting Acro S.
For Me, 'towelroot' was the easiest way to root my phone. After that, you can manually download SuperSU app from play store.
Even You can try it
http://towelroot.com/
Regards,
hitman-xda
Click to expand...
Click to collapse
WOW! thanks
---------- Post added at 06:32 PM ---------- Previous post was at 06:09 PM ----------
hitman-xda said:
BPaul's Beta1 Flashing Guide
(As B2 version is flashable over B1, i created this guide for newer users who are facing ERROR7)
The process is little bit different compaired to B2 flashing process.
--PHONE NEEDS TO BE ROOTED AND USB DEBUGGING ENABLED.--
*_Downloads_*
1. ROM http://d-h.st/yt2G
2. Kernel http://d-h.st/nJXM
3. Flashtool (install it) http://d-h.st/Kb8
(After installing, goto installation folder and then drivers, install it. Select xperia acro s, fastboot driver while installing)
4. Min ADB and Fastboot (install it) https://drive.google.com/file/d/0B1S0LCuXCnnmOWhnUk1ZWVdQakE/view?pli=1
5. SuperSU http://download.chainfire.eu/supersu
*_FLASHING B1_*
1. UNZIP downloaded ROM to a folder. (You'll see 2imgs and 2recoverys)
2. Copy TWRP to your internal memory of phone.
3. Now open Min ADB and Fastboot and type below command.
-adb shell
-su
-dd if=/sdcard/twrp.img
of=/dev/block/mmcblk0p11
4. Open Flashtoool.
5. Click flash button.
6. Select fastboot mode .
7. Remove USB, Reboot phone to fastboot mode. (Power off phone, push vol up key and connect USB )
--FOLLOW BELOW STEPS CAREFULLY--
8. Setect SYSTEM to flash and open system.img from the extracted folder. (wait minimum 6 mins)
9. Select Kernel to flash and open downloaded kernel boot_07_05_15.img (wait for a min)
10. Reboot device into system.
DONE!
Your phone will take a long time to boot up for the first time, so just dont worry.
Also for Flashing Beta2 version your phone needs to be rooted. For that copy downloaded SuperSU to your phone and install it manually through your recovery.
NOW YOU CAN FLASH B2 VERSION WITHOUT ANY ERROR.
Regards,
hitman-xda
Click to expand...
Click to collapse
When I type: dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p11
it says that there's no such file or directory even though I copied twrp.img to my phone?
PhantomSuppressor said:
WOW! thanks
---------- Post added at 06:32 PM ---------- Previous post was at 06:09 PM ----------
When I type: dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p11
it says that there's no such file or directory even though I copied twrp.img to my phone?
Click to expand...
Click to collapse
Did you rooted your phone?
Was towelroot successful?
And do not place twrp.img in any folder. Just in internal memory.
hitman-xda said:
Did you rooted your phone?
Was towelroot successful?
And do not place twrp.img in any folder. Just in internal memory.
Click to expand...
Click to collapse
Yes it was successful and I did place the twrp.img in internal memory
PhantomSuppressor said:
Yes it was successful and I did place the twrp.img in internal memory
Click to expand...
Click to collapse
Try connecting USB to another port.
If still it dosent work, try restarting phone.
hitman-xda said:
Try connecting USB to another port.
If still it dosent work, try restarting phone.
Click to expand...
Click to collapse
Still nothing, after trying both of those

Flashtool freezes when creating bundle (ftf)

Anyone else had the same problem? Window just freezes and nothing happens. Is there any other way to get official firmware in .ftf format?
http://imgur.com/a/9KLdq
I'm doing something wrong or what?
Is there any way to install dstrikerz1's rom without downgrading?
Analala said:
http://imgur.com/a/9KLdq
I'm doing something wrong or what?
Is there any way to install dstrikerz1's rom without downgrading?
Click to expand...
Click to collapse
You need only recovery to flash Dstriker, no need to downgraded. Root with Kingroot, flash dual recover by nut, then flash rom...
levone1 said:
You need only recovery to flash Dstriker, no need to downgraded. Root with Kingroot, flash dual recover by nut, then flash rom...
Click to expand...
Click to collapse
Problem is I really want to avoid kingroot. I installed it once and then had to re-flash system again because it couldn't be uninstalled. And I don't trust Chinese proprietary software.
Analala said:
Problem is I really want to avoid kingroot. I installed it once and then had to re-flash system again because it couldn't be uninstalled. And I don't trust Chinese proprietary software.
Click to expand...
Click to collapse
If you're wanting to flash Dstriker, then you're going to reflash system anyway, just make sure to check box for 'system' when wiping in recovery...
If you really want to downgrade and root, try a newer version of Flashtool. New versions create the whole ftf just by downloading. All you have to do is wait until it's done, and click flash.
levone1 said:
If you're wanting to flash Dstriker, then you're going to reflash system anyway, just make sure to check box for 'system' when wiping in recovery...
If you really want to downgrade and root, try a newer version of Flashtool. New versions create the whole ftf just by downloading. All you have to do is wait until it's done, and click flash.
Click to expand...
Click to collapse
I tried downloading different firmware version on a different computer but i still get program freeze when i tried to bundle it. If i try to flash downloaded firmware then firmware selector cant find it either. See for yourself - http://imgur.com/r61Rr7m http://imgur.com/36nbNG7
Analala said:
I tried downloading different firmware version on a different computer but i still get program freeze when i tried to bundle it. If i try to flash downloaded firmware then firmware selector cant find it either. See for yourself - http://imgur.com/r61Rr7m http://imgur.com/36nbNG7
Click to expand...
Click to collapse
I'm not a Flashtool expert, but I've flashed roms at least a dozen times, and I don't even see that screen anymore. I remember in older versions you used to have to download and then create an ftf, bit about a year ago there was an update where FT and Xperifirm were able to work together, and the flashable ftf was created automatically. Ever since then, I just click on the firmware I want in Xperifirm, and it downloads, and prepares the file, and I just click 'flash' and connect the phone and it's done.
levone1 said:
I'm not a Flashtool expert, but I've flashed roms at least a dozen times, and I don't even see that screen anymore. I remember in older versions you used to have to download and then create an ftf, bit about a year ago there was an update where FT and Xperifirm were able to work together, and the flashable ftf was created automatically. Ever since then, I just click on the firmware I want in Xperifirm, and it downloads, and prepares the file, and I just click 'flash' and connect the phone and it's done.
Click to expand...
Click to collapse
Maybe its in the latest update. The problem is I get an error when trying to launch x10flasher.jar. I have no idea what could have caused this problem. I got freshly installed java so everything should be fine.
http://imgur.com/a/0oOwz
1. Download Flashtool 0.9.23.1 and install it
2. Download x10flasher.jar from the same page
3. Open folder where you just installed Flashtool, and simply paste x10flasher.jar
4. Move and replace - YES
that's how you upgrade to 0.9.23.2
As for making ftf files:
1. when you have Flashtool, open XperiFirm from there, as picture attached
2. when firmware of your choosing finished downloading close XperiFirm windows (red markers in attached pic) but dont close little window in Flashtool (green "circle" in attached pic)
3. after few seconds Flashtool starts creating FTF version of the firmware you downloaded via XperiFirm
4. when progress bar finishes you have your firmware avaible to flash via "lighting icon" in flashtool
Aculard said:
1. Download Flashtool 0.9.23.1 and install it
2. Download x10flasher.jar from the same page
3. Open folder where you just installed Flashtool, and simply paste x10flasher.jar
4. Move and replace - YES
that's how you upgrade to 0.9.23.2
As for making ftf files:
1. when you have Flashtool, open XperiFirm from there, as picture attached
2. when firmware of your choosing finished downloading close XperiFirm windows (red markers in attached pic) but dont close little window in Flashtool (green "circle" in attached pic)
3. after few seconds Flashtool starts creating FTF version of the firmware you downloaded via XperiFirm
4. when progress bar finishes you have your firmware avaible to flash via "lighting icon" in flashtool
Click to expand...
Click to collapse
Thanks fam! I thought x10flasher.jar was some kind of executable installer. Now everything works .
Me too , i thought x10flasher.jar is for Xperia X10 phones ... Problem solved , bundle created successfully .
Thanks to Aculard ...
Aculard said:
1. Download Flashtool 0.9.23.1 and install it
2. Download x10flasher.jar from the same page
3. Open folder where you just installed Flashtool, and simply paste x10flasher.jar
4. Move and replace - YES
that's how you upgrade to 0.9.23.2
As for making ftf files:
1. when you have Flashtool, open XperiFirm from there, as picture attached
2. when firmware of your choosing finished downloading close XperiFirm windows (red markers in attached pic) but dont close little window in Flashtool (green "circle" in attached pic)
3. after few seconds Flashtool starts creating FTF version of the firmware you downloaded via XperiFirm
4. when progress bar finishes you have your firmware avaible to flash via "lighting icon" in flashtool
Click to expand...
Click to collapse
Please could inform why Flashtool not showing FTF files after I Download it
also it's in Firmware folder
Thanks Mate
Thanks a lot to mate recomended jar update.
This forum not granted me quote.
I have the same issue between gentoo nor W10.
Regards.
Thanks so much for your solution. I have replaced the x10flasher.jar and it is working really good. Thanks again.
aculard said:
1. Download flashtool 0.9.23.1 and install it
2. Download x10flasher.jar from the same page
3. Open folder where you just installed flashtool, and simply paste x10flasher.jar
4. Move and replace - yes
that's how you upgrade to 0.9.23.2
as for making ftf files:
1. When you have flashtool, open xperifirm from there, as picture attached
2. When firmware of your choosing finished downloading close xperifirm windows (red markers in attached pic) but dont close little window in flashtool (green "circle" in attached pic)
3. After few seconds flashtool starts creating ftf version of the firmware you downloaded via xperifirm
4. When progress bar finishes you have your firmware avaible to flash via "lighting icon" in flashtool
Click to expand...
Click to collapse
thank you so much ive been trying to do this for so long
Thank you,
Aculard said:
1. Download Flashtool 0.9.23.1 and install it
2. Download x10flasher.jar from the same page
3. Open folder where you just installed Flashtool, and simply paste x10flasher.jar
4. Move and replace - YES
that's how you upgrade to 0.9.23.2
As for making ftf files:
1. when you have Flashtool, open XperiFirm from there, as picture attached
2. when firmware of your choosing finished downloading close XperiFirm windows (red markers in attached pic) but dont close little window in Flashtool (green "circle" in attached pic)
3. after few seconds Flashtool starts creating FTF version of the firmware you downloaded via XperiFirm
4. when progress bar finishes you have your firmware avaible to flash via "lighting icon" in flashtool
Click to expand...
Click to collapse

[GUIDE] [EMUI9] P20 Lite Basics

Spoiler: Quick Links
Official LineageOS 16.0 (15.02.2021)
.401 Stock Images (C432)
Stock Recovery
Stock E-recovery
Official TWRP (3.7.0)
Official TWRP (3.4.0-1)
Modified TWRP (3.4.0)
Heavily Modified TWRP (3.4.0)
Magisk Patched Recovery (25.2)
Magisk-Delta Patched Recovery (25.2-delta)
Stock Kernel (4.9.148)
Phenix Kernel (4.9.319 by Turex)
Phenix Permissive Kernel (4.9.319 by Iceows)
Phenix Permissive Kernel (4.9.235 by Abdelhay.ali)
Phenix Enforcing and Permissive Kernel for Android 13 (4.9.319 by Abdelhay.ali)
Selinux Rules for Android 13 (by Abdelhay.ali)
Everything Else (47GB)
Special key combos:​
Power + Vol+ = Recovery Mode
While USB connected, Power + Vol+ = Erecovery Mode
While USB connected, Vol- = Fastboot
Plug USB while holding down Vol+ + Vol- = Download Mode
Power + Vol+ + Vol- = Force Dload
Flashing Any GSI​Note:​Phh is "retiring". Community of builders created trebledroid initiative to keep his work alive. Don't expect same level of quality for a while.
Use vndklite variants.
At no point you need to wipe /data or any other partition. Just do factory reset.
If you want to backup via twrp you need to have encryption disabled.
Almost all chromium based browsers including chrome freeze after few minute of use. That is caused by DRM not working as intended in gsis. To fix it flash DRM fix.
Permissive kernel shouldn't be used daily. Please only use it for debugging purposes.
Prerequisites:​
ADB and Fastboot Installed (1)
Any Arm64 AB GSI image (1) (2) (3) (4) (5)
Google apps package (Optional) (1) (2) (3) (4)
TWRP
Unlocked Bootloader
Spoiler: Android 12 and Below
Spoiler: GSI with GAPPS
Tick "Enable OEM Unlock" from developer options
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash gsi image: fastboot flash system drag & drop img file to console
Flash Stock Recovery: fastboot flash recovery_ramdisk and drag & drop img file to console
Boot into recovery: power + vol+ while NOT connected to pc
Factory reset: Factory Reset > Type yes > Press power
Boot into system
Spoiler: Vanilla GSI + Gapps + Zips
Tick "Enable OEM Unlock" from developer options
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash gsi image: fastboot flash system drag & drop img file to console
Flash Phenix Kernel (Optional): fastboot flash kernel and drag & drop img file to console
Flash this TWRP: fastboot flash recovery_ramdisk and drag & drop img file to console
Boot into recovery: power + vol+ while NOT connected to pc
Factory reset: Wipe > Swipe Factory Reset
Resize system: Wipe > Advanced Wipe > Tick System > Repair or Change File System > Swipe Resize File System
if it fails issue these commands from your computer:
adb shell "/sbin/e2fsck -fp /dev/block/platform/hi_mci.0/by-name/system"
adb shell "/sbin/resize2fs /dev/block/platform/hi_mci.0/by-name/system"
Encrypt or Decrypt /Data (Optional): Mount > Tick Vendor > adb push drag & drop fstab file to console /vendor/etc
Flash DRM fix (Optional): ''
Flash NFC fix (Optional / Might not Work): ''
Flash Gapps Zip (Optional): ''
Boot into system: Reboot > System
Spoiler: Android 13 and Beyond(?)
Tick "Enable OEM Unlock" from developer options
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash gsi image: fastboot flash system drag & drop img file to console
Flash one of these kernel (Optional): fastboot flash kernel and drag & drop img file to console
Flash this TWRP: fastboot flash recovery_ramdisk and drag & drop img file to console
Boot into recovery: power + vol+ while NOT connected to pc
Factory reset: Wipe > Swipe Factory Reset
Flash this AIO fix : Advanced > ADB Sideload > Swipe to Start Sideload > Write adb sideload and drag & drop zip file to console
Flash Gapps Zip (Optional): ''
Boot into system: Reboot > System
Spoiler: Tweaks
Spoiler: TWRP on Erecovery, Magisk on Recovery Setup
Flash over to erecovery:
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash one of these (1) (2) twrp images: fastboot flash recovery_ramdisk and drag & drop img file to console
Boot into twrp: power + vol+ while NOT connected to pc
Push twrp to /cache: adb push drag & drop img file to console /cache
Flash twrp to erecovery: Install > Install Image > Select twrp image from /cache folder > Pick erecovery_ramdisk partition > Swipe
After you set up your phone and made sure you don't need stock recovery, flash magisk:
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash magisk patched image: fastboot flash recovery_ramdisk and drag & drop img file to console
From now on this is how you boot:
No keypress: System (Long yellow warning)
Power & Vol+ before Yellow Warning : System with magisk (Short yellow warning)
Vol+ on Yellow Warning : TWRP
If you want to return to stock erecovery, do these:
Boot into twrp
Push erecovery image to /cache: adb push drag & drop img file to console /cache
Flash erecovery to erecovery: Install > Install Image > Select erecovery image from /cache folder > Pick erecovery_ramdisk partition > Swipe
Spoiler: Passing Safetynet (For Android 12 and Below
Keep in mind that Safetynet is deprecated and Google is encouraging developers to switch to Play Integrity API. To pass safetynet you need to have 3 checkmarks, as such you'll need to follow all 3 instructions I'm about to give you.
Spoiler: Evaluation Type Basic
Disable "Spoof Pixel 5" & Enable Safetynet in phh options then reboot.
Download YASNAC from play store and check for "Evaluation Type" from result.
If it says Basic and others fail you can skip this part.
If test fails or doesn't finish do these:
Install Magisk
Enable Zygisk & Enforce denylist
Install Universal SafetyNet Fix module by kdrag0n
Now check YASNAC again. It should finish test and say Basic in evaluation type.
Spoiler: Basic Integrity Fail
This happens because root is detected most of the time.
If your GSI has Dynamic Root, uncheck root from phh settings.
If your GSI has SU, securize from phh settings.
If you had to flash magisk because of evaluation type, tick google play and google play services in denylist.
If those didn't fix, contact GSI maintainer.
Spoiler: CTS Profile Match Fail
This happens because build fingerprint is not play certified.
Make sure you have safetynet option ticked in phh settings and do these:
Edit /data/adb/phh/secure
Add these 2 lines to bottom:
resetprop_phh ro.build.fingerprint HUAWEI/ANE-LX1/HWANE:9/HUAWEIANE-L01/9.1.0.368C432:user/release-keys
resetprop_phh ro.build.version.security_patch 2020-08-01
Reboot and test again.
Everytime you untick safetynet you have to edit this file again. You can also pick any other fingerprint from here should you choose to. You need both fingerprint and patch date. If you want to simulate other devices add following lines:
resetprop_phh ro.product.brand HUAWEI
resetprop_phh ro.product.device HWANE
resetprop_phh ro.product.manufacturer HUAWEI
resetprop_phh ro.product.model ANE-LX1
resetprop_phh ro.product.name ANE-LX1
Spoiler: Passing Play Integrity (For Android 13 and Beyond)
If you want to pass it you're going to have to read this wall of text. I can't shorten it.
What is Play Integrity:
Google enforces Play Inregrity once your api level is set to 33 (android 13). I currently don't have enough information about it other than apps can decide which checks to perform on your device. One of those checks is called strong integrity. We can't pass strong integrity because it requires hardware backed checks which our device lack. However you can still fool some apps that don't enforce strong integrity.
How you can fool it:
Ever since magisk retired magiskhide, some forks have been made to keep it maintained and improved. One of those forks is Magisk Delta. Before you head over to it's github and install it, you still need to install a valid CTS fingerprint. Then you can install Magisk Delta.
Steps:
Disable Spoof Pixel 5 & Enable Safetynet from phh settings if they exist.
Add these 2 lines to bottom of /data/adb/phh/secure (create if it doesnt exist) & Reboot
resetprop_phh ro.build.fingerprint HUAWEI/ANE-LX1/HWANE:9/HUAWEIANE-L01/9.1.0.368C432:user/release-keys
resetprop_phh ro.build.version.security_patch 2020-08-01
If you have magisk :
- Download Magisk Delta apk
- Change .apk to .zip
- Install it as magisk module
If you don't have magisk :
- Download & install Magisk Delta apk
- Patch recovery_ramdisk & flash it via fastboot
Enable Zygisk and MagiskHide from Magisk Delta App
Install this module : https://github.com/HuskyDG/safetynet-integrity-fix/releases
MAKE SURE GMS IS NOT IN HIDELIST
Reboot and test safetynet. (Feel free to link any app that tests for Play Integrity)
Spoiler: I went back to EMUI, why it looks like aosp?
That happens because EMUI stores it's themes and few stock apps in /data/hw_init folder. When you factory reset with stock recovery, they are preserved. But when you use twrp to factory reset they are removed. Doing factory reset once from twrp is enough to make EMUI think it's corrupted, in acuality it isn't. To fix it you can either let EMUI update from system settings or you can download this, extract hw_init folder and push folder to /data from twrp with this command :
adb push drag & drop hw_init folder to console /data
Flashing LineageOS 16.0​Note:​Stock kernel from EMUI .300> have trouble with wifi. Use Phenix 4.9.319 or above to fix it.
Prerequisites:​
ADB and Fastboot Installed (1)
Google apps package (Pick Pie or 9.0 editions) (1) (2) (3) (4)
LineageOS Zip (From Archive or From Mega)
Phenix Kernel (Else you won't have wi-fi)
TWRP (3.4.0 is needed for factory reset functionality)
Unlocked Bootloader
Spoiler: Steps
Tick "Enable OEM Unlock" from developer options
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash this TWRP: fastboot flash recovery_ramdisk and drag & drop img file to console
Flash Phenix Kernel (Required for Wi-Fi): fastboot flash kernel and drag & drop img file to console
Boot into twrp: power + vol+ while NOT connected to pc
Flash lineage zip: Advanced > ADB Sideload > Swipe to Start Sideload > Write adb sideload and drag & drop zip file to console
Factory reset: Wipe > Swipe Factory Reset
Boot into Vanilla LineageOS or Keep following to flash gapps
Encrypt or Decrypt /Data (Optional): Mount > Tick Vendor > adb push drag & drop fstab file to console /vendor/etc
Flash gapps zip: Advanced > ADB Sideload > Swipe to Start Sideload > Write adb sideload and drag & drop zip file to console
Boot into system: Reboot > System
Getting Stock Firmware Files And Downgrading​Sources:​
A certain russian site (linking is prohibited)
EMUI's System Updater (via root)
Firmware Finder (Revived)
HiSuite
Huawei Update Extractor
HuRUpdater Guide / HuRUpdater Download (For older builds)
HwOTA8 (For Emui 8)
Spoiler: Getting Individual Images
Firmware finder has been revived and you can use that to get your prefered cust or build.
If you need only one image not the whole build, I uploaded each one you'd typically need below.
CUST.img
DTS.img
ERECOVERY_KERNE.img
ERECOVERY_RAMDI.img
ERECOVERY_VBMET.img
ERECOVERY_VENDO.img
FASTBOOT.img
KERNEL.img
ODM.img
PRODUCT.img
RECOVERY_RAMDIS.img
RECOVERY_VBMETA.img
RECOVERY_VENDOR.img
SYSTEM.img
VBMETA.img
VENDOR.img
XLOADER.img
They are from .401 c432.
If you wiped /data once you probably won't have emui themes etc if you go back to emui. To fix that you can push hw_init folder (in data.7z) to /data. Not the contents of it, just put the folder in root of /data. It should be like this: /data/hw_init
Spoiler: Hisuite
Connect your phone to pc and open up hisuite. Check for updates and if it finds one it'll download following files update_full_base.zip, update_full_ANE-L01_hw_eu.zip and update_full_cust_ANE-L01_hw_eu.zip to your documents folder. update_full_base.zip file contains main UPDATE.APP. You can extract images from it with Huawei Update Extractor
Spoiler: EMUI's System Updater
Flash magisk patched image from quick links. After you get root in EMUI allow system updater to do its job and update. It'll ask to reboot, allow it. It will throw you back to system after reboot because recovery is not stock. Get a file manager that allows root access. Allow system updater to download again. But this time do not allow it to reboot. First one downloaded OTA, second one downloaded FullOTA. Which is better for archival purposes. After download is done go to /data/update with a root file explorer. Copy HwOUC folder to internal storage and from there to your pc. There should be 3 folders with numbers. You can find our main update_full_base.zip in one of them.
Spoiler: Downgrading
Spoiler: From EMUI 9 to EMUI 9
Spoiler: Using just the SYSTEM.IMG
Get files of your prefered build. I recommend build .278. Extract SYSTEM.IMG from UPDATE.APP via huawei update extractor and flash it with fastboot flash system . Factory reset with stock recovery then flash any TWRP except for the official ones. Official TWRPs freezes when wiping /data which is what we need to do. After wiping /data boot into system. You should have aosp background with square app icons if you did correctly. Check for system updates and it should find your current build. Download and install.
Spoiler: Using dload from Certain Russian Site
BOOTLOADER WILL RELOCK, DON'T DO THIS IF YOU DON't HAVE YOUR BL CODE
For this you need to have a sd card that is formated as exfat. Fat32 doesn't allow >4gb files so exfat is required. Download your prefered build from Androidhost.ru or mega link above. Inside the zip file you'll find a folder named dload. Extract this folder to somewhere and transfer it to your sd card. Folder structure should look like below. Hw_eu and L01/L21 will depend on your region and single/dual sim status. After this unplug your phone and shut it down. Start pressing vol- vol+ and power all at the same time. Different kind of yellow warning will appear and a screen with blue progress bar over black background will appear. If you downloaded correct variant for your phone it'll start progressing. After process is done you'll boot into stock emui with NO yellow warning. This is because your bootloader is locked. Do whatever you want at this point but remember, unlocking bootloader again will low level factory reset your phone.
-/storage/AAAA-BBBB/dload
---/update_sd
---/ANE-L01_hw_eu
---/ANE-L21_hw_eu
Spoiler: From EMUI 9 to EMUI 8
If I recall correctly there is only one way to do this. You can't dload between emui versions. You also need to be on stock emui for hisuite to function. Some people say a specific hisuite version is required but it wasn't the case for me. Plug your phone to pc, hisuite should show up beside your phone in drives section. Install it and open it. Do whatever it instructs you to function correctly. After you see your phone in app click Update button. Then click on "Earlier Versions". It'll show version 8.0.0.167 along with some warnings. Rest it pretty straightforward. Follow along and it'll return you back to emui 8. But if you're doing this to unlock your bootloader, build .167 is not enough. Exploit that dc-unlocker uses is patched in this version. So you have to roll back further. I had success with .125 build but up until .150 could work. Link to .125 build.
edit ? : Revised guide
Frax3r said:
Hello there! Alive parts of this forum is still filled with simple help requests so I decided to put together a simple all-in-one thread that basically covers most stuff. I don't wanna get into bootloader unlocking because right now only free way to do so is with potatoNV which I do not know how to use. Dc-unlocker is an option too but it is 4€ so pick your poison.​​Special key combos:​
Power + Vol+ = Recovery Mode​
While USB connected, Power + Vol+ = Erecovery Mode​
While USB connected, Vol- = Fastboot​
Plug USB while holding down Vol+ + Vol- = Download Mode​
Power + Vol+ + Vol- = Force Dload​
Flashing LineageOS 16.0​Prerequisites:​
Emui Version below 9.1.0.300
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Los16 zip
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip
Steps:​
Get the Prerequisites
I recommend sending los 16 zip, recovery_ramdis.img and gapps zip to sd card if possible
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash recovery_ramdisk to console and drag twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Install and select los 16 zip file
If you want to disable encryption do it now
Press Install and press Install Image
Select and flash stock recovery_ramdis.img to recovery_ramdisk partition
Press Reboot and select shut down
Press and hold power + vol+ buttons until short yellow warning shows up
Select factory reset and type yes, while it is doing that plug the phone to pc
After factory reset is complete select reboot option and hold down vol- until you're at fastboot
Repeat step 6-7-8
Los 16 don't need to be resized so go to install and select gapps zip
Reboot to system
Flashing Any GSI​Prerequisites:​
Unlocked Bootloader and FRP
adb and fastboot installed on pc
GSI image (1) (2)
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip (Optional)
Notes:​If you're gonna use Phh's AOSP11 and anything that based on it (with the exception of @eremitein's stuff), use arm64-ab-vndklite variant. For anything else use full vndk version. Full vndk version of Phh's AOSP11 does not allow you to resize system on any twrp.
Steps for gapps versions:​
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash system to console and drag gsi .img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
You should be at stock recovery_ramdisk, do a factory reset
You're good to boot up the system
Steps for vanilla versions with custom gapps:​
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
If you want to disable encryption do it now
Send adb reboot bootloader command from console
After restart write fastboot flash system to console and drag gsi .img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
You should be at stock recovery_ramdisk, do a factory reset
Plug your phone back and press reboot from screen
While booting press and hold vol- button until you're at fastboot
Write fastboot flash recovery_ramdisk to console and drag twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Wipe, press Advanced Wipe, select System, press Repair or Change File System, press Resize File System, swipe to resize
Press Install, select and flash gapps zip
Reboot to system
Disable Encryption​Prerequisites:​
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Official TWRP
Stock recovery_ramdis.img
Notes:​You can disable encryption at any step, even after booting, but in order to disable it you have to do a factory reset from stock recovery_ramdis. Because of this I recommend doing between flashing gsi and flashing gapps.
Steps:​
Get the Prerequisites
Boot to TWRP (power + vol+ after shutting down)
Allow modifications
Press Mount, select Vendor
Connect phone to PC
You can do next part 2 ways, if you're good with command line interface use steps 7 through 11, if not skip to step 12
Type adb shell and press enter
Type nano /vendor/etc/fstab.hi6250 and press enter
Remove fileencryption=aes-256-xts:aes-256-cts part from 16th line, make sure there's only one comma between check and reservedsize
Press Ctrl + X then Y and press enter
Go to step 18
Type adb pull /vendor/etc/fstab.hi6250 and press enter
If you have adb in your $PATH go to your user profile folder, if not go to folder where adb.exe resides
Open fstab.hi6250 via a text editor (please use notepad++)
Remove fileencryption=aes-256-xts:aes-256-cts part from 16th line, make sure there's only one comma between check and reservedsize
Save file and open a command prompt
Send this command adb push ./fstab.hi6250 /vendor/etc/fstab.hi6250
View attachment 5422531
Now you need to do a factory reset with stock recovery_ramdis.img, if you have it installed go to step 21 if not do 19 or 20 first
If you have TWRP installed, press Install and press Install Image then select and flash stock recovery_ramdis.img to recovery_ramdisk partition
If not shut down phone, connect it to pc and hold down vol- until you're at fastboot, then write this command fastboot flash recovery_ramdisk and drag recovery_ramdis.img over to console then press enter
Shut down phone and unplug it from pc
Press and hold power+ vol+ until you see short yellow warning
Press Factory Reset and type yes
You've successfully decrypted your phone and you're good to boot up or flash gapps
Getting Stock Firmware Files And Downgrading​Prerequisites:​
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Huawei Update Extractor
Firmware Zip (EMUI8 and EMUI9)
HiSuite
Erecovery
EMUI's System Updater (via root)
HuRUpdater Guide / HuRUpdater Download
HwOTA
Getting stock files are problematic because of huawei. Least shadiest way to get them are the hardest so bear with me.
Androidhost.ru : Click the EMUI9 from prerequisites and search p20 lite. You should get a wide variety of versions to pick from. Make sure to match the Cust in the file to yours if you don't know what you're doing. C432 for Europe for example. After you download the zip file open it up and find the dload folder. You can either get this folder and paste it right into your sd card to force dload or you can open this folder and extract update_sd.zip. Inside update_sd.zip you'll find a file named UPDATE.APP. Use Huawei Update Extractor to open this file and there you'll see all the partitions you need. If HUE gives error while opening it, go to settings and untick "Verify file checksum". You can extract .img files by right clicking and selecting extract option on each partition. Normally you can't open these .img files but after pushing them through simg2img you'll be able to explore them too. But lets be real if you need guides for this, all you need is recovery_ramdis.img.
Using Dload Folder : Your sd card can't be FAT32 for this. FAT32 by nature don't allow files larger than 4gb so you can't get this folder to your sd card. Format it to ExFat via any guide on the internet then copy the dload folder to your sd card's root. It can't be inside any folders. Then shut your phone and press Power + Vol+ + Vol- all at the same time. It'll boot to erecovery which'll check the integrity of files then install them regardless of your EMUI version. So it is a good way to downgrade. Keep in mind tho you can't dload back to emui 8 from emui 9. And any successful dload will lock your bootloader back.
Hisuite : You can actually get firmware files pretty easily with hisuite but it requires real work. You see, hisuite downloads firmware files right into your documents folder. Connect your phone to pc and open up hisuite. Check for updates and if it finds one it'll download following files update_full_base.zip, update_full_ANE-L01_hw_eu.zip and update_full_cust_ANE-L01_hw_eu.zip. It might not get all 3 files most of the time so you have to copy each of them and update a few versions consecutively to get them. Keep in mind, it deletes each update file after it is successful so make sure to make a copy of them some place else. I recommend reverting back to EMUI8 through hisuite and then updating it to latest one to get all files. It is tidious but you need to do this once. It doesnt update you to .370 from .132. It'll send you .132 then .200 then .368 then latest whatever. You can actually use these files with HuRu updater or HwOTA to manually update. Or you can get the UPDATE.APP inside them and extract images with Huawei Update Extractor.
Erecovery : This one requires some network knowledge and it'll only get you the latest version so I don't think it worth the hassle. You need a router that allows you to change dns address for DHCP clients. Which most of them do these days. Now you need to create and run a dns server on your pc. I recommend adguard home. Pihole works too. Use Windows Subsystem For Linux or Docker to install either of them. Once you get them up and working set them to log dns requests. I believe you know where this is going. Open your router's interface and enter adguard home/pihole ip address which maps back to your pc's local address. Check if it works or not by opening up few sites on your phone which should be connected to your wifi and isn't set up to use a different dns server. If all is good open up erecovery on your phone and connect to your wifi. If you set it up correctly it should get the latest version from huawei which will show up on your log. Use that url to download it to your pc and extract it same as others. There was a paid service that used this method to send specific versions to your erecovery.
EMUI's System Updater : This is tricky and my favorite. Get the official TWRP .img and patch it with magisk manager. Then flash it via fastboot. I know, "twrp and magisk? wtf?" just do it. It takes a long time to boot but it works don't question me right now. After you get root in EMUI allow system updater to do its job and update. It'll ask to reboot, allow it. It will throw you back to system after reboot cuz recovery is hijacked. duh. Get a file manager that allows root access. Allow system updater to download again. But this time do not allow it to reboot. First one downloaded OTA, second one downloaded FullOTA. Which is better for archival purposes. After download is done search for a folder named HwOUC in /system. Copy it to internal storage and from there to your pc. You can find our main UPDATE.APP inside update_full_base.zip. Other zips include cust and all that which HuRu and HwOTA requires.
Magisk​Prerequisites:​
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Stock recovery_ramdis.img
Notes:​Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses. But hey it is still working without modifications unlike a-only devices so that's a win. As a foot note, you CAN use twrp image instead of stock recovery_ramdis.img but it'll take longer to boot. Using .380's recovery_ramdis.img on .278 build will not work. Make sure to match your EMUI build with ramdisk you're flashing. Ask me how I know.
Steps to install older version:​
Get the Prerequisites
No, I mean literally just get the Prerequisites and thats it
Open up your browser and find a bin service (pastebin will suffice)
Create a paste with following
Code:
{
"app": {
"version": "8.0.7",
"versionCode": "4834",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk",
"note": "https://cdn.jsdelivr.net/gh/topjohnwu/[email protected]/app/src/main/res/raw/changelog.md"
},
"stub": {
"versionCode": "18",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/stub-release.apk"
},
"uninstaller": {
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip"
},
"magisk": {
"version": "v21.4",
"versionCode": "21400",
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip",
"note": "https://topjohnwu.github.io/Magisk/releases/21400.md",
"md5": "ee6dd05579776e7de3a6077087846e53"
}
}
Get the paste's raw url
Take the recovery_ramdis.img to internal storage
Install magisk manager 8.0.7
Open it's settings and select custom channel
Write the raw url you just created
Allow it to check for updates and it'll find that 21.4 is the latest version
Click install and select recovery_ramdis.img
After it finishes patching get the magisk_patched.img to your pc
Get your phone to fastboot mode
After connecting to pc, write this fastboot flash recovery_ramdisk to console and drag magisk_patched.img over to console and press enter
Now if you enter recovery it'll boot to android with magisk but if you boot normally it will not detect magisk so each time you restart you have to use Power + Vol+ combo in order to get magisk
Remember to switch custom channel to stable channel if you want to receive updates.
I know that you can pretty much reduce the amount of flashing and restarting by flashing twrp to erecovery but since erecovery is a lifeline for most people here I decided not to get into that. But for those who are interested check this thread.​
Edit: Grammar
Click to expand...
Click to collapse
I wish good luck to those who will use your guide .
Among other things, the HwOTA and HuRupdater methods have not worked since February (unless someone has the necessary files stored on the disk). Huawei changed servers and Firmware Finder is dead.
EMUI 8 firmware download doesn't work for the same reasons .
avenger.forsyth said:
I wish good luck to those who will use your guide .
Click to expand...
Click to collapse
Everyone has the right to write a guide, but the author must know what he is writing about. Guide made by the "copy/paste" method will not help anyone very much...
Frax3r said:
Hello there! Alive parts of this forum is still filled with simple help requests so I decided to put together a simple all-in-one thread that basically covers most stuff. I don't wanna get into bootloader unlocking because right now only free way to do so is with potatoNV which I do not know how to use. Dc-unlocker is an option too but it is 4€ so pick your poison.​​Special key combos:​
Power + Vol+ = Recovery Mode​
While USB connected, Power + Vol+ = Erecovery Mode​
While USB connected, Vol- = Fastboot​
Plug USB while holding down Vol+ + Vol- = Download Mode​
Power + Vol+ + Vol- = Force Dload​
Flashing LineageOS 16.0​Prerequisites:​
Emui Version below 9.1.0.300
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Los16 zip
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip
Steps:​
Get the Prerequisites
I recommend sending los 16 zip, recovery_ramdis.img and gapps zip to sd card if possible
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash recovery_ramdisk to console and drag twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Install and select los 16 zip file
If you want to disable encryption do it now
Press Install and press Install Image
Select and flash stock recovery_ramdis.img to recovery_ramdisk partition
Press Reboot and select shut down
Press and hold power + vol+ buttons until short yellow warning shows up
Select factory reset and type yes, while it is doing that plug the phone to pc
After factory reset is complete select reboot option and hold down vol- until you're at fastboot
Repeat step 6-7-8
Los 16 don't need to be resized so go to install and select gapps zip
Reboot to system
Flashing Any GSI​Prerequisites:​
Unlocked Bootloader and FRP
adb and fastboot installed on pc
GSI image (1) (2)
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip (Optional)
Notes:​If you're gonna use Phh's AOSP11 and anything that based on it (with the exception of @eremitein's stuff), use arm64-ab-vndklite variant. For anything else use full vndk version. Full vndk version of Phh's AOSP11 does not allow you to resize system on any twrp.
Steps for gapps versions:​
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash system to console and drag gsi .img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
You should be at stock recovery_ramdisk, do a factory reset
You're good to boot up the system
Steps for vanilla versions with custom gapps:​
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash system to console and drag gsi .img over to console and press enter
If you want to disable encryption do it now
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
You should be at stock recovery_ramdisk, do a factory reset
Plug your phone back and press reboot from screen
While booting press and hold vol- button until you're at fastboot
Write fastboot flash recovery_ramdisk to console and drag twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Wipe, press Advanced Wipe, select System, press Repair or Change File System, press Resize File System, swipe to resize
Press Install, select and flash gapps zip
Reboot to system
Disable Encryption​Prerequisites:​
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Official TWRP
Stock recovery_ramdis.img
Notes:​You can disable encryption at any step, even after booting, but in order to disable it you have to do a factory reset from stock recovery_ramdis. Because of this I recommend doing between flashing gsi and flashing gapps.
Steps:​
Get the Prerequisites
Boot to TWRP (power + vol+ after shutting down)
Allow modifications
Press Mount, select Vendor
Connect phone to PC
You can do next part 2 ways, if you're good with command line interface use steps 7 through 11, if not skip to step 12
Type adb shell and press enter
Type nano /vendor/etc/fstab.hi6250 and press enter
Remove fileencryption=aes-256-xts:aes-256-cts part from 16th line, make sure there's only one comma between check and reservedsize
Press Ctrl + X then Y and press enter
Go to step 18
Type adb pull /vendor/etc/fstab.hi6250 and press enter
If you have adb in your $PATH go to your user profile folder, if not go to folder where adb.exe resides
Open fstab.hi6250 via a text editor (please use notepad++)
Remove fileencryption=aes-256-xts:aes-256-cts part from 16th line, make sure there's only one comma between check and reservedsize
Save file and open a command prompt
Send this command adb push ./fstab.hi6250 /vendor/etc/fstab.hi6250
View attachment 5422531
Now you need to do a factory reset with stock recovery_ramdis.img, if you have it installed go to step 21 if not do 19 or 20 first
If you have recovery_ramdis.img in your sd card, press Install and press Install Image then select and flash stock recovery_ramdis.img to recovery_ramdisk partition
If not shut down phone, connect it to pc and hold down vol- until you're at fastboot, then write this command fastboot flash recovery_ramdisk and drag recovery_ramdis.img over to console then press enter
Shut down phone and unplug it from pc
Press and hold power+ vol+ until you see short yellow warning
Press Factory Reset and type yes
You've successfully decrypted your phone and you're good to boot up or flash gapps
Getting Stock Firmware Files And Downgrading​Prerequisites:​
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Huawei Update Extractor
Firmware Zips
HiSuite
Erecovery
EMUI's System Updater (via root)
HuRUpdater Guide / HuRUpdater Download (don't work anymore)
HwOTA (don't work anymore)
Getting stock files are problematic because of huawei. Least shadiest way to get them are the hardest so bear with me.
Androidhost.ru : Click the "Firmware Zips" from prerequisites and search p20 lite. You should get a wide variety of versions to pick from. Make sure to match the Cust in the file to yours. C432 for Europe for example. After you download the zip file open it up and find a folder named "dload". You can either get this folder and paste it right into your sd card to force dload or you can open this folder and extract update_sd.zip. Inside update_sd.zip you'll find a file named UPDATE.APP. Use Huawei Update Extractor to open this file and there you'll see all the partitions you need. If HUE gives error while opening it, go to settings and untick "Verify file checksum". You can extract .img files by right clicking and selecting extract option on each partition. Normally you can't open these .img files but after pushing them through simg2img you'll be able to explore them too. But lets be real if you need guides for this, all you need is recovery_ramdis.img.
Using Dload Folder : Your sd card can't be FAT32 for this. FAT32 by nature don't allow files larger than 4gb so you can't get this folder to your sd card. Format it to ExFat via any guide on the internet then copy the dload folder to your sd card's root. It can't be inside any folders. Then shut your phone and press Power + Vol+ + Vol- all at the same time. It'll boot to erecovery which'll check the integrity of files then install them regardless of your EMUI version. So it is a good way to downgrade. Keep in mind tho you can't dload back to emui 8 from emui 9. And any successful dload will lock your bootloader back.
Hisuite : You can actually get firmware files pretty easily with hisuite but it requires real work. You see, hisuite downloads firmware files right into your documents folder. Connect your phone to pc and open up hisuite. Check for updates and if it finds one it'll download following files update_full_base.zip, update_full_ANE-L01_hw_eu.zip and update_full_cust_ANE-L01_hw_eu.zip. You only need update_full_base.zip file, others are used to work on HuRUpdater and HwOTA but they are deprecated since February. Inside update_full_base.zip you'll find UPDATE.APP which you can extract images from with Huawei Update Extractor.
Erecovery : This one requires some network knowledge and it'll only get you the latest version so I don't think it worth the hassle. You need a router that allows you to change dns address for DHCP clients. Which most of them do these days. Now you need to create and run a dns server on your pc. I recommend adguard home. Pihole works too. Use Windows Subsystem For Linux or Docker to install either of them. Once you get them up and working set them to log dns requests. I believe you know where this is going. Open your router's interface and enter adguard home/pihole ip address which maps back to your pc's local address. Check if it works or not by opening up few sites on your phone which should be connected to your wifi and isn't set up to use a different dns server. If all is good open up erecovery on your phone and connect to your wifi. If you set it up correctly it should get the latest version from huawei which will show up on your log. Use that url to download it to your pc and extract it same as others. There was a paid service that used this method to send specific versions to your erecovery.
EMUI's System Updater : This is tricky and my favorite. Get the official TWRP .img and patch it with magisk manager. Then flash it via fastboot. I know, "twrp and magisk? wtf?" just do it. It takes a long time to boot but it works don't question me right now. After you get root in EMUI allow system updater to do its job and update. It'll ask to reboot, allow it. It will throw you back to system after reboot cuz recovery is hijacked. duh. Get a file manager that allows root access. Allow system updater to download again. But this time do not allow it to reboot. First one downloaded OTA, second one downloaded FullOTA. Which is better for archival purposes. After download is done search for a folder named HwOUC in /system. Copy it to internal storage and from there to your pc. You can find our main UPDATE.APP inside update_full_base.zip. Other zips include cust and all that which HuRu and HwOTA used to require.
Magisk​Prerequisites:​
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Stock recovery_ramdis.img
Notes:​Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses. But hey it is still working without modifications unlike a-only devices so that's a win. As a foot note, you CAN use twrp image instead of stock recovery_ramdis.img but it'll take longer to boot. Using .380's recovery_ramdis.img on .278 build will not work. Make sure to match your EMUI build with ramdisk you're flashing. Ask me how I know.
Steps to install older version:​
Get the Prerequisites
No, I mean literally just get the Prerequisites and thats it
Open up your browser and find a bin service (pastebin will suffice)
Create a paste with following
Code:
{
"app": {
"version": "8.0.7",
"versionCode": "4834",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk",
"note": "https://cdn.jsdelivr.net/gh/topjohnwu/[email protected]/app/src/main/res/raw/changelog.md"
},
"stub": {
"versionCode": "18",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/stub-release.apk"
},
"uninstaller": {
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip"
},
"magisk": {
"version": "v21.4",
"versionCode": "21400",
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip",
"note": "https://topjohnwu.github.io/Magisk/releases/21400.md",
"md5": "ee6dd05579776e7de3a6077087846e53"
}
}
Get the paste's raw url
Take the recovery_ramdis.img to internal storage
Install magisk manager 8.0.7
Open it's settings and select custom channel
Write the raw url you just created
Allow it to check for updates and it'll find that 21.4 is the latest version
Click install and select recovery_ramdis.img
After it finishes patching get the magisk_patched.img to your pc
Get your phone to fastboot mode
After connecting to pc, write this fastboot flash recovery_ramdisk to console and drag magisk_patched.img over to console and press enter
Now if you enter recovery it'll boot to android with magisk but if you boot normally it will not detect magisk so each time you restart you have to use Power + Vol+ combo in order to get magisk
Remember to switch custom channel to stable channel if you want to receive updates.
I know that you can pretty much reduce the amount of flashing and restarting by flashing twrp to erecovery but since erecovery is a lifeline for most people here I decided not to get into that. But for those who are interested check this thread.​
Edit: Grammar
Edit 2: Update about HwOTA and HuRUpdate
Click to expand...
Click to collapse
Oh, man! Are you serious?
I don't know what anyone expects from a guide... Is it better to just repeat the same thing over and over again? "Flash system with fastboot, factory reset with stock recovery, flash and boot twrp, resize system, flash gapps" is literally the summary of this. That summary is what you'll get as an answer if you ask for help on any telegram group. Instead of saying flash twrp, I wrote how you can flash twrp. Thats why it's so long. This guide is for "how" not "what".
Frax3r said:
I don't know what anyone expects from a guide... Is it better to just repeat the same thing over and over again? "Flash system with fastboot, factory reset with stock recovery, flash and boot twrp, resize system, flash gapps" is literally the summary of this. That summary is what you'll get as an answer if you ask for help on any telegram group. Instead of saying flash twrp, I wrote how you can flash twrp. Thats why it's so long. This guide is for "how" not "what".
Click to expand...
Click to collapse
I would say that even so far, people have managed to install GSI, Magisk, etc. .
Btw, Recovery and eRecovery are the same for all models and build numbers . They are even compatible with LLD and BND models.
Frax3r said:
Thats why it's so long
Click to expand...
Click to collapse
It is long because because of procedures that are too complicated, e.g. chapter "Disable Encryption" .
It is long because of duplicate procedures, e.g. chapter "Flashing Any GSI".
Sorry but Chapter "Magisk" is useless. Nowadays nobody needs to install the old Magisk. Rather focus on some of the nuances of installing Magisk on EMUI 9.1 that would be helpful.
Frax3r said:
Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses.
Click to expand...
Click to collapse
No comment...
Frax3r said:
Get the official TWRP .img and patch it with magisk manager
Click to expand...
Click to collapse
No comment...
Have a good day!
Frax3r said:
Hello there! Alive parts of this forum is still filled with simple help requests so I decided to put together a simple all-in-one thread that basically covers most stuff. I don't wanna get into bootloader unlocking because right now only free way to do so is with potatoNV which I do not know how to use. Dc-unlocker is an option too but it is 4€ so pick your poison.
I have uploaded all my resources for this device to here. Inside EMUI folder you'll find some of the versions that I archived with the methods I explained on getting firmwares section. You can find recovery_ramdis.img from each of these version inside RECOVERY_RAMDISK folder as well.​​Special key combos:​
Power + Vol+ = Recovery Mode​
While USB connected, Power + Vol+ = Erecovery Mode​
While USB connected, Vol- = Fastboot​
Plug USB while holding down Vol+ + Vol- = Download Mode​
Power + Vol+ + Vol- = Force Dload​
Flashing LineageOS 16.0​Prerequisites:​
Emui Version below 9.1.0.300
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Los16 zip
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip
Steps:​
Get the Prerequisites
I recommend sending los 16 zip, recovery_ramdis.img and gapps zip to sd card if possible
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send this command from pc : adb reboot bootloader
When you're at fastboot write fastboot flash recovery_ramdisk to console and drag & drop twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Install and select los 16 zip file
If you want to disable encryption do it now
Press Install and press Install Image
Select and flash stock recovery_ramdis.img to recovery_ramdisk partition
Press Reboot and select Recovery
Press Factory Reset and type yes, while it is doing that plug the phone to pc
Press Reboot and when screen is off start holding down vol- until you're at fastboot
Repeat step 6-7-8
Los 16 don't need to be resized so press Install and select gapps zip
Press Reboot System
Flashing Any GSI​Prerequisites:​
Unlocked Bootloader and FRP
adb and fastboot installed on pc
GSI image (1) (2)
Official TWRP
Stock recovery_ramdis.img in recovery_ramdisk partition
Your choice of gapps zip (Optional)
Notes:​If you're gonna use Phh's AOSP11 and anything that based on it (with the exception of @eremitein's stuff), use arm64-ab-vndklite variant. For anything else use full vndk version. Full vndk version of Phh's AOSP11 does not allow you to resize system on any twrp.
Steps for gapps versions:​
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send this command from pc : adb reboot bootloader
When you're at fastboot write fastboot flash system to console and drag & drop gsi .img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Press Factory Reset and type yes
When it is done press Reboot
Steps for vanilla versions with custom gapps:​
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send this command from pc : adb reboot bootloader
When you're at fastboot write fastboot flash system to console and drag & drop gsi .img over to console and press enter
If you want to disable encryption do it now
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Press Factory Reset and type yes, while it is doing that plug the phone to pc
Press Reboot and when screen is off start holding down vol- until you're at fastboot
Write fastboot flash recovery_ramdisk to console and drag & drop twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Wipe, press Advanced Wipe, select System, press Repair or Change File System, press Resize File System, swipe to resize then go back to main screen
Press Install, select and flash gapps zip
Press Reboot System
Disable Encryption​Prerequisites:​
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Official TWRP
Stock recovery_ramdis.img
Notes:​You can disable encryption at any step, even after booting, but in order to disable it you have to do a factory reset from stock recovery_ramdis. Because of this I recommend doing between flashing gsi and flashing gapps.
Steps:​
Get the Prerequisites
Flash and boot TWRP
Allow modifications
Press Mount, select Vendor
Connect phone to PC
You can do next part 2 ways, if you're good with command line interface use steps 7 through 11, if not skip to step 12
Type adb shell and press enter
Type nano /vendor/etc/fstab.hi6250 and press enter
Remove fileencryption=aes-256-xts:aes-256-cts from 16th line, make sure there's only one comma between check and reservedsize
Press Ctrl + X then Y and press enter
Go to step 18
Type adb pull /vendor/etc/fstab.hi6250 and press enter
If you have adb in your $PATH go to your user profile folder, if not go to folder where adb.exe is
Open fstab.hi6250 via a text editor (please use notepad++)
Remove fileencryption=aes-256-xts:aes-256-cts from 16th line, make sure there's only one comma between check and reservedsize
Save file and open a command prompt
Send this command adb push ./fstab.hi6250 /vendor/etc/fstab.hi6250
View attachment 5422531
Now you need to do a factory reset with stock recovery_ramdis.img
If you have recovery_ramdis.img in your sd card, press Install and press Install Image then select recovery_ramdis.img and pick recovery_ramdisk partition
If you don't have recovery_ramdis.img in your sd card, shut down phone, connect it to pc and hold down vol- until you're at fastboot, then write this command fastboot flash recovery_ramdisk and drag recovery_ramdis.img over to console then press enter
Shut down your phone and unplug it from pc
Press and hold power+ vol+ until you see short yellow warning
Press Factory Reset and type yes
You've successfully decrypted your phone and you're good to boot up or flash gapps
Getting Stock Firmware Files And Downgrading​Prerequisites:​
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Huawei Update Extractor
Firmware Zips
HiSuite
Erecovery
EMUI's System Updater (via root)
HuRUpdater Guide / HuRUpdater Download (don't work anymore)
HwOTA (don't work anymore)
Getting stock files are problematic because of huawei. Least shadiest way to get them are the hardest so bear with me.
Androidhost.ru : Click the "Firmware Zips" from prerequisites and search p20 lite. You should get a wide variety of versions to pick from. Make sure to match the Cust in the file to yours. C432 for Europe for example. After you download the zip file open it up and find a folder named "dload". You can either get this folder and paste it right into your sd card to force dload or you can open this folder and extract update_sd.zip. Inside update_sd.zip you'll find a file named UPDATE.APP. Use Huawei Update Extractor to open this file and there you'll see all the partitions you need. If HUE gives error while opening it, go to settings and untick "Verify file checksum". You can extract .img files by right clicking and selecting extract option on each partition. Normally you can't open these .img files but after pushing them through simg2img you'll be able to explore them too. But lets be real if you need guides for this, all you need is recovery_ramdis.img.
Using Dload Folder : Your sd card can't be FAT32 for this. FAT32 by nature don't allow files larger than 4gb so you can't get this folder to your sd card. Format it to ExFat via any guide on the internet then copy the dload folder to your sd card's root. It can't be inside any folders. Then shut your phone and press Power + Vol+ + Vol- all at the same time. It'll boot to erecovery which'll check the integrity of files then install them regardless of your EMUI version. So it is a good way to downgrade. Keep in mind tho you can't dload back to emui 8 from emui 9. And any successful dload will lock your bootloader back.
Hisuite : You can actually get firmware files pretty easily with hisuite but it requires real work. You see, hisuite downloads firmware files right into your documents folder. Connect your phone to pc and open up hisuite. Check for updates and if it finds one it'll download following files update_full_base.zip, update_full_ANE-L01_hw_eu.zip and update_full_cust_ANE-L01_hw_eu.zip. You only need update_full_base.zip file, others are used to work on HuRUpdater and HwOTA but they are deprecated since February. Inside update_full_base.zip you'll find UPDATE.APP which you can extract images from with Huawei Update Extractor.
Erecovery : This one requires some network knowledge and it'll only get you the latest version so I don't think it worth the hassle. You need a router that allows you to change dns address for DHCP clients. Which most of them do these days. Now you need to create and run a dns server on your pc. I recommend adguard home. Pihole works too. Use Windows Subsystem For Linux or Docker to install either of them. Once you get them up and working set them to log dns requests. I believe you know where this is going. Open your router's interface and enter adguard home/pihole ip address which maps back to your pc's local address. Check if it works or not by opening up few sites on your phone which should be connected to your wifi and isn't set up to use a different dns server. If all is good open up erecovery on your phone and connect to your wifi. If you set it up correctly it should get the latest version from huawei which will show up on your log. Use that url to download it to your pc and extract it same as others. There was a paid service that used this method to send specific versions to your erecovery.
EMUI's System Updater : This is tricky and my favorite. Get the official TWRP .img and patch it with magisk manager. Then flash it via fastboot. I know, "twrp and magisk? wtf?" just do it. It takes a long time to boot but it works don't question me right now. After you get root in EMUI allow system updater to do its job and update. It'll ask to reboot, allow it. It will throw you back to system after reboot cuz recovery is hijacked. duh. Get a file manager that allows root access. Allow system updater to download again. But this time do not allow it to reboot. First one downloaded OTA, second one downloaded FullOTA. Which is better for archival purposes. After download is done search for a folder named HwOUC in /system. Copy it to internal storage and from there to your pc. You can find our main UPDATE.APP inside update_full_base.zip. Other zips include cust and all that which HuRu and HwOTA used to require.
Magisk​Prerequisites:​
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Stock recovery_ramdis.img
Notes:​Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses. But hey it is still working without modifications unlike a-only devices so that's a win. New installer for magisk kinda broken for our device, because of that I recommend installing and booting an older version. It's safe to update it afterwards from magisk manager. As a foot note, you CAN use twrp image instead of stock recovery_ramdis.img but it'll take longer to boot. Using .380's recovery_ramdis.img on .278 build will not work. Make sure to match your EMUI build with ramdisk you're flashing. Ask me how I know.
Steps to install older version:​
Get the Prerequisites
No, I mean literally just get the Prerequisites and thats it
Open up your browser and find a bin service (pastebin will suffice)
Create a paste with following
Code:
{
"app": {
"version": "8.0.7",
"versionCode": "4834",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk",
"note": "https://cdn.jsdelivr.net/gh/topjohnwu/[email protected]/app/src/main/res/raw/changelog.md"
},
"stub": {
"versionCode": "18",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/stub-release.apk"
},
"uninstaller": {
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip"
},
"magisk": {
"version": "v21.4",
"versionCode": "21400",
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip",
"note": "https://topjohnwu.github.io/Magisk/releases/21400.md",
"md5": "ee6dd05579776e7de3a6077087846e53"
}
}
Get the paste's raw url
Take the recovery_ramdis.img to internal storage
Install magisk manager 8.0.7
Open it's settings and select custom channel
Write the raw url you just created
Allow it to check for updates and it'll find that 21.4 is the latest version
Click install and select recovery_ramdis.img
After it finishes patching get the magisk_patched.img to your pc
Get your phone to fastboot mode
After connecting to pc, write this fastboot flash recovery_ramdisk to console and drag magisk_patched.img over to console and press enter
Now if you enter recovery it'll boot to android with magisk but if you boot normally it will not detect magisk so each time you restart you have to use Power + Vol+ combo in order to get magisk
Remember to switch custom channel to stable channel if you want to receive updates.
I know that you can pretty much reduce the amount of flashing and restarting by flashing twrp to erecovery but since erecovery is a lifeline for most people here I decided not to get into that. But for those who are interested check this thread.​
Edit: Grammar
Edit 2: Update about HwOTA and HuRUpdate
Edit 3: Simplify some steps and add my own mega.nz archive
Click to expand...
Click to collapse
Only now I have time to read your instructions carefully, what is this nonsense ???
Frax3r said:
Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses. But hey it is still working without modifications unlike a-only devices so that's a win. New installer for magisk kinda broken for our device, because of that I recommend installing and booting an older version.
Click to expand...
Click to collapse
I'll give you some advice if I may - don't write about things you don't understand! And this applies not only to Magisk.
avenger.forsyth said:
It is long because because of procedures that are too complicated, e.g. chapter "Disable Encryption" .
Click to expand...
Click to collapse
Is it better to just link decryption zip or write what that decryption zip does?
avenger.forsyth said:
It is long because of duplicate procedures, e.g. chapter "Flashing Any GSI".
Click to expand...
Click to collapse
People use gapps versions because they don't want to waste time by flashing zips. That's why it's 2 part. Gapps one is shorter.
Frax3r said:
Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses.
Click to expand...
Click to collapse
Magisk-in-recovery as in "magisk hijacking recovery" not "installing magisk using recovery". You can't even find huawei section in it's installation instructions. Look here and here. As for the nuance you asked, installing magisk in EMUI is literally same as installing it in GSI or LOS. You patch the image, flash the image, boot the image.
Frax3r said:
As a foot note, you CAN use twrp image instead of stock recovery_ramdis.img but it'll take longer to boot. Using .380's recovery_ramdis.img on .278 build will not work. Make sure to match your EMUI build with ramdisk you're flashing. Ask me how I know.​
Click to expand...
Click to collapse
I added "ask me how I know" part for a reason. I tried. You CAN patch official twrp with magisk and it WILL boot. If a person unlocks their bootloader for the first time how is he supposed to get stock recovery_ramdis.img? Get the mmcblock of recovery_ramdisk? How is he supposed to do that if he flashes twrp over to recovery_ramdisk partition? We can't use "fastboot boot" so that's out of option. Use a different recovery_ramdis.img you might say. I TRIED. .380's recovery_ramdis.img patched with latest magisk won't boot if you're at .278. I created a folder where I patched .380 recovery with each different version of magisk starting from 20.4 up to latest version and none of them booted on los 16 which was installed upon .278. It is not universal as you might think.
-Alf- said:
Only now I have time to read your instructions carefully, what is this nonsense ???
I'll give you some advice if I may - don't write about things you don't understand! And this applies not only to Magisk.
Click to expand...
Click to collapse
Care to elaborate? I am open to constructive criticism. As for what I know, I do know that you won't find yourself bootlooping if you follow these steps by the letter. I saw your instructions on los 16 and other threads too. Here's a criticism for you, do not tell people to wipe /data or factory reset with twrps and especially do not expect them to flash twrp over to erecovery. Wiping /data or factory reset from twrp always resulted in phone freezing for me. I guess twrp in erecovery could fix freezing but there's a reason why they are asking for help and you expect them to overwrite their only lifeline. 1-2 extra rebooting and flashing won't hurt anyone. When you wipe /data or factory reset with most twrps, including official one, some folders that needs to be untouched (huawei am i right) gets deleted. So you have to use stock recovery_ramdis.img or an advanced twrp which compansates it. Check the tishserg's twrp for example. I use that not the official twrp for these things. And it can write to erecovery which is exactly why I didn't advocate on using it in this guide. Have a good day...
Frax3r said:
Here's a criticism for you, do not tell people to wipe /data or factory reset with twrps and especially do not expect them to flash twrp over to erecovery. Wiping /data or factory reset from twrp always resulted in phone freezing for me.
Click to expand...
Click to collapse
Use recommended TWRP, not 3.4.0. and above, which is not fully compatible with hi6250 devices (including official one). Did you know?
Btw, I never advised anyone to do a factory reset in TWRP, on the contrary
https://forum.xda-developers.com/t/...twrp-3-2-1-0-12-05-2018.3789306/post-85472227
Frax3r said:
New installer for magisk kinda broken for our device, because of that I recommend installing and booting an older version.
Click to expand...
Click to collapse
Everyone knows that it is possible to install the latest version right away...
-Alf- said:
Use recommended TWRP, not 3.4.0. and above, which is not fully compatible with hi6250 devices (including official one). Did you know?
Btw, I never advised anyone to do a factory reset in TWRP, on the contrary
https://forum.xda-developers.com/t/...twrp-3-2-1-0-12-05-2018.3789306/post-85472227
Everyone knows that it is possible to install the latest version right away...
Click to expand...
Click to collapse
Yes you said that here. However my own experience says otherwise. Before my current los 16 installation I used official 3.5.2. Flashed los, flashed stock recovery, flashed phenix kernel, flashed gapps all from it. I even used nano from adb shell to edit fstab.hi6250. I used backup and restore only on kernel partition but it was successful anyway. What that incompatibility be? Is it boot override thing? If you have twrp in recovery and send reboot to recovery from android it just keeps booting to twrp in each reboot even tho you select otherwise from twrp's reboot menu. BTW tishserg's twrp have an option to remove that override if you find yourself in that loop. As for factory reset part, you said format /data here. We had a discussion here because of that. My bad on reading wrong. While writing this I realised incompatibility is probably about formating /data on twrp 3.4.0 and above. If that is the case I'll update the post. Good thing I didn't tell people to format /data from twrp. My steps might be long but they are correct. It is wrong to call all this a nonsense.
Everyone might know it is possible to install latest magisk but not everyone knows how to install an older version now that magisk's future is uncertain. After magisk removes magiskhide from its code people are gonna wanna go back to latest version that worked while waiting for module version of it. Patching twrp image with magisk is highlight of this post but it is literally what flashing magisk.zip (.apk to .zip) from twrp does with the latest version. If patching twrp is bad then why is my guide to installing an older version, which allows you to select which image to patch, is the target? + With that .json, you can make magisk manager patch the image with your own modified version of magisk should you upload it somewhere and change the links.
Hi,
I'm building trying to port Ubuntu Touch to this device and I'm running into a few challenges. I have already reverted to stock 2 times and re-unlocked the bootloader (starting from EMUI 9). So far I have only flashed recovery_ramdisk with twrp as I was worried I might not be able to revert to stock if I flashed erecovery.
Question 1: Is this correct or a misunderstanding?
Installing Ubuntu Touch requires the data partition to be formatted to ext4. I can do that from twrp, but someone (maybe you) wrote that wiping the data partition with twrp was liable to create trouble.
Q2: Same question as above.
I understand Huawei requires the kernel and ramdisk to reside in separate images on separate partitions. So I have used this guide (https://wiki.postmarketos.org/wiki/Huawei_P10_Lite_(huawei-warsaw)) to separate the boot.img produced in my build, and then flashed these two image files to the kernel and recovery_ramdisk partitions respectively. However, examining the LOS 16.0 rom that can be installed, I see that it contains a "boot.img".
Q3: Can I flash my boot.img without separating into kernel and ramdisk first, and if so, which partition should I flash?
Q4: After flashing the image files I built (kernel.img and ramdisk.img along with system.img), do I need to reboot to a recovery (if so, which?) and wipe something (if so, what?) before rebooting?
aribk said:
Hi,
Question 1: Is this correct or a misunderstanding?
Q2: Same question as above.
Q3: Can I flash my boot.img without separating into kernel and ramdisk first, and if so, which partition should I flash?
Q4: After flashing the image files I built (kernel.img and ramdisk.img along with system.img), do I need to reboot to a recovery (if so, which?) and wipe something (if so, what?) before rebooting?
Click to expand...
Click to collapse
Hello,
If I understood you correctly you're asking if you can flash stock erecovery after you've modified it. Answer is yes, you can flash twrp on it and when you're done you can flash stock erecovery image over it. Fastboot won't allow you to flash anything on erecovery partition tho. So you need to use certain twrps that are capable of flashing over erecovery. s_mak and tishserg twrps should allow that iirc. First flash any one of those twrps to recovery_ramdisk then boot into it afterwards flash same twrp image to erecovery partition from inside the twrp.
Yes, if you look at last few replies in this thread that was exactly the conversation. However that is only the case with official twrp. If you use s_mak or tishserg's twrps from the mega link in the thread you should be able to wipe without a problem.
Last 2 questions are beyond me I'm afraid. PostparketOS and Ubuntu Touch are inherently very different to android and they could require some stuff that are unique to them. However I would imagine you wouldn't need to wipe anything after flashing those images.
aribk said:
Hi,
I'm building trying to port Ubuntu Touch to this device and I'm running into a few challenges. I have already reverted to stock 2 times and re-unlocked the bootloader (starting from EMUI 9). So far I have only flashed recovery_ramdisk with twrp as I was worried I might not be able to revert to stock if I flashed erecovery.
Question 1: Is this correct or a misunderstanding?
Installing Ubuntu Touch requires the data partition to be formatted to ext4. I can do that from twrp, but someone (maybe you) wrote that wiping the data partition with twrp was liable to create trouble.
Q2: Same question as above.
I understand Huawei requires the kernel and ramdisk to reside in separate images on separate partitions. So I have used this guide (https://wiki.postmarketos.org/wiki/Huawei_P10_Lite_(huawei-warsaw)) to separate the boot.img produced in my build, and then flashed these two image files to the kernel and recovery_ramdisk partitions respectively. However, examining the LOS 16.0 rom that can be installed, I see that it contains a "boot.img".
Q3: Can I flash my boot.img without separating into kernel and ramdisk first, and if so, which partition should I flash?
Q4: After flashing the image files I built (kernel.img and ramdisk.img along with system.img), do I need to reboot to a recovery (if so, which?) and wipe something (if so, what?) before rebooting?
Click to expand...
Click to collapse
aribk said:
So far I have only flashed recovery_ramdisk with twrp as I was worried I might not be able to revert to stock if I flashed erecovery.
Question 1: Is this correct or a misunderstanding?
Click to expand...
Click to collapse
Misunderstanding. You can revert to stock via eRecovery & wi-fi.
Huawei has Recovery and eRecovery, each has different functions.
You can use the following combinations in your phone:
- Recovery + eRecovery (stock FW)
- TWRP instead of Recovery + eRecovery
- Recovery + TWRP instead of eRecovery
aribk said:
wiping the data partition with twrp was liable to create trouble.
Q2: Same question as above.
Click to expand...
Click to collapse
Same answer as above. Formatting (not wiping) data with TWRP 3.4+ is dangerous (running stock EMUI).
Q3: All this only works on EMUI 8 as far as I know.
Q4: follow the instructions, imo.
P.S.: as you can see, mobile Linux projects such as Ubuntu Touch, postmarketOS or Sailfish OS work only partially on Hua/Ho phones,but we already talked about that .
-Alf- said:
Same answer as above. Formatting (not wiping) data with TWRP 3.4+ is dangerous (running stock EMUI).
Click to expand...
Click to collapse
Re-reading your answer above, I see I'd like to double check: Is this dangerous only if you are running stock EMUI, or would it also be dangerous to use TWRP 3.4+ to format the data partition when you wish to run a different system on the device, as in my case?
aribk said:
aribk said:
or would it also be dangerous to use TWRP 3.4+ to format the data partition when you wish to run a different system on the device, as in my case?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hard to say, no one has experience with different system . But I don't think it matters - see Mr. Frax3r's post above (and read carefully bro ).
I'm bumping the thread, few improvements are made for android 13.
Thank you for the update.
I have modified Phenix_4.9.235-phenix-1.0 rebased on Harmonyos to make it permissive which make most A13 GSIs boot normally on my phone. I have attached the updated one.
Frax3r said:
After you set up your phone and made sure you don't need stock recovery, flash magisk:
Click to expand...
Click to collapse
magisk-patched stock recovery remains functional, available and usable.

Question Find Device storage corrupted. Your device is unsafe now.( POCO F3 and Other MIUI Devices)

Last night I do have a problem with the custom rom that I have installed, because of the battery problem keeps on dropping, so I decided to go back to the official stock rom which is for global however after flashing the fastboot rom via Miflash Tool, I have a welcome message that says Find Device storage corrupted. Your device is unsafe now. I thought that I just need to activate this to the device admin, after a reboot I tried to check it out if this message if this message will still pop up, and it keeps on popping up. I have flashed the rom again and it keeps on happening.
Things that I have Tried:
So I tried to check for other ways that I could get rid of this but this doesnt work on the terminal via TWRP. "
[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now".
[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now". How to fix "Find Device storage corrupted. Your device is unsafe now" ? (At your own risk... I'm not responsible for damage or brick) Required : - Be rooted and...
forum.xda-developers.com
".
The one that works:
Things that you needed:
1. Download Mi Flash Tool(https://www.xiaomiflash.com/)
2. Minimal ADB and Fastboot
3. 7zip or BreeZip
4. TWRP A12(
TWRP A12.rar
drive.google.com
) if you are using other MIUI and devices and want to check it this will work then just use your twrp that is recommended for your mui device.
5. Global Rom (https://xiaomifirmwareupdater.com/miui/alioth/stable/V12.5.6.0.RKHMIXM/)
warning: make sure that you are using the right rom for your device, my device that I am using is a global variant so I need to flash a global version, if you are using other MIUI device and want to check it out just download the miui that works for you must be on a later update of the rom if the latest current rom that you are working on right now didnt work.
Steps to follow.
1. Extract the Rom which you have downloaded using the 7zip or BreeZip, so for me I extracted the version 12.5.6.0 take note that this is not the latest rom but for this to work we need to be in a later update this rom is an android version 11.
2. after extracting the fastboot rom file type TGZ you will notice that the one that you extracted is on a TAR file type, and you need to extract the TAR file type for you to have the folder "alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global_62b4f5d6ca"
3. Using the Mi Flash Tool, just pick the clean all and start the flashing.
4. After flashing the rom set up the phone but do not update it.
5. On your extracted folder for the rom go to the folder that says images and look for 'persist" this is an img file. copy the persist img file and paste it on your Internal memory of your phone.
6. Turn off your phone and go to fastboot by pressing the volume down as well as the power button. You will notice that the fastboot logo is the older version since we are using an older rom.
7. Extract the TWRP A12 and you should have the disc recovery image of it, copy and paste it on your Minimal ADB and Fastboot folder and rename it "recovery".
8. While you are on the Minimal ADB Fastboot folder make sure that your phone is plug in to the usb port on your computer, click the cmd here on the Minimal ADB and Fastboot Folder and you should able to run the cmd.
9. run the following commands:
fastboot devices (then press the enter)
warning: make sure that the fastboot devices is able to see your device.
after seeing the device run this command:
fastboot boot recovery.img (then press enter)
the device should boot to the twrp if its on chinese look for settings and set it to english. we are not flashing the twrp we are just going to use it temporarily thats why we are only going to boot it to twrp recovery.
10. On your twrp, go to install, click the install image and look for your persist.img that we have copied earlier to your internal memory
you should find it on the sdcard folder. just flash and you will see that you have successfully flashed the persist image and then just reboot your phone.
After rebooting your phone you will notice that the "Find Device storage corrupted. Your device is unsafe now." will not prompt. Since I already have the current fastboot rom I have tried to flash the current fastboot rom and locked my device and fixed the problem permanently without any problem.
You wrote too much for something that could be written in a few sentences. And why would anyone downgrade an android or flash a clean fastboot ROM? (Android or MIUI version doesn't matter)
Summary guide:
1. Download the fastboot ROM from here and extract the "persist.img" image or dump the "persistbak" partition from your device and rename this file to "persist.img"
2. Put persist.img into your device's internal memory and go to TWRP
3. In TWRP, go to: Install> select install image> select file persist.img> select "Persist" partition
4. Restart the device, it should work fine
uvzen said:
You wrote too much for something that could be written in a few sentences. And why would anyone downgrade an android or flash a clean fastboot ROM? (Android or MIUI version doesn't matter)
Summary guide:
1. Download the fastboot ROM from here and extract the "persist.img" image or dump the "persistbak" partition from your device and rename this file to "persist.img"
2. Put persist.img into your device's internal memory and go to TWRP
3. In TWRP, go to: Install> select install image> select file persist.img> select "Persist" partition
4. Restart the device, it should work fine
Click to expand...
Click to collapse
Wrote it down for the newbies that doesnt know how to fix anyway thanks for the summary. I have to downgraded it because the latest current rom doesnt work give me "invalid sparse file format at header magic" error as I flash the persist.img file, via twrp.
mizuhored said:
Wrote it down for the newbies that doesnt know how to fix anyway thanks for the summary. I have to downgraded it because the latest current rom doesnt work give me "invalid sparse file format at header magic" error as I flash the persist.img file, via twrp.
Click to expand...
Click to collapse
If you are using TWRP from Nebrassy then use skkk TWRP or OrangeFox. Flashing persist should work fine on both recoveries (I did it myself recently).
uvzen said:
If you are using TWRP from Nebrassy then use skkk TWRP or OrangeFox. Flashing persist should work fine on both recoveries (I did it myself recently).
Click to expand...
Click to collapse
Thats great but this is the one that works for me anyways. At least we have found out the things that we needed in order for it to be fixed. Just sharing my ideas and how did I fixed the problem myself. Thanks for sharing of your ideas. Hoping that we could share our ideas to others as well. Been on a nightmare last night cant sleep because of this problem. Trying to figure out what to do since using the cmds via terminal on twrp doesnt work for me. Need to downgrade for me to fix it.
mizuhored said:
Thats great but this is the one that works for me anyways. At least we have found out the things that we needed in order for it to be fixed. Just sharing my ideas and how did I fixed the problem myself. Thanks for sharing of your ideas. Hoping that we could share our ideas to others as well. Been on a nightmare last night cant sleep because of this problem. Trying to figure out what to do since using the cmds via terminal on twrp doesnt work for me. Need to downgrade for me to fix it.
Click to expand...
Click to collapse
Could you please confirm if flashing persist.img doesn't mess up with sensor like fingerprint, l1, compass etc..? I have seen other forums talking about possibility of losing these in case perist is flashed from rom. I have this message for some time now, but all other sensors work fine, even l1 certification and saftynet. Thanks in advance.

Categories

Resources