I am in desperate need of help you guys! I screwed up so hard that I don't even know where to begin...
THE SITUATION:
-Right now when I go to turn on my phone, it will only stay on the current SAMSUNG GALAXY S I9000 screen (the very first screen when booting your phone) and it keeps flashing in and out.
Before trying to use Odin to put back the original Kernal on my phone, it was just stuck as the SAMSUNG GALAXY S I9000 screen, still wouldn't start. <I followed this website step by step>
http://www.samsunggalaxysforum.com/...-to-a-stock-rom-after-installing-darky's-rom/
BEFORE ALL OF THIS EVER HAPPENED:
I finally rooted my phone and manage to download Clockworkmod recovery on my phone and then used it to flash Darky's 10.2 custom ROM. Everything turned out great except at the beginning of the boot, the screen turned all rainbow coloured, completely distorted, and it continued to do that. I then tried to go back to Recovery mode to do the Voodoo lagfix but I couldn't even get into the recovery mode anymore, it either wouldn't let me, or it did but the screen didn't go to it properly (more likely the first one). I read somewhere that if you reflash your phone again, it should make all the tweeks go away. So I tried that from the Darky's tools menu and ever since then, I've been stuck with the Boot Screen this whole time...
I already bricked my phone once, and that was before the Flashing Boot Screen.
I really need help you guys, I would at least like to have my phone back to the original basis, at least! Your help would be greatly appreciated!
THANK YOU
P.S. (i'm not that great at all this phone tweeking, but I've succeeded in doing it up until yesterday)
Can you get into download mode (vol down+home+power while putting the battery in)?
If you can, just reflash a stock or custom rom in odin (like a darky odin rom) as guided by whatever rom you choose.
If you cannot get into download mode then we should know that too.
Edit: oh it looks like you could (and hopefully still can). Try a different rom or reflash. Sometime things do go wrong but as long as you can get to the download screen you should be fine in the end.
G
gfacer said:
Can you get into download mode (vol down+home+power while putting the battery in)?
If you can, just reflash a stock or custom rom in odin (like a darky odin rom) as guided by whatever rom you choose.
If you cannot get into download mode then we should know that too.
Edit: oh it looks like you could (and hopefully still can). Try a different rom or reflash. Sometime things do go wrong but as long as you can get to the download screen you should be fine in the end.
G
Click to expand...
Click to collapse
Yes, I can get into download mode! (thank you for reading my post).
If it's not too much to ask, could you maybe find the ROM that would be good for me to flash, considering my situation?
I want to be sure that it's what the top tech guys would recommend
A link would be appreciated
thank you again!
I'd start with a Darky rom - lots of users - active forum and odin editions for your situation. I have to go but you'll find the link on the first page of the development section.
G
gfacer said:
I'd start with a Darky rom - lots of users - active forum and odin editions for your situation. I have to go but you'll find the link on the first page of the development section.
G
Click to expand...
Click to collapse
So in essence all I have to do is flash the Darky ROM V10.2 with Odin using the Download mode on my phone and it should be okay?
Wait one caveat. Was it a gingerbread rom or froyo? Use a Darky rom of the same type...
Then yes it should be ok if you follow their guide. Cross fingers.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
Wait one caveat. Was it a gingerbread rom or froyo? Use a Darky rom of the same type...
Then yes it should be ok if you follow their guide. Cross fingers.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
well...I did everything you said. The ROM is on there alright, it flashed and everything (And I know this because now when the boot screen STILL FLASHES, the darkcore & darky's rom logo are on it too).
THIS TIME AROUND:
The stock recovery seems to work...
any ideas??
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Alright I'll try and reflash the same one using a different version of odin the. I'll let you know what happened
gfacer said:
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
tried ezodin, flashed it, and i still get the exact same thing I've exhausted every single possibility there is!!!
I really need help on this, my warranty is not gonna do anything because i have the phone rooted..
If you flash a stock rom with pit the root is gone. It won't boot but they can't prove it was you either and I don't think it was you.
But see my other post on your other thread for one last thought.
G
Sent from my GT-I9000M using XDA Premium App
gfacer said:
If you flash a stock rom with pit the root is gone. It won't boot but they can't prove it was you either and I don't think it was you.
But see my other post on your other thread for one last thought.
G
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
okay that could be useful data potentially (let's hope it won't have to be).
If you didn't see my reply from the other thread, here it is:
Once I rooted my phone, I automatically went from Stock Froyo to Darky's 10.2 extreme edition. It worked and everything except for that color disfiguration and the clockworkmod recovery not working.
It's weird because after I flashed my first darky's rom, i checked the phone and it said that the firmware version was 2.3.X (I believe X may have been 4). So from what you're saying, I don't exactly think it has anything to do with the fact that I went straight from froyo stock to GB darky ROM.
So are you saying that I should flash darky's 9.3 for Froyo and THEN flash the latest version?
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Ok, so just to be 100% on this
-I should flash Darky's 9.2 froyo onto my phone,
-then I should flash regular GB onto my phone (Not sure about the bootloader part though, if you could clarify that)(Also where would I get JUST a stock GB ROM?)
-then I can flash a custom GB ROM?
gfacer said:
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
well i can safely say that flashing the 9.2 froyo rom was a fail. It's still doing the same old routine.
I just know that this problem can be fixed somehow without sending it in to bell or samsung or something.
roma17 said:
well i can safely say that flashing the 9.2 froyo rom was a fail. It's still doing the same old routine.
I just know that this problem can be fixed somehow without sending it in to bell or samsung or something.
Click to expand...
Click to collapse
I think you are right but other than trying again and again, which I've done before -though now I know why I had too - I am out of suggestions. Good Luck and if I have a brainwave I'll let you know.
Sent from my GT-I9000M using XDA Premium App
OK a few last brainwaves:
1) Try a fully complete stock rom with cache.rfs, dbdata.rfs, factoryfs.rfs, modem.bin, param.lfs, zImage, and sbl.bin (this was from JL2 rom for Bell - not sure if they all have the sbl.bin) and pit.
The key is to make sure it is complete. Try downloading the same rom from 2 different sources just to be sure its not a corrupt download (going overboard I know).
2) Can you get into recovery? Try to format partitions (not system) under advanced features (I think - I only have 3e right now as I am trying to diagnose other issues).
3) If you have a froyo rom on at one point, try to put a steam recovery kernel on. Its not really being developed anymore but I think that if you put a CWM packaged rom on to the external SD you could flash from there or at least move it to the internal and then flash it. Worth a shot. Or you might be able to transfer one in regular CWM recovery - can't recall as I have not had to try for about 8 months.
4) If you really want to try something completely different, and I am not sure I've got the balls if it was me but if you can get a file to flash from CWM or steam that you can get on from the external SD, you might try CM7. It uses a completely different file system so you'd have to go back to froyo via odin only (as a samsung based rom will not play well when flashed on top of the cm7 file system).
And calling it a day at this one...
gfacer said:
OK a few last brainwaves:
1) Try a fully complete stock rom with cache.rfs, dbdata.rfs, factoryfs.rfs, modem.bin, param.lfs, zImage, and sbl.bin (this was from JL2 rom for Bell - not sure if they all have the sbl.bin) and pit.
The key is to make sure it is complete. Try downloading the same rom from 2 different sources just to be sure its not a corrupt download (going overboard I know).
2) Can you get into recovery? Try to format partitions (not system) under advanced features (I think - I only have 3e right now as I am trying to diagnose other issues).
3) If you have a froyo rom on at one point, try to put a steam recovery kernel on. Its not really being developed anymore but I think that if you put a CWM packaged rom on to the external SD you could flash from there or at least move it to the internal and then flash it. Worth a shot. Or you might be able to transfer one in regular CWM recovery - can't recall as I have not had to try for about 8 months.
4) If you really want to try something completely different, and I am not sure I've got the balls if it was me but if you can get a file to flash from CWM or steam that you can get on from the external SD, you might try CM7. It uses a completely different file system so you'd have to go back to froyo via odin only (as a samsung based rom will not play well when flashed on top of the cm7 file system).
And calling it a day at this one...
Click to expand...
Click to collapse
Okay, basically at this point, I just want my phone to work I've tried what you said. I remember that before rooting my phone initially I was running Froyo 2.2.1. So I found the ROM for that ( http://www.samfirmware.com/WEBPROTECT-i9000.htm ) Just like you said. I downloaded from the *Provider Samsung Galaxy S i9000 heading and picked the I9000BOJS5 ## from February 2011 because I think somewhere around there I updated my phone to Froyo. Flashed it, did everything, still no luck.
I've had a recent hunch though. When the bootscreen boots up, it keeps saying i9000 only, when before it used to say i9000M at least for a little bit (yes my phone is i9000m). Is there a stock froyo rom that's specifically designed to go with the i9000m model? Or are they just all the same?
Never give up
-Thank you so much
I'm pretty much at wits end and completely out of ideas. Long story short, I've successfully used several different Rom's and Kernels without issue but decided to just revert back to stock. I'm just trying to reflash back to the original EA24 Rom. However it flat out refuses to reflash the modem. Everything else works fine and if I omit the modem file when flashing via Heimdall it works perfectly (minus 3G obviously).
However, if I include the modem file or try to flash just the modem after flashing the Rom, it just hangs once it reaches 100%. I've attempted it no less than a dozen times and it just refuses to flash the modem. No errors, it just hangs.
Does anyone have any ideas at all on how to correct this? Sprint was zero help whatsoever.
There's a post in the development section. The really recent so should be easy to find.
Sent from my SPH-P100 using XDA App
Yeah keep trying. I've had Odin hang modem before. Alternate between heimdall and Odin. Rodderik has a thread that should help in Dev section.
Sent from my SPH-D710 using XDA App
Hello all, I'd like to apologize in advance if this is covered somewhere but I searched and may just be missing it.
So here's the issue. Bought galaxy tab 8.9 wifi around when it was released. Used it for a few months. Played with a few roms and kernels, got a ****ty rom combination and just lost interest in the roms (mostly because work forced me into an iphone so I had to give up my gnex).
Fast forward a year I pick up my tablet again.
Played around with it for a day and couldn't get things restored properly.
I believe it was on a stock rom but someone elses kernel when I tried all this. But OTA update wouldn't work.
So I installed CWR through odin. Installation went fine.
Then rooted the phone through CWR, again everything working properly.
Tried to flash to most current version of AOSP and tablet and it won't boot. Screen stay's black after 20 minutes.
I can get into the tablet via Odin to repair it I'm just not sure what files I need.
So what I was looking for was to bring the tablet back to stock, if possible. To start from scratch.
I have the file for stock recovery, but not a stock kernel or stock rom. I have not been able to find these for my model of device. GT-P7310MA
Any help pointing me in the right direction would be appreciated. Again I apologize if this is covered somewhere else I just haven't been able to find it.
Go to sammobile.com for the stock Rom. You'll have to register but it's free. You'll download a zip file. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA. Just have auto-reboot and f.reset checked. You'll be good to go. Use Odin 1.85
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Thanks that worked. Got everything back to stock and now running CM10 on it with no probs.
synthetikv said:
Thanks that worked. Got everything back to stock and now running CM10 on it with no probs.
Click to expand...
Click to collapse
Great! Another satisfied customer!
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
What's good, chaps? This problem is currently on Overcome 4.1.0--beautiful ROM.
So what had happened was......
My Tab's WiFi worked perfectly, until yesterday (from the time of this post). Before this problem occurred, I had tried to flash a file I though would be useful for the Tab. The file sent my Tab into bootloops, and I scolded myself for not having made a nandroid.
I decided it'd be a good chance to try another ROM.
I eventually lighted on MIUI v4. I liked it for 5 minutes, then wanted to go back to Gingerbread (Overcome). I read that the MIUI ROM was an MTD ROM; I have no idea what that is, heh.
The only way to return to Gingerbread was to use Odin, so I did that. I followed every instruction on flashing the Overcome ROM to the letter. The installation went smoothly....until I found out my WiFI is broken. In fact, the baseband comes up as unknown--that never happened before. The Tab was getting a cellular signal, but that was it. I tried to reinstall the modem using Odin--no good. I tried using the fix from the Overcome Thread--no good.
I don't know what's wrong or what to do next.
If anyone can help me shed some light on this, it'd be greatly appreciated!
Thanks in advance!
I don't know why most people will try to fix their broken tab using overcome rom, find it broken but didn't tell how it was when it was merely on SG-stock-safe-v5
remember, Gb-stock-safe-v5 is Gingerbread from Samsung, JQ1 rom, in fact.
If it is broken at that stage, it is an entire different story than if it broke under Overcome ROM.
So which one is it?
Sorry for my late reply!
I found out it was broken when I reflashed the Overcome ROM. I never tried WiFI when I flashed GB-Stock-Safe-v5, so I can't tell you anything from there.
Did I do the right thing in using Odin, when downgrading from ICS 4.0.4 to GB 2.3.6?
No idea. But re-do the GB-stock-safe-v5 again and see how it goes.
If all good, add overcome kernel, see again how it goes.
if all good, flash overcome rom, and then see again.
Be methodical when you want to find your root cause.
Alright, I'll give it a go. Thanks for your help!
For the record, does downgrading from flashing a ROM with a different partition set-up have to be done a certain way?
just need a rom that has pit file and you tick the repartition in Odin.
That should take care of the downgrading from MTD rom
Followed your instructions and everything is back to normal!
Thanks again!
priyana said:
just need a rom that has pit file and you tick the repartition in Odin.
That should take care of the downgrading from MTD rom
Click to expand...
Click to collapse
tried every thing. flash froyo, flashed ginger. flashed Overcome's. flashed other roms like Boca or Miui.
but nothing can bring back the wi-fi even tried overcome's wi-fi fix and wpa-supplicant with proper permissions bla bla bla...
the tab was working fine before and was on overcome's last rom. but suddenly if wi-fi switched on, tab started giving constant re-starts.
do you think it's a hardware issue now? i flashed 2.3.6 stock on which it doesn't give restarts but wi-fi keeps scanning and switching off by itself.
3G works fine no issues at all.
please someone tell me if there is any thing that i'm not trying.
Yours sounds like hardware issue.
Sent from my GT-N7100 using xda app-developers app
Hello all, got a GT-P1000 Galaxy Tab1, it was previously ruined, and wouldn't boot anything but download mode, and wwhen charging the symbol would come up but never change.
So i decided to Reflash the FW with stock and that flashed fine the first time. But i was stuck on the samsung logo boot loop. As in Samsung logo would stay for 2 minutes, then disappear and reappear to do the exact same.
So i followed the overcome method - of flashing the SafeStockv5 Modem, and PIT. This booted straight into the OS of 2,3.3 and is booting fine.
My problem is that it starts up in italian, so need to select english, and there are a few Italian APPS, that can't be removed.
Anyone got any ideas on what FW i can flash to the tablet? If i try and do the 'stock' FW it hangs in oding on Hidden.rfs and won't budge. So forces me to reflash with Overcomes stock.
It's supposedly a UK Unbranded Galaxy Tab 1.
Any other info needed please ask.
Overcome gb stock safe v5 is Italian ROM. But it comes up only in English for me.
There are no Italian apps in there either.
Can you re flash it again?
Sent from my GT-N7100 using XDA Free mobile app
Hazeno said:
So i followed the overcome method - of flashing the SafeStockv5 Modem, and PIT. This booted straight into the OS of 2,3.3 and is booting fine
Click to expand...
Click to collapse
I have a P1000 that my daughter left out in the rain overnight. After stripping it down and drowning it in iso-pro alcohol I was able to get it to start and get to the download screen.
I've followed the Overcome method of restocking it (no errors) but also cannot get past the Samsung logo. Can you tell me where you got the files from that you used to restock please? I'm using the ones I've used previously but there must be some subtle difference because it refuses to start.
Could this be anything to do with the fact that I did manage to upgrade this thing to CM11 (before the rain incident), can I no longer downgrade to GB? I shouldn't need to revert to a different stage should I? Is far as I remember I've done this before all the way to GB then up to CM11, but I can't be certain.
Any thoughts on what to try next - be a shame to throw the thing out when it is so close to working again.