Database Users

[Q] Hard brick ?

Im at a loss i tried to do the voodoo lag fix and it did not work right so i tried to clockwork recovery and restore my nandroid back up and it gets stuck at lost&found or at halgps_config. So i have tried to odin back to stock and ive used the original files and the ji6 files aqnd all i can get to is the stick together and then galaxy s screen after that it will go blank and only the backlight on the bottom keys lights up. Odin always shows pass and works correctly am i missing something or is it really fubar thankd for any help..

Ok so you can get it to download mode correct? If so get the rom from eugene froyo that doesnt brick and the true stock rom run the froyo rom thru odin first then your gonna get an error message that ok pull the battery and put it back in download mode get ready to flash the true stock rom but on odin you have to click repartion on the top left then click start all good aftet that let me know how it works k
Sent from my SGH-T959 using XDA App

dont forget to take out your sim and memory card

aaron1992 said:
dont forget to take out your sim and memory card
Click to expand...
Click to collapse
That's not really necessary. I've had to do this twice in the last 24 hours and I left my SIM and MicroSD in and everything worked fine.

I did this same thing, but I can't get into download mode. Any suggestions would be GREATLY appreciated!

are you doing it the way like take your batt out, put your batt in, hold both volume buttons and plugging in usb cable? that takes you right to DL mode, but odin doesnt always recognize it so you might have to unplug and plug it back in.

I don't know where my head is at. I just wasn't using the correct steps to get into download mode. Its working fine now. Thanks for your help!

thanks for the info i will try eugenes 2.2 now and let you know

did the eugene froyo and then to stock and i dont know how but it worked like a charm only thing different is i got an error when i had repartition checked for stock rom but i unchecked it and bingo just like new thanks for the help these forums rock!!!!

Stuck on Galaxy S screen!

Hi guys I hope someone can help me, I rooted my S and did factory reset ready to install darkys 9.3 rom, installed cwm and CF-Root-XW_OXX_JV1-v1.3-BusyBox-1.17.1_NO-CWM.zip that cf file, everything went ok with odin and when the phone rebooted it wont get past the Galaxy S screen, cant get into download or recovery mode and when I hold the power button it goes off and then comes straight back on, is there anything I can do to sort it, I am on Virgin, 2.2.1 JPW, thanks for any help

Did you came from another custom rom before flashing Darky's?
Have you disabled any lagfix before flashing?

Hi m8. Stock and no lagfix applied. I have been in touch with Virmin and they are couriering a new phone to me tomorrow. Thx for the reply.

sarbe said:
Hi m8. Stock and no lagfix applied. I have been in touch with Virmin and they are couriering a new phone to me tomorrow. Thx for the reply.
Click to expand...
Click to collapse
No 3 buttons combo = JIG
Always Check that you have the 3 B COMBO, before flashing anything it's on a steacky thread!! (i think admin should change the color of the sticky thread).

Will they charge you for a new phone as you have a custom rom on the exchange .
jje

No 3 button combo m8.
It is on stock m8 after doing factory reset.

GOOD .
jje

Lagfix
I also encountered this. But my problem was that I had lagfix enabled when flashing a new kernel. Just reflashed the previous kernel and disabled the lagfix. Flashed the new kernel again and everything was good.

I also found this when updating from JM7 to JS5, directly.
Seems it was a patience issue. That screen can take a long time after a flash.
Once also it ended by a shutdown after a while. Reflashing to JM5 then to JS5 through the 3 combo buttons solved it + repartition

sarbe said:
Hi guys I hope someone can help me, I rooted my S and did factory reset ready to install darkys 9.3 rom, installed cwm and CF-Root-XW_OXX_JV1-v1.3-BusyBox-1.17.1_NO-CWM.zip that cf file, everything went ok with odin and when the phone rebooted it wont get past the Galaxy S screen, cant get into download or recovery mode and when I hold the power button it goes off and then comes straight back on, is there anything I can do to sort it, I am on Virgin, 2.2.1 JPW, thanks for any help
Click to expand...
Click to collapse
Man, hope you get/got your new phone but you fu**ed up. Your problem stands out like dogs balls. You've even put it in capital letters.
1. You flashed CF ROOT JV1-NO CWM.
JV1 = Gingerbread. You were on 2.2.1 Froyo. Of course it won't boot up.
NO CWM - means exactly that. What's the purpose of installing cwm/recovery then flashing a kernal that ends with NO CWM?? It doesn't support it. How were you going to flash darkys?
Man, not knocking you but you really need to read instructions before doing **** like this. Any 2.2.1 (maybe even 2.2) cf root version would have avoided this.
2. You say the phone was stock when returned because you factory reset. You forgot that you flashed a custom kernal after that based on firmware that hasn't even been officially released yet. The reason it wouldn't boot. So, it aint stock. Shouldn't matter anyway as Sammy will just force it into download mode and reflash.
3. Since you initially flashed with Odin, then 3 button method was working before. So, the lesson for us all is: jv1 kernal + froyo base = brick. Jig sellers aren't complaining.
I'm also with virgin but using docs 2.2.1 (or CM7 2.3.3 depending on the time of day). If your near Melbourne I'm more than happy to help out with your new phone.
Sent from my GT-I9000 using XDA Premium App

ttf said:
No 3 buttons combo = JIG
Always Check that you have the 3 B COMBO, before flashing anything it's on a steacky thread!! (i think admin should change the color of the sticky thread).
Click to expand...
Click to collapse
3 button combo must have been working initially as he flashed kernal with odin. It was the kernal that busted it.
Sent from my GT-I9000 using XDA Premium App

sxi200 said:
3 button combo must have been working initially as he flashed kernal with odin. It was the kernal that busted it.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Not sure, maybe he made it with "adb reboot download" command.

boot loop (black and white text)

hi,
info : bell GT-i900m
rom : darky's 9.2
so heres my problem. my phone crashed yesterday so i removed the battery and then when I launch it back i got stock in the Darky's boot screen. I was also unable to go to CWM to update to the last version of Darky's rom so i used odin to flash the original 2.1 and now whatever version of the firmware i try to flash on the phone install successfully in odin but i get a "Galaxy S GT-9000" that appear in loop every 5-10 second until i remove the battery. I still have access to download mode....
anybody have a solution ? should i install a stock rom and go to warranty ? or should I just trow it 2 second in the microwave so they dont see that i installed costum rom ?

Sounds like corrupt and faulty movinand. Send it back for warrantee. Don't even worry about what rom is on it, it's a hardware fault. I sent mine back with a half booting custom froyo with speedmod, they didn't care. If you want to be safe, just flash a stock rom quickly. Don't microwave it...
Sent from xda premium app on i9000m.

thanks a lot i'll send it to bell tomorrow

Can you boot the stock 2.1 you installed through Odin?

Flash jpc with repartition.
Flash jl2 on top. If that still doesnt work, then its most like the good ol' faulty chip.
REFER TO THIS

Daneshm90 said:
Flash jpc with repartition.
Flash jl2 on top. If that still doesnt work, then its most like the good ol' faulty chip.
REFER TO THIS
Click to expand...
Click to collapse
Flashing the JL2 on top/after JPC is done WITHOUT repartition!!! just clarifying that, learnt from reading on here and helping a couple of people with them, lol.
(the i9000m's don't like repartitioning and flashing done at the same time, needs restart between them.. not a clue why, they're "special", lol.)

Flash Boot and spl.bin with heimdall. This is The solution.

It is definitely your bootloader.... flash jl2 firmware but there is a fixed one somewhere here on xda as the one from samfirmware is missing dbdata. Worked like a charm for me. (I also have it on my laptop somewhere pm me and ill find it) then you should flash superoptimized kernel or speedmod kernel via Odin with reboot unchecked. You should have recovery back. I've been through this issue and spent hours trying to get back to normal.
I have a few files to get you running if you get stuck....like I said just hit me up with a pm
Sent from my GT-I9000 using XDA Premium App

solved

Hi all, i have a problem... my phone wont boot when i press power button it just shows the i5800 screen, BUT i can get to download mode but that wont help because i flashed again with odin and it said "passed" but its stuck on i5800 screen. i have tried everything... it all started today when my phone fell from my pocket and the battery flew out. so i think it might be broken or something. if you know what to do please help
EDIT: it seems i can flash eclair but when ever i try to flash ANY custom ROM (POX, indroid, lestatious, kyrillos) it stucks on the i5800 screen...

What ROM you flashed?
Sent from my GT-I5800 using XDA App

Because i had the same problem... when the flash is very fast mostly something is wrong
Sent from my GT-I5800 using XDA App

im flashing original eclair fw and then ill try to upgrade it to 2.2 via kies and then ill post it to repair center

liilaaluu said:
Because i had the same problem... when the flash is very fast mostly something is wrong
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
this is not the same... it fell out of my pocket and never booted again

super bump please help!

try shaking the phone
keep it near your ears and shake
if you hear some sounds then maybe something is broken
roll back to eclair and try updating via kies-that may help a lot
if updated - take to service center
even if not
take to service center and tell them i never used kies so not on froyo(if they ask)
One more thing
Do this all after some time of no flashing,rooting,anything like that to the phone
let it be as it is for some time
sometimes this really helps(hpnd wid me)

cdesai said:
try shaking the phone
keep it near your ears and shake
if you hear some sounds then maybe something is broken
roll back to eclair and try updating via kies-that may help a lot
if updated - take to service center
even if not
take to service center and tell them i never used kies so not on froyo(if they ask)
One more thing
Do this all after some time of no flashing,rooting,anything like that to the phone
let it be as it is for some time
sometimes this really helps(hpnd wid me)
Click to expand...
Click to collapse
i cant update to any froyo ROM... not via odin OR kies...
what will i say to them? sorry i cant install any C-ROM only stock eclair can you fix it? i mean they have to repair it because i pay 4e month so they will repair it no matter what... but still that would sound pretty dump if i go there and say: help me i cant install any C-ROM

Have you tried the usual as in taking the battery out for a minute, wiping data/cache + factory reset? Then trying to install as stock JPM? And have you just waited for several minutes for it to go past the I5800 screen? If it takes a moment for it to gather its bearings after a sudden drop.

PolarSoul said:
Have you tried the usual as in taking the battery out for a minute, wiping data/cache + factory reset? Then trying to install as stock JPM? And have you just waited for several minutes for it to go past the I5800 screen? If it takes a moment for it to gather its bearings after a sudden drop.
Click to expand...
Click to collapse
i took battery out for half an hour then i rebooted and i gave 40 minutes time to get past the i5800 screen, havent tried stock jpm, but i have wiped everything.

jazux said:
i took battery out for half an hour then i rebooted and i gave 40 minutes time to get past the i5800 screen, havent tried stock jpm, but i have wiped everything.
Click to expand...
Click to collapse
As we Finns would say at this point... Perkele! It is dead, man. One last resort is stock JPM. Maybe you need to risk it and stick in the bootloader aswell...

Try flashing an earlier FroYo version like JP9 and then flash JPM or some other new version.
Sent from my GT-I5801 using Tapatalk

PolarSoul said:
As we Finns would say at this point... Perkele! It is dead, man. One last resort is stock JPM. Maybe you need to risk it and stick in the bootloader aswell...
Click to expand...
Click to collapse
yeah i have said that today many times i have flashed eclair with bootloader so its not a problem

few poeple has similar issue. when flashed jpf (with bootloader), problem is gone.

hodostamas said:
few poeple has similar issue. when flashed jpf (with bootloader), problem is gone.
Click to expand...
Click to collapse
tried flashing jp9 with bootloader and it goes to samsung logo but thats it... but well thats progress too

flash eclari -> try updating with kies -> get stuck and tell them that you got stuck while updating with kies

jazux tell us how u solved :-(

Mr.Gamer said:
jazux tell us how u solved :-(
Click to expand...
Click to collapse
the solution was simple i bought a new sd-card and BAM, my phone booted with froyo i dont know what was wrong but my phone just wont boot if theres sd-card inside... maybe its because it fell from my pocket, something broke and now it wont boot with sd inside

stubborn_d0nkey said:
flash eclari -> try updating with kies -> get stuck and tell them that you got stuck while updating with kies
Click to expand...
Click to collapse
did that already didnt work but i solved it already so...

[Q] S4 Bootloop, Can enter download but not recovery

Hi,
I have been searching and searching. I tried to install a kernel to my phone, its been forever so i don't remember which one.
It just reboots every 5 seconds without any screens coming up. I can not get into recovery mode
I can get into download mode and have flashed stock I337UCUAMDB_ATTAMDB_I337UCUAMDB with odin, but it doesnt fix anything.
What can I do to get to stock recovery and fix my phone?

What happens if you put it on download mode and then cancel with vol down

It falls back into the bootloop of restarting every 5 seconds with no screens coming up. No entry into recovery.

And if you pull the battery and put it back in does it try to boot?

What firmware were you on and was it loki'd if you were on mdl?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

I have taken the battery out and replaced it. It does not automatically try to boot. After pressing power it goes into the same boot cycle. Also, thank you for your quick attention!

megatilter said:
I have taken the battery out and replaced it. It does not automatically try to boot. After pressing power it goes into the same boot cycle. Also, thank you for your quick attention!
Click to expand...
Click to collapse
When did it start doing what's it's going. Did you do anything before hand? Do you know what firmware you where on before you tried odin? Was it mdb?

"What firmware were you on and was it loki'd if you were on mdl?"
Previous to my obvious blunder with the kernel download, I was using goldeneye rom from android develepment, sucessfully.
Dont know if that answers the question but i have also tried to flash AMDL with odin but have the same results.

megatilter said:
"What firmware were you on and was it loki'd if you were on mdl?"
Previous to my obvious blunder with the kernel download, I was using goldeneye rom from android develepment, sucessfully.
Dont know if that answers the question but i have also tried to flash AMDL with odin but have the same results.
Click to expand...
Click to collapse
When you used odin did you only have f.reset and auto-reboot checked and flashed the md5 file in PDA

jd1639 said:
When you used odin did you only have f.reset and auto-reboot checked and flashed the md5 file in PDA
Click to expand...
Click to collapse
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.

megatilter said:
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.
Click to expand...
Click to collapse
I think you've broken it too. Sounds like you flashed the wrong kernel and at that point you were more or less hosed. Look into jtag, mobiletechvideos.com. They can probably fix it. It'll cost you $60.00 +
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

jd1639 said:
I think you've broken it too. Sounds like you flashed the wrong kernel and at that point you were more or less hosed. Look into jtag, mobiletechvideos.com. They can probably fix it. It'll cost you $60.00 +
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
i've never seen a kernel hard brick a device or corrupt the recovery partition. i also rarely see a user flash a file and not remember what they just flashed. he/she possibly flashed an incompatible kernel or flashed a non-loki'd kernel without flashing loki-doki. either way, recovery would still be accessible to correct this issue. i feel that there is more to this.
OP, see jd's jtag post above.

megatilter said:
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.
Click to expand...
Click to collapse
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA

megatilter said:
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA
Click to expand...
Click to collapse
Great news! You got lucky, make sure you read and learn on xda. And always know what you flash.

megatilter said:
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA
Click to expand...
Click to collapse
Care to share how you got Kies working? I have a similar problem and I can't get Kies to recognize my phone.

Fix!
So What you gota do
1. Pull Out Battery Put back in
2.Go To Download Mode
3. Download The TWRP.tar For Your Phone
4.Run Odin as Admin, Tick Pda, for pda select the TWRP.tar
5. Hit Start, Then Pull Out battery put it back in
6.Get A Micro Sd And Put The Cyanogenmod Rom, and the gapps the ones for your phone
7.Insert microsd in phone
8. Boot Recovery and go to mounts and mount the microsd
9, Go Advansed, file manager, ext sd, And Copy the cyanogenmod and the gapps to internal storage
10. Flash the cyanogen mod and the gapps. DO THIS PART CAREFULLY OR MIGHT HARD BRICK!
11. Reboot And youl boot to cyanogenmod! OH yeah! Replay if this helped or if you have any problems