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
Related
Seriously, lol..
I am coming from a CE device and going to android is a little bit of a learning curve.. Not that its harder but its different obviously.
What I am asking basically.. All these guides that are written out talk about things as if we already know them..
Don't get me wrong, they are written great, but I don't know certain lingo.. For example I am really wanting to install a ROM.. Just got my evo a few weeks ago, Rooted it and thats it.. Looking into Roms and reading the instructions, its like "WHATTT??"
Sure they explain how to do it, but they don't explain in detail certain steps.. It happens as many people assume they should know..
For example (and they are all like this)
I am looking at the FRESH'S rom.. Seems like a good Rom from what I read, but looking at the instructions for just the Radio
http://geekfor.me/faq/flash-radio/
2) Boot in to RA and pick “Flash zip from sdcard”
RA?? What is RA??
Before these instructions it says "Don’t flash this unless you have a CDMA Evo 4g"
I am sure most people know what CDMA is, but I don't.. Have no Idea, lol
I am basically hoping there is a guide "FOR IDIOTS"
Thanks all
ra is a recovery, you can have either clockworkmod or amon_ra, they both do the same so its personal choice.
cdma is type of network, ie sprint, verizon, cricket. gsm is the other, ie att etc.
now that your phone is rooted, make a backup before anything else. you boot into recovery by turning the phone off, then give it 5 secs then hold Volume down button and then pressing the power button, when it responds you can let go. wait for img file checks to finish then press volume down once to highlight recovery and press power to select. you will now be in recovery. go into nandroid and make a backup.
you can use rom manager from the market to flash many roms however the fresh and damagecontrol links are currently erroring.
before flashing any roms be sure to wipe data and cache either in recovery if done manually or by checking the box in rom manager
Anyone wanna help a fellow brotha out and make a quick 10 bucks.. Lunch money at least.. Just to call me and maybe walk me through some of it, or atleast verbally explain some things
Paypal will be done right away..
Id really appreciate it..
install rom manager, you can make a backup through it. its an automated app, tell it what to do and it will boot into recovery and do it then reboot again
Have Rom manager.. I just did a "boot into Recovery" I then did a nandroid backup.. But why? I did this with Titanum.. How many back ups do I need? This is where I get confused..
I did a couple things with Titanuim and it took like 600 megs of space, now I am doing what seems like the same thing with nandiod back up?
Now, do I just unzip both the fresh rom and the radio, put it in a folder on my Sdisk, open rom manager, choose manually install or whatever it says, and point it to the unzipped Fresh Rom??
If yes, then how do I do the radio?
THANKS
Also, I know my apps will be gone by doing a root, and I could just download then again,,, (correct??)
What about my contacts and pictures and videos??
THanks
you don't unzip the rom, and you shouldnt need the new radio, put the fresh zip on your sd card and in rom manage tell it to flash it and check wipe data and cache.
you can always redownload your apps from the market, purchased ones stay purchased
no loss of pics or vids. sd card isnt wiped
you can check your current baseband version and if its the same then your already set
fastfed said:
Have Rom manager.. I just did a "boot into Recovery" I then did a nandroid backup.. But why? I did this with Titanum.. How many back ups do I need? This is where I get confused..
I did a couple things with Titanuim and it took like 600 megs of space, now I am doing what seems like the same thing with nandiod back up?
Click to expand...
Click to collapse
Titanium will backup your apps and app data too if you want. When flashing a new ROM you can download titanium from the market and then restore all of your apps.
Doing a nandroid backup in essence takes a snapshot of what your phone looks like at that point in time (apps, user preferences, theme, etc) and saves it. At any point later on, after trying different ROMs, changing settings, etc you can revert to that nandroid backup and restore it. Doing so will bring your phone back to that exact state when you performed the nandroid as if you never did any of the changes afterward.
And a lot of your questions can probably be answered in the post linked in my sig.
m4rk0358 said:
Titanium will backup your apps and app data too if you want. When flashing a new ROM you can download titanium from the market and then restore all of your apps.
Doing a nandroid backup in essence takes a snapshot of what your phone looks like at that point in time (apps, user preferences, theme, etc) and saves it. At any point later on, after trying different ROMs, changing settings, etc you can revert to that nandroid backup and restore it. Doing so will bring your phone back to that exact state when you performed the nandroid as if you never did any of the changes afterward.
Click to expand...
Click to collapse
Thank you for explaining that.. MAkes sense now..
Also.. You say I don't need a new radio, but the main Fresh Rom post, says I "SHOULD " get the new radio, (which he posted) and install that before or after..
fastfed said:
Also.. You say I don't need a new radio,
Click to expand...
Click to collapse
I did?
you would install the radio after, manually in recovery. leave it zipped too, put it in an easy place to get, like the root of the card.
m4rk0358 said:
I did?
Click to expand...
Click to collapse
I said it mark, I was assuming OP had all current updates which include the radio
m4rk0358 said:
And a lot of your questions can probably be answered in the post linked in my sig.
Click to expand...
Click to collapse
Did you write that? its really the best I have come across.. Thanks!! I am on my way.. Its in the middle of the rom install..
Wish me luck
I still need to find out if I should install the "Recommended" Radio or not..
THANKS GUYS!!
NewZJ said:
I said it mark, I was assuming OP had all current updates which include the radio
Click to expand...
Click to collapse
Well.. I have all the current (Sprint/Evo) updates.. But nothing from aftermarket..
Phone just rebooted.. Here we go
Oh one more thing..
If I feel to revert back to stock and use the "nandroid" back up, will it back up the radio I had then too??
Looks Like I am done... That was nice and easy (thanks to Rom manager)
I am now going to install the radio that was recommended.. Can I use Rom manager for that too??
in TitaniumBackup (tiB) ... go to Batch .. Backup all user apps
(i would suggest purchasing tiB. the paid version is MUCH faster and you won't have to click on each app to restore it. i also like that you can create a flashable zip file for your backup. ie: an update.zip file. it's under the the "More" section.)
i would suggest using Amon_RA as your loader. here is the thread to review it http://forum.xda-developers.com/showthread.php?t=705026&highlight=amon_ra
do a nandroid. (don't forget to copy a nandroid onto your computer once in a while...having ur nandroid exist only on ur sdcard sux if you lose ur phone or ur card melts)
- between ROMs..do a full wipe. (ie: From Fresh to BakedSnack or CM6) just do it. it will save you stress and irritation. it will also help you streamline your recovery process and develop overall familiarity with the system.
- when upgrading a ROM (ie: Fresh 3.1 to Fresh 3.1.1 or 3.2) usually you can just wipe your Cache and DalvikCache (always read the FirstPost of your ROM ... some times you need to full wipe)
- Flashing a kernel can have significant impacts on your device. always flash Cache and DalvickCache. always have a good nandriod ready. always be plugged in or have >50% battery. always in this case means...not technically "Required", but don't cry to me if something goes awry.
the tiB will restore your applications but not settings. some apps like launcherPRO OR adw.Launcher or SMSbacup+ etc will allow you to export your settings. then you simply import your settings when needed. usually works quite well.
the nandroid is more like a 'Ghost Image' we use on computers. it will allow you to recover your devices almost 100% to the point it was when the image was taken. similar to tiB but diferent. tiB backups up the apps. nandroid backs up the whole system.
check this thread for Radios... http://forum.xda-developers.com/showthread.php?t=715485
yes, you will flash the radio zips in the recovery console as well
this is a combo zip and should work fine http://www.mediafire.com/file/ry3k8....00.09.01_WiMAX_26023_R01_PRI_NV_1.77_003.zip
OK.. Now that I have FRESH ROM.. I would like to get a theme.. Right? Isn't this what most people do after a Root,Rom,Radio, Theme??
Thanks
Umm this is not good.. where are all my contacts? I was under the impression they would stay.. How do I get them back? I did a nandroid back up and a Titanium too.. Where did they go? Or should I just sync to my computer again?
Thanks
if your contacts are synced to gmail they will appear shortly after sync, if you have them on your computer you can sync them that way
once the radio is current you don't have to update it again, it won't be downgraded with flashing roms
Welcome,
I've compiled ClockWorkMod 3.0.1.4 and I made some changes to it, copying BlaY0's work for the HTC Legend.
Changes:
Removed menu entries for updating via /sdcard/update.zip
[*]Stripped some "No" line entries from confirmation menus (only 1 left)
[*]Removed some insane size values from partitioning list
[*]Recovery is closed using pkill instead of ps and grep
Installation
Code:
Copy the desired update.zip to your sdcard and apply it from ClockWorkMod
Extras:
Install noconfirm to remove the "no" lines. Works on all clockworkmod-based recoveries.
Thanks to BlaY0, Cyanogen and Koush
Thanks. Thanks a ton! You actually addressed what annoyed me most with this recovery. I have to admit, I do miss RA on the Vision...
But no complaining here, thanks for your work!
Edit: Ugh, I don't get it with the .no_confirm file. Put it where...?
Going to try this, sounds good =))
Sent from my HTC Vision using Tapatalk
Aha i just moved this in clockwork recoveries files then i just renamed the rec.img with the recovery of the g2 then flash it...
Sent from my HTC Vision using Tapatalk
So this still has the fix for power off while charging? And just the menu for sdcard update has been removed that can be noticed other than that, the other two updates to it is file size or so??
Sent from my HTC Vision using Tapatalk
noodles2224 said:
So this still has the fix for power off while charging? And just the menu for sdcard update has been removed that can be noticed other than that, the other two updates to it is file size or so??
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
It still powers on when charging
And he did remove the other "NO" from the list, so now it's a lot easier
Hey hey! I like what you've done with the source file. I was using your recovery while in the process of making a backup and thought it was pretty neat because I couldn't for the life of me figure out where and what to edit in source since nothing is commented out by anyone. I can read the code but have a difficult time tracing it through. I'm still newbie with the C++
But anyways, while backing up, I was reminded of how annoying it is to backup the system, data, cache, sd-ext, boot, and etc folders into img files for every backup of CM7 when the only thing that really needs to be backed up is the data folder to data.img which contains all the userdata, settings and applications downloaded from the market. The only exception would be if I had changed keymap files, changed stuff inside /system/app/ folder, or any other folder/files other than data since the previous backup of the same rom.
So, if I was to make ONE backup of CM7 Tuesday morning, and wanted to make a backup of the very same rom later on in the day (containing more recent apps, emails, settings, etc. ) I would have to delete the old backup already saved and start the backup process over again from the beginning, or I would have to keep making duplicates of the same backup that differs only by the data.img file, wasting precious space on a baby **** sized microsd. IMO it completely ruins the purpose of the automatic backup feature of Rom Manager since I have to remind myself to delete the previous backup everyday. However, I do think it'll be useful if clockworkmod can be modified.
SO, I was wondering, where should I be looking in the source to add an option such as "backup data only",
that when selected,
1.) Looks for an extra line in the md5sum file for every folder in /sdcard/clockworkmod/backup/ that specifies the android version (cm7, cm6, date, w/e)
2.) Compares extra line with what it's about to back up (via contents of /system/build.prop ) and
3.) if they match up
calls only the function that backs up the data folder excluding calls for the backup of system, cache, boot, etc.
Sorry, if its confusing how I've explained it. Its quite late here in soFla, and I didn't get no sleep 8(
But I'm sure you get what I mean considering that you know some code. That's a very rough pseudo-code I guess.
Another method that probably is a lot easier, if possible, would be to figure out what command/message Rom-Manager leaves behind for clockworkmod before rebooting to clockworkmod. If it is a small script like I hope it is, backing up only data.img would be a heck of a lot easier since I'm pretty sure the source has an individual definition call for backup for each partition.
so how do i fix this powering on issue.. its starting to piss me off -.- lol,. least how to fix it on stock recovery.
CaliBoyPhillip said:
so how do i fix this powering on issue.. its starting to piss me off -.- lol,. least how to fix it on stock recovery.
Click to expand...
Click to collapse
I think this issue is caused by the hardware on the desire z and thus is unfixable. If you press power off from the menu will it just power on again? Because then the entry should be renamed to reboot recovery.
thrice43 said:
Hey hey! I like what you've done with the source file. I was using your recovery while in the process of making a backup and thought it was pretty neat because I couldn't for the life of me figure out where and what to edit in source since nothing is commented out by anyone. I can read the code but have a difficult time tracing it through. I'm still newbie with the C++
But anyways, while backing up, I was reminded of how annoying it is to backup the system, data, cache, sd-ext, boot, and etc folders into img files for every backup of CM7 when the only thing that really needs to be backed up is the data folder to data.img which contains all the userdata, settings and applications downloaded from the market. The only exception would be if I had changed keymap files, changed stuff inside /system/app/ folder, or any other folder/files other than data since the previous backup of the same rom.
So, if I was to make ONE backup of CM7 Tuesday morning, and wanted to make a backup of the very same rom later on in the day (containing more recent apps, emails, settings, etc. ) I would have to delete the old backup already saved and start the backup process over again from the beginning, or I would have to keep making duplicates of the same backup that differs only by the data.img file, wasting precious space on a baby **** sized microsd. IMO it completely ruins the purpose of the automatic backup feature of Rom Manager since I have to remind myself to delete the previous backup everyday. However, I do think it'll be useful if clockworkmod can be modified.
SO, I was wondering, where should I be looking in the source to add an option such as "backup data only",
that when selected,
1.) Looks for an extra line in the md5sum file for every folder in /sdcard/clockworkmod/backup/ that specifies the android version (cm7, cm6, date, w/e)
2.) Compares extra line with what it's about to back up (via contents of /system/build.prop ) and
3.) if they match up
calls only the function that backs up the data folder excluding calls for the backup of system, cache, boot, etc.
Sorry, if its confusing how I've explained it. Its quite late here in soFla, and I didn't get no sleep 8(
But I'm sure you get what I mean considering that you know some code. That's a very rough pseudo-code I guess.
Another method that probably is a lot easier, if possible, would be to figure out what command/message Rom-Manager leaves behind for clockworkmod before rebooting to clockworkmod. If it is a small script like I hope it is, backing up only data.img would be a heck of a lot easier since I'm pretty sure the source has an individual definition call for backup for each partition.
Click to expand...
Click to collapse
I understand the issue. I do have an idea for you which I will work on later today. It's an update.zip with a script in it which will yaffs up the data partition and put the data.img into /sdcard/clockworkmod/backup/*foldername*/
Next is should take the md5sum and write it to md5sums.txt
Like this you can restore your backup. I can cook you a custom recovery which has added update from /sdcard/update.zip baked in, but changed to /sdcard/clockworkmod/backupdata.zip
I know this isn't the easiest way to do it, but it is the easiest to code for me, so I'll use it untill I expand my knowledge
schaggo said:
Thanks. Thanks a ton! You actually addressed what annoyed me most with this recovery. I have to admit, I do miss RA on the Vision...
But no complaining here, thanks for your work!
Edit: Ugh, I don't get it with the .no_confirm file. Put it where...?
Click to expand...
Click to collapse
Ah how stupid of me, it should go in sdcard/clockworkmod/
I'll confirm and update the first post, thanks for pointing it out
Mikevhl said:
I think this issue is caused by the hardware on the desire z and thus is unfixable. If you press power off from the menu will it just power on again? Because then the entry should be renamed to reboot recovery.
Click to expand...
Click to collapse
Yeah, it happens regardless If i plug in my charge and pull of battery and back in or pull out battery and put back in and plug charger haha... same with power menu ugh... =( I'm on a T-Mobile USA G2 if that helps but its pretty much a DZ
CaliBoyPhillip said:
Yeah, it happens regardless If i plug in my charge and pull of battery and back in or pull out battery and put back in and plug charger haha... same with power menu ugh... =( I'm on a T-Mobile USA G2 if that helps but its pretty much a DZ
Click to expand...
Click to collapse
Nah I'm on a Desire Z so it's the same. Since this does not happen on other devices, the problem isn't caused by clockworkmod. The bootloader is just coded to boot into recovery when AC plugs in. I don't know if this happen the stock recovery as well. It could be caused by gfree, but also it could just be that the stock recovery forces the system to be shut down. Whatever it is, we won't be able to fix it..
Mikevhl said:
I understand the issue. I do have an idea for you which I will work on later today. It's an update.zip with a script in it which will yaffs up the data partition and put the data.img into /sdcard/clockworkmod/backup/*foldername*/
Next is should take the md5sum and write it to md5sums.txt
Like this you can restore your backup. I can cook you a custom recovery which has added update from /sdcard/update.zip baked in, but changed to /sdcard/clockworkmod/backupdata.zip
I know this isn't the easiest way to do it, but it is the easiest to code for me, so I'll use it untill I expand my knowledge
Click to expand...
Click to collapse
Damn... Why are you so OG? I would appreciate that so much. How many source files were actually modified from the original clockworkmod source? If its not many, would you mind commenting out some important bits of code so I can pick up from somewhere when looking through the code and have a better understanding of the basic/general algorithm used by the original dev? Its cool if you don't though lol. I still appreciate what you've already put together.
thrice43 said:
Damn... Why are you so OG? I would appreciate that so much. How many source files were actually modified from the original clockworkmod source? If its not many, would you mind commenting out some important bits of code so I can pick up from somewhere when looking through the code and have a better understanding of the basic/general algorithm used by the original dev? Its cool if you don't though lol. I still appreciate what you've already put together.
Click to expand...
Click to collapse
Do you mean the things that I've removed and added? If you take a look at the sources you will aee that there is a line on which the modification takes place, next a + or - which indicates if the line was added or removed. Is that what you mean?
Mikevhl said:
Do you mean the things that I've removed and added? If you take a look at the sources you will aee that there is a line on which the modification takes place, next a + or - which indicates if the line was added or removed. Is that what you mean?
Click to expand...
Click to collapse
Whoops yes I understand the layout now. sorry. I was curious as to where, and which file to begin looking to unstand customizing cwm
Mikevhl said:
Nah I'm on a Desire Z so it's the same. Since this does not happen on other devices, the problem isn't caused by clockworkmod. The bootloader is just coded to boot into recovery when AC plugs in. I don't know if this happen the stock recovery as well. It could be caused by gfree, but also it could just be that the stock recovery forces the system to be shut down. Whatever it is, we won't be able to fix it..
Click to expand...
Click to collapse
actually, it DOES happen on other devices, and it IS a clockwork issue that, to my knowledge, Koush is aware of and is looking to fix. Before I came to the g2, I had a red mytouch 4g which, when rooted and CWM was installed, would boot into recovery from a powered down state when it connected to the charger. The explanation I heard back then was that the stock recovery for the phone would boot up upon connecting to a charger while off, but that it would somehow keep the screen off. however, when the recovery is replaced with CWM, it still exhibits this behavior, but it does not keep the screen off.
Just an fyi, though, in the mexDroid forum OP, there is a modded version of CWM which, when installed, will keep the phone off while charging. I have personally verified that it works (now if only someone would find a way to have android start up and shut down at preset times, like to have an alarm go off.. that would be awesome).
Would it be safe to assume that this'll also work on my galaxy tab?
Sent from my GT-P1000 using XDA Premium App
JasonTCelum said:
Would it be safe to assume that this'll also work on my galaxy tab?
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
no, that's a bit of a stretch, as each recovery is made for the device that uses it, not device-agnostic. However, if you would like to try it out and dont mind taking the risk, you never know, you could get lucky.
mt4g?
Currently loving this on my G2 is there any chance of it becoming compatible for the mytouch 4G?
Ill be the Guinea!
Alright, as some of you know, I really, really, REALLY, messed up on my last root attempt.
Apparently I didn't backup what I was supposed to. That was my own stupid a55 mistake and I have admitted to it.
I DO plan to attempt a root again so that I can get this theme on my phone: http://forum.xda-developers.com/showthread.php?t=1042268
There are things that I need to know before I attempt this (and yes I know there are forums already on this but I need to be 110% sure)
1) How do I back up EVERYTHING on my phone and put it on my computer or SD card or somewhere that I can go to incase I mess up again?
2) What is the EASIEST program/method to root this Samsung Epic 4g?
3) (I'm not too sure what I'm talking about here ((remember, I'm a total noob)))
I tried CWM 3.0.0.5 before... is this a ROM that I attempted to go to?
3ii) If I should'nt be using CWM, what should I use?
4) Is Froyo and CWM the same time of thing? or two different things completely?
and finally:
5) Give me all of your recommendations on this please! I DON'T WANNA MESS UP AGAIN!
And please none of this "You messed up before, dont try it again!" crap, I know I messed up, and I know this is stupid, but the fact of the matter is, I'm trying it again to get this theme on my device. So PLEASE help me out!
Thanks everyone!
cheech92007 said:
Alright, as some of you know, I really, really, REALLY, messed up on my last root attempt.
Apparently I didn't backup what I was supposed to. That was my own stupid a55 mistake and I have admitted to it.
I DO plan to attempt a root again so that I can get this theme on my phone: http://forum.xda-developers.com/showthread.php?t=1042268
There are things that I need to know before I attempt this (and yes I know there are forums already on this but I need to be 110% sure)
1) How do I back up EVERYTHING on my phone and put it on my computer or SD card or somewhere that I can go to incase I mess up again?
2) What is the EASIEST program/method to root this Samsung Epic 4g?
3) (I'm not too sure what I'm talking about here ((remember, I'm a total noob)))
I tried CWM 3.0.0.5 before... is this a ROM that I attempted to go to?
3ii) If I should'nt be using CWM, what should I use?
4) Is Froyo and CWM the same time of thing? or two different things completely?
and finally:
5) Give me all of your recommendations on this please! I DON'T WANNA MESS UP AGAIN!
And please none of this "You messed up before, dont try it again!" crap, I know I messed up, and I know this is stupid, but the fact of the matter is, I'm trying it again to get this theme on my device. So PLEASE help me out!
Thanks everyone!
Click to expand...
Click to collapse
Ok, first things first. Not to be rude, but you are at the first step of enjoying Epic goodness; rooting your phone. It should be obvious that this step is covered ALL over XDA and a simple google search would have lead you to the following page:
CWM 3.0.0.5
There are already wayyyy too many threads asking questions that were answered long before they were ever even asked in the first place.
Okay, now that that's out of the way .
1. If you're absolutely freaked about losing anything, MyBackup and MyBackup Pro will back up all your apps. Then simply plug your phone into your computer and copy the entire contents of your sd card to your harddrive. Mybackup Root can be used once your rooted and is free.
2. Use the link i posted.
3. CWM is not a Rom. It replaces the default recovery subsystem with one you can use to flash Roms. You enter it from the off state by pressing Volume Down+Camera+Power. Do not use CWM 3.0.2.4.
4. Froyo is simply the version of android. The Samsung Epic is on Froyo, or 2.2. Roms come in various flavors like Eclair(2.1), Froyo(2.2), and hopefully soon for the Epic, Gingerbread(2.3).
5. Search around the Epic Android Development for a Rom that makes you excited. A good suggestion for you would be Midnight 5.2. All you have to do is download the Rom .zip file to your SD, boot into CWM 3, Install from SD, and point it to the .zip. Read the forums for how to safely install their Roms like clearing data and making/restoring backups.
Remember, everything you've asked has been asked and answered many times, so please search next time to avoid making unnecessary threads and to gain your answer faster!
RandomKing said:
Ok, first things first. Not to be rude, but you are at the first step of enjoying Epic goodness; rooting your phone. It should be obvious that this step is covered ALL over XDA and a simple google search would have lead you to the following page:
CWM 3.0.0.5
There are already wayyyy too many threads asking questions that were answered long before they were ever even asked in the first place.
Okay, now that that's out of the way .
1. If you're absolutely freaked about losing anything, MyBackup and MyBackup Pro will back up all your apps. Then simply plug your phone into your computer and copy the entire contents of your sd card to your harddrive. Mybackup Root can be used once your rooted and is free.
2. Use the link i posted.
3. CWM is not a Rom. It replaces the default recovery subsystem with one you can use to flash Roms. You enter it from the off state by pressing Volume Down+Camera+Power. Do not use CWM 3.0.2.4.
4. Froyo is simply the version of android. The Samsung Epic is on Froyo, or 2.2. Roms come in various flavors like Eclair(2.1), Froyo(2.2), and hopefully soon for the Epic, Gingerbread(2.3).
5. Search around the Epic Android Development for a Rom that makes you excited. A good suggestion for you would be Midnight 5.2. All you have to do is download the Rom .zip file to your SD, boot into CWM 3, Install from SD, and point it to the .zip. Read the forums for how to safely install their Roms like clearing data and making/restoring backups.
Remember, everything you've asked has been asked and answered many times, so please search next time to avoid making unnecessary threads and to gain your answer faster!
Click to expand...
Click to collapse
Okay the main thing that I am confused about is number 5. Why do I want these ROM's exactly? Pretty much all I want is that Red Angry Alien theme.
cheech92007 said:
Okay the main thing that I am confused about is number 5. Why do I want these ROM's exactly? Pretty much all I want is that Red Angry Alien theme.
Click to expand...
Click to collapse
After reviewing your other posts, I am now aware that you have asked a lot of this and already been answered but are clearly not interested in reading the information presented to you. This should have been continued in the last thread that you started, but what's done is done. Your key problem is rooting with CWM which converts the file system to EXT4. You will have to flash a new rom or kernel immediately following or the phone can't boot. This means that you must have a new rom or kernel .zip file on your sd card PRIOR TO ROOTING. I haven't messed around too much with a rooted stock rom, but at the least you need a new kernel, search for and try VisionKernel if thats all you want.
Please refrain from starting any more threads, you've already been given more information than you need by myself and others. Search around XDA, it can be fun!
RandomKing said:
You will have to flash a new rom or kernel immediately following or the phone can't boot. This means that you must have a new rom or kernel .zip file on your sd card PRIOR TO ROOTING. I haven't messed around too much with a rooted stock rom, but at the least you need a new kernel, search for and try VisionKernel if thats all you want.
Click to expand...
Click to collapse
Alright, I just downloaded the EB13-DUALFS-KERNEL.zip to my desktop...is THIS what you were talking about that I need on my SD card first? I looked inside it and it has a KERNEL file in it... So I put this on my SD card, then ROOT, then UNZIP the EB13 on my devices when Im in CWM Reboot?
cheech92007 said:
Alright, I just downloaded the EB13-DUALFS-KERNEL.zip to my desktop...is THIS what you were talking about that I need on my SD card first? I looked inside it and it has a KERNEL file in it... So I put this on my SD card, then ROOT, then UNZIP the EB13 on my devices when Im in CWM Reboot?
Click to expand...
Click to collapse
There is no unzipping. In CWM, you simply select "Install from sd", point to your .zip file, and tell it to start. CWM is pretty straight forward to navigate. It will probably take a couple minutes, after which you will select the Reboot option and watch your phone load.
cheech92007 said:
Okay the main thing that I am confused about is number 5. Why do I want these ROM's exactly? Pretty much all I want is that Red Angry Alien theme.
Click to expand...
Click to collapse
What randomking said....and
I didn't see what the red angry alien theme was designed for.... it just says ec05...ec05 is the latest build of froyo we have. Because all you want is a theme I'm going to suggest you do the oneclick root cwm version 2.5.5(stock file system).
I assume you'll need to be on a deodexed rom to flash that, but you may want to try it(since you learned how to odin you can just about recover from anything) and see if it works.
After you run the oneclick 2.5.5 root your good to go, just boot back into clockworkmod(2.5.5 is green text and not orange) click down to backup/restore, click on it and then click backup. This is what's called a nandroid. A nandroid is a complete backup of your entire system, including all user data. The only thing it will not backup is the kernel, since your not changing the kernel it won't matter. If you have problems or mess up you just wipe everything/factory reset/cache/dalvik cache and instead of going to backup, you select restore....blaam exactly the way your phone was when you backed it up. BTW backing up and restoring takes about 10minutes and don't try it when your battery is almost dead.
Hope that helps a bit more and don't rush it, the theme will be here for a long while I'm sure.
RandomKing said:
There is no unzipping. In CWM, you simply select "Install from sd", point to your .zip file, and tell it to start. CWM is pretty straight forward to navigate. It will probably take a couple minutes, after which you will select the Reboot option and watch your phone load.
Click to expand...
Click to collapse
Great, Thank you so much I really appreciate it.
Now all I need to do is get my theme on here xD
cheech92007 said:
Great, Thank you so much I really appreciate it.
Now all I need to do is get my theme on here xD
Click to expand...
Click to collapse
On second thought cheech, go herehttp://forum.xda-developers.com/showthread.php?t=1009997 and watch every single one of these videos and don't ask anything more untill you have.....deal?
epic4GEE said:
On second thought cheech, go herehttp://forum.xda-developers.com/showthread.php?t=1009997 and watch every single one of these videos and don't ask anything more untill you have.....deal?
Click to expand...
Click to collapse
yessir!
cheech92007 said:
yessir!
Click to expand...
Click to collapse
I'll thank that post later if you really watch ALL those videos.....they're really helpful
i havent been able to restore any backups for a while now, not an issue since im not as bad with the crackflashing addiction lol
well went to try a restore, didnt work-error while flashing boot img
tried advanced restore and got the same messge.
how do i check to see why it isnt working properly?
ive never been able to get an answer for this issue before so a little help would be awesome
reason i tried a backup, i did a flashover on cm7, and lost some(quite a few) of my pictures...so i tried the backup and got that crap again
so ya...not sure whats up
OMG_VTEC said:
i havent been able to restore any backups for a while now, not an issue since im not as bad with the crackflashing addiction lol
well went to try a restore, didnt work-error while flashing boot img
tried advanced restore and got the same messge.
how do i check to see why it isnt working properly?
ive never been able to get an answer for this issue before so a little help would be awesome
reason i tried a backup, i did a flashover on cm7, and lost some(quite a few) of my pictures...so i tried the backup and got that crap again
so ya...not sure whats up
Click to expand...
Click to collapse
shouldn't your pictures have been on your sd card?
anyways, you didnt really give any helpful information as to what your problem is, but maybe you could try this http://forum.xda-developers.com/showthread.php?t=714114
yes they were on my sd card, thats what doesnt make a lot of sense about it
and its not say md5 mismatch, i told you everything my phone said...all it says is "error flashing boot img"
if i had helpful info pertaining to this issue id be a lot closer to solving it...
Yeah, There shouldn't be an MD5 mismatch when your phone generated the MD5 to begin with.
I would suggest reflashing clockwork a few times from within ROM manager. It is the first option on the app which says "Flash ClockworkMod Recovery"
If that doesn't help your problem:
It shouldn't make a difference because ROM Manager is made by the CWM team but I would suggest trying to create a backup from within Clockwork and see if you can then restore the backup or even to just try restoring the backup you already made from within CWM rather than trying to use ROM manager. I've heard a lot about ROM manager having problems, so even though it takes a little more work you might want to take that route from now on.
In case you don't know how, all you need to do to get to clockwork is hold down the power button on your phone and then select reboot into recovery.
Once you're in recovery mode you need to select backup/restore using the optical joystick at the bottom of the phone to make your selections. When you make a backup from within clockwork you are unable to change the name before the backup is created but when you boot your phone up you can use any file manager to navigate to the clockwork/backup folder on your SD card and the bottom one should be the most recent because they are listed by date and then time that they were created.
I know it is a little redundant but it is always worth trying the easiest thing first before trying to overhaul your phone.
i dont use rom manager for anything...
i think im gonna try to complete reflash and re root and see what happens...kinda pissed i lost a lot of my pictures though
really confuses me...
try checking the internal flash memory, for some reason some of my pictures wind up there on accident sometimes. When you connect to your PC it is the third mass storage that shows up usually. I don't know how to access it from within the phone. and I apologize for the confusion but the title of the thread is "ROM manager issue" so that's what i thought you meant.
i tend to mistakenly call cwm rom manager since thats where i got it from
Hi. I managed to root my S3 and remove Knox. At first, TWRP was working fine, but after a few unsuccessful attempts to flash CM, I think i screwed it up. My backup files are gone, and it won't make a new one as it "cannot access storage." It also takes up about 6 gigs of storage on the phone per applications manager, which seems like a lot.
Is there a way to delete it and do a fresh install? now that I am rooted, would another backup/recovery be better?
I have tried searches, nothing seems to be on oint. Perhaps I was casting my net too wide or too narrow.
THANKS
Probably has to do with the /0/0/0 folders. Every time you flashed something, itd create a new /0 directory. Your stuff is still there but the path is messed up so it doesn't know where to look. In twrp file manager look for /storage/0/0/0 or something/somewhere like that. (It's been a while so I may not be remembering exactly right) this is a well documented issue though, so if im wrong just Google it and you're sure to find the right info. I believe it may be covered in one of the sticky threads too.
Sent from my SM-N900T using Tapatalk
Idk if this is your issue or not but I had a problem where recovery couldn't find the files or access storage I had the wrong version of recovery flashed and it wouldn't read anything I originally had the right one but somehow I lost recovery and ended up flashing the wrong one and it did what you are describing I'm on cwm so I'm not sure which is the right twrp but I'd just make sure you have the right one for your model. Good luck figuring it out though I know you will if you do your homework you will get it.
I went in and looked at the files, I had several named backups. I deleted all but one.
Goo Manager wouldn't load the newest TWRP, so I went to the app store and downloaded the app.
Now it takes far less space and recognizes the one backup.
THANKS for bearing with me.
I put a copy of the backup on my computer, just in case. Going to try flashing CM again, hope I can get it to work.