Verizon SCH-I545, rooted NC5 using towelroot, installed safestrap and was running fine on HyperDrive.
Chose to do a full wipe (to try and solve SD card issue) via Safestrap and BOOM - won't boot.
I'm using Odin 3.09, and I've tried (after verifying MD5) both ROMS here: http://forum.xda-developers.com/showthread.php?t=2735172&nocache=1
MD5 checks out, Odin3 connects to phone and "approves" the AP file input. After clicking start It runs through the process until about 3 seconds after it gets to "recovery.img"...
"Complete(Write) operation failed"
Phone says the following
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
System Status: Custom
KNOX Kernel Lock: 0x0
KNOX Warranty Void: 0x0
CSB-Config-LS8: 0x30
Write Protection: Enabled
eMMC Burst Mode: enabled
Start (224,1440)
Happens each time. I've tried 4 USB ports with 2 different USB cables.
KIES was suggested by the boot screen that says there's a firmware issue, but KIES says my phone is not eligible to upgrade.
Help Please!
--UPDATE--
ran PIT file and at least got the samsung broken lock screen, but still no boot, still Odin fail.
--UPDATE 2--
after second boot the samsung screen is no longer, back to KIES screen
--UPDATE 3--
ran PIT again, samsung broken lock. this time it stayed.
Got to Android System Recovery. It says:
Android system recovery <3e>
KOT49H.I545VRUFNC5
and then at the bottom
E:failed to mount /system (Invalid Argument)
#MANUAL MODE #
-- Applying Multi-CSC...
E:failed to mount /system (Invalid Argument)
can't mount '/system/ (Invalid Argument)
E:failed to mount /system (Invalid Argument)
--RESOLUTION--
I used my wife's old Win XP laptop and, with the same files on a flash drive, it worked smoothly. I'm not sure why there's a difference, there just was. Thanks everyone for the help!
zigzampow said:
Verizon SCH-I545, rooted NC5 using towelroot, installed safestrap and was running fine on HyperDrive.
Chose to do a full wipe (to try and solve SD card issue) via Safestrap and BOOM - won't boot.
I'm using Odin 3.09, and I've tried (after verifying MD5) both ROMS here: http://forum.xda-developers.com/showthread.php?t=2735172&nocache=1
MD5 checks out, Odin3 connects to phone and "approves" the AP file input. After clicking start It runs through the process until about 3 seconds after it gets to "recovery.img"...
"Complete(Write) operation failed"
Phone says the following
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
System Status: Custom
KNOX Kernel Lock: 0x0
KNOX Warranty Void: 0x0
CSB-Config-LS8: 0x30
Write Protection: Enabled
eMMC Burst Mode: enabled
Start (224,1440)
Happens each time. I've tried 4 USB ports with 2 different USB cables.
KIES was suggested by the boot screen that says there's a firmware issue, but KIES says my phone is not eligible to upgrade.
Help Please!
--UPDATE--
ran PIT file and at least got the samsung broken lock screen, but still no boot, still Odin fail.
--UPDATE 2--
after second boot the samsung screen is no longer, back to KIES screen
--UPDATE 3--
ran PIT again, samsung broken lock. this time it stayed.
Got to Android System Recovery. It says:
Android system recovery <3e>
KOT49H.I545VRUFNC5
and then at the bottom
E:failed to mount /system (Invalid Argument)
#MANUAL MODE #
-- Applying Multi-CSC...
E:failed to mount /system (Invalid Argument)
can't mount '/system/ (Invalid Argument)
E:failed to mount /system (Invalid Argument)
Click to expand...
Click to collapse
you are flashing the NC5 firmware in odin right if so then keep trying it took me a couple times to get mine to run correctly also tried on a couple different ports and or cables
Tomsgt said:
you are flashing the NC5 firmware in odin right if so then keep trying it took me a couple times to get mine to run correctly also tried on a couple different ports and or cables
Click to expand...
Click to collapse
Correct- trying to flash NC5. Just kind of out of ports and out of cables to try haha
zigzampow said:
Correct- trying to flash NC5. Just kind of out of ports and out of cables to try haha
Click to expand...
Click to collapse
Maybe a bad download? Did you check MD5?
riker147 said:
Maybe a bad download? Did you check MD5?
Click to expand...
Click to collapse
Yup- MD5 checked and passes. Not sure what's going on at this point. I'm going to try and see if I get the same results on another computer
I had something similar happen a while back and it ended up being a formatting issue. I spent days trying to flash various recoveries and backups. It turned out my /system was getting corrupted when I formated with it. I am am mdk using twrp so its a little different than you but somehow my recovery was corrupted and causing the problem. After I managed to update twrp and reformat everything I was good to go.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Thanks everyone for the help!
So I ended up getting everything to work...
All I had to do was take a new microUSB cable to my wife's Win XP laptop that hasn't been turned on in literally 10 years. But it has USB (and a dial up modem which we did not try haha) --- and I put all the files I needed on a flash drive, and it worked first time, no bugs no challenges. VERY odd.
Thanks again!
Related
Hello all,
I'm having a problem getting my phone to boot up when I tried flashing back to stock with Odin 1.37 using .512 pit and SGH-T959UVKA6. I have done it successfully in the past, but the mistake i made this go round is I accidentally checked "re-partition" and it gets stuck on the following error in Android System Recovery 3e:
update media, please wait
E: Can't mount /dev/block/st110
(invalid argument)
E: copy_dbdata_media: Can't mount DBDATA:
your storage not prepared yet. Please use UI menu for format and reboot actions.
copy default media content failed.
Can anyone advise if they have fixed this error in the past? I really need to get this phone back to TMO for under warranty repair and am kind of scared of being screwed here.
Bigbass12 said:
Hello all,
I'm having a problem getting my phone to boot up when I tried flashing back to stock with Odin 1.37 using .512 pit and SGH-T959UVKA6. I have done it successfully in the past, but the mistake i made this go round is I accidentally checked "re-partition" and it gets stuck on the following error in Android System Recovery 3e:
update media, please wait
E: Can't mount /dev/block/st110
(invalid argument)
E: copy_dbdata_media: Can't mount DBDATA:
your storage not prepared yet. Please use UI menu for format and reboot actions.
copy default media content failed.
Can anyone advise if they have fixed this error in the past? I really need to get this phone back to TMO for under warranty repair and am kind of scared of being screwed here.
Click to expand...
Click to collapse
Nothing to big happened. I check repartition every time I never have any problems.
If it shows u anything ur good.
Boot into download mode and odin back again.
Sent from my SGH-T959 using XDA App
Hmm....
I would agree with you except the following:
1. Tried to flash same without checking repartition...failed x3.
2. tried to flash to JI6 with same pit file...failed.
3. tried to change pit file to 513 and tried again with KA6...failed.
4. tried to go back to 512 and JI6...failed.
I have tried several times variants of all those combos...all failed.
Per the following post I am trying this fix:
http://forum.xda-developers.com/showthread.php?t=734475
hopefully going back to JFD will fix this....
****NOTE: When I say "Failed" I mean I get the same message that I got when I first received the error.....
Success
Wow the post really did it! Gotta love XDA...quick someone teach me how to thank around here...lol
My Verizon Samsung Galaxy Note II (also known as i605) was Jailbreak by CASUAL yesterday( http://forum.xda-developers.com/showthread.php?t=2118348 ).After I did some wipe at the new TWRP recovery, I sadly found my i605 won't get pass the first screen while booting, and it just stuck there...
Then I tired to restore the stock to I605VRLI3 by Odin, but it still won't pass the first screen...
The saddest thing is when I press vol up+home+power, the TWRP recovery is gone also! It changed back to the original recovery<3e>:crying::crying:,and under a few lines:
-------------------------------------------------------------
E:failed to mount /system (Invalid argument)
can't mount '/system'(Invalid argument)
E:failed to mount /system (Invalid argument)
# MANUAL MODE #
-- Appling Multi-csc...
E:failed to mount /system (Invalid argument)
can't mount '/system'(Invalid argument)
E:failed to mount /data(Invalid argument)
can't mount '/data'(Invalid argument)
E:failed to mount /data(Invalid argument)
E:failed to mount /system (Invalid argument)
-------------------------------------------------------------
(Photos attached)
I have tried the VRALJB stock,but Odin is fail whild "NAND Write Start"...it can only pass the I605VRLI3,and failed to boot again...
Can anyone help? I would greatly appreciate...I am so stuck...
Regard!!!
Im thinking you some how damaged your memory. I haven't seen this on an Android device
Yet but back in the day I did this to a good number of razor's. If it won't take a flash at all then
Your memory is probably damaged.
I'm not sure about that because it's still loading the bootloader. You should try to odin it
Back to stock. Try the route 666 root injected stock rom. There is something about that rom
It got me unbroken one time. If it will take that rom then just redo the casual and reinstall your
Twrp. And then put what ever rom you want on it.
If it won't. .. then....
If it was me I would take out the insurance. Then I'd drop it off the roof of my house.
krazzykiller said:
Im thinking you some how damaged your memory. I haven't seen this on an Android device
Yet but back in the day I did this to a good number of razor's. If it won't take a flash at all then
Your memory is probably damaged.
I'm not sure about that because it's still loading the bootloader. You should try to odin it
Back to stock. Try the route 666 root injected stock rom. There is something about that rom
It got me unbroken one time. If it will take that rom then just redo the casual and reinstall your
Twrp. And then put what ever rom you want on it.
If it won't. .. then....
If it was me I would take out the insurance. Then I'd drop it off the roof of my house.
Click to expand...
Click to collapse
Yes insurance fraud always option number 1! Really?
op try two things. First, boot back into recovery and do a factory reset. Second if that didn't work you will need to Odin again and make sure it is successful before proceeding. There is a great guide in development if you need help. I recommend the alternate restore file but full stock would be great to.
The root66 doesn't contain boot loader, recovery, kernel anything so it may not be enough
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Yes insurance fraud always option number 1! Really?
op try two things. First, boot back into recovery and do a factory reset. Second if that didn't work you will need to Odin again and make sure it is successful before proceeding. There is a great guide in development if you need help. I recommend the alternate restore file but full stock would be great to.
The root66 doesn't contain boot loader, recovery, kernel anything so it may not be enough
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I tried the I605VRLI3 stock by odin, it pass,.but it won't help, still fail to boot & stop at the first screen...
I remember one of wipe in the TWRP recovery means fully format the system, include the partition. I think I may made a mistake here...
Is there any ideas about re-partition?
Did you include the sch-i605_16gb.pit file in Odin?
SECTION 1B) At:
http://forum.xda-developers.com/showthread.php?p=1181
Also I used this to preserve bootloader unlocked but if you are that hosed you may need to revert back to the official version then go through root and unlock again using CASUAL.
Sent from my SCH-I605 using Tapatalk 2
samsung sch-i605 wont boot pass verizon logo and when boot into recovery it says
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : unknown
Successfully applied multi-CSC.
E: Failed to mount /data (Invalid argument)
Can't mount '/data' (Invalid argument)
any ideas on how to fix this
E: Failed to mount /data (Invalid argument)
E: Can't mount /data/log/recovery_log.txt
My daughters phone has done the same thing. I have tried everything. I can get Odin to put in the Pit file and stock, but it is completely locked up! I have tried everything.
I recently upgraded phones and I'm looking to sell my old gs3. But I had put a costom Rom on it awhile back but during the process at one point I ran into the same problem with the logo screen but I fixed it (I completely forget how) and that was that untill recently when I attempted to return the phone to stock by updating it to 4.3 with kies and that was fine it wasn't until I ran a master reboot that the logo problem resurfaced at that point I tryed to use Odin to flash stock firmware which after doing further research was a terrible idea to do with 4.3 but that's where I'm at my phone does not boot up past the Samsung logo luckily I can still access the dowload mode. I am thinking that I'm going to try flashing a root66 stock 4.3 is that a good idea. Any help would be much appreciated, thank you
Update:I tryed flashing the root 66. I did the newest 4.3 tmobile download i could find which is what fixed it when this happened about a year ago but this time it did nothing. Also when i boot into recovery mode at the bottom under where it says Seccessfully applied multi-CSC it says in red lettering
E:failed to mount /data (Invalid argumen
t)
can't mount '/data'(invalid argument)
E:failed to mount /data (Invalid argumen
t)
E:Can't mount /data/log/recovery_log.txt
imfukked said:
I recently upgraded phones and I'm looking to sell my old gs3. But I had put a costom Rom on it awhile back but during the process at one point I ran into the same problem with the logo screen but I fixed it (I completely forget how) and that was that untill recently when I attempted to return the phone to stock by updating it to 4.3 with kies and that was fine it wasn't until I ran a master reboot that the logo problem resurfaced at that point I tryed to use Odin to flash stock firmware which after doing further research was a terrible idea to do with 4.3 but that's where I'm at my phone does not boot up past the Samsung logo luckily I can still access the dowload mode. I am thinking that I'm going to try flashing a root66 stock 4.3 is that a good idea. Any help would be much appreciated, thank you
Update:I tryed flashing the root 66. I did the newest 4.3 tmobile download i could find which is what fixed it when this happened about a year ago but this time it did nothing. Also when i boot into recovery mode at the bottom under where it says Seccessfully applied multi-CSC it says in red lettering
E:failed to mount /data (Invalid argumen
t)
can't mount '/data'(invalid argument)
E:failed to mount /data (Invalid argumen
t)
E:Can't mount /data/log/recovery_log.txt
Click to expand...
Click to collapse
Hmm . Did you have the device encrypted or anything along those lines?
I'm good dude. I figured it out.
imfukked said:
I'm good dude. I figured it out.
Click to expand...
Click to collapse
Good deal. Care to share in case others run across this issue?
stuck booting at logo screen
hello, my s3 did the same thing keis wouldnt even recognize my phone after rooting and trying to go back to stock rom, found when installing using odin, i installed tar file in boot img i had to download a zip unpack it and istalled kernal tar and bingo solved my problem, hope it helped..
Hello,
Yesterday I unlocked my Galaxy S3 i9300, turned the Wifi on and soon after that my phone started to reboot.
This happened a few times before, but this time it got stuck on the "Galaxy S3" Screen.
So I booted in the Recovery Mode (TWRP 3.1.10) and was planning to wipe the cache partition, but I got the Error that the Recovery is unable to mount Any Partition..
So I cant do anything.
I wanted to ask, why my phone can not mount any Partitions anymore for example (system, efs, cache..).
What exatly is damaged and is it repairable?
I took a picture of the Error Message, but i dont know how to upload it. So I wrote it down.
Hope someone can help me and sorry for my bad english.
Kind Regards.
Error Message:
Updating partition details...
Failed to mount ´/efs´(invalid argument)
Failed to mount ´/cache`(invalid argument)
Failed to mount ´/system´(Invalid argmunent)
Failed to mount ´/data´(Invalid argmunent)
Failed to mount ´/preload´(Invalid argmunent)
Flash stock rom via Odin. Root it and try again.
ArdaCsknn said:
Flash stock rom via Odin. Root it and try again.
Click to expand...
Click to collapse
I am facing same errors. in these type of error i can't flash with odin, can't hard reset, can't install any recovery, i have tried many roms but all failed. i was thinking about to re-partition it but there is a file required for this .pit file. i have searched on google but i didn't find any .pit file for my Samsung S3 SHV-E210k. i have asked in thread but no response from anyone. so i am thinking to threw my phone away. :crying: :crying: :crying:
E30325i said:
Hello,
Yesterday I unlocked my Galaxy S3 i9300, turned the Wifi on and soon after that my phone started to reboot.
This happened a few times before, but this time it got stuck on the "Galaxy S3" Screen.
So I booted in the Recovery Mode (TWRP 3.1.10) and was planning to wipe the cache partition, but I got the Error that the Recovery is unable to mount Any Partition..
So I cant do anything.
I wanted to ask, why my phone can not mount any Partitions anymore for example (system, efs, cache..).
What exatly is damaged and is it repairable?
I took a picture of the Error Message, but i dont know how to upload it. So I wrote it down.
Hope someone can help me and sorry for my bad english.
Kind Regards.
Error Message:
Updating partition details...
Failed to mount ´/efs´(invalid argument)
Failed to mount ´/cache`(invalid argument)
Failed to mount ´/system´(Invalid argmunent)
Failed to mount ´/data´(Invalid argmunent)
Failed to mount ´/preload´(Invalid argmunent)
Click to expand...
Click to collapse
Try to find .pit file and flash it with odin. and then flash your stock rom.
My phone's model is SHV-E210K, i have searched on google but haven't found any .pit file related to my phone.
The sboot.bin file is the bootloader and it is not flashing because the bootloader in the phone is newer than than the bootloader in the ROM, the ROM is not for the phone, try a different USB cable, and/or try different USB ports.
The problem is recovery has gone crazy. Recovery mounts partitions. I've seen this problem a lot with twrp. When it happened to me I flashed the latest official cwmr via Odin. If you have a stock rom on the phone you can flash a stock recovery too. DO NOT FLASH A STOCK RECOVERY IF YOUR ROM ISN'T STOCK/ROOTED STOCK!!!
Beamed in by telepathy
Please help phone stuck on samsung galaxy siii gt-i9300 logo have got cwm recovery and odin need stock rom with pit ?
Try flashing the latest stock ROM with Odin or factory reset.
where do i find stock rom with pit file ? cannot seem to locate
Try flashing without a pit file.
Stock roms are at Sammobile.com, updato.com, or Samsung-firmware.org.
thanks i will try again but i believe i damaged pit when i was trying to root by selecting re partion box, so re flash with pit firmware or replace motherboard ?
tried to flash stock rom and rom with pit no just stuck on startup with samsung galaxy siii gt-i9300 can get into recovery and odin mode.
Try flashing a stock firmware first. If there is any problems with the partitioning odin will tell you.
If odin says you need a pit file that's when you start looking for one.
thanks for all your help, after flashing with stock rom using odin, phone now boot to samsung logo and keeps looping ?
When i trying to root i think by mistake i ticked the re partion box should i get another motherbaord ?
If the phone flashed a stock ROM without a pit file, try performing a factory reset from recovery mode.
I get this message;
E: failed to mount /data (invalid argument)
cant mount to /data (invalid argument)
Manual mode
applying multi csc
applied csc code
succesfully applied csc code
E: failed to mount /data (invalid argument)
cant mount to /data (invalid argument)
E: failed to mount /data (invalid argument)
quick update after factory reset and loading stock 4.3 phone came to life again, i then installed linear rom and rooted with twrp.