Database Users

copy my rom to another phone

I've searched a dozen different ways to try to read up on this but can't find a thread, I don't want to make a custom rom just copy mine as setup to another epic. If this is easily found could someone just point out the correct search terms. I thought to put this in development but the question seemed to general.

kiab115 said:
I've searched a dozen different ways to try to read up on this but can't find a thread, I don't want to make a custom rom just copy mine as setup to another epic. If this is easily found could someone just point out the correct search terms. I thought to put this in development but the question seemed to general.
Click to expand...
Click to collapse
About the only way I could think of doing so would be to go into your clockworkmod folder and copy the backup you have there and move that to the same folder of the other phone and try restoring that. Not sure if it would work being the google accounts/contacts and whatever else.

Just make a nandroid backup. Take the sd card out of the original epic, root your new epic using one click 3.0.0.6, boot into clockwork And then click on backup and restore and restore the nandroid backup you made. Not sure if it'll work, but I would assume it would.

It should work, you may hit an MD5 mismatch and you'd have to copy the MD5 file from a backup on the new phone to the old backup but it will probably be fine.

And make sure you flash a kernel that is ext4 compatable!
Sent from my SPH-D700 using XDA App

Thanks for the reply's, I did try to take the backup folders (3 in all) and copy them to the new phone, but I did get an md5 mismatch. I need to do this for 30+ company phones so I'm looking for the easiest way to get all the apps and layouts we want to each phone.

Lol, I think you better start changing MD5 instead of posting. Thats a lot of phones!!

Do a nandroid backup and backup everything using my backup root and wipe then put sd in new epic flash cwm3 let it convert to ext4 if that's what you were on otherwise use cwm2.5 and restore the system from cwm only boot up into system go to market log in download my backup root and restore all with that. If it can't find ur backup it sometimes makes an "SD" folder on the sd card itself
Edit: if md5 is mismatched just use any rom zip like srf or bonsai as the system backup is basically just a rom the mybackuproot holds all the app data and phone data
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app

qbking77 said:
Just make a nandroid backup. Take the sd card out of the original epic, root your new epic using one click 3.0.0.6, boot into clockwork And then click on backup and restore and restore the nandroid backup you made. Not sure if it'll work, but I would assume it would.
Click to expand...
Click to collapse
This is how you do it. Yes and like mentioned, flash a EXT4 kenel

Make an odin tar... way easier not to mention quicker on a mass scale, and more reliable. I made a post detailing how.
Sent from my SPH-D700 using XDA App

chris41g said:
Make an odin tar... way easier not to mention quicker on a mass scale, and more reliable. I made a post detailing how.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I read threw those post to see if anyone suggested this,atleast it didnt get to a couple pages...
+1 on the odin.tar,way easier.
Sent from my MyFrankenstein EC05OCE using XDAP App...

Transferring Nandroid Backups

I have a problem. I deleted a few apps that i can't seem to install or get back, even if i download the apks and such. So i was wondering, if someone provided me with their stock nandroid backup, would it work on my Evo? I tried flashing a stock ROM but it didnt work, with the files i needed still missing, and I'm desperate to just have a completely stock nandroid backup. Anyone have any idea about this?

You can't (or really shouldn't) use a nandroid from a different phone. Why didn't a flash of a stock rom work? What apps are you trying to install?
We're comin from a pure power source.

So you can't take the apk files and use ES file manager and set it to root priv and mount permissions and install the apks that way from your sd card.

You can restore nandroids from other phones but not recommended. I did it from my old phone to my new one.
To make it work.
1. Make nand of your phone
2. Make nand on phone you want to use
3. Copy nand files over the top of the nand made on your phone.
4. Restore nand on your phone with modified files.

make sure you don't backup wimax on the source phone.

I can't install Facebook for sense and HTC peep
Sent from my PC36100 using XDA App

Wouldn't it be much faster to flash a new rom and start over? If not faster def. safer, less chance of screwing up Wimax

I've tried flashing stock rom and fresh rom, both times these apps didn't show up, and when I try to install just the apk, it just says "application not installed "
Sent from my PC36100 using XDA App

I used to move my backups between Hero phones with no issues

ronnienyc said:
I used to move my backups between Hero phones with no issues
Click to expand...
Click to collapse
Your hero didn't have wimax now did it..........
Sent from my PC36100 using XDA App

You can easily delete wimax.img and remove its line from nandroid.md5 and you should be fine. As long as that img is gone, your wimax will be safe.

Find a copy of root explorer... using that, copy the apks that you want to your system>app folder ( your system will have to be mounted rewritable) once the apks are in place, change their permissions to resemble other apks in the folder... once you do that, reboot your phone

Use Amon RA recovery and uncheck wimax

Warning - do not rename Backup folders!

so i made a backup via CWM recovery and, to recognize the backup, i renamed the folder to the name of the ROM... when i tried restoring it, i got a size mismatch error... good thing i made a backup of all of my sdcard, including the original name of the folder, and the restore worked again
SO PLEASE! do *NOT* rename the backup folder!!

and this is news because....?
Sent from my HTC Vision using xda premium

androidcues said:
and this is news because....?
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
because i didn't see someone doing it... so i think its new...
—————
|RIROZIZO|
—————

I agree thanks for the heads up. I'm sure there are those that don't know this. I found out the hard way monthes ago.
Sent from my Mikes HTC G2 with Google using xda premium

I didn't know this either. Surprising that this isn't more widely known. Learned this afew months ago by mistake. Never thought of making a post though.
Koodos!

Uh..duh
Sent from my HTC Vision using xda premium

Actually, here's the deal
You CAN rename backups. I do it all the time. What you CANNOT do is add spaces.
My_Rom <----works
My Rom <-----will fail
I usually use camel casing (camelCasing). I've seen people with this problem in a few other phone forums and just happened to stumble on this
OP, if you rename your backup to one that has no spaces, then you should be alright!
Hope I helped!

i didn't try without spaces, but could a space make the md5sum different? i thought just renaming the thing changes the md5sum

Riro Zizo said:
i didn't try without spaces, but could a space make the md5sum different? i thought just renaming the thing changes the md5sum
Click to expand...
Click to collapse
Nope, the md5sum is stored in a .txt file in the backup folder and doesn't ever change (even with the name). If you change the .txt file in any way it'll probably break the back up. I'm not sure the logistics behind it, but spaces break something that removing the space will fix.

A couple things.. The spaces are because of the file reader cannot register the new tokens, some programs (windows and most OSs) are completely fine with this, however some just don't have he exception to deal with it. As for changing the .txt file with the md5, that wont actually break the backup, but CWM will think that it is cause they don't matchup

Why not just use 4ext? They name the backup for you, very nice recovery.

[Q] blobs in clockworkmod folder?

Hi everyone... enjoying my nexus 7, couldn't be any better...
Anyway, my question... I first heard of the blobs on my Asus transformer, and never really looked into them any further...
I noticed my storage going down quite a bit, and looked into why it was going down... in the clockworkmod folder there is the back folder, all fine, and the blobs folder... the blobs folder 2gb+ in there... can anyone tell me what the blobs folder is and what it does?
Thanks, Matt
Sent from my Nexus 7 using xda premium

The blobs folder contains portions of your CWM backups.
When you make a new backup, CWM checks the blobs folder to see what has changed between backups, since it's likely that a lot has remained the same.
This can actually save a lot of space, and make backups happen faster.

ffff00 said:
The blobs folder contains portions of your CWM backups.
When you make a new backup, CWM checks the blobs folder to see what has changed between backups, since it's likely that a lot has remained the same.
This can actually save a lot of space, and make backups happen faster.
Click to expand...
Click to collapse
Thanks for the reply... I noticed they did take a lot less time to backup... so the safest way to delete a backup is through ROM manager? As I would usually just delete the backup folder (the ones inside the backup folder)... but half of my nandroid is still there?
Sent from my Nexus 7 using xda premium

I haven't had to delete any yet, but I'd assume that managing them through Rom Manager would be best.
Good luck

Thanks again, will try that way next...
Sent from my Nexus 7 using xda premium

found this thread through google.
cos i was wondering why there is this blobs subfolder in cwm folder, since it's the first time i encountered it.
by the way it's the 1st time i'm using cwm touch to backup so the new prog has got to do something with since there are no blobs folder since i've been using the non touch version of cwm.
and i also noticed that it makes backups faster the non touch version.
thanks.

radeonxt said:
found this thread through google.
cos i was wondering why there is this blobs subfolder in cwm folder, since it's the first time i encountered it.
by the way it's the 1st time i'm using cwm touch to backup so the new prog has got to do something with since there are no blobs folder since i've been using the non touch version of cwm.
and i also noticed that it makes backups faster the non touch version.
thanks.
Click to expand...
Click to collapse
I don't think it is touch version, I think it is the newest 6.x.x.x clockwork.mod versions... I have many touch versions installed on different devices, but this is the first time.I've seen the blob folder...
Sent from my HTC One X using xda premium

I was hoping to use ROM Manager or ROM Toolbox Pro to backup my Nexus 7 into one file or folder, so that I could then take it off the tablet to store on my laptop in case I need it in the future. I don't want these damned blobs taking up my precious space.
WHAT SHOULD I DO?

bulldozed said:
I was hoping to use ROM Manager or ROM Toolbox Pro to backup my Nexus 7 into one file or folder, so that I could then take it off the tablet to store on my laptop in case I need it in the future. I don't want these damned blobs taking up my precious space.
WHAT SHOULD I DO?
Click to expand...
Click to collapse
I'm not sure.. as it is (what I believe to be) a feature of 6.x.x.x. maybe you/someone could compile a 5.x.x.x. version and see if it just creates the backup folder and not blobs...
Sent from my HTC One X using xda premium

From the source: https://plus.google.com/103583939320326217147/posts/L5aVZe7C9vg
It's new functionality in CWM 6.x.

pixelens said:
From the source: https://plus.google.com/103583939320326217147/posts/L5aVZe7C9vg
It's new functionality in CWM 6.x.
Click to expand...
Click to collapse
Thanks, as I expected...
Sent from my HTC One X using xda premium

I actually preferred how it was before. Now it's impossible to download the clockworkmod folder over in Windows.

https://plus.google.com/112476065271141473049/posts/CHoh72BD3aj

So basically it's impossible to store my CWM backups on my PC or the cloud now, or export via TB. And the blobs folder is already at 2gb on my 8gb Nexus 7 after only two backups. Time for TWRP.

fonseca898 said:
So basically it's impossible to store my CWM backups on my PC or the cloud now, or export via TB. And the blobs folder is already at 2gb on my 8gb Nexus 7 after only two backups. Time for TWRP.
Click to expand...
Click to collapse
+1
I have the same exact concern.
Plus this time i had to manually specify a backup to internal SD. The first time i did a nandroid i selected "Backup" and it over wrote my external SD card - I may have used an older CWM in the past that didn't behave like that - but this sure did get my blood boiling.

it may be faster on the backup process itself, but copying the blob folder to PC or deleting it, takes ages.
i don't kinda like this way of backup
so: what is the last safe version of CWM using the old style ?

It takes long due to blobs folder containing 16000+ of small files and windows is trying to index it first before moving. What I do is to zip that folder on the device and move it then ....
Sent from my Galaxy Nexus using xda premium

I've been wondering about this too. I know it took longer for backups to complete but it was nice just being able to drop a backup folder to my computer for those "just in case" times.

yeah this sucks. I use TB for regular backups and nandroid only when making massive changes, so why would I need it to be slightly faster at the expense of gigs of wasted space?

I switched Tod TWRP because of this stupid blobs. Backup to PC takes forever. TWRP has the old method. It also supports mount of external USB devices and backup to them.

[Q] Incorrect recovery time.

I've noticed this since I installed garwynn's version of CWM. Just installed the official CWM touch recovery and experiencing the same thing.
When making a backup, the date and time are very wrong. For instance, today is June 11th and the recovery is saying that it's February 15th, 1970. 1970-02-15.08.16.07 should be 2013-06-11.09.57.xx.
Any idea on how to solve this problem?

I don't know for a fact, but unless garwynn speaks up, I would try to run another cwm backup to see if the date corrects itself. I would highly suspect the invalid date backup is bad. I don't have proof to back up my opinion BTW.

Philz recovery had the same issue on mine but a traul through the settings in recovery and I was abke to alter time.date ect
Now alls good
Sent from my GT-I9300 using xda premium

adie1234 said:
Philz recovery had the same issue on mine but a traul through the settings in recovery and I was abke to alter time.date ect
Now alls good
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Where did you alter the date/time at?

In philz its in the advanced settings menu
Sent from my GT-I9300 using xda premium

Rom manager
If you do a backup using ROM manager, the dates come out right no matter which recovery you are on.

It has been a problem on all official CWM based recoveries for quite a long time now. It got messed up in one of the updates upstream a long time ago and it's been lost in the code. (Something like that)
But basically it's not really a problem or effecting any actual utility. And btw don't try manually changing the back up names as it will mess up the MD5 and you won't be able to restore them.
Sent from my kTWEAKed, Turbo Charged, CrossBreeding, NOS injected, OCed, UVed, BEAST of an S4

I've changed the name of the folder within the backup folder so it would be easier to know what that backup was. You don't use spaces in the folder name. Md5 still works. I md5 a file, then change the name of the file and md5 it again. Same sum. Granted, you shouldn't be drastically messing around with backups, but I don't see any harm in renaming a folder to like stock.rooted or stockrooted instead of a date and time. The files in the folder haven't been altered. When you're poking around with recovery, it makes backups easier to choose if they are different ROM backups.

oscarthegrouch said:
I've changed the name of the folder within the backup folder so it would be easier to know what that backup was. You don't use spaces in the folder name. Md5 still works. I md5 a file, then change the name of the file and md5 it again. Same sum. Granted, you shouldn't be drastically messing around with backups, but I don't see any harm in renaming a folder to like stock.rooted or stockrooted instead of a date and time. The files in the folder haven't been altered. When you're poking around with recovery, it makes backups easier to choose if they are different ROM backups.
Click to expand...
Click to collapse
Do not change the names of the internal folders, that would mess the restore part.
Sent from my SPH-L720 using Tapatalk 4 Beta

inlineboy said:
It has been a problem on all official CWM based recoveries for quite a long time now. It got messed up in one of the updates upstream a long time ago and it's been lost in the code. (Something like that)
But basically it's not really a problem or effecting any actual utility. And btw don't try manually changing the back up names as it will mess up the MD5 and you won't be able to restore them.
Sent from my kTWEAKed, Turbo Charged, CrossBreeding, NOS injected, OCed, UVed, BEAST of an S4
Click to expand...
Click to collapse
So, if you have changed the name what does one do? I am currently experiencing this at the moment? Am I screwed at this point?