• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Sprint/Cricket] Recovery Problems

Shmooey

Shmooey

Well-Known Member
Ok so Im in the process of rooting my S3 but my recovery wont mount the internal storage thing. I already checked out a different thread of a person having the same problem (this one http://androidforums.com/sprint-cri...oot/747509-cant-mount-sdcard-in-recovery.html) and got the fixed/modded recovery fix thing. How do I go about installing the new recovery cause it says to flash it with adb but I dont really know much about that kinda stuff.

Thanks in advance
 

Attachments

  • picture067.jpg
    picture067.jpg
    29.1 KB · Views: 75
o.k...this is how I read how to do this....do you agree?

Me said:
I would use the adb.zip file he has posted as you don't need the full sdk.
Download it, extract it and move it to a folder on your desktop.
Then download the recovery.img of your choice and put it in that same folder.

Make sure usb debugging is enabled on your device.
I'm assuming you have the phone drivers installed?
Plug your phone in and open up a command prompt at that folder you have with the adb and recovery.img file in it.
Run the commands he posts there.
Click to expand...
 
Ok so I followed those instructions and this is what I got from the command prompt


C:\Users\Garrett\Desktop\Android>adb push recovery.img /sdcard/recovery.img
2659 KB/s (6318080 bytes in 2.320s)

C:\Users\Garrett\Desktop\Android>adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18su
shell@android:/ $ su
/system/bin/sh: su: not found
127|shell@android:/ $
 
I would think after the "adb shell" command, you would see this:

C:\Users\Mike\Desktop\android-sdk\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Click to expand...
 
Mikestony said:
hmmmm, I wish I was more versed in adb :)
Do you get the "daemon starting" message after the "adb shell" command?
Click to expand...

Noo after I enter in adb shell I get "shell@android:/ $". I do remember getting the deamon not running/starting thing from one of my previous attempts, not sure what I did but I still remember getting that message
 
ah, try this then...type the following:
Code: 
adb kill-server

wait a few seconds, then type:
Code: 
adb start-server

Does the daemon start and recognize your device?
 
Alright did that and got this:

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
 
Typed that in and it shows:

List of devices attached
0ba052fa device

Just going to assume thats my phone :D
 
Yes, you are doing better than I am since mine says its offline:( 3 different cords and 2 ports later, still nothing:( But, that's my problem for later :D

Anyways, type:
Code: 
adb shell
 
Alright typed that in and got:

shell@android:/ $

Btw that sucks how your thing says offline. I know that my phone will only come up for sure on 1 of my ports, the other 2 are iffy
 
Shmooey said:
Alright typed that in and got:

shell@android:/ $

Btw that sucks how your thing says offline. I know that my phone will only come up for sure on 1 of my ports, the other 2 are iffy
Click to expand...
Meh, I'll worry about that later lol....

Well, I guess let's try and type the "su" command shall we? ;)
 
All right....let me back the bus up a sec....
I re-read thru this thread.
What recovery do you have now? It appeared in your screenshot in your first post that you had clockworkmod.
But in your first sentence, you stated you were in the process of rooting...as in, you are not rooted yet?
 
Mikestony said:
All right....let me back the bus up a sec....
I re-read thru this thread.
What recovery do you have now? It appeared in your screenshot in your first post that you had clockworkmod.
But in your first sentence, you stated you were in the process of rooting...as in, you are not rooted yet?
Click to expand...

Im following this guide ([HOW TO] Easiest Root and Recovery: SGS3 LTE Sprint, T-Mobile, AT&T, Rogers - xda-developers)

Recovery: CWM Recovery v5.5.0.4

Not rooted yet but I think the next step in that guide is flashing the zip that would root it.
 
Ah, that's why the command "su" won't work....
So that's where the hangup is....you cannot flash the zip.? Because your internal or external will not mount?
I'm not understanding that then :(
 
Mikestony said:
Ah, that's why the command "su" won't work....
So that's where the hangup is....you cannot flash the zip.? Because your internal or external will not mount?
I'm not understanding that then :(
Click to expand...

Ya like when I go to try and access the external or internal it says:

E: Can't mount /emmc/

and/or

E: Can't mount/sdcard/
 
You must log in or register to reply here.
Back
Top Bottom