Database Develop

[Q] Bell i9000 compatible firmware

Hi, I was just wanting to clarify what firmwares are safe to use on the Bell i9000.
I previously screwed up my phone because I flashed JPC and it corrupted my internal memory.
I was hopping to clear up what can be flashed on the Bell version of the i9000 and what can't me.
So far this is what I know.
Good:
JP2
JP3
BOJI
HVJHI
GJH2
JM2
JM4
XWJM5
JM7
JM8
UGJH2
1.20Ghz Kernel
Bad:
JPC
JPH
(possibly caused by One click lagfix)
To keep 850mhz radio
Modem: http://www.mediafire.com/?qic38waf8px13mz
CSC: http://www.mediafire.com/?7ow6p25nhzle5jo

JPC worked fine on my Bell Vibrant. Any of the international firmwares will work without any issues short of the issues inherent in the firmware already.

That was my understanding as well, but many people and all of the seem to have Bell Vibrants are getting corrupt sd cards from JPC, which basically bricks the phone.

My Bell Vibrant was Bricked no idea why ? because i didn't root or use a custom ROM so Bell [email protected]#$%# me over. Dammit 500 $ paper weight.
Now i gotta wait 3 to 6 weeks unless someone knows how to unbrick one without the 3 button recovery mode ?
Anyone ideas ? lol

Fuzz21 said:
My Bell Vibrant was Bricked no idea why ? because i didn't root or use a custom ROM so Bell [email protected]#$%# me over. Dammit 500 $ paper weight.
Now i gotta wait 3 to 6 weeks unless someone knows how to unbrick one without the 3 button recovery mode ?
Anyone ideas ? lol
Click to expand...
Click to collapse
No exactly what this thread is about sorry.

I also have a brick sent back to Bell/Samsung for repairs due to JPC.
I'm pretty sure any other firmware is fine. I had the HK JP2 installed without issue. Other than that I just stuck with the UGJH2 as it's nearly as new as any of the international firmwares and runs smooth, even without a lagfix.

mafiaboy01 said:
Hi, I was just wanting to clarify what firmwares are safe to use on the Bell i9000.
I previously screwed up my phone because I flashed JPC and it corrupted my internal memory.
I was hopping to clear up what can be flashed on the Bell version of the i9000 and what can't me.
So far this is what I know.
Good:
HK JP2
JP3
UGJH2
Bad:
JPC
JPH
Click to expand...
Click to collapse
I've had no problem with JPC. I've flashed it a couple of times over the past few weeks. It ran extremely well. JPH on the other hand has hooped my phone.

jentech said:
I've had no problem with JPC. I've flashed it a couple of times over the past few weeks. It ran extremely well. JPH on the other hand has hooped my phone.
Click to expand...
Click to collapse
For me and some others JPC did it :S

jentech said:
I've had no problem with JPC. I've flashed it a couple of times over the past few weeks. It ran extremely well. JPH on the other hand has hooped my phone.
Click to expand...
Click to collapse
JPC ran like garbage on mine but no major issues aside from the lag, JPH though has been a champ for me thus far.
Sent from my GT-I9000 using XDA App

we need to pin down as to what caused these SDCARD errors so we can all avoid that.
I'm thinking maybe repartitioning with the wrong pit file might cause something like this ?
I'm using JPC on my I9000m now, working nicely (some lag here and there, but nothing AutoKiller can't take care of), and since I saw the post about the SDCARD error on one of the i9000m, am a bit hesitant to flash JPH.
Problem is, if it does get bricked, its basically paper weight because am in the US and doubt Bell or Samsung US/Canada would be willing to help.

I also would like to find out what is causing the problems, it has to be an issue with only some of the Bell ones because there are people running these frimwares with no issues.

mafiaboy01 said:
I also would like to find out what is causing the problems, it has to be an issue with only some of the Bell ones because there are people running these frimwares with no issues.
Click to expand...
Click to collapse
am just throwing out ideas here, but it could be one of the lag fixes causing corruption in the internal memory if not correctly uninstalled before flashing new firmwares ?
jentech, did you use any of the lag fixes prior to flashing JPH ?

madmack said:
am just throwing out ideas here, but it could be one of the lag fixes causing corruption in the internal memory if not correctly uninstalled before flashing new firmwares ?
jentech, did you use any of the lag fixes prior to flashing JPH ?
Click to expand...
Click to collapse
JPC messed mine with no lagfix installed. This has been ruled out in several threads on xda.
Sent from my I7500 using XDA App

it is also highly likely that us bell users are flashing with bell modem so that we can keep 850 out of the box and is root of the sdcard corruption.
for some reason i remember having nexus one that every firmware and mod always strongly warned that froyo modem is required as well as flushing dalwik cache right after upgrading from éclair.
and here most of us are doing just that using jh2 with froyo.
well as for me i know i wont be upgrading to froyo as long as this thing with sdcard keeps happening as my 30 days was up on sept 9 so no more DOA and even if under warranty still not willing to be without the phone for more than a month.

madmack said:
am just throwing out ideas here, but it could be one of the lag fixes causing corruption in the internal memory if not correctly uninstalled before flashing new firmwares ?
jentech, did you use any of the lag fixes prior to flashing JPH ?
Click to expand...
Click to collapse
I lag fixed mine but as others have said it doesn't seem to be the cause.
Though I did seem to find a progressive decay in the phone until it finally shut off and never started. It wasn't all of a sudden.

mafiaboy01 said:
I lag fixed mine but as others have said it doesn't seem to be the cause.
Though I did seem to find a progressive decay in the phone until it finally shut off and never started. It wasn't all of a sudden.
Click to expand...
Click to collapse
Which lag fix ? if you used OCLF, did you allocate the entire internal memory to it ?

madmack said:
Which lag fix ? if you used OCLF, did you allocate the entire internal memory to it ?
Click to expand...
Click to collapse
Yes I did use OCLF, I only allocated the default so something like 800mb.
Sent from my GT-I9000M using XDA App

All the ones bricked, were you also having issues with the 3 button recovery? Trying to see if there is any connection there.

I'm reading around regarding this error, and it seems some guys with other phones and the same error got things running back by using Parted. You basically boot into recovery, push Parted to the bin folder, and then repartition/format that failed block: mmcblk0p1
I'm not sure what the file system currently is on that block, but the guys I got this info from were formatting it to ext2. I think if we modify it to match the filesystem that our ROMs require, then we're good. It's a long shot though, and if anybody has a bricked phone with them now, they could give it a go before sending it back for repair.

I used kies yesterday and upgraded to UGJH2, don't remember what it was before, whatever was factory loaded but now I am having all sorts of problems that I did not before.
GPS is way out of wack. Phone freezes. Signal disappears. Right now it's running smoothly but all day it was going retarded.
I give it a bit, if it doesn't sort itself out by the time froyo rolls I'll be flashing this sucka.
Thanks for the heads on good roms.

Reverting to which stock before flashing new ROM

Guys,
I really appreciate the wealth of good information here about the Captivate. I do have a quick, specific question I haven't seen answered but perhaps I missed so apologies in advance if I did.
I am on a rooted factory 2.1 phone right now and would like to flash a new ROM (undecided but will probably try a few). I have seen a few mentions that it is advisable (necessary?) to revert to stock before doing this and I am curious if it matters if I revert back to 2.1 or if I can 'revert' to 2.2 and would that be any advantage/disadvantage since it seems to be a temporary thing anyway.
I see both files on mobiletechvideo's site among other places. Would really love to know if there is any difference and if, in fact, I do need to do this step at all.
Thanks.
-Dan

The only step you'd need to take is to backup your things, and to do a Master Clear. It shouldn't really matter too much actually, so if you can't be bothered, feel free to flash away!

Thanks, venomio.
To follow up, I ended up flashing to 2.1 but using a version that had the 3-button fix (for getting into recovery mode I believe, which my phone could not do). Everything worked pretty much flawlessly getting back to 2.1 and 3-button fix was successful.
Then I flashed to Cognition 4.2.2 and again, everything went perfectly.
So if anyone stumbles across this in their research, go for it.

update to Gingerbread ?

I have an ATT Captivate which I managed to update from original Android 2.1 to 2.2 firmware, version I897UCJI6.
This was before ATT release their official 2.2 update.
I also managed to unlock the phone.
I have to admit I am totally ignorant of this stuff, and I was lucky enough not to brick my phone during those updates.
I am very unhappy with the battery life of my phone, and I read that the Gingerbread dramatically improves this aspect.
So, shall I upgrade to Gingerbread?
If yes, I am confused with the many sites which offer advice with how to do this, some contradicting with others. (One indicated to reverse back to 2.1 before upgrading to 2.3, other didn't say that, etc etc)
Should this upgrade be successfull, what happens to the lock/unlock status?
Do I need to unlock again?
Which is a trusted site?
Any advice?
Thank you for any help

UnLock stays after flashing.
As for a trusted site.... Ummm you found it. Xda...

Thank you
Will this upgrade really improve battery life?
If not I'll stay with 2.2

I got Max of 18 or so hours on froyo, I can go over 2 days now. Ymmv though.

Thanks again
I assume this would be the thread to follow, right ?
http://forum.xda-developers.com/showthread.php?t=1233620
Which indicates the use of this file : I897UCKH3_noboot.tar.md5 (dated 8/24/2011, 305191 KB)
I did find another file somewhere, presumably doing the same thing - that file name is:
I897UCKH3_HOME.tar.md5 (dated 8/19/2011 298421 KB)
I stated before I am kind of ignorant, and easily confused with all those information.
Which one is the right file?
Am I on the right track?

If you going to use KH3 without bootloaders you need to flash This bootloaders first.

Is there a thread for novices, where all those terms are explained, or where the procedures to be followed are explained for somebody who who can follow indicated steps (without really knowing the meaning of all those terms) which could lead to 100% success?
I don't mind reading a little, but I don't have time to become an expert (and I'm sure many readers here are like me, looking for plain simple advice on how to upgrade their phones, without having the skills and knowledge to do it)
Reading those posts here can be sooo confusing...
Somebody recommends you to do this, somebody recommends you to do that, and the poor you have no clue what they're talking about...

Simple if you want Gingerbread you need new bootloaders (except Cyanogenmod and MIUI). Bootloaders are like the BIOS in your computer. If you mess up the bootloaders you can hardbrick your phone.

Got it
Next logical question would be WHY the person who indicated how to upgrade to Gingerbread (http://forum.xda-developers.com/showthread.php?t=1233620) did not tell in his post that you need new bootloaders.
Or at least I do not see that in his post.
Which means that a novice like me can ruin his/her phone very easy..

No bootloader ODIN packages are made for people that already have the GB bootloaders. So you don't get a hard brick.

http://forum.xda-developers.com/showthread.php?t=1232703
I believe this is what you want to use.

mirceani said:
Got it
Next logical question would be WHY the person who indicated how to upgrade to Gingerbread (http://forum.xda-developers.com/showthread.php?t=1233620) did not tell in his post that you need new bootloaders.
Or at least I do not see that in his post.
Which means that a novice like me can ruin his/her phone very easy..
Click to expand...
Click to collapse
Flashing a GB ROM without GB bootloaders won't ruin your phone. May cause a bootloop, but not a hard brick. Cezar is super picky about things being safe. If you had hit the link he had for tips and tricks, it says something about bootloaders.

After reading all related posts, I am still confused - pls help:
I understand that if I follow Cesar's link, I need bootloaders first.
If I follow Przekret's link, I do NOT need bootloadres first (they are included)
So how do I decide which route to follow ? In the end I get the same result, GB 2.3.4 - correct?
I am currently on Froyo, UCJI6, rooted and unlocked.
Do I loose my rooting (I understand that unlocking stays)
Again, which method should I use (Cesar or Przekret) ?
Thank you

If you need bootloaders, don't use Cezars.
As these are stock roms, you will lose root. But if you flash any custom ROM, it should be rooted.

No method is incorrect. I would flash Bootloaders firs because there seems to be less chance to hard brick (I've noticed sometimes ODIN doesn't flash one bootloader after another). Thats my personal experience, but like I said neither of the methods are incorrect, I just never used the one with bootloaders included since I already had them when KH3 came out, so I can't speak for that package myself.

How do I know if I need bootloaders or not?

Unless you bought that phone modded with the GB bootloaders you need them. No real way to know except flashing a GB rom like cezars package. If it works You didn't need them, If it din't work then you soft bricked your phone and you might need a jig to get in to Download mode again.

mrhaley30705 said:
If you need bootloaders, don't use Cezars.
As these are stock roms, you will lose root. But if you flash any custom ROM, it should be rooted.
Click to expand...
Click to collapse
sorry for my ignorance, what is a "stock rom" and what is a "custom ROM" ?

prbassplayer said:
Unless you bought that phone modded with the GB bootloaders you need them. No real way to know except flashing a GB rom like cezars package. If it works You didn't need them, If it din't work then you soft bricked your phone and you might need a jig to get in to Download mode again.
Click to expand...
Click to collapse
OK
since I bought the phone from ATT a year ago, running 2.1, I would assume that I do NOT have them, so I do need them

mirceani said:
sorry for my ignorance, what is a "stock rom" and what is a "custom ROM" ?
Click to expand...
Click to collapse
A stock rom is that package that Cezare and pretzel posted. A custom rom is Fusion V, Pinnacle, Fasty II, among many many other. All those are based on the stock KH3 that cezar and prertzel posted

[Q] My phone is stuck in a bootloader loop

I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them. *fixed

Caelrie said:
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them.
Click to expand...
Click to collapse
Easy fix. ODIN flash the stock COD6 software. Then start over again with cf auto root. There is a thread that had all of the files you need in one zip.
Sent from my SM-N910T using XDA Free mobile app

Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.

Caelrie said:
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Click to expand...
Click to collapse
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)

absinthesummer said:
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
Click to expand...
Click to collapse
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile

Caelrie said:
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Click to expand...
Click to collapse
Cool, glad you got it sorted. Yeah as long as you can access download mode you're golden, and a bonus if you can get into recovery as well.
Excellent job actually searching and reading and fixing your problem, far too many people want answers just handed to them, so kudos to you for that.
Just for the future if you need help, try to remember and list all steps you took (even if you don't know where you went wrong) in excruciating detail because it helps us troubleshoot and figure out what the problem is. Without certain pertinent info it could take a lot longer to solve it.
Overall good job, glad you're up & running.

Go to rapture download the rom and load it to sd card. Then follow directions exactly and u will be ok. No loading anything. Fresh start
BAD ASS NOTE 4

I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.

ElAguila said:
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
Click to expand...
Click to collapse
Technically you shouldn't be flashing just the partial firmware. It sets up a base so that you can flash a lollipop rom in recovery without issues. I'm not sure why someone is recommending just flashing the partial firmware only. I guess they figured it wouldn't cause issues.
Anyway, here is how the partial firmware should be used:
Flash partial firmware in Odin
Flash flashable stock lollipop in recovery.
Set up rom, make a backup.
From here you can restore your old kitkat backups without the problems that some are seeing (those who Odin the full firmware are having problems restoring kitkat backups/flashing kitkat roms without Odining ank4 first). The partial firmware prevents that but it's designed to be flashed right before flashing a lollipop rom.
I hope that helps some of you who are having issues.

Screen is off... Cant figure out why

Hey fellas,
I recently flashed a new rom and wiped my entire phone. Ever sense then my "touch" has been off about a half inch, it always think I am lower than what my finger actually is. I returned to stock and it was fine, I flash everything over again and the problem comes back. The issue seems to be flashing CF Auto-root 78542, has anybody ran into this issue before?

I found a more up to date (78557) version, I will try that and report.

Nope thats not it either.

Make sure you are using the correct version. Normally this occurs because you flashed the wrong model number.
Sent from my SM-N910T using XDA Free mobile app

Thats what I thought but I don't think so. I am going to double check and maybe re download everything

As far as I can tell, everything is good.. N910T

Hell-Razor said:
Hey fellas,
I recently flashed a new rom and wiped my entire phone. Ever sense then my "touch" has been off about a half inch, it always think I am lower than what my finger actually is. I returned to stock and it was fine, I flash everything over again and the problem comes back. The issue seems to be flashing CF Auto-root 78542, has anybody ran into this issue before?
Click to expand...
Click to collapse
Don't worry, here is the fix for it.
I had the exact same problem a few weeks ago.
Go to the dialer screen and click in:
*#2663# screen fix works perfect, it will display a menu, select re-calibrate
or update or something to that effect, ( I forgot the exact wording)
But when you see that menu screen you will know which one to click.
You might have odin flashed the wrong twrp for the phone, but either
way this will fix it.
I would suggest that before you do this, odin flash the n910t
stock samsung firmware, that way twrp will get over-written.
Good luck,
Have a great day!

Will do. I really want to go back to the fire kat rom but I am tired and dont feel like messing around with things anymore. Just want a WORKING phone lol

Its defenetly CF AUTO ROOT. I tried an older and newer version with nothing, what the hell ive never had this issue.
And the *#2663# isnt working.

Hell-Razor said:
Its defenetly CF AUTO ROOT. I tried an older and newer version with nothing, what the hell ive never had this issue.
And the *#2663# isnt working.
Click to expand...
Click to collapse
We both have the identical phones N910T (I am assuming).
If that's the case perhaps you should try it again, be sure to do a
full wipe first and then odin flash the official stock COG2 firmware
before entering the code.
Be sure NOT to odin flash twrp recovery or cf-autoroot
after odin flashing the firmware, don't flash anything
except the odin flash official COG2 firmware until the
problem is solved.
It has to work because it worked for me and I had the
identical problem as you are having now.
Good luck!.

I am almost done downloading the 5.1.1 official t-mo zip. If this doesnt work I will try that.
Thank you by the way

Sweet it worked. Now I just need to figure out how to root the sob so I dont run into this issue anymore.