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.
Related
hello
i have the following problem,
my phone wont boot into the os
but boots directly into recovery mode
ive tried to go to download mode and try the odin way, but my pc doesnt recognize my phone anymore
i tried installing the samsung drivers and samsung kies
(worked fine before i tried to flash new rom and install recovery cwm)
ive tried to flash another rom, it succeeds to install the rom but still boots in recovery mode
i also tried to install the stock firmware but it says an error: cant open emmc gt-i9001 (bad) seven
i cant try to use recovery 6 because i have no acces to the internal sd card
i use another phone to put the roms in the external sd card
have i overlooked something?
i have read the similar topics, and googled it, but no specific solution to this problem
i think ive tried everything, please help me
Have you tried a factory reset from the stock recovery?
twizzle654 said:
hello
i have the following problem,
my phone wont boot into the os
but boots directly into recovery mode
ive tried to go to download mode and try the odin way, but my pc doesnt recognize my phone anymore
i tried installing the samsung drivers and samsung kies
(worked fine before i tried to flash new rom and install recovery cwm)
ive tried to flash another rom, it succeeds to install the rom but still boots in recovery mode
i also tried to install the stock firmware but it says an error: cant open emmc gt-i9001 (bad) seven
i cant try to use recovery 6 because i have no acces to the internal sd card
i use another phone to put the roms in the external sd card
have i overlooked something?
i have read the similar topics, and googled it, but no specific solution to this problem
i think ive tried everything, please help me
Click to expand...
Click to collapse
try this
forum.xda-developers.com/showpost.php?p=24831012&postcount=1330
thank for trying to help
@bodh
yes i have tried factory reset, it still boots into recovery
@dkmali
i already tried that way
but odin doesnt recognize my phone, how do i get that to work?
twizzle654 said:
thank for trying to help
@bodh
yes i have tried factory reset, it still boots into recovery
@dkmali
i already tried that way
but odin doesnt recognize my phone, how do i get that to work?
Click to expand...
Click to collapse
How did you get into this situation? DId you try flashing something that caused it? What preceded this issue?
calisro said:
How did you get into this situation? DId you try flashing something that caused it? What preceded this issue?
Click to expand...
Click to collapse
it happened when i installed recovery cwm
i still have the problem when i go into recovery mode, i cant get out
i used another pc to make odin work, i used a bootloader and the os got booted
so the issue is sort of fixed.. i just dont go into recovery mode again
appreciate the help!
twizzle654 said:
it happened when i installed recovery cwm
i still have the problem when i go into recovery mode, i cant get out
i used another pc to make odin work, i used a bootloader and the os got booted
so the issue is sort of fixed.. i just dont go into recovery mode again
appreciate the help!
Click to expand...
Click to collapse
I had this problem once to. On my HTC Flyer, nothing I could do to recognize the phone. I had to ditch the HTC Driver and tried every copy of the android drive I could find on XDA. I will see if I can find the file that worked for me. But in the interim you may want to try a few.
BTW I am not an expert. This worked for me and it sounds like the same situation to me. :fingers-crossed:
Here's a question: where'd you get the recovery? http://www.clockworkmod.com/rommanager, i don't see your device as supported. Also, i believe they're called universal naked drivers, that may be of help.
calisro said:
How did you get into this situation? DId you try flashing something that caused it? What preceded this issue?
Click to expand...
Click to collapse
bodh said:
Here's a question: where'd you get the recovery?, i don't see your device as supported. Also, i believe they're called universal naked drivers, that may be of help.
Click to expand...
Click to collapse
downloaded it on this forum in the i9001 section
yeah im trying that driver thing out right now thx
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1 if you havent found them.
and in this thread: http://forum.xda-developers.com/showthread.php?t=2129298, the cwm versions are removed.."CWM 6.0.2.7 is not save to use, you may damage your phone. "
so hopefully you tried these: http://forum.xda-developers.com/showthread.php?t=1843825
I am not a developer or anything & havent read many forums...but while playing with myTouch I did get stuck a few times.
Somethings I cant point out if u wanna try as a layman:
1. can u mount your sd card through recovery?
2. if you can than just pick another rom for your device and put it onto your sd card
3. wipe data & partition, wipe cache, delete davlik. some devices work ONLY with wipe script (for my friend only the wipe script worked)
4. dont use odin. go to cwm recovery & install zip from sd card & choose the rom (the 1 from step 2).
I think that should get u out safely....hope it helps
@bodh
i actually installed a cwm 5 version
maybe thats the cause of the whole problem
@indiankarmas
i did install multiple roms from the sd card, first cm9 then stock rom
but it doesnt really work
how i fixed the problem:
when i flashed cm9 and used the bootloader with odin to pass the recovery mode my phone booted the stock os
installing from the external sd didnt work, i just wiped my phone for nothing
it booted the stock os, i didnt want this but this made my pc recognize my phone
so i transferred the rom and gapps in the internal sd
got back to recovery mode and installed from internal sd
and used the bootloader again to pass the recovery mode
again, i appreciate you guys trying to help me out
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
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!!
I recently tried to install an custom rom onto my note 2, didnt work very well i was unsure what i was doing and never installed an custom recovery. i tried to install the rom using stock recovery and after it said installing it threw out the "no command error" and went straight to stock recovery. Ive done some research on this and all the possible fixes require an computer connection and programs like odin or fastboot my problem is that my phone hasnt been able to connect to my pc for sometime now, it doesnt even detect an connected device.(from download or recovery mode). please let me know if there is anyway to install some sort of fix using stock recovery with an zip file from a sd card. Please if anyone can help me.
Hi, my Galaxy S2 was working great with KitKat that I flashed and then thought why not try a new LiniageOS. That Rom failed to install and I figured I would try an updated TWRP recovery. I tried the newest version and it failed to install. It warned me I had no rom installed on reboot but I rebooted anyway and went back to recovery. No issues until I tried an earlier version of TWRP that failed during install as well and now is in boot loop with no Rom. Can not enter recovery mode either. Can enter download mode but Odin and my computer do not seem to detect my phone when plugged in via usb. Tried 3 usb cables but only one computer available. Samsung usb drivers installed.
Any ideas what to do next.
Thanks!
FarmerDaveo said:
Hi, my Galaxy S2 was working great with KitKat that I flashed and then thought why not try a new LiniageOS. That Rom failed to install and I figured I would try an updated TWRP recovery. I tried the newest version and it failed to install. It warned me I had no rom installed on reboot but I rebooted anyway and went back to recovery. No issues until I tried an earlier version of TWRP that failed during install as well and now is in boot loop with no Rom. Can not enter recovery mode either. Can enter download mode but Odin and my computer do not seem to detect my phone when plugged in via usb. Tried 3 usb cables but only one computer available. Samsung usb drivers installed.
Any ideas what to do next.
Thanks!
Click to expand...
Click to collapse
I have already answered in you other thread:
No Rom and Corrupt Recovery S2 i9100
Hi, my Galaxy S2 was working great with KitKat that I flashed and then thought why not try a new LiniageOS. That Rom failed to install and I figured I would try an updated TWRP recovery. I tried the newest version and it failed to install. It...
forum.xda-developers.com