Database Develop

[Q] Unable to flash UOT zip

Hey guys, I've looked around and haven't found any reason why I SHOULD'NT be able to flash a custom theme from the Ultimate Online Kitchen, so I'm posting for suggestions as to why I am getting this error when trying to flash this... here is the error message I keep getting:
Installing update...
E:Error in /sdcard/Flashing/Themes/UOT-08-25-17-41-1.zip
(Status 0)
Installation aborted.
I also tried flashing it from the root of the SD card with the same results.
At the kitchen I am using the Type MTD (default) update binary...
Looking forward to your suggestions, maybe I have my settings wrong in the kitchen

From the how-to page:
WORKAROUND for recovery error (Status 0):
1. Unzip your ROM and find
META-INF/com/google/android/update-binary file
2. Put this file in the UOT zip (overriding UOT's file)
Click to expand...
Click to collapse

I saw that in the How TO section and tried different ways:
1: Just dragging the file (update-binary)to root of the zip
2: Navigating in the zip to where the update-binary is and dropping it in there
3: Unpacking the zip and placing the file in the root of the zip
4: Unpacking the zip and replacing the file in the zip with the one from my rom
They all yield the same results (I'm pullin' my hair out) because the 2nd technique should've worked

did you ever figure out how to make this work?

My bad fellas, I should've posted back that I got this resolved...
I eventually downloaded a fresh copy of my ROM, unzipped the entire thing instead of just dragging out the file I needed.
I then deleted the file I was replacing with the one I got from my ROM and it went fine (after about 10 tries).
I also flashed my recovery to my phone and the amss and the dsp1...
Anyway, now I'm a cookin' fool changing themes every other day

cdzo72 said:
My bad fellas, I should've posted back that I got this resolved...
I eventually downloaded a fresh copy of my ROM, unzipped the entire thing instead of just dragging out the file I needed.
I then deleted the file I was replacing with the one I got from my ROM and it went fine (after about 10 tries).
I also flashed my recovery to my phone and the amss and the dsp1...
Anyway, now I'm a cookin' fool changing themes every other day
Click to expand...
Click to collapse
Hi, I am from CR too
I am trying to do this but no luck
Galaxy S2 i9100
Ice Cream I9100XXLPQ
I have the file but when I try to install it I get the error (Status 0)
I understand this:
WORKAROUND for recovery error (Status 0):
1. Unzip your ROM and find
META-INF/com/google/android/update-binary file ----->> What do they mean to unzip the ROM?? I installed ICS from a .tar.md5 file and it is without folders (opening with Winrar). I also searched in the phone with root explorer and didn't find META-INF....
2. Put this file in the UOT zip (overriding UOT's file)
PV!

mrfmanuel said:
Hi, I am from CR too
I am trying to do this but no luck
Galaxy S2 i9100
Ice Cream I9100XXLPQ
I have the file but when I try to install it I get the error (Status 0)
I understand this:
WORKAROUND for recovery error (Status 0):
1. Unzip your ROM and find
META-INF/com/google/android/update-binary file ----->> What do they mean to unzip the ROM?? I installed ICS from a .tar.md5 file and it is without folders (opening with Winrar). I also searched in the phone with root explorer and didn't find META-INF....
2. Put this file in the UOT zip (overriding UOT's file)
PV!
Click to expand...
Click to collapse
I have a i9100 also and you really don't need the kitchen because there so many themed ROMs out there. If you like send me a private message and will contact you with pointers on getting the most out of your i9100

[Q] Failed Flashing CM9, Tried Several Things, Please Help

Hello All!
I am having an issue trying to flash Cyanogen Mod 9 on my rooted Verizon Galaxy Tab 7 (SCH-I800, the older model).
I downloaded Cyanogen Mod 9 (cm-9.1.0-p1c.zip) and placed it on my SD card. Using GooManager I rebooted into recovery to flash the rom. When I tried to flash it I got an assertion error on the following statement:
assert(getprop("ro.product.device") == "galaxytab7c" || getprop("ro.build.product") == "galaxytab7c" ||
getprop("ro.product.device") == "p1c" || getprop("ro.build.product") == "p1c" ||
getprop("ro.product.device") == "SCH-I800" || getprop("ro.build.product") == "SCH-I800" ||
getprop("ro.product.device") == "SPH-P100" || getprop("ro.build.product") == "SPH-P100" ||
getprop("ro.product.device") == "vzwtab" || getprop("ro.build.product") == "vzwtab");
...
...
To try and outsmart the updater script I disabled asserts using the recovery menu but strangely enough (and probably a good topic for another thread) the assert statement STILL failed. (So much for disabling asserts. )
I figured something must be wrong with disabling the asserts so I decided to try a different approach. I unzipped cm-9.1.0-p1c.zip in a temp folder on my PC and proceeded to edit updater_script using notepad. I removed the entire assert statement and saved the file then re-zipped it up and called it cm-9.1.0-p1c_NOASSERT.zip.
I then copied this new zip file back over to my flash card and rebooted into recovery. The updater script no longer failed on the assert however it just halted without giving me any useful information. Here is the log of the script:
-- Installing: /sdcard/cm-9.1.0-p1c_NOASSERT.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
So here I am. Stuck at this point and I don't know what to do. I tried installing with the original rom. I tried turning off asserts and installing again. I modified the updater script to remove the assert statement but that just pushed the error further down the line (and made it less verbose).
I am 99.9% sure I downloaded the correct rom and that my device is indeed a Verizon (CDMA) Samsung Galaxy Tab 7 model number SCH-I800.
I even checked the /system/build.prop file on my tablet and there was a property called ro.product.device and it was set to SCH-I800.
...
ro.build.tags=test-keys
ro.product.model=SCH-I800
ro.product.brand=samsung
ro.product.name=SCH-I800
ro.product.device=SCH-I800
ro.product.board=s5pc110
...
I am at a loss for what to do next. Can anyone give me advice to point me in the right direction or even better tell me exactly what to do!
Thank you!!
Jan

When editing the zip and updater-script do not re-zip the file. The way I do this on my S2 (will be same for any device) using 7zip is:
- Open zip and drag and drop the updater-script from 7zip onto my PC
- Edit in Notepad++ and save
- Drag updater-script back into 7zip window where it was
- Close 7zip
I've never had to re-zip the file and I edit the ROM zip I'm compiling and using every time to remove and add apps, edit build.prop etc Same principle should apply to any device using CWM zips so hope it helps

AvRS said:
When editing the zip and updater-script do not re-zip the file. The way I do this on my S2 (will be same for any device) using 7zip is:
- Open zip and drag and drop the updater-script from 7zip onto my PC
- Edit in Notepad++ and save
- Drag updater-script back into 7zip window where it was
- Close 7zip
I've never had to re-zip the file and I edit the ROM zip I'm compiling and using every time to remove and add apps, edit build.prop etc Same principle should apply to any device using CWM zips so hope it helps
Click to expand...
Click to collapse
Why do you think it's better to use 7zip and pull the file out, edit it, then put it back in. I don't understand why that would be different that unzipping the whole thing then re-zipping it up. The only thing I can think of as to why your method might work is if there is some kind of checksum or special "tag" in the original zip that gets lost doing it my way.

I just thought of something else.... Could it be that I am having the problem because I am going from the stock setup straight to Cyanogen Mod 9? Do I have to put CM7 on my device first then update to CM9?

AvRS said:
When editing the zip and updater-script do not re-zip the file. The way I do this on my S2 (will be same for any device) using 7zip is:
- Open zip and drag and drop the updater-script from 7zip onto my PC
- Edit in Notepad++ and save
- Drag updater-script back into 7zip window where it was
- Close 7zip
I've never had to re-zip the file and I edit the ROM zip I'm compiling and using every time to remove and add apps, edit build.prop etc Same principle should apply to any device using CWM zips so hope it helps
Click to expand...
Click to collapse
OMG YOUR SUGGESTION WORKED!!! I love you!!! (Don't worry I am a girl. )

Glad to hear it worked
Only reason I think it works is because it's a tried and tested process seriously though I'm not sure but possibly I think re-zipping the file could change the compression or like you say maybe break some checksum or whatever.
Haha like the extra bit
Sent from my GT-I9100 using xda premium

AvRS said:
When editing the zip and updater-script do not re-zip the file. The way I do this on my S2 (will be same for any device) using 7zip is:
- Open zip and drag and drop the updater-script from 7zip onto my PC
- Edit in Notepad++ and save
- Drag updater-script back into 7zip window where it was
- Close 7zip
I've never had to re-zip the file and I edit the ROM zip I'm compiling and using every time to remove and add apps, edit build.prop etc Same principle should apply to any device using CWM zips so hope it helps
Click to expand...
Click to collapse
Opening tru 7zip works on mine too. Thanks much!

Follow up using Mac
MarlX said:
Opening tru 7zip works on mine too. Thanks much!
Click to expand...
Click to collapse
I ran into this same issus. I had to edit using 7-zip (Parrallels VM).
My approach that got me a working CM9 on my SGH-849 T-Mobile (GT-P1000 )was to download/install Heimdall suite for MAC.
Download and extract GB-Stock-Safe-V5. I then downloaded cwm-5-p1.tar. I replaced the zImage in the Subdirectory GB_Stock_Safe_V5 with the cwm zImage and moved the t-mobile modem file and gt-p1000 files to this same GB_Stock_Safe_V5 subdirectory. I then opened terminal and cd'd to this subdirectory.
I ran Heimdall with "heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose"
I had previously loaded the modified CM-9 file and Gapps to my micro sd card. So, when the system rebooted, I could do the factory reset, clear cache, and (advanced) clear Dalvik cache. and install from zip.
All seems to be working. Thanks for the zip file hint -- last piece of the puzzle for me.
Jack

AvRS said:
When editing the zip and updater-script do not re-zip the file. The way I do this on my S2 (will be same for any device) using 7zip is:
- Open zip and drag and drop the updater-script from 7zip onto my PC
- Edit in Notepad++ and save
- Drag updater-script back into 7zip window where it was
- Close 7zip
I've never had to re-zip the file and I edit the ROM zip I'm compiling and using every time to remove and add apps, edit build.prop etc Same principle should apply to any device using CWM zips so hope it helps
Click to expand...
Click to collapse
WORKED PERFECTLY on my Sprint Samsung Galaxy Tab SPH-P100!
Was getting the status 7 error after removing the ASSERT portion of the script and then Installation Aborted error with no explanation.
I download the trial version of WinZip for OSX, pulled out the updater-script, edited the file in VIM, and dragged it back into the .zip file.
So awesome! (Not a girl and yes I clicked the thanks button)

Assert lines in updater script code?
AvRS said:
When editing the zip and updater-script do not re-zip the file. The way I do this on my S2 (will be same for any device) using 7zip is:
- Open zip and drag and drop the updater-script from 7zip onto my PC
- Edit in Notepad++ and save
- Drag updater-script back into 7zip window where it was
- Close 7zip
I've never had to re-zip the file and I edit the ROM zip I'm compiling and using every time to remove and add apps, edit build.prop etc Same principle should apply to any device using CWM zips so hope it helps
Click to expand...
Click to collapse
Total n00b question here, but which lines are the assert lines? I tried looking for the obvious "assert lines here", but nothing so helpful. Any help would be appreciated, GB is now so old as to be about unusable these days.
edit: I was in the wrong file, but now I can't get the edited updater back into the folder. I shall persevere, though!

I managed to edit the update script, but now after flashing, the tab just hangs out the Samsung screen. Any suggestions?
edit: poking around some more, I found I had deleted too many lines. Oops!

[Q] CWM Recovery: patching backups; updating CM

Some simple (I hope) questions. Let's say I do a full CWM backup and copy the complete backup directory to my desktop. If I now want to change something inside this backup can I simply change the relevant .tar.a file(s), write their new checksums into nandroid.md5, copy everything back to the sd card and expect the whole thing to work?
No 2: I have just let the HD+ update itself to cm-10.1.3-ovation (final) and all went swimmingly. However, I saw that the update is not done incrementally, instead the whole zip is downloaded and the /system tree simply overwritten with its contents. I had put some bits and pieces into /system/app and /system/bin and modified a few files inside of /system, all of which changes were of course gone. So a better update strategy might be to download any new version from the CM website to a desktop machine, patch the .zip file there and then have CWM install it. Can CWM install such an update file like any other .zip or is the update.zip route the correct way?
Or perhaps the best way to update in such a scenario is to download the .zip, sync it with an existing CWM backup (as in the first question) and restore the backup?!

If you get the md5 sum right editing the tar should work.
You can edit the downloaded zip before you flash it and it will still install. But editing after install is about the same amount of work.
What I used to do on the Nook Color was to modify the gapps zip to add the /system changes I wanted and then reflashed the gapps every time I flashed a new ROM. That way gapps were refreshed and the new changes were inserted in /system. Or, you could make your own zip to flash only your changes. The easiest way to make one is to edit the gapps zip to put your changes in and then delete the gapps files from the zip.
Do these zip changes with archive software without totally unzipping and rezipping.
Edit: Since some of my changes were modifications to build.prop, I developed a script to edit the new ROM's build.prop on the fly as part of the zip. That way build date, etc stayed right. If you want, I can use PM to send you a copy of my old edited gapps for you to study. However, since you are on CM10.1 stable, you will probably not be updating again.
Sent from my Nook HD+ running CM10.1 on emmc.

> If you get the md5 sum right editing the tar should work.
Okay, thanks for the confirmation.
> You can edit the downloaded zip before you flash it and it will still install.
But how do I trigger that install, once in CWM? That was my 2nd question.
> But editing after install is about the same amount of work.
Not in my case as I have a) no MTP and b) can easily auto-sync huge directory trees with a powerful command line tool.
I think the best way forward is to ignore the installing of new install .zips via CWM, however this is done. Instead I'll produce a nandroid-compatible backup directory and "restore" that.
Thanks again for your help.

TooMuchSloeGin said:
> If you get the md5 sum right editing the tar should work.
Okay, thanks for the confirmation.
> You can edit the downloaded zip before you flash it and it will still install.
But how do I trigger that install, once in CWM? That was my 2nd question.
> But editing after install is about the same amount of work.
Not in my case as I have a) no MTP and b) can easily auto-sync huge directory trees with a powerful command line tool.
I think the best way forward is to ignore the installing of new install .zips via CWM, however this is done. Instead I'll produce a nandroid-compatible backup directory and "restore" that.
Thanks again for your help.
Click to expand...
Click to collapse
You don't trigger it, you manually boot to CWM and manually install it. Go to install zip from SD and choose where you put it.
And by editing after install, I meant editing /system once it is installed on the Nook.
Sent from my Nook HD+ running CM10.1 on emmc.

Error status 7

Hello,
I currently have Tsunami X 5.6 android 4.2.2.
I want to update to Kitkat roms but I cant.
I get "status 7" error while trying to install.
I understood that it's because I have an old CWM recovery (6.0.3.2).
How do I update it?
Sorry for the n00b question..

Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing called “asserts”.
How To Fix Statue error:
DO A NANDROID BACKUP if you haven't done so already just in case...
1. Copy the ROM zip file to your computer and extract it using your favorite unzipping software.
2. Once unzipped, browse to the META-INF/com/ google/android directory. You will find two files called “update-binary” and “updater-script”.
3. Rename “updater-script” to “updater-script.txt” and open with your favorite text file editor.
4. Get rid of the line starting with “assert” to next semi-colon. Usually this is the first line or one of the first lines at the top of the text file.
5. Save file.
6. Rename “updater-script.txt” back to “updater-script”.
7. Rezip all the files you’ve unzipped.
8. Copy the new, edited zip file to your phone.
9. Try re-installing ROM, now it should install fine without Status 7 error.

-MaoR- said:
Hello,
I currently have Tsunami X 5.6 android 4.2.2.
I want to update to Kitkat roms but I cant.
I get "status 7" error while trying to install.
I understood that it's because I have an old CWM recovery (6.0.3.2).
How do I update it?
Sorry for the n00b question..
Click to expand...
Click to collapse
If the previous answer is too complicated for you, just flash CM10.2 that will do proper partition for the latest ROMs and give you updated CWM recovery with which you can flash any KK rom. Just reboot once intonthe OS, then back to recovery and flash a KK rom. Don't forget to manually wipe /system before installing KK.
You will need to flash zip twice, as first time it will disolay warning of repartition and abbort with status 7. By next attempt it will work flawless.

pryerlee said:
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing called “asserts”.
How To Fix Ststue error:
DO A NANDROID BACKUP if you haven't done so already just in case...
1. Copy the ROM zip file to your computer and extract it using your favorite unzipping software.
2. Once unzipped, browse to the META-INF/com/ google/android directory. You will find two files called “update-binary” and “updater-script”.
3. Rename “updater-script” to “updater-script.txt” and open with your favorite text file editor.
4. Get rid of the line starting with “assert” to next semi-colon. Usually this is the first line or one of the first lines at the top of the text file.
5. Save file.
6. Rename “updater-script.txt” back to “updater-script”.
7. Rezip all the files you’ve unzipped.
8. Copy the new, edited zip file to your phone.
9. Try re-installing ROM, now it should install fine without Status 7 error.
Click to expand...
Click to collapse
tetakpatak said:
If the previous answer is too complicated for you, just flash CM10.2 that will do proper partition for the latest ROMs and give you updated CWM recovery with which you can flash any KK rom. Just reboot once intonthe OS, then back to recovery and flash a KK rom. Don't forget to manually wipe /system before installing KK.
You will need to flash zip twice, as first time it will disolay warning of repartition and abbort with status 7. By next attempt it will work flawless.
Click to expand...
Click to collapse
Thanks guys.
I actually did flash CM 10.2 just before even seeing the your comments.
It worked great and now I actually think on staying with this ROM lol..
It's very clean and nice.
Thanks again!

Samung Galaxy Tab S2 T819 Bootloader T819xxu2brb2

Hey,
i cant install LineageOS, cuz when im in TWRP it says the Package i tried to install is only for other Bootloader versions
my Version is T819xxu2brb2

Obstkartoffel said:
Hey,
i cant install LineageOS, cuz when im in TWRP it says the Package i tried to install is only for other Bootloader versions
my Version is T819xxu2brb2
Click to expand...
Click to collapse
Until officially fixed:
Open the newest version, like lineage-15.1-20180313_142801-UNOFFICIAL-gts210velte.zip
Go to: \META-INF\com\google\android\ and there extract updater-script
Open with Notepad++. Starting on line 2 you can see all supported loaders. Modify one of them to yours. Save and move back to the zip file overwriting the current file.
DONE.

emuandco said:
Until officially fixed:
Open the newest version, like lineage-15.1-20180313_142801-UNOFFICIAL-gts210velte.zip
Go to: \META-INF\com\google\android\ and there extract updater-script
Open with Notepad++. Starting on line 2 you can see all supported loaders. Modify one of them to yours. Save and move back to the zip file overwriting the current file.
DONE.
Click to expand...
Click to collapse
Im always getting Error 7.. tried to wipe data, dalvik and cache.. nothing works.. some tips?
E: found the issue, forgot to change getprop, just changed the other bootloader infos... *facepalm*