Database Develop

(Q)Bell user on Froyo trying to get back to the 2e recovery console having issues

I am in a pickle here. I want to try this as my first custom ROM made especially for bell users.
http://forum.xda-developers.com/showthread.php?t=846237
However I am on froyo with JK3 which has a 3e recovery console. Several threads on the board point me to this kernel to enable 2e recovery console which is required for this custom ROM install.
http://forum.xda-developers.com/showthread.php?t=788108
However it doesnt appear to me that this can be used by jk3 users. I am really new to this and have spent several hours reading. Am I wrong or am i missing something ?
My phone reads as follows:
PDA: I9000UGJK3
PHONE: I9000UGJK3
CSC: I90000BMCJK3
FIRMWARE VERSION 2.2
KERNAL VERSION 2.6.32.9 [email protected] #1
Any help would be much appreciated. I have read over 200 pages on the forum tonight alone and I am stuck
Thx

A lot of people have been there You have 2 options:
1) Flash an older firmware known to use 2e. The easiest thing to do is probably flash JH2 using Odin. JH2 was the last 2.1 official firmware for Bell. Get it from samfirmware.com
2) Flash a kernel that allows you to run clockwork. Check this post of mine where I installed SpeedMod on JK3.
http://forum.xda-developers.com/showpost.php?p=9777680&postcount=53
I don't know what others would say but it might be better for your app data to stay with Froyo 2.2. In that case, go with option 2. Be sure to backup your data just in case
Good luck with that ROM. On my phone, I'm running his Doc RomMOD v2 (JPU) and it's great!

what am I missing ? I thought that if you have jk3 on your phone you could only apply jk3 roms and kernels? is that incorrect ?

Some, kernels and root solutions are not compatible with all firmwares. If you're not concerned with data loss, I believe you can flash any firmware you want (ignoring device specific requirements).
The options I described above are ones that worked for me.

[SOLVED]Darky's v10.0 RC3. How do I flash to CM7/MIUI?

Hi. I wanted to get a quick taste of Gingerbread a month or so ago, and tried the RC release of Darky's 10 version rom (I flashed RC3, and haven't installed anything newer after that).
Since then, lots of progress has been made on CM7/MIUI front. I want to try them. Thing is, all of the tutorials (both for CM7 and MIUI) say something like "make sure You have Froyo bootloaders" or something similar. And I have Android 2.3.3 right now. Do I need to downgrade to some kind of Froyo rom first? I am scared of doing this alone unguided - I almost bricked my phone once when flashing Darky's v10 through Odin.
Help appreciated!
PS The process looks generally the same for both MIUI and CM7, right? That's why I put them both in this thread.
PPS I don't care about my data - it can all get wiped.

Yeah you need to flash a froyo with FROYO BOOTLOADERS Make sure you do this. Go to samfirmware and get I think it was JPU or whichever has the bootloaders. After that flash speedmod froyo kernel. Then make a backup.
Once you do that, get ROM manager in the market and select CM7. If you don't want to buy Rom manager (you should though because it will make updating to the nightlies very easy) go to CWM and flash normally
Easy wasn't it

Easiset way to make sure that you have Froyo bootlaoders installed:
Flash EZBase - this can be found here: http://forum.xda-developers.com/showthread.php?t=991792&highlight=Ezbase
Then simply download the files required and forllow the relevant instructions for that particular rom.

I flashed my phone with CM7 successfully with the help of EZBase! Thanks!

[Q] GB Bootloaders

I have moved from froyo to gingerbread at last and despite having a few little issues I am happy with the end result, however, I did find some of the 'instructions' surrounding the process both on here and other sites to be extremely vague, one of the main points of issue was regards ensuring you have a specific version fully installed before you commit to a custom rom.
I understand this relates to the installation of newer bootloaders that are able to support the new gingerbread code as well as older froyo.
I then found a post that shows how to avoid the full installs and only update the bootloader section itself, this has been tried and tested and accepted as working.
I have found that some posters have only succeeded with version xxx, some say to only update to the latest yyy, understandable and easy to follow....
But does anyone know of a location for the bootloaders ONLY, to use via odin?
And as an aside to that, how to check the actual version of the bootloader?
From my HTC days, it came up on a screen during flashing etc, but I have not seen any like that on the SGS.
I have checked the usual places, but they only seem to contain kernels and modems, not the bootloaders.
Any help apprecated
Cheers

Here are the standalone bootloaders for Froyo and Gingerbread put together by Nitr8 : http://forum.xda-developers.com/showthread.php?t=1089989
I don't know of anyway to check your bootloader version but if your running GB fine you know your on a Gingerbread bootloader. Froyo works with GB bootloaders so the only reason you may want to change them is if your moving to a CM7 rom which requires the froyo one. This thread tends to explain everything quite well: http://forum.xda-developers.com/showthread.php?t=1011701
Hope this helps

Shrapnel2 said:
Here are the standalone bootloaders for Froyo and Gingerbread put together by Nitr8 : http://forum.xda-developers.com/showthread.php?t=1089989
I don't know of anyway to check your bootloader version but if your running GB fine you know your on a Gingerbread bootloader. Froyo works with GB bootloaders so the only reason you may want to change them is if your moving to a CM7 rom which requires the froyo one. This thread tends to explain everything quite well: http://forum.xda-developers.com/showthread.php?t=1011701
Hope this helps
Click to expand...
Click to collapse
Sure does, my reason to determine the bootloader version is as follows, I was looking to try out an alternate rom and it said you MUST have a JVO bootloader or the rom would have issues.... hence looking for versions as such.
I did have an issue and before I reported back, i thought to locate the JVO bootloader and install it first and see if the problems continued...
Cheers

Yeah, the easiest way to acquire specific bootloader is probably to download an entire rom, eg JVO including bootloaders

[Q] Downgrade 2.3.3 to 2.2.1?

Hi,
I have two issues - firstly, three button recovery didn't work on my phone from new. The latest Android upgrade(2.3.3) has enabled it on 3e, but I think that's due to an error in the firmware(Three branded) - it says "can't access to '/system/csc/H3G/system'.'
I'm not getting on at all with Gingerbread(battery sucks, ogg files not playing properly, browser doesn't scroll nicely), and would like to downgrade back to an unbranded 2.2.1. I've been looking around and have grabbed some ROMs, odin, the "Aries_P-SBL" file needed to enable 2e recovery - but I'm also seeing things about updated bootloaders after the Gingerbread update, and I'm not totally confident in what I'm doing.
I'd like to downgrade to "I9000XWJSD", 2.2.1 released May 2011. The handset is Three(UK) branded, but has been SIM-unlocked(using the code provided by Three, and an alternative SIM does work). *#1234# gives PDA as I9000NEJVD, PHONE as I9000NEJV5, and CSC as I9000H£GJV6, with a build date of May 4th 2011. "About phone" gives a Build number of GINGERBREAD.NEJVD, Baseband version I9000NEJV5.
Will I be okay to do the 2e recovery, then the downgrade to the stock Samsung 2.2.1 flash? I have made the USB 3-resistor jig, and that puts me into download mode without a problem.
Sorry it was long-winded! Thanks!

The first thing you have to do is installing a 2.2.1 stock rom with froyo bootloaders(search for it in the forum, you'll find a couple of threads about it.
Very easy very simpel. Hope this will help you out.

Thanks for the reply. So I just drop down to 2.2.1 before thinking about installing the 2e recovery thing? Most things I've read indicate I need to have 2e recovery before flashing...
http://forum.xda-developers.com/showthread.php?t=1102881
On that page, "JSD" comes with bootloaders. Would that be safe to use on my handset?
Also, what is the "PIT" file for, and do I need to mess around with that?

EzBase is a good way of downgrading easily

http://forum.xda-developers.com/showthread.php?t=991792
^That? I shall bookmark it and have a look tonight.

Right, I've read through. The PDF guide for EZbase suggests 2e recovery is needed - how important is this? The guide for installing it suggests I need to root my device and check a string somewhere - but I can't root it using superoneclick, it just hangs.
How do I approach this? I have a working jig here, will that be sufficient to risk the flash without 2e installed? Should I just bite the bullet and go for EZbase 2.2.1, in the hope that I can then root the phone and check for that string?

Anyone, please? I'm technically minded and fairly competent, but as I get my internet through my handset(tethering) I'll be up the creek without a paddle if the phone ends up bricked... I need to be sure I'm not likely to mess things up!

I did it a couple of weeks ago, using this guide:-
http://forum.xda-developers.com/showthread.php?t=1100906
Went down to JPU, then straight to JSD. After gaining confidence by not c*cking it up, I chopped and changed modems a few times. ZSJPG had nice battery life but relatively sluggish/poor data connection and signal strength, so I used the Gingerbread 3UK modem from my last firmware - it works well for me.

[Q] I9000M 2.2 UGKC1 to 2.2.1 XXJPY questions

OK, so I've been reading guides, FAQs, how-tos, and various forum posts, and thought I had a pretty good handle on how to flash FW to this machine. So, last night I backed up everything important, and downloaded from here ( http://forum.xda-developers.com/showthread.php?t=1102881 ) the following:
2.2 UGKC1/UGKC1/BMCKC1/Sbl. This is the stock FW as currently installed on my I9000M from upgrading through Kies.
2.2.1 XWJS8/XXJPY/OXXJS5 (MultiCSC) (no sbl)
So just as a sanity test I first tried flashing the UGKC1 PDA file over to my I9000M using Odin. This worked as expected, since it's the same kernel.
Next, I tried to flash over just the XXJPY PDA file over to my I9000, using Odin. No re-partition, no PIT, no modem or CSC. No go - it just repeatedly displays the GT-I9000M screen and never boots the kernel. Couldn't get into recovery mode from this state, but was able to access 3-button download mode.
So, tried flashing over the 2.2.1 XXJPY PDA, Phone and CSC files. Same as before - no actual boot.
I flashed it back to the 2.2 UGKC1 PDA, phone and CSC files, and did a factory data reset and cache clear, and everything was fine running 2.2 again.
From reading here it appears that others have successfully installed 2.2.1 or even 2.3.x kernels on Bell Canada GT-I9000M phones. So, what important step did I miss?
Do I need to re-partitiion? Do I need to use a 2.2.1 FW that includes the boot loader?
For now I'm OK running 2.2, but would eventually really like to be on 2.3.x and don't want to wait for Samsung to make 2.3.x (what happened to 2.2.1) available to GT-I9000M phones. I'll leave it alone for now as I'm going on vacation in a couple of weeks and don't want a hosed phone.

What happens if you flash just a kernel like CF root or speedmod? My only other thought is to redownload jpy and try again as maybe the download was corrupted.
Also with another kernel like speedmod you could download and install a custom rom on cwm (clockwork mod) via recovery that is 2.2.1
I've had some problems with 2.3.4 (never tried 2.3.3) so I am back on Froyo for a bit until things get sorted out a bit more.
G

I don't know if there is a suitable version of CF Root for the UGKC1 firmware - they mostly seem to be oriented to the more international versions. As usual, in Canada we get something a little weird. Don't know about speedmod.
I don't think there should have been any problem with the downloads, as the files themselves are in md5 format, which means they are getting verified by Odin 1.8 when it goes to use them, as I understand it. If they were corrupted Odin should complain about it.
With the announcement ( http://forum.xda-developers.com/showthread.php?t=1158492 ) that Gingerbread is supposed to get an official release to Bell phones soon (which mine originally was), I might just let this lie, for now.

There is a gentleman on youtube by the name of AndroidGalaxyS (original, I know) that has some excellent and detailed walkthroughs and reviews of various ROMs for the I9000M.
youtube.com/user/AndroidGalaxyS
Specifically in your case, you'll want to watch this one that shows how to install 2.3.4 JVP:
youtube.com/watch?v=cLXQn0gOBuA&feature=feedu
Good luck.

I agree that the source maybe lacking. I just found out that the JL2 firmware from samfirmware.com is missing db_data file so I would always get an error after flashing that. KC1 would also not always boot for me so it might be missing something too.
That said what are you trying to accomplish? If you are just trying to go to another stock rom I'd just leave it and put a custom kernel on to give you root and CWM recovery.
Most any other Froyo rom is flashable from CWM in recovery and you do not need to worry about odin except to recover from bad things and it looks like you can do that. Gingerbread is different because they changed the bootloaders and that means Odin.
Of course its getting harder to dig back and find those Froyo roms since the rest of the i9000 world has been on GB for a while.
G

Thanks for the replies, so far. Mostly I was just experimenting, and trying out XXJPY was just a first step in my experimentation before moving on to GB. Part of the reason for this is that it seems like a lot of the modified kernels and so on are meant to be flashed over certain versions of the firmware, and those versions don't include the Bell/Virgin-specific ones. Or maybe I've misunderstood how this stuff works.
Yes, while my attempts to install XXJPY have been a complete failure, even when re-partitioning with a PIT file, when I re-flashed back to the stock UGKC1 FW everything was fine.
At this point I'm just trying to get a better understanding of where this went wrong. I've never specifically updated the SBL - the JPY package I installed didn't include it, and I didn't check off the "Update boot loader" box when re-installing KC1.
I've seen a number of posts here from people who updated I9000Ms to other FW, but unfortunately they don't seem to have detailed exactly where they started from, or exactly what they installed, or how.