Database Develop

i9000XXJPM - password?

Hello all,
For unknown reasons, the i9000 update/flash seems to have had me more concerned and confused than anything I flashed for a long time - Im too used to HTC and nokia devices!
I finally decided I wanted to try flashing over to XXJPM - so I downloaded Odin, then the I9000XXJPM.rar, then the 8.3.pit and I thought - no more worrying, I have 3 button recovery, I can always reflash or some shizzle.
Then I tried to open the xxJMP.rar and unpack the .tar file to flash - and it asks for a password. Did I expect one? Not really, not after reading reports of everyone testing this F/W.....I never once came across a password.
I did try samsung then thought I had better ask.
Am I meant to try and crack this rar?
Can someone advise me? Is there a useable xxJMP somewhere?>
My stock UK vodaphone Galaxy is lagging like a glasweigan drunkard!
I got everything ready and I want to flash!!

yarod_g14 said:
Hello all,
For unknown reasons, the i9000 update/flash seems to have had me more concerned and confused than anything I flashed for a long time - Im too used to HTC and nokia devices!
I finally decided I wanted to try flashing over to XXJPM - so I downloaded Odin, then the I9000XXJPM.rar, then the 8.3.pit and I thought - no more worrying, I have 3 button recovery, I can always reflash or some shizzle.
Then I tried to open the xxJMP.rar and unpack the .tar file to flash - and it asks for a password. Did I expect one? Not really, not after reading reports of everyone testing this F/W.....I never once came across a password.
I did try samsung then thought I had better ask.
Am I meant to try and crack this rar?
Can someone advise me? Is there a useable xxJMP somewhere?>
My stock UK vodaphone Galaxy is lagging like a glasweigan drunkard!
I got everything ready and I want to flash!!
Click to expand...
Click to collapse
Pass = samfirmware.com

samfirmware.com

please read...well ..the password is well known if u read carefully

nandihno said:
please read...well ..the password is well known if u read carefully
Click to expand...
Click to collapse
Were you waiting under the bridge for me?
Thanks to others
Sent from my GT-I9000 using XDA App

[Q] Keep [hard] bricking phone flashing ODIN v3

First, thanks for the look.
Second, I have read the related threads to this, but none are like my special situation.
Twice I've had to get a warranty replacement for my Captivate after trying to restore from ODIN. Both times, the restore starts, then freezes mid-process. I've let it sit for an hour both times and nothing changes. Frozen. I have no choice but to unplug the USB cable, and remove the battery. The phone is then dead. I mean DEAD. Powered off & completely unresponsive. No power on. Screen doesn't light. "USB device is not recognized" when plugged into a PC w/ drivers. NODA. KAPUT.
I've successfully flashed w/ ODIN before, so I have no idea why certain times it decides to stop.
I'd like to use Clockworkmod to flash in between roms, but after re-flashing I always get the boot loop (AT&T screen is as far as it gets.) I try re-flashing to the original ROM, a backup of the stock ROM. Nothing works.
I REALLY don't want to try and get a 4th warranty phone if this happens again.
I know Clockworkmod requires a compatible ROM, but I've never seen one (Perception, Cognition etc.) that says it is. I know you need a backup of the nanroid, but isn't Clockworkmod supposed to do this?
Can someone straighten me out so I don't get yet another bricked phone?!
Thanks.
EDIT: Basically, I can flash a custom ROM just fine using Clockworkmod. Except when ODIN decides to be a *****, I can flash the stock ROM back, then another custom ROM. I want to flash from one custom ROM to another (or a backup of the stock ROM) without having to rely on a program that's bricked my phone twice!
Thanks again.

had this happen to me one night while trying to change roms. I used ROM Manager to flash back to a stock backup I made and stuck at ATT logo. got the phone into download mode and it would go a little then the screen would turn green or blue or orange, sometimes black and freeze running odin. I just kept at it, leaving the battery out for different intervals, holding volume keys with usb plugged in and then inserting battery. took about 30 tries but it finally took and odin flashed me back to stock. Just don't give up, try try again...you may get lucky

Development, I think not
Sent from my SGH-T959D using XDA App

bulletproof1013 said:
Development, I think not
Sent from my SGH-T959D using XDA App
Click to expand...
Click to collapse
Well, i figured since it was about ROMS it would belong here.
If there's a better place then move the thread.

bulletproof1013 said:
Development, I think not
Sent from my SGH-T959D using XDA App
Click to expand...
Click to collapse
NOTHING like throling auseless thread int he wrong section ... except we ve been politely asked by the admins to stop doing it so I will refrain from doing it ..
to answer you question , it seem like
the usb port/ card or even motherboard , ( might also be a bad usb cable) is at fault here , if you have a jig ( witch I advise you to build one asap if your into flashing roms ) I would never leave my phone plugged in to my pc when somethign is not responding . for example when flashing a kernel or even back to stock I know exatly how long thisi suppose to take and if its hanging I will unplug it and use the jig to go back in download mode and restart again , if your more cautious ten me then dotn , but nothing takes longer then 5 minuttes to flash on your phone so if by 10 minutes i dont work then your screwd so not worth letting your phone drain its battery ..
btw any questions belong in q&A no matther how relevant they are .

Without meaning to be rude, have you consider how reliable the computer you're flashing from is?
If you've seen the same behaviour twice, flashing two separate phones, then it seems likely that there's something specific either to the PC hardware (cables, ports), software (Odin, downloaded ROM, USB drivers) or method (human error of some kind) you're using.
Is there anything about your setup which might interrupt data on the USB line to the phone as it's being flashed?
Hope this helps,
AoN

i read on another forum somewhere that you cannot flash a stock backup from rom manager over a custom rom. that rom manager does not back up the kernel/modem etc...not sure how true it is, but I know the only time this ever happened to me was when I flashed a stock backup from ROM manager over a custom ROM.

DAGr8 said:
NOTHING like throling auseless thread int he wrong section ... except we ve been politely asked by the admins to stop doing it so I will refrain from doing it ...
Click to expand...
Click to collapse
For every non-development thread that is posted, one actual relevant thread gets bumped to page two. It hurts development, our at least slows it down.
Of course, that doesn't mean you should be rude or anything.
Sent from my GT-I9000 using XDA App

Also, if you're not doing it already, make sure you plug your USB cable into a USB port that is directly attached to your motherboard. Like the ones in the back. Many people have had issues using the front side USB ports or even going through a USB hub.
Also I guess it's worth it to reinstall drivers and do the normal windows type troubleshooting.

Soft-Bricked, No PC connectivity

Hey there, i am feeling somewhat overwhelmed with all of the advice going on out there and need someone who can give me the answer to my specific problem hardware wise without breaking a sweat...
I flashed a froyo 2.2 rom onto my phone a while ago, recently all of my apps stopped working, and i could no longer install any apps.
Couple days ago i tried openning gmail and the screen went black and gave me the bzzzzzz...............................bzzz...bzzz...
vibrating error that you usually get when an app crashes.
Now the phone continues doing that even when booted up and stuff
It starts right after the S screen and repeats until the battery is removed.
My phone can't get into download or reset mode using the 3 button method so i bought a jig off of ebay, works like a charm.
however NOW, i cannot get the computer to see the phone; both when it is on and attached and in download mode and attached. Odin can't see it, neither can Kies.
If i can get either to see it, i can look up the flashing process to make sure everything is right.... but as of yet nothing i am doing is making a difference.
Thanks for any help

Ok, I'd focus on odin so disable Kies (in task manager processes - all the kies processes).
Then I would 1) reinstall the drivers (standalone ones) 2) Have a few versions of odin to try (like 1.3, 1.7 and ez odin) 3) Clean your usb port on the phone (and computer maybe too - whats the harm?).
Usually if you are sure the drivers are Ok then you should be able to odin working with a nice clean port. They are more sensitive to dirt/moisture or whatever than they should be.
Try that and let us know...
BTW Some people think that the order is important but I've never noticed that. I always have odin open and then connect it but cant hurt to try the other way around too.

Hey thanks alot,
I am at work right now but i am optimistic about trying that out lol.
Just so i know for when the time comes and if Odin works, what files do i need to flash it? .pit, .tar and anything else specific for Bell Canada?
I only ask because you are with Bell so it is probably a very simple answer for you. Otherwise I am sure i can find it elsewhere.
Thanks,
I'll keep you updated
Josh

Download the complete jl2 rom from link I posted yesterday (search my posts) with repartition ticked, then flash the kc1 rom from stock rom link on xda or at samfirmware.com and flash without repartition if you want the latest. You could just try the kc1 step but I you need to repartition.
Sent from my GT-I9000M using XDA Premium App

Hey man,
my phone has never been sent in for repairs or replaced...
I was reading one of your other posts and you advised another member to send it in and maybe they will replace/update hardware?
I have still had my phone for less than a year so sending it in will be no problem at all...
Should i flash to the latest myself or return to stock and send it in?
I really appreciate your help.
Thanks

Well he knows his is broken as he can see that his internal memory reads 0 (which means its cooked - ask me how I know...) and he was trying to fix it in a round about way. Or there was the guy who flashed a captivate rom - that was just a big no-no.
You might just have a corrupt partition or some other corruption in the file system. I seem to get that all the time and its a pain but very fixable .

Alright, sooo
-uninstall Kies
-install drivers only
-try to connect to Odin
-If succesful flash with Odin
-dance with joy
Got it, I will update you later when i get home.
Thanks

installed drivers on my work computer (32 bit windows xp) and nothing... I've tried phone off, phone on, phone in d/l mode... It doesn't pick up anything...
I can try it on my Windows 7 comp at home and see if that works but i'm wondering what the worst case scenario is just bringing into Bell and having them fix it... Am i looking at charges, warranty voiding, etc.. etc... to have it fixed or could i BS my way out of it?

Fuuuuuuuuuuuuuuuuuu
pretty sure i flashed the wrong firmware on my phone, when it boots up it says GT-I9000 not GT-I9000M.
It worked fine for like 6 months so i never questioned it... damn damn damn

Not to be completely devious but i got an extended warranty that replaces the phone due to water damage, theft, etc. etc...
If there is no other way should i take advantage of that?
I would hate to jump to one of those actions but i am somewhat panicking becuase i made a super-noob mistake and effed up my phone....

I9000 firmware is completely compatible. The text you see is from the kernel which are always for i9000 unless you have one of the three bell firmwares. So that's not the issue.
Sent from my GT-I9000M using XDA Premium App

RogueCow27 said:
Not to be completely devious but i got an extended warranty that replaces the phone due to water damage, theft, etc. etc...
If there is no other way should i take advantage of that?
I would hate to jump to one of those actions but i am somewhat panicking becuase i made a super-noob mistake and effed up my phone....
Click to expand...
Click to collapse
I would keep trying. I have gotten warranty before and I was in the same predicament as you almost except I knew that the internal memory was dead. But that was also around the time when most of the I9000M models were dying. They might be checking more now.
If you get odin to flash a stock rom then you can go for it but by then you should be able to fix it.
Sent from my GT-I9000M using XDA Premium App

Alright i will keep trying.
As far as the firmware goes, my gf and i both have the same phone, but she kept heres official and i put custom roms on mine (just the 2.2 because it wasn't available)
We are both on bell canada so i asked her to boot up her phone and the beginning message on hers says GT-I9000M so it freaked me out lol
I will try on my home computer,
keep your fingers crossed for me

Alright, so Odin can now see my phone (it was the damn cord, my Win 7 comp couldnt see it but my xp work laptop can)
Which firmware would you recomend flashing? Stock gingerbread or a slight variation?
I am at work right now so i can wait a bit for a good response. It'd really help me out if you could provide links and tips to the best firmware out right now (i have no problem flashing a custom ROM if it is good).
Thanks alot,
Josh

Succesfully Flashes Gingerbread 2.3.4
Thanks for all your help!!!

how did you manage to see it in odin?
i have te same problem with restarting just after first screen (after flashing to gingerbread) but i cant see it in odin so i cant flash it again?
when i connect it when turned off, a small icon appears with usb connected sound but its still not visible.
Is it maybe my win7?
help, anyone please

Did you start in Download mod? Did you kill the Kies processes in you Win7 task manager ?
If yes, sometimes Windows takes time to install the drivers (be sure ton be connected to the internet), you should also close and relaunch Odin.

i launched download mode with sdk, and now i cant start it.
i went to another pc with xp. it installs drivers but odin cant recognize it.

Well i did it on my work XP computer becuase WIN 7 wasn't recognizing it. But it turns out the whole time the cable i was using would connect to charge, but not act as a pc connection.

[Q] I think its Bricked..and odin doesnt work

hey guys i have a captivate that i tried flashing and was successful then i tried again and the screen went black. im not sure if my battery died during the process or what but idk what to do. I cant get into recovery mode, i can only get into downloading mode but none of the odin's ive downloaded have recognized my device today. they worked fine yesterday. then i tried "hemidall one click" to try and get it back to stock but no luck. also when i try to power on I get the "Cornkernel" loading screen since that was the kernel i had loaded when it was working, but it fills the bar then shuts off. so it seems like im going to be at the mercy of a computer program since i am unable to access anything on the phone, right? I recently upgraded to gingerbread before all of the flashing of the new roms. all i want is to get back to either froyo or gingerbread, i dont really care, heck ill even take 2.1 at this point. if anyone knows whats going on and can help me thatd be great.
Thanks

Remember to use a rear usb hub for destop and run as admin. Heimdall will mess up your odin drivers.

You may also want to check out the captivate connection issues thread.
Also, to clarify further on prbassplayer's point about Heimdall, it will write its drivers over the drivers assigned to the USB port you are plugged into when it detects your phone. So if you have 4 USB ports and you use port 3 for Heimdall, it would look like this:
1 - Odin port
2 - Odin port
3 - Heimdall port
4 - Odin port
All this means is that you'll need to be aware of the port you used with Heimdall, or just reinstall the odin drivers (they'll overwrite the Heimdall setup).

OK so i tried what you mentioned in that thread on the connection issue and unfortunately it didn't work. is there a way i could start fresh? like delete all the drivers from my computer and then try it again, or do u not think that would work? im open to any ideas/suggestions right now because i hate having an extra paperweight and the thought of buying a new phone.

Don't know if this'll help or even why it worked for me but, when I had problems with odin recognizing my phone, I reinstalled/repaired samsung kies and odin would work for at least one flash.
Note: used full odin (not oneclick)
Good luck

hey guys thanks a bunch i finally got it to work. i had to use a different computer like you said. What a great feeling to have a functional phone again..
Thanks Again!!

So i got the phone back up and running android 2.1 and I would like to get it back to the stock 2.3 I had before the whole mess of rooting and stuff. but when i try to upgrade with kies or straight on the phone it ends up failing and telling me to try it again. any ideas why this is happening? or how to fix it.

blackjack54 said:
So i got the phone back up and running android 2.1 and I would like to get it back to the stock 2.3 I had before the whole mess of rooting and stuff. but when i try to upgrade with kies or straight on the phone it ends up failing and telling me to try it again. any ideas why this is happening? or how to fix it.
Click to expand...
Click to collapse
Kies sucks lol
look at my sig the first "go to" has the One Click Odin file to get you to stock and rooted 2.3 ...should take no more then 5 mins to do it

the link on that page for the 1 click odin doesnt work.

Try looking >>HERE<<. There are more one clicks there than you will ever need (hopefully)

Thanks I think I might try one of those. But considering what happened earlier in the week i want to clarify/ask a few ?s about that page. How do I know which Gingerbread to use of the 3 listed? How do I know whether or not to click the one with or without the bootloader? I'm new at this with android but I used to flash roms on my old windows mobile htc TILT.

blackjack54 said:
Thanks I think I might try one of those. But considering what happened earlier in the week i want to clarify/ask a few ?s about that page. How do I know which Gingerbread to use of the 3 listed? How do I know whether or not to click the one with or without the bootloader? I'm new at this with android but I used to flash roms on my old windows mobile htc TILT.
Click to expand...
Click to collapse
if you have never flashed GB bootloaders, you need to. Just oonce will work from that time forward. After you flash bootloaders, it's best to avoid them. A bad bootloader flash is one of the few things that will turn a Captivate into a paperwight. About which GB to use, I would say KK4. Its the same as the Official KK4 that was released. So to recap, flash bootloaders only once, then use no bootloader packages after that.

Im not sure if I unlocked them or not honestly. I know i had the phone rooted at one point and was running Cerberus rom. is there any way for me to check?

If you don't know, flash them.

ok i apologize in advance if this is a stupid obvious question..i got the odin one click and i was looking at the page u referred to me to and im wondering what the kernel is for? you cant place it in the odin one click obviously so is that just to keep things together or do i actually need it?

The kernel links are just to use if you want to root the stock rom. You have to use full Odin for those. Stick with the one click until you feel more comfortable in flashing AND do a lot research before your next flash.

so i got the KK1 gingerbread working and everything seems to work fine but now my data doesnt work. So I cant get ATT 3g or edge or anything the only internet i recieve is wifi. anyone know why this is? or how to fix it. ive tried a reboot and nothing ive tried changing the settings under network settings.

[Q] when you turn it off you will never turn it on again

Hi guys,
I've been looking around a bit but unfortunately I did not find any solution to my problem
Well, I'm a newbie and I got my desire c last december.
Basically since I got it, I've been flashing loads of different roms and never had a problem with it.
Yesterday, I wanted to try the cm10 and I started having difficulties: I got a bootloop after flashing it.
I said "no problems", I tried to reflash it and got the same..then I decided to change rom.
When I changed I had no problems at all..well till I decided to turn off the phone.
Here is the situation I'm stuck now: no matter which rom I decide to flash I always report the same problem, when I turn off the phone I'm never able to turn it on again (when I turn it on I can see the htc logo and only a black screen after)
how can I resolve that? Please I need some help

ilikemyhtc said:
Hi guys,
I've been looking around a bit but unfortunately I did not find any solution to my problem
Well, I'm a newbie and I got my desire c last december.
Basically since I got it, I've been flashing loads of different roms and never had a problem with it.
Yesterday, I wanted to try the cm10 and I started having difficulties: I got a bootloop after flashing it.
I said "no problems", I tried to reflash it and got the same..then I decided to change rom.
When I changed I had no problems at all..well till I decided to turn off the phone.
Here is the situation I'm stuck now: no matter which rom I decide to flash I always report the same problem, when I turn off the phone I'm never able to turn it on again (when I turn it on I can see the htc logo and only a black screen after)
how can I resolve that? Please I need some help
Click to expand...
Click to collapse
I'll suppose you tried clean flashing. Check which kernel you are using.
You need to use CM10 kernel for CM10 and Sense for the Sense roms.
If its the correct kernel, try a lower clock frequency.
If you havent tried clean flashing:
Dirty flashing can cause a lot of errors so i suggest that you perform a clean flash.
If you get this error again, you should try to post a logcat using adb. There are guides on how to do that all over the web.
I hope i helped, and if there are any further questions, ask away :3

ommicsiy conduted
thanks for the answer!
well actually I did a clean flash..
and it can't be a matter of kernel since I tried different roms with different kernels and the problem is the same..
tomorrow after work I'll try the logat and post it

since I was not able to do it trough adb (-waiting for the device- for about 30 mins..)
I flashed again a rom and used catlog.
here is the outcome!