HI I have unzip my update.zip which i get from RFS used ultraISO with kitchen V0.98 。 I use kitchen deodex all of the apks and jars file， then I signed to the APKS with 21choose。And news the new zip file。 after this， I get the apps and framework file to recovery RFS file which I get from the new ZIP file ， i delete all the odexs file in the RFS。 I flash my cellphone with the new RFS I have made ， the cell phone can't power on 。 why ？
thx！！！
mapleshadow said:
HI I have unzip my update.zip which i get from RFS used ultraISO with kitchen V0.98 。 I use kitchen deodex all of the apks and jars file， then I signed to the APKS with 21choose。And news the new zip file。 after this， I get the apps and framework file to recovery RFS file which I get from the new ZIP file ， i delete all the odexs file in the RFS。 I flash my cellphone with the new RFS I have made ， the cell phone can't power on 。 why ？
thx！！！
Click to expand...
Click to collapse
I'm not really sure what you are doing. If you deodex the ROM, the odex files shouldn't have to be deleted manually. Maybe I don't understand. No, I don't understand.
logcat is your friend... Connect a usb cable and do a 'adb logcat' from the command prompt while the phone is booting. You'll have to have the Android SDK downloaded and be in the tools folder or have it in your path to use adb.
I don't delete the *.odex manually, the files were deleted by the kicthen automatic.
After that, I made a update.zip, then upload the file, the device stuck in the startup loop.
Seriously, I do NOT modify any *.odex, just repack them.
I don't know why? Can you help me?
mapleshadow said:
I don't delete the *.odex manually, the files were deleted by the kicthen automatic.
After that, I made a update.zip, then upload the file, the device stuck in the startup loop.
Seriously, I do NOT modify any *.odex, just repack them.
I don't know why? Can you help me?
Click to expand...
Click to collapse
I can't help without more information. Can you get the output from 'adb logcat' while the phone is stuck in the startup loop and post it here?
The kitchen is really meant for Android on HTC phones, so your mileage may vary. Other device manufacturers tend to do some things differently.
This question has been asked in the Android Kitchen thread. Please do not start redundant threads.
Related
Ive done a backup on my phone and created a flashable zip (update.zip)
Now im playing around with dsixda's kitchen and trying to extract the system.tar, however it fails most likely due to fact the the system.tar is empty
the files in the archive are as follows
Meta-inf -- <folder>
boot.img -- <8192KB>
image-edify -- <1KB>
system.ext4.tar -- <0KB>
system.ext4.tar.a -- <976,563KB>
system.ext4.tar.b -- <68,151KB>
By the looks of things it has split the system.ext4.tar because its over a gig
How can i compile this into one file or one image so that the kitchen can read it, I'm on a windows 7 PC but i can run linux in a vbox if necessary.
Thanks
Try using the zip file in your input folder.
dsixda's kitchen should be able to extract from it
mikep99 said:
Try using the zip file in your input folder.
dsixda's kitchen should be able to extract from it
Click to expand...
Click to collapse
Already tried, it comes back saying its deleting the part a and part b files and then says the system.ext4.tar isnt a valid archive.
Is it a stock rom?
If so, download the firmware from sammobile and put the tar.md5 file into your input folder (after removing the .md5 suffix).
Thats worked for me in the past....
It is stock, but i have removed the bloatware, installed a few mods, i was hoping to use this particular one really as a base. Ive already played around with fully stock and i kind of broke the whole thing
I'm not too sure then unless theres some tool you can find to merge the 3 tar files into 1...
Never had to do it so I'm unable to suggest anything I'm afraid.
Hi, I have new Prestigio tablet PMT5777_3G and I want to modify it's default ROM. I followed this tutorial: http://forum.xda-developers.com/showthread.php?t=1801690. I successfully extracted system folder, but I have no idea how to create updater-script for this specific ROM. If I understand correctly I need to get updater-script from original ROM.
I've got something that resembles original ROM, but it's folder structure is completely different from what I would expect.
I would expect:
META-INF
system
boot.img
I've got:
APDB_MT6582_S01_MAIN2.1_W10.24
boot-sign.img
BPLGUInfoCustomAppSrcP_MT6582_S00_MOLY_WR8_W1315_MD_WG_MP_V12_P4_1_wg_n
cache-sign.img
Checksum.ini
EBR1-sign
lk-sign.bin
logo-sign.bin
MBR-sign
MT6582_Android_scatter.txt
preloader_htt82_tb_jb5.bin
recovery-sign.img
secro-sign.img
system-sign.img
sro-lock-sign.img
sro-unlock-sign.img
userdata-sign.img
I'm an android developer, but have no experience with custom ROM's and now am in a situation, where I want to get that custom ROM up and running, but am unable, because I can't figure out how to create updater-script or extract it from files that I currently have. It would be great if someone could point me to the right direction of what to do next.
Thanks
P. S. It seems it's against the rules to ask questions here, but I can't seem to find where else to ask this on xda
Dantenas said:
Hi, I have new Prestigio tablet PMT5777_3G and I want to modify it's default ROM. I followed this tutorial: http://forum.xda-developers.com/showthread.php?t=1801690. I successfully extracted system folder, but I have no idea how to create updater-script for this specific ROM. If I understand correctly I need to get updater-script from original ROM.
I've got something that resembles original ROM, but it's folder structure is completely different from what I would expect.
I would expect:
META-INF
system
boot.img
I've got:
APDB_MT6582_S01_MAIN2.1_W10.24
boot-sign.img
BPLGUInfoCustomAppSrcP_MT6582_S00_MOLY_WR8_W1315_MD_WG_MP_V12_P4_1_wg_n
cache-sign.img
Checksum.ini
EBR1-sign
lk-sign.bin
logo-sign.bin
MBR-sign
MT6582_Android_scatter.txt
preloader_htt82_tb_jb5.bin
recovery-sign.img
secro-sign.img
system-sign.img
sro-lock-sign.img
sro-unlock-sign.img
userdata-sign.img
I'm an android developer, but have no experience with custom ROM's and now am in a situation, where I want to get that custom ROM up and running, but am unable, because I can't figure out how to create updater-script or extract it from files that I currently have. It would be great if someone could point me to the right direction of what to do next.
Thanks
P. S. It seems it's against the rules to ask questions here, but I can't seem to find where else to ask this on xda
Click to expand...
Click to collapse
Since you are a beginner to ROM development, I would recommend the use of dsixda's Android kitchen, which you probably have downloaded already. If not use this link
http://forum.xda-developers.com/showthread.php?t=633246
Follow these steps to obtain the file structure and Meta-Inf folder for your custom rom.
1. Open the folder where you have placed the kitchen.
2. You will find a folder called original_update.
3. Open that folder and copy your boot.img and system.img files into it. ( In your case it is boot-sign.img and system-sign.img. Rename those files into boot.img and system.img and place them in the folder )
4. Now open the kitchen. ( Refer the above link to know how to do it )
5. You will find " 1. Set up working folder from ROM " option under Main Menu.
6. Type 1 and you will be directed to another menu. Click Enter.
7. Select your boot.img and system.img from the menu.
8. Now follow the instructions that appear on the screen.
9. When you successfully complete the steps, you will have the required Working folder, with boot.img, system folder and Meta-Inf folder, which will contain the updater-script (It will be automatically generated)
All the best. :good:
Hit Thanks if this helped you... PM me if you need further help or search the forum for detailed instructions.
Thanks, this helped me, but I still can't create ROM.
I encountered a problem with kitchen:
Code:
Available ROMs:
(1) system.img and boot.img
Enter selection number (default=1, cancel=0, r=refresh):
Found original_update/system.img
Found original_update/boot.img
The new working folder will be named WORKING_061614_070841
Change the name (y/n)? (default: n):
Creating working folder WORKING_061614_070841 ...
Copying boot.img ...
Copying system.img ...
Adding an update-script ...
NON-YAFFS/NON-TAR FILE FORMAT DETECTED IN ROM
Mounting system.img to loopback device and then extracting files ...
Error: Unable to mount system.img
Error: No /system/framework folder found!
Press Enter to continue
This creates my missing update-script and boot.img, but system folder is empty.
Would it be a good idea to extract all system files from device and attempt to create ROM with them, and this update-script, or is there something I could do with system.img to make it extract?
Try this
Don't worry. There's always an alternative. Try this simple method.
1. Boot into CWM (Clockwork Mod) Recovery. (I'm pretty sure you know how to do it, if not, you can feel free to search the forum)
2. Choose Backup and Restore.
3. Make a backup in your external sdcard.
4. Now boot normally, open your external sdcard. You will find a folder called clockworkmod. Copy that folder to your PC.
5. Inside that folder, you will find the backup.
6. Now, copy boot.img and system.ext4.tar.a to your original_update folder of the kitchen.
7. Warning! Do not copy system.ext4.tar, only copy system.ext4.tar.a
8. Once you have copied these two files, rename system.ext4.tar.a into system.ext4.tar
9. Now, open android kitchen and follow the exact same steps as you did before.
10. When you choose the available rom, you will find the screen as below.
Code:
Available Roms:
(1) system.ext4.tar and boot.img
11. Choose it and follow the instructions. You will have your required working folder.
Try this and let me know if you still face any issues. :good:
I was unable to load CWM recovery, because it is not supported by my device. I tried TWRP too, which also doesn't support my device. Is it possible to do without CWM?
Dantenas said:
I was unable to load CWM recovery, because it is not supported by my device. I tried TWRP too, which also doesn't support my device. Is it possible to do without CWM?
Click to expand...
Click to collapse
I'm sorry my friend, even if you create your own ROM, you require either one of them to flash the ROM to your device. Seeing you so keen on developing the rom, try to use any yaffs tool to create your system.img from extracted system folder. You may refer this thread.
http://forum.xda-developers.com/showthread.php?t=1645412
[FONT="]4 - Way Reboot Menu for Nabi2 JB 4.1[/FONT][FONT="]Haven't seen a lot of development for the Nabi2 as much as we had before and got the idea from my my Galaxy Phones. This is the extended Reboot Menu only and not the "Power Menu". I do not recommend flashing to Custom Roms as the ROMs may contain special permissions/policies ( if added ) that the Rom Developer may have implemented or even may be require so the Custom Rom may run or function properly. [/FONT][FONT="]
[/FONT][FONT="]Knowing there may not be any for the Nabi2 ATM, I guess we are safe from this LOL. [/FONT]
[FONT="]The Extended Reboot Menu Includes:[/FONT][FONT="]REBOOT[/FONT][FONT="]
[/FONT][FONT="]( Normal Complete Reboot)[/FONT]
[FONT="]HOT BOOT[/FONT][FONT="]
[/FONT][FONT="]( Quick Reboot for restarting the Android Shell only )[/FONT]
[FONT="]DOWNLOAD ( Not Working Correctly, will look into this one. Will also be renamed to BOOTLOADER )[/FONT][FONT="]
[/FONT][FONT="](Bootload Mode)[/FONT]
[FONT="]RECOVERY[/FONT][FONT="]
[/FONT][FONT="]( Restarts phone in your Recovery )
[/FONT][FONT="]SHUT DOWN[/FONT][FONT="]
( Turns the Tablet Off )[/FONT][FONT="]
[/FONT][FONT="]===================================================================[/FONT][FONT="]
[/FONT][FONT="]DISCLAIMER:[/FONT]
======================================================================================================================================
[FONT="]By YOU, the USER, flashing this file or manually pasting to modify your Android System, YOU understand and know what YOU are doing. I nor anyone will be held liable nor responsible for YOUR doing if your phone bricks. As always, as is suggested by many and myself, please make sure you perform a complete[/FONT]
[FONT="]NANDROID BACKUP[/FONT]
[FONT="]before flashing and/or modifying your OS or the mentioned stock .jar file. I also suggest YOU keep a separate copy of the stock .jar file handy, like in your External SDcard, if the phone decides not to boot up. Knowing this, YOU assume all responsibility for what happens as YOU, the USER, know and comprehend what YOU are doing and understand the consequences or severity of damages that can be brought to your [/FONT][FONT="]
[/FONT][FONT="]device by flashing or modifying your OS incorrectly. [/FONT]
[FONT="]You[/FONT][FONT="] Have Been Warned !![/FONT][FONT="]
[/FONT][FONT="]===================================================================[/FONT][FONT="]
[/FONT][FONT="]What's Needed / Recommended:[/FONT][FONT="]Rooted Device [/FONT][FONT="]( to extract the needed files Manually for backup )[/FONT][FONT="]
Custom Recovery ( TWRP for Flashing the ZIP and/or using the File Manager )
If you can do it via ADB Commands then all power to you.....[/FONT]
[FONT="]I provided [/FONT][FONT="]BOTH[/FONT][FONT="] , the stock NABI2 [/FONT][FONT="]( Stock NABI2 JAR )[/FONT][FONT="] and modded NABI2 .jar [/FONT][FONT="]( android.policy.jar )[/FONT][FONT="] files and the flashable zip [/FONT][FONT="]( Nabi2_4wayboot.zip )[/FONT][FONT="] below. If the flashable ZIP does not work for you let me know please. [/FONT]
[FONT="]What To Do:[/FONT][FONT="]
You have two choices on installing the .jar file. You can either Flash the ZIP in TWRP or manually copy & paste or push the .jar file to system/framework/. If you decide to do this manually, you will then need to set the file permissions to the modified android.policy.jar file to 0644. You can rename the stock .jar file with " .bak " at the end so you don't have to delete it from the framework folder if you so choose. Now using TWRP I was not able to automatically get the File Explorer to work properly but I did flash the Aroma File Manage in recover. It load up although the button presses and screen were off but I managed to copy and paste and set permissions to the file.
[/FONT]
[FONT="]The flashable zip may give you an SELinux Error but it will flash correctly.
[/FONT]
[FONT="]
Words of caution.....[/FONT][FONT="]if you attempt to do this manually and are still actively booted in your Android OS while modifying or deleting the .jar file, there is the highest probability that your tablet will immediately reboot and you will not be able to boot up the OS again and remain stuck on the Nabi boot screen as the android.policy.jar is no longer visible to your OS. This is why you need to do this before booting up like in recovery.
[/FONT]
[FONT="]===================================================================[/FONT] [FONT="]
Thanks and credits go out to :
[/FONT][FONT="]
@[/FONT][FONT="]tdunham[/FONT][FONT="]
@[/FONT][FONT="]CNexus[/FONT][FONT="]
@kahvitahra
for the information gathered on the How-Too's and the files needed for this MOD. If I missed someone please PM me or let me know.....
[/FONT]
[FONT="]
Enjoy!
[/FONT]
looks like a handy mod ... I haven't had a chance to try it out but I will .
thanks for making it .
I know this is old but thanks for this. Going to give it a go on my kids Nabi this week.
Hippie459MN said:
I know this is old but thanks for this. Going to give it a go on my kids Nabi this week.
Click to expand...
Click to collapse
Your Welcome. If you do upgrade the Nabi 2 up to 4.4.2. KitKat, here is the thread for that one.
DarkAngel said:
Your Welcome. If you do upgrade the Nabi 2 up to 4.4.2. KitKat, here is the thread for that one.
Click to expand...
Click to collapse
:good:
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.
Flashing Issues | Will not pass Android Logo
I have have the T-Mobile version of the S5 and it is currently running XtreStolite rom on lollipop. I have been messing around with the SystemUI and framework apks. (getting them to work every now and again)
However, I was searching around and tried to push the apk files through adb at first, instead of a complete reflash with the modified apks inside, with no luck. Adb says that the files were successfully sent but are not there and no changes are made. I then stumbled across a method using a flashable zip that is supposed to just replace the files I need.
I n doing so, after reboot the phone just sits at the Android Logo on powerup, them I have to reflash or restore my recovery. My question is this: Is there a method that allows me to setup a flashable zip with the system/priv-app/systemui/systemui.apk so that it will only replace those files and not the whole system folder itself?
There may be some more information that I am leaving out, sorry I have not slept all night and I am about to go to class.
Thanks in advance, if I have posted incorrectly, please advise.
RockyCaballero said:
I have have the T-Mobile version of the S5 and it is currently running XtreStolite rom on lollipop. I have been messing around with the SystemUI and framework apks. (getting them to work every now and again)
However, I was searching around and tried to push the apk files through adb at first, instead of a complete reflash with the modified apks inside, with no luck. Adb says that the files were successfully sent but are not there and no changes are made. I then stumbled across a method using a flashable zip that is supposed to just replace the files I need.
I n doing so, after reboot the phone just sits at the Android Logo on powerup, them I have to reflash or restore my recovery. My question is this: Is there a method that allows me to setup a flashable zip with the system/priv-app/systemui/systemui.apk so that it will only replace those files and not the whole system folder itself?
There may be some more information that I am leaving out, sorry I have not slept all night and I am about to go to class.
Thanks in advance, if I have posted incorrectly, please advise.
Click to expand...
Click to collapse
Here download this https://www.androidfilehost.com/?fid=24052804347782219
Extract and Add whatever directories/folders you want inside the system folder and flash. The script just extracts the system folder as a whole so as long as you make the correct folders, file names, directories etc it'll flash everything to the right spot.
Delete the jar file out of system/framework/ tho since it's a 5.1.1 jar file I did
Much obliged sir, worked perfectly. I'm sure it was the coding. [emoji2]