Database Develop

[Q] Flashing stock 2.2.1 ROM on branded i9000 questions.

A friend of mine is on a T-Mobile UK Samsung Galaxy S. He's stuck on a non-simlocked and non-netlocked 2.2 (JP3), T-Mobile UK aren't releasing 2.2.1 any time soon, and hence he wants to upgrade to an unbranded 2.2.1. He doesn't want to root it... he just wants to be on the same or similar firmware as I'm on (i.e. a stock, stable, UK, unrooted, no "lagfix", etc, 2.2.1).
He has Odin. He has the Windows drivers installed. But I have some questions.
I'm on JPY which has been perfect for me. Zero problems. Is there much advantage with JS5? What has changed/added between JPY and JS5?
Best place to get the European firmware is here? http://forum.xda-developers.com/showthread.php?t=846913
Does he need just a pit file, or other files (e.g. tar) too?

extorian said:
A friend of mine is on a T-Mobile UK Samsung Galaxy S. He's stuck on a non-simlocked and non-netlocked 2.2 (JP3), T-Mobile UK aren't releasing 2.2.1 any time soon, and hence he wants to upgrade to an unbranded 2.2.1. He doesn't want to root it... he just wants to be on the same or similar firmware as I'm on (i.e. a stock, stable, UK, unrooted, no "lagfix", etc, 2.2.1).
He has Odin. He has the Windows drivers installed. But I have some questions.
I'm on JPY which has been perfect for me. Zero problems. Is there much advantage with JS5? What has changed/added between JPY and JS5?
Best place to get the European firmware is here? http://forum.xda-developers.com/showthread.php?t=846913
Does he need just a pit file, or other files (e.g. tar) too?
Click to expand...
Click to collapse
JPY is the lastest UK rom pointless using anything else until its out for the UK
People here just love new numbers and letters.
if he is going from branded would be best to use a pit file. ( pit 512)
then flash the 3 JPY files.
I tend to debrand phones when I get them in as I don't think its fair being stuck on older versions.

So... download Odin + PIT from the top of that page I linked. Flash the 512 PIT using Odin with repartition. Download the JPY firmware from the same page. Flash the 3 files in there. Reboot. Done?
What about clearing cache? Factory reset?
Anything else?

Flashing with Odin will do the factory reset.
Sent from my GTI-9000 Using that XDA app thingy

We've hit a problem
He's been trying the files on this thread: http://forum.xda-developers.com/showthread.php?t=846913
He selected repartition, and flashed the PIT file + JPY_JPY_JPY.tar at the same time (although I believe we've tried one at a time too).
Now when he reboots his phone it doesn't boot - it just vibrates.
He's tried going into recovery and clearing the cache, user data, factory reset, etc.
He can still get into download mode and recovery.
Any suggestions?

extorian said:
We've hit a problem
He's been trying the files on this thread: http://forum.xda-developers.com/showthread.php?t=846913
He selected repartition, and flashed the PIT file + JPY_JPY_JPY.tar at the same time (although I believe we've tried one at a time too).
Now when he reboots his phone it doesn't boot - it just vibrates.
He's tried going into recovery and clearing the cache, user data, factory reset, etc.
He can still get into download mode and recovery.
Any suggestions?
Click to expand...
Click to collapse
Flash pit with repartition selected.
Wait till you see a green box with pass
Unplug phone take battery out.
Then put it back on download
Click reset it Odin
Untick repartition
Select all three jpy files.
Plug in phone. Click start.
Leave till you see green pass.
Sent from my GTI-9000 Using that XDA app thingy

All three files? Should they have come with the firmware download? That only contained a 300MB file JPY_JPY_JPY.tar.

extorian said:
All three files? Should they have come with the firmware download? That only contained a 300MB file JPY_JPY_JPY.tar.
Click to expand...
Click to collapse
Different to how I get them direct for Samsung. So wouldn't know sorry.
Sent from my GTI-9000 Using that XDA app thingy

Can we get the JPY firmware direct from Samsung?

No, but samfirmware.com has all those firmwares.

Yeah they have JPY. However it's just a 512 PIT file. Is that all he needs?

Thats what i flash JPY with .
Error solving with a rom install i usually wipe everything flash back to eclair with 512 pit and repartition . That works i then flash to Froyo no repartition .
jje

Still no joy
OK, so as per the instructions above (I think), we made sure the SIM and SD card are removed. Connected the phone. With Odin, ticked Repartition, and then flashed the 512 .pit file. Waited until we saw the green box in Odin with Pass on it. Unplugged the phone and took the battery out. Put battery back in and booted the phone into download mode. Clicked Reset in Odin. Made sure re-partition was unticked. Made sure the pit file is no longer selected. Added the JPY_JPY_JPY.tar to the PDA section. Plugged in phone. Clicked start. Left it until we saw green pass. On restarting the phone, it to boots past the Galaxy S splash screen and tune then there's a single vibrate followed by a double, which then repeats.
Did we do something wrong? We noticed in Recovery there is an error displayed:
E:can't mount /dev/block/st110 (invalid arguement)
E:copy_dbdata_media:cant mount DBDATA:
copy default media content failed
What else can we try to get to JPY?
The firmware from samfirmware.com and the firmware linked from the firmwares post on XDA (mentioned earlier) both give an identical JPY_JPY_JPY.tar. We've been unable to find any firmwares with the three JPY files in it. Anyone have a link? Or any other things we can try?

extorian said:
Still no joy
OK, so as per the instructions above (I think), we made sure the SIM and SD card are removed. Connected the phone. With Odin, ticked Repartition, and then flashed the 512 .pit file. Waited until we saw the green box in Odin with Pass on it. Unplugged the phone and took the battery out. Put battery back in and booted the phone into download mode. Clicked Reset in Odin. Made sure re-partition was unticked. Made sure the pit file is no longer selected. Added the JPY_JPY_JPY.tar to the PDA section. Plugged in phone. Clicked start. Left it until we saw green pass. On restarting the phone, it to boots past the Galaxy S splash screen and tune then there's a single vibrate followed by a double, which then repeats.
Did we do something wrong? We noticed in Recovery there is an error displayed:
E:can't mount /dev/block/st110 (invalid arguement)
E:copy_dbdata_media:cant mount DBDATA:
copy default media content failed
What else can we try to get to JPY?
The firmware from samfirmware.com and the firmware linked from the firmwares post on XDA (mentioned earlier) both give an identical JPY_JPY_JPY.tar. We've been unable to find any firmwares with the three JPY files in it. Anyone have a link? Or any other things we can try?
Click to expand...
Click to collapse
You only use the PIT file and choose re-partition when you have the 3 separate flashing files.
When you have the singe JPY tar file you do not select re-partition and do not use the PIT file - do the following:
put phone into download mode
open Odin
choose your single JPY file as the PDA
make sure "re-partition" is UNTICKED
DO NOT select your PIT file
connect your phone to PC via USB
Odin will detect your phone - click start
let Odin do its stuff until your phone restarts
you are now on 2.2.1 stock
I always do an immediate factory reset.....it seems to sort out any lags or issues that you occasionally get after flashing
good luck!

When he tries to just the .tar without repartition or .pit, Odin fails.
When he tries to format the internal SD card from Recovery it says:
E:can't mount /dev/block/st110 (invalid arguement)
E:copy_dbdata_media:cant mount DBDATA:
copy default media content failed
It could be that repartitioning previously has messed stuff up? Maybe the wrong PIT (we used 512)? I've read in a few places that Clockwork recovery can fix this. Thoughts?
Or is there a 3 file JPY option we can use?

So, according to this thread http://forum.xda-developers.com/showthread.php?t=784958#8180949 it seems we messed up the partitions by using the pit file originally with repartition. If JPY isn't a full firmware we'll need to flash back to a full firmware to fix it. For example he says "The reason for this screwup is because the JH7 tar package does not contain params or dbdata files, it's not meant to be a full installer- it's meant to be an upgrade. When you partitioned you deleted your existing dbdata and params partitions on your phone, so when JH7 tried to set them up they didn't exist."
We're going to try JPU (somewhere said that's a full update) with 512 pit + repartition, then if that boots update to JPY (no pit, no repartition).

FIXED!!!
After putting the three-file JPU on it from samfirmware.com with 512 pit and repartition, it booted up into 2.2.1 fine. We then flashed the JPY tar (no pit, no repartition), and it's working.
Thanks for the help guys.

Thats great news. X
Sent from my GT-I9000 using XDA App

Hi I am the friend that has caused the headache throughout this thread, I'd just like to say a big thank you to extorian and everyone else that provided input and solutions to getting the rom installed on my phone.
I'm over the moon with the update, phone runs better than ever. Thanks again.
Sent from my GT-I9000 using XDA App

[Q] What is my firmware?! (Bell Canada i9000m)

I'm on Bell Canada.
My I9000M is currently in boot loops.
I've searched and searched but I can't find the all the files I need to revert to stock.
I need the following:
PIT:
PDA:
PHONE:
CSC:
Can someone please tell me what files I need and where I can download them?
I find the instructions on samfirmware to be very poorly written.
Edit: I found this url: http://forum.xda-developers.com/showthread.php?t=1022445 should I use these files? If so, what PIT should I use?

you can find it all here : http://forum.xda-developers.com/showthread.php?p=12685962
Never mind. I didnt read your edit. I recovered mine from a soft brick by using those files without bootloader, no pit or repartition.
Good Luck

Flashed with these 3 files and boot is still looping!
Any ideas?

Search for EZ base. Its a pre configured set of poison files used specifically to restore your phone.

Kops said:
Search for EZ base. Its a pre configured set of poison files used specifically to restore your phone.
Click to expand...
Click to collapse
Trying this - will report back.
Failed.
Still boot looping.

Just use odin with the pit file and checked repartition. When you get bootloops you should always flash with pit and checked repartition instead of saving like 10 seconds to mount them. Just mount the phone, pda and csc (if any), mount the pit file, tick the repartition option and flash it.

Soft bricked N7000. How to?

Tried everything I could with Odin and phone still stuck in a start loop.
I was downgrading from checkROM to official firmware ZSLA2 with CWM (I wanted to keep ROOT, so I selected "Keep CF-Root kernel") due to stability issues, after restarting the phone got into the start loop.
I flashed with Odin official ZSLA2 with the same result (looped start). I flashed XXKKA (again looped start). During the flashing process, Odin says the flashing was successful. By the way, both ROMS are tar.md5 files.
I tried to remove the battery for over 30 minutes and charge it for 2 hours, tried re-partition in Odin (it's my understanding that with a stock rom, it creates a clean installation), but Odin fails to start the process.
What else can I do?
I am sorry if this has previously asked, but I've been searching for over 2 hours and nothing similar came. Somebody mentioned to use a PIT file in addition, but the other person who got his phone soft bricked didn't solve the problem either. As downloading a ROM is time consuming and I've got many problems with upload sites in china (cannot access to most of them), I would thank any help in regards this issue.

Sounds like your kernel isn't talking properly to your ROM.
A fresh start is your best bet. Flash a stock rom and kernel from Odin and reroot it with CF-Root.
What files are you putting into Odin? There should be a total of 4.
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)

I am using official ROM N7000ZSLA2_N7000ZSLA2_N7000XLA4_HOME.tar.md5 into PDA and also tried ROM N7000XXKKA_N7000XEUKK3_N7000XXKK5_HOME.tar.md5, which I used successfully in the past to make root into my phone.
Does it really make a difference to flash 4 separate files instead of a full pack? Where can I find an official ROM with pda radio and kernel separated? Just untar the ROM?

btyork said:
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)
Click to expand...
Click to collapse
Oh, they do come into the Note; I flashed the Beta ICS, and one of the things they mention is to use the PIT file for the 16GB version, instead of the 32GB that comes with the leaked ROM. Unfortunately I deleted that ROM, and donwloading it is painfully slow and also wouldn't necessarily solve my problem as I couldn't even make a phone call.

True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.

Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.

btyork said:
True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.
Click to expand...
Click to collapse
This are the files I am flashing:
Sorry, I am new user and still cannot post screen captures. I do have more than the 5 files.
In XXKKA I have:
Boot
Cache
Factoryfs
Hidden
Modem
param.lfs
Sbl
zImage
In ZSLA2:
Cache
Factoryfs
Hidden
Modem
zImage
btyork said:
Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.
Click to expand...
Click to collapse
I can only enter into Download mode, not recovery mode.
Odin is full wipe, right? What the hell am I doing wrong?

N7000xxla1_n7000oxala1_oxa
http://hotfile.com/dl/141060546/b0c7420/N7000XXLA1_N7000OXALA1_OXA.rar.html
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han

choihan06 said:
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han
Click to expand...
Click to collapse
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you

mrfan said:
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you
Click to expand...
Click to collapse
I have just recently dowloaded and installed the rom without problem. What do you mean by corrupted rom?
Sent from my GT-N7000 using xda premium

I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.

Fix The problem
I had the same problem, the device got into start loop. JUST DO A FULL WIPE..! and the device should start normally. I worked for me.... :good:
Sent from my GT-N7000 using xda premium[/QUOTE]

[Q] i need help for my friend's sgs 1

hi frnd i own a Xperia Neo V but here i am for my frnd he has did something wrong with his phone and its not booting up i can enter recovery/download mode i just want to knwo how to flash i9000
i have downloaded
Flashprogram Samsung I9000 + Pits
firmware version XAJW5_XEU from samfirmware
i have flashed 5830 and 5801 but i dont find odin to be similar as them
can any1 tell me how to flash i9000 and what pit to use cause i can see 3 pits in it
803
513
512
or a full procedure will be helpful
am just trying to help my frnd to fix his S1

you will need to have the galaxy S drivers installed on the computer they can be downloaded and installed as part of Kies or seperatly from a thread in the I9000 (SGS) section of XDA just search for "Samsung Drivers.exe"
As for flashing Phone put it into download mode and connect USB cable
If the file downloaded is a single file .TAR place into PDA of odin
if 3 file place PDA into PDA, CSC into CSC and PHONE into PHONE and flash.
Most GingerBread ROMs use 512 PIT check on samfirmware as to the suggested PIT file.
NOTE a pit file is not always required but cannot hurt. just ensure that repartition is not checked

what will happen if i re partition it.. will it format everything

imranaryan said:
what will happen if i re partition it.. will it format everything
Click to expand...
Click to collapse
re partition will fully wipe the OS partitions, not the SDcard partition but sometimes errors do occur with the SDcard.
The ROM on the phone does retain a copy of the PIT file and can access it during a odin flash.
it is very important to use the correct pit file for the rom or it will not boot

Semi-Brick....could be the eMMC brick!?!?

Hello all,
I recieved a Galaxy Note for repair from a friend of mine. She says that the phone was working normally until it rebooted and then didnt get past the first Samsung Galaxy Note Logo.....she took it to samsung who said it was a faulty motherboard (hint: possible eMMC brick, though in India, thats their go-to response). The phone now shows a firmware upgrade failed sign (PHONE----------!-----------PC) telling me to plug it into Kies, which doesnt recognize it. It doesnt go into recovery mode at all but goes into download mode. I opened odin and flashed a stock gb rom with pit file(repartition ticked). The phone gets stuck at Set Partition. Have tried different Odins, different USB Cables, ticking diff. options in odin and god knows what else. How do i get this phone up and running? Is it the emmc brick bug? I think it is...

did you kill kies processes before using odin?

Yup. Done already....no change

if it gets stuck at repartition process, then its more than an eMMC brickbug. How its the phone right now?, can you go to recovery?. The best you can do: flash a safe kernel and then a cyannogenmod (or AOSP) rom, if it boots (probably you will get a lot of force closes), try to flash a jelly bean stock rom (without repartition) and then repartition it.
If still not work, the last option its jTag (riff box), it will repartition the whole phone.
Sorry my bad english

Hmmm, I'm not sure about that last part, but if I do it without repartition, it gets stuck at nand write of cache. Right now, it either goes into upgrade failed connect to kies sign or into download mode, both of which I'm guessing are the same

try uninstall and reInstall you samsung usb driver...
http://forum.xda-developers.com/showthread.php?t=961956
and try use other pc odin version..
try flash without repartition.

Checked. Same issue

xyancompgeek said:
Checked. Same issue
Click to expand...
Click to collapse
Odin stuck on?..
lets try flash kernel using pc odin
http://forum.xda-developers.com/showthread.php?t=1901191

Odin is stuck on this screen. Phone is in download mode. Cannot go into recovery.

You might need a usb jtag thing.maybe that will help in getting ur phone 8dentifiedby odin
Sent from my GT-N7000 using xda app-developers app

It is recognized by Odin, it just cant flash anything. One thing though, odin 3.07 atleast has the courtesy to tell me that it failed on set partition, odin 1.85 gets stuck at set partition.

what are you trying to do? you are only selecting the PIT file and nothing else in Odin. use the Original PIT not modified one with the rom file in PDA .
Nothing more is supposed to happen if only PIT file is added to odin. Donot use a custom PIT file till its confirmed a EMMC corruption.. use the original PIT file from Dr Ketans Guide in Original Dev Section