Related
I have had my GS4 for a few days now. Its rooted and running DarthStalker. When I reboot the phone esp from TWRP it just gets stuck on the GS4 screen. Its most of the time sometimes when I reboot from the screen it fixes it self, Or do a full wipe. Do I have to odin stock again? I got it working by full wiping DarthStalker and reinstalling again.
I had this issue too, i even tried to use cwm and see if that fixed the problem but it wouldnt even boot doing a full wipe, i odined back to stock and rerooted , installed twrp and i have no problems now.
unciviilized said:
I had this issue too, i even tried to use cwm and see if that fixed the problem but it wouldnt even boot doing a full wipe, i odined back to stock and rerooted , installed twrp and i have no problems now.
Click to expand...
Click to collapse
Issue has been experienced here as well. I may reinstall twrp if it continues and re-root if it continues after that. Good to hear its not just me
C.Sweat said:
Issue has been experienced here as well. I may reinstall twrp if it continues and re-root if it continues after that. Good to hear its not just me
Click to expand...
Click to collapse
I dont think it would do any good, after installing cwm i couldnt do anything just boot into recovery. So to get it running i pushed twrp .tar file thru odin but still had to fully wipe everytime i reboot it. So i just odined to stock. I was a little scared as a week before i had hard bricked an S3.
re: bootup issues
unciviilized said:
I dont think it would do any good, after installing cwm i couldnt do anything just boot into recovery. So to get it running i pushed twrp .tar file thru odin but still had to fully wipe everytime i reboot it. So i just odined to stock. I was a little scared as a week before i had hard bricked an S3.
Click to expand...
Click to collapse
Next time you have problems booting up normally or have bootloops for whatever reason, do a "factory reset"
in either cwm or twrp and nine out of ten times after doing that the phone will boot normally.
Misterjunky said:
Next time you have problems booting up normally or have bootloops for whatever reason, do a "factory reset"
in either cwm or twrp and nine out of ten times after doing that the phone will boot normally.
Click to expand...
Click to collapse
it didnt work for me, you even replied to my thread suggesting the same method.
I can't say I've ever been stuck on the Samsung logo, but I can't count how many times I've gotten hung up on the TWRP splash screen. :\
lordcheeto03 said:
I can't say I've ever been stuck on the Samsung logo, but I can't count how many times I've gotten hung up on the TWRP splash screen. :\
Click to expand...
Click to collapse
Yeah i still get that from time to time, still buggy.
Sent from my SGH-M919 using Tapatalk 2
Use this and you won't have anymore problem.http://forum.xda-developers.com/showthread.php?t=2281367
flash the zip in recovery.
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.
As the title says i am trying to install the Saberkat 1.5 rom on my SGH-I317. I am using Philz recovery and i am on the 4.4.2 bootloader. I was running DN3 previously and attempted to do a clean flash to Saberkat 1.5. The installation of the rom goes fine, but when i reboot the phone gets stuck at the Samsung screen for 15+ mintues. I have gone through the Saberkat 1.5 forum post, but i can not find anyone who is having the same issue as myself.
Thank you for any help you may be able to provide me.
Avaleria said:
As the title says i am trying to install the Saberkat 1.5 rom on my SGH-I317. I am using Philz recovery and i am on the 4.4.2 bootloader. I was running DN3 previously and attempted to do a clean flash to Saberkat 1.5. The installation of the rom goes fine, but when i reboot the phone gets stuck at the Samsung screen for 15+ mintues. I have gone through the Saberkat 1.5 forum post, but i can not find anyone who is having the same issue as myself.
Thank you for any help you may be able to provide me.
Click to expand...
Click to collapse
Format everything except the sd card like the system the preload boot dont format the modem tho and then reboot the recovery and it should say if you wanna root hit no the flash the rom like normal and it should work
terpin32 said:
Format everything except the sd card like the system the preload boot dont format the modem tho and then reboot the recovery and it should say if you wanna root hit no the flash the rom like normal and it should work
Click to expand...
Click to collapse
That is what i always do. I format everything except for the sd card, and wipe both caches. I selected no at the root screen, and it gets to the samsung screen and just sits there.
Avaleria said:
That is what i always do. I format everything except for the sd card, and wipe both caches. I selected no at the root screen, and it gets to the samsung screen and just sits there.
Click to expand...
Click to collapse
I had a similar problem when I first tried to flash DN3 v5 4.4.2 (from Skynote Air 4.3 w/4.1.2 bootloader). The problem was that I was using an old version of Philz (5.5) and it would always stick at the "Samsung" screen after the flash. I switched to Philz 6.41 and it worked fine after that. The only problem is that the backups are not compatible (6.41 can't restore 5.5 and 5.5 can't restore 6.41).
I will attempt this when I get home, will advise on the outcome.
jsdad said:
I had a similar problem when I first tried to flash DN3 v5 4.4.2 (from Skynote Air 4.3 w/4.1.2 bootloader). The problem was that I was using an old version of Philz (5.5) and it would always stick at the "Samsung" screen after the flash. I switched to Philz 6.41 and it worked fine after that. The only problem is that the backups are not compatible (6.41 can't restore 5.5 and 5.5 can't restore 6.41).
Click to expand...
Click to collapse
Updated to the latest Philz version, and still gets stuck at the Samsung screen. I am going to flash TWRP and try again to see if that makes a difference.
Avaleria said:
Updated to the latest Philz version, and still gets stuck at the Samsung screen. I am going to flash TWRP and try again to see if that makes a difference.
Click to expand...
Click to collapse
I couldn't get twrp to work I only got it to work on Philz after I formated everything and I mean everything but the modem and the ext sd card then reboot the recovery and then just flash the rom and only the rom first if it doesn't have a boot sound it won't work
terpin32 said:
I couldn't get twrp to work I only got it to work on Philz after I formated everything and I mean everything but the modem and the ext sd card then reboot the recovery and then just flash the rom and only the rom first if it doesn't have a boot sound it won't work
Click to expand...
Click to collapse
I appreciate your help, i havnt had issues with any other rom. Ive done DN3, EzKat, Slimfast, and they all installed and booted up perfectly. I will chuck it up to bad luck and try a different rom.
Avaleria said:
I appreciate your help, i havnt had issues with any other rom. Ive done DN3, EzKat, Slimfast, and they all installed and booted up perfectly. I will chuck it up to bad luck and try a different rom.
Click to expand...
Click to collapse
4.4.2 is the only I had problems with not booting but Philz is the only one I can get every rom to boot
Funny thing, I tried to flash Saberkat 1.0 and it worked fine. Must be something with 1.5 that isn't working
/Close this thread please
Soo.. I decided to install Cynogen Mod 5.1.1 onto the Note 2. And, All worked fine....
But here is an issue. A while back I had to unlock the phone, which required me to install TWRP.. Now the issue is i think i installed it into the Boot instead of recovery.. So now whenever i select ANY power option in TWRP, the phone restarts into TWRP again.. Now, All i had to do was just do a battery pull and all was good.. Except for now..
I tried to update CM through TWRP, but it did something and now the phone boots into TWRP no matter what. I got the Android universal toolkit or whatever running and trying to fix the boot.img, But have been unsuccessful so far..
So, Any help that i can get would be appreciated.
Things I have done:
1. Reflashed boot.img with original.
2. Reflashed recovery with newer twrp
3. Factory reset, formated/
4. Installed backup with 4.4.2 installed still
5. Googled everything
Click to expand...
Click to collapse
AFTER 5 HOURS OF WORK I FIXED IT!
I reinstalled the Original recovery. Then rebooted, and it all worked.. 1:02 AM and tired as heck....
Can you tell me how you installed the original recovery? I did the same thing and now all my phone boots into is TWRP.
Alright.. It's a bit of a Google.. But you gotta find the original recovery for the phone on the web.. The recovery for the gt-n100 or whatever works. So look for that.
J.Naw said:
Alright.. It's a bit of a Google.. But you gotta find the original recovery for the phone on the web.. The recovery for the gt-n100 or whatever works. So look for that.
Click to expand...
Click to collapse
Okay thanks! I managed to find the one for my phone
Hello So i have come to this magical website that has helped me with my issues before to bring up one of my own that i can't seem to find a solution for.
So recently i have rooted my Galaxy S6 using ODIN and what not. And everything went perfect, soon after that i flashed TWRP recovery on my phone so i could get some ROM's. But when i tried booting into TWRP, it gave me a welcome screen telling me to select a language. As soon as i tried making a selection i saw that i wasn't able to Tap nor swipe anywhere or anything really. So i was like....ok let me just flash a different versoin. Booted up to recovery and still ran into the same problem. I can't use the tough interface and idk what to do. Came here for some help
Model : SM-G920P
Version of TWRP : twrp-3.0.2-1
========UPDATE========
So recently i was trying to download exposed and caught myself not knowing what to do at all. I booted into recovery yet again cause i flashed a different version. And same thing happened. I try navigating through TWRP interface and still can't get it to do anything. So i try going back my regular usage of my phone, and then hit problem #2....it kept booting into recovery. And every time i try to reset my phone it just automatically boots into recovery. IDK what to do :/ and would love for someone to help me out.
Reflash the stock rom via odin..u need to be in download mode for this download the rom search it here on sprint xda ... After succesful flash download app call flashify go to recovery flash twrp download the version u havent flashed before im sure u already know the one that didnt worked before ... flash yup it then it will take u too recovery wipe to enter if touch still not works reflash again via odin in download mode then flashify different version of TWRP
Grab the TAR file from here: https://dl.twrp.me/zerofltespr/
Flash via ODIN.
This might not really help the OP. But for anyone whom stumbled upon the same problems. Just do
adb recovery
And the phone should boot into OS normally after stuck on TWRP which the touchscreen is not working
Sent from my Note 3 using XDA Labs
Happened to me as well, I just out smarted them , use an OTG and a mouse and you're golden.
Solved TWRP Touch not Working on S6edge
Hey I had the same problem too. I solved it by getting the right TWRP for my device. You can find it here. Please copy the url "twrp.me/Devices/"
dasboogie said:
Hey I had the same problem too. I solved it by getting the right TWRP for my device. You can find it here. Please copy the url "twrp.me/Devices/"
Click to expand...
Click to collapse
I downloaded the right file, yeah. But I can't run the image on my phone since I can't use the touch screen. Is there another way to run the image on my phone?
Sorry for the late response. Have you tried an OTG cable with a USB mouse. I had to do this just last week. Those OTG cable are lifesavers for this phone.
Hamoonhassan said:
Happened to me as well, I just out smarted them , use an OTG and a mouse and you're golden.
Click to expand...
Click to collapse
It happened to me too, but the problem is to the STOCK ROMS too, when i install them, the touchscreen doesnt work until i use OTG with mouse, help please?