I was running AOKP 38 when the battery died. The phone got stuck in bootloop and when i tried restoring from cwm I lost the ability to boot into ANY RECOVERY!!!
When i try odin, it wont recognize the phone and both my pc's give me the message that the usb device isnt working.
Please helppppppp
Sounds like you don't have the right USB drivers installed on your computers.
Sent from my SCH-I500 using Tapatalk
i've already unistalled and reinstalled the samsung drivers. when i plug the phone into pc, i get the windows error message that the usb device is malfunctioning and windows has stopped it.
You are in download mode, right? It's just that it's better to rule these things out and you didn't specifically say that it was.
I cant even 3 finger into recovery!!! The phone just continuously runs the samsung screen.
Remove the battery, then hold volume down and plug in the USB cable. Do you see a yellow triangle?
yes, the yellow triangle comes on
Let me explain a little further. Ive been running AOKP 38 and on thursday I let my battery fully die. The phone never came on again. I have done a nandroid backup and everything is also backed up in Titanium. The phone will not boot into recovery nor will phone boot at all. ODIN wont pick up my phone and I've bought a new Samsung chord and reinstalled the Samsung drivers. Still nada.
Try a different USB port. Also, give Heimdall Suite a try.
ok so i went out and scored a sweet fassy. Brought it home, hooked up to pc and it picks up!!!!! Go figure. Im sooooo lost
Shelby is probably right. You need to install the Google USB driver from SDK Manager.
Sent from my SCH-I500 using xda premium
mikey71 said:
ok so i went out and scored a sweet fassy. Brought it home, hooked up to pc and it picks up!!!!! Go figure. Im sooooo lost
Click to expand...
Click to collapse
My laptop totally recognizes my sister's stock fascinate, but stopped recognizing my fascinate after a similar low battery / bootloop situation.
I had much success using a totally different computer to flash with odin or heimdall. I had to try 3 diff pcs until i hit paydirt.
To this day, the two laptops I used all the time for my fascinate no longer recognize it, yet other pcs recognize & odin fine. Likely other programs interfering with USB. Either way, way easier to borrow someone's pc, than to try & troubleshoot what is up with the usb connection.
At least you can get into download mode. That's half the battle right there.
Try another pc or possibly heimdall & good luck
You are not alone, others have come back from this. http://forum.xda-developers.com/showthread.php?p=28326672
Sent from my SCH-I500 using xda premium
Related
I have CWM 3.0.8, and want to get back to the red recovery, so that I can flash a new rom on my fascinate. The problem is, that I can not for the life of me get my phone to show up on Odin. I have tried on two different computers. I have used Odin on both computers for this phone, so the drivers are all installed. Any ideas? The rom I have now is a force close nightmare. I would like to get back to something that is stable.
Thanks for any help,
Brad
bradbradbrad said:
I have CWM 3.0.8, and want to get back to the red recovery, so that I can flash a new rom on my fascinate. The problem is, that I can not for the life of me get my phone to show up on Odin. I have tried on two different computers. I have used Odin on both computers for this phone, so the drivers are all installed. Any ideas? The rom I have now is a force close nightmare. I would like to get back to something that is stable.
Thanks for any help,
Brad
Click to expand...
Click to collapse
Follow this guide.
http://forum.xda-developers.com/showthread.php?t=1001064
Sent from my SCH-I500 using XDA Premium App
Ive used odin before, I just cant get the fascinate to be detected by the computer. It wont even mount the sd card via the usb cable to transfer files. I got the phone in download mode, connected to the computer through the usb cable, but can not get the yellow "added" dialog in odin so that I can flash the .tar file...
Thanks for the help so far,
Brad
Maybe a stupid question but do you have Odin open before you plug the phone in.
Sent from my SCH-I500 using XDA Premium App
You can also try to reinstall drivers or even odin check to see that you have odin 3 1.3 and maybe reinstall odin it can be found here in one of the forums.
I have tried it both ways, going into download mode, then opening odin, and first opening odin, then going into download mode.
Now, I have another problem. I was able to do a data wipe, which stopped the force close loop. I was then able to get my phone workable at least. Then, while resetting everything, I dropped it on my coffee table and the touch screen will not respond. The phone's soft keys work fine and i can turn it on, but have to do a battery pull to turn it off. I have tried turning off/rebooting, and again doing a data wipe. I don't know what else to do other than take it in, but I don't think that is possible since it is rooted
I was trying the new CyanogenMod 7 on my Vibrant. I was trying to restore my old ROM through Nandroid since CM7's GPS isn't working yet. I'm guessing I should of flashed another kernel first, but now my phone won't get past the Vibrant screen. Won't even get into recovery.
Here is where it gets tricky. My phone isn't recognized by windows. I'm having the same problem as here: http://forum.xda-developers.com/showthread.php?t=777696. So I can't flash new firmware through Odin. I have the drivers installed on multiple computers and none of them will recognize my phone.
So no recovery and no Odin. What do I do?
This is odd. Have you re-installed the drivers? I can fix this for you if it comes to it with JTAG also btw so be sure to PM me if it comes down to it.
Pull battery..hold up/down volume button..plug it into usb cable while holding volume button down then insert battery
do you have installed the drivers for nexus s
cm7=nexus s
Thanks for the suggestions,
I have the drivers installed and the phone has been able to be recognized for a while. I haven't been able to mount my SD card for some time now.
I did the battery out, cable in, hold buttons and all that. I can get the phone in to download mode no problem, but that's as far as I get.
I haven't tried Nexus S drivers. I'm not sure it will work since computers haven't been recognizing my phone way before CM7, but I have nothing to lose at this point.
ok first post so i wont waste any time getting to my problem, how I caused it and what i have tryed to fix it.
i have a vibrant running 2.2, last night i tryed to root using aio toolbox not knowing it only worked for 2.1(my mistake).. so heres what happened it boot my phone into download mode and from there i tryed to install packages only to get a error about signature so i reboot my phone and tryed to use odin to downgrade only to realize that somehow i screwed up my phones ability to connect to pc, it charges but does not go in debugging massstorage etc, so from there i went back into download mode and tryed to reinstall packages only to get error about missing update.zip, i dont have superuser and dont know how to get the update.zip back without usbmode or superuser. ive tryed everything else, it will detect my wifes vibrant but not mine. i know its my phone not the pc/usb/drivers etc etc PLEASE HELP NEWBERT
just keep trying odin to get back to 2.1
my usb's dodgy aswell, charges and takes like an hour or 2 before it actually comes up on computer and phone saying its connected
i messed up mine the other day and it took me like 2 hours of trying to get it to connect to odin going through all 4 of my usb ports like 10 times each but it eventually did it so just keep trying
try different ways:
pull battery out and connect usb and open odin
hold vol up and down and push battery back in and it should go to download mode
or
leave battery in, open odin hold vol up and down and plug usb in and that should go to download mode
mine only works with the 2nd way for some reason, the 1st way seems to work for most people though
ive tryed this it will go into download mode but odin wont detect it, i think its something with my drivers on my phone. im completely new to this but i know it worked flawlessly untill i tryed to root, im not sure what went wrong besides i used aio toolbox intended for 2.1 on 2.2
Odd. I have never used the AIO Toolbox, never felt the need to, but yes, if you are able to get into download mode, but ODIN is not recognizing, it does sound like a driver issue.
You may want to uninstall/reinstall (here are the drivers, be sure to note the 32/64 tabs) LINK
Also, make sure you have the latest ODIN (check my going back to stock guide)
You might also want to make sure the pit/tar you have for JFD are good by checking the md5, I use hashtab to do this. (I realize you are not at that point yet).
Try rebooting your PC, pulling your battery and waiting a bit... trying different USB ports, be sure to remove other USB devices too before rebooting your PC (my ODIN will NEVER work with my webcam hooked up).
If that does not work, wonder if other drivers would help...
+1 follow above
- So the phone won't boot completely? That sux!
- If it did you could bluetooth the update.zip from her phone to urs.
.....but.......
- It automatically boots into recovery?thats odd
***How are you getting into Download mode?(the yellow triangle with android dude shoveling) Button combo maybe?
I'm pretty sure i have attempted every solution on here (XDA) and elsewhere to troubleshoot my problem. I am hoping it is obvious, but i've put hours into this and i could really use some help!
My tablet is (or was) a Verizon 4G LTE Galaxy 10.1
I had successfully rooted it when i first got it using Odin...i flashed a ROM...can;t remember which one (obviously a wrong one) and ever since it has been rather temperamental.
Over the course of the past week i have been to APX and back... Heimdall (which i am pretty sure i am not doing correctly) to attempting to flash firmware..stock roms etc...
I don;t know whether it is a driver issue, or if i need a stock rom or to flash firmware....but here is where i am at now.
If i try to power up normally...the Samsung galaxy tab logo bootlader flashes for a sec or two...the screen then either goes black...and repeats a few times...or sometimes it flashes the logo and the backlight stays on until i turn it off.
(Seems to be a fairly common problem)
If i hold the volume up and power together...i can get to the Odin download screen with the flashing droid and the midget droid that appears to be walking away from a trash can.
HOWEVER, when i plug the tab into my laptop (windows 7 x64) (i also have access to a (windows 7 x86) and my girlfriends xp machine. I've tried on all mostly on my x64 machine.
Heres the thing.
When i power down...sometimes just pressing the power button once or twice...sometimes, while off i hold the volume down button for a few sec..and all of a sudden the comp reads the device and i can get open ODIN...get the yellow COM thing...but never seem i always get the same error message...can not open/find com/port...
so i can get into odin on my comp with a black screen on my device...or i can get to download mode on my device and my machine wont recognize it.
I seem to have inherited a little bit of everyones problems on here...
Please tell me that there is hope for my tablet...please help? I'm sure you can imagine my frustration. TY.
joshualectric said:
I'm pretty sure i have attempted every solution on here (XDA) and elsewhere to troubleshoot my problem. I am hoping it is obvious, but i've put hours into this and i could really use some help!
My tablet is (or was) a Verizon 4G LTE Galaxy 10.1
I had successfully rooted it when i first got it using Odin...i flashed a ROM...can;t remember which one (obviously a wrong one) and ever since it has been rather temperamental.
Over the course of the past week i have been to APX and back... Heimdall (which i am pretty sure i am not doing correctly) to attempting to flash firmware..stock roms etc...
I don;t know whether it is a driver issue, or if i need a stock rom or to flash firmware....but here is where i am at now.
If i try to power up normally...the Samsung galaxy tab logo bootlader flashes for a sec or two...the screen then either goes black...and repeats a few times...or sometimes it flashes the logo and the backlight stays on until i turn it off.
(Seems to be a fairly common problem)
If i hold the volume up and power together...i can get to the Odin download screen with the flashing droid and the midget droid that appears to be walking away from a trash can.
HOWEVER, when i plug the tab into my laptop (windows 7 x64) (i also have access to a (windows 7 x86) and my girlfriends xp machine. I've tried on all mostly on my x64 machine.
Heres the thing.
When i power down...sometimes just pressing the power button once or twice...sometimes, while off i hold the volume down button for a few sec..and all of a sudden the comp reads the device and i can get open ODIN...get the yellow COM thing...but never seem i always get the same error message...can not open/find com/port...
so i can get into odin on my comp with a black screen on my device...or i can get to download mode on my device and my machine wont recognize it.
I seem to have inherited a little bit of everyones problems on here...
Please tell me that there is hope for my tablet...please help? I'm sure you can imagine my frustration. TY.
Click to expand...
Click to collapse
Have you tried rhis method
http://rootzwiki.com/topic/7718-romleakodineg01-factory-stock-odin-image-vzw-lte-tab-101/
Sent from my GT-P7510 using Tapatalk
...
Thanks for the quick reply. I think i did try this at one point...the problem still stands...when i am in odin dl mode on my tab...the com tab wont turn yellow and comp wont read my device.
If i do it the other way....with a black screen...it wont be able to communicate or find the port. ...but ill try again right now.
Nope....epic fail. There has to be a solution, right?
As long as you can get into download mode you should be able to fix it. Most likely the issue is not your tab but the drivers on your computer.
I spent the better part of a day frustrated trying to go from the leaked 3.2 to official 3.2 having issues similar to you with Odin. Funny thing is for me the PC somehow ended up not recognizing the tab on the USB port I used to flash on but would on others so I simply swapped Ports and continued. Little did I realize that although things seemed okay that issue was a symptom and Odin was now flashing corrupted info onto the tablet.
A simple reboot of the PC fixed things for me. That you have tried other machines though is worrisome. Still there's a chance it still is a driver issue so I would check drivers on the PC and perhaps install kies if you don't have it to see if the drivers with kies help.
Since you're on the Verizon tab flash back to stock 3.1 and flash stock recovery. Then let all the OTA updates run. After that all you need to do is flash cwm and Pershoots kernel along with superuser to be rooted. There is no better ROM for our Verizon tab than this and all wifi ROMs are incompatible with it.
Still, no luck. When i am in download mode on my tab....my computer doesn't recognize it. When I just power up and and plus it in, the screen goes black but the computer sees the device as well as ODIN. However sometimes it is recognized as APX and sometimes it is recognized as a Samsung android device... usually with one or two driver errors.
So, it seems obvious that it would be a driver issue... i've tries kies, and as many variations of drivers i can find.,.. when in APX mode i try to flash using the nvflash method in cmd or heimdall, otherwise i try ODIN and it seems to be successful until the "setup connection" point.
Is there a way (if it is even something i should do ) to get drivers on my device in its current state?
Im at a loss...i know this thing can be resurrected...everything just seems so backwards. Any thoughts?
I know that this is a very basic question, but do you have USB Debugging enabled?
George
No way to check now, as he says the tablet doesn't boot any more.
It sounds like a driver issue for sure, and to be clear here the ONLY requirement that I know of when flashing with odin on the TABLET end is for it to be in download mode waiting for usb BEFORE being plugged in. So when I say driver issue Im talking about on the PC side here. Have kies installed just to get the drivers, fire up odin and get the tab into download mode while unplugged. Plug it in and watch odin to see if the com port status lights up. If not swap usb port and repeat. Do not use a hub and ypu may want to remove unnecessary usb devices too just to see.
I have an um-rooted samsung galaxy player 3.6 (running gingerbread 2.3.6) I was browsing an app when suddenly it crashed! the battery was low, so at first I thought to plug it in, but before I did, I noticed that it was rebooting every 4-5 seconds. plugged it in, took out battery, tried putting in recovery (put bat. back in, hold power and both volume buttons) but it vibrates and just goes back into boot loop. it pops up with the samsung logo, stays for 3 or so seconds, screen goes dark, then it does it again.
I have been messing with it. when it starts booting, my computer recognizes it as OMAP3630 which google has told me is the name of the processor. It tries to install drivers but fails due to "umplugged device" when it turns off
Weird! If you have data to recover try using adb logcat to see what's going on. Otherwise reflash with Odin. I have only experienced this problem when using heimdall to flash my us yp-gs1, but it happens right after flashing.
What app were you using when it happened?
Sent from my SGH-I777 using xda app-developers app
a Forum app. It has not been flashed either. it is all stock 2.3.6 gingerbread. if i put the battery in then plug it in (without hitting any power buttons) it goes to a loading circle (that does not move at all) and just stays there. the computer does not recognize it in this state. its only 3 months old, but I have no idea where the recipt is!
weird! im sticking with my answer tho, if you want to fix it then put it in download mode and flash it
if you cant get to download mode then buy a $2 usb jig
Tried it! no luck. got it in download mode. ran odin and It said pass! BUT it only took 3 seconds? and then instead of flashing just samsung then rebooting, it started flashing samsung with a caution symbol under it and rebooting. went to do it again and it says suctom binary current binary:custom. so it seems it worked but did not fix my problem
Did you flash normalboot and factoryfs both?
Sent from my SGH-I777 using xda app-developers app
joshkidner said:
Tried it! no luck. got it in download mode. ran odin and It said pass! BUT it only took 3 seconds? and then instead of flashing just samsung then rebooting, it started flashing samsung with a caution symbol under it and rebooting. went to do it again and it says suctom binary current binary:custom. so it seems it worked but did not fix my problem
Click to expand...
Click to collapse
I had a similar problem with the galaxy player 5.0. Took out my micro sd card from it and somehow that worked. Hasn't gone on any reboot cycle since.
I was gonna try the fs whatever one, but now i cannot get my computer to recognize it! i tried another factory reset and that didnt help. i got it to work once. Guess I will have to keep trying? I got school so I cant do it now (16, junior in High school)
yep you'll need to get to download mode to flash it. like i said before, a $2 usb jig will always do the trick (i loooove mine)
I dont have any problem getting it into download mode, my problem is getting the computer to recognize it. gonna have to try it on a dif computer I guess, which is weird, because I got it to work once, but now it wont. I flashed the normalboot the first time, what did i do wrong? should I have flashed the other (fs or whatever is is) one instead? thanks for the help!
When I'm in a bootloop after heimdall testing I need to flash factoryfs. For you I would say flash both. Try another cable/ try another USB port
Sent from my SGH-I777 using xda app-developers app