[Q] Interchangable Data Images? - HD2 Android Q&A, Help & Troubleshooting and Genera

I'm using an android build X, but i wanna try out android build Y, but can I just drop X's data image in Y? so I can keep my apps/customizations etc...

I´m with you...same question here

No. The data image will be specific to that build, so it will cause problems if you use it with other builds. When upgrading a build it is usually okay, but still not 100% safe.
Look at Titanium Backup for backing up your system, apps and assoicated data. It'll re-install everything for you with 1 click (in the paid version - lots of clicks in the free version!!)

True, it's not guaranteed to work out. But on the other hand, what harm can be done? Just back up your SD before you try.
It's probably not a good idea to copy your data.img when switching from, lets say, a CM6 build to a Desire HD build. But copying data image never failed for me.

Related

Undo apps2sd?

Hi all...
I've been getting a lot of suspicious errors recently (force closes and app shortcut names disappearing) and I'd like to go from apps2sd back to just a normal setup with my apps on the internal phone storage.
Can somebody please verify that the instructions here are up to date? I'm a little nervous about wiping my data (or bricking my phone).
http://wiki.cyanogenmod.com/index.php/Apps2SD
Also, can somebody tell me whether doing this will wipe out the (single) app I paid for from the Marketplace? If so, can I redownload it, or will I need to pay for it a second time?
I originally got apps2sd set up by using the recovery ROM prior to flashing Modaco's custom ROM v1.1.
The easiest thing to do would be to load the new RA 1.5.1 recovery image.
Then boot into it.
Go to Partiton SD
Select FAT EXT3 SWAP
and then set the partition sizes of EXT3 and SWAP to 0
Is there a reason you want to do this???
This runs a very very minimal chances of bricking your phone. The other method on that Wiki page has more potential to get you in trouble.
Did see the market place question.
There is a method laying around somewhere to copy all of your apps back to the phone instead of loosing them. Restoring a Nandroid backup would likly put them all back into the /apps/ directory sd card or not. apps2sd just changes the location of that directory really.
But the market does keep track of your google account and what apps you purchase, you wont have to re purchase (maybe on a totaly new handset).
hope my jiberish has made sense
jashdlfjasdhfjablgjkasgjlkasfhlajshf
At first I was interested in the whole apps2sd process, but have yet to implement it on my rooted, Fresh 1.0 Hero since so far, I haven't really seen a need for it.
But if you were to 'turn on' apps2sd and then decide later that you don't want it, there's a possibility of bricking?? Although I assume you can always reflash the RUU if something like that were to happen? Hopefully?
Think I'll stay away from the whole offloading applications thing for awhile.
mkhopper said:
At first I was interested in the whole apps2sd process, but have yet to implement it on my rooted, Fresh 1.0 Hero since so far, I haven't really seen a need for it.
But if you were to 'turn on' apps2sd and then decide later that you don't want it, there's a possibility of bricking?? Although I assume you can always reflash the RUU if something like that were to happen? Hopefully?
Think I'll stay away from the whole offloading applications thing for awhile.
Click to expand...
Click to collapse
The possibilities of bricking the phone are very slim, but they still exist. If a phone is truly a brick, not even RUU can help. RUU has to be able to detect the phone is there in Windows, so if its beyond that RUU is useless.
Nothing to worry about as long as follow the *usually* very well written step by steps across the interweb.
If it makes you feel any better I have only heard of one or two people to brick the Hero. Most things are recoverable.
Yeah, sorry, I didn't expect it would brick the phone so much as badly mess it up - like if it expects to run apps from the SD card and they aren't there I could see the phone being tough to use as a phone, but it wouldn't really be "bricked" in the sense of not responding to user input at all.
As far as why I want to do this, I haven't really seen a huge need for apps2sd yet, and when I was recently helping an app developer to debug their app it was just one more weird variable that seemed like a possible source of problems. I'm also hoping to start developing apps myself soon, so having a more vanilla phone seems like a good idea. (I also was influenced by the Fresh ROM apps2sd rant, to be honest.)
Anyhow, thanks for your replies. I'll probably repartition the card from RUU and then restore from Nandroid at that point. Will a repartition wipe the card filesystems out, or is the partitioner smart enough to preserve the existing data?
What I did is RUUed back to 1.2, OTA updated to 1.6
Flashed to the 1.5.1 image
(At this point I went to mess with the partitions and there was no ext)
Flashed to Fresh 1.0

[Q] How to Change Between Android Roms?

I have been using shubCRAFT CM6 for almost 4 days now. And everything is PERFECT "seriously.....everything" (including battery life) I am using Chuckydroidrom and im curious to know if i can switch android Rom while keeping my data (sms etc) if i can switch to try out a different android rom. What is the proper way to do it?
[Q] If "everything is PERFECT "seriously.....everything" (including battery life)".... why would you want to try another build?
seriously if you are having NO problems then stick with it until the first actual ROM is available to flash.
to 'answer' your [Q]..... I'm not sure you can backup and transfer user data between these different builds/ports.
IF you have achieved perfection already, you would be silly to mess with it anyway IMHO
I know this (below) refers to upgrading mattc 1.4 to 1.5 but it MIGHT also apply to upgrading any build to any other build without losing user data.
backup and try it?
http://forum.xda-developers.com/showpost.php?p=7541674&postcount=1438
thesweeney said:
I know this (below) refers to upgrading mattc 1.4 to 1.5 but it MIGHT also apply to upgrading any build to any other build without losing user data.
backup and try it?
http://forum.xda-developers.com/showpost.php?p=7541674&postcount=1438
Click to expand...
Click to collapse
before trying, save the data.img file to ur pc... coz if anything goes wrong, u can go back to ur original build and jus copy the file back(evrything will b back to normal)
jjblaster3 said:
before trying, save the data.img file to ur pc... Coz if anything goes wrong, u can go back to ur original build and jus copy the file back(evrything will b back to normal)
Click to expand...
Click to collapse
my question is i am usin 512mb data.image i got 4gb data.image also... How can i change it with all my previous data... I need the bigger storage with older files on 512mb data.image... Any help here??
I copy the entire SD CARD to a file... Delete/Format/Copy New. Then I add the. Apk's, Media (Pictures, Sounds, etc). Done.
---
Sent from my DROID HD2 with XDA.
victorbd said:
my question is i am usin 512mb data.image i got 4gb data.image also... How can i change it with all my previous data... I need the bigger storage with older files on 512mb data.image... Any help here??
Click to expand...
Click to collapse
I need to know this as well been searching around for it and have gotten no answer
Sent from my HTC Desire using XDA App
U can try to back everything up n when you put the new build copy the "data.img" and you should have all your apps and stuff, and it'll boot faster on the first boot.
Sent from my HTC HD2 running DarkStone HD2Froyo v1

Nandroid and Restores

Hi Guys,
I recently bought my Nexus one this past weekend. I'm coming from a Windows Mobile fan(boy) perspective of many years. Not the hugest linux fan, but at least the base level of Android control is a menu and not "dev cmd etc" command line stuff
I like the Nexus one so far. I tried CompanionLink/gSyncit/Nitrodesk Touchdown/Android-sync(Alpha)/Remember The Milk etc, and they all don't sync Outlook very well..so I'm happy to keep my Winmo phone for its use for that, which is excellent and easier to type imho for that kind of stuff within a windows environment. Kind of like a Palm pilot.
As for Apple. I'm proud to say I've never touched one for years, until yesterday. I *had* to get my father a slidey smartphone as a gift, because they're awesome to see and navigate. Since he's not a big data guy I couldn't justify a nexus one, so a used iphone 3G fit the bill.
Hope i don't have to touch it too much tho!
Anyways, I thought I'd give you guys some history on where I'm coming from as an introduction and seeing as I havent posted on here in a few years.
So..regarding my questions:
*Nandroid backups Question
- A nandroid-ext backup will not occur, and will display the ADB Error if you don't actually have an extended partition on your SD Card, correct?
I was trying to do an Nandroid+ext backup, because noobishly i thought it just meant it would backup everything. It didn't work, and neither did the "plug it in the charger tricks" etc, or check if you have enough sd space. So I figured it was because i didnt actually have an extended SD partition. Stock 4gig micro SD btw.
A NAND backup worked after that.
- How do I check if my SD card has an extended partition btw?
*Sdcard/Nandroid folder Question
Are nandroid backups saved here in a chronological order?
Meaning
/first directory asfldkjsdafjs/
/second directory aslkdfjljds/
First is my stock rom backup?
Second is my Cyanogen backup?
Say I do a third backup (it appears third right)? Will it be my Cyanogen backup *plus* all my added stuff I've done since then? Like widgets, contacts, email account setups?
*ROM Recovery
- So as a noob I'd like to play around a bit. But I'd also like to populate my phone with backgrounds (sd card), contacts, ringtones (sd card), Apps (sd and main mem) etc.
Say I want to move from my current rom (cyanogen 6) to say MUIMUI (sp?) in a week. When I goto Bootloader recovery and select the Muigungui.zip, will it still keep the phone "mine" on restore?
Thanks a lot for your help guys! I hope to join the Nexus One discussions now too after this my first post!
Your Nandroid backups are named by date and time of your backup.
Every backup you make, backups ALL user-accessible partitions on the phone. That includes pretty much EVERYTHING, both system (ROM) and data (everything else). All the rest of your questions have answers logically derived from this statement, please use the required logic.
Your SD card doesn't have anything unless you made it - which is obviously not the case, or previous owner made it - which is also obviously not the case, since you had stock ROM.
Thank you Jack.
I understand better now.
On looking at my sd folder structure, I see:
sdcard/HT096P800012/BCDES-date-4 numbers
Does the HT096P800012 subfolder stay the same, or does nandroid add more HT subfolders in time. (just a curiousity question)
In the 4 numbers part, if I did two backups on 201001103, does the higher number indicate the most latest backup by the logic you describe?
also, some backup folders have nandroid.md5 as a file and some don't. What is that?
Nerdy questions I know. I do thank you for your help?
(PS: If I update my radio with a new one, that doesn't affect my phone proper right?)
The upper folder stays the same - it's the name of your device.
4 numbers are hours and minutes
nandroid.md5 is MD5 sum of the backup, for verification. Not needed for restoring, AFAIK.
Radio doesn't affect your phone in any bad way, as long as it's compatible with your OS (radios for Eclair were different from radios for Froyo), and as long as you're flashing it correctly, without removing the power from the phone when it's in process of flashing.
Thank you so much!

Help with increasing phone internal storage / Data.img size

I am currently running Superram 1.5 and am trying to increase the "internal" storage of the phone. I have skewered the forums and I understand this involves increasing the Data.img size beyond the initial 256mb compaction. Using TopoResize I have resized my data.img to 1.9 GB, however, i still had access to only 256 MB. I reinstalled Superram 1.5 and tried again with a fresh data image and also failed.
Can someone point me in the right direction, please?
Is there an XML i am to edit or something so the system recognizes the change?
App2SD just isn't cuttin it.
Much thanks to anyone who can help.
Well once the data img is used I don't think you can simply just enlarge it, it has never worked for me that way.. The only solution I can think of, is for you to get a new data image, a bigger one than the one you currently use, and restart your rom with that data img. You can find lots of Build threads with blank data images in them, eg. JDMS/MDJ. If you want to back up stuff, use titanium backup from the market.
data image resizing
Firstly, that should read "scoured" lol -not skewered. And "compaction" should read capacity. Sorry, was trying out swype with XDA App.
Now, more impotently. When you say "restart your rom," you mean to just substitute one image file for another in windows and restart superRAM, correct?
I will not have to reinstall SuperRAM 1.5?
Also, since superram runs off the RAM of the device, will using a image file from a different build cause a problem?
Finally, has anyone out there increased there Image file in size via TopoResize and had success? Was it before the initial launch of your android build or after?
Any help would be much appreciated. Thanks all
Kailkti said:
Well once the data img is used I don't think you can simply just enlarge it, it has never worked for me that way.. The only solution I can think of, is for you to get a new data image, a bigger one than the one you currently use, and restart your rom with that data img. You can find lots of Build threads with blank data images in them, eg. JDMS/MDJ. If you want to back up stuff, use titanium backup from the market.
Click to expand...
Click to collapse
I big to differ. It can be increased. I used to do that during my android SD days.
@OP, you haven't scoured "a lot" yet. Search for datai.img maker, it can resize and create data.img.
Sent from my HD2 Droid HD using XDA App
Issue resolved
Issue resolved.
In the interests of others who may encounter this problem, here is the solution.
Simply get titanium backup and back up all your apps and info, then find a 2GB image from another build and substituted the old image file (data.img) with the new image file (renaming in appropriately) and used titanium backup to restore mostly everything. Titanium backup does a very good job restoring, even Astrid tasks returned, yay.
I originally didn't what to attempt this because SuperRAM is a unique build in the way it runs but there seems to be no issue.
One thing did come up, however.
I attempted to use a 4GB image as a replacement at first and that did not work.
Something about it being too large.
I read someplace that android has a difficulty with image files larger then 2 GB, can someone confirm?
Resize
@Jose - I have tried using toporesize, It seems to increase the size of the data.img but only allow me to use the original 256MB. End result is ineffective.
thedarklion said:
@Jose - I have tried using toporesize, It seems to increase the size of the data.img but only allow me to use the original 256MB. End result is ineffective.
Click to expand...
Click to collapse
Sorry but I did not suggest toporesize but data.img maker.
Sent from my HD2 Droid HD using XDA App
jose makalolot said:
Sorry but I did not suggest toporesize but data.img maker.
Sent from my HD2 Droid HD using XDA App
Click to expand...
Click to collapse
Easy enough mistake to make, but toporesize is data.img maker. To OP (and for posterity's sake), I don't know if you tried it but if you tried making a new data.img using toporesize/data.img maker, you "should" have achieved about the same effect. Glad you got this solved though.
Hey Guys. How are you toady?
I come here with new problems! Probably this thread is solved but i got problem with Toporesize.
Anyway I solved why my Android crash all the time! Was the sd and now I installed few games but I will be glad to install Chainfire also but no way to go true because I do not have storage enough.
I try to use toposize to resize my data.img (inside i have many app and I did a backup) but I got this error, see pic.
If I make the fresh data.img no problem, but the Android do not turn on with "new" data.img, i looking just to resize mine without compromise it.
someone know how to do it?

[Q] Updating Builds?

Hi all,
I've been lurking on these boards for sometime, taking in lots and lots of info. I have to say first of all that this place is great. Thanks to all the devs and hard working individuals who make our devices unique (esp. the HD2)
To get to the point, I have a TMOUS HD2 and had xbmod's WP7 and android on sd dual booting. all was running smooth (after A LOT of mistakes) and I vowed never to touch it again...well that didn't happen because I wanted to upgrade to xbmod's NoDo update. I read another thread on here that said you can backup partitions from the SD card to another hard drive, then copy them back to restore everything, but that did not work for me at all.
So the question is, is there a way to update between similar builds (in my case, xbmod 1.04 to 1.10) without losing data/apps/etc. I know that since it's on NAND it'll be tougher than SD Android but I figured I would ask. While we're on the subject...is anyone trying to develop running WP7 on SD? That'd be sweet. Thanks!
I would love to just update my rom too but I guess that is not possible for our HD2 as of yet or else everybody would be doing it. As from what I understand is that all your apps that you have downloaded from the market gets repopulated. Apps that were sideloaded are lost, but I believe if you search you can find that one person who made an app to automatically re-install all your apps once flashed to a new rom. As far as settings and other stuff you would have to redo them.
soapbox23 said:
Hi all,
I've been lurking on these boards for sometime, taking in lots and lots of info. I have to say first of all that this place is great. Thanks to all the devs and hard working individuals who make our devices unique (esp. the HD2)
To get to the point, I have a TMOUS HD2 and had xbmod's WP7 and android on sd dual booting. all was running smooth (after A LOT of mistakes) and I vowed never to touch it again...well that didn't happen because I wanted to upgrade to xbmod's NoDo update. I read another thread on here that said you can backup partitions from the SD card to another hard drive, then copy them back to restore everything, but that did not work for me at all.
So the question is, is there a way to update between similar builds (in my case, xbmod 1.04 to 1.10) without losing data/apps/etc. I know that since it's on NAND it'll be tougher than SD Android but I figured I would ask. While we're on the subject...is anyone trying to develop running WP7 on SD? That'd be sweet. Thanks!
Click to expand...
Click to collapse
there is a way of backing up the data for the appps but not the apps them selves, if you wait for a week there should be a backup utility that may work
im not talking full rom backups, i know they are there, im talking app and data backup....maybe will know soon
Any movement on this data backup scheme?
ojaidave said:
Any movement on this data backup scheme?
Click to expand...
Click to collapse
aye its working fine, its in beta just now, i dont think him made a public release yet
it backs up all the DATA from each app, it doesnt however backup the apps them selves, so you would do the following
run the backup
flash your device
install all the apps you want
restore the backup
it does not backup SMS
i made a thread about doing this manually which works as well, but the app makes it a lot easier.
http://forum.xda-developers.com/showthread.php?t=1082343
Haven't heard anything...still waiting also want my Mango already!

Categories

Resources