New $600 paper weight - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

So my brand new SD care went corrupt while I had a lot of programs running from it... By means of Link2SD app I put system files on there too and now I get
E:failed to mount /system (Invalid argument)
I can't seem to fix this problem and it doesn't seem that this problem arises very often because I have found nothing in searching. Any help would be great... I don't want to have to put a hammer to it and then call Asurion for a replacement..... but that does sound fun lol.
I have tried to Odin everything I have in my backups but not sure if any of those are actually the original rom. I have been trying to figure out how to Odin CM or TWRP on to it... or get them install in some form with out the APK. I saw something about them being able to fix the issue.

Have you tried using ODIN and flashing back to a fresh, stock ROM?

I forgot to put all that. I have tried to Odin everything I have in my backups but not sure if any of those are actually the original rom. I have been trying to figure out how to Odin CM or TWRP on to it... or get them install in some form with out the APK. I saw something about them being able to fix the issue.

Our phones do not support CM or TWRP because we have a locked bootloader. You are on a Verizon G900V, right?
Here's a link to a post with stock ROMs you can Flash via Odin. Choose the appropriate one for the version you want and Flash. Make sure you back up anythibg you want to save.
http://forum.xda-developers.com/showthread.php?t=2784880

It doesn't matter what I flash I get the same error. The other things I have found say that the system and/or EFS needs to be re-made so to speak. TWRP has a command that does it and CM allows you to go in though ADB and do it..... That is the best I have found for answers so far. I don't see anything for FlashFire or SuperUser.

Flash using ODIN not FlashFire or anything else.

I have flashed with Odin.... I get no where.... doesn't matter what kernel I use or ROM or anything.... I was saying that the people that have solved this porblem before are using CW or TWRP to access the ADB to send commands for the phone to re-setup the system/EFS

Did you Flash the pit file on the page I linked earlier? That should repartition everything.

Still the same problem

So I just kept flashing tar files from the post above and finally the NI2 took along with the pit file. Thanks for your help @btonetbone

Eventually the NI2 + .pit file being flashed together fixed the problem.

Related

[Q] AT7T GS4 Softbrick help

Hello, and thanks for reading this. I know it's long, but I wanted to be specific.
I got a brand new AT&T Galaxy S4 yesterday, and decided I wanted to run CM. I easily rooted using this
method, but ran into problems in multiple attempts to install CWM. I found out about the MF3 software version, which I have, so I installed safestrap.
In safestrap, I factory reset, installed CM 10.2-20131102.zip
snapshot, and then installed loki-doki.zip as mentioned in this thread (there were some mentions in the xda forums but I can't find the one I was looking at earlier.) The problem is I forgot to make
a new rom slot/partition thing, so I think I wrote over the stock rom.
Now, when I turn on the phone, an option for safestrap comes up. If I choose to not go through safestrap, the screen goes blank black, but the phone stays on until I
hold the power button and it vibrates, indicating a power down. Safestrap's recovery mode still works as expected.
What I've already tried:
1. Factory reset. Nothing changed.
2. Create rom slot for CM, install, and boot (Has since been uninstalled). Nothing changed.
3. manually put stock rom zip into phone. Computer did not recognize device.
4. Use adb to push same stock rom zip onto phone. ADB did not see device.
5. Change PIT via ODIN as per a thread I can no longer locate. Nothing changed.
6. Take a stock rom and flash it from ODIN (I used the PDA, then bootloader, option because I wasn't sure which to select.) Both failed.
Is this something y'all can help me with? What do I do? If you have any ideas, questions, comments, please ask. I know I need more information.
Thanks for the help.
FalseAim said:
Hello, and thanks for reading this. I know it's long, but I wanted to be specific.
I got a brand new AT&T Galaxy S4 yesterday, and decided I wanted to run CM. I easily rooted using this
method, but ran into problems in multiple attempts to install CWM. I found out about the MF3 software version, which I have, so I installed safestrap.
In safestrap, I factory reset, installed CM 10.2-20131102.zip
snapshot, and then installed loki-doki.zip as mentioned in this thread (there were some mentions in the xda forums but I can't find the one I was looking at earlier.) The problem is I forgot to make
a new rom slot/partition thing, so I think I wrote over the stock rom.
Now, when I turn on the phone, an option for safestrap comes up. If I choose to not go through safestrap, the screen goes blank black, but the phone stays on until I
hold the power button and it vibrates, indicating a power down. Safestrap's recovery mode still works as expected.
What I've already tried:
1. Factory reset. Nothing changed.
2. Create rom slot for CM, install, and boot (Has since been uninstalled). Nothing changed.
3. manually put stock rom zip into phone. Computer did not recognize device.
4. Use adb to push same stock rom zip onto phone. ADB did not see device.
5. Change PIT via ODIN as per a thread I can no longer locate. Nothing changed.
6. Take a stock rom and flash it from ODIN (I used the PDA, then bootloader, option because I wasn't sure which to select.) Both failed.
Is this something y'all can help me with? What do I do? If you have any ideas, questions, comments, please ask. I know I need more information.
Thanks for the help.
Click to expand...
Click to collapse
A few things...
CM will not work on SafeStrap as of right now, it's AOSP-based whereas SS currently only supports TouchWiz-based ROMs.
Is your stock ROM-slot intact, or did you flash over it as well? if so move on to the next bullet.
Your need to take these files and use ODIN to flash back to stock MF3 (I don't know what stock files your using) and start from scratch.
Alternatively, you can try to flash a TouchWiz-based ROM (look here) in a ROM-slot other then stock in SafeStrap and see if it works, just don't forget to flash the MF3 modules afterwards.
NighthawkXL said:
A few things...
CM will not work on SafeStrap as of right now, it's AOSP-based whereas SS currently only supports TouchWiz-based ROMs.
Is your stock ROM-slot intact, or did you flash over it as well? if so move on to the next bullet.
Your need to take these files and use ODIN to flash back to stock MF3 (I don't know what stock files your using) and start from scratch.
Alternatively, you can try to flash a TouchWiz-based ROM (look here) in a ROM-slot other then stock in SafeStrap and see if it works, just don't forget to flash the MF3 modules afterwards.
Click to expand...
Click to collapse
I really appreciate the help. I had no idea CM would not work with SafeStrap. Is it possible to get CWM through SafeStrap? If not, I'll just have to do some research to see if I want one of the TW-based ROMs, I've never looked into it before. Actually, just before you posted, I started the Odin flashing in this thread, which seems to be another thread pointing to the same file downloads written by the same guy as the thread you posted. The phone is back to perfect stock; no root, no SafeStrap, still MF3 software version. I'm going to reroot and reinstall SafeStrap, and not be so reckless this time. Thanks again for the help!
No CWM won't run on the locked MF3 bootloader. SafeStrap is "recovery" itself designed specifically for MF3 devices. Just use a TW Rom and br careful!
Sent from my SGH-I337 using Tapatalk
NighthawkXL said:
No CWM won't run on the locked MF3 bootloader. SafeStrap is "recovery" itself designed specifically for MF3 devices. Just use a TW Rom and br careful!
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Do you think you could help me install a ROM? I tried to get GoldenEye, but it didn't work. I made a new ROM slot and didn't change any of the default sizes. Then I activated that ROM slot, wiped the data, and intalled the GoldenEye zip file from the /sdcard folder. The I rebooted, and installed the MF3 modules on the same ROM slot. Then I rebooted again, but all I got was a black screen. I was able to get back into SafeStrap and the stock ROM still works, but what did I do wrong installing GoldenEye?
I deleted and then remade the ROM slot, and tried installing the two files again without rebooting in between, but it didn't change anything. But I did notice the following when trying to install the MF3 modules:
Installing 'sdcard/jflteatt-MF3-modules.zip'..
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Updating partition details...
E:Unable to mount internal storage.
SafeStrap says "Successful," but this text doesn't sound like it. I couldn't find any in-depth tutorial on using SafeStrap, so I'm not sure what to try next.
Thanks for the help.
FalseAim said:
Do you think you could help me install a ROM? I tried to get GoldenEye, but it didn't work. I made a new ROM slot and didn't change any of the default sizes. Then I activated that ROM slot, wiped the data, and intalled the GoldenEye zip file from the /sdcard folder. The I rebooted, and installed the MF3 modules on the same ROM slot. Then I rebooted again, but all I got was a black screen. I was able to get back into SafeStrap and the stock ROM still works, but what did I do wrong installing GoldenEye?
I deleted and then remade the ROM slot, and tried installing the two files again without rebooting in between, but it didn't change anything. But I did notice the following when trying to install the MF3 modules:
Installing 'sdcard/jflteatt-MF3-modules.zip'..
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Updating partition details...
E:Unable to mount internal storage.
SafeStrap says "Successful," but this text doesn't sound like it. I couldn't find any in-depth tutorial on using SafeStrap, so I'm not sure what to try next.
Thanks for the help.
Click to expand...
Click to collapse
All of this is covered in the "SafeStrap" thread.

semi soft bricked i337m

Solace50 said:
is there an odin file that can wipe the device clean as does twrp since for some odd reason i cant flash twrp, i think its due to samsungs bootloader puts on write protection if somethings out of place. though i did before and it worked fine. anywho i can boot into the os but have no functionality. i would assume i can still fix this through odin. i tired pushing a ota tar from my carrier but still did not work. i figure if i can wipe the os clean from the phone then push the OTA again perhaps it would then show offical status again since that would also change the recovery back to stock as well.
Click to expand...
Click to collapse
essentially i need the i337m/m919v pit file "i assume they would be identical" to perform a clean wipe from odin of which i cant seem to find it posted anywhere.
i did however find
http://softwarearab.com/Flash File/SAMSUNG/PIT files for Samsung/i337M/
edit: all is well, least the url is on xda for others who may encounter the same issue. apparently i corrupted the recovery partition or something. after wiping/repartitioning with odin i could get into the stock recovery so i assume twrp should work as well now.
edit: apparently i cant find the delete button and accidentally quoted myself.

[Q] Need some assistance!

Sup you guys,
I may be in a new predicament for myself, so I would like to ask a few questions before I tackle this task. It seems that I've flashed a JB rom on the stock slot of SS, and I thought that I had the NC2 kernel intact to do so. However, all I get is a black screen and then a botched up system partition, a soft brick if you will, on the stock slot. Couldn't mount the system, so wiping anything is out the window. In order to make my phone usable for now, I had to install a rom on Slot 1. All is fine, but the battery drain is a killer, so I would like recover the system partition of the stock slot. Now, I've read a few threads that kind of pertains to my situation and I learned that a pit file flash can recover it back to normal. Can I just flash only the pit through Odin, or are there other steps that I have to do to get this back on track? Any help and guidance would be greatly appreciated.
I need help too
krazyg said:
Sup you guys,
I may be in a new predicament for myself, so I would like to ask a few questions before I tackle this task. It seems that I've flashed a JB rom on the stock slot of SS, and I thought that I had the NC2 kernel intact to do so. However, all I get is a black screen and then a botched up system partition, a soft brick if you will, on the stock slot. Couldn't mount the system, so wiping anything is out the window. In order to make my phone usable for now, I had to install a rom on Slot 1. All is fine, but the battery drain is a killer, so I would like recover the system partition of the stock slot. Now, I've read a few threads that kind of pertains to my situation and I learned that a pit file flash can recover it back to normal. Can I just flash only the pit through Odin, or are there other steps that I have to do to get this back on track? Any help and guidance would be greatly appreciated.
Click to expand...
Click to collapse
I just got into ROMs and safeatrap and such. I started by trying to load them to the stock slot, which failed every time. I then made slots and had 3 ROMs, but the battery life was not good.
So I wanted to put a ROM on the stock slot. This is with nc2 on kitkat. When I went to load a ROM in stock slot, safestrap failed saying it couldn't mount /system. I tried wiping, but there too it said fail to mount /system.
I did "Fix Permissions" and rebooted. I was greeted by the Samsung boot screen, but it froze there. No safestrap, nothing. I recovery booted and the stock recovery says "E:failed to mount /system (Invalid argument)"
So now it seems that no part of my phone can get to /system. I will look into a .pit file and would appreciate guidance as well.
Seems like you have the problem that I had a week ago. I fixed it by flashing a stock tar and the pit file through Odin. Though I wasn't too sure if just flashing pit would repair the system partition (though, I think it would've been fine; I should've just done it with no questions asked), but in my situation, I got a bit more desperate as my problem got sort of worse. Yea, running any rom on any slot other than the stock slot will kill your battery quick. So a reminder, if you have a messed up system partition, do not let the battery die because your phone will be soft bricked and you won't be able to boot up to anything other than Download mode. At that point, I just flashed the stock tar and the pit file just to be on the safe side and start over. After I rooted and installed SS, I went and checked if it was working properly. It did for the most part, but I remember that I was still on slot 1 before my battery died and SS was highlighted that I was still on that slot. I think because of that, it gave me certain errors on some of things I was testing out, but you will be able to install normally on the stock slot again. There are some other issues I have because of that ordeal, but it's not game breaking, so make sure that you're on the stock slot before flashing the files through Odin.
krazyg said:
Seems like you have the problem that I had a week ago. I fixed it by flashing a stock tar and the pit file through Odin. Though I wasn't too sure if just flashing pit would repair the system partition (though, I think it would've been fine; I should've just done it with no questions asked), but in my situation, I got a bit more desperate as my problem got sort of worse. Yea, running any rom on any slot other than the stock slot will kill your battery quick. So a reminder, if you have a messed up system partition, do not let the battery die because your phone will be soft bricked and you won't be able to boot up to anything other than Download mode. At that point, I just flashed the stock tar and the pit file just to be on the safe side and start over. After I rooted and installed SS, I went and checked if it was working properly. It did for the most part, but I remember that I was still on slot 1 before my battery died and SS was highlighted that I was still on that slot. I think because of that, it gave me certain errors on some of things I was testing out, but you will be able to install normally on the stock slot again. There are some other issues I have because of that ordeal, but it's not game breaking, so make sure that you're on the stock slot before flashing the files through Odin.
Click to expand...
Click to collapse
Thanks for the reply. I flashed a stock tar last night since the stock bootloader couldn't mount /system. Not sure which slot was selected in safestrap, I couldn't get back in because it would freeze before safestrap.
I did not use a .pit file (FYI), and am now back on stock ROM.
What I woluld like isto flash a custom ROM, say a debloated, rooted ROM with ODIN. I see they are all zips with folders, not .tar. Maybe I could take out the recovery.img and put it into a ROM's zip and save the zip as a tar and flash it? Would this possibly break my device if it tried to flash a wrong recovery? I don't know.
If anyone has some knowledge of these things, I would appreciate tips.
Why wouldn't you towel root, install SS, and install a ROM?
xdadevnube said:
Why wouldn't you towel root, install SS, and install a ROM?
Click to expand...
Click to collapse
Because I have only been able to get ROMs working on slots 1-4 of SS and not stock slot, so the battery life is terrible. Also, it would be faster and easier just to flash a ROM with ODIN and not have to worry if my version of android has a working root method (thankfully towelroot v3 worked).

[Q] I don't get it

I had to Odin and went back to ncg. I have searched and posted in relevant forums and no answers that work. I am rooted have safestrap and I have flashfire. I would like to go up to the new MOAR rom. For some reason when I try to flash anything with safestrap it fails everytime, just shows updating partitions and then a red failed.
When I try with flashfire I can not see zips on my SD or internal. Everyone says it should work fine. It doesnt. I did repatriation with pit when going to ncg. I try flashing the stock rooted OA8 and it fails. Any help is super appreciated. I did not have trouble when I first got the phone and rooted but I started at OA8 and went to ncg.
Is there no solution?
jhr5474 said:
Is there no solution?
Click to expand...
Click to collapse
Odin back to NCG but using the full wipe tar file found here. Then root again with towelroot. Download supersu from playstore. Update binaries and reboot. Install busybody from playstore and install. Install safestrap. You should be good to go.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
Tulsadiver said:
Odin back to NCG but using the full wipe tar file found here. Then root again with towelroot. Download supersu from playstore. Update binaries and reboot. Install busybody from playstore and install. Install safestrap. You should be good to go.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
Click to expand...
Click to collapse
I have done this 3 times now thinking that I had a bad flash or something. Still I am not able to flash any roms with safestrap. I get failed EVERYTIME! This is with multiple downloads so I know they are not bad downloads. I have also tried using flashfire. I am wondering if I should odin and flash up then back to ncg since the newer ones repartition differently?
jhr5474 said:
I have done this 3 times now thinking that I had a bad flash or something. Still I am not able to flash any roms with safestrap. I get failed EVERYTIME! This is with multiple downloads so I know they are not bad downloads. I have also tried using flashfire. I am wondering if I should odin and flash up then back to ncg since the newer ones repartition differently?
Click to expand...
Click to collapse
it sure can't hurt.
jhr5474 said:
I have done this 3 times now thinking that I had a bad flash or something. Still I am not able to flash any roms with safestrap. I get failed EVERYTIME! This is with multiple downloads so I know they are not bad downloads. I have also tried using flashfire. I am wondering if I should odin and flash up then back to ncg since the newer ones repartition differently?
Click to expand...
Click to collapse
Seems like that pit file messed things up. I've always stayed away from it. I'm guessing you used it with Beantowns full NGC tar. Maybe you should try it again. You could use Misterxtcs this time. Other than that you could try connecting a thumb drive directly to your phone and see if Flashfire can see zips on it. Won't fix anything but it might get you on Moar. I know you've tried a lot of times and this is getting old. I've also heard of people trying different versions of Odin in trying to find one that works for their specific problem.
You could also try connecting to kies to see if their emergency recovery might help.
Edit: everything I read says to leave that pit file alone unless you are bricked. Your idea of flashing a firmware from higher up sounds like a good plan. Maybe OC4.
SOLVED! I bought a crappy SD from geek.Com 128gb put a 4 gb in and I was able to see zips and flash fine with flashfire.
Running themed MOAR and loving it. Thanks guys.

Paying to get this fixed

My s7 edge got stuck at boot screen so i reflashed stock rom and rerooted then restored the backup i had, it said fail because of low memory while restoring the system and now when i try to reflash the stock rom on odin it says model dismatch fail.
If someone could help me fix this I'm willing to pay something decent, but not a whole lot lol
Re-download the stock rom and flash it
Meboyzram said:
Re-download the stock rom and flash it
Click to expand...
Click to collapse
i did that lol thats when it says "model dismatch fail"
Do you have custom recovery?
Do you have a custom recovery?
Do you have the right and the newest Odin Version?
Did you try it with another transfercable or USB-Port?
Do you have the newest samsung drivers?
Did you have any Odin problems like this before?
My suggestion:
Just do a full wipe on your phone. Downlad the newest Odin Version. Get your device into download mode (maybe try different transfercables or USB Ports and the newest samsung drivers) and see if it works now.
If yes, flash the right Bootloader and Modem for your device and then flash the rom you wanted to flash.
If this didnt work, (and you have a custom recovery) try to reinstall the rom without any backups via the recovery at first and check afterwards, if the device is now recognized by Odin.
Good luck
JustAnotherAndroid said:
My s7 edge got stuck at boot screen so i reflashed stock rom and rerooted then restored the backup i had, it said fail because of low memory while restoring the system and now when i try to reflash the stock rom on odin it says model dismatch fail.
If someone could help me fix this I'm willing to pay something decent, but not a whole lot lol
Click to expand...
Click to collapse
I guess you still have twrp installed.
1. Step: go to TWRP and wipe everything except your SD-Card
2. Step: enter download mode on your device and then plug your usb in (maybe try a different usb-port or even another computer, or another usb cable)
3. Step:Flash the newest bootloader & modem in one step.
4. Step: Enter TWRP again and flash the firmware.zip via the installation process
I dont have TWRP, but i got it fixed, somehow my roomate got it, thanks anyways guys
So all he got was my phone to turn on, im still having this model dismatch fail issue..
Maybe You're trying to flash wrong firmware? What model did You buy?(check box) and what firmware did You download?
If nothing works then download 7zip. And remove all files from that tar.md5 file and leave system.img only. And then try reflashing it.
This way no matter what device You connect it should force flash this image file. Although it might be dangerous (a tiny little bit) so first make sure that You have proper firmware for Your model.
ProtoDeVNan0 said:
Maybe You're trying to flash wrong firmware? What model did You buy?(check box) and what firmware did You download?
If nothing works then download 7zip. And remove all files from that tar.md5 file and leave system.img only. And then try reflashing it.
This way no matter what device You connect it should force flash this image file. Although it might be dangerous (a tiny little bit) so first make sure that You have proper firmware for Your model.
Click to expand...
Click to collapse
Yes, I've used these files multiple times before i did what i did, ill give that a try, if it works, i owe you.
If system.img by itself will flash successfully and Your phone won't boot then add slowly more files to that tar file (boot.img, recovery.img etc)
You could also try looking for a pit file for Your phone and then flash it with it. Pit file usually fixes most problems even broken partitions.
And make sure that You put that tar file in AP/PDA.
If nothing above works then send me screenshots of ODIN and the file that You're trying to flash. Maybe I'll notice something. But I hope You'll fix it
JustAnotherAndroid said:
Yes, I've used these files multiple times before i did what i did, ill give that a try, if it works, i owe you.
Click to expand...
Click to collapse
So I tried, and i get some invalid file error
These are the files that are in the AP one
https://gyazo.com/a72785631ad62d412a8c40eb464d3126
I found out my problem, i was still uing the modified version of odin that i used to root my phone

Categories

Resources