Related
Today i am going to refresh my rom . After finishing, Galaxy S can not open...
Is Galaxy S or the battery problem?
Have any method to slove this problem?
I bought from Optus in Australia
Now Version is JM5 and he old version is Jm5,if i go to the custom services ,will i cease the warrant?
Thanks everyone to help.
as long as you flashed it with a samsung-made firmware and not a custom ROM, i think your warrantly should still be ok!
If you seek help from the guys here, my guess is that you need to explain a bit more in detail what's not working, besides "cannot open".
"New version is JM5 and old version is JM5" ??
dudeldei said:
If you seek help from the guys here, my guess is that you need to explain a bit more in detail what's not working, besides "cannot open".
"New version is JM5 and old version is JM5" ??
Click to expand...
Click to collapse
"cannot open" mean when i press the turn on/turn off button don't have any respond.
"New version is JM5 and old version is JM5" That is mean Before and after flashing version, the reason of flash again is i can not use Galaxy but i can enter the download mode. i think this information may help you to find mine problems..but i am not sure.
mcall_r said:
as long as you flashed it with a samsung-made firmware and not a custom ROM, i think your warrantly should still be ok!
Click to expand...
Click to collapse
But i refresh Galaxy via Odin, is it still ok?
ososos said:
But i refresh Galaxy via Odin, is it still ok?
Click to expand...
Click to collapse
Flash I9000DTJG4 if you got your phone from Optus in Australia.
Find it here.
i cannot switch on the Galaxy S even by any modes.
Simply, i think it is broken down and I dont know what to do. I am not sure if my warrant is still effective or not.
You know, generally flash the rom will cease warrant.I think people l solve my problem there... Because Xda's is professional...
Can someone move this thread :-(
I almost fell of my chair when reading "BIG PROBLEMS WITH I9000".
Big problem with flashing you mean !!
OH.. sorry .......
Admin move to correct section.
Sorry about that
Try charging the battery. and then switch on the phone..
SGS is pretty unbrickable
No problem
I hope you find a solution quick.
1. If the phone is turned off then remove the SD card, the SIM card and the battery.
2. Put the battery in only then enter Download mode. Hold in vol down and Home buttons then press the power button. Works every time.
3. OPTUS is currently using I9000DTJG4 available here
4. Set up ODIN with the correct files. PIT 512 and the code file called ADD_OPS.tar from the download.
5. Select Re-Partition.
6. Connect your phone to your computer via USB cable. Wait for com to come up in ODIN.
7. Flash the Aussie firmware.
Wish you luck my friend.
no no no... i CANNOT OPEN SGS AT ANY MODE..
It seems sgs don't have the battery... i cannot charge the phone ..
ososos, unfortunately it sounds like a full brick to me. I think there have been about 5 occurrences of this (myself being one of them), one guy managed to get his to power on my holding home + volume down + power and inserting the battery whilst these buttons were being held.
However as a general rule if your phone won't even turn on you'll need to send your phone off for repair.
Hmmm try using some friend's battery if he too has SGS... Or try charging only the battery at optus.. GL mate..
Hi,
Last night my Galaxy S was low on battery, and I kept trying to turn it on for it to die right away (it was working as expected I guess)
This morning after I charged my phone it wouldn't turn on at all! It loads to the logo screen, makes that jingle sound and then holds and doesn't turn on.
I can get to recovery and download mode.
I put OCLF on like 2 months ago, but haven't modded/flashed ANYTHING since. It is very bizarre how it just died.
I'm wondering what my options are now. Obviously I would rather not loose all my personal files. Since I can get into download mode, can I just flash a new firmware? I'd like FroYo anyway, but I haven't got a clue what to do.
Great start to the year – !
Cheers,
Mitch
EDIT: I just decided to try the "Clear User Cache" option and then reboot to no avail. Now I can't get back into recovery mode!?!? Download mode still works. Huhh?? Is this expected? Have I lose Recovery Mode entirely now? Crap.
seeeems like an odin flash via the download mode is the only way. There are a few tutorials on this site and even tut vids on youtube so you should be fine if you just follow everything they do (as long as it works for them of course)
How do I know what version to flash? I have read a few tutorials and they all have started with "Dial x and check you have y" etc. Obviously I can't do any of that.
What is the *safest* firmware I can flash?
My phone currently has some optus variety.
Please forgive the noodish question.
Mitch
Where are you located? And who is your provider?
Hi,
I'm in Sydney Australia and my provider is Optus.
Thanks
Hi,
I still can't get my phone working and am not clear how to proceed.
What would be the best firmware to flash to my Optus Galaxy S that bricked out of the blue? Should I just send it back to Samsung?
Thank You
m1tch37 said:
Hi,
I still can't get my phone working and am not clear how to proceed.
What would be the best firmware to flash to my Optus Galaxy S that bricked out of the blue? Should I just send it back to Samsung?
Thank You
Click to expand...
Click to collapse
Hey mate go to samfirmware and get I9000DTJG4 thats the stock optus rom once you get phone up and running then upgrade to 2.2.1.
Sounds like you'll need to do a flash of a stock rom..
By the way, the old oclf had some issues that might lead to system corruption (unfortunately I'm not very sure exactly what it does, or whether it could lead to this problem). I'd suggest getting one of the newer lag fixes available here when you do get your phone running again
tragusman said:
Hey mate go to samfirmware and get I9000DTJG4 thats the stock optus rom once you get phone up and running then upgrade to 2.2.1.
Click to expand...
Click to collapse
tragusman has got it right. Depending on what the issue is, you'll either recover nicely or your phone is toast. Flash the above stock firmware and give it a shot. Note that you'll likely loose your data and settings.
If you're new to flashing firmwares, check the great reference guide on where to find Odin and how to use it (this is the app you'll use to flash the above firmware).
http://forum.xda-developers.com/showthread.php?t=723596
After flashing, try getting into recovery mode. If you can look for an error message under the standard menu. Can't get to d/l mode? You're probably in trouble. Get into recovery and see an error msg? Post the error here or google it for a solution. No error msg? You're probably ok - restart the phone.
Good luck.
Thanks guys.
I'm about to try it now, but before I start potentially breaking my phone even more, I was just thinking: Could I just send it back to Samsung? Would they fix it, or identify right away I have changed something and void my warranty.
Mitch
m1tch37 said:
Thanks guys.
I'm about to try it now, but before I start potentially breaking my phone even more, I was just thinking: Could I just send it back to Samsung? Would they fix it, or identify right away I have changed something and void my warranty.
Mitch
Click to expand...
Click to collapse
If it's broke, you can't break it any more I've sent phones back in for support after flashing back stock firmware (flashing it after it "died").
i was installing the ics repack zclp1 with pc odin but it stuck on data.img
what should i do?
can i remove the cable?
please help ...
you can restart but dont reboot phone any you turn it once the bootloader is flashed you will be safe you can also check the link in my sig
antiguangenius said:
you can restart but dont reboot phone any you turn it once the bootloader is flashed you will be safe you can also check the link in my sig
Click to expand...
Click to collapse
Please stop offering your 'bootloader' advice to guys having problems after flashing Angelom's ICS kernel.
Bootloader is not going to help because their problem is corrupted data partition. Nothing to do with the bootloader whatsoever.
Ok
chasmodo said:
Please stop offering your 'bootloader' advice to guys having problems after flashing Angelom's ICS kernel.
Bootloader is not going to help because their problem is corrupted data partition. Nothing to do with the bootloader whatsoever.
Click to expand...
Click to collapse
ummm read properly before you respond
I SAID HE CAN RESTART THE FLASH BECAUSE THE BOOTLOADER IS FLASHED FIRST SO HE IS SAFE.
i never told him to flash his bootloader obvoiusly he is try to root or install ics so a smart guy will click on the rooted or rom link for help....
PS
look before you leap.....
Let me guess re-partition was on in odin?
If yes u need to call samsung.
avetny said:
Let me guess re-partition was on in odin?
If yes u need to call samsung.
Click to expand...
Click to collapse
you dont need to call samsung.... i have use the repartition few times..... sounds like he has a bad flash chip....
antiguangenius said:
you dont need to call samsung.... i have use the repartition few times..... sounds like he has a bad flash chip....
Click to expand...
Click to collapse
so whats the solution mate? we have tried everything. pit, odin, cwm, kernel flash, it gets stuck either at boot n700 logo or at factoryfs or data.im on odin
antiguangenius said:
ummm read properly before you respond
I SAID HE CAN RESTART THE FLASH BECAUSE THE BOOTLOADER IS FLASHED FIRST SO HE IS SAFE.
i never told him to flash his bootloader obvoiusly he is try to root or install ics so a smart guy will click on the rooted or rom link for help....
PS
look before you leap.....
Click to expand...
Click to collapse
No, you read properly before you respond, and even more properly before dishing out any more useless advice to people with a very specific problem, i.e. bricked phones after flashing Angelom ICS kernel v1.2.
Read this, for instance:
http://forum.xda-developers.com/showpost.php?p=23256341&postcount=405
and this:
http://forum.xda-developers.com/showpost.php?p=23256829&postcount=406
I'll say no more about it.
androidindian said:
so whats the solution mate? we have tried everything. pit, odin, cwm, kernel flash, it gets stuck either at boot n700 logo or at factoryfs or data.im on odin
Click to expand...
Click to collapse
ok ok ok i have took sometime and read almost every one issue.. the problem is indeed global.... due to the 1.2 recovery, angelom rom or what ever.....
I have put some thought into in.... i could be wrong or sound like an idiot to say this but it seem like the boot block for the main flash chip it been corrupted with the wrong header....
for eg. most note is 16gb, lets say with a A14BC ok check sum.... the rom seem to be interfering with that checksum or flash header... so when the odin which has only a specific command to modify that flash chip look for the checksum to proceed.. its not getting it so it waits and waits and waits... which is what its officially programmed to do.. i'm guessing that these it a specific switch odin needs to start with to over ride its normal procedure and reset flash to its original state or there's a higher level program to do this.... these flash chips was programmed in the phone not out so there has to be a way to revive them... its electronics...... it remind me of the boot legged usb flash cards, you will buy one at 32gb months later it wont work properly or at all.
but nevertheless most people getting the N7000 bootlogo and nothing after its just like a pc with a bad harddrive the phone is looking for the Unified Extensible Firmware Interface (UEFI) which is a specification that defines a software interface between an operating system and platform firmware.. its not that because odin can't load it... odin cant load if for many reason which can be the flash chip has been corrupted so the full size cant be read or the checksum mismatched... only fix i believe it there is if odin has a special switch which ignore checksums or it had a grandfather program we don't have access to....
bottom line is the flash chip aka hard drive from the note is not formatted and/or partitioned so its not accepting the firmware aka the os.......
we need the chinese that made these thing to say whats missing.... or a samsung tech so leak something...
PS maybe if someone force a SGS2 rom on it since they're close devices, that might set the flash back in order then try the note rom.... preferably someone with a busted device that wanna take the leap.... will be interested to see where the SGS2 rom flash stops.... crazy idea but who know might work after all the device is already not working...
antiguangenius said:
ok ok ok i have took sometime and read almost every one issue.. the problem is indeed global.... due to the 1.2 recovery, angelom rom or what ever.....
PS maybe if someone force a SGS2 rom on it since they're close devices, that might set the flash back in order then try the note rom.... preferably someone with a busted device that wanna take the leap.... will be interested to see where the SGS2 rom flash stops.... crazy idea but who know might work after all the device is already not working...
Click to expand...
Click to collapse
Those are some really interesting thoughts.
And this chap here http://forum.xda-developers.com/showpost.php?p=23305688&postcount=1
Did something similar and succeeded, though the root cause was different it seems to be matching with your analysis!!
antiguangenius said:
ok ok ok i have took sometime and read almost every one issue.. the problem is indeed global.... due to the 1.2 recovery, angelom rom or what ever.....
I have put some thought into in.... i could be wrong or sound like an idiot to say this but it seem like the boot block for the main flash chip it been corrupted with the wrong header....
for eg. most note is 16gb, lets say with a A14BC ok check sum.... the rom seem to be interfering with that checksum or flash header... so when the odin which has only a specific command to modify that flash chip look for the checksum to proceed.. its not getting it so it waits and waits and waits... which is what its officially programmed to do.. i'm guessing that these it a specific switch odin needs to start with to over ride its normal procedure and reset flash to its original state or there's a higher level program to do this.... these flash chips was programmed in the phone not out so there has to be a way to revive them... its electronics...... it remind me of the boot legged usb flash cards, you will buy one at 32gb months later it wont work properly or at all.
but nevertheless most people getting the N7000 bootlogo and nothing after its just like a pc with a bad harddrive the phone is looking for the Unified Extensible Firmware Interface (UEFI) which is a specification that defines a software interface between an operating system and platform firmware.. its not that because odin can't load it... odin cant load if for many reason which can be the flash chip has been corrupted so the full size cant be read or the checksum mismatched... only fix i believe it there is if odin has a special switch which ignore checksums or it had a grandfather program we don't have access to....
bottom line is the flash chip aka hard drive from the note is not formatted and/or partitioned so its not accepting the firmware aka the os.......
we need the chinese that made these thing to say whats missing.... or a samsung tech so leak something...
PS maybe if someone force a SGS2 rom on it since they're close devices, that might set the flash back in order then try the note rom.... preferably someone with a busted device that wanna take the leap.... will be interested to see where the SGS2 rom flash stops.... crazy idea but who know might work after all the device is already not working...
Click to expand...
Click to collapse
makes a lot of sense.
so do you think its an issue in the chinese i9220 kernel itself? or was it an issue created with angeloms kernel of i9220?
androidindian said:
makes a lot of sense.
so do you think its an issue in the chinese i9220 kernel itself? or was it an issue created with angeloms kernel of i9220?
Click to expand...
Click to collapse
I'm actually running chriskelo rom, i did flash the chinese ics first then the chriskelo... my phone works fine.. before the chriskelo i did flash team ics but was getting massive FC so i tried to flash back the GB but it would just stuck at modem which naturally comes after bootloader.... so what i did was download a GB Modem for recovery then flash it then reflash rocket rom v22 all in recovery and my phone was back up and running in a matter of 20 mins
as response to the i9220 and N7000 differences there must be some internal differences which only samsung knows cant just be language and region thats controlled by the csc...
CSC = Country Sale Code
CSC code depends on the region where the phone was sold.
CSC contains the phone settings (internet, wap, mms...), specific applications which available in certain regions, and operator customizations.
CSC code could be changed by flashing a new firmware (including CSC file) on phone. That will change phone language and settings.
Use *#272*IMEI# code on phone to view the list of the available CSCs, or change CSC.
china have many different mobile rules that the rest of the world so its more than just the firmware.....
I just made a thought.... can someone try to download a firmware that has all the pieces some can be found in my guide in my sig and flash the phone in the reverse order... that is flash only the CSC file then the phone file then the PDA then lastly the bootloader.... can someone please try them individually... and report back...
antiguangenius said:
I'm actually running chriskelo rom, i did flash the chinese ics first then the chriskelo... my phone works fine.. before the chriskelo i did flash team ics but was getting massive FC so i tried to flash back the GB but it would just stuck at modem which naturally comes after bootloader.... so what i did was download a GB Modem for recovery then flash it then reflash rocket rom v22 all in recovery and my phone was back up and running in a matter of 20 mins
as response to the i9220 and N7000 differences there must be some internal differences which only samsung knows cant just be language and region thats controlled by the csc...
CSC = Country Sale Code
CSC code depends on the region where the phone was sold.
CSC contains the phone settings (internet, wap, mms...), specific applications which available in certain regions, and operator customizations.
CSC code could be changed by flashing a new firmware (including CSC file) on phone. That will change phone language and settings.
Use *#272*IMEI# code on phone to view the list of the available CSCs, or change CSC.
china have many different mobile rules that the rest of the world so its more than just the firmware.....
I just made a thought.... can someone try to download a firmware that has all the pieces some can be found in my guide in my sig and flash the phone in the reverse order... that is flash only the CSC file then the phone file then the PDA then lastly the bootloader.... can someone please try them individually... and report back...
Click to expand...
Click to collapse
yes, before sending my phone to samsung yesterday, I did try that with KL8 firmware. starting from the kernel, bootloader, csc, ums, and at the end code/pda, but again stuck at factoryfs.img
http://forum.xda-developers.com/showthread.php?t=1532830 >> just saw this thread, makes me wonder.. if the chinese leak has something to do with this.
but when i was on cf repack, i could easily flash another kernel like angelom or another rom, only after angelom issues started.
were you able to flash via odin a stock rom being on cf kernel ics?
androidindian said:
yes, before sending my phone to samsung yesterday, I did try that with KL8 firmware. starting from the kernel, bootloader, csc, ums, and at the end code/pda, but again stuck at factoryfs.img
http://forum.xda-developers.com/showthread.php?t=1532830 >> just saw this thread, makes me wonder.. if the chinese leak has something to do with this.
but when i was on cf repack, i could easily flash another kernel like angelom or another rom, only after angelom issues started.
were you able to flash via odin a stock rom being on cf kernel ics?
Click to expand...
Click to collapse
I didnt still on ICS but I did went back to GB once no issue,,, but all this ICS issues is hurting my head.... I'm going back to GB NOW... I'll report in a few mins....
Hi, need help to get back to gb v20s and forget ics.First battery usage is crazy I have to charge it min twice a day,over night percentage goes down for 20 and few times phone shuts down for no reason.I did official update and no root. Anyway what do I have to do to have good old gb v20s back on my phone and use it normaly like before ics.Than you all for help.
dfrimmel said:
Hi, need help to get back to gb v20s and forget ics.First battery usage is crazy I have to charge it min twice a day,over night percentage goes down for 20 and few times phone shuts down for no reason.I did official update and no root. Anyway what do I have to do to have good old gb v20s back on my phone and use it normaly like before ics.Than you all for help.
Click to expand...
Click to collapse
i´ve been facing the same problem, but it was simple to solve it.
follow this, http://forum.xda-developers.com/showthread.php?t=1715272
meanwhile yesterday i´ve upgrades to ics v30B, and the phone it´s much better than with the previous v30A release.
hope i could help you.
Thanks for suggestion but I would rather like to go back to stock v20s instead of custom ROM.
dfrimmel said:
Thanks for suggestion but I would rather like to go back to stock v20s instead of custom ROM.
Click to expand...
Click to collapse
in that case the only help i can give you is:
to register in a portuguese forum androidpt and follow this http://www.androidpt.com/index.php?/topic/30923-howto-repor-firmware-original/
but i think you can find information about how to make samrtfdlash os original stock rom in XDA.
I tried method from this portuges forum but it throw me an error and proces stoped. Please anybody I really need help, today I got date 02.01.1970 date on my phone dont know how, and in one moment I was unable to lock phone because when I press power button printscreen occur this stock ICS give me just a trouble and I cant use my phone can you please help me get back to stock GB where everything went fine.
Hi guys,
Bit of an awkward one, I need to restore my Note from CM10 to a standard rom to send it back to Samsung for repair of the USB and screen burn in.
Only problem is the USB not working means I cannot do it via the PC, is there any other way I can sort this out or am I stuck with replacing the USB connection myself and stuck with a bad screen?
Maybe with mobile ODIN? Not sure if they can detect if I use that? Also any idea whats the best stock rom to use please? (UK Based)
Cheers for your help.
mobile odin is the way to go... while on cm, clean the data. then load any stock jb rom file and flash.. dont use ota survival option in mobile odin.
JonP81 said:
Hi guys,
Bit of an awkward one, I need to restore my Note from CM10 to a standard rom to send it back to Samsung for repair of the USB and screen burn in.
Only problem is the USB not working means I cannot do it via the PC, is there any other way I can sort this out or am I stuck with replacing the USB connection myself and stuck with a bad screen?
Maybe with mobile ODIN? Not sure if they can detect if I use that? Also any idea whats the best stock rom to use please? (UK Based)
Cheers for your help.
Click to expand...
Click to collapse
Just download some stock rom and flash it. Then reset flashcounter (& triangle) using triangleaway (I know older version worked on SGS2) and You're good to send.
Download the Stock ROM from Sammbile.com of your own country.
Use Mobile Odin to flash the STOCK ROM
Then reset the counter by Triangle Away, Yes it works fine.
And then send it to SC.
:good:
Thanks for the help guys, one last problem, how can I use Triangle away without root? As I guess I best not send it back to samsung with it rooted.
you cannot.. you will need to root. use TA and then unroot it again.
Was just reading the description on mobile odin and it says it doesnt increase the count so I should be ok just with that.... hopefully
flashing a stock rom doesnot increase counter. if your count is 0 and binary is official, then its fine
JonP81 said:
Thanks for the help guys, one last problem, how can I use Triangle away without root? As I guess I best not send it back to samsung with it rooted.
Click to expand...
Click to collapse
Yeah, You're right. Sorry, I gave You the wrong order.
First reset counter and triangle, then flash stock ROM (as it doesn't increase flash counter)