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
Related
Been using Franco's Rom and Kernel and it's been great. However, I like to update to his v.14 kernel. I did the format
1. Wipe
2. Partition, etc...
3. Load v5 Rom
4. Restart
My problem is right here, the warning is to delete the tweaks file and the script file (which I don't have one) in File Manager. I use the OI manager that comes with v5 Rom but it just wont' delete, and I don't want to load the new kernel because of all the warnings, please help :-(...
calculus1918 said:
Been using Franco's Rom and Kernel and it's been great. However, I like to update to his v.14 kernel. I did the format
1. Wipe
2. Partition, etc...
3. Load v5 Rom
4. Restart
My problem is right here, the warning is to delete the tweaks file and the script file (which I don't have one) in File Manager. I use the OI manager that comes with v5 Rom but it just wont' delete, and I don't want to load the new kernel because of all the warnings, please help :-(...
Click to expand...
Click to collapse
it wont delete cause of permissions. I use root explorer for this kind of work. In this particular case i had deleted the nececary scrips from the flash zip and i flashed afterwards. (i had a clean install)
I am trying the clean install as well, can you give the instructions or point me to somewhere where I can read more about this, thanks for your time and effort.
Do I just delete it in the Devoid.Franco v5 zip before flashing and then restart the process (the only file that I can find is tweaks.sh)
Sorry, found the init.d file as well. Would I delete those files in the zip, rezip and then start the process over?
you just delete them from the zip and you flash it as usuall. just dont forget to disable verification check on your recovery or else it will give you error
Sorry, just a newb when it comes to this.
I couldn't delete the two files from the devoid.franco.v5.zip file so I did the following:
1. Extract the zip file
2. Deleted the two files
3. Rezipped the files into a new devoid.franco.v5.zip
4. Load the zip into the micro sd card after all the wipe and partition
5. Disabled Signature check
6. Tried the flash and it said it can't open the zip because it's bad :-(...
This can't be that hard when all the other kernels was easy to install...
calculus1918 said:
Sorry, just a newb when it comes to this.
I couldn't delete the two files from the devoid.franco.v5.zip file so I did the following:
1. Extract the zip file
2. Deleted the two files
3. Rezipped the files into a new devoid.franco.v5.zip
4. Load the zip into the micro sd card after all the wipe and partition
5. Disabled Signature check
6. Tried the flash and it said it can't open the zip because it's bad :-(...
This can't be that hard when all the other kernels was easy to install...
Click to expand...
Click to collapse
Extracting a zip and re-zipping it DOESN'T work. You are not supposed to unzip the file. Just flash the rom, delete the offending files using root explorer, and then flash the kernel.
Sent from my LG Optimus One P500 using XDA App
You should't extract the file and rezip it. It corrupts it when it comes to flashing. I personally browse the zip file with winrar and simple delete the files i need. I also add files to zip this way like apks, ringtones etc
Trying winrar and it seems to work, gone to see if I can finish the entire process. Thanks so much for your time again. In the future, can I send the apps that I want directly into this zip? I can to sue something zipsigner before to get calendar, etc... Thanks again!!!
An alternative way for a clean install:
1: wipe everything
2: flash devoid.franco.v5
3: reboot (to check if everything is ok)
4: reboot into recovery
5: mount /system partition under 'mounts and storage' (clockworkmod)
6: from pc type (with phone still in recovery): 'adb shell'
7: in adb shell, type: 'rm /system/etc/tweaks.sh'
8: in adb shell, type: 'rm /system/etc/init.d/00script'
9: flash franco.kernel.v14
10: reboot
I Hope it helps,
Bye
You're welcome m8.
And yes you can have the apps you want inside the rom this way very easilly. just put them in app folder. I did this with some removed apps like browser and calendar and also removed zeam launcher and used adw launcher (personal taste) I even tried that with frameworks (aka themes) and it worked great
Thanks so much to both of your posts, it's working. One last questions, thought setcpu was already implemented in this kernel, but I don't see it anywhere? Again, thanks again for everyone's time and effort, learned so much today (wife is mad though because we need to do house work, lol, lol, better get going)... She said, "who formats their phone 5 times in 1 month, lol, lol"
setcpu is NOT included, you have to install it.
See first post in franco.kernel thread for the link.
Eh! eh! you are not in Europe, I guess if you have to help your wife NOW!!!
Barcelona-ManchesterUTD right NOW...
oh yes the wifes. my gf gets fustrated like "wtf are roms and kernels?? its just a phone!!! you call people and they call you back" rofl
One last note on setcpu. When i was using last version (2.13), every time i rebooted my phone the settings where gone and had to set them again. I switched to v2.1 and it worked like a charm. Have no idea if that is general issue or only me had it. Just thought i should tell you
Done via editing the zip with rar and all worked smoothly.
Thx all
/W
Hi guys,
Couldn't find the answer to this anywhere but I noticed in the newer releases of busybox there's no 'zip' command anymore. I'm running busybox 1.19 on my Incredible.
I have been using this command to create different bootanimation.zip files from my phone but am wondering if there is an alternative command I can use from within Android. I've tried tar -cvzf but I believe tar archives/compresses the files differently and renaming the extensions to .zip does not work.
Any ideas besides using an actual PC to do what I want to do?
Thanks,
Zebdor
Sent from my Incredible using XDA App
There are apps out there such as AndroZip, that essentially creates zip files.
If you are doing this for an app, there are built in zip classes in Java.
java.util.zip.*;
Edit: Just realized you asked for it to be command line. I will keep looking!
Yeah, I used to use 'zip -0r ...' to zip up a folder but for some reason the busyboxes I've tried downloading don't come with the zip command anymore...
I'm looking through the BusyBox source...
Does it have to be .zip? I mean there are plenty of others to choose from such as tar, gz, bz.
I can't find anything on the website why it is left out.
Best of luck
travmanx said:
I'm looking through the BusyBox source...
Does it have to be .zip? I mean there are plenty of others to choose from such as tar, gz, bz.
I can't find anything on the website why it is left out.
Best of luck
Click to expand...
Click to collapse
I was thinking of using tar and gz but every tutorial I've read says Android requires the bootanimation to be in .zip format uncompressed. I even tried tarballing it as bootanimation.tar but it didn't work...
did anyone ever find an answer to this?
im currently trying to find a portable binary for just zip (or something like busybox that includes zip) because im trying to automate creation of a cwm zip ON an android device during the installation of another cwm zip
iXNyNe said:
did anyone ever find an answer to this?
im currently trying to find a portable binary for just zip (or something like busybox that includes zip) because im trying to automate creation of a cwm zip ON an android device during the installation of another cwm zip
Click to expand...
Click to collapse
This seems to work fine: https://code.google.com/p/zip-for-android/people/[email protected]
I thought I was crazy...
I have surely been missing the zip command too... I just got done downloading and about to reboot into recovery to install...
Zarchiver is a free app in the market that i use to.make boot animation zips and any other kind of zip on my Android device.
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.
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
toknitup420 said:
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
Click to expand...
Click to collapse
It could be missing metadata. Are you starting with this fimware? I can unpack it and locate the files with unique permissions. It may help figure out what is missing. Not using sparse dat is not your issue. set_metadata will work once we track down the problem.
SuperR. said:
It could be missing metadata. Which firmware are you starting with? I can unpack it and locate the files with unique permissions. It may help figure out what is missing. Not using sparse dat is not your issue. set_metadata will work once we track down the problem.
Click to expand...
Click to collapse
Do you want a copy of the current project I have in kitchen. I can upload it to my drive. I just used the zip from the may factory image.
Edit
Wow I just realized that was a link lol. I totally misread lol. Yes I'm using that firmware.
toknitup420 said:
Do you want a copy of the current project I have in kitchen. I can upload it to my drive. I just used the zip from the may factory image.
Edit
Wow I just realized that was a link lol. I totally misread lol. Yes I'm using that firmware.
Click to expand...
Click to collapse
You did not misread, i changed it I will check it out when I get a chance. No need to upload your project.
toknitup420 said:
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
Click to expand...
Click to collapse
Can you try this updater-script to see if it fixes the issue? There are actually 2 attached, with_vendor and no_vendor in case you extracted vendor too. If you replace it in the kitchen, make sure you zip the ROM manually because the kitchen will change it before zipping based on the files you have.
SuperR. said:
Can you try this updater-script to see if it fixes the issue? There are actually 2 attached, with_vendor and no_vendor in case you extracted vendor too. If you replace it in the kitchen, make sure you zip the ROM manually because the kitchen will change it before zipping based on the files you have.
Click to expand...
Click to collapse
so i cant zip manually because i dont have perms for one file in system. heres a pic. ill just add the script into an existing zip i built from kitchen.was
update
so i was able to move the script into the correct location and zip up the file. however when it flashes the updater script is somehow becoming merged with the original instead of just the new script. it still shows the original script text when flashing.
toknitup420 said:
so i cant zip manually because i dont have perms for one file in system. heres a pic. ill just add the script into an existing zip i built from kitchen.was
update
so i was able to move the script into the correct location and zip up the file. however when it flashes the updater script is somehow becoming merged with the original instead of just the new script. it still shows the original script text when flashing.
Click to expand...
Click to collapse
I will build a rom and upload for you to try. Are you building with vendor included or without?
SuperR. said:
I will build a rom and upload for you to try. Are you building with vendor included or without?
Click to expand...
Click to collapse
I built it without. Do you recommend to build it with vendor. Should that file be root like that. The one that's in that pic I sent.
toknitup420 said:
I built it without. Do you recommend to build it with vendor. Should that file be root like that. The one that's in that pic I sent.
Click to expand...
Click to collapse
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
SuperR. said:
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
Click to expand...
Click to collapse
OK I'll try it now. Good looks.
SuperR. said:
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
Click to expand...
Click to collapse
it flashes with no errors but it wont boot past splash screen.
toknitup420 said:
it flashes with no errors but it wont boot past splash screen.
Click to expand...
Click to collapse
Please try marlin n2g47o test rom 2:
https://www.androidfilehost.com/?fid=745425885120737663
SuperR. said:
Please try marlin n2g47o test rom 2:
https://www.androidfilehost.com/?fid=745425885120737663
Click to expand...
Click to collapse
flash went through without error but still boot looping at splash screen.
toknitup420 said:
flash went through without error but still boot looping at splash screen.
Click to expand...
Click to collapse
Moved to a dedicated thread as this issue is only about Pixel.
I will do more thinking on what could be causing it. I was pretty sure the last rom would fix it but clearly I was wrong lol
SuperR. said:
Moved to a dedicated thread as this issue is only about Pixel.
I will do more thinking on what could be causing it. I was pretty sure the last rom would fix it but clearly I was wrong lol
Click to expand...
Click to collapse
Lol good stuff. Keep me posted. I'll test whatever you throw at me.
toknitup420 said:
Lol good stuff. Keep me posted. I'll test whatever you throw at me.
Click to expand...
Click to collapse
Here is a new approach so I don't have to keep uploading full roms. Use the kitchen to extract the last rom I sent into a new project. In your file manager, navigate to your project directory and delete the 00_project_files directory. Extract the attached file into your project directory. Build rom with kitchen. Test rom.
Next time, you won't need to extract the rom zip again, just replace the 00_project_files directory.
edit: forgot to mention, after replacing the 00_project_files directory with the one in the zip, change perm types to something else, then back to set_metadata. Then build your rom
SuperR. said:
Here is a new approach so I don't have to keep uploading full roms. Use the kitchen to extract the last rom I sent into a new project. In your file manager, navigate to your project directory and delete the 00_project_files directory. Extract the attached file into your project directory. Build rom with kitchen. Test rom.
Next time, you won't need to extract the rom zip again, just replace the 00_project_files directory.
edit: forgot to mention, after replacing the 00_project_files directory with the one in the zip, change perm types to something else, then back to set_metadata. Then build your rom
Click to expand...
Click to collapse
flashing seemed to hang at setting perms. but it eventually went through. still looping at splash screen though.
toknitup420 said:
flashing seemed to hang at setting perms. but it eventually went through. still looping at splash screen though.
Click to expand...
Click to collapse
Can you send the original updater script that booted but did not have bluetooth?
SuperR. said:
Can you send the original updater script that booted but did not have bluetooth?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B4VEhClrJEWpNnJNVUJTRFV4ODQ/view?usp=sharing
https://drive.google.com/file/d/0B4VEhClrJEWpTmlYWC1CQ0s3LVE/view?usp=sharing
thats the binary and the script. i converted script to binary when i was building rom. this rom boots and runs ok other than bluetooth. its not completely stock though. i have my modded framework settings and system ui apks in there. but they are all signed so i dont think they would mess with anything.
toknitup420 said:
https://drive.google.com/file/d/0B4VEhClrJEWpNnJNVUJTRFV4ODQ/view?usp=sharing
https://drive.google.com/file/d/0B4VEhClrJEWpTmlYWC1CQ0s3LVE/view?usp=sharing
thats the binary and the script. i converted script to binary when i was building rom. this rom boots and runs ok other than bluetooth. its not completely stock though. i have my modded framework settings and system ui apks in there. but they are all signed so i dont think they would mess with anything.
Click to expand...
Click to collapse
Did you convert the new one you just tried after swapping 00_project_files to update-binary? If not, try it please. If so, try without please
Instructions:
https://jolla.com/sailfishxinstall/
Download:
http://images.devaamo.fi/sfe/suzu/
thanks to all the guys that worked on this port.
Kernel source:
https://github.com/mer-hybris/android_kernel_sony_msm
This make_ext4fs works for flashing on macOS
For some reason with this build the system-icons vanish for me after restarting the device once :/
I had much better results using this build.
Also by default (at least with the image I linked) only two of the 6 cpu-cores are enabled. To fix that one must add this under the init-section of the /init.loire.pwr.rc file and reboot (All credit for this go to abranson from the #sailfishos-porters irc).
Thanks for this port! are you planning to continue building for Xperia X or is a test build before official release?
Enviado desde mi F5121 mediante Tapatalk
keep going till then, also ive updated the above link
how flash it?
FuLiterary said:
how flash it?
Click to expand...
Click to collapse
read the first post
FuLiterary said:
how flash it?
Click to expand...
Click to collapse
make sure when you are flashing sailfish support only F5121 and does not support sdxc
Hello, friend! I am a Chinese user, I do not understand the tutorial, there is no mor
Jozinek said:
so only Linux or MacOS too?
Click to expand...
Click to collapse
Flashing works on macOS too. You just need to use the make_ext4fs I linked instead of the one linked on top.
janeliang34 said:
Hello, friend! I am a Chinese user, I do not understand the tutorial, there is no mor
Click to expand...
Click to collapse
extract the tar, open a terminal inside the extracted folder and run ./flash.sh
One question. Zip file with AOSP should be moved intact or only vendor folder from inside it?
Seems it has to be whole .zip.
Jozinek said:
i never make something like this in MacOS (i have Macbook Air, but also with Windows), can you write step by step how to make it. This is something totally new for me (i flashed hundreds of XPERIA smartphones, i have Emma tool, but never try this...)
Click to expand...
Click to collapse
Sure thing
First of all your bootloader needs to be unlocked. I'm assuming you already did that but if not you should read about backuping your drm-keys because otherwise they can't be recovered after unlocking your bootloader unless you do that.
If you don't have fastboot installed yet follow this guide.
After that download the first file linked at the top of this thread.
Unpack the archive (if you can't open it I recommend "the unarchiver" from the app-store).
Place both this file and the zip from the third link at the top in the unpacked folder (in the path where the flash.sh is). Don't unpack the .zip file!
After that open a terminal and navigate to your unpacked folder (if you don't know how to do that google for "terminal tutorial mac").
Run
Code:
chmod +x flash.sh
chmod +x make_ext4fs
to mark the flash-script and the make_ext4fs-file as executable.
Boot your device into fastboot mode (hold volume up while it's turned off and plug in your usb-cable) and finally run
Code:
./flash.sh
to install sailfishOS on the device.
If there is a "hybris-recovery.img" file in the directory (can't quite remember if that's the case with this build) also run
Code:
fastboot flash recovery hybris-recovery.img
to install a sailfishOS specific recovery.
After that you can reboot your device and enjoy Sailfish OS
@Jozinek
You didn't unpack the .tar.bz, inside are all files needed to flash. Than You have to move make_ext4fs, AOSP.zip and flash.fs into created (by unpacking) folder and start/cd Terminal there.
Jozinek said:
Edit3 - it worked now, it was bad make_ext4fs, thanks all of you
Click to expand...
Click to collapse
So that means you are doing a review on YouTube, right?
Friend, is there a tutorial for Windows installation? To be more detailed, this is my first contact
janeliang34 said:
Friend, is there a tutorial for Windows installation? To be more detailed, this is my first contact
Click to expand...
Click to collapse
Right now there is no windows support. The final build (which will be officially sold by Jolla) will make windows-installation possible.
If you know your way around cygwin you could probably get it to flash using windows (other than the flash.sh script there's nothing *nix-exclusive).
Is the rom stable enough for daily use ? and is Alien Dalvik available in this rom to run Android apps ?
no android dalvik or any software that needs license, this version is just community version like aosp without play store.
when flashing there's error make_ext4fs: no such file or directory, when i use the second one there's error: wrong exec format