I tried to flash a rom and after the phone rebooted it says:
E:Cant mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
Cant start phone or anything (
Reflash
That fails install stock rom via ODIN .
jje
It was some stock rom i installed from samfirmware.com using odin ..
Now no matter what i try i get the same error
BelugaHval said:
It was some stock rom i installed from samfirmware.com using odin ..
Now no matter what i try i get the same error
Click to expand...
Click to collapse
I got this error once, went away when I flashed again with re-partition (this was with the XXJPU ROM on samfirmware.com).
This happened to me, download a bunch of roms and open them look for a dbdata file inside. DON'T extract but once you find it flash that rom, it will work!
Sent from my GT-I9000 using XDA App
it happen to me too, this is how u can fix it: just find the wright CSC and use this stock ROM
http://forum.xda-developers.com/showthread.php?p=9532608#post9532608
BelugaHval said:
I tried to flash a rom and after the phone rebooted it says:
E:Cant mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
Cant start phone or anything (
Click to expand...
Click to collapse
Flash back to an stock Eclair 2.1 ROM like JM8 or JH2
then flash back to stock Froyo 2.2 of your choice
before you boot into the OS
go into Recovery Mode
select Format Internal SD
select wipe data
select wipe cache
select reboot
now it should work like normal
AllGamer said:
Flash back to an stock Eclair 2.1 ROM like JM8 or JH2
then flash back to stock Froyo 2.2 of your choice
before you boot into the OS
go into Recovery Mode
select Format Internal SD
select wipe data
select wipe cache
select reboot
now it should work like normal
Click to expand...
Click to collapse
To the OP, I'm +1 this reco. All other suggestions are typically variations of this but this is the most straight forward and complete.
It happen to me, I just had to find the right CSC, flash Eclair, then the custom ROM
Related
Hi
I recently got my phone back from repair (damaged screen). Phone came completaly wiped as you can imagine but before it was sent away it was running on OCLF 2.0 by Ryanza...After I got it back ive noticed that there were some problems like notification bar got stuck, appz were very laggy etc..
I came to the conclusion that this is because of some partition corruption or sth.
I tried to update firmware via Odin but whatever i try it always fails before installing giving me that in the recovery mode:
E:Can't mount /dev/block/stl10
(invalid argument)
E:copy_dbdata_medua:Can't mount DBDATA:
I tried different Froyo version but it always downloads firmware from pc and fails just after that...(through Odin)
Recovery mode (3e) still works but i worry my partition structure may be damaged ...
Is there something else i can do to fix it??
Appreciate every help You can give me.
Try an eclair firmware and check repartition in odin. There are a bunch of threads in the q&a forum. Search for your error msg.
its very important that you use all 3 files, with repartition ticked, to get rid of these errors
I tried to repartition with both checked and unchecked....but will try to use eclair ...does using phone(modem) makes any difference?
managed to fix the problem flashing old JPC with 512 pit ...thx for help guys..appreciate it.
Using Odin to flash I9000XXJPY. Odin finishes correctly and the phone restarts and goes into the recovery screen. I get two error messages.
Message 1:
update media, please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBATA:
Message 2:
your storage not prepared yet, please use UI me nu for format and reboot actions.
copy default media content failed.
If I reboot system it gets stuck on the logo screen.
Sounds to me like the first step would be to reflash the ROM and see if that solves it.
If you still have the same trouble, flash a recovery ROM such as your original stock ROM or Darky's Resurrection and go from there.
Of course, more technically minded types here will likely have better/more complete advice.
Good luck
rschenck said:
Sounds to me like the first step would be to reflash the ROM and see if that solves it.
If you still have the same trouble, flash a recovery ROM such as your original stock ROM or Darky's Resurrection and go from there.
Of course, more technically minded types here will likely have better/more complete advice.
Good luck
Click to expand...
Click to collapse
Tried that several times and didn't work. Any other tips.
Flash a stock 2.1 rom using 3 files plus pit file and repartition ticked. I'd format the internal sd and do another factory restore then to make the phone as clean as possible before re flashing jpy. If using 3 files use pit file with repartition ticked. If one file skip pit and ensure repartition is un ticked. I've done this loads of times to get back to stock rom after custom roms. Good luck, hope this helps
Sent from my GT-I9000 using XDA App
Flash JPU first with repartition ticked using 512.pit, then flash the JPY you have without repartition. JPU also has the 3-button activated bootloaders and works great... no need to go back to 2.1, imho.
Im having this same issue and flashed many combos but still not working.
It seems the int sd is not formatted correctly and wont mount.
Tyxerakias said:
Flash JPU first with repartition ticked using 512.pit, then flash the JPY you have without repartition. JPU also has the 3-button activated bootloaders and works great... no need to go back to 2.1, imho.
Click to expand...
Click to collapse
Yeah you can do that too. It doesn't really matter which you flash to as long as it's the 3 files with pit and repartition. It's only a base rom to enable you to get the phone clean and to flash over again
Sent from my GTI9000 using XDA App, Froyo 2.2.1, Darky's v9.3, Voodoo 5.4.1, ADW launcher + gingerbread theme
Use Odin 1.7 from my signature.
Which Firmware you ON & what did you flash?
Hi!
I've been using CM9 nightly's since some days ago, but when I updated to the version of the day 19, it began with FC until that this morning, it reboot suddenly and it hasn't boot again.
I suppose that if i reflash the XXJW4, so i've tried it but, when it tries to boot, it boots on recovery and gives the following errors:
E: copy_dbdata_media: Can't mount /dbdata
your storage not prepared yet. please use UI men u for format and reboot actions.
Meida files copy failed
---Deleting files
E: failed to mount /dbdata (File exists)
E: delete_data_files: Can't mount /dbdata
your storage not prepared yet. please use UI men u for format and reboot actions.
Meida files copy failed
----Updating filesystem....
E: failed _filesystem_for_rfs:can't mount /dbdata
Of course, it doesn't boot now.
Any solution? Thanks a lot!
I had similar problem and I had to do full cycle
restore from recovery also was giving me bootloop
1. flash stock gingerbread rom
2. flash CF-Root (corresponding with ROM)
3. install CM9 from recovery (wipe data and cache).
If you still can go to the download mod, try to flash a ginger stock rom.
Sent from my GT-I9000 using XDA Premium App
Look to the message of Tyxerakias 29th March 2012, 02:25 PM in Galaxy S9000 General.
[ROM] I9000XXJW4 (2.3.6) [19.03.2012][ValuePack Firmware] (in General)
--------------------------------------------------------
Tyxerakias 29th March 2012, 02:25 PM
# 77To those of you who get bootloops after flashing:
Go into download mode, and flash this, via odin, after you unzip it. (i.e. flash the .tar file, as usual - not the zip).
dbdata.tar
Cheers
Explanation: The bootloops are caused because the dbdata file is missing from the rom (it's just a Kies upgrade, not a full rom), and you probably ticked repartition when flashing.
nope.
in my case repartitioning was not checked, because I'm having a bootloop after flashing kernel, updatet rom, ... from CWM, so there is no option to repartition.
Those recovery fixes never worked for me, but maybe authors case is easier.
finally i have fixed it flashing a stock rom (JVU), XXJW4, root, CM9 and that is! thank you everybody!
Yes. Me too.
But... I've had boot-loop like 8 times now. It's irritating I have to flash stock, CM9, slim-ics every time. even worse I don't know what causes the boot-loop. Tooday I just rebooted to CWM, cleaned dalvik-cache and cache and my phone didn't start any more. I was on semaphore 1.0.0s kernel.
Now I'll try stock slimICS kernel and we'll see...
i tried to wipe date by android recovery system and from then my note cant boot, i cant access clockworkmod but i cant restore from a nadroid backup , its says error while mounting /system... any help???
also on the startup i got a message
applied the csc-code : XEU
Successfully applied mmulti-csc
e:failed to mount /data (Invalid argument)
e:copy_log_files_to_data :: can't mount /data
mesiah said:
i tried to wipe date by android recovery system and from then my note cant boot, i cant access clockworkmod but i cant restore from a nadroid backup , its says error while mounting /system... any help???
also on the startup i got a message
applied the csc-code : XEU
Successfully applied mmulti-csc
e:failed to mount /data (Invalid argument)
e:copy_log_files_to_data :: can't mount /data
Click to expand...
Click to collapse
mesiah, you have the correct nick....you haven´t read about the Hardbrick bug, have u??...You are not supposed to wipe running an ICS kernel...read this:
http://forum.xda-developers.com/showthread.php?t=1633943
try using odin to flash back to stock GB...but if you get stuck in the NAND WRITE part...I have bad news for u.
i tried it but nothing, also i tried to install a rom that i have stored in my sd, it started but it stuck in 57% of the installation... do you have any explain ??``
i tried it again and it stuck on 80%
mesiah said:
i tried it but nothing, also i tried to install a rom that i have stored in my sd, it started but it stuck in 57% of the installation... do you have any explain ??``
i tried it again and it stuck on 80%
Click to expand...
Click to collapse
You are probably hardbricked for wiping in ICS....read the post I sent u.
when i open the device it stucks in samsung logo as i have read in this guide http://forum.xda-developers.com/showthread.php?t=1656635 this is a soft brick as i understand??? i confused ... what options i have???
mesiah said:
when i open the device it stucks in samsung logo as i have read in this guide http://forum.xda-developers.com/showthread.php?t=1656635 this is a soft brick as i understand??? i confused ... what options i have???
Click to expand...
Click to collapse
mesiah...I have already told u...flash a stock GB firmware with ODIN PC....if you get stuck there, then u are hardbricked...
glevitan said:
mesiah...I have already told u...flash a stock GB firmware with ODIN PC....if you get stuck there, then u are hardbricked...
Click to expand...
Click to collapse
can samsung fix it?
mesiah said:
can samsung fix it?
Click to expand...
Click to collapse
If it's hardbrick and you are under warranty, then you will have to use your warranty and they will either replace your phone or give you a new motherboard.
so do you know the cost?? i have one more samsung galaxy note with a dangerous kernel , what i have to do ?
read the stickies in the forum. they really describe the problem in detail.
Hi, i flashed my phone with custom rom and my phone keep restarting everytime i started it. And i cant use recovery (twrp) because it restarts in recovery mode too, it can go only in download mode.. please tell me its not hard brick that cant be fixed in software. Thanks
Well if it only restarts in download mode the only thing you can do is to return to stock. Download the latest firmware of your device variant and flash it via Odin. I suggest you to flash a lollipop one and then update to Marshmallow if you want.
kuntlsx said:
Hi, i flashed my phone with custom rom and my phone keep restarting everytime i started it. And i cant use recovery (twrp) because it restarts in recovery mode too, it can go only in download mode.. please tell me its not hard brick that cant be fixed in software. Thanks
Click to expand...
Click to collapse
Yo!
First, calm down because its not hard brick You can fix it and its quite easy.
Follow these steps:
1) Download and install the proper DRIVERS for your phone (it should be done automatically when you connect the phone to the PC).
2) The phone should have at least 50% battery!
3) Download ODIN program. I'm using v3.09
4) Download the stock rom for J500FN from here: MEDIAFIRE <--- click . This is a firmware which i have uploaded in past, for faster download and is based on 5.1.1 lollipop.
If you want other firmware, then check on SAMMOBILE or other website.
You can use SamFirm to download firmwares faster: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 (even if says deprecated, it works fine).
5) Extract ODIN archive and run it (.exe file).
6) Extract the stock rom .zip archive and you will get a xxxxxxxxxxxxxxxx.tar.md5 file (xxxxxxxxxx= name of the stock rom)
7) Restart the phone in DOWNLOAD MODE, by holding Power + Home + Volume down buttons same time.
A "Warning" window will apear, now press the "vol up" button to get "DOWNLOAD MODE" and conect the phone to the pc
If the ODIN see the phone, on the "ID:COM"line(midle-left) you will see "0:[COMx]"(x= port number)
8) On the ODIN press "AP" button, a window will apear, search in it the location of the xxxxxxxxxxxxxx.tar.md5, select it and open.
9) Now press "START" button and wait until ODIN finish.
When it finish, the phone will boot automatically and in ODIN will apear a big green PASS.
10) Phone is booting. Yayyy!
Click to expand...
Click to collapse
Here is a Q&A (questions and answers) thread with useful and basic informations: http://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-qa-thread-galaxy-j5-series-t3382922 .
#Henkate said:
Yo!
First, calm down because its not hard brick You can fix it and its quite easy.
Follow these steps:
Here is a Q&A (questions and answers) thread with useful and basic informations: http://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-qa-thread-galaxy-j5-series-t3382922 .
Click to expand...
Click to collapse
I just tried that and now im stuck on Samsung logo loop
kuntlsx said:
I just tried that and now im stuck on Samsung logo loop
Click to expand...
Click to collapse
Now flash TWRP and go to recovery and wipe data, cache and dalvik cache. Then the bootloop should be gone.
If you still have a bootloop after doing this, then try to reflash the stock rom.
#Henkate said:
Now flash TWRP and go to recovery and wipe data, cache and dalvik cache. Then the bootloop should be gone.
If you still have a bootloop after doing this, then try to reflash the stock rom.
Click to expand...
Click to collapse
Just got this when tried to wipe
E:Unable to mount storage.
E:Unable to mount '/data'
kuntlsx said:
Just got this when tried to wipe
E:Unable to mount storage.
E:Unable to mount '/data'
Click to expand...
Click to collapse
Huh. Try to mount them at Mount option in recovery.
#Henkate said:
Huh. Try to mount them at Mount option in recovery.
Click to expand...
Click to collapse
I got same error, i cant check checkbox for /data
Unable to mount '/data'
kuntlsx said:
I got same error, i cant check checkbox for /data
Unable to mount '/data'
Click to expand...
Click to collapse
Then reflash stock rom and reboot. If you get bootloop, go to recovery ( STOCK recovery) and wipe data and cache, but keep in mind that when you are wiping data, it may wipe the whole internal memory, not just data. It happened to me on some newer firmware. And then reboot again.
#Henkate said:
Then reflash stock rom and reboot. If you get bootloop, go to recovery ( STOCK recovery) and wipe data and cache, but keep in mind that when you are wiping data, it may wipe the whole internal memory, not just data. It happened to me on some newer firmware. And then reboot again.
Click to expand...
Click to collapse
Thank u so much, it works! :highfive::highfive: