Database Info

Huawei Honor 6 H60-L12 bricked

Hello all
A friend of mine has a Huawei Honor 6 H60-L12.
He tried to do a firmware update and he bricked the phone.
I bought it and I am desperately trying to recover it.
Here is what I know about the phone:
It had Android 5.1.1
It had Emui 3.1 and was trying to upgrade to 4.0
(Probably was rooted)
It is H60-L12
No matter what I do, I cannot enter recovery mode with the 3 button trick.
I can anytime enter Fastboot mode.
I tried to unbrick it with HONOR Multi-Tool, everything seems to work alright, but flashing boot.img fails. After unbrick I should enter recovery mode but it does not work, phone remains stuck with the Honor logo.
Computer connects to phone in Fastboot mode, Multi-tool and fastboot command works, I also have the drivers installed.
I know that after bricking the rooted phone, I should restore it and remove root before upgrade but I cannot get there.
Please advise
Best regards,
Janos

janos666 said:
Hello all
A friend of mine has a Huawei Honor 6 H60-L12.
He tried to do a firmware update and he bricked the phone.
I bought it and I am desperately trying to recover it.
Here is what I know about the phone:
It had Android 5.1.1
It had Emui 3.1 and was trying to upgrade to 4.0
(Probably was rooted)
It is H60-L12
No matter what I do, I cannot enter recovery mode with the 3 button trick.
I can anytime enter Fastboot mode.
I tried to unbrick it with HONOR Multi-Tool, everything seems to work alright, but flashing boot.img fails. After unbrick I should enter recovery mode but it does not work, phone remains stuck with the Honor logo.
Computer connects to phone in Fastboot mode, Multi-tool and fastboot command works, I also have the drivers installed.
I know that after bricking the rooted phone, I should restore it and remove root before upgrade but I cannot get there.
Please advise
Best regards,
Janos
Click to expand...
Click to collapse
Instead of using the honor multi tool, why don't you use the Android SDK platform tools and connect to your phone through adb. You can solve any problem using that. You have to do everything manually but it works and never disappoints as long as you can enter fastboot mode.
Download android SDK and install it. Run the program and only choose platform tools to download. You don't need anything else
Download the latest firmware for your phone and unzip it to get dload folder which will have an update.app in it.
Download Huawei update extractor and open update.app in it.
Extract recovery, boot, Cust and system images from update.app and save them to the platform tools folder.
Flash them using adb and then do a forced update.
Will work wonders. If you need any help or need more info, please let me know.

Hello muradulislam
First of all, thank you for trying to help me.
I tried something similar to your suggestion but I still have problems.
Let me explain.
My phone is H60-L12
Latest stable firmware which I found is this one:
H60-L02-L12_EMUI3.1_Android5.1_C00B535.zip
I extracted the boot, cust, recovery and system images with Huawei update extractor.
My device is detected in fastboot mode, fastboot devices gives me this result:
c:\adb>fastboot devices
F6CDU15117010953 fastboot
When I try to flash the boot.img, it gives me this error:
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (10274 KB)...
OKAY [ 1.092s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 1.135s
I tried to continue with the rest but I think this is useless.
Please tell me what to do.
Best regards,
Janos

janos666 said:
Hello muradulislam
First of all, thank you for trying to help me.
I tried something similar to your suggestion but I still have problems.
Let me explain.
My phone is H60-L12
Latest stable firmware which I found is this one:
H60-L02-L12_EMUI3.1_Android5.1_C00B535.zip
I extracted the boot, cust, recovery and system images with Huawei update extractor.
My device is detected in fastboot mode, fastboot devices gives me this result:
c:\adb>fastboot devices
F6CDU15117010953 fastboot
When I try to flash the boot.img, it gives me this error:
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (10274 KB)...
OKAY [ 1.092s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 1.135s
I tried to continue with the rest but I think this is useless.
Please tell me what to do.
Best regards,
Janos
Click to expand...
Click to collapse
My expertise are quite limited but may be, just may be (wishful thinking), you can to flash the twrp recovery specific for your phone. Boot into that and flash a custom ROM from there.
It may not work as I guess, boot.img is needed before entering recovery but give it a try. It never hurts.

Come on, guys!
There must be somebody who can help me.
Guillermo, panamera2011 and muradulislam tried to help me and I want to thank you for their patience.
Problem is, that I am still missing something.
There are 2 weeks now, each day after work I try to revive this phone.
These are the facts I know:
Tried the programs on 4 different machines, Windows 7, Windows 8.1, Windows 10, 32 bit and 64 bit versions.
Tried different sets of drivers (the one from Android SDK, the Universal ADB drivers, the ones installed by multi-tool)
Result is always the same.
I can flash anytime, any version of cust.img recovery.img and system.img but I can flash only the boot.img which is resulting from an EMUI2.3 or EMUI3.0 package.
If I try to flash boot.img from EMUI3.1 or EMUI4.0, I get the following error:
sending 'boot' (10274 KB)...
OKAY [ 1.103s]
writing 'boot'...
FAILED (remote: flash write failure)
Click to expand...
Click to collapse
I tried flashing different stock or CWM or TWRP recoveries. They all are written correctly, but I cannot enter any recovery mode.
Someone advised me to try to flash fastboot.img. It is not working, gives error.
I have already many hours and maybe hundreds of firmware writes, I downloaded around 100 GB of firmwares....
There must be an idea how to save this phone.
I am open to any decent advice.
Best regards,
Janos

janos666 said:
Come on, guys!
There must be somebody who can help me.
Guillermo, panamera2011 and muradulislam tried to help me and I want to thank you for their patience.
Problem is, that I am still missing something.
There are 2 weeks now, each day after work I try to revive this phone.
These are the facts I know:
Tried the programs on 4 different machines, Windows 7, Windows 8.1, Windows 10, 32 bit and 64 bit versions.
Tried different sets of drivers (the one from Android SDK, the Universal ADB drivers, the ones installed by multi-tool)
Result is always the same.
I can flash anytime, any version of cust.img recovery.img and system.img but I can flash only the boot.img which is resulting from an EMUI2.3 or EMUI3.0 package.
If I try to flash boot.img from EMUI3.1 or EMUI4.0, I get the following error:
sending 'boot' (10274 KB)...
OKAY [ 1.103s]
writing 'boot'...
FAILED (remote: flash write failure)
I tried flashing different stock or CWM or TWRP recoveries. They all are written correctly, but I cannot enter any recovery mode.
Someone advised me to try to flash fastboot.img. It is not working, gives error.
I have already many hours and maybe hundreds of firmware writes, I downloaded around 100 GB of firmwares....
There must be an idea how to save this phone.
I am open to any decent advice.
Best regards,
Janos
Click to expand...
Click to collapse
@DigiGoon
You can flash boot.img from emui 2.3 or 3.0? If its written correctly then may be you can try to boot into that emui version by flashing Cust, system and recovery from the same firmware?
Your last hope is Huawei customer service.

Yes, I can flash cust, recovery and system from the same EMUI2.3 or 3.0 package, but I am still unable to boot recovery.
Unfortunately, Huawei customer service will not help me because phone is H60-L12 (Chinese version) and they don't provide support only for L04

janos666 said:
Yes, I can flash cust, recovery and system from the same EMUI2.3 or 3.0 package, but I am still unable to boot recovery.
Unfortunately, Huawei customer service will not help me because phone is H60-L12 (Chinese version) and they don't provide support only for L04
Click to expand...
Click to collapse
Well, I have mentioned DigiGoon in the previous reply. May be he can help a bit.

@janos666
You can always put your desired boot.img in a flashable zip, and flash it via TWRP recovery.

Hi DigiGoon!
No, I cannot, because I was never able to access any kind of recovery

janos666 said:
Hi DigiGoon!
No, I cannot, because I was never able to access any kind of recovery
Click to expand...
Click to collapse
You can't mix LP and MM ROMs and IMG files. If you want to downgrade, for example, from MM to LP you must use B800 transitional package.
So you must use IMG files from last installed working ROM.

muradulislam said:
@DigiGoon
You can flash boot.img from emui 2.3 or 3.0? If its written correctly then may be you can try to boot into that emui version by flashing Cust, system and recovery from the same firmware?
Your last hope is Huawei customer service.
Click to expand...
Click to collapse
zinko_pt said:
You can't mix LP and MM ROMs and IMG files. If you want to downgrade, for example, from MM to LP you must use B800 transitional package.
So you must use IMG files from last installed working ROM.
Click to expand...
Click to collapse
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.

janos666 said:
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.
Click to expand...
Click to collapse
Sure. I would go from there as I sometimes mixed boot.img from LP or MM and always got bootloop. I would stick to IMG files from last installed ROM.

janos666 said:
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.
Click to expand...
Click to collapse
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?

DigiGoon said:
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?
Click to expand...
Click to collapse
Hi DigiGoon !
Sorry, which one is the flash transition package?
Which parts to flash from it?
Which is notification LED? I can see only one red LED blinking sometimes, but only when battery is low.

DigiGoon said:
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?
Click to expand...
Click to collapse
Isn't there an option to flash all img files from fastboot?
P.S. I just got new info from the guy who flashed it first time. He says he tried to write version:
H60-L02-L12_emui3.1_android5.1_c00B535

Is there such thing as "not correctly unlocked" or "partially unlocked" bootloader?
When i try to write some parts of the firmware, i get the following error:
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
Normally this would mean that the bootloader is NOT unlocked, but anyway i test it, it says unlocked.
If i type fastboot oem get-bootinfo, i get the following result:
c:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.003s]
finished. total time: 0.005s
Click to expand...
Click to collapse
Also the fastboot screen displays in red "PHONE UNLOCKED"
I can write some parts of the firmware, but not the fastboot.img, and boot.img only from EMUI2.3 or EMUI3.0
Please help me

janos666 said:
Is there such thing as "not correctly unlocked" or "partially unlocked" bootloader?
When i try to write some parts of the firmware, i get the following error:
FAILED (remote: Command not allowed)
Normally this would mean that the bootloader is NOT unlocked, but anyway i test it, it says unlocked.
If i type fastboot oem get-bootinfo, i get the following result:
c:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.003s]
finished. total time: 0.005s
Also the fastboot screen displays in red "PHONE UNLOCKED"
I can write some parts of the firmware, but not the fastboot.img, and boot.img only from EMUI2.3 or EMUI3.0
Please help me
Click to expand...
Click to collapse
Some threads mention of locking and unlocking your device again. Give that a try. May help...

muradulislam said:
Some threads mention of locking and unlocking your device again. Give that a try. May help...
Click to expand...
Click to collapse
I don't have the unlock code that's why I cannot try to relock it... And in this state I cannot get the necessary info to obtain the unlock code.
Anyway, when I tried to unlock with a bogus unlock code (1234567812345678), it gave me an error something like this:
Command failed, bootloader already unlocked.

janos666 said:
I don't have the unlock code that's why I cannot try to relock it... And in this state I cannot get the necessary info to obtain the unlock code.
Anyway, when I tried to unlock with a bogus unlock code (1234567812345678), it gave me an error something like this:
Command failed, bootloader already unlocked.
Click to expand...
Click to collapse
The info you are missing is device id, another user got his device id using Huawei hacker toolkit v 1.4, his model was h60-L02. May be you can give it a try.
You have to lock it before trying to unlock again.
Fastboot OEM lock xxxxxxxxxxxxxxxx...

Root: Stuck at "Your device is booting now"

Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!

if you have the boot backup then restore it.

venugopalu007 said:
if you have the boot backup then restore it.
Click to expand...
Click to collapse
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.

if you cannot find the boot.img
just do a rollback bro
here is the link
first dload this
http://download-c.huawei.com/download/downloadCenter?downloadId=94070&version=376169&siteCode=de-h
and this now
if your device is BLN-L21C432B151 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v84712/f1/full/update.zip
or BLN-L21C185B131 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v75593/f1/full/update.zip

I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img

Stinks said:
I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img
Click to expand...
Click to collapse
The guide from "cyberkey.in/how-to-root-honor-6x-100-working/" is simply wrong when it comes to flashing the twrp recovery. If you really followed this guide completely then you flashed the recovery to the boot partition.
Use "fastboot flash recovery twrp.img" to flash the recovery.
You will still have to flash the boot image to your boot partition then (fastboot flash boot boot.img).

Stinks said:
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.
Click to expand...
Click to collapse
Use fastboot flash recovery twrpname.img to flash the recovery

Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.

V
Stinks said:
Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.
Click to expand...
Click to collapse
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.

venugopalu007 said:
V
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.
Click to expand...
Click to collapse
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?

Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
Bro y this ,just do a rollback .

Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
I recommend you to download firmware files only from the official honor website or by using the huawei firmware finder(https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146)
In this case try to use huawei firmware finder to get the right stock version for your phone. Download these two files: e.g. update.zip & update_full_BLN-L21_hw_eu.zip.
Export the following image files: recovery, system, boot and cust.
The try to flash them:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
If flashing a partition via fastboot fails then it is usually because it's the wrong image or just not made for your phone.

Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.

Stinks said:
Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.
Click to expand...
Click to collapse
Glad you revived your phone

question
​
Stinks said:
Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!
Click to expand...
Click to collapse
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.

[email protected] said:
question
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.
Click to expand...
Click to collapse
did you solve your issue.....I have same problem now

nokiasatyam said:
did you solve your issue.....I have same problem now
Click to expand...
Click to collapse
Hello, could you be more specific about your problem? I'll be able to help you.
Brief Explanation:
From the screen on which you're stuck, press and hold power button for about 10 seconds to forcibly restart your device. when you see the same screen again, immediately press and hold volume up button(for about 3 seconds) to boot to eRecovery.
> Choose shut down option on eRecovery. press and hold vol down button and insert the charging cable to boot to fastboot.
> Press and hold power and volume up button to boot to recovery. (You could do this even from fastboot screen and the screen you're stuck at).

Huawei Mate 9 command not allowed but the bootloader is unlock

Hey guys i got a new problem with my phone. I did a factory reset and later i unlocked the bootlader again but when i tried to do something with adb said ''Command not allowed'' later when i tried to install twrp said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 471859200 bytes
sending 'recovery' (8728 KB)...
OKAY [ 0.252s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.266s

Are you on Oreo?
Edit: seeing your thread below this one you are.
Oreo uses RECOVERY_RAMDISK instead of RECOVERY.
So you'd flash with fastboot flash recovery_ramdisk recovery.img
Make sure you're flashing a recovery for Oreo

ante0 said:
Are you on Oreo?
Edit: seeing your thread below this one you are.
Oreo uses RECOVERY_RAMDISK instead of RECOVERY.
So you'd flash with fastboot flash recovery_ramdisk recovery.img
Make sure you're flashing a recovery for Oreo
Click to expand...
Click to collapse
I'm loving you so much right now

ante0 said:
Are you on Oreo?
Edit: seeing your thread below this one you are.
Oreo uses RECOVERY_RAMDISK instead of RECOVERY.
So you'd flash with fastboot flash recovery_ramdisk recovery.img
Make sure you're flashing a recovery for Oreo
Click to expand...
Click to collapse
I flashed with it but when i opened the recovery mode he opened erecovery from huawei and i flashed twrp for oreo

CommunalH said:
I flashed with it but when i opened the recovery mode he opened erecovery from huawei and i flashed twrp for oreo
Click to expand...
Click to collapse
Could you send me the recovery you're flashing?

ante0 said:
Could you send me the recovery you're flashing?
Click to expand...
Click to collapse
When i tried to flash to oreo i downloaded a file named Hwota8, in there were the twrp named TWRP8_3.0.3

CommunalH said:
When i tried to flash to oreo i downloaded a file named Hwota8, in there were the twrp named TWRP8_3.0.3
Click to expand...
Click to collapse
Good, that's the correct one
Can you boot to system?

ante0 said:
Good, that's the correct one
Can you boot to system?
Click to expand...
Click to collapse
I don't hace OS right now, options neither

CommunalH said:
I don't hace OS right now, options neither
Click to expand...
Click to collapse
What is your model of mate 9? (LxxCxxxBxxx)
I thought you should try to flash ramdisk and kernel as well, in case KERNEL partition is broken too it would probably go to erecovery (erecovery uses its own kernel.)
If you are on AL00 or C636 you can use dload right away. If not we'll have to find another way.

ante0 said:
What is your model of mate 9? (LxxCxxxBxxx)
I thought you should try to flash ramdisk and kernel as well, in case KERNEL partition is broken too it would probably go to erecovery (erecovery uses its own kernel.)
If you are on AL00 or C636 you can use dload right away. If not we'll have to find another way.
Click to expand...
Click to collapse
I don't know here to find my build number without OS, i know it's MHA-L09B

Partition error when trying to restore stock recovery with fastboot

I successfully unlocked the bootloader, flashed TWRP, and installed SuperSU, but now I sold my Mate 9, and the guy would like it back to stock. I extracted RECOVERY.img (the stock recovery) from Update.zip, and used the command: fastboot flash recovery_ramdisk RECOVERY.img and got this output:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (54884 KB)...
OKAY [ 1.749s]
writing 'recovery_ramdisk'...
FAILED (remote: partition error)
finished. total time: 1.796s
Any suggestions come to mind what I may be doing wrong?

No, you can not do that. You can use erecovery to back stock or use dload method (https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656)

gazavn said:
No, you can not do that. You can use erecovery to back stock or use dload method (https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656)
Click to expand...
Click to collapse
With all due respect, don't think all that is necessary. I have been following this comprehensive guide:
https://forum.xda-developers.com/mate-9/how-to/hacking-customizing-managing-huawei-t3589996
and this fellow says I should be able to simply extract the recovery.img from update.zip, and fastboot flash it. If I'm not mistaken you are talking about rebranding it as if I were going to update the phone. I'm not trying to be combative, just seems like a lot of monkeying around...

UPDATE:
I was using the wrong image. I had confused an UPDATE.APP from a different file. Plus I had an olde version of HuaWei Update Extractor. The correct .img file was labeled recovery_ramdis.img, I had been trying RECOVERY.img.

[TWRP] TWRP 3.4-0-0 For Umidigi A7 Pro[MT6763][Android 10]

TWRP for Umidigi A7-Pro phone.
Whats working:
Adb
Mtp
USb-OTG
MicroSD
Flash Image
Mount System , Vendor, product (contents of SUPER).... mount allows reading the partitions, but was not able to write to them
Back-Up/Restore to/from usb (or micro sdcard).... Due to size of super.img needed to format card ext4
Logcat
Screenshot
Known bug:
data decryption is not working, so not able to read or backup internal storage.
Built with Minimum Manifest _branch 10.0 :
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
Kernel source :
****USED STOCK PREBUILDT___MFG Not RELEASED SOURCE*****
Device Tree :
https://github.com/mrmazakblu/Device-TWRP-Umidigi-A7-Pro
Download : https://github.com/mrmazakblu/Device-TWRP-Umidigi-A7-Pro/releases

Thanks for your work!
Does "Flash Image" mean it is now possible to flash Custom Rom's like Lineage OS?
If so which version would I need to download?
Would [GSI][10] LineageOS 17.x GSI (all archs) be the correct version?

torusJKL said:
Thanks for your work!
Does "Flash Image" mean it is now possible to flash Custom Rom's like Lineage OS?
If so which version would I need to download?
Would [GSI][10] LineageOS 17.x GSI (all archs) be the correct version?
Click to expand...
Click to collapse
No, not directly , anyway. You can flash boot
Img, recovery.imf, and super.img.
You could use lpmake and unpack your super.img and repack with the gsi-system.img on your pc and flash that new super.img
There are people using similar tools on the recovery, but I have not tried it.
There is one that cought my attention "system swapper". Unfortunatly I have not tried it yet.
If all you want is to try gsi, stock fastbootD can flash it

i just got this device for my little ones for xmas
so i have time to test whatever until then....
as long as i can still spflash stock image afterwards

mrmazak said:
No, not directly , anyway. You can flash boot
Img, recovery.imf, and super.img.
You could use lpmake and unpack your super.img and repack with the gsi-system.img on your pc and flash that new super.img
There are people using similar tools on the recovery, but I have not tried it.
There is one that cought my attention "system swapper". Unfortunatly I have not tried it yet.
If all you want is to try gsi, stock fastbootD can flash it
Click to expand...
Click to collapse
how to flash gsi on umidigi a7 pro using fastboot bro? or can you put the link of the Ipmake tool for unpacking and repacking super.img thanks

Kidkulafuw8 said:
how to flash gsi on umidigi a7 pro using fastboot bro? or can you put the link of the Ipmake tool for unpacking and repacking super.img thanks
Click to expand...
Click to collapse
I have it written in another device thread. But steps are the same.
[stock Rom] Blu G-90 G0310WW
Blu G90 device shipped from factory with Android 10 as with other devices from blu they do not have a public download of there roms. So here is the stock rom pulled from the device with SP-Flash tool. Both the shipped rom build fingerprint...
forum.xda-developers.com

For now there are still some problems to install .zip, like magisk and gapps, for example, but I hope that it will continue in development until reaching a stable version. Thanks!

Hello may i ask how do i patch vbmeta?

Hello, do you think you will be able to get data decryption working anytime in the future? I need help with a bricked phone...

Hi, I did not find twrp umidigi a3s do you have please

Alucard said:
Hello may i ask how do i patch vbmeta?
Click to expand...
Click to collapse
adb reboot bootloader
fastboot --disable-verification flash vbmeta vbmeta.img

mrmazak said:
No, not directly , anyway. You can flash boot
Img, recovery.imf, and super.img.
You could use lpmake and unpack your super.img and repack with the gsi-system.img on your pc and flash that new super.img
There are people using similar tools on the recovery, but I have not tried it.
There is one that cought my attention "system swapper". Unfortunatly I have not tried it yet.
If all you want is to try gsi, stock fastbootD can flash it
Click to expand...
Click to collapse
Can you please tell me how to do it?
I've tried flashing DotOs 5.2, I extracted it then compressed it back into a zip file then tried to flash it using FastboodD (selecting The option "apply update from Sd Card") but it always gives me the same error "Footer is wrong, Signature verification failed, error 21, Fota installation aborted, Bad file descriptor" Pls help what should I do?

imfedupwiththisphone said:
Can you please tell me how to do it?
I've tried flashing DotOs 5.2, I extracted it then compressed it back into a zip file then tried to flash it using FastboodD (selecting The option "apply update from Sd Card") but it always gives me the same error "Footer is wrong, Signature verification failed, error 21, Fota installation aborted, Bad file descriptor" Pls help what should I do?
Click to expand...
Click to collapse
Your process is not correct. And not along the outline I mentioned in the quoted post.
You cannot flash zip file in fastbootd.
There are more detailed guides here on xda. I do not have a link at the moment. But try and search for "flash gsi with fastbootd" I'm sure you can find guide available.

mrmazak said:
Your process is not correct. And not along the outline I mentioned in the quoted post.
You cannot flash zip file in fastbootd.
There are more detailed guides here on xda. I do not have a link at the moment. But try and search for "flash gsi with fastbootd" I'm sure you can find guide available.
Click to expand...
Click to collapse
It's no problem, I've already solved it

Hello mrmazak, how are you?
I finally managed to flash a GSI on the Umidigi A7 pro. Flashed PHH's GSI AOSP, version 411 - Android 12.
The problem is that when flashing your TWRP, I can't boot, it's in a loop.
I flashed like this:
[email protected]:~/Documentos/A7pro/twrp 340 MRMazak$ sudo su
[sudo] senha para edupaz:
[email protected]:/home/edupaz/Documentos/A7pro/twrp 340 MRMazak# adb devices
List of devices attached
A7PRO205020712 device
[email protected]:/home/edupaz/Documentos/A7pro/twrp 340 MRMazak# adb reboot fastboot
[email protected]:/home/edupaz/Documentos/A7pro/twrp 340 MRMazak# fastboot devices
A7PRO205020712 fastboot
[email protected]:/home/edupaz/Documentos/A7pro/twrp 340 MRMazak# fastboot --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta' OKAY [ 0.014s]
Finished. Total time: 0.027s
[email protected]:/home/edupaz/Documentos/A7pro/twrp 340 MRMazak# fastboot flash recovery recovery.img (I renamed the image)
Sending 'recovery' (23168 KB) OKAY [ 1.389s]
Writing 'recovery' OKAY [ 0.330s]
Finished. Total time: 1.732s
[email protected]:/home/edupaz/Documentos/A7pro/twrp 340 MRMazak# fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.052s
Click to expand...
Click to collapse
Can you give me an idea how to fix the problem?
Now, after writing this message, which I called myself, that this version of TWRP is for Android 10. Do you have any predictions to launch for Android 12?

Umidigi A7 Pro
So ive been out of the loop for several years. I did manage to get root on stock rom finally, now that magisk has been fixed. Been impressed with the ease of use with magisk modules. Its nice to have access to root apps too.
Of course, im still running stock recovery, but am interested in getting custom recovery in there to have the ability to backup/restore, and possibly flash a rom, if any were available.
Thats not really a priority tho, and im wondering if, at this point, if its worth bothering spending the time to change recovery? For a layman, and fairly avg user, would it be beneficial, or would you all say best to just wait and enjoy rooted stock rom for the time being?
Thanks for the effort in developing for this device. Its a solid phone for the money. Only issue ive had is with it not notifying of message push notices in certain apps. Seems to be the rom, cause i can tether to it and get notices on time with every other device