Here's what I did to get JVH (with 850mhz band) and CSC for Canada on my phone. It worked for me at least
Files:
SpeedmodK15E_withLoaders.tar.md5 (8.38 MB)
http://www.multiupload.com/SRVH1BTK8R
JVH_KC1_BMC.zip (169.32 MB)
http://www.multiupload.com/1FHETKJOWA
StockJVH_Kernal_noLoaders.tar.md5 (5.47 MB)
http://www.multiupload.com/PM3AXR7JFG
**************Disclaimer:***************
I'm not responsible if this bricks your phone, as "the boss" said if I break mine, she'll break me... or I get a $20 replacement phone
Backup your /efs folder, backup EVERYTHING, just in case... I'm paranoid so I did it all
ROM NOTES:
Got deodexed from here:
http://forum.xda-developers.com/showpost.php?p=11256520&postcount=1
Modem:
KC1
Busybox:
1.18.4
Hosts file updated for ad blocking using:
http://winhelp2002.mvps.org/hosts.htm
Here's the steps I followed:
Save all files to folder/desktop
Connect phone via usb and copy JVH_KC1_BMC.zip to root of sdcard
Restart phone in download mode
Open Odin and click PDA
Select Speedmod tar file
Uncheck Auto-Reboot
Check F.Reset Time (I don't know what it does, but it's always checked)
Flash the tar.
Once complete and the box says "PASS" in green, unplug your phone and pull the battery (I was told it's safe, as it's in the MIUI instructions as well)
Put battery back in and start phone in recovery with VOL UP+HOME+POWER
In recovery choose to update from zip
Choose file from sdcard
Choose the JVH_KC1_BMC zip file and update
The phone will restart/install.
Once it's started up for the first time I recommend restarting in download mode and flashing the stock JVH kernal
You can also use any kernal you want.
Let me know if I can help at all. I was trying to make a completely odin flashable tar for this but failed miserably :9
I'll do my best to answer any questions however this is my first time making something to flash for you all
Note:
I'm not sure where to put this, sorry to mods/admins if it's in the wrong spot, please let me know
Hi,
I saw your thread, and I found it very interesting for people who own a Bell SGS 9000m Vibrant and wanna upgrate to Gingerbread.
So I decided to flash the Gingerbread JVH ROM just like you did, but I need to know a few things:
1. Will I be able to downgrade to my original stock froyo after this flash ?
2. Will I be able to update via Kies in case Bell release an official gingerbread update ?
3. Right now my phone is SIMUnlocked, will I lose my SIMunlockation after the flash ?
4. And is my actual configuration right to excecute this flash or should I flash something else before ?
My configuration is the following:
Baseband version
I9000UGJL2
Firmware
2.2
Kernel
2.6.32.9
[email protected] #3
Build number
FROYO.UGJL2
galaxy s vibrant bell
gt-i9000m
Thanks for your hard work, I hope to read back from you soon.
I have exact same configuration and exact same questions as poster above!!!
Still no answer... Guess we'll have to try if wanna know...
nguetto said:
Hi,
I saw your thread, and I found it very interesting for people who own a Bell SGS 9000m Vibrant and wanna upgrate to Gingerbread.
So I decided to flash the Gingerbread JVH ROM just like you did, but I need to know a few things:
1. Will I be able to downgrade to my original stock froyo after this flash ?
2. Will I be able to update via Kies in case Bell release an official gingerbread update ?
3. Right now my phone is SIMUnlocked, will I lose my SIMunlockation after the flash ?
4. And is my actual configuration right to excecute this flash or should I flash something else before ?
Click to expand...
Click to collapse
1. yes, it's possible
2. yes, but you would either need to downgrade first or do a kies hack
3. no
4. you can do it straight
Thanks zorxd.
I am going to try. So there is no need for me to select any Pit file or did the guy forget to mention it ? Also can we tick the repartition option in Odin?
Sorry if I ask usekess question I am used to flash android but new to the SGS flashing...
when you repartition you need a PIT file.
My advice is to not repartition unless you need it.
Too late... I did it got stuck into bootloop. I had an error when I tried to install the zip from the recovery (I had recovery 3e) : E : Short write of /tmp/sideload/package.zip (No space left on device) . However, I flashed the back eclair JHL and went back to the stock eclair rom. I am going to restart from there following your intructions. I now have recovery 2e ( Somehow I can't get ClockWorkMod Recovery to load directly; it always send me to recovery 2e and there I apply update.zip to go to CWM recovery)
Thanks for your help, I'll let you know if I manage to get it done.
Still get the error E:Short write of/tmp/sideload/package.zip (No space left on device) when try to install JVH_KC1_BMC.zip from the recovery 3e ( this recovery comes right after I flash SpeedmodK15E_withLoaders.tar ...
Don't know what else to try... Help please..
I did it a slightly different way. From 2.2, I flashed a stock 3 part gingerbread rom (phone, PDA, CSC) with bootloader update using ODIN 1.82. I then flashed CF root gingerbread kernel for CWM3 and then flashed the KC1 modem from clockwork recovery for the 850 band.
Could you please show me the exact files you used so I can try to do the same ?
Aren't there at least a couple threads on how to install jvh/jvp on an i9000? Its the exact same process as those you just have to flash the kc1 modem via cwm after you are done. It sounds like you guys are experimenting too much.
Sent from my Darky's i9000m
nguetto said:
Could you please show me the exact files you used so I can try to do the same ?
Click to expand...
Click to collapse
Our canadian phone is not really different from all the other ones, so you don't need a special "Bell Canada" installation.
If you want JVH, you can follow this thread:
http://forum.xda-developers.com/showthread.php?t=818556
You don't have to do everything like fugumod, etc. I would flash JVH via odin and then flash CF root kernel via odin so you get CWM3.
There's also leaked 2.3.4 JVP gingerbread out, if you feel inclined:
http://forum.xda-developers.com/showthread.php?t=1102881
There's a way to enable 850 band on the different gingerbread modems, but i never bothered, I just flashed the KC1 modem for Bell which has the band (via CWM3). Search for I9000UGKC1
http://forum.xda-developers.com/showpost.php?p=9874879&postcount=1
Okay I am really starting to freak out now...
I am stuck in bootloop, I can't get out og it. I tried flash Back the Stock Bell Firmware but it keeps boot looping. Download mode is okay. But it started doing this I had a message like sd could not be mounted in recovery 3e. Now I can't even access recovery after I flash Eclair but Download mode is still okay...
Aby ideas ?
Have you tried flashing back the stock JL2 firmware from bell? (found on samfirmware.com)
I've never encountered this error before, I wonder if it is a problem with the bootloaders, as the official froyo firmware from bell had a secondary bootloader and gingerbread has its own bootloaders as well.
nguetto said:
Okay I am really starting to freak out now...
I am stuck in bootloop, I can't get out og it. I tried flash Back the Stock Bell Firmware but it keeps boot looping. Download mode is okay. But it started doing this I had a message like sd could not be mounted in recovery 3e. Now I can't even access recovery after I flash Eclair but Download mode is still okay...
Aby ideas ?
Click to expand...
Click to collapse
I imagine you'll need the stock bell firmware as said above and also the proper PIT file to go along with it.
Sent from my Darky's i9000m
Also if you repartitioned it when you tried to flash the whatever it was when you tried you will also have to repartition it when going back down to froyo.
2.2 and 2.3 use different bootloaders therefore if you try to mix and match rom's without the bootloaders and repartioning you will get a ****y phone.
Sent from my Darky's i9000m
Thanks for your help guys. I didn't solve it yet, but i will open a new thread to prevent this one from getting to messy.
I've got CM10 running well on my girlfriends i9000m, but she has mentioned that in some locations where she used to get good signal (with the factory rom), she now doesn't. I thought I'd try using other modem.bins to see if I could improve this. However, I must not know what I'm doing.
I tried replacing the modem.bin using download mode (I tried both odin and heimdall). The first modem.bin I tried didn't work though (no cell connectivity at all anymore). This didn't surprise me, as I thought I'd have to try a few before I found one that worked for me (seeing it's a i9000m). Anyway, when I tried flashing back the original modem.bin (which I pulled from the CM10 zip), it didn't work either. I ended up reloading the whole CM10 zip through CWM to get it working again.
So my question is: can I not load just a modem.bin though download mode? Do I have to load modems using recovery? Why is there a difference? And if I do need to use recovery, could anyone point me to a post that tells you how to make your own modem.zip?
Any input is appreciated!
Brad
Recovery zip files
http://forum.xda-developers.com/showthread.php?p=31131934
All basically using same update-script made for cm7/9/10.
Replace your modem.bin in any of these using any PC zip tool prior flashing by recovery should work.
O-T said:
Recovery zip files
http://forum.xda-developers.com/showthread.php?p=31131934
All basically using same update-script made for cm7/9/10.
Replace your modem.bin in any of these using any PC zip tool prior flashing by recovery should work.
Click to expand...
Click to collapse
Thanks for the link. By looking at the actual update script, I'm going to assume that the main problem with flashing the modem in download mode is that the proper permissions don't get set.
Any one know how to recover this Tab? It does not turn on at all. Bricked flashing firmware file with ODIN. Got stuck and everything broke after that.
So no one knows anything about unbricking this tab?
A,
hey hey, good morning, provided you didn't trash your pit/patition info your tab should be recoverable,
you will need these, [not addressing the stock option here]
recovery, flash via odin first, you'll know real quick if you're done or not, if you get any pit error messages, yup, dead
https://www.androidfilehost.com/?fid=95916177934547320
note- if odin complains about the signature just remove the .md5 extension from the file
rom, put this on your sdcard and flash via recovery
http://forum.xda-developers.com/tab-4/development/rom-sm-t231-odex-root-t3052254
this rom will cover sm-t230/nu/31,
that's probably your best option. usually when odin bites it on a flash, you'll need to get a successful recovery.img or boot.img
to go through to get odin out of the error mode it gets stuck in. BUT, like i said before, if you boned your pit/partition info, then
you're done.
m
A painful experience - see below - taught me that a NANDROID backup isn't enough.
I had to find a PIT file, a bootloader and a modem.
What else does one need to be able to get back to an earlier version, and is there some software to do that
automatically?
I've tried an Android-5.0 for which I had to flash the boot loader and the modem, as well.
The Android-5.0 system booted well but it turnt out that I got insurmountable difficulties with WLAN
authentication. Therefore I wanted to go back to Kitkat (4.4.2) which I had backed up by TWRP.
I could restore the system but got a boot loop - no wiping helped.
Then I tried to install a stock 4.4.2 system but ODIN-3.09 has stalled for more than an hour such that I had
to kill it. Now my device was broken. Luckily I did find a suitable PIT file, boot loader and modem.
Even then ODIN didn't succeed. With the help of Philz-Touch-Recover I could reformat some partitions.
Only after that ODIN succeeded - together with the PIT file - to flash the bootloader and the modem,
Only now, I could boot into the old version.
Many thanks for a hint,
Helmut.
So my brand new SD care went corrupt while I had a lot of programs running from it... By means of Link2SD app I put system files on there too and now I get
E:failed to mount /system (Invalid argument)
I can't seem to fix this problem and it doesn't seem that this problem arises very often because I have found nothing in searching. Any help would be great... I don't want to have to put a hammer to it and then call Asurion for a replacement..... but that does sound fun lol.
I have tried to Odin everything I have in my backups but not sure if any of those are actually the original rom. I have been trying to figure out how to Odin CM or TWRP on to it... or get them install in some form with out the APK. I saw something about them being able to fix the issue.
Have you tried using ODIN and flashing back to a fresh, stock ROM?
I forgot to put all that. I have tried to Odin everything I have in my backups but not sure if any of those are actually the original rom. I have been trying to figure out how to Odin CM or TWRP on to it... or get them install in some form with out the APK. I saw something about them being able to fix the issue.
Our phones do not support CM or TWRP because we have a locked bootloader. You are on a Verizon G900V, right?
Here's a link to a post with stock ROMs you can Flash via Odin. Choose the appropriate one for the version you want and Flash. Make sure you back up anythibg you want to save.
http://forum.xda-developers.com/showthread.php?t=2784880
It doesn't matter what I flash I get the same error. The other things I have found say that the system and/or EFS needs to be re-made so to speak. TWRP has a command that does it and CM allows you to go in though ADB and do it..... That is the best I have found for answers so far. I don't see anything for FlashFire or SuperUser.
Flash using ODIN not FlashFire or anything else.
I have flashed with Odin.... I get no where.... doesn't matter what kernel I use or ROM or anything.... I was saying that the people that have solved this porblem before are using CW or TWRP to access the ADB to send commands for the phone to re-setup the system/EFS
Did you Flash the pit file on the page I linked earlier? That should repartition everything.
Still the same problem
So I just kept flashing tar files from the post above and finally the NI2 took along with the pit file. Thanks for your help @btonetbone
Eventually the NI2 + .pit file being flashed together fixed the problem.