I have been trying to figure this out for the past few days and I am stuck. I would like to create a simple updateable zip which I can run after flashing a new rom. The important bits are
Code:
delete("/system/media/audio/ui/camera_click.ogg");
delete("/system/media/audio/ui/camera_focus.ogg");
delete("/system/media/bootanimation.zip");
delete("/system/app/Bubbles.apk");
delete("/system/app/Galaxy4.apk");
delete("/system/app/FireworkWallpaper.apk");
delete("/system/app/LiveWallpapers.apk");
delete("/system/app/LiveWallpapersPicker.apk");
delete("/system/app/MagicSmokeWallpapers.apk");
delete("/system/app/NoiseField.apk");
delete("/system/app/PhaseBeam.apk");
delete("/system/app/VisualizationWallpapers.apk");
First I tried this http://fokke.org/site/content/howto-create-android-updatezip-package
When I went to run it and learned this method is way odd and depricated.
Next I tried this http://forum.xda-developers.com/showthread.php?t=903598 and I get an installation aborted message when I run the zip.
Lastly I tried this http://forum.xda-developers.com/showthread.php?t=966468 and I get the same installation aborted message.
Any ideas?
lethologica said:
I have been trying to figure this out for the past few days and I am stuck. I would like to create a simple updateable zip which I can run after flashing a new rom. The important bits are
Code:
delete("/system/media/audio/ui/camera_click.ogg");
delete("/system/media/audio/ui/camera_focus.ogg");
delete("/system/media/bootanimation.zip");
delete("/system/app/Bubbles.apk");
delete("/system/app/Galaxy4.apk");
delete("/system/app/FireworkWallpaper.apk");
delete("/system/app/LiveWallpapers.apk");
delete("/system/app/LiveWallpapersPicker.apk");
delete("/system/app/MagicSmokeWallpapers.apk");
delete("/system/app/NoiseField.apk");
delete("/system/app/PhaseBeam.apk");
delete("/system/app/VisualizationWallpapers.apk");
First I tried this http://fokke.org/site/content/howto-create-android-updatezip-package
When I went to run it and learned this method is way odd and depricated.
Next I tried this http://forum.xda-developers.com/showthread.php?t=903598 and I get an installation aborted message when I run the zip.
Lastly I tried this http://forum.xda-developers.com/showthread.php?t=966468 and I get the same installation aborted message.
Any ideas?
Click to expand...
Click to collapse
Off the top of my head, I'd have to look later, isn't it "delete_file"?
Perhaps I'm wrong.
But what are you getting in the recovery.log (/tmp/recovery.log).
Also, have you mounted /system before you try to delete the files?
Perhaps post your whole script?
HI
Sorry if i am in the wrong section to post. If I am, please move to a more convenient group.
I made a custom Rom in the android kitchen. Everything went through well, no problems at all. then when I try to install to my phone, it wont install and I get these errors:
One error I got while installing was: Installation Abored: Status 6.
Now I get this error white installing: E:Cant open /sdcard/primou_signed_031613_094637.zip (bad) Installation aborted.
Whats going on because I havent changed/converted any update scripts just added an apk then zip aligned it. The original roms install ok, but my own dont install when everything is set the same.
please help me. THANKS
I can upload my two custom roms for you to have a look to see if you can make sense of it. it is for HTC ONE V gsm.
Just try to unzip it and zip it again using WinRAR or 7Zip
Ace 2 Gt-i8160L LATIN. How to install CM?
When I install CM, don't wok sim-card and not IMEI.
Restore IMEI don't helped.
This is modem or hw problems, i think.
Sorry my english is bad.
...
Replace tee folder in rom zip /system/lib with the one from stock rom
Sent from my GT-I8160 using Tapatalk
1) backup tee folder
2) On build.prop change all GT-I8160L to GT-I8160 (without L)
3) all wipes factory/cache/dalvik
3) Install CM_Xversion
4) Whith roo explorer replace tee folder
Enjoy.
2) also can delete assert :/
4) you can just replace in zip before flashing (just sayin)
Sent from my GT-I8160 using Tapatalk
When to alter ROM
teddytsen said:
2) also can delete assert :/
4) you can just replace in zip before flashing (just sayin)
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Am located in New Zealand, and hence using model i8160L, running stock JB ROM
Am trying to modify / install Maclaw CM KK ROM -- but am having problems
-- it "reads" the ROM and "immediately" (afaik) but aborts installation
-- NO ERROR MESSAGES come up for any indication as to why it's aborting
Am trying to do the following -- appreciate any feedback to correct procedure if I'm making eny errors
(i) omitting any and all references to L in 8160L string -- should I restrict it to any particular lines? -- using Build.Prop Editor
-- the Settings/About Device shows it as an 8160, rather than an 8160L after the Build.Prop changes, but the boot screen still shows it as the 8160L -- but at least I don't get the error message about trying to install ROM on wrong device
(ii) before attempting installation, downloading the latest ROM, unzipping the ROM using 7zip, deleting "tee" folder
-- and pasting tee folder from the stock JB ROM installed on my phone
(iii) re-zipping the ROM using 7zip -- I notice I get a different MD5 to that llsted on the download page
(iv) attempting to flash the modified ROM in Recovery mode, but it aborts
Don't know enough to know if install procedure tries to validate the "to be installed" ROM's MD5 and aborts since it's different from that on the download page
Don't know what purpose of tee folder is -- is it to connect to local carrier?
How about if I try to install "unmodified" ROM (in its unmodified form) and once it's installed, if it does (?), replace the tee folder at that later stage, to check for ability to connect to carrier?
Do I need to unlock the SIM card first --- as that's also something I haven't done
(naturally, I've backed up and able to restore to what I had before attempting the install)
KiwiCool60a said:
Am located in New Zealand, and hence using model i8160L, running stock JB ROM
Am trying to modify / install Maclaw CM KK ROM -- but am having problems
-- it "reads" the ROM and "immediately" (afaik) but aborts installation
-- NO ERROR MESSAGES come up for any indication as to why it's aborting
Am trying to do the following -- appreciate any feedback to correct procedure if I'm making eny errors
(i) omitting any and all references to L in 8160L string -- should I restrict it to any particular lines? -- using Build.Prop Editor
-- the Settings/About Device shows it as an 8160, rather than an 8160L after the Build.Prop changes, but the boot screen still shows it as the 8160L -- but at least I don't get the error message about trying to install ROM on wrong device
(ii) before attempting installation, downloading the latest ROM, unzipping the ROM using 7zip, deleting "tee" folder
-- and pasting tee folder from the stock JB ROM installed on my phone
(iii) re-zipping the ROM using 7zip -- I notice I get a different MD5 to that llsted on the download page
(iv) attempting to flash the modified ROM in Recovery mode, but it aborts
Don't know enough to know if install procedure tries to validate the "to be installed" ROM's MD5 and aborts since it's different from that on the download page
Don't know what purpose of tee folder is -- is it to connect to local carrier?
How about if I try to install "unmodified" ROM (in its unmodified form) and once it's installed, if it does (?), replace the tee folder at that later stage, to check for ability to connect to carrier?
Do I need to unlock the SIM card first --- as that's also something I haven't done
(naturally, I've backed up and able to restore to what I had before attempting the install)
Click to expand...
Click to collapse
md5 sum change probably because you uncompressed and re-compressed file.
no you dont have to unlock carrier.
use total commander and delete first 3 lines in updater-script.(all before mount.. bahblablah) and then compress it, then try.
btw it doesnt show any status errors?
When to alter ROM cont'd
teddytsen said:
md5 sum change probably because you uncompressed and re-compressed file.
no you dont have to unlock carrier.
use total commander and delete first 3 lines in updater-script.(all before mount.. bahblablah) and then compress it, then try.
btw it doesnt show any status errors?
Click to expand...
Click to collapse
MANY MANY thanks for your very prompt reply, and further information
"status errors" -- as a result of ?? -- no status errors evident after rebooting with modfified Build.Prop
had lots of "fun" on my previous efforts with custom ROMs -- played with several on a Huawei G300 I had --
-- but, gee, this is an ongoing learning process -- now to learn about updater script !!!
(only learnt about Total Commander from your post - despite its high rating -- but note others have used other things for "text editing")
(but have discovered some TUTs on xda)
Reading more carefully through the posts I see it may be possible to flash the ROM, and then later, substitute the tee folder supplied in the Maclaw ROM with the stock JB one -- right?
I'll definitely learn more about updater-script, but I'll try to flash the ROM again without modifying the ROM === OK?
KiwiCool60a said:
MANY MANY thanks for your very prompt reply, and further information
"status errors" -- as a result of ?? -- no status errors evident after rebooting with modfified Build.Prop
had lots of "fun" on my previous efforts with custom ROMs -- played with several on a Huawei G300 I had --
-- but, gee, this is an ongoing learning process -- now to learn about updater script !!!
(only learnt about Total Commander from your post - despite its high rating -- but note others have used other things for "text editing")
(but have discovered some TUTs on xda)
Reading more carefully through the posts I see it may be possible to flash the ROM, and then later, substitute the tee folder supplied in the Maclaw ROM with the stock JB one -- right?
I'll definitely learn more about updater-script, but I'll try to flash the ROM again without modifying the ROM === OK?
Click to expand...
Click to collapse
-Dont care about ro.build.model. once assert is deleted you dont have to change it. And its not mandatory.
-I recommended total commander just because its the only root browser i have that shows the assert in 3 lines exactly. Unless es etc. You can also use other editors ^.^
-like when installation is aborted, it says status 7(or 0 etc)
Sent from my GT-I8160 using Tapatalk
Many thanks -- now for the "rest" and time for tee
teddytsen said:
-Dont care about ro.build.model. once assert is deleted you dont have to change it. And its not mandatory.
-I recommended total commander just because its the only root browser i have that shows the assert in 3 lines exactly. Unless es etc. You can also use other editors ^.^
-like when installation is aborted, it says status 7(or 0 etc)
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Many thanks!! KK installed -- that was the "fascinating" thing -- no status errors on previous failed attempt at installation -- nothing
but now it's installed -- with GApps added, and now to "worry" about the rest of it all
unsurprisingly -- if tee does what I think it does -- but I can't find a TUT on that anywhere
-- so currently, I can't connect to my local carrier, so it's currently not a :"phone" as such
even more frustratingly, computer found phone when it was first plugged in, but now seems to have lost it!! time to reboot system
-- and, it's been a while since I used CM but I can't find extsdcard!!
Cm file manager?
Settings-general settings-access mode- root
Sent from my GT-I8160 using Tapatalk
Permissions
teddytsen said:
Cm file manager?
Settings-general settings-access mode- root
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
sorry, not used to that one -- for that matter, I tend to stay away from things affecting the system I don't know
so I'm lost in permissions in different apps -- can't find "paste" in CM file, and can't find RW permissions in ES!!
But you're being exceptionally patient! thanks, heaps
Lot easier than I thought -- and MANY thanks again
KiwiCool60a said:
sorry, not used to that one -- for that matter, I tend to stay away from things affecting the system I don't know
so I'm lost in permissions in different apps -- can't find "paste" in CM file, and can't find RW permissions in ES!!
But you're being exceptionally patient! thanks, heaps
Click to expand...
Click to collapse
Actually, it's a lot easier than I thought -- working phone, with KK installed -- without need to unlock carrier!!
Many thanks for the guidance, patience ....
and, of course, to the ROM developers
Repeated problems with Maclaw KK ROM
KiwiCool60a said:
Actually, it's a lot easier than I thought -- working phone, with KK installed -- without need to unlock carrier!!
Many thanks for the guidance, patience ....
and, of course, to the ROM developers
Click to expand...
Click to collapse
Many thanks for past help with intall procedure -- but have had repeated problems of late -- last installed ROM on March 9th -- could install several versions prior to that date, and use them successfully, but since then have been unable since I repeatedly get "Error searching for networks", and hence cannot connect to carrier, and hence unable to use phone as phone, though other functions seem to work OK, -- any ideas??
I was having problem with flashing cm12.1 zip.
I was getting error "error executing updater binary" in recovery.(Now i flashed it).
How i did it?........
1)I decompressed system.new.dat(which was in the zip) to ext 4...
2) then again decompressed ext4 to output folder(which was the old way to make zips).for more info http://forum.xda-developers.com/and.../how-to-conver-lollipop-dat-files-to-t2978952.
3)then edited updater script using refrence of updater script of mokee zip files(i was able to flash mokee51.1 roms).
voila it flashed successfully.
Now the que is why this happens?Am i the only one who faces this problem.
..God knows how frusted i was due to this.......
dtechgeek said:
I was having problem with flashing cm12.1 zip.
I was getting error "error executing updater binary" in recovery.(Now i flashed it).
How i did it?........
1)I decompressed system.new.dat(which was in the zip) to ext 4...
2) then again decompressed ext4 to output folder(which was the old way to make zips).for more info http://forum.xda-developers.com/and.../how-to-conver-lollipop-dat-files-to-t2978952.
3)then edited updater script using refrence of updater script of mokee zip files(i was able to flash mokee51.1 roms).
voila it flashed successfully.
Now the que is why this happens?Am i the only one who faces this problem.
..God knows how frusted i was due to this.......
Click to expand...
Click to collapse
On what recovery and version was this happened? And thanks for the link you gave, might be i need it in the future, if i have such an issue like yours.
presetz said:
On what recovery and version was this happened? And thanks for the link you gave, might be i need it in the future, if i have such an issue like yours.
Click to expand...
Click to collapse
I tried TWRP 2.8.6.0,philz.cwm....
I am running lineageos-nightly-20170706 on my OnePlus 3 - I've tried to update it using both lineageos-nightly-20170803 and lineageos-nightly-20170810 - both give the same error when TWRP tries to install the file:
assert failed: op3.verify_modem('2017-06-27 21:43:31== "1"
updater process ended with ERROR: 7
Error installing zip file '/data/data/org.lineageos.updater/app_updates/lineage-14.1-20170810-nightly-oneplus3-signed.zip'
I did a full wipe and flash installing this, but I don't want to lose all the config work I've done if I don't have to - so I wanted to try updating this time. Am I doing something wrong or missing something? I download it, then choose Install - it reboots the pphone to TWRP (3.0.4-1), I click Install, then Up a Level so I can find the file in /data/data/org.lineagos.updater/app_updates, select the zip file, and swipe to install it.
Thanks,
Brian
bwgreen9 said:
I am running lineageos-nightly-20170706 on my OnePlus 3 - I've tried to update it using both lineageos-nightly-20170803 and lineageos-nightly-20170810 - both give the same error when TWRP tries to install the file:
assert failed: op3.verify_modem('2017-06-27 21:43:31== "1"
updater process ended with ERROR: 7
Error installing zip file '/data/data/org.lineageos.updater/app_updates/lineage-14.1-20170810-nightly-oneplus3-signed.zip'
I did a full wipe and flash installing this, but I don't want to lose all the config work I've done if I don't have to - so I wanted to try updating this time. Am I doing something wrong or missing something? I download it, then choose Install - it reboots the pphone to TWRP (3.0.4-1), I click Install, then Up a Level so I can find the file in /data/data/org.lineagos.updater/app_updates, select the zip file, and swipe to install it.
Thanks,
Brian
Click to expand...
Click to collapse
Firmware...
I am not an android expert - what do I need, and how do I apply it?
bwgreen9 said:
I am not an android expert - what do I need, and how do I apply it?
Click to expand...
Click to collapse
Well, your firmware is outdated, you need to update it.
This should help you out:
http://lmgtfy.com/?iie=1&q=Oneplus+3+modem+firmware+xda
bwgreen9 said:
I am not an android expert - what do I need, and how do I apply it?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
I flashed this one in recovery 4.1.6 Firmware + Modem, and then i flashed the full zip of the lineage update.