• 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

Filesystem Root Contents

12 posts in this topic

Posted · Report post

Hi all, having copiously tinkered with my hudl, I now have extra bits and bobs in the root of my hudl's file system. I'm having a bit of a tidy up, I've managed to remove all the extraneous stuff from the /system folder as I can compare this to the stock system image to work out what's been added, however, I don't know what was original in the root of the filesystem. Could someone provide me with a list of what their hudl has as standard in / ? Thanks!

 

Side note: As I understand it, when flashing with RKFlashtool, flashing the system.img to the correct offset paramaters on the hudls storage copies the contents of the system.img and dumps it into the /system folder. Similarly, the boot goes to /boot and kernel to /kernel and so on? If this is so, where do the extra stock files on the root of the storage come from? Are they not contained by the RKFlashtool rom dump images?

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

nobody willing to just screenshot the list of files on the root directory of their hudl?

Edited by flurry
0

Share this post


Link to post
Share on other sites

Posted · Report post

do the full backup images such as these (containing the system.img, boot.img, kernel.img etc) contain absolutely everything needed to restore the hudl or are there other files needed?

0

Share this post


Link to post
Share on other sites

Posted · Report post

What are you after my friend and I will supply it if I can - looking at your previous posts now......

0

Share this post


Link to post
Share on other sites

Posted · Report post

Working on your request now - goes without saying, if you don't have a copy of the user partition or a backup of it you'll not have a completely 'restored' as was hudl.

0

Share this post


Link to post
Share on other sites

Posted · Report post

Working on your request now - goes without saying, if you don't have a copy of the user partition or a backup of it you'll not have a completely 'restored' as was hudl.

 

so if I have the full backup image and a copy of my user data partition I have a copy of everything on the hudl?

 

Thanks, so much CaptainMidnight, that image is exactly what I was after - massively appreciated!

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

While updating those Linux backup / restore scripts of a previous thread, if you included the user partition, then wiped your hudl and followed the long restore - it was like it was before the wipe.

Including the user partition in those scripts does extended the scripts run time by a big factor though.

Edited by CaptainMidnight
0

Share this post


Link to post
Share on other sites

Posted · Report post

While updating those Linux backup / restore scripts of a previous thread, if you included the user partition, then wiped your hudl and followed the long restore - it was like it was before the wipe.

Including the user partition in those scripts does extended the scripts run time by a big factor though.

 

that makes sense now, thanks! Are the parameters of the user partition known/available?

 

when writing the various images to the hudl does the rkflashtool write the contents of the img or the img itself (which then mounts to the right point?), ie, does writing the system.img to the hudl drop the contents of the img into /system, or does it drop the system.img onto the hudl's nand and then mount it to /system?

 

apologies for the many questions, but I'm not finding much on google to explain how it works!

0

Share this post


Link to post
Share on other sites

Posted · Report post

As far as I'm aware, rkflashtool is just a bit copier/dumper i.e. just like the Linux dd command.

The reason I say that is when you backup partitions you're just dumping data which also includes crud if the partition isn't fully used.

0

Share this post


Link to post
Share on other sites

Posted · Report post

As far as I'm aware, rkflashtool is just a bit copier/dumper i.e. just like the Linux dd command.

The reason I say that is when you backup partitions you're just dumping data which also includes crud if the partition isn't fully used.

 

crud being the unused extra space within each img?

0

Share this post


Link to post
Share on other sites

Posted · Report post

Exactly!

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.