Database Info

[Q] CWM recovery filenames

This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.

phoneturf said:
This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.
Click to expand...
Click to collapse
Are you talking about the folder name? Because that shouldnt affect it. Inside the folder that is created for each backup, there are backup files which dont have any dates/times in the filename itself.

I vaguely remember reading about this, but I can't recall how it was resolved. Try updating your can to 5.5.0.4 Touch or 5.8.1.3 (?? something along those lines) and seeing if that resolves it. Outside if that I must ask the obvious, did u Google "md5 checksum error cwm"?

Are you using the same CWM version as you did when you backed up? If you didnt, then thats one reason. You have to stay on the same CWM version, many of these CWM versions floating around have different fixes in there.
One way around this is to go to Advanced Restore and restore all the IMG files from there.
Dixit

ihtfp69 said:
I figured I would post this fix here in case anyone else ran into this problem. This is assuming you did not change the folder names and let Clockworkmod create them. I haven't had it happen until today, but it's not a nice message to see when you are trying to do a restore.
Code:
Checking MD5 sums...
MD5 mismatch!
Do this to fix:
To fix this problem use the code below. Substitute the final folder name for the backup you need to fix.
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
When that finishes, re-run the restore and everything should be fine.
NOTE: As rpearl stated, there could be something really wrong with your nandroid, so use this tutorial as a learning experience and not a fix-all. In my case, everything was fine after restoring. However, that may not always be the case. Do this with caution.
Click to expand...
Click to collapse
Use this method to potentially fix.

dixit said:
Are you using the same CWM version as you did when you backed up?
Dixit
Click to expand...
Click to collapse
That is correct on most of them. I updated to CWM Touch for the last one, but it did not restore either. To check this out, I just did a backup and without changing the name did a restore and it worked fine. The thing that was odd in the backups that would not restore was that it immediately bombed out of the checksum each time as if it was checking the name itself first.

That is brilliant. I did not realize you could generate the MD5 from ADB and stick it right into the folder. Thanks!

The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.

bdbx18 said:
The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.
Click to expand...
Click to collapse
Are you using touch or standard CWM? I wonder if this only happens in touch version. I will try this in the next few days.

I changed the name of one of the backups I created with CWM touch and it restored fine using touch. I suppose my earlier problem may have been trying to restore a backup created with old CWM using touch version.

well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..

garydv2002 said:
well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..
Click to expand...
Click to collapse
If you are using sk8erwitskil version of the CWM touch (ClockworkMod TOUCH 5.5.0.4 v3.5) then most likely you didnt follow one of the directions on the front page. This is a known issue. Here it is again. You need to create that file on the location you backing upto.
For CWM to recognize the .hidenandroidprogress file you need to boot into CWM and go to mounts and storage>>mount /sdcard then go back to backup & restore and make a restore and it should work everytime (as long as you do the steps in that order and you have the .hidenandroidprogress file in /sdcard/clockworkmod & /sdcard/external_sd/clockworkmod folders)
There is a known bug in ClockworkMod 5.5.0.4 that long file names can POSSIBLY cause backups to hang. There is a solution/workaround:
•boot into recovery
•try to make a backup (no matter if it passes or fails proceed to next step)
•either through terminal emulator or through adb run the following command EXACTLY:
Code:
touch /sdcard/clockworkmod/.hidenandroidprogress
•if you are backing up to external sdcard then run the following:
Code:
touch /sdcard/external_sd/clockworkmod/.hidenandroidprogress

im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?

garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
Not sure, I used that for awhile but then went back to the other touch and Ive had those two files still in my directories.
I would go ahead and create those two files (one for internal SD and one for external SD if you got one you are using that is) and try it again. Make sure you call that file exactly the way it is, or copy/paste the code identically if you do it through ADB.
Dixit

garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
I use that one, takes less than 5 minutes on my class 10 sd.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Well the crazy thing is after sitting there over an hour waiting I finally took out the battery and even though it never said complete all the files are there but I still don't trust that it made a good backup so I deleted those files tried putting in the code above and it still would not work so I flashed back to version 5.0.2.0 thats not touch and it made a perfect backup in under 2 minutes. Might be one of those it just ain't gonna work right on this specific phone thing or it could be the little green gremlins at it again lol... who knows.. I'll just wait for new version of touch to come along and try it. It won't be long till a newer greater version comes along as fast as technology is going today.. thanks for the help. I'm learning more and more each day from you guys on xda.....
Sent from my SAMSUNG-SGH-I727 using XDA

Not sure if this is the cause of the issue but for nandroid backups you can't make a folder name with spaces otherwise you will get an md5 sum error. Try renaming the folder with underscores instead of spaces

[Solved!] Difficulty updating to 1.63.531.2 without setting up from scratch

Initial phone stats: DS Mod 1.55.531.3, hboot 1.45.0013, s-on/unlocked via HTC unlocker.
I'm trying to update my own phone to 1.63.531.2 via the PG59IMG.zip file found here, http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24 , but I'm running into problems applying this update and keeping it after restoring a Nandroid backup. It would be a huge amount of work to set up my phone from square one, and I'd like to avoid the process if at all possible.
The steps I've followed (twice, now, with no joy) are the following:
* apply the update through the PG59IMG.zip
* flash CWM 5.0.2.7
* flash Superuser
* restore most recent Nandroid backup
* flash 1.63.531.2 boot image (for wi-fi fix)
And this puts me back at my starting point, with the 1.63.531.2 update not applied.
I know I'm going about this the wrong way, but I can't figure out the correct method to make this work. The fact that I flashed the DS Mod 1.55.531.3 ROM back after unlocking might have something to do with this, however, I just can't nail down why. Really could some help to make this work.
TIA for any suggestions --
--
KingCheetah

hey, real quick, after flashing the 1.63.531.2 update, instead of restoring your full nandoid of 1.55.531.3, go to 'advanced restore', choose that nandroid, and choose only 'restore data'. that will put all your apps and data onto the new update, rather than flashing you all the way back to what you had before.
you could also backup and restore your data with an app called Mybackup Root, or some people use Titanium Backup. I personally like using the advanced data restore in CWM, or else Mybackup.

Yogi, I thought your suggestion would be a smoking gun. However, I'm having the same problem as described in this thread: http://forum.xda-developers.com/showthread.php?p=25431819#post25431819
Might you have any suggestions for addressing the md5 problem? I'm coming up empty...
Thanks for your help --
--
KingChetah

yeah, come to think of it, I've had that problem before as well. did you try what xmc suggested? also, perhaps try the Modaco 4.0.0.9 version of CWM to do the advanced data restore... if my memory serves me, I have had more success overall with that version. unfortunately that's about all I got!
the other sugestion would be to flash your full nandroid, then use Mybackup Root to back everything up. then after updating, DL the app again and restore.
good luck and keep us posted!

yogi2010 said:
yeah, come to think of it, I've had that problem before as well. did you try what xmc suggested?
Click to expand...
Click to collapse
Yes, and for the backup I want to restore, all the md5s are the same between the files and what is listed in the nandroid.md5 file. So, the method XMC suggested really doesn't do anything.
yogi2010 said:
also, perhaps try the Modaco 4.0.0.9 version of CWM to do the advanced data restore... if my memory serves me, I have had more success overall with that version. unfortunately that's about all I got!
Click to expand...
Click to collapse
Hmm, okay, I'll give that a try. Weird that CWM 5.0.2.7 has this problem. Also frustrating.
yogi2010 said:
the other sugestion would be to flash your full nandroid, then use Mybackup Root to back everything up. then after updating, DL the app again and restore.
Click to expand...
Click to collapse
I'll keep this as the last resort, because I'd rather not have to download an app for just this purpose. Nandroid backups have served me fine so far. Call me a minimalist.
I'll try Modaco and see what happens. Thanks much for the idea to try.
--
King Cheetah

Sadness
Using Modaco didn't work. Although the Advanced Restore sees the file and appears to run successfully, it says it can't find a data.img file and an Android.img file, so it doesn't restore the info.
So, I guess it's down to trying Mybackup Root and see what happens. Getting tired of redoing this process over and over.
Why can't things "just work" in these situations?
--
KingCheetah

check the other thread....problems with restoring backup
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
or actually...just flash the data.img through fastboot....its ten times easier
but the data.img in the same directory as adb and fastboot....then run the two commands with your phone in the bootloader
fastboot erase data
fastboot flash data data.img

xmc wildchild22 said:
or actually...just flash the data.img through fastboot....its ten times easier
but the data.img in the same directory as adb and fastboot....then run the two commands with your phone in the bootloader
fastboot erase data
fastboot flash data data.img
Click to expand...
Click to collapse
The problem with this is the file "data.img" doesn't exist in a Nandroid backup. As I stated in my previous message, the Advanced Restore process tossed up a message that the file didn't exist (which is correct).
The files within a given Nandroid backup folder are the following:
.android_secure.vfat.tar
boot.img
cache.ext4.tar
data.ext4.tar
nandroid.md5
recovery.img
system.ext4.tar
From the Advanced Restore problem thread (http://forum.xda-developers.com/showthread.php?t=1624319):
xmc wildchild22 said:
then take the system.img from the 1.63 update and put in replace of the nandroids one....then redo the md5 checksum for the system.img like i had showed before
Click to expand...
Click to collapse
I would love to try this, but since the 1.63 update is a PM59IMG.zip, I can't open it with a zip file manager--it throws up a "central directory not found" error. Unless there's another program besides 7zip that's needed to handle this type of zip file...
Edit: I just realized that, as you can see from the file list above, a Nandroid backup also doesn't have a "system.img" file--it has a "system.ext4.tar," but not "system.img." So being able to pull anything from a PM59IMG.zip file is a moot point at this juncture.
Banging one's head against the keyboard does little constructive good, but it's really tempting at this point --
--
KingCheetah

just try opening it with a plain windows explorer

xmc wildchild22 said:
just try opening it with a plain windows explorer
Click to expand...
Click to collapse
Using the "Explore" option from the right-click context menu in Windows Explorer gives the following error: "The Compressed (zipped) Folder is invalid or corrupted." (Since archive files on my laptop are associated with 7zip, this is the only method by which I can access Win XP's native archive file handling.)
This has been the case with all PM59IMG.zip files--they don't register as normal zip files.
Thanks for the suggestion, though --
--
KingCheetah

hmm...maybe tht zip is corrupted because it works for me....DL this --> http://tinyw.in/Mzg2

Nope, not corrupted because it works just fine to update my phone to 1.63 (as stated before, I've done this twice now). Also, that's the exact same source from whence I downloaded my copy of the file. The PM59MG.zip for 1.55.531.3 gives exactly the same error, and I used that without difficulty as well.

KingCheetah said:
Nope, not corrupted because it works just fine to update my phone to 1.63 (as stated before, I've done this twice now). Also, that's the exact same source from whence I downloaded my copy of the file. The PM59MG.zip for 1.55.531.3 gives exactly the same error, and I used that without difficulty as well.
Click to expand...
Click to collapse
Use winrar to open the PG59IMG.zip files - that's what I used to make all the custom ones with, and also what I used to open the leaked ones we started from.
You won't be able to edit existing leaked ones, because they are locked and have an HTC signature.
Sent from a digital distance.

Thanks for the pointer, Blue, and I'll keep this in mind. But as I added to my previous post (#8), I realized that a Nandroid backup doesn't have a "system.img" file--it has a "system.ext4.tar," but not "system.img." So being able to pull anything from a PM59IMG.zip file is a moot point at this juncture.
I think I'm going to have to wait for a 1.63 ROM that can be installed through CWM rather than the PM59IMG.zip method. The DS Mod 1.55.531.3 worked well for me, and all apps/data were just there after I flashed it. Maybe I just got lucky with the process I followed previously, who knows? (http://forum.xda-developers.com/showthread.php?t=1508406&page=4 post #39)
At any rate, I've got a truly mean headache from working on this all day. Time for a break with a bit of ice on ye old cervical vertebrae.
Thanks again for chiming in --
--
KingCheetah

No prob, didn't read through and shot from the hip on the last post I saw, out at dinner and skimming the forums on smoke breaks
Sent from a digital distance.

does anyone know the deal with the implementation of tar backups? I think that came into play at some point, and I wonder if that has anything to do with anything.
I just checked a backup I made with the Modaco CWM, and the files in it are all .img files, including data. and I know for a fact I have done backups and advanced data restores with that recovery. it would be a hassle, but if you get re-energized you might make the backup and do the restore with Modaco. definitely would be a hassle if it didn't work, but you could also make a backup with Mybackup, and have that ready too, as well as probably have a data.img to try and flash thru fastboot like xmc suggested.
anyway, hopefully we'll get this all sorted out. take it easy!

well .tar are used ever since cwm started working with ext4....maybe imgs are only ext3 or lower or its just inefficient

On that note, I did use the modaco 4.0.0.9 recovery to make the nandroids I pulled the system images from to get the bases from which I de-odexed, and when finished I uploaded to my host and they are the de-odexed bases I posted in dev.
I am pretty sure I went with modaco recovery for that because cwm 5.0.2.7 output tar files and it just saved a step in the process.
If you are working with the .tar files then jump on linux to unarchive them if that's what you are trying to do.
I just ran the deodex process using windows, because the first working deodex tool I found was a windows tool.
Generally I use modaco .9 for nandroids I want to work with in windows, and cwm 5 for nandroids I want to work with in linux.
We're probably leaving the restaurant soon, if we split up I'll actually read back through the thread when I get home and see if I have anything else to add.
Sent from a digital distance.

Yogi, you're brilliant!
yogi2010 said:
I just checked a backup I made with the Modaco CWM, and the files in it are all .img files, including data. and I know for a fact I have done backups and advanced data restores with that recovery.
Click to expand...
Click to collapse
[facepalm] Of course! This is why my Advanced Restore attempt with Modaco failed--because I used the CWM 5.0.2.7 backup, which did not have the files Modaco would have referenced. Duh! I wasn't even thinking along the lines of a file type mismatch between the two recoveries. Baka baka baka...
yogi2010 said:
it would be a hassle, but if you get re-energized you might make the backup and do the restore with Modaco. definitely would be a hassle if it didn't work, but you could also make a backup with Mybackup, and have that ready too, as well as probably have a data.img to try and flash thru fastboot like xmc suggested.
Click to expand...
Click to collapse
At this point, not a hassle, but the best chance to accomplish this thing with a minimum of fuss and bother. I'll give this a shot right after a bit 'o java. Thank you, Yogi, for highlighting something that should have been obvious to me when Modaco gave the error message that "data.img" didn't exist. Oy!
However, this still leaves unanswered the question of why CWM 5.0.2.7 is tossing up the md5 mismatch error when one tries to use Advance Restore, and that files aren't seen by CWM via Advance Restore until one accesses regular Restore. Paperskye is having the exact same problem in this thread: http://forum.xda-developers.com/showthread.php?t=1624319 . Should this be brought to the attention of the CWM devs? It really seems like a rather show-stopping error for CWM...unless Advanced Restore isn't really used with 5.0.2.7 and the MT4GS. There just doesn't seem to be a good reason for the observed behavior.
Many thanks for your encouragement. I'll report back with results on the next try with Modaco --
--
KingCheetah

It's a beautiful thing!
Using Modaco for my backup prior to the update, then Advanced Restore of data afterward = perfect restore of my phone environment with 1.63 on board. Done with as little fuss as I was hoping to encounter. Yogi, you get the prize. The only thing I had to manually put back was my custom boot animation, but that's trivial.
I think I'll just leave Modaco on as my recovery for now, since AR is functional with it and CWM 5.0.2.7 is not. Makes me wonder, from just an everyday backup standpoint, is there any real advantage of CWM over Modaco? I wish there was more information on how the recovery module functions on the CWM website--I'd like to read up on it for educational purposes. Guess I'll do a Google to find more.
So ridiculously happy right now. In a stew of things going wrong, at least something went right.
Big rumbling purr of gratitude --
--
KingCheetah

[SOLVED] Efs?

What is it? Because I want to download the mokeeOS, but the installation is confusing me, so I wanna know if the efs matters
Sent from my SGH-T959V using XDA

1. Yes efs matters a lot
2. I don't know a whole lot but it holds the network info, imei number, and alot of other really important things
Sent from my SGH-T959V using xda premium

Although there is a way to make sure you have a backup, flash this file in cwm
sourceforge.net/projects/teamacid/files/fb/cwm/cm7-efs-backup.zip/download
And there will be two files in the root of your sd card
Efs-backup.tar and efs-backup.tar.md5 ( I suggest save it to your computer, it saved my ass )
And you can restore this backup at anytime by flashing this
sourceforge.net/projects/teamacid/files/fb/cwm/cm7-efs-restore.zip/download
Good luck
Sent from my SGH-T959V using xda premium

Efs is the files system that holds the unique identifiers for your device. Without it, your phone is basically useless. You won't be able to connect to any network properly do things like phone calls, internet, texting, are all degraded, if they even work at all... Make sure you know what you are doing before messing with it. Fb created a vet good guide on the wiki. Follow it to a T!
Sent from my SGH-T959V using XDA

I would suggest using a root browser to copy the EFS folder to somewhere safe on your PC and copy a 2nd back-up to your SD card. I lost IMEI going from CM7 to moKeeOS but was able to easliy restore it with a back-up and a root browser.
The flashable EFS back-up/restore from FB should still be used, but with EFS/IMEI I don't think you can be too careful and backing it up manually as previously stated is a good idea.

Yeah, I keep multiple copies of it on my PC. The reason being is that I copy it whenever I do a backup before a flash. So I have a directory with the date with 3 folders: efs, nandroid, and sdcard. I used adb to copy them:
Code:
cd efs
adb pull /efs/
Probably overkill, but better to be safe than sorry, eh?

Ok, but once you lose IMEI and don't have a backup (I received this phone for repair), then what can I do?

serialteg said:
Ok, but once you lose IMEI and don't have a backup (I received this phone for repair), then what can I do?
Click to expand...
Click to collapse
It's pretty much screwed without the OEM Samsung/Tmo software. You would have to send it to Samsung for repair, or you might get lucky and get an engineer to hook you up, but that is unlikely...

thomas.raines said:
It's pretty much screwed without the OEM Samsung/Tmo software. You would have to send it to Samsung for repair, or you might get lucky and get an engineer to hook you up, but that is unlikely...
Click to expand...
Click to collapse
thanks for the answer. that OEM software isn't available in the forums or anywhere else for us? because I swear I flashed something OEM'ish without root with heimdall.
also, the imei is on the battery part of the phone, can't i fix it?
i read somewhere that you could use a phone just fine without imei on the about phone.

you can use the phone without imei, but it doesn't function as well as it would with it. Also, i was using titanium backup and it said my device's id was changed, and it showed my actual imei. If i were to restore it, would that fix the imei?

EFS help on the SGH-T959V
Basically, I've had a hell of a time with some EFS drama this weekend, made a total noob mistake, but in a stroke of luck I was able to "recover" so to speak my EFS even after it was supposedly "wiped."
After some thorough research and READING and bit of thought, I realized that the PIT mapping layouts between BML and MTD are indeed different, and that in theory if one remaps to BML (in layman's terms a stock partition map) then the EFS data originally on the phone gets correctly remapped (at least in my case it did).
To reiterate:
1. I did a nandroid backup. Basic ****. I hope to god you at least did this step too.
2. I used the cm7-efs-backup.zip script to backup my EFS. This was my first mistake. In my case, I don't know why I'm still researching, this script failed to make a backup .tar on my sdcard or anywhere else for that matter. It didn't throw any error messages either on the screen in the process. Not trying to attack the authors of that script, I'm just saying it didn't work for me this time.
3. I pushed the TWRP boot.img with Heimdall
4. I used the cm7-efs-restore.zip script which also "succeeded" but did nothing to restore any sort of EFS obviously because there was no backup to begin with.
5. I flashed R11 unofficial cm7 and booted up. Everything was fine but the IMEI was corrupted and I confirmed that the new MTD EFS partition was empty. On T-Mobile I could place no calls and only got sporadic and intermittent data access.
It was at this point I was sure I had ruined my phone.
After some more careful reading I realized that the original EFS was still present on the firmware, however the new MTD layout I flashed (wisely) stores its EFS partition in a different physical location. In theory, I thought if I reverted to BML and a stock ROM then I would recover the original EFS. In my case, this was successful.
1. I accessed the most recent "boot.img" file from my most recent nandroid and pushed that back to the device with Heimdall
2. At this point you have to flip your USB drivers back to USB Composite Device.
3. I then used a Heimdall one click to return to a rooted stock KJ6 "Gremlin Remover"
4. Upon restart, everything was fine (sigh of relief)
At this point, I'm still trying to determine why my EFS cannot be backed up with a few automatic tools. I made a backup of the file structure, but even lyriquidperfection's EFS Pro 1.4.7 can't make a backup of the EFS. It can access the ADB Server, but the backup 'fails'.
I'll check back in after I figure out why.
Hopefully this info will help anyone else who has switched to MTD and has a missing EFS.

nick.tansy said:
At this point, I'm still trying to determine why my EFS cannot be backed up with a few automatic tools. I made a backup of the file structure, but even lyriquidperfection's EFS Pro 1.4.7 can't make a backup of the EFS. It can access the ADB Server, but the backup 'fails'.
I'll check back in after I figure out why.
Hopefully this info will help anyone else who has switched to MTD and has a missing EFS.
Click to expand...
Click to collapse
I had similar issues yesterday. If your trying to install the twrp and then downgrade to the version with wifi dont flash the boot.img with heimdall. Follow the instructions for installing via cwm.
Just install the zip that has twrp in it. But follow the directions for normal cwm installation.
Also when trying to make a backup of your efs, make sure system is mounted. I initially did not have any problem but I was on antonx's kernel and when you flash with that recovery it would mount properly. What is happening is system isnt getting mounted. So its making a null backup.
The most important thing to do is when you are trying to make a backup of your efs is mount system!

Hi have you tried the updated EFS Pro v1.7.13? It can now automatically detect the mount point of the '/efs' folder for back up and restore. Also many many bug fixes and new code to communicate with adb.exe alot more quickly and efficiently.
Head over to the forum and check it out.

I already solved this problem, but this would seem useful other people with the same problem. But what forums are you exactly referring to?
Sent from my SGH-T959V using XDA

mierkat09 said:
I already solved this problem, but this would seem useful other people with the same problem. But what forums are you exactly referring to?
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
This one.
http://forum.xda-developers.com/showthread.php?p=18524176

[Q] How to restore phone from backup made prior to ROM download

http://forum.xda-developers.com/showthread.php?t=1875914
Hi I used the above guide to root my phone and I also did the backup from recovery mode thing AND I backed my phone up with Kies on my computer beforehand. Well I messed my phone up and had to use Odin to restore it and now I'd like to see how I can restore my phone from the backup I made in recovery mode. Every time I try to backup using kies it crashes on my computer. Also, if possible, I'd like to know a way to not have to use the same app I used to back the phone up to restore it. I used an app called EZ Recovery or something like that. If someone could help with this I'd appreciate it thank you!

gamer6592 said:
http://forum.xda-developers.com/showthread.php?t=1875914
Hi I used the above guide to root my phone and I also did the backup from recovery mode thing AND I backed my phone up with Kies on my computer beforehand. Well I messed my phone up and had to use Odin to restore it and now I'd like to see how I can restore my phone from the backup I made in recovery mode. Every time I try to backup using kies it crashes on my computer. Also, if possible, I'd like to know a way to not have to use the same app I used to back the phone up to restore it. I used an app called EZ Recovery or something like that. If someone could help with this I'd appreciate it thank you!
Click to expand...
Click to collapse
So currently you are unrooted and still using the Odin factory rom? If so, the first steps are to:
1) Re-root
2) Unlock your bootloader using EZ Unlock v1.2 found here: http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
3) Custom Recovery backup files are proprietary, they only will restore using the same recovery you used. For the GSIII, you have two custom recoveries to use: ClockWorkMod or TWRP. If you want to restore to your previous backup that you made using your linked guide, then EZ Recovery will be the absolute easiest to use.
Two questions:
A) Why don't you want to use EZ Recovery? It's the easiesr way to install CWM recovery and you only use it once.
B) Which recovery did you select to make a backup using EZ Recovery? Was it touch based?
3) [Edit] Disregard my question about Kies, I believe I misinterpreted what you asked.
Sent from my SCH-I535 using xda-developers app

SlimSnoopOS said:
So currently you are unrooted and still using the Odin factory rom? If so, the first steps are to:
1) Re-root
2) Unlock your bootloader using EZ Unlock v1.2 found here:
3) Custom Recovery backup files are proprietary, they only will restore using the same recovery you used. For the GSIII, you have two custom recoveries to use: ClockWorkMod or TWRP. If you want to restore to your previous backup that you made using your linked guide, then EZ Recovery will be the absolute easiest to use.
Two questions:
A) Why don't you want to use EZ Recovery? It's the easiesr way to install CWM recovery and you only use it once.
B) Which recovery did you select to make a backup using EZ Recovery? Was it touch based?
3) [Edit] Disregard my question about Kies, I believe I misinterpreted what you asked.
Sent from my SCH-I535 using xda-developers app
Click to expand...
Click to collapse
The reason I didn't want to use EZ Recovery is because I thought it was an app that requires root, and I didn't want to root anymore because I thought that was why my phone jacked up in the first place, even though it was probably just because I'm dumb.
I did the backup as explained in that guide, as well as the one explained in the video I have posted. I didn't know if they were both necessary or if they were different types of backups or something so I did them both. Neither were touch based. The only thing that was touch based was when I touched the part in the apps to go into the recovery mode that I used to backup my phone. One just said to click on "backup" the other tutorial said click on "backup to ext sd card" so I did both. Both were initiated through the recovery mode thing though where you use the volume buttons and the power button. Thank you for the help!
Edit: I realized I can't link so if you go to "that place where you broadcast yourself" and after it says "watch?" And "v [equals]" in the link, paste the following: cgvEYCXHy7k&sns=em
(Sorry I deleted the link and it still kept saying I had a link in here I didn't know what was triggering it. Lol)

gamer6592 said:
The reason I didn't want to use EZ Recovery is because I thought it was an app that requires root, and I didn't want to root anymore because I thought that was why my phone jacked up in the first place, even though it was probably just because I'm dumb.
Click to expand...
Click to collapse
Well if you want to restore to that exact ClockWorkMod (CWM) backup, you do in fact need to be rooted. Even if you don't want to do anything else.
Just reboot into recovery using EZ Recovery, select "Backup and restore," then restore your backup. It's relatively easy honestly.
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Well if you want to restore to that exact ClockWorkMod (CWM) backup, you do in fact need to be rooted. Even if you don't want to do anything else.
Just reboot into recovery using EZ Recovery, select "Backup and restore," then restore your backup. It's relatively easy honestly.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
SlimSnoopOS said:
Well if you want to restore to that exact ClockWorkMod (CWM) backup, you do in fact need to be rooted. Even if you don't want to do anything else.
Just reboot into recovery using EZ Recovery, select "Backup and restore," then restore your backup. It's relatively easy honestly.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Okay thanks I'll do that. I suppose it can't hurt to do it again. If it does I'll just have to restore my phone yet again. Couple questions though:
1: Is my phone any different right now since I used that Odin thing? I honestly didn't know what it was. I just looked up how to unbrick your phone because I tried downloading jelly bean and I got that software not authorized by verizon message so I followed another youtube video's tutorial and they said download that app and do a bunch of other stuff with it.
2: http://forum.xda-developers.com/showthread.php?t=1840414
In this thread, his first link (Titled "this page") has a bunch of things called nightlies. Wtf are those? Just a crap load of re-issued versions of the same software (jelly bean)? Are they all from trusted developers or could anybody post one there? Should I take any precautions in making sure I don't get a messed up version/virus? I would assume in that video I referenced, the two downloads he was talking about were just the top/newest "nightly" in that link and the other download he was talking about (GAPPS or Google Apps) is the second one from the top in that other link, right? The one that says it's for Android Version 4.1.x?
3: In that first link I sent you, the guide to rooting, at the bottom it says that rooting and bootloader unlocking are completely finished but the reason everyone says they think my phone messed up and gave me the unauthorized software message was because I didn't unlock my bootloader. There is a second link in the jelly bean download guide for downloading a different boot unlocker. Is that the one I should be downloading? Should I do that on top of everything else I did in that rooting guide?
4 (last question I promise): Also, in that bootloader unlocker he said I should really "know what I'm doing" if I am running windows because it was intended for Mac and Linux. I run windows and I really don't want to run linux or Ubuntu or anything and i don't have a Mac. I haven't actually downloaded or tried to run the BL unlocker yet but I mean is it really that hard to use on Windows? I know it may sound quite hard to believe because of how much of an idiot I sound like when it comes to rooting and crap but I really AM, at least in my opinion, quite good with computers. At the very least as far as fundamentals go. But yeah when it comes to programming and all this stuff, I'm as dumb as a rock. But what does "know what I'm doing" mean? Is the BL Unlocker you linked to different? Should I just use yours?
Thanks man you're the ****.

gamer6592 said:
Okay thanks I'll do that. I suppose it can't hurt to do it again. If it does I'll just have to restore my phone yet again. Couple questions though:
1: Is my phone any different right now since I used that Odin thing? I honestly didn't know what it was. I just looked up how to unbrick your phone because I tried downloading jelly bean and I got that software not authorized by verizon message so I followed another youtube video's tutorial and they said download that app and do a bunch of other stuff with it.
Click to expand...
Click to collapse
Whenever you use Odin, it's primarily to return to stock or flash a modified image to your Samsung device. In essence what you want to only use Odin for, is to return to the way you purchased your phone: fresh out of the box. You "should" be on a stock image if that's what resolved your previous issue which led to you creating this thread. In all honesty, I'm amazed that you fixed your phone via youtube. Going forward, all that you need to know about the Verizon GSIII is here: http://forum.xda-developers.com/showthread.php?t=1762709
Stick to using XDA for now.
2: http://forum.xda-developers.com/showthread.php?t=1840414
In this thread, his first link (Titled "this page") has a bunch of things called nightlies. Wtf are those? Just a crap load of re-issued versions of the same software (jelly bean)? Are they all from trusted developers or could anybody post one there? Should I take any precautions in making sure I don't get a messed up version/virus? I would assume in that video I referenced, the two downloads he was talking about were just the top/newest "nightly" in that link and the other download he was talking about (GAPPS or Google Apps) is the second one from the top in that other link, right? The one that says it's for Android Version 4.1.x?
Click to expand...
Click to collapse
Nightlies = a new version of that rom is updated each night. Some things may break, some things may be fixed but from nightly to nightly, there are new things introduced and new things broken. A nightly is essentially a prolonged "beta" of the overall rom. You can update from one nightly to another or even choose to update weekly if that works best for you, it's all about choice. Now in regards to CM10, CM10 = CyanogenMod10. This is the most popular Android rom and is supported on the most amount of Android phones. The [OFFICIAL] Verizon GSIII CM10 rom is one rom that is pulling software and improvements that are being worked on hourly by the "lead" or primary CyanogenMod team. If that doesn't make sense, the Verizon GSIII version of CM10 is one branch from the giant, ever growing tree that is CyanogenMod.
The "OP" or original post is the very first post, on the first page of any thread. It is also labeled #1. So, the OP of your thread would be your initial post which I responded to. When reading rom threads, the OP is where all the primary information and download links are. People will use this term all the time. I'm just dropping knowledge on this for future reference.
Usually, developers or respected developers have that title just below their name. For example, look at my name and it does not say "recognized developer." This is a title granted by the awesome people that run XDA to people who apply for this title. If accepted, this is a label that informs new users that this is someone of knowledge. Now, if someone doesn't have this title, then this does not mean they did not develop said rom or that they do not know what they're doing. Anyone can be a developer, but just know that there are people here who will easily put you in your place if you pretend to be one.
The thing about XDA is, you download anything and everything at your own risk. By modifying your phone software, you and you alone voided your warranty and accept this. Now, to answer your question. The OP in any thread that is in the Development or Original Development section is supposed to be a "true and reliable" link. If there were ever a virus or malware posted in the Development section, this is unquestionably a website that will remove it. For any and every phone that has a forum on XDA, there are moderators (or mods) who patrol and work for XDA to keep this place awesome, concise, and welcoming to new and old users alike. If you look at any given world/regional/carrier phone, there are a team of moderators who govern those entire threads. Sure, someone can post a spam link at any time but you should feel relatively safe knowing that there are people in place to control for those things. Now, if you see links ANYWHERE else, then I don't suggest downloading it unless you see others have done so as well and provided significant feedback as well.
This is by no means a rule but if a thread has over maybe 30 pages, then it's something that many others have used. Read a few pages if you have any doubts. The most recent posts about the rom are always at the end of the thread. The CM10 link that you posted has over 600 pages...it's trusted lol. The nicest way to say this is...the most popular roms may be the threads with the most pages.
Also, stick to downloading roms from XDA or Rootzwiki and download only what you feel comfortable with downloading to your phone. You mentioned a youtube video earlier, disregard it and refer to DroidStyle's Guide that I linked after your first question. Rooting may not be for you and that is perfectly fine because this is a hobby. As you can tell, there's a LOT to learn and I've barely scratched the surface.
3: In that first link I sent you, the guide to rooting, at the bottom it says that rooting and bootloader unlocking are completely finished but the reason everyone says they think my phone messed up and gave me the unauthorized software message was because I didn't unlock my bootloader. There is a second link in the jelly bean download guide for downloading a different boot unlocker. Is that the one I should be downloading? Should I do that on top of everything else I did in that rooting guide?
Click to expand...
Click to collapse
To properly unlock the bootloader on the GSIII, you need to be rooted first then you need to download EZ Recovery v1.2. I provided and labeled that in a prior post. The "unauthorized software" message occurred because you (I am assuming btw) watched that youtube video from July which predates when our bootloader was officially unlocked (August) and followed its instructions. Since our bootloader was unlocked on August 15, 2012: you must be rooted and unlocked prior to flashing roms or kernels.
You can use that thread to root BUT for the sake of helping you, just download EZ Unlock v1.2 (bootloader unlock tool) that I linked to on Rootzwiki.
4 (last question I promise): Also, in that bootloader unlocker he said I should really "know what I'm doing" if I am running windows because it was intended for Mac and Linux. I run windows and I really don't want to run linux or Ubuntu or anything and i don't have a Mac. I haven't actually downloaded or tried to run the BL unlocker yet but I mean is it really that hard to use on Windows? I know it may sound quite hard to believe because of how much of an idiot I sound like when it comes to rooting and crap but I really AM, at least in my opinion, quite good with computers. At the very least as far as fundamentals go. But yeah when it comes to programming and all this stuff, I'm as dumb as a rock. But what does "know what I'm doing" mean? Is the BL Unlocker you linked to different? Should I just use yours?
Thanks man you're the ****.
Click to expand...
Click to collapse
Because I do not want to confuse you further, the only bootloader unlock tool you need to know of is EZ Unlock v1.2 which is located on Rootzwiki. If you rooted with your laptop, just install EZ Unlock v1.2 and press "Unlock." You only need to do this one time and can uninstall the app afterwards.
To restore your CWM backup, you need to:
1) Root
2) Unlock via EZ Unlock v1.2
3) Install CWM using EZ Recovery
4) Reboot into recovery
5) Restore your backup in CWM recovery
6) Enjoy your backiup predating the triangle warning "Unauthorized software on this device" incident
Did I cover everything? haha

SlimSnoopOS said:
Whenever you use Odin, it's primarily to return to stock or flash a modified image to your Samsung device. In essence what you want to only use Odin for, is to return to the way you purchased your phone: fresh out of the box. You "should" be on a stock image if that's what resolved your previous issue which led to you creating this thread. In all honesty, I'm amazed that you fixed your phone via youtube. Going forward, all that you need to know about the Verizon GSIII is here: http://forum.xda-developers.com/showthread.php?t=1762709
Stick to using XDA for now.
Nightlies = a new version of that rom is updated each night. Some things may break, some things may be fixed but from nightly to nightly, there are new things introduced and new things broken. A nightly is essentially a prolonged "beta" of the overall rom. You can update from one nightly to another or even choose to update weekly if that works best for you, it's all about choice. Now in regards to CM10, CM10 = CyanogenMod10. This is the most popular Android rom and is supported on the most amount of Android phones. The [OFFICIAL] Verizon GSIII CM10 rom is one rom that is pulling software and improvements that are being worked on hourly by the "lead" or primary CyanogenMod team. If that doesn't make sense, the Verizon GSIII version of CM10 is one branch from the giant, ever growing tree that is CyanogenMod.
The "OP" or original post is the very first post, on the first page of any thread. It is also labeled #1. So, the OP of your thread would be your initial post which I responded to. When reading rom threads, the OP is where all the primary information and download links are. People will use this term all the time. I'm just dropping knowledge on this for future reference.
Usually, developers or respected developers have that title just below their name. For example, look at my name and it does not say "recognized developer." This is a title granted by the awesome people that run XDA to people who apply for this title. If accepted, this is a label that informs new users that this is someone of knowledge. Now, if someone doesn't have this title, then this does not mean they did not develop said rom or that they do not know what they're doing. Anyone can be a developer, but just know that there are people here who will easily put you in your place if you pretend to be one.
The thing about XDA is, you download anything and everything at your own risk. By modifying your phone software, you and you alone voided your warranty and accept this. Now, to answer your question. The OP in any thread that is in the Development or Original Development section is supposed to be a "true and reliable" link. If there were ever a virus or malware posted in the Development section, this is unquestionably a website that will remove it. For any and every phone that has a forum on XDA, there are moderators (or mods) who patrol and work for XDA to keep this place awesome, concise, and welcoming to new and old users alike. If you look at any given world/regional/carrier phone, there are a team of moderators who govern those entire threads. Sure, someone can post a spam link at any time but you should feel relatively safe knowing that there are people in place to control for those things. Now, if you see links ANYWHERE else, then I don't suggest downloading it unless you see others have done so as well and provided significant feedback as well.
This is by no means a rule but if a thread has over maybe 30 pages, then it's something that many others have used. Read a few pages if you have any doubts. The most recent posts about the rom are always at the end of the thread. The CM10 link that you posted has over 600 pages...it's trusted lol. The nicest way to say this is...the most popular roms may be the threads with the most pages.
Also, stick to downloading roms from XDA or Rootzwiki and download only what you feel comfortable with downloading to your phone. You mentioned a youtube video earlier, disregard it and refer to DroidStyle's Guide that I linked after your first question. Rooting may not be for you and that is perfectly fine because this is a hobby. As you can tell, there's a LOT to learn and I've barely scratched the surface.
To properly unlock the bootloader on the GSIII, you need to be rooted first then you need to download EZ Recovery v1.2. I provided and labeled that in a prior post. The "unauthorized software" message occurred because you (I am assuming btw) watched that youtube video from July which predates when our bootloader was officially unlocked (August) and followed its instructions. Since our bootloader was unlocked on August 15, 2012: you must be rooted and unlocked prior to flashing roms or kernels.
You can use that thread to root BUT for the sake of helping you, just download EZ Unlock v1.2 (bootloader unlock tool) that I linked to on Rootzwiki.
Because I do not want to confuse you further, the only bootloader unlock tool you need to know of is EZ Unlock v1.2 which is located on Rootzwiki. If you rooted with your laptop, just install EZ Unlock v1.2 and press "Unlock." You only need to do this one time and can uninstall the app afterwards.
To restore your CWM backup, you need to:
1) Root
2) Unlock via EZ Unlock v1.2
3) Install CWM using EZ Recovery
4) Reboot into recovery
5) Restore your backup in CWM recovery
6) Enjoy your backiup predating the triangle warning "Unauthorized software on this device" incident
Did I cover everything? haha
Click to expand...
Click to collapse
Lol. PERFECT. Last couple loose ends though.
1: Will the restore take me to the last time I did all this recovery mode backup crap? The main reason I'm concerned about all this is because I have a game I've put hundreds of hours into that I'm trying to recover my progress on. I'd like it though if when I do restore, I still remain rooted because once I retrieve my game I'd like to try once more to get JB.
2: Is there a way, if my recovery is successful, to get Jelly Bean and THEN recover all this?
Yet again, you rock man. Lol Thanks
Edit: I restored anyways and THANK GOD found that my game save data was still intact. Everything is exactly the way I had it, with root and everything. So NOW my only questions are:
1: Since i rooted my phone the way in the guide I linked to the first time and then the second time I did it the way your guide link said, but the restore was made from the first time I rooted, is that restore I just did from your guide completely gone and now my phone is 100% back to as if I hadn't done anything else after rooting it my way yesterday? If so, should I root my phone yet again except doing it the way your guide said to again because apparently the first way I did it from my guide is what messed my phone up initially, right? So what should I do? Just download EZ-Unlock and keep my phone like it is or start all the way over with your method?
2: Since it was possible to retrieve my game save data with my previous root, do you think if I root again successfully or w/e I need to do and then get Jelly Bean, that my save data and stuff will transfer over as is to Jelly Bean also?

gamer6592 said:
2: Is there a way, if my recovery is successful, to get Jelly Bean and THEN recover all this?
Yet again, you rock man. Lol Thanks
Click to expand...
Click to collapse
Yes, you just restored using CWM correct? First step would be to download "titanium backup" via the Play Store and now you can back up app data (don't do system data) so that when you wipe/flash roms you can restore that app data. Last time I used the free version (a year ago) the free version did app backups/restore but app restores were one at a time and you have to tap install for each app. The paid version (proud paid user here!) does app restore without you having to press "install" for each app you're restoring. There are other app backup utilities but this is likely the most popular and most powerful. You will have to manually recreate your homescreen layout.
Step 2 would be to download a rom, boot into recovery, factory reset then wipe dalvik cache, then flash your rom. Once the rom boots up and you've signed into Gmail, re-download Titanium Backup and restore your apps.
If you were to try this of course.
Edit: I restored anyways and THANK GOD found that my game save data was still intact. Everything is exactly the way I had it, with root and everything. So NOW my only questions are:
1: Since i rooted my phone the way in the guide I linked to the first time and then the second time I did it the way your guide link said, but the restore was made from the first time I rooted, is that restore I just did from your guide completely gone and now my phone is 100% back to as if I hadn't done anything else after rooting it my way yesterday? If so, should I root my phone yet again except doing it the way your guide said to again because apparently the first way I did it from my guide is what messed my phone up initially, right? So what should I do? Just download EZ-Unlock and keep my phone like it is or start all the way over with your method?
Click to expand...
Click to collapse
If you just did a restore via CWM, you're still rooted. Have any doubts? Download "Root Checker" from the Play Store and it will tell you if you're rooted. Your CWM backup is already rooted, you need to be rooted to install a custom recovery so you're set. The CWM restore file is actually located on sdcard/ClockWorkMod/Backup (or something to that effect) and onside should be a file name that contains "1970" and resembles a calendar date. The date is wrong, unfortunately that's just how recovery is. I'm not sure how to rename CWM backups because doing so incorrectly changes the file integrity and will cause your CWM restore to fail should you try restoring it. Your CWM restore file does not delete itself once you use it, it continues to take up space and sits there until you need it or you delete it using CWM.
What messed you up the first time was the fact that you didn't unlock your bootloader before flashing CM10. There's nothing wrong with the CWM backup that you have. Do you have just the one CWM backup or two?
TWRP recovery allows you to name backups but I wouldn't get into that until you're more familiar with CWM and the flashing process.
2: Since it was possible to retrieve my game save data with my previous root, do you think if I root again successfully or w/e I need to do and then get Jelly Bean, that my save data and stuff will transfer over as is to Jelly Bean also?
Click to expand...
Click to collapse
I definitely do and you don't need to root again btw.
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Whenever you use Odin, it's primarily to return to stock or flash a modified image to your Samsung device. In essence what you want to only use Odin for, is to return to the way you purchased your phone: fresh out of the box. You "should" be on a stock image if that's what resolved your previous issue which led to you creating this thread. In all honesty, I'm amazed that you fixed your phone via youtube. Going forward, all that you need to know about the Verizon GSIII is here: http://forum.xda-developers.com/showthread.php?t=1762709
Stick to using XDA for now.
Nightlies = a new version of that rom is updated each night. Some things may break, some things may be fixed but from nightly to nightly, there are new things introduced and new things broken. A nightly is essentially a prolonged "beta" of the overall rom. You can update from one nightly to another or even choose to update weekly if that works best for you, it's all about choice. Now in regards to CM10, CM10 = CyanogenMod10. This is the most popular Android rom and is supported on the most amount of Android phones. The [OFFICIAL] Verizon GSIII CM10 rom is one rom that is pulling software and improvements that are being worked on hourly by the "lead" or primary CyanogenMod team. If that doesn't make sense, the Verizon GSIII version of CM10 is one branch from the giant, ever growing tree that is CyanogenMod.
The "OP" or original post is the very first post, on the first page of any thread. It is also labeled #1. So, the OP of your thread would be your initial post which I responded to. When reading rom threads, the OP is where all the primary information and download links are. People will use this term all the time. I'm just dropping knowledge on this for future reference.
Usually, developers or respected developers have that title just below their name. For example, look at my name and it does not say "recognized developer." This is a title granted by the awesome people that run XDA to people who apply for this title. If accepted, this is a label that informs new users that this is someone of knowledge. Now, if someone doesn't have this title, then this does not mean they did not develop said rom or that they do not know what they're doing. Anyone can be a developer, but just know that there are people here who will easily put you in your place if you pretend to be one.
The thing about XDA is, you download anything and everything at your own risk. By modifying your phone software, you and you alone voided your warranty and accept this. Now, to answer your question. The OP in any thread that is in the Development or Original Development section is supposed to be a "true and reliable" link. If there were ever a virus or malware posted in the Development section, this is unquestionably a website that will remove it. For any and every phone that has a forum on XDA, there are moderators (or mods) who patrol and work for XDA to keep this place awesome, concise, and welcoming to new and old users alike. If you look at any given world/regional/carrier phone, there are a team of moderators who govern those entire threads. Sure, someone can post a spam link at any time but you should feel relatively safe knowing that there are people in place to control for those things. Now, if you see links ANYWHERE else, then I don't suggest downloading it unless you see others have done so as well and provided significant feedback as well.
This is by no means a rule but if a thread has over maybe 30 pages, then it's something that many others have used. Read a few pages if you have any doubts. The most recent posts about the rom are always at the end of the thread. The CM10 link that you posted has over 600 pages...it's trusted lol. The nicest way to say this is...the most popular roms may be the threads with the most pages.
Also, stick to downloading roms from XDA or Rootzwiki and download only what you feel comfortable with downloading to your phone. You mentioned a youtube video earlier, disregard it and refer to DroidStyle's Guide that I linked after your first question. Rooting may not be for you and that is perfectly fine because this is a hobby. As you can tell, there's a LOT to learn and I've barely scratched the surface.
To properly unlock the bootloader on the GSIII, you need to be rooted first then you need to download EZ Recovery v1.2. I provided and labeled that in a prior post. The "unauthorized software" message occurred because you (I am assuming btw) watched that youtube video from July which predates when our bootloader was officially unlocked (August) and followed its instructions. Since our bootloader was unlocked on August 15, 2012: you must be rooted and unlocked prior to flashing roms or kernels.
You can use that thread to root BUT for the sake of helping you, just download EZ Unlock v1.2 (bootloader unlock tool) that I linked to on Rootzwiki.
Because I do not want to confuse you further, the only bootloader unlock tool you need to know of is EZ Unlock v1.2 which is located on Rootzwiki. If you rooted with your laptop, just install EZ Unlock v1.2 and press "Unlock." You only need to do this one time and can uninstall the app afterwards.
To restore your CWM backup, you need to:
1) Root
2) Unlock via EZ Unlock v1.2
3) Install CWM using EZ Recovery
4) Reboot into recovery
5) Restore your backup in CWM recovery
6) Enjoy your backiup predating the triangle warning "Unauthorized software on this device" incident
Did I cover everything? haha
Click to expand...
Click to collapse
Okay awesome. Haha. Perfect. I am wanting to try doing jelly bean again. I'm kinda lost though. That guide doesn't explain ****. So I go to that nightlies page and just download the top one, right? And then download the second from top GAPPS thing in that other link? I download them i.e throw them on my phone or ext SD card from my computer, right? If I do this I'd like to make another backup on my phone because I've even gotten more data on it since I just recovered my backup, but I don't want to have 2 backups just sitting there using up so much memory. How do I delete the old one and replace it with a new and more current one? Will anything mess up if I delete the old one? Also, I made both backups, the "backup" option one from the recovery mode screen, as well as the "backup to external SD card" option one from the same screen so I'd like to delete them both and just make a new one.
When I installed that app and just simply clicked the unlock button, that unlocked my bootloader, right? I keep hearing the word unlock so I can't help but feel like there's multiple things I need to be "unlocking."
So at this point, other than doing a fresher backup, the only thing I have to do is download the top nightly thing or w/e and that GAPPS thing to my computer, then drag them to the folder for either my internal memory or my EXT SD card? Then what do I do? I know I have to execute them from that recovery mode thing but which app do I use to enter recovery mode? Does it matter?
EDIT: Also, I downloaded and bought Titanium Backup and this thing is like trying to learn a foreign language. Wtf am I even supposed to be doing with it? Lol.

gamer6592 said:
Okay awesome. Haha. Perfect. I am wanting to try doing jelly bean again. I'm kinda lost though. That guide doesn't explain ****. So I go to that nightlies page and just download the top one, right? And then download the second from top GAPPS thing in that other link? I download them i.e throw them on my phone or ext SD card from my computer, right?
Click to expand...
Click to collapse
Aight, my question to you is do you like TouchWiz? Because any AOSP rom (CyanogenMod, AOKP, Codename Android, etc.) will basically have the interface/UI of a Google Galaxy Nexus or a Nexus 4. It will not have anything Samsung related. Is this ok? If so, read on.
GApps = Google apps. When you see the GApps page, there should be a few dozen to choose from.
You have the proper steps. Once you download the AOSP rom and respective GApps, move these two zips outside of any folder on either your internal or external sd card. I'm going to stop here and tell you to backup your IMEI, which you only need to do this one time. Everything you need to know is described in this thread. Backup your IMEI:
http://forum.xda-developers.com/showthread.php?t=1852255
If I do this I'd like to make another backup on my phone because I've even gotten more data on it since I just recovered my backup, but I don't want to have 2 backups just sitting there using up so much memory. How do I delete the old one and replace it with a new and more current one? Will anything mess up if I delete the old one? Also, I made both backups, the "backup" option one from the recovery mode screen, as well as the "backup to external SD card" option one from the same screen so I'd like to delete them both and just make a new one.
Click to expand...
Click to collapse
Nope, nothing messes up. Just boot into CWM, go to "backup and restore," and delete the previous backups. Once it deletes them, select the option for "Free up space" for your internal sd card, then do this once more for your external sd card if you deleted backups. Now, make a new backup. I suggest keeping at least an old CWM backup or this new CWM from today on a computer in case of unforeseen issues down the road. This file will still be incomprehensible in the sense that the date on the zip is from 1970 and is off by at least 2-3 months.
When I installed that app and just simply clicked the unlock button, that unlocked my bootloader, right? I keep hearing the word unlock so I can't help but feel like there's multiple things I need to be "unlocking."
Click to expand...
Click to collapse
Correct. It doesn't do anything more once you've selected "unlock." It serves one function, to unlock your bootloader.
So at this point, other than doing a newerbackup, the only thing I have to do is download the top nightly thing or w/e and that GAPPS thing to my computer, then drag them to the folder for either my internal memory or my EXT SD card? Then what do I do? I know I have to execute them from that recovery mode thing but which app do I use to enter recovery mode? Does it matter?
Click to expand...
Click to collapse
Yes, but first I need you to backup your IMEI. Once you've successfully done this, I or someone else will tell you how to wipe/install your first rom.
EDIT: Also, I downloaded and bought Titanium Backup and this thing is like trying to learn a foreign language. Wtf am I even supposed to be doing with it? Lol.
Click to expand...
Click to collapse
To backup app data
1) Open Titanium Backup
2)Tap "Backup/Restore"
3) Tap "Click to edit filters." Make sure "Filter by status" is set to "All", make sure "Filter by type" is set to "User" only. Press the green check mark on the upper right corner. What this does is filter the apps that show and limits them to just the user apps: apps that you downloaded and apps that came with the phone.
4) You should see a list of your apps now. Right? Good, now tap the grey checkmark on the top right then on this new screen tap "Run" for "Backup all user apps."
5) This new list of apps should have checkmarks next to them. Uncheck whichever apps that you do not want to backup. I usually Uncheck Google Apps because that data is backed up to the cloud. Everything checked will be backed up, tap the green checkmark to begin your backup and you're done.
To restore apps, do Step 3 but instead select "backed up" for "Filter by Status" and select "Uninstalled" for "Filter by type." Then for Step 4, scroll down and tap "Run" for "Restore missing apps with data." I strongly suggest only restoring just that one game's data and maybe a few apps to minimize any issues that will occur once you use the rom.
**This does not backup texts nor phone calls.
Most importantly, only download roms to your phone if it states: d2vzw or SCH-i535. This is our device's model name.

SlimSnoopOS said:
Aight, my question to you is do you like TouchWiz? Because any AOSP rom (CyanogenMod, AOKP, Codename Android, etc.) will basically have the interface/UI of a Google Galaxy Nexus or a Nexus 4. It will not have anything Samsung related. Is this ok? If so, read on.
GApps = Google apps. When you see the GApps page, there should be a few dozen to choose from.
You have the proper steps. Once you download the AOSP rom and respective GApps, move these two zips outside of any folder on either your internal or external sd card. I'm going to stop here and tell you to backup your IMEI, which you only need to do this one time. Everything you need to know is described in this thread. Backup your IMEI:
http://forum.xda-developers.com/showthread.php?t=1852255
Nope, nothing messes up. Just boot into CWM, go to "backup and restore," and delete the previous backups. Once it deletes them, select the option for "Free up space" for your internal sd card, then do this once more for your external sd card if you deleted backups. Now, make a new backup. I suggest keeping at least an old CWM backup or this new CWM from today on a computer in case of unforeseen issues down the road. This file will still be incomprehensible in the sense that the date on the zip is from 1970 and is off by at least 2-3 months.
Correct. It doesn't do anything more once you've selected "unlock." It serves one function, to unlock your bootloader.
Yes, but first I need you to backup your IMEI. Once you've successfully done this, I or someone else will tell you how to wipe/install your first rom.
To backup app data
1) Open Titanium Backup
2)Tap "Backup/Restore"
3) Tap "Click to edit filters." Make sure "Filter by status" is set to "All", make sure "Filter by type" is set to "User" only. Press the green check mark on the upper right corner. What this does is filter the apps that show and limits them to just the user apps: apps that you downloaded and apps that came with the phone.
4) You should see a list of your apps now. Right? Good, now tap the grey checkmark on the top right then on this new screen tap "Run" for "Backup all user apps."
5) This new list of apps should have checkmarks next to them. Uncheck whichever apps that you do not want to backup. I usually Uncheck Google Apps because that data is backed up to the cloud. Everything checked will be backed up, tap the green checkmark to begin your backup and you're done.
To restore apps, do Step 3 but instead select "backed up" for "Filter by Status" and select "Uninstalled" for "Filter by type." Then for Step 4, scroll down and tap "Run" for "Restore missing apps with data." I strongly suggest only restoring just that one game's data and maybe a few apps to minimize any issues that will occur once you use the rom.
**This does not backup texts nor phone calls.
Most importantly, only download roms to your phone if it states: d2vzw or SCH-i535. This is our device's model name.
Click to expand...
Click to collapse
Gosh this is a pain in my ass... I've been working on this ALL DAY. Kid you not.
I finally just figured out how to do everything with downloading that ADB crap and I am doing part B (SynergyROM's "Plan B" manual backup). I am really worried because I have a slight problem... Now whenever I boot into recovery mode (holding volume up+home+power) it doesn't look the same as when it did the previous times i had to boot into recovery. The options are completely different and there isn't one for "install zip from sd card". Following is a description of what it says/how it looks now:
(it says the following in blue letters)
"ANDROID SYSTEM RECOVERY <3e>
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache"
____________________________________________________________
(then it says the following in yellow letters)
# manual mode #
-- Applying Multi-CSC...
Applied the CSC-code : VZW
Successfully applied multi-CSC
And it has that picture of the android in the background with the thing that looks like you could twist it on it's back and the hologram coming out of it's front.
Why is my recovery mode different all of a sudden? It's like I'm just getting the standard Android version of RM now.
EDIT: I clicked "flash CWM Recovery" and now it boots into the regular CWM RM screen.
Okay. I'm all done with the IMEI backups and stuff.
I can haz Jelly Bean now?
Man I wish there was an IM or something I could contact you at so I didn't have to have you keep coming back to this thread so many times. Plus, I'm impatient. I want JB already! Lol. I appreciate it though!

Go haz your jellybeans! Lol sorry for the delayed response, I just got off work. Keep a backup of the Synergy folder (the backed up IMEI file) on your laptop for safe keeping.
As a reminder, this AOSP rom you're installing is stock Jellybean aka what's on a Galaxy Nexus or Nexus 4.
To flash a rom:
1) boot into CWM recovery
2) Factory reset, wipe cache, go into "Advanced" and wipe Dalvik Cache
3) Install rom. If you're installing CM10, AOKP, or any Android Open Source Project (A.O.S.P.) rom then install GApps as well.
4) Reboot and enjoy.
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Aight, my question to you is do you like TouchWiz? Because any AOSP rom (CyanogenMod, AOKP, Codename Android, etc.) will basically have the interface/UI of a Google Galaxy Nexus or a Nexus 4. It will not have anything Samsung related. Is this ok? If so, read on.
GApps = Google apps. When you see the GApps page, there should be a few dozen to choose from.
You have the proper steps. Once you download the AOSP rom and respective GApps, move these two zips outside of any folder on either your internal or external sd card. I'm going to stop here and tell you to backup your IMEI, which you only need to do this one time. Everything you need to know is described in this thread. Backup your IMEI:
http://forum.xda-developers.com/showthread.php?t=1852255
Nope, nothing messes up. Just boot into CWM, go to "backup and restore," and delete the previous backups. Once it deletes them, select the option for "Free up space" for your internal sd card, then do this once more for your external sd card if you deleted backups. Now, make a new backup. I suggest keeping at least an old CWM backup or this new CWM from today on a computer in case of unforeseen issues down the road. This file will still be incomprehensible in the sense that the date on the zip is from 1970 and is off by at least 2-3 months.
Correct. It doesn't do anything more once you've selected "unlock." It serves one function, to unlock your bootloader.
Yes, but first I need you to backup your IMEI. Once you've successfully done this, I or someone else will tell you how to wipe/install your first rom.
To backup app data
1) Open Titanium Backup
2)Tap "Backup/Restore"
3) Tap "Click to edit filters." Make sure "Filter by status" is set to "All", make sure "Filter by type" is set to "User" only. Press the green check mark on the upper right corner. What this does is filter the apps that show and limits them to just the user apps: apps that you downloaded and apps that came with the phone.
4) You should see a list of your apps now. Right? Good, now tap the grey checkmark on the top right then on this new screen tap "Run" for "Backup all user apps."
5) This new list of apps should have checkmarks next to them. Uncheck whichever apps that you do not want to backup. I usually Uncheck Google Apps because that data is backed up to the cloud. Everything checked will be backed up, tap the green checkmark to begin your backup and you're done.
To restore apps, do Step 3 but instead select "backed up" for "Filter by Status" and select "Uninstalled" for "Filter by type." Then for Step 4, scroll down and tap "Run" for "Restore missing apps with data." I strongly suggest only restoring just that one game's data and maybe a few apps to minimize any issues that will occur once you use the rom.
**This does not backup texts nor phone calls.
Most importantly, only download roms to your phone if it states: d2vzw or SCH-i535. This is our device's model name.
Click to expand...
Click to collapse
SlimSnoopOS said:
Go haz your jellybeans! Lol sorry for the delayed response, I just got off work. Keep a backup of the Synergy folder (the backed up IMEI file) on your laptop for safe keeping.
As a reminder, this AOSP rom you're installing is stock Jellybean aka what's on a Galaxy Nexus or Nexus 4.
To flash a rom:
1) boot into CWM recovery
2) Factory reset, wipe cache, go into "Advanced" and wipe Dalvik Cache
3) Install rom. If you're installing CM10, AOKP, or any Android Open Source Project (A.O.S.P.) rom then install GApps as well.
4) Reboot and enjoy.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Lol. Okay thanks but.. I don't remember if you ever answered me on whether it matters if I drag the thing to my phone or my SD card. And also, if I just download and drag the top "nightly" thing and then download and drag the 2nd from top GAPPS thing. Should I create a folder and put them both in or just leave them out by themselves in the main directory or does it matter?

Just put both the nightly and Gapps on your internal storage for now. Leave them on the root of the sd card (in no folders).
If recovery let's you use your external sd card, then use that if you prefer cuz it doesn't matter. If recovery fails to see your external sd card (meaning it didnt let you perform a backup to the external sd) then it needs to be formatted to Fat32 before you can flash anything off of the external sd.
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Just put both the nightly and Gapps on your internal storage for now. Leave them on the root of the sd card (in no folders).
If recovery let's you use your external sd card, then use that if you prefer cuz it doesn't matter. If recovery fails to see your external sd card (meaning it didnt let you perform a backup to the external sd) then it needs to be formatted to Fat32 before you can flash anything off of the external sd.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yay!!! I did it!! You rock man I owe you one. My only other question is how I get everything back on my phone like my apps and app data and stuff. Thanks dude!

gamer6592 said:
Yay!!! I did it!! You rock man I owe you one. My only other question is how I get everything back on my phone like my apps and app data and stuff. Thanks dude!
Click to expand...
Click to collapse
TB = Titanium Backup
Congrats! From my previous post on TB:
To restore apps with TB, do Step 3 but instead select "backed up" for "Filter by Status" and select "Uninstalled" for "Filter by type." Then for Step 4, scroll down and tap "Run" for "Restore missing apps with data." I strongly suggest only restoring just that one game's data and maybe data from a few other apps to minimize any issues that will occur once you use the rom. I rarely have force closes or random issues after restoring apps but that's a risk one takes when restoring apps and app data. If you notice an app is behaving unusually, uninstall it and then re-
download it from the Play Store.
Never restore system data.
Sent from my SCH-I535 using xda app-developers app

lol.. you're gonna hate me but... I'm pretty sure I want to switch back... TB messed up my game data so I can't recover it so I really want to at least recover my entire phone from the CWM backup and THEN maybe go back to jelly bean again because the game I'm playing let's you store your data on their servers so I'd rather do that and THEN come back to jelly bean and restore from their servers... but yeah my game is not working at all :'-( lol.. fml

Just restore your Nandroid backup in CWM then do whatever it was you needed to do
Sent from my SCH-I535 using xda app-developers app

how to tell if bootloader is unlocked after rooting...

followed this thread http://forum.xda-developers.com/showthread.php?t=2046439 yesterday to root my samsung galaxy s3 and unlock the bootloader, but i am unsure if it worked 100%. i know it is rooted because i dl'ed titanium backup and it works, but how do i tell if my bootloader is unlocked or not? did a search, couldn't find an answer, so i am asking here.

There's not really a concrete way to tell however if you reboot and the Samsung logo flashes by in a second then you're unlocked. Typically it sits for three to five seconds on this screen but once unlocked, this screen just flashes by.
Sent from my SCH-I535 using xda app-developers app

considering we all use the same unlocked aboot.img, it's pretty easy to concretely verify that you're bootloader is unlocked.
but im too stupid to write a script, and no one wants to do it because it's a bit longer than timing the samsung boot logo (which when you compare time-invested to information given, is pretty reliable)
basically involves comparing the md5 of the aboot.img of your phone to the known unlocked aboot.img (will try to find the terminal/adb shell commandsi posted before)
found it:
The unlocked md5 is: 0ba9ad45fc15cf3d62af7dd363686b3f
So if you pull a copy of your current aboot partition and save it to your sd card.
Run the following in ADB shell or terminal. Make sure you run it as superuser:
dd if=/dev/block/mmcblk0p5 of=/storage/sdcard0/aboot.img
That command will save an aboot.img to your internal sd. Check it's md5 and see if it matches.
Can run in adb:
md5 /storage/sdcard0/aboot.img
or
use any of the many md5 checking apps out there

SlimSnoopOS said:
There's not really a concrete way to tell however if you reboot and the Samsung logo flashes by in a second then you're unlocked. Typically it sits for three to five seconds on this screen but once unlocked, this screen just flashes by.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
ok, cool, thanks! so it looks like the root took, but the bootloader didn't unlock. the samsung logo took 3 seconds to pass by. so what do i need to do now to unlock it? should i repeat the steps from what i did yesterday?

corbn89 said:
considering we all use the same unlocked aboot.img, it's pretty easy to concretely verify that you're bootloader is unlocked.
but im too stupid to write a script, and no one wants to do it because it's a bit longer than timing the samsung boot logo (which when you compare time-invested to information given, is pretty reliable)
basically involves comparing the md5 of the aboot.img of your phone to the known unlocked aboot.img (will try to find the terminal/adb shell commandsi posted before)
found it:
The unlocked md5 is: 0ba9ad45fc15cf3d62af7dd363686b3f
So if you pull a copy of your current aboot partition and save it to your sd card.
Run the following in ADB shell or terminal. Make sure you run it as superuser:
dd if=/dev/block/mmcblk0p5 of=/storage/sdcard0/aboot.img
That command will save an aboot.img to your internal sd. Check it's md5 and see if it matches.
Can run in adb:
md5 /storage/sdcard0/aboot.img
or
use any of the many md5 checking apps out there
Click to expand...
Click to collapse
I'm gonna bookmark this cuz this is a really good explanation. I don't ever suggest dd methods (nor memorize them) cuz I know a single typo could brick the device.
a.demarco said:
ok, cool, thanks! so it looks like the root took, but the bootloader didn't unlock. the samsung logo took 3 seconds to pass by. so what do i need to do now to unlock it? should i repeat the steps from what i did yesterday?
Click to expand...
Click to collapse
Just sideload EZ Unlock v1.2 and press the unlock button. You'll hear an audio confirmation and boom, unlocked.

ok, so now i am confused. i have the correct supersu+bootloader on the sd card, and the supersu app on the phone, but the samsung logo still takes a while to disappear.
edit: nevermind, got it working, samsung logo now just flashes by. thanks again for all your help!

SlimSnoopOS said:
I'm gonna bookmark this cuz this is a really good explanation. I don't ever suggest dd methods (nor memorize them) cuz I know a single typo could brick the device.
Just sideload EZ Unlock v1.2 and press the unlock button. You'll hear an audio confirmation and boom, unlocked.
Click to expand...
Click to collapse
Yep, it's pretty straightforward. I tested my unlocked bootloader with this. Haven't had a chance to tested while locked though (will have to wait till my next odin to stock).
But yeah, as long as no one switches the "if" and the "of" it should be safe (aka accidentally pasting something into the normally inaccessible partition rather than copying out to the sd)
---------- Post added at 10:32 AM ---------- Previous post was at 10:29 AM ----------
a.demarco said:
ok, so now i am confused. i have the correct supersu+bootloader on the sd card, and the supersu app on the phone, but the samsung logo still takes a while to disappear.
Click to expand...
Click to collapse
sometime that image doesn't take for whatever reason. just use the app slimsnoop os linked to, should do the trick

a.demarco said:
ok, so now i am confused. i have the correct supersu+bootloader on the sd card, and the supersu app on the phone, but the samsung logo still takes a while to disappear.
edit: nevermind, got it working, samsung logo now just flashes by. thanks again for all your help!
Click to expand...
Click to collapse
Great! Just so you know, you can uninstall EZ Unlock (if you installed it that is) and never use it again. You will not need it again unless you do the following which which will re-lock your bootloader:
1) take a Verizon OTA
2) Odin flash a stock image
Make sure to do a nandroid and happy flashing!

SlimSnoopOS said:
Great! Just so you know, you can uninstall EZ Unlock (if you installed it that is) and never use it again. You will not need it again unless you do the following which which will re-lock your bootloader:
1) take a Verizon OTA
2) Odin flash a stock image
Make sure to do a nandroid and happy flashing!
Click to expand...
Click to collapse
still learning all about this, i will have to search what a nandroid is. i am doing a backup currently using titanium backup (free version right now), and it seems to be working well.
i want to flash either the cm 10.1 or jellybeans v.15 i think, just gotta read more about them.

a.demarco said:
still learning all about this, i will have to search what a nandroid is. i am doing a backup currently using titanium backup (free version right now), and it seems to be working well.
i want to flash either the cm 10.1 or jellybeans v.15 i think, just gotta read more about them.
Click to expand...
Click to collapse
Ahh, you'll see a lot of terms thrown around like that haha here's a glossary of common terms taken from DroidStyle's guide in the dev section.
Basically a nandroid is a complete system or rom backup akin to a computer backup. You perform a nandroid in custom recovery (CWM or TWRP) however its labeled as "Backup" in both recoveries. "Nandroid" is just the common name for it. The reason you perform a nandroid is to have a safe point to restore your phone to if you flash a rom, kernel, or mod and your phone begins to misbehave. Before flashing your first rom, it's highly recommended that you perform a nandroid in your custom recovery and even save a copy on a computer so you always have that in two places. It may take about 1.5-2 GB's of space per backup so I wouldn't keep too many on your phone at a time.

SlimSnoopOS said:
Ahh, you'll see a lot of terms thrown around like that haha here's a glossary of common terms taken from DroidStyle's guide in the dev section.
Basically a nandroid is a complete system or rom backup akin to a computer backup. You perform a nandroid in custom recovery (CWM or TWRP) however its labeled as "Backup" in both recoveries. "Nandroid" is just the common name for it. The reason you perform a nandroid is to have a safe point to restore your phone to if you flash a rom, kernel, or mod and your phone begins to misbehave. Before flashing your first rom, it's highly recommended that you perform a nandroid in your custom recovery and even save a copy on a computer so you always have that in two places. It may take about 1.5-2 GB's of space per backup so I wouldn't keep too many on your phone at a time.
Click to expand...
Click to collapse
good to know... should i bother with titanium backup at all? or just boot into cwm and do a nandroid from there?

a.demarco said:
good to know... should i bother with titanium backup at all? or just boot into cwm and do a nandroid from there?
Click to expand...
Click to collapse
Perform both actually. Backup apps with TB so when you flash a rom you can restore apps at once if you actually like the rom. I typically restore a few apps when trying new roms then if I like the rom, I'll restore more apps. Backup with CWM so that in case you dislike the rom you flash, you can completely restore to your previous rom. They serve two similar functions yet distinctly different as well.

SlimSnoopOS said:
Perform both actually. Backup apps with TB so when you flash a rom you can restore apps at once if you actually like the rom. I typically restore a few apps when trying new roms then if I like the rom, I'll restore more apps. Backup with CWM so that in case you dislike the rom you flash, you can completely restore to your previous rom. They serve two similar functions yet distinctly different as well.
Click to expand...
Click to collapse
awesome, thank you for the help. doing the nandroid backup right now through cwm, backing it up to the external sd card so i can then save it to the computer.
so i should only use the tb to back up the apps? oops, i backed everything up on it, was wondering why it took so damn long!

a.demarco said:
awesome, thank you for the help. doing the nandroid backup right now through cwm, backing it up to the external sd card so i can then save it to the computer.
so i should only use the tb to back up the apps? oops, i backed everything up on it, was wondering why it took so damn long!
Click to expand...
Click to collapse
No problem! Yea, TB is useful for a lot once you have a grasp of the basic functions. Only backup user apps and do not backup/restore system apps. Depending on the number of apps and their storage size, backup time varies. You can always delete the previous TB backup files cuz its stored in the Titanium Backup folder of your internal or external sdcard. Doesn't hurt to copy that to a computer every once in awhile too.

corbn89 said:
considering we all use the same unlocked aboot.img, it's pretty easy to concretely verify that you're bootloader is unlocked.
but im too stupid to write a script, and no one wants to do it because it's a bit longer than timing the samsung boot logo (which when you compare time-invested to information given, is pretty reliable)
basically involves comparing the md5 of the aboot.img of your phone to the known unlocked aboot.img (will try to find the terminal/adb shell commandsi posted before)
found it:
The unlocked md5 is: 0ba9ad45fc15cf3d62af7dd363686b3f
So if you pull a copy of your current aboot partition and save it to your sd card.
Run the following in ADB shell or terminal. Make sure you run it as superuser:
dd if=/dev/block/mmcblk0p5 of=/storage/sdcard0/aboot.img
That command will save an aboot.img to your internal sd. Check it's md5 and see if it matches.
Can run in adb:
md5 /storage/sdcard0/aboot.img
or
use any of the many md5 checking apps out there
Click to expand...
Click to collapse
So when I start up terminal emulator, next to where it says "[email protected]:/ $" I type in su right? Then hit enter? Then on the following line I type: "dd if=/dev/block/mmcblk0p5 of=/storage/sdcard0/aboot.img"
After I type this a copy of aboot.img will be saved to my external memory card and from there I can match it up with the unlocked md5 and if it matches this garuntees that my bootloader is unlocked. Is this correct?
I'm a noob, please forgive me.

jricks said:
So when I start up terminal emulator, next to where it says "[email protected]:/ $" I type in su right? Then hit enter? Then on the following line I type: "dd if=/dev/block/mmcblk0p5 of=/storage/sdcard0/aboot.img"
Click to expand...
Click to collapse
Correct.
After I type this a copy of aboot.img will be saved to my external memory card and from there I can match it up with the unlocked md5 and if it matches this garuntees that my bootloader is unlocked. Is this correct?
I'm a noob, please forgive me.
Click to expand...
Click to collapse
It will save to your internal sdcard. sdcard0 = internal storage, sdcard1 = external sdcard.
Sent from my SCH-I535 using xda app-developers app

Much appreciated my friend.
Sent from my SCH-I535 using xda app-developers app

Let us know what your results are and which method you used to unlock.
I confirmed it on my phone that used the ez unlock app but multiple trials by others would be beneficial. Thanks

SlimSnoopOS said:
Correct.
It will save to your internal sdcard. sdcard0 = internal storage, sdcard1 = external sdcard.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I did everything mentioned above and it saved to my internal card however im unable to view it. What program do i to install to view it.
Sent from my SCH-I535 using xda app-developers app

You don't need to view it. You just need to run the file through a md5 checksum app or check the md5 with terminal or adb using the command I posted earlier