Database Info

Was Bricked - CLT-L04 with EMUI 8.1 - the fixed ended up giving me EMUI 9 CLT-L04

Bricked my phone by doing the following:
Honor View 10 ROMs are compatible with P20 Pro, I installed and used them all. Then the other day they made a mod that force the EMUI 9 update so I ran it. The mod ended rebranding my entire phone to Honor View 10 followed by boot loops like crazy. So then I went into twrp and tried to format thinking it would help. It ended up deleting everything including eRecovery. The only this I had access to was fastboot. Yes I brought this on my self lol. I paid a lot for Funky Huawei but nothing worked. I tried every tool they had.
Fix: (Turns out my phone's structure is now EMUI 9\Android 9)
1- Downloaded my phone image (CLT-L04 - EMUI 9 version), extracted the update.app file from it.
2- Used EMUI extractor app to extracted everything from the update.app file (Lots of image files)
3- Noticed userdata.img wasn't in the extracted files so I downloaded multiple images that are similar models to my phone until I found it.
4- Used fastboot command to flash the userdata.img, followed by eRecovery.img, followed by the rest I pulled from that update.app file.
after about three reboots I was back into my phone except I now have EMUI 9.

My case is similar. I downgraded from B195 to rollback B161. Now I am literally doomed. No erecovery, no huawei logo, just plain black fastboot screen. My bootlodaer is unlocked and I'm unable to relock it. Huawei is denying service, is there any way to revive my black dead phone???
twrp.img gets flashed succesfully but doesnt boot into it.

QuazIqbal said:
My case is similar. I downgraded from B195 to rollback B161. Now I am literally doomed. No erecovery, no huawei logo, just plain black fastboot screen. My bootlodaer is unlocked and I'm unable to relock it. Huawei is denying service, is there any way to revive my black dead phone???
twrp.img gets flashed succesfully but doesnt boot into it.
Click to expand...
Click to collapse
Can you try this.
Files that you will be downloading are,
update.zip
update_full_CLT-L29_hw_eu.zip (Or whatever model of phone you have)
Get them here by searching for your model and click filelist
Prep:
a. Rename update_full_CLT-L29_hw_eu.zip to update_all_hw.zip
b. Download this Flash tool and extract in to a folder in your PC
c. Copy update.zip and update_all_hw.zip to ZIPS-HERE folder (you can find this folder where you have extracted Flash tool
How to flash Firmware
1. Double click to run the file cmd-here.exe. It opens command prompt in the same folder where you are.
2. Once command prompt opens, type FLASH.bat and follow steps carefully. Once flashing is complete, it will boot normally.
- if it fails to detect the files try removing the .zip from the names of the files in the ZIPS-HERE folder
This should bring back eRecovery, recovery, system, whatever. Even at the end if it fails the structure should be rebuilt enough for you to recover via HiSuite application. This worked for me.

Vedrick said:
2. Once command prompt opens, type FLASH.bat and follow steps carefully. Once flashing is complete, it will boot normally.
- if it fails to detect the files try removing the .zip from the names of the files in the ZIPS-HERE folder
This should bring back eRecovery, recovery, system, whatever. Even at the end if it fails the structure should be rebuilt enough for you to recover via HiSuite application. This worked for me.
Click to expand...
Click to collapse
Thanks for offering your help. Mine case looks different....
I have tried this, after flashing twrp in the fastboot the device fails to boot into twrp recovery, it's all black, only fastboot is accessible in the black screen.

I experienced the same problem. Bricked my P20 Pro and can only access fastboot (no access to erecovery). Could you tell me which image that you used to flash userdata.img and erecovery.img? I tried several images but none of them contains userdata.img and erecovery.img.
Thanks.
Edit:
Also, aside from userdata.img and erecovery.img, what files did you flash to the phone?

przival said:
I experienced the same problem. Bricked my P20 Pro and can only access fastboot (no access to erecovery). Could you tell me which image that you used to flash userdata.img and erecovery.img? I tried several images but none of them contains userdata.img and erecovery.img.
Thanks.
Edit:
Also, aside from userdata.img and erecovery.img, what files did you flash to the phone?
Click to expand...
Click to collapse
Update : Good news finally. My device is now unbricked by flashing downloaded OTA from Firmware Finder (Oreo B161 simple non-rollback version) using DC phoenix via testpoint mode. P.S. Flashing B195 pie didn't worked earlier.

QuazIqbal said:
Update : Good news finally. My device is now unbricked by flashing downloaded OTA from Firmware Finder (Oreo B161 simple non-rollback version) using DC phoenix via testpoint mode. P.S. Flashing B195 pie didn't worked earlier.
Click to expand...
Click to collapse
Nice one!!
Can I ask that you help me out as I'm in the same situation? I'm scared about removing back cover and loading credit to CD and still not being able to fix it. A step-by-step idiots guide would be greatly appreciated.
How was it removing the back?
Did you need to buy a new back glass case?
Were are the test points and how do you trigger them?
What FW did you use exactly?
Sorry for the questions but I've yet to find anyone who's provided help to sort it.

QuazIqbal said:
Update : Good news finally. My device is now unbricked by flashing downloaded OTA from Firmware Finder (Oreo B161 simple non-rollback version) using DC phoenix via testpoint mode. P.S. Flashing B195 pie didn't worked earlier.
Click to expand...
Click to collapse
can i ask you are your phone relock after update or not ??if yes are you unlock your phone again with same number and in the end can you give us full guide what you done to unbrick your phone

Deano1889 said:
Nice one!!
Can I ask that you help me out as I'm in the same situation? I'm scared about removing back cover and loading credit to CD and still not being able to fix it. A step-by-step idiots guide would be greatly appreciated.
How was it removing the back?
Did you need to buy a new back glass case?
Were are the test points and how do you trigger them?
What FW did you use exactly?
Sorry for the questions but I've yet to find anyone who's provided help to sort it.
Click to expand...
Click to collapse
I will do my best to answer tomorrow, God willing. Please wait
---------- Post added at 09:04 PM ---------- Previous post was at 08:55 PM ----------
black_1986 said:
can i ask you are your phone relock after update or not ??if yes are you unlock your phone again with same number and in the end can you give us full guide what you done to unbrick your phone
Click to expand...
Click to collapse
After this process your bl will be in 'locked' state. If you had my kind of downgrade brick the imeis and serial will number will not be disturbed. You may simply use your old bl code to unlock. However I messed up my oeminfo but due to my own stupidity, I'm looking to restore my imei and will try to unlock again.

If possible, could you share the files you use?

Downgrade/Unbrick Honor 9 with IMEI fix

First of all sorry for my poor English. If you see any language errors, you may always tell them.
After a long road trying to fix my Honor after a bricked it with flashing wrong files with fastboot, I finally fixed it. Because it was so hard to find the right manual, I will write my method down.
This will work for any kind of brick. By example: black screen or reboot cycle. It will also work when you were on EMUI 9 or on a version with a security patch later then June.
Requisites
Access to the inside of your phone
DC-Phoenix + HCU license
ChimeraTool License
TWRP Files for your phone. I used this one.
Huawei Update Extractor
View attachment nvme.zip: got it from [url]https://t.me/huaweihax[/URL]
HUAWEI USB COM 1.0 driver installed
You can only install this driver with driver signature enforcement disabled. For this is Google your best friend.​Firmware files
You can find those on androidhost.ru. Be sure you download the right files. You need two files: one with a security patch later then June 2018, but with EMUI 8 and also a firmware that was released just before June. Unzip already the files you downloaded.
I used the versions B378C432 and B366C432 for the Honor 9 (STF-L09).​
Fixing your phone
Go into test point mode. See the attached picture. You need to ground this point with some metal plate of the phone. For this you can use a paperclip. You need to press the power button while grounding the test point. You can see in Device Manager if you succeeded when you see HUAWEI USB COM 1.0
{
"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"
}
Start DC-Phoenix and go into the 'update OEMINFO' tab. There you need to select the right bootloader. For me it was the selected on in the picture. You can try as much if you want. This won't harm your phone. Unlock FRP and Update OEMINFO don't need to be checked. Press update and when you get the message with completed you can go to the next step.
Close DC-Phoenix and open ChimeraTool. Cholera will see your phone, if everything went right. Now you need to go to the update firmware tab. Select there the update.app and update_xxx_hw_xxxx.app files from the firmware with the security patch later then June. Otherwise there will be errors while flashing the xloader partition. Now flash these.
Normally your phone reboots automatically. Check in the settings/about if you still have your IMEI. If its not 0000000000 your lucky, otherwise go to the next step.
Shutdown your phone and go into fastboot. You have to extract: kernel, system, vendor and ramdisk from update.app from the firmware with a security patch before June. Flash those files with fastboot:
Code:
fastboot flash kernel kernel.img
It's possible that you get an error while flashing vendor. We fix this later.
Try rebooting.
Code:
fastboot reboot
If it doesn’t boot, go back into fastboot. Flash TWRP:
Code:
fastboot flash recovery_ramdisk twrp.img
.
Go into TWRP by holding volume-up and power. Be sure your phone isn't charging, otherwise it will boot into erecovery. In TWRP you need to flash NVME.zip (you need to flash it 4 times, it's a security precaution). After flashing NVME.zip it should be possible to fastboot flash vendor and reboot correctly.
Check your security patch in settings/about. If it's lower then June, then you've done everything right. Before you use HCU, you need to flash the right recovery_ramdisk (recovery_ramdis) again. Extract it from update.app and flash it with fastboot. Reboot again and let now the magic begin with HCU.
Check in settings/about if you can see your IMEI. If so, then you can use Hisuite to go back to an official firmware.

Hi, I followed your instructions, and unfortunately it did not work. I was able to revive the phone but only with the latest (STF-L09 8.0.0.385 (C432) - STF-L09C432E2R1P5B175 (9.0.1.175)) firmware, everything else is XLOADER error ... My problem now is that I use the IMEI can not fix. Do you know what I can do there? Thank you.

tomek5 said:
Hi, I followed your instructions, and unfortunately it did not work. I was able to revive the phone but only with the latest (STF-L09 8.0.0.385 (C432) - STF-L09C432E2R1P5B175 (9.0.1.175)) firmware, everything else is XLOADER error ... My problem now is that I use the IMEI can not fix. Do you know what I can do there? Thank you.
Click to expand...
Click to collapse
Did you tried the last steps with flashing a lower firmware version with fastboot? I think it also could work when you're on B385.

Item 8, which firmware "update.app recovery_ramdisk" B385 or B366?.
There is no recovery_ramdisk there are both recovery_ramdis.

tomek5 said:
Item 8, which firmware "update.app recovery_ramdisk" B385 or B366?.
There is no recovery_ramdisk there are both recovery_ramdis.
Click to expand...
Click to collapse
You have to use B385. Recovery_ramdisk is equal to the partition named recovery_ramdis.

TWRP (stf-twrp-zxz-0.3.img) hangs on startup image.
Item 5. Should I flash everything (kernel, system, vendor and ramdisk) or just kernels?

tomek5 said:
TWRP (stf-twrp-zxz-0.3.img) hangs on startup image.
Item 5. Should I flash everything (kernel, system, vendor and ramdisk) or just kernels?
Click to expand...
Click to collapse
Weird. Yes, you have to flash the four files.

I did everything that flashed the firmware (STF-L09C432B378 (8.0.0.378)). All without success, always the same, as soon as I flashe the kernel, the system, the manufacturer and the Ramdisk starts the phone to Honor picture and boots again into the Fastboot. TWRP will not work anymore.
fastboot flash kernel KERNEL.img
fastboot flash system SYSTEM.img
fastboot flash ramdisk RAMDISK.img
fastboot flash vendor VENDOR.img

tomek5 said:
I did everything that flashed the firmware (STF-L09C432B378 (8.0.0.378)). All without success, always the same, as soon as I flashe the kernel, the system, the manufacturer and the Ramdisk starts the phone to Honor picture and boots again into the Fastboot. TWRP will not work anymore.
fastboot flash kernel KERNEL.img
fastboot flash system SYSTEM.img
fastboot flash ramdisk RAMDISK.img
fastboot flash vendor VENDOR.img
Click to expand...
Click to collapse
Have you tried booting with volume up and power button pressed? If the blue screen comes up, you can stop pressing the power button. Did you already ones succeeded to get into TWRP?

yes, here I come to the erecovery.

tomek5 said:
yes, here I come to the erecovery.
Click to expand...
Click to collapse
You have to unplug your phone. It may not be charging when you try to get into TWRP.

OK, I did it, the IMEI is back. Did it without TWRP. After flashing the kernel, system, vendor and ramdisk I did a Factory Reset. Then HCU.
Thank you for your help!!!

Clarification
waterboy1602 said:
First of all sorry for my poor English. If you see any language errors, you may always tell them.
After a long road trying to fix my Honor after a bricked it with flashing wrong files with fastboot, I finally fixed it. Because it was so hard to find the right manual, I will write my method down.
This will work for any kind of brick. By example: black screen or reboot cycle. It will also work when you were on EMUI 9 or on a version with a security patch later then June.
Requisites
Access to the inside of your phone
DC-Phoenix + HCU license
ChimeraTool License
TWRP Files for your phone. I used this one.
Huawei Update Extractor
View attachment 4766798: got it from https://t.me/huaweihax
HUAWEI USB COM 1.0 driver installed
You can only install this driver with driver signature enforcement disabled. For this is Google your best friend.​Firmware files
You can find those on androidhost.ru. Be sure you download the right files. You need two files: one with a security patch later then June 2018, but with EMUI 8 and also a firmware that was released just before June. Unzip already the files you downloaded.
I used the versions B378C432 and B366C432 for the Honor 9 (STF-L09).​
Fixing your phone
Go into test point mode. See the attached picture. You need to ground this point with some metal plate of the phone. For this you can use a paperclip. You need to press the power button while grounding the test point. You can see in Device Manager if you succeeded when you see HUAWEI USB COM 1.0
View attachment 4766797
Start DC-Phoenix and go into the 'update OEMINFO' tab. There you need to select the right bootloader. For me it was the selected on in the picture. You can try as much if you want. This won't harm your phone. Unlock FRP and Update OEMINFO don't need to be checked. Press update and when you get the message with completed you can go to the next step.
View attachment 4766799
Close DC-Phoenix and open ChimeraTool. If everything went right, shall Chimera see your phone. Now you need to go to the update firmware tab. Select there the update.app and update_xxx_hw_xxxx.app files from the firmware with the security patch later then June. Otherwise there will be errors while flashing the xloader partition. Now flash these.
Normally your phone reboots automatically. Check in the settings/about if you still have your IMEI. If its not 0000000000 your lucky, otherwise go to the next step.
Shutdown your phone and go into fastboot. You have to extract: kernel, system, vendor and ramdisk from update.app from the firmware with a security patch before June. Flash those files with fastboot:
Code:
fastboot flash kernel kernel.img
It's possible that you get an error while flashing vendor. We fix this later.
Try rebooting.
Code:
fastboot reboot
If it doesn’t boot, go back into fastboot. Flash TWRP:
Code:
fastboot flash recovery_ramdisk twrp.img
.
Go into TWRP by holding volume-up and power. Be sure your phone isn't charging, otherwise it will boot into erecovery. In TWRP you need to flash NVME.zip (you need to flash it 4 times, it's a security precaution). After flashing NVME.zip it should be possible to fastboot flash vendor and reboot correctly.
Check your security patch in settings/about. If it's lower then June, then you've done everything right. Before you use HCU, you need to flash the right recovery_ramdisk (recovery_ramdis) again. Extract it from update.app and flash it with fastboot. Reboot again and let now the magic begin with HCU.
Check in settings/about if you can see your IMEI. If so, then you can use Hisuite to go back to an official firmware.
Click to expand...
Click to collapse
Just for clarification, am sorry if am being a dummy, Step 3: after closing DC phonix, do i use chimera tool for only checking the phone's visibility or I close it again and flash with DC phonix? Please help

Trig18 said:
First of all sorry for my poor English. If you see any language errors, you may always tell them.
After a long road trying to fix my Honor after a bricked it with flashing wrong files with fastboot, I finally fixed it. Because it was so hard to find the right manual, I will write my method down.
This will work for any kind of brick. By example: black screen or reboot cycle. It will also work when you were on EMUI 9 or on a version with a security patch later then June.
Requisites
Access to the inside of your phone
DC-Phoenix + HCU license
ChimeraTool License
TWRP Files for your phone. I used this one.
Huawei Update Extractor
: got it from https://t.me/huaweihax
HUAWEI USB COM 1.0 driver installed
You can only install this driver with driver signature enforcement disabled. For this is Google your best friend.
Firmware files
You can find those on androidhost.ru. Be sure you download the right files. You need two files: one with a security patch later then June 2018, but with EMUI 8 and also a firmware that was released just before June. Unzip already the files you downloaded.
I used the versions B378C432 and B366C432 for the Honor 9 (STF-L09).
Fixing your phone
Go into test point mode. See the attached picture. You need to ground this point with some metal plate of the phone. For this you can use a paperclip. You need to press the power button while grounding the test point. You can see in Device Manager if you succeeded when you see HUAWEI USB COM 1.0
Start DC-Phoenix and go into the 'update OEMINFO' tab. There you need to select the right bootloader. For me it was the selected on in the picture. You can try as much if you want. This won't harm your phone. Unlock FRP and Update OEMINFO don't need to be checked. Press update and when you get the message with completed you can go to the next step.
Close DC-Phoenix and open ChimeraTool. If everything went right, shall Chimera see your phone. Now you need to go to the update firmware tab. Select there the update.app and update_xxx_hw_xxxx.app files from the firmware with the security patch later then June. Otherwise there will be errors while flashing the xloader partition. Now flash these.
Normally your phone reboots automatically. Check in the settings/about if you still have your IMEI. If its not 0000000000 your lucky, otherwise go to the next step.
Shutdown your phone and go into fastboot. You have to extract: kernel, system, vendor and ramdisk from update.app from the firmware with a security patch before June. Flash those files with fastboot: It's possible that you get an error while flashing vendor. We fix this later.
Try rebooting. If it doesn’t boot, go back into fastboot. Flash TWRP:
Just for clarification, am sorry if am being a dummy, Step 3: after closing DC phonix, do i use chimera tool for only checking the phone's visibility or I close it again and flash with DC phonix? Please help
Click to expand...
Click to collapse
You should use Chimera to flash the firmware.

Thanks
waterboy1602 said:
You should use Chimera to flash the firmware.
Click to expand...
Click to collapse
Thank you very much , my device is now fully operational on EMUI9 though I used Dc phonix to flash it in upgrade mode.
Thanks again ??

Hi, waterboy1602!
Are you sure that for HCU works only with security patches LOWER than June 2018 ?
I am trying to find out exactly this dates, and firmware to downgrade.
BTW. On 4pda admins wrotes that it is not possilbe to downgrade to no_gpu_turbo version.
Do you know something about it ?

daemonserj said:
Hi, waterboy1602!
Are you sure that for HCU works only with security patches LOWER than June 2018 ?
I am trying to find out exactly this dates, and firmware to downgrade.
BTW. On 4pda admins wrotes that it is not possilbe to downgrade to no_gpu_turbo version.
Do you know something about it ?
Click to expand...
Click to collapse
Yes, after a lot of trial and error I found out that it only works with a firmware lower then June 2018. I know that most people say it's impossible to downgrade to no_gpu_turbo. I found this way to work with my phone. I've put a lot of time into it to find this way. I hope it will also work for you.

Hi, such a question, what should I do if I short-circuited the wrong contacts and after flashing the phone is forever detected as a comport and will not turn

DydoserLolekDrago said:
Hi, such a question, what should I do if I short-circuited the wrong contacts and after flashing the phone is forever detected as a comport and will not turn
Click to expand...
Click to collapse
Honestly I have no idea. If the testpoints don't work anymore, I dont think you have a lot of options.

how exactly do i ground the testpoint?
i connect it with gnd? or just press it with the
paperclip?
can it break the phone?

Honor 8 loopboot - some partition errors in the flash - twrp

I can not find a way to avoid errors in the flash process, I attach some images.
{
"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"
}
a bit of context and history of the things I did:
This is an Honor 8 FRD-AL00 from China, in 2017 I unlocked the bootloader, I rebrand the phone into its Europe version FRD-AL09, then I updated to Emu5, then in my first vacation on Europe (I am from Argentina), the phone ask me for an update. As I knew that I used an Europe ROM, full rebrand, I did not saw nothing nothing wrong with that (if I wanted an update on Argentina, I have to forced with the hisuite), so I accept the official update there.
Results: the phone was bricked.
I buy a new phone there, I kinda forget over some years, now I want to fix it, but seem that it is quite hard, I dont think this is a soft brick.
First I had problems installing TWRP, the only way was using the Multi-Tool8 from @teammT flashing the TWRP 3.1.1 as Erecovery.
If i try to update the twrp to 3.4 from the same twrp or using fastboot, I cant.
I tried to flash a ROM from a similar year than my last correct update, fail using commands, fail using the tool, fail using an extra SD on dload, fail using TWRP.
I tried the same thing with the stock firmware for FRD-AL09 (the multi-tool8 always recognize the phone as FRD-AL09, but I have errors when is flasshing.
The only firmware that I can flash without errors, is one from C185 (mid east latin america), which is the most downloaded firmware in huawei, with emui8 and android 8, but I dont have the cust.img in that update, the bootloop continue.
I tried with a different latin versionbut the flash does not work.
I tried with a custom rom (lineage for honor8), the instalation process seem ok, until I receive the same errors at the end (it can not mount vendor, cust, etc).
I tried to format system, cust, or the partitions that I receive errors, changing first to fat or anyone else, then apply again ext4, but nothing happen, the error persist.
I even had a backup made with TWRP when the phone was working fine, I tried to restore that backup with TWRP and I receive error.
I tried to do all these test using a linux with fastboot (in case I was having issues with some drivers), but I receive the same errors.
Still not sure how to choose the right firmaware, I already tried with 10 already.... most fullota firmwares does not have all the files that I need to unbrick.
I already tried with android 6, 7 y 8, from c432, c185, and one more.
I tried by dload (update), by the 3 zips in twrp, by img from twrp or fastboot, or using the multi tool.
Today I will keep trying to update twrp from 3.1.1 to 3.4, (maybe that would help me to install android 8 roms?) Where I can find the extra cust.img?
I really need to repair this phone, I dont care if it is with an official or custom firmaware, I know that all this seem hard to solve, but I would appreciate at least a clue that would help me to save this phone.

AngelLestat said:
I can not find a way to avoid errors in the flash process, I attach some images.
a bit of context and history of the things I did:
This is an Honor 8 FRD-AL00 from China, in 2017 I unlocked the bootloader, I rebrand the phone into its Europe version FRD-AL09, then I updated to Emu5, then in my first vacation on Europe (I am from Argentina), the phone ask me for an update. As I knew that I used an Europe ROM, full rebrand, I did not saw nothing nothing wrong with that (if I wanted an update on Argentina, I have to forced with the hisuite), so I accept the official update there.
Results: the phone was bricked.
I buy a new phone there, I kinda forget over some years, now I want to fix it, but seem that it is quite hard, I dont think this is a soft brick.
First I had problems installing TWRP, the only way was using the Multi-Tool8 from @teammT flashing the TWRP 3.1.1 as Erecovery.
If i try to update the twrp to 3.4 from the same twrp or using fastboot, I cant.
I tried to flash a ROM from a similar year than my last correct update, fail using commands, fail using the tool, fail using an extra SD on dload, fail using TWRP.
I tried the same thing with the stock firmware for FRD-AL09 (the multi-tool8 always recognize the phone as FRD-AL09, but I have errors when is flasshing.
The only firmware that I can flash without errors, is one from C185 (mid east latin america), which is the most downloaded firmware in huawei, with emui8 and android 8, but I dont have the cust.img in that update, the bootloop continue.
I tried with a different latin versionbut the flash does not work.
I tried with a custom rom (lineage for honor8), the instalation process seem ok, until I receive the same errors at the end (it can not mount vendor, cust, etc).
I tried to format system, cust, or the partitions that I receive errors, changing first to fat or anyone else, then apply again ext4, but nothing happen, the error persist.
I even had a backup made with TWRP when the phone was working fine, I tried to restore that backup with TWRP and I receive error.
I tried to do all these test using a linux with fastboot (in case I was having issues with some drivers), but I receive the same errors.
Still not sure how to choose the right firmaware, I already tried with 10 already.... most fullota firmwares does not have all the files that I need to unbrick.
I already tried with android 6, 7 y 8, from c432, c185, and one more.
I tried by dload (update), by the 3 zips in twrp, by img from twrp or fastboot, or using the multi tool.
Today I will keep trying to update twrp from 3.1.1 to 3.4, (maybe that would help me to install android 8 roms?) Where I can find the extra cust.img?
I really need to repair this phone, I dont care if it is with an official or custom firmaware, I know that all this seem hard to solve, but I would appreciate at least a clue that would help me to save this phone.
Click to expand...
Click to collapse
Flash EMUI8 and immediately wipe system and extract and flash https://github.com/phhusson/treble_...v300.l/system-roar-arm64-aonly-vanilla.img.xz (this is the compressed form extract using 7zip)
so that you flash system-roar-arm64-aonly-vanilla.img. into system partition.

AngelLestat said:
I can not find a way to avoid errors in the flash process, I attach some images.
a bit of context and history of the things I did:
This is an Honor 8 FRD-AL00 from China, in 2017 I unlocked the bootloader, I rebrand the phone into its Europe version FRD-AL09, then I updated to Emu5, then in my first vacation on Europe (I am from Argentina), the phone ask me for an update. As I knew that I used an Europe ROM, full rebrand, I did not saw nothing nothing wrong with that (if I wanted an update on Argentina, I have to forced with the hisuite), so I accept the official update there.
Results: the phone was bricked.
I buy a new phone there, I kinda forget over some years, now I want to fix it, but seem that it is quite hard, I dont think this is a soft brick.
First I had problems installing TWRP, the only way was using the Multi-Tool8 from @teammT flashing the TWRP 3.1.1 as Erecovery.
If i try to update the twrp to 3.4 from the same twrp or using fastboot, I cant.
I tried to flash a ROM from a similar year than my last correct update, fail using commands, fail using the tool, fail using an extra SD on dload, fail using TWRP.
I tried the same thing with the stock firmware for FRD-AL09 (the multi-tool8 always recognize the phone as FRD-AL09, but I have errors when is flasshing.
The only firmware that I can flash without errors, is one from C185 (mid east latin america), which is the most downloaded firmware in huawei, with emui8 and android 8, but I dont have the cust.img in that update, the bootloop continue.
I tried with a different latin versionbut the flash does not work.
I tried with a custom rom (lineage for honor8), the instalation process seem ok, until I receive the same errors at the end (it can not mount vendor, cust, etc).
I tried to format system, cust, or the partitions that I receive errors, changing first to fat or anyone else, then apply again ext4, but nothing happen, the error persist.
I even had a backup made with TWRP when the phone was working fine, I tried to restore that backup with TWRP and I receive error.
I tried to do all these test using a linux with fastboot (in case I was having issues with some drivers), but I receive the same errors.
Still not sure how to choose the right firmaware, I already tried with 10 already.... most fullota firmwares does not have all the files that I need to unbrick.
I already tried with android 6, 7 y 8, from c432, c185, and one more.
I tried by dload (update), by the 3 zips in twrp, by img from twrp or fastboot, or using the multi tool.
Today I will keep trying to update twrp from 3.1.1 to 3.4, (maybe that would help me to install android 8 roms?) Where I can find the extra cust.img?
I really need to repair this phone, I dont care if it is with an official or custom firmaware, I know that all this seem hard to solve, but I would appreciate at least a clue that would help me to save this phone.
Click to expand...
Click to collapse
I think that the error 255 might be a bad download
-------------------------------------------
PLEASE TRY THIS SOLUTION
I think that the solution to fix this device is "Hurupdater" you just have to rename the 3 firmware files and flash the hurupdater in the same folder using twrp. It should flash the firmware file and also it keeps the bootloader unlocks. it works on honor 8. Hurupdater is also a better way to flash updates.
[Tool] [HuRUpdater] [0.4] [Flash official firmware in recovery
Here I present my tool to flash Honor stock firmware in TWRP recovery. I have tested it on all currently available firmwares for Honor 9 STF but still this tool is beta. HuRUpdater Huawei Recovery Updater Flash official firmware zip files Can...
forum.xda-developers.com
--------------------------------------------
But if hurupdater method does not work (Im sure Hurupdater would actually work though)
1. Restart device
2. When your on the "Your device has been unlocked and can't be trusted" quickly hold volume button (make sure you are doing it fast enough), it should boot into a stock recovery look alike screen.
3. Now click button that says about downloading latest firmware. Pick your wifi. DONE
Beware that this will relock the bootloader and also put your device on android oreo (EMUI 8)

CHECK_123 said:
I think that the error 255 might be a bad download
-------------------------------------------
PLEASE TRY THIS SOLUTION
I think that the solution to fix this device is "Hurupdater" you just have to rename the 3 firmware files and flash the hurupdater in the same folder using twrp. It should flash the firmware file and also it keeps the bootloader unlocks. it works on honor 8. Hurupdater is also a better way to flash updates.
[Tool] [HuRUpdater] [0.4] [Flash official firmware in recovery
Here I present my tool to flash Honor stock firmware in TWRP recovery. I have tested it on all currently available firmwares for Honor 9 STF but still this tool is beta. HuRUpdater Huawei Recovery Updater Flash official firmware zip files Can...
forum.xda-developers.com
--------------------------------------------
But if hurupdater method does not work (Im sure Hurupdater would actually work though)
1. Restart device
2. When your on the "Your device has been unlocked and can't be trusted" quickly hold volume button (make sure you are doing it fast enough), it should boot into a stock recovery look alike screen.
3. Now click button that says about downloading latest firmware. Pick your wifi. DONE
Beware that this will relock the bootloader and also put your device on android oreo (EMUI 8)
Click to expand...
Click to collapse
Nice but once hurupdater does not work and need to relock bootloader, the bootloader can be difficult to unlock again.

jjgvv said:
Nice but once hurupdater does not work and need to relock bootloader, the bootloader can be difficult to unlock again.
Click to expand...
Click to collapse
I think you can try the "Your device has been unlocked and can't be trusted" trick and from what i posted then clicking download latest firmware. But it would relock bootloader and put it into EMUI 8. Unlocking the bootloader is also easy anyways, once you get the bootloader code, you can write it down or put it in notepad to always have the bootloader unlock code.
The Honor 8 also has 2 recoveries, one from holding vol up from "Your device has been unlocked and can't be trusted" and also the normal recovery partition where you usually put twrp in (vol up + power button)
You can also use hurupdater to go from android 8 to android 7. The hurupdater method should work because it flashes all the partitions including "Cust.img".
If you dont want to use Hurupdater, then I think you should just do "Your device has been unlocked and can't be trusted" method because it downloads stock firmware including "Cust.img".
And also you dont have to flash "Cust.img". If you extract "Cust.img" you can manually the files on to /cust then It should maybe work.

CHECK_123 said:
I think you can try the "Your device has been unlocked and can't be trusted" trick and from what i posted then clicking download latest firmware. But it would relock bootloader and put it into EMUI 8. Unlocking the bootloader is also easy anyways, once you get the bootloader code, you can write it down or put it in notepad to always have the bootloader unlock code.
The Honor 8 also has 2 recoveries, one from holding vol up from "Your device has been unlocked and can't be trusted" and also the normal recovery partition where you usually put twrp in (vol up + power button)
You can also use hurupdater to go from android 8 to android 7. The hurupdater method should work because it flashes all the partitions including "Cust.img".
If you dont want to use Hurupdater, then I think you should just do "Your device has been unlocked and can't be trusted" method because it downloads stock firmware including "Cust.img".
And also you dont have to flash "Cust.img". If you extract "Cust.img" you can manually the files on to /cust then It should maybe work.
Click to expand...
Click to collapse
lol 2 recovery partitions
anyway maybe update.app can be extracted?

jjgvv said:
lol 2 recovery partitions
anyway maybe update.app can be extracted?
Click to expand...
Click to collapse
Yes, there is also a app called "ZArchiver" in Play Store. It can extract "Update.app". But I dont think it can extract .img files. You may need a computer to extract the .img files.

CHECK_123 said:
Yes, there is also a app called "ZArchiver" in Play Store. It can extract "Update.app". But I dont think it can extract .img files. You may need a computer to extract the .img files.
Click to expand...
Click to collapse
.img is easy, if you get system.img then nice, but i cant extract the super.img where system.img is in it.

Stock rom of Doogee S96 pro

Dear community,
I have a doogee S96 pro, I'm from Italy, and I installed TWRP from the unofficaltwrp guide.
Now I'm no more able to boot, the phones goes directly to the recovery.
Probably magisk was no able to patch the system and to disable the tm verity (avb). I have a super partition, and from what I saw the fstab is inside the vendor partition inside super.
Doogee does not provide stock roms, so I cannot restore the phone as factory settings, that's why I open this thread.
Is someone available to help me booting into Android or available to give me the stock boot/recovery img? It's a fast and safe procedure, I can give more details on how to do.
Thank you!

Dear @giubenez I had a similar problem. But after I got in touch with doogee support they sent me the firmware. I want to share it with you and with any other person that wants to ROOT THE DOOGEE S96 PRO
The following link is the firmware and upgrade tool. Please open and download.
Please note that if your computer system is French you need to change the name of the downloaded file.
Spoiler: Link
ZN129（S96）
Folder
1drv.ms
When upgrading the firmware, please do not select the 'Format All+Download' option
When flashing the phone, please set up the software first, turn off the phone, and then connect the phone to the computer.
Best wishes

Wow! thank you!!!
You saved... us!
Why doogee does not respond to me? why they not post the firmware on the forum? WTF

@giubenez Im very happy to contribute something. IDK why doogee doesnt list this firmware in their website. I was very lucky to receive an answer to my emails.
Also I successfully rooted my S96 PRO, but I learned a few things in the process that might be helpful to you or anyone trying to root this model.
1) After flashing the boot.img (using magisk method). The device went into a boot loop. I could not enter into recovery mode either. I discovered vbmeta was responsible for the boot loop.
Google introduced vbmeta which is also a verity check. An option to bypass this check is to flash an empty vbmeta.img before attempting to flash TWRP recovery.
Click to expand...
Click to collapse
I solved this by flashing an empty vbmeta file.
Code:
fastboot flash vbmeta vbmeta.img
You can download the vbmeta.img file I used HERE
2) After flashing vbmeta, the device finally booted and the root was done. But the first time, I noticed all the internal storage folders and files were encrypted. (I know this is normal when you browse files through TWRP, but it happened to me while using the phone in the first boot)
I solved that by wiping > Format Data in TWRP
3) Here you can find the files I used to install TWRP and remove the orange state notification on boot: LINK "Credits to www.getdroidtips.com"

Ankiseth said:
@giubenez Im very happy to contribute something. IDK why doogee doesnt list this firmware in their website. I was very lucky to receive an answer to my emails.
Also I successfully rooted my S96 PRO, but I learned a few things in the process that might be helpful to you or anyone trying to root this model.
1) After flashing the boot.img (using magisk method). The device went into a boot loop. I could not enter into recovery mode either. I discovered vbmeta was responsible for the boot loop.
I solved this by flashing an empty vbmeta file.
Code:
fastboot flash vbmeta vbmeta.img
You can download the vbmeta.img file I used HERE
2) After flashing vbmeta, the device finally booted and the root was done. But the first time, I noticed all the internal storage folders and files were encrypted. (I know this is normal when you browse files through TWRP, but it happened to me while using the phone in the first boot)
I solved that by wiping > Format Data in TWRP
3) Here you can find the files I used to install TWRP and remove the orange state notification on boot: LINK "Credits to www.getdroidtips.com"
Click to expand...
Click to collapse
GOD BLESS YOU, Ankiseth!
YOU SAVE MY PHONE! SPFLASH AND EVERYTHING WORKS!

Hi guys : I need help. Since the last firmware update (settings/about phone/update) DOOGEE-S96Pro-EEA-Android10.0-20210128, my Ir Camera don't work anymore
Video : https://oracle.tuxme.net/s/Xng63Ej3kJoJhOj
When I used the dial mode *#*#8613#*#* SINGLE TEST
* INFRAED LIGHT : i see the IR light
* Night Vision camera : app crash like the camera when i switch to the night vision mode.
Doggee mail me :
Good day, I would like to ask you to help us. Please use the following link: https://1drv.ms/u/s!AvX9KABcpSV1kTOgCMsUkLyXY-we?e=nMchxl Download the previous version of the S96pro firmware and follow the tutorial to return the phone to OTA The previous version (ver3.02) was upgraded. The tutorial has been included in the firmware compression package. Please test the night vision camera after flashing the camera and let me know if it can be used normally. Thank you very much.
Click to expand...
Click to collapse
But the documentation is .... you know ...
Have you a step by step tutorial or tools to do that ?
Beanpod_ActiveTool is a tool to modified serials, Imei ?
Have i to used SP Flash tool ?
Thanks guys !!
by the way @Ankiseth :
Please note that if your computer system is French you need to change the name of the downloaded file.
Click to expand...
Click to collapse
which file ?

berzerking said:
Hi guys : I need help. Since the last firmware update (settings/about phone/update) DOOGEE-S96Pro-EEA-Android10.0-20210128, my Ir Camera don't work anymore
Video : https://oracle.tuxme.net/s/Xng63Ej3kJoJhOj
When I used the dial mode *#*#8613#*#* SINGLE TEST
* INFRAED LIGHT : i see the IR light
* Night Vision camera : app crash like the camera when i switch to the night vision mode.
Doggee mail me :
But the documentation is .... you know ...
Have you a step by step tutorial or tools to do that ?
Beanpod_ActiveTool is a tool to modified serials, Imei ?
Have i to used SP Flash tool ?
Thanks guys !!
by the way @Ankiseth : which file ?
Click to expand...
Click to collapse
There Is Hope Brother... I Just Downloaded The Files And Used The SCATTER-LOADING FILE From 3.02 on SP-FlashTools 5.2 Switched It To Download Only And Hit Download .. Plugged In My Phone To USB While OFF And aftyer the loading was complete .. Phone Reboot As If NEW. ( HARD RESET) EVERYTHING LOST WARNING.. But IR CAMERA is Working AGAIN!!!!! Now i Just Have To ReLoad All Apps And Accounts .. And Wait For The oukitel WP7 i ordered out of frustration. Will Be Doing A Review Comparison On Both Cameras !!!!! You Can Follow Me Here If Interested https://www.youtube.com/channel/UCYOpd4yooYgKS-0xe63jnCw

Hi all. Thanks for the information. I was in touch with doogee and they say to me that there is an update during this WE (S9S88A7.DGE.DOOGEE.EEA.HB.HJAYYDVFAZ.0128.V3.03820210313-2312.
Nothing change IR camera don't work
I will flash my S96pro during the week with S9S88A7.DGE.DOOGEE.EEA.HB.HJ.AYYDVFAZ.1130.V3.02.zip and I'll post here what happened

HouseOwl said:
) EVERYTHING LOST WARNING.. But IR CAMERA is Working AGAIN!!!!!
Click to expand...
Click to collapse
Yes !!!!! it s alive !!!!
Thank you dude ! my ir works again !!!!!

btw a couple of days after your post, another user posted the same folder on https://4pda.ru/forum/index.php?showtopic=1010578&st=340.
I rooted the phone by using the 4pda method (i.e. flashing super.img, boot.img, vbmeta.img). After that I flashed twrp and it was fine. Everything was working.
After that I downloaded the OTA update and the phone is no more able to boot, simply goes to TWRP. I tried formatting data, dalvik and cache but the situation is always the same: when i try to boot i go to the recovery. Any idea? Thank you

berzerking said:
But the documentation is .... you know ...
Have you a step by step tutorial or tools to do that ?
Beanpod_ActiveTool is a tool to modified serials, Imei ?
Have i to used SP Flash tool ?
Thanks guys !!
by the way @Ankiseth : which file ?
Click to expand...
Click to collapse
Can you write a tutorial? Have you used SP flash tool?
Thank you!

giubenez said:
btw a couple of days after your post, another user posted the same folder on https://4pda.ru/forum/index.php?showtopic=1010578&st=340.
I rooted the phone by using the 4pda method (i.e. flashing super.img, boot.img, vbmeta.img). After that I flashed twrp and it was fine. Everything was working.
After that I downloaded the OTA update and the phone is no more able to boot, simply goes to TWRP. I tried formatting data, dalvik and cache but the situation is always the same: when i try to boot i go to the recovery. Any idea? Thank you
Click to expand...
Click to collapse
I solved in this way:
>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
(with the empty vbmeta
>fastboot.exe flash recovery recovery.img
(with the stock recovery)
>fastboot reboot
after that the update attempted to start and failed, the phone then boot to android.
The updates always failes after that, so I disabled them.

this is why the update fails..is it because I used the the Russian super img?
{
"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"
}
#edit: it was because I flashed the wrong recovery. With the correct one, i still have issues with the update: md5 chechsum controll is not passed and the update aborts.
I don't care, I prefer a rooted phone without the updates.

your device has not passed the test and may not work properly - Here is a message on the screen . Constantly overloaded is not included in the recovery. The firmware doesn't help.

Could someone repost the S96Pro stock firmware... I can't find it anywhere online, thanks in advance

I'm uploading them.
https://bit.ly/3en9EZY

Thanks giubenez ,u saved me but now I have the watermark from formatting Google Key State : Fail, I don't see a factory mode file to freeze, tried ADB and couldn't find the build prop values, has anyone else ran into this with a fix?

I can't get what problem are you facing. I unlocked and rooted my s96 pro.
If you describe your issue i can help you solving it.
However, i found very risky to root the phone, if you plan to do the ota updates avoid TWRP since it'll make you bootloop at the moment you try to install the update.
The only way to solve it is to flash the stock recovery through adb.

So.. yeah.
I have recently procured this device and want to install twrp, and stock and/or test a gsi and in what capacity the phone works with one of those.
Enabled both developer mode & the usb debug mode and adb devices lists the device.
N.B; the supplied s96pro cable does not seem to carry data, "presumably" because doogee is cheapskates on cables, as well in the support department. I had to use my sony headphone cable. Go figure, its consequential at least, so there's that.
In any case, read this thread and have downloaded all files, including the apparently new stock rom that is listed since yesterday in the evidently wholesome user Ankiseth's link above.
Questions:
In the 4pda link there are some instructions, specifically the adb command with the boot.img, however.. the links seems to be dead. What to do?
A) Can I first do the vbmeta command and then use our lord and savior Ankiseth's twrp recovery file and follow a generic "Case II: Devices with A/B partition scheme" mentioned in this xda twrp guide?
B) Hope that some other wholesome user share the boot.img file?
(Or, can I use the one in the zip file 'S9S88A7.DGE.DOOGEE.HB.HJ.AYYDVFAZ.1203.V3.04' ?)
-
After twrp is accessible can I use twrp/adb and install either the mentioned shared rom and any gsi for that matter?
I use linux and sure there is spflash, but the adb & twrp combo "subjectively feels" as a more stable way of doing things.

Update 2. Got both twrp and magisk going. Now to figure out if I can install a gsi.
Update, got spflashtool working and used the latest stock rom mentioned in my previous post.
However.
I patched the boot.img from said stock rom in magisk and also flashed twrp-recovery with fastboot.
No luck. Magisk seems not to be installed and the usual twrp gui does not show, seems to be the stock recovery. Got a orange state though.

TruConnect CloudMobile Stratus C5 Elite Firmware

Hello,
I have been trying to root this device for some time now without success. I know for Magisk to work I need a copy of the boot.img from the stock factory image and I have been unable to find the factory image anywhere. I know there's a way to pull the boot.img from the device itself with TWRP installed but, there's no TWRP image for this device either and I need the recovery.img to port that over. I wonder if there is a way to pull the boot.img and recovery.img from the device without TWRP installed and without root? Perhaps someone knows. I was able to unlock the bootloader in fastboot with: fastboot flashing unlock .
This is a very light device with not a lot of memory or storage and I'd love to be able to tweak it out a bit to remove a lot of clutter and enable it to run smoother and charge faster and hold a charge longer. I removed some bloat through adb. Any help would be greatly appreciated. I will attach screenshots of the system specs below. Thank you for your time.
{
"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"
}

I have that phone at home, I've tried numerous ways to root it with no avail. The ONLY solution I can suggest is finding a program that can extract the entire firmware from the phone and then taking it from there. Plus, with a unlocked bootloader u shouldn't have an issue getting it done. I do remember coming across the topic of firmware extraction online and im pretty sure one of the methods involved ADB, but it's a painstaking process cus u have to extract everything one by one. Search Google about that method. Good luck man.

I am having problems with my lock screen pattern the buttons are not working. What do I do I can't get in my phone

__Pno.0iD said:
I have that phone at home, I've tried numerous ways to root it with no avail. The ONLY solution I can suggest is finding a program that can extract the entire firmware from the phone and then taking it from there. Plus, with a unlocked bootloader u shouldn't have an issue getting it done. I do remember coming across the topic of firmware extraction online and im pretty sure one of the methods involved ADB, but it's a painstaking process cus u have to extract everything one by one. Search Google about that method. Good luck man.
Click to expand...
Click to collapse
Full_Device_Stock_Backup.7z | by kushpr for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I found this. I'm not sure who it is. I have not tested it. But a boot image is present. It maybe for Android 10 or 11 but it holds vbmeta as well. If bootloader is unlocked I would assume patch with magisk and flash via fastboot flash boot. I tried many ways to fastboot boot a image as I don't wish to flash a untested image. It always fails so I'm not entirely sure.
******curiosity ed the cat. These do not boot. FML LOL******.
The boot images do not boot. However if I flash the provided vbmeta as fastboot flash --disable-verification --disable-verity vbmeta /patchedvbmeta.img then the user provided twrp fastboot flash boot /c5twrp.img. I can then fastboot reboot and it will now load twrp with no storage being mounted. I also prior fastboot flashing unlock.
Fastboot flashing unlock_critical
Not sure if that worked for critical or not.

JovialQuestion said:
Full_Device_Stock_Backup.7z | by kushpr for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I found this. I'm not sure who it is. I have not tested it. But a boot image is present. It maybe for Android 10 or 11 but it holds vbmeta as well. If bootloader is unlocked I would assume patch with magisk and flash via fastboot flash boot. I tried many ways to fastboot boot a image as I don't wish to flash a untested image. It always fails so I'm not entirely sure.
Click to expand...
Click to collapse
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Heres the files for the device I found but again I've tested none

Hey, flashed the boot images and now phone won't boot, which was expected honestly, but how do I restore original firmware from the bin files in the backup.7z archive?

Kylethedarkn said:
Hey, flashed the boot images and now phone won't boot, which was expected honestly, but how do I restore original firmware from the bin files in the backup.7z archive?
Click to expand...
Click to collapse
I'm not sure as I did not upload the bin file. However I did find out that boot img and frimware is not for the Android 12 go but 10 go release C5 stratus but the twrp when I flashed to the boot partition would boot it. You can try and see if flashing it will boot the twrp img and ar least your able to use root adb. Otherwise I'm still trying to figure it out. I simply found the files while searching

JovialQuestion said:
Full_Device_Stock_Backup.7z | by kushpr for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I found this. I'm not sure who it is. I have not tested it. But a boot image is present. It maybe for Android 10 or 11 but it holds vbmeta as well. If bootloader is unlocked I would assume patch with magisk and flash via fastboot flash boot. I tried many ways to fastboot boot a image as I don't wish to flash a untested image. It always fails so I'm not entirely sure.
******curiosity ed the cat. These do not boot. FML LOL******.
The boot images do not boot. However if I flash the provided vbmeta as fastboot flash --disable-verification --disable-verity vbmeta /patchedvbmeta.img then the user provided twrp fastboot flash boot /c5twrp.img. I can then fastboot reboot and it will now load twrp with no storage being mounted. I also prior fastboot flashing unlock.
Fastboot flashing unlock_critical
Not sure if that worked for critical or not.
Click to expand...
Click to collapse
I have tested the Full Stock Backup and it's 100√ working..

Kylethedarkn said:
Hey, flashed the boot images and now phone won't boot, which was expected honestly, but how do I restore original firmware from the bin files in the backup.7z archive?
Click to expand...
Click to collapse
What I did was I put the phone on Brom/preloader and flash with Rom2Box version 3.0 , select on Firmware folder .no scatter file

Smil3yWulf said:
What I did was I put the phone on Brom/preloader and flash with Rom2Box version 3.0 , select on Firmware folder .no scatter file
Click to expand...
Click to collapse
Thanks for this

Mtkclient allowed me to root mine

Smil3yWulf said:
I have tested the Full Stock Backup and it's 100√ working..
Click to expand...
Click to collapse
Awesome.. I know the C-5 twrp uploaded by the same person worked when I flashed it to the boot partition after the flashed boot img failed for me. If it has a recovery partition maybe you can flash that and try it out to the recovery partition
Twrp
20.82 MB folder on MEGA
mega.nz

My bootloader is unlocked, twrp flashed to recovery booting fine when selected from the button combo preloader or whatever, but I still have no boot.img. I only have access to computers running linux right now so rom2box is kinda not a reliable option for me. Is there some way of turning boot.bin and/or boot_para.bin into a bootable boot.img? Or is there any way anybody who still has one of these phones could get a working one from their phone by way of twrp or something? Is the c5 treble compatible?

Jason Hugg said:
My bootloader is unlocked, twrp flashed to recovery booting fine when selected from the button combo preloader or whatever, but I still have no boot.img. I only have access to computers running linux right now so rom2box is kinda not a reliable option for me. Is there some way of turning boot.bin and/or boot_para.bin into a bootable boot.img? Or is there any way anybody who still has one of these phones could get a working one from their phone by way of twrp or something? Is the c5 treble compatible?
Click to expand...
Click to collapse
A boot.bin file is a img. .bin .img .fex .iso are all image files. How large is the boot.bin file. 34mb? 64mb and this bootloader doesn't fastboot boot unless it's got dtb and I'm not familiar with it. Flash the boot.bin and try to boot if your boot slot is already messed up should not be a issue to try.

What ended up working for me was to go to the Advance Fastboot tab in the Android part of rom2box and flash each partition, rebooted after and success. So I fastboot flash --disable-verification --disable-verity vbmeta vbmeta.bin, which allowed me to fastboot flash recovery twrp-C5.img and it boots fine from the boot selection screen. After/during initial setup, phone did a mandatory system up[date, but since I knew I could reflash and recover from a screw up, I installed Magisk Manager and used it to patch and flash the boot.bin included in the backup and it worked fine. Just figured I'd post an update in case it might help anyone else

Jason Hugg said:
Sorry my page keeps redirecting and I am posting in the wrong posting
Click to expand...
Click to collapse

I have the boot.img for the cloud stratus C5 elite if you still need it. I have the complete stock firmware for the phone. If you need it just message me

chuck1es909090 said:
I have the boot.img for the cloud stratus C5 elite if you still need it. I have the complete stock firmware for the phone.
Click to expand...
Click to collapse
DO NOT SEND IN EMAILS. This is a forum so people can get assistance with the help of others. You can share the files here but it's not recommended to share your email asking for people to contact you that way. Not to mention everyone can now see your email and your personal data