edit: on a whim I looked at the heimdall command line options and saw "close pc screen" as one of the arguments and tried that and it booted up perfectly!!!!! So relieved it was something that simple!
I got my S4 last night and immediately tried to root it after I got it, I read up on some stuff (not new to rooting, I've rooted multiple devices in the past) and attempted to flash TWRP via Odin but then it said it failed for some reason, I tried again and it failed. I figured everything was fine until I rebooted and got "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again." I tried to connect it to my old Windows XP pc (my main pc runs Arch Linux) and kies kept saying "connecting" no matter how many times I tried to make it connect or reinstall the drivers.
I can get to download mode and I'm trying to flash the stock firmware via heimdall but it's taking forever to uncompress the image. I got the images from here: http://forum.xda-developers.com/showthread.php?t=2258628
I tried to flash cf-autoroot with heimdall in hopes that it would restore my bootloader but it wouldn't flash because it said it was missing an XML file.
I think I'm just missing the bootloader/recovery image but I'm not sure. Am I heading in the right direction?
If you have root and still have access to the phone when u turn it on flash cwm recovery via Odin or if Ur phone turns on nd have root then download goomanager nd you can install twrp with that app with no problems
Sent from my SGH-M919 using xda premium
im having the same issue...
i am flashing Modem_UVUAMDL.tar and philz touch 5.08.5-jfltetmo as recovery, OUDHS jfltetmo also, but nothing is working
i was running infamous 4.0 ROM, flashed the cyanogenmod nightly and somehow everything exploded and now the only thing on my screen is the SGS4 stock image... it wont boot into recovery mode only download.
i am on an OSX using heimdall and i do not ever have access to a PC!
icecreamwithyou said:
im having the same issue...
i am flashing Modem_UVUAMDL.tar and philz touch 5.08.5-jfltetmo as recovery, OUDHS jfltetmo also, but nothing is working
i was running infamous 4.0 ROM, flashed the cyanogenmod nightly and somehow everything exploded and now the only thing on my screen is the SGS4 stock image... it wont boot into recovery mode only download.
i am on an OSX using heimdall and i do not ever have access to a PC!
Click to expand...
Click to collapse
Did you find a fix I have the same issue but I do have a pc?
brando56894 said:
edit: on a whim I looked at the heimdall command line options and saw "close pc screen" as one of the arguments and tried that and it booted up perfectly!!!!! So relieved it was something that simple!
I got my S4 last night and immediately tried to root it after I got it, I read up on some stuff (not new to rooting, I've rooted multiple devices in the past) and attempted to flash TWRP via Odin but then it said it failed for some reason, I tried again and it failed. I figured everything was fine until I rebooted and got "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again." I tried to connect it to my old Windows XP pc (my main pc runs Arch Linux) and kies kept saying "connecting" no matter how many times I tried to make it connect or reinstall the drivers.
I can get to download mode and I'm trying to flash the stock firmware via heimdall but it's taking forever to uncompress the image. I got the images from here: http://forum.xda-developers.com/showthread.php?t=2258628
I tried to flash cf-autoroot with heimdall in hopes that it would restore my bootloader but it wouldn't flash because it said it was missing an XML file.
I think I'm just missing the bootloader/recovery image but I'm not sure. Am I heading in the right direction?
Click to expand...
Click to collapse
I just recently purchased a rooted S4 and I downloaded a ROM from this site that wasn't compatible with my S4 and flashed it (BIG mistake I know now). So now I can't start up my phone. I read here that I should wipe out the divalk cache/cache and restart (didn't work). Reset to factory settings and reboot (didn't work). Download the TWRP flashable zip and flash it from the Recovery memory then reboot (didn't work). Now I'm really worried. Can you please help me?
Warrior1016 said:
I just recently purchased a rooted S4 and I downloaded a ROM from this site that wasn't compatible with my S4 and flashed it (BIG mistake I know now). So now I can't start up my phone. I read here that I should wipe out the divalk cache/cache and restart (didn't work). Reset to factory settings and reboot (didn't work). Download the TWRP flashable zip and flash it from the Recovery memory then reboot (didn't work). Now I'm really worried. Can you please help me?
Click to expand...
Click to collapse
What does it do when you boot up?
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.
Hey All,
I have a current predicament on my hands.. I have a N7105T that I had rooted and I noticed my TWRP was out of date..So I decided to update it using an app I downloaded from the play store (Name has been lost to me) but it downloaded it and installed and updated..But I had presumed that something had gone wrong because It didn't reset on its own, so i reset it myself and after that it wouldn't load and was stuck on the boot screen (Where it tells you what phone you have)
I looked on here and found a solution, downloaded Odin and a restore TAR for my particular model..after that successfully worked I then decided to try and install a new rom on my phone...Well that was a bad idea, I did as was instructed wiped the data etc: clean installation..but for some reason it kept failing to install..
So now I cant even get into the Boot Manager and all its showing is that there was a problem with the firmware and to use Kies to fix it up, So I downloaded a stock rom from sammobile and followed the instuctions to load the rom onto my phone from another topic on this site...
It is now constantly failing when I try and use Odin to load the rom...It just hangs and then says failed in red.
I am stessing because I really need my phone and I know I should have just left it working but I like to try and experiment but unfortunately it has backfired on me.
I have the samsung drivers installed and I have one stock rom for my particular phone but I am in the process of downloading an older version.
My Provider is Telstra.
I hope I have provided enough info and not rambled on too much.
Regards
Justin
I had the same problem with you... I've learned that I shouldn't trust thing I don't download my self and read what it says.....
Anyways what I would suggest is go to twrp website and download the .tar of the recovery and use Odin to install it on to your phone and see if you can get into the recovery mode
(Volume down+power or volume up+home+power)
If that does the work install Kies onto your phone and under tools -》firmware upgrade and initialize (note you should only do this as your last resort since it'll put a boot loader that you won't want onto your phone
Gl
Sent from my SGH-I317M using Tapatalk
lil-devil said:
I had the same problem with you... I've learned that I shouldn't trust thing I don't download my self and read what it says.....
Anyways what I would suggest is go to twrp website and download the .tar of the recovery and use Odin to install it on to your phone and see if you can get into the recovery mode
(Volume down+power or volume up+home+power)
If that does the work install Kies onto your phone and under tools -》firmware upgrade and initialize (note you should only do this as your last resort since it'll put a boot loader that you won't want onto your phone
Gl
Sent from my SGH-I317M using Tapatalk
Click to expand...
Click to collapse
Ok...First I thank you for the help with Twrp
I have installed a stock rom from sammobile, I have got Twrp working but I have some problems atm
1. I cannot copy files onto my External SD Card
2. My Phone Memory is showing as Minus Storage
3. My Sim Card cannot be read from my phone.
Would you know of any fixes for these issues
Really wish I can help you but my best suggestion is to use Kies and do the firmware upgrade. ....
Sorry~
Sent from my SGH-I317M using Tapatalk
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
Hi,
I have been trying to add a new rom to my phone after the latest update removed root and messed up my phone (still booted and worked, just not the same)
So far, I have downloaded odin 3.07, TWRP 2.8.10, and have Cyanogen 11 M12 but i cant get to the point where i can install anything.
What am i missing? I have drivers installed, but ODIN doesn't find it.
Thoughts?
Thanks,
Chris
Are you able to get into download mode? Was your phone recognized by Odin before the update?
Updated:
Tried a different computer...Odin flash TWRP, then was able to add Cyanogen....weird but now it works!
Likely was the computer issues
Old
yes, i can access download mode...but from there, Odin doesnt see it (only while phone is on)
im on stock recovery as well (<3e) KOT49H.I747UCUFNJ1
Chris
Sounds like a driver problem. You're using at least Odin 3.07?
Try uninstalling all of the drivers and and let Windows install its own drivers.