Database Info

Evo Shift Root Exploit and Development Thread

Please place all of your discussions about obtaining root on the Evo Shift here.
Temp root:​Temporary root can be acheived a number of ways on the shift the easiest being either z4root app or the visionary plus root app.​
Z4root:
download here and install as you would any other apk
open the app and hit temporary root
let it run till you are notified of its success
you now have temporary root!!
*Note you have to reapply z4 each time you reboot your phone
Visionary:
full instructions and the link to visionary can be found here.​ http://android.modaco.com/content/h...m/320722/19-nov-r14-visionary-one-click-root/
IMPORTANT NOTE!
PLEASE DO NOT ACCEPT ANY OTA UPDATES!!!!!!!!!!!!!!!!!​
they patched the root exploit on the desire z when they updated you can most definitely expect them to do the same for the shift so please for that sake of everybody being able to get proper root do not accept any updates unless further notified!!!
unless you just dont care about root that is.....

so far, we got a temporary root.
No point in trying unrevoked as it scans for the device name and shows
"sorry, the device 'speedy' is not suppored" (paraphrasing)
wish i knew alittle more about this.
You can get to hboot by Holding down the vol down while powering on

Also in a previous thread bubby323 requested a dump of /system and dnalevelc obliged:
* http://www.digglesworth.net/evoshift/system.7z
In another forum (androidcentral) someone noted that an app called VISIONary works to auto temp-root the Shift upon boot.
* http://android.modaco.com/content/h...m/320722/19-nov-r14-visionary-one-click-root/
Edit: Also there's code to temp root the G2 using a different exploit below. I haven't attempted to run it on my Shift. Possibly not relevant since it has a newer version but could be if an update is pushed to the Shift:
* https://github.com/tmzt/g2root-kmod/tree/scotty2/scotty2/psneuter

got the shift today. MAN this thing is fast! i'd love to see unrevoked release a small update that supports the shift. otherwise i can do it the long way but i can't wait to see the scores once i get a custom ROM on it.

Visonary does work, I turned on temproot on boot and then i pressed temproot now and it rebooted the phone. The phone was either taking its time or got stuck on the 4G for 2-3 mins so I pulled the battery and started the phone up again. I installed connectbot and typed su and got a #. Tried the reboot command and it wouldn't let me so I went into root explorer and it prompted the su app, gave it permission and started hacking away at bloatware..... no luck, it still came back from the grave :\

I successfully Temp rooted with z4root (http://forum.xda-developers.com/showthread.php?t=833953) and I couldnt get the download off the market so I just went to 4shared.com and searched z4root and picked up 1.3.0 which is the latest version....
It worked great and I used Titanium back up and a screen shot app that both needed root.

does anyone think the rageagainstthecage exploit will work on this? i assume people are working on it? cause if it does, that means unrevoked3 could possibly release a new version with shift support, right? since unrevoked is just an automated rageagainstthecage, right?
edit: i mean, for permanent root, S-OFF.

steven1022 said:
I successfully Temp rooted with z4root (http://forum.xda-developers.com/showthread.php?t=833953) and I couldnt get the download off the market so I just went to 4shared.com and searched z4root and picked up 1.3.0 which is the latest version....
It worked great and I used Titanium back up and a screen shot app that both needed root.
Click to expand...
Click to collapse
Z4Root temp root was a success but SU is telling me to upgrade by going into recovery, How do I go about this? I can't get any permissions for Rom Manager, Titanium, BusyBox, Etc...

rhodiggah said:
Z4Root temp root was a success but SU is telling me to upgrade by going into recovery, How do I go about this? I can't get any permissions for Rom Manager, Titanium, BusyBox, Etc...
Click to expand...
Click to collapse
Nevermind, figured it out. I accidentally rebooted, therefore, I lost root...

yokken said:
does anyone think the rageagainstthecage exploit will work on this? i assume people are working on it? cause if it does, that means unrevoked3 could possibly release a new version with shift support, right? since unrevoked is just an automated rageagainstthecage, right?
edit: i mean, for permanent root, S-OFF.
Click to expand...
Click to collapse
yes, the rage exploit is what works and is what z4root uses. However I couldn't get the actual binary to work from the CLI using adb.

Just curious--with this temp root, will the wireless tether app work? At least until the phone is restarted. I use that app quite a bit with my Hero, to get on the sites blocked at work on my ipad

tatonka_hero said:
Just curious--with this temp root, will the wireless tether app work? At least until the phone is restarted. I use that app quite a bit with my Hero, to get on the sites blocked at work on my ipad
Click to expand...
Click to collapse
yes as reported by others i dont have yet but want...

http://twitter.com/unrevoked/status/24492360310198272#

riggsandroid said:
http://twitter.com/unrevoked/status/24492360310198272#
Click to expand...
Click to collapse
blocked at work (thus the wifi tether needed )
what's it say? lol

Yes we finally got a forum
But on to the good stuff and not so good stuff
Even though we only have temp root partitions on the shift can be flashed using dd I won't go into exactly how to do it till I get home because the commands have to be EXACT!!!! Or u risk bricking your phone... I've had to ruu a couple times now
O btw the ruu that was previously leaked appears to be exactly what was released on the shift.
Sent from my PG06100 using Tapatalk

"Maybe good news for people with the HTC Wildfire. We're looking at it. (Also maybe good news for people with Evo Shift 4G sooner or later.)"

Here is a link to the thread with the leaked RUU if anyone needs it
linky

BrandoKC said:
Here is a link to the thread with the leaked RUU if anyone needs it
linky
Click to expand...
Click to collapse
has this been tested? is this the stock RUU that ships with the phone? can it be flashed no problems to return to factory if i mess something up with root? (like remove an application that is integral to the OS or to sense or something)

StAlphonso said:
has this been tested? is this the stock RUU that ships with the phone? can it be flashed no problems to return to factory if i mess something up with root? (like remove an application that is integral to the OS or to sense or something)
Click to expand...
Click to collapse
Take a look at bcnice's post two above mine

riggsandroid said:
http://twitter.com/unrevoked/status/24492360310198272#
Click to expand...
Click to collapse
Great tip. It's just a matter of time now...

HTC Sense force closes every time I install an app; rooted

So yeah, any time I install an app from the market or the Amazon store, Sense force closes. I'm rooted using stock ROM. Known issue, or more importantly, advice?
Sent from my myTouch_4G_Slide using XDA Premium App

Did you try fixing permissions inside rom manager? That normally fixes root related fc issues.

Hmm I'm not actually sure what you mean. ROM manager?
Sent from my myTouch_4G_Slide using XDA Premium App

You're rooted and you don't have ROM Manager?

rorytmeadows said:
Hmm I'm not actually sure what you mean. ROM manager?
Sent from my myTouch_4G_Slide using XDA Premium App
Click to expand...
Click to collapse
You are kidding right? Please say this is a joke?

AndroidBotx said:
You are kidding right? Please say this is a joke?
Click to expand...
Click to collapse
Why? I rarely use it, and have only installed it a few times but don't usually keep it installed.
Honestly it's not necessary, but does let you easily install a custom recovery in some situations. For an S-OFF device there are much easier and more convenient ways to do so.
For the first few months we had the device there was no official recovery and ROM Manager was dangerous to use (not so anymore)

Blue6IX said:
Why? I rarely use it, and have only installed it a few times but don't usually keep it installed.
Honestly it's not necessary, but does let you easily install a custom recovery in some situations. For an S-OFF device there are much easier and more convenient ways to do so.
For the first few months we had the device there was no official recovery and ROM Manager was dangerous to use (not so anymore)
Click to expand...
Click to collapse
Press "flash recovery" and grant Superuser permissions. Not that hard.
Delivered via candygram for Mr. Mongo.

Haha I didn't realize I was so far out of the loop! With my phones, I root to get access to system folders, system apps, and to run adfree. I don't flash ROMs at all and always keep stock ROM. If I saw "ROM manager" before, I probably brushed it off without thinking because I associated it with custom ROMs.
Sent from my myTouch_4G_Slide using XDA Premium App

rorytmeadows said:
Haha I didn't realize I was so far out of the loop! With my phones, I root to get access to system folders, system apps, and to run adfree. I don't flash ROMs at all and always keep stock ROM. If I saw "ROM manager" before, I probably brushed it off without thinking because I associated it with custom ROMs.
Sent from my myTouch_4G_Slide using XDA Premium App
Click to expand...
Click to collapse
ROM Manager also allows you to flash ClockworkMod recovery and fixes your apps permissions. Once we get AOSP on this phone, you'll see what's really available.

blackknightavalon said:
fixes your apps permissions
Click to expand...
Click to collapse
So, I ran the fix app permissions from the ROM Manager and that didn't change anything. I went to install something from the market and although I didn't get a FORCE CLOSE pop up message, I did notice the MyTouch splash coming back up reloading Sense once again...
:-(
I appreciate any help offered. Thanks,

rorytmeadows said:
So, I ran the fix app permissions from the ROM Manager and that didn't change anything. I went to install something from the market and although I didn't get a FORCE CLOSE pop up message, I did notice the MyTouch splash coming back up reloading Sense once again...
:-(
I appreciate any help offered. Thanks,
Click to expand...
Click to collapse
That is 100% normal when using the bone stock rom. Thats why 95% of peeps who root use a custom rom.

AndroidBotx said:
That is 100% normal when using the bone stock rom. Thats why 95% of peeps who root use a custom rom.
Click to expand...
Click to collapse
Not only that - but i've noticed on the stock ROM every time I plug my phone into a computer without rebooting first it locks up and restarts - I have yet to have this happen on my ROM or any of the others I used before that.
Once you root the stock ROM, it just doesn't seem to work as well, and I had the restart issue before root was available for us with this device. At first I thought it was my computer doing it, but now with an older desktop in service it happens on that too, and other random computers I plug into that my friends own too...I dunno.
There is a lot to be said for running a custom ROM instead of the stock one, beyond all the little fixes and enhancements they bring.
...but, that's why we all work together here to constantly bring better software with more support for these devices all over XDA.
rorytmeadows said:
So, I ran the fix app permissions from the ROM Manager and that didn't change anything. I went to install something from the market and although I didn't get a FORCE CLOSE pop up message, I did notice the MyTouch splash coming back up reloading Sense once again...
:-(
I appreciate any help offered. Thanks,
Click to expand...
Click to collapse
When is the last time you cleared cache and dalvik-cache? That might help with some of your issues.
I wrote a flashable-zip package that will do just that if you don't want to do it manually, it does a wipe (not format) so is compatible with all 3 clockworkmod recoveries we have available, since 4.0.0.8 and 4.0.0.9 don't implement the format command correctly.
Blue6IX said:
Third one is: Blue6IX_C01_Wipe.zip
MD5: a8c57de781b2abfca2dfcdcae57d439c
This one will wipe the /cache partition and also wipe dalvik-cache. Use this one if you are having problems with specific apps, especially when changing to a different version of an already installed app.
Click to expand...
Click to collapse
Either manually doing it or flashing my script might help with your issues, or might have no effect.
The next time you boot after doing so the machine will have to rebuild both cache and dalvik-cache, so it will take a little longer to boot that first time and after it's done and has sat for 5 minutes or so you should reboot the machine again before using it, just to get everything worked out right.
Hope it helps!

(SOLVED)[Q] how to tell if phone is already rooted.....

So I just picked up a skyrocket and I went to update OTA and it downloaded the update and when it went to restart to install the update the phone booted into clockwork. I wasnt able to find a thread for this specific device about it so I am asking here now. MOD if there is one please point me in the right direction. I did notice that there is no att bloatware on the device. Thanks.

Terminal editor, type su, press enter, see what happens.
Other clues: presence of Superuser app.
You have a custom recovery also which will need to be ODINed away.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Yes, it does have superuser. As far as Terminal editor/ODINed i'll be honest I have no idea what you are talking about. First sammy device that I have had long enough to keep and want to keep. Use to HTC branded devices. But thank you I think it is rooted because of the superuser app.

Questions should be posted in Q&A. Moved.
Side note: I recommend you read a lot before you mess with it. Although this device seems to be very difficult to hardbrick misusing ODIN can lead to one.
Cheers

Go to market download root checker. Run it. If a super user prompt appears, that's a good sign.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

occupational_hazard said:
Go to market download root checker. Run it. If a super user prompt appears, that's a good sign.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Yes it does, superuser prompt comes up. I really would just rather have this back to completly stock running 2.3.6 until the 4.0 update rolls out. Not sure which is better. Rooted or unrooted????? Also am not sure if it has ODIN....I tried to boot into recovery to run ODIN3 and upgrade to 4.0.4 but when trying to power on into bootloader it just vibrates and will not boot until I release the volume up rocker. Other than curiosity the phone works and performs flawlessly. With superuser being installed and after installing titanium I am sure it is rooted. Still not sure what ODIN is (like I said used to the HTC branded phones and never cared about root) Thanks for all the information. Also I am not sure if I will be able to update to 4.0 when the OTA update rolls out, im not concerned about it being rooted or not (have not found a reason to have rooted yet). Anyone know if it can be updated OTA even though it has root?

didozer said:
Yes it does, superuser prompt comes up. I really would just rather have this back to completly stock running 2.3.6 until the 4.0 update rolls out. Not sure which is better. Rooted or unrooted????? Also am not sure if it has ODIN....I tried to boot into recovery to run ODIN3 and upgrade to 4.0.4 but when trying to power on into bootloader it just vibrates and will not boot until I release the volume up rocker. Other than curiosity the phone works and performs flawlessly. With superuser being installed and after installing titanium I am sure it is rooted. Still not sure what ODIN is (like I said used to the HTC branded phones and never cared about root) Thanks for all the information. Also I am not sure if I will be able to update to 4.0 when the OTA update rolls out, im not concerned about it being rooted or not (have not found a reason to have rooted yet). Anyone know if it can be updated OTA even though it has root?
Click to expand...
Click to collapse
Ota will not work with cwm...you need the stock recovery to do an ota......rooted I don't believe matters
Sent from my A500 using Tapatalk

StolenVW said:
Ota will not work with cwm...you need the stock recovery to do an ota......rooted I don't believe matters
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Can I download and install via sd card when the update is available. Only time I have used cwm is on my wifes old eris.

didozer said:
Can I download and install via sd card when the update is available. Only time I have used cwm is on my wifes old eris.
Click to expand...
Click to collapse
You need stock recovery. You need to read the stickies for a few days before you do anything.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Or just keep your phone as is, and wait when ics officially drops, just wait a day and someone will have a flashable zip of it for cwm. Might as well learn the perks of being rooted now and learn your way around the phone
Sent from my SAMSUNG-SGH-I727 using xda premium

Its all set now. Had to figure out the whole Odin thing. Ended up just redoing to software using my computer with a one click method. Can't remember who made it but it was from android central but mad by member on here. So thank you to that mamber Kenny something?? Any was have it flashed to 4.0.4 with no bugs. Everything works perfect and so far battery life is great. I must say that so far I am loving this phone. At first I wasn't sure about going away from my vivid but I can't find any reason to have any regrets. Thanks guys I appriciate your help and input.

can u put solved in ur title

[HOW TO] Root Atrix 2 running on Android GB(2.3.6) / ICS(4.0.4).

This is a method to root Atrix 2 running on Android GB(2.3.6) / ICS(4.0.4).​
EDIT: Last updated on 26th July 2012
WHAT WORKS: Everything including the setting inside superuser which was not working in superuser 3.1
If you use this MOD, then please click on thanks button below.
I have updated this method to latest version of superuser 3.1.3 and su binary 3.1.1 for better compatibility with various Apps.
By following the below instructions you will be rooted in no time. If you have any questions feel free to ask.
Features added in superuser 3.1.3:
1.Temp unroot
2. Ota survival
3. Outdated binary Notification
Method:
1. Enable "USB debugging" in your phone settings
2. Download the attachment Named "Motofail Root (superuser 3.1.3, su binary 3.1.1).zip" to root Android GB(2.3.6)
or Attachment named "ICS_root(superuser 3.1.3 and su binary 3.1.1) .zip" to root Android ICS (4.0.4).
3. Uninstall your old Motorola drivers from PC and install these new drivers.
4. Connect your phone with original USB cable that came with your phone.
5. To root Android GB(2.3.6) click on "Click-To-Root.bat" in the attachment folder or
To root Android ICS(4.0.4) click on "Root.bat" in the attachment folder
6.Your phone will reboot 2-3 times don't remove the USB cable during this process
NOTE: If you are unable to Root even after following the above MOD then perform a Factory restore after OTA update and retry.

Can i root the ics with this?
And my phone is rooted,but can i re-root it?

atrix2 said:
Can i root the ics with this?
And my phone is rooted,but can i re-root it?
Click to expand...
Click to collapse
YES

Thanks for the new update.......
Sent from my GT-S6102 using Tapatalk 2

Please be aware that other A2 users have had issues with Superuser versions higher than 3.0.3.
Sent from my SAMSUNG-SGH-I747 using xda premium

jimbridgman said:
Please be aware that other A2 users have had issues with Superuser versions higher than 3.0.3.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I haven't been having problems, but I always have been using the older motofail exploit then updating the binary from within the app.

lkrasner said:
I haven't been having problems, but I always have been using the older motofail exploit then updating the binary from within the app.
Click to expand...
Click to collapse
I had the issue the other day, on stock 2.3.6, I also saw that alterdlikeness had a similar issue as well. It was updating past the 3.03 on both su and Superuser.
I had issues on my A2 with 3.1 only, and it would just FC and not work. I had to remove and basically re-root, and leave it at 3.0.1.

jimbridgman said:
I had the issue the other day, on stock 2.3.6, I also saw that alterdlikeness had a similar issue as well. It was updating past the 3.03 on both su and Superuser.
I had issues on my A2 with 3.1 only, and it would just FC and not work. I had to remove and basically re-root, and leave it at 3.0.1.
Click to expand...
Click to collapse
hmm. good to know in case it ever happens to me. I guess I will know I am not alone.

I don't know about other variants but it is working on ATT ROM and I have also assisted the same method to one user in India on androidcentral who was on MEART ROM and it even worked for him.

prasannapmv said:
I don't know about other variants but it is working on ATT ROM and I have also assisted the same method to one user in India on androidcentral who was on MEART ROM and it even worked for him.
Click to expand...
Click to collapse
You missed the point I was trying to make to those wanting to update thier binaries for su and superuser.... not new root exploits.
I just want everyone to know there are issues with 3.1... however today an update to 3.1.2 today has been proven to work for those having the issues that both alteredlikness and I have seen with FCs.
Sent from my MB865 using xda premium

On Stock 2.3.6 rooted. The new updates to the Superuser app allow you to update the binary and use the settings now.

Updating thread for superuser 3.1.2 now..

This method works as stated today I was trying to update my su binary but update was not getting successful so I unrooted and rooted back using this method now everything is updated and running smoothly.

About to root my girlfriends phone to eventually install Lithium.
Coming from a AT&T Galaxy S2 so things are a bit different here.
Should I use this method or Jimmy's from this thread? http://forum.xda-developers.com/showthread.php?t=1327741
After that what steps do I need to take to get CWM installed so I can backup and install a new ROM?
Thanks thanks!

seanpr123 said:
About to root my girlfriends phone to eventually install Lithium.
Coming from a AT&T Galaxy S2 so things are a bit different here.
Should I use this method or Jimmy's from this thread? http://forum.xda-developers.com/showthread.php?t=1327741
After that what steps do I need to take to get CWM installed so I can backup and install a new ROM?
Thanks thanks!
Click to expand...
Click to collapse
I think they are the same, except this one has a more updated version of superuser - I think (someone correct me if I'm wrong).
I personally have always used the one in Jimmy's thread and just update the superuser app and binary (and, thanks for reminding me about that post - I never thanked him until today - and due credit to p3droid & JRW 28 of course).
As for CWM recovery, just install the A2 Bootstrap app after being rooted. Use the bootstrap app - top button, OK, bottom button to boot into recovery.
Good luck to you and your girl!

alteredlikeness said:
I think they are the same, except this one has a more updated version of superuser - I think (someone correct me if I'm wrong).
I personally have always used the one in Jimmy's thread and just update the superuser app and binary (and, thanks for reminding me about that post - I never thanked him until today - and due credit to p3droid & JRW 28 of course).
As for CWM recovery, just install the A2 Bootstrap app after being rooted. Use the bootstrap app - top button, OK, bottom button to boot into recovery.
Good luck to you and your girl!
Click to expand...
Click to collapse
Boom, was one setup ahead of you and just finished all that. Currently backing up in CWM and waiting for a painfully slow download of Lithium and we should be jammin. Can't believe how easy it all was actually.
So I assume since this CWM is loaded from an app there's no way to boot into recovery should a bootloop or rom failure happen? Is that something people worry about?
Thanks for your response bud.

seanpr123 said:
Boom, was one setup ahead of you and just finished all that. Currently backing up in CWM and waiting for a painfully slow download of Lithium and we should be jammin. Can't believe how easy it all was actually.
So I assume since this CWM is loaded from an app there's no way to boot into recovery should a bootloop or rom failure happen? Is that something people worry about?
Thanks for your response bud.
Click to expand...
Click to collapse
The cwm on boot feature may already be included in Lithium (edit: yes, it it included - just checked)... if not, you can set that up rather painlessly. And, yes, some of us do worry about that very much so..

Great thanks! worked perfectly for me on the ICS leak (non AT&T A2)

So I am on Atrix Xperia 4 rom and i was wondering if there is any way to re-root my phone to ICS and then flash the ics rom? I really havent seen anyone ask this yet but sorry if I am repeating anyones question.

matt_12tall said:
So I am on Atrix Xperia 4 rom and i was wondering if there is any way to re-root my phone to ICS and then flash the ics rom? I really havent seen anyone ask this yet but sorry if I am repeating anyones question.
Click to expand...
Click to collapse
Are you on the ICS leak already? Are you on AT&T? If you are on the ICS leak and on AT&T there is a way to root it in the leak thread in the General section. I put the files back up today.
If not, I really am not sure, one of the guys on the other leaks might be able to help there.

[Q] Bad Recovery flash? (SOLVED)

I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich

Anyone?
Sent from my SCH-I535 using xda premium

Never mind...

Macrodroid said:
I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Click to expand...
Click to collapse
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.

david_hume said:
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
Click to expand...
Click to collapse
Ok, I've gotvtwrp 2.6.3.0 loaded, works... But, I cannot mount anything, backup totally fails. Any ideas? Twrp also asks for a password for some reason...
Btw, nice to see a familiar face on here! How's life treating you these days?
Sent from my SCH-I535 using xda premium

Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app

stolo said:
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks! After going through Rom Manager and letting it update CWR on it's own, I finally got everything working now! Backup of the Stock Rom is done finally and I can start flashing some Rom's to get comfortable with things... Hopefully, I can start putting out some Rom's for this device soon!! Thanks for all the help, I really appreciate it!

I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app

stolo said:
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Got wicked loaded up! So far, so good. I might try pulling a repo on cm11 sometime soon...
Sent from my SCH-I535 using xda premium