Hello all
I find myself posting here because I don't have the required 10 posts to pose my question elsewhere.
I recently switched from Clockwork to AmonRA recovery. My second backup was of my stock SenseROM. My first backup was of CM 7.0.2.1, which could not be restored. My flash to CM 7.0.3.1 was successful, so I wasn't concerned.
Now, I cannot restore the stock SenseROM. I have transferred the recovery log to the SD card, but do not know how to decipher it.
I did change the name of the folder in /sdcard/nandroid, but not the names of the folders inside that folder.
Basically I'm not sure the proper way to rename a RA backup, and if there is any way to fix/repair the stock SenseROM that I cannot restore.
Thanks for your patience and help.
Skid
Skid71 said:
Hello all
I find myself posting here because I don't have the required 10 posts to pose my question elsewhere.
I recently switched from Clockwork to AmonRA recovery. My second backup was of my stock SenseROM. My first backup was of CM 7.0.2.1, which could not be restored. My flash to CM 7.0.3.1 was successful, so I wasn't concerned.
Now, I cannot restore the stock SenseROM. I have transferred the recovery log to the SD card, but do not know how to decipher it.
I did change the name of the folder in /sdcard/nandroid, but not the names of the folders inside that folder.
Basically I'm not sure the proper way to rename a RA backup, and if there is any way to fix/repair the stock SenseROM that I cannot restore.
Thanks for your patience and help.
Skid
Click to expand...
Click to collapse
I don't know the name it needs to be. But if you need stock rom Ruu sense to unroot I have links to the latest Ruu you would need in my guide.
Skid71 said:
Hello all
I find myself posting here because I don't have the required 10 posts to pose my question elsewhere.
I recently switched from Clockwork to AmonRA recovery. My second backup was of my stock SenseROM. My first backup was of CM 7.0.2.1, which could not be restored. My flash to CM 7.0.3.1 was successful, so I wasn't concerned.
Now, I cannot restore the stock SenseROM. I have transferred the recovery log to the SD card, but do not know how to decipher it.
I did change the name of the folder in /sdcard/nandroid, but not the names of the folders inside that folder.
Basically I'm not sure the proper way to rename a RA backup, and if there is any way to fix/repair the stock SenseROM that I cannot restore.
Thanks for your patience and help.
Skid
Click to expand...
Click to collapse
I was actually at a restaurant eating dinner when I was initially replying to your post and then all of a sudden, my phone rebooted and kept bootlooping so I had to rewipe and restore a nandroid backup while driving home...Sorry. Anyway, you cannot rename the folder which the nandroid backups are kept in, but you can rename the backups themselves as long as you don't use special characters. If you did change the name of the folder that the nandroids are in, you will not be able to restore. If you remember the name of the folder, change the name back to what it was. If you're familiar with ADB, connect your device to your computer, start the Terminal app (I use a MacBook) and then type, "adb connect". It *should* display the name of your device which is the same name as the folder that the nandroids are kept in.
Skid71 said:
Hello all
I find myself posting here because I don't have the required 10 posts to pose my question elsewhere.
I recently switched from Clockwork to AmonRA recovery. My second backup was of my stock SenseROM. My first backup was of CM 7.0.2.1, which could not be restored. My flash to CM 7.0.3.1 was successful, so I wasn't concerned.
Now, I cannot restore the stock SenseROM. I have transferred the recovery log to the SD card, but do not know how to decipher it.
I did change the name of the folder in /sdcard/nandroid, but not the names of the folders inside that folder.
Basically I'm not sure the proper way to rename a RA backup, and if there is any way to fix/repair the stock SenseROM that I cannot restore.
Thanks for your patience and help.
Skid
Click to expand...
Click to collapse
Just to be sure, the backup you're trying to restore is one that was created with Amon Ra, right? You can't restore a backup that was made with Clockwork. So, as long as the backup you're restoring was made by Amon Ra, it should restore.
You said you renamed the file right? Which folder exactly did you rename? If you renamed the nandroid backup itself, it cannot have any spaces in the name, or any odd characters. Keep the name simple, with no spaces. If that's what you renamed, try renaming it to something short and simple, then try restoring again.
If you renamed a different folder (the folder that the nandroid backups are actually in), I don't think you can do that at all. mine is like this : /nandroid/HT066HL***/(nandroid backups). If you renamed the one that is bolded, I'm almost positive that will bork things. You can only rename the backups themselves, and as I said, you can't use spaces. Double check your stuff, and see if it sounds like any of that might be your problem. Good luck.
EDIT: Dang Doug! Your post wasn't there when I started typing! I got distracted on a phone call during my reply, and delayed it way too long. Didn't mean to step on your toes man. At least our advice is the same! BTW, which rom bootlooped ya? I had that happen on decks 1.2m today.
k2buckley said:
Just to be sure, the backup you're trying to restore is one that was created with Amon Ra, right? You can't restore a backup that was made with Clockwork. So, as long as the backup you're restoring was made by Amon Ra, it should restore.
You said you renamed the file right? Which folder exactly did you rename? If you renamed the nandroid backup itself, it cannot have any spaces in the name, or any odd characters. Keep the name simple, with no spaces. If that's what you renamed, try renaming it to something short and simple, then try restoring again.
If you renamed a different folder (the folder that the nandroid backups are actually in), I don't think you can do that at all. mine is like this : /nandroid/HT066HL***/(nandroid backups). If you renamed the one that is bolded, I'm almost positive that will bork things. You can only rename the backups themselves, and as I said, you can't use spaces. Double check your stuff, and see if it sounds like any of that might be your problem. Good luck.
EDIT: Dang Doug! Your post wasn't there when I started typing! I got distracted on a phone call during my reply, and delayed it way too long. Didn't mean to step on your toes man. At least our advice is the same! BTW, which rom bootlooped ya? I had that happen on decks 1.2m today.
Click to expand...
Click to collapse
I'm thinking I borked myself then
I'll try to describe this...
nandroid/AmonRASenseROM/BDS-20110525-****
I should not have changed the bolded part, but instead, change the "BDS-20110525****" part?
I think I can change the name of that folder, or better yet, just move the "BDS..." folder to the folder that is named HT0CFH***** which contains my current CM 7.0.3.1 backup. I DID NOT change that folder name.
My gosh, did that make any sense?
And yes, that Sense ROM was backed up with AmonRA.
Really appreciate the help!
Skid71 said:
I'm thinking I borked myself then
I'll try to describe this...
nandroid/AmonRASenseROM/BDS-20110525-****
I should not have changed the bolded part, but instead, change the "BDS-20110525****" part?
I think I can change the name of that folder, or better yet, just move the "BDS..." folder to the folder that is named HT0CFH***** which contains my current CM 7.0.3.1 backup. I DID NOT change that folder name.
My gosh, did that make any sense?
And yes, that Sense ROM was backed up with AmonRA.
Really appreciate the help!
Click to expand...
Click to collapse
That is correct. You should not have changed the bolded part. You wanted to leave that what it originally was (I think it may be the phone's serial number, but not sure). The BDS-20110525 is the actual backup that you created. It is coded by the date you created the backup. So it looks like you created that one on the 25th (or 24th, often times the recovery will stamp my nandroid backup time as the next day for some reason. I'll make one on the 19th, but will have the date code of the 20th in there). So, as far as fixing the issue goes....I'm not positive how to get that folder named back to what it originally was..as I'm not sure what the exact name would have been. Hopefully someone else will chime in on it, and confirm what the name of that folder should be. I'll check in a second and see if that number is indeed my serial number. If it is, you should be able to rename it to that, and try it out.
Yes, I confirmed that the name of that folder should indeed be the serial number of your phone, in all capital letters. To get your serial number, you can either use adb, by typing 'adb devices', and the number it gives back to you will be your serial. If not, shut your phone down and pull your battery. Your serial number is back there. If you rename that folder with your serial number, you should be good to go (hopefully). Give it a shot.
Edit: And just to clarify, the one you CAN rename, is the BDS-20110525 one. Just be sure to not have any spaces in the name, or odd characters, as has already been noted. You should be on the right track after that.
k2buckley said:
That is correct. You should not have changed the bolded part. You wanted to leave that what it originally was (I think it may be the phone's serial number, but not sure). The BDS-20110525 is the actual backup that you created. It is coded by the date you created the backup. So it looks like you created that one on the 25th (or 24th, often times the recovery will stamp my nandroid backup time as the next day for some reason. I'll make one on the 19th, but will have the date code of the 20th in there). So, as far as fixing the issue goes....I'm not positive how to get that folder named back to what it originally was..as I'm not sure what the exact name would have been. Hopefully someone else will chime in on it, and confirm what the name of that folder should be. I'll check in a second and see if that number is indeed my serial number. If it is, you should be able to rename it to that, and try it out.
Click to expand...
Click to collapse
In trying to decipher the recovery log, I noticed that the other folder created in /nandroid was also the number of the phone (not sure if it's the serial). When I first made the Sense ROM backup, I changed the name of that folder (instead of the folder contained inside), then made a backup of the CM ROM. I noticed that it created another folder within /nandroid that was identical to the folder it created when I made the Sense backup. I hope I'm not confusing you as much as myself.
Anyway, what I did was rename the correct Sense ROM folder, then moved it to the "HT0CFHL****" folder. I hope that does the trick.
**Edit** I did use a - when renaming the Sense ROM. No spaces. That sound alright?
______________________________________________________________
Hope you don't mind another question while I'm here.
When performing a backup, should I just do a backup of the items that AmonRA recovery already has chosen, or should I do the Wimax, sd-ext, etc?
Would just like to make sure I'm doing this right.
Wish I would have started out with AmonRA instead of Clockwork (no offense meant)
Thanks again
Skid
Skid71 said:
In trying to decipher the recovery log, I noticed that the other folder created in /nandroid was also the number of the phone (not sure if it's the serial). When I first made the Sense ROM backup, I changed the name of that folder (instead of the folder contained inside), then made a backup of the CM ROM. I noticed that it created another folder within /nandroid that was identical to the folder it created when I made the Sense backup. I hope I'm not confusing you as much as myself.
Anyway, what I did was rename the correct Sense ROM folder, then moved it to the "HT0CFHL****" folder. I hope that does the trick.
______________________________________________________________
Hope you don't mind another question while I'm here.
When performing a backup, should I just do a backup of the items that AmonRA recovery already has chosen, or should I do the Wimax, sd-ext, etc?
Would just like to make sure I'm doing this right.
Wish I would have started out with AmonRA instead of Clockwork (no offense meant)
Thanks again
Skid
Click to expand...
Click to collapse
Okay, I am slightly confused, but not too confused, haha. So when you created the CM backup, and you say that you were left with a duplicate folder, which folder do you mean? That's all I'm confused about. Do you mean the one containing your serial number, that you renamed (the one that starts with H), or do you mean the BDS-2011...one? If you mean the BDS-2011 one, then that is normal. Every backup you create is automatically named BDS-20110524 (or whatever the date/time is). If you look closer, the time should be different. Anyways, if that is not what you're referring to, then it may have regenerated the folder which contains your backups (because it has to be named as your serial number, so since you changed the name of the first one, it may have regenerated a new one. In which case, if you moved your first backup to that new folder, it SHOULD work. (i think that's what you said you were doing..). If that worked, just delete the folder that you renamed, and leave the new one. You should then be good to go.
I hope I understood you right. If I did, it sounds like you should be set.
EDIT: forgot to answer your second question:
To be honest, I don't use Amon Ra 2.3. I have always stayed with the earlier version of 1.8.0, as it has NEVER faild me, so I saw no reason to change it. It is slightly different than the version you're on, as there are no backup options. It just automatically backs up what it needs to. With your version you do have the option to select what you backup. I for sure would make a couple backups that include your wimax.img. That is important to have, for if you ever lose your RSA keys, that backup of the wimax.img is how you would recover them. You would only need to include sd-ext if your sd card is partitioned, and you're using DT a2sd. If you are, then including the sd-ext is a must. If you don't have your card partitioned, or don't know what DT a2sd is, then you don't need to worry about backing up your sd-ext. I honestly don't recall what the other options are, and hopefully someone else who actively uses that recovery will help ya with that. I believe I remember there being an android_secure, recovery, or something like that. Sorry. Just definitely include the wimax.img. I believe that my friend Dougjamal posted something in the General section about the recommended way to backup using Amon Ra. Search that out, and you may find the answers. Good luck
Here's how I rename my nandroids and it works.
\nandroid\HT121HL07014\BDEARS-20110318-0300-koni_III
Anything else i Ever tried = fail
k2buckley said:
Okay, I am slightly confused, but not too confused, haha. So when you created the CM backup, and you say that you were left with a duplicate folder, which folder do you mean? That's all I'm confused about. Do you mean the one containing your serial number, that you renamed (the one that starts with H), or do you mean the BDS-2011...one? If you mean the BDS-2011 one, then that is normal. Every backup you create is automatically named BDS-20110524 (or whatever the date/time is). If you look closer, the time should be different. Anyways, if that is not what you're referring to, then it may have regenerated the folder which contains your backups (because it has to be named as your serial number, so since you changed the name of the first one, it may have regenerated a new one. In which case, if you moved your first backup to that new folder, it SHOULD work. (i think that's what you said you were doing..). If that worked, just delete the folder that you renamed, and leave the new one. You should then be good to go.
I hope I understood you right. If I did, it sounds like you should be set.
Click to expand...
Click to collapse
Yeah, confusing. But yes, you are correct sir. I'm itching to try flashing to it, but I'm a bit hesitant since the only current ROM backup I have is one with the pre-selected (in AmonRA) choices.
I'm not communicating very effectively tonight.
I appreciate the help.
Skid71 said:
Yeah, confusing. But yes, you are correct sir. I'm itching to try flashing to it, but I'm a bit hesitant since the only current ROM backup I have is one with the pre-selected (in AmonRA) choices.
I'm not communicating very effectively tonight.
I appreciate the help.
Click to expand...
Click to collapse
Well, I think you should be all set. If not, this is what I would do. Take both of your nandroid backups (the folder labeled BDS-2011....) and copy them to a different folder.
Then be sure you have a directory on your sd card named: nandroid/(your serial number). Then place both of your nandroid backups in that folder. (the one with your serial number). Then boot to recovery, and select backup/restore. Then select 'restore backup'. You should then see the folder named as your serial number. Select it. You should then see your backups. Select the one you want to restore, and try to do it. It should work.
k2buckley said:
EDIT: Dang Doug! Your post wasn't there when I started typing! I got distracted on a phone call during my reply, and delayed it way too long. Didn't mean to step on your toes man. At least our advice is the same! BTW, which rom bootlooped ya? I had that happen on decks 1.2m today.
Click to expand...
Click to collapse
(laughing)....You know it's not a big deal with me. As much as we post in these forums, it's a surety that we will post similar replies around the same time. As for the rom, it was SalvageMod. It hadn't happen prior to today and it haven't happened since. I was eating and replying from inside a Cracker Barrel restaurant when it occurred....lol
posting & replying via the XDA Premium app.
Just wanted to say thanks again to you both. I sincerely appreciate the time and help. Coming from WinMo 6.5, this is my first android device. It becomes quite the little hobby.
I hope to soak in knowledge like a sponge then pass it on.
XDA is a great community.
Thanks again
Skid
Skid71 said:
Just wanted to say thanks again to you both. I sincerely appreciate the time and help. Coming from WinMo 6.5, this is my first android device. It becomes quite the little hobby.
I hope to soak in knowledge like a sponge then pass it on.
XDA is a great community.
Thanks again
Skid
Click to expand...
Click to collapse
You're very welcome, my friend. Before purchasing my Droid Incredible last year, I was a die-hard Blackberry user. (First Blackberry was the 7290 and the last one was the original Bold 9000 with several other models in between). After I rooted the D-Inc, I realized that the capabilities with Android devices were vast. I then wanted a larger screen and was torn between the Droid X and the EVO. Being that I was already familiar with HTC Sense, I chose the EVO and without doubt, I made the right choice. This device is amazing and through trial and error and from being helped by the good people who frequent these forums, I've learned a great deal and am still learning. I love this community and I try to help others and often as I can. The success rate is less than 100% but the effort is more than that....lol. Anyway, take care and enjoy your day...
posting & replying via the XDA Premium app.
Exact same thing happened to me. I kept reading posts saying to get amon recovery. So I did. But when I went to try and restore it wouldn't let me choose a clockwork restore. I just used Rom manager and re flashed clockwork. Then went and did a restore. I like clockwork so I will keep it. Don't know what makes amon so special. Seems like the same options.
Sent from my PC36100 using XDA App
sand1303 said:
Exact same thing happened to me. I kept reading posts saying to get amon recovery. So I did. But when I went to try and restore it wouldn't let me choose a clockwork restore. I just used Rom manager and re flashed clockwork. Then went and did a restore. I like clockwork so I will keep it. Don't know what makes amon so special. Seems like the same options.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Amon Ra is known to be more reliable. It wipes better, and flashes more reliably. Clockwork works flawlessly for some, but not for all. Amon Ra seems to be nearly flawless for all who use it. Also, if you continue using clockwork, you will surely run into some zips that you cannot flash, such as anything that is scripted with edify. Clockwork only supports amend scripting, and there are still PLENTY of zips out there that are edify only. In that case, clockwork will tell you that it can't flash it, and you need to change the scripting to amend. Amon flashes both amend and edify. Also, the newest clockwork doesn't flash radios for some reason, the flash will just not take.
So yea, clockwork works perfectly, and everyone else who suggests amon ra is wrong.
k2buckley said:
So yea, clockwork works perfectly, and everyone else who suggests amon ra is wrong.
Click to expand...
Click to collapse
Wow, I never said it was perfect or anyone was wrong. I simply never ran into problems with clockwork and had a problem with amon. So I didn't know why people would use it.
I greatly appreciate you informing me. I guess if I ever have a problem with clockwork and decide to use amon I will do a backup first thing so restore will be usable.
I also saw on Rom manager that certain things wouldn't work without clockwork. And Rom manager seems to make flashing easier.
Sent from my PC36100 using XDA App
sand1303 said:
Wow, I never said it was perfect or anyone was wrong. I simply never ran into problems with clockwork and had a problem with amon. So I didn't know why people would use it.
I greatly appreciate you informing me. I guess if I ever have a problem with clockwork and decide to use amon I will do a backup first thing so restore will be usable.
I also saw on Rom manager that certain things wouldn't work without clockwork. And Rom manager seems to make flashing easier.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yea, sorry didn't mean to come off harsh. Sorry about that. And yes, Amon Ra doesn't work with rom manager. I won't get started on my opinions on ROM manager, lol
Clockwork jacked up my phone before and left a bad taste in my mouth!
It's all good!
Sent from my PC36100 using XDA App
Hi, its my first time posting, I figured I wanted to sign up to XDA eventually so why not when I feel like I've completely ruined my phone... or at least internal sd card...
Basically I rooted my phone and was flashing the Jellybam rom, and everything was going smoothly until I got to the bootloader and my phone started bootlooping. My first thought was 'Oh but I have a backup'. So I went to my backup in CWM and to my dismay I got an error saying "No files were found."
I could clearly see my files from exploring around on my sd card however they were now in a file called '0' and CWM could not read them from there. Without a working ROM I started to panic. However I had a zip of CM10 still on my internal sd card so I flashed that and (luckily) it worked.
Not really being too competent with flashing new ROMs yet I was quite happy that I had anything. So I used titanium backup to reinstall my old apps and data. However once they were installed I now get an error with 'the process android.process.media has stopped'.
I'm guessing this has do do with the fact that I have all my files still on the '0' folder. All the other folders from the '0' folder were the same except they were all empty, soooooo I decided to delete them. At this point I'm guessing that was a really bad idea because my initial plan of moving all the files from '0' to my pc then back to my phone, I did not think about the fact that I would be moving 14 Gb of data...
So basically now I'm hoping if someone knows a way to revert my phone to 4.1.2 by somehow moving all the files from '0' back onto the internal storage (basically getting rid of this '0') folder. The CM10 ROM is a 4.1.2 ROM so its not like I'm fudging up my phone further (I hope).
If you could be as detailed as possible as to what to do that would be great, because I'm really really new to this....
From what I've read I've heard a couple of suggestions:
1. updating the recovery.img of CWM will work? How exactly do I do this?
2. opening abd shell recovery and moving the files like that (however I deleted all the other files in the internal storage apart from '0' because that was where all the data was stored and everything else was empty...'
help. :crying:
0Capita said:
Hi, its my first time posting, I figured I wanted to sign up to XDA eventually so why not when I feel like I've completely ruined my phone... or at least internal sd card...
Basically I rooted my phone and was flashing the Jellybam rom, and everything was going smoothly until I got to the bootloader and my phone started bootlooping. My first thought was 'Oh but I have a backup'. So I went to my backup in CWM and to my dismay I got an error saying "No files were found."
I could clearly see my files from exploring around on my sd card however they were now in a file called '0' and CWM could not read them from there. Without a working ROM I started to panic. However I had a zip of CM10 still on my internal sd card so I flashed that and (luckily) it worked.
Not really being too competent with flashing new ROMs yet I was quite happy that I had anything. So I used titanium backup to reinstall my old apps and data. However once they were installed I now get an error with 'the process android.process.media has stopped'.
I'm guessing this has do do with the fact that I have all my files still on the '0' folder. All the other folders from the '0' folder were the same except they were all empty, soooooo I decided to delete them. At this point I'm guessing that was a really bad idea because my initial plan of moving all the files from '0' to my pc then back to my phone, I did not think about the fact that I would be moving 14 Gb of data...
So basically now I'm hoping if someone knows a way to revert my phone to 4.1.2 by somehow moving all the files from '0' back onto the internal storage (basically getting rid of this '0') folder. The CM10 ROM is a 4.1.2 ROM so its not like I'm fudging up my phone further (I hope).
If you could be as detailed as possible as to what to do that would be great, because I'm really really new to this....
From what I've read I've heard a couple of suggestions:
1. updating the recovery.img of CWM will work? How exactly do I do this?
2. opening abd shell recovery and moving the files like that (however I deleted all the other files in the internal storage apart from '0' because that was where all the data was stored and everything else was empty...'
help. :crying:
Click to expand...
Click to collapse
1- Your solution
2- Was quite the bad idea to delete it all so this solution won't work now.
clockwordmod.com is where you'll find the latest recovery.
BWolf56 said:
1- Your solution
2- Was quite the bad idea to delete it all so this solution won't work now.
clockwordmod.com is where you'll find the latest recovery.
Click to expand...
Click to collapse
So how exactly do I do that? I just download the the latest clockwork mod and flash it? Why can't it be updated via an automatic updater? And what will it do to the file or will it change clockwork mod so that it will scan the entire sd card?
Also if I just remade folders identical to the ones I deleted, will that still work?
I'm just trying to get my phone to be as functional as it was before this all started.
Thanks for replying btw!
0Capita said:
So how exactly do I do that? I just download the the latest clockwork mod and flash it? Why can't it be updated via an automatic updater? And what will it do to the file or will it change clockwork mod so that it will scan the entire sd card?
Also if I just remade folders identical to the ones I deleted, will that still work?
I'm just trying to get my phone to be as functional as it was before this all started.
Thanks for replying btw!
Click to expand...
Click to collapse
That's a lot of question for the simple fix I gave you.. I haven't used cwm in a while so Idk what changed in the update but if people said it fixed it, then it did..
0, 1, 2, etc.. Is something that came with JB, it's for the different users. Not much can be done about it.
About how you should do that: Go on their website, FOLLOW their instructions to a T, Enjoy.
As for why it can be updated via an automatic updater.. Well I'm not the person you should ask.
B said:
Wolf56;371questions it's a lot of question for the simple fix I gave you.. I haven't used cwm in a while so Idk what changed in the update but if people said it fixed it, then it did..
0, 1, 2, etc.. Is something that came with JB, it's for the different users. Not much can be done about it.
About how you should do that: Go on their website, FOLLOW their instructions to a T, Enjoy.
As for why it can be updated via an automatic updater.. Well I'm not the person you should ask.
Click to expand...
Click to collapse
Sorry for all the questions, I'm just worried that I messed up my phone. Would you know if I were able to be able to access my old clockwork mod backups and used one of them, would it put my 0 files back into the internal storage like they used to? Or would it only revert the settings and I would still be SOL.
0Capita said:
Sorry for all the questions, I'm just worried that I messed up my phone. Would you know if I were able to be able to access my old clockwork mod backups and used one of them, would it put my 0 files back into the internal storage like they used to? Or would it only revert the settings and I would still be SOL.
Click to expand...
Click to collapse
Yes, that's the whole point of the cwm update. Now to flash it!
Or, go digg through the cm nightly thread. They had a flash able zip that would restore your internal sd after downgrading Android versions.
BWolf56 said:
Yes, that's the whole point of the cwm update. Now to flash it!
Click to expand...
Click to collapse
Well here's my latest problem... I tried to update CWM with an .img however when I tried to run it in the terminal it said there was not enough space... I don't know what to do... there is definitely a couple gigs free so I don't know what is wrong...
mrhaley30705 said:
Or, go digg through the cm nightly thread. They had a flash able zip that would restore your internal sd after downgrading Android versions.
Click to expand...
Click to collapse
the cm nightly thread? So theres a zip that would make 4.2 go back to 4.1?
Okay update:
I managed to flash update the new version of CWM... still can't use backup... I get a /system fail
It doesn't downgrade you're ROM. It fixes the 0 folder issue
mrhaley30705 said:
It doesn't downgrade you're ROM. It fixes the 0 folder issue
Click to expand...
Click to collapse
Ugh Okay I've given up... I dont know what else to try. Now that I've updated my CWM I cant flash the old CM10 because it reads it as a 4.1 and uncompatable... FML.
Can anyone point me to where I can find the Odin stock factory? I guess I'll just start from scratch...
http://db.tt/rWFbAFiF
Link to restore files from /0 directory
Credits go to madmack
Sent from my SGH-I747 using xda app-developers app
Helloworld294 said:
http://db.tt/rWFbAFiF
Link to restore files from /0 directory
Credits go to madmack
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
OOOMMMMMGggg ahhhhhh, that would have been so helpful but I've already started to factory reset it. Thanks though!
ahhhhhhhhh
Forget cwm it sucks use twrp and be done with all the problems
Sent from the scary door....
So I was got my s3 awhile back and rooted it and ran Clean bean without any problems, well after those annoying system update messages started to get to me I decided I wanted to try and new rom and update my phone a bit as I would be leaving the country and wanted my phone updated. So I decided to flash slimbeam , It went off without a hitch. Only problem was I could not figure out how to get Titanium backup to restore all my contacts and app data. I saved all the backup files on my computer and even after putting them in the Titanium backup directory it would not let me do it. Anyway.....I decided to try and use the titanium backup program that lets you extract the data from a nandroid backup and flash it in recovery. I forgot to put it on my internal card when doing so and when I did my wipe I deleted it (epic facepalm) so I have to reflash cleanbean go back into my phone and make the .zip file to flash...
So I got tired and went to bed before flashing anything else, when I wake up. My phone is stuck on the samsung boot image screen. I try starting only to get the same thing. So I boot to CWS recovery and try to restore one of my nandroid backups. I accidentally hit backup to external sd and it started to run a backup, thenn my car charger came unplugged and the phone died....thinking it would just make that specific nandroid corrupt I thought nothing of it. So I reboot to CWS recovery again and actually try to do a restore with my oldest nandroid, But I get the error "Error updating /system" and error updating "/data".....I tried multiple backups that I have, none of them work and all produce that message.. 'm fairly new to this, What Am I doing wrong? I really love this site and all you guys do and I will be forever greatful of any help you guys can give me. I leave the country for Mexico in 2 days and I cant afford to pay the $150 to get my phone warrantied from sprint!
Thanks in advance, and sorry for spelling/grammar mistakes (at work, not suppose to be on here)
-Lucid.
Lucid420 said:
So I was got my s3 awhile back and rooted it and ran Clean bean without any problems, well after those annoying system update messages started to get to me I decided I wanted to try and new rom and update my phone a bit as I would be leaving the country and wanted my phone updated. So I decided to flash slimbeam , It went off without a hitch. Only problem was I could not figure out how to get Titanium backup to restore all my contacts and app data. I saved all the backup files on my computer and even after putting them in the Titanium backup directory it would not let me do it. Anyway.....I decided to try and use the titanium backup program that lets you extract the data from a nandroid backup and flash it in recovery. I forgot to put it on my internal card when doing so and when I did my wipe I deleted it (epic facepalm) so I have to reflash cleanbean go back into my phone and make the .zip file to flash...
So I got tired and went to bed before flashing anything else, when I wake up. My phone is stuck on the samsung boot image screen. I try starting only to get the same thing. So I boot to CWS recovery and try to restore one of my nandroid backups. I accidentally hit backup to external sd and it started to run a backup, thenn my car charger came unplugged and the phone died....thinking it would just make that specific nandroid corrupt I thought nothing of it. So I reboot to CWS recovery again and actually try to do a restore with my oldest nandroid, But I get the error "Error updating /system" and error updating "/data".....I tried multiple backups that I have, none of them work and all produce that message.. 'm fairly new to this, What Am I doing wrong? I really love this site and all you guys do and I will be forever greatful of any help you guys can give me. I leave the country for Mexico in 2 days and I cant afford to pay the $150 to get my phone warrantied from sprint!
Thanks in advance, and sorry for spelling/grammar mistakes (at work, not suppose to be on here)
-Lucid.
Click to expand...
Click to collapse
Ok Lucid, stay calm.
First off, never do any work in Recovery without a fully charged phone. You're just asking for trouble if you're relying on the cable being plugged in.
I've never had good luck with trying to restore data in TiBu from a nandroid backup.
I'm not going to go into how to make your backups work. I'm honestly more concerned with just getting your phone back into working order. This thread has the most current Stock Rom in TAR form. Odin instructions can be found in this post within that thread.
After you're back to 100% stock, unrooted, you can follow the rooting guide to gain root back.
THANKS
topherk said:
Ok Lucid, stay calm.
First off, never do any work in Recovery without a fully charged phone. You're just asking for trouble if you're relying on the cable being plugged in.
I've never had good luck with trying to restore data in TiBu from a nandroid backup.
I'm not going to go into how to make your backups work. I'm honestly more concerned with just getting your phone back into working order. This thread has the most current Stock Rom in TAR form. Odin instructions can be found in this post within that thread.
After you're back to 100% stock, unrooted, you can follow the rooting guide to gain root back.
Click to expand...
Click to collapse
Thanks man! Most appreciated! You just relieved a large amount of stress! I'll pay it forward!
topherk said:
Ok Lucid, stay calm.
First off, never do any work in Recovery without a fully charged phone. You're just asking for trouble if you're relying on the cable being plugged in.
I've never had good luck with trying to restore data in TiBu from a nandroid backup.
I'm not going to go into how to make your backups work. I'm honestly more concerned with just getting your phone back into working order. This thread has the most current Stock Rom in TAR form. Odin instructions can be found in this post within that thread.
After you're back to 100% stock, unrooted, you can follow the rooting guide to gain root back.
Click to expand...
Click to collapse
Do what he said, I can vouch that restoring data through tibu from a nandroid has never worked for me either. If you backed up your contacts with Google you can just export them into a file (either .csv or .xml i forget) and then import that into your contacts
Sent from my SPH-L710
sevenpioverthree said:
Do what he said, I can vouch that restoring data through tibu from a nandroid has never worked for me either. If you backed up your contacts with Google you can just export them into a file (either .csv or .xml i forget) and then import that into your contacts
Sent from my SPH-L710
Click to expand...
Click to collapse
And after looking through the sextape forums thread a bit more, you don't actually have to reroot, just use the following TAR file:
"Restore" Versions - Wipes your user data
SPH-L710_MD4_1130792_Stock_Restore [EXE|TAR.MD5.GZ]
SPH-L710_MD4_1130792_Rooted_Restore [EXE|TAR.MD5.GZ]
Click to expand...
Click to collapse
They also have really good instructions for the Odin work on there.
Hope you get it working!
GOT IT! Thanks for the help man, worked like a charm. Even learned a thing or two .....So can you tell me how I get my stuff back using titanium backup? I got the backup files on my computer and I'm flashing a rom as I type this.
Lucid420 said:
GOT IT! Thanks for the help man, worked like a charm. Even learned a thing or two .....So can you tell me how I get my stuff back using titanium backup? I got the backup files on my computer and I'm flashing a rom as I type this.
Click to expand...
Click to collapse
Here is a link to a post where I talked about Tianium Backup and what not to restore. It should be fairly informative.
In TiBu for SMS and call logs hit menu from the main screen and backup data as XML, select save locally when it's done. Move the xml files to external SD if you're gonna flash a 4.2.2 rom, flash new rom move the xmls back to internal, go to tibu, same menu, restore from xml and select which one you want to restore. It'll open a quasi file explorer, locate the corresponding xml for the option you chose(call log, SMS, wifi, bookmarks) and select it. It will restore the data via XML and you'll have all your call logs, sms, bookmarks and wifi accesspoints back like you never left your previous rom.
°•○●¤◇★S☆A: Son's of Android★◇¤●○•°
I like to break stuff!