So i tried to updated to a custom firmware after i JUST received my galaxy S back.
And it got bricked.
It failed during the initial flash with Odin, no big worry i thought as i'll just reflash it. It constantly failed until I changed the USB slot. Now after I've even completed the flash the phone boots up shows the "GT-i9000/m" logo then shows those 9 bars that show its trying to load the battery charger. Then the screen goes black and it tries that over and over again.
Anybody had this problem? I think it's a soft brick and can be resolved before sending it back in and losing the phone for another month.
is download mode working then ? does odin recognise the phone ??
if so download a stock firmware with all 3 files and pit. and use re-partition. and see how that goes.
actually if it is a software problem there are lots of possible procedure to fix that just reflash it with an official firmware using odin
I've tried the following:
use odin 512pit and a tar file and using odin with a 803pit and a tar file.
Both resulted in the same thing.
Is there a specific FW i should try?
edit:
With and without repartitioning.
try JM8 with PIT and pda.modem,csc. and re partition again.
I know wher eto get JM8, but how/where do I get the PDA.modem and csc?
hmm yea i know what u mean, most modern firmwares only come in 1 file now. download that. but im not sure what pit to use. il have a look now.
i think its 512 pit
here try this
Tried everything. I think it might be a hardware error.
Last ditch effort of Jm8 in odin 1.0 now... will let you know if it works.
Edit:Nothing worked.
Gonna go return the phone/send it back to samsung.
Double EDIT:
Flashed the phone back with JL2 that i got from Samsung and checked EVERYTHING in ODIN. Phone went past the boot logo repetition and into the "S" but doesn't do anything more. Just gets stuck after that. (corrupted internal SD)
so if the JL2 didnt succeed what would be on it at present ? if its a custom rom just go back to odin do a flash and disconnect half way through and totally brick the phone..
then blame it on a kies update when you return it. you dont want them to find out you have modified it in any way not recommended by samsung. or they may not replace and may charge you.
Related
Hi
Has anyone discovered how to solve the problem of the black screen after logo S
the phone is dead?
Everything started suddenly. I think the voodoo lagfix was failed and the phone
froze. I rebooted but it stayed at the Logo S and I could here the robot voice
of the voodoo lagfix trying to do something.
I left the phone for few hours but nothing. I did that few times.
Then I decided to flash it with Odin.
After 10 flashes with different firmwares and different pit
the phone at the first boot was going to the recovery and was saying
that it can not mount the flash block. I could not even wipe the partitions because
of the mount problem. When I was starting the phone it was going to the Logo S
and then black screen and it was dead.
After flashing with Heidel I was able to overcome the mount problem
but again the phone was dead after the Logo S.
Do you know how to overcome this dead situation after the logo S?
I want to flash it with any ROM as long as it works and then I will reflash it with Kies.
I also tried to flash it with Kies during download mode but Kies keeps trying
to find it but at the end it fails.
I have a 3 button phone but for some reason I am unable to properly flash it.
Any suggestions before I throw the phone out of the window??
Thanks
You are experiencing the sdcard corruption problem. No way to fix it. Phone needs to be replaced. No way to fix it.
I though the repartition in Odin does that thing.
Is there any hack which will repartion and format the internal SD card?
Ive had this happen a number of times. Dont know what causes it, but I find that if I limit the amount of extra mods, I seem to be ok. Extra Mods, like Lag Fix (my Bell seems just fine without it running on jpk), and anything that really involves modifying the system files... But gotta love you guys that work on these things, you keep the scene alive.
Anyway what I do to fix that problem is Flash back to TMobile Vibrant ROM and for whatever reason it works for me. Filename that I use is T959UVJFD, forget where I got it, but its on here somewhere. I have only ever used pit 512, and if I have to, I go back to JH2 or JM8 modem and CSC.
Id try it without flashing the Radio and CSC first, if it doesnt work try changing them.
Good Luck,
By the way I am now running JPK, using the JH2 radio and CSC and have the 850 band on Bell (at least I think I have it, my phone normally runs on 1900), rooted, and no other mods.
So you are saying that you recovered from this black screen and can't mount the dbdata?
Interesting.
I will try it. I dont care if the rom does not really work. I want the rom to re-format
the internal SD. After that I will flash my nandroid.
I think we need a debugging kernel which we can flash it and it can give us all the necessery utilities i.e. parted, kernel with all file system support, nandroid,
applying the update.zip from the external sd etc
I will post the result later. I hope your trick to work
unfortunatelly I have the same results
For a moment I thought I can see something.
I had shell so I did the adb shell and I could see the redbend_us
which I think it is from the voodoo lag fix.
After the second reboot I lost everything.
I flashed it with the rom you suggested but with everything.
I will try without the modem but I think it will not make any difference
sounds like you have this problem
http://forum.xda-developers.com/showthread.php?t=793404
i also face this situation . . what i done was
1. install JM8 over stock firmware
2. then tayutama ROM with voodoo lag fix v 1.1
3. after my phone works well and i was happy
4. then i do factory reset cause of my internet doesnt work but market works
5. then i got some weird massages on my phone . . they keep coming
6. i decided to flash again with JM8 . .
7. i flashed the phone then the these thing coming to me
boot animation and after black screen . . . . .ive flashes four times with JM8 but didn't worked
ive then decided to do some froyo build on the dead phone
then i flash my phone over JPK with 803.pit
successfully flashed but on recovery screen stops with some error
then i reflashed it with JPK + 512.pit . . .
then my phone booted and runinng JPK
thats cools down my hart . . . .still i remember that 1 hour with no screen phone
now using JPK + Doc's ROM with OCLF v2+
abt JPK its cool with new features . . . . .
i think lag fixes done some thing when we flash . . .
think we have to remove lag fix before the flash
but how ?????
I tried to flash with the JPK as you suggested with 512 and 813 pit
and at both times it gave me the error
it can't mount the dbdata and sd
Of course as usual goes to Logo S and then I have the Black screen of death
Hmmm, kinda strange. I have never used the Voodoo fix, but have played with the One-Click fix since not using it my phone seems much more stable. Not sure if it is related.
Anyway did you try a Wipe after flashing the TMobile Rom? And in recovery does it still give you the errors? If memory serves me correct after flashing that ROM, the errors I was getting in Recovery mode were gone.
Did you try JPK with repartion enable . . .try it with 803 first and after 512 . .
think it will work remember to repartion enables
I tried everything. I think I flashed me phone more than 20 times.
Yesterday I tried it flash it with Kies assuming kies will format the internal SD.
THere is a registry key for emergency mode and I enabled it.
I put my phone in download mode and kies detected it and start flashing with the
original firmware.
When the procedure finished kies powered off the phone.
That was the last time I saw my phone alive.
I can not power it on. It is dead.
I dont know what Kies did to the phone but the phone is dead
Now I have to send it to Samsung
Guys... I´m in trouble... I´m on JPM and flashed CF-Root-JPM-v1.2-Busybox-1.17.1 but my phone was taking too long, like more than 20min at Galaxy S boot. I knew something did go wrong, removed the battery and I entered download mode again and re-flashed... Same thing! My phone is not getting past Galaxy S boot up picture!! I can't enter recovery mode but can enter download mode! Is there anything I can do to bring my phone back to life?! PLEASE HELP ME!
I already tried to flash new roms in odin. My device is recognized but odin hangs and does nothing...
I need some advice on this, did I kill a new phone?! I´m scared
Please Help!
- UPDATE: SOLVED!
Hi there, I'm having the same problem on my I9000B. Please help me.
This is my story, I had upgraded my 2.1 firmware to VIVO's 2.2 Froyo via KIES with the Kies Registry Patcher (used ZVV). Everything worked perfectly, but I wanted to root my I9000B so I made the terrible mistake of using CF-Root via Odin, (http://forum.xda-developers.com/showthread.php?t=788108) following the exact instructions. The kernel replacement (zImage file) was for the I9000 so I had the touchscreen problems. When the phone booted showed Samsung galaxy S GT-I9000B and then inmeadeatly the "B" dissapeared.
Because of my n000bness I tried to use the zImage file from this ROM (VIVO's) (http://forum.xda-developers.com/showthread.php?t=858483), by downloading my own .tar created file (with 7-zip) of the zImage file. Here is were things went down. I got the android - USB cable boot icon. I could not go into recovery mode but I could do download mode, so I re-flashed VIVO's ROM (the one published here) with Odin:
I used the 803 .pit file, Odin 1.3
I did not check re-partition
I selected the ROM as the PDA file and I left PHONE and CSC blank.
the ROM was downloaded to the phone and Odin did not gave me problems.
My problem here is that I get the black screen with vibrations from time to time on boot. This is exactly what happens:
The phone starts showing "Samsung galaxy S.... GT I9000B (at least shows "B")
I can get into recovery mode but the following appears:
Code:
update media, please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please us UI menu for format and reboot actions.
copy default media content failed.
Then I did a factory reset, succesfully completed, tried again flashing the ROM but with Re-partition box checked (as instructed here: http://forum.xda-developers.com/showthread.php?t=723596) but the same stuff happens.
Please tell me what to do! I know it was a stupid mistake trying to fix ony the zImage file, and stupider was using CF-Root on my non-compatible device.
PS: I can get into download mode with no problems
Code:
pda i9000bvjjpa
phone i9000bvjjpa
csc i9000bzwjp3
I have exactly the same problem
but i can go into recovery mode and download mode.
the galaxy screen is I9000 and my sgs is I9000B
any ideas?
A friend of mine has the same issue on his SGS. Both recovery and download mode working.
Have you done JUST like this:
Figueiredo81 said:
Guys... I´m in trouble... I´m on JPM and flashed CF-Root-JPM-v1.2-Busybox-1.17.1 but my phone was taking too long, like more than 20min at Galaxy S boot. I knew something did go wrong, removed the battery and I entered download mode again and re-flashed... Same thing! My phone is not getting past Galaxy S boot up picture!! I can't enter recovery mode but can enter download mode! Is there anything I can do to bring my phone back to life?! PLEASE HELP ME!
I already tried to flash new roms in odin. My device is recognized but odin hangs and does nothing...
I need some advice on this, did I kill a new phone?! I´m scared
Click to expand...
Click to collapse
1. Enter your phone in dl-mode, but don't connect yet.
2. Open Odin, tag re-partition, auto reboot and f.reset time, make sure efs clear and bootloader -fields are NOT checked. select CORRECT PIT-file (2.1 ROMS usually 512, 2.2 ROMs many times 803, samfirmware always tells which one to use next to the dl-link of a ROM-file), enter your phone in dl-mode, plug, wait it to be recognized by Odin.
3. Click start, wait until Odin shows PASSED, unplug your phone, remove the battery for 30 seconds, enter dl-mode again, don't plug just yet.
4. In Odin, click Reset. Then select PDA, Modem and CSC files compatible with the PIT-file used in re-partition, plug your phone, make sure re-partition NOT checked and no PIT-file selected (once again, make sure you use correct PDA for the PIT you flashed). auto-reboot and f.res.time should be selected. Make sure efs clear and bootloader -fields are NOT checked.
4- Plug your phone and when recognized, click start. Wait to be passed. Now your phone will boot (or if not, boot manually) and should work just fine.
Edit: Try to put Eclair ROM, for example JM2, not jpa, and see if it works better.
Thanks!!
Sir, you have saved my phone and my whole week. This is what I did:
With this method I tried the Vivo Brazil's 2.2 Rom again and did not work, same error, tried using both 803 and 512 pit files.
Then I downloaded an 2.1 firmware (JG9, which was the same that came with the new phone) from Claro Brazil that I found on google and flashed it with the 512 pit and worked perfectly. I had been strugling with this problem the las 6 hours and solving this was urgent because I'm going to vacation now.
Now I can re-update via Kies and return to Froyo were everything worked.
I will not try to do things like this in such a risky way (risky because I don't know)
Thank you very much.
Margaliini said:
1. Enter your phone in dl-mode, but don't connect yet.
2. Open Odin, tag re-partition, auto reboot and f.reset time, make sure efs clear and bootloader -fields are NOT checked. select CORRECT PIT-file (2.1 ROMS usually 512, 2.2 ROMs many times 803, samfirmware always tells which one to use next to the dl-link of a ROM-file), enter your phone in dl-mode, plug, wait it to be recognized by Odin.
3. Click start, wait until Odin shows PASSED, unplug your phone, remove the battery for 30 seconds, enter dl-mode again, don't plug just yet.
4. In Odin, click Reset. Then select PDA, Modem and CSC files compatible with the PIT-file used in re-partition, plug your phone, make sure re-partition NOT checked and no PIT-file selected (once again, make sure you use correct PDA for the PIT you flashed). auto-reboot and f.res.time should be selected. Make sure efs clear and bootloader -fields are NOT checked.
4- Plug your phone and when recognized, click start. Wait to be passed. Now your phone will boot (or if not, boot manually) and should work just fine.
Edit: Try to put Eclair ROM, for example JM2, not jpa, and see if it works better.
Click to expand...
Click to collapse
Well, the good news is that it appears that the "E:Can't mount /dev/block/stl10" error msg can be resolved.
http://forum.xda-developers.com/showthread.php?t=788850
This thread discussed this specific error message. For some reason, they're claiming that flashing JPC with 512 pit and repartition checked is doing the trick. I'm assuming this will result in data loss but I guess that's better than losing the phone entirely You should be able to flash to whatever firmware you want afterwards (assuming it works).
JPC:
http://www.multiupload.com/WB3104V8G0
Pass = samfirmware.com
512 PIT
http://www.multiupload.com/I5WICSBFJ1
Report back if this works for you.
Please, post the link or give me directions for the Claro's ROM. I am having the same problem here.
Thanks.
gtg2 said:
Well, the good news is that it appears that the "E:Can't mount /dev/block/stl10" error msg can be resolved.
http://forum.xda-developers.com/showthread.php?t=788850
This thread discussed this specific error message. For some reason, they're claiming that flashing JPC with 512 pit and repartition checked is doing the trick. I'm assuming this will result in data loss but I guess that's better than losing the phone entirely You should be able to flash to whatever firmware you want afterwards (assuming it works).
JPC:
http://www.multiupload.com/WB3104V8G0
Pass = samfirmware.com
512 PIT
http://www.multiupload.com/I5WICSBFJ1
Report back if this works for you.
Click to expand...
Click to collapse
worked here
thanks
thanks for the help i love you no homo !
Un Loko said:
Sir, you have saved my phone and my whole week. This is what I did:
With this method I tried the Vivo Brazil's 2.2 Rom again and did not work, same error, tried using both 803 and 512 pit files.
Then I downloaded an 2.1 firmware (JG9, which was the same that came with the new phone) from Claro Brazil that I found on google and flashed it with the 512 pit and worked perfectly. I had been strugling with this problem the las 6 hours and solving this was urgent because I'm going to vacation now.
Now I can re-update via Kies and return to Froyo were everything worked.
I will not try to do things like this in such a risky way (risky because I don't know)
Thank you very much.
Click to expand...
Click to collapse
JM2 with pit method is perfect. my "E: can't mount /dev/block/mmcblk0p1" problem has finally been solved.
Thanks
This worked for me.
http://samsunggalaxysforums.com/sho...CIAL-STOCK-FROYO-2.2.1-IS-OUT!!!!-(i9000XXJPU)
???I bought my Phone from CSpire but stuck on At&t Logo???
Samsung Galaxy s Showcase stuck on the At&t Logo...Will not let me go into Download mode??? Help please?
So I got my Galaxy S..used from a friend. it's a used unit and it's running eclair DXJG4 firmware. I've decided to upgrade it to froyo via odin (MTP Driver issue made me not use kies anymore)..At first I tried ticking repartition and flashed it and odin fails and the phone wont go past the galaxy S GT-I9000 screen. (I downloaded my DXJPA firmware from samfirmwares and I ticked both three PDA, PHONE and CSC and all of them are linked to the single tar). I tried the second time...repartition ticked AGAIN (I think this is the main problem cause now) and only ticking PDA. Odin passed. But phone still stuck at boot screen (the Galaxy S GT-I9000 screen). please help?
Ive read some topics..seems that I need to reflash it back to eclair JG4 firmware with repartition ticked and flash froyo without repartition? The most confusing part for me is whether to tick phone and CSC or not.
hi heres a guide on dxjpa http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install-froyo.html
btw dxjpa isnt the latest, dxjpe is latest
guide to dxjpe:http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install-froyo.html
You can try this.
When the phone is froze on the screen, connect it to the PC. If you can access your SD card from within Windows, format the sd card. Power down the phone, and power it back up. It should then boot past the screen.
i think the main problem is about im using a single tar for csc, phone and pda. might need to reflash though.
electro: I can't, its stuck in the galaxy S GT-I9000 screen. windows wont recognize it.
kongmyy said:
i think the main problem is about im using a single tar for csc, phone and pda. might need to reflash though.
electro: I can't, its stuck in the galaxy S GT-I9000 screen. windows wont recognize it.
Click to expand...
Click to collapse
redownload it from the link that i have gave u.have try using it and it definitely works
so I can just reflash it with the correct csc, pda files that is in the link you given and it will work? Or i need to downgrade to eclair first and then upgrade again. because I'm worried my last 're-partition' with the wrong files might need me to downgrade.
im downloading the files right now. wish it could be downloaded soon though, my connection is slow right now.
which one u downloading dxjpa or dxjpe?
u have to enable repartition
dxjpa. okay i will enable. wish me good luck
shouldnt have any problems if u follow the steps on the blog
tried it and now my phone works nicely. Thanks!
probably think u should upgrade to dxjpb since it is actually based on dxjpa with some cleanups of the rom
Hello Guys,
I'm quite an intensive flasher and never had a problem ever, running lovely ICS at the moment and my phone is fine. But here's the problem, a friend of mine also has a SGS and hers suddenly got stuck in a bootloop today (she had stock on it, never did anything to it and had no flashing history or something). So I said, let me try to fix, I should be able to reflash the software and it should be working again. Sadly enough, it didn't go as I hoped.
I flashed JVU trough Odin with Pit file.
(Sadly enough I am not allowed to post pictures, goo.gl/28pPX < pic link)
And as you can see, No problems there. Everything went fine. So the phone boots, and then this happens:
goo.gl/D0vnU
This happens everytime, no matter what i try to flash. First time I have ever seen this and I just don't know what do with it..
When I try to reboot the phone it just starts bootlooping again. I'm clueless, so can anyone help me with this ?
Thanks in advance!
Stoux
I would just flash the same jvu but with bootloaders
Sent from my GT-I9000 using Tapatalk
Try to flash this rom is one of the best Gingerbread roms, just follow all the instructions there.
good luck
You say : flashed jvu through odin...did you have 3 files(phone , modem ,cscand odin pit file) and have repartition checkbox ticked in odin?? and can you get phone into download mode???
Stoux2 said:
Hello Guys,
I'm quite an intensive flasher and never had a problem ever, running lovely ICS at the moment and my phone is fine. But here's the problem, a friend of mine also has a SGS and hers suddenly got stuck in a bootloop today (she had stock on it, never did anything to it and had no flashing history or something). So I said, let me try to fix, I should be able to reflash the software and it should be working again. Sadly enough, it didn't go as I hoped.
I flashed JVU trough Odin with Pit file.
(Sadly enough I am not allowed to post pictures, goo.gl/28pPX < pic link)
And as you can see, No problems there. Everything went fine. So the phone boots, and then this happens:
goo.gl/D0vnU
This happens everytime, no matter what i try to flash. First time I have ever seen this and I just don't know what do with it..
When I try to reboot the phone it just starts bootlooping again. I'm clueless, so can anyone help me with this ?
Thanks in advance!
Stoux
Click to expand...
Click to collapse
You just have to find a small file called " dbdata.rfs " amd flash it through odin (in pda ) .
Or you can always download a full firmware which have four files .pit, csc, modem, code and flash them with odin and u will be good to go!
Sorry for the late reaction (and the bump of the thread).
I did flash trough odin, like 9001 times. Everytime I would just get into a bootloop, Stock or Custom Rom. I was able to get in CWM but that was just a mess. It had to do with a faulty SD-Card or something, its @ Samsung now. Anyways, thanks for the help everbody!
Hello everyone- I hope someone can give me some advice i haven't tried yet on my issue. This is my first post and i searched through a million forums for ideas, my apologies if i missed anything or if anything below is unclear. I tried to list everything out that i have tried in case i missed anything.
Note 9 - SM-N960U (TMB) went into a boot loop randomly (possible after a Samsung update as it happened overnight).
Steps I've taken so far:
- Tried the normal steps first as instructed by Samsung, clear cache-partition, factory reset device etc - still stuck in boot loop.
- Took phone to authorized Samsung service center, they could not fix. phone now on blue screen "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC Software"
- Smart switch recovery software would not recognize the phone, updated drivers multiple times, still no detection.
-Downloaded stock TMB firmware from SamMobile (N960USQS9FUG2) - Tried to flash with Odin (versions 3.13 and 3.14 - patched and unpatched) kept getting stuck at vendor.img.ext4 in CSC file or system.img.ext4 in the AP file.
-Tried to Re-Partition without Pit file and with the pit file - PIT file name: CROWNQLTE_USA_SINGLE.pit - Odin would get stuck on same files.
-Tried to re-partition with Nand Erase selected and Pit file attached - Odin would freeze at setting the partition.
Is there anything else i can try or is this phone officially a paper weight?
You are able to flash firmware from the emergency screen. When one of my devices did this I was able to get things up and running with Odin flash from that screen. I can't remember what partition was broken when it happened on my Note 8, but the only way to fix was putting in new mother board. I'm not saying go this route. Might try combination firmware. I'm sure someone will chime in if I am wrong. I tried to flash stock on my SM-N950U after being rooted. It would show pass in Odin but would never boot..just bootloader. As I said above my only option was new motherboard. I wish I could find the message from a developer that helps me a ton, and which partition it was that was the issue. If I find it I will let you know.
butchieboy said:
You are able to flash firmware from the emergency screen. When one of my devices did this I was able to get things up and running with Odin flash from that screen. I can't remember what partition was broken when it happened on my Note 8, but the only way to fix was putting in new mother board. I'm not saying go this route. Might try combination firmware. I'm sure someone will chime in if I am wrong. I tried to flash stock on my SM-N950U after being rooted. It would show pass in Odin but would never boot..just bootloader. As I said above my only option was new motherboard. I wish I could find the message from a developer that helps me a ton, and which partition it was that was the issue. If I find it I will let you know.
Click to expand...
Click to collapse
Thanks for the reply @butchieboy, If you find those messages i would definitely appreciate it! I should have specified that i was able to run the Odin flash from the recovery page. That's a good idea to try combination firmware, never done it before though. Would i just try an older AP or CSC with the up to date other files? or just a combination of old and new and see if something happens?
Overall i think i may be in the boat you were in with your Note 8- something seems seriously wrong with the memory partitions that seem like it may be unfixable via flash. i'll have to see if i can find a motherboard that's worth the price to see if it's worth it at this point.
Combo firmware needs be on same bootloader that you are currently on