[Q] Can you unroot without using a PC? - Samsung Epic 4G Touch

I'm new and I hope I'm not posting this in the wrong place or re-posting an old question, but I have been searching on this and other sites for days and haven't been able to find anything pertaining to my question, so sorry in advance If I'm not posting this correctly.
I have a rooted epic touch with rogue boot loader installed and UnNamed rom installed. I really liked the way it was running until I had some kind of malfunction happened and now the battery charge light won't shut off and the battery drains within a couple hours of standby time. the phone is only a couple months old and would like to take it to the sprint store as I'm assuming this is an obvious hardware issue. My problem is that my pc doesn't recognize my phone anymore so I can't flash back to stock and get rid of root, voiding my warranty. I have tried uninstalling and reinstalling kies and stand alone drivers multiple times with no avail. I've tried with the battery and sd card removed and have also tried on multiple pc's (2 win7 and and xp machine). every time it says the drivers weren't installed successfully and to replace the device being connected.
My question: Is there a way to revert to stock off of the internal memory of the phone? I know there are zip roms you can flash from the boot loader but I was wondering if there was a way to flash a rom from zip and install the original boot loader as well as get rid of root? Any help I can get would be extremely appreciated and again I apologize if I am wasting anyone's time by asking in the wrong place or re-asking a question.

Ok so I downloaded the Calkin's_Stock_Rooted_EK02_ROM_v1.0 and got it on my sd card via dropbox. Flashed and now have a stock rom on it which I think is a step in the right direction.
The only thing is now I have clockwork boot loader and still rooted. and still not recognizing on pc. anyone know of an unrooted zip with original boot loader?

I couldn't get my PC to recognize either of my 2 E4GT's, each due to a different reason, both issues were resolved by going through each step in sfhub's debugging checklist:
sfhub said:
This post is for the FAQ section:
Why is the install stuck waiting for device to be connected?
Your phone isn't being recognized by your PC as an Android device.
When the drivers are installed and the phone is properly recognized, you should see the following in start->run->devmgmt.msc
Code:
Android Phone
SAMSUNG Android ADB Interface
Modem
SAMSUNG Mobile USB Modem
Until you get the SAMSUNG Android ADB Interface to show up, neither ADB nor this script will work.
Here is a debugging checklist:
1) dial ##UPST# (##8778#) in the dialer and verify AP (or ALL) is checked (if CP is checked, phone won't be recognized as an Android device)
2) restart the ADB server (choose Option G to stop the server, it'll get started automatically by the script)
3) verify USB Debugging is ENABLED
4) verify USB drivers are installed (Win7-64bit see below)
5) try a different usb cable
If you are in Win7-64bit try changing the default install location for the drivers:
If you see an error like this:
Try running the CMD prompt (or e4gtauto-sfx.exe) as Administrator. Right-click on the CMD icon (or e4gtauto-sfx.exe) and select "Run As", then select Administrator.
If that doesn't work, try disabling windows firewall.
Click to expand...
Click to collapse

I went down that list and everything seemed to be in order but still no recognition by pc. I kept uninstalling and reinstalling the drivers and switching usb ports and it finally installed the drivers successfully long enough for odin to recognize it and to flash back to stock. As soon as it was done the machine stopped recognizing it again. Lucky break I guess. So I can now return it to sprint and deal with the hardware issue.
I would still like to find a zip file like the tar that I flashed that installs stock recovery and non rooted ek02 rom and kernel from cwm, if that's even possible.
Thanks Godswrath, for helping me out.

You could use wifi explorer to get files on to sd card and mobile Odin to flash the tar file back to stock....
Sent from my SPH-D710 using xda premium

Lol....I am a noob.
They make a mobile Odin? That would have saved my like 4 hours....

Related

[Q] trying to get clockworkmod 3.0.0.4 on my epic 4g

I tried putting cockworkmod 3.0.0.4 onto my epic but nothing happened the first time I tried it. I had usb debugging on before so I know its not that.... but now it won't even recognize my phone when I click run in the oneclick root fle.
Should I reset my phone and try it again? If so how do I do that...
Do you have the Samsung drivers installed? If no then download and install them, if yes then redownload and reinstall them.
Is your data cable good? Can you get into mass storage? Why Clockwork 3.0.0.4? Go with 3.0.0.6, it is much more compatible with most ROMs. And make sure you have an EXt4 compatible ROM ready to flash after the file system conversion.
I had a similar issue with mine. If you have the current drivers installed, and a better USB cable, it seems there's not a whole lot else you can do besides cross your fingers. I tried mine on 2 different computers (work and home). My home computer, which CWM has never liked in the past, was the one that did the trick. Had to experiment with different USB slots, and restarting the computer every time it didn't work. Also don't know if it makes a difference or not, but the CWM version I finally got to work was from the links in the youtube how to video for SyndicateROM - Frozen (not the links the syndicate guys provided) . Good luck!
I had to use an old XP machine for my first one-clock root/CWM install. None of my win7 machines would work.
Not sure why, but now the win7 machines work fine. Using the same drivers on all of them.
Again, it's a shot in the dark, but have you tried an XP computer?
Here are a few things you could try:
1) First you need to have the Android SDK installed on your computer. This will allow you to access your phone through adb which is required in order to install any version of CWM. You can download the SDK from here, developer.android.com/sdk/index.html
2) Next you have to set up the environment variables which will allow you to use adb to connect to your phone. This is a very important step and it must be done correctly. Here is a You Tube video which walks you through the process, youtu.be/b1qgKA_eT2g
3) Once you have those two steps completed you can begin to install CWM. Here is another You Tube video for that portion, youtu.be/cFrA__9bURo
Troubleshooting tips:
1) Make sure that you have the correct drivers installed on your machine. If you can connect you phone and access the SD card then you have the proper drivers already installed. If your unable to access the SD card then you may have a problem with the drivers.
2) Make sure that your plugging in the USB cable directly into the back of your computer. DO NOT plug it into any type of USB hub or the front of your machine.
3) If it is not being detected in one of the USB ports, unplug and try another.
**Im unable to post links at the moment so you will have to copy and past the youtube and other links into another browser window to access the web pages**
Good Luck
1. You don't need the SDK to install CWM.
Tips: start here first and these should fix your problem.
Sent from my SPH-D700 using Tapatalk
Top Nurse said:
1. You don't need the SDK to install CWM.
Click to expand...
Click to collapse
Taking a look in the CWM3.zip folder it looks like the program bundles adb within the program. I may have been incorrect in stating that you need to install the SDK onto your machine.
I have been rooting different Android phones for over a year now (I still dont claim to know everything) and the SDK has been installed on my machine ever since then. My previous phone required the SDK in order to root and I just assumed that was still needed for CWM3.
Thanks for the correction Top Nurse.
Any luck getting CWM onto your phone jsoileau2?
Why CWM 3.0.0.4 and not CWM 3.0.0.6?
Sent from my SPH-D700 using XDA App
It was not too clear if you had root already or you was trying to run one click a second time. If you do have root, try dl rom manager from market then let it install cwm for you. Win7 people try using the 32bit drivers.
If you downloaded one click 2.5.5, it has all the files you need to root and install cwm 2.5.1.0. No need to set up sdk stuff, it's all in the zip of one click. Also try reboot computer and phone if adb isn't seeing the phone. Try different usb port on computer if rebooting doesn't help.
Try turning off any antivirus program you might be using.
Don't use Rom Manager, there are many problems with it on the Epic.
I don't know if it makes any difference but I've always went to start, run, cmd, cd to directory where one click is, then run.bat
Sometimes it is necessary to be at a command prompt instead of just clicking on the file. I don't know if this is one of those instances or not.
Rom manger doesn't install the cwm (well on epic it tries to.) But it does download it. Try it.
Then boot into recovery and install zip from /sdcard/clockworkmod/download/mirrorbrain.cynogenmod.com/ and the cwm zip will be there.
Install it.
It worked for me.
Sent from my SPH-D700 using XDA Premium App

[q] So i think my Epic is screwed...

First and foremost, been a long time lurker here (first time poster) on XDA... and the community here is just outstanding.
So I've decided to root my epic, everything was great. I used the one click 2.5CWM root, and realized I wanted to try out another rom that wasn't compatible. Reflashed with the( ReRFS.Format.ROM.EC05 ) (since it kept me stuck on the samsung black screen) then went ahead and flashed the zip for CWM 3.0.0.6 with viperrom,...
Now here's where it gets interesting... I want to be able to revert back to a stock rom, and flash syndicate... but for some reason my CWM wont allow me to flash any .zip files from SD card. It says "failed to mount /sdcard". i formated it on my pc, it reads / writes fine, but anytime i boot into clockwork, it can't mount my sd card. I can still boot into my phone, it's still usable for daily usage, but it just doesn't look like what I like.
Now I've tried running Odin, but when im in the download mode, odin will not recognize my phone being plugged in. I've downloaded the proper drivers, for both my win7 x64 and 32 bit computers, tried every USB port etc... and it still wont work.
any idea on what I can do to get my CWM to work?
Use Odin with a non-stock cable.
I've tried it with 4 different data cables, 2 Samsung OEM, and 2 generics...
Have you tried a different PC, or Heimdall?
Make sure you're using Odin 1.61, the correct PIT, and the EC05 TAR.
http://k0nane.info/rom/odin-pit.zip
http://k0nane.info/rom/SPH-D700-EC05-8gb-REL.tar
Also there is a small amount of phones that did not want to Odin correctly unless the battery was out. You can try that too.
So I've tried to run Heimdall, and i'm still experiencing the same issue that I was having with Odin.
Every time I plug in my device via USB (samsung OEM data cable, only cable i have that will prompt that a device is connected) windows will pop up with a message, device not recognized (unknown device in device manager when in download mode) it seems to be fine and it'll recognize it correctly when I have the phone running (booted up into the rom)
I ran the zadig.exe for the drivers, and nothing seems to work.
Instead of Odin, try the SWUpdate for EB13, it is much less fickle
Place your phone in download mode (keyboard #1 and the power button) and see if it will connect/install
If It works, you can then move on to either upgrade to EC05 using the stock update zip, or install CWM and flash your FAV ROM
My comp doesn't seem to want to recognize the phone anymore... everything is "unknown device" now
Yeah get your hands on a blackberry cable. My guess it will help your cause. Make sure the drivers are installed on your pc as well.
im just going to reformat my netbook and do a fresh install on the drivers, too tires of the "guess work" i'll keep you guys posted on how that goes
SUCESS!
my epic is back to full stock via Heimdall. (took a little playing around to get)
@qbking77 - Thanks for the tip, I ended up using a 7" black berry data cable, and heimdall recognized it.
The only thing now though, all of the wires i have now, don't seem to let me use One Click Root CWM 3.0.2.5 I'll try it with my OEM samsung cable (that worked before) when i get home, I'll keep you guys posted.
Thanks again!

[Q] Soft bricked i9250 international

Hi and thanks for taking the time to read this
My brother tried to do the update of his nexus through the phone download (not through the sd card or connecting to a computer). Since this it will not start up and if i go to download mode it says that it is downloading constantly (have left for hours).
I can make it to the clockworkmod recovery v6.0.1.0 but unfortunately my brother didnt make a backup before trying to update to 4.2 jellybean.
The unfortunate part of this equation is that i cant access the phone via usb as the drivers wont install and the phone doesnt have an sd card slot except the sim card slot. So placing the correct files on the phone is proving too hard for me to complete.
Sorry if this situation has been covered before but i have searched for about 1.5 hours now to no avail. I would very much appreciate if someone can take me through how to get this phone working in any way possible (i dont care if he loses all data and goes back to stock).
Regards
Sam from New Zealand
samakbuchanan said:
Hi and thanks for taking the time to read this
My brother tried to do the update of his nexus through the phone download (not through the sd card or connecting to a computer). Since this it will not start up and if i go to download mode it says that it is downloading constantly (have left for hours).
I can make it to the clockworkmod recovery v6.0.1.0 but unfortunately my brother didnt make a backup before trying to update to 4.2 jellybean.
The unfortunate part of this equation is that i cant access the phone via usb as the drivers wont install and the phone doesnt have an sd card slot except the sim card slot. So placing the correct files on the phone is proving too hard for me to complete.
Sorry if this situation has been covered before but i have searched for about 1.5 hours now to no avail. I would very much appreciate if someone can take me through how to get this phone working in any way possible (i dont care if he loses all data and goes back to stock).
Regards
Sam from New Zealand
Click to expand...
Click to collapse
CWM recovery offers the ADB interface. I would:
1. get the naked driver package (see Efrant's guide)
2. boot device into recovery and connect usb cable
3. open windows device manager, find your device and manually update the driver
4. use adb to backup the /sdcard to your computer
5. flash 4.2 stock images using fastboot
6. done
Petrovski80 said:
CWM recovery offers the ADB interface. I would:
1. get the naked driver package (see Efrant's guide)
2. boot device into recovery and connect usb cable
3. open windows device manager, find your device and manually update the driver
4. use adb to backup the /sdcard to your computer
5. flash 4.2 stock images using fastboot
6. done
Click to expand...
Click to collapse
op, if you just want to get the device to working state again, and dont care about any data:
1. get the naked driver package (see Efrant's guide)
2. boot device into bootloader and connect usb cable
3. open windows device manager, find your device and manually update the driver
5. flash 4.2 stock images using fastboot
step 3 is the same, the same procedure, the same driver; windows is dumb so you have to tell it again when device is in bootloader (which, btw, is NOT the same as download mode).
Hi and thank you for the replies.
I have downloaded the naked driver but cant get it to work. I have followed the steps to make it work but i get to the device manager and there is no option for uninstalling current driver (as it has none currently). It only has update driver software (which if i use windows to search for it cant find any) and properties. The Galaxy Nexus icon in the device manager has the yellow exclamation mark sign on it. I can
When i try to manually find the naked driver it comes up with the following error
Windows found driver software for your device but encountered an error while attempting to install it.
Google Galaxy Nexus ADB Interface
Access Denied.
Where to from here lads, i appreciate the input
samakbuchanan said:
Hi and thank you for the replies.
I have downloaded the naked driver but cant get it to work. I have followed the steps to make it work but i get to the device manager and there is no option for uninstalling current driver (as it has none currently). It only has update driver software (which if i use windows to search for it cant find any) and properties. The Galaxy Nexus icon in the device manager has the yellow exclamation mark sign on it. I can
When i try to manually find the naked driver it comes up with the following error
Windows found driver software for your device but encountered an error while attempting to install it.
Google Galaxy Nexus ADB Interface
Access Denied.
Where to from here lads, i appreciate the input
Click to expand...
Click to collapse
if you're using windows 7, i read something about you need to disable windows digital driver signature check, or something in those lines.
can't help any further on that subject, since i'm a Linux user (Windows knowledge is very limited) and also that is an operating system's issue and would be better discussed in a Windows forum, IMO.
bk201doesntexist said:
if you're using windows 7, i read something about you need to disable windows digital driver signature check, or something in those lines.
can't help any further on that subject, since i'm a Linux user (Windows knowledge is very limited) and also that is an operating system's issue and would be better discussed in a Windows forum, IMO.
Click to expand...
Click to collapse
Thank you for another helpful reply! Yes i am using windows 7 - i will try to perform the task now - results soon. In the meantime if anyone else knows instructions on how to do this i would love to hear
I am at work and dont have administrator settings on windows 7 so i went to an older computer and started fastboot.exe. I went to recover and there was the IP address of the computer went to that and recovered. From there i went to reboot and now i am just getting a Google in the middle of the phone (as before). I will wait some time to see if it will start up now. If not what is my plan?
So i havent got any closer to having a usable phone.
Im up to this step:
"flash 4.2 stock images using fastboot" how do i do this? i have fastboot and i have the stock image
samakbuchanan said:
So i havent got any closer to having a usable phone.
Im up to this step:
"flash 4.2 stock images using fastboot" how do i do this? i have fastboot and i have the stock image
Click to expand...
Click to collapse
[HOW-TO] [GSM & CDMA] Return to stock for ALL Galaxy Nexus phones (latest JOP40C)
Thanks for that i had since found that and have printed it and will work through each step methodically. I have the stock image on download.
I have spent the best part of my working day on it now. Fingers crossed it all works out.
Thanks to all who have helped me through this far

Phone not recognized by PC after root (but still rooted)

So here's the story:
1) Phone worked flawlessly before root. Did an OTA to stock 4.1.1
2) Flashed CWM with Odin v1.85 --> removed battery --> worked without issues
3) Applied SuperSU v0.87 and this didn't go without issue. While in CWM before the reboot, there was some extra prompt (I have rooted a S3 before and did not receive the prompt) however I cycled too fast and I don't think I hit the right option. The phone rebooted anyway and I had root so I didn't think anything of it.
4) Wanted to add files to my SDcard a couple of days later and the phone didn't show up in My Computer (yes USB debugging is enabled, tried all USB ports, changed cables, uninstalled and reinstalled Samsung drivers, I've never used Kies to do anything with my phone - disabled it from the start)
I thought I should revert to stock and start over so I booted into recovery and CWM wasn't there anymore but I still had SU access. I installed Mobile Odin and placed CWM (the .tar file) on my internal (Placed on SDcard --> moved with My files to internal) and flashed CWM and while I didn't see any errors, now I'm data wiped/factory reset but I still can't boot into CWM, I still have SU, and my phone is still not recognized by my computer.
Anyway for me to fix this issue?
Android version: 4.1.1
Baseband: T999UVDLJA
Kernel: 3.031-370274...SMP PREEMPT Fri Oct 19
Build number: JRO03L.T999UVDLJA
tmayne said:
So here's the story:
1) Phone worked flawlessly before root. Did an OTA to stock 4.1.1
2) Flashed CWM with Odin v1.85 --> removed battery --> worked without issues
3) Applied SuperSU v0.87 and this didn't go without issue. While in CWM before the reboot, there was some extra prompt (I have rooted a S3 before and did not receive the prompt) however I cycled too fast and I don't think I hit the right option. The phone rebooted anyway and I had root so I didn't think anything of it.
4) Wanted to add files to my SDcard a couple of days later and the phone didn't show up in My Computer (yes USB debugging is enabled, tried all USB ports, changed cables, uninstalled and reinstalled Samsung drivers, I've never used Kies to do anything with my phone - disabled it from the start)
I thought I should revert to stock and start over so I booted into recovery and CWM wasn't there anymore but I still had SU access. I installed Mobile Odin and placed CWM (the .tar file) on my internal (Placed on SDcard --> moved with My files to internal) and flashed CWM and while I didn't see any errors, now I'm data wiped/factory reset but I still can't boot into CWM, I still have SU, and my phone is still not recognized by my computer.
Anyway for me to fix this issue?
Android version: 4.1.1
Baseband: T999UVDLJA
Kernel: 3.031-370274...SMP PREEMPT Fri Oct 19
Build number: JRO03L.T999UVDLJA
Click to expand...
Click to collapse
Sigh...
Go here and follow the instructions. My 10 year old was able to do it without an issue.
http://forum.xda-developers.com/showthread.php?t=1949687
Reload the samsung drivers on the computer and boot into download mode. After loading the root66 version via odin download Rom manager from the store and load cwm.
Sorry OP but I does anyone know a way to connect to a PC without install the samsung drivers? I'm asking because I don't have permission to install anything to my computer at work. I've tried this http://forum.xda-developers.com/showthread.php?t=1711009
and this https://play.google.com/store/apps/...9pZC5tdWx0aW1vdW50c2RjYXJkLndpZGdldC5mcmVlIl0.
but still no go. They all treated my SD Card as CD drive which can read only. Any input is greatly appreciated.
jcbofkc said:
Sigh...
Go here and follow the instructions. My 10 year old was able to do it without an issue.
http://forum.xda-developers.com/showthread.php?t=1949687
Reload the samsung drivers on the computer and boot into download mode. After loading the root66 version via odin download Rom manager from the store and load cwm.
Click to expand...
Click to collapse
Thanks for the quick reply and I apologize if I wasn't clear but I was attempting to use Mobile Odin (my first time) because my phone was not being recognized by my PC and thus desktop Odin wasn't working either (even after reinstalling drivers and booting in download mode which I tried before posting).
However, I did find the answer eventually. If people have problems losing CWM after root, the error I made was not extracting the image file from the .tar before flashing with Mobile Odin. I eventually returned to stock but that didn't solve my PC not recognizing my device until I found this:
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
Credit was given to Nacos on XDA
I didn't bother with Kies and obviously used the latest Samsung USB drivers. Problem solved!
Perfect.
Sorry if I sounded a little short. I am glad you found the solution.
after rooting my phone (samsung galaxy s duos 2) it is not getting detected by pc when connected using usb. Everything else works fine. Please help me to resolve this issue
[email protected] said:
after rooting my phone (samsung galaxy s duos 2) it is not getting detected by pc when connected using usb. Everything else works fine. Please help me to resolve this issue
Click to expand...
Click to collapse
Probably best if you ask in your devices forum if you think it had to do with how you rooted. They'll be more familiar with it and any problems that can occur.
http://forum.xda-developers.com/s7582
The only thing I can say is to uninstall kies, install standalone USB drivers (try both the latest and the older version released for your device on Samsung's site), reboot pc and phone and try to connect again.
Good luck!
Sent from my SGH-T999 using Tapatalk
tmayne said:
Thanks for the quick reply and I apologize if I wasn't clear but I was attempting to use Mobile Odin (my first time) because my phone was not being recognized by my PC and thus desktop Odin wasn't working either (even after reinstalling drivers and booting in download mode which I tried before posting).
However, I did find the answer eventually. If people have problems losing CWM after root, the error I made was not extracting the image file from the .tar before flashing with Mobile Odin. I eventually returned to stock but that didn't solve my PC not recognizing my device until I found this:
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
Credit was given to Nacos on XDA
I didn't bother with Kies and obviously used the latest Samsung USB drivers. Problem solved!
Click to expand...
Click to collapse
well nobody wants to help me fix my issue so i will trthis and hope it works.. malfun after trap kernel root no wifi and phone malfunction not recognized by pc.. worked fine nevver any issues till i used g360t1 trap kernal root, didnt relise twrp had a official for his model or i eould have done that so now i need to go on pc to revert back then root using twrp but pc wont connect to phone ahj bullsht
now glad i have root but cant get on pc and all fixs do nothing, not usb cord or pc or mtp settings ect ect not drivers nothing like that.. can i flash stock using twrp, yes but no not me not my phone keeps saying fail so stuck with no wifi and cant connect to pc to tether and its pissing me off.. can someone please help like how has this never happened to anyone at all.. its not a common sense fix here
Don't work , tried all still not working after root
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
Is there no fix ?

[Q] Cannot initiate USB data connection on GS3 (rooted, CM10; Win 7)

A few weeks after rooting and installing CM10 on my GS3, it stopped recognizing any form of USB data connection. It still charges from both computer and wall adapter, but I cannot initiate a data transfer or recognize my device using ADB.
I have tried:
three different OEM Samsung cables (from SG3/SG4 phones)
all the ports on two different Win 7 laptops
all the ports on an Ubuntu desktop
enabling or disabling USB debugging
with different combinations each time. No "USB connection" dialog has shown up on the phone, and no "new device" dialog has shown up on any of the computers. I know that I can get ADB working with a different Android phone (HTC Inspire 4G) so I know that my main laptop has USB ports that work and the cables I've tried work as well, so I'm left to assume that the issue is with the GS3. External visual inspection does not suggest the USB port on the phone is damaged, and the phone is only a year old, so I don't believe that is the cause.
Is there a system setting that I may have modified on the GS3 that would disable all forms of USB communication?
(The end goal is to get at least ADB working so I can try and recover some deleted files from the internal memory; I haven't found a reliable method that does not require ADB so I'm trying to get that to work. I know that transferring files on or off can be accomplished with the external SD card or over Wifi but that is not what I'm looking for)
Any suggestions from anyone?
I am not sure. Could be a software issue. I would try backing up your current cm ROM and try installing a fresh touchwiz ROM to see of that works, to rule out software issues. This could also be a android 4.3 issue. Could try stickmount or a similar otg app from the market.
Sent from my Nexus 7
stelv said:
I am not sure. Could be a software issue. I would try backing up your current cm ROM and try installing a fresh touchwiz ROM to see of that works, to rule out software issues. This could also be a android 4.3 issue. Could try stickmount or a similar otg app from the market.
Sent from my Nexus 7
Click to expand...
Click to collapse
I don't think any OTG app like stickmount will help; I'm not trying to connect devices to my phone. I'm trying to get my computer to recognize my phone (and vice versa) in order to get ADB working.
If I can avoid flashing a RAM I'd like to, because I'm still interested in recovering those deleted files. If that is the only thing that would help, though, then I'll do it. Any other suggestions?
Install Kies and that should get the drivers for the pc in place. Odin should recognize the device when it is in the download mode. If that works, then the pc to phone connection is OK and I'd look to software instead of hardware.
Or, if you boot into your custom recovery, either CWM or TWRP, you should be able to get ADB to recognize the device and issue commands including pulling the files on Internal storage. TWRP also has a file browser built in that might be useful.
I have tried uninstalling any Samsung drivers then using the SGS3 toolkit to install the official drivers, but that didn't change anything on the PC end.
Additionally, I tried finding my device while it was in recovery using ADB and there was no connection indication either.
I currently have CWM installed, but I didn't see a mounting option like I've seen for TWRP. Can I flash TWRP without a computer?
Or try this out: Download mode>Connect via USB>Let Windows download and update all drivers until the notification in the bottom right says it's ready to use>Unplug>Battery Pull>Boot normally>connect again. Voila! It works every time when it's being wonky and its a simple way that doesn't require a bunch of downloads!
installing insecure adb might help
Rebooting into download mode does nothing.
I believe rooting and installing CM10 means I already have insecure adb?
thanks
thanks
what next?
aEx155 said:
Rebooting into download mode does nothing.
I believe rooting and installing CM10 means I already have insecure adb?
Click to expand...
Click to collapse
I have this same issue, in download mode, the device is still not connecting.
what is the next step? I have followed this thread and have the still have the same issues.

Categories

Resources