Hi everyone,
I have an 10.8 inch wifi only tablet imported from China, non-pro, model CMR-W09C00 which was running firmware B123.
I was playing around trying to convert it to a global firmware and tried to flash it with the same firmware 123 but for CMR-W09C432 using Huawei Firmware Finder.
Turns out this was a pretty bad idea
Now the tablet is not booting and I can't figure out how to recover. Here's what I tried:
1. eRecovery is not working, it downloads the firmware completely and tries to install but fails. It did work fully once before I tried to flash the wrong firmware.
2. Wiping cache and data partition does nothing
3. I have access to fastboot and can unlock/lock the bootloader at will.
4. I have the full-OTA zip file for the original firmware CMR-W09C00B123 and have extracted all the img files contained in update.app
5. I'm trying / hoping to flash images to recover (with bootloader unlocked) but I'm a bit confused at this step.
All the instructions I found in my research mention mostly flashing just boot.img, system.img and recovery.img but I'm missing some of those files from the update.app or I guess they could be named differently. I don't have a boot.img, just a fastboot.img which I'm sure is not the same. I also don't have a recovery.img, just recovery_ramdis, recovery_vbmeta, recovery_vendor, erecovery_ramdis, erecovery_vendo, erecovery_vbmet and erecovery_kerne.
I was able to flash system.img successfully but that didn't help.
Also tried to use the unbrick feature from Huawei Multi-Tool but here again I seem to be missing image files. Multi-Tool says it needs system.img, ramdisk.img, cust.img, ramdisk_recovery.img and userdata.img.
Of those, I think I'm missing cust.img for sure, ramdisk_recovery I might have but it's named differently (recovery_ramdis) and userdata.img I don't think I really need.
I'm attaching a txt file with a list of all the img files I do have in case it can be useful or rings a bell for someone.
Oh yeah, I also tried flashboot update update.zip but it's only giving me this warning:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
So...does anyone have any advice or suggestions? Is there a better method to recover that I missed?
Any help is appreciated!
Flash the ramdisk.img to ramdisk and report back please. I have an M3 that is in the same condition as yours, but I am on an extended deployment and won't be able to test this for at least another month :/
fargonaz said:
Flash the ramdisk.img to ramdisk and report back please. I have an M3 that is in the same condition as yours, but I am on an extended deployment and won't be able to test this for at least another month :/
Click to expand...
Click to collapse
Thanks for taking the time to the reply mate, sorry to hear about your M3.
I tried fastboot flash ramdisk ramdisk.img and it said flashed successfully but the device is still not booting. Nothing else seems to have changed either.
Let me know if I misunderstood what you wanted to try or if you have any other ideas.
Cheers
etheberge said:
Hi everyone,
I have an 10.8 inch wifi only tablet imported from China, non-pro, model CMR-W09C00 which was running firmware B123.
I was playing around trying to convert it to a global firmware and tried to flash it with the same firmware 123 but for CMR-W09C432 using Huawei Firmware Finder.
Turns out this was a pretty bad idea
Now the tablet is not booting and I can't figure out how to recover. Here's what I tried:
1. eRecovery is not working, it downloads the firmware completely and tries to install but fails. It did work fully once before I tried to flash the wrong firmware.
2. Wiping cache and data partition does nothing
3. I have access to fastboot and can unlock/lock the bootloader at will.
4. I have the full-OTA zip file for the original firmware CMR-W09C00B123 and have extracted all the img files contained in update.app
5. I'm trying / hoping to flash images to recover (with bootloader unlocked) but I'm a bit confused at this step.
All the instructions I found in my research mention mostly flashing just boot.img, system.img and recovery.img but I'm missing some of those files from the update.app or I guess they could be named differently. I don't have a boot.img, just a fastboot.img which I'm sure is not the same. I also don't have a recovery.img, just recovery_ramdis, recovery_vbmeta, recovery_vendor, erecovery_ramdis, erecovery_vendo, erecovery_vbmet and erecovery_kerne.
I was able to flash system.img successfully but that didn't help.
Also tried to use the unbrick feature from Huawei Multi-Tool but here again I seem to be missing image files. Multi-Tool says it needs system.img, ramdisk.img, cust.img, ramdisk_recovery.img and userdata.img.
Of those, I think I'm missing cust.img for sure, ramdisk_recovery I might have but it's named differently (recovery_ramdis) and userdata.img I don't think I really need.
I'm attaching a txt file with a list of all the img files I do have in case it can be useful or rings a bell for someone.
Oh yeah, I also tried flashboot update update.zip but it's only giving me this warning:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
So...does anyone have any advice or suggestions? Is there a better method to recover that I missed?
Any help is appreciated!
Click to expand...
Click to collapse
I think I am in a similar spot. I went from a custom ROM back to stock, but now all attempts at installing full OTAs fail. Did you ever figure this out how to fix it?
Thanks
Related
This is for real, folks. The first working custom recovery for Asus ZenPad 8.0 Z380M and a method to flash it under a locked bootloader. This took quite a bit of work to make, partly due to having to find a way to bypass the locked bootloader. And because of a kernel configuration issue that limited the size of the initial ramdisk, which took some serious effort to weed out. @lss1977 helped to port it to this device. And of course, credits to TeamWin for TWRP.
In addition to this thread, the current Z300M/Z301M TWRP thread and the the old Z300M recovery/rooting thread may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the other.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)*
MediaTek VCOM drivers (available through Windows Update)
Z380M scatter file, attached
Recovery image, attached
Z380M preloader file (optional), available inside the stock firmware download
ZenPad Z380M tablet upgraded to Android N
* If you prefer to use a more recent SP Flash Tool, check out the special image file below.
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 8.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image (twrp-3.2.1-0-z380m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z380m.img
Once inside TWRP, flash twrp-3.2.1-0-z380m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
(Updated February 3, 2018: updated kernel to firmware 5.3.18; up-to-date TWRP 3.2.1 sources)
SP Flash Tool v5.1532
Z380M Scatter file for all storage sizes (right click, Save link as...)
Recovery image
Signed image for Flash Tool only -- may be flashed with recent SP Flash Tool versions -- DO NOT INSTALL USING ANY OTHER METHOD -- tested with SPFT 5.1736.
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Nice one now lets get some custom roms done.
Has anyone installed this yet? I see the file has been downloaded a few times. Any feedback is welcome.
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
The way I did it was to edit the init.rc file inside the boot ramdisk and comment out the service block that calls install_recovery.sh. I used the MTK boot image unpack/repack tools. I don't know, it seems like changing anything on the system partition will break OTA updates because of dm-verity. Because that depends on verifying each block of the file system. I have never even mounted the system as R/W in recovery.
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
PxYra said:
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
Click to expand...
Click to collapse
OK, I added the scatter file as a download. It was a pain in the ass to copy & paste. (But it did work.)
Problem fixed downloaded new version of flashtool 5.16 and scatter working
Ok I installed TWRP on Z380M P00A, and wanna say to other
1. Use VCOM drivers only from splash tool official site
2. To install VCOM drivers first need enter chinese recovery tablet, then in windows device manager you see USB device, install manualy drivers (don forget in windows disable driver signature)
3. Use only SP-Flash-Tool-v5.1532.00, newer or older version not properly working with this phone
Ok, thanks for the update, PxYra. Just to let you know, there are signed versions of VCOM drivers floating around so you don't need to mess with signature enforcement. Here's one: https://www.androidfilehost.com/?fid=24591000424943663. They are also updated by Windows so you can just let Windows Update install them.
Thanks for your work.
Flashing procedure works only with "MTK_AllInOne_DA.bin" method for me. But this is OK!
(Updated May 6, 2017: added kernel from firmware 5.3.7, source code cleanup)
Click to expand...
Click to collapse
is it possible to get the older versions? I need Android 6.x, because of xposed-Framework for my Zenpad 8.0 Z380M.
Greets Freisei
Hey freisei...
I never posted a version for Android 6. There was just one based on the 5.3.6 kernel, practically the same as the current one. That's why I didn't keep it. I could try to build one for you if you want, but I can't test it of course. Does this recovery not boot at all on the old firmware?
It's strange that the DA_PL.bin method didn't work for you. What happened when you tried it? I suppose the old preloader doesn't allow it(?).
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:05 PM ----------
Can anyone help me? after selecting recovery img, pressing download and inserting usb cable, nothing happens. Thanks in advance
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Pires_7 said:
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Click to expand...
Click to collapse
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Pires_7 said:
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
Click to expand...
Click to collapse
Nope, no chance.
diplomatic said:
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Nope, no chance.
Click to expand...
Click to collapse
Ok. I made some real s*it, I think I deleted every partition except recovery. Can you provide me a twrp backup or some way around my problem?
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
diplomatic said:
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
Click to expand...
Click to collapse
i was able to extract system.new.dat from stock firmware zip, but it extracts to a system folder. How do I flash this through sp flash tool?
OK, the system folder you don't need. It should have produced a system.img file also. That's the file you need to flash. Just select it for the system partition row in the partition list and then Download. Hopefully that will be enough.
EDIT: I just looked at the script, and realized the system.img.img file gets deleted in the process. So what you need to do is start the extraction, then after it makes system.img.img, when it starts extracting individual files, hit Ctrl+C. Then you'll end up with the img file.
Thank you very much! it works! YOU are the BEST!
please tell me, in your scatter file, address partition_name: frp (0x80a5000) is correct? if i format this partition (frp), google account remove?
Hello,
I've been recently trying to root my Asus Zenfone 3 Max (ZC520TL) using SP Flash tool,
however, I haven't found the correct scatter file for my device. Does anyone know where
I could find a MT6737 scatter file? Thanks in advance!
Hi. From my experience, correct scatter files that work (not just any random scatter file) reside in a ROM/Firmware zip.
Doing a little searching, I found that you can download stock firmware for you device from Asus officially. They offer them in the support section.
Here is the link: https://www.asus.com/us/Phone/ZenFone-3-Max-ZC520TL/HelpDesk_Download/
Should you download the official firmware specific to your device and unzip the file, (in all probability) you will also find the correct scatter file which you are looking for (something like xxxxx_scatter_file.txt).
(also keeping in place a stock rom is never but never a bad idea )
However... You mentioned that you need the scatter file to root??? I have not any idea as to why you would need SP Flash tool for any other reason than flashing stock.
Unless you are flashing full custom rom which cannot be flashed through recovery perhaps?
Anyway... Good luck!!!
Thanks for the quick response!
r&xp said:
Hi. From my experience, correct scatter files that work (not just any random scatter file) reside in a ROM/Firmware zip.
Doing a little searching, I found that you can download stock firmware for you device from Asus officially. They offer them in the support section.
Here is the link:
Should you download the official firmware specific to your device and unzip the file, (in all probability) you will also find the correct scatter file which you are looking for (something like xxxxx_scatter_file.txt).
(also keeping in place a stock rom is never but never a bad idea )
However... You mentioned that you need the scatter file to root??? I have not any idea as to why you would need SP Flash tool for any other reason than flashing stock.
Unless you are flashing full custom rom which cannot be flashed through recovery perhaps?
Anyway... Good luck!!!
Click to expand...
Click to collapse
I needed the Flash tool because I was trying to flash TWRP, and from there install superuser. I did as you said, but when I tried loading the scatter file
the program recognized it as invalid. A huge thanks for the help though!!!
mcAlex42 said:
I needed the Flash tool because I was trying to flash TWRP, and from there install superuser. I did as you said, but when I tried loading the scatter file
the program recognized it as invalid. A huge thanks for the help though!!!
Click to expand...
Click to collapse
Ok... No worries!! We will probably figure it out in the end.
By the way, I am not sure I understand exactly how you were going to use SP Flashtool to flash TWRP. From my experience it does not work that way. You need platform tools (adb and fastboot).
platform tools here ----> https://developer.android.com/studio/releases/platform-tools.html
It is with these that you will unlock bootlader, and after bootloader is unlocked, first flash supersu, install busybox and lastly flash twrp.
Please look at my how-to root and twrp section. It is not for your device, but it will give you a good idea of the process: https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727
Please also check your private messages. I am sending you some links you might find helpful.
hi there.
soooo I kinda bricked my mate 10 lite (RNE-L21C432)
bootloader is unlocked, rooted.
I tried flashing a flashable rom and got a bootloop...sooooo
I downloaded the firmware via huawei firmware finder , the oreo one.
I opened the UPDATE.APP via huawei update extractor, there are alot of files, so can you please tell me what files I need to extract and flash to unbrick my phone?
I extracted system, kernel, vendor and odm for now, system flashed fine. but I cant flash kernel it gives me the error FAILED: remote: command not allowed
can you pleaste help me?
Edit: I can flash system, I did flash kernel, I can flash recovery too, but when I try to flash anything else, it gives me that error
Edit2: can someone tell me which files do I need to extract via huawei update extractor to flash? I know that system.img is one of them
konopla4 said:
hi there.
soooo I kinda bricked my mate 10 lite (RNE-L21C432)
bootloader is unlocked, rooted.
I tried flashing a flashable rom and got a bootloop...sooooo
I downloaded the firmware via huawei firmware finder , the oreo one.
I opened the UPDATE.APP via huawei update extractor, there are alot of files, so can you please tell me what files I need to extract and flash to unbrick my phone?
I extracted system, kernel, vendor and odm for now, system flashed fine. but I cant flash kernel it gives me the error FAILED: remote: command not allowed
can you pleaste help me?
Click to expand...
Click to collapse
Check if you're still FRP unlock in Fastboot.
ante0 said:
Check if you're still FRP unlock in Fastboot.
Click to expand...
Click to collapse
Both bootloader and from are unlocked
konopla4 said:
Both bootloader and from are unlocked
Click to expand...
Click to collapse
Ah, didn't see your edit.
Fastboot is limited in flashing, you can't flash everything.
From memory I think it is:
System, vendor, recovery_ramdisk, recovery_vendor, recovery_vbmeta, ramdisk, kernel, cache, userdata
You could use HWOTA for Mate 10 Lite if you can get into stock recovery, as it will flash the full update.app rather than the limited partitions fastboot can flash.
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
ante0 said:
Ah, didn't see your edit.
Fastboot is limited in flashing, you can't flash everything.
From memory I think it is:
System, vendor, recovery_ramdisk, recovery_vendor, recovery_vbmeta, ramdisk, kernel, cache, userdata
Click to expand...
Click to collapse
So I can flash all of these without getting the error and it'll will restore my system?
I remember on p8 lite I needed to flash only system, boot, and cust. To restore the system. It was much easier.
konopla4 said:
So I can flash all of these without getting the error and it'll will restore my system?
I remember on p8 lite I needed to flash only system, boot, and cust. To restore the system. It was much easier.
Click to expand...
Click to collapse
Edited while you posted, use HWOTA if you can get into stock recovery
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
ante0 said:
Edited while you posted, use HWOTA if you can get into stock recovery
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
Click to expand...
Click to collapse
Yeah, just noticed.
So hwota. I don't have the "stock recovery" I can only flash the recovery that I extract from update.app
The one I flash is bugged for some reason, probably because it's from a slightly different system than the one I had.
konopla4 said:
Yeah, just noticed.
So hwota. I don't have the "stock recovery" I can only flash the recovery that I extract from update.app
The one I flash is bugged for some reason, probably because it's from a slightly different system than the one I had.
Click to expand...
Click to collapse
If it can be booted into it should work. HWOTA will replace it anyway with a no-check recovery. Or you could use TWRP by Caucava21 and use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to update from TWRP.
Either way will work.
ante0 said:
If it can be booted into it should work. HWOTA will replace it anyway with a no-check recovery. Or you could use TWRP by Caucava21 and use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to update from TWRP.
Either way will work.
Click to expand...
Click to collapse
Waaaait it, I can update from TWRP?
Or is it a specialized one?
konopla4 said:
Waaaait it, I can update from TWRP?
Or is it a specialized one?
Click to expand...
Click to collapse
It's a script, but it needs a TWRP that's compatible. The one by Catuva21 is (or so I've heard).
How should I install an original Huawei rom , no brand, downloaded from their cloud?
The name file is: ATU-L11C55CUSTC55D1B150 (8.0.0.150).zip
the ROM is a .zip with the files in the photo inside:
I tried the procedure to extract the update.app file and put it in the dlod folder of the SD card, but it does not install.
I have the privileges of ROOT and I have unlocked the bootloader, I can not install the
* TWRP Recovery.
Help!
since it is not possible to install the ROM version "update.APP", unzipping this with "HuaweiUpdateExtractor", which files should I flash with fastboot in bootloader mode?
Is this possible?
Yes, use the HuaweiUpdateExtractor and flash the system.img with fastboot.
Best regards
Yes, use the HuaweiUpdateExtractor and flash the system.img with fastboot.
Best regards
which files should I flash?
you need to download the full rom, go here: https://www.mobileheadlines.net/download-huawei-y6-2018-firmware-files-all-versions/
download the FullOTA-MF for your model and extract the zip, after that use huaweiupdateextractor on the update.app and extract SYSTEM.img
reboot into bootloader and flash the extracted SYSTEM.img to your phone using fastboot flash system SYSTEM.img
please make a tutorial thread. i want to use the original rom too.
Fakkurai said:
you need to download the full rom, go here: https://www.mobileheadlines.net/download-huawei-y6-2018-firmware-files-all-versions/
download the FullOTA-MF for your model and extract the zip, after that use huaweiupdateextractor on the update.app and extract SYSTEM.img
reboot into bootloader and flash the extracted SYSTEM.img to your phone using fastboot flash system SYSTEM.img
Click to expand...
Click to collapse
I tried and despite the flash of fastboot is successful I always find myself with the original TIM branded ROM, I do not know what else to do!
henryxp said:
I tried and despite the flash of fastboot is successful I always find myself with the original TIM branded ROM, I do not know what else to do!
Click to expand...
Click to collapse
there are paid rebranding services, which can work for qualcomm based devices
mutahharbashir said:
there are paid rebranding services, which can work for qualcomm based devices
Click to expand...
Click to collapse
yes I know, there's a guy, the one who gave me the bootloader code, that wants $ 20 to debrandize it, too much for so little ..
Hi,
I have global Honor 9, updated to 8.0.0.379(C432), unlocked and rooted.
Previously in order to get the OTA I flashed stock recovery B364 since it was the recovery of the version I had.
Now I found recovery B368, I couldn't find recovery C432 anywhere. Does it matter? will I be able to get the OTA if I flash stock recovery B368 while I have firmware C432, or will it brick my phone?
Thanks
Clonimus said:
Hi,
I have global Honor 9, updated to 8.0.0.379(C432), unlocked and rooted.
Previously in order to get the OTA I flashed stock recovery B364 since it was the recovery of the version I had.
Now I found recovery B368, I couldn't find recovery C432 anywhere. Does it matter? will I be able to get the OTA if I flash stock recovery B368 while I have firmware C432, or will it brick my phone?
Thanks
Click to expand...
Click to collapse
C432 is the code for the HONOR 9 global (STF-L09C432), yor version is B379 and you can extract the recovery from the FULL-OTA firmware file version B379.
mtvento said:
C432 is the code for the HONOR 9 global (STF-L09C432), yor version is B379 and you can extract the recovery from the FULL-OTA firmware file version B379.
Click to expand...
Click to collapse
How do I do that?
I opened the image file there was no recovery.img
Also, I tried using the "Huawei Update Extractor" but I couldn't figure out what the recovery was (there was no file there called recovery)
Thanks
Clonimus said:
How do I do that?
I opened the image file there was no recovery.img
Also, I tried using the "Huawei Update Extractor" but I couldn't figure out what the recovery was (there was no file there called recovery)
Thanks
Click to expand...
Click to collapse
Extract the update.app file from the firmware .zip file you downloaded;
launch the Huawei Update Extractor and select "Unknown" as profile and the extracted update.app as file,
it should read the content and give you a list of files inside, with all the .img ones too.
Right click an the one you need and select extract and the destination.
In case of error opening the file go to the extractor settings and disable header crc checking.
Hope it helps you
I downloaded the Update.zip and update_full_STF-L09_hw_eu.zip from this link.
The update.app from Update.zip file didn't work, it gave the error recovery_ramdis.img: invalid header crc - expected: 16878 got: 54779
So I disabled the header crc check as you suggested, but doesn't it create a risk of corrupted extraction?
I attach 2 pics:
one has no img with the name "recovery", can it be under a different name - this is from the full ROM
The other has multiple recovery img files, none is "recovery.img", they have different prefixes (similar ones, like RAMDI and RAMDIS), which one do I need to use? is it different than "recovery.img"?
Thanks
Clonimus said:
I downloaded the Update.zip and update_full_STF-L09_hw_eu.zip from this link.
The update.app from Update.zip file didn't work, it gave the error recovery_ramdis.img: invalid header crc - expected: 16878 got: 54779
So I disabled the header crc check as you suggested, but doesn't it create a risk of corrupted extraction?
I attach 2 pics:
one has no img with the name "recovery", can it be under a different name - this is from the full ROM
The other has multiple recovery img files, none is "recovery.img", they have different prefixes (similar ones, like RAMDI and RAMDIS), which one do I need to use? is it different than "recovery.img"?
Thanks
Click to expand...
Click to collapse
recovery_ramdis.img