Just a quick question for all the super users out here. I currently have a captivate that is rooted and sideloading enabled. Due to speaker issues it is being replaced after rooting my new phone ( from ATT ) what would happen if I copied my current settings.db file over to the new phone? Would this cause issues? I know I could just redo the sideloading part but I am curious.
Assuming you are going to be running the same setup you should be fine.
I own an Evo, so I don't know much about these.. but can anyone confirm if this would work?
1. make nandroid backup of old phone
2. root new phone
3. install clockwork recovery on new phone
4. make nandroid backup of new phone
5. restore nandroid backup from old phone
I know this works on an Evo, but on the Evo you have to use amen ra recovery so you don't restore your old 4g RSA keys. Does the Captivate have any device specific files that cannot be transferred between phones? If not, I don't see why this wouldn't work.
i dont know if it causes trouble but i have 2 phones and the setting file is different on each one so it might have some problems if the wrong thi ng is change
Related
I've been doing a lot of reading lately and I am finally about to flash my first ROM. Below is a list of what I've done as far as backup and prep. What I want to know is if there is anything important that I missed?
Made a nandroid backup with CWM
Backed up apps with Titanium Backup
Backed up efs directory from the phone
I have a copy of settings.db on my compuer
I have Odin 1-click on my computer
I have a jig made up just in case
Also, since I am on stock 2.1(JH7), I assume I don't need to go through the odin 1-click step, right?
Thanks in advance for your help
looks like you have everything covered except one thing (maybe): if you have an unlocked phone, check the forums to learn how to get your unlock back *before* flashing
i also put a copy of my sd card onto my computer in case something goes bad, but that's just my paranoia/ocd
and you should flash at 100% battery and reset the battery stats while flashing. you can even flash while the phone is plugged into the computer or ac outlet, so the flashing process doesn't drain from the phone battery. some ppl say this is voodoo, but i always flash at 100% and reset the battery stats while changing roms because its a convenient time to reset stats
sublimaze said:
looks like you have everything covered except one thing (maybe): if you have an unlocked phone, check the forums to learn how to get your unlock back *before* flashing
Click to expand...
Click to collapse
OK, thanks. I'm glad you mentioned that. I do have it unlocked and I didn't even think about it. I have to go to Thailand in a few weeks for work so I need it unlocked.
I think I remember reading that the unlock code is located in the nv_data.bin file and can be found by searching the file with a hex editor. I'll have to read a little more and play around with that before I flash.
I have been reading a lot lately, but could not find an answer to my noob question. I was just wondering if I flash an I9000 based ROM and lose my unlock or my product code gets messed up, can I just copy the original nv_data.bin file to the new ROM or will that cause me other problems. I know there are post as to how to fix this, but they are geared toward people who didn't make a backup and copying original would be much easier and quicker. Thanks.
^^^ Any help with above question?
I also have one other question. I've been poking around with Root Explorer and I see that all the sytem apps are naturally stored in /system/app folder, but I don't see the downloaded apps in there. I see what apperar to be my downloaded apps in /data/app folder. Is this where they are stored and if so, can I just copy them out and then copy them back after I flash a new ROM? If so, is there anything else I have to do with them to make them work again (like chown through adb)? I was wondering this because I have some paid apps and I don't know if they will automatically be available for download again once I sign on to the market and I don't want to lose them. Thanks for any help.
happy new year to everyone.
I've just bought nexus s gt i9020 in U.K
Ginger 2.3.1
grh78
baseband i9020xxjk8
I'm going to root and install clockwork via ONE-CLICK-ROOTon it and I have one question ;
When should I backup my eds folder, before or after is rooted ?
thank u in advance
if any one of u bought recently the same nexus s from carephonewarehouse and already made all steps(rooting, clockwork, new room) and want to advice me, I'll really appreciate this
As soon as you make backup, safer you are..
but should/can I backup it before rooting and installing clockwork?
ok so ill root phone, then install clockwork and then run eds tool to backup folder, is that correct?
If you can back it up via adb do it as soon as possible, not sure if you actually need root for this. I believe you'll be wanting a copy with set permissions (so archive it as a .tar.gz file, which stores this data), and a raw translation of the device it is mounted under.
I personally got all my info from here, and happily so far have never had to even think about going through my backups. All worked fine (though it takes a while for the RAW to copy over).
thanks mate for help
I rooted my S3, changed one file, and am now stuck in the startup screen. I've looked on the forums but I'd like to confirm what my recovery options are.
(1) Since I have no backup*, can I recover from a factory recovery for my model and still keep some of my data, apps and customizations?
It's a N American SIII (Rogers Wireless Samsung SGH-I747M). I can boot successfully into both Odin and CWM Recovery (Clockwork 5.5). BusyBox installed. I do not have a functioning MicroSD.
*I only did one thing:
renamed framework-res.apk to framework-res.apk2 to test permissions. Errors and crash ensued, then I restarted and here I am.
That apk file is part of a fix which is circulating that corrects a bug in the North American models' battery reporting, which requires replacing the apk with a slightly modified version. I thought trying a file rename was a safe small test, prior to backing up. The name "framework" should have tipped me off probably.
(2) Is factory recovery my best option? I would love to get in and just name the file back. But I can't get in.
(3) Was some automatic backup made that I overlooked? Rooting and the learning curve took so many steps I can't remember myself.
(4) Can I just restore the /system directory perhaps?
Yep, relative noob here. Hope my question is placed correctly and I haven't missed another post with the answers I need, if not pls advise.
Copied question to a better thread
It's now in the Android Q&A, see:
http://forum.xda-developers.com/showthread.php?p=28256764
Just getting used to the forum here.
NEVER FEAR find a ROM that you want to install and flash it using Odin or copy it to SD card and flash using clockwork mod And no there is no secret backup BTW once you get your phone working again make a backup then Go to where its stored And label it ALWAYS backup as soon as you root your phone
If you can manage, push a similar framework (taken from someone else) using adb...
Typed using a small touchscreen
How?
jezus101 said:
NEVER FEAR find a ROM that you want to install and flash it using Odin or copy it to SD card and flash using clockwork mod And no there is no secret backup BTW once you get your phone working again make a backup then Go to where its stored And label it ALWAYS backup as soon as you root your phone
Click to expand...
Click to collapse
You can flash a ROM using Clockwork instead of Odin? I totally missed that memo! Tips please
I found that Clockwork required the file to be in the internal SD folder -- I couldn't access the External SD card under any circumstance. There was no way to get a file to the internal file system without a functioning ROM. This is still confusing me. Maybe I had the wrong version of Clockwork or was doing it wrong. Not for lack of trying.
Hi everyone. Long-time reader, first time poster here.
Well, I've gotten myself in a bit of a jam. My Relay is rooted and has CWM 6.0.1.2 running the stock ROM per one of the awesome devs working on this phone. In a bout of zeal, I found a guide for installing Google Wallet on unsupported devices that involved editing the build.prop file to have the device identify itself as another. I dove in head first... My first mistake was not doing a CWM backup and my second mistake was that I backed up the build.prop file to the internal memory rather than the external SD card (seems pretty inaccessible there). After rebooting, the device black-screened after the Relay 4G splash and can only be brought back up by pulling the battery, though it still gets stuck at startup.
I had a look around and found these very similar threads, but they are for the S3:
http://forum.xda-developers.com/showthread.php?t=1895631
http://forum.xda-developers.com/showthread.php?t=1830191
I can also get into CWM and Odin mode, but Odin3 and adb don't see the device for some reason and CWM doesn't appear useful without a backup. From what I've gathered, the easiest way to recover from this is a flashable zip with the stock build.prop file.
Would anyone be able to make one of those or otherwise bail me out? Any help would be greatly appreciated!
Edit: If it helps any, I used ES File Explorer to do this, which apparently doesn't do permissions quite right. I'm not sure if it affects this, but I figured I'd throw it in here anyway.
Bumping in desperation here! Can anyone just paste in their build.prop? I'm on UVLJ1 (haven't had time to do the latest update due to root).
hmm... you should be able to go into download mode and flash the stock rom to recover the phone i think?
I think this is the answer. Flashing stock will give you what you need, it can be done through CWM (gee one's flashable zip for instance).
Wipe system/data through the format menu.
I wish I knew what a build.prop was.
installed it and rebooted my Samsung Relay and the screen went black. I pressed the power button and nothing happened.
The phone is now officially a paperweight. Also I had root privileges.
Can you help me please, I do not know what to do?:crying:
tacoman3148 said:
Hi everyone. Long-time reader, first time poster here.
Well, I've gotten myself in a bit of a jam. My Relay is rooted and has CWM 6.0.1.2 running the stock ROM per one of the awesome devs working on this phone. In a bout of zeal, I found a guide for installing Google Wallet on unsupported devices that involved editing the build.prop file to have the device identify itself as another. I dove in head first... My first mistake was not doing a CWM backup and my second mistake was that I backed up the build.prop file to the internal memory rather than the external SD card (seems pretty inaccessible there). After rebooting, the device black-screened after the Relay 4G splash and can only be brought back up by pulling the battery, though it still gets stuck at startup.
I had a look around and found these very similar threads, but they are for the S3:
http://forum.xda-developers.com/showthread.php?t=1895631
http://forum.xda-developers.com/showthread.php?t=1830191
I can also get into CWM and Odin mode, but Odin3 and adb don't see the device for some reason and CWM doesn't appear useful without a backup. From what I've gathered, the easiest way to recover from this is a flashable zip with the stock build.prop file.
Would anyone be able to make one of those or otherwise bail me out? Any help would be greatly appreciated!
Edit: If it helps any, I used ES File Explorer to do this, which apparently doesn't do permissions quite right. I'm not sure if it affects this, but I figured I'd throw it in here anyway.
Click to expand...
Click to collapse
I'm not very good at this also,but...Can you connect your phone to your computer and mount your phone from cwm and get the build.prop file that way?Or maybe do a factory reset?
So i broke the glass on my n5 but it's working ok, recently i manged to buy a cheap new white one, and basically have 2 working phones.
I want to transfer all my stuff from the old > new, i'm wondering, apart from the usual Titanium path, is there any google service or other method that will make a copy of my old phone on the new one?
What would be the best approach here, if Titanium, are there any shortcomings?
ty
Why not backup in TWRP (make sure NOT to backup EFS) and then restore (once again, WITHOUT EFS) on the other phone? Everything will be exactly the same.
Also make sure they're both on the same bootloader/baseband.
You forget the content of your /sdcard. Use adb pull/push to transfer your favorite folders/files to your new device.
Tnx gents! I was thinking of nandroid, but wasn't sure it can work between phones.
They have the same baseband, by the same bootloader you mean the same version/build number?
Of course i will transfer sdcard by other means.
btw. it's strange google doesn't offer simple backup/restore to new phone
invisibles said:
Tnx gents! I was thinking of nandroid, but wasn't sure it can work between phones.
They have the same baseband, by the same bootloader you mean the same version/build number?
Of course i will transfer sdcard by other means.
btw. it's strange google doesn't offer simple backup/restore to new phone
Click to expand...
Click to collapse
I did that,since I asked Google to replace my phone due to abattery charging problem. I installed same bootloader same radio same twrp version on both phones,backup all the "SD card" with a PC,and then made a nandroid backup. Now if you export the whole nandroid folder on the new phone ,you will not be able to install it because the folder name is related to the phone serial (if you look at the nandroid folder is named with many random charters). To solve this I created a nandroid backup on the new nexus 5 ,and renamed the backup of the old one with the name of the new one. This worked for me . I don t know if now you have to do the rename stuff no with last versions, but was like this 8 months ago (don't remember twrp version).
Don t backup efs partition and restore on the new one,it contains the imei and other stuff,and don't try to flash a 32gb nandroid backup on a 16gb model, I don't know if it will work
It worked, i also found out you can migrate stuff from the old nexus using google tap&go through nfc, don't know how much that restores..
Ty all for the help