Related
I've been reading here at XDA, I can find the instructions - no problem.
However, in the WIKI there are a few things I don't understand.
The problem also is that all the posts assume you know what's going on and they start in the middle of a thread.
Then there's advice to use Odin, not to use Odin, use this, don't use this.
Some say unmount the SD card, some make no mention of SD card.
Then there's different backups. I've seen Titanium mentioned.
There's advice to get the latest drivers from Samsung - The phone isn't even in the dropdown list of phones, and the letters for the model don't match.
There's the custom ROM advice. Since there aren't many for this phone as yet - and all you want to do is remove crap, what do you look for?
I have to get rid of that stupid Doubletwist and airsync before I toss the phone!
Z
It is rather confusing isn't it...
In a simple answer....
Find the SuperOneClick zip file in one of those threads in the Dev forum & root the phone.Then go get TitaniumBackup ( Pro Recommended ) & you can remove the bloatware. I'd recommend the Pro Version so you can freez the apps you don't delete.
That's what i did on my SGS4G ( and i am not a experianced modder myself )
One problem. I downloaded superoneclick and NET can't find the runtime file.
I'm using XP and ver 4 of NET. I turned off NOD32 and Online Armor.
Z
zuben el genubi said:
One problem. I downloaded superoneclick and NET can't find the runtime file.
I'm using XP and ver 4 of NET. I turned off NOD32 and Online Armor.
Z
Click to expand...
Click to collapse
Uninstalled NET 4 and put in 3. I can open the file, but NOD32 keeps quarantining RAGE. Says it's a trojan.
I don't really want a custom ROM - but would like some more information on Titanium Backup. The Market won't download to the phone, but going to the market on the phone will let me download.
Thanks,
Zuben
Moved as not android development
zuben el genubi said:
Uninstalled NET 4 and put in 3. I can open the file, but NOD32 keeps quarantining RAGE. Says it's a trojan.
I don't really want a custom ROM - but would like some more information on Titanium Backup. The Market won't download to the phone, but going to the market on the phone will let me download.
Thanks,
Zuben
Click to expand...
Click to collapse
Let it scrub the RAGE file, you need the other one actually to make it work
Which one? PSneuter?
Also some confusion about the Samsung driver. I also have a Galaxy 3. I downloaded Kies and the driver. I downloaded the new driver (did not install it)and stuck it in a folder named Samsung on the Desktop. Kies is in the Samsung folder in programs and I assume that the original driver is in there, too. The driver is listed in Add/Remove programs.
I can either delete Kies or rename that file to something else, and stop Kies from running. So there's 2 drivers, and I suspect they are the same.
Since I can't send a download from the Market on the PC to the phone, I have to download from Market on the phone. I can't install Titanium unless I root, but can I get to Titanium from the phone if I do root?
Thanks
Z
I use linux... so i have no idea what Kies is or does..
zuben el genubi said:
Which one? PSneuter?
Also some confusion about the Samsung driver. I also have a Galaxy 3. I downloaded Kies and the driver. I downloaded the new driver (did not install it)and stuck it in a folder named Samsung on the Desktop. Kies is in the Samsung folder in programs and I assume that the original driver is in there, too. The driver is listed in Add/Remove programs.
I can either delete Kies or rename that file to something else, and stop Kies from running. So there's 2 drivers, and I suspect they are the same.
Since I can't send a download from the Market on the PC to the phone, I have to download from Market on the phone. I can't install Titanium unless I root, but can I get to Titanium from the phone if I do root?
Thanks
Z
Click to expand...
Click to collapse
So which phone are you trying to Root? Samsung Galaxy 3 or Samsung Galaxy S 4G? If your rooting the S 4G you can find the drivers here http://downloadcenter.samsung.com/c...728034640796/SGH-t959_Vibrant_USB_Drivers.zip
I have no experience with rooting with XP but I assume it would be essentially the same steps.
If your looking to do stuff on your Galaxy 3 then please go to this forum
http://forum.xda-developers.com/forumdisplay.php?f=868
and do your research over there.
It’s not that difficult to root the SGS 4G Phone. The first thing you need to do is make sure your phone is communicating with your computer. Install the Samsung USB drivers.(make sure you have the right drivers for your O.S. either 32bit or 64bit) In your phone go into Settings/Applications/Development and make sure you check “USB debugging”. Connect your Tethering cable to your phone. On your home screen you should see “USB Connected” popup on top of your screen. You should be able to press USB connected button from the drop-down menu on the home screen and see the external SD card on the computer now. If that works then Turn off USB storage. (leave “USB debugging” checked) Open NOD32 application from your system tray. Go to Settings and select “Temporarily disable antivirus,” put your password in if prompted. Then Download SuperOneClickv1.7-ShortFuse, expand the file and go to SuperOneClickv1.7-ShortFuse Directory. Run the SuperOneClick App. When it opens don’t change anything and just click “Root” and let it run. It should say rooted when done. Then go to the Market on your phone and get Titanium Backup and install it. It will ask for SuperUser permission and accept that on your phone. If that fails press “Problems” button, Then “Get Busybox”. Install the new Busybox. You may have to close and reopen Titanium Backup again. I would say to download and install ClockworkMod after rooting and before getting Titanium Backup, Except ClockworkMod currently does not work for the SGS 4G Yet. So, skip that step for now. You should be able to backup your phone after this.
nwpro3 said:
It’s not that difficult to root the SGS 4G Phone. The first thing you need to do is make sure your phone is communicating with your computer. Install the Samsung USB drivers.(make sure you have the right drivers for your O.S. either 32bit or 64bit) In your phone go into Settings/Applications/Development and make sure you check “USB debugging”. Connect your Tethering cable to your phone. On your home screen you should see “USB Connected” popup on top of your screen. You should be able to press USB connected button from the drop-down menu on the home screen and see the external SD card on the computer now. If that works then Turn off USB storage. (leave “USB debugging” checked) Open NOD32 application from your system tray. Go to Settings and select “Temporarily disable antivirus,” put your password in if prompted. Then Download SuperOneClickv1.7-ShortFuse, expand the file and go to SuperOneClickv1.7-ShortFuse Directory. Run the SuperOneClick App. When it opens don’t change anything and just click “Root” and let it run. It should say rooted when done. Then go to the Market on your phone and get Titanium Backup and install it. It will ask for SuperUser permission and accept that on your phone. If that fails press “Problems” button, Then “Get Busybox”. Install the new Busybox. You may have to close and reopen Titanium Backup again. I would say to download and install ClockworkMod after rooting and before getting Titanium Backup, Except ClockworkMod currently does not work for the SGS 4G Yet. So, skip that step for now. You should be able to backup your phone after this.
Click to expand...
Click to collapse
This is good information, but what about for Mac users? I was previously able to root my Samsung Vibrant just by installing the update.zip file via CWM. Should Mac users wait for this course or can we make it happen now?
Also, what's the benefit of rooting right now? Just to remove bloatware? There's no custom roms yet, right?
Look at the Unix instructions about associating the USB ID with the Mac. I haven't tried it, but I suspect that is the missing step.
Update: Nope -- According to Google, http://developer.android.com/guide/developing/device.html#setting-up
Setup your system to detect your device.
* If you're developing on Windows, you need to install a USB driver for adb. If you're using an Android Developer Phone (ADP), Nexus One, or Nexus S, see the Google Windows USB Driver. Otherwise, you can find a link to the appropriate OEM driver in the OEM USB Drivers document.
* If you're developing on Mac OS X, it just works. Skip this step.
* If you're developing on Ubuntu Linux, you need to add a rules file...
(Emphasis mine)
Sent from my SGH-T959V using XDA App
I'm wanting to root the 4G. The Galaxy3 was bought unlocked so it doesn't have the crap on it. Like I said, the ROM seems to be ok, it's just the stupid bloatware.
Chamgea said:
This is good information, but what about for Mac users? I was previously able to root my Samsung Vibrant just by installing the update.zip file via CWM. Should Mac users wait for this course or can we make it happen now?
Also, what's the benefit of rooting right now? Just to remove bloatware? There's no custom roms yet, right?
Click to expand...
Click to collapse
Macs are out of my Knowledge base. I've taught PC repair at LAUSD in Ca, but haven't studied the Mac thing. It's something I want to learn, just have not got around to it yet.
I have recreated this method based on this post to make it much easier for everyone to get this setup on their devices with complete details.
Confirmed Working With
1. Windows 7
2. Mac OS X 10.6 (Snow Leopard)
3. Mac OS X 10.7 (Lion)
4. Other OS versions possible just not yet confirmed/tested (only thing stopping is driver support)
How to Enable UMS Mode on your Verizon Galaxy S III
1. Make sure you are currently rooted ***VERY IMPORTANT***
2. Download and install the Samsung Official Verizon Galaxy S III USB Drivers - Link Here
3. Download and install GScript Lite from the Play Store onto your device - Link Here
4. Download the Verizon Galaxy S III UMS-MTP Switcher Scripts to your computer - Link Here (or attachment at bottom of OP)
5. Create a folder called "gscript" on the root of your internal storage (/sdcard partition)
6. Extract the two scripts from the zip file (from step #4) into that folder on your device - Screenshot Here
7. Open GScript Lite on your device
8. Press the Menu key on your device and select "Add script"
9. Press the "Load file" button and select "UMS Mode.sh", then press the "Save" button and the UMS Mode script will be added to the list
10. Press the Menu key on your device and select "Add script" again
11. Press the "Load file" button and select "MTP Mode.sh", then press the "Save" button and the MTP Mode script will be added to the list
12. Select the "UMS Mode" script from the list and allow Superuser for root access
13. The script will now run and do not worry if GScript Lite force closes at the end as this is perfectly normal
14. On your Windows 7 computer you will see it will try to install "SAMSUNG Mobile MTP Device" as one of the drivers and fail *this is normal*
15. Go into Device Manager on your computer, right click "SAMSUNG Mobile MTP Device" and select "Properties"
16. Click on the "Driver" tab and click the "Update Driver" button, a prompt will then come up
17. Select "Browse my computer for driver software", then select "Let me pick from a list of device drivers on my computer" on the next screen
18. Select "USB Mass Storage Device" as the new driver from that list and finish up that install
19. At the end you will see something like this on your computer - Screenshot Here
20. Windows will install final drivers automatically and a new "Disk drive" will show up on your computer, this is your external SD card on your device
21. If you want to return to MTP Mode, just select "MTP Mode" script from GScript Lite on your device and after it force closes you will be back to normal
Click to expand...
Click to collapse
Benefits of UMS Mode
USB Mass Storage (UMS) Mode used the old way of managing USB storage (like Galaxy S II and so on) before that changed to Media Transfer Protocol (MTP) Mode (aka. Device mode) with the Samsung Galaxy Nexus. The benefit of UMS Mode is that it will work with special devices that try to read your phone like a car radio head unit will now be able to read the songs, pictures, videos, etc through the USB port properly, as well as your TV (if it has USB support of course), among many other devices. Also it's a much more reliable method of transferring files on your computer since it's basically direct access to the SD Card as opposed working through a special protocol with MTP or PTP Mode. This mod will enable your SD Card to show up as a regular disk drive instead of a device on whatever you plug into with a USB port. Hope that helps explain it a bit without being too technical. For details on why Google decided to switch to MTP Mode see this article.
Click to expand...
Click to collapse
Awesome, sweet write up. :good:
I may have to try this. The MTP doesn't work on my Mac for some reason. Android file transfer just crashes whenever I try it.
Do you have to enable the script at boot?
Explanation in OP very summary.
Plug the phone where? In the computer or the AC adapter?
If in the computer then why is necessary that to run the script.
If you don't use the GScript Lite then what do you use to run the scripts (Terminal?).
If you copy the script to the phone then the files should have which extension? I mention that because there is nothing attached.
Do not forget that you're dealing here with a lot of noobs.
Please be so kind and review the OP.
If the script works correct then this is a big deal and I congratulate you but do it like a pro.
Cheers.
jb_alphamale said:
Do you have to enable the script at boot?
Explanation in OP very summary.
Plug the phone where? In the computer or the AC adapter?
If in the computer then why is necessary that to run the script.
If you don't use the GScript Lite then what do you use to run the scripts (Terminal?).
If you copy the script to the phone then the files should have which extension? I mention that because there is nothing attached.
Do not forget that you're dealing here with a lot of noobs.
Please be so kind and review the OP.
If the script works correct then this is a big deal and I congratulate you but do it like a pro.
Cheers.
Click to expand...
Click to collapse
OP only copied and pasted someone else's thread/work.
http://forum.xda-developers.com/showthread.php?p=28670285#post28670285
Yeah I figured that out.
Now we have the link.
Thanks Beknatok.
Edit: Well it does not work on Verizon SIII.
jb_alphamale said:
Yeah I figured that out.
Now we have the link.
Thanks Beknatok.
Edit: Well it does not work on Verizon SIII.
Click to expand...
Click to collapse
Well lets try and get it to work. Some dev must want this too.:fingers-crossed:
jb_alphamale said:
Yeah I figured that out.
Now we have the link.
Thanks Beknatok.
Edit: Well it does not work on Verizon SIII.
Click to expand...
Click to collapse
I just tried it and it works perfectly.
This part is very important:
If Windows fails to find the correct driver, go to the Device Manager and manually set it to use the driver, "USB Mass Storage Device". It seemed to try to stick with the MTP driver in my case.
Click to expand...
Click to collapse
OK here is what I did.
Installed Script Manager free from the market.
Copied both scripts into sdcard\scripts folder.scripts folder created by myslef.
Opened the mass storages.sh script and run it.
I've got bunch of error messages that it cannot find this and that.
The phone was connected to the computer.
If necessary I can screenshot the errors.
open1your1eyes0 said:
I just tried it and it works perfectly.
This part is very important:
Click to expand...
Click to collapse
jb_alphamale said:
OK here is what I did.
Installed Script Manager free from the market.
Copied both scripts into sdcard\scripts folder.scripts folder created by myslef.
Opened the mass storages.sh script and run it.
I've got bunch of error messages that it cannot find this and that.
The phone was connected to the computer.
If necessary I can screenshot the errors.
Click to expand...
Click to collapse
Don't use those scripts, I have issues with them as well. Just copy/paste the OP text into your own script using GScript Lite.
OK let's try. I'll report back.
Edit: OK I did what you proposed. Created the script in GSript Lite and saved then ran. Nothing happens. After I run it GScript FCs. I'm giving up.
This is so simple that I don't think that I'm messing up something.
open1your1eyes0 said:
Don't use those scripts, I have issues with them as well. Just copy/paste the OP text into your own script using GScript Lite.
Click to expand...
Click to collapse
jb_alphamale said:
OK let's try. I'll report back.
Edit: OK I did what you proposed. Created the script in GSript Lite and saved then ran. Nothing happens. After I run it GScript FCs. I'm giving up.
This is so simple that I don't think that I'm messing up something.
Click to expand...
Click to collapse
GScript does have force close issues but don't worry, it still runs as long as you don't see any errors when it's done.
I have just extracted the working GScripts I created and added them to OP for anyone who wants to import them into their GScript Lite. Just create a folder called "gscript" on your internal memory "/sdcard" partition and put those two .sh files into that folder. Then just use the app to add each of them as a new script (load file).
If Windows fails to find the correct driver, go to the Device Manager and manually set it to use the driver, "USB Mass Storage Device". It seemed to try to stick with the MTP driver in my case.
Click to expand...
Click to collapse
Can someone help me with this part? I have no idea how to do this. I feel so dumb.
Please be informed that I have completely updated and rewrote my own guide for the OP. You will see all details and screenshots necessary to get this setup. If something is not clear please feel free to let me know and I will try to answer as best as I can. Please be advised that this has only been tested and guaranteed to work 100% on Windows 7 based computers so far. I cannot confirm for Windows XP, Mac OS X, Linux, or other devices. If someone can test this elsewhere would be greatly appreciated. Hope this helps you guys.
works perfect/
Great!
Worked great for me. :good:
nice
So what does this enable you to do? Browse the entire internal memory when connected to USB, opposed to just the microSD?
This will enable your SD Card to show up as a regular disk drive instead of a device on whatever you plug into with a USB port. This was the old way of managing USB storage before that changed to MTP Mode (device mode) with the Samsung Galaxy Nexus. The benefit of UMS is that it will work with special devices that try to read your phone like a car radio will now be able to read the songs through the USB port, also your TV (if it has USB support of course). Also it's a much more reliable method of transferring files on your computer since it's basically direct access as opposed working through a special protocol with MTP Mode. Hope that helps explain it a bit without being too technical.
Found this today: http://forum.xda-developers.com/showthread.php?t=1711009
Hi to all here. i just want to ask anyone what to do with my phone. well first of all, my phone is a sky pantech vega racer im-a760s, not really a match for samsungs popularity but budget wise this is the model for me. it has a dual core. now my problem starts when i started editing the build.prop in its system (tweaked for some texting problem of limited character sending). of course i know what im doing on that part, but the only thing i didn't think that would happen was, i copied it in my computer, i edited it there, then i saved it as "all" in file type so it wont become a ".txt" format. but when i placed it in my phone. the file instantly disappeared, i think it was only hidden and the phone just cant identify it nor read it like something. now i restarted the phone, it booted up to its logo then it just went blank and it just stops there. i tried pushing recovery with adb in my pc cmd. but it cannot detect my device(no problem with my adb installation to eliminate this from the question), i also tried putting an sd card with a recovery file but there was no option for sd card path. but the phone can still function well, i know because it can still be loaded under flashboot, download screen and S / W upgrade menu and it can still perform wipes for all partition and caches and can reset for factory settings etc. but whenever i will reboot, its not going to complete. anyone please help me how to make my phone be detected by my pc. The usb drivers are just fine, updated it many times, read all procedure for making the driver connect perfectly. i reformatted the sd so it wont be a problem when i put it in. but in the recovery menu i just cant see my sd card, theres just the option for "update from external storage" but it doesn't have anything inside. what a mess. i cant make my phone reflashed cause its not responding with the connection with my pc. but when i am opening an odin (just used for connection monitoring) there are two yellow boxes with com port like these: 0:[com7] and 0:[com9], so i know it is still somehow communicating with my pc. please help any advice, i dont want to resort to jtag for im not sure if it will support my phone and it's already avialable for the model but definitely not going to send my phone for repair cause it will be costly. thanks to all who will respond. Please help thank you. additionally: OS was ics version 4.0.4 and rooted. already gone through rooting several times with no problem. just the editing part.
to edit Android files on Windows use only Notepad++ anyway do not use Windows notepad this is for Windows files formatting only
well, you have to get build.prop from your phone edit on PC then copy back
so enter recovery connect phone to PC create a folder say C:\tmp
to get build.prop from phone
Code:
adb devices
adb shell
mount system
exit
that's to mount system partition then
Code:
adb pull /system/build.prop C:\tmp\build.prop
edit it and copy back to phone
Code:
adb push C:\tmp\build.prop /system/build.prop
maybe is not your case ? but I wanted to give you an idea
@ruscan.calin
Thanks, great. i will try this one once i get my phone recognized by my pc, adb seems not able to find my devcie have this message like this one:
"
c:\>adb devices
adb server is out of date. killing...
*daemon started successfully *
list of devices attached "
and that's it nothing happens.
thanks for the advice i will definitely use this once i get my phone connected with my system. thanks a lot
cruelink said:
@ruscan.calin
Thanks, great. i will try this one once i get my phone recognized by my pc, adb seems not able to find my devcie have this message like this one:
"
c:\>adb devices
adb server is out of date. killing...
*daemon started successfully *
list of devices attached "
and that's it nothing happens.
thanks for the advice i will definitely use this once i get my phone connected with my system. thanks a lot
Click to expand...
Click to collapse
start phone in recovery mode do not connect to PC at this time
open Device Manager now connect phone to PC
if you see ADB Interface connecting in Dev Manager it's ok if not you have a problem with phone drivers so install it again
ruscan.calin said:
start phone in recovery mode do not connect to PC at this time
open Device Manager now connect phone to PC
if you see ADB Interface connecting in Dev Manager it's ok if not you have a problem with phone drivers so install it again
Click to expand...
Click to collapse
Hi, cant still afford to make the adb component in my device manager to appear, but it's good to inform you that it helped me a bit because i was able to see the storage of my phone and i was also able to put some files in there without any hassle that alone was satisfying me that my phone is not really dead. sad to say i did everything i could to have my pc detect my phone via recovery menu, but still no devices found. it's really weird that some links are saying that i should make my phone's "usb debugging" enabled, wherein fact i cant even go beyond my original problem(bricked phone), i can't even see the inside of my phones directory, only the storage one that was activated just recently. i even did a reinstallation of my usb, uninstalled every other phone related usb installation to avoid conflicts reinstalled my phones proper usb installer then restart. no progress still to be called. it makes me feel that the phone was just trap in the state of booting and not knowing what to do because it cant see any command inside its system. i cant go into the systems directory as well. and that's the only way i think i could revive my phone in replacing a new build.prop, as you advised to be edited in a notepad++ which i recently acquired and installed. by the way how do i save the build.prop to its original file format, and what is the extension. thanks alot for helping out. im getting a little brighter each step of the way, im not loosing it to come to smashing my phone to pieces instead of keeping a very expensive paper weight.
usb debugging enabled is not useful in this case (you can't set it )
build.prop is a file with .prop extension save file with notepad++ name it build.prop then check location of file it should be build.prop notepad from Windows saves it as build.prop.txt that's not good also notepad adds some formatting characters inside file that's wrong so use only Notepad++ when working on Android files (or VIM for Windows editor etc anyway do not use Windows editors they are good for Windows files only)
-try these things on another computer (to install drivers etc)
-I advised somebody to send a mail to manufacturer and he got a reply with a link to stock rom... that's great !
-if you link me your build.prop file I can tell you if it's ok
-pc link - that's to be solved firstly check manufacturer site for sync software/ drivers even send mail
isa. rgiespea
ruscan.calin said:
usb debugging enabled is not useful in this case (you can't set it )
build.prop is a file with .prop extension save file with notepad++ name it build.prop then check location of file it should be build.prop notepad from Windows saves it as build.prop.txt that's not good also notepad adds some formatting characters inside file that's wrong so use only Notepad++ when working on Android files (or VIM for Windows editor etc anyway do not use Windows editors they are good for Windows files only)
-try these things on another computer (to install drivers etc)
-I advised somebody to send a mail to manufacturer and he got a reply with a link to stock rom... that's great !
-if you link me your build.prop file I can tell you if it's ok
-pc link - that's to be solved firstly check manufacturer site for sync software/ drivers even send mail
Click to expand...
Click to collapse
that's great news, you actually come to emailing the phones manufacturer? wow, im flattered. well you're a very nice guy to help me out on this. and i have good news too. i found out that i have a little conflicting usb drivers, as i have installed samsung for my previous phone(samsung galaxy 1) i had it liquidated for this new one. but a little hard on the support. you gave me a new idea about the usb. so i uninstalled all the related usb drivers and have it reinstalled. now i am able to communicate with OTA firmware server, and i got a reading that was not happening before(stucked in just detecting the phone) now i have a percentage reading of downloading or so. but i still have to wait if it will complete and have it repaired. so by now you can give me a little more help cause im still not at it in pushing through the use of adb programming. and the link you mentioned, i'll wait for the progress about it and see what really was it. and thanks a lot. really appreciate it.
fixed bricked phone via OTA by fixing link to pc.
Hi, i thank you for your help. i managed to fix the phone myself. i just missed the simple step that you advised me. fix the link first to pc. i have installed another model of the phone for the same manufacturer with different type so that was causing the mixed up for updating and recovering via the OTA site of the phone. so yey. you helped a lot. i thank you. i am now running at ics version 4.0.4 and now rooted. i will not commit the same mistake of saving the build.prop with another format. that was bad. so then i'll be very careful in editing the build.prop and first of all, i will keep a backup inside where i can access it even if it will be hard bricked. never forget that one from now on. so this is it. i thank you. of all the place ive been circling around for answer. here is where i found it. and just one person. hooray. thank you very much.
cruelink said:
Hi, i thank you for your help. i managed to fix the phone myself. i just missed the simple step that you advised me. fix the link first to pc. i have installed another model of the phone for the same manufacturer with different type so that was causing the mixed up for updating and recovering via the OTA site of the phone. so yey. you helped a lot. i thank you. i am now running at ics version 4.0.4 and now rooted. i will not commit the same mistake of saving the build.prop with another format. that was bad. so then i'll be very careful in editing the build.prop and first of all, i will keep a backup inside where i can access it even if it will be hard bricked. never forget that one from now on. so this is it. i thank you. of all the place ive been circling around for answer. here is where i found it. and just one person. hooray. thank you very much.
Click to expand...
Click to collapse
that's good news ! and thanks for feedback
feedback is an invaluable resource ! (some just forget about that from my experience :laugh: NOT your case ! )
***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.
Many have faced this problem while using a new phone (Lollipop, Marshmallow and later) with MTKDroid Tools.
Here is the issue - MTKDROID ships with an older version of ADB. (The program hasn't been updated for a few years but it still works.)
This ADB cannot recognize the newer phones. So the obvious solution is to replace the older adb.exe from the 'adb' folder of MTKDroid Tools. But MTKDroid recognizes this and refuses to start, showing us the 'It is impossible to start ADB' error.
I have made a workaround which starts MTKDroid with the older adb and immediately when it finds everything to be OK, replaces it with a newer one. It worked for me. So I hope it will for you too.
Download the zip in attachment.
Instructions.
Goto your MTKDroid/adb folder and delete everything in it.
Open the zip file you have downloaded with winrar or 7zip or anything.
Inside the zip file, there will be 8 files. Copy all these files to the adb folder.
Now you can double click StartMTKDROIDTOOLS.bat and press enter to start MTKDroid Tools. A few black console windows will come and ask you to wait 10 seconds (this is to make sure MTKDroid is loaded completely), wait and don't worry it will close itself when the work is done.
There you go problem fixed and MTKDroid is ready for your command!
NOTE: This fix will help you to start MTKDroidTools and use it to create a scatter file for flashing and backup purposes with SPFlash tool. From what I learned, you can't use this to root your phone unless you enable the temporary root shell from Engineering Mode.
To do that, open your phone dialer, dial *#*#3646633#*#* .
Swipe left to reach Log and Debugging section, there select user2root, in it enable root shell and now connect your phone using the above method.
This method is not guaranteed to work on every phones out there and I still recommend flashing SuperSU the old fashioned way.
Please reply back with any of your troubles or suggestions.
Hi, Thank you for posting this I was disappointed when the tool did not work. But thanks to you it's working now and I can do my surgery xD
pig_slay said:
Hi, Thank you for posting this I was disappointed when the tool did not work. But thanks to you it's working now and I can do my surgery xD
Click to expand...
Click to collapse
I hope it lives.. :fingers-crossed:
Thanks so much, Adithya! This was a life-saver. I had spent over a day trying to get MTKDroidTools to work and only now found your post!
I have a new Nook tablet (BNTV450). This runs Marshmallow and the adb v31 included with MTKDroidTools 2.5.0 could not connect with it, as you reported. (BTW, I'm using 2.5.0 because 2.5.1-2.5.3 have a malware built in. androidmtk.com says not to worry about the malware (!) but my anti-virus reports it as w32.malware.heur which is quite serious. Anyway, these later versions of MTKDroidTools also use adb v31.)
I did need to make one small change due to a race condition: I added a 2 second delay between the call to run startup.bat and the call to run MTKDroidTools. So this section of StartMTKDROIDTOOLS.bat now reads:
start Startup.bat
timeout 2
cd..
start MTKdroidTools.exe
Without this on my Windows 10 PC, MTKDroidTools starts too quickly and picks up the newer version of adb even though startup.bat had just replaced it. The 2 second delay allows MTKDroidTools to find the old version reliably.
So thanks again for this! Really helpful!
Best,
Dennis
DMcRitchie said:
Thanks so much, Adithya! This was a life-saver. I had spent over a day trying to get MTKDroidTools to work and only now found your post!
I have a new Nook tablet (BNTV450). This runs Marshmallow and the adb v31 included with MTKDroidTools 2.5.0 could not connect with it, as you reported. (BTW, I'm using 2.5.0 because 2.5.1-2.5.3 have a malware built in. androidmtk.com says not to worry about the malware (!) but my anti-virus reports it as w32.malware.heur which is quite serious. Anyway, these later versions of MTKDroidTools also use adb v31.)
I did need to make one small change due to a race condition: I added a 2 second delay between the call to run startup.bat and the call to run MTKDroidTools. So this section of StartMTKDROIDTOOLS.bat now reads:
start Startup.bat
timeout 2
cd..
start MTKdroidTools.exe
Without this on my Windows 10 PC, MTKDroidTools starts too quickly and picks up the newer version of adb even though startup.bat had just replaced it. The 2 second delay allows MTKDroidTools to find the old version reliably.
So thanks again for this! Really helpful!
Best,
Dennis
Click to expand...
Click to collapse
You're welcome.
I have included the changes you suggested.
Also I found this on stackoverflow which might help on w32.mal.heur detections.
W32 is the platform: Windows 32
Malware is the Category
Heur (Heuristic) might refer to what usually is the family or might be some specific naming of your AV
The heuristic term usually refers to detections based on generic signatures which look suspicious.
That detection looks very generic and might be a false positive.
Click to expand...
Click to collapse
Since the nature of the tool is indeed a hack itself your AV might be showing a false positive.
Still it's all up to you to decide.
All the very best.
Post updated.
Added a 2 sec delay to call MTKDroidTools. (Thanks @DMcRitchie)
Added a guide on rooting.
This doesn't work for me. I used to Only get the phone not recognized error now, after copying over the 8 new files to my now empty ADB folder, I get the error that says Impossible to start ADB.
I'm using a Figo Atrium upgraded from Lollipop to Mashmallow using the SP Flash Tool. All I'm trying to do now it root the device, I don't need a custom rom. Using MTK Droid Tools version 2.5.3
Edit: Fixed it. I had to turn off then back on UBS Debugging, simply revoking the USB did not work. It's seeing my device now but says it can't root my device and sends me to an html page with lots more instructions. The tool tells me my device can be rooted this way. https://forum.xda-developers.com/showpost.php?p=38337401&postcount=5 Grrr.. time to spend days jumping through more hoops.
Divergent Droid said:
This doesn't work for me. I used to Only get the phone not recognized error now, after copying over the 8 new files to my now empty ADB folder, I get the error that says Impossible to start ADB.
So this didn't fix it, just made it worse. Is there another way to fix? I'm using a Figo Atrium upgraded from Lollipop to Mashmallow using the SP Flash Tool. All I'm trying to do now it root the device, I don't need a custom rom. Using MTK Droid Tools version 2.5.3
Click to expand...
Click to collapse
This was supposed to fix the 'impossible to start error'. You shouldn't have used it if you were not facing that issue.
Don't worry you can just redownload MTK Droid Tools to fix that.
As for rooting, MTK Droid Tools CAN NOT ROOT phones newer than kitkat. Your best bet is to flash a custom recovery and flashing super su.
This guide is for those people who can't use SP Flash Tools because they need a scatter file which MTK Droid Tools can't make for newer androids.
All the best.
Thanks.
You gave me the most detailed answer so far. I got the info to use MTK Droid Tools from a website claiming it will work for Android 6.0 Marshmallow. That's why I tried it. If you are very knowledgeable about rooting in general, perhaps you'll answer my other thread asking someone to help me understand these things better. it seems according to you, i would be able to flash a new rom and SuperSU? See my other post and answer there. https://forum.xda-developers.com/general/help/guru-to-discuss-rooting-t3683594 - I did try the folks at the SuperSU sub forum and they cant help me.
When i connect Infinix Note 4 Pro X571 (bricked) to pc for Mtk to detect, it just boots to recovery mode (twrp)
tried using Maui Meta, it automatically installed vcom drivers then it said "it cannot find Kernal USB comport for AP and Modem handshake. Please check the usb driver version or find the driver owner to check"
thank you so much!! it works
I Get This Only :/ What's wrong? Noob Mistake?
qounik said:
I Get This Only :/ What's wrong? Noob Mistake?
Click to expand...
Click to collapse
I have the same issue. I just want to backup some stuff.
EDIT: this worked for me https://forum.xda-developers.com/showpost.php?p=75722412&postcount=14
Hi
Great fix but I still have a problem, I only have the hardware and baseband detected nothing else, so I can not save.
An idea ?
Thanks