Related
for some reason, i can connect to kies with no problem, but when i go to upgrade the firmware to the newest JI6 official, it fails and shows the attached picture. any ideas? I need to get this update because my vibrant is acting up pretty ba and as far as I know, this is the only current fix. I dont want to use the samfirmwares.com version because I want the official version. Help!
What version of Kies are you on? I'm on 1.5.1 and I never see an update. Maybe 1.5.3 can see the update?
Just updated mine about an hour ago through kies. Worked fine.
Kies Version: 1.5.1
Prior Rom: Bionix 1.4
Kernel: Stock
im on 1.5.3 and it still wont work, i just tried it again. I tried rebooting the pone and computer and still nothing worked. it just keeps saying unable to update. when you installed kies, did you install it as the UK as your country or US?
Mine says "PC Connection only available in idle screen Close running applications" when I try to connect with Samsung Kies mode???? What am I doing wrong?
Back out of everything on the phone, make sure you are in Kies mode. Run Kies first, then connect phone.
I have yet to see on the forum where somebody went from the JI5 from Kies to JI6 either OTA or through Kies. I've tried 1.5.1 and 1.5.3.81 for Kies and neither will update my phone.
Updating through Kies right now. I had to do the regedit fix for Kies 1.5.3.
EDIT: Whew, phone isn't bricked. Just made it past the Vibrant screen.
is it possible that kies may brick the phone?
How long is the Kies update taking for you guys? I'm pretty sure I'm hung up. It made it through the downloading, and now it's about a 1/4 of the way through the upgrade bar, but hasn't moved for an hour and a half.
I am totally stock. No mods, no nothing.
nateball said:
How long is the Kies update taking for you guys? I'm pretty sure I'm hung up. It made it through the downloading, and now it's about a 1/4 of the way through the upgrade bar, but hasn't moved for an hour and a half.
I am totally stock. No mods, no nothing.
Click to expand...
Click to collapse
that's not good. if i'm in your condition maybe i'm already sweating. maybe just wait a little more.
i tried to do this but the kies hung up when it's copying my contacts.
Well, it's not gonna do me any good to sweat. I'm over two hours now of just watching it sit there 25% done. No movement at all, computer's cpu is at 0% use. I think I have to pull the plug and then call Tmob if the phone is messed up.
Just to be clear, I was 100% stock, no root, no fixes, nothing other than apps installed from the marketplace. Here goes nothing...
nateball said:
Well, it's not gonna do me any good to sweat. I'm over two hours now of just watching it sit there 25% done. No movement at all, computer's cpu is at 0% use. I think I have to pull the plug and then call Tmob if the phone is messed up.
Just to be clear, I was 100% stock, no root, no fixes, nothing other than apps installed from the marketplace. Here goes nothing...
Click to expand...
Click to collapse
what happened? me too, i unplugged my phone before anything goes wrong.
ive made the backup of my contacts, but after that it cant continue to update, it fails every time, i guess i am stuck waiting for the ota unless someone has a fix for kies
My phone now only shows an image of a mobile phone and a desktop with a caution sign in between them. The same image shows if I restart using the power button, pull the battery, shake it vigorously, etc. I do believe I am now the proud owner of a non-functioning phone. Kies will not recognize it, nor does windows recognize it when it is plugged in. Crap.
I guess I'm off to the T-mobile store to try and get a replacement.
im in same boat i have no clue what im doing wrong? im i missing steps here?
if has any idea what i need to please help.
im a bone stock
Well, I'm pretty sure that we are now lacking functioning firmware on the phone. I'm thinking a new phone is the way to go, but maybe they can do something at the store.
Anyone where the update is stuck, you will probably have a soft brick at this point. However, this does not mean your phone is broken completely, it just means you will probably have to get into Download Mode and Flash via Odin.
Have fun
nateball said:
My phone now only shows an image of a mobile phone and a desktop with a caution sign in between them. The same image shows if I restart using the power button, pull the battery, shake it vigorously, etc. I do believe I am now the proud owner of a non-functioning phone. Kies will not recognize it, nor does windows recognize it when it is plugged in. Crap.
I guess I'm off to the T-mobile store to try and get a replacement.
Click to expand...
Click to collapse
that was my experience using kies too (whether 1.5.1 or 1.5.3). since then, i've used odin (v1.3) about 6 times (not a lot, i know) with all successes. don't let it scare you.
to get into download mode just do the following.
1) pull battery then put it back in so the phone is completely off
2) disconnect usb from phone (but leave it connected to pc)
3) while holding down volume up and down buttons together, insert usb cable
that should take you straight to download mode.
then load up odin (check the bible for flash instructions -- pretty simple though). what i did was flash to JFD, then flashed to JI5. worked like a charm.
honestly, kies was a nightmare to get working and once it did, it messed up. odin has been simple and painless. one note, after flashing with odin, first boot may be slow. when i flashed JI6 OTA over JI6 leaked, it took about 10 minutes, at least, to boot.
good luck!
I know it's not helping you guys: but my Kies update (newest release) was smooth sailings after I did the registry fix.
I did none of the backups suggested (I tried so many times before so they were already done this time)
Let me know if you want details about my config.
Sent from my SGH-T959 using XDA App
Thanks for all the suggestions everyone, but I did make judicious use of the search button and google before I took it back to the store. I tried every single combination of button presses for every single mode, from every single forums posts I could find. No luck at all. The T-mob guys also had no luck, and it just so happened that a Samsung rep stopped by to see how the Vibrant was being received by the public and he couldn't get any recovery mode to work either. (He had no idea about when Froyo might be out though..... just in case you were wondering) Anyhow, I'm pretty sure that I for one believe in the myth of the hardware locked Vibrants.
I think we need a new Poll for anyone that needs to change their answer after upgrading to JK4...Perhaps give JK4 a few days to make sure it's running smoothly before voting...
(Thanks Electroz for the original Poll!)
I got to experience 5 minutes of froyo before multiple force closes and then dead. It went into a reboot loop never getting past the white i9000m logo.
Updated with Kies (latest version--no registry mod)
I was stock JH2.
No lagfix ever installed
I've never flashed any rom.
Sorry guys, Kies is not safer...
Now I have to convince Bell to honor the warranty...
I don't think there are any issues with Kies or Odin for flashing. I've flashed many times, sometimes 4 times in one day and I've never had any issues. There does seem to be the usual SD issues but I also think there is a USB communications issue. There have been many reports of data corruption while writing to internal/external SD with large files. I personally had an issue pulling large files off of internal/external SD. I think if this problem occurs while flashing new firmware it could cause some corruption that could be noticeable right away or after a bit of use. The partitioning on this device seems to be more sensitive than others and a hiccup while flashing could cause some major issues.
trinitonesounds said:
I got to experience 5 minutes of froyo before multiple force closes and then dead. It went into a reboot loop never getting past the white i9000m logo.
Updated with Kies (latest version--no registry mod)
I was stock JH2.
No lagfix ever installed
I've never flashed any rom.
Sorry guys, Kies is not safer...
Now I have to convince Bell to honor the warranty even though I'm on Rogers...
Click to expand...
Click to collapse
They don't care.
I went today and they just took it and didn't ask anything that sounds like they cared about if I am not with Bells.
I gave them my bro's phone number and info since he is with Bell, just to avoid any problems.
Just don't say something like the phone is "unlocked" lol...the phone is dead so they won't find out anyways if you don't tell them. They won't ask either.
Just tell them that you upgraded through kies and it got the problem.
it's a hardware defect, if it dies it dies
after all the evidence we've seen (all the reports by our members)
if it's good it will work regardless of what firmware you use, and regardless of the way you flash the firmware
the lag fixes and froyo just accelerates the problem and makes it more evident sooner than later
which is good in a way, it's better to find out before your warranty runs out
ok im pretty sure mine is a full brick. maybe you can tell me.
less than 24 hours after updating to 2.2 i started getting all of these errors in various programs, so i rebooted the phone, but after it plays the little intro thingy the screen just goes black and thats it. cant do anything else. i tried a factory reset and still the same thing. so is that it?
also. i bought this phone at best buy, but network unlocked it to use on rogers. should i be contacting samsung directly about a replacement/fix? anyone here done that? im REALLY scared that are gonna give me a phone that i am unable to network unlock.
thanks for any info.
some one welcome me to the club of defund Bell Internal SD
http://forum.xda-developers.com/showthread.php?t=867157
@evil-doer
I am in the exact same boat as you! I bought from Best Buy, then unlocked to use on Rogers. Last night, I updated to official Froyo through Kies, and then it just died on me today (many app force closes and then just drop dead). When I get into recovery mode, it says can't mount the SD card.
I think I will just go to a Bell Store tomorrow and see what happens. I will let you know how it goes. Please let me know how yours go too. Thanks.
Mines a goner too
Same issue, have a forced app closure, shut the phone off and it wouldn't start up anymore. Just flashes the Galaxy S GT-I9000M white logo non-stop now.
I can put it into download mode and load up 2.1 (stock) and get to the coloured Galaxy S logo, but then it just goes to a black screen. In recovery mode, it shows stuff about not being able to mount the SD on E:\. I'd assume that's the internal flash?
Luckily I haven't had it for >30 days (on Virgin Mobile) so I'm hoping I can just exchange it and be on my way. I have to call them though apparently since I bought it online.
i did not have Force Close, the phone just got really really hot during batch restore of TitaniumBackup
jdrom said:
Mines a goner too
Same issue, have a forced app closure, shut the phone off and it wouldn't start up anymore. Just flashes the Galaxy S GT-I9000M white logo non-stop now.
I can put it into download mode and load up 2.1 (stock) and get to the coloured Galaxy S logo, but then it just goes to a black screen. In recovery mode, it shows stuff about not being able to mount the SD on E:\. I'd assume that's the internal flash?
Luckily I haven't had it for >30 days (on Virgin Mobile) so I'm hoping I can just exchange it and be on my way. I have to call them though apparently since I bought it online.
Click to expand...
Click to collapse
how did you load up 2.1? i can put my phone in download mode but nothing happens after that. and how do you get in to recovery mode?
Well I can load up 2.1 with Odin and with the auto reboot option checked, it'll go straight to recovery mode after flashing (for whatever reason). Otherwise I can't get to recovery mode.
Success so far... 12 hours after upgrade.
I sucessfully upgraded to Froyo yesterday.
I had problems with Kies at first and had to do a factory reset before the upgrade. The FileSearcherforKiesFix.exe altough it detected two bad files wasn't enough to make Kies happy.
This phone was bought in october and had the voodoo lagfix installed from the begining. I disabled the lagfix before the froyo upgrade.
My previous samsung phone; the GT-8000 (Omnia II) did have an internal SD card failure after a few months of operation... Also a Bell phone. I'm really concerned by that trend with Samsung and Bell...
I recommend NOT to upgrade. With JH2 I had NO problems. I upgraded to JK4 and about 24 hours later (this morning) I started getting force closes. XDA App. wouldn't open and just scrolling through memory management gave me haptic feedback (even though I had it disabled) and random closes. The phone became unusable fast. I tried a reboot and the phone booted to a black screen where only the buttons lit up. I went into recovery mode and I saw some dbdata error. I figured my phone was a goner. I ended up formatting the internal memory, clearing cache and then doing a factory reset. The phone is up and running now...but for how long.
Well... you're going to have upgrade eventually so best to do it now while you are under warranty in case something happens...
nemethb said:
I recommend NOT to upgrade. With JH2 I had NO problems. I upgraded to JK4 and about 24 hours later (this morning) I started getting force closes. XDA App. wouldn't open and just scrolling through memory management gave me haptic feedback (even though I had it disabled) and random closes. The phone became unusable fast. I tried a reboot and the phone booted to a black screen where only the buttons lit up. I went into recovery mode and I saw some dbdata error. I figured my phone was a goner. I ended up formatting the internal memory, clearing cache and then doing a factory reset. The phone is up and running now...but for how long.
Click to expand...
Click to collapse
How's that the case?
Stock JG9 w/ OCLF -> Stock JH2 (kies,voodoo lagfix) -> JK3 (Odin, Speedmod kernel w/ tweaks flashed through odin to get 2e back, no lagfix) -> JK4 (hacked kies, speedmod kernel w/ tweaks flashed through odin to get 2e back, no lagfix)
No SD failure so far, touch wood. Original phone purchased day after launch.
Mine died today, started getting FC and then the whole thing froze. I tried restarting it but after the samsung splash screen all I had were glowing buttons.
It ran fine for about a day on JK4 before that on JH2 it never gave any problems.
BTW it was stock updated through Kies.
The guy at the Bell store told me they never get these phones returned, this was a first for him. Either it was his first day on the job or it's typical Bell BS.
Just had my second phone die. The first one died after 28 days with no upgrade. This one after 8 days, 2 days after upgrading to Froyo...
Same thing happened to me this morning.. Froyo was working fine for just over a day and then this morning I turn on my phone, get a bunch of FCs.. I reboot.. get another bunch of FCs.. reboot.. and now it won't go through the "S" splash screen. When the screen disappears I press the buttons and it just glows..
I don't know if it's bricked or what.. when I run recovery I get this error.
E: can't mount /dev/block/mmcblkOp1 (I/O Error)
E: Copy_dbdata_media:can't mount SDCARD:
your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed.
Is this what everyone else is getting? And what are my alternatives?
If my phone is pooched then I'll be pretty pissed since this is my 3rd SGS, I gave the SGS up when it had issues in low reception and the 850 band lock fixed it. If this totally pooches my phone I'm never buying another Samsung mobile product again.
So.... I was stuck at the M logo after trying to update to a newer version of MIUI. I successfully SBF'd back to stock froyo and my phone won't activate. When the activation call tells me to press "1", it simply goes silent.
Now I somehow bypassed the activation screen, I don't think that was a good idea because it forced me to connect via wifi. I just said "screw it anyway" and went ahain to reroot. Then I installed CM7 (since I current don't have the MIUI zip I was previously running on my phone). Now I am stuck at the CM7 logo. Not sure if I should SBF again or what I should do. I'm kinda freaked.
Also, I have never had a problem SBFing before. This seems more serious than before.
Update: Wiping data allowed me to boot up in CM7. Still cannot activate my phone. Whenever it prompts me to press "1", all I get is complete silence.
I'm currently at UT Dallas, so I don't think location is a problem is it? Actually it shouldn't be because I bricked my phone here before. Had to reactivate it and it worked great.
Man, this is the first time my phone won't activate.
Yes I know I am posting a lot, but since no one is here to help currently I'm trying things out on my own.
I tried restoring a nandroid I had of CM7 previously. Man I thought this was always a failsafe....
Just thinking of things I did since the last time I activated my phone. I updated something (radio version, I don't really know much about it), it was supposed to make my 3G faster or whatever. But I mean I've SBF'd, factory reset and everything, so that shouldn't be an issue?
Gosh dang, I just want my phone back the way it was 2 hours ago.
One of the reasons nandroid might not be working is that I might have a different version of clockwork on my phone. I remember before having a version where the test was blue, but I forgot the version number. Now the one I get with rom manager is green (like the one I had before I got the blue one).
Man I am sooo confused here. I am completely at a loss. I am out of ideas. I need help.
So I realized I did not have the second init version of clockwork. I just flashed that, and I'm waiting to see if I will get any errors. If I get this to work I am going to flash the version of MIUI I had and try to restore my more recent nandroid (since Ive gotten MIUI).
Yup problem solved. Not sure what was causing the problem, but at least its solved. I'm gonna be extra careful next time I flash something.
Service Provider - Sprint
Model no. SPH-L720
Just picked up my Galaxy S4 from Bestbuy with stock 'Build no.' (MDC). As soon as i started using my phone, sprint pushed a 'over the air' (OTA) update. Had it downloaded, installed, and rebooted.
As I started using the phone more by clicking on the stock app. the phone starts to reboot itself. Long story short. I thought i'll fix it by rooting the phone. Same issue and reboot itself more, kept crashing.
I now unrooted the phone using Odin-OC for FULL ERASE since i have nothing on the phone to begin with. I'm guessing this is a hardware issue. I'm wondering if anyone out there that is having the same issue.
Thanks.
If the Galaxy s4 is faulty (hardware issue), the phone vibrate twice before samsung logo appear.
so from what you are saying as soon as you booted you got the MDL update correct? what "stock app" are you clicking on that is causing the phone to reboot? random reboots are commonly linked to specific software malfunctions most of which can be corrected easily. not saying you didnt get the bad one from the batch but if you provide more info we should be able to work out the kinks if its software related.
l3et9jwh2000 said:
Service Provider - Sprint
Model no. SPH-L720
Just picked up my Galaxy S4 from Bestbuy with stock 'Build no.' (MDC). As soon as i started using my phone, sprint pushed a 'over the air' (OTA) update. Had it downloaded, installed, and rebooted.
As I started using the phone more by clicking on the stock app. the phone starts to reboot itself. Long story short. I thought i'll fix it by rooting the phone. Same issue and reboot itself more, kept crashing.
I now unrooted the phone using Odin-OC for FULL ERASE since i have nothing on the phone to begin with. I'm guessing this is a hardware issue. I'm wondering if anyone out there that is having the same issue.
Thanks.
Click to expand...
Click to collapse
i also have this problem but i have no solution, samsung told me either i need a new battery or get my phone replaced pronto
xxaddictedxx said:
so from what you are saying as soon as you booted you got the MDL update correct? what "stock app" are you clicking on that is causing the phone to reboot? random reboots are commonly linked to specific software malfunctions most of which can be corrected easily. not saying you didnt get the bad one from the batch but if you provide more info we should be able to work out the kinks if its software related.
Click to expand...
Click to collapse
Sorry for the late respond, my phone will automatically reboot itself. While in any apps, game app and while using the camera to take pictures; my phone reboot itself. Once it is on, the phone will not respond (freezes) and reboot itself again and again. This usually stop by the forth or fifth time of continues self booting.
l3et9jwh2000 said:
Sorry for the late respond, my phone will automatically reboot itself. While in any apps, game app and while using the camera to take pictures; my phone reboot itself. Once it is on, the phone will not respond (freezes) and reboot itself again and again. This usually stop by the forth or fifth time of continues self booting.
Click to expand...
Click to collapse
i know you said that you are no longer rooted but have you tried rerooting and flashing a differant rom?
Typically random reboots are kernel related. When rooted did you try flashing any custom kernels, mods, try OC/UV, or anything along those lines?
Otherwise, sounds like a faulty device, maybe bad memory.
Same problem
A week after getting the galaxy s4 my phone started rebooting typically 2 times a day sometimes none at all, contacted sprint they said to come in and there fix was a factory reset lol, so decided to root and install triforce rom with kt kernel , still getting random reboots, im playing with the kt kernal settings hoping to find a sweet spot
Honestly... I think it's the MF9 update. It hasn't happened to me, but I've seen it for plenty of people. Everyone here running build no. MF9??
I am now, but my reboots started right when the phone came out
Sent from my SPH-L720
Hi folks.
So after a sleepless night and a lot of guessing and clicking around with no luck, I finally decided to ask for help.
The story:
Yesterday, I decided to open up my lovely N4 to perform the thermal pad mod (that can be found on these forums), as it was going really hot around the CPU at time and it seemed like a good solution.
Now, I'm no stranger to disassembling microelectronics without breaking them (few weeks ago, I successfully resoldered a broken power button in my old T989 that I've been using before N4).
What couldn't let me sleep at night:
And here is where the problem emerged. After re-assembling my sweet little phone (yes, i did it perfectly right), I tried to boot up and all i could see was an endless and really annoying bootloop, but as the device booted up, I did not worry much. While doing some research, I read that there's people experiencing bootloops with 4.3, so I thought that after disconnecting the battery, it just might've had happened on its own (I was using stock 4.3 with faux kernel before the nightmare started)
At this point, I booted into recovery and tried to flash the rom over, but unfortunately nothing positive happened. Then I tried factory reset and flashing different roms, also with no luck. This is when things started to get really frustrating, as no matter what I flashed, the bootloop was (and is) still there. But then I tries to restore a backup that I did right after getting my N4, back in November, and it WORKED. Why do i still have a problem then? Because it was 4.1 and OTA was giving me error every time I wanted to flash the update, so I kept flashing till i get some results. And then one of the N4 toolkits wiped my entire internal memory and I ended up with only being able to use sideload. Then I tried ALL of the N4 toolkits that can be found in here, to wipe everything and bring my phone back to everything stock, but the bootloader is locked so it cant do it, and it cant unlock it because I cant boot into the system.
Conclusion:
The phone works fine, and it proved it. But no matter what I try to flash (other than the old backup), the persistent bootloop is still there smiling at me like an a****le.
Any ideas?