Related
It seems as though a lot of people have had this problem for other phones but I haven't been able to find a solution to it (forgive me if its somewhere very obvious ).
After editing my framework-res.apk I am trying to push it back into my milestone through the SDK so I have tried to get my phone to show up while in recovery mode so I can push it back on.
The problem is that while in recovery my phone won't appear under "adb devices" I have tried using GOT's recovery and also the regular Openrecovery v1.37
Thanks
bump. i also need this. btw have you tried using a script to do it?
danboard said:
It seems as though a lot of people have had this problem for other phones but I haven't been able to find a solution to it (forgive me if its somewhere very obvious ).
After editing my framework-res.apk I am trying to push it back into my milestone through the SDK so I have tried to get my phone to show up while in recovery mode so I can push it back on.
The problem is that while in recovery my phone won't appear under "adb devices" I have tried using GOT's recovery and also the regular Openrecovery v1.37
Thanks
Click to expand...
Click to collapse
Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=698059
and especially did you install this driver?
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
I do have read the thread and I have installed that driver. While in recovery mode using GOT's or OpenRecovery I notice that under device manager it says my phone is listed as "Android Phone" and if my phone is on and I connect it to my computer with USB debugging it lists it as "ADB interface". I can't get the phone to appear under adb devices while in recovery mode.
USB-Debugging active? (Settings-->Development)
It is when the phone is on, but what I am trying to do is push a file to the phone while its "off" in recovery mode so the usb debugging is irrelevant or so i believe.
Yes, sorry, you are right.
As I can remember, I have had a similar problem a year ago...
Try to copy adb into another directory and use it from there. Sounds stupid, but helped me in the past.
Sent from my Milestone using XDA App
I just tried changing my directory for the sdk but doesn't seem to help. Just to make sure is there anything i need to do once inside the OpenRecovery? After loading up the update.zip i connect it to my PC and in cmd I navigate to the SDK folder. So far thats all I m doing and checking its connected with "adb devices" which always comes up empty. Just want to make sure I m not missing any steps considering I have the usb drivers installed and the sdk SHOULD be installed correctly since i can access them when the phone is on.
danboard said:
I just tried changing my directory for the sdk but doesn't seem to help. Just to make sure is there anything i need to do once inside the OpenRecovery? After loading up the update.zip i connect it to my PC and in cmd I navigate to the SDK folder. So far thats all I m doing and checking its connected with "adb devices" which always comes up empty. Just want to make sure I m not missing any steps considering I have the usb drivers installed and the sdk SHOULD be installed correctly since i can access them when the phone is on.
Click to expand...
Click to collapse
I have the same problem as you described. Is it solved?
I am using windows 7 and the driver is also installed correctly. only problem is the empty device list..
micdim said:
I have the same problem as you described. Is it solved?
I am using windows 7 and the driver is also installed correctly. only problem is the empty device list..
Click to expand...
Click to collapse
Seems OK now. I just reinstalled official SDK.
dl.google.com/android/installer_r08-windows.exe
ROOTING:
Since z4root, one of the easiest ways to root, is not working on Froyo in Galaxy 3, I decided to make this separate thread for instructions on how to root Froyo using Superoneclick.
First and foremost: Enable USB Debugging by going to Settings>Applications>Development. Make sure it is ticked.
Download the attached Superoneclickv1.5.zip file. Extract its contents. Make sure your phone drivers are installed on the computer (Samsung Kies). Then follow the steps:
1. From the extracted contents, run the file named Superoneclick.
2. Turn off your phone, then connect it to the computer using the USB Cable. Don't turn on the phone. Keep it off but connected to the computer.
3. In Superoneclick, click on the 'Root' button. After a few seconds, it'll say 'Waiting for device'.
4. Now turn on your phone (while it is still connected to the computer). Superoneclick will detect the phone.
5. Now the phone will be rooted, while it is starting up. When it is started, it'll be rooted.
6. After rooting, download and install busybox on your phone. It should take care of any slowing down of your phone after rooting.
That's it. The phone is now rooted, although it would be so much better if z4root worked on Froyo..
For those getting stuck at the 'pushing raceagainstthecage' step, try this method. Credits go to haree:
1. login as admin and then open the application. Or right click on Superoneclick.exe and click on 'Run as administrator'.
2. turn off ur Virus protection
3. remove all the additional external USB devices(this seems to confuse the SW)
i removed all the above mentioned
and then follow the instructions u will be successful
it worked for me now i have 2.2 and rooted
Click to expand...
Click to collapse
UNROOTING INSTRUCTIONS:
Unfortunately, the method to unroot by clicking on the Unroot button in Superoneclick does not work. So follow the following steps to unroot.
1. Download rootexplorer.apk (attached) and install Root Explorer on phone.
2. Run Root Explorer. A 'Superuser Request' prompt will come up. Press Allow.
3. Now, on the top, there will be a button saying 'Mount R/W'. Press it. It should change to 'Mount R/O'. The button should say 'Mount R/O' in order for you to be able to do anything in the following steps.
4. Now scroll to the bottom, click on system. Then click on bin.
5. In the bin folder, look for a file named 'su'. Long press on this file, and select Delete to delete it.
6. Now go back to the system folder by pressing the Back button once.
7. Now enter the app folder. Scroll down and look for the file named 'superuser.apk'. Long press on this file and delete it.
8. Exit Root Explorer after this. Uninstall it if you don't want to use it.
9. That's it. Your phone will be un-rooted.
Another method to unroot:
1. Download and install Terminal Emulator (attached).
2. Run Terminal Emulator on the phone. If you don't see a keyboard to type, press Menu and press Toggle Soft Keyboard.
3. Type su and press enter. Press Allow on the 'Superuser Request' prompt. The $ sign will change to a #.
4. Now type the following line exactly as it is and press enter: mount -o rw,remount /dev/block/mtdblock3 /system
5. Nothing will happen visually. The pointer will shift to a new line.
6. Now type the following line and press enter: rm /system/bin/su
7. Again, type following line and press enter: rm /system/app/superuser.apk.
8. Now exit Terminal Emulator. Your phone is un-rooted.
Hehe, first i thought it makes no sense to write a howto on this since its described in the SOC thread anyway, but man the idea to do it during boot is ubercool, didn't think of that...
FadeFx said:
Hehe, first i thought it makes no sense to write a howto on this since its described in the SOC thread anyway, but man the idea to do it during boot is ubercool, didn't think of that...
Click to expand...
Click to collapse
I know it's explained in the SOC thread, but many people keep asking on the "Samsung Galaxy 3 GT-i5800: root, gps fix, upgrading" thread about rooting Froyo, so I thought it's better to have one SOC thread right in the Galaxy 3's Development Section. It'll save everyone reading through a lot of pages on that thread..
addicted2088 said:
I know it's explained in the SOC thread, but many people keep asking on the "Samsung Galaxy 3 GT-i5800: root, gps fix, upgrading" thread about rooting Froyo, so I thought it's better to have one SOC thread right in the Galaxy 3's Development Section. It'll save everyone reading through a lot of pages on that thread..
Click to expand...
Click to collapse
hi
when i see a few reports that this is working for our G3 ill add this link to the roll up thread very nice of you to give this info to all keep up the good work
one question will this also un root the phone
haree said:
hi
when i see a few reports that this is working for our G3 ill add this link to the roll up thread very nice of you to give this info to all keep up the good work
one question will this also un root the phone
Click to expand...
Click to collapse
Can't unroot using the same procedure, but have added another procedure to do it.
This method does work for everyone. The only new step in my procedure is to do it while the phone is booting.
help! !
cant root. stuck at "waiting for device"..... tried everything.. no luck. can anyone help?
coolzarjun said:
cant root. stuck at "waiting for device"..... tried everything.. no luck. can anyone help?
Click to expand...
Click to collapse
Are your phone drivers properly installed? Does your computer make a 'Hardware connected' ding sound when you turn on the phone? If not, then you'll have to install Samsung Kies and then connect the phone to the computer to install the drivers. Try rooting after that.
all drivers are installed.. i reinstalled twice.. when i connect in usb debugg.. says installing some adb stuff after fews secs.. comp says hardware might not work properly not properly installed. all other drivers wrk fine.. wat can i do to install adb drivers properly. . i have windows xp
coolzarjun said:
all drivers are installed.. i reinstalled twice.. when i connect in usb debugg.. says installing some adb stuff after fews secs.. comp says hardware might not work properly not properly installed. all other drivers wrk fine.. wat can i do to install adb drivers properly. . i have windows xp
Click to expand...
Click to collapse
Connect your phone to your computer. Then open the Device Manager. Then look for the entry 'SAMSUNG Android Composite ADB Interface' in the list. It might be under the ADB Interface tab. Right click on the 'SAMSUNG Android Composite ADB Interface' and uninstall it.
Then reconnect your phone to the computer and see if the ADB drivers get installed properly this time.
did that also....uninstalled and connected the phone. still the same error..
hardware not properly installed.. it might not work properly
i got windows xp 32-bit
can u help ?? plz !
coolzarjun said:
did that also....uninstalled and connected the phone. still the same error..
hardware not properly installed.. it might not work properly
i got windows xp 32-bit
can u help ?? plz !
Click to expand...
Click to collapse
Sorry, I'm using Windows 7, so I've no idea what to do about the drivers in Windows XP. Try updating Kies..
i also have win 7 and it doesnt work...help??
reist said:
i also have win 7 and it doesnt work...help??
Click to expand...
Click to collapse
I can't help if the drivers on your computer are not installed properly. After connecting the phone while it is ON, open the Device Manager and see if the ADB driver is properly installed.
If the drivers are properly installed, this method will work..
Edit: As mentioned by mhndk14 below, enable USB Debugging in Settings>Applications>Development.
I also had the same problem with windows 7. Just make sure that the USB Debugging is enabled and then try again. It worked for me.
how to bring the phone back to factory settings
hi how can i get back my phone to the original factory settings? i rooted using z4mod and when unrooted the live wallpapers wont go... and how do i get my boot menu when restarted on my 1 5801??
nageshkaja said:
hi how can i get back my phone to the original factory settings? i rooted using z4mod and when unrooted the live wallpapers wont go... and how do i get my boot menu when restarted on my 1 5801??
Click to expand...
Click to collapse
To remove the Live Wallpapers, you'll have to root your phone, and then use Root Explorer to remove the files Livewallpaperspicker.apk from system/app, and libRS.so and librs_jni.so from system/bin. Then un-root your phone. Be sure to press the 'Mount R/W' button in Root Explorer to be able to delete the files.
As for restoring your boot menu, that procedure is there somewhere in the Development section. The boot menu changes because of upgrading, not rooting.
It seems i have lost haptic feedback after rooting(jpb), anybody else experience this?
Edit: lol
It was probably sue to the "forced" reboot, but I accidently dropped my phone (batteries feel out) and now it's working
stubborn_d0nkey said:
It seems i have lost haptic feedback after rooting(jpb), anybody else experience this?
Edit: lol
It was probably sue to the "forced" reboot, but I accidently dropped my phone (batteries feel out) and now it's working
Click to expand...
Click to collapse
Yeah, haptic feedback stops working sometimes on JPA and JPB after rooting. But restarting the phone corrects it. (Although your method of restarting the phone was too brutal!! )
Thanks addicted2088...worked perfectly...
successfully rooted..........
now i need to know how to install live wallpapers......
thanks
First off, Mark great program. I'e searched the tread and didn't find this question.
I have a Verizon S3 I535 4.1.1 and want to retrieve my pictures and data from the phone. Currently the screen broke so I can't unlock the phone password nor can I put the phone in USB debugging mode. Is there a way I can use this app to retrieve my data?
Thanks
Bump...Anyone?
AltecBX said:
Bump...Anyone?
Click to expand...
Click to collapse
Can't you just plug it into your USB port? I don't have mine in USB debug mode and I can just open an explorer window and navigate to the device.
Just_AGuy said:
Can't you just plug it into your USB port? I don't have mine in USB debug mode and I can just open an explorer window and navigate to the device.
Click to expand...
Click to collapse
I do have it plugged in to the USB port, I just can't access any files but the pre-loaded drivers that on it. I need to first unlock my phone to see the files in it.
I'm just trying to get important pictures off the phone.
Can someone help me out. These are my new born pics from the hospital.
Couldn't you grab the SDK tools, then use the command:
ADB pull \sdcard\DCIM
(or wherever your pictures are located, for me it's \0\SDcard\DCIM because I'm on 4.2)
Sent from my Nexus 4 using xda premium
every gavenel
I don't know how to do that. This is a screen shot I get when I open Samsung GS3 Toolkit.
Also is another screenshot of what happens when I plug the phone to the computer
AltecBX said:
First off, Mark great program. I'e searched the tread and didn't find this question.
I have a Verizon S3 I535 4.1.1 and want to retrieve my pictures and data from the phone. Currently the screen broke so I can't unlock the phone password nor can I put the phone in USB debugging mode. Is there a way I can use this app to retrieve my data?
Thanks
Click to expand...
Click to collapse
open back cover, take out sd card, plug in sd card reader, profit. its in dcim
dragon1357 said:
open back cover, take out sd card, plug in sd card reader, profit. its in dcim
Click to expand...
Click to collapse
it doesn't have a SD card. The baby pictures are in the internal memory.
bump!!
Can Anyone please help me out with this...
AltecBX said:
Can Anyone please help me out with this...
Click to expand...
Click to collapse
Dude. Learn how to use adb. Problem solved. You're not going to get a simpler or easier answer than that.
Sent from my SCH-I535 using xda app-developers app
Did you try to reinstall the USB drives?
I had an issue recently that when I plugged my S3 into my computer noting came up. Reinstalling the drives fixed it for me.
If you haven't already tried, you could installing Kies. You can get to your phones from that.
---------- Post added at 10:15 AM ---------- Previous post was at 10:01 AM ----------
thebeastglasser said:
Couldn't you grab the SDK tools, then use the command:
ADB pull \sdcard\DCIM
(or wherever your pictures are located, for me it's \0\SDcard\DCIM because I'm on 4.2)
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
^^^ This
You only need to know a few linux commands id you don't know where your files are located.
adb help will give you a list of commands.
to test if your are able to connect, type adb devices
it will return you phone device number if attached properly.
Use adb shell
This will open a shell so you can cd to directories to find that files and path you need.
Then use as stated above adb pull <location> <remote>
Guys, I don't have my phone is USB debug mode. My phone was locked when the screen cracked. I've installed Samsung Kies for the Samsung drivers, I installed the Samsung drivers from their website, I've also installed the drivers from the phone when plugged in through USB, which is the only thing I see.
-Ajrty33 - I've tried using ADB, but it doesn't recognize a phone connected in the computer. Keeps coming up with nothing found. My understanding is that you need USB Debugging enabled to have it detect the phone, no?
-Just_AGuy - I've tried using the ADB Linux commands to detect the phone. it comes up with nothing. What else can I try?
--Thanks for the help people...I'm really appreciating it
AltecBX said:
-Just_AGuy - I've tried using the ADB Linux commands to detect the phone. it comes up with nothing. What else can I try?
Click to expand...
Click to collapse
When you type adb devices, does it just come back with "List of devices attached" then nothing under that?
If it doesn't list any devices, you have bigger problems.
Have you tried different USB port too? I've seen issues with USB3 port not working with odin and the Motorola equivalent RSD lite.
It still could be drivers. I had issue with mine a while ago. I tried reinstalling them and it appeared to install but didn't properly. I had to reboot the computer a couple times and reboot the phone.
As a last resort you might bring it to Verizon and see if they can get the files off for you.
It comes up with no device found. I tried another USB port and nothing. I've tried connecting my wife's phone and it works on all USB ports.
It did install new drivers when I connected her phone and it's the same model.
That's too bad. It sounds like you have hardware issues. Take it to the techs at the Verizon store, I don't think even they can screw it up more.
I just tried installing Kies on my work computer. After doing so, the computer didn't recognize my phone. I rebooted both the computer and the phone. The computer still didn't see the phone.
I shut off the phone and did a battery pull. Then restarted the phone and plugged in the USB cable. The computer recognized the phone and reinstalled the drivers.
Try it.
Just_AGuy said:
I just tried installing Kies on my work computer. After doing so, the computer didn't recognize my phone. I rebooted both the computer and the phone. The computer still didn't see the phone.
I shut off the phone and did a battery pull. Then restarted the phone and plugged in the USB cable. The computer recognized the phone and reinstalled the drivers.
Try it.
Click to expand...
Click to collapse
I tried that. I then installed in other computer running Windows 7 64bit, same issue.
A few days ago I've tried using ADB but it said my device is offline. Earlier I tried ADB over network. Again, it said my phone is offline. So I wanted to see if I can get ADB access from the bootloader. Surprize: I can't get into the bootloader. If I turn my phone off and press Volume Down + Power, it just boots.
Now, my phone is working good, I just wanted adb access to do that darn EFS backup. And what's up with that "can't get into bootloader" stuff? I did it fine and dandy when I rooted my phone..
EDIT: well, since I can not do the backup the normal way, I just downloaded the efs folder as a zip. and dev/block/. Is it as effective as the normal way?
andrei1015 said:
A few days ago I've tried using ADB but it said my device is offline. Earlier I tried ADB over network. Again, it said my phone is offline. So I wanted to see if I can get ADB access from the bootloader. Surprize: I can't get into the bootloader. If I turn my phone off and press Volume Down + Power, it just boots.
Now, my phone is working good, I just wanted adb access to do that darn EFS backup. And what's up with that "can't get into bootloader" stuff? I did it fine and dandy when I rooted my phone..
EDIT: well, since I can not do the backup the normal way, I just downloaded the efs folder as a zip. and dev/block/. Is it as effective as the normal way?
Click to expand...
Click to collapse
It is Vol-Up + Power for bootloader. And you can't have adb access in bootloader mode. Only fastboot access.
Ok but why isn't adb working? Why does it always say it's offline?
Sent from my Google Nexus S
andrei1015 said:
Ok but why isn't adb working? Why does it always say it's offline?
Sent from my Google Nexus S
Click to expand...
Click to collapse
It could be that you installed some software/driver that overrides a working USB driver.
Try install Google USB driver from Android SDK Tools.
Install Android SDK Tools
When SDK Manager runs, select Google USB Driver, see attached pic
If missed, run SDK Manager again as Administrator
Also, make sure you turn on Developer options and "check" Andoid (USB) debugging option in Developer options setup.
_android_ said:
It could be that you installed some software/driver that overrides a working USB driver.
Try install Google USB driver from Android SDK Tools.
Install Android SDK Tools
When SDK Manager runs, select Google USB Driver, see attached pic
If missed, run SDK Manager again as Administrator
Also, make sure you turn on Developer options and "check" Andoid (USB) debugging option in Developer options setup.
Click to expand...
Click to collapse
Yup, I have all of the above.. Still offline >.<
andrei1015 said:
Yup, I have all of the above.. Still offline >.<
Click to expand...
Click to collapse
Do you have the Samsung Galaxy Nexus ADB interface showing in your device manager?
Try uninstall and reload again.
Almost = https://dl.dropbox.com/1/view/xiulpm329s4wxcd/Apps/CloudShot/shot_25022013_192328.png
Still it says offline.
(thank you for trying to help me )
In fastboot mode it looks like this:
just tested at work and it says "device" instead of "offline" which is good I think. The only difference is that at work I installed the SDK long after I got it at home and it has a slightly different folder structure and it also comes with eclipse.
Resolved. Downloaded the new SDK with ADT from the android site and it works. Please forgive me for posting so many times. Can someone please delete this thread?
andrei1015 said:
Resolved. Downloaded the new SDK with ADT from the android site and it works. Please forgive me for posting so many times. Can someone please delete this thread?
Click to expand...
Click to collapse
Good for you.
Anyway, if you followed post #4 and installed the new SDK Tools, would have saved you a lot of time.
***ONLY FOR RELAYS RUNNING ICS 4.0.4***
Samsung had just released the official Jelly Bean 4.1 update for this phone on April 22 or so and this root method only works for Ice Cream Sandwich devices.
I know there's already a thread of how to root the ICS Samsung Galaxy S Relay 4G which is right here: http://forum.xda-developers.com/showthread.php?p=34515281 but I thought that it may be hard for some people to do it without a visual tutorial. Here's my helpful tutorial video of how to root the Samsung Galaxy S Relay 4G: https://plus.google.com/u/0/108388305247615258469/videos <-- You can easily find the video because it's the only video on that album.
Files Needed:
Winrar: http://www.win-rar.com/download.html?&L=0
Odin v3.07: http://www.4shared.com/zip/CGo6TP1O/Odin307.html? or for the latest and updated versions: http://forum.xda-developers.com/showthread.php?t=1738841
Rooted System IMG: http://www.4shared.com/rar/nhGK59WR/SGHT699_rootedtar.html?
CWM File: http://www.4shared.com/zip/wLHTlktW/cwmtar.html?
If none of the links above work, message me at [email protected] or reply to this topic and I will reupload the files.
Steps:
1) On your phone, go to Settings-->Developer Options and turn on USB Debugging.
2) Turn off your phone and put it in Download Mode/Odin mode.
3) Download the odin307, sght699_rooted.tar, and that cwm.tar files from the links given above.
4) Extract all the files with WinRAR or other file extracting programs.
5) Open Odin v3.07
6) Make sure that it says "Added!" on the bottom left box. If it doesn't say Added, unplug and plug your phone from the computer.
7) Deselect/Uncheck "Auto Reboot" and "F. Reset Time"
8) Click on Phone and a pop up should come up.
9) Find the SGHT699_rooted folder that you extracted in Step 4 and open the file inside it.
10) Click Start. This will take a while but it should not take more than 14 minutes.
11) Once it's done, click Reset.
12) Unplug and plug your phone again. It should say "Removed!" when unplugged and "Added!" when plugged on the bottom left box.
13) Deselect/Uncheck "F. Reset Time" but this time, keep the "Auto Reboot" marked/checked.
14) Click on PDA and a popup should come up.
15) Find the cwm folder that you extracted in Step 4 and open the cwm.tar.md5 file.
16) Click Start.
Once it finishes, your phone should reboot and be rooted. To check if it is actually rooted, go on Applications and find Superuser. If it is there, then you are rooted. Enjoy!!
Very nice. You are missing information, need to add the original posts/threads for the files that you mirrored so we can get version numbers and dates associated with the downloads. Feel free to edit the wiki in my sig if you want to help!
Ok. Thanks, but there's a problem. The files I mirrored other than Odin v3.07 are gone. The original link where the original tutorial was is gone. I had the link in my bookmarks but when I click on it, the webpage is unavailable. Ive tried viewing it from other computers and devices and it still wont work. So I decided to make a new one. Thanks again! The links should be updated in a few.
Sent from my SGH-T699 using xda app-developers app
Thanks.
Version is UVAMA2?
Sent from my SGH-T699 using xda premium
XIAOSpider said:
Thanks.
Version is UVAMA2?
Sent from my SGH-T699 using xda premium
Click to expand...
Click to collapse
What's UVAMA2?
USB won't connect properly; want to un-root
You're rooting video was very helpful.
However, now that the phone is rooted, when I try to connect to my computer with USB cable, I get error message to the effect that the computer can't recognize the hardware ID of the device, so can't back-up the files on the phone or the SD card. I have all the latest Samsung USB drivers, and the computer recognizes that a Samsung device is connected, but the USB connection fails anyway.
How do I un-root the phone - do I have to boot up in download mode and use ODIN? Will this wipe my data, or just go back to the unrooted ROM and keep my data intact?
-----------
Chrizuki said:
I know there's already a thread of how to root the Samsung Galaxy S Relay 4G which is right here: http://forum.xda-developers.com/showthread.php?p=34515281 but I thought that it may be hard for some people to do it without a visual tutorial. Here's my helpful tutorial video of how to root the Samsung Galaxy S Relay 4G: http://www.youtube.com/watch?v=GKgemJTeRWo
Files Needed:
Winrar: http://www.win-rar.com/download.html?&L=0
Odin v3.07: http://www.4shared.com/zip/CGo6TP1O/Odin307.html? or for the latest and updated versions: http://forum.xda-developers.com/showthread.php?t=1738841
Rooted System IMG: http://www.4shared.com/rar/nhGK59WR/SGHT699_rootedtar.html?
CWM File: http://www.4shared.com/zip/wLHTlktW/cwmtar.html?
If none of the links above work, message me at [email protected] or reply to this topic and I will reupload the files.
Steps:
1) On your phone, go to Settings-->Developer Options and turn on USB Debugging.
2) Turn off your phone and put it in Download Mode/Odin mode.
3) Download the odin307, sght699_rooted.tar, and that cwm.tar files from the links given above.
4) Extract all the files with WinRAR or other file extracting programs.
5) Open Odin v3.07
6) Make sure that it says "Added!" on the bottom left box. If it doesn't say Added, unplug and plug your phone from the computer.
7) Deselect/Uncheck "Auto Reboot" and "F. Reset Time"
8) Click on Phone and a pop up should come up.
9) Find the SGHT699_rooted folder that you extracted in Step 4 and open the file inside it.
10) Click Start. This will take a while but it should not take more than 14 minutes.
11) Once it's done, click Reset.
12) Unplug and plug your phone again. It should say "Removed!" when unplugged and "Added!" when plugged on the bottom left box.
13) Deselect/Uncheck "F. Reset Time" but this time, keep the "Auto Reboot" marked/checked.
14) Click on PDA and a popup should come up.
15) Find the cwm folder that you extracted in Step 4 and open the cwm.tar.md5 file.
16) Click Start.
Once it finishes, your phone should reboot and be rooted. To check if it is actually rooted, go on Applications and find Superuser. If it is there, then you are rooted. Enjoy!!
Click to expand...
Click to collapse
nosch454 said:
You're rooting video was very helpful.
However, now that the phone is rooted, when I try to connect to my computer with USB cable, I get error message to the effect that the computer can't recognize the hardware ID of the device, so can't back-up the files on the phone or the SD card. I have all the latest Samsung USB drivers, and the computer recognizes that a Samsung device is connected, but the USB connection fails anyway.
How do I un-root the phone - do I have to boot up in download mode and use ODIN? Will this wipe my data, or just go back to the unrooted ROM and keep my data intact?
-----------
Click to expand...
Click to collapse
Oops, sorry. Forgot the part of your reply that said you've installed all the drivers. What do you mean by it can't recognize it? Does the SGH-T699 still show up on your My Computer?
If you want to unroot, go here: http://forum.xda-developers.com/showthread.php?t=2166242
Just follow the steps and no, it won't wipe out all your data (Well, it didn't wipe mine, but I'm sure it won't.)
Sent from my SGH-T699 using xda app-developers app
Problems connecting with USB (MTP driver install failure)
Chrizuki said:
Oops, sorry. Forgot the part of your reply that said you've installed all the drivers. What do you mean by it can't recognize it? Does the SGH-T699 still show up on your My Computer?
If you want to unroot, go here: http://forum.xda-developers.com/showthread.php?t=2166242
Just follow the steps and no, it won't wipe out all your data (Well, it didn't wipe mine, but I'm sure it won't.)
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse
When I connect the USB cable, Windows has a popup message that says:
" Hardware ID missing
Windows cannot identify the device plugged into the Samsung Mobile USB Composite Device.
For assistance, contact the hardware manufacturer"
Sometimes it tries - and fails - to install the MTP device driver.
However, when I go into Windows Device Manage, it does list SAMSUNG Android Phone | SAMSUNG Android ADB Interface, and when trying to update its drivers, it says I have the most up to date ones installed.
- What does "Hardware ID missing" mean? How do I get the phone to communicate with the computer using USB?
I thought it might have to do with Android Ice Cream Sandwich and the media device (MTP) protocol for USB, but, I had no problems getting the computer to recognize my son's (unrooted) Galaxy S 3, which also has ICS and is pretty similar to the Galaxy S Relay 4G. That's why I suspect the problem is with my rooted version.
Is there anything else I should try before un-rooting the phone?
nosch454 said:
When I connect the USB cable, Windows has a popup message that says:
" Hardware ID missing
Windows cannot identify the device plugged into the Samsung Mobile USB Composite Device.
For assistance, contact the hardware manufacturer"
Sometimes it tries - and fails - to install the MTP device driver.
However, when I go into Windows Device Manage, it does list SAMSUNG Android Phone | SAMSUNG Android ADB Interface, and when trying to update its drivers, it says I have the most up to date ones installed.
- What does "Hardware ID missing" mean? How do I get the phone to communicate with the computer using USB?
I thought it might have to do with Android Ice Cream Sandwich and the media device (MTP) protocol for USB, but, I had no problems getting the computer to recognize my son's (unrooted) Galaxy S 3, which also has ICS and is pretty similar to the Galaxy S Relay 4G. That's why I suspect the problem is with my rooted version.
Is there anything else I should try before un-rooting the phone?
Click to expand...
Click to collapse
Install kies or the USB driver directly from samsung.com. Try the USB driver first, then kies if it doesn't work.
Nocturin said:
Install kies or the USB driver directly from samsung.com. Try the USB driver first, then kies if it doesn't work.
Click to expand...
Click to collapse
Already tried both. USB driver is OK, the problem is with MTP. Kies only works via WiFi; does not recognize device with USB. I also tried Samsung tech support's suggestions, none of which changed the situation
nosch454 said:
Already tried both. USB driver is OK, the problem is with MTP. Kies only works via WiFi; does not recognize device with USB. I also tried Samsung tech support's suggestions, none of which changed the situation
Click to expand...
Click to collapse
Have you tried downloading the SDK Manager from "http://developer.android.com/sdk/index.html"? Open the big file that you just downloaded and open up SDK Manager. Install the Google USB Driver and as well as the Android SDK Tools and Android SDK Platform-tools. Once downloaded, go back to the android-sdk-windows folder and go to the "platform-tools" folder inside and hold Shift and right click on "adb" and select "Open Command Window Here" of something like that. The command prompt will open. Type in "adb devices" and tell me what comes up. If you see your device(It should be a bunch on numbers and letters) on there, it means it is recognizable. This might not solve your problem as I do not know what "Hardware ID missing" exactly is. But I will do some research.
I did as you suggested, and was able to see my phone when I ran "adb devices" from the command prompt. And, Windows, recognizes it too, because when I click on the button to remove attached USB devices, it lists SAMSUNG_Android_SGH-T699. But, I still get the hardware ID missing message whenever I connect the USB cable. Frustrating! But, thanks for trying to help me - you seem very knowledgeable.
What you can try and do to fix the USB hardware error is go to control panel then go to "uninstall a program" and uninstall the samsung driver once you uninstalled it reconnect your phone and let it reinstal the files and i believe it should fix your problem
Samsung Noob here with a question.
Ok, I know this is gonna sound kinda noobish, but I come from HTC phones, and this is my first Samsung. Do I need to flash ClockworkMod Recovery on this, or do I flash a rom to the 4G Relay using Odin? If I use Odin, can someone give a quick overview on how?
Gh0sTly said:
Ok, I know this is gonna sound kinda noobish, but I come from HTC phones, and this is my first Samsung. Do I need to flash ClockworkMod Recovery on this, or do I flash a rom to the 4G Relay using Odin? If I use Odin, can someone give a quick overview on how?
Click to expand...
Click to collapse
you'll need to install a recovery as you did on HTC as ROMs usually come as recovery-flashable zips.
there's a cwm recovery available here which can flashed using Odin. If you don't like the cwm on the relay you can flash TWRP from cwm over it. TWRP comes with more options and the touchscreen-control you might be used to.
from (any) recovery you can just install update zip-files just as you used to on your HTC.
I had used the "howto root the Galaxy S Relay" thread, and then realized, I should just SU and reboot recovery. :victory:
nosch454 said:
I did as you suggested, and was able to see my phone when I ran "adb devices" from the command prompt. And, Windows, recognizes it too, because when I click on the button to remove attached USB devices, it lists SAMSUNG_Android_SGH-T699. But, I still get the hardware ID missing message whenever I connect the USB cable. Frustrating! But, thanks for trying to help me - you seem very knowledgeable.
Click to expand...
Click to collapse
If anybody else got this error do the following:
- uninstall all samsung drivers / software
- connect your phone to the pc
- the driver installation should 'fail', but you can access the storage
- install the samsung drivers now while phone is plugged in
After the installation the phone will be recognized and everything is fine - this worked twice for me now, so I guess it should do it.