Hi
Today my parents got their Galaxy S with Froyo on it.
I installed Gingerbread JVQ with Root and now everytime you boot I got a really weird screen which I have never seen before.
Here's a video http://www.youtube.com/watch?v=GG8vKd-On1A
After the boot you can use it normally.
My question is, can I upgrade to 4.1.1 SlimBean without any trouble?
I really haven't seen this befor and have no Idea if something is wrong with the Screen.
KUN1
I have his twinbrother the Samsung Galaxy S Plus.. And it looks like some files are corrupted. So i recommend a full reflash with a stock rom and no root to see if it is solved..
If so then you can easy go to slimbean
I have flashed JVQ twice but I will try again with JVU
KUN1 said:
I have flashed JVQ twice but I will try again with JVU
Click to expand...
Click to collapse
Why not trying cm 10.1 base rom's ?
If i remember well, you have problem with bootloader from froyo on GB ROM.
Flash 3 file GB ROM with pit and re-partition checked,
also after rooting consider switching to ICS or JB rom. I recommand one from AOSP line. good luck
kronos111 said:
Problem with bootloader from froyo on GB ROM.
Flash 3 file GB ROM with pit and re-partition checked
Click to expand...
Click to collapse
Agree with the above also re-download the Rom that you choosed as it may have been corrupted
Everything is fine now
I reflashed JVU with repartition and the bug was gone.
That happens if you run a GB or above rom while still using the froyo bootloader. Aside from that weird screen there are no other noticeable side effects. Where on earth did you even managed to get your hands on a I9000 with froyo bootloader anyway? The GB update came out years ago.
AW: [Q] Weird Screen Issue ?!
I bought the phone from another person.
I also don't know why he hasn't updated ^^
But normally if you flash a 3 file rom the bootloader should also be upgraded, shouldn't it?
After 3 times it finally changed the bootloader.
Sent from my GT-I9000 using xda app-developers app
KUN1 said:
I bought the phone from another person.
I also don't know why he hasn't updated ^^
But normally if you flash a 3 file rom the bootloader should also be upgraded, shouldn't it?
After 3 times it finally changed the bootloader.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Not all rom files have the bootloader in them. I am not sure why, but that's just the way it is. Back then there was a mad scramble to figure out which of the rom files contain bootloaders because even though you cannot brick your phone while flashing a rom, you can brick it if you somehow corrupt the bootloader.
Related
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 am wondering if it is possible to flash back to a stock rom without hooking up to a computer, is there a stock rom that can be installed right from CWM using a zip on the SD Card?
Only one i remember is a kb1 rom by ou812bkewl.
Thanks, I found that here: http://forum.xda-developers.com/showthread.php?t=963403. This isn't true stock as it was modified but hopefully it does enough to serve it's purpose.
Yeah, but all true"stock"packages are going to be for a flash utility (Odin/Heimdall for the captivate).
check out MOBILE ODIN
Mobile ODIN sounds super promising! That old rom originally suggested did not pan out, won't flash with the newer versions of CWM.
studacris said:
check out MOBILE ODIN
Click to expand...
Click to collapse
Dude, totally forgot about that. Is there an emoticon for "duh?"
Mobile Odin's saying my device is not supported.....I'm going to jump off a cliff lol. What I'm trying to do is flash any other ROM than what I have now. I flashed the RC1.0.1 Captivate ROM and now whenever I try to flash a different ROM it fails assertions. I'm guessing this is the same reason mobile ODIN is saying my device is not supported. I'm not going to be around a computer that I have set-up for ODIN for a few days, looks like I'm waiting. Thanks for trying to help me out folks
Mobile Odin requires you to be Rooted. And this flashes the firmware files, not cwm.zips files. (Not sure what u tried and why it said u weren't supported.)
I believe he's talking about the ICSSGS RC 1.0.1. From demonwave(which is rooted). If so, he's stuck if he doesn't have a computer. I had this on my Dev captivate and i couldn't flash from ics to cm7.
I think part of the not supported problem is the screen density, part is the build.prop. Just my $.02.
mrhaley30705 said:
I believe he's talking about the ICSSGS RC 1.0.1. From demonwave(which is rooted). If so, he's stuck if he doesn't have a computer. I had this on my Dev captivate and i couldn't flash from ics to cm7.
I think part of the not supported problem is the screen density, part is the build.prop. Just my $.02.
Click to expand...
Click to collapse
Ok, gotcha. So how did u get off of ICS ?? Flash stock kf1 ??
oooppss off day today...don't mind this misplaced post
4-2ndtwin said:
Ok, gotcha. So how did u get off of ICS ?? Flash stock kf1 ??
Click to expand...
Click to collapse
Yeah. Only way possible for me.
That's exactly my problem.
Sent from my I9000 using XDA App
Hi excuse my ignorance im a dhd user slightly different.
I rooted my wifes phone,clockwork was okay but would only boot cm7..would not allow gapps.
So i reverted to taking it back to froyo. Then i wanted ics on it,so flashed that,i kept her data so tried resoring that.
Now it just hangs at galaxy s screen
I cant enter into clockwork at all. It does enter download thankgod.
Thing is taking it back to froyo takes a while! Is there any way to take her straight to ics or cyn 7 or different rom without doing froyo.
The kernels for this phone are slighty different from mine the way they work..so how do i get the exact kernel and rom running again,
Also lol her data is on a back up i did will tgat still be there? Rom manager must save it somewhere?
ill be honest i have no idea anymore when coming to the galaxy s,im fairly confident with my dhd,but this has got me stumped
plus ill be a goner if i cant get it restored lol
Sorry for the looooong question
Sent from my Desire HD using XDA Premium App
T hink your problem is that you tried to install ICS on Froyo Base. SInce Gingerbread there is a new bootloader. If you want to install ICS or any Gingerbread-based ROM, you have to install a JVH base ROM (with bootloader), for example Ficeto_Deodexed_JVH_I9000_ODIN, first. This will update the bootloader and you may flash any newer rom via CWM.
If you have an boot-loop now, you may try flashing Ficeto_Deodexed_JVH_I9000_ODIN via ODIN, its a very basic ROM (see this thread).
Thanks for your help,its up and running again
Sent from my Desire HD using XDA Premium App
Pandur2000 said:
T hink your problem is that you tried to install ICS on Froyo Base. SInce Gingerbread there is a new bootloader. If you want to install ICS or any Gingerbread-based ROM, you have to install a JVH base ROM (with bootloader), for example Ficeto_Deodexed_JVH_I9000_ODIN, first. This will update the bootloader and you may flash any newer rom via CWM.
If you have an boot-loop now, you may try flashing Ficeto_Deodexed_JVH_I9000_ODIN via ODIN, its a very basic ROM (see this thread).
Click to expand...
Click to collapse
thats a good solution. i was facing this problem with a friends phone
Yep worked a treat,the roms on but still cant actually flash anything else,i thinks its s voodoo kernel i put on causin. The issue...but
Im leaving it now lol,its got gingerbread thats fine.
Sent from my Desire HD using XDA Premium App
Hi, I flashed my phone to gingerbread a while ago, not too sure how I did it, but I somehow managed to successfully . Anyways, It does function properly; however, I noticed when I restart the phone it calls itself a GT-i9000 when it starts. This is something that wasn't the same before, and I'm sure that has something to do with what you're about to help me with.
I don't think I changed the bootloader at all, which is what I am afraid of. I am interested in changing the phone back to factory settings, or if you guys have a suggestion on anything that is faster, I'd like to hear about that too!
Thanks, screen caps of settings available on request.
The GB package probably included GB bootloaders. They are backwards compatible with froyo roms if that is what you are reverting too.
Or you can Odin stock boot loaders or find a stock package that includes them.
Sent from my SGH-T959 using Tapatalk 2
I am not able to re flash back to stock because i formatted again and lost the files. As far as i read its a gingerbread version called XVJ1. Not sure if that helps out any.
Sent from my GT-I9000 using XDA
My phone had the "m" in the boot screen when I bought it, after I rooted it, it was gone, but other than the "m" missing for 18 months, it's working great.
I'm on WEUI 4.04 with Semaphore 1.1.1 kernel and UGKG3 modem
I find it very fast and stable, battery life 1 to 3 days depending on useage
Hope this helps...
My hasn't had the m since the day after I bought it. You live in Canada right? If so the stock firmware you need is Ugkg3. Get it from the ramads firmware thread in general. Flash all three files under appropriate sections and voila back to stock gingerbread. If you want to upgrade your firmware, flash jw5 under pda but flash kg3 under phone and csc. Then root with semaphore 2.7.4. By flashing that under pda after the firmware upgrade. And top it off with flashing Dmore3.3 in cwm after. Great rom for gingerbread. Gl.
Sent from my GT-I9000 using xda premium
Hi everyone,
Recently my phone loses IMEI after flashing any ROM, even after flashing kernel only (Semaphore 3.0.0 on CM10.1.3, for example). I have flashed the phone many of times before with different ROMs, kernels, sounds, fonts, animations, etc., but never had this issue before. Something has changed and I don't know what it is. It's getting annoying I just did a full cycle by the book: Format int/ext storage -> One-click stock ROM -> One-click Corn kernel -> Cyanogen 10.1.3 Stable (flash to repartition, flash the again). The phone works perfectly. Flashed another JB ROM to test, the same one I have flashed many times before with no issues (HellyBean 4.2.2, CM-based), and bam - lost IMEI again!
I have no problem restoring IMEI. The question is why the phone loses IMEI now after ROM change but never before?
What you describe suggests something has changed in the install scripts on either the CM or Helly roms.
It seems like flashing 10.1.2. instead of .3 would test CM as cause.
sent from one of my two SGH-I897 Captivates
I was thinking about this, it started somewhere around CM 10.1.2. But if the cause is changes in CM installation, then am I the only one experiencing this issue? I don't see many comments about lost IMEI on 4.2.2 ROMs. Yes, I know it happens, but not on every flash. I tried flashing Xylon 2.3.3 ROM, the one I flashed at least 3 times before with no issues, and same thing - lost IMEI. Seems like EFS is now in a place that gets wiped every time I flash something.
I tried installing cyanmod 4.2.2 and lost my imei. So I flashed back to 2.3.5 I think ill leave it where its at
Sent from my SAMSUNG-SGH-I897 using xda premium
Pajar0913 said:
I tried installing cyanmod 4.2.2 and lost my imei. So I flashed back to 2.3.5 I think ill leave it where its at
Click to expand...
Click to collapse
Try again. Android 4.2.2 is much better than stock 2.3.x.
Val D. said:
Try again. Android 4.2.2 is much better than stock 2.3.x.
Click to expand...
Click to collapse
Will It erase it again? I took me forever to unlock it to T-Mobile. I don't want to loose that.
Sent from my SAMSUNG-SGH-I897 using xda premium
Pajar0913 said:
Will It erase it again? I took me forever to unlock it to T-Mobile. I don't want to loose that.
Click to expand...
Click to collapse
The phone will stay unlocked. Just try again and you"ll be fine. Use latest CM10.1.3 Stable release.
Is it a one click Odin file. I have the one for 2.3.5
Sent from my SAMSUNG-SGH-I897 using xda premium
Pajar0913 said:
Is it a one click Odin file. I have the one for 2.3.5
Click to expand...
Click to collapse
No. Read this Guide how to update your phone.