Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Taxmaster said:
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Click to expand...
Click to collapse
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
elesbb said:
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Hello! I actually downloaded Philz touch recovery in both .zip and in .md5, so that is what I intend to go with. The issue is how I push it using adb, as I believe I need to install something in order to do so, but I don't have any administrative privileges! This is what's preventing me from running ODIN in the first place!
Can you confirm that I can push using adb without installing anything?
Thank you! - Taxmaster
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Monkz said:
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Click to expand...
Click to collapse
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Taxmaster said:
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Click to expand...
Click to collapse
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
lordcheeto03 said:
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
Click to expand...
Click to collapse
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
elesbb said:
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
Click to expand...
Click to collapse
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Taxmaster said:
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Click to expand...
Click to collapse
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
lordcheeto03 said:
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
Click to expand...
Click to collapse
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Taxmaster said:
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Click to expand...
Click to collapse
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
elesbb said:
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
Click to expand...
Click to collapse
I think I just need to accept that fact that I have been had and that the only thing I can do is wait until I'm home to use ODIN. Absolutely asinine in my opinion, however it seems the only logical conclusion at this point.
If anyone else cares to chime in with suggestions, please let me know!
-Taxmaster
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
coolastar said:
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
Click to expand...
Click to collapse
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
Same, TWRP just has too many problems.
CWM is much more reliable.
Sent from my SGH-M919 using xda premium
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
If you were using TWRP 2.6.0, that could have been the problem. I reverted back to 2.5.0.2 and like many others, have had no issues. If you had a TWRP backup, that might have fixed it early on.
Hi,
I tried to downgrade my Telus SGS3 to 4.1.1 but Odin failed at 75% and now my device is bricked. I can get to download mode easily. I tried Kies, but could never connect to the device even though I have all drivers installed correctly. I tried to reflash 4.2.2 but also failed the same way. I then tried to flash Cyanogen using CWM. I first tried to flash CWM using heimdall but also failed (error claiming interface failed). I then converted the recovery.img to .tar.md5 (7zip to tar and md5sum to md5) and flashed using Odin which went fine and was able to boot into CWM. I put both the ROM and gapps on the SDCARD and flashed from CWM but I got an error stating that (cwm failed to verify whole-file signature). I even tried to flash using adb sideload which seamed to finish 100% but when rebooting it returned the same signature error.
Please any advice. What bothers me is that I have done this many times before and never went into any issue. If I could at least make Kies connect to recover the damn thing.
PS: my GS3 is SGH-i747M and I downloaded the ROMs from sammobile and update-samsung
Thanks
SOLVED ...
I do not get it! I used a Samsung Galaxy Nexus cable and "voila" it worked from the first time!
goldfinsh said:
Hi,
I tried to downgrade my Telus SGS3 to 4.1.1 but Odin failed at 75% and now my device is bricked. I can get to download mode easily. I tried Kies, but could never connect to the device even though I have all drivers installed correctly. I tried to reflash 4.2.2 but also failed the same way. I then tried to flash Cyanogen using CWM. I first tried to flash CWM using heimdall but also failed (error claiming interface failed). I then converted the recovery.img to .tar.md5 (7zip to tar and md5sum to md5) and flashed using Odin which went fine and was able to boot into CWM. I put both the ROM and gapps on the SDCARD and flashed from CWM but I got an error stating that (cwm failed to verify whole-file signature). I even tried to flash using adb sideload which seamed to finish 100% but when rebooting it returned the same signature error.
Please any advice. What bothers me is that I have done this many times before and never went into any issue. If I could at least make Kies connect to recover the damn thing.
PS: my GS3 is SGH-i747M and I downloaded the ROMs from sammobile and update-samsung
Thanks
Click to expand...
Click to collapse
BTW, when I flashed CWM, the menu I got is:
reboot system now
apply update from ADB
apply update from sd card
wife data/factory setting
wipe cache partition
and there is no "Install zip from sd card"!!!
Ok so today I tried to flash TWRP on my Note II today through the GooManager app from the Play Store, it went well and then asked to reboot. After the reboot it is stuck on the SAMSUNG Galaxy Note II screen in all white, with a black background. I know I should try to flash the stock firmware with Odin but when in download mode (which it can enter but not the Recovery or OS) it is not detected. I have tried on a Windows XP, Vista and 7 computer with no luck on each. I have downloaded Heimdall for my Mac and again it is not detected. I have read that there could be an eMMC problem or something like that but I was working just fine like two minutes ago. Again it will not boot into either the Recovery or OS after sitting there for minutes, I can upload a photo if need be but I dont think its that hard to imagine. Oh I was on OmniRom the release the one before the one released yesterday with CWM. I wanted to update but since i was on CWM i needed to flash TWRP and it was not downloading for whatever reason so i went with the app method, which has worked before on my Xperia X10 so i was semi confident, anyway I'm rambling now... Again if anyone would be able o help me I will buy you a beer! wait I can't I'm underage, well when I turn 21 I'll buy you a beer!
Thanks!
Yoshi5005 said:
Ok so today I tried to flash TWRP on my Note II today through the GooManager app from the Play Store, it went well and then asked to reboot. After the reboot it is stuck on the SAMSUNG Galaxy Note II screen in all white, with a black background. I know I should try to flash the stock firmware with Odin but when in download mode (which it can enter but not the Recovery or OS) it is not detected. I have tried on a Windows XP, Vista and 7 computer with no luck on each. I have downloaded Heimdall for my Mac and again it is not detected. I have read that there could be an eMMC problem or something like that but I was working just fine like two minutes ago. Again it will not boot into either the Recovery or OS after sitting there for minutes, I can upload a photo if need be but I dont think its that hard to imagine. Oh I was on OmniRom the release the one before the one released yesterday with CWM. I wanted to update but since i was on CWM i needed to flash TWRP and it was not downloading for whatever reason so i went with the app method, which has worked before on my Xperia X10 so i was semi confident, anyway I'm rambling now... Again if anyone would be able o help me I will buy you a beer! wait I can't I'm underage, well when I turn 21 I'll buy you a beer!
Thanks!
Click to expand...
Click to collapse
Your phone was on OMNI ROM with CWM recovery, you installed TWRP via goo manager and since then it's not booting up, right ?
I think the easiest option now is to flash stock via ODIN. Did you ever connect your phone using USB ?
Are you trying with the cable that came along with this phone ? I know samsung drivers can get messy, try installing KIES it will automatically install the appropriate drivers, then exit KIES and start odin with Admin right(right click-> Run as Administrator).
If you have a full back-up and if Odin works try flashing CWM first via ODIN and the reboot in to recovery and restore your backup.
ciphercodes said:
Your phone was on OMNI ROM with CWM recovery, you installed TWRP via goo manager and since then it's not booting up, right ?
I think the easiest option now is to flash stock via ODIN. Did you ever connect your phone using USB ?
Are you trying with the cable that came along with this phone ? I know samsung drivers can get messy, try installing KIES it will automatically install the appropriate drivers, then exit KIES and start odin with Admin right(right click-> Run as Administrator).
If you have a full back-up and if Odin works try flashing CWM first via ODIN and the reboot in to recovery and restore your backup.
Click to expand...
Click to collapse
I tried installing Kies, closing it with Task Manager and then using both Odin v3.07 and v1.8.5. With both they never detected my phone, and in Heimdall it still does not recognize my phone. And yes that is exactly what happened.
Oh and Windows finally said something and it said that the usb device connected cannot be recognized...
Sorry fixed it!
Yeah so... The USB cable I was using was broken or whatever so I changed it and yeah its detected, thanks anyway!
Glad to know it's fixed.
Sent from my SGH-T889 using xda app-developers app
Hi everyone,
Just wanted to give you a few details before I get into where I'm at now.
I decided for the first time to root and flash CM11 on my Samsung Galaxy S4 and everything went flawlessly so I wanted to try it on my S3 T999. I had a lot of trouble this time around every step of the way. I tried using CM's installer that they have but every time I would switch the USB mode from MTP to PTP using the CM OneClick app, my phone would no longer get recognized AT ALL through my computer, so I factory reset it through Samsung's settings and decided to just do it using ODIN and a guide here help me along.
So I started over and followed http://forum.xda-developers.com/showthread.php?t=2563955 this guide. Downloaded ODIN, I downloaded TWRP v2.5.0.0 because it states the dt2mo users might have problems with 2.6+. Followed the rest of the guide, everything went well. Then I downloaded cm-11-20140210-SNAPSHOT-M3-d2tmo.zip and Gapps for CM 11.
Currently:
Booted into recovery, backed up to my SD card, did a factory reset, then went to install the above snapshot. It failed saying error executing updater binary in zip. I tried to restore my backup I just made and rebooted and it just sits at the Samsung logo. Not sure where to go from here. Someone in another thread mentioned to flash the latest twrp using ODIN but I tried to connect to ODIN when in download mode and the S3 doesn't get recognized.
EDIT: Two more things. I did an Advanced Wipe once. Dalvik Cache, System, Data, and Cache. And After failing to flash, when I try to reboot, TWRP states I lost root and asking if I wanted it back...
follow the instructions in this thread and flash the root 66(pre-rooted firmware) firmware for your T999:
http://forum.xda-developers.com/showthread.php?t=1949687
T999_UVUEMJC
Official JB Firmware - Latest JB 4.3 Firmware
Cobra281 said:
follow the instructions in this thread and flash the root 66(pre-rooted firmware) firmware for your T999:
http://forum.xda-developers.com/showthread.php?t=1949687
T999_UVUEMJC
Official JB Firmware - Latest JB 4.3 Firmware
Click to expand...
Click to collapse
I'm currently downloading root 66 for T999 but I have tried to connect through ODIN before and it is no longer recognizing my phone. Nothing happens. I had this problem all day yesterday after messing with the usb connections that I mentioned in my first post.
EDIT!:
It seems as though already having connected the phone to the computer and THEN booting into download mode recognized the phone and started downloading the drivers.
3itmn said:
I'm currently downloading root 66 for T999 but I have tried to connect through ODIN before and it is no longer recognizing my phone. Nothing happens. I had this problem all day yesterday after messing with the usb connections that I mentioned in my first post.
EDIT!:
It seems as though already having connected the phone to the computer and THEN booting into download mode recognized the phone and started downloading the drivers.
Click to expand...
Click to collapse
also i presume that you're using the stock\original Samsung USB cable that came with the S3?
Cobra281 said:
also i presume that you're using the stock\original Samsung USB cable that came with the S3?
Click to expand...
Click to collapse
Thank you for linking me to that firmware! That worked, I'm back up and running 4.3. I would still like to be able to flash CM11 but I don't know what I did wrong. Should I have went with the latest TWRP or used something else?
3itmn said:
Thank you for linking me to that firmware! That worked, I'm back up and running 4.3. I would still like to be able to flash CM11 but I don't know what I did wrong. Should I have went with the latest TWRP or used something else?
Click to expand...
Click to collapse
not a problem. personally, i like TWRP, especially since it installs automatically when you download the GooManager app
Hello everyone,
I'm relatively new at rooting and just so happen the note 10.1 2014 is my first guinea pig.
First off, I have successful rooted my note via Odin 3.09 with CF-autoroot with autorootp600mj4.tar.md5 and stockrecoverymj4.tar.md5. Rootchecker shows that it's rooted.
Next I installed Titanium backup and back up and then uninstall all 5 files of Knox securities.
Next I installed GooManager and installed TWRP from OpenSourceRecovery option and then rebooted with recovery.
So now is where the problem starts. Whenever I tried rebooting into recovery, I keep getting the Android recovery system (with red triangle sign and a laying down android picture).
Here's some method that I did to try and fix this.
1. Manually reboot recovery ( Did not work) goes into Android recovery system again.
2. I reinstalled TWRP again using GooManager, still doesn't work.
3. Downloaded the appropriate TWRP .tar files for Samsung galaxy note 10.1 2014 from TWRP main site and flash with Odin. I got a Pass!. Then when I do a reboot recovery, it goes into the Android recovery system again.
So far I don't know what I'm doing wrong. I've checked to make sure every step is correct, especially when I was rooting (E.g. making sure USB debugging is enabled, open source is enable, and so on)
I've tried to find my solution via google but to no avail. If you have any suggestions, it will be greatly appreciated. Thank you.:good:
I had same issue. You have to install it with Odin.
Sent from my SM-P600 using XDA Premium HD app
Simply flash via Odin, but untick " Auto Reboot " within odin before flashing.
Reboot manually into recovery , you will get a permanent TWRP
Got it
Thank for reassuring me that it can be done.
I found out the problem. The tar files from TWRP that I donwloaded was the wrong version. TWRP version was openrecovery-twrp-2.6.3.3-lt03wifiue.img. And I used that to flash on Odin and it worked thereafter. I hope this will help other people who have similar issues.