Related
Hello Im new to the forums
So I was trying to root my evo but i ended up messing it up. It wouldn't read the usb cable or charge and would also not read my SD card. I ended up being able to make it read my SD card but i still haven't been able to resolve the USB issue. I have searched several threads but all those methods of fixing the usb issue require your EVO to be rooted which mine is not.
does anyone know of a way to fix it without being rooted?
and i can't root my phone because it won't read the USB cable while the phone is booted up into android only in fastboot
bump.............
lancerevox279 said:
Hello Im new to the forums
So I was trying to root my evo but i ended up messing it up. It wouldn't read the usb cable or charge and would also not read my SD card. I ended up being able to make it read my SD card but i still haven't been able to resolve the USB issue. I have searched several threads but all those methods of fixing the usb issue require your EVO to be rooted which mine is not.
does anyone know of a way to fix it without being rooted?
and i can't root my phone because it won't read the USB cable while the phone is booted up into android only in fastboot
Click to expand...
Click to collapse
Trying to follow your problem so I'm assuming that your cable is defective. The OEM (HTC) cable provided with my Evo was defective and I had to torque the cable back at the neck of the connector to get it to work but sometimes it would still disconnect. I just bought another cable from eBay and problem solved, I had it in two days and it was cheap.
well i don't think the cable is defective because i can still connect it to the computer in fastboot and run adb commands thru the fastboot
is there a way to run the usb fix through fastboot usb from adb in the command prompt? i read the thread in which it shows the commands needed to fix the usb not reading but it requires super user and i was wondering if you can run that through fastboot instead
the cable isnt defective, you bricked your phone by rooting it incorrectly.
It's actually really hard to brick a phone. Your phone does not energize when it's bricked, hence the name.
You actually don't need a computer to root your phone so the whole USB cable doesn't have to be an issue. I read a post a while back by XDA users that rooted their phones without a computer and then found this on YouTube. I have NOT tried this but it appears plausible.
HTC EVO 4G from Sprint - How to Root and Unlock Nand Protection - Full Root No PC or ADB.
You have to understand that it's really difficult to give you solutions without knowing most of the parameters of your technical challenge. I don't think your phone is bricked but a defective phone is possible hence its irregular behavior--and I mean defective before you purchased it. But persist with this and you'll find that you'll learn a lot in the process. Good luck.
semperlux said:
It's actually really hard to brick a phone. Your phone does not energize when it's bricked, hence the name.
You actually don't need a computer to root your phone so the whole USB cable doesn't have to be an issue. I read a post a while back by XDA users that rooted their phones without a computer and then found this on YouTube. I have NOT tried this but it appears plausible.
HTC EVO 4G from Sprint - How to Root and Unlock Nand Protection - Full Root No PC or ADB.
You have to understand that it's really difficult to give you solutions without knowing most of the parameters of your technical challenge. I don't think your phone is bricked but a defective phone is possible hence its irregular behavior--and I mean defective before you purchased it. But persist with this and you'll find that you'll learn a lot in the process. Good luck.
Click to expand...
Click to collapse
thanks ill make sure to try this yeah i figured i did screw up the phone myself i doubt the phone was defective because it has worked flawlessly until i tried to root it and it messed up
ok well when i tried to flash the PC36IMG.zip it said update failed! main version is older. then it only gave me the option to reboot or not reboot?
lancerevox279 said:
ok well when i tried to flash the PC36IMG.zip it said update failed! main version is older. then it only gave me the option to reboot or not reboot?
Click to expand...
Click to collapse
I wish I could help you more but I've never encountered this problem. Try this thread? This user seems to be having a similar issue.. (going to read thread myself).
I know there are various threads like this one but my situation is a bit different. I tried using odin to clean install 2.2 to then use the custom rom epic experience. I attempted to install 2.2 using odin but it would get stuck in "setup connection" and I would have to quit and try again. Last time I tried my phone got the "phone connection caution computer" icon and to get into recovery I would have to hold the power and camera button, not the volume down button. When I go to try and install things straight from my SD card I would get an error like "status 7" cus I didn't have the sprint apps to install 2.2. I believe I get these errors installing straight from the card cus I rooted my phone, modifying the kernal cus I read somewhere because when trying to update, it tries to verify but can't cus things are missing or edited cus of the root. I can't try to use odin again because my computer can't recognize the phone anymore regardless reinstalling the samsung drivers. SOOOO, I'm basically ****ing stuck for sure I think. The way I access the SD card is by using an adapter. The only way I see this working is if I find a fix using the SD card, but it's looking slim cus of the stupid root.
I don't know much about this yet, as I'm still learning myself. Did you try using another usb port and are you putting the phone in download mode?. Restart the computer and the phone. Make sure odin is running before you plug in the phone as well. And try another usb port. Are you using the cable that came with the phone? That one trends to have problems for some people.
Edit: I don't believe your phone is bricked either, people tend to throw the word around to much because that arnt quite sure about the definition. Just hang in there and the community will help you get back up and running. Good luck
Sent from my shoe, I mean....Epic shoe... I mean Samsung Epic!
mxcoldhit said:
I don't know much about this yet, as I'm still learning myself. Did you try using another usb port and are you putting the phone in download mode?. Restart the computer and the phone. Make sure odin is running before you plug in the phone as well. And try another usb port. Are you using the cable that came with the phone? That one trends to have problems for some people.
Edit: I don't believe your phone is bricked either, people tend to throw the word around to much because that arnt quite sure about the definition. Just hang in there and the community will help you get back up and running. Good luck
Sent from my shoe, I mean....Epic shoe... I mean Samsung Epic!
Click to expand...
Click to collapse
You see, I'm out of options. Last thing I thought of was installing a custom rom 2.1 rom cus 2.2 roms need odin, but I try to install and I get a signature error or whatever. I'm about to throw the phone against the wall, crack the screen, and use my warranty and get a new phone cus I literally tried EVERYTHING. I spent my ****ing 8 hours of my saturday trying to fix this.
Try a different computer my new Dell XPS 9100 will never reconize my Epic, however, my wifes laptop will always reconize it. I know that sounds weird, I always thought I had a poblem with my phone but it ended up being my computer.
Sent from my SPH-D700 using XDA App
cbpagent72 said:
Try a different computer my new Dell XPS 9100 will never reconize my Epic, however, my wifes laptop will always reconize it. I know that sounds weird, I always thought I had a poblem with my phone but it ended up being my computer.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
omfg, I used my mom's lappy and the drivers worked. Meaning I can try and use an odin fix.
Odin can be tricky to use because of a few factors other than itself. 1) if you can, use a deskto pc and attach to a usb port literally on the motherboard, no front or pci, this may work, but this I what I found (reading countless threads) to be the most failsafe for everyone. 2) your sammy usb cable is for charging or non critical data transfer ONLY, as it is garbage... repeatedly proven in the threads. 3) reboot pc and phone, boot phone into download mode, (hold down 1. On physical keyboard and press power... DO NOT CONNECT YET! Start up odin, place files where needed (.pit, etc...) uncheck all but what you're told in the flashing instructions with the file you're flashing, most have awesome detals, but sometimes your little issue is resolved on page 50 of the thread... not in the OP. Ok so now plug in the usb connection, odin should find it. If it doesn't, search for drivers, uninstall, reinstall start over, OR you have a bad connection, refer back to usb port and cable. I have 1 out of 4 mobo usb ports that the drivers will maintain a connection to, so try another. Then, once odin has a connection, make sure you're following the guides to the T (and read all the posts)... after that, odin is your best friend. The problem lies elsewhere... odin is the goods. If you have run into problems maintaining connection, and plan to re-root, read all the one click posts and if it drops connection a lot, enter the commands in one by one, repeat if one fails till it sticks. There are way better guides, but you seem to have run into the same issues I did, and after hours and hours, I got that scary ass reconnect me now screen. Just read the whole threads, and if your problem hasn't already been resolved, post in the appropriate thread, so others may learn from your discoveries!
Don't give up, once you figure out the quirks of the relationship between your pc and phone, and of course meticulously follow instructions, your elation when successful will make you forget that pesky 'bricked' screen... trust me I got it too, and no matter how much everyone says you can't brick these following instructions on here... its still scary till it all works. If things are wonky, wipe, go back to DI18 and start over... or just sit tight for froyo roms... good luck!
Oh, and sorry for no links, but it would seem you've probly already read em all... not sure I can do links...
Maybe its just my eeepc that doesn't like the drivers, good luck! Sounds like you're on the way... oh don't forget with the drivers to let em install on connect, leave it plugged in for like 10 mins, unplug, it will then complain it wasn't done, reconnect, then after that finishes, reboot. Crazy drivers...
At least I got a computer recognizing my phone, so I can try and use odin. I've been trying to use this fix
http://forum.xda-developers.com/showthread.php?p=9755894#post9755894
and so far odin has been stuck at this one step "file analysis..."
Yeah I used that method to no avail, but it was about 3 pasts old at the time, so I figured id try
something more stable. Tried a couple dk17 roms, then went back to 2.1 and am now using syndicate xtreme. Id suggest going back to DI18, then go from there. Let me check for another post of mine, theres a dialer code I had to do too at one point...
Ok when doing one click root, someone suggested ##8778# in the dialer, then keyboard enter, then set UART to pda not modem. This and removing comodo firewall, all the sudden my intermittent connection was solid. Not responsible for what this does, but it worked for me. Never found out what it does..... still curious. So this may help you even in odin, try to flash di18 after doing this, then the all in one rom you're looking at...
Oddly enough, I managed to semi-brick my phone several hours ago - my wireless adapter was on the same USB header, and both the wireless adapter and the phone crapped out while trying to flash with Odin.
Thankfully I was still able to get into download mode, and plugging the phone into a different USB port worked fine.
After some more research, about 10 hours of it, odin finally cooperated with me after I downloaded about every kind of file that could make my phone work and finally got it into 2.1
I first flashed the stock kernal to get it working, then flashed stock 2.1
Now I'm that my phone isn't rooted anymore I tried installing 2.2 through the recovery menu and I still get error status 7. Any ideas?
Probly best to post in the thread for the package/rom you are trying to install... others using it should be able to help... or you can do a 2.1 rom and wait for a final froyo based rom... glad to hear you're not bricked... the only way I've heard you can absolutely do that with these is installing a GSM rom or something crazy like that... but non-functional phone is scary regardless...
ungovernable1977 said:
Probly best to post in the thread for the package/rom you are trying to install... others using it should be able to help... or you can do a 2.1 rom and wait for a final froyo based rom... glad to hear you're not bricked... the only way I've heard you can absolutely do that with these is installing a GSM rom or something crazy like that... but non-functional phone is scary regardless...
Click to expand...
Click to collapse
Alright I completely fixed my phone. After I rooted my phone on 2.1, I then used odin v1.6 to install the froyo .tar file into pda and it worked. I then rooted it again so now I'm back to normal. Honestly, I did so many things I forgot what I did but I now have my phone functional. Thanks for help everyone, I greatly appreciate it!
Okay first of all, let me start by saying this is my first post and I AM a noob, so be patient.
Okay, my problem is that I can't root my Sprint Samsung Intercept. I've tried SuperOneClick, Z4Root, Universal Androot, and some other one. NOTHING has worked. The SuperOneClick somewhat worked, it installed SuperUser but when I downloaded apps that require a root, they said my device isn't rooted.
I'm with Sprint and running 2.2.1.
Pease help because this is driving me crazy!!
i dont know how this stuff works either but my brother has that phone. it could be your usb isn't reading. or rather, your computer isn't recognizing the device. google samsung intercept usb and you'll see a lot of issues. this may not be your problem but its better to tell you just in case. so far for his cell phone, because he wants to tether it to his computer, so far nothing works. not downloading the right drivers. loading without debugging. mounting the sd card. thats one big solution that hasn't worked. i have high hopes for this other fix, to load samsung pc studio. New_PC_Studio_1.4.0.IL2_4.exe is the file. you can google and find it.
this site has some info. if it works and i remember to, ill repost and let you know.
en.kioskea (take out space, insert a dot)net/forum/affich-240949-samsung-sgh-f480-usb-driver-problem
hope this helps. if not then good luck. and heck if anyone else knows why exactly it does this and a real fix other than the whole disable usb debugger issue. then let me know. i even thought about trying to load the sdk for android to see if that would create some sort of connection with the phone and computer. thanks and take care
hope this helps
sdx-developers is the best place for intercept developement
http://forum.sdx-developers.com/int...ructions-on-rooting-spring-samsung-intercept/
follow the first step to get SWUpgrade setup (the rest is instructions for eclaire [pretty sure])
http://forum.sdx-developers.com/int...-2-2-(easy-root-via-swupgrade)-(battery-mod)/
flash this kernal with SWUpgrade and youll be rooted.
http://forum.sdx-developers.com/int...important-features-working!)-(updated-11311)/
i assume youll be wanting a recovery as well i recommend cm01 get the tar and flash it just like the kernal
intercept doesnt have many custom roms but there is tons of mods you can apply to the stock rom
I tried SWUpgrade and I bricked my last phone but it didn't matter because it was already defective.
Sent from my SPH-M910 using XDA App
did you patch SWUpgrade? delete everything in the binary folder except the file you were trying to flash?
ive never had a problem with it. it even saved me from quite a few softbricks in the short time ive had my intercept.
I did everything the videos and forums said to do. When I did that I got a different kernal but I couldn't get any service, my phone would restart every 2-5 minutes, and it would randomly vibrate. Until I got another one. I finally got SuperOneClick to get passed the "waiting for device" stage and I supposedy rooted my phone, when I tried to install apps that required root access they said my device is not rooted.
Sent from my SPH-M910 using XDA App
So I want to root my phone, but I cannot get ANY computer to recognize the phone when it is in either download mode, or debug mode.
I'm running Sprints stock EB13 right now.
I've downloaded the samsung drivers and installed them.
I've tried 3 computers -- A XP 32bit, a vista 64bit, and a 7 64bit system. I've also tried 3 different cables. Nothing works.
The phone is recognized fine in mass storage mode.
Tried restarting the phone many times, removing the battery, etc.. same with the computer side of things.
I'm out of ideas to try and can't find a good post with a fix.
Thanks for any input!
syntax_erorr said:
So I want to root my phone, but I cannot get ANY computer to recognize the phone when it is in either download mode, or debug mode.
I'm running Sprints stock EB13 right now.
I've downloaded the samsung drivers and installed them.
I've tried 3 computers -- A XP 32bit, a vista 64bit, and a 7 64bit system. I've also tried 3 different cables. Nothing works.
The phone is recognized fine in mass storage mode.
Tried restarting the phone many times, removing the battery, etc.. same with the computer side of things.
I'm out of ideas to try and can't find a good post with a fix.
Thanks for any input!
Click to expand...
Click to collapse
what are you running on your PC that you want to connect to the phone with?
Odin (in download mode?)
ADB in debugging mode?
What exactly are you trying to run ??
jdelano said:
what are you running on your PC that you want to connect to the phone with?
Odin (in download mode?)
ADB in debugging mode?
What exactly are you trying to run ??
Click to expand...
Click to collapse
I wanted to use Odin to go back to DI18 at first. After that didn't work I tried ADB in debug mode, and that no longer works!
I know ADB in debug mode used to work when I was on DI18 because I used it before when I first got my phone. Now I've upgraded to EB13 from the file samsung provided on their website. I've also tried a hard re-set of the phone and that didn't help either.
I had a similar issue. I was able to resolve it by creating a fresh user in windows and then running it from there.
Sent from my SPH-D700 using XDA Premium App
iil said:
I had a similar issue. I was able to resolve it by creating a fresh user in windows and then running it from there.
Click to expand...
Click to collapse
umm..yeah three complete different computers?...I don't think thats the case.
syntax_erorr said:
So I want to root my phone, but I cannot get ANY computer to recognize the phone when it is in either download mode, or debug mode.
Click to expand...
Click to collapse
I had this exact problem with my Epic also. I tried rooting my fone too, for like 2 months straight, with no luck... Tried every technique, software, and trick in the book and nothing worked...
2 days ago though, I finally rooted it using this solution:
Forget about trying to "root" it.
Instead, flash the "Stock EB13 Deodexed EXT4 + CW 3.0.0.6" to your fone (search the forum, you'll find it and the thread that explains how to do it).
It's pre-rooted too!
It worked fabulous for me. I am now rooted and well on my way to fully customizing my fone.
Odin is finicky though... I had to switch the usb cord around to several different ports before it recognized my fone. Also, it kept locking up at a certain point in the flashing process, but after moving the image from "Phone" to "PDA" (you'll know what these are once you open up Odin), it worked brilliantly.
Try it, it works!
P.S. Just in case this helps anyone; I should note that originally I upgraded from Eclair to the official unrooted straight from Samsung (before they pulled it) stock Froyo. I loved it, but wanted it rooted.
I read somewhere that it was easier to root it if you reverted back to Eclair first. So I did (search forum for uninstalling Froyo).
And from Eclair, I flashed to the above mentioned rooted and deodexed version of Froyo (EB13).
Hope it helps!
syntax_erorr said:
I wanted to use Odin to go back to DI18 at first. After that didn't work I tried ADB in debug mode, and that no longer works!
I know ADB in debug mode used to work when I was on DI18 because I used it before when I first got my phone. Now I've upgraded to EB13 from the file samsung provided on their website. I've also tried a hard re-set of the phone and that didn't help either.
Click to expand...
Click to collapse
Might try looking at the usb on the phone to check for something preventing a good connection; I've read where people have found bent connectors and were able to fix it.
Good luck; that has to be extremely frustrating.
I tried everything like you, multiple cables, multiple computers, EVERYTHING!!!
I finally broke down and took it to sprint and they couldnt even get it to connect or fix the problem so i got a new epic. You might just want to take it back and get another one. Im on my 3rd epic now so that should tell you something about these ****TY phones...
My friend has the samsung intercept and I was going to help him root it. I have tried Z4root and gingerbreak but they didn't work.
Does anyone have a site on how to root? Or instructions?
I am a very experienced android user and I am very comfortable with ADB if it is needed.
Anybody know?
Let's try again. Does anyone here know?
S.D.X. Everything you need to know for the intercept
Yes I found that method as well. We tried that about twenty times along with another 1 click at xda, z4, and gingerbreak. Is there an Adb method? Also, would rageagainstthecage work?
Jmoney47 said:
Yes I found that method as well. We tried that about twenty times along with another 1 click at xda, z4, and gingerbreak. Is there an Adb method? Also, would rageagainstthecage work?
Click to expand...
Click to collapse
S.D.X. is a website S.D.X. developers They have several guides to rooting.I rooted mine with a programed called sw updater with my pc but now ther are easier ways.
Ok thank you I will check it out
You're going to need to run one (or several) of the root exploits (until they 'take') and then edit some files manually via adb to make it permanent. See the SDX Developers website as previously noted.
It won't let me post a link but Google this...
how-to-install-custom-kernelrom-on-your-intercept-using-cm01-recovery
I did it with SWUpgrade Tool, but...
1) Even though I could connect and swap files between my phone and my computer over USB, SWUpgrade for some reason would not recognize my USB connection on Windows XP SP 3. This page along with the Samsung driver link on the same page saved my ass...
Google this - Troubleshoot driver error June Fabrics android
2) With the SWUpgrade you have to be really quick and unplug the USB and take out the battery when he says to, or you will not get the custom recovery installed. It took me about 4 tries before I was able to get the custom recovery in my phone.
I previously did the rageagainstthecage method, and while it worked, at one point I stupidly took out the battery when it froze before I had put in a custom recovery and done a backup and I very nearly bricked my phone. It would not bootup after that no matter what. Fortunately I was able to boot into the Virgin Mobile recovery and start from scratch wiping and resetting my phone, but I had to re-download all my apps from the Market all over again which fortunately the Market kept a record of.
I used the first link for the kernel and I am very happy. Just take it slow, be careful, and follow the instructions exactly.
Rooting using ADB Tool Manual Method
Please see my post in the following thread:
http://forum.xda-developers.com/showthread.php?p=13849534#post13849534
Ok guys thanks for the advice however I have been having one problem:
I cannot seem to get the drivers installed successfully on my computer. It is windows vista x86. I have tried the easytether drivers and the samsung drivers but for some reason they don't work. Any ideas?