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.
Related
Ok I messed up and need a little help.
Went through a couple threads to troubleshoot and not gotten very far.
I9000M
I was using a older froyo version of docs rom with voodoo kernal.
I decided to try to flash stock JVH with all files (pda, phone, CSC) with odin 1.7
re-partition checked, update bootload checked, 512 pit
phone reboots and when wiping data error message "E:format_volume: rfs format failed on /dev/block/mmcbl0p2"
No recovery but download works
You tried flashing eclair then froyo?
Sent from my GT-I9000 using XDA App
http://insanity.rollus.net/EZbase/EZbase-2.00.pdf
I usually revert to EZBase when switching roms. Maybe someone else can confirm this is a solution?
Flash back to KC1 using Odin.
And if you get the famous E: Can't mount /dev/block/stl10 (invalid Argument) message, follow the instructions in this thread:
http://forum.xda-developers.com/showthread.php?t=984140
Worked for me after flashing back to KC1 coming from JVH
Fixed !
Thanks you all !
used the EZbase and then flashed to KC1 ..booted right up !!!
Thanks again !
Ok something isn't right...
I was flashing Toxic Crazy8 because I couldn't deal with CM7's battery life. I am trying to Odin back to stock first. I go through the entire process and when Odin is done, the phone boots into recovery and says
"E:can't mount /dev/blok/st110 (invalid argument)
E:copy_dbdata_media:can't mount DBDATA
Copy default media content failed."
When I reboot phone I get the Vibrant Screen, the Tmo start up screen and then I got nothing.
Any ideas on what is going on?
I used the PIT512 and T959UVJI6 for my Odin files.
Thanks
Never mind, I used a different Tar file and got it working
MOD Edit: Glad to hear research helped you mate
Cheers,
M_T_M
First of all, sorry for my poor english, its not my mothers language, but I hope you will get what I mean.
My experience with errors during custom rom flashing & fixing them.
A lot of people have had this problem, when they try to mount internal SD card from recovery (to access it on PC) they get this error:
Code:
E:Can't mount /sdcard, E:Unable to write ums lunfile (No such file or directory)
I can't explain why its occurring, what is causing it, but from time to time I fixed it by just rebooting again to recovery, or in android, then turn it off, take out battery, then put it back, and boot again in recovery, well for me it was like a lottery, sometimes its worked sometimes not.
Last time I was unable to get pass that error, tried everything but still no luck. So I thought maybe I will flash stock firmware, and its gonna be OK. But no, not this time, I took as usually XXJVU firmware, PIT512, Odin3 v1.3 (with re-partition checked) and let the flashing to begin. In Odin everything was OK, till I got into phone after restart, where its should copy all the media files, and finalize firmware installation. What I got there was this:
Code:
-- cpoying media files...
E:failed to mount /sdcard (file exists)
E:copy_dbdata_media:cant mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.
Media files copy failed.
# MANUAL MODE #
-- Appling Multi-CSC...
Installing Multi-CSC
Aplied the CSC-code 'KOR'
Successfully applied multi-CSC.
After this I tried few other 2.3.x stock firmwares, but all of them got stuck at the same place.
I did a lot of searching on google, I found a few "worth to try" solutions (mostly from XDA members) but none of them actually fixed my problem. And I also seen that many people are getting the same exact thing. So I did a temporary fix, I put an old 1GB SD card into my phone, trough recovery mounted it successfully and flashed CodeNameAndroid, I was able to boot into android, but many things wasn't working, and still, internal SD card wasn't accessible, so next thing was, while I was on my break, I bring my phone to a phone repair shop, and the guy said that he can try to flash it back to stock firmware, so I gave him a shot, later when I came by, he said that he was unable to fix it, so that was where its all ended. But still I didn't believed that my almost 4 months old phone's internal SD card just simply died. So what I did, I went home and tried once again. And here is what I did:
Solution
1. Took the same XXJVU firmware
2. Flashed it using: Odin3 v1.3, PIT512, Re-partition ON.
After that I got into SGS logo bootloop, and the same thing, and I was ready to threw my phone against the wall. But before I still had a hope that maybe I can fix it, so this time I did these steps:
3. Same firmware
4. Flashed it using: Odin3 v1.3, PIT503, Re-partition OFF, and Phone Bootload update ON
And guess what ? Its worked!
There wasn't any errors, nothing, its just booted and I had my phone in service again.
I hope this will help someone who has exactly the same problem, and can't find a way to fix it.
Please, can u upload the 503 pit file ?
When Re-partition is OFF the PIT-file will NOT BE FLASHED by Odin.
Partition Information Table of whatever PIT-file will have no effect on phone.
Most Samsung ROMs need 512.PIT to set correct file system RFS and size of /system /data + + partitions. Not necessary to reset your partitions/filesys every time you flash ROM.
Use 512.PIT when you have ext4 (lagfix) filesys, CyanogenMod, MIUI or ICS ROMs and want to return to Samsung stock.
Bootloader (Sbl) of Froyo and Gingerbread are not the same. Odin will take care of updating bootloader IF PHONE.tar includes sbl.bin.
DO NOT tick update bootloader, just flash PHONE, MODEM, CSC and you'll get updated bootloader.
More here: http://forum.xda-developers.com/showthread.php?p=14273101
Sent from my GT-I9000
Problem with internal SD not solved yet
O-T said:
When Re-partition is OFF the PIT-file will NOT BE FLASHED by Odin.
Partition Information Table of whatever PIT-file will have no effect on phone.
Most Samsung ROMs need 512.PIT to set correct file system RFS and size of /system /data + + partitions. Not necessary to reset your partitions/filesys every time you flash ROM.
Use 512.PIT when you have ext4 (lagfix) filesys, CyanogenMod, MIUI or ICS ROMs and want to return to Samsung stock.
Bootloader (Sbl) of Froyo and Gingerbread are not the same. Odin will take care of updating bootloader IF PHONE.tar includes sbl.bin.
DO NOT tick update bootloader, just flash PHONE, MODEM, CSC and you'll get updated bootloader.
More here: http://forum.xda-developers.com/showthread.php?p=14273101
Sent from my GT-I9000
Click to expand...
Click to collapse
After applying the methode as described in post 1, it did not resolve my problem. Internal SD still not usable.
When following the above (link to post) all the possible solutions did not work.
Could someone please let me know how to fix the internal SD so it can be used again?
Thanks in advance!:good::good:
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.
So my wife has this note 4 and a few weeks ago it started doing the bootloop thing... Tried a few solutions but nothing stuck.
since the device is in top shape(never dropped, always in original cover etc) i refuse to accept it just dies after a little more than 2 years of use.
No there is no warranty left, no a phoneshop is not an option. this is now my toy and i want to get it fixed
things i can do:
use odin to set it up with twrp
boot into downloadmode
look at it being stuck in first bootscreen
things i tried:
replaced the battery
first thing was wipe cache, that made it wake up from the bootloop temporary.
installed wake_lock as per found threads on the web, this didn't really do much as the phone would still reboot
factory reset from the phone settings menu, no help
factory reset from bootmenu, same result aka nothing
i did a few different (all) wipe options from the bootmenu
tried installing a repair firmware but this would fail in odin (3.12.7)
now when i boot into twrp i cant do anything because it is unable to mount data/cache/system etc
storage volume turns up as 0
kies says it doesn't support the device
smartswitch tells me the same.
so we can boot into twrp or downloadmode
wich tells me the device isnt "DEAD" but more coma-like
anybody that can help out?
Try to format /data with TWRP. You will lose all data but at this point I think your main priority is just to get the device to wake up. Flash latest stock downloaded from updato or sammobile and install via Odin. If Odin fails, please post what error message you get.
ShaDisNX255 said:
Try to format /data with TWRP. You will lose all data but at this point I think your main priority is just to get the device to wake up. Flash latest stock downloaded from updato or sammobile and install via Odin. If Odin fails, please post what error message you get.
Click to expand...
Click to collapse
i cant even use format data with twrp
unable to mount
/data
/cache
/system
/modem
/efs
/firmware
first line says:
Erimary block device '/dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '/data' is not present!
the hole keeps getting deeper
stash_nl said:
i cant even use format data with twrp
unable to mount
/data
/cache
/system
/modem
/efs
/firmware
first line says:
Erimary block device '/dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '/data' is not present!
the hole keeps getting deeper
Click to expand...
Click to collapse
Yeah you've got an issue on your hands. Just keep digging and you'll find the answer eventually.
Apparently, there have been reported cases of your problem and having been fixed (on other systems, though)
For example this thread where they fixed it on a Nexus 7: https://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
Just keep searching
I'll keep digging around and let you know if I find something related to your problem
EDIT: Might be corrupted partitions. Try to re-flash ROM but using a PIT file in Odin (to re-partition) and see if it fixes your issue
ShaDisNX255 said:
Yeah you've got an issue on your hands. Just keep digging and you'll find the answer eventually.
Apparently, there have been reported cases of your problem and having been fixed (on other systems, though)
For example this thread where they fixed it on a Nexus 7: https://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
Just keep searching
I'll keep digging around and let you know if I find something related to your problem
EDIT: Might be corrupted partitions. Try to re-flash ROM but using a PIT file in Odin (to re-partition) and see if it fixes your issue
Click to expand...
Click to collapse
tried using cwm recovery but that seems to have even less posibilities than twrp so that one is of the table
I read that post you referred to and followed a trail to a post about PIT files. sounds promissing but i can"t figure out what PIT file i need for my particular device
Need to know how to determine that before i can proceed with using a PIT file because i read that you mustn't cross flash a wrong pit.
Furthermore... storage still shows up as 0 no mount, nothing partitionable/formatable
stash_nl said:
tried using cwm recovery but that seems to have even less posibilities than twrp so that one is of the table
I read that post you referred to and followed a trail to a post about PIT files. sounds promissing but i can"t figure out what PIT file i need for my particular device
Need to know how to determine that before i can proceed with using a PIT file because i read that you mustn't cross flash a wrong pit.
Furthermore... storage still shows up as 0 no mount, nothing partitionable/formatable
Click to expand...
Click to collapse
Hopefully you'll find the correct PIT file, you just need to make sure you have the correct model and correct storage capacity
By now i am getting MMC: mmc_read fail errors
anybody???
like, help n stuff