After having a lot of problems installing froyo when it came, i finally found a solution. But after the update, i can only turn my phone on when it's connected to PC or power supply.
Does anybody have the same problem, or maybe a solution ?
You have pulled the battery out and put it back in (maybe waiting half aminute or so)? Does it work after you disconnect it from the charger?
It might be a battery stats problem. there are som galaxy s users with a similar problem, and a factory reset/wipe has resolved the issue for some people.
here:
h t t p://samsunggalaxysforums.com/showthread.php/3403-Galaxy-S-will-not-turn-on-unless-it-s-plugged-in
Unfortunately it didn't work. also, my adb doesn't work, i can't root my phone and can't use it as a disk drive on my PC
I've tried to downgrade it to Eclair, and tried to use fake-flash, but it says that signature verification failed.
Related
I updated my Fascinate yesterday OTA to DL09 from Verizon and now when I connect to my laptop I get the big bad blue screen stating that it has stopped to protect my computer from damage. I have rebooted 3 time without any positive result. Anyone else having this issue or know of any fix. Thanks
Try putting the phone into debug then try it.
Z an B son!
Yes, I have the same problem...
and we are not the only one's .... http://forum.xda-developers.com/showthread.php?t=911543
I am not able to connect to my MAC
Tried factory reset .. still didnt work...
The Blue Screen of Death (BSOD) is not the same as the problems that people are having with mounting USB.
I have been all over forums today and this is the first I have heard of a BSOD.
In the BSOD will be an error number. Something like a Fatal Error has occurred at xxxxxxxx in module yyyyyyyy
Google the exact error message and see what you come up with.
Fixed he issue
I got the problem fixed. What I found was that the phone was showing up as a cd rom drive and by doing this my PC automatically started opening up CD rom software on my pc that was totally not compatible with the phone LOL. Isnt it just like Verizon for pushing more of there crap on us to screw up the works.
Thanks for everyone's help.
Hey guys I've been watching this forum for a while now and I need some help.
I searched around and found nothing relevant..
I got the latest kies, finally my sgs connected in kies mode, perfect. Popup for update, okay. Now... The first time i did this it showed me some progress bar which was probably something downloading. After that, the phone simply disconnected. Kies didn't show up anything, just that the phone was no longer linked to kies. The phone still showed the mtp application screen. After a few seconds kies shows 'Connecting...' and recognizes the phone again.
The second time it doesn't even get to the progress bar. When I click update, the phone simply vanishes from the kies screen.
I have not applied any lagfixes or anything, haven't rooted my phone.. Actually a few days ago I made a hard reset and everything is smooth. I just want that froyo already, I'm still running eclair.
Please, if you have a solution post it here, or at least point me in the right direction. I'm pretty much a noob when it comes to phones so.. Any help will be appreciated.
I dont know what to say
U already hard reset the phone.
Check with sgs tools what firmware do you have.
In case you have major issues.
Check the three button combo.
Uninstall kies, hard reset and try again.
Maybe is a usb problem .
How is the mount sd working ?
Sent from my GT-I9000 using XDA App
I had a problem just like this and it turned out to be a faulty USB connection. Try a different lead and USB port on the PC first.
Thanks for your replies guys, but unfortunately I still have a problem.
Reinstalled kies, nothing. Hard reset the phone again. Nothing.
Three button combo working perfectly.
In settings, the firmware seems to be 2.1-update1.
Usb problem, I don't think so. The SD card mode works flawlessly. There's one more thing I noticed. When I plug my phone in kies mode, windows also recognizes the phone, showing it up in my computer. The point is that when kies loses link to the phone, windows still finds the phone to be there, e.g. phone disconnects from kies, but not from windows. That's pretty weird..
You guys have any other suggestions..? What is the risk of flashing my phone manually to 2.2? I wanted to avoid that at all cost.
Kies also does not like the phone to be plugged in via any hub. It is best always to plug direct into a system board USB outlet.
Oh forgot to mention. I was indeed plugging the usb cable into a hub, and tried plugging in directly from the motherboard connectors and still no luck.. No idea what to do next.
Might be worth putting the phone into recovery and going to Tools, Emergency firmware recovery.
Well in the 3-button thingy i only have 'reboot system now', 'apply sdcard:update.zip', 'wipe data/factory reset' and 'wipe cache partition'. Halp plox?
Looks like you are left with two routes .
one take phone to service centre
two flash the phone to upgrade .
If flashing i would go the rom kitchen route .
That is only requiring a USB mass storage mode connection to transfer update file to sd card .
jje
I would try it. What are the risks and what happens if something goes wrong? I read somewhere that if I the 3-button combo is working I have nothing to worry about since I can reflash my phone at any given time. Is that true?
To get into recovery it is Home button. DOWN volume and Power on.
You will see a yellow triangle with "DOWNLOADING" Do not turn off the target. When you have this and have opened Kies just plug the USB in and use the recovery option if you can. As with all flashing there is always a risk so do this if you are prepared to accept this.
I've been doing a bit of research and as I saw around the only way you can mess up your flash is simply by disconnecting the cable when you shouldn't. I never actually saw anyone on different forums that have failed flashing so.. That thing pretty much gave me some courage, like hell..
I found a guide which I think would work:
http://samsunggalaxysforums.com/showthread.php/2921-How-to-use-Odin-to-upgrade-to-Froyo-from-Eclair
Do you think this is okay? Also the guy sais we should check *#1234# for PDA, and mine seems to be I9000XWJFB. He said we 'should be on JM1, JM2, JG1, JF1 etc...'. I assume that my phone falls into that category?
If this guide is erroneous please point me in the right direction, if you could.
Hi
I have an HTC Legend, but it's so buged
When i try to turn it on, it has to be connected to a cable, or else it goes into bootloop.
I've tried to make a factory reset, tried to install a different RUU, tried to downgrade it, but the adb shows no devices.
I've run out of ideas, so please help me
Somehow I managed to get the same issue. It goes into bootloop unless it's connected to a pc... I already went back to the stock 2.2 rom and deleted everything but nothing changed.
Funny thing is that after I got this problem I first installed the old 1.31 rom and that one worked without the usb cable. The 2.05 to. But as soon as I installed the 3.14 it started again with the bootloop thing...
Did you find any solutions?
Ok, after installing the stock rom I noticed that the usb is not working so I just needed to unbrick the phone and that solved a problem.
(I just did not think about that before because usb was still working when I installed cm7 but the bootloop problem was already there.)
CrWEE said:
Ok, after installing the stock rom I noticed that the usb is not working so I just needed to unbrick the phone and that solved a problem.
(I just did not think about that before because usb was still working when I installed cm7 but the bootloop problem was already there.)
Click to expand...
Click to collapse
What exactly means unbricking the phone?
I got simillar problems: since CM7 final I have bootloops when my phone isn't connected to power. Also I can't mount the sd card from a computer (when I press the button on the phone it works for like 5seconds and then unmounts again).
I already tried downgrading again to CM7 RC4 and other versions(I always wiped before), but the problem persists. Also upgrading to another radio version didn't work .
virus54 said:
I have this problem too
but i found one way to stop this rebot loop util u reboot your phone again...
enter into recovery mode and via adb write the command
adb devices
Click to expand...
Click to collapse
now press volume up and power button(when you see black screen with phone)
press on reboot system now and it will work for you for one time
each reboot you have to follow those steps
Click to expand...
Click to collapse
after this do a usb brick to use your usb http://android.modaco.com/content/h...com/309961/usb-brick-rickrolled-b0rked-fixed/
I had exactly the same problem, the USB unbrick linked to above solved the problem. If you need the image hex edited for you give me a shout
My galaxy s was hanging on boot (at the big S logo). This wasn't the first time and last time I had tried everything and reflashed. Yet this time odin crashed (windows gave me the 'Odin.exe stopped working' notification) and my phone powered off...
Now it won't give me anything, not download mode, OS or recovery (screen stays black, not even sure if the phone boots at all, hardware buttons also stay off)
Couldn't find anything usefull, any thoughts?
Cheers
Try the JIG to force it into download mode and try again. If odin crashes again, try flashin within windows safe mode. Sometimes it prevents crashing
mrjraider said:
Try the JIG to force it into download mode and try again. If odin crashes again, try flashin within windows safe mode. Sometimes it prevents crashing
Click to expand...
Click to collapse
Will that force the device to boot too? If thats true I will give it a shot this week, hopefully. See if i can get hold of one somewhere.
Thanks for the quick reply
tinyhitman said:
my phone powered off...
Click to expand...
Click to collapse
I Think this is the problem, you may have tried flashing when you had little battery charge and that will cause serious problems as bootloader would have failed.
your only option would be read the My Android Solutions about Problem:- Cannot enter Download or Recovery Mode
xsenman said:
I Think this is the problem, you may have tried flashing when you had little battery charge and that will cause serious problems as bootloader would have failed.
your only option would be read the My Android Solutions about Problem:- Cannot enter Download or Recovery Mode
Click to expand...
Click to collapse
EDIT: I thought it was weird indeed that my phone powered off, since it had a full/near full battery (at least it told me)
Great thread ! Yet unfortunately none of the steps work for me up untill the JIG, I'll have to get hold onto one or make a homemade one (only got a single micro-usb at the moment, so that'll be a sacrifice) Havn't really got a lot of time on my hands but eventually i'll have to give the JIG a shot.
Realize that it seems like the phone isn't powered at all.
EDIT: no "usb device detected" notifications/sounds in windows when plugged in (for adb)
Also: My volt-o-meter told me that my battery outputted 6+ volts... can't seem to reproduce at the time of writing this though....
tinyhitman said:
EDIT: no "usb device detected" notifications/sounds in windows when plugged in (for adb)
Click to expand...
Click to collapse
could be a USB cable failure (guessing) try
2) Problem:- Cannot connect to PC or Unknown Device, getting Code 43 or any other code or NO response when using USB cable in My Android Solutions
did you tried to remove the battery several seconds holding down the powerbutton and put it back again?
btw i also had issues with a galaxy note and a broken usb cable. screen was black because of an empty battery, you should try an other battery maybe a friends one
hi all i bought defy about a year ago as a second phone from ebay with cm7 installed.last week i purchase another phone and give my 7 years old daughter. however i reset everything and phone turn old version blur mod then stuck on m logo i download rom and sort the problem.
real problem starts now i try to install cm 9 download all required files wiped the phone and install the rom however it didn't restart stuck on black screen and only white led when connected with usb also didn't connect or recognized by rds lite.I found tread battery wake up from i think was ''mggrager'' or something else finally rds recognized the phone and install another sbf but still stays same as black screen and white.i read so many threats on this side or others and each i installed custom roms without clearing cache
battery replaced with replacement battery also original
all drivers installed
it doesn't respond any buttons or usb connection
rds only with battery jump
please help what to do
I'm having the same problem as you are, i believe... I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport... I take my phone home, not really giving it much importance, and i noticed it would never charge and/or turn on, and that when I connect it to the pc, nothing happened other than the white led coming on.. RSD won't recognized it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
I don't know if i should make a thread of my own.. i think we have the same problem, and i REALLY need my phone back.. so i guess we could just help each other fixing it somehow....
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOLA_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
i already tried several times this method however no luck i am really not sure what to do any more i think only option try to find latest rom or first rom then try again if any luck will update and give the links
pasha543 said:
i already tried several times this method however no luck i am really not sure what to do any more i think only option try to find latest rom or first rom then try again if any luck will update and give the links
Click to expand...
Click to collapse
bump 4 help