Related
"E: Can't mount /dev/block/mmcblk0p2 (Invalid argument) E:/copy_data_default_apk:Can'
I know you guys don't like new posts, but I've spent the past 2 days trying to figure this out and I am about to give up.
I'll just lay this out in bullets and this is just a last attempt before I throw this phone out:
Phone: GT-i9000 bought full price from Bell, unlocked running on Fido
Rom Installed: ROM Name: All In One Edition Version: 7.0 Developer: Spike_M Firmware: XXJPY
I shut the phone off because it stopped responding to any touches, turn it back on and its stuck on the SAMSUNG GALAXY S Logo.
Can enter DOWNLOAD mode using three button combo, but not RECOVERY mode.
This means that I tried to flash a new FW using ODIN. What I tried to flash:
Used:
Odin3 v1.3
PDA = I9000XXJPU-REV03-PDA-low-CL747761.tar
PIT = s1_odin_20100512.pit
PHONE = MODEM_I9000XXJPU.tar.md5
CSC = GT-I9000-CSC-MULTI-OXAJPU.tar.md5
When I click Start on Odin with either ☐ Re-Partition or ☑ Re-Partition, it reboots into RECOVERY mode, "Wipes Data", and gives me this error message:
HTML:
"E: Can't mount /dev/block/mmcblk0p2 (Invalid argument) E:/copy_data_default_apk:Can't mount DBDATA: your storage and not prepared yet. Please use UI menu for format and reboot actions."
and just hangs.
I found this link: forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage
and tried the solution. I can access the adb shell when the phone is stuck in recovery mode, but I don't have root access so I can't push any files like parted onto the /sbin folder because it says "Permission denied"
If anyone can tell me if phone is a lost cause, I can stop trying already and get on with my life. If anyone can help, I would really appreciate it. Thanks a lot.
my "E: can't mount /dev/block/mmcblk0p1" problem has been solved by this.
It may not be the same problem but the following solved my "E: can't mount /dev/block/mmcblk0p1" problem, not "E: can't mount /dev/block/mmcblk0p2". I used JM2, 512 pit.
Credit to Margaliini
1. Enter your phone in dl-mode, but don't connect yet.
2. Open Odin, tag re-partition, auto reboot and f.reset time, make sure efs clear and bootloader -fields are NOT checked. select CORRECT PIT-file (2.1 ROMS usually 512, 2.2 ROMs many times 803, samfirmware always tells which one to use next to the dl-link of a ROM-file), enter your phone in dl-mode, plug, wait it to be recognized by Odin.
3. Click start, wait until Odin shows PASSED, unplug your phone, remove the battery for 30 seconds, enter dl-mode again, don't plug just yet.
4. In Odin, click Reset. Then select PDA, Modem and CSC files compatible with the PIT-file used in re-partition, plug your phone, make sure re-partition NOT checked and no PIT-file selected (once again, make sure you use correct PDA for the PIT you flashed). auto-reboot and f.res.time should be selected. Make sure efs clear and bootloader -fields are NOT checked.
4- Plug your phone and when recognized, click start. Wait to be passed. Now your phone will boot (or if not, boot manually) and should work just fine.
Edit: Try to put Eclair ROM, for example JM2, not jpa, and see if it works better.
Thanks, I'll try that and report back to you...
Please help me I have this problem your suggestion did not work please help
and thanks
alaaflashaliraqi said:
Please help me I have this problem your suggestion did not work please help
and thanks
Click to expand...
Click to collapse
u can try this
Solved
If problem is still valid, I have found a kind of solution (or rather workaround) which can be found on YT.
www youtube com/watch?v=zdMhYYdMB08
Best regards
fteller said:
If problem is still valid, I have found a kind of solution (or rather workaround) which can be found on YT.
www youtube com/watch?v=zdMhYYdMB08
Best regards
Click to expand...
Click to collapse
Using some advice from your guide along with the fix found here, I was able to revive my once unresponsive internal sdcard http://forum.xda-developers.com/showthread.php?t=1665123
How did you mange to fix this Mount problem finally ?
E: Can't mount/dev/block/mmcblk0p2 (invalid argument
E:copy_data_default_apk:Can't maount DBDATA
Mu phone gets into download mode , and recognized by Odin (i have tried to put I9000xxJPU the download process was finished with no error, but when the phone made restart to start the update process i got the error message above). since the the phone is stuck in endless loop on the main samsung opening screen.
I tried to do this tip : (with the I9000xxJPU)
http://www.youtube.com/watch?v=zdMhYYdMB08
but got the same result ...i am not convinced that's the same error as mine ...
Please , any replay will be of great help.
Ran:fingers-crossed:
find dbdata
u can see here for i9000
http://forum.xda-developers.com/showthread.php?p=38025542
Sent from my GT-I9000 using xda premium
Apply again stock with pit file ...this error will finish.
Sent from my GT-I9000 using xda app-developers app
Dont work still
Hi ,
Thanks for your replay.
I tried to put the dbdata.tar file in the link that you said .
The phone seems to update dbdata when its satrted, but still get stucked with the same error...
Do you think a new stok will solve it ? i tride already 3 of thoes...(if you can give a link for somthing that you think that is recommanded i will be greatfull)..
Any outher guesses?
---------- Post added at 08:42 AM ---------- Previous post was at 08:38 AM ----------
Hi ,
Thanks for your replay.
I tried to put the dbdata.tar file in the link that you said .
The phone seems to update dbdata when its satrted, but still get stucked with the same error...
Do you think a new stok will solve it ? i tride already 3 of thoes...(if you can give a link for somthing that you think that is recommanded i will be greatfull)..
Any outher guesses?
Doesn't meter what rom I Flash I get this error: http://imageshack.us/photo/my-images/823/img201207201510251.jpg/
I have copyed all files: parted, e2fsck etc and did what says on this post: http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20 (number 23)
When im trying to parted, its just says: "no such file or directory" http://imageshack.us/photo/my-images/844/shell2.jpg/
If i try to format - i receiving such errors: http://imageshack.us/photo/my-images/801/img201207201436181.jpg/
http://imageshack.us/photo/my-images/841/img201207201437371.jpg/
please advice how to use parted?
Edit:
I have managed to open parted, but now i cant remove any partitions, after rm command its remains same.
http://img685.imageshack.us/img685/5201/printuo.jpg
How can i remove partitions?
Bezeq said:
Doesn't meter what rom I Flash I get this error: http://imageshack.us/photo/my-images/823/img201207201510251.jpg/
I have copyed all files: parted, e2fsck etc and did what says on this post: http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20 (number 23)
When im trying to parted, its just says: "no such file or directory" http://imageshack.us/photo/my-images/844/shell2.jpg/
If i try to format - i receiving such errors: http://imageshack.us/photo/my-images/801/img201207201436181.jpg/
http://imageshack.us/photo/my-images/841/img201207201437371.jpg/
please advice how to use parted?
Edit:
I have managed to open parted, but now i cant remove any partitions, after rm command its remains same.
http://img685.imageshack.us/img685/5201/printuo.jpg
How can i remove partitions?
Click to expand...
Click to collapse
You do not need to remove any partitions... Just flash stock rom, and try again... Same happened to me, i couldnt mount any partition in recovery, now it fine
foggydisaster said:
You do not need to remove any partitions... Just flash stock rom, and try again... Same happened to me, i couldnt mount any partition in recovery, now it fine
Click to expand...
Click to collapse
I have tryed to flash many roms, 2.2.1 2.3.1 2.3.5 .2.3.6, (JVT, JVR, LPY, and new ones) always same issue: "E: failed to mount /data (invalid argument) and then bootlooping.
I`m sure my mmcblk0p2 is broken, question is how to force delete this partition or flash rom in to external SDcard!
Bezeq said:
I have tryed to flash many roms, 2.2.1 2.3.1 2.3.5 .2.3.6, (JVT, JVR, LPY, and new ones) always same issue: "E: failed to mount /data (invalid argument) and then bootlooping.
I`m sure my mmcblk0p2 is broken, question is how to force delete this partition or flash rom in to external SDcard!
Click to expand...
Click to collapse
Well you cant flash roms onto sdcard... But if your partition is broken, then sorry but im a noob
Sent from my GT-I9000 using xda app-developers app
Have you tired using a pit file?
flash a stock rom from samfirmware.com with ODIN.(eg. jw5)
to extract the password is "samfirmware.com"
tick repartition and use 512 pit file(included in rom from samfirmware).
check youtube for "flash with odin" if u dont know how.
edit:u are trying to flash from from samsungs 3 recovery.u need cwm(clockworkmod) to flash.
go to CF-ROOT(for i-9000) thread and follow instructions and read all in the OP(1-2-3 posts)
again u need ODIN to flash it.
hey
there is the best wasy to do that...just go to sammobile.com
there sign up first and then download the firmware (in firmware tab) and flash-programs...
the make sure to use oidn3_v1.0 only...
you can also download the flash-guide if you need it...
its simple..:laugh:
Thanks to everyone for replays, but nothing helped me x_x
if i flash 2.2.1 or 2.3.6 i receiving this error:
https://www.box.com/s/4d4b108a0246f9f56c7c
If i flash 2.3.3 or 2.3.4:
https://www.box.com/s/f09fd945620c03daffa9
And then it keep showing me GT 9000 logo......
yes i used 512pit and using 1.82 odin
I know there is way to install in to external SDcard: http://www.youtube.com/watch?v=zdMhYYdMB08
I had such error and successfully installed rom in to sdcard but i had issue with phone signal, so tried to re install rom and now its keep teling me cant mount data..
What can i do?
Hello,
Did you try this http://forum.xda-developers.com/showthread.php?t=984140 ?
mystic324 said:
Hello,
Did you try this http://forum.xda-developers.com/showthread.php?t=984140 ?
Click to expand...
Click to collapse
Yep, keep shows only gt-9000 logo..
I had a very similar problem earlier this year.
From what I could see the partitions on the phone's internal storage weren't able to be accessed. In adb I tried using parted and rm but the partitions there (/dev/block/mmc/blk0) didn't ever change. I also tried various .pit files and Android versions through Odin but nothing worked.
I took my phone in for repairs after flashing a really old version; as close as possible to what it came with, and they fixed it. The repair was due to 'mechanical fatigue' according to them. I assumed the internal storage was some how broken or corrupted and couldn't be written to.
Not sure, if you manage to solve this.
From you screenshots I can see you are using 3e recovery. I would suggest you to flash a kernel which support cwm recovery mode.
I have heard peoples getting this error while using it on 3e.
Captain_17
Yes Captain_17, i have exactly same problem, cant give it to repair since purchased it from abroad.
erpurohit said:
Not sure, if you manage to solve this.
From you screenshots I can see you are using 3e recovery. I would suggest you to flash a kernel which support cwm recovery mode.
I have heard peoples getting this error while using it on 3e.
Click to expand...
Click to collapse
3e recovery because i`ve flashed 2.2 and 2.2.1 or any other official roms, i can flash CWM easy but as Captain_17 said i can see but cant touch
files or partitions.
If flash CWM then phone will boot to CWM only, and i cant flash any rom from CWM because i cant copy files to internal storage and external (sdcard) cwm doesn't see it.
Sorry man, wish I could be of more help. I tried every available option I could find online but nothing worked.
Seems to be a hardware problem and replacing the damaged part is the only solution.
Silly question, but you ticked re-partition? try flash 2.2.1 or 2.3.3 with 512 pit and repartition
Also, you could try to flash Darky ressurection via odin, not completely stock rom. I know that this is just tweaked stock, but you could try do that.
And, you could try to use Heimdall instead of odin - http://forum.xda-developers.com/showthread.php?t=1196179
I have read somewhere that heimdall is more preferable than odin in some cases.
Bezeq said:
Yep, keep shows only gt-9000 logo..
Click to expand...
Click to collapse
I once also a similar problem and flash2.1 Eclayr. But then I had to restore recowery to flash. as with you, I do not know if it helps.
I have a Samsung Galaxy Pop with “com.android.phone” error each time the device restarts. The network goes down and comes back again. This happens twice.
I had upgraded my handset from 2.2.1 to 2.2.2 using Kies in Sept 2012. I somehow got a chance to copy the I559DDEH31_HOME.tar.md5 file which Kies creates for upgrade. The contents of the file are amss, boot.img, cache.rfs, recovery.img & system.rfs.
I have tried Odin to flash but have been unsuccessful.
I would like to know if I can use “dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096” command using adb shell to restore the handset to its original state?
I am not that good at Android so would like to know if somebody can help me.
deep143in said:
I have a Samsung Galaxy Pop with “com.android.phone” error each time the device restarts. The network goes down and comes back again. This happens twice.
I had upgraded my handset from 2.2.1 to 2.2.2 using Kies in Sept 2012. I somehow got a chance to copy the I559DDEH31_HOME.tar.md5 file which Kies creates for upgrade. The contents of the file are amss, boot.img, cache.rfs, recovery.img & system.rfs.
I have tried Odin to flash but have been unsuccessful.
I would like to know if I can use “dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096” command using adb shell to restore the handset to its original state?
I am not that good at Android so would like to know if somebody can help me.
Click to expand...
Click to collapse
No replies??
deep143in said:
No replies??
Click to expand...
Click to collapse
Why don't u flash a new gingerbread 2.3.6 stock rom? Froyo is kind of outdated. Make sure to backup your contacts and everything if u decide to do so.
kirakun said:
Why don't u flash a new gingerbread 2.3.6 stock rom? Froyo is kind of outdated. Make sure to backup your contacts and everything if u decide to do so.
Click to expand...
Click to collapse
Hi Kirakun,
I would love to do that but unfortunately I am not able to find dedicated Gingerbread 2.3.6 stock rom for Samsung Galaxy Pop CDMA (India) SCH-I559.
I have searched a lot but found only for Samsung Galaxy mini or S5570 which are the GSM versions of the same model.
I have also found that some have already bricked their phones using the other versions.
So I have decided to stick to froyo.
I just wanted to make sure that if I restore the /system partition using system.rfs command (dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096) shouldn't create any new problems.
deep143in said:
Hi Kirakun,
I would love to do that but unfortunately I am not able to find dedicated Gingerbread 2.3.6 stock rom for Samsung Galaxy Pop CDMA (India) SCH-I559.
I have searched a lot but found only for Samsung Galaxy mini or S5570 which are the GSM versions of the same model.
I have also found that some have already bricked their phones using the other versions.
So I have decided to stick to froyo.
I just wanted to make sure that if I restore the /system partition using system.rfs command (dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096) shouldn't create any new problems.
Click to expand...
Click to collapse
that will ruin your phone
and for the message just need to wipe data from recovery
deep143in said:
Hi Kirakun,
I would love to do that but unfortunately I am not able to find dedicated Gingerbread 2.3.6 stock rom for Samsung Galaxy Pop CDMA (India) SCH-I559.
I have searched a lot but found only for Samsung Galaxy mini or S5570 which are the GSM versions of the same model.
I have also found that some have already bricked their phones using the other versions.
So I have decided to stick to froyo.
I just wanted to make sure that if I restore the /system partition using system.rfs command (dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096) shouldn't create any new problems.
Click to expand...
Click to collapse
My bad i was not aware of this different version. Yes do try what dheeraj has said.
I think that entering recovery should be same for u, just switch off phone, press home button and power button simultaneously and hopefully you will enter recovery.
Navigate using volume button and do a wipe data and cache. Doing so you will lose any app and everything from your phone, so do a backup before.
dheeraj (dhlalit11) said:
that will ruin your phone
and for the message just need to wipe data from recovery
Click to expand...
Click to collapse
I have already tried to wipe from recovery twice but still face the same error. Everything resets to factory defaults except this error which pops up at every restart..
reflash firmware through odin
and I will recommend you to take it to Samsung care
---------- Post added at 04:50 PM ---------- Previous post was at 04:50 PM ----------
reflash firmware through kies
and I will recommend you to take it to Samsung care
dheeraj (dhlalit11) said:
reflash firmware through odin
and I will recommend you to take it to Samsung care
---------- Post added at 04:50 PM ---------- Previous post was at 04:50 PM ----------
reflash firmware through kies
and I will recommend you to take it to Samsung care
Click to expand...
Click to collapse
I have done the wipe data and cache. Below is the response:
-- Wiping cache...
Formatting CACHE:...
umount(/cache) attempt 1
(Unknown error: 0) rc=0
Cache wipe complete.
-- Wiping data...
Formatting DATA:...
Formatting CACHE:...
umount(/cache) attempt 1
(Unknown error: 0) rc=0
Cache wipe complete.
But unfortunately same error.
I cannot flash firmware as I do not have one supported for this model of samsung (CDMA version). KIES says that the firmware is up to date so cannot flash from there as well.
deep143in said:
I have done the wipe data and cache. Below is the response:
-- Wiping cache...
Formatting CACHE:...
umount(/cache) attempt 1
(Unknown error: 0) rc=0
Cache wipe complete.
-- Wiping data...
Formatting DATA:...
Formatting CACHE:...
umount(/cache) attempt 1
(Unknown error: 0) rc=0
Cache wipe complete.
But unfortunately same error.
I cannot flash firmware as I do not have one supported for this model of samsung (CDMA version). KIES says that the firmware is up to date so cannot flash from there as well.
Click to expand...
Click to collapse
In case if you don't mind I would like to know how my phone will get ruined if I use the system.rfs from the original firmware file downloaded by Kies?
Secondly, is there a particular version of ODIN I need to use for this handset? I have tried 1.85, 3.07 and 4.38 versions.
Actually I do not have any other files than the I559DDEH31_HOME.tar.md5 required by ODIN.
I would prefer to go to Samsung service centre only when I am left with no option or if the handset fails to do its regular tasks.
Anyways, thanks for your suggestion.
you will do it while your phone is running and while doing it your mobile will reboot in the process due to change in some critical files
and we also don't know what is the structure of system.rfs
dheeraj (dhlalit11) said:
you will do it while your phone is running and while doing it your mobile will reboot in the process due to change in some critical files
and we also don't know what is the structure of system.rfs
Click to expand...
Click to collapse
Dheeraj, I understand what you are trying to say. I was plannning to do so in recovery mode. I have checked through ADB that I can access the device when in recovery mode. Will it still be a problem?
deep143in said:
Dheeraj, I understand what you are trying to say. I was plannning to do so in recovery mode. I have checked through ADB that I can access the device when in recovery mode. Will it still be a problem?
Click to expand...
Click to collapse
Alternatively I can also do when the phone is in download mode..
What do u think?
well you can't in download mode
but of you have cwm then it would be easy
open system.rfs with soft which can mount iso etc.
Copy the content of system to you sdcard
now flash aroma file manager and with the help of that copy all the files your your system.rfs to your system partition
and with dd it may copy files to /system/system or directly to /root
dheeraj (dhlalit11) said:
well you can't in download mode
but of you have cwm then it would be easy
open system.rfs with soft which can mount iso etc.
Copy the content of system to you sdcard
now flash aroma file manager and with the help of that copy all the files your your system.rfs to your system partition
and with dd it may copy files to /system/system or directly to /root
Click to expand...
Click to collapse
I used a linux machine to mount the system.rfs. Extracted phone.apk and installed the app using root explorer.
Finally the problem com.android.phone has been resolved..
Thanks for your help.
deep143in said:
Hi Kirakun,
I would love to do that but unfortunately I am not able to find dedicated Gingerbread 2.3.6 stock rom for Samsung Galaxy Pop CDMA (India) SCH-I559.
I have searched a lot but found only for Samsung Galaxy mini or S5570 which are the GSM versions of the same model.
I have also found that some have already bricked their phones using the other versions.
So I have decided to stick to froyo.
I just wanted to make sure that if I restore the /system partition using system.rfs command (dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096) shouldn't create any new problems.
Click to expand...
Click to collapse
the upgrade is available in India but only at the official samsung repair center.
u will have to visit 'em get it upgraded
Hello everybody, I'm new to this forum, but I'm reading it for about 8 months now. I have a problem with my Samsung Galaxy S I9000. After flashing with Odin3 v1.83(with 512.pit file, bootloader, PDA, PHONE and CSC), and I got a green "PASS!" on it, and after phone rebooted in Recovery Mode, I've got following error while Copying media files:
E:Failed to mount /sdcard (Invalid Argument)
After that, I tried flashing bunch of different ROM's but I always get the same error. Phone can go into Download mode, Recovery mode with no problem, I can also normally turn on phone and in a beggining I get a lot of "Force Close" pop-ups, but after that my phone works okay, I can go into settings and there I can see that there is no memory, so that means that my phone doesn't even sees my 8GB external micro sd card. When I try to open Camera, I get this error:
Turn off usb storage before using camera.
I currentlly have i9000XWJVZ 2.3.6 ROM on it, with CF-Root-XX_OXA_JVZ-v4.3-CWM3RFS(Clockwork Recovery v3.0.0.5). When I'm in Recovery mode and access my phone via ADB, and try to manually mount sdcard, this is what I get:
~ # mount sdcard
mount sdcard
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: I/O error
I've also tried partitioning my external 8GB micro SD card with linux(I found a video on youtube: "Samsung i9000 mmcblk0p2 error recovery"), and then tried to flash ROM on it, but I get the same error.
Can somebody please help me, I'm getting really desperate.
All ideas are welcome, Thanks.
Hi there! I have a similar problem. After updating from Android 2.3.4 Build MCGv7.6 ( I9000XXJVK) I keep on getting CWM. I can also return to download mode and use Odin with success - with as only result a changed CMW version at max. Returning to CWM 3.0.0.5 and stock rom Froyo doesn't result in a applied rom. When i try to mount /emmc and /sd-ext it simply states Error mounting /emmc! Even though I didn't format it! When I look in AROMA explorer in CWM from Semaphore_JB_2.9.12, I can see that both /emmc and /sdcard have ----- as permissions instead of rxwrx or something alike. If permissions are the problem here, Fix Permissions doesn't appear to have an effect on these two folders. Is there another way to restore these permissions?
Thanks guys for your time! :good:
@ficko flash dbdata.rfs as PDA in odin.
Sent from my GT-I9000 using Tapatalk 2
knuckles1978 said:
@ficko flash dbdata.rfs as PDA in odin.
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
I've tried that, but with no luck.. always the same error.
Check my signature:laugh:
EwOkie said:
Check my signature:laugh:
Click to expand...
Click to collapse
Can't see sigs, I'm using tapatalk.
Sent from my GT-I9000 using Tapatalk 2
EwOkie said:
Check my signature:laugh:
Click to expand...
Click to collapse
Your tutorial was the first thing I tried, it fixed the wipe error, but the main error (E:Failed to mount /sdcard) stayed.
Possible solution is to Format your SD card by using SDFormatter (Windows)
01. Download "SDFormatter" from the link above
02. Install "SDFormatter"
03. Enable "USB Debugging Mode" from Developer Options in settings.
04. Connect your tablet to PC (USB).
05. Then, tap the "USB Strage Mode" to connect to PC.
06. Backup data on INTERNAL_SD card.
07. Run "SDFormatter".
08. Specify the drive letter of INTERNAL_SD in SDFormatter and click "(Option)" button.
09. "FORMAT TYPE" select "FULL OVERWRITE" and set "FORMAT SIZE ADJUSMENT" to "ON" and click "OK"
10. Now click "FORMAT" and wait for the procedure to complete. (Can take approximately 1 hour 40 minutes)
11. After format is completed you can recopy the backup files back onto the INTERNAL_SD
Let me know if that works
If not hopefully someone else can give more info
EwOkie said:
Possible solution is to Format your SD card by using SDFormatter(Windows)
01. Download "SDFormatter" from the link above
02. Install "SDFormatter"
03. Enable "USB Debugging Mode" from Developer Options in settings.
04. Connect your tablet to PC (USB).
05. Then, tap the "USB Strage Mode" to connect to PC.
06. Backup data on INTERNAL_SD card.
07. Run "SDFormatter".
08. Specify the drive letter of INTERNAL_SD in SDFormatter and click "(Option)" button.
09. "FORMAT TYPE" select "FULL OVERWRITE" and set "FORMAT SIZE ADJUSMENT" to "ON" and click "OK"
10. Now click "FORMAT" and wait for the procedure to complete. (Can take approximately 1 hour 40 minutes)
11. After format is completed you can recopy the backup files back onto the INTERNAL_SD
Let me know if that works
If not hopefully someone else can give more info
Click to expand...
Click to collapse
This worked!
It took me about an hour, and after it was finished, I was able to flash ROM without any errors. Thank you so much for this, you saved my phone.
No problem glad it worked out for you:good:
Ficko2210 said:
This worked!
It took me about an hour, and after it was finished, I was able to flash ROM without any errors. Thank you so much for this, you saved my phone.
Click to expand...
Click to collapse
EwOkie said:
No problem glad it worked out for you:good:
Click to expand...
Click to collapse
I got the same problem but my phone alway boot loop. How can I enable USB Debugging mode to format internal SD
zaniku1 said:
I got the same problem but my phone alway boot loop. How can I enable USB Debugging mode to format internal SD
Click to expand...
Click to collapse
Explain your issue please
EwOkie said:
Explain your issue please
Click to expand...
Click to collapse
Thanks for your response
Here is my problem
1. Phone got boot loop (Never pass splash Galaxy S).
2. Try to flash a new rom via ODIN (several version JPA, JW4 , JVU..) then got error as below
--Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. Please use UI
menu for format and reboot actions
Media files copy failed.
--Wipping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wip failed.
--Applying Multi-csc...
Installing Multi-csc
Can't access to '/system/csc/TMB/system/'.
Successfully applied multi-CSC.
3. After reboot phone still boot loop.
Refer to My signature at bottom HOW TO GUIDE it show steps on what you need to do....
dbdata and PIT File is all there.....just follow instructions and it will set you free!
EwOkie said:
Refer to My signature at bottom HOW TO GUIDE it show steps on what you need to do....
dbdata and PIT File is all there.....just follow instructions and it will set you free!
Click to expand...
Click to collapse
Yep, seconded. dbdata.rfs and PIT file, that's what you need
Sent from my Nexus 7 using Tapatalk HD
After flash dbdata.rfs.tar, it still showed same error message.
zaniku1 said:
After flash dbdata.rfs.tar, it still showed same error message.
Click to expand...
Click to collapse
You could try changing the way you do it. I can't remember whether you should flash dbdata straight after the rom, or if you should let it fail to boot then go back into download mode and flash it.
I do remember though that it was a bit fussy with me like that, so try it both ways.
I also found that flashing your GB ROM twice, one after the other seemed to help sometimes too. (Just noticed that I've written a .txt file in my GB ROM folder on my PC reminding me to do this, so there must have been a reason for it - been a while since I've played with gingerbread so I can't remember why)
So there's a couple of things for you to try.
Sent from my Nexus 7 using Tapatalk HD
Flash the JVU Rom First with PIT and Root...
When Finished Root pull battery ....put battery back in after 30 seconds
Reset ODIN Flash dbdata ..Done
Hope this helps
knuckles1978 said:
You could try changing the way you do it. I can't remember whether you should flash dbdata straight after the rom, or if you should let it fail to boot then go back into download mode and flash it.
I do remember though that it was a bit fussy with me like that, so try it both ways.
I also found that flashing your GB ROM twice, one after the other seemed to help sometimes too. (Just noticed that I've written a .txt file in my GB ROM folder on my PC reminding me to do this, so there must have been a reason for it - been a while since I've played with gingerbread so I can't remember why)
So there's a couple of things for you to try.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
EwOkie said:
Flash the JVU Rom First with PIT and Root...
When Finished Root pull battery ....put battery back in after 30 seconds
Reset ODIN Flash dbdata ..Done
Hope this helps
Click to expand...
Click to collapse
Thanks both of you. I will try.
EwOkie - Should I use CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS for rooting phone or others?
CF Root is in the HOW TO GUIDE or HERE
CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS is the correct one to use ...
Everythng you need is in there
After restoring a backup, Includes EFS I am not able to reboot my phone anymore.
I tried flashing stock, a few combinations..
Combinations bootloop on Factory Binary logo, Stock ROMs on Samsung logo.
Download mode:
ODIN MODE
DOWNLOAD SPEED: FAST
Product name: N950F (My model is N950F/DS but it's normal it says N950F)
Current Binary: Samsung Official
System Status: Custom
RMM State: Prenormal
FRP Lock: OFF
OEM Lock OFF
Secure download enabled.
Also my Knox is 0x030c.
In recovery I get this:
Code:
#Fail to open recovery_Cause (No such file or directory)
Stock/Combinations flash fine. But on reboot they boot into stock recovery and gives this error:
Reboot Recovery Cause is Unknown
Support SINGLE-SKU
File based OTA
E:Failed to mount /efs (Invalid argument)
Supported API: 3
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
Dm-verity verification failed...
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
Remove failed dir '/system/carrier/att/priv-app invalid directory
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Bad file descriptor)
E:Failed to mount /efs (Bad file descriptor)
E:Failed to mount /efs (Bad file descriptor)
E:Failed to mount /efs (Bad file descriptor)
E:Failed to mount /efs (Bad file descriptor)
E:Failed to mount /efs (Bad file descriptor)
(A lot of times)
Any ideas? I really miss this phone.
Thanks in advance!! I'm on CRGA if that helps, So I can flash ARG1 combination, CRG1 firmware, CRGA firmware.
I had no issues with EFS before at all, All issues came after this backup restore.
Flashing custom recovery gives me this: imgur.com/a/zKcoJVp
Errors in stock recovery: imgur.com/a/ywIXfx7
Samsunguser932 said:
I had no issues with EFS before at all, All issues came after this backup restore.
Flashing custom recovery gives me this: imgur.com/a/zKcoJVp
Errors in stock recovery: imgur.com/a/ywIXfx7
Click to expand...
Click to collapse
Have you tried formatting data, where you have to type yes? I believe TWRP still has mounting issues, so you have to format like I said, then TWRP should mount properly.
You will have to flash stock with Odin to get rid of the binary issue., I believe.
stonedpsycho said:
Have you tried formatting data, where you have to type yes? I believe TWRP still has mounting issues, so you have to format like I said, then TWRP should mount properly.
You will have to flash stock with Odin to get rid of the binary issue., I believe.
Click to expand...
Click to collapse
I can't flash TWRP at all, Please read my whole post.. I tried flashing stock and this is as far as I get right now.
Samsunguser932 said:
I can't flash TWRP at all, Please read my whole post.. I tried flashing stock and this is as far as I get right now.
Click to expand...
Click to collapse
I was just trying to make sense of your post if I'm honest.
If you can not flash stock with Odin, contact Samsung for repair.
stonedpsycho said:
I was just trying to make sense of your post if I'm honest.
If you can not flash stock with Odin, contact Samsung for repair.
Click to expand...
Click to collapse
I can't , Solution now?
Samsunguser932 said:
I can't , Solution now?
Click to expand...
Click to collapse
Why can't you contact Samsung for repair?
sefrcoko said:
Why can't you contact Samsung for repair?
Click to expand...
Click to collapse
He does not want to take it, because it's a n950x live demo unit :silly::silly:
sefrcoko said:
Why can't you contact Samsung for repair?
Click to expand...
Click to collapse
SebastianSNRL said:
He does not want to take it, because it's a n950x live demo unit :silly::silly:
Click to expand...
Click to collapse
Because it's bought through work, It is a lease.
Samsunguser932 said:
Because it's bought through work, It is a lease.
Click to expand...
Click to collapse
Well, take it to your work for them to sort it out, just don't tell them what you tried to do.
Surely they would get you a replacement?
How did you restore your efs partition?
Bootloader 4?
PM me.
stonedpsycho said:
Well, take it to your work for them to sort it out, just don't tell them what you tried to do.
Surely they would get you a replacement?
Click to expand...
Click to collapse
I am starting to think it's a hardware issue and this might be how it should be done..Problem is it says System Status: Custom, And I can't change it to Official without booting :crying:
Samsunguser932 said:
I am starting to think it's a hardware issue and this might be how it should be done..Problem is it says System Status: Custom, And I can't change it to Official without booting :crying:
Click to expand...
Click to collapse
Your bootloader states prenormal, maybe this post will help you with that.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
stonedpsycho said:
Your bootloader states prenormal, maybe this post will help you with that.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Click to expand...
Click to collapse
I can't boot at all..
Samsunguser932 said:
I can't boot at all..
Click to expand...
Click to collapse
Ok stupid question.
Since your on bootloader v4 since your on crga
1) did you flash any firmware with 4 in like N950FXXU"4"CRGA because you can't flash bootloader v. (3 or 2 or 1)
2) Have you tried the latest Odin?
3) have you flashed the CSC file (this one erases files and set up like new phone) instead of home_CSC?
And since Knox is Tripped there is no going back! So hope your company doesn't mind a rooted phone.
You'll need combination files that's for N950FXXU4CRGA (pay attention to the 4) if your going to flash combination files.
Sent from my SM-N950F using Tapatalk
Samsunguser932 said:
I can't boot at all..
Click to expand...
Click to collapse
What is current status?
Havethi you read esf mount Error fix in gen section sticky thread by me?
BluePhnx said:
Ok stupid question.
Click to expand...
Click to collapse
dr.ketan said:
What is current status?
Havethi you read esf mount Error fix in gen section sticky thread by me?
Click to expand...
Click to collapse
You 2 read my post entirely, I am limited on only stock recovery and stock ROM, I can't even boot stock ROM. So that fix if it's the data one is useless
Samsunguser932 said:
You 2 read my post entirely, I am limited on only stock recovery and stock ROM, I can't even boot stock ROM. So that fix if it's the data one is useless
Click to expand...
Click to collapse
Ok I have read it, you can't use that method as you are not allowed to flash twrp and that method needs to to have twrp installed.
Last option before sending service station
Flash pit file and tick re partition
You can find pit file by extracting csc tar file
dr.ketan said:
Ok I have read it, you can't use that method as you are not allowed to flash twrp and that method needs to to have twrp installed.
Last option before sending service station
Flash pit file and tick re partition
You can find pit file by extracting csc tar file
Click to expand...
Click to collapse
I tried that, I got many solutions I want to try first, I still don't know what exactly went wrong for my device to do this, What will Service station say to "System Status: Custom", I can't reset it to official when I can't boot.
dr.ketan said:
Ok I have read it, you can't use that method as you are not allowed to flash twrp and that method needs to to have twrp installed.
Last option before sending service station
Flash pit file and tick re partition
You can find pit file by extracting csc tar file
Click to expand...
Click to collapse
The pit file included into the CSC file don't will be used while the firmware flash process?
Don't be afraid to hit the "Thanks" button if someone helped you. It don't hurts