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..
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
Okay, so here's the deal -
The phone was previously running stock rooted 2.2. I backed up the stock kernel, then used SGS Kernel Flasher to flash the Voodoo kernel. I decided to go back to the backed up stock kernel and used SGS Kernel Flasher to do that, and that's where everything went to hell. Now the phone will go through the T-Mobile and Galaxy S boot animations, but after that finishes, it'll just move straight to a black screen. The capacitive buttons light up and respond to the touch, but other than that, nothing happens.
I'm still able to get the phone into both download mode and the stock 3e recovery. However, when I boot into 3e recovery, I get a bunch of errors that say the following:
-- movi_checking done! . . .
E:Can't mount /dev/block/stl11
(Invalid argument)
E:Can't mount CACHE:recovery/command
update media, please wait
E:Can't mount /dev/block/stl10
(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.
E:Can't mount /dev/block/stl11
(Invalid argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/stl11
(Invalid argument)
I've tried to used Odin to re-flash the stock firmware several times using several different methods, (this included), but Odin almost immediately gives me a big giant FAIL! every time I try. I've also tried it with the re-partition button checked, and when I do that it seems to start working, but then gets stuck on set-partition.
So, any ideas? Thanks in advance.
TL;DR: Phone goes through usual boot animations, then gets stuck at black screen but capacitive buttons light up and respond to touch. Using Odin to reflash stock firmware not working. Plz halp.
Okay, well, just in case anyone happens to find themselves in the same position I was in, here's how I fixed it:
Opened up Odin, and tried to reflash the Voodoo kernel. It failed and sent me to that pc ! phone screen. Kept Odin open and just hit start again and it went through. Got a voice that said something about insufficient internal storage I think? Then the phone just booted up and all is back to normal.
Next time disable voodoo lagfix from recovery before going back to stock kernel.
Sent from my SGH-T959 using Tapatalk 2
Alex9090 said:
Next time disable voodoo lagfix from recovery before going back to stock kernel.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I realized that was the problem after.
Question - so now the phone still has voodoo lagfix, but it's back on the stock recovery. Is there any way to get Clockwork back? I already tried reflashing the Voodoo kernel, but for whatever reason, it didn't flash CWM with it.
What do you mean it still has voodoo? Check what kernel version you have on your phone by going into settings. If you have stock recovery then most likely your using stock kernel now. You might be talking about voodoo folder on your sdcard, well it stays there until you delete it.
I'm 90% certain I still have Voodoo lagfix enabled because the last thing I flashed before it started working again was this kernel in Odin. But, like I said, it didn't flash CWM with it for whatever reason. I haven't flashed anything since.
In the settings menu, it says 2.6.32.9 under Kernel version. The phone's running the stock KA6 build at the moment.
Thanks for the help, by the way.
Okay, so I managed to get Red CWM back. I used Voodoo Toggle Reboot to disable it, reflashed the Voodoo kernel, and it put Red CWM back on there.
So, now I guess my only question is, can I use Red CWM to flash other roms? I'll make sure to disable Voodoo Lagfix before I do this time.
Computar said:
Okay, so I managed to get Red CWM back. I used Voodoo Toggle Reboot to disable it, reflashed the Voodoo kernel, and it put Red CWM back on there.
So, now I guess my only question is, can I use Red CWM to flash other roms? I'll make sure to disable Voodoo Lagfix before I do this time.
Click to expand...
Click to collapse
Yes, you can. Make sure when you disable voodoo, let the phone reboot so it can convert the partition back to rfs.
Got everything up and running and put CM7 RC2 on there. Thanks!
I have a GT-I9100M from Bell in Canada. My phone is broke and I've spent the last 24 hours trying to fix it with no avail
I was running the stock ICS rom from Bell. I rooted the phone and removed all the Bell bloatware and that was it.
Yesterday I came across a Rom that had the S3 version of Touchwiz so I decided to try it out - Salman ICS ROM for Galaxy S2 i9100! [TouchWiz UX][S Voice][GS3 ROM]
The rom installed perfectly and when it restarted, it stopped at the Samsung Galaxy boot screen. I attempted to go into recovery mode and it couldn't.
It would go into download mode. So I tried to flash the stock bell ICS rom - I9100MUGLD3_I9100MBMCLD3_BMC_www.samsdroid.com. It flashed with no issues but when it rebooted - back to the boot screen I go.
I flashed a CF kernal so that I could get into CWM and attempt to wipe it. It kept hanging on formatting /data.
I came across this guide - http://forum.xda-developers.com/showthread.php?t=1449771 and followed the steps and got no where.
Is my phone completely dead and if it is not - how do I get it back in working condition?
Help!!:crying:
When you flashed Bell's stock ROM from the guide thread, could you reach the recovery mode screen? I had the same problem and I simply did a factory reset after I flashed the stock ROM.
After I tried to flash my stock firmware with ODIN
I get stuck at Android System Recovery <3e>
and get these errors:
E: failed to mount /cache (no such file or directory)
E: Cant mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Cant open /cache/recovery/recovery_kernel_log
E:failed to mount /efs (No such file or Directory)
E:failed to mount /cache (no such file or directory)
E:cant mount /cache/recovery log
E:cant open /cache/recovery log
and as you can imagine the list goes on..... and when I hit reboot system now - it just freezes at the Samsung i9100 boot screen.
AAARRGGG
I did some more reading and someone suggested trying a Frankenstein rom KK5 as it does a complete wipe of the data partition on the phone. When I tried this, it does stuck on datafs.
I believe that my phone is broken
kmacsouris said:
I did some more reading and someone suggested trying a Frankenstein rom KK5 as it does a complete wipe of the data partition on the phone. When I tried this, it does stuck on datafs.
I believe that my phone is broken
Click to expand...
Click to collapse
looks like you have hit the eMMC brick, you could try to flash a pit file, and flashing it with repartition activated... This its the only thing you could try, before sending it off for repair
Best regards
Sendt fra min GT-I9300 med Tapatalk2
try to find a Stock ICS which does a full wipe. Usually the first edition of stock ICS
of each region does that.
Dear friend i understand your fear and i wan t to share with you my research, my trouble came for downgrading from ics to GB and now i have the red letters with the e cant mount **** , so i found that installing this rom (XXKH3) with the Phone Bootloader Update filed checked could fix it.
The original post is in spanish so if you need it it is here.
Scroll down until ERROR: E: Can't mount cache
http://www.taringa.net/posts/celulares/14623579/samsung-galaxy-S2---downgrade-ICS-a-Gingerbread.html
But on this post the link to XXKH3 is broken so i found this other link on english with the link working
http://www.theandroidsoul.com/how-to-install-xxkh3-on-samsung-galaxy-s-2-ii-i9100/
I'll try this thing in a couple hours when the download finish due to my 1.5 mb internet and i'll let you know any new,
Good luck
Hello
I had installed CM 11 4.4 on my Galaxy S2. Today I decided to downgrade it to 2.3.x so I used Odin and took stock 2.3.4 ROM with PIT/PDA/PHONE/CSC.
At the installation , there was a error in the phone - data 0 error (or something like that, I didnt remember). After the installation process in Odin, the phone stuck at Samsung logo. I can go into the Download Mode. Now I cant flash any ROM because I have errors in Odin. I tried to use the OneClick tool but it dont work. Its my first phone brick so idk what should I do. Please help
This is a error after I flashed 2.3.4 :
E:failed to mount /data (Unknown error:0) E: install_application_for_customer:Cant mount / data your storage not prepared yet, please UI menu for format nad reboot actions, copy application failed
I repaired this error but I still cant boot into the phone menu. It stuck at the boot Samsung logo. Wipe data/cache is not the fix. I tried different ROMs and kernels.
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