Related
hi i followed this guide posted here http://forum.xda-developers.com/showthread.php?t=1064074
but i dont understand the script part i downloaded the cm7 rom and opened the script in that with note pad and changed it to the one from the guide but when i install the rom i get
"E:Syntac error in update-script"
Installation aborted.
so can someone tell me what im doing wrong
sorry if its in the wrong forum but i thought since its x10 development then i should ask here mods feel free to delete
and i know im going to get people saying i shouldn't try this unless i know what im doing but i have a spare x10 so just wanna give it a try
thanks for any help
rls190687 said:
hi i followed this guide posted here http://forum.xda-developers.com/showthread.php?t=1064074
but i dont understand the script part i downloaded the cm7 rom and opened the script in that with note pad and changed it to the one from the guide but when i install the rom i get
"E:Syntac error in update-script"
Installation aborted.
so can someone tell me what im doing wrong
sorry if its in the wrong forum but i thought since its x10 development then i should ask here mods feel free to delete
and i know im going to get people saying i shouldn't try this unless i know what im doing but i have a spare x10 so just wanna give it a try
thanks for any help
Click to expand...
Click to collapse
How come you didn't post it there instead of creating an entirely new thread
Sent from my X10project using XDA App
can u post the contents of the update-script here?
also are u using amend or edify syntax?
rls190687 said:
hi i followed this guide posted here http://forum.xda-developers.com/showthread.php?t=1064074
but i dont understand the script part i downloaded the cm7 rom and opened the script in that with note pad and changed it to the one from the guide but when i install the rom i get
"E:Syntac error in update-script"
Installation aborted.
so can someone tell me what im doing wrong
sorry if its in the wrong forum but i thought since its x10 development then i should ask here mods feel free to delete
and i know im going to get people saying i shouldn't try this unless i know what im doing but i have a spare x10 so just wanna give it a try
thanks for any help
Click to expand...
Click to collapse
The Tutorial is for MIUI 2.2 so why you use it on CM 7 (2.3)?
DooMLoRD said:
can u post the contents of the update-script here?
also are u using amend or edify syntax?
Click to expand...
Click to collapse
update-script (7.17 KB) http://www.multiupload.com/KF64P2PXIR
updater-script (15.91 KB) http://www.multiupload.com/PSIF0CNN6I
update-binary (254.04 KB) http://www.multiupload.com/C4UNKXBW32
these are the files from the 2 roms
the 1st on is js script
Delete updater-script and update-binary
rdannar said:
make sure you delet updater and update binary from folder and replace with update-script
Click to expand...
Click to collapse
realunited123 said:
Delete updater-script and update-binary
Click to expand...
Click to collapse
tryed that followed the guide
the 2 roms im trying to mix are
cm7 js rom
and
RCMixS_v1.1_++_CM7Hboot
http://forum.xda-developers.com/showthread.php?t=988570
its probly not ganna work but 4t id give it a try
rls190687 said:
tryed that followed the guide
the 2 roms im trying to mix are
cm7 js rom
and
RCMixS_v1.1_++_CM7Hboot
http://forum.xda-developers.com/showthread.php?t=988570
its probly not ganna work but 4t id give it a try
Click to expand...
Click to collapse
Sense! Its probably not going to boot with that tutorial. Better to try with an AOSP build.
rls190687 said:
update-script (7.17 KB) http://www.multiupload.com/KF64P2PXIR
updater-script (15.91 KB) http://www.multiupload.com/PSIF0CNN6I
update-binary (254.04 KB) http://www.multiupload.com/C4UNKXBW32
these are the files from the 2 roms
the 1st on is js script
Click to expand...
Click to collapse
u need only amend script (update-script)
here is the modified one:
http://dl.dropbox.com/u/8691868/test/update-script
please test it...
also u are certain of the following things:
1) toolbox binary is copied to /system/bin
2) busybox binary is copied to to /system/bin or /system/xbin
3) iwmulticall binary is copied to to /system/xbin
DooMLoRD said:
u need only amend script (update-script)
here is the modified one:
http://dl.dropbox.com/u/8691868/test/update-script
please test it...
also u are certain of the following things:
1) toolbox binary is copied to /system/bin
2) busybox binary is copied to to /system/bin or /system/xbin
3) iwmulticall2 binary is copied to to /system/xbin
Click to expand...
Click to collapse
thanks ill test it now
the files are there in the right folders
iwmulticall2 is just called iwmulticall
tho
DooMLoRD said:
u need only amend script (update-script)
here is the modified one:
http://dl.dropbox.com/u/8691868/test/update-script
please test it...
also u are certain of the following things:
1) toolbox binary is copied to /system/bin
2) busybox binary is copied to to /system/bin or /system/xbin
3) iwmulticall2 binary is copied to to /system/xbin
Click to expand...
Click to collapse
thanks i tested it
i get
e:cant symlink /system/bin/reboot
e:failure at line 29:
symlink toolbox system:bin/reboot
i checked the files and the reboot file is in the bin folder
rls190687 said:
thanks i tested it
i get
e:cant symlink /system/bin/reboot
e:failure at line 29:
symlink toolbox system:bin/reboot
i checked the files and the reboot file is in the bin folder
Click to expand...
Click to collapse
well then u have to manually check every file of the update.zip in /system/bin & /system/xbin to verify that there are no files with same name as the new symbolic links that are being created...
View attachment META-INF.rar
here is one to compare and remember to use notepad++ to edit, not regular notepad
if you get a can't symlink error
that means the file is still in the folder
when that happens you can do one of two things.. on delete the line from update script
or two... the one I prefer... delete the file from the actuall rom folder
ex.. cannot symlink ifconfig
I would go to bin and delete ifconfig
another tip is once the rom starts installing you will want to install another rom that is working... the farther you get in the installation the better the chances are you messed up it going into recovery... then you can be sure that after the error you reboot into recovery.. this has saved me many times of having to reflash the whole bb with flashtool wich takes a lot longer than a recovery restore
Does somebody know if Touchwiz 4 will work on the Ace?
http://forum.xda-developers.com/showthread.php?t=1077641
Hope so!
Sent from my GT-S5830 using XDA Premium App
dude i am ready to take risk but how to install
boot into recovery and installthe .zip
wont't work its a clockworkmod installation package...
Yeah thought so
Sent from my GT-S5830 using XDA Premium App
kills999 said:
wont't work its a clockworkmod installation package...
Click to expand...
Click to collapse
just replace file update-binary from file for root gingerbread upd_1.zip and it will work....
ingbrzy said:
just replace file update-binary from file for root gingerbread upd_1.zip and it will work....
Click to expand...
Click to collapse
can you please post the file?
ingbrzy said:
just replace file update-binary from file for root gingerbread upd_1.zip and it will work....
Click to expand...
Click to collapse
dude can u send me the link
Here extract update-binary with winrar and replace... I didnt test it... it will just allow install zip file with touchwiz without clockwork...
but file with touchwiz 4 is for 240dpi and SGA has 160dpi... So I am not sure if it will work properly...
so we will need some voluntary testers
so we will need some voluntary testers
dude i am ready just give me the files.....
Try it... file with replaced update-binary is HERE
reboot to recovery mode and apply .zip file...
I didnt try, so good luck...
ingbrzy said:
Try it... file with replaced update-binary is HERE
reboot to recovery mode and apply .zip file...
I didnt try, so good luck...
Click to expand...
Click to collapse
waiting for results
You wanted it!
Sent from my GT-S5830 using XDA Premium App
ingbrzy said:
Try it... file with replaced update-binary is HERE...
Click to expand...
Click to collapse
instalation aborted...
error in /tmp/sideload/package.zip (status 0)
during installation writes... TouchWiz4 for Tab
cult007 said:
instalation aborted...
error in /tmp/sideload/package.zip (status 0)
during installation writes... TouchWiz4 for Tab
Click to expand...
Click to collapse
Try again with attached files....
182dpi try first....
if it will not install automatically at recovery mode, you can add files manually with root explorer to the folder:
system / app /
system / lib /
sorry no success... i copied files with rootexplorer... wiped twlauncher's and dalvik's cache... set the rights
...there is just blank screen and after a minute FC
cult007 said:
sorry no success... i copied files with rootexplorer... wiped twlauncher's and dalvik's cache... set the rights
...there is just blank screen and after a minute FC
Click to expand...
Click to collapse
So, now we know TW4 is not working on SGA...
possible that the problem is here...
[tutorial] manually moving apps to /system/app
Requirements:
- Rooted SGA
- File Explorer with Root permission (i'm using File Expert)
NOTE: I was only successful in moving apps/games without 'lib' linked to them
Click to expand...
Click to collapse
Hi guys, i created my first own rom but while flashing it with TWRP 2.5 i get error "Error executing update binary in the zip"
So is there any solution?
First see you are properly rooted by using root checker.
Also it may be the problem of TWRP . Try flashing it through cwm.
Sent from my Micromax A116 using xda app-developers app
---------- Post added at 04:28 AM ---------- Previous post was at 04:26 AM ----------
I faced this problem twice with a particular rom using twrp. I used cwm and it worked fine.
Sent from my Micromax A116 using xda app-developers app
---------- Post added at 04:44 AM ---------- Previous post was at 04:28 AM ----------
Try downgrading the twrp version to 2.3
Sent from my Micromax A116 using xda app-developers app
princechandela said:
Hi guys, i created my first own rom but while flashing it with TWRP 2.5 i get error "Error executing update binary in the zip"
So is there any solution?
Click to expand...
Click to collapse
In between of updater script try to print some texts at various places to identify the reason and then you can work to resolve the error. It will give you a hint of the problem Happy porting.
No!
I think you are not understanding my problem. My problem is when I create stock ROM from kitchen and flash it I get error as I mentioned in first post.
princechandela said:
I think you are not understanding my problem. My problem is when I create stock ROM from kitchen and flash it I get error as I mentioned in first post.
Click to expand...
Click to collapse
i understood , that is the reason i suggested.
rajneeshk said:
i understood , that is the reason i suggested.
Click to expand...
Click to collapse
OK I got your point now and I found the error the error at the beginning of the script as soon as script starts trap shows update-binary error. Now what?
princechandela said:
OK I got your point now and I found the error the error at the beginning of the script as soon as script starts trap shows update-binary error. Now what?
Click to expand...
Click to collapse
Please share your updater script.
Sent from my Micromax A116i using XDA Premium 4 mobile app
rajneeshk said:
Please share your updater script.
Sent from my Micromax A116i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
here is the script :
princechandela said:
here is the script :
Click to expand...
Click to collapse
1. I hope you only used notepad++ or editplus to modify updater script and build.prop ( notepad will corrupt these files)
2. Try replacing your META-INF folder with the ROM you were able to flash succesfully on your device ( do modifications as per your need in updater script)
3. please ensure files like marked in green color i.e. symlink("dumpstate", are present in system\bin folder
4. please ensure files like marked in red color i.e. symlink("toolbox", "/system/bin/restorecon"); are not present in their respective locations.
5. all files written under set_perm or set_perm_recursive should be present in their respective locations.
6. please insert ui_print("line number x ") after each line so that you get to know which line has caused the error.
Hope, i am clear
rajneeshk said:
1. I hope you only used notepad++ or editplus to modify updater script and build.prop ( notepad will corrupt these files)
2. Try replacing your META-INF folder with the ROM you were able to flash succesfully on your device ( do modifications as per your need in updater script)
3. please ensure files like marked in green color i.e. symlink("dumpstate", are present in system\bin folder
4. please ensure files like marked in red color i.e. symlink("toolbox", "/system/bin/restorecon"); are not present in their respective locations.
5. all files written under set_perm or set_perm_recursive should be present in their respective locations.
6. please insert ui_print("line number x ") after each line so that you get to know which line has caused the error.
Hope, i am clear
Click to expand...
Click to collapse
i got your point one quest are my location right in format command and mount command?
EDIT:
i didn't your step 6 and i replaced the update binary file and now my rom is flashing correctly but can you tell me what was the error with update-binary file? it was the file created by kitchen.
script even don't start executing and before it i get "error executing update-binary" any help?
princechandela said:
script even don't start executing and before it i get "error executing update-binary" any help?
Click to expand...
Click to collapse
have you taken care notepad++ and meta-inf folder?
rajneeshk said:
have you taken care notepad++ and meta-inf folder?
Click to expand...
Click to collapse
I got success by using option 2 in kitchen(lazy mode) the the zip is now flashing but now my question is should i edit update script after zip is created and signed?
princechandela said:
I got success by using option 2 in kitchen(lazy mode) the the zip is now flashing but now my question is should i edit update script after zip is created and signed?
Click to expand...
Click to collapse
if you are able to flash , why you want to edit updater script?
rajneeshk said:
if you are able to flash , why you want to edit updater script?
Click to expand...
Click to collapse
I just want to add some ui print command and the apks in data folder are not flashing because the dont have right location in the script
princechandela said:
I just want to add some ui print command and the apks in data folder are not flashing because the dont have right location in the script
Click to expand...
Click to collapse
You can modify the updater script and then can zip and sign again.
Sent from my Micromax A116i using XDA Premium 4 mobile app
Just replace the updater-binary from any other zip and you are good to go. Kitchen has known problems with updater-scripts
SaketJoshi said:
Just replace the updater-binary from any other zip and you are good to go. Kitchen has known problems with updater-scripts
Click to expand...
Click to collapse
I replaced updater binary from some other some other stock rom zip from a116 but it didnt work.
princechandela said:
I replaced updater binary from some other some other stock rom zip from a116 but it didnt work.
Click to expand...
Click to collapse
copy whole META-INF folder from stock.zip to your zip. After that, modify the script.
rajneeshk said:
You can modify the updater script and then can zip and sign again.
Sent from my Micromax A116i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't know but i am again getting this problem even if i use option 2(lazy mode) in kitchen.
I did everything again from scratch but i am still getting error executing update binary error.
Hi all, my first post here, I hope its not in the wrong section
I know this will probably be a very noob question, but I have been trying to create a .zip file with my stock rom I downloaded from a site, (I have a HTM-H9500 [MTK 6582]), I was creating the zip in android kitchen, but whatever i do i always get Error: status 0 in CWM, I read that this would probably because of update-binary or updater-script, I have tried creating update-script (without the r) and CWM directly says that its very old and that i should create updateR-script, however when i do all the process again with updater-script I get this annoying status 0 error.
What can i do? I searched this topic in the net and all the sugestions people had said havent worked for me.
Thanks in advance and sorry for my bad english.
Replace the update-binary file from an existing custom ROM of your device with the ROM you made using kitchen that should do the job.
Also while adding the file to zip make sure you set the compression to store
Hit thanks if I helped.
Sent from my C5302 using XDA Free mobile app
Tech N You said:
Replace the update-binary file from an existing custom ROM of your device with the ROM you made using kitchen that should do the job.
Also while adding the file to zip make sure you set the compression to store
Hit thanks if I helped.
Sent from my C5302 using XDA Free mobile app
Click to expand...
Click to collapse
Hi! Thanks for the quick answer, the thing is because my phone is not very popular i havent found any other custom rom other than the stock specifically for my phone (thats why i was trying to port from another device that is very similar, but first i tried to do this process with my stock rom) so i dont have any other update-binary file other than this one.
About the other thing, how can i change the compression rate in android kitchen ?
Again, thanks a lot and sorry for my english
AlpinoSoyYo said:
Hi! Thanks for the quick answer, the thing is because my phone is not very popular i havent found any other custom rom other than the stock specifically for my phone (thats why i was trying to port from another device that is very similar, but first i tried to do this process with my stock rom) so i dont have any other update-binary file other than this one.
About the other thing, how can i change the compression rate in android kitchen ?
Again, thanks a lot and sorry for my english
Click to expand...
Click to collapse
Go to play store and download zipme app.
Create any flashable app using zip me and then copy it to PC. Open the META-INF Folder then com->android ->Google then open it and you'll see a update-binary file. That is your stock binary
Open the final zip after creating the ROM. If om Windows open the zip (ROM) created and open the zip created using zipme.
Copy the update-binary from zipme ZIP to kitchen created zip and when you'll do this you will see a menu that will ask that are you sure about adding this file, search around a bit and you'll see the compression option
Tech N You said:
Go to play store and download zipme app.
Create any flashable app using zip me and then copy it to PC. Open the META-INF Folder then com->android ->Google then open it and you'll see a update-binary file. That is your stock binary
Open the final zip after creating the ROM. If om Windows open the zip (ROM) created and open the zip created using zipme.
Copy the update-binary from zipme ZIP to kitchen created zip and when you'll do this you will see a menu that will ask that are you sure about adding this file, search around a bit and you'll see the compression option
Click to expand...
Click to collapse
Seriously, thanks lot, means a lot to me, im not used to get much help in forums haha, what you said worked flawlessly, now i get status 7 error, but this means where going somewhere, il keep digging to fix this.
Thanks again
AlpinoSoyYo said:
Seriously, thanks lot, means a lot to me, im not used to get much help in forums haha, what you said worked flawlessly, now i get status 7 error, but this means where going somewhere, il keep digging to fix this.
Thanks again
Click to expand...
Click to collapse
Glad to help friend
Status 7 is error with your mount points.
In your updater-script when you'll open it (open using NOTEPAD++ ONLY, don't use notepad or wordpad) you will see two lines as
Format ("MTD", "SYSTEM"); and other would be mount.
Check these two lines and replace them with your device mount paths
You'll be having no problem.!
Tech N You said:
Glad to help friend
Status 7 is error with your mount points.
In your updater-script when you'll open it (open using NOTEPAD++ ONLY, don't use notepad or wordpad) you will see two lines as
Format ("MTD", "SYSTEM"); and other would be mount.
Check these two lines and replace them with your device mount paths
You'll be having no problem.!
Click to expand...
Click to collapse
Thanks !
In my updater-script I have this two lines
format("MTD", "system");
mount("MTD", "system", "/system");
I know i should know this by now but what are you refering to with 'your device mount paths'?
Thanks a lot, trying to learn here
AlpinoSoyYo said:
Thanks !
In my updater-script I have this two lines
format("MTD", "system");
mount("MTD", "system", "/system");
I know i should know this by now but what are you refering to with 'your device mount paths'?
Thanks a lot, trying to learn here
Click to expand...
Click to collapse
Do you have a recovery.img for your device?
Extract it using kernel kitchen and then after extracting it you' ll get a folder named ramdisk.
Open it go to etc and then recovery.fstab.
Open it with notepad++ and see the mount paths for your device just copy and replace it.
Mount path is the line that tell CWM where to install the particular files. If you face any problems then attach your recovery.img and updater-script and I'll have look at it
Tech N You said:
Do you have a recovery.img for your device?
Extract it using kernel kitchen and then after extracting it you' ll get a folder named ramdisk.
Open it go to etc and then recovery.fstab.
Open it with notepad++ and see the mount paths for your device just copy and replace it.
Mount path is the line that tell CWM where to install the particular files. If you face any problems then attach your recovery.img and updater-script and I'll have look at it
Click to expand...
Click to collapse
Well i didnt had kernel kitchen so after downloading it and runing it i only found those 5 options:
1 work with boot.img files
2 work with kernel.sin and ftf files
3 work wih kernel.elf files
4 work with init ramdisk
5 editing bootsplash image
But nothing to extract recovery.img, i suposed that i should just change recovery.img name to boot.img and do the process but i get an empty folder in the output folder, what should I do?
Thanks thanks thanks again
Google this tool "std unpack" open to first link and download that tool.
Drag your recovery.img to STD unpack and you'll get your files.
Alternatively you can also use kitchen to unpack the recovery.img
Just go to advanced options then go to boot unpacking tools and follow steps as suggested
Sent from my C5302 using XDA Free mobile app
Tech N You said:
Google this tool "std unpack" open to first link and download that tool.
Drag your recovery.img to STD unpack and you'll get your files.
Alternatively you can also use kitchen to unpack the recovery.img
Just go to advanced options then go to boot unpacking tools and follow steps as suggested
Sent from my C5302 using XDA Free mobile app
Click to expand...
Click to collapse
Seriously, sorry to be this stupid, but i cant find anything googling "std unpack" "std unpack tool" or "std unpack download" just a bunch of c++ questions..
Thanks again..
EDIT: nevermind i did it with kitchen like you said in advanced options, this is what I have in recovery.fstab
# mount point fstype device [device2]
/misc emmc /dev/misc
/data ext4 /dev/block/mmcblk0p7
/system ext4 /dev/block/mmcblk0p5
/cache ext4 /dev/block/mmcblk0p6
/boot emmc /dev/bootimg
/recovery emmc /dev/recovery
/emmc vfat /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
How should i change the lines: format("MTD", "system"); and mount("MTD", "system", "/system"); according to that?
Again, thanks for the extensive help
AlpinoSoyYo said:
Seriously, sorry to be this stupid, but i cant find anything googling "std unpack" "std unpack tool" or "std unpack download" just a bunch of c++ questions..
Thanks again..
EDIT: nevermind i did it with kitchen like you said in advanced options, this is what I have in recovery.fstab
# mount point fstype device [device2]
/misc emmc /dev/misc
/data ext4 /dev/block/mmcblk0p7
/system ext4 /dev/block/mmcblk0p5
/cache ext4 /dev/block/mmcblk0p6
/boot emmc /dev/bootimg
/recovery emmc /dev/recovery
/emmc vfat /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
How should i change the lines: format("MTD", "system"); and mount("MTD", "system", "/system"); according to that?
Again, thanks for the extensive help
Click to expand...
Click to collapse
Ready to help always
Use this command for format.
format("ext4", "EMMC", "/dev/block/mmcblk0p5", "system") ;
For mount statement just replace format with mount and keep rest same.
Tech N You said:
Ready to help always
Use this command for format.
format("ext4", "EMMC", "/dev/block/mmcblk0p5", "system") ;
For mount statement just replace format with mount and keep rest same.
Click to expand...
Click to collapse
Thanks again man...
Im still getting status 7 error but now it says format() expects 3 args, got 4
AlpinoSoyYo said:
Thanks again man...
Im still getting status 7 error but now it says format() expects 3 args, got 4
Click to expand...
Click to collapse
Update-binary error only. Try to get a update-binary for your mobile model this is only the problem rest everything is ok.
Also keep a nandroid backup ready if anything goes wrong just explore your device. If it is a Mediatek6557 (just a example) device then search for the any handset running the board of mtk 6557 and download it's custom ROM and replace update-binary and it will work. Download CPU-Z for your phone from play store to get detailed information of your device and board.
Tech N You said:
Update-binary error only. Try to get a update-binary for your mobile model this is only the problem rest everything is ok.
Also keep a nandroid backup ready if anything goes wrong just explore your device. If it is a Mediatek6557 (just a example) device then search for the any handset running the board of mtk 6557 and download it's custom ROM and replace update-binary and it will work. Download CPU-Z for your phone from play store to get detailed information of your device and board.
Click to expand...
Click to collapse
Well thanks, i'll kep searching, one last thing, why would my update-binary wont work? i mean, im using stock rom and trying to flash stock rom again, why would i need a different one?
AlpinoSoyYo said:
Well thanks, i'll kep searching, one last thing, why would my update-binary wont work? i mean, im using stock rom and trying to flash stock rom again, why would i need a different one?
Click to expand...
Click to collapse
You using stock ROM but according to device it doesn't know stock or custom for it everything we flash is just a external source which is implemented in it.
Tech N You said:
You using stock ROM but according to device it doesn't know stock or custom for it everything we flash is just a external source which is implemented in it.
Click to expand...
Click to collapse
Well like you said i kept searching and found an update binary that did the trick and everything flashed just fine, however, even though i didnt get a bootloop, when i turn on the phone it shows the brand logo as always and then its just a black screen.
Any ideas? Thanks !!
Check the permissions in updater-script to and hope you can boot into recovery, restore the phone to old state and then using kitchen convert your updater-script (edify) to update-script (amend) and check for errors. Ignore error with the format and mount command
Sent from my C5302 using XDA Free mobile app
Tech N You said:
Check the permissions in updater-script to and hope you can boot into recovery, restore the phone to old state and then using kitchen convert your updater-script (edify) to update-script (amend) and check for errors. Ignore error with the format and mount command
Sent from my C5302 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks again, what should i look for in permissions in updater-script?
and update-script (without r) gives me problems when i try to flash in cwm
Update-script is old format and isn't used much more. New devices use updater-script for flashing
Sent from my C5302 using XDA Free mobile app
Remember: Backup first! Be rooted! Have busybox installed! (We will create a recovery flashable zip which updater-script uses busybox commands)
To deodex your current device state follow the steps below:
Make sure you have adb and your device drivers installed on your computer (how to: installing and using adb).
Open command line and pull /system/app, /system/priv-app and /system/framework from phone via adb to your computer.
Code:
adb pull /system/app app
adb pull /system/priv-app priv-app
adb pull /system/framework framework
This will generate the folders "app", "priv-app" and "framework" containing the pulled files in the current directory.
Generate a list containing the folders with "arm"-folders which have to be deleted later in the phone (not the "lib/arm"-folders!!). Do this by opening terminal and navigate to the folder containing your previously pulled folders "app", "priv-app" and "framework" and type
Code:
dir /s /a:d /b arm | find /v "\lib\arm" > loglist.txt
There now should be a textfile containing all paths to the "arm"-folders. We'll need it later...but the textfile should look like:
Code:
<Directory you pulled your files to>\priv-app\3DTourViewer_HD_M2\arm
<Directory you pulled your files to>\priv-app\BackupRestoreConfirmation\arm
<Directory you pulled your files to>\priv-app\CloudAgent\arm
<Directory you pulled your files to>\priv-app\CSC\arm
....
Install Java (if you don't already have) and de-odex the pulled files with this tool.
Put the deodexed files into the folders /system/app, /system/priv-app and /system/framework in the attached zip.
Edit the zips' updater-script (META-INF\com\google\android\updater-script) according to the previously generated folder list. Take the textfile generated in 3. and replace
all \ with /
the path <Directory you pulled your files to> (see above example) in the textfile with "/system
It then should look like:
Code:
"/system/priv-app/3DTourViewer_HD_M2/arm
"/system/priv-app/BackupRestoreConfirmation/arm
"/system/priv-app/CloudAgent/arm
"/system/priv-app/CSC/arm
....
Then replace line end characters with ", (remember to remove the very last comma in the line or to insert a very last " in the line in case the last line doesn't contain line end character(s)) to get a comma-separated list of your folders:
Code:
"/system/priv-app/3DTourViewer_HD_M2/arm","...","/system/priv-app/BackupRestoreConfirmation/arm"
Modify the 'delete-recursive' entries in the updater-script according to your list and save it (do neither modify the encoding of the file nor the line end characters! Has to be "LF"! )
Boot into recovery.
Clear cache and dalvik-cache.
Flash zip.
Reboot (in my case it took some minutes).
I recommend using Notepad++ as editor because it's easy to use and much more powerful than standard windows editor.
reserved
SHA_NDY said:
Ok, I finally managed to do it.
If anyone is interested in how it worked I can try to provide my way to success ...
Remember: Backup first! Be rooted! Have busybox installed!
Make sure you have adb and device drivers installed on your computer.
Pull /system/app, /system/priv-app and /system/framework from phone via adb to your computer.
Code:
adb pull /system/app app
adb pull /system/priv-app priv-app
adb pull /system/framework framework
This will generate the folders "app", "priv-app" and "framework" containing the pulled files in the current directory.
Generate a list containing the folders with "arm"-folders which have to be deleted later in the phone. Do this by opening terminal and navigate to the folder containing your previously pulled folders "app", "priv-app" and "framework" and type
Code:
dir /s /a:d /b arm | find /v "\lib\arm" > loglist.txt
There now should be a textfile containing all paths to the "arm"-folders. We'll need it later...but the textfile should look like:
Code:
<Directory you pulled your files to>\priv-app\3DTourViewer_HD_M2\arm
<Directory you pulled your files to>\priv-app\BackupRestoreConfirmation\arm
<Directory you pulled your files to>\priv-app\CloudAgent\arm
<Directory you pulled your files to>\priv-app\CSC\arm
....
Install Java (if you don't already have) and de-odex the pulled files with this tool.
Put the deodexed files into the folders /system/app, /system/priv-app and /system/framework in the attached zip.
Edit the zips' updater-script (META-INF\com\google\android\updater-script) according to the previously generated folder list. Take the textfile generated in 3. and replace
all '\' with '/'
the path '<Directory you pulled your files to>' (see above example) in the textfile with '/system'
'/arm' with '/arm"'
Line end characters with ','
to get a comma-separated list of your folders. Modify the 'delete-recursive' entries according to your list and save the updater-script (do not modify the encoding of the file)
Boot into recovery.
Clear cache and dalvik-cache.
Flash zip.
Reboot.
Attached: the zip-file body which has to be edited as you need it...do not touch the permission settings in the updater-script...
Click to expand...
Click to collapse
One question , have you use twrp 2.8.1.1 ?
Inviato dal mio SM-G850F utilizzando Tapatalk
belthazor86 said:
One question , have you use twrp 2.8.1.1 ?
Click to expand...
Click to collapse
Yes, I used TWRP 2.8.1.1
I'm not sure but perhaps it will also work flashing with Flashify app.
Ok,now I can do it again. In this time i have modified the file updater-script with information of my textfile
Inviato dal mio SM-G850F utilizzando Tapatalk
Nothing,bootloop again..I give up. Nothing Xposed for me
Inviato dal mio SM-G850F utilizzando Tapatalk
The bootloop problem was a LF replaced by CRLF in the edited updater-script...
I followed your guide and everything went well. No bootloop.
But I got some popup notifications that google services and some google related stuff has stopped so I can not finish the initial setup.
Any clue what went wrong?
I assume your downloadable deodexed france 5.0.2 is for galaxy G850F ... Flashed it ... Bootloop ...
zalood said:
I followed your guide and everything went well. No bootloop.
But I got some popup notifications that google services and some google related stuff has stopped so I can not finish the initial setup.
Any clue what went wrong?
Click to expand...
Click to collapse
Hey zalood,
I only moved through all the steps described in the guide after initial setup was done. I'm not sure if there are files/libs/preferences missing before setup is complete.
zalood said:
I assume your downloadable deodexed france 5.0.2 is for galaxy G850F ... Flashed it ... Bootloop ...
Click to expand...
Click to collapse
This zip is for deodexing a stock state france 5.0.2 ROM, not the ROM itself. Same for russian zip...
I hope this was helpful.
SHA_NDY said:
Hey zalood,
I only moved through all the steps described in the guide after initial setup was done. I'm not sure if there are files/libs/preferences missing before setup is complete.
This zip is for deodexing a stock state france 5.0.2 ROM, not the ROM itself. Same for russian zip...
I hope this was helpful.
Click to expand...
Click to collapse
Thanks SHA_NDY.
Perhaps I was also wiping the data instead cache and dalvik only.
Will try again in the morning and revert back ...
Deodexing and flashing successful . . .
Thanks a lot for this Guide . .
first of all thank you, for this guide :good:
when I try to install it TWRP says "E: Error executing updater binary in zip ' /sdcard....", but i don´t touched the updater-binary file.
can someone give me an advice ?
albert-319 said:
first of all thank you, for this guide :good:
when I try to install it TWRP says "E: Error executing updater binary in zip ' /sdcard....", but i don´t touched the updater-binary file.
can someone give me an advice ?
Click to expand...
Click to collapse
Which TWRP version do you use? I use 2.8.1.1 and everything works perfect.
If you don't succeed in flashing with e.g. other TWRP version you can take a zip (something you already flashed) that you know to work with your TWRP version. Delete everything in the zip EXCEPT the updater-binary and place the files you deodexed into the zip (keep the folder structure according to the attached zip in this thread) and place your updater script.
Do you have busybox installed?
Hi, just flashed stock russian firmware, set up google account and etc, flashed twrp 2.8.1.1. then russian zip to deodex but stuck on android logo, do I have to update gapps after setting account and then flash deodex zip?
diego1810 said:
Hi, just flashed stock russian firmware, set up google account and etc, flashed twrp 2.8.1.1. then russian zip to deodex but stuck on android logo, do I have to update gapps after setting account and then flash deodex zip?
Click to expand...
Click to collapse
I'm not sure if I did so to get it working. I think I remove the zip files, everyone should do like described in the tuto, don't know what side-effects do occur...sorry
Dear SHA_NDY,
So I followed all the steps in your tutorial.
So what I did was unzipped the zip file that you had attached, and then updated the directories with the deodexed files and updated the updater script as well. I then zipped the file back up and tried to flash it but it wouldnt flash for me.
What am I doing wrong?
Thank you
harper86 said:
Dear SHA_NDY,
So I followed all the steps in your tutorial.
So what I did was unzipped the zip file that you had attached, and then updated the directories with the deodexed files and updated the updater script as well. I then zipped the file back up and tried to flash it but it wouldnt flash for me.
What am I doing wrong?
Thank you
Click to expand...
Click to collapse
Can you provide your zip for download? Thanks
SHA_NDY said:
Can you provide your zip for download? Thanks
Click to expand...
Click to collapse
Hi Shandy. Fixed it. What I did was just flashed arter97 deodex system image file via ODIN and works pretty well now. Just had to re root after that.
Thank you
Then replace line end characters with ", (remember to remove the very last comma in the line) to get a comma-separated list of your folders:
Code:
"/system/priv-app/3DTourViewer_HD_M2/arm","...","/system/priv-app/BackupRestoreConfirmation/arm"
Modify the 'delete-recursive' entries in the updater-script according to your list and save it (do neither modify the encoding of the file nor the line end characters! Has to be "LF"! )
Click to expand...
Click to collapse
Im trying so much but dont get this part.
At the monent i am here now
"/system/priv-app/3DTourViewer_HD_M2/arm
"/system/priv-app/BackupRestoreConfirmation/arm
"/system/priv-app/CloudAgent/arm
"/system/priv-app/CSC/arm
....
Click to expand...
Click to collapse
@SHA_NDY maybe you can explain it a little more?
maybe in german?
ManuFisch said:
Im trying so much but dont get this part.
At the monent i am here now
@SHA_NDY maybe you can explain it a little more?
maybe in german?
Click to expand...
Click to collapse
I'll give it a try but don't recall any German from childhood .
If you're using notepad++ or notetab pro, then you can do a replace using regular expressions, so put your cursor at the top of the doc and for the "find" field, use this [\r\n]+ and click on 'use regular expressions' if it's there, (which is carriage return line feed, which is at the end (invisible) of each line). In the replace field, put ", (exactly), and then replace-all. If the entire document is now a single line, then it's good. Probably you have to remove the last comma manually.
So now you've edited your .txt file that you created in the OP steps, so now open the updater-script file in the .zip. There are 3 "delete-recursive" sections like delete-recursive("... "), one for apps, one for priv-apps and one for framework, so copy the first batch of modified text from the .txt file that are "apps" (up till the framework one), and paste them over the entire innards of the ("...") clause of the delete-recursive. Same for framework (only one entry), and same for priv-apps.
I'm just writing from memory so maybe I mispelled something. ANyway, when you're completed, make sure to overwrite updater-script in the .zip and you should be ready to either mess up your phone (back it up!) or make it xposed compat.
cheers.