Database Users

i think i just broke my 2nd SGS

hey fellas
i just went to go from 2.3 back to darky ROM and my phone is having a fit, its constantly rebooting at the first boot screen, i still got download mode though
no matter what i try nothing works.
have tryed darky RE, JM5, JL2, JH1, DV3 the JVK, download EZBase now to see what happens
this is my 2nd phone i have ****ed up doing this i think

aussiesausage said:
have tryed darky RE, JM5, JL2, JH1, DV3 the JVK, download EZBase now to see what happens
this is my 2nd phone i have ****ed up doing this i think
Click to expand...
Click to collapse
Are any of those stock rom's you are trying, or are they all Darky's roms?
Flash a stock rom, hopefully that will get you up and running. After that, format your sd card.

couple of them are stock, none worked.
downloading a march 2011 stock firmware from samfirmware now, aswell as EZBase rom

If darkys is a 2.2.1 based rom then you need to flash to that base first.
Try a stock 2.2.1 firmware in odin with all 3 files and tick repartition. I use jpu and always works.
Sent from my GT-I9000 using XDA App

MY fix for broken phones is .
Use Odin flash Eclair with pit 512 and repartition checked .
Phone works flash base Froyo .
Phone works you can now customize as required .
Choose a rom this time that does not kill phone .
jje

thanks fellas, will try that.
i've flashed about 5 ROMS and tryed repartion and none have worked, will try a eclair, gotta go download one

ok, JPU did not work. 3 files, re-partion and 512 pit
oh dear

When you say jpu didn't work, did the process actually start in Odin and complete?
If not, just reboot download mode again, close and restart odin and try again.
Sent from my GT-I9000 using XDA App

yeah it said PASS, just got the stupid white reboot thing.
JE3 ( 2.1 ) halfed worked, it went into recovery, dont some **** then booted. then i got something like "kernel panic pload" with all this red writing ????????
i think that might be cause i got a 2.2 kernel flashed?
broken phone broken?

here is what im getting
Uploaded with ImageShack.us
LINKL http://img405.imageshack.us/i/img20110402030025.jpg/

sorry for the spam typing, now im getting this. and it goes to the animated SGS logo, hangs for about 1 minute then phone turns off
Uploaded with ImageShack.us

sorry for spam typing, now im getting this, it goes to the animated boot logo then hangs and turns off
Uploaded with ImageShack.us

thanks for the help guys. but phone is dead
it will not even turn on now, plug into charger nothing happens. held in power button for ages and it wont turn on, no download mode, nothing.
my 2nd SGS dies, this is 1 month old. time to call mobicity and warranty it
damn im sick of this thing

aussiesausage said:
thanks for the help guys. but phone is dead
it will not even turn on now, plug into charger nothing happens. held in power button for ages and it wont turn on, no download mode, nothing.
my 2nd SGS dies, this is 1 month old. time to call mobicity and warranty it
damn im sick of this thing
Click to expand...
Click to collapse
yes, happened that to me too. If it;s not starting anymore, than you must rewrite it's bootloader with JTAG...JIG won;t help. The point is, when you tried to go back on 2.2.1 you should first flash the bootloader with heimdal. With bootloader updated you shouldn't have any problem flashing back JM8 or something
sorry for you

Crysis21 said:
yes, happened that to me too. If it;s not starting anymore, than you must rewrite it's bootloader with JTAG...JIG won;t help. The point is, when you tried to go back on 2.2.1 you should first flash the bootloader with heimdal. With bootloader updated you shouldn't have any problem flashing back JM8 or something
sorry for you
Click to expand...
Click to collapse
may i ask what JTAG is?

There might be answer to your misery, check Yovi's thread, he found hard reset method for totally bricked phone.
Sent from my GT-I9000 using XDA Premium App

Edit. Just read you can not power up. Go with Jobiza's post.
Flash just a kernel in PDA ie voodoo or speedmod k13. Nothing else and auto reboot checked. After that flash away.
This happened to me and I tried different combos for hours till this method and it worked.
Good luck mate.
Sent from my GT-I9000 using XDA App

Don't know did you tried it, but if you are able to go to Download Mode, download JVK with bootloaders from XDA, start Odin check Re-Partition and Phone Bootloader Update select filef from new FW connect phone and it should do the magic I hope.
If not http://forum.xda-developers.com/showthread.php?t=1018620

Maybe last resort?
http://forum.xda-developers.com/showthread.php?t=1018620&page=2

^^^
Yeah aussiesausage!
Let us know if this works! You can do it!

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

ODIN DL09 --> reboots to recovery

Not really sure why it keeps doing this but after an ODIN to DL09 with re-partition, my phone just boots to stock recovery no matter what I do...cannot get Android to boot...A CM7 install went bad earlier during the install and since the reinstall has a reboot in it, it was stuck in a bootloop trying to install it...Anyway why isn't ODIN taking care of all of this? Do I need to ADB and clear something? Thanks for any help guys

dmasjz45 said:
Not really sure why it keeps doing this but after an ODIN to DL09 with re-partition, my phone just boots to stock recovery no matter what I do...cannot get Android to boot...A CM7 install went bad earlier during the install and since the reinstall has a reboot in it, it was stuck in a bootloop trying to install it...Anyway why isn't ODIN taking care of all of this? Do I need to ADB and clear something? Thanks for any help guys
Click to expand...
Click to collapse
I never used a pit when odining DL09 and it worked fine for me, maybe try it without it...
blazing through on my VZ Droid Charge

dmasjz45 said:
Not really sure why it keeps doing this but after an ODIN to DL09 with re-partition, my phone just boots to stock recovery no matter what I do...cannot get Android to boot...A CM7 install went bad earlier during the install and since the reinstall has a reboot in it, it was stuck in a bootloop trying to install it...Anyway why isn't ODIN taking care of all of this? Do I need to ADB and clear something? Thanks for any help guys
Click to expand...
Click to collapse
I had this happen to me the other day, you likely downloaded the wrong DL09 odin files. This is the DL09 you want (I bet it's several dozen megs larger than the one you have, if you did the same thing as me).
Flash that with the re-partition PIT and then you should be good.

Not sure what the issue was, but heimdall fixed it, thanks, will go back and odin DL09 now

KitsuneKnight said:
I had this happen to me the other day, you likely downloaded the wrong DL09 odin files. This is the DL09 you want (I bet it's several dozen megs larger than the one you have, if you did the same thing as me).
Flash that with the re-partition PIT and then you should be good.
Click to expand...
Click to collapse
Yes you're right, the DL09.tar.md5 I had is about 308 megs.......Weird....Thanks!!!!

[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

SM-n9005 major problem!

Hey
I just flashed my note 3 to android 5.0 with Odin, and if I would boot it up it the Samsung logo would freeze and then the phone would restart in a weird way- the screen flashes and phone vibrates a couple of times. I wiped data and cache but then it would get stuck at "Android is upgrading", everytime it got stuck at upgrading certain number of apps (like 32 out of 190) and at that point I would take out the battery. After this I boot up the phone and now the number of apps that needed to be upgraded were decreasing so I repeat the process of taking the battery out until I get it to boot up. So finally the phone boots up and I start setting it up and the "S health has stopped working" pops up and after a short time the phone freezes and restarts in a same way I mentioned above.
Does anybody know a solution for that? Phone works fine when I flash it to 4.4.2.

thecreator101 said:
Hey
I just flashed my note 3 to android 5.0 with Odin, and if I would boot it up it the Samsung logo would freeze and then the phone would restart in a weird way- the screen flashes and phone vibrates a couple of times. I wiped data and cache but then it would get stuck at "Android is upgrading", everytime it got stuck at upgrading certain number of apps (like 32 out of 190) and at that point I would take out the battery. After this I boot up the phone and now the number of apps that needed to be upgraded were decreasing so I repeat the process of taking the battery out until I get it to boot up. So finally the phone boots up and I start setting it up and the "S health has stopped working" pops up and after a short time the phone freezes and restarts in a same way I mentioned above.
Does anybody know a solution for that? Phone works fine when I flash it to 4.4.2.
Click to expand...
Click to collapse
did you update Modem and Bootloader before flashing lollipop??

nijom said:
did you update Modem and Bootloader before flashing lollipop??
Click to expand...
Click to collapse
No I didn't, can this be the cause of the problem? If so what kind of modem and bootloader do I have to install?

It might be best to start over by flashing the latest stock ROM from sammobile.com via Odin.

audit13 said:
It might be best to start over by flashing the latest stock ROM from sammobile.com via Odin.
Click to expand...
Click to collapse
I've tried it already. Flashed a stock rom via odin and even through kies, didn't work... Flashing new modem and bootloader doesn't seem to work either.

Were you able to successfully flash the latest stock ROM successfully or did it fail in Odin?

audit13 said:
Were you able to successfully flash the latest stock ROM successfully or did it fail in Odin?
Click to expand...
Click to collapse
It was successful in Odin but still doesn't work on my note 3.

thecreator101 said:
It was successful in Odin but still doesn't work on my note 3.
Click to expand...
Click to collapse
Is that firmware does not work ??
Are you sure you are flashing the firmware for your model ??
have you upgraded with no apps installed as it could be an app that's the problem .

JJEgan said:
Is that firmware does not work ??
Are you sure you are flashing the firmware for your model ??
have you upgraded with no apps installed as it could be an app that's the problem .
Click to expand...
Click to collapse
Yeah, im flashing sm-n9005 firmware as i have the same model, even tried flashing different regions. Im not sure how to flash with no apps installed, can you explain?

You're using the latest stock ROM from sammobile? Performed a factory wipe before booting the stock ROM for the first time? Tried flashing with a pit file?

thecreator101 said:
Yeah, im flashing sm-n9005 firmware as i have the same model, even tried flashing different regions. Im not sure how to flash with no apps installed, can you explain?
Click to expand...
Click to collapse
Are you plugged directly into a USB port, not a hub, Pc Usb only, it can make a difference, also check ya dont have Kies installed, this can also be a nuisance, AND IF you use a pit file, make sure you use the right one, Quite often phones become unflashable and report errors after an incorrect pit was used.

audit13 said:
You're using the latest stock ROM from sammobile? Performed a factory wipe before booting the stock ROM for the first time? Tried flashing with a pit file?
Click to expand...
Click to collapse
Not from sammobile, i used other site to download. I did do a factory wipe though, but haven't tried flashing with a pit file.