Related
Rom Manager doesn't seem to know that I've got CWM installed. When I rooted and installed CWM I didn't do it through Rom Manager originally. Now CWM won't let me use it to manage my backups and keeps asking me if I want to install CWM? I've got Google Wallet installed so I'm a little nervous flashing things needlessly.
Any suggestions?
Thanks
edit: CWM v5.5.0.4
do you try "wipe cache" and "advanced->wipe dalvik cache?"
Thanks, I just tried, it took quite a while to clear the cache. When I booted up it went through a whole Optimizing Apps process, I'm not sure if that was due to wiping the dalvik cache? But it still didn't fix the Rom Manager issue.
Its probably not yet compatible if you have the touch version of cwm installed, so it wants to flash the standard one. Or you could always just let rom manager just reflash cwm overtop and then you may be good to go.
EvanVanVan said:
Rom Manager doesn't seem to know that I've got CWM installed. When I rooted and installed CWM I didn't do it through Rom Manager originally. Now CWM won't let me use it to manage my backups and keeps asking me if I want to install CWM? I've got Google Wallet installed so I'm a little nervous flashing things needlessly.
Any suggestions?
Thanks
Click to expand...
Click to collapse
Maybe it can't detect it? I know we had to set which CWM version we had installed on the SGS.
Maybe try to run the install?
Sent from my Galaxy Nexus using Tapatalk
I don't have the touch version installed (doesn't seem to be the touch version anyway). I should have said this in the first post but it CWM v5.5.0.4.
Herman76 said:
Maybe it can't detect it? I know we had to set which CWM version we had installed on the SGS.
Maybe try to run the install?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Flashing CWM over CWM shouldn't wipe my phone right? It's only the stock bootloader that requires a full wipe?
I installed ROM manager and then CWM via ROM manager last night and its CWM v5.5.0.2 which ROM manager thinks is the latest: perhaps it can't deal with 5.5.0.4 yet...
Clancy_s said:
I installed ROM manager and then CWM via ROM manager last night and its CWM v5.5.0.2 which ROM manager thinks is the latest: perhaps it can't deal with 5.5.0.4 yet...
Click to expand...
Click to collapse
ah, that would probably do it...guess i'll just wait it out a little longer, thanks
I have the exact same issue as this Rom Manager refuses to see I have CWM installed so just keeps telling me I need to install it it also can't download and flash its own version and just freezes after download
So any updates on this or more users experiencing it ?
I think I've found the solution. In ROM Manager tap the menu button at the top and then tap Manual Flash Override. Next it'll ask you if you've flashed CWM manually so tap OK because that's what we've done. Next pick which GN you have and then choose CWM 3.x+. There you have it, it should work now.
Don't use ROM Manager - problem solved!!
Seriously, though, it's a TERRIBLE piece of software
I'm fairly new to using it but it seems decent, why is it so terrible? I had an eris before this and did everything manually through recovery, this seems like it's a lot better than that.
It's just more trouble than it's worth. Why not just manually flash CWM using fastboot and get your head around that as opposed to an app which can - frankly - break things?
Flashing it via fastboot is what causes the above issue. Since you flash it manually rom manager can't see it, that's why I posted the above steps to kind of "force" rom manager to see the manually installed version.
But if you're not using ROM Manager then what's the issue? Copy ROM to SD card, reboot to recovery, flash ROM...where is ROM Manager needed in that equation?
If you're not using it then there is no issue, but this thread isn't about using it or not, it's about getting it to work with the galaxy nexus when you manually flash CWM.
I like it for the backup and restore feature and being able to change the names used to backup
hello, i just got my first android phone so I'm new to this sort of stuff, though I love being able to unlock hidden potential of different devices, so naturally I discovered the ability to root smart phones and all that good stuff.
The model I have is the Samsung Galaxy Gio GT-S5660M. It's running 2.3.4. Gingerbread version.
I've been reading a lot of guides and for the most part rooting and adding additional utilities like flash, etc. seems pretty simple. However, I have not yet been able to find out how to create a back of up of my stock firmware when I bought the phone in case I end up bricking it, or decide I want to return to stock.
I've read many guides that claim to show how to create back ups and recovery points, but I'm still having trouble understanding it.
To be more specific, I would like to create as opposed to download, a back up of the phone in it's current state which is, as I said earlier, stock. I did a factory reset since I had some stuff installed while I was fiddling with it for the first time.
thx
You have to root it before you can back up stock rom so, firstly you root it (you can find guides here on xda)
Then install clockworkmod recovery: warning: DON'T EVER USE ROM MANAGER TO INSTALL CLOCKWORKMOD ON YOUR GIO, IT WILL BRICK YOUR PHONE!! use one of the recoveries found in xda, you will also find guides to install them there.
Then third; backup in clockworkmod using "backup and restore"
Sent from my GT-S5660
iok1 said:
You have to root it before you can back up stock rom so, firstly you root it (you can find guides here on xda)
Then install clockworkmod recovery: warning: DON'T EVER USE ROM MANAGER TO INSTALL CLOCKWORKMOD ON YOUR GIO, IT WILL BRICK YOUR PHONE!! use one of the recoveries found in xda, you will also find guides to install them there.
Then third; backup in clockworkmod using "backup and restore"
Sent from my GT-S5660
Click to expand...
Click to collapse
so first of all, what I'm looking for is called a ROM right?
what I don't get though is how come I need to modify the device before creating the backup. Isn't the phone modified at that point? Or is the stock configuration being stored somewhere on the phone that I can't see without clockwork?
You cannot create a backup without the recovery mod CWM Clockwork Recovery Mod. But to install this you need your device rooted (modified so you can modify and view system files)
gfyrdr said:
so first of all, what I'm looking for is called a ROM right?
what I don't get though is how come I need to modify the device before creating the backup. Isn't the phone modified at that point? Or is the stock configuration being stored somewhere on the phone that I can't see without clockwork?
Click to expand...
Click to collapse
1 - you don't need to search for a rom to backup your stock rom
2 - you need to root your phone in order to be able to backup your rom
3 - you need to install a more advanced recovery (program "similar" to pc BIOS) in order to do a nandroid backup
4 - after you flash that more advanced recovery (aka CWM -> ClockWorkMod), you backup your rom in "backup and restore" menu, backup. It will then store your rom in a folder.
5 - you should strongly consider after that, to install a custom rom made by many of the devs here on XDA in order to have a better experience with your phone...
0M3G4_ said:
1 - you don't need to search for a rom to backup your stock rom
2 - you need to root your phone in order to be able to backup your rom
3 - you need to install a more advanced recovery (program "similar" to pc BIOS) in order to do a nandroid backup
4 - after you flash that more advanced recovery (aka CWM -> ClockWorkMod), you backup your rom in "backup and restore" menu, backup. It will then store your rom in a folder.
5 - you should strongly consider after that, to install a custom rom made by many of the devs here on XDA in order to have a better experience with your phone...
Click to expand...
Click to collapse
+1 That was what I wanted to say
I've already uploaded a stock ROM backup last fall of the same Gingerbread ROM you're running, along with instructions on how to make one yourself or flash mine.
The best advice I can give you is: research, research, and more research.
Good luck,
Darkshado
Sent from my Nexus S using XDA
What software do you recommend to clockworkmod Gio with?
s!mon said:
What software do you recommend to clockworkmod Gio with?
Click to expand...
Click to collapse
I use px-cwm-v2.zip recovery.
You flash it using stock recovery.
thx for the replies. I will give it a try.
Darkshadow, whats the thread's name where you posted the ROM and instructions? I'd like to check that out too.
Also, whats a good rom to consider upgrading to? Something that has the ability to play flash videos.
EDIT:
If I understand correctly, roms are basically whole operating systems that have been customized by the developer. So a rom can be already rooted and have clockwork as well as other custom stuff, and I just need to flash it. The alternative to this is to do everything manualy... root the current OS, add clockwork and whatever else. Correct?
Also, I'm not sure yet if a rooted phone has any extra options on it's own, or if it's only a set up that's sole purpose is to allow other applications to be installed who then will give the user better control over his device.
I've run into a little problem.
I'm following this guide: http://forum.xda-developers.com/showpost.php?p=16963172&postcount=1
I've got Odin and the tar downloaded, but when I go into download mode with my phone and connect it to the PC, it says that the device driver was not successfuly installed, and I get no confirmation in Odin that a connection has been made between the phone and the program.
What am I missing?
Thx.
EDIT:
Nevermind, I needed to install Kies. Don't even need to run it. Apparently it has the driver that's needed.
Okay, I've rooted my phone successfully. Now the next step is to install Clockwork and create a back up.
Now that I understand a little bit the way Odin and flashing ROM works, I think it would be better to just download a stock ROM and in case something goes wrong, I can just flash it the way I flashed the rooted one.
(I think I saw a completely stock ROM somewhere for my model but I don't remember where. A link would be appreciated if it exists.)
Correct me if I'm wrong pls.
Also, if I do that, then is there any reason to install Clockwork since I've read that many ppl have issues with installing it and it's riskier than rooting or installing other software.
Right now I think what I'm most interested in is installing Adobe Flash Player 11 or something of the sort that can play flash videos and streams.
^
http://forum.xda-developers.com/showpost.php?p=19623732&postcount=1
taken from the sticky
i'm also thinking of installing cwm
looking at the sticky, http://forum.xda-developers.com/showpost.php?p=20397988&postcount=8
how outdated is this cwm?
I'm using Opera as my browser so from what I've learned, flash doesn't work with it period. Is skyfire a good alternative?
Also, like I said, I don't think I need the clockwork if I can get a clean stock ROM that I can just flash if something goes wrong. As I don't intend to download many apps or add many phone numbers (memorized instead), a backup isn't really needed.
nvmd, i just went ahead and installed the cwm in that link, there's a 5.0.2.7 though if that is even the newest one
now, i cant seem to backup my phone
it says it cannot mount /system
try dolphin browser
anonxlg said:
nvmd, i just went ahead and installed the cwm in that link, there's a 5.0.2.7 though if that is even the newest one
now, i cant seem to backup my phone
it says it cannot mount /system
try dolphin browser
Click to expand...
Click to collapse
Did you pick the ext4 + rfs version?
Sent from my GT-S5660
Clockwork is not riskier than other things you do. Just follow steps and you see no problems.
anonxlg said:
^
http://forum.xda-developers.com/showpost.php?p=19623732&postcount=1
i'm also thinking of installing cwm
looking at the sticky, http://forum.xda-developers.com/showpost.php?p=20397988&postcount=8
how outdated is this cwm?
Click to expand...
Click to collapse
its an older version, its 5.0.2.7, theres also 5.0.2.8 but these give some problems after installing/wiping, so some people still use the older version.
Hello guys,
I'm new here. I have the same problem as anonxlg. It says can't mount system. I also used the version from the big thread for new users. Can anyone enlighten me on what to do? I've been searching the forum and google, but can't make it work. I feel like a compleet noob now, and I don't feel special about it.
RJ88
Edit: I kept searching, and finally found a working 5.0.2.7 version. First I had another 5.0.2.7 version, but when I tried to install it didn't work. I finally found "signed_cwm-5.0.2.7-flashablezip-ext4+rfs.zip (Flash from Recovery)" on http://forum.xda-developers.com/showthread.php?t=1421650 (through google actually. I have to get used to this site), and I'm making my backup now.
thanks RJA88, backup worked
edit/update
i used the cwm linked and backup worked, i tried installing cm9 beta8 (galaxyics), and it would get stuck after samsung bootscreen (it flashes a white pick or soemthing before full back screen)
i tried restoring backup i made, and it didnt work, some mount error again
i reverted back to 5.0.2.6 and did the restore backup again, and this time it goes up the the galaxy gio gt5660m screen and just stop..
note that i do not know what the rfs/ext4 is for for the gio if that is what is causing problems
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
lordcheeto03 said:
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
Click to expand...
Click to collapse
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
Swetnes said:
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
SectorNine50 said:
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
Click to expand...
Click to collapse
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
SectorNine50 said:
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
Click to expand...
Click to collapse
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
drumist said:
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
Click to expand...
Click to collapse
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
You are correct, the Nitro is P930. And I'm sure this doesn't need pointing out, but when you download the ROM, make sure it's for P93x and not SU640. Most of the ROMS in the developer section have versions for both models.
Also, when you say you can't access CWM after flashing a ROM, how are you trying to access it? Holding Power+Volume down until the Factory Reset screen pops up? It still shows that screen even with CWM installed, but when you press the power button to perform the factory reset it SHOULD take you into CWM Recovery instead.
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
To access recovery, turn the device completely off. (If you're in a bootloop, pull battery or hold power button for ~20 seconds until screen stays off.) Then when phone is off, press and hold volume down and power buttons at the same time, not releasing until you see text asking if you want to factory reset. Press power button twice to confirm and you'll get to recovery.
Is this the method you're using to try to get to CWM?
My guess as to why you are getting bootloops is that you aren't wiping data first.
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
SectorNine50 said:
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
Click to expand...
Click to collapse
Good luck. Other possible things to try:
1) Check zip MD5 hash (or just redownload and replace) to make sure it's not corrupted.
2) Reformat entire SD card.
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
SectorNine50 said:
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
Click to expand...
Click to collapse
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
drumist said:
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
Click to expand...
Click to collapse
Ah, thank you! I must've been viewing an old thread. Now that I look at the version number, it appears that's the version I had been hunting for since the newest one didn't work.
Interesting, I most certainly misunderstood, I was under the impression that "rooting" the device was a filesystem level permission change. Good to know!
It seems like we are getting closer to a solution here. Thanks for your patience!
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
SectorNine50 said:
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
Click to expand...
Click to collapse
Yeah, the new one (6.0.1.5) just came out. I'll have to test it to see if it works for me.
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Malnilion said:
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Click to expand...
Click to collapse
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I really enjoy the integration Rom Manager/CM Updater has with CWM. If twrp is capable of running the install scripts those two use, I might consider trying it out, but I don't really like manually going through the steps to flash a rom every day.
Hi,
My dad has rooted his Xperia S device,
He has a custom rom from work which he wants to backup before installing a new one.
When he tries to run nanandroid or Rom Manager it doesn't work.
nanandroid asks for update - it updates and it asks for an update again
Rom Manager says it does not support this device.
How can we backup the device (Simply if possible).
Thanks
Backup via CWM
I suggest online nandroid backup. It is in playstore. The application allows backup without entering CWM. The back up is in clockwork folder on sdcard usually. Simplest backup. Hope it helps.
Edit: just saw you tried nandroid. Maybe you don't have root permission?
Sent from my Xperia S using xda app-developers app
mmm273 said:
Backup via CWM
Click to expand...
Click to collapse
I'm assuming you meant CWM Rom manager,
I referred to it as Rom Manager in my initiall post
YYvo - I gave it root access,
I alse tried instaliing and ininstalling - still the same.
if it matters he tries to install onandriod script 6.0 (keep in mind I accept and install it, and he keep asking for it regardless)
The script installed should be 6.14 in nandroid. As for CWM it doesn't necessarily mean the Rom manager. Look for the thread that shows how to install CWM on Xperia S. I assumed it already had it as you said it had a custom Rom installed. If it has, To enter restart phone and hold volume up when led starts.
Sent from my Xperia S
itayze said:
I'm assuming you meant CWM Rom manager,
I referred to it as Rom Manager in my initiall post
YYvo - I gave it root access,
I alse tried instaliing and ininstalling - still the same.
if it matters he tries to install onandriod script 6.0 (keep in mind I accept and install it, and he keep asking for it regardless)
Click to expand...
Click to collapse
No ROM manager, only CWM recovery ....
tl;dr: What happens if I upgrade to CWM 6 after having used Darkside Superwipe on CWM 5?
And now the long explanation of what happened:
I have a Telus T989D, and I had installed the stock Telus JB ROM from this thread: http://forum.xda-developers.com/showthread.php?t=2343748
I previously had CWM, but as per the instructions in the thread I installed TWRP, ran the Infamous Superwipe zip file, and then proceeded to flash the ROM.
Then today I decided to install CM 10.1. The first thing I did was flash CWM 6.x (I forget the exact version, but it was the latest one) from ODIN. Then I downloaded the latest stable build (CM 10.1.2). I then ran the Infamous Superwipe zip file again, and flashed CM 10.1. The result was that the phone would get stuck on the Cyanogenmod circle logo. I did some Googling and found out some people who had bootloops after installing Cyanogenmod, and it was suggested that this was due to a bad wipe, and that using Darkside Superwipe would fix the problem. So I proceeded to give Darkside Superwipe a try... Of course at the time I hadn't realized that 1) What I had was not actually a boot loop (it wasn't rebooting, it was just stuck at the logo), and 2) that Darkside Superwipe should not be used with CWM 6. After flashing the Darkside file, my CWM 6 would load up but would fail to flash ANY zip file that I selected (it would just get stuck on the first line, "Installing xxx.zip"). It would also fail to wipe the /cache partition (would freeze at "wiping /cache partition").
After soft-bricking my phone by trying to flash a different recovery from Heimdall, I ended up following a guide on this forum to flash the stock Gingerbread ROM from Odin. I then flashed CWM 5.0.2.7, did the Darkside Superwipe, installed CM 10.1, and now thankfully the phone works.
My question is... Does anybody know what happened here? And any ideas what will happen if I try to upgrade my CyanogenMod later on? Will I have any issues running CWM 5.x with CM 10.1 or 10.2? I'm a bit afraid of updating to CWM 6 since I have no idea what the result will be.
I later learned that Infamous Wipe is only to be used with TW-based 4.1.2 ROMs, since it adds a preload partition. Did I end up somehow messing up my partitions by using the Infamous & Darkside Superwipe files?
Sorry for the long post... I just figured I should give as much information as possible! I'd really appreciate it if anybody has an explanation for what happened (messed up partitions?) and how to fix it!
OK so what u need to do first is stop flashing all these recoveries, DL twrp2.6.1.0 and flash that with Odin, stay with this recovery, cwm is OK but not updated frequently enough to keep up with newer flashing scripts, now don't use superwipe/super cache wipes with twrp, they will cause loops, do a full wipe with twrp, mount to USB move all files off SD cards and format them, replace any/all files from SD card that u want, now flash ROM, flash gapps, reboot and let sit ten min, this should fix ur issues, as far as what happens, u used superwipe scripts on 6.x+cwm, those scripts were meant for cwm5x, it'll loop every time...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
OK so what u need to do first is stop flashing all these recoveries, DL twrp2.6.1.0 and flash that with Odin, stay with this recovery, cwm is OK but not updated frequently enough to keep up with newer flashing scripts, now don't use superwipe/super cache wipes with twrp, they will cause loops, do a full wipe with twrp, mount to USB move all files off SD cards and format them, replace any/all files from SD card that u want, now flash ROM, flash gapps, reboot and let sit ten min, this should fix ur issues, as far as what happens, u used superwipe scripts on 6.x+cwm, those scripts were meant for cwm5x, it'll loop every time...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks soupysoup! I will do that the next time I update the phone. And just another quick question: do you know if TWRP is safe to use with CyanogenMod (since it seems that they recommend CWM)?
Faruk88 said:
Thanks soupysoup! I will do that the next time I update the phone. And just another quick question: do you know if TWRP is safe to use with CyanogenMod (since it seems that they recommend CWM)?
Click to expand...
Click to collapse
Yes, actually I reccomend twrp to everyone for every ROM, the only way a ROM could be recovery specific would be if the ROM called for specific flashing scripts a certain recovery used/ran but twrp is updated a lot and always uses the newest flashing scripts in there builds, plus the recovery itself is very user friendly, the newest version is 2.6.1.0, go check that out n fully 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
Yes, actually I reccomend twrp to everyone for every ROM, the only way a ROM could be recovery specific would be if the ROM called for specific flashing scripts a certain recovery used/ran but twrp is updated a lot and always uses the newest flashing scripts in there builds, plus the recovery itself is very user friendly, the newest version is 2.6.1.0, go check that out n fully 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Perfect, thanks! Just one last question, then: In your previous post you said to flash TWRP through Odin. Does it matter if I flash through Odin or if I just download Goo manager and switch to TWRP from there? Which one of the two options is safer/better?
Faruk88 said:
Perfect, thanks! Just one last question, then: In your previous post you said to flash TWRP through Odin. Does it matter if I flash through Odin or if I just download Goo manager and switch to TWRP from there? Which one of the two options is safer/better?
Click to expand...
Click to collapse
U can use goo manager if u want, but I will say this, sometimes too can cause soft bricks, in which case u would need Odin to recover , so in my professional opinion I would suggest using Odin from scratch
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app