Ok so I came from an HTC Hero which I rooted with z4root and I had ClockworkMod Recovery. I have had my Xperia play for a few months now and I have been trying to find a way to root it. Well I finally did using this tool here: http://forum.xda-developers.com/showthread.php?t=1487221. Well as soon as I got my root permission and I saw that I had superuser, I went straight to the market and downloaded Rom Manager. I tried to flash ClockworkMod Recovery from there but it says that R800x does not have an officially supported ClockworkMod Recovery yet. Well then I tried the flash alternate recovery part which is RA Recovery v.1.6.2. Well it acts like it is going to download then it gives me a message saying an error occurred while flashing your recovery. So my question is: Can someone please help me get a working recovery going on my phone?
The R800x has a locked bootloader so you can't use CWM in quite the same way. Look for the app calleo CWM in the market. It's for our phone and installs CWM in \system.
You won't be able to use custom kernels or OC unless you unlock the bootloader. However, there are a few ROMs you can try, and you can do a nandroid as well.
See the stickies in this section for more info and links,
Sent from my R800x using XDA
Just tried, it works! Thank you!
Sent from my R800x using Tapatalk
This couldn't have come at a better time for me. I just installed CWM Auto-Installer and it (at least seems to for now) works great.
Sent from my R800i using XDA
Hi all! xD
I want to know, how to update mi CMW Recovery on my T-Mobile G2
Currently, I have the ver. 3.0.4.0, and I saw in CMW's page, that the newest is the 5.0.2.7 (non-touch) and 5.8.1.0 (touch)
I heard, that if I update the recovery from the Rom Manager, it may break down everything D:!!!!
So, the question is....Will be everything alright if I Update the recovery from the ROM Manager? xD
And another thing, is it advisable to use touch recovery? Or it's better the clasic one?
Thanks a lot
first off i love the touch recovery, much easier so go that route. also i prefer 4ext recovery as i like the ui and it feels faster and has a few more options. but if you realy want to stay with koush id be suprised updating through rom manager would cause problems, if it did that would be another reason in my book not to use it. but you can always take the latest version and update via fastboot, adb or terminal emulator if needed
Sent from my HTC Vision using xda premium
Yes it is fine to update through ROM Manager.
If you are wanting touch recovery it can be achieved through rom manager but you must pay for it think it's only 99cents or if you go to clockworkmod.com you can download it for free the install process is different though Google it can't remember how I achieved it but was easy and worth it
Sent from my SGH-T959V using XDA
Ques.. like you
Sent from my HTC Vision using XDA Premium App
Im upgrading to an SGS3 from SGS2 and am curious whether the SGS2 usb jig will work on the SGS3 for resetting the flash counter?
Nope. You have to use triangle away. But if you utilize the no trip root method and install TWRP from goo manager you will never increment the flash counter.
Sent from my SAMSUNG-SGH-I747 using xda premium
d3athsd00r said:
Nope. You have to use triangle away. But if you utilize the no trip root method and install TWRP from goo manager you will never increment the flash counter.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I've only ever used 4EXT and CWM, am able to install CWM from TWRP recovery? This phone seems to use a different recovery method than I've used. I take it it's not incorporated into the Kernel like SGS2 where I can just flash a kernel with CWM.
I just saw the "Stupid Question" thread where this probably could have been asked so I apologize for starting a new thread for this question.
The S3 does not follow the same method of recovery as the S2. Kernels do not come with a recovery. You have to install the recovery manually. You can either use zips found in the recovery's thread or you can utilize goo manager to install TWRP (menu>install openscript recovery) or ROM manager to install CWM.
Sent from my SGH-I747 using xda premium
Twrp is similar to 4ext and cwm. Use it the same way.
So does this mean that 4EXT is an accepted recovery console for the I747? I have been reading a ton and I see so many people flashing with CWM and no one has mentioned 4EXT. Just wanting to make sure before taking the dive with my favorite recovery software.
Thanks!
jbonham said:
So does this mean that 4EXT is an accepted recovery console for the I747? I have been reading a ton and I see so many people flashing with CWM and no one has mentioned 4EXT. Just wanting to make sure before taking the dive with my favorite recovery software.
Thanks!
Click to expand...
Click to collapse
Honestly you will be better off with TWRP. I have completely stopped using CWM due to several issues it was involved in. So far not a single issue with TWRP. It's a quick download and install from the market, install the recovery from the app, and your good as gold.
1 thing to remember, as the devices get newer, some methods that you may be used to doing such as 4EXT may no longer be valid anymore.
Got it. I appreciate the quick reply and the heads up. Much props!
Forget about 4ext, it's no longer relevant now that you have the S3. Pick either CWM or TWRP (I recommend TWRP) and move on.
Sent from my SGH-I747 using xda premium
As others have suggested, go with TWRP. Used 4ext when I had my Inspire and loved it. However, check 4ext out on the Play Store and you'll find the S3 isn't listed as compatible. Tried CWM on the S3, and had issues, so switched to twrp and haven't looked back.
Hello,
So I've been rooted for a while now, i was going to install a custom rom but decided not to a few months ago. Tonight, i decided to install aokp, however my phone would not go into cwm, only stock recover. I could have sworn it was installed, but fine, so i installed it once again with auto reboot in odin checked, and it still wouldnt enter cwm. I then tried to install it again with auto reboot checked off so i could see if i could enter it without the reboot. I ended up getting into it, but then when i was taking a NANDROID, it just froze on one of the first steps. Fine, reboot, try to enter cwm again. Nope, just stock android recovery. I am sure im installing it correctly and pressing the right button combos. I am at a total loss for what is stopping me from being able to enter cwm. I hope you guys know/help me find whats going on.
Thanks!!!
Zay
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
pcshano said:
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
Click to expand...
Click to collapse
Yes my phones rooted.
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Zay48 said:
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Click to expand...
Click to collapse
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
pcshano said:
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
Click to expand...
Click to collapse
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
if you still want cwm then i guess you can try flash stock rom and root it again and see
since you're going to flash a custom rom which will delete all your data anyways
Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
RPelham said:
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Zay48 said:
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Click to expand...
Click to collapse
Bump
what version of CWM are you currently running?
you could always try to download GooManager or ROM Manager from the Play Store.
then from one of those, install the custom recovery, GooManager for TWRP or ROM Manager for CWM.
xBeerdroiDx said:
what version of CWM are you currently running?
Click to expand...
Click to collapse
3.0.7
Zay48 said:
3.0.7
Click to expand...
Click to collapse
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
zetsui said:
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
Click to expand...
Click to collapse
He's not having a problem restoring images, he's having a problem making his first nandroid.
Sent from my SGH-I747 using xda app-developers app
Zay48 said:
3.0.7
Click to expand...
Click to collapse
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
RPelham said:
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Download rom manager and update your cwm and then try making a nandroid again.
Sent from my SGH-I747 using xda app-developers app
CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
That said... If you insist in CWM, this is the guide I followed to get a successful CWM flash. (This was the CWM I was running successfully for the brief time TWRP disbanded.)
http://wiki.cyanogenmod.org/w/Install_CM_for_d2att
The above is for the ATT variant only. If you have a different variant and can't find the link, post back and I'll find it for you
Sent from my SGH-I747 using xda app-developers app
CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
apparently it's still around because new android users who want to root use those guides with outdated files
RPelham said:
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Preach brother!
Maybe I am not looking in the right places, but I am trying to figure out how to change from clockwork mod recovery to twrp recovery. All the instructions for installing twrp that I have found only allows tells how to install from a fresh root. I am already rooted and just want to use Twrp now in the place of CWM. Can anyone point me in the right direction? Am really not understanding what I am doing and want to NOT brick my phone
KuroXue said:
Maybe I am not looking in the right places, but I am trying to figure out how to change from clockwork mod recovery to twrp recovery. All the instructions for installing twrp that I have found only allows tells how to install from a fresh root. I am already rooted and just want to use Twrp now in the place of CWM. Can anyone point me in the right direction? Am really not understanding what I am doing and want to NOT brick my phone
Click to expand...
Click to collapse
I use this from CNexus... http://forum.xda-developers.com/showthread.php?p=41313260 its the best of both worlds. But from my understanding if you just want cwn you just download the zip and flash. Your nandroid from twrp are not compatible with cwm so make sure u keep them separately or delete them and make new ones. Again this is from my research. I use both and have no problem switching.
Sent from my SPH-L710 using xda app-developers app
KuroXue said:
Maybe I am not looking in the right places, but I am trying to figure out how to change from clockwork mod recovery to twrp recovery. All the instructions for installing twrp that I have found only allows tells how to install from a fresh root. I am already rooted and just want to use Twrp now in the place of CWM. Can anyone point me in the right direction? Am really not understanding what I am doing and want to NOT brick my phone
Click to expand...
Click to collapse
Just download goo.im from the market...I think it is called goo manager. They have an option that will auto install it.
I know about goo. Used it in my touchpad. Will installing twrp from here do anything to my existing status? Or just remove cwm and replace it with twrp? Has anyone tried it already?
Sent from my SPH-L710 using xda app-developers app
Just flash TWRP right over using goo manager.
Sent from the future via Tapatalk 4