[SCRIPT/TOOL] Convert2Dualboot-SD Tool v1.4[Linux/OSX/Android/DOS][6/8]

[RASTAVIPER]

Tried again with new version and nothing changed.
Only noticed during conversion this message : Local entry CRC does not match cd.
But conversion finished without any other message.

Checked also gapps MD5 and its correct, so its not faulty download.

Unleashed from my Revolutionized Desire HD

 

[racks11479]

SCRIPT ERRORS!!!!!!

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.

-RACKS

 

[DizzyDen]

I'm ashamed if I missed something

 

[RASTAVIPER]

Just tried 1.3 version and still getting this error : Zip Warning. Local entry CRC does not match cd.

Also, you have to do something with download server.
Both my phone and tablet cant download with Opera or dolphin from this terracheta site.
Only stock broswer seems to work.

 

[racks11479]

Just tried 1.3 version and still getting this error : Zip Warning. Local entry CRC does not match cd.

Also, you have to do something with download server.
Both my phone and tablet cant download with Opera or dolphin from this terracheta site.
Only stock broswer seems to work.

I'll look into it tomorrow. Thank u for pointing out issues.

Feedback helps with progress

Sent from my NookColor using Tapatalk

 

[leapinlar]

Racks and others, a user on the Q&A forum had a question on your conversion and did not have ten posts to post here. I don't know if you watch that forum, so I told him I would alert the users here. Maybe one of you can help him. His nick is kontam.

 

[RASTAVIPER]

Racks and others, a user on the Q&A forum had a question on your conversion and did not have ten posts to post here. I don't know if you watch that forum, so I told him I would alert the users here. Maybe one of you can help him. His nick is kontam.

This is the error that this user is having during script.
Something about library.

 

[racks11479]

Mkimage error on the Android Script.

Looks like it's another mistake on my end. 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.3a is up for the Android script.

Thanks,
Racks

 

[shumash]

Mkimage error on the Android Script.

Looks like it's another mistake on my end. 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.3a is up for the Android script.

Thanks,
Racks

I tried to use the scripts to convert the newest Mirage 20120518 for primary. Used both DOS and Linux versions. Both produced zips that flashed without errors, but when I tried to boot into them, they failed without warning, and I ended up in the stock emmc ROM. Went back to my old, kludged-up method, and it installed properly.

 

[racks11479]

I tried to use the scripts to convert the newest Mirage 20120518 for primary. Used both DOS and Linux versions. Both produced zips that flashed without errors, but when I tried to boot into them, they failed without warning, and I ended up in the stock emmc ROM. Went back to my old, kludged-up method, and it installed properly.

Dangit

If it's booting into stock, that means the ramdisk isn't being modded correctly. Can you unzip the newly prepped zips to check the date on the ramdisk.img? Also check and see if updater-script and vold.fstab was modded as well?

Not sure what the issue is, did it give you any errors when the srcript was running? I'll do a convert when i get home tonight to try and reproduce the issue. Thanks for reporting it.. hopefully soon all these issues will be ironed out. Sorry guys.

Thanks,
Racks

 

[vejur79]

I used the Android 1.3a script and the gapps-ics-20120429-signed.zip gapps file and tried to update it to the alternate boot. I ended up with a RDBSD_Alt_20120518_gapps-ics-20120429-signed.zip file. I flashed that resulting file and checked the Google Services Framework. The version number is still at 4.0.1-21203.

Am I missing something?

Ron.

 

[racks11479]

I used the Android 1.3a script and the gapps-ics-20120429-signed.zip gapps file and tried to update it to the alternate boot. I ended up with a RDBSD_Alt_20120518_gapps-ics-20120429-signed.zip file. I flashed that resulting file and checked the Google Services Framework. The version number is still at 4.0.1-21203.

Am I missing something?

Ron.

I just prepped that same file on my nook and flashed it. Mine says version 4.0.4-299849.

I know this is a dumb question, but are you using the CWM that is included with the dualbootSD?

 

[RASTAVIPER]

I just prepped that same file on my nook and flashed it. Mine says version 4.0.4-299849.

I know this is a dumb question, but are you using the CWM that is included with the dualbootSD?

Its the same matter that I have posted so many times earlier.
No matter what I can't update also to newer gapps.
And yes I am also using the alternate CWM.

Unleashed from my Nook Color at 1.2G

 

[shumash]

Dangit

If it's booting into stock, that means the ramdisk isn't being modded correctly. Can you unzip the newly prepped zips to check the date on the ramdisk.img? Also check and see if updater-script and vold.fstab was modded as well?

Not sure what the issue is, did it give you any errors when the srcript was running? I'll do a convert when i get home tonight to try and reproduce the issue. Thanks for reporting it.. hopefully soon all these issues will be ironed out. Sorry guys.

Thanks,
Racks

The ramdisk.img date in the scripted zips is 2/28/2008, the date in the Mirage update zip. The one in my successful zip is 3/25/2012. The vold.fstab appears to have been modded properly, i.e. SD card 7, emmc 8, and USB auto. FWIW, pretty much everything but a few selected files, like vold.fstab, bootanimation.zip, powervr.ini, profile, sysctrl.conf, etc. have the 2/28/2008 timestamp in the modded zip. So it looks like it didn't update the ramdisk at the minimum.

 

[racks11479]

The ramdisk.img date in the scripted zips is 2/28/2008, the date in the Mirage update zip. The one in my successful zip is 3/25/2012. The vold.fstab appears to have been modded properly, i.e. SD card 7, emmc 8, and USB auto. FWIW, pretty much everything but a few selected files, like vold.fstab, bootanimation.zip, powervr.ini, profile, sysctrl.conf, etc. have the 2/28/2008 timestamp in the modded zip. So it looks like it didn't update the ramdisk at the minimum.

If you dont mind digging into the script. Could you open up the script with gedit and in the pb () section of the script. Remove all lines that says 'clear'. Then run the script again and youshould be able to see output if u scroll up a bit after its finished. Then post output here?

Thanks

Sent from my NookColor using Tapatalk

 

[leapinlar]

deleted

I was all wet like I suspected, so deleted the comment. Carry on.

 

[DizzyDen]

The ramdisk.img date in the scripted zips is 2/28/2008, the date in the Mirage update zip. The one in my successful zip is 3/25/2012. The vold.fstab appears to have been modded properly, i.e. SD card 7, emmc 8, and USB auto. FWIW, pretty much everything but a few selected files, like vold.fstab, bootanimation.zip, powervr.ini, profile, sysctrl.conf, etc. have the 2/28/2008 timestamp in the modded zip. So it looks like it didn't update the ramdisk at the minimum.

There will only be 4 modified files... that is to be expected... the speed improvements in the execution is that we now only extract and update the files we have to... saving extracting the entire zip file.

We extract, modify and update:
in ROM files:
init.encore.rc in /ramdisk.img
/META-INF/com/google/android/updater-script
/system/etc/vold.fstab

in Gapps files:
META-INF/com/google/android/updater-script
install-optional.sh

so... those files are the ones that should show time and date of update... the others will maintain the date/time stamp of the original ROM or Gapps zip file.

EDIT
For those having problems... please make sure you use option 7 to clear out any older files... the scripts work by sorting the files in modify-for-* folder and attempting to use the last rom and gapps it finds that way.

 

[vejur79]

I just prepped that same file on my nook and flashed it. Mine says version 4.0.4-299849.

I know this is a dumb question, but are you using the CWM that is included with the dualbootSD?

Yeah I'm using the CWM included with the dualbootSD. I tried it again with no luck. I used a text editor to look at script and it seems to be 1.2.

Ron.

 

[DizzyDen]

Yeah I'm using the CWM included with the dualbootSD. I tried it again with no luck. I used a text editor to look at script and it seems to be 1.2.

Ron.

That's because we forgot to change the version number in the header of the script... no worries.

 

[DizzyDen]

The ramdisk.img date in the scripted zips is 2/28/2008, the date in the Mirage update zip. The one in my successful zip is 3/25/2012. The vold.fstab appears to have been modded properly, i.e. SD card 7, emmc 8, and USB auto. FWIW, pretty much everything but a few selected files, like vold.fstab, bootanimation.zip, powervr.ini, profile, sysctrl.conf, etc. have the 2/28/2008 timestamp in the modded zip. So it looks like it didn't update the ramdisk at the minimum.

digging deep into why gapps is being zipped into the ROM... upadte SOON!