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
my i9000 got stuck in galaxy gt i90000 logo....
how to boot it again with diferent rom.......
it can get in to downloade mode......
need help and steps to flash a rom i am from india ........
You can find instructions on www.samfirmware.com. Just go to the rom download page. You will need to create an account first.
Anyway, it's quite straight forward. Open Odin, plug your phone into your PC with download mode on. Put the pit file in pit, the pda file in pda, phone in phone and csc in csc. (Some roms only have a single file instead of 3. That means the phone and csc is combined with pda, so just put that in pda). Leave partition unchecked. Flash.
snapper.fishes said:
You can find instructions on www.samfirmware.com. Just go to the rom download page. You will need to create an account first.
Anyway, it's quite straight forward. Open Odin, plug your phone into your PC with download mode on. Put the pit file in pit, the pda file in pda, phone in phone and csc in csc. (Some roms only have a single file instead of 3. That means the phone and csc is combined with pda, so just put that in pda). Leave partition unchecked. Flash.
Click to expand...
Click to collapse
actualy i tried to flash this stock firmware I9000DXJPE
after this only it got stuck ther..........
all the steps u told where done
but i will try the site you told thanks for the responce dude............
snapper.fishes said:
You can find instructions on www.samfirmware.com. Just go to the rom download page. You will need to create an account first.
Anyway, it's quite straight forward. Open Odin, plug your phone into your PC with download mode on. Put the pit file in pit, the pda file in pda, phone in phone and csc in csc. (Some roms only have a single file instead of 3. That means the phone and csc is combined with pda, so just put that in pda). Leave partition unchecked. Flash.
Click to expand...
Click to collapse
done it still the same pls help..................................
you must be doing something wrong... if download mode works then it should be able to flash a ROM. try this http://forum.xda-developers.com/showthread.php?p=10860237
Hi,
Trying to unbrick my phone is driving my mind totally mad!
So far I have tried installing several CF roots with ODIN and tried to reflash the ROM with I9000XWJS3. All of them lead to no success, just a black screen and the phone vibrates every 10 seconds.
Trying to find information on this forum is easy.. but trying to put all those pieces of information together is somewhat impossible for me.
I am from the Netherlands and bought this SGS 2nd hand from someone who has rooted it. However I have no idea how that person has done that with which piece of software. I also have no idea what build number it currently has. However I do know there is no sim-lock, because the owner bought it from the KPN telecom provider and has no problems using a sim-card from T-mobile.
I am able to get into the download mode (3 button combo thingy) and Odin can successfully flash the ROM of my SGS.
Now what I need to know is which PIT, ROM, CSC, Modem files etc. I need to make this phone working again. Preferably I'd like to run it on Froyo 2.2.1 with Android market installed.
try downloading the firmwares from samfirmwares.com
http://forum.xda-developers.com/showthread.php?t=846913 download the firmware from here. preferably JM8 flash that thru odin with PIT and REPARTITION and that should do the trick. then you can flash over a new rom like JPY (2.2.1)
I've successfully unbricked my Galaxy with the 'Froyo ROM that does not brick' here - "h t t p://w w w.4shared.com/file/dJiyRz3v/EUGENE373_SamsungS_Froyo_PDA.html" (Can't post as actual link because I'm not allowed to yet, just copy and paste the bit between the speech marks into a new window and remove the spaces).
As per previous poster's instructions; flash through Odin as PDA with PIT and REPARTITION (Original instructions for this ROM said not to use repartition but that didn't work for me)
You should then be able to Odin flash any new rom you like, but when you do DON'T use REPARTITION or PIT, otherwise your phone will just get bricked again.
I feel that flashing the firmwares which needs partition is safer and better than those that isn't....for my case I prefer flashing JPU than JPY or JPX...it works every time I got my phone semi-bricked, hehe...
Hello,
Yesterday i had similar problem ater trying to flash Darky's resurrection edition.
After the boot i had a black screen just like you.
Here's how i finally unbricked:
Download
- PIT 803 file multiupload.com/6JX2LEUCTY
- I9000XWJS3 pakcage from samfirmware.com (european for my case), PIT803 version : hotfile.com/dl/100247999/301207f/I9000_XEN_I9000XWJS3.rar.html
(The pwd is samfirmware.com)
The package I9000 XEN I9000XWJS3 contains 3 file (which i think is the key, trying to repartition with only one PDA file seem to soft brick the phone)
In Odin, tick repartition, for PIT select the PIT 803 file
For PDA, choose I9000XWJS3-REV03-ALL-low-CL830616.tar.md5
For CSC, choose GT-I9000-CSC-XENJS3.tar.md5
For PHONE, choose MODEM_I9000XXJPY.tar.md5
After the flash, your phone will reboot in rescue, unplug it and do a wipe/factory reset, then reboot and you should be ok.
The goal was only to unbrick my phone, but i'm totally happy with this firmware for now, my phone is a lot faster than before, and i don't feel the need of a lagfix anymore!!
Please note that this is just my experience, and you should wait for more advanced users help.
I wanna know if you can help me, ...
I was on sprint gtab stock rom DJ30 which updated to EA24 and EB28. Data service worked very well. Then I flashed voodoo CWM in order to install Honeycomb rom. Then install the rom via CWM. The installation was indeed finished, but it stucked in samsung logo boot. I turned off device and boot in cwm mode. Sure, it was HC rom's CWM. But it couldnt mount system, Seems the convertion to ext4 didnt work. Worse thing it couldnt mount sdcard either. So I couldnt reinstall the rom. I also couldnt reboot, so i had to long press the power button.
Stop trying installing HC rom on my device, i decided to revert back to stock rom (DJ30>EA24). But it was weird, i cant revert to stock rom with modem.bin inside the package. It always stuck in modem.bin when flashed with odin. But, when i use the package with no modem, it can flashed succesfully. I had flashed that stock rom (with modem.bin) million times without fail, but now always fail.
Yeah, my gtab is running but without modem.bin so no signal and i cant use data services. Like wifi only tab.
Many ways i've tried:
- I've tried flashed DJ30 with no modem first. Okay, it is successful. But when flash with EA24 (with modem) it stuck on modem.bin.
- I've tried flashed DJ30 with modem.bin. And it also stucked on modem.bin. Trying flashed EA24 without modem.bin, it is succesful.
- Try using heimdall. Progress 100% but it wont reboot. But when i retry n uncheck modem. Flashing work flawlesly.
- Try using odin modem only flash. Progress bar is full but it wont reboot.
- Try flashing via CWM, but still no luck.
Weird, huh. Seems my gtab cannot use modem.bin anymore.
Any clue? Thanks before ...
I'd appreciate if you can help me flashing modem.bin to my device. Or it end up with wifi only tab.
EDIT: even OTA update, stuck on "verifying modem ... updating modem ..."
I would like to bump this as I am having the same issues also. I am flashing my Sprint Galaxy Tab to EA24, and it is held up at modem.bin.
I posted a question on this, and am hoping that someone helps us.
Thanks in advance,
Claud
try re-partition and flash pit by using odin,i suffered the same issue with my vzw tab
depending on which file you're using to restore. You need to use the .tar.md5 file from the EA24 flasher and rename it to just .tar, then flash with Odin. I've flashed this several times and it gets past modem.bin just fine. If you are using the 2 files 1 with modem (Epic 4g modem) and 1 without modem you're not using the right files. I ran into the same issue with the with/without modem files. Here's a link to the EA24 flasher and the .tar.md5 file you need to go back to stock.
http://www.multiupload.com/LXQKGX5RHL
Bumping this to avoid making a new thread.
I've done many reverts back to stock from different ROMs, but this past time coming from BTL or HC (Sprint Tab btw) I'm also getting hung up on modem.bin. Never had a problem here before, so not sure what's going on.
I didn't use a pit and only had reboot checked and it worked fine.
I've never included pit. I've just always put SPH-P100.EA24.SECURE.REV07-FULL_CL871413.tar in the PDA slot and let it go through. And tried checking re-partition, but it does not go through that way.
Maniken50 said:
I've never included pit. I've just always put SPH-P100.EA24.SECURE.REV07-FULL_CL871413.tar in the PDA slot and let it go through. And tried checking re-partition, but it does not go through that way.
Click to expand...
Click to collapse
Pretty sure if you try to re-partition, you have to have the correct pit file for it to know the right places to recreate the partition table. If you're just flashing back to stock, there's no need for the pit file.
pvtjoker42 said:
Pretty sure if you try to re-partition, you have to have the correct pit file for it to know the right places to recreate the partition table. If you're just flashing back to stock, there's no need for the pit file.
Click to expand...
Click to collapse
That's what I thought and never had a need for it. Guess I do now. Think it would even work?
Maniken50 said:
That's what I thought and never had a need for it. Guess I do now. Think it would even work?
Click to expand...
Click to collapse
I've never had to repartition a device, but i've read about it working for people to bring them back from boot looping etc. If somehow the partition table gets corrupted etc. If you're already soft bricked, there's no harm in trying.
Having the same issue, trying to go from Rooted GB to BTL then back to GB or EA24
Hi,
I am having the same issues, does anyone have the .PIT file available by any chance, all of the packcages that I have downloaded for the sprint tab seem to not have any pit included...
ezitec said:
Hi,
I am having the same issues, does anyone have the .PIT file available by any chance, all of the packcages that I have downloaded for the sprint tab seem to not have any pit included...
Click to expand...
Click to collapse
http://www.mediafire.com/?jb40cs460rf8aq7
Try that one.
I have the same problem with a Verizon Galaxy Tab. The archive modem.bin lock in 100% via Heimdall. Someone conseguiui solve this problem?
mbanton said:
I have the same problem with a Verizon Galaxy Tab. The archive modem.bin lock in 100% via Heimdall. Someone conseguiui solve this problem?
Click to expand...
Click to collapse
You need to look at one of the stock VZW threads and find the files you need there, as the sprint modem will make things worse for you. Not sure if the pit files are the same or not between the sprint and VZW tabs..
pvtjoker42 said:
You need to look at one of the stock VZW threads and find the files you need there, as the sprint modem will make things worse for you. Not sure if the pit files are the same or not between the sprint and VZW tabs..
Click to expand...
Click to collapse
I have the correct files for the tab for Verizon. I have the original files Following: Sbl.bin boot.bin cache.rfs dbdata.rfs efs.rfs factoryfs.rfs ldb.db modem.bin param.lfs param.rfs pit.pit zImage
But my problem is how to record using that pit. What other files should I use a recording that will restore the partition table?
I fear that a problem occurs with even higher tab.
I am having this issue as well, and I'm also coming from HC and on Sprint. I have no trouble flashing any kernel/rom of my choosing EXCEPT for the modem.
At this point, I'm just trying to reflash it back to stock. I've got the Sprint EA24 files, including the pit (tried with and without) but it refuses to flash the modem. If I omit the modem, it flashes perfectly fine and I'm left with a bone stock tab with no modem.
Is there anyone here who went to HC and then managed to go back? As stated by others, I've gone back to stock before without issue. The HC build seems to be what caused this problem
I ran spacemoose's HC port for a day or 2 and then went back to stock until the official GB came out. I've had no issues flashing the whole EA24, or any other updates.. with and without the modem..
Hmmmm. Maybe different hardware revisions? You have any suggestions? I'm completely out of ideas and it's of little use to me without 3G.
I just did a flash back to complete stock (including modem) 2 days ago, and it didn't hesitate once while flashing everything with Heimdall. Only thing I can say is keep trying.
At this point, I've attempted to flash it no less than a dozen times and still can't get the modem to flash. I'm completely baffled as to why it won't accept it.
I rooted my phone and wanted to flash back to stock so I can update with the OTA and re-root, but I downloaded the zip for the AT&T tar files and everything seemed to pass MD5 checks and went okay, but as soon as I hit Start, the program just continues to say NAND Write Start for over 20 minutes, and won't flash, how do I go about re-trying this without bricking my device? It's still plugged in atm in download mode.
What version of Odin are you using? I had this problem because I had v3.10 and the s6 is not compatible with that version, you have to have v3.10.6.
Mine did that, I closed odin, reopened, put each .md5 file in right section (AP in AP, BL in BL, CSC in CSC, ect) and it worked
If Odin is having trouble flashing to your phone. Here is some simply tips and tricks to try.
1. Try flashing everything except for the bootloader .
2. Try running Odin as admin.
3. Try upgrading to the newest Odin available.
4. If all else fails, open Samsung Kies, and go to emergency recovery, put your model # and serial # in, and it will flash your phone to stock for you, then you can try again.
5. Also make sure all of the correct drivers are installed for your phone, sometimes Windows can be bad about that. Try getting drivers from samsung directly.
6. Try a new USB Cable, as crazy as that is, I have had some not work, and others work fine.
7. Try a different USB Port on the PC, or restart the PC.
I hope this helps.
I tried just flashing the ROM and CSC and it flashed just fine, I left out the CP file, what is that? Everything seems fine just flashing the ROM and CSC, but do I need to flash the CP file too, for anything?
CSC is the consumer software customization and is specific to geographical region and carriers. It contains the software packages specific to that region, carrier branding and also APN settings for data connection, MMS etc for your service provider.
I hope this helps
I didnt get it. Do you mean to put each .md5 file in all sections? ? Please help me
_Dennis_ said:
Mine did that, I closed odin, reopened, put each .md5 file in right section (AP in AP, BL in BL, CSC in CSC, ect) and it worked
Click to expand...
Click to collapse
Please help me out. I am having same problem NAND WRITE stuck.
Solved
Thanks everyone for your post. But what I did is, just downloaded the Odin v3.10.6......that worked with S6. And I guess S6 is not compatible to other earlier versions of odin. So better try with Odin v3.10.6.
Nand write start fail solved
I have solved using Odin3 v3.10.7 with firmware VZW-G920VVRU4BOK7-20151211140939 and Windows 7 for Galaxy S6 SM-G920V
NAND stucked
kishor1995 said:
Thanks everyone for your post. But what I did is, just downloaded the Odin v3.10.6......that worked with S6. And I guess S6 is not compatible to other earlier versions of odin. So better try with Odin v3.10.6.
Click to expand...
Click to collapse
can u tell the steps u did? to do it
Help
I am having the same issue and I have done everything suggested here but still is NAND fail. Any ideas
bonniegertz said:
I am having the same issue and I have done everything suggested here but still is NAND fail. Any ideas
Click to expand...
Click to collapse
Were you finally able to get it to work?
Its working!
Zoide_ said:
Were you finally able to get it to work?
Click to expand...
Click to collapse
Yes, I gave up but a friend of mine found a thread that talks about using Kies to bring it back to factory default. You need to know the serial # and IMEI # If you can find this information, you can reset it using Kies.
Had the same problem. Used Odin 3.10.6
But before all this, I connected phone with debugging enabled in windows and authorized it, the problem never resurfaced