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)
Weird colors on boot usually are a sign of an incorrect bootloader version. Since you seem to be familiar with darky stuff (ugh) you could try the darky resurrection edition; there should be easy to follow instructions on their site.
tamaleddon said:
Weird colors on boot usually are a sign of an incorrect bootloader version. Since you seem to be familiar with darky stuff (ugh) you could try the darky resurrection edition; there should be easy to follow instructions on their site.
Click to expand...
Click to collapse
I just flashed the RE version and it's making some progress. Definitely no weird colors.
PROBLEM:
-the boot screen is still flashing when trying to boot my phone, only this time it's with the "Darkcore & Darky's ROM" logo on it. The flashing is at a slower pace this time around.
ALSO:
I can get into the stock recovery screen, I hope this can somehow help
what should I doo!!?!
Ok see your here too and more q's for you based on what I see here:
1) What did you start with as a rom before 10.2 (stock GB, Froyo rom or ???)
2) The RE version - was that GB or Froyo?
I am thinking as the other poster alluded to is that maybe you went from a Froyo rom to 10.2 without getting the GB bootloader from a stock rom (odin with bootloader update checked) and now you are still working with the wrong bootloader?
If that sounds like what happened try flashing the RE edition for Froyo (9.3 I think) if you haven't already.
G
gfacer said:
Ok see your here too and more q's for you based on what I see here:
1) What did you start with as a rom before 10.2 (stock GB, Froyo rom or ???)
2) The RE version - was that GB or Froyo?
I am thinking as the other poster alluded to is that maybe you went from a Froyo rom to 10.2 without getting the GB bootloader from a stock rom (odin with bootloader update checked) and now you are still working with the wrong bootloader?
If that sounds like what happened try flashing the RE edition for Froyo (9.3 I think) if you haven't already.
G
Click to expand...
Click to collapse
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?
As far as i read on the Darky Site you have to activate Lagfix to install 10.2
Do you?
In other case.
Install Resurrection 9.2 FW:
(sorry. new member no links outside allowed: Go darky forum, stable roms, darky resurrection 9.2)
If that works your bootloader if for Froyo and afterwards you can go on to flash Darkys 10.2 like written in the Darky Forum.
But i would suggest to stay on Darky´s 9.5 with 2.2.1
It is the stable version with no bugs at all. This gingerbread sucks a lot with Akku Drain, Light sensor and other thing. Also no call records.
I will stay on 9.5 so far. Best solution at the moment...
The thing with installing 10.2 you installed without installing 2.3.3 rom before could be, that is maybe possible to install Darkys 10.2 Theme on a 2.2.1?
But no guarantee...
roma17 said:
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?
Click to expand...
Click to collapse
The colour distortion problem is 100% caused by incorrect bootloaders. Download jvq from samfirmware (or another 3 file gingerbread of you have one already), use the Odin version contained in the download, tick repartition and update bootloader then flash.
Download cf root for jvq and flash that as PDA without repartition. After the phone boots downlaod darkyrom from the market and from it flash darky 10.2.
Personally the kernal that comes with darkys takes too long to load the phone so I use galaxian instead. Phone flies and it's the first custom jvq rom I've used which doesn't reboot itself.
Sent from my GT-I9000 using XDA Premium App
sxi200 said:
The colour distortion problem is 100% caused by incorrect bootloaders. Download jvq from samfirmware (or another 3 file gingerbread of you have one already), use the Odin version contained in the download, tick repartition and update bootloader then flash.
Download cf root for jvq and flash that as PDA without repartition. After the phone boots downlaod darkyrom from the market and from it flash darky 10.2.
Personally the kernal that comes with darkys takes too long to load the phone so I use galaxian instead. Phone flies and it's the first custom jvq rom I've used which doesn't reboot itself.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Thanks for your response! Greatly appreciated. But at the time, I'm just looking to get my phone to work. It still doesn't work, it's still only stuck flashing the bootscreen, nothing else.
From my other post:
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
Yes jl2 or kc1 roms are I9000M specific. But both need dbdata.rfs added to the roms from samfirmware.com if you repartition.
There was a post on the cm7 forums with a complete jl2 rom someone compiled with dbdata.rfs added. Look for that post as it might have some other info too.
The i9000 you see means the kernel is for i9000. But that shouldn't matter.
It's worth a try but I think that a trip to samsung is on your phones future.
Sent from my GT-I9000M using XDA Premium App
Could be that you have a lagfix enabled and the stock ROM can't read the EXT4 file system. If so, try flashing another custom ROM via Odin (e.g. GingerReal), disable the lagfix to go back to RFS, then from there you can go back to the stock ROM.
gfacer said:
Yes jl2 or kc1 roms are I9000M specific. But both need dbdata.rfs added to the roms from samfirmware.com if you repartition.
There was a post on the cm7 forums with a complete jl2 rom someone compiled with dbdata.rfs added. Look for that post as it might have some other info too.
The i9000 you see means the kernel is for i9000. But that shouldn't matter.
It's worth a try but I think that a trip to samsung is on your phones future.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Well CM7 forum is down but here is the most of the link, you can google this and look at the cached pages. cyanogenmod topic/15707-how-to-restore-to-stock-on-your-gt-i9000m/
You should be able to click to the multi upload link too.
Now - you are aware of course that our i9000m models can suck and die fairly readily, especially when flashing certain roms. Has yours even been returned yet? Mine has and they replaced the motherboard. You may actually have a warrenty job and in any regard they won't likely fight too hard (just flash it to one of the jl2 or kc1 rom first).
If you want to find out for sure. look for the i9000m threads where they install eclair and use the external sd to boot and then look at the memory (internal then shows as external I think - its in the thread). Basically if it shows 0 available you're hooped.
gfacer said:
Yes jl2 or kc1 roms are I9000M specific. But both need dbdata.rfs added to the roms from samfirmware.com if you repartition.
There was a post on the cm7 forums with a complete jl2 rom someone compiled with dbdata.rfs added. Look for that post as it might have some other info too.
The i9000 you see means the kernel is for i9000. But that shouldn't matter.
It's worth a try but I think that a trip to samsung is on your phones future.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
I'm downloading the ROM from this link, could you verify it?
http://forum.xda-developers.com/showthread.php?t=883568
It may not have dbdata.rfs in it which you need if you repartition. I think they leave it out so regular users do not have to reinstall all their Apps.... Just look at what's in the file...
Sent from my GT-I9000M using XDA Premium App
gfacer said:
It may not have dbdata.rfs in it which you need if you repartition. I think they leave it out so regular users do not have to reinstall all their Apps.... Just look at what's in the file...
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
there is a I9000UGJL2_homebinary_add_param.tar
and a SS_DL.dll
so All i would have to do is just put that .tar file in PDA field and get a regular .pit file and check off the re-partitions
gfacer said:
It may not have dbdata.rfs in it which you need if you repartition. I think they leave it out so regular users do not have to reinstall all their Apps.... Just look at what's in the file...
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Okay, I have great news!!!!!!!!
I flashed that previous stock froyo ROM and finally can use my phone once more!!!
THANK YOU VERY MUCH!! Special thanks goes to gfacer! I could never have done it without you!
needless to say, I still require a custom ROM such as Darky's 10.2 RE on this phone of mine.
As a final request, would you be so kind to list all the things necessary for me to do in order to get all the way to darky's 10.2 with the lagfix and all?
Or if not, at least a thread or website that says exactly how to do it on my phone (i9000m) ?
Thanks ever so much!!!
Great!
My advice would be to pretend it never happened, but read all the instructions for the rom you are interested in and start from scratch.
Generally I would go custom froyo kernel from odin which will root you and give cwm generally, update bootloader to gb via a stock rom or ezbase, then flash 10.2 via cwm.
Darky has excellent guides also look at ezbase thread.
Sent from my GT-I9000M using XDA Premium App
roma17 said:
Okay, I have great news!!!!!!!!
I flashed that previous stock froyo ROM and finally can use my phone once more!!!
THANK YOU VERY MUCH!! Special thanks goes to gfacer! I could never have done it without you!
needless to say, I still require a custom ROM such as Darky's 10.2 RE on this phone of mine.
As a final request, would you be so kind to list all the things necessary for me to do in order to get all the way to darky's 10.2 with the lagfix and all?
Or if not, at least a thread or website that says exactly how to do it on my phone (i9000m) ?
Thanks ever so much!!!
Click to expand...
Click to collapse
To load Darky 10.2 successfully on your phone, you have to flash JVP or JVQ bootloader over your phone. The best solution is flash Stock Rom with bootloader over your phone. Then, flash Darky rom over your phone.
Related
anyone with an australian handset had much luck installing android v2.3.3 on their device without the help of a 3rd party rom like darkys or ultibread?
ive managed to install (original-xxjvk) functioning on samsung galaxy s with only a custom kernel if anyone is interested in a howto. ive only had my galaxy for a few weeks and have only managed to get it running myself without forced closes etc.
i dunno if anyone is having the same amount of trouble as i am trying to hook into android v2.3.3 but i think ive mastered it for aussies lookin to use the latest android on australian networks no hassles. i just didn't want to post a howto for something everyone has already worked out lookin like a fool. heh.
any replies appreciated.
I've been running stock JVK for about a month now, and Stock JVB since Saturday, Virginmobile (phone from Optus). No issues here.
Stock jvk with fugu mod, rooted and voodoo 7 sound with camera mods. I turned Hspda off today and since 7am till now 5pm still have 78%(and I use it fairly heavy). Runs well only thing I want next is android lockscreen and I'm happy.
On Virgin.
Sent from my GT-I9000 using Tapatalk
It took me a good 7 hours, haha all night trying to get GB on mah phone... had all sorts of problems as well.
Eventually, I installed I9000XWJVH, and it seems to be going good.
^^^
Just in time to flash 2.3.4 this evening
Downloading it right now.
Just worried about me having a non-stock kernel... using CWM (I think) with CWM Recovery... (CF-Root-XW_NEE_JVH-v3.2-CWM3RFS)
Are you flashing with Odin?
It wouldn't be a bad idea to flash the stock firmware first to get the updated bootloaders.
Yeah, I am using Odin.
flash stock jvh again?
Nope...
If you have your filesystem converted to ext4, just convert back to rfs.
If you really want to be sure of a clean flash, flash a 3 file firmware with a 512 pit and re-partition.
ok, well, I have no idea if I have ext4 or not... I don't remember ever seeing or doing anything with that, so, I am assuming I am still on rfs.
I have 3 files and a pit for the JVP. Do I just use those and flash with odin + repartition and that's it?
Don't need to do anything before?
I had stock JVK running for quite a while with no problems but with all the tasty looking ROMs out there I gave up and went for Simply Honey. First was using Darkys which was nice but SH wins me over with its lush blue-look =)
Now running JVO with no issues. Can get 6-8hrs heavy usage out of my phone =)
I know this sounds really blonde, but...
I'm trying to find a way to upgrade my Android OS to 2.3 (from 2.1) - however my phone is locked to Telstra and I'm finding it difficult (with my limited knowledge of Android) to upgrade.
Can someone please help me out? I'd be so grateful!
I found the best Guide to be: [GUIDE] Flash/Install/Update to Gingerbread 2.3.4 to I9000: Detailed guide for n00bs
It isn't too difficult but do read, re-read & go through the steps a few times before committing any changes.
Be prepared though... This flashing thing can get quite addictive as there seems like there is always another ROM that does just a little more than your current ROM & often just a little faster.
Good luck.
Oh - To keep all the grumpy forum members happy, do a quick search before asking a question such as this. You are not the first to ask this and there are many threads that have covered possible answers.
Just Updated to 2.3.3 Unbranded from Darky's Rom.
Had to Downgrade to 2.2 then to 2.3.3 as Odin just kept Failing.
Bear with me guys......haven't posted much on here, more of a lurker.
I have been following the AOSP Rom for the Fascinate for the last two weeks and now with the MMS working I would love to give it a shot. I have a couple of questions before I get started.
I am currently running ComRom 2.1 with the PBJ-50 Kernel. No themes or anything like that.
1. Is it safe to just do a data wipe and factory reset then just install the Rom over top of what I have?
2. Is there a Kernel and a Modem with the ROM?
3. Anything special I need to know if I decide to go back to another Rom (from what I have read just ODIN back to stock and Rom away)?
Sorry if these have been answered already.....I searched and did not find my answers. Thank you for your time.
millwood said:
Bear with me guys......haven't posted much on here, more of a lurker.
I have been following the AOSP Rom for the Fascinate for the last two weeks and now with the MMS working I would love to give it a shot. I have a couple of questions before I get started.
I am currently running ComRom 2.1 with the PBJ-50 Kernel. No themes or anything like that.
1. Is it safe to just do a data wipe and factory reset then just install the Rom over top of what I have?
2. Is there a Kernel and a Modem with the ROM?
3. Anything special I need to know if I decide to go back to another Rom (from what I have read just ODIN back to stock and Rom away)?
Sorry if these have been answered already.....I searched and did not find my answers. Thank you for your time.
Click to expand...
Click to collapse
1. I couldn't answer this with certainty as I haven't flashed it myself and haven't yet dug through the CM7 thread in development to put together correct steps
2. yes there is, but you can flash a custom kernel like OTB or the gingerbread leaks' (ec09) modem as I've seen these work though not for everyone
3. as far as I know all you need to do to go back is just odin back to eclair/froyo with the 2.2 atlas pit file and proceed from there
don't have any experience with CM7 other than what I've read so someone who's done it could probably shed more light on this
tapatalked from my GINGERBANGED Fascinate
I just flashed cm7 today...
1. Data wipe, cache and factory reset should be enough. You need to download and install the 7/04 build, let it boot up and reboot back into recovery and then install the 7/13 build and then the gapps. There is also a modified cwm that you can flash to your phone that's been edited for cm7 not everyone uses it but I did and it works perfectly.
2. There is a kernel included but alot of people have better audio quality with one of the otb kernels.
There isn't a modem. But it seems like most of the newer modems are fine so your current one with comrom is probably good.
3. To do back to stock youll have to use a full odin package. But you probably won't want to anyway.
Sent from my SCH-I500 using XDA Premium App
Thank you for the answers. Now I am more comfortable. Thanks.
Not sure how important it is, but I would wipe cache and dalvik as well. I used ED04 modem for a while, and switched to EC09 modem after everyone seemed to recommend it for the MTD roms. TBH, I havent noticed much difference between the 2 radios, they both worked well for me. As far as flashing back to a TW rom, check the sticky in the dev section:
http://forum.xda-developers.com/showthread.php?t=1124391
I am already running the EC09 modem. Have been for about a week or so. I watched as others have had good luck with it so I made the jump. I probably will stick with the EC09 as it seems to work fine with AOSP MIUI Rom that I want to try. I tried the EC09 on my wife's fascinate and it ran like crap.....kind of funny how two different build dates run to differently.
I followed [GUIDE] Installing a Rom/CWM recovery/Kernel/Root or going back to Stock for NEWBIES! Section 3 for an MTD. I want to put on the Vanilla Gingerbread ROM someone made. But when I did the Odin I got a fail.
My Fascinate is rooted and running Hardware version: I500.04, Firmware: 2.2.2, Kernel: 2.6.32.9, and build SCH-I500.ED05. I have CWMR 3.0.0.8 w/ ROM Manager v4.8.0.2.
I have tried everything I can think of and everything I could find in any forum especially this one and for the life of me can not get it to go. Any assistance is of great help. And if anyone is in the Fayetteville / Raleigh NC area that could offer me a actual hand in doing this would be of really great help.
jaed.43725 said:
I followed [GUIDE] Installing a Rom/CWM recovery/Kernel/Root or going back to Stock for NEWBIES! Section 3 for an MTD. I want to put on the Vanilla Gingerbread ROM someone made. But when I did the Odin I got a fail.
My Fascinate is rooted and running Hardware version: I500.04, Firmware: 2.2.2, Kernel: 2.6.32.9, and build SCH-I500.ED05. I have CWMR 3.0.0.8 w/ ROM Manager v4.8.0.2.
I have tried everything I can think of and everything I could find in any forum especially this one and for the life of me can not get it to go. Any assistance is of great help. And if anyone is in the Fayetteville / Raleigh NC area that could offer me a actual hand in doing this would be of really great help.
Click to expand...
Click to collapse
What failed in odin? going by what you posted, you didnt follow the guide. Also you need to use cwm4 fixed for cm7, not cwm3 which is exactly what the guide specifies.
Could me running Windows 7 64-Bit have anything to do with it not working?
jaed.43725 said:
Could me running Windows 7 64-Bit have anything to do with it not working?
Click to expand...
Click to collapse
64 bit windows should work if you have it set up correctly. I need more details on whats failing? Does the computer recognize the device?
Yes the computer does recognize the phone.
Feel free to ask any queations so I can give you any info you need.
jaed.43725 said:
Yes the computer does recognize the phone.
Click to expand...
Click to collapse
if your on a stock rom now. just odin cwm4, three finger into recovery wipe all three, then flash the vgb zip. basically follow the guide from steps 13 on.
What Odin version?
Sent from my SCH-I500 using xda premium
Odin3 v1.3
I may just have gotten it to work. It is taking awhile to load the new ROM however. I am not sure how long I should let it boot. Its been sitting on the SAMSUNG screen for about 5 min.
Three finger back into recovery and reflash. sometimes you have to flash twice to get mtd roms to take.
It worked. Thank you very much.
Your welcome!
I got it to work. But now it wont let me log into the market and gmail just does a flash thing and goes back to the apps screen.
Thats because u need to flash gapps...read the bottom of section 3 in the guide.
yep, did that and everything works great now. Thank you everyone.
Thanks to Adam Outler for the One Click packager!!! Thanks to Prezket for the leaks!
Introduction
This package will totally reset your Captivate to UCKK4. This package is intended for use on AT&T, however it will work with the Rogers SGH-i896 if you reset APN.
This package includes:
Repartitioning: Repartition to stock KK4
Reloading: IBL/PBL, PARAM, SBL, SBL2, Kernel, Recovery, FactoryFS and modem
formatting:Cache and DBdata
This package does not wipe:
EFS(Where your serial number and carrier information is stored)
SDCard (where your pictures are stored)
You may use this code to reformat the Data and SDCard *2767*3855# There is no way to do this from Download Mode. The code will leave the EFS untouched.
There are now two versions!!! I am not responsible if anything happens to you device.
DOWNLOADS
KK4 One Click w/ BL
KK4 One Click w/out BL
Instructions:
Get the latest version of java here: http://java.com/en/download/installed.jsp
Put your phone into "Download Mode"
Run the program once, and if it does not work, then check the "Flash Bootloaders" checkbox and flash again.
How I created this package:
The stock Captivate part.pit came from my device using Heimdall(Download Pit option)
Uploaded the KK4 firmware to my device.
Performed "wipe data" in recovery mode
Created a Heimdall tar.gz package using Heimdall 1.3
Finally, I used my Heimdall One-Click *BETA* packager to generate this one-click
This procedure can be reproduced for any custom ROM in the future.
Appreciate this. I am starting to delve into the world of Heimdall as of late.
Interested in learning about the alternative to Odin. I started earlier this week. And I must confess that it does look promising. Anyway, thanks for sharing.
Nice one
Sent from my SAMSUNG-SGH-I897 using xda premium
Where did you get the missing files?
Edit
Also probably wouldn't hurt to add info about drivers, java, etc (everything that's needed to make it work on windows).
What missing files? the BL, dbdatafs.rfs, cache,rfs,?
They are from KH3 base
Kk4 has a cache.rfs. I meant the param.lfs and the dbdata file. Kk4 also has boot.bin and sbl.bin in it. Not picking on you, i was just curious. I made a kk4 one click, pulling the missing files from kf1 (i thought it was the only leak with a full set of files), but i knew it would be a few days before i could test it.
Ohh then I didn't pull the cachefs.rfs, I had already tested it and It works! So I just pulled everything from KF1, sorry forget about that one as it has been so long and so many leaks
I'm running hacksungs ice build 8. All I have to do is run the program and it will go back to stock gingerbread with the boot loaders?
Sent from my SGH-I897 using XDA App
Correct. It repartitions for you, you might have to do it twice to flash to bootloaders so it will repartition the phone for RFS system use.
b-eock said:
Ohh then I didn't pull the cachefs.rfs, I had already tested it and It works! So I just pulled everything from KF1, sorry forget about that one as it has been so long and so many leaks
Click to expand...
Click to collapse
Yep, everytime I make a "latest i897 GB leak" One Click for myself, I pull the param.lfs and the larger dbdata.rfs from the KF1 leak. All the other necessary files are contained in the leaks (except for .pit). I use the .pit file from the KF1 and the only other thing I do is open the larger cache.rfs from the KF1 and open the cache.rfs from the latest leak that I am working on, with MagicISO (have to open this twice, one for each cache.rfs), and then I drag the Command file from the KF1 to the latest leak and drop it and select yes to overwrite the existing command file there. Because the Command file that is with the KF1 will wipe cache and data. The command file in all of the leaks since kf1 - up to kk4 will just wipe cache. (Can look at the command files with wordpad or notepad, etc.) It is just my personal preference though. If I make a one click, I like for it to be a full wipe and be able to repartition.
Can I get KK4 Bootloaders only, CWM,Odin or Heimdall flashable? How to check which BLs that I am currently on? I have flashed both i9000, and i897 BLs before but lack understanding of which version, or how it matters. Currently using a KK4 ROM: Serenity. Would KK4 BLs impede using ROMs from other branches, e.g. JVT or JVZ?
Please pardon my lack of sophistication.
OP updated.
p1gnone said:
Can I get KK4 Bootloaders only, CWM,Odin or Heimdall flashable? How to check which BLs that I am currently on? I have flashed both i9000, and i897 BLs before but lack understanding of which version, or how it matters. Currently using a KK4 ROM: Serenity. Would KK4 BLs impede using ROMs from other branches, e.g. JVT or JVZ?
Please pardon my lack of sophistication.
Click to expand...
Click to collapse
There are no specific KK4 bootloaders only.
This is Heimdall One click version, not CWM(look in development section for others)
When the phone boots up, do you have an AT&T screen? If so then you have I897GB bootloaders, if your on a KK4 ROM.
And I suggest using BL's native to the ROM you are running
I.E. I9000 GB ROM=I9000 GB BLs, I897 GB ROM=I897 GB BLs
^ if you dont do that, then when trying to use the stock music player while the screen is off it will skip really bad then reboot.
p1gnone said:
...... How to check which BLs that I am currently on? I have flashed both i9000, and i897 BLs before but lack understanding of which version, or how it matters. Currently using a KK4 ROM: Serenity.....
Click to expand...
Click to collapse
Since u r on a GB Rom, if ur boot up ur phone and see i9000, then that is the bootloaders u have. (we didn't have i9000 Froyo BLs)
If u see the at&t world phone screen, then u have the i897 GB BLs.
If u flash a GB Rom without GB Bootloaders, u will have a messed up pixelated screen when it boots.
4-2ndtwin said:
Since u r on a GB Rom, if ur boot up ur phone and see i9000, then that is the bootloaders u have. (we didn't have i9000 Froyo BLs)
If u see the at&t world phone screen, then u have the i897 GB BLs.
If u flash a GB Rom without GB Bootloaders, u will have a messed up pixelated screen when it boots.
Click to expand...
Click to collapse
To the extent that I have made a pt of having GB BLs when using GB ROMs this I have followed the advice of ROM developers. check.
Also the initial boot image had made clear i9000 or native i897.
I was just wondering if there were changes that were appreciable.
B
Thought about putting up just the tar.gz for regular Heimdall users?
yahh I will will later right now I am on windows, and dual booting between ubuntu and windows, so I will start it later tonight and post update tomorrow! Working on school work right now, and some theming
b-eock said:
There are no specific KK4 bootloaders only.
This is Heimdall One click version, not CWM(look in development section for others)
When the phone boots up, do you have an AT&T screen? If so then you have I897GB bootloaders, if your on a KK4 ROM.
And I suggest using BL's native to the ROM you are running
I.E. I9000 GB ROM=I9000 GB BLs, I897 GB ROM=I897 GB BLs
^ if you dont do that, then when trying to use the stock music player while the screen is off it will skip really bad then reboot.
Click to expand...
Click to collapse
I think he means is there a way to flash only the bootloaders from KK4 and not the whole ROM.
I have never used Heimdall and the only time I have flashed with ODIN was Designgears JF6 One Click and mine boots up with the AT&T world so I assume I am using Eclair bootloaders???
I am currently running Teamhacksungs ICS (To be CM9) Build 14 with the stock kernel and am one of the unfortunate ones getting reboots during phone calls when the screen is off and saw this post and was wondering if you thought it could be because I am not using GB bootloaders?
I was considering reverting to stock KK4 with a complete wipe and reload back to stock and then reflash Build 14 to see if it made any difference with KK4/GB bootloaders on my reboot during phone calls but wanted to do this as a last resort. I saw a KF1 bootloader only one click package here and was wondering if I flashed this would ICS build 14 even boot or would I have to reflash the whole KK4 ROM and start from scratch?
Are there any differences between the bootloaders in KF1 and KK4?
Sorry for all the questions, I'm still learning.....
Thanks
If you read that thread then you would know that you have go to stock, and if you do flash while on an MTD rom then it will not boot.
b-eock said:
If you read that thread then you would know that you have go to stock, and if you do flash while on an MTD rom then it will not boot.
Click to expand...
Click to collapse
I had read most of the thread and saw the warning for cyanogenmod users but had also read CyanogenMod was now compatible with GB boot loaders and didn't know if the information in the OP of that thread was current or not. Also asked since you mentioned the music app acting up when the screen was off due to incorrect boot loaders and was wanting your thoughts on whether phone reboots during a call when screen was off could be the same reason. No reason to be rude dude. I'm going to flash to KK4 with bootloaders and flash back to Build 14 and see if makes any difference. I haven't flashed to stock in over a year anyways. Thanks for the info and the one click.
Sent from my SGH-I897 using XDA App
I've always been happy with Checkrom. My previous ROM only lasted 4 hours, so when I saw V7 coming out I immediately flashed it.
After I succesfully flashed it I found out that the kitchenpro app didn't work and later I read that development was stopped. Not even swype which was part of the original samsung.
I now want to flash another ROM, but am afraid to follow the wrong procedure and brick it. It seems I can't even do a factory reset without the risk of bricking it.
I will never flash a checkrom product again.
Can I go into recovery and just flash wanamlite? Does it even work, as it's the standard recovery and not the full CWM?
No (extra) risk of bricking it?
I would appreciate a straightforward answer...
Another checkrom thread..
Sent from My Samsung Galaxy S2 running Paranoidandroid Rom.What else if not?=P
No, a direct question for answer I can't find anywhere.
I've always been helpful in fora on subjects I knew much about. Please, please refrain from answering if you don't know the answer or don't want to give it.
Look at the forum on www.checkrom.com. The instructions of flashing a kernel through Odin and a new rom are written in the V7-section.
Good luck
Sent from my GT-I9100 using xda app-developers app
Simply flash a safe kernel i.e. siyah kernel, reboot in to recovery and flash a rom(might want to do a full wipe beforehand) or restore a backup.
Good luck, this worked out for me.
frater said:
I've always been happy with Checkrom. My previous ROM only lasted 4 hours, so when I saw V7 coming out I immediately flashed it.
After I succesfully flashed it I found out that the kitchenpro app didn't work and later I read that development was stopped. Not even swype which was part of the original samsung.
I now want to flash another ROM, but am afraid to follow the wrong procedure and brick it. It seems I can't even do a factory reset without the risk of bricking it.
I will never flash a checkrom product again.
Can I go into recovery and just flash wanamlite? Does it even work, as it's the standard recovery and not the full CWM?
No (extra) risk of bricking it?
I would appreciate a straightforward answer...
Click to expand...
Click to collapse
First off, wise decision...
With respect to getting out of this, you want to flash a 4.0.3 based ROM. Don't go for a 4.0.4 based one quite yet, regardless of recovery type, if you're after a quick and safe fix.
You want to flash Siyah Kernel first, and then flash the ROM from there.
Siyah Kernel can be flashed via ODIN (flash the TAR as a PDA file).
Then go about your procedure to flash as usual. As above I'll re-iterate, don't flash a 4.0.4 based ROM yet (LQ5 or LQM I believe), as these are not always 100% safe in all scenarios.
You're much better to stick away from these for now.
Again, I have no idea why "developers" are going about releasing ROMs which are based on these kernels, without clear and noticeable warnings about what people are getting into...
Oh well... Hope it goes well, just follow this and you'll be fine.
Use Odin to flash siyah,
then use siyah's recovery to install new rom
zzkonzz said:
Use Odin to flash siyah,
then use siyah's recovery to install new rom
Click to expand...
Click to collapse
Exactly what Pulser has already said. Why repeat it again?
Sent from my GT-I9100 using Tapatalk 2
Thanks all....
Now not on checkrom anymore...
It should be noted that Leo, the main dude, says on Checkrom.com:
"No more ROM development for SGS2.
On that note i am closing the thread."
...and slammed the thread closed here on XDA too!
The last time I used Odin was when I bought my SG2. Since then I flashed all my different ROMs with CWM.
Although I'm glad I'm not using checkrom anymore and never will because of the way they stopped their development I do have to admit it had more than decent battery life (their 4.04 version).
I‘m currently on wanamlite and after 2 hours I'm already on 60% :-(
I used to have cyanogenmod 7 on my HTC HD2?
It might be an idea to try 9 or 10
Check out ParanoidAndroid. I'm getting about 30 hours off of the battery.
Sent from my GT-I9100 using xda app-developers app
Very bad form closing the threads when quite a number of people had flashed the new checkrom with the promise of a fix. They could have at least fixed the kernal issue rather than just abandoning it. Very disappointed. Going to try to flash the kernal via ODIN if I can remember even how!