I flashed the 4.4 kernel from this thread ( http://forum.xda-developers.com/showthread.php?t=2521427 ) to gain TWRP (I had CWM) in order to install CM11. But now TWRP can't mount anything: whenever I try to wipe or install a zip, it fails to mount system, dalvik cache and data. I tried using droidstyle's method of a stock restore in this thread ( http://forum.xda-developers.com/showthread.php?t=1238070 ) but Odin only displays "<OSM> All threads completed. (succeed 0 / failed 0)" immediately after pressing start and nothing else. What do I do? I really need to fix my phone.
Anubis_2541 said:
I flashed the 4.4 kernel from this thread ( http://forum.xda-developers.com/showthread.php?t=2521427 ) to gain TWRP (I had CWM) in order to install CM11. But now TWRP can't mount anything: whenever I try to wipe or install a zip, it fails to mount system, dalvik cache and data. I tried using droidstyle's method of a stock restore in this thread ( http://forum.xda-developers.com/showthread.php?t=1238070 ) but Odin only displays "<OSM> All threads completed. (succeed 0 / failed 0)" immediately after pressing start and nothing else. What do I do? I really need to fix my phone.
Click to expand...
Click to collapse
odin is a finicky program. have you installed the samsung USB drivers? tried multiple USB ports on your computer? different USB cables? (i know people usually recommend the OEM cable but mine didnt work a lot of the time, a motorola one worked for me pretty much flawlessly every time, think it came with a droid x or somethin)
also about the TWRP brick, that's actually happened to me before, i usually dont bother with it and when i had this phone i actually just flashed kitkat using cwm
skepticmisfit said:
odin is a finicky program. have you installed the samsung USB drivers? tried multiple USB ports on your computer? different USB cables? (i know people usually recommend the OEM cable but mine didnt work a lot of the time, a motorola one worked for me pretty much flawlessly every time, think it came with a droid x or somethin)
also about the TWRP brick, that's actually happened to me before, i usually dont bother with it and when i had this phone i actually just flashed kitkat using cwm
Click to expand...
Click to collapse
Used a factory S4 cable and it worked. Thanks for the help. No idea where my Fascinate cable went.
Related
Hi, so I've been flashing for a while now on my phone and my friend wanted to root his phone so i agreed to help him out. After flashing multiple files in order to get cwm recovery and just get everything working, the phone started to act up.
Here are the problems:
Phone can boot into stock recovery but i cant flash anything from it
i wiped data/factory reset many times.
i tried to install the cwm kernal by applying update from sd card (I followed the install custom recovery instructions from here: http://wiki.cyanogenmod.org/w/Install_CM_for_i777) but when into recovery to flash, 2 red signs come up saying "E: Failed to verify whole-file signature" and "E: signature verificatoin failed" after this is just aborts the process
i tried download mode, but none of my computers recocgnize the phone (2 computers) i have tried all usb ports, reinstalling usb drivers, different usb ports many times but all have failed
if i try to boot, the phone just stays stuck on the Samsung galaxy s2 logo (no triangle? even though its rooted)
my only option is to hang out in recovery, i have a bunch of files saved to an external sd card but i cannot access that from stock recovery
any help would be appreciated, Thanks
You can not install any unsigned files with stock 3e recovery, as you have discovered. That is normal behavior.
I don't know why performing a wipe data/factory reset from 3e recovery does not clear the phone to boot normally. It should. But since it won't...
You will need to get the phone recognized by a computer, and then flash with Odin, or you could try flashing with Heimdall command line. I would suggest that you flash the full stock plus root I777UCKH7 (2.3.4), and then when it boots normally into the system, install Mobile Odin Lite or Mobile Odin Pro, and use that to flash a custom kernel. You can find the stock firmware in the Download Repository, and the basic directions in my guide, both of which are linked in my signature.
creepyncrawly said:
You can not install any unsigned files with stock 3e recovery, as you have discovered. That is normal behavior.
I don't know why performing a wipe data/factory reset from 3e recovery does not clear the phone to boot normally. It should. But since it won't...
You will need to get the phone recognized by a computer, and then flash with Odin, or you could try flashing with Heimdall command line. I would suggest that you flash the full stock plus root I777UCKH7 (2.3.4), and then when it boots normally into the system, install Mobile Odin Lite or Mobile Odin Pro, and use that to flash a custom kernel. You can find the stock firmware in the Download Repository, and the basic directions in my guide, both of which are linked in my signature.
Click to expand...
Click to collapse
The hardest part about this is getting my computers to recognize the phone
i guess i shouldve mentioned this earlier, i attempted to flash in Odin but it was stuck on zImage so i unplugged it
before i flashed in odin, i used to be able to boot into the phone like touchwiz and whatnot, now it just gets stuck on the samsung galaxy s ii boot logo
This is now [Solved}! thanks for the help creepyncrawly! i figured it out after doing some more reasearch online. apparently, youre not supposed to use the charger wire that came with the device since samsung doesnt want to waste their time on creating a good enough cable for this kind of stuff. so i grabbed some random cable that i found in my house, hooked it up and BAM! both of my computers were able to detect my phone just finished flashing bone stock on the phone thanks
I noticed in your post that you tried everything but another cable. But I'm glad you got it working. I had the same problem before too. Cables are finicky little things.
Sent from my SGH-I777 using xda app-developers app
Hi Guys,
I hope someone can help as I'm at the point where I feel like cutting my face off with a spoon!
This is the standard GT-i9100
My mate bought a Galaxy S2 from someone who flashed CM on the phone, it was working but then apparently it started freezing up and after a reboot it did not go past the initial boot screen that displays the triangle with the exclamation mark.
Obviously I can't boot into the phone to see what version of CM it was but I can get into CWM which I can see is running version 6.0.1.9
From what I can tell it was CM 10 ICS.
I tried some of things I found on the forum but it didn't help
-wipe data/factory reset option in CWM
-wipe cache
-wipe dalvik cache
Note: when you get into CWM it straight away brings up E:Can't mount /cache/recovery/command
it also has logs in the same directory it cant mount or open
I figured to try get back up and running I should just try flash a newer version of CWM so that I can load cm11 kitkat on the device.
So I tried to use Odin3 v1.85 and CWM-KitKatCompatible-i9100.tar
But when I tried to flash it, it just hands at NAND Write Start!!
I uninstalled Kies (but not the drivers) turned off AV and firewall but still cant get it right.
I also tried odin 1.83 and v1.3
I'm not sure what to try next or if I'm even going in the right direction, should I be trying to load a different CWM at this point or do I have to do something else first since the phone seems like its soft bricked?
Any help will be greatly appreciated!
Try mounting USB Storage from CWM Recovery and see if your sdcard appears on your PC.
If yes, you can flash a CWM compatible with kitkat, wipe data, and flash a cm11 rom
Lysergic Acid said:
Try mounting USB Storage from CWM Recovery and see if your sdcard appears on your PC.
If yes, you can flash a CWM compatible with kitkat, wipe data, and flash a cm11 rom
Click to expand...
Click to collapse
I tried that and it still didn't work, something on CWM is actually corrupt.
I actually think the partitions are corrupt but there also maybe an issue with my Samsung drivers on windows 8.1 I should have done it on my win7 PC as I have now hard bricked the phone when trying to repartition with a pit file.
Apparently my local Samsung service centre can fix it and out the original ROM on but they are going to charge the equivalent of $25 which I guess is acceptable since the phone was basically free.
Gex010 said:
I tried that and it still didn't work, something on CWM is actually corrupt.
I actually think the partitions are corrupt but there also maybe an issue with my Samsung drivers on windows 8.1 I should have done it on my win7 PC as I have now hard bricked the phone when trying to repartition with a pit file.
Apparently my local Samsung service centre can fix it and out the original ROM on but they are going to charge the equivalent of $25 which I guess is acceptable since the phone was basically free.
Click to expand...
Click to collapse
Have you tried to flash the Stock ROM with Odin? That's always the best thing to do when everything else fails
Hi I am currently having a problem with my Galaxy S4 (NC5) I am running 4.4.2 with HyperDrive 18.1 installed. Yesterday I noticed that I couldn't access the web over data so I decided to bring my phone back to stock ROM to see if that would fix the problem.
I Did a factory reset and wiped cache. After that I tried flashing a stock ROM I found online via Odin. Odin got to system and then kept failing every single time. I am now stuck at a Samsung logo with a open lock that says custom. I have an External SD and I have a backup of when I first got the phone.
What can I do ?
Chrome1909 said:
Hi I am currently having a problem with my Galaxy S4 (NC5) I am running 4.4.2 with HyperDrive 18.1 installed. Yesterday I noticed that I couldn't access the web over data so I decided to bring my phone back to stock ROM to see if that would fix the problem.
I Did a factory reset and wiped cache. After that I tried flashing a stock ROM I found online via Odin. Odin got to system and then kept failing every single time. I am now stuck at a Samsung logo with a open lock that says custom. I have an External SD and I have a backup of when I first got the phone.
What can I do ?
Click to expand...
Click to collapse
Try a different USB cable, different USB port, and if that fails, redownload the TAR
npjohnson said:
Try a different USB cable, different USB port, and if that fails, redownload the TAR
Click to expand...
Click to collapse
Okay so I follow the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2735172 and used the files provided. I flashed the full wipe via Odin with the PIT file. And I was able to boot successful. After that I rooted my phone via Towel root and then I installed safestrap. However in safe strap it says
E: Unable to mount '/system'
E: Unable to mount '/systemorig'
I tried installing Hyperdrive 19 and when it started to install it got to 30% and then came right back to the safestrap menu.
Chrome1909 said:
Okay so I follow the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2735172 and used the files provided. I flashed the full wipe via Odin with the PIT file. And I was able to boot successful. After that I rooted my phone via Towel root and then I installed safestrap. However in safe strap it says
E: Unable to mount '/system'
E: Unable to mount '/systemorig'
I tried installing Hyperdrive 19 and when it started to install it got to 30% and then came right back to the safestrap menu.
Click to expand...
Click to collapse
Huh. Make sure you are using 3.75 for the SCH-i545. Not for the S5
I would use the full wipe TARs and try it. That should clear all the error issues up you are seeing. A few of us have the seen the system mount issue that you describe and so far the only way I've found to get rid of them is to use the full wipe TARs.
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
William31 said:
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
Click to expand...
Click to collapse
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
mattnmag said:
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
Click to expand...
Click to collapse
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
William31 said:
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
Click to expand...
Click to collapse
Cool. Glad you got it fixed.
As you know, you can root with GhettoRoot from this thread: http://forum.xda-developers.com/showthread.php?p=57238246
Then can install Safestrap from this thread: http://forum.xda-developers.com/showthread.php?p=51616723
I've never used Safestrap because I can use regular custom recoveries like CWM and TWRP. I'm still on a 4.1.2 unlocked bootloader and currently running TrentsKKRom, Build #2...which is 4.4.2 based with stock kernel, so I think it would work with Safestrap.
I'd recommend reading through the Safestrap thread thoroughly and asking questions there to make sure you get everything installed correctly. I've read that with Safestrap, you need to make a backup of your Stock ROM first and save it somewhere safe, like to your computer and on your external sd card...so you can easily restore it if needed. (I'd also make a backup of the ESF in Safestrap if it lets you, then save it somewhere safe).
After you are rooted with Safestrap, you'll have to flash custom ROM's over the stock slot in Safestrap, as the other slots apparently don't work. Again, you're limited to only using Touchwiz ROM's with the stock kernel because of the bootloader still being locked.
Check out TrentsKKRom and Alliance build 30 . (I personally like Trent's build 2 best with the S5 clean theme). I've also found Trent's ROM to be really smooth without UI lagging, the Bluetooth works good with no stuttering, and it pairs well with my Sony Smartwatch 3. (Edit: If you do try Trent's ROM, you may need to install a couple apps.... Chainfire's Supersu app to control your root permissions (at least I needed to), and the FolderMount app to fix a KitKat internal storage mounting issue).
Have fun!!
Hope you guys can help me, I ran outta ideas. Here's my problem: I was on a cm12s based rom, downloaded latest SlimRom and when I was installing (using twrp recovery) it gave me an error: "Unable to mount /system". I read some stuff on different websites and ended up trying with another rom and other Recovery's (philz and cwm) but none of that helped. After that I downloaded stock rom to install via Odin but Odin doesn't recognize my phone, I installed Samsung USB drivers, installed kies, tried with different usb cables, tried with different computers but Odin simply doesn't recognize it, now my phone is stuck at download mode since I don't have os installed, is there any way to fix unable to mount system problem? Or to make Odin recognize my phone? I would really appreciate your help.
anyone?
JoseLoarca97 said:
Hope you guys can help me, I ran outta ideas. Here's my problem: I was on a cm12s based rom, downloaded latest SlimRom and when I was installing (using twrp recovery) it gave me an error: "Unable to mount /system". I read some stuff on different websites and ended up trying with another rom and other Recovery's (philz and cwm) but none of that helped. After that I downloaded stock rom to install via Odin but Odin doesn't recognize my phone, I installed Samsung USB drivers, installed kies, tried with different usb cables, tried with different computers but Odin simply doesn't recognize it, now my phone is stuck at download mode since I don't have os installed, is there any way to fix unable to mount system problem? Or to make Odin recognize my phone? I would really appreciate your help.
Click to expand...
Click to collapse
Haven't you taken Nandroid Backup? Am sure atleast Backup should help you boot your phone back
Regarding Odin, i usually avoid it because of same issues of detection. It seems to be very sensitive. However i would suggest borrowing an original cable from someone and see if that works. First and the last time i used ODIN, I tried atleast 4 non samsung cables which never worked with ODIN. The Samsung original cable did the trick for me.