Hey,
is it possible to create your own ota update?
Why this idea? When I create my own update.zip I have to boot into recovery system and install update.zip there. Creating a ota update file is much faster, because the phone would reboot and the installation is going on without user interaction.
So is this possible? Are there any topics about ota-update files?
Thanks flo
Related
Hi,
I recently ported the ClockworkMod recovery to a new device. I built a fakeflash using the CyanogenMod SDK without errors, but when I install the update.zip signed with the test keys it fails the signature verification. I found the ota certificates zip file the device used, but I don't know how to sign it using the device's ota certificates. Any help is greatly apperciated.
Note: OTA updates don't work on my Nexus 5 due to TWRP blocking them. Now my phone doesn't recognize the OTA update anymore (When my phone went to install the OTA updated and rebooted, it rebooted into TWRP instead and completely ignores the updates existence since then). To fix this I plan to simply push the factory img of 5.0.1 to my device directly. I downloaded the factory .img from Google's website .
However instead of a .img file i'm used to, I got a .tgz. I extracted that and got a .tar and then extracted that to finally get my folder with the .img files. However now I'm not sure which one to push to my device. There is a img file called "radio-hammerhead-m8974a-2.0.50.2.22.img" but judging by the file size, I don't think that's the correct one (only 45MB). There is a .zip file called "image-hammerhead-lrx22c.zip" but this contains multiple .img files, the largest one called "system.img". I'm guessing this is the correct one to push to my device via adb since it's about 1GB in size?
I suspect pushing the entire .zip file to my phone and flashing that would be bad as it looks like it'll overwrite TWRP?
Any help would be greatly appreciated.
Here's a lot of useful information about OTA's Check it out: http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
You'll need boot and system at least,
If you plan on keeping twrp and root, you may as well just flash one of the flashable zips already available in the development forum
Actually you should have a radio and bootloader img file. First one is - as the name says - the latest radio software (which is needed for GPS, WiFi, cellular network and so on). Second one is the latest bootloader. I'd update them both.
From the zip archive you should only flash certain imgs - if you flash all your data will be wiped (factory reset). What img files does the zip contain?
Why are you pushing them to your phone? You need to flash with fastboot from your computer. There is not just one img file for the update, there are several for different partitions on the phone. Have a look through some of the guides in the general section. Also, flashing one of the stock flashable zips would be much faster, but why not learn a little as you update.
Vomer has a thread of flashable 5.0 and 5.0.1 stock Google ROMs. Don't worry about factory images because you will lose everything once you flash these and it's a much bigger pain imo to back everything including internal on your phone up.
snappycg1996 said:
Don't worry about factory images because you will lose everything once you flash these
Click to expand...
Click to collapse
Not necessarily true.
You can flash bootloader, radio, and system without losing anything. You'll just have to reroot afterward.
Hello,
My device is the Mate 9 (MHA-L29C185B110) and I seem to have a problem with the camera.
When pressing the button to take a photo, the camera app restarts itself. I try again, but didn't work, to no avail.
I also tried to record a video. It seems to work, but the camera freezes but it's still counting, otherwise recording.
I have just recently flashed a custom recovery img (TWRP), the boot img on another thread that prevents the device from being automatically encrypted, and SuperSU root.
Do any of you have a solution to this problem?
Would this be because I haven't flashed Public_data.zip and Full_HW_data.zip?
And will this problem fix if I completely install the MHA-L29C185B172's firmware?
SeanPHTRPW said:
Hello,
My device is the Mate 9 (MHA-L29C185B110) and I seem to have a problem with the camera.
When pressing the button to take a photo, the camera app restarts itself. I try again, but didn't work, to no avail.
I also tried to record a video. It seems to work, but the camera freezes but it's still counting, otherwise recording.
I have just recently flashed a custom recovery img (TWRP), the boot img on another thread that prevents the device from being automatically encrypted, and SuperSU root.
Do any of you have a solution to this problem?
Would this be because I haven't flashed Public_data.zip and Full_HW_data.zip?
And will this problem fix if I completely install the MHA-L29C185B172's firmware?
Click to expand...
Click to collapse
It could be a problem if you flashed a boot image for a different model. You need boot image for C185B110. It should work without hw and Public zips, but a lot of other things break without flashing those. Updating to C185B172 will fix it.
By the way, which supersu did you use?
If the one from the "Decrypt" thread in Guides you don't need to flash a pre-decrypted boot image, the installer does it for you.
ante0 said:
It could be a problem if you flashed a boot image for a different model. You need boot image for C185B110. It should work without hw and Public zips, but a lot of other things break without flashing those. Updating to C185B172 will fix it.
By the way, which supersu did you use?
If the one from the "Decrypt" thread in Guides you don't need to flash a pre-decrypted boot image, the installer does it for you.
Click to expand...
Click to collapse
As for the SuperSU, I think I took it from the full root guide w/o decrypt img, but obviously I had to use a decrypt img because of stock
SUPERSU-2.79-MATE9-init.d_support
For the boot (No force encryption boot)
This is probably where things went wrong. I flashed the wrong build image.
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
I had to use above link because I couldn't flash SuperSU since I don't have an external sd to extract it from (Since you have to format your data before flashing it)
I couldn't find the hw and public zips for C185B110, so if you have it, a link would be generous.
Would flashing stock boot img for MHA-L29C185B110 fix it?
and what would happen if i flash stock boot.img?
and do you have a decrypt boot.img for C185B110?
Thanks!
SeanPHTRPW said:
As for the SuperSU, I think I took it from the full root guide w/o decrypt img, but obviously I had to use a decrypt img because of stock
SUPERSU-2.79-MATE9-init.d_support
For the boot (No force encryption boot)
This is probably where things went wrong. I flashed the wrong build image.
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
I had to use above link because I couldn't flash SuperSU since I don't have an external sd to extract it from (Since you have to format your data before flashing it)
I couldn't find the hw and public zips for C185B110, so if you have it, a link would be generous.
Would flashing stock boot img for MHA-L29C185B110 fix it?
and what would happen if i flash stock boot.img?
and do you have a decrypt boot.img for C185B110?
Thanks!
Click to expand...
Click to collapse
It would probably fix it yes, but no boot image or hw/public exist for B110 so I'm guessing it shipped with that build.
You'd have to update, using https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
I don't think you can use Firmware Finder as you're probably missing the System Update feature.
Either that one I linked or FunkyHuawei, but Funky cost money to use.
Thanks,
I will try using the link you used.
although it is not clear.
On manual update step A, do you need to download all three?
the base, the OS(windows) and the model?
and where do i put these files?
and on b and c on update zip
do i have to download two update.zip?
for example, C185B110 and C185B172
do i also need to download full ota instead of just ota? fullota is incompatible, says firmware finder on mobile
SeanPHTRPW said:
Thanks,
I will try using the link you used.
although it is not clear.
On manual update step A, do you need to download all three?
the base, the OS(windows) and the model?
and where do i put these files?
and on b and c on update zip
do i have to download two update.zip?
for example, C185B110 and C185B172
do i also need to download full ota instead of just ota? fullota is incompatible, says firmware finder on mobile
Click to expand...
Click to collapse
Yes, download base, os and MHA. Extract all to the same folder. You should only have one folder named HWOTA and the files/folders in that. If it extracts to a folder with the same name as the zips, enter the folders and copy hwota folder then go back one folder and paste/merge so you end up with one folder named HWOTA. Easiest way is putting it directly in C:\hwota\, if your windows version allows it. Else place it on desktop. (long file paths or a path containing spaces might make hwota not function correctly).
You need to download all 3 files (fullota update.zip, hw zip and Public zip), easiest way is using firmware finder to download. Either mobile or the pc version. For pc go to the common base tab and search for your model and then download the build you want including public and HW zips.
You only need to download the fullota update, hw and Public zip of the build you're updating to. If you're on b110 and going to update to B172 you only need to download B172.
Rename the files according to the guide (update.zip, update_all_hw.zip and update_data_public.zip), place them in either hwota/update folder or make a HWOTA folder on your sdcard and put the renamed files there.
When running hwota, select script update folder or sdcard update folder depending on where you put the files. Select same model update.
One last question:
Does it have to be FULLOTA, not just OTA?
I am sharing with you here my version of HuRUpdater 0.4 customized for the Mediapad M5. I am not taking any credit here for HuRUpdater, the original work can be found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279. Please follow the instructions there on how to install it to an SD card. Also unzip the hurupdater zip, and in a sub folder you will find huruupdate-binary and busybox. Place these two files in the same folder on the as card where you have the other zips. Finally run it from custom recovery.
Your boot loader needs to be unlocked.
HuRUpdater can be used to:
Recover the tablet from a soft brick or bootloop. As long as you can install and access TWRP, it should be good to go.
Restore the tablet back to stock after installing a custom ROM.
Install full OTA updates after unlocking the bootloader, since it appears you cannot install OTAs anymore once the bootloader is unlocked.
Revert back to an older version of the ROM (watch out for XLOADER versions though, make sure that match https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241)
When I was trying to install an OTA after unlocking my bootloader and installing a custom ROM, I found out that HuRUpdater doesn't work out of the box for the Mediapad M5, so I made some minor customizations:
HuRUpdater looks for the volume keys when it starts up in order to read user inputs, and if it doesn't find it, it bails out. I removed that check for the volume keys, so the script will now run without requiring any user input.
HuRUPdater brings its own busybox binary, but it uses unzip trying to install it, which doesn't seem to be available on the M5. I changed it to copy it to the destination instead from the same folder as the other zips.
HuRUpdater checks whether the update will lock your bootloader, and then require you to press a volume key to confirm. Since volume keys are not working and this locking is probably undesired, the script will now bail out if it finds that your booloader may become locked.
NOTE: After successful flash you have to factory reset! And this must be done using the stock recovery, not TWRP!
I have only used it successfully on the Mediapad M5, but but there should be no reason why it wouldn't work on other devices on which HuRUpdate fails when looking for volume keys.
First big thanks for your post! I have a blank Mediapad here without anything any system flashed on it. When I flash HuRU it states an error with the following lines in recovery.log:
Code:
mkdir: 'utils': File exists
cp: bad '/external_sd/CMR-W09C432/hurupdate-binary': No such file or directory
chmod: utils/hurupdate-binary: No such file or directory
cp: bad '/external_sd/CMR-W09C432/busybox': No such file or directory
chmod: utils/busybox: No such file or directory
/tmp/updater[261]: unzip: not found
/tmp/updater[261]: /tmp/utils/busybox: not found
Error with update.zip file. See recovery.log for more details
Updater process ended with ERROR: 1
Any idea on how to fix this?
valko8877 said:
First big thanks for your post! I have a blank Mediapad here without anything any system flashed on it. When I flash HuRU it states an error with the following lines in recovery.log:
Code:
mkdir: 'utils': File exists
cp: bad '/external_sd/CMR-W09C432/hurupdate-binary': No such file or directory
chmod: utils/hurupdate-binary: No such file or directory
cp: bad '/external_sd/CMR-W09C432/busybox': No such file or directory
chmod: utils/busybox: No such file or directory
/tmp/updater[261]: unzip: not found
/tmp/updater[261]: /tmp/utils/busybox: not found
Error with update.zip file. See recovery.log for more details
Updater process ended with ERROR: 1
Any idea on how to fix this?
Click to expand...
Click to collapse
Oh, sorry, think you found a bug and I need to update the instructions. Please unzip the hurupdater zip, and in a sub folder you will find huruupdate-binary and busybox. Place these two files in the same folder on the sd card where you have the zips and try again.
konradsa said:
Please unzip the hurupdater zip, and in a sub folder you will find huruupdate-binary and busybox. Place these two files in the same folder on the sd card where you have the zips and try again.
Click to expand...
Click to collapse
Thanks a lot! That worked. It got way too late for me, to come to this idea by my own. Spent several hours to revert to stock firmware and now your version of HuRU seems to to do its work. Currently its flashing Huawei's ZIP files.
valko8877 said:
Thanks a lot! That worked. It got way too late for me, to come to this idea by my own. Spent several hours to revert to stock firmware and now your version of HuRU seems to to do its work. Currently its flashing Huawei's ZIP files.
Click to expand...
Click to collapse
Great, glad it worked for you, I updated the instructions in the first post. The reason I ended up with variant of hurupdater is just like you I found out nothing else works, I was trying to install an OTA.l after unlocking boot loader. When I have some time I will think about how to make this a little more seamless. Let me know if you see any other problems.
konradsa said:
Let me know if you see any other problems.
Click to expand...
Click to collapse
Yeah, so far so good, tablet is now on stock firmware. The flash was successful, after extracting both binaries from your HuRU ZIP to same folder as the other ZIP's including HuRU, flashing the HuRU ZIP itself again and letting it do it's magic. That tool saved me a lot of more hours of working out on how to revert to Stock, while every Huawei way to go and also the Androids way to go have failed. Thanks again! I can also confirm, that the "vanilla" version of HuRU does not work on Mediapad because of the mentioned error of not finding the user input device. Using the specialized Mediapad one instead did it's thing. Thumbs up!
You really saved me!!!! I tried everything before this post... I was about to give up.
Wanted to install multi user function (which has been deleted in the lite version), gone through a series of steps and post including unlocking, rooting, flashing custom bootloader, installing a mask, etc... throughout the way something happened and I got stuck at the TWRP bootloader, nothing worked, everything I tried yielded an error of some kind. This was my salvation! I'll be forever in debt! Tanks a lot!!!!
Hi team.
I am new to customizing ROM/firmware. I downloaded the official rom which is rootable and unlockable with bootload.
The official ROM has two ".bin" files "HLTE202N_1.bin" and "HLTE202N.bin".
Does anyone know which software can open/unzip them? I want to delete preinstalled apps and install my apps into it and finally zip them into ".bin" file and then flash them into the phone? Thanks.
ROM can be downloaded here https://drive.google.com/open?id=1JBzsFrtGtIXLYTPTMA2cc9spp_dxF_WX
Thanks!