• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.
Sign in to follow this  
Followers 0

[HELP] Cannot Deodex ICS Stock ROMS with DSIXDA Kitchen

14 posts in this topic

Posted

Okay, so I downloaded the stock images from google and i've tried and tried and when I come up to load the system.img file in ext2read it will not show up at all. i select the image but the program does nothing. any ideas what I might be missing?

Windows 7 64bit

Java JDK 32 and 64bit (dont ask)

dsixda ver. 181

thanks!

0

Share this post


Link to post
Share on other sites

Posted

ext2read is for ext2 images, the GN has ext4 but not one compatible with the dsixda kitchen. I'm currently trying to work out what to do but no one really wants to help :(

0

Share this post


Link to post
Share on other sites

Posted (edited)

I don't use Windows, so you may need to set up a VM running something like Ubuntu to sucessfully do the update.

The images from the google update are a 'Sparse EXT4" volume. You need to use utility called simg2img which can be found within ext4_utils.zip (attached to the following)

http://forum.xda-dev...d.php?t=1081239

Download the sources, and compile them by using 'make'

Then extract the system.img from the Google Update to the folder where the simg2img binary has been compiled, and type:

#./simg2img system.img sys.img

This will create a sys.img file (around 640MB), copy this new file (aswell as the boot.img file extracted from the update) into dsixda/original_update and run the kitchen :)

As a quick note, Don't run simg2img on boot.img, it's not needed!

Edited by PaulW21781
0

Share this post


Link to post
Share on other sites

Posted

Top man, think that's where I was going wrong yesterday. Will get onto it with my VM next week

0

Share this post


Link to post
Share on other sites

Posted (edited)

I already have a fix for this issue in the Android Kitchen but have not checked it into GitHub yet. ;)

Or rename file to system.img.ext4 before extracting, and then run kitchen.

-dsixda

Edited by D I
0

Share this post


Link to post
Share on other sites

Posted

Thank you and awesome job dsixda!!! I will give that a try as well. And to others, thank you as well. PaulW thanks for the quickfix for the facebook text on xda. not that I use facebook much but eh.

I want to be in ubuntu right now but my desktop is down right now. and my laptop is win7 64bit.

Again Thank you everyone!

0

Share this post


Link to post
Share on other sites

Posted

dsixda you legend! :D

0

Share this post


Link to post
Share on other sites

Posted

Well, using the above tips I've got a ROM built. Happy days you'd think? WRONG!

ROM won't flash, getting 'error status 0' - anyone know how to sort it? I think it's to do with the updater-script but don't know for sure

0

Share this post


Link to post
Share on other sites

Posted

I got the same error too. thats okay its progress in my eyes lol

0

Share this post


Link to post
Share on other sites

Posted

It's down to the updater-script and also where certain parts of the ROM now need to be as we no longer have separate locations for internal and external files. It's all a bit confusing!

0

Share this post


Link to post
Share on other sites

Posted

I'll just be waiting for this Git push hopefully if that is what dsixda was intending :-D. I could what I use to do and just copy that stuff and use someone else's updater scripts.

0

Share this post


Link to post
Share on other sites

Posted

Basically, the su and busybox binaries needs to go to /xbin as opposed to /bin and then use someone's updater-binary/updater-script and it seems to work

0

Share this post


Link to post
Share on other sites

Posted

one more noob at building source question...

Can you download Google apps source code to compile into your own builds yourself or no?

0

Share this post


Link to post
Share on other sites

Posted (edited)

I've been trying to find it myself but I can't find anything from Google directly

dsixda has updated the kitchen but it's still wrong, the kernel doesn't flash properly and I kept boot looping once I got the updater-sript working so I'm gonna try again in the new year and make my desktop a complete linux box as opposed to using a VM

Edited by EddyOS
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.