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)
Related
Hello Friends,
With MaZel using much of the services from Aroma Installer, here you go with one more great work from the developer of Aroma - amarullz.
I have provided the link for Aroma File Manager developed by amarullz. This is a file manager that can be used in recovery boot menu. While being in recovery if you want to modify some files, or move some files, no need to boot the phone again. You can do all the operations with the help of Aroma File manager while being in the recovery menu itself.
Along with the file manager, i have attached a configuration file which has the touch calibration done for our device. So you can directly start using it insead of calibrating it again.
How to Use :
Download the attached Aroma File manager and Configuration file to your sdcard.
Put the both the files in the same folder.
Reboot to CWM
Select the Aroma file manager zip via "Install zip from sdcard"
Bingo....You got your file manager opened. You can change the themes and fonts in settings.
Currently the configuration file has calibration done for SGR and themes set to ICS with Roboto font.
Download link for Aroma File manager - Link
Original Source - Aroma File Manager
P.S : I have zipped the config file and uploaded it as .cfg extension is not a valid one for uploading. So please unzip the config file and put it in the same folder where you copy the Aroma File manager zip file.
Great effort and tool buddy...
the day is not far when selva would be called as a RECOGNIZED CONTRIBUTOR
yup buddy. I agree with you. Now we have list of buddies like MJ, ADAM & SELVA..these three are RC & RD as well..
thanks buddy
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
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
Thank's to this forum I have phone with 16gb memory, fastboot , TWRP and rooted - this is really great, thank you!
There is new update for 6039H - - 010 07p ~55Mb the of size, waiting for installation.
1st - where is this the file? Where "System updates" app is hiding it?
2nd - should we check update.zip somehow before flashing or just modify, flash and see results.?
Thank you.
Sent from my 6039H using Tapatalk
Just found where is ota hidden : /data/data/com.tcl.fota/.fotadownload
You need to have "Show hidden files" enabled in file manager to see/find it.
I tried use ota_modifier.sh get error:
ota_modifier.sh update.zip
The provided file is not a zip file!
then:
file update.zip
update.zip: Java Jar file data (zip)
In my system LXLE 14 witch is actually Ubuntu there is "zip" not a "Zip" witch is expected from script. I had to change this - editing script. One letter - big difference for linux.
Flashing update_modified.zip filed...
"/system/bin/app_process32" has unexpected contents.
E: Error executing updater binary in zip .... [path to my modified zip]
Error flasing zip [path]
[edit]
If you see this error reason is - root. Need to be fully unrooted!
Now everything went fine. Flashed thru TWRP, rerooted. Whole process takes quiet of time be patient.
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.