Related
On first boot I get
Can not mount / dev/block/stl10 (Invalid argument)
copy_dbdata_media: Can not mount DBDATE
Not Prepared your storage yet, please use UI menu for format and reboot actions
default copy content failed half
wiping / data cache and Does not Seem To fix anything.
Format sdcar unresponsive
HELP any occurrence and brick my phone
criskelo said:
On first boot I get
Can not mount / dev/block/stl10 (Invalid argument)
copy_dbdata_media: Can not mount DBDATE
Not Prepared your storage yet, please use UI menu for format and reboot actions
default copy content failed half
wiping / data cache and Does not Seem To fix anything.
Format sdcar unresponsive
HELP any occurrence and brick my phone
Click to expand...
Click to collapse
Go to Download Mode and flash ROM XWJM8 with pit512 and Re-Partition,after flash XXJPM with pit803 and without Re-Partition-this help
sardor said:
Go to Download Mode and flash ROM XWJM8 with pit512 and Re-Partition,after flash XXJPM with pit803 and without Re-Partition-this help
Click to expand...
Click to collapse
Fixed in a while I explain
My solution
With Odim 1.3, pit 512,
in my case JH2 I9000T GT
But for Europe JM8
Mark Re-partition, phone EFS clear and Phone bootloader Update
Then start
This process started well
JPM Process
Then uncheck re-partition, phone EFSclear and Phone Bootloader Update
JPM Pit 803 and firm JPM
Start
To enjoy
Thanks
criskelo said:
Then uncheck re-partition, phone EFSclear and Phone Bootloader Update
Click to expand...
Click to collapse
Is it normal for T model, or you just use weird and dangerous settings for fun?
Wiping EFS can lead to test-imei number and broken product code. Be sure you haver a backup of that folder before wiping that.
criskelo... I tried this and I didn't get anywhere :/
I had the same issue and it took me 2 hours to resolve (with a lot of pain, lol).
I've simply flashed the XWJM8 version using odin 1.3, no pit file and HENCE no repartition ticked.
It then booted to recovery console, because there was another error (can't remember which one cause I was too excited).
Anyway I did a wipe, cash clear and reformat SD card at the menu and let it boot.
After that I have flashed the latest version XXJPY also without PartitionInformation Table. (PIT). Then all the wipe and format stuff again.
I have now to go from scratch to setup anything again, but hey, at least my phone is alive again.
Some additional info. I also had that connection symbol on the screen with exclamation mark and triangle....so I thought I was done (due to trials with pit 512 which hung), but after removing battery and some trials I was able to enter download mode again....
Why happened that? I DON'T KNOW! I simply wanted to reflash the XXJPY stock rom, this time with pit512 and it lead to the topic of this thread!!!
This su**ed a lot, I didn't even modify something before!!!!
So: Less is even more! Don't fiddle with EFS and bootloader options it worked for me even without a pit!
Thanks to sardor for the initial idea, the XWJM8 seems to be a fixing rom for that when used properly, anyway to load a pit without to tick repartition is not a useful setting!
Well I was a long time reader at this great forum, IMHO the best regarding phone stuff, because there is the most useful knowledge shared.
I hope my first post will save other phones as well from sending it to repair.
Thanks I'm happy again..(let's see how long it'll last..lol...)
bricked my samsung galaxys and recoverd it
Hi I had exact same problem I totally bricked my i9000 Australian Optus version
I used
I9000DTJG4 firmware Australian Optus
With pit 512
And odin3 v1.3
Got all the files from
samfirmware . com / WEBPROTECT - i9000 . htm
Had to sign up but it’s free
However following criskelo's advice I unchecked the re partion box in odin
Even though the site above tells u to check it
And it worked
Thanks for everyone’s help on this thread.
Without you I would have had an expensive paper waited
Also the reason I got here in the first place as because I messed around with lag fix in clockwork recovery when I don’t know anything about it.
I was lucky this time but it’s really not worth playing around with things you doing understand.
sardor said:
Go to Download Mode and flash ROM XWJM8 with pit512 and Re-Partition,after flash XXJPM with pit803 and without Re-Partition-this help
Click to expand...
Click to collapse
I was messing with Darky's Rom which alway cause problems for me and found myself in the same situation as the first post.
What worked for me.
JM8 (2 files = code to PDA - Modem to PHONE) + Repartition + 512pit
after reset different error so goto download mode again then:
JPM + 803pit
Default OS reconfigures, Thank Fook
Awesome, thanks buddy! I have spent too much time trying to fix this phone and it all totally pays off now!
Here is the fix for the Bell firmware:
Background info: I orginally tried the Lagfix and bricked my phone, this is how I finally fixed it...
1. Using Odin v1.82
Put Phone in download mode
Use PDA: I9000UGJH2
Use Phone: Modem.bin
(both files came from samfirmware, I9000UGJH2 download)
Use: 512.pit(also from samfirmware at the bottom of the i9000 page)
Check Re-Partition, Auto-reboot, F. reset time, phone EFS clear and Phone bootloader update. I know everyone above says don't but I tried their way first and it didn't work, I would recommend you do try their way first and if no results try mine.
2. Using Odin v1.82
Put Phone in download mode
Use PDA: I9000UGJL2
Use 803.pit
Check only Auto-reboot, F. reset time
Good luck! I hope you do your happy dance like I did!!
crazycanuckeh said:
Awesome, thanks buddy! I have spent too much time trying to fix this phone and it all totally pays off now!
Here is the fix for the Bell firmware:
Background info: I orginally tried the Lagfix and bricked my phone, this is how I finally fixed it...
1. Using Odin v1.82
Put Phone in download mode
Use PDA: I9000UGJH2
Use Phone: Modem.bin
(both files came from samfirmware, I9000UGJH2 download)
Use: 512.pit(also from samfirmware at the bottom of the i9000 page)
Check Re-Partition, Auto-reboot, F. reset time, phone EFS clear and Phone bootloader update. I know everyone above says don't but I tried their way first and it didn't work, I would recommend you do try their way first and if no results try mine.
2. Using Odin v1.82
Put Phone in download mode
Use PDA: I9000UGJL2
Use 803.pit
Check only Auto-reboot, F. reset time
Good luck! I hope you do your happy dance like I did!!
Click to expand...
Click to collapse
hey how did it worked for you. Not working for me.
did you extracted the tar file? which file did you loaded into the pda tab then ?
Didnt worked for me at all
sardor said:
Go to Download Mode and flash ROM XWJM8 with pit512 and Re-Partition,after flash XXJPM with pit803 and without Re-Partition-this help
Click to expand...
Click to collapse
you saved my phone after me corrupting internal SD! just did my victory dance though hands still shaking a bit
Just thought I would add to what got my phone back running again after having the Can't mount DBDATA error. It's a bell I9000M.
Used Odin 1.3 , Flashed Darky's resurection per his instructions pulled battery once complete, went back into download mode and flashed stock JL2 with Odin , re-partition un-checked and no Pit file and after that my phone was running again.
You can find Darky's Resurection Here!
Can not find the link for the JL2 stock rom but it's in the general section somewhere.
the xxjpu version worked for me
tlick repartition
add 512 pit
tick and add pda
tick and add modem
tick and add csc
go to download mode
connect usb
press start
Need help with Fascinate
Hey guys, I've read the above posts but frankly it's above my skill.
Some how I ended up with the same message that the OP got.
Can someone walk me through the steps to completely fix my phone and get it back to bone stock?
I'm not familiar with PIT and other files. I need someone to hold me hand on this one...
cddt said:
I was messing with Darky's Rom which alway cause problems for me and found myself in the same situation as the first post.
What worked for me.
JM8 (2 files = code to PDA - Modem to PHONE) + Repartition + 512pit
after reset different error so goto download mode again then:
JPM + 803pit
Default OS reconfigures, Thank Fook
Click to expand...
Click to collapse
Was also messing around with darky. decided to go back to 9.5 for now. also got the error, then did what cddt said (thanks!!).
first flash - different error (something about CSC)
for second flash i used JS7 + 803pit + no repartitioning
worked flawlessly Thanks!
Stuck in boot loop
Samdroid_G_S said:
Just thought I would add to what got my phone back running again after having the Can't mount DBDATA error. It's a bell I9000M.
Used Odin 1.3 , Flashed Darky's resurection per his instructions pulled battery once complete, went back into download mode and flashed stock JL2 with Odin , re-partition un-checked and no Pit file and after that my phone was running again.
You can find Darky's Resurection Here!
Can not find the link for the JL2 stock rom but it's in the general section somewhere.
Click to expand...
Click to collapse
Hi,
I have bell sgs and I tried this and since then my phone is on boot loop. I can only go in download but not recovery. IT all started when I installed the boot loader for gingerbread...
Flashing Error - resolved
cddt said:
I was messing with Darky's Rom which alway cause problems for me and found myself in the same situation as the first post.
What worked for me.
JM8 (2 files = code to PDA - Modem to PHONE) + Repartition + 512pit
after reset different error so goto download mode again then:
JPM + 803pit
Default OS reconfigures, Thank Fook
Click to expand...
Click to collapse
Just followed this and it worked a treat thank you
Hi there,
I am having issues the same way. I am unable to do something. Can some explain me the procedure how to do it.
From where can i get the files.
Please help me out
Hi, I got the JPY ROM from the thread in the general discussion, and any time i have tried to flash it onto my phone, the phone refuses to start properly. It just vibrates a couple of times and black screens.
I am using Odin 1.3 and PIT 512 for this as it says on SamFirmware.com.
Is this the ROM not working properly, or me doing something wrong?
Mate did you click repartition in odin?If you did then you SHOULDNT!!!!
Try to get in to recovery mod with the 3 button combo and make a factory reset if yo had NOT clicked repartition.
In case had HAD clicked repartition in Odin then i guess you ll have to download a foul stock firmware and flash it.Meaning a firmeare that has Modem and CSC files aswell and not only PDA file...
I'm just about to flash XXJPY and I was just wondering, do I have to unroot 'before' flashing the single file (pda) XXJPY or can I leave it as is..?? Does it make any difference..??
Thanks
tackygr said:
Mate did you click repartition in odin?If you did then you SHOULDNT!!!!
Try to get in to recovery mod with the 3 button combo and make a factory reset if yo had NOT clicked repartition.
In case had HAD clicked repartition in Odin then i guess you ll have to download a foul stock firmware and flash it.Meaning a firmeare that has Modem and CSC files aswell and not only PDA file...
Click to expand...
Click to collapse
haha, thanks mate, i forgot to try that, i'll give it a go later.
topcat888 said:
I'm just about to flash XXJPY and I was just wondering, do I have to unroot 'before' flashing the single file (pda) XXJPY or can I leave it as is..?? Does it make any difference..??
Thanks
Click to expand...
Click to collapse
nah you dont need to have it rooted to flash JPY.
I believe the JPY file in the general forum is just an upgrade / high level package which is why you dont tick repartition. Usually look for posts by Richthofen- hes the dude who converts it to mid level packages so you can couple it with a CSC and modem.
hi there same thing happened to me i updated this thru samsung kies im stock at black screen would factory reset make my phone work again? i need help please please please
dopeee said:
nah you dont need to have it rooted to flash JPY.
I believe the JPY file in the general forum is just an upgrade / high level package which is why you dont tick repartition. Usually look for posts by Richthofen- hes the dude who converts it to mid level packages so you can couple it with a CSC and modem.
Click to expand...
Click to collapse
I am already rooted so should I un-root before flashing or just leave it rooted..???
And also have SGS Battery Icon Mod installed, again does this have to be un-installed before flash or not..??
Can someone post a link to the right ROM that I can use to update using ODIN that will not result in existing data lost ? The one that I downloaded is a single tar file (Size - 298,890KB) that contains these files. If this is the right file, do i just specify the tar file in the PDA and uncheck repartition ?
modem.bin
param.lfs
zimage
cache.rfs
factoryfs.rfs
Does anybody know the difference between the two XWJS5 firmwares?
Difference...
Yes. The previous one is for Heimdall and the new one is for Odin.
As I saw.
I have heard that the new one contains a bootloader update.
I don't know if its true tho.
/qsec
temilla said:
Does anybody know the difference between the two XWJS5 firmwares?
Click to expand...
Click to collapse
Previous JS5 was an update flash (1 file), this one is a FULL Rom (3 file, 242mb). The same difference between JS3 and XEN JS3.
Anyway it shouldn't be 803 .pit. To recover from experimental partitioning I use JS3-full (which is tagged as 803) with 512.pit since 803 doesn't work for me.
matticala said:
Anyway it shouldn't be 803 .pit. To recover from experimental partitioning I use JS3-full (which is tagged as 803) with 512.pit since 803 doesn't work for me.
Click to expand...
Click to collapse
Thanks for that ! I'm trying to install these JS5 since yesterday with .pit 803 without success : mount problem at reboot after odin success, formating in recovery doesn't work and updating couldn't been done by new rom (vibrate loop reboot).
Changing to 512 .pit seems to solve this problem : my phone just restarts on JS5 now !
matticala said:
Anyway it shouldn't be 803 .pit. To recover from experimental partitioning I use JS3-full (which is tagged as 803) with 512.pit since 803 doesn't work for me.
Click to expand...
Click to collapse
OT- that's interesting as I flashed js3 with 803 unsuccessfully but it works with 512.
Sent from my GT-I9000 using XDA App
Content of I9000 XEN I9000XWJS5.rar:
Code:
GT-I9000-CSC-XENJS3.tar.md5
I9000XWJS5-REV03-ALL-low-CL869633.tar.md5
MODEM_I9000XXJPY.tar.md5
Confirmed there are a bootloader and a Sbl file, even though those are likely the same of those included in the previous XEN JS3. I'll make a checksum to verify
UPDATE: there is no update in this new XEN JS5, md5sum for boot.bin is identical to the one bundled within XEN JS3
MarkyG82 said:
OT- that's interesting as I flashed js3 with 803 unsuccessfully but it works with 512.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
guys please let me understand.... so why you are speaking about .512 and .803 .pit?
Using odin with last rom js5 from samsungfirmware I have to select just one file in pda tab, whitout .pit file.
what's wrong in my flashing way?
Be careful on updating. Double check the bootloader and Sbl.bin. We don't want the sgs to be locked, like the galaxy tab.
Sent from my GT-I9000 using XDA App
userinit said:
guys please let me understand.... so why you are speaking about .512 and .803 .pit?
Using odin with last rom js5 from samsungfirmware I have to select just one file in pda tab, whitout .pit file.
what's wrong in my flashing way?
Click to expand...
Click to collapse
.pit file is used to flash the full rom (phone + modem + csc) with re-partition flagged, basically the pit file tells odin where to write the filesystems.
Whenever you have just one file (phone), you don't need either pit or re-partition flag. This last XEN JS5 is a FULL rom.
g00ndu said:
Be careful on updating. Double check the bootloader and Sbl.bin. We don't want the sgs to be locked, like the galaxy tab.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
doublechecked boot.bin (where identical), not sbl.bin though
g00ndu said:
Be careful on updating. Double check the bootloader and Sbl.bin. We don't want the sgs to be locked, like the galaxy tab.
Click to expand...
Click to collapse
You're right !
I still have my DL mode after flashing these files ...
Wendigogo said:
You're right !
I still have my DL mode after flashing these files ...
Click to expand...
Click to collapse
Was Auto Reboot selected? Does Odin show a green success after completition?
Official thread
matticala said:
Was Auto Reboot selected? Does Odin show a green success after completition?
Click to expand...
Click to collapse
Yes for the two questions !
Wendigogo said:
You're right !
I still have my DL mode after flashing these files ...
Click to expand...
Click to collapse
Just for clarify it, Samsung's 'locked' bootloader on Galaxy Tab is not the problem about download mode... The signed bootloader also allow flashing the device later... The problem is just about the files what you can use... With Samsung's signed bootloader you can flash in the future just also signed kernels, you basically you willl not able to flash custom ROM-s in the future... You can flash firmwares with Odin, you can flash Samsung beta firmwares also, just simply could not flash custom ROM-s... This could be big problem or verly small also based on your usage habit. While I use 2.2.1 I simply not use custom ROM-s, but of course before I used... Nowadays 'signed' situations could not break my life with i9000, but with Galaxy Tab it could ... at least in the near future, as it's ROM not as good as the current i9000 versions...
Hi,
eboIa said:
Just for clarify it, Samsung's 'locked' bootloader on Galaxy Tab is not the problem about download mode... The signed bootloader also allow flashing the device later... The problem is just about the files what you can use... With Samsung's signed bootloader you can flash in the future just also signed kernels, you basically you willl not able to flash custom ROM-s in the future... You can flash firmwares with Odin, you can flash Samsung beta firmwares also, just simply could not flash custom ROM-s...
Click to expand...
Click to collapse
Thanks for explaining this ! But I couldn't understand why you couldn't donwgrade to a non-locked bootloader with Odin ? Don't have access to it ? But without access to it it couldn't be modified with latest Samsung FW via Odin ?
Hi
Still not patched to fixed.
for me it is interesting too why it is so messy about downgrade, could someone just wipe bootloader and force flash older back?
when i flash this i cant get the swedish keyboard in my phone
any ideas on this ist this the european ver i reverted back to I9000XWJM5 i kies tells me there is no update
Sorry one is not hiedemell both are odin one is full 3 file package which requires 803 pit file and other is single pda file flashable without pit or repartition from any previous stock rom
Sent from my GT-I9000 using XDA App
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
Hi, i have galaxy tab:
PDA: XWJMG
PHONE: XXJMA
Now i started ODIN 1.7 and selected p1000-mck-r3-ext4-cwm.tar in PDA. I didnt select Re-Partition and did not tick anything and did not select PIT file. Now when i connect it says 'added' and when i click on start it goes through the process and says "failed' in the end. Now my tab shows yellow triangle on it. Help
Do you by any chance have locked bootloaders? Anyway as long as the computer recognizes your tab you can fix it. Just use search.
Sent from my Desire HD using XDA App
Robi-K said:
Do you by any chance have locked bootloaders? Anyway as long as the computer recognizes your tab you can fix it. Just use search.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I dont know about bootloader, its an untouched piece. Please tell me how to fix this tab... :-(
Look at the stickyes in the gsm tab development. Just download a rom that doesn't contain bootloaders and flash it via odin. Again you can find such roms in the development section. Read read and read again and you will be able to fix your tab. One question, why did you flash your tab in the first place?
Sent from my Desire HD using XDA App
Download this firmware http://files.deodexed.com/ModADroid-Galaxy-Tablet/Rotohammer/JME/
Then goto http://forum.xda-developers.com/showthread.php?t=932082 & read the bit where it says if your tab does not boot...
Hope this helps
Mark
You need to dload the P1 hidden pit & full J4 version fw
Is it maybe because the rom you selected says cwm? Isn't that supposed to be flashed in clockwork mod?
Thanks guys for all your help, i flashed pit to my phone via ODIN and piece is alive and working now and gave the tab back to my friend. Now just need to know for the future i have ODIN v1.31 and P1_EUR.pit. I selected pit and P1000JPJJ2 on PDA. Now just need to know before flashing do i need to select repartition?
As i read through the tutorial you only select repartition when you are flashing with the pit file!
If you are installing firmware, Flash the custom kernel that is linked on the same page as the overcome rom 2.13 without partition, Then hold vol up and power will put you in recovery mode, You can flash the rom through there useing the install zip from sdcard option but you must copy the custom rom onto the sd card first....
Regards
Mark
slyevo said:
As i read through the tutorial you only select repartition when you are flashing with the pit file!
If you are installing firmware, Flash the custom kernel that is linked on the same page as the overcome rom 2.13 without partition, Then hold vol up and power will put you in recovery mode, You can flash the rom through there useing the install zip from sdcard option but you must copy the custom rom onto the sd card first....
Regards
Mark
Click to expand...
Click to collapse
Well, i know how to flash custom rom, just wanted to flash the firmware through odin since it seems easier...i downloaded P1000JPJJ2 from the following site and it says no repartition, my problem solved..thanks anyway
http://www.thegalaxytabforum.com/index.php?/topic/112-samsung-galaxy-tab-firmware-list/
i have the same problem like the first post. I am using P1000 for asia (malaysia). now i can do nothing with my tab but odin still able to detect it. anyone could help forward me the link for the said rom without bootloader. the link given in the previous post already dead.
andrew21 said:
Hi, i have galaxy tab:
PDA: XWJMG
PHONE: XXJMA
Now i started ODIN 1.7 and selected p1000-mck-r3-ext4-cwm.tar in PDA. I didnt select Re-Partition and did not tick anything and did not select PIT file. Now when i connect it says 'added' and when i click on start it goes through the process and says "failed' in the end. Now my tab shows yellow triangle on it. Help
Click to expand...
Click to collapse
I had the same problem earlier and then i learned that bootloader for stock JM is signed so it show error ... completion (write) failed ... when you try to upgrade or install custom rom using Odin. I reverted back to resurrect my tab by Odin with pit (follow pit version) and check repartition, auto reboot. It works for me but not sure if it will work for others. Good luck.