Related
someone please tell me what does ADB stand for????????
i hate myself for being such a noob but what can i do?!?!?! whats adb pleaseeee...
and why is it that everytime i go into command prompt to try and do stuff with the phone it never finds "androidsdk"
ahh!!!!!
Frenzifun said:
someone please tell me what does ADB stand for????????
i hate myself for being such a noob but what can i do?!?!?! whats adb pleaseeee...
and why is it that everytime i go into command prompt to try and do stuff with the phone it never finds "androidsdk"
ahh!!!!!
Click to expand...
Click to collapse
How about you tell everyone what you are trying to do, and what you are typing in command prompt.
Android Debug Bridge....
Do you have Samsung drivers installed/setup?
Take a nice deep breath and do one learning step at a time. Android has a lot to teach. I would also encourage learning the phone use basics, reading up on things before attempting any mods. Welcome to android family.
Here is a good thread to start in.... http://forum.xda-developers.com/showthread.php?t=790004
tats_06 said:
Android Debug Bridge....
Do you have Samsung drivers installed/setup?
Take a nice deep breath and do one learning step at a time. Android has a lot to teach. I would also encourage learning the phone use basics, reading up on things before attempting any mods. Welcome to android family.
Click to expand...
Click to collapse
lol ... well i already opened another thread about how to put hebrew fonts on the phone to support hebrew instead of seing empty boxes on facebooks and websites and what not... my phone Was rooted, Was voodooed but there was force closing on things and market stopped working so i completely stocked the phone, only thing that doesnt work now is my phone memory which is on 0.00 which i read and you apparently have to root the phone all over again
so right now... the phone memory is my only issue, i guess i can live without hebrew if its too much of a hassle to install while rooted::
http://forum.xda-developers.com/showthread.php?t=480964
i have no idea how to work this^^^
i have the drivers installed like i said, i was able to odin, root, and voodoo, clockwork as well ofcourse. now phone is completely stock except for that memory issue.
http://forum.xda-developers.com/showthread.php?t=804457&highlight=phone+memory
completely got lost in this thread... so yeah, those are my problems with the phone at the moment. i wont mention the obvious of gps etc.
another awesome issue, everytime my phone is turned off and back on, it starts that set up process all over again... language; facebook; google... etc... why?
Once you install adb on your computer you have to go to change the path on your computer to point to that folder. Or you can change your directory to the one that holds the adb file from within the command prompt. This should allow you to run the commands.
The issue you are having with the memory on your phone is because voodoo did not completely uninstall. You can fix this by running the steps in this forum to uninstall voodoo. Don't try the one step zip, you are going to have to do the three step manual method to make this work. Don't forget the final step to wipe data.
Once this is done voodoo will be gone, memory should be back, and phone should stop resetting on every boot.
Obviously you aren't the only one to ever have these issues. But you can recover.
Good luck.
Sent from my SCH-I500 using XDA App
No intro
Here is what I did:
Wanted to flash new ROM, [ROM] Super Clean DI01 + AOSP apps, (Thanks to everyone who worked on it AND everyone on this forum cause Ive spent the past week reading the threads and felt confident enough in the info and the support to try).
BUT
when trying to download with ODIN (not certain if this was the right method, too late now) found that it did not work, couldnt see file when looking in the PDA browse.
STUPIDLY disconnected phone from computer while in DOWNLOAD MODE. You know, when the screen says "DONT DISCONNECT FROM TARGET". Apparently, the rebus string for "you dun f*cked up" is a phone symbol... a yellow triangle w/!...computer symbol.
What do I do to get back to fun?
Tried reboot, tried CWR reboot, tried Nandroid restore w/reboot still the YDFU symbol
*EDIT* I continued searching while awaiting a response and found this thread: Stuck on connection warning screen. This got me out of the YDFU screen into a nice force loop. Since I am not a -complete noob- I pulled a nandroid backup outta my hat and ...tada back to good, now to the fun!
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!
Ok, I want to leave a message on here for future noobs like me with a Galaxy S
i9000 but it might work for others too.
My issue when flashing custom roms is that I have not been able to access my galaxy from my computer via usb since literally day 1 (when it did work once).
I spent a week trying to connect to Kies on multiple computers (vista and Windows 7). Tried via Android SDK, even tried hiemdall. I almost tried in ubuntu also but I never did get that working as I really don't know linux well enough. I've now given up...
So then I saw that you can do flashing all on the phone with the clockwork mod. With clockwork, my first rom flashed, well, like clockwork! But then I had some issues with lag and hang ups and reception and I decided to switch to another rom (seearms jl2 based rom - good stuff so far).
However this rom install went sideways... It said that it had installed ok but on reboot it stalled on the Galaxy I9000 screen and froze. Luckily I could still use the 3 button recovery to boot to clockworks but the hitch was that I HAD NO OTHER ROM to flash back to.
I had done a backup through clockworks but when I tried to restore it said the systems.img file was missing so it skipped it and the end result was the same freeze.
Normally everone says to reflash at this point with odin but that was not an option for me. So this is where I got lucky. The SeeARMs rom included Steam recovery module (though I thought it was the stock 3 button recovery menu for a while - I was panicking a little). I highly recommend seeing if you can get steam because it allows access to the External SD card for flashing which can be a lifesaver. Ahh, finally I could get the old rom on that, reflash it and go one with my life. My theory being that at least the issues would be aligned with the this rom and it worked.
So the lessons I learned:
1) Always have your new rom and your old rom on the interanal SD card in case of issues.
2) check your nandroid backup - even try testing it? - they don't always work perfectly with every device.
3)I highly recommend finding out if Steam or similar will work if you cannot access the USB connection and load things on when things go wrong.
Some tips I saw that also worked for me
1) flash a new kernel before you flash a new whole rom.
2) if things go sideways, try redownloading or retransferring the file to make sure there were no errors.
I did both and then reflashed (with my old rom Voodoo Doctor, SeeArms Rom and Darky's 8.1 rom on the card just to have options) and all was good!
PS: the steam recovery knocked off the first letter of the file when executing for some reason so I had to make 2 copy's of each rom I wanted access to ie Darkysrom.zip and arkysrom.zip just look for that error when you are doing this.
Good post - hopefully it'll help someone out who's stuck.
Hopefully
I'd like to stick some of that in on the thread for your rom but I need put another 7 half relevent messages out there before I am worthy... I understand the rule but I'd rather only post where it is meaningful...
GF
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...
Hi guys, Last night I accidently unplugged my phone while installing ClockWORKMOD recovery. Now when I boot my device it is stuck on the Downloading screen. I tried everything including the posts here but the Odin software doesn't see my phone and removing the battery and reinstalling does nothing. I even wiped the phone and factory reset via the clockwork... No Luck. It will not install the Crash ROM either. I get error 7.
It seems like I bricked the phone but I know there is always a way back to life. At least I hope. Any help guys would be great.
thxs
Carlo
shpack said:
Hi guys, Last night I accidently unplugged my phone while installing ClockWORKMOD recovery. Now when I boot my device it is stuck on the Downloading screen. I tried everything including the posts here but the Odin software doesn't see my phone and removing the battery and reinstalling does nothing. I even wiped the phone and factory reset via the clockwork... No Luck. It will not install the Crash ROM either. I get error 7.
It seems like I bricked the phone but I know there is always a way back to life. At least I hope. Any help guys would be great.
thxs
Carlo
Click to expand...
Click to collapse
You need to properly install the correct drivers on your PC. There should be no reason that ODIN doesn't see your phone if they are installed correctly. A quick search of the forums should get you the proper drivers to install. You can also try Kies emergency recovery, but it is hit and miss. Good luck.
+1 if you can get into download you can Odin. Use the usb ports in the back of the pc. You might have to use a different computer also. For the life of me I can't get Odin on my pc to recognize the device but I have no problem with my laptop.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Wow, didn't we just fix this problem like 2-3 threads ago, IN THIS FORUM?
TheAxman said:
Wow, didn't we just fix this problem like 2-3 threads ago, IN THIS FORUM?
Click to expand...
Click to collapse
That's the thing, these exact same types of threads just keep rolling through one after the other...people don't search and they don't read. That's the reason they are in the situation they are in to begin with and it seems they just don't learn.
Fortunately, the AT&T S4 forum has come far enough along that the sticky threads and the threads like your guide can be linked for these people to put a little time into finding a solution for themselves. Most of them don't like it (they want it done for them), but if it is all they get, they will finally have to do something the right way on their own.
Actually, a few people are thankful for being pointed in the right direction, but most are still pissed because it means they have to do what they should have done in the first place...follow XDA rules, use the search function, and read. If you don't do everything for them and hand it to them on a plate they call you names and say you are a ****, unhelpful, etc... I just laugh about it because it becomes clear why their phone is F'ed up in the first place. The thing is, sometimes you just can't help people. Just every now and then, someone comes along that needs help and is willing to do things the right way.
You can NOT have kies drivers and samsung drivers loading at the same time, I do not use kies at all, and my pc has NEVER gave me a issue yet using odin, including in my G3 days. uninstall that worthless kies and proceed. If you have to use kies, load it as needed then remove it.
And as always with the lovely microsoft windows, after you un-install anything you have to reboot, for it to work properly.
Linux is my BUD!