Related
Hi all,
Yesterday i flashed miui LP on my Redmi 2 Prime. In the evening i tried to flash the miui KK with fastboot rom. But ended up with unspecified error . I tried many things but no luck. Then i followed direct method and that worked. Following is the procedure.
Note:
1. This will erase all your data and internal storage so better you backup them first.
2. I'm not responsible if anything goes wrong with your device.
Requirement:
1. Minimal ADB and Fastboot
2. Fastboot rom
3. Mi Pc Suite (for drivers, you can skip if already installed drivers)
Preparing:
1. Install Mi Pc Suite.
2. Install Minimal ADB and Fastboot.
3. Extract fastboot rom anywhere.
4. Copy all the files from images folder to the directory where Minimal ADB And fastboot is installed.
for example C:\Program Files (x86)\Minimal ADB and Fastboot
Procedure:
1. Connect your phone to pc in fastboot mode,
your Pc will install some drivers automatically.
2. Go to Minimal ADB and Fastboot directory .
3. Hold shift and right click.
4. Click open command window here.
5. Enter fastboot devices command.
If you see your device name in list of devices attached in command window then your good to go.
6. Now enter the following commands given below one by one in sequence.
fastboot flash partition gpt_both0.bin
fastboot flash tz tz.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash tzbak tz.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash hypbak hyp.mbn
fastboot erase boot
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash persist persist.img
fastboot flash sec sec.dat
fastboot flash splash splash.img
fastboot reboot
Or
Simply put Flash All.bat (Attached Bellow) in Minimal ADB and Fastboot directory and double click on it (No need to enter those commands). Your Devices will reboot automatically when flashing done.
congrats
Hit thanks
It fails at the first step. Can't flash the partition table, it always says "FAILED (remote: failed to write partition)"
I've tried several different ROM packs, even tried one for a different Redmi 2 version, and still can't do it.
did you place all the files in minimal adb and fastboot folder?
gabika1941 said:
It fails at the first step. Can't flash the partition table, it always says "FAILED (remote: failed to write partition)"
I've tried several different ROM packs, even tried one for a different Redmi 2 version, and still can't do it.
Click to expand...
Click to collapse
did you place all the files in minimal adb and fastboot folder? And what you mean by using several different rom package? This method is only for fastboot rom made for redmi 2 only. Make sure your phone is detected by PC in fastboot mode with command fastboot devices.
I have tested this method three times without any errors. You are surely doing something wrong.
screenshot
gabika1941 said:
It fails at the first step. Can't flash the partition table, it always says "FAILED (remote: failed to write partition)"
I've tried several different ROM packs, even tried one for a different Redmi 2 version, and still can't do it.
Click to expand...
Click to collapse
Can you attach a screenshot of your minimal adb and fastboot folder here. Also attach screenshot of your cmd window when you face error.
rkmadotra said:
Can you attach a screenshot of your minimal adb and fastboot folder here. Also attach screenshot of your cmd window when you face error.
Click to expand...
Click to collapse
i have a similar problem :
C:\Xiaomi\wt86047_pro_images_6.3.25_20160307.0000.16_5.1_cn_ee14351bfb\images>fastboot.exe flash partition gpt_backup0.bin
target reported max download size of 268435456 bytes
sending 'partition' (16 KB)...
OKAY [ 0.005s]
writing 'partition'...
FAILED (remote: failed to write partition)
finished. total time: 0.018s
C:\Xiaomi\wt86047_pro_images_6.3.25_20160307.0000.16_5.1_cn_ee14351bfb\images>
Click to expand...
Click to collapse
I have a 2014813 , was using a moded 2014811 rom on it. Kept crashing wanted to reflash , and installed TWRP on it , that said can't mount partitions and now i can't flash neider the 811 or the 813 roms to it . Just keeps saying error writing to partition . I can attach a screenshot of the Miflash tool if it helps. And above is the Command prompt error.
Pushing just 5 img files didn't worked for me and was stuck on MI logo, but pushing all files was reviving my phone!
Thank you very much for this method!
sir, my Redmi 2 is bricked
when I am trying to flash this the error messages is coming like
cannot load " gpt_both0.bin".
like these and so on. when I am using flash all.bat same messages is coming and then after erasing boot the phone reboots with black screen .
sir please help me
your help will be highly appriciated.
[email protected]
My phone stucks on Mi logo what will do
yeah!!!!!!!!!!!! after trying many other methods like recovery through adb ,command prompt,mi flash tool,mi pc suit...... i downloaded atleast 4-5 roms to just confirm that whether flash tool has some problem or the ROMs..........but if something worked after constantly trying many things in past three days it is this method.......seriously...
FYI this is the way i used it and u should probably use the same way
-> download MI flash tool (google it)
->install(in C
->download any compatible ROM for ur phone
->open :- C:\Program Files\Xiaomi\MiPhone\Google\Android
->paste all the contents of image folder from the ROM into this android folder
->then download this Flash All.bat from here and extract it...
->put your phone in fastboot mode ->connect it via usb
->then double click your Flash all.bat file-> give it some time->once finished ur device will start automatically
->after 10 mins or so disconnect ur phone from pc ... give it 4-5 mins , ur phone will be out of bootloop and u will be awarded with a new MIUI
Yes! It worked for me as well.
Thanks for your steps.
(FYI this is the way i used it and u should probably use the same way
-> download MI flash tool (google it)
->install(in C
->download any compatible ROM for ur phone
->open :- C:\Program Files\Xiaomi\MiPhone\Google\Android
->paste all the contents of image folder from the ROM into this android folder
->then download this Flash All.bat from here and extract it...
->put your phone in fastboot mode ->connect it via usb
->then double click your Flash all.bat file-> give it some time->once finished ur device will start automatically
->after 10 mins or so disconnect ur phone from pc ... give it 4-5 mins , ur phone will be out of bootloop and u will be awarded with a new MIUI )
and it worked good.
My Mi Account was locked and could not connect to internet at all.
I had tried using Flash tools, PC suite - Flash methods and nothing worked. I had spend more time to fix my mobile in all these ways.
But this method is awesome. Only took around 15 minutes to completely flash my mobile.
After flashing the mobile, I am able to connect to internet and I have also created a new Mi-Account and linked my G-Mail account to it.
Am super happy now.
Thanks a lot.
However I would wish to add another details to the above setps:
The Flashall.BAT too needs to be extracted and copied into the same folder where the contents from ROM's Image folder were copied.
awesome bro thankyou very much.it's working absolutely well:good::good:
Tried a similar method and got my redmi2 prime hard bricked. Can someone tell me the test points in the device 2014818?
Thanx This works for me. successfull to flash my redme 2
Simply put Flash All.bat (Attached Bellow) in Minimal ADB and Fastboot directory and double click on it (No need to enter those commands). Your Devices will reboot automatically when flashing done.
congrats
Hit thanks[/QUOTE]
Will this work for Redmi note 3 Snapdragon??
Hello
I am stick in bootloop with my Redmi 3 (after trying Flashify).
Tried the above method with high hopes, as I have been trying everything else also with no luck.
I have downloaded a ROM for my device of course.
It all seems to go well until I launch the Flash_All.bat
Then the DOS commands are executed in 5 to 10 secs, and my devices reboot, but in a bootloop again
I got a breif view at the DOS commands, and it basically, at several lines says somthing, like: "failed to write, device is locked"
see attached sreen shot
does this mean my problem has no solution and I can simply throw away my device?
Thanks
rkmadotra said:
Hi all,
Yesterday i flashed miui LP on my Redmi 2 Prime. In the evening i tried to flash the miui KK with fastboot rom. But ended up with unspecified error . I tried many things but no luck. Then i followed direct method and that worked. Following is the procedure...
Click to expand...
Click to collapse
You solved my problem :good:
Thank you buddy..... This method works
Fastbooting method did not bring back my stock model number that is hm2014818. It changed to 2014817 when i flashed miui 8 64bit rom for redmi 2. Now i am not able to go back to my original model number even by fastboot method. Any help please??
will the flash all.bat support on other mi device's??
stuck at erasing user data
flashing stuck at flashing userdata
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 6T in fastboot mode (Power and volume-);
Connect the OnePlus 6T to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
FLASHER ADVANCED GUIDE
flash-all-partitions-fastboot.bat : this .bat will flash all possible partitions through fastboot (Except persist) , there are some criticals partitions that can't be flashed through fastboot;
flash-only-persist.bat : this .bat will flash only persist partition in fastboot mode (This is good for people that have problems with sensor);
flash-all-partitions-recovery-criticals.bat : this .bat will boot the twrp and will flash criticals partitions, use this carefully;
flash-system-boot-vendor.bat : this .bat is the same of older flash-all.bat and so it will flash only vendor, system and boot;
flash-all-partitions.bat : this .bat will run flash-all-partitions-fastboot.bat , then flash-only-persist.bat and then flash-all-partitions-recovery-criticals.bat .
Now usually the one needed is only the first "flash-all-partitions-fastboot.bat" but if you are badly bricked i recommend to use flash-all-partitions.bat .
DOWNLOAD
All roms on AFH: https://www.androidfilehost.com/?w=files&flid=284914
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 6T
BRANDED PHONE
GUIDE: https://forum.xda-developers.com/on...-t-mobile-oneplus-6t-to-t3865966/post78131430
T-Mobile OnePlus 6T Internationa ROM: https://www.androidfilehost.com/?fid=11410963190603845445
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (you need to extract images.zip before proceed)
Fastboot Partitions:
Code:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash fw_4j1ed_a fw_4j1ed.img
fastboot flash fw_4j1ed_b fw_4j1ed.img
fastboot flash fw_4u1ea_a fw_4u1ea.img
fastboot flash fw_4u1ea_b fw_4u1ea.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
If you need also persist partition, this is the command:
Code:
fastboot flash persist persist.img
Criticals Partitions, for these you need to boot the TWRP:
Code:
fastboot boot TWRP.img
When you are in TWRP you need to run these commands to push and flash all criticals partitions:
Code:
adb push abl.img /sdcard/abl.img
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_a
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_b
adb push cmnlib.img /sdcard/cmnlib.img
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_a
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_b
adb push cmnlib64.img /sdcard/cmnlib64.img
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_a
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_b
adb push devcfg.img /sdcard/devcfg.img
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_a
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_b
adb push hyp.img /sdcard/hyp.img
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_a
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_b
adb push keymaster.img /sdcard/keymaster.img
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_a
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_b
adb push xbl.img /sdcard/xbl.img
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_a
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_b
adb push xbl_config.img /sdcard/xbl_config.img
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_a
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_b
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
Thanks to @SaiBork for first time tested
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
Thanks to @Dark Nightmare for T-Mobile Rom Version
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
If you are unable to use pools or moneybox, you can also make a normal donation, all private donations will be added in the moneybox:
Thanks Mister :good:
Great work, thx
This is great work. Thanks!
If anyone has the T-Mobile firmware or OTA captured, please post it.
Would it be wise to extract the zip to the 6T prior to rooting just in case something goes wrong?
shizat63 said:
Would it be wise to extract the zip to the 6T prior to rooting just in case something goes wrong?
Click to expand...
Click to collapse
This fastboot rom are completely stock rom, not modified
mauronofrio said:
This fastboot rom are completely stock rom, not modified
Click to expand...
Click to collapse
Right.
So before rooting the device, would it be good to copy the images from this zip to a dir on the 6T in case something goes wrong with the rooting process? For example if Magisk or TWRP mess something up, and the 6T is in a bootloop.
Or are the images in the zip only for flashing from your PC to the 6T? So it would be of no use to have the images sitting on the 6T as a backup.
Hello. after flashing with flash-all.bat, my 6T just boots to the bootloader unlocked warning and stays there. I don't know what to do next.
EDIT: Nevermind, after trying again it worked.
shizat63 said:
Right.
So before rooting the device, would it be good to copy the images from this zip to a dir on the 6T in case something goes wrong with the rooting process? For example if Magisk or TWRP mess something up, and the 6T is in a bootloop.
Or are the images in the zip only for flashing from your PC to the 6T? So it would be of no use to have the images sitting on the 6T as a backup.
Click to expand...
Click to collapse
Actually there is not a twrp that support decryption so if you also have the images on the phone you can't flash it in twrp mode. At this moment these roms can be only flashed through fastboot with a pc
Seoyoon said:
Hello. after flashing with flash-all.bat, my 6T just boots to the bootloader unlocked warning and stays there. I don't know what to do next.
EDIT: Nevermind, after trying again it worked.
Click to expand...
Click to collapse
Perfect:good:
thank you thank you thank you OP! Nearly bricked my phone while trying to install root (something got messed up with TWRP) and I couldn't even get out of bootloader into recovery. I just got my phone a few hours ago, that would have been sad
nhshah7 said:
thank you thank you thank you OP! Nearly bricked my phone while trying to install root (something got messed up with TWRP) and I couldn't even get out of bootloader into recovery. I just got my phone a few hours ago, that would have been sad
Click to expand...
Click to collapse
Perfect:good:
If you want to support this and others my projects please consider making a donation, thanks.
After using flash-all.bat I'm getting the "Your device is corrupt" red error message on boot. I can skip by pressing power twice and phone boots normally.
I see people with 6 had to use MSM download tool to get rid of the error.
Is there any solution for 6T?
nhshah7 said:
thank you thank you thank you OP! Nearly bricked my phone while trying to install root (something got messed up with TWRP) and I couldn't even get out of bootloader into recovery. I just got my phone a few hours ago, that would have been sad
Click to expand...
Click to collapse
Just for the sake of your sanity in the future, if you can get to bootloader and device files are available, you can always get it up and running. I learned that very quickly way back in the day
iaTa said:
After using flash-all.bat I'm getting the "Your device is corrupt" red error message on boot. I can skip by pressing power twice and phone boots normally.
I see people with 6 had to use MSM download tool to get rid of the error.
Is there any solution for 6T?
Click to expand...
Click to collapse
Only msm tool i think
Well same situation here got boot loop trying to root then after install using flashall.bat now I can't get a VOLTE and now I complete lost signal but when I swap my sim card to sim slot 2 everything work...kinda weir but does anyone know how to fix it?
_BГ@ckθut said:
Well same situation here got boot loop trying to root then after install using flashall.bat now I can't get a VOLTE and now I complete lost signal but when I swap my sim card to sim slot 2 everything work...kinda weir but does anyone know how to fix it?
Click to expand...
Click to collapse
Did you have a branded version?
mauronofrio said:
Did you have a branded version?
Click to expand...
Click to collapse
Oh I has unlock one from on plus website and use it on Verizon...is that what u mean...sorry I'm new to OP device
Edit: I try to do fastboot flash modem A and B also factory reset but seem not work...
_BГ@ckθut said:
Oh I has unlock one from on plus website and use it on Verizon...is that what u mean...sorry I'm new to OP device
Click to expand...
Click to collapse
Branded version are different, they have a particoular partitions for volte, i think the only.method to solve your problem is to find another person with the same branded device and make a partitions backup that you can restore
mauronofrio said:
Branded version are different, they have a particoular partitions for volte, i think the only.method to solve your problem is to find another person with the same branded device and make a partitions backup that you can restore
Click to expand...
Click to collapse
So how do I make that? Do I need provide any information or anything?
He guys,
as you've read I bricked my phone and I don't know how or where I did the mistake?
Status before brick:
-) FW: EMUI 8.xxx (not exactly sure which one it was)
-) TWRP: 3.2.3.0
-) Rooted
-) BL: unlocked
-) PHONE Unlock
-) FRP Unlock
What I wanted to do:
-) FW Update to: EMUI 9.0 via FirmwareFinder
What I've done:
-) Did a Titanium Backup
-) Installed Firmware Finder
-) Downloaded the Firmware CLT-L29C432E5R1P9B195 (9.0.0.195) (BUT there were ONLY 2 files)
-) 1. file was "update.zip"
-) 2. file was "update_full_CLT-L29_hw_eu.zip"
-) Renamed the files to
-) 1. kept file name "update.zip"
-) 2. file renamed "update_full_CLT-L29_hw_eu.zip" --> update_all_hw.zip
-) Put the 2 files + hurupdater_04.zip + recovery.img (TWRP 3.2.1.0.img) to a folder in Root on my device
-) Reboot to recovery -> TWRP
-) TWRP -> Install -> hurupdater_04.zip
ERRORS:
-) first I saw a message --> "CLT-L09 "Firmware installing --> how can that happened, if I downloaded the CLT-L29 version?
-) Then it aborted the installing process
Current situation:
-) TWRP is installed again --> TWRP 3.2.1.-0 by Pretorian
-) PHONE Unlock
-) FRP Unlock
-) no OS
!! Cannot access my files either via TWRP or Windows explorer --> all files are encrypted and have totally weird names
So please, please help me installing an OS again!
!! And is there a chance to get access to my pictures back???
I appreciate every helpfull advise.
Thanks in advance!!!
He guys,
nobody has an idea to solve/help me with my issues/situation?
I searched the forum and also other forums and pages to find a solution to "my" problem, but without any helpful results.
I am afraid of doing an eRecovery restore because of losing all my data.
I have currently: TWRP installed -> Files/folders with weird names (shown in TWRP & Phone connected to PC "Explorer")
What can I do to save, restore, copy my pictures and files from phone to PC?
Please give me some hints.
This way brought me back
Try downloading the firmware here: FIRMWARE
Then follow these instructions: HEREhttps://forum.xda-developers.com/huawei-p20-pro/development/huawei-p20-pro-charlotte-l29c432b131-8-t3809964
Got me out of a pinch a few times.
Vedrick said:
Try downloading the firmware here: FIRMWARE
Then follow these instructions: HEREhttps://forum.xda-developers.com/huawei-p20-pro/development/huawei-p20-pro-charlotte-l29c432b131-8-t3809964
Got me out of a pinch a few times.
Click to expand...
Click to collapse
Thanks for the help and the links.
BUT before I'll start doing this, there is just one issue left: the encrypted "storage / files" (pics etc.) in TWRP.
BEFORE I want to say, that I've removed all the security barriers like fingerprint, pattern and faceID !!!!
I tried using this https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
with different kinds of TWRP versions:
TWRP 3.2.1-0.img
twrp_clt_0.1.img frome here
https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
twrp-3.2.1-0-charlotte-mod.img frome here
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
twrp-3.2.3-4-charlotte.img
But nothing works, my files shown in TWRP -> storage are still encrypted and still shown with weird gibberish names?
Do you know how to solve this, or where I can get the right TWRP version?
I'm totally at the end of ideas and not finding the right way to get access to my pictures and stuff again.
Da_Hausa said:
Thanks for the help and the links.
BUT before I'll start doing this, there is just one issue left: the encrypted "storage / files" (pics etc.) in TWRP.
BEFORE I want to say, that I've removed all the security barriers like fingerprint, pattern and faceID !!!!
I tried using this https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
with different kinds of TWRP versions:
TWRP 3.2.1-0.img
twrp_clt_0.1.img frome here
https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
twrp-3.2.1-0-charlotte-mod.img frome here
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
twrp-3.2.3-4-charlotte.img
But nothing works, my files shown in TWRP -> storage are still encrypted and still shown with weird gibberish names?
Do you know how to solve this, or where I can get the right TWRP version?
I'm totally at the end of ideas and not finding the right way to get access to my pictures and stuff again.
Click to expand...
Click to collapse
I honestly don't think any twrp will work, another reason i'll never buy a huawei again. You could try extracting the image files from the update.app that you get from the update.zip file. then manually flash:
You can extract the image files using EMUI Extractor Application.
fastboot flash cust cust.img
fastboot flash system system.img
I believe the pictures are located on the userdata partition. be sure to flash the right android version as it may depend on what framework you have and how far you got when it was updating. You may want to verify the location of those pictures first.
SO I replicated your soft brick, after I backup up my photos. I ccouldn't save them. I'm up and running though. Turns out I had to first manually flash those image files located in update.app. Then I had to do this
Modified\Updated (Bricked device fix)
1) Try downloading the firmware here: FIRMWARE
2) Extract the update.app file from the update.zip, then use EMUI extractor to extract all the image files. You'll then need to manually flash a few of them: (You can move all these images into the main folder of the Reflash tools located in step 3, then run CMD-HERE)
Commands: (Some might error, i forget which but its alright)
fastboot flash cust cust.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
fastboot flash recovery_ramdisk recovery_ramdis.img (Very Important)
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash vector vector.img
fastboot flash system system.img
fastboot reboot, unplug the USB-C cable and hold the volume up button. this will put you into recovery mode.
Then you'll need to format data using with the EMUI recovery and if given the option format cache.
Reboot back into bootloader\Download mode.
3) Then follow these instructions: HEREhttps://forum.xda-developers.com/huawei-p20-pro/development/huawei-p20-pro-charlotte-l29c432b131-8-t3809964
Got me out of a pinch a few times.
Unfortunately I seem to have the same issue. I followed @Vedrick's tutorial.
However after fastboot reboot I'm stuck on 'Your device is booting now...'
Any ideas?
I worry that perhaps the 'boot image' on my p20 is messed up. However in the .APP file I can't find the boot image to restore. I do however see 2 SYSTEM images.
nvm! Got it! Had to fastboot erase userdata.
Follow these easy steps
Makes sure you have the GSI image on your sdcard before starting this, if your coming from lineage OS backup your data!
1.Unlock Bootloader
2. Boot into bootloader, check your slot if on B switch to A and vice versa.(fastboot set_active a/b) or you can stay in your current active slot up to you.
3.Download twrp and flash it (fastboot flash boot boot.img)
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
5.Boot into twrp,Format data or in bootloader run this command "fastboot format userdata" to get rid if encryption else gsi wont boot then, go to "install" navigate to your sdcard where you place the gsi , look for 'select image" then flash your gsi.
6.To flash gapps(skip if the gsi includes them) if your using a aosp gsi go to twrp then go into /wipe/advanced wipe/ select system on the options then "repair or change file system" then press on "resize file system" this will resize your system partiton back to 3.X gigs and allow you to flash gapps.
7.Then reboot to system
8. Your gsi "should" boot
Downloads:
http://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
https://forum.xda-developers.com/pr...bled-device-development/gsi-havoc-os-t3930030 Havoc OS the gsi ive been using for some weeks.
Fixes and WorkArounds
Volte Fix for GSi
Install the volt-ims.apk as you would normally install an apk, download here http://www.mediafire.com/file/l0x88jx5zxyknhh/volte-ims.apk/file
For root( magisk) and twrp flash http://www.mediafire.com/file/de8tccz7gr93831/twrp-magisked-los-boot.img/file
To pass SafetyNet flash this http://www.mediafire.com/file/867xncq865vvtct/Universal-safetynet-fix-v3.zip/file
Also I created a template for what works on phhusson Treble experiments wiki:
https://github.com/phhusson/treble_experimentations/wiki/ZTE-Axon-10-Pro
CREDITS:
Unjustifieddev for his work on lineage, and the boot.img im using.
All the gsi creators
Screenshots of Havoc OS gsi running on my zte axon 10:
Android Q Gsi works too
you can also use the zte android 9 stock kernel and vendor
That all is great news.....bravooo
Any issues with the havoc gsi?
blcistheking said:
Any issues with the havoc gsi?
Click to expand...
Click to collapse
Only the Fingerprint is broken
noobstyle1337 said:
Only the Fingerprint is broken
Click to expand...
Click to collapse
its only broken if you have a a2020g, works fine if you have a a2020u, current los kernel is missing a2020g fingerprint firmware from what i can gather.
Bliss 12.7 Android 10 gsi on a2020u.
rafyvitto said:
Follow these easy steps
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
==
Click to expand...
Click to collapse
whenever i try this i just get
"fastboot: unknown option -- disable-verity"
Mr. DR. Professor Electro said:
whenever i try this i just get
"fastboot: unknown option -- disable-verity"
Click to expand...
Click to collapse
Skip that step not needed, just flahs the disable encryption zip file in twrp to disable encryption.
i have bootloader unlocked ive wiped everything even flashed disable encryption but whenever i try to install the zip for lineage 17 i get an "error installing zip file' am i doing something wrong?
honestly i cant even flash any rom zip i have i just get error 1s , i even wipe data/format before flashing am i doing something wrong am i supposed to be on a or b while doing this or what
Futility's Forgotten Soldier said:
i have bootloader unlocked ive wiped everything even flashed disable encryption but whenever i try to install the zip for lineage 17 i get an "error installing zip file' am i doing something wrong?
Click to expand...
Click to collapse
Lineage 17 is very broken right now, i would suggest flashing bliss 2.7 gsi, check my telegram channel for more info.
cant escape bootloop hell and error 255
rafyvitto said:
Follow these easy steps
Makes sure you have the GSI image on your sdcard before starting this, if your coming from lineage OS backup your data!
1.Unlock Bootloader
2. Boot into bootloader, check your slot if on B switch to A and vice versa.(fastboot set_active a/b) or you can stay in your current active slot up to you.
3.Download twrp and flash it (fastboot flash boot boot.img)
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
5.Boot into twrp,Format data or in bootloader run this command "fastboot format userdata" to get rid if encryption else gsi wont boot then, go to "install" navigate to your sdcard where you place the gsi , look for 'select image" then flash your gsi.
6.To flash gapps(skip if the gsi includes them) if your using a aosp gsi go to twrp then go into /wipe/advanced wipe/ select system on the options then "repair or change file system" then press on "resize file system" this will resize your system partiton back to 3.X gigs and allow you to flash gapps.
7.Then reboot to system
8. Your gsi "should" boot
Downloads:
http://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
https://forum.xda-developers.com/pr...bled-device-development/gsi-havoc-os-t3930030 Havoc OS the gsi ive been using for some weeks.
Fixes and WorkArounds
Volte Fix for GSi
Install the volt-ims.apk as you would normally install an apk, download here http://www.mediafire.com/file/l0x88jx5zxyknhh/volte-ims.apk/file
For root( magisk) and twrp flash http://www.mediafire.com/file/de8tccz7gr93831/twrp-magisked-los-boot.img/file
To pass SafetyNet flash this http://www.mediafire.com/file/867xncq865vvtct/Universal-safetynet-fix-v3.zip/file
Also I created a template for what works on phhusson Treble experiments wiki:
https://github.com/phhusson/treble_experimentations/wiki/ZTE-Axon-10-Pro
CREDITS:
Unjustifieddev for his work on lineage, and the boot.img im using.
All the gsi creators
Click to expand...
Click to collapse
rafyvitto said:
Lineage 17 is very broken right now, i would suggest flashing bliss 2.7 gsi, check my telegram channel for more info.
Click to expand...
Click to collapse
having trouble
Steps I followed:
(bootloader been unlocked but double checked to be sure)
Started from LineageOS 16 clean flashed based
booted rom made sure Debug was enable in settings did nothing else
booted to bootloader
>fastboot set_active a
>fastboot boot "D:\Android\Flash\Recovery.img"
In Recovery:
Installed Twrp zip
install zip DisableForcedEncryption.zip
-reboot bootloader
>fastboot flash vbmeta "C:\Users\chris\Downloads\ZTE_Flash\vbmeta.img"
>fastboot format userdata
boot to recovery:
Installed GSI Image of Havoc OS to System image
Flashing system image......
simg2ing '/sdcard1/Havoc-OS-v2.9-20190914-phhgsi_arm64_ab-offical.img' 'dev/block/bootdevice/by-name/system_a'process
ended with ERROR: 255
got creative because nothing i was doing was fixing the problem so i went into fast boot and
>fastboot flash system "location/of/Havoc.img"
now no longer can acess the recovery not even but fastboot boot img command and back in a bootloop hell
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot "D:\Android\Flash\Recovery.img"
downloading 'boot.img'...
OKAY [ 0.605s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.640s
also i have no way to return to the original 10 pro rom whenever i flash it via the EDL tool with one of the US edl
Zips you provided i have boot loop but it gives me enough so i can have bootloader mode accessible but i have to rerun
the bootloader unlock. but flashing Lineage 16 seems to be the only thing to make my phone functional without giving it boot loop hell
ill try do it with bliss later but if there's anywhere i went wrong or how to solve the 255 let me know i really want to try out one of those GSIs
but im running on the US rom and using the TWRP for my pro from the fourms so i just really confused here idk if i could possibly give you anymore details
ok update i got it working
1. the 255 i fixed by
"
Reboot into recovery, TWRP
Go to the terminal in "Advanced"
Type cd /system to change the path to the system folder
Type rm addon.d to remove the addon file
Type exit to quit from the terminal
Now back to TWRP home, try backup/restore again, it should works.
Further adjustment: do check the use rm -f to format disk settings of TWRP, to make sure TWRP won't mess up the filesystem."
secondly what was ruining me was a big dumb mistake on my part you HAVE to do " --disable-verity --disable-verification flash vbmeta vbmeta.img" with the latest ADB tool kit I was using minimal adb and fastboot then got it to work
In step 5,i can not boot into TWRP and phone displays ZTE crashdump mode.
Please help.
Thanks.
Edit: I fixed it and can flashed this rom but it has some bugs.
Reposting here (from the Magisk forum) on the advice of a Senior Moderator.
I have a Pixel 5 and two days ago now I updated from redfin-2110-rq3a.211001.001-factory-23f4cec2 to redfin-2111-sp1a.211105.004-factory-749e8f9f (yes the Aus version), i.e. from the October version to the November version.
All went well until I tried to root the device using Magisk - something I've done *many* times. The trouble is that after I flashed the patched boot.img, the device would not boot - it started to for a few seconds and then went back into fastboot mode.
I've tried a few times but always the same result.
And it seems that you cannot rollback to the October release - the flash-all.sh completes OK but the subsequent boot hangs.
BTW (1): I'm still using the canary channel, is this still necessary?
BTW (2): I also posted in the github Magisk issues page and that issue was promptly closed with the comment "format data". Really?!
Help.
Curiouser and curiouser: this works
adb reboot bootloader
fastboot boot redfin-2111_boot_magisk_patched.img
gone_bush said:
Reposting here (from the Magisk forum) on the advice of a Senior Moderator.
I have a Pixel 5 and two days ago now I updated from redfin-2110-rq3a.211001.001-factory-23f4cec2 to redfin-2111-sp1a.211105.004-factory-749e8f9f (yes the Aus version), i.e. from the October version to the November version.
All went well until I tried to root the device using Magisk - something I've done *many* times. The trouble is that after I flashed the patched boot.img, the device would not boot - it started to for a few seconds and then went back into fastboot mode.
I've tried a few times but always the same result.
And it seems that you cannot rollback to the October release - the flash-all.sh completes OK but the subsequent boot hangs.
BTW (1): I'm still using the canary channel, is this still necessary?
BTW (2): I also posted in the github Magisk issues page and that issue was promptly closed with the comment "format data". Really?!
Help.
Click to expand...
Click to collapse
Sorry, but you are going to have to wipe your phone here. On the next updates you won't have to following these instructions.
Get the vbmeta.img from the factory image (the same place you got the boot.img) and put it into your fastboot folder.
In bootloader/fastboot enter:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Then enter:
fastboot -w (<---this wipes your phone)
Then flash the patched boot image as you normally would and reboot.
In the future for updates, download both the ota.zip and the factory image. Pull the boot.img from the factory image and patch it. Pull the vbmeta.img and put it into your fastboot folder with the patched boot.img. Sideload the OTA and when the flash is done, boot to bootloader using the volume/power buttons on your phone from recovery (you'll be there to sideload the ota.zip) IF YOU BOOT TO /SYSTEM YOU'LL HAVE TO WIPE AGAIN!
Flash the vbmeta.img with fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img, then flash the patched boot.img and reboot. You won't have to wipe again as long as you don't boot to /system and don't forget to flash the vbmeta.img with disabling verity and verification.
xunholyx said:
Sorry, but you are going to have to wipe your phone here. On the next updates you won't have to following these instructions.
Get the vbmeta.img from the factory image (the same place you got the boot.img) and put it into your fastboot folder.
In bootloader/fastboot enter:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Then enter:
fastboot -w (<---this wipes your phone)
Then flash the patched boot image as you normally would and reboot.
In the future for updates, download both the ota.zip and the factory image. Pull the boot.img from the factory image and patch it. Pull the vbmeta.img and put it into your fastboot folder with the patched boot.img. Sideload the OTA and when the flash is done, boot to bootloader using the volume/power buttons on your phone from recovery (you'll be there to sideload the ota.zip) IF YOU BOOT TO /SYSTEM YOU'LL HAVE TO WIPE AGAIN!
Flash the vbmeta.img with fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img, then flash the patched boot.img and reboot. You won't have to wipe again as long as you don't boot to /system and don't forget to flash the vbmeta.img with disabling verity and verification.
Click to expand...
Click to collapse
Thank you for your reply. Some questions:
1) What's changed that required a wipe? (Let's face it, it's a MAJOR PITA! Thankfully, I do use TitaniumBackup )
2) You state "download both the ota.zip and the factory image" - what's the difference?
3) Re "Pull the vbmeta.img" - in the current instance, is that from the November file (SP1A.211105.004), if not, from where?
4) Do I have this right for future updates?
* Unpack the downloaded file and put the boot.img and vbmeta.img files in a safe place
* Sideload the update by
adb reboot recovery
Apply update from ADB
adb sideload <ota-update.zip>
* Use volume buttons to boot into bootloader (booting into system will mean I'll have to do another wipe!)
* fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
* flash patched boot.img
* boot
5) Re using Magisk to patch the boot.img: can, say, the November boot.img be patched whilst the phone is running the October update?
Yeah, I know, answering my questions is all you've got to do with your life
1: verified boot is needed in Android 12. Patching the boot.img breaks the signature from Google
2: after flashing the factory image in fastboot you're promoted to press any key to continue, which boots the phone to system iirc (I could be mistaken ~ it's been over a year since I flashed a factory image). You can boot to bootloader from recovery after you sideload the OTA.
3: yes. From the update you are applying.
4: I guess.... Place the vbmeta.img in your fastboot folder the same as the patched boot.img (at least that's where I always put the patched boot.img). Put the pulled boot.img wherever you like to transfer it to your phone from to patch. The rest after that part is correct.
5: yes
EDIT: (Sorry I forgot to use the reply button)
xunholyx said:
1: verified boot is needed in Android 12. Patching the boot.img breaks the signature from Google
2: after flashing the factory image in fastboot you're promoted to press any key to continue, which boots the phone to system iirc (I could be mistaken ~ it's been over a year since I flashed a factory image). You can boot to bootloader from recovery after you sideload the OTA.
3: yes. From the update you are applying.
4: I guess.... Place the vbmeta.img in your fastboot folder the same as the patched boot.img (at least that's where I always put the patched boot.img). Put the pulled boot.img wherever you like to transfer it to your phone from to patch. The rest after that part is correct.
5: yes
EDIT: (Sorry I forgot to use the reply button)
Click to expand...
Click to collapse
Thank you for yor replies and time - much appreciated!