Hello,
I upgraded to Froyo last week, and hadn't had any problems until now. Yesterday when I had my bluetooth hooked up to the phone, it all of a sudden disconnected, which has happened many times before when the phones battery goes dead. So, last night I plugged into the wall to charge it, and this morning I wake up to the screen constantly flashing on and off (showing the black startup screen that says "Galaxy S I9000 Samsung".
I've tried plugging it into my computer, plugging it back into the wall charger, and booting into recovery mode, but all it does is show the battery charging screen momentarily (batteries shows to have no charge it whatsoever), and then switches back to flashing the startup screen.
Can someone please help me out, it would be greatly appreciated.
Thank you very much,
Cam
Hi Cam,
I have the same issue as you have and I'm trying to find the way to reload my device with the stock OS Android 2.1 Eclair that includes the bootloader that seems defective for some reason.
I was bounced by from Bell support to Samsung support, then to Best Buy where I got it and back to Bell.
I'll keep you in the loop if I find a solution.
Good luck
Maxx
maxximux2000 said:
Hi Cam,
I have the same issue as you have and I'm trying to find the way to reload my device with the stock OS Android 2.1 Eclair that includes the bootloader that seems defective for some reason.
I was bounced by from Bell support to Samsung support, then to Best Buy where I got it and back to Bell.
I'll keep you in the loop if I find a solution.
Good luck
Maxx
Click to expand...
Click to collapse
Hey Maxx,
I called Samsung this morning and they told me to take it to the Bell store where I purchased it from, and they may need to flash it or send it in for repairs.
Definitely keep me in the loop, it's much appreciated. This is extremely frustrating.
Thanks,
Cam
Hi Cam,
I will try the instruction found in the post http://forum.xda-developers.com/showthread.php?t=870058 after work.
Let's hope this will do the trick.
Maxx
Hi Maxx,
Did you get a chance to try it out? If so, did you have any luck?
Thanks,
Cam
Hi Cam,
No success with any firmware combination I tried, I think the only thing left is to send it back for repair. There is many others that have the same issues. All seems to be related to an internal SD card that is defective.
Maxx
Thanks, dude. Unfortunately it looks like I'll be sending it back today. You know whether or not I should take the two SD cards out before sending it back? I presume I should at least take out the card that I purchased separately?
Very late reply but this happened for me today (i was trying to install cwm through program Heimdall). So i put phone to download mode and using odin i was able to push in android 2.3.6 and everything works fine (except root permision gone).
Related
So I was hoping that anyone here could shed some light on an issue that one of my friends who just bought a Nexus is having. His N1 is bone stock, and is an AT&T model. Every once in a while, completely out of the blue, the screen will turn black and restart, but then enter an infinite boot loop, where the only solution is to remove the power adapter and battery.
In trying to pinpoint the problem, we have noticed:
-It really only tends to happen when the device is plugged in.
-It's not related to the battery, charger, or microSD (since we tried mine to no avail)
-It's probably not kernel, ROM, or radio related (we let it do the OTA 2.2 update, and the crashes were still present)
I don't understand why it only happens when the phone is plugged in. The phone isn't hot to the touch, so I doubt that the battery is over heating.
Any help will be greatly appreciated. Thanks!
PS. I tried searching, but the only mention of boot loops I could find were on custom ROMs and Kernels...
Exact Same problem and Phone here!!!
Just got it today too! Please any suggestions would be nice! Want to root this phone but to afraid there is a hardware issue!
My friend ended up calling HTC and they asked him to return it, which he did, for a full refund. Ironically, he ended up getting a Samsung Galaxy S (ATT Captivate variety). Nexus one, although less powerful, is more sleek in my book...
I've got almost the exact same problem on an AT&T N1 running Froyo FRF91, the two differences I have are that the phone does feel hot to the touch, and that it never happened on 2.1. If anybody has some info on this it would be greatly appreciated, but I will be calling HTC/Google in the next few days to see if we can resolve this problem.
Hey guys,
I had a very similar problem with my phone rebooting while charging especially on the Car Dock. I ended up doing an exchange with Google/HTC and received another unit. This one now has no problems with rebooting. I suggest calling and getting your units replaced. My guess is there was a bad batch that have hardware issues.
Jay
jpav80 said:
Hey guys,
I had a very similar problem with my phone rebooting while charging especially on the Car Dock. I ended up doing an exchange with Google/HTC and received another unit. This one now has no problems with rebooting. I suggest calling and getting your units replaced. My guess is there was a bad batch that have hardware issues.
Jay
Click to expand...
Click to collapse
What can I do if it is unlocked? Any chance they still help you out? Or just forget it?
I don't think it would hurt to just give them a call. I have read some forums where people have sent unlocked phones in for repair and then got them back fixed and re-locked. It is worth a shot instead of having a faulty phone. I did the exchange option and it did take me a while to get my replacement phone, but that was due to HTC moving their repair facility according to the tech. The techs that I have talked to have been helpful. If I thought a tech was no good I just hang up and try again with a different person.
Jay
I have been having pretty much the exact same issues.
I have an AT&T unlocked/rooted N1.
Random reboots frequently when the phone is charging via plug or USB for seemingly no reason. I thought it may have been an app, or combination of apps, so I tried a combination of different steps to try and find a solution.
Wiped data/cache
Wiped data/cache & fix apk permissions (Amon Ra 1.7.0.1)
Wiped data/cache and flashed the current ROM I was using again
Wiped data/cache and flashed different ROMs (both 2.1 and 2.2 w/proper radio) including MCR r16-21, PhoenRom, LeoFroYo, Cyanogen 5/6 RC1 and even tried intersectRaven's Kernel's
Reformated the SDCard both via gparted from Ubuntu live cd and Amon Ra's recovery 1.7.0.1
Swapped out the SDCard thinking possibly a bad block
And finally re-flashed back to shipping stock 2.1 and stock recovery w/successful OTA 2.2 install
All steps I was able to get my N1 to randomly reboot plugged in or not. I even had it sitting on my desk at work unused for 30-40 min (running CM RC1) and it rebooted with no user input what-so-ever. It happens more often while plugged in but was not limited to charging state.
All that said, I finally called support, took about 30 min total to arrange a replacement. This included a factory reset while on the phone with the tech and I was able to get the phone to reboot within a few minutes of first boot.
Take it for what it is worth, but I am positive that this is a hardware issue in my case. Just hope my replacement goes without penalty (unlocked and all) and that my new N1 doesn't have the same issues.
Firstly, may I apologise, I know this has been covered, I've trawled the internet for hours but just can't seem to get an answer.
I recently updated my UK, unlocked Galaxy S to Froyo via the registry hack, all was fine (ish). Because Froyo had been delayed in the UK and wasn't as great when it was running on my phone I thought it would be safer to revert back to 2.1 and wait until the official UK release came out (I know some will ask me why I did this, I just felt that Froyo was held back for a reason and I couldnt get an answer as to if I could update to the UK version if I already had the Scandinavian one). So I did the reg hack again and was offered 2.1. Everything seemed to go smoothly until the phone rebooted after downloading from Kies. Now the phone's animation starts then the flashing S symbol displays for an extended time. After that, the screen goes black. If I touch the two touchscreen buttons they stay on but do not go off. If I hold the power button the phone turns itself off and when the phone is powered off and I plug it into my PC with a USB, the battery charging sign comes on.
The phone was rooted and I did have the OCLF on but uninstalled that and un-rooted before changing the firmware so it was back to stock.
Before I get 20 people telling me to put the phone in download/recovery mode I must tell you that I can't. My phone has never been able to do it. I've tried every single way and button order suggested. I'm not the only one who's phone won't do it either so it's not just me. The only way I ever saw recovery mode on my phone was when I used the one click root on the PC.
I'm at a total loss. Debugging was turned off because Kies won't let you do anything with it turned on and so ADB recovery is out also.
Please help if you can.
Many thanks,
Ryan
Boot to download mode, do a repartition with Odin and 512 pit flash, remove battery and boot again to download mode and then do a odin firmware flash to which ever firmware you want.
thanks intratech but I can't boot the phone into recovery or download mode (sorry should have stated that). Believe me, I have tried every combination. I did a lot of research and discovered that there are quite a few people for whom that feature was disabled.
if the 3 button combo is not working on your phone, you should not do these risky stuff actually
take a look at this thing
http :/ / forum.xda-developers.com/showthread.php?t=819551
remove spaces
thanks Noobproof. I remember coming across that thread last night. Although I consider myself ok with software, soldering and slicing just isn't my forte. I haven't got a clue about soldering, etc. I've just come back from the Carphone Warehouse (Samsung suggested I go there as they are the service centres listed on the Samsung UK website). The engineer had the phone for half hour and said that the "board was faulty". Haven't got a clue what he meant by that, unless he meant the internal SD which a few people have had go on them. Anywho, he told me to ring Samsung and send it in for a repair. I did that and need to send my phone special delivery to a company called regenersis in Scotland.
I knew rooting and flashing custom roms was a risk, that's why I never touched Odin,etc. I used Kies to upgrade to Froyo and Kies to downgrade back to Eclair. You would think that sticking to official Samsung software would be safe. I must admit, when it was going well I loved my Galaxy but more and more I'm starting to wish I'd opted for the Iphone.It just seems that there have been so many glitches and bugs, I mean, why should there ever be a need for lag fix in the first place? I often found myself keeping my fingers crossed when downloading simple apps as that was usually touch and go!
Feeling a bit deflated now. Was hoping some clever boffin had designed a software solution that would recognise the phone and force it into download/recovery mode.
Ah well, thanks for taking the time to respond anyway.
Best wishes,
Ryan
You know i was very happy when i for the phone for the first time and while i was doing a research (i live in turkey and there is no stock android market here) i came along this forum. And i have learned that i havent got the 3 button combo. I downloaded the 3 button fix abd took the phone to samsung centre.
They told me that they cannot flash it and i made a huge fight then they accepted and i have my 3 buttons. Never give up your phone. I dont think the internal sd is faulty it is just corruppted if you can access the recovery menu you could fix it. Any way you have to find a service centre that has an anyway jig box other a jtag box otherwise they will have to replace the motherboard. Good luck
Sent from my GT-I9000 using XDA App
I had the same problem all i did was use a different firmware .. didnt choose anything in pitfile and did not check on repartition but checked only F reset and Auto reboot and flashed my phone and voila it booted perfectly fine
Hope it helps others with black screen problem after booting
thanks
mike
I had the same problem too. This method really works.
Wysłano z GT-I9000 z użyciem Tapatalk
Ok I have read about 50 different posts that are similar to my situation but none of them seem to be exactly what I'm looking for. Here is what is happening with a little background.
Running Stock 2.1 on a BELL Mobility Vibrant.
No Custom Roms.
I did have the OCLF installed (Almost 3 months ago without issue)
Phone is also Rooted
Last night I was at a friends place showing off my phone as they were ready to get a new one. I showed them all the cool apps, google maps, google Sky, Soundhound, Bar Code Scanner, etc.. They were sold and are no longer getting an iPhone.
I came home and went to bed. I woke up this morning and the phone was off.. I turned on the phone and once it booted up it said the battery was dead.. No problem.. Power the phone down.. Replace battery and reboot.
It would not reboot.. it gets stuck at the Galaxy S logo screen
My phone is one of these earlier models that doesn't have access to the 3 button recovery so I was using the ADB reboot-recovery to access the menu.. However, this no longer works.. it just reboots the phone and gets stuck at the logo.
I have tried ADB logcat and it just loops and loops.. (Thousands of lines of data)
I have tried a few different batteries.. I have tried powering it up connected to a wall outlet (power) as well as to the computer (it does detect the USB and makes the USB connect sounds (windows7))
Keis and ODIn both don't see the device.. (Not surprising)
Have tried 3-4 different methods to get to the download screen as suggested in other posts and none of them work.
Is there anything else I can try short of taking the phone back to Wireless Wave?
Just uploaded a dump of the logfile from AGB Logcat Cmd. In case that helps.
If you can't get the download screen, then your best bet is making a homemade jig. Search google for how to make one. I made mine when I encountered this problem and it works every time when I am unable to get a download screen.
I guarantee that it'll work for you as well. Good luck.
[HOWTO] [REF] Get Download Mode without 3-button combo using homemade JIG
Can you clarify? Are you unable to get into recovery AND download mode?
gtg2 said:
Can you clarify? Are you unable to get into recovery AND download mode?
Click to expand...
Click to collapse
Hey...my phone is currently stuck at a boot screen loop and it doesnt stop doing it. What can i do to fix this? I am able to get into download mode but not recovery mode. i know how to use odin, but can anybody guide me to which files i should use to put into odin to fix my phone? please help, thanks!! BTW, my phone is i9000 from BELL CANADA also!
Alright, follow this link and you'll get your three buttons working.
http://forum.xda-developers.com/showthread.php?t=785201
Make sure you get ODIN v1.3 and not v1.0 because the older one doesn't have a bootloader flash option.
zumi78878 said:
Hey...my phone is currently stuck at a boot screen loop and it doesnt stop doing it. What can i do to fix this? I am able to get into download mode but not recovery mode. i know how to use odin, but can anybody guide me to which files i should use to put into odin to fix my phone? please help, thanks!! BTW, my phone is i9000 from BELL CANADA also!
Click to expand...
Click to collapse
My Galaxy S from Bell is doing the same thing I spent 6 hours yesterday and so far 3 hours trying to get a replacement over the counter and so far its go to where you got the phone (Future Shop) they say only 14 day return window on this phone and mine started do it 16 days after i got it. Future shops says to go to Bell Store. Bell Store says Future shop should be handling this. now I am on my second call to Bell Corp and they are trying to keep me as a customer since I told them if this is not fixed today or replaced I am send the phone back and they can take their 3 year contract and stuff it.
so far looking good she is being very understanding and trying to help me
we shall see how this will go..
well 2 hours on the phone with them and the rep Named Laura is doing her best to get me a swapped phone today but she keeps hitting roadblocks between Future Shop and her own jobs corporate policies
with Bell this phone is 30 Days for straight across exchange but with Future Shop this is a 14 day policy since my phone died at day 16 its no longer covered by Future Shop and Bell hasn't been able to help me yet.
Laura is now trying to go above her bosses heads' and do good for me they have notes that my phone is considered DOA and should just be swapped by Bell Stores wont help me due to this phone being purchased at Future Shop
oh so frustrating...
UPDATE:
well after 2.5 hours on the phone with Laura and full of empty promises she cannot do anything for me Future shop has a 14 day policy Bell has a 30 Day policy and the phone is now 17 day old and nothing but a brick.
so I am heading to the nearest Bell store and dropping off the Phone and telling them to stuff the contract and all my bills good riddance.
nyk0n said:
so I am heading to the nearest Bell store and dropping off the Phone and telling them to stuff the contract and all my bills good riddance.
Click to expand...
Click to collapse
Let us know how that goes.
I predict the first murder in Canada inside a mobile phone dealership occurs in the next month over a Galaxy.
Ok yesterday i got my i9000m. Rooted, and one click lag fixed. Stock 2.2 Froyo.
Today the phone would not wake up from sleep. Turned it off and on again and got past boot animation then just get a black screen (the buttons light up). Restarted a few times with same result.
Then i reformatted through recovery and rebooted. Got through to TouchWiz but it was very laggy and found no Google apps along with the phone saying there was no SDcard. So i reformatted again. Now the phone has the same problem, gets past boot animation but does not wake up.
Can someone please help me.
Do you know what build it was running? (JK4 or JL2)
If you got it through a store/Bell store, take it back and demand a new one on the spot. You've got symptoms of Internal SD card failure.
If you bought it off of eBay or some other source, you can try to take it in to Bell and hope they'll fix/replace it, or call up Samsung (1-800-726-7864) to send it in to them.
Best of luck.
I got mine today and right out of the box it was running JK4, the 1st phone they gave me was a boot loop, 2nd phone worked flawlessly, just return it if it's less than 2 week old they'll replace it on the spot
I bought it 2nd hand and im a rogers customer... :\ not sure if its JL2 or JK4
maybe a friend on bell can try and send it back for me?
Also I AM able to get into recovery and downloader mode. Suggestions?
You could try grabbing the official JL2 build and flash via Odin, if that doesn't help you could always call Samsung, they don't seem to care who you're signed up with and their turnaround time is apparently pretty fast.
got_milk said:
You could try grabbing the official JL2 build and flash via Odin, if that doesn't help you could always call Samsung, they don't seem to care who you're signed up with and their turnaround time is apparently pretty fast.
Click to expand...
Click to collapse
I agree you got nothing to lose..Flash stock and see how you go
Bricked. Like completely. Ugh...
Thanks anyways.
Hi there,
I fear I hard bricked my G1 (after long years of good service as gps device thanks to a 2600mAh battery).
Since it was quite slow on CM7, I downgraded it to CM6.1. But this would'nt boot. (boot loop)
So I did a bit of reading and decided to downgrade the radio too. I downloaded a flashable zip and flashed it the usual way in the CWM recovery - which didn't finish (after a few minutes), so I removed the battery.
Since then my G1 wont start any more. On top of that, it want event charge. If I try to charge it the status led wont event light up. (I already tried it with two different batteries, both yield the same results.)
Funny thing though: If I don't charge it and let it sit for a few hours, the status LED very shortly lights up when pressing the power button. (But other than this nothing happens and if I press the power button again shortly after the LED stays dead.)
So ... I fear the problem is hardware and not software related.
Does anybody have an idea what could be broken (software or hardware) and if it's software based if there's a way to revive my phone?
(Before anybody asks ... yes, I have newer android phones, but I really live my G1 for nostalgic value so if there a way to get it running again I definitely would try.)
thx a lot,
Bapf
Sounds like you need JTAG, and don't take this the wrong way, but flashing firmware isn't the usual way, its the way you brick your phone. If possible always use fast boot to flash firmware or you are asking for a brick.
You can buy the JTAG equipment yourself and the software is free. Or you can see if you can find someone locally to do it. Unless you have a particular sentimental value to this phone it maybe cheaper to buy a new one.... Sorry for bad news
Sent from my Nexus 7 using xda premium
Bricked G1 - Try Again w/ SIM Card IN!
I had the exact symptoms mentioned in this post - tried nearly everything until I finally put back in the SIM card (even through I don't have T-Mobile anymore) - it booted again and registers the AC adapter and/or USB cable. Hope this helps some who are struggling at this level as I did!!
Bapf said:
Hi there,
I fear I hard bricked my G1 (after long years of good service as gps device thanks to a 2600mAh battery).
Since it was quite slow on CM7, I downgraded it to CM6.1. But this would'nt boot. (boot loop)
So I did a bit of reading and decided to downgrade the radio too. I downloaded a flashable zip and flashed it the usual way in the CWM recovery - which didn't finish (after a few minutes), so I removed the battery.
Since then my G1 wont start any more. On top of that, it want event charge. If I try to charge it the status led wont event light up. (I already tried it with two different batteries, both yield the same results.)
Funny thing though: If I don't charge it and let it sit for a few hours, the status LED very shortly lights up when pressing the power button. (But other than this nothing happens and if I press the power button again shortly after the LED stays dead.)
So ... I fear the problem is hardware and not software related.
Does anybody have an idea what could be broken (software or hardware) and if it's software based if there's a way to revive my phone?
(Before anybody asks ... yes, I have newer android phones, but I really live my G1 for nostalgic value so if there a way to get it running again I definitely would try.)
thx a lot,
Bapf
Click to expand...
Click to collapse
I don't know if this will work,as I've never encountered a situation such as this, but have you tried bootloader(power button+camera button)?
If you can get it into bootloader, then I have the original rc29 DREAIMG.NBH file(plus, rc29 is the best place to start if you want to root it or install a custom rom).If you get it working and just want stock 1.6, i have those updates as well.
(all said out of hope, I have a g1 and I love it,I'm really glad that someone else shares my enthusiasm!!)
If bootloader works, give me your email and i'll send you the files, good luck!:fingers-crossed:
Nope. It won't even start the bootloader.
Sent from my Nexus 4 using xda app-developers app
Well thats unfortunite, I guess it's just for a soft brick.