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.
Related
Hello all you Triple-Booters out there! I would like to introduce to you:
Convert2Dualboot-SD Tool
What is this you ask?
This is a little tool that I've put together that will convert any standard flashable roms for our Nook Color to be DualbootSD compatible. No more waiting on my lazy arse to update you guys!!! I used APK manager as a base for my script. I've written 3 different versions that will run on Linux, OSX and Android. All neccesary binaries are included with each version.
Click to expand...
Click to collapse
Can I use any kind of flashable zips?
Yes and no. You could use any standard flashable "rom" or "gapps" zips only.
Click to expand...
Click to collapse
How do I use it?
You drop a standard rom .zip into a "rom-to-modify" folder. Then execute a shell script that will give you an option to convert it for flashing to Primary or Alternate boot on the DualbootSD.
Click to expand...
Click to collapse
Can I use any CWM Recovery for flashing?
Absolutely not! Only use the CWM Recovery that was included with the DualbootSD.
Click to expand...
Click to collapse
Will you be updating this to add new features and stuff?
Not sure what features I can add, but you can always check the CHANGE LOG in post 3.
Click to expand...
Click to collapse
Can you give us step by step directions on how to use this?
Of course! See second post for more details.
Click to expand...
Click to collapse
***Disclaimer: Usual disclaimer applies here as well... you use this at your own risk, I am not responsible for anything that happens to any of your devices. You assume all responsibility when using this tool.***
Credits:
Daneshm90 for the APK Manager Script I used as a base
Pinako/Inportb/Jyio/Boss! - for his Android binaries
DizzyDen - for porting this over to DOS and his many ideas to get the script to where it's at
HacDan - for some bash guidance
If I forgot someone else, please notify me.
Convert2Dualboot-SD Tool-README
Convert2Dualboot-SD-Linux v1.4
DOWNLOAD
*C2DSD=Convert2Dualboot-SD*
1-Extract the zip file you just downloaded anywhere on your system
2-In the C2DSD folder, there are 2 folders called "modify-for-pri" and "modify-for-alt". Copy your rom.zip and/or gapps.zip file into its respective folder. No need to rename the file as long as it has a .zip extension.
3-Open up terminal and cd into Convert2Dualboot-SD-Linux
4-At the termninal prompt execute the C2DSD script
Code:
$ sh convert*
5-This will give you a menu where you can choose to modify the "rom" and/or "gapps" for either Primary or Alternate boot. It will also give you an option to clear out recently modded zips. Now with option to mod both ROM & GAPPS on the fly. Just place both files inside either "modify-for-pri" or "modify-for-alt" and choose the option to modify both from the menu.
6-Choose your option and wait while it does its thing.
7-Once it's finished you can exit the program by choosing "0"
8-Now browse to the C2DSD folder and you can find your DualbootSD modded rom file either in "Primary-Mod" or "Alternate-Mod" depending on your earlier selection.
9-Copy that file to the /sdcard partition of your DualbootSD
10-Boot to CWM Recovery that is included with the DualbootSD
11-Flash and enjoy!
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------
Convert2Dualboot-SD-OSX v1.4
DOWNLOAD
*C2DSD=Convert2Dualboot-SD*
1-Extract the zip file you just downloaded anywhere on your system
2-In the C2DSD folder, there are 2 folders called "modify-for-pri" and "modify-for-alt". Copy your rom.zip and/or gapps.zip file into its respective folder. No need to rename the file as long as it has a .zip extension.
3-Open up terminal and cd into Convert2Dualboot-SD-OSX
4-At the termninal prompt execute the C2DSD script
Code:
$ ./convert*
5-This will give you a menu where you can choose to modify the "rom" and/or "gapps" for either Primary or Alternate boot. It will also give you an option to clear out recently modded zips. Now with option to mod both ROM & GAPPS on the fly. Just place both files inside either "modify-for-pri" or "modify-for-alt" and choose the option to modify both from the menu.
6-Choose your option and wait while it does its thing.
7-Once it's finished you can exit the program by choosing "0"
8-Copy that file to the /sdcard partition of your DualbootSD
9-Boot to CWM Recovery that is included with the DualbootSD
10-Flash and enjoy!
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------
Convert2Dualboot-SD-Android v1.4
DOWNLOAD
*C2DSD=Convert2Dualboot-SD*
1-This will allow you to modify the zip files directly on your Nook
2-Extract the zip file you just downloaded to the root of your DualbootSD /sdcard partition.
3-The folder should be named c2dsd
4-In the c2dsd folder, there are 2 folders called "modify-for-pri" and "modify-for-alt". Copy your rom.zip or gapps.zip file into its respective folder. No need to rename the file as long as it has a .zip extension.
5-Open up any Terminal Emulator and cd into the c2dsd folder which should be "/sdcard/c2dsd"
6-At the termninal prompt execute the C2DSD script
Code:
$ su
# sh convert*
7-This will give you a menu where you can choose to modify the "rom" and/or "gapps" for either Primary or Alternate boot. It will also give you an option to clear out recently modded zips. Now with option to mod both ROM & GAPPS on the fly. Just place both files inside either "modify-for-pri" or "modify-for-alt" and choose the option to modify both from the menu.
8-Choose your option and wait while it does its thing.
9-Once it's finished you can exit the program by choosing "0"
10-Now you can choose to boot to CWM Recovery that is included with the DualbootSD
11-Choose "install zip from sdcard" and browse to either "Primary-Mod" or "Alternate-Mod" depending on your earlier selection.
12-Flash and enjoy!
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------
Convert2Dualboot-SD-DOS v1.3
DOWNLOAD
*C2DSD=Convert2Dualboot-SD*
1-Extract the zip file you just downloaded anywhere on your system
2-In the C2DSD folder, there are 2 folders called "modify-for-pri" and "modify-for-alt". Copy your rom.zip and/or gapps.zip file into its respective folder. No need to rename the file as long as it has a .zip extension.
3-Open up command window and cd into Convert2Dualboot-SD-DOS or create a shortcut on your desktop
4-At the command prompt execute the C2DSD script
Code:
convert2dualboot-sd-dos
5-This will give you a menu where you can choose to modify the "rom" and/or "gapps" for either Primary or Alternate boot. It will also give you an option to clear out recently modded zips. Now with option to mod both ROM & GAPPS on the fly. Just place both files inside either "modify-for-pri" or "modify-for-alt" and choose the option to modify both from the menu.
6-Choose your option and wait while it does its thing.
7-Once it's finished you can exit the program by choosing "0"
8-Copy that file to the /sdcard partition of your DualbootSD
9-Boot to CWM Recovery that is included with the DualbootSD
10-Flash and enjoy!
Click to expand...
Click to collapse
And that's all she wrote... well he, being me.
If I've helped in anyway. Don't hesitate to hit the thanks button.
Change log:
v1.4 (6/8/2012)
-Fixed gapps being zipped with rom when converting rom & gapps together
-Added SDCacheMount to converted roms (see the SDCacheMount thread for more info)
-Fixed mkimage binary executing error for Linux version
-No DOS update yet.... DizzyDen?????
-Thanks goes to xda user "shumash" for the SDCacheMount addition into the script
v1.3a
-Mkimage error on Android Script fixed.
-Mkimage is dependent on 'libmusl.so' which I did not include and linked in the tools folder. I overlooked this tidbit because I had "BOTBREW" installed on my system so it never complained about linking to it.
v1.3
-I effed up on the script!
-RASTAVIPER kept asking me about issues with his gapps. Apparently the mod for Gapps Alt Boot had the wrong mount points inserted into the updater script. NOW I SEE IT!
-Also in the DOS version. Prep of ROM Alt Boot had the wrong mount points as well. Sorry guys.
-It's been fixed and uploaded. Please don't use v1.2 anymore. Thanks.
v1.2
-Changed up UI layout of script: Please re-read README from post 2 above for edited instructions.
-Edited script to speed up mod process (Thanks DizzyDen!)
-Added option to mod both "ROM & GAPPS" on the fly
-Android version now has a tool.img file. This makes modding quicker and safer.
-Added DOS version ported by DizzyDen! (Thank you sir!)
-Modding for EMMC dualboot version in the works???? (That's if you guys want it)
v1.1
-Added gapps option
-Cleaned up some scripting behaviors
v1.0
-Initial release
Well.. after some thought, it really didn't make sense to release this without an option to mod gapps for the DualbootSD. I mean what good is a rom without gapps?!
Convert2Dualboot-SD v1.1 is up if anyone wants to try.
Check post 3 for all changlogs.
Thanks,
Racks
Taking advantage of the opportunity to try something new, I made a dual-boot card for my sister-in-law.
This is cool. I actually haven't tested the card yet as I have my device flashed to internal and have modded the recovery some. I haven't backed up any of the changes I made (I know, I know) and don't want to have to do it again.
I may try updating the card now that you've included gapps, though. I hadn't made a bootable card since I first rooted this thing, and to be honest it was by accident even that time. So I was wondering how to get gapps, was thinking about setting an alt-recovery just for that.
But anyway, I hadn't looked at how to do the gapps yet, maybe it was easier than that. But this seems even easier.
Cool, man! I bet the dual/triple booters will love being able to make their own updates. The experience I had last night couldn't have been easier. My wife got me and her sister the Nooks at the same time, I am excited for her to see what I have been talking about the last six months.
I will be sure to try this once my NC gets here. Thanks!
Racks,
Works great but there's an odd 0 byte file in the DB zip called ^[email protected] Is that an artifact and can I just delete it?
shumash said:
Racks,
Works great but there's an odd 0 byte file in the DB zip called ^[email protected] Is that an artifact and can I just delete it?
Click to expand...
Click to collapse
DB zip? Sorry, but what are you referring to with that?
And could you also let me know which one you used? OSX, Linux, Android?
Edit: That might just be the stupid __MACOSX hidden folder that osx likes to include Forgot to exclude that and the .gitignore file when zipping. Although they aren't detrimental to running the C2DSD Tool, you can choose to delete them if you wish.
Thanks,
Racks
Thanks a lot Racks... great work... we'll get together and sort out the windows based version... can include it in your work here... or as another feature of the IMEI generator.
DizzyDen said:
Thanks a lot Racks... great work... we'll get together and sort out the windows based version... can include it in your work here... or as another feature of the IMEI generator.
Click to expand...
Click to collapse
Awesome to hear! Was hoping you would jump in.
We'll hook up and get the Windows based version here as well as incorporate it into your IMEI generator.
Thanks!
Racks
racks11479 said:
Awesome to hear! Was hoping you would jump in.
We'll hook up and get the Windows based version here as well as incorporate it into your IMEI generator.
Thanks!
Racks
Click to expand...
Click to collapse
Sounds like a plan... I just got in from work... and am off tomorrow.
DizzyDen said:
Thanks a lot Racks... great work... we'll get together and sort out the windows based version... can include it in your work here... or as another feature of the IMEI generator.
Click to expand...
Click to collapse
racks11479 said:
Awesome to hear! Was hoping you would jump in.
We'll hook up and get the Windows based version here as well as incorporate it into your IMEI generator.
Thanks!
Racks
Click to expand...
Click to collapse
+1 from a meathead windows user here.
Sent from my NookColor racks tripple boot using Tapatalk 2
racks11479 said:
DB zip? Sorry, but what are you referring to with that?
And could you also let me know which one you used? OSX, Linux, Android?
--SNIP--
Thanks,
Racks
Click to expand...
Click to collapse
Sorry for being vague. I meant the modded dualboot sd zip build. But I tried it again and it was fine, so let's say no more about it, eh?
On a related note, since you're so motivated now, how about creating those separate cache1 and cache2 partitions so that we don't have to wait so long to boot between the two?
Anyone who tried the new modding option and that would like to share with us which CM9 rom (nightly) did he convert and is working fine after conversion?
spdsl said:
+1 from a meathead windows user here.
Sent from my NookColor racks tripple boot using Tapatalk 2
Click to expand...
Click to collapse
Was hoping to have something before I had to go to work this morning... didn't get it completed...
to keep as close as Racks' I will have a DOS batch file available sometime tonight...
True Windows GUI version will be available early in the week.
Keeping with Racks' desires... both will be open source and stored on his github... I use AutoIT for windows programming these things.
shumash said:
On a related note, since you're so motivated now, how about creating those separate cache1 and cache2 partitions so that we don't have to wait so long to boot between the two?
Click to expand...
Click to collapse
Racks, I just sent you a PM that might help with this issue.
shumash said:
Racks,
Works great but there's an odd 0 byte file in the DB zip called ^[email protected] Is that an artifact and can I just delete it?
Click to expand...
Click to collapse
UPDATE: I converted the latest Mirage build, and when I tried to flash it, Recovery complained that it wasn't a valid zip file. Checked it and the same weird file was in the converted flashable zip. When I ran the conversion a second time, all was good and it flashed as expected. I had deleted all the extraneous _MACOSX and .gitignore file stuff prior to running it the first time. BTW, the problem in the quoted post was when I converted an ICS build the first time, too. Racks, do you think that there is something that occurs the first time the script is run that is different on subsequent runs that might account for this?
Just installed nightly 28.4 without Opengl and then gapps which appeared in the folder Primary Mod after conversion.
After that I cant get inside shop.I click to open it and it gets me back to main menu.
Any ideas?Reflashing of gapps didnt work.
RASTAVIPER said:
Just installed nightly 28.4 without Opengl and then gapps which appeared in the folder Primary Mod after conversion.
After that I cant get inside shop.I click to open it and it gets me back to main menu.
Any ideas?Reflashing of gapps didnt work.
Click to expand...
Click to collapse
Primary mod is for Primary boot. Default primary boot was CM7, so I'm assuming you formatted /system1 & /data1 before flashing?
Could you also unzip the contents of the converted gapps zip. And check the updater script. All /system variables should be /system1.
-Racks
I didn't format anything before flashing. I thought this as an upgrade, so after conversion I just proceed to flashing.
Finally, I flashed your own gapps that you have at your dualboot topic and now everything is back to normal.
Unfortunately, even after this upgrade, I still continue to deal with FC issues of mail, Facebook and of other random apps.I think there is some problem with my card and CM9, since CM7 runs perfect from emmc or from same mem card.
Unleashed from my Revolutionized Desire HD
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
HERE IS A GUIDE FOR YOU ALL YOU CAN CREATE YOUR OWN ROM BY THIS METHOD.I AM NOT RESPONSIBLE FOR BRICKED DEVICES.
Click to expand...
Click to collapse
Requirement to make a custom rom
*JAVA JDK installed on your SYSTEM
*WIN XP/ 7/8/8.1.
*package given in download section
Who is this kitchen for ?
Those who are brand new to
creating custom ROMs and
want an easy place to start
learning
Those who just want to modify
shipped ROMs or someone
else's custom ROMs to their
liking
Those who are confused by all
those scripts and complex
commands required for
building and extracting
This is NOT a tool to
automatically turn you into a
full-fledged ROM developer.
ROM development normally
involves work from the ground
up and involves time , research
and patience .
Click to expand...
Click to collapse
PRESS THANKS IF YOU LIKE MY WORK..
Kitchen setup
setting up dsixda kitchen
1.download all the three link and unzip kitchen.rar and cywin package.
2.open cywin_package then open folder now, you can see 3 icons, a read-
me,a setup, and a folder. Choose
the setup. Here you will choose
install from local directory. Next,
navigate to the the folder of
extraction of cygwin and choose
the folder cygwin_packages inside
the cygwin extraction folder. Wait
for some time. Then, you will come
across a list of file. Click the 2-
circle-arrows,untill, it displays
“install”
after the procedure is complete,
run the batch file cygwin.bat . Now, minimise
it and copy kitchen folder,
keep it in some location where you have installed your cygwin package open home/ajay-pc(in my case this is administrator name of my pc)kitchen
now, open the batch file window
and type
cd c:\kitchen
wait for some time and then when
the location the changed, type
./menu
Click to expand...
Click to collapse
press thanks if you like my work
GUIDE
now minimize the batch file and extract official rom there you will find system.img then extract it using magic iso or flash
the official stock rom using odin the take a nandroid backup u will get system.rfs.tar in your sd card extract it using magic iso then make a folder in called rom and open it. again create a folder called system and copy all data from system.rfs.tar which u have extracted(do drag and dropping).
Now copy meta-inf of any stock rom and copy and kernel to rom folder.
Now you will get two folder and one file in your rom folder zip the folder content and copy the file where you have installed cygwin/home/ajay/kitchen/original update folder.
now open command shell which you have minimized 1st create working folder then add root permission,deodex your rom.
and at last press 99 to build your rom..
note-if it ask you to change updater script to update script change it but dont forget to change it back to updater script.now you will get your rom in output folder copy it to your sd card flash it if error occur unzip the zip file and delete meta-inf and boot.img and again copy meta-inf of any rom and kernel to it and zip it..again flash the rom..
PRESS THANKS IF YOU LIKE MY WORK
DOWNLOADS
Downloads
Link for cygwin click here :good:link for kitchen click here :good:link for magic iso click here :good:
Link for official firmware click here :good:
PRESS THANKS IF YOU LIKE MY WORK
CREDIT
DSIXDA for Android Kitchen
Samsung for this awesome device
ME for this Guide
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]
I would like to deodex the Codex system. How Can I do that? 232 Stock-based update. I have the Sony Xperia z2.
This is a very compressed and short guide, but hopefully it'll help you to start (it assumes you already have your phone rooted and have recovery installed) :
1ST OF ALL : MAKE NANDROID BACKUP.
you'll need to have JAVA installed on your machine, download and install that.
- on your device, enable "usb debugging" from developer options
- connect your device to PC, click "allow" on device for usb debugging
- have adb.exe on your pc, navigate to that folder and press shift+right click in empty space in the folder, choose "open command window here"
- in the cmd window that shows up type these commands in order :
adb pull /system/app system/app/
adb pull /system/priv-app system/priv-app/
adb pull /system/framework system/framework/
adb pull /system/vendor/app system/vendor/app
adb pull /system/build.prop system/build.prop
this will get you a folder next to your adb.exe file called "system" with all the files inside
- open system/vendor/app folder and copy "ims" and "chrome customizations" to system/app folder
- open system/framework/ folder and copy "SemcGenericUxpRes" to system/app folder
download deodex tool from here : http://forum.xda-developers.com/galaxy-s5/general/tool-deodex-tool-android-l-t2972025 (if you're not sure if your system is 32 or 64, get the 32 version)
- extract SVADeodexerForArtx32.zip to your c:/ drive
- open SVADeodexerForArt.exe and browse to where your "system" folder is (same folder as adb.exe)
- check app/framework/priv-app in the program options
- click deodex
- once done, create a flashable zip file from the resulting folders (remember to move files from "app" folder back to "framework" and "vendor" folder in the same order, or you'll get FCs)
- have SuperSU and flashable NUT recovery too on sdcard
- flash deodexed zip, then flash SuperSU and NUT recovery files again
- clear cache/dalvik, reboot
This is a rough guide, basically how I do it. if you need further help, post here and I'll try to respond or someone else will help/correct me if I made a mistake.
thanks
i deodexd with SVADeodexerForArtx64.exe
after that
how to create flashble zip
and which folders will i zip?
pls tellme bro
see attached file for creating flashable zip.
you need to copy the deodexed version from the SVADeodexerForArtx64 folder (you'll find app, framework, priv-app folder there) just open the zip with winrar, drag and drop folder, do a replace (don't change any settings).
Remember to move the "SemcGenericUxpRes", "ims" and "chrome customizations" to their respective folders (framework and vendor/app) to avoid FCs
Once you do that, your deodex file is ready to flash, then after that reflash SuperSU and NUTs recovery.
thanks
thanks bro.:laugh::laugh::laugh::laugh::laugh::laugh::laugh:
it is working bro
thanks thanks
and small Dought can i use this empty zip file for future versions like android 6.0
and how to conform my lolipop5.1.1 is deodexed
One question :what does it mean nut recovery???is clockworkmod recovery right?
rameshkotibani said:
thanks bro.:laugh::laugh::laugh::laugh::laugh::laugh::laugh:
it is working bro
thanks thanks
and small Dought can i use this empty zip file for future versions like android 6.0
and how to conform my lolipop5.1.1 is deodexed
Click to expand...
Click to collapse
I'm not sure if this zip will work for Android 6.0 since it's not available to test atm. Let's wait until it's out and see then
To confirm your rom is deodexed, use a file explorer with root acces (es explorer) and navigate to /system/, then do a search for "odex" and you should not find any files.
Cris95 said:
One question :what does it mean nut recovery???is clockworkmod recovery right?
Click to expand...
Click to collapse
NUTs dual recovery is what is used on locked bootloader Z2 phones, it has both CWM and TWRP for you to choose from, just google "NUTs dual recovery Z2" or search the forums here for more details.
thank bro......
ticktock666 said:
see attached file for creating flashable zip.
you need to copy the deodexed version from the SVADeodexerForArtx64 folder (you'll find app, framework, priv-app folder there) just open the zip with winrar, drag and drop folder, do a replace (don't change any settings).
Remember to move the "SemcGenericUxpRes", "ims" and "chrome customizations" to their respective folders (framework and vendor/app) to avoid FCs
Once you do that, your deodex file is ready to flash, then after that reflash SuperSU and NUTs recovery.
Click to expand...
Click to collapse
i did all you said, but after flashing the deodex.zip with the deodexed apk´s inside i get bootloop.
Tried everything but no chance. Always bootloop - damn