Hey All,
Here is my funky story. I bought a GT-P1000N from Amazon Unlocked for development. Not realizing this would be a unit that was supposed to be sold in Brazil and not the USA, I started flashing away. All was well until.... it went dark. Unable to revive the unit, I took it to a cool little place here in Toronto called M-Tech and the guy used a Riff box to revive it. He was able to reflash the original Stock rom onto it.
PDA1000NUBJM2
Phone: Unknown
CSC: P1000NUUBJM2
All attempts to flash various Modems have failed using either Odin or Heimdall. Using either one, flashing the modem.bin will appear to PASS, and the tablet will reboot, but *#1234# is still reporting above.
Additionally, and oddly, I tried to flash Humbros's rom, starting with the Kernel zImage using Odin, this too seemed to Flash PASS, and upon restarting, Kernel reports the same original Kernel as before, not the new one.
Kernel: 2.6.32.9 [email protected] #1
Build number: FROYO.UBJM2
Any ideas how I can get a new modem.bin to flash at least?
Also, why is the Kernel flash not taking?
Thanks,
BluePlanetMan
I once did something like that to my p1000l with odin. The solution was to flash only the modem.bin with odin in phone section
Btw kernel wont stick if you flash it in phone section in odin, it needs to be in pda section.
Try flashing a whole rom w/repartition in odin if the above doesn't work
Sent from my GT-P1000L using XDA App
Ok,
I flashed Roto JME V4, and all looked ok, but I have NO touch screen. So, went back into download mode and reflashed P1000NUBJM2 which seems to be the only rom that will work and give me a touch screen.
Attempts to flash a kernel (of the ones I tried) have failed, Odin flashes, says Pass, but Kernel stays the same as before. Also same results for Modem.bin I have tried several different ones, but Baseband is still showing as "Unknown"... I am stumped as to why this would be??? I wish I could have gotten into the settings when Roto was flashed just to see what the Kernel and Baseband looked like, but I had not control to look at it.
You have the latin version of the tab. You need to flash the kernal by humbertos to get your touch screen working
Related
I messed up my Bell SGS playing with odin.
Lost the 3 button options and ended up hacking a jig to get it into DL mode. done
Goal - a Functioning phone. Now what?
Thinking I should odin the I9000M_JL2_JL2_JL2_JL2_UG_BMC.tar.
But with or without repartition?
Can I use any 512pit?
I think repartitioning is where i messed it up.
Now all of this happened because I wanted seeARMS.JL2.v0.4 but couldn't update with the <3e> recovery mode.
Knowing that seeArms is my second (first?) goal, is there a different firmware I should flash something other than BMC to give me back update functions, but stable to resuscitate my phone?
There's ages of material here and I don't want brick my phone or waste time, I've done enough of that by myself.. now I'm looking for some expert opinion.
thanks
Best option for bell users is darkys rom. For further info check darky's rom info
Lyon huntington said:
I messed up my Bell SGS playing with odin.
Lost the 3 button options and ended up hacking a jig to get it into DL mode. done
Goal - a Functioning phone. Now what?
Thinking I should odin the I9000M_JL2_JL2_JL2_JL2_UG_BMC.tar.
But with or without repartition?
Can I use any 512pit?
I think repartitioning is where i messed it up.
Now all of this happened because I wanted seeARMS.JL2.v0.4 but couldn't update with the <3e> recovery mode.
Knowing that seeArms is my second (first?) goal, is there a different firmware I should flash something other than BMC to give me back update functions, but stable to resuscitate my phone?
There's ages of material here and I don't want brick my phone or waste time, I've done enough of that by myself.. now I'm looking for some expert opinion.
thanks
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App
Lyon huntington said:
I messed up my Bell SGS playing with odin.
Lost the 3 button options and ended up hacking a jig to get it into DL mode. done
Goal - a Functioning phone. Now what?
Thinking I should odin the I9000M_JL2_JL2_JL2_JL2_UG_BMC.tar.
But with or without repartition?
Can I use any 512pit?
I think repartitioning is where i messed it up.
Now all of this happened because I wanted seeARMS.JL2.v0.4 but couldn't update with the recovery mode.
Knowing that seeArms is my second (first?) goal, is there a different firmware I should flash something other than BMC to give me back update functions, but stable to resuscitate my phone?
There's ages of material here and I don't want brick my phone or waste time, I've done enough of that by myself.. now I'm looking for some expert opinion.
thanks
Click to expand...
Click to collapse
Flash the stock JL2 firmware with Odin the use super one click to root your phone then flash a new kernel with SGS Kernal flasher from the market... then u will have clockwork recovery then wipe and flash seeArms! Its a great rom but not as fast as darkys
Get the stock firmware from samfirmware.com u can get the .pit file from there to
Sent from my bell GT-I9000m using XDA App
repartition yes? .pit universal?
Jason123420 said:
Flash the stock JL2 firmware with Odin the use super one click to root your phone then flash a new kernel with SGS Kernal flasher from the market... then u will have clockwork recovery then wipe and flash seeArms! Its a great rom but not as fast as darkys
Get the stock firmware from samfirmware.com u can get the .pit file from there to
Sent from my bell GT-I9000m using XDA App
Click to expand...
Click to collapse
So the stock JL2 that I have is a .tar and .dll
I have a 512.pit from a beta 2.2 , are they different?
Did I mention boot problems too? Hanging @ Samsung, no splash ani.
I guess the .pit means yes on repartition?
Thanks
Just use the stock firmware and .pit from samfirmware.com and when Odin is open do not tick off repartirion... just put the .pit in it's spot and the tar in th's PDA part and flash
Sent from my GT-I9000 using XDA App
Now I'm no pro... I just flashed a rom once and got stuck in a boot loop and this is what worked for me
Sent from my GT-I9000 using XDA App
Recovery back but can't mount /dev/block/stl10
Decided to try Darkys v9.2 Resurrection.. no go.
Flashed JL2 and got recovery back but crash after animation.
3e recovery shows me Can't mount /dev/block/stl10.
some threads say dead, others make ref. to old builds.
any current ideas?
thanks
Sorry man like I said I'm no pro... ide flash stock jl2 back and send it back to Samsung for repair maybe they will do something for your warranty
Sent from my GT-I9000 using XDA App
Lyon huntington said:
Decided to try Darkys v9.2 Resurrection.. no go.
Flashed JL2 and got recovery back but crash after animation.
3e recovery shows me Can't mount /dev/block/stl10.
some threads say dead, others make ref. to old builds.
any current ideas?
thanks
Click to expand...
Click to collapse
Download a full firmware for your model and locale (with dbdata in it) and flash it with repartition with the pit proposed (samfirmware.com) then, I believe, you will have a full functioning phone. If everything is ok, then flash ... whatever.
It's Alive! - Can't mount /dev/block/stl10 fixed.
Hey All,
Got it all working again.
Repaired: Can't mount /dev/block/stl10
the fix: A full firmware (pda/csc/phone/pit) flash w/repartition.
Flashed w/repartition - I9000XXJP2.7p. (the only FULL firmware I had on-hand)
on reboot the system does a media check and was successful in reformatting and mounting the internal SD.
Phone didn't like the ROM and still logo of death, but..
A quick Jig into Download Mode..
Flashed I9000UGJL2_homebinary_add_param.tar with no repartition
(can't remember if I used .pit).
And Success!! my phone is alive and running 2.2
Thanks for the help, and hopefully this thread can help others.
Everyone should build/get a jig
There is nothing more awesome than being able to force download your non-booting phone.
I could not have done this repair without one.
http://forum.xda-developers.com/showthread.php?t=819551.
The only problem now is it's back to stock...
oh phone, how can I crash you next?
thanks again everybody!
tsinc said:
Download a full firmware for your model and locale (with dbdata in it) and flash it with repartition with the pit proposed (samfirmware.com) then, I believe, you will have a full functioning phone. If everything is ok, then flash ... whatever.
Click to expand...
Click to collapse
Yes, do this. For repartition to work the .tar has to have dbdata.rfs, otherwise it won't work.
Then flash a speedmod kernel with odin for root/cwm and flash you're favourite custom rom
unlock&root owngrade or speedmod kernel? suggestions?
Forgot to mention that all this started after I got the phone back from Bell service after SD card failure.
I know mod methods changed with the latest firmware, as I had used the update.zip method that is now unavailable.
My phone went in unlocked and rooted
the phone came back re-locked (old code doesn't work? wtf?),
and it was unrooted w/3e recovery
Can the phone unlock code change?
Will downgrading to 2.1 make unlocking easier?
or is unlocking just as simple after a speedmod kernel with odin for root/cwm
Which is better?
downgrade the firmware to 2.1 and root using the old update.zip method or speedmod kernel?
Which kernel? (link please )
cheers
Lyon huntington said:
Hey All,
Got it all working again.
Repaired: Can't mount /dev/block/stl10
the fix: A full firmware (pda/csc/phone/pit) flash w/repartition.
Flashed w/repartition - I9000XXJP2.7p. (the only FULL firmware I had on-hand)
on reboot the system does a media check and was successful in reformatting and mounting the internal SD.
Phone didn't like the ROM and still logo of death, but..
A quick Jig into Download Mode..
Flashed I9000UGJL2_homebinary_add_param.tar with no repartition
(can't remember if I used .pit).
And Success!! my phone is alive and running 2.2
Thanks for the help, and hopefully this thread can help others.
Everyone should build/get a jig
There is nothing more awesome than being able to force download your non-booting phone.
I could not have done this repair without one.
http://forum.xda-developers.com/showthread.php?t=819551.
The only problem now is it's back to stock...
oh phone, how can I crash you next?
thanks again everybody!
Click to expand...
Click to collapse
All you did was flash UGJL2 with no repartition and it brought your phone back?
Kops said:
All you did was flash UGJL2 with no repartition and it brought your phone back?
Click to expand...
Click to collapse
You know what....I've been trying various combinations of CSC/MODEM/PIT and everything to get this phone running again.
All I did was select a FULL UGJL2, and thats IT. NO pit, NO repartition, and it worked
The best way to revive your I9000m is to first flash JPC (a three file ROM) with 512 PIT and repartition ticked. The phone will still be in a boot loop. Then flash the JL2 PDA without repartition or PIT. The best way to go back to stock! Has always worked for me. I9000m's are not the same as other I9000's and do not flash repartition and the PDA in the same flash! Good luck!
Hi,
This is my first time experimenting with flashing custom roms. I was trying to flash a custom rom onto my perfectly working newly rooted sgs (using odin), but the first rom i tried has gotten my phone to boot loop and now I don't know what to do with it. I can get to the download screen just fine and recovery mode but don't knwo what to do. Please help, I really can't afford a new phone/ don't know if samsung will let me replace it now.
Oh, the rom was the XXJVK Gingerbread which is near the top of the forums right now, if that helps at all.
I really just need my phone to be usable, I didn't expect to mess it up. Thanks again to anyone with information.
I assume you were running jl2. The problem might be because of bootloader issue.
When you were flashing gingerbread did you use pit file and repartition?
I am not a pro but If you download JL2 and flash it, should be good to go. Try not to repartition and flash without using pit file.
I did use the .pit and repartition. I'm guessing this was a no no? I'll look for jl2 and try flashing that. Might you direct me to the right download?
http://www.multiupload.com/6GRS1OWRJW
I have no idea if it will work or not. Same thing happened to me also when I was trying to flash darkys rom and I was able to open the phone after I flashed with bells original rom. Give it a try. If its a boot loop I assume its a firmware problem. You should be able to fix it. The problem might be the repartirion and pit file. I am not sure about it. Hope this helps.
Just try flashing again with boot loader update ticked in odin. I'm pretty sure that repartition and pit do nothing to the bootloader. If that doesn't work I'll add more after I shower, I stink!
Sent from my GT - I9000 running Darky's 9.5 w/ DamianGTO's Ultimate Kernel using XDA Premium App.
A bootloop = ****ed framework and/or /system/ (rom)
Flashing bootloaders will not fix the problem, they are not related at all. And if a bootloader flash fails your phone will actually be bricked.
Just flash a stock rom with odin. I recommend jl2 if you want to go official stock, js8 for fastest froyo stock or jvk for the latest leaked beta. Tick update bootloaders for jvk or jl2 flash because jvk requires jvk bootloaders and jl2 because it supposedly fixes corruption problems. Remember bootloaders are overwritten every time you flash them and us risky.
Sent from my GT-I9000 using XDA Premium App
Thanks a million guys, I did flash the stock jl2 (no .pit or partition, nor bootloader update) and the phone booted. It fed me a gajillion force closes, but i managed to connect to kies and updated it that way, so now I have a perfetly working phone again. I'll probably experiment with a few more things now that I know how to fix this.
Again, Thanks guys!
Hi all,
Trying to update a friends SGS, and having a bit of a problem. I have sucessfulyl flashed GB 2.3.3 from ROMKitchen to it, however trying to flash any other kernel to it fails... sorta.
After flashing the ROM the recovery is always Samsung default (3e). I have used Odin to try and flash different kernels (Voodoo GB experimental - both the initial release, and the latest version, and several others)
The odd part is this seems to work, until the phone is rebooted - for instance today after flashing Voodoos latest, I reboot into the OS and checked Settings > About Phone, the kernel had updated to "curio (at) carton #Voodoo" but after rebooting this is undone..
Unfortunately the friend I am doing all this for was on tight schedule and had to leave, so there wasn't much time for experimentation, but has anybody seen this happening, and know what to do?
Kernel Flash
Did you make sure that in Odin you put the .tar file into the field PDA and not Phone? I flashed once curios kernel through the Phone-field and the modem did not flash correctly.
Besides that I never had any problems flashing a kernel. You can try the app SGS Kernel flasher from the market if you happen to have problems again.
dachau said:
Did you make sure that in Odin you put the .tar file into the field PDA and not Phone? I flashed once curios kernel through the Phone-field and the modem did not flash correctly.
Besides that I never had any problems flashing a kernel. You can try the app SGS Kernel flasher from the market if you happen to have problems again.
Click to expand...
Click to collapse
Yeah, It's definitely in PDA. The odd thing about this all is I did the very same process on my phone, and it worked. On his no matter what I do his recovery will always end up at stock - even the kernel in the romkitchen package doesn't seem to be taking effect.
Then update recovery as always via Clockwork post .
jje
Hi,
I was trying to install cynogenmod 7.1 on my galaxy s vibrant i9000. My carrier is bell
Model Number GT-I9000M
Firmware Version 2.3.3
Baseband Version I9000UGKG3
Kernel Version 2.6.35.7-I9000UGKG3
[email protected]#2
build GINGERBREAD.GKG3
When I was trying to do go in recovery mode, backup Rom or change ROM with ROM manager, it went on the 3e recovery setup and was saying something about the whole-signature failed. I've read somewhere that this was due to the fact that my kernel was restricting something and that I needed to change my kernel with Odin in order to not being signature verifed anymore. So I picked up a kernel on a forum and tried to put it in my galaxy s in download mode with Odin and the PDA button while having the re-partition button unchecked.
After doing so, odin said that the operation failed and when I disconnected my phone, there was only a small icon showing a cellphone and a computer with a small triangle with a ! in it between the cellphone and the computer. In other words I messed things up and my sgs wont boot anymore.
Can someone give me a good kernel to put in my phone so it can reboot? Because I still can go in download mode!
I know, Im a total newbie...
Thanks
I assume that the ID:COM box in Odin went yellow before you pressed the Start button initially....
If not, that's your first problem that needs to be addressed, as you can't flash unless Odin can see your phone.
You can get a rooted kernel here.
If that doesn't get you up and running and you haven't downloaded UGKG3, go here and search for UGKG3 and download it.
omg, thank you sooooooo much! It worked!
Do you know a kernel that I could use to for my phone to accept custom ROMs ?
Glad that worked.
UGKG3 does not have a lot of support from the developer community, as it's a rather rare release with only a couple of carriers using it.
Semaphore and CF-Root seem to be the popular ones that include CWM.
Not sure which one you would use with UGKG3, as it's not well supported.
hey
i rooted my galaxy S I9000 with odin an the cf kernel: CF-Root-XW_DBT_JVI-v3.7-CWM3RFS.tar.
the flash worked fine, but after the reboot I get no connection to my mobile network. When I want to see the options in Mobile Network I get the message: Insert SIM card to access network services" but it is insertet correctly.
thanks for your help
I think I now know what I did wrong. I used the phone field in Odin to flash. Now with *#1234# in Phone there is written down: UNKNOWN. Is there a way to reset this to the normal version?
if you flashed the kernel as phone, then you probably didn't get it rooted successfully either.
Flash the phone file that you were using originally and it should be fixed. I think you can probably try to flash a kernel with CWM under PDA, and use cwm to get a new modem file (search around, there are a lot).
A definite solution is to just flash the entire firmware again - though if you're going that route might as well update to the latest jvu firmware or something.
rallisch said:
I think I now know what I did wrong. I used the phone field in Odin to flash. Now with *#1234# in Phone there is written down: UNKNOWN. Is there a way to reset this to the normal version?
Click to expand...
Click to collapse
Just flash back to stock ROM first using ODIN, then root it again keeping the cfroot file under the right tab!!