Convert updater-script to make it support lower version CWM and TWRP - Android General

I have build a tool that will convert updater script to support CWM version below 5 and TWRP version below 3. If you go to install latest custom ROMs like CM 13 or 12 with CWM version below 5 or TWRP version below 3 you will get an error with status 7 because they do not support new updater-script which is placed in "META-INF\com\google\android" location in your flashable zip file. There is only two way to fix this problem is by converting script or upgrading recovery. If there is no latest recovery for device then you have to convert the updater-script.
Tool is developed in javascript language with html user interface. So you just need html5 supported browser(Firefox, Chrome etc) to run this tool.
To use this tool offline download the zip file attached below and extract. In extracted folder select index.html file and open with browser. Now click browse button there and select your updater-script that you want to convert. Immediately browser will save modified updater-script file or will ask you to save. Chrome browser will automatically add .txt extension with the modified file.So you have to manually remove that. Recomended firefox
To use this tool online without downloading just visit http://minify.cf/usc.
***************************************************If you get status (6) error *******************************************
This error happens when your update-binary does not support modified updater-script. So use update-binary linked in inside the tool. This will work 100% sure.

Related

[GUIDE] Creating Rom Update.zip

Hello Guys,This is an updated guide for creating an update.zip for your rom.I know that there are a few guides out there but i think my guide is a bit simpler and straight forward.
Step 1:
Download AutoUpdateCreator_V1.1
Step 2:Extract file and click on "CreateUpdateZip.exe"
Step 3: You can either drag your created zip file or press ENTER (If you did not compress your rom yet)
Step 4:Now drag & drop your ROM Folder in the program
**NOTE** Structure of ROM folder should be as follows:
ROM FOLDER(Containing)
---System
---Data
Note: If you get an error it means that your ROM Structure is incorrect!!)
Step 5:Now that everything is done,zip is signed go to GENERATED ZIPS in autoupdatecreator folder.
Step 6:Copy your update-script in your generated zip file at /META-INF/COM/GOOGLE/ANDROID/
(Do NOT replace Update-binary file!)
Other Notes:
(Update Script must be created,there are templates available)
(Editing Update Script with normal windows text editor will cause Status 6 Error)
(Adding an incorrect or non existing file in update-script will also give you a Status 6 Error)
Cheers
Thanx for work.means now i can convert .tar files into zip?and can flash from cell
not working in last cwm
switch to Edify error
Hey man, i guess you can help me. I have a samsung double time and it can't be flashed via odin, my wifi and all connections, except mobile data are not working. So i have the .tar firmware extracted. Is there any way to create an update.zip file from this firmware.
Stavr0s91i said:
Hello Guys,This is an updated guide for creating an update.zip for your rom.I know that there are a few guides out there but i think my guide is a bit simpler and straight forward.
Step 1:
Download AutoUpdateCreator_V1.1
Step 2:Extract file and click on "CreateUpdateZip.exe"
Step 3: You can either drag your created zip file or press ENTER (If you did not compress your rom yet)
Step 4:Now drag & drop your ROM Folder in the program
**NOTE** Structure of ROM folder should be as follows:
ROM FOLDER(Containing)
---System
---Data
Note: If you get an error it means that your ROM Structure is incorrect!!)
Step 5:Now that everything is done,zip is signed go to GENERATED ZIPS in autoupdatecreator folder.
Step 6:Copy your update-script in your generated zip file at /META-INF/COM/GOOGLE/ANDROID/
(Do NOT replace Update-binary file!)
Other Notes:
(Update Script must be created,there are templates available)
(Editing Update Script with normal windows text editor will cause Status 6 Error)
(Adding an incorrect or non existing file in update-script will also give you a Status 6 Error)
Cheers
Click to expand...
Click to collapse
The Download link is offline

[Q] Can't get a zip signed with SignAPK

Hello,
since several days now I try to sign a repacked update.zip to update with the normal recovery menu (not CWM) for my AM8726-MX Teclast tablet with Android 4.1.1 (ext4 filesystem). To track down the error I took a simple zip to root the tablet that works without problems from here: http://forum.xda-developers.com/showpost.php?p=41759110&postcount=36
The comment in the zipfile says: "signed by SignApk"
I unpacked the zip, deleted the CERT and MANIFEST files in the META-INF directory and packed the files into a new zipfile (WinRAR, 7-Zip, zip under Linux etc.)
I used signapk.jar with testkeys to sign the the new zipfile. The file has no zipfile comment. When I try flash the zip to my tablet in recovery mode ("apply update from EXT") it just says "Verifying update package..." and then "Installation aborted.". When I unpack the working signed zipfile and the one I repacked and signed myself and compare the single files they are all IDENTICAL. So far I tried:
- Different signapk.jar downloads (they seem all the same)
- Different java version (1.6, 1.7, Linux and Windows)
- Different Linux versions (32bit and 64bit)
- Different keys
- Different compression programs (WinRAR, 7-Zip, zip under linux)
I am running out of ideas so is there anybody who can give me a hint what is going wrong?
Thanks, HellG.
Darkstar2000 said:
Hello,
since several days now I try to sign a repacked update.zip to update with the normal recovery menu (not CWM) for my AM8726-MX Teclast tablet with Android 4.1.1 (ext4 filesystem). To track down the error I took a simple zip to root the tablet that works without problems from here: http://forum.xda-developers.com/showpost.php?p=41759110&postcount=36
The comment in the zipfile says: "signed by SignApk"
I unpacked the zip, deleted the CERT and MANIFEST files in the META-INF directory and packed the files into a new zipfile (WinRAR, 7-Zip, zip under Linux etc.)
I used signapk.jar with testkeys to sign the the new zipfile. The file has no zipfile comment. When I try flash the zip to my tablet in recovery mode ("apply update from EXT") it just says "Verifying update package..." and then "Installation aborted.". When I unpack the working signed zipfile and the one I repacked and signed myself and compare the single files they are all IDENTICAL. So far I tried:
- Different signapk.jar downloads (they seem all the same)
- Different java version (1.6, 1.7, Linux and Windows)
- Different Linux versions (32bit and 64bit)
- Different keys
- Different compression programs (WinRAR, 7-Zip, zip under linux)
I am running out of ideas so is there anybody who can give me a hint what is going wrong?
Thanks, HellG.
Click to expand...
Click to collapse
I found a newer version of the signapk.jar that works. I searched for the zip comment "signed by SignApk" and found it in the newer version on git and here: http://www.android-hilfe.de/attachm...d1338829904-meine-rom-update-zip-packager.zip
Darkstar2000 said:
I found a newer version of the signapk.jar that works. I searched for the zip comment "signed by SignApk" and found it in the newer version on git and here: http://www.android-hilfe.de/attachm...d1338829904-meine-rom-update-zip-packager.zip
Click to expand...
Click to collapse
What command did you use to get the comment? I'm using those files and I still don't get it, and further, trying to unzip it in TWRP commandline gives me "unzip: zip flags 1 and 8 are not supported" where an unsigned zip does not..
I have the same problem

[GUIDE] How to flash OTA packages through TWRP for Letv le1 pro X800

For Letv le1 pro if you have TWRP installed you won't be able to update via OTA automatically. It will fail and it is a real pain to always download the full rom package and flash. Moreover an OTA update notification will pop up continuously which is really annoying.
Here I will tell how to update via TWRP by doing a small modification to the OTA package.
Things Needed:
Winrar
Notepad ++
Steps
1. At first download the OTA package but don't reboot to install it
2. Copy the update zip from the ota update folder of you phone to your pc
3. Open the update.zip file but don't extract it. Just open it via winrar
4. In winrar window navigate to META-INF>com>google>android>updater-script
5. Double click on updater script and open it with Notepad ++
6. In Notepad++ window delete everything from row 8 up to the above line of "# radio update task" like the image sample below
https://drive.google.com/file/d/0B-mgR2LkvkEtQjVSU0tsNWdXRjQ/view?usp=sharing
7. Save it and close winrar
8. Copy this zip file to your phone and you will able to flash it via TWRP.
thank u for this helpful tutorial

Inazuma ROM for T-Mobile users

So I want to start off by saying that I'm not stealing the developers work. He just seems to not fix the issue related in the t-mobile aroma installer for his 2.8 version rom.
So the error is "Syntax error aroma-config on line 143 col 8"
Go here to download his rom > Thread
Download the one for tmobile 2.8.
After you have downloaded it, extract the zip file and go to "\Inzuma 2.8 tmobile\META-INF\com\google\android"
You are going to replace the file "aroma-config"
Download the fixed aroma installer.zip file from the attachements
Unzip the .zip file, copy and replace the aroma-installer file to the "META-INF\com\google\android" directory
Lastly once you have replaced the file, simply zip all the folders and flash it using your recovery
and that's it. easy fix, the error was caused by a simple code error (which I fixed real quick)

[FIRMWARE] Modified Stock rom ULEFONE NOTE 9P

ULEFONE NOTE 9P, Stock rom is not real bloated, but just a little.
From Build
GQ3092SH1-HC-M629-ULEFONE-20200703_V05
Patch for the newer build (20200904-V07) is ready for sharing also.
****NOTE TESTING HAS NOT BEEN DONE ON MIXING NEW SYSTEM.IMG ON OLD VENDOR*****
****RECOMMEND DOING FULL UPDATE OR DOWNGRADE BEFORE FLASHING MODIFIED SYSTEMS****
Stock roms are published on ULEFONE gdrive.
https://drive.google.com/drive/folders/1Bq16pmRMaFEVT_xZilWhhdzTzk9fojV8
I removed the adupus/FOTA apps, child mode, simple_mode, mfg customization to chrome, verizon provider remote sim lock app.
Added adaway hosts file for ad-blocking in browser.
Flashed back to phone in same way as flashing GSI rom.
adb reboot fastboot (fastbootd, not bootloader)
fastboot flash system modified-system.img ( fastboot.exe on pc needs to be from July 202 or newer)
when flashing is done, from menu on phone screen select boot to recovery.
perform factory reset and reboot.
https://www.androidfilehost.com/?w=files&flid=318156
In case you are wondering , how I made changes. I will tell you.
I used SuperR-Kitchen script/ tool
credits to @SuperR.
Start a new project. Add the stock firmware. Needs to be as a zip. So extract the embed-ed *.rar file downloaded from Ulefone. Re-zip just the contents of the final folder. In other words, the zip needs to be the files, not the files inside a folder, inside other folder.
The kitchen will ask if you want to extract the vendor and product images and use them in you rom. I did not make changes to those partitions, so did not extract or include them.
When unpacking is completed. You can browse the extracted system folder.
The attached files have an .txt extension in order to upload them here. But in the kitchen tool you need to remove the extension.
Code:
Add "host" file to /system/system/etc in your extracted rom folder and replace host file that is already there.
Add "bloat_custom" to the kitchen folder "super_r/tools/root/
run #6 debloat menu then #2custom debloat option from kitchen #8 rom tools menu
run deodex option from #8 rom tools
When edits are done. Use #8 rom tools , #7 build menu, #2 build etx4 img
select system, then sparse, system.img
Keep permission type as raw_image
That's all. Use caution when adding additional programs you want removed.
Hi. On Ulefone Gdrive, there are both android 10 and 11 rom files. but it says upgrading from 10 to 11 is 'forbidden'. Is there any way to bypass this restriction?
Edit for those who are wondering: Ulefone has removed the restriction and it can be upgraded to android 11 without any issue. You do lose your data during the process, though.

Categories

Resources