So I have had my Fascinate for a couple months now, and before that I had a D1. Never had any problem with it and was always careful about making backups and installing the correct ROMS for my phone. But now I apparently made a big ol' mistake.
When I turn on my phone the SAMSUNG logo pops up and it boots to the samung recovery and I get this message.
E:Cant' mount /dev/block/stl11
(Invalid argument)
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
#MANUAL MODE#
E:Cant' mount /dev/block/stl11
(Invalid argument)
E:Cant' mount /dev/block/stl11
(Invalid argument)
I can use the update.zip to load into CWM and that works but I get this message.
E:Cant' open /cahe/recovery/log
When I try to install a .zip I get this.
Copying files...
E:Failure at line 4:
copy_dir PACKAGE:system: SYSTEM:
Installation aborted.
or
Copying files...
Failure at line 2:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
if I try to restore from a backup it gets to the
Restoring cache part and hangs up
I cant seem to load into DOWNLOADING (bootloader?) for Odin or adb.
It was working fine last night and I tryed Kaosinate's alpha Froyo last night and I got that to load and install fine. When I was done testing it out I tryed to restore to the back up I just made. I think that the kernel that goes with is ROM was a Voodoo lagfix one, and when I restored my old ROM it would boot up completely fine but the touchscreen us totally unresponsive.I tryed to do a full data/cache wipe and then restoring again and I still got the same problem. I then try to install a different rom and it got stuck on some screen with alot of text on it when it was booting. I had to do a battery pull and thats when I got to this point.I guess my question is. Did I brick my phone?
I love this problem I have done it many times now you have to get a d101 and flash back to Odin and put your phone in download mode by turning it off hold down on the volume and plug in your USB cable and have Odin open
Sent from my SCH-I500 using XDA App
BlackHoleSlam said:
I love this problem I have done it many times now you have to get a d101 and flash back to Odin and put your phone in download mode by turning it off hold down on the volume and plug in your USB cable and have Odin open
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
THANK YOU MISTER GUY ON THE INTERNET!
I admit to all noobish actions on my part.
No its not noobish it just different I came from a OG Droid also and I have encountered this many times where with my og Droid I would have just restored and error fixed
Sent from my SCH-I500 using XDA App
So I'm trying to install update.zip in recovery to get to clockwork. Problem is its not letting me install it, I'm getting the following error:
E:Can't mount /dev/block/vold/179:9
(no such file or directory)
E:Cant mount SDCARD:update.zip
Ive tried various downloads, and 2 different SD cards still no luck. Also tried various Odin's too.
Should I try to flash to stock then start over? I was running a Voodoo kernel and did a fixed lagfix(odd typing that) now I'm stuck. This really has me puzzled.
By the way i cant boot to android either
Thanks for all the help and awesome forum!
Well I'm back to stock now, but at least its not a brick
if anyones curious or has this problem i used the adrynalyne.us/files/kernels/DI01package3.tar.md5 to flash the stock rom.
So I installed CWM 6.0.3.2 today on my S4 i9505, and when I go into CWM recovery, I get the following errors:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
This makes me unable to flash any custom roms, wipe any data. In other words, it makes CWM not work.
I've tried formatting my SD card, but still get the same error.
I've tried googling this over and over for the past couple months, every couple weeks, but have had 0 luck. So here I am, asking for XDA's help.
XDA, how can I fix this?
You can the a look there http://forum.xda-developers.com/showthread.php?t=2279579 in the thread ( look at the last 10 pages ) you can find 6.0.3.3 , that flash with Odin and see if your problem is fixed.
If not you can test TWRP recovery. ( flash with Odin too )
http://forum.xda-developers.com/showthread.php?t=2265588
GT-I9505 / Nexus 4 Tapatalk
Tylog said:
You can the a look there http://forum.xda-developers.com/showthread.php?t=2279579 in the thread ( look at the last 10 pages ) you can find 6.0.3.3 , that flash with Odin and see if your problem is fixed.
If not you can test TWRP recovery. ( flash with Odin too )
http://forum.xda-developers.com/showthread.php?t=2265588
GT-I9505 / Nexus 4 Tapatalk
Click to expand...
Click to collapse
I'll try that now. I think I tested TWRP a month ago, and had the same problem. I'll look into it now, thanks!
Good luck
GT-I9505 / Nexus 4 Tapatalk
Tylog said:
Good luck
GT-I9505 / Nexus 4 Tapatalk
Click to expand...
Click to collapse
No luck man Back to stock rom now. Again. For the 5th time. D:
OK, so here is the backround...This is my very first Android device (S4 MK2 4.3) ever. I been on the Iphone since standing in line for the original release, so I have absolutely experience with Android at all.
I got my phone and Rooted it on day one. I'm on the stock ROM. Day two I decided to so a Wifi Hotspot Mod by replacing the .odex and .jar files. On reboot, I discovered I had soft bricked my phone when it got stuck on the yellow Sprint screen. I gave my self a quick crash course, and fixed the issue by flashing stock MJA with Odin 3.7 and then OTA update to MK2, then re-rooted.
My question is to do with the Wifi hotspot mod. I have found a huge amount of information out there, but there seems to be conflicting information as to if I can actually do this with the 4.3. Could someone please confirm if there is a hotspot mod that is compatible with the MK2 4.3 and maybe guide me to some info?
Thanks in advance for your help.
You can try this :
http://forum.xda-developers.com/showthread.php?p=48590490
It's a zip file just flash it through a custom recovery.
Sent from my Nexus 5 using Tapatalk
BIGSAMDA1ST said:
You can try this :
http://forum.xda-developers.com/showthread.php?p=48590490
It's a zip file just flash it through a custom recovery.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This link above, post 337.
Outstanding, thanks for the quick replies!
My next question is about stock recoveries. I was trying implement the Clockwork recovery mod. When I started ROM Manager, the only installation file listed was for Sprint S4 jfltespr. My confusion was with the jfltespr. I was expecting to see one for MK2 or MJA. Is the jfltespr like a catch all for any Sprint phone?
Jfltespr is the sprint gs4.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Jfltespr is the sprint gs4.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Awesome! Thanks for the the quick helpful responses and being NOOB friendly I'm sure I will be back.:laugh:
newest problem
Sorry to post another problem so soon, but I'm having problems backing up using clockworkmod 6.0.4.4
So I did the clockworkmod install through ROM Manager. When I select to Backup Current Rom it boots me into recovery mode. Once there it tries to mount the sd card. It counts down from 20 to 1 and finally times out. At the end of that I get this: Error processing rom manager script.
I'm not sure what I'm doing wrong here. The micro sd is formatted in FAT32
Any ideas?
Install goomanager.
Then use THAT to install custom recovery (CWM or TWRP).
Once installed open it.
Then Hit Menu button and select “Install OpenRecoveryScript” (jfltespr is for Sprint). Once installed it will tell you it's done.
You can then use GooManager to 'reboot to recovery'.
Rom Manager uses a 'temp recovery' that often doesn't work.
leaderbuilder said:
Install goomanager.
Then use THAT to install custom recovery (CWM or TWRP).
Once installed open it.
Then Hit Menu button and select “Install OpenRecoveryScript” (jfltespr is for Sprint). Once installed it will tell you it's done.
You can then use GooManager to 'reboot to recovery'.
Rom Manager uses a 'temp recovery' that often doesn't work.
Click to expand...
Click to collapse
K, I did that but when I try to manually boot into recovery it hangs on the teamwin screen for a little while. Eventually it launches the GUI and I can initiate a backup, but this is what happens:
E:unable to mount '/data'
E: unable to recreate /data/media folder
updating partition detals...
E:unable to mount '/data'
E:unable to mount internal storage
E:unable to mount/data/media during gui startup.
running boot script...
finished running boot script.
E:unable to mount /data/media/twrp/.twrps when trying to read settings f
E:unable to mount '/data'
E:unable to mount '/data'
E:unable to mount '/data'
E:updating partition details...
E:unable to mount '/data'
*total number of partitions to back up: 3
*total size of all data: 2073mb
*available space 28041mb
[backup started]
*backup folder: /external_sd/twrp/backups/1e0bf818/1970-01-08--02-24-1
backing up system...
breaking backup file into multiple achives...
*generating md5...
*md5 created.
E:unable to mount '/data'
My progress bar gets maybe 1/4 of the way complete and then the message at the top of the screen changes to
Backup Complete
Failed
I'm not sure what I'm missing. I tried this twice with the same outcome.
I did just notice that it added 1.9 gigs of data to my card. The files are
boot.emmc.win
boot.emmc.win.md5
system.ext4.win000
system.ext4.win001
system.ext4.win000.md5
system.ext4.win001.md5
Does this mean that it was actually successful event though I had the unable to mount and failed messages???
In twrp >advanced fix permisions.
Also check the size of storage you have left on your ExternalSD.
You may also want to flash Reverpats repacked TWRP v. 2.6.3.1 in recovery - now that you have recovery.
Grab it here
Put on your ExternalSD, boot to recovery, install zip from externalsd.
Then reboot 'RECOVERY'.
Repair permissions, reboot phone completely. Then back to recovery and try backup again.
chunter001 said:
I did just notice that it added 1.9 gigs of data to my card. The files are
boot.emmc.win
boot.emmc.win.md5
system.ext4.win000
system.ext4.win001
system.ext4.win000.md5
system.ext4.win001.md5
Does this mean that it was actually successful event though I had the unable to mount and failed messages???
Click to expand...
Click to collapse
you're missing like half of your stuff. you can also fix permissions in rom manager if you have that instead of twrp. i'm far from expert status, but maybe try changing your default backup format (in the backup and restore part of recovery mode) to tar?
Could also try PC Odin the recovery tar(s) either twrp, CWM or Philz (CWM based). They're here just search.
leaderbuilder said:
Could also try PC Odin the recovery tar(s) either twrp, CWM or Philz (CWM based). They're here just search.
Click to expand...
Click to collapse
Sorry, but I'm completely new to this. Would I just get the .tar for the recovery and put it to PDA just like a stock ROM?
yes
Just can't get it to work. Here is question, since I already have custom recovery I just can't save a backup...is there another way to backup the ROM? Maybe to my computer, then I could just transfer it to my externalSD?
So this is pretty much where I am stuck
Ok, so I got the phone rooted, custom recovery installed, and the one mod that I really needed flashed. I am unable to backup my phone with either Clockwork or TWRP. Both tell me that data can't be mounted.
Is there another way that I could save a nandroid backup to my computer, then move it to my external sd card to be flashed through the custom recovery if needed?
Any help would be appreciated.
Hey, hope someone here can help me out.
So I got TWRP working, I wiped my phone (and didn't make a backup, believe me I feel incredibly stupid for this) and now I'm trying to get a custom ROM to run on it. Problem is I keep getting these errors when I try installing them.
detected filesystem ext4 for /dev/block/platform/msm_sdoc.1/by-name/
unmount of /system: Invalid argument
unmount of /system failed: no such volume
E:Error executing updater binary in zip '/external_sd/cm-12-20-150417-NIGHTLY-trltetmo (1).zip'
Error flashing zip 'external_sd/cm-12-20150417-NIGHTLY-trltetmo (1).zip'
Updating partition details
E: Unable to mount '/system'
I've been looking for a solution for a few hours now and can't find anything. Any help would be super awesome.
Thanks
Potatochip Man said:
Hey, hope someone here can help me out.
So I got TWRP working, I wiped my phone (and didn't make a backup, believe me I feel incredibly stupid for this) and now I'm trying to get a custom ROM to run on it. Problem is I keep getting these errors when I try installing them.
detected filesystem ext4 for /dev/block/platform/msm_sdoc.1/by-name/
unmount of /system: Invalid argument
unmount of /system failed: no such volume
E:Error executing updater binary in zip '/external_sd/cm-12-20-150417-NIGHTLY-trltetmo (1).zip'
Error flashing zip 'external_sd/cm-12-20150417-NIGHTLY-trltetmo (1).zip'
Updating partition details
E: Unable to mount '/system'
I've been looking for a solution for a few hours now and can't find anything. Any help would be super awesome.
Thanks
Click to expand...
Click to collapse
have you tried a different recovery ?
Guys im very sure most of you here are rooted. So i really need your help. My device is Note 4 N910G. but is already deadboot. no ODIN no Recover not Responding anymore but only detected as Qualcom device in computer. I need someone of my same phone model to flash unbrick creator via custom recovery. then kindly upload the file because it will automatically create unbrick files for phones that is flashed with it. its unbrick creator.zip then i need the uploaded files so i could flash it through my sd card using Win32 disk image loader. after it i will put the sd card on my deadboot phone and try if it goes to download mode. So i really need you guys to help me cause ive not yet exhausted the possibilities yet. i Havent tried this solution yet so if theres anyone whos willing to help could you kindly do it for me. Id really appreciate the thought of it. Thank you very much!!