Hi,
I´m getting software install failed! on my Huawei wile doing an OTA ROM update.
It is an intermediate update so update.app does not have system.img, but rather the update.zip has folders with a patch for the /System.
As of that, I wanted to know what's wrong, so, is there any log file created from the update procedure?
G Play Mini - CHC-U01 Update to V100R001C434B120
OTA URL:
http://update.hicloud.com/TDS/data/files/p3/s15/G854/g104/v29161/f1/full/update.zip
Inside update.zip is update.app (and the folders to patch the /system) which in turn compacts another update.app inside.
So, either "open inside" update.app or extract update.app from update.zip, rename that update.app to update.zip and open the last update.zip to get the update.app that can be opened with HuaweiUpdateExtractor to get the *.img files (exept system.img).
Since I can´t adb in recovery I can´t do a logcat.
Can anyone help me debug the OTA update?
Build Number
This is getting more like a diary...
I found the log file in ./splash2/recovery.log
Now, where is the system getting the information of the build number other than from build.prop, because the info on the "about" menu is different form what is in ro.build.display.id or any other variable on the file.
I'll appreciate any help!
I found that the variable is stored in ./cust/hw/eu/prop/local.prop (on my case the path "eu" is because my CustCVersion is European, on Russian should be .../ru/prop/local.prop").
Unfortunately I didn´t know that CWM doesn´t include cust.img on nandroid backups, so i don´t have the original ./cust structure to replace the original settings.
i have update fail with chc-u01 firmware 6.0.
how cani do?
Related
Hello
here i am posting here because i cant post on Miscellaneous Android Development , how ever i think i post there before while working on B5512
I Just got new G700 it came with B115 middle east channel , phone is good but as a start is there is a update i must ask my self is root ready , and CWM for sure so i start the digging
@chamaruco thank you for your great thread which saved and helped many people
now i got a file and i think you were looking for it ""G700-U10_V100R001C00B124CUSTC432D001_Firmware_Portugal_Channel-Others_4.2.1_EMUI 1.8_05021LMW.zip"" it contain usb upgrade and sd upgrade with drv and flash tool
i notice EMUI 1.8 not 1.6 which i saw for example a permission manager with it on P6 is that here in that rom too ?
is that rom improved than mine b115 phone is good for first look but
(in B115)
1-camera quality is strange i dont mean bad but it look very strange it is like very poor on quality
2-in call volume is too low in my opinion all " in test mode"
Question now did any one get that update "EMUI 1.8 B124" can tell is there is any improvements ?!
Question am i able to flash CWM image directly with flash tool to save some annoying procedures ?!
a member here provide flasher and cwm.img and orginal recovery.img
i did not work with the phone yet need to shift data from old phone remove ext2 part and prepare for change , and feeling lost here
want to strike it all once
i will upload "EMUI 1.8 B124" soon as it came from a private server
any suggestions are welcome
When you install 1.8 you will notice there is only a tap error from uploader..it is a 1.6 emui. That's all.
Hello
some info to add
incase of softbrick the phone and unable to flash using spflash tool and receive " not allowed , forbidden "
solution
inside the usb upgrade >> flash "Rework-Secro" using scatter in same folder then you will be able to use download mode again
how to install this firmware i.e. B124 on G700-10
chamaruco said:
When you install 1.8 you will notice there is only a tap error from uploader..it is a 1.6 emui. That's all.
Click to expand...
Click to collapse
chamaruco; Thanks for the best of the best user guides you have been making for all of us, but what i want to know is to be able to install the B124 into my phone i.e. G700-10, i have rooted my phone using farmaroot, made a back up of my factory shipped OS and make all my data backup safe through Hisuit, have downloaded the firmware B124 Purtogal version, extracted the zip, (it is now carrying META-INF, boot.img, cust.img, logo.bin, sdload.log, system.img) i have made a folder in my SD card named dload and copied the files in it, uninstalled mobileuncle, reinstalled new mobileuncletool, copied my backuped recovery.img into my SDcard and somehow installed the recovery in to my mobile,
now please show me the way forward, what i need to do and how, please step by step if you kindly can. please.
YOU ARE THE BEST CHAMARUCO
talvigi said:
chamaruco; Thanks for the best of the best user guides you have been making for all of us, but what i want to know is to be able to install the B124 into my phone i.e. G700-10, i have rooted my phone using farmaroot, made a back up of my factory shipped OS and make all my data backup safe through Hisuit, have downloaded the firmware B124 Purtogal version, extracted the zip, (it is now carrying META-INF, boot.img, cust.img, logo.bin, sdload.log, system.img) i have made a folder in my SD card named dload and copied the files in it, uninstalled mobileuncle, reinstalled new mobileuncletool, copied my backuped recovery.img into my SDcard and somehow installed the recovery in to my mobile,
now please show me the way forward, what i need to do and how, please step by step if you kindly can. please.
YOU ARE THE BEST CHAMARUCO
Click to expand...
Click to collapse
Dload inside put update.app file, restart in updatemode
chamaruco said:
Dload inside put update.app file, restart in updatemode
Click to expand...
Click to collapse
But my mobile does not boot into CWM recovery mode as i have seen in my previous Qmobile A8 it always restarts in the defualt recovery mode which only give options to "1. reboot, 2. update from SDcard, 3. update from cashe, 4. wipe/delete user data and wipe/delete cache and in the last there is a calibarate TP, AND OFF COURSE THESE ALL ARE THE ANDROID BUILTIN RECOVERY STEPS NOT OF THE CWM
And off course there is not any file or folder named update.app in the downloaded .zip/extracted file. "as i have mentioned above the folder contains a folder named META-INF and three img files named as boot cust and system while a .bin file named logo too.
THANKS FOR YOUR TIME AND HELP.
foffa said:
Hello
some info to add
incase of softbrick the phone and unable to flash using spflash tool and receive " not allowed , forbidden "
solution
inside the usb upgrade >> flash "Rework-Secro" using scatter in same folder then you will be able to use download mode again
Click to expand...
Click to collapse
So after I select the Reworked scatter file there is only the sec_ro partition checked to flash. So after flashing it do I now select the previous scatter file and then flash everything (including preloader)?
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Downunder35m said:
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Click to expand...
Click to collapse
Thank you for this explanation, but the explanation of the video to better understand everyone
Will see if I can at least add some pics while working on Nougat.
Hello,
Thanks for you tutorial.
I have a h96 Pro+ and the last firmware was a .img file... (Link of the firmware : https://mega.nz/#F!d1tHVZgA!Qc0mAom7FBHT9HDv3rGtGQ )
Is there a good guy who can convert this .img to a .zip file please ?
A lot of users are asking for this, me too and if you can help me to do this it will be really cool and appreciate
Thank you,
Carmin.
Thanks for your explanation im trting to port 7.1.1 to my tv box and i have found one funcional the only troble is the wi fi drivers not working ill give it a try latter today
Sent from my SM-N9300 using Tapatalk
Hello!
So, I have a Android Box MXQ 4K and I'm trying to create an update.zip from the latest update (wich I only found in .IMG format).
I know the box can do a update from a update.zip file. So I extracted the files from the IMG, extracted the system.img, and created the update.zip file using instructions that I found here in the forum. But it gave me an error that wasn't a valid package (yes, I signed it). I didn't tried to aply the update.zip direct from the Recovery Menu, because if I stay too much time (30s+) on the recovery menu, it gives me a Green Screen. What are my options?
I'm trying to root my M5 (SHT-W09, C567). I have unlocked the bootloader and installed Magisk but am having problems extracting and patching the ramdisk.img file. I would appreciate anyone who could double check my steps or see if they spot my error.
Here is what I have done.
1) Using HFF, downloaded, the Update.zip file (full image), size is approximately 4 GB.
2) Copied image over to Windows laptop
3) Downloaded Huwei Image Extractor
4) Set image extractor to unknown profile
5)Under settings, unchecked verify header and file checksum
6) The extractor extracted 33 files
Here is where I need assistance, how do I proceed? Do i need to .zip the ramdisk file and then copy it over to the tablet? I've attached an image of the files that were extracted. Any assistance would be appreciated.
Thanks,
Rick
@C5Longhorn you can now select the RAMDISK.img entry from that bundle and extract it to your PC. Then you copy that file by e.g
adb put RAMDISK.img /sdcard/
onto your device. Then you need to open Magisk-Manager (which you should have already installed on your device) and seldct the RAMDISK.img from /sdcard/ and a patched_boot.img will be created. This is the file which you later on need to flash back onto your device as ramdisk.img
AndDiSa said:
@C5Longhorn you can now select the RAMDISK.img entry from that bundle and extract it to your PC. Then you copy that file by e.g
adb put RAMDISK.img /sdcard/
onto your device. Then you need to open Magisk-Manager (which you should have already installed on your device) and seldct the RAMDISK.img from /sdcard/ and a patched_boot.img will be created. This is the file which you later on need to flash back onto your device as ramdisk.img
Click to expand...
Click to collapse
Ok, i copied the file to my computer desktop, and then attached device to computer and I copied into my SD card download folder but kept getting an error when I would run Magisk that it failed.
Do I need to use adb to push the file or does it not matter how it's copied. Maybe I'm placing in the wrong folder or need to zip file.
I'll try again and screenshot the messages. I really appreciate your help.
Sent from my Pixel 2 using Tapatalk
@C5Longhorn how you copy the file to your device doesn't matter. Do you have Magisk-Manager installed? Did you select the patch option and did you choose patch boot file and did you select the RAMDISK.img as the file to be patched? What is the error message Magisk-Manager is giving you? Did you use MagiskManager-5.7.0.apk?
Yes, to all. I'll capture and post the error I'm receiving when I can get back to the tablet. Thanks again.
Sent from my Pixel 2 using Tapatalk
I finally got it. I zipped the ramdisk file, moved it to Dropbox and then downloaded it locally to the tablet. I then went through the Magisk Manager process and it created the patched file.
I'm rooted now but notice I can't open Magisk without the app closing very quickly afterwards.
Is this normal? Also, I noticed "preserve AVB 2.0/dm-verity is not checked. Should it be?
Sent from my SHT-W09 using Tapatalk
I wiped the Magisk app data and now the app will open.
Sent from my SHT-W09 using Tapatalk
If run MagiskManager - run 1..2 second - self-close : it's a bug.
The new Version is 5.8.0 and i hope it's debuged.
The Bug is a optical Problem, root work.
Can version 5.8 be installed without losing root or do you have to repush the patched file again?
Sent from my Pixel 2 using Tapatalk
I installed 5.8 Magisk Manager and did not have to reload ramdisk image file.
Sent from my SHT-W09 using Tapatalk
2 Way for install Magisk
Way 1 : the device is new and TWRP is not available
download your build, extract "ramdisk.img" and copy on device (example: to "download")
download MagiskManager.App (actual 5.8.0), install, run and let MM modify the boot.img (in OREO is inside ramdisk.img)
fastboot flash ramdisk patched_boot.img
Way 2 : install "twrp_p10_0.1.img"
fastboot flash recovery_ramdisk twrp_p10_0.1.img
boot to recovery (TWRP) and TWRP-Install Magisk-v16.0.zip (actual)
this 2 way work on my device CMR-AL09 8.0.0.161(C432)
i use way 1 if device new on market and twrp not available
if twrp available i use way 2
the core-question is : the build from your device
extract from your-build full-update "ramdisk.img"
All Huawei/Honor with OREO have the same OS, but the build is different
HI,
I would like to update my mediapad to the latest update available.
However, you can't update through the official updater when you're root.
Can i flash back the original ramdisk.img and do the official update, then root it back with the new ramdisk.img patched ?
Tanogeek said:
HI,
I would like to update my mediapad to the latest update available.
However, you can't update through the official updater when you're root.
Can i flash back the original ramdisk.img and do the official update, then root it back with the new ramdisk.img patched ?
Click to expand...
Click to collapse
Normally when there are changes on the ramdisk.img a full update image will be installed by the OTA update process. Your proposed way will be probably sufficient to get only the delta update.
anyone have any idea how to install incremental updates manually? i have an ota incremental package, have even dumped the contents and have the .img files inside but not sure what to do with them as they are not full partition images just the increments(i guess just the parts that need to be changed of the actual partitions) is there any way to merge them or how else should they be used? i tried to use payload dumper with --diff but that just keeps giving me an error that boot image type isnt supported so i can get all the other files and no boot image with it. if anyone has any ideas i would greatly appreciate it. i downloaded the oneplus software updater to try the local upgrade/update and it just keeps telling to put it in the root directory and i have put the zip and the extracted contents in every directory i can think of to no avail. oxygen updater also doesnt support this device (yet)
nvm i found the answer thanks to someone on tg..
encrypt the incremental with ofpflasher and update