Database Develop

[Q] e:can´t mount /dev/block/st110

Hi! I have flashed my phone many times and it have worked fine but this time i tried to update to xwjm7 and everything flashed ok but when it try to start after flash i can read this:
update media, please wait...
E:Cant mout /dev/block/st110
(invalid argument)
E:copy_dbdata_media:cant mount DBDATA:
copy default media conent failed.
i have tried factoryreset then it starts to the samsung S logo but after that the screen is black.
please help me
/regards
andreas

I had similar problems. Try flashing a new CSC, MODEM and PDA. Using a different CSC is probably what worked for me.

Which firmware did you use?
I downloaded the
GT-I9000_I9000XWJM8
but cant seem to get the flashing to work, And there are many files to choose from

I had same problem when flashing JM8.
I skipped the PIT with tick repartition in the first place.
Did you use OCLF in your previous firmware ?
I then followed all steps correctly and all went fine.

So what was the solution for this. Ive tried flashing the original ROM back but it keeps giving me the same error. Ive tried repartioning, not repartioning, pit 512, different ROMS. Im stuck in this loop. Can someone please try to help me out?
EDIT: fixed. Flashed JM8 with .512 repart, then flashed with the Telstra DVJH3 ROM. Back to stock.

Same problem with a mexican Galaxy S.
Solution:
1) Flash JM8 with 512 repart. Note, Result: phone doesnot work at first boot, but at least try to load, discard error and enter in Download Mode
2) Flash JPM with out repart, Result: working phone with Android 2.1
3) Flash JPY with out repart, Result: working phone with Android 2.2.1
Result: Galaxy S with Working Froyo again!!
Thanks you all for sharing.

No need. Just flash stock XXJPU ROM... it's all you need since DBDATA is broken and that firmware contains the file, which isn't in most others...

go to my profile. and look for a thread called my trick to unbricking a soft brick or sonething download the file dbdata.rfs.tar and flash without a pit in odin
Sent from my GT-I9000 using XDA App

[Q] Failed Installation with Darky's 5.2

Okay, the more I try the more I think my phone is hosed. I don't understand what went wrong but something did, and it is seemingly impossible to fix. (I'm on Bell if it matters any)
So, I tried to install Darky's 5.2 ROM yesterday. All was going well. I got JPU installed fine and it booted perfectly. The next step was to flash CFRoot with Odin.
Upon flashing CFRoot, my phone started to loop the Galaxy S GT I9000 screen (the one before the boot screen)
It would not stop looping this screen. So I tried to flash back to JPU, no luck. Same looping.
I flashed to JH2 & JM8. Instead of looping the screen, it goes into recovery. I get the following in red text:
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:copy default media content failed.
E:Can't mount /dev/block/stl11
(Invalid Argument)
E:Can't mount /dev/block/stl11
(Invalid Argument)
Now I'm at a loss for what to do. Every 2.1 firmware yields the same problems at the recovery menu. Every 2.2 firmware loops the Galaxy S screen (screen before bootscreen)
I've flashed to JPU multiple times, flashed to JP6 multiple times. I've tried different kernels (super optimized and Voodoo) and all give the same results. Nothing is working.
What can I do? Is my phone dead?
EDIT: Looks like my phone is dead.... Internal SD card killed itself.
Off to the Bell store I go....

Andrewwelton said:
Okay, the more I try the more I think my phone is hosed. I don't understand what went wrong but something did, and it is seemingly impossible to fix. (I'm on Bell if it matters any)
So, I tried to install Darky's 5.2 ROM yesterday. All was going well. I got JPU installed fine and it booted perfectly. The next step was to flash CFRoot with Odin.
Upon flashing CFRoot, my phone started to loop the Galaxy S GT I9000 screen (the one before the boot screen)
It would not stop looping this screen. So I tried to flash back to JPU, no luck. Same looping.
I flashed to JH2 & JM8. Instead of looping the screen, it goes into recovery. I get the following in red text:
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:copy default media content failed.
E:Can't mount /dev/block/stl11
(Invalid Argument)
E:Can't mount /dev/block/stl11
(Invalid Argument)
Now I'm at a loss for what to do. Every 2.1 firmware yields the same problems at the recovery menu. Every 2.2 firmware loops the Galaxy S screen (screen before bootscreen)
I've flashed to JPU multiple times, flashed to JP6 multiple times. I've tried different kernels (super optimized and Voodoo) and all give the same results. Nothing is working.
What can I do? Is my phone dead?
EDIT: Looks like my phone is dead.... Internal SD card killed itself.
Off to the Bell store I go....
Click to expand...
Click to collapse
Well, I did the same as I was foolish enough to install a wrong Kernel from CF-root thread. Did you download the right Kernel for your ROM? (JPU)
Its just a matter of download the right Kernel but flashing Darjy's ROM makes it slightly complicated as it has a Voodoo Kernel. You need to flash a stock Froyo using Odin with repartition enabled. Then move on to Custom ROM.
Hope this helps.

CF-Root caused me the same problem!!!
I think this might be causing Bell cards to die.
I can't seem to fix this... I've tried repart. with 512 pit and the three JM9 files.. I've tried JPU, JK3, JH2... exact same results.
Any suggestions?
I tried to flash stock JPU, then CF-Root... to install Doc's ROM... but after I flashed CF-Root, got the same problem.

slaman said:
CF-Root caused me the same problem!!!
I think this might be causing Bell cards to die.
I can't seem to fix this... I've tried repart. with 512 pit and the three JM9 files.. I've tried JPU, JK3, JH2... exact same results.
Any suggestions?
I tried to flash stock JPU, then CF-Root... to install Doc's ROM... but after I flashed CF-Root, got the same problem.
Click to expand...
Click to collapse
Are you sure you are using the right Kernel? All the firmwares have different root kernels. And also, I hope you are putting the CF-root file to PDA, without repartition ticked.

[Q] Galaxy Tab seems to be bricked (soft)

Now first, I would like to make it clear that I can still charge the Tab (batt icon still showing).
This all started when 2 weeks after installing Overcome 1.2.1 with a 2.0.1 kernel, I started getting random process errors onscreen. It got to the point where "process com.android.com" was force closing, rendering the phone unusable. I decided to flash the ROM to ROTO's JMI (Wipe). The phone boots but the errors were still there, as if they weren't wiped at all. Long story short, I went back and forth with a couple of ROMS that I have (even my stock JK1) and then it started booting straight to recovery and showing this:
verifying the filesystem. please wait.
verified the updated filesystem. finished
-- Wiping cache. . .
Formatting CACHE. . .
update application. please wait
E:Can't mount /dev/block/mmcblk0p2
(Invalid argument)
E:install_application_for_customer:Can't mount DATA:
your storage not prepared yet. please use UI menu for format and reboot actions.
copy application failed.
-- Applying Muti-CSC. . .
Installing Muti-CSC
multicsc : src /system/csc/XEU/system/ .
Anyone who can lend their ideas on how I can get the Tab back will be much appreciated.

i had restore my tab to the stock firmware one week ago very easy:
-download the JMI (i have european tab version) from here
-unzipped and flash via Odin3_v1.7 with PIT file according with my screenshoot!

I'll try that one. Thanks!

Tried the above suggest by ovigt71 and now I am stuck at the glowing Samsung boot screen.

You will need to get the tab into download mode and flash a new rom/kernel with odin or heimdal.
Sent from my "way better than an iPad" tab.

Merkez said:
Tried the above suggest by ovigt71 and now I am stuck at the glowing Samsung boot screen.
Click to expand...
Click to collapse
Have you tried JMI or JMK? with JMI has to work! I already did that two times and works like a charm. I reverted from Overcome 1.2.0.....With JMK I didn't try yet. I come back to Overcome because is more faster! I'll try today to revert to JMK...just for testing ! you should try one more time! Flash with PIT file via Odin, but get this Pit file as per attachment, not the one which is coming with Odin !!! seems to work better!

Hi! Yeah, i tried that too. First with a Euro pit, and then that P1 pit. Didn't work either. I might have to bite the bullet and bring this in to the local Samsung repair center.

[Q] Plz HELP!!! Galaxy S not Booting

I tried using Rynza's lagfix on galaxy I9000 running on 2.2. once done, the phone restarted but never came back. every time I see a black screen after the silver Samsung logo disappears. Tried re-flashing with the same rom i was having before, using ODIN. but the same issue persists.
please help. I think I bricked the phone....

if you can get it into download mode still youll be ok, as you can reflash the stock rom and try the lagfix again

you should try to flash xxjpu from samfirmware.com and pit.512 included and make sure that you tick "repartition"
hope it's going to help you

I was running I9000DDJP6. Once the boot screwed up, i re-flashed with I9000DDJP6 and I9000BVJJPD. both r froyo. As suggested, I shall try with xxjpu
I am using Odin 3 V1.3, what are the options should i choose? I mean apart from re-partition?
The phone is still keeps on vibrating with a black screen

Now when I flashed it...i got this error
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
Any idea how do i fix it?

Try fresh flash. 2.1 eclair with 512.pit. After that new firmware via odin.

do i need to re-partition?

guys the issue is fixed....my phone is back online.....thanks all of you....and special thanks to trustsyzaa....i flashed with xxjpu and its on again!!! CHEERS

Repairing the A6 after installing unsuitable recovery.tar

#1# I have a Samsung A6 Tab [SM-T580 Series] and unfortunately i installed a wrong custom recovery with Odin, because i forgot looking and the number.
Afterwards my Tab bricked. Download mode is still operational!
#2# The best advice i could find afterwards was to install a stock rom.
However i can't find either the correct stock rom or the correct twrp.tar.
#3# The problem arrived after i renamed twrp.tar to recovery.tar, because flashing or installing by first trying didn't work.
The XDA-Link to supported devices shows me only TWRP for A 10.1, A 9.7 and A8. That's why i am in a state of desperation.
My Questions so far are: Would replacing recovery.tar with the correct custom recovery or the original recovery by using Odin unbrick the Tab?
If not, where i may find the correct stock rom?

dontdropme said:
#1# I have a Samsung A6 Tab [SM-T580 Series] and unfortunately i installed a wrong 10.1, A 9.7 and A8. That's why i am in a state of desperation.
My Questions so far are: Would replacing recovery.tar with the correct custom recovery or the original recovery by using Odin unbrick the Tab?
If not, where i may find the correct stock rom?
Click to expand...
Click to collapse
flashing stock mostly solve problems. i don't know what you type during searching, but when i googling "SM-T580" there r so many sites provide your firmware (sammobile, samsung-firmware.org). From MM (6) until android 7 and 7.1 available and you unable to find it?
top brand like sams*ng it is not hard to find any firmware or whatever related to i think

Thanks for answering, you are right. Sammobile has the firmware i need. I found it. However, i still would like to know if an official TWRP exists for my device, just for the future, if i would need the possibility to backup or restore files.

dontdropme said:
Thanks for answering, you are right. Sammobile has the firmware i need. I found it. However, i still would like to know if an official TWRP exists for my device, just for the future, if i would need the possibility to backup or restore files.
Click to expand...
Click to collapse
go here and check if your device TWRP officially supported.
https://twrpbuilder.github.io/downloads/twrp/ and/or https://twrp.me/Devices/

Before flashing Stock Rom i extracted revocery.img from AP and converted it to recovery.tar without compressing and tried to solve the problem this way, re-flashing original recovery, but it failed.
So i tried it again and installed the newest version of Odin and in the second try i flashed AP, BL, and CSC.
Odin allows me to pass the full flashing process with no error.
But after the reset the tablet stucks in a loop of system updating and stops at 32%.
Notes in the download mode are "FRP-unlock: off" and "System: Custom" changed to "System: Offical. "
The red line "Recovery is not seandroid enforcing" vanished.
However it still says "Recovery: Custom" in the download mode and this shouldn't be possible after flashing Stock Rom.
At this moment the following errors appear.
No Support SINGLE_SKU
Supported API: 3
E: failed to mount/efs (invalid argument)
dm-verity error...
E: failed to mount /cache (invalid argument)
E: Can't mount /cache/recovery/last_kernel_manual
E: Can't open /cache/recovery/last_kernel_manual
E: failed to mount /cache (invalid argument)
E: Can't mount /cache/recovery/last_locale
Does this mean the partitions are damaged?
The only advices i found on google were, to flash with re-partitioning and to find the pit file. But i am afraid this would make it worse. Should i go to a repair service center or is it possible to still fix it?

If you download the stock firmware and flash the whole rom via odin and look in i believe is ap or csc.tar you should find the pit file extract it via 7zip or other alternative and load it with the pit selector in odin and reflash stock rom including the bl,ap,cp,csc and you should have a fully booting A6
Sent from my [device_name] using XDA-Developers Legacy app

Ok, i found the pit-file in CSC, but a CP file doesn't exist for SMT-580 Wi-Fi as far as i know.
I assume that i need to flash with re-partitioning and that i need to get sure the pit-file is for a 16 GB device.
But will this really solve my "[invalid argument]-issue"???

dontdropme said:
Ok, i found the pit-file in CSC, but a CP file doesn't exist for SMT-580 Wi-Fi as far as i know.
I assume that i need to flash with re-partitioning and that i need to get sure the pit-file is for a 16 GB device.
But will this really solve my "[invalid argument]-issue"???
Click to expand...
Click to collapse
yes theoretically it should solve all your issues and you should be able to reboot the device

allenjthomsen said:
yes theoretically it should solve all your issues and you should be able to reboot the device
Click to expand...
Click to collapse
Ok, flashing with Odin works, showing me no error, but i am still stucked in a bootloop. If i try to get in to the recovery mode it tells me, that it installs the update.
It does that, until it reaches 32%. I have tried flashing the stockrom with re-partitioning and the pit-file. Didn't work. Next thing i tried was to start Odin as Admin and with a newer version of the firmware. Didn't work. What changed is that "Current Binary: Custom" to "Current Binary: Samsung Official".
System Status is still: "Custom".
It still refuses to mount the system or to get to 100%, so that i could see the recovery mode with all it's options.
Could it be, that the CPU or the Memory is damaged?

Try to flash twrp then wipe factory data eeset and format data then flash stock again and see if that helps you boot to stock
Sent from my [device_name] using XDA-Developers Legacy app