I have a bit of a situation, I have the AT&T Galaxy s4, and I able to boot into it properly, it's running the Goldeneye ROM, all my apps are working, and I don't have the triangle, or the padlock custom logo. In other words my phone is working great, except for one thing. I ran triangle away, which I am beginning to think was a mistake, and ever since then, while the phone itself works great, I am absolutely unable to get into recovery mode at all. The phone acts like it's going to go into recovery, then boots normally. This would not be particularly bothersome, except I would like to be able to back up my phone in the event of something happening with it, which has happened once before. I've searched the forums, and everything I have come up with has solutions for a phone that is bricked, or otherwise won't boot, which does not apply to me. My phone works, and works well, I just want to be able to back the darn thing up, and have a recovery in case of emergency, or worse, I get bored and want to change roms.
dsly4425 said:
I have a bit of a situation, I have the AT&T Galaxy s4, and I able to boot into it properly, it's running the Goldeneye ROM, all my apps are working, and I don't have the triangle, or the padlock custom logo. In other words my phone is working great, except for one thing. I ran triangle away, which I am beginning to think was a mistake, and ever since then, while the phone itself works great, I am absolutely unable to get into recovery mode at all. The phone acts like it's going to go into recovery, then boots normally. This would not be particularly bothersome, except I would like to be able to back up my phone in the event of something happening with it, which has happened once before. I've searched the forums, and everything I have come up with has solutions for a phone that is bricked, or otherwise won't boot, which does not apply to me. My phone works, and works well, I just want to be able to back the darn thing up, and have a recovery in case of emergency, or worse, I get bored and want to change roms.
Click to expand...
Click to collapse
Why don't you just download goomanager and install TWRP open script, or ROM manager and install clock work recovery?
When going into recovery (volume up+home+power) continue to hold the volume up+home once you feel the phone vibrate. If you hold the power to long it'll just cause it to boot normally. Make sure you're not holding power too long lol.
Sent from my SGH-I337 using XDA Premium 4 mobile app
I tried ROM manager (I actually have to pro version, I purchased it a couple phones back) and it was showing that TWRP AND Clockwork were installed on the phone, but the phone will not boot into either. It shows the galaxy s4 logo, blue print that says recovery booting, then boots normally, Goldeneye rom has a boot to recovery option, the same thing happens, I even downloaded a boot to recovery app and ran that, same thing. It's like the recovery is there, but just will not open.
Br4nd3n said:
Why don't you just download goomanager and install TWRP open script, or ROM manager and install clock work recovery?
When going into recovery (volume up+home+power) continue to hold the volume up+home once you feel the phone vibrate. If you hold the power to long it'll just cause it to boot normally. Make sure you're not holding power too long lol.
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
dsly4425 said:
I tried ROM manager (I actually have to pro version, I purchased it a couple phones back) and it was showing that TWRP AND Clockwork were installed on the phone, but the phone will not boot into either. It shows the galaxy s4 logo, blue print that says recovery booting, then boots normally, Goldeneye rom has a boot to recovery option, the same thing happens, I even downloaded a boot to recovery app and ran that, same thing. It's like the recovery is there, but just will not open.
Click to expand...
Click to collapse
How about "dd"method using terminal emulator. I do understand it uses the same partition but give it a shot.
sent from a I337 MF3 S4
If ADB Terminal emulator doesn't work than I'm assuming somehow your recovery partition is broke. You may need to flash back to the stock amdl firmware through Odin.
Sent from my SGH-I337 using XDA Premium 4 mobile app
jball said:
How about "dd"method using terminal emulator. I do understand it uses the same partition but give it a shot.
sent from a I337 MF3 S4
Click to expand...
Click to collapse
I am going to be honest, as i've never had an issue remotely like this before, I am completely unfamiliar with what the "dd" method in terminal emulator is. I am more than willing to look it up, but honestly I am not even sure what parameters I would use to search that.
dsly4425 said:
I am going to be honest, as i've never had an issue remotely like this before, I am completely unfamiliar with what the "dd" method in terminal emulator is. I am more than willing to look it up, but honestly I am not even sure what parameters I would use to search that.
Click to expand...
Click to collapse
It's hidden in here http://forum.xda-developers.com/showthread.php?p=46798778
Related
Got a replacement Vibrant today and it will not boot into recovery with vol up/dwn/power buttons, any ideas? I booted my first Vibrant daily into recovery, this one won't do it.
Have you tried Quick Boot in the market?
SugarMouth said:
Got a replacement Vibrant today and it will not boot into recovery with vol up/dwn/power buttons, any ideas? I booted my first Vibrant daily into recovery, this one won't do it.
Click to expand...
Click to collapse
The thing with these Vibrants is that some of them have that problem where the phone doesn't register that your pushing the volume buttons at boot up...only the power button, which is why it just turns on and nothing else. This is a known issue that was found out by another canadian phone company(Bell)
I just bought a Vibrant and I could not boot into recovery from day one...after a week I took it back 'today' and got a replacement and now it works. I guess me and you were the unlucky ones.
If you really want it to work I would take it back somehow because this isn't fixable, its a hardware issue on boot.
-By the way, you can still boot to recovery from adb or rom manager, anything like that, just not physically. The down side of this is that if your in a boot loop and your computer doesn't recognize your phone your screwed. It also doesn't recognize Download Mode either to restore.
Hope it works out for you.
Wow so I'm screwed? Hard to call up T-Mobile and say "hey my phone won't boot into recovery, I need to switch it."
s15274n said:
Have you tried Quick Boot in the market?
Click to expand...
Click to collapse
I need root for that and I can't boot into recovery to get root.
SugarMouth said:
Wow so I'm screwed? Hard to call up T-Mobile and say "hey my phone won't boot into recovery, I need to switch it."
Click to expand...
Click to collapse
Actually thats exactly what I did...I told them I like to have control over my phone and that I use the recovery to "clean up" my phone every month or so and I like to use the recovery to do it. I also told them in the past i've used the recovery to install OTA updates that simply did not want to install over the air, so I would download it myself and install manually. The T-mo rep didn't seem to care.
So why not root this way then, and use quick boot once you have root
http://forum.xda-developers.com/showthread.php?t=739300
s15274n said:
So why not root this way then, and use quick boot once you have root
http://forum.xda-developers.com/showthread.php?t=739300
Click to expand...
Click to collapse
Exactly...do that. Like I said in my first post, you can still do everything thru Quickboot, Rom Manager, etc and ADB. You just won't be able to get to recovery that way if your phone won't boot or is stuck in a boot loop..that would suck.
As I mentioned in your other thead on this subject, I have the same problem with a brand-new Vibrant, and I don't want to root it yet. Only way I was able to get into clockwork recovery was via 'adb reboot recovery' method. Once I'd done that, I was able to install and run wirelessap tethering without rooting, infrastructure mode and all. Still not rooted, but I never did get my intended 'factory-fresh' nandroid backup, I gave up and popped in my SIM and installed a few things before I got adb talking to the phone. (running adb on ubuntu box, hadda kill and restart server as root to fix permissions issue)
j
I got my replacement vibrant, after bricking the first one, and I can confirm that I am not able to boot into recovery by holding the volume buttons. I hope samsung hasn't changed something...
But thankfully I was able to finally get into recovery using ADB...
So my Vibrant has been turning off randomly. I think its because of the loose battery or maybe it's just over-heating. But a few days ago, after turning it on there is only a black screen and lit capacitive buttons at the bottom.
It boots up normal, with the vibrant name, t-mobile animation, and the Galaxy S boot animation, then black screen! This started to happen after a few reboots, and now it won't rebbot properly, just black screen. It seems like I have to restore my phone, but the problem is I cannot get the phone into recovery or download mode! Please advise.
Samsung Vibrant, Eugene Eclair v6 custom rom with lag fix
First of all, there's no such thing as semi brick, there's brick or not. Try installing your Rom again..
Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App
iwillkillyou said:
Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
dude, he cant back up if he cant access the homescreen. neither can he use rom manager..
cant use the hardware buttons to get into dl or recovery either... read op guys...
2010ngojo said:
[Q] Need help with semi/soft brick!
So my Vibrant has been turning off randomly. I think its because of the loose battery or maybe it's just over-heating. But a few days ago, after turning it on there is only a black screen and lit capacitive buttons at the bottom.
It boots up normal, with the vibrant name, t-mobile animation, and the Galaxy S boot animation, then black screen! This started to happen after a few reboots, and now it won't rebbot properly, just black screen. It seems like I have to restore my phone, but the problem is I cannot get the phone into recovery or download mode! Please advise.
Samsung Vibrant, Eugene Eclair v6 custom rom with lag fix
Click to expand...
Click to collapse
Do this bro... just tested it myself, works fine...
get adb installed on your computer, should already have it if your rooting but if not get it, youll find it in the stickied thread for informative links in the development section.
get a cmd prompt open on your computer and type in
>adb devices
let it start up deamon and it will tell you device not found, its ok.
now type and have ready...
>adb reboot recovery (do NOT press enter yet)
start your phone like normal. before its even finished with the boot up tmobile animation and the galaxy s (but after the plain vibrant text/picture) logo press enter. if it says error: device not found then wait all the way till galaxy s only you did it too early...
screen will go black and reboot into standard recovery... hope to goodness you had a working clockwork recovery installed and nandroid ready for this next part...
go down using your volume keys and select reinstall packages using the power key
now in clockwork recovery go down to nandroid
now go to restore
go to your earliest back up and restore it.
there you go.
I would start fresh get odin set up and reinstall the original rom at this point as something may still be corrupted, reroot, install latest clockworkmod, latest vibrant 9 rom (im using and see no bugs and runs better then the vibrant 6 rom i had) and DONT install the lag fix until the newest "TRUE" lag fix comes out with the new file system and kernel that JAC is working on and has almost ready.
good luck and pm me if any of these steps need further explanation.
Pypanys thanks for that post, I learn something new but he said its bootsup normally, but it goes to a black screen after the boot logo he can enter recovery mode, same thing happen to me. I was opening maps and it crashed, it frooze the phone, to I restarted the phone and enter recovery amd deleted user apps, and it did the fix,
Sent from my SGH-T959 using XDA App
iwillkillyou said:
Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
iwillkillyou said:
Pypanys thanks for that post, I learn something new but he said its bootsup normally, but it goes to a black screen after the boot logo he can enter recovery mode, same thing happen to me. I was opening maps and it crashed, it frooze the phone, to I restarted the phone and enter recovery amd deleted user apps, and it did the fix,
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
hes just stated man that he cant even get into recovery, my guess is hes locked out using the volume up/down keys like many new phones are (which btw is a known defect, spend 10min on the phone with tmobile doing thier trouble shooting to show them it doesnt work and they send you a replacement..) sooooo I gave him a way to get into recovery without the buttons and not having to wait till he gets to a black screen where possibly its frozen and he cant use adb commands.
I was just making mention to you also that he cant even back stuff up NOW (hopefully he already archived all his apps and data) and hes better off starting fresh since hes getting problems using his current rom/lagfix....
Thanks for the quick reply p()()pypants, but i will have to try your method later. It's late and I have class (college) tomorrow, but i will post my results soon. Thank you again.
Edit 1:
Btw, is there a way to back up my current rom? Like the way rom manager back up roms? I know my current rom works before so that's why I want to back it up.
Edit 2:
Actually i did not use adb to root my phone, just used the one click method. So can you please give me more detailed instructions on how to install/use adb?
Okay, I typed in "adb reboot recovery" and press enter as my phone booted up during the t-mobile animation and at the Galaxy S boot animation. Neither time work. Then I reentered it again after the black screen. That did not work either. CMD keeps on returning "error: device not found" and the phone stays on with the black screen.
2010ngojo said:
Okay, I typed in "adb reboot recovery" and press enter as my phone booted up during the t-mobile animation and at the Galaxy S boot animation. Neither time work. Then I reentered it again after the black screen. That did not work either. CMD keeps on returning "error: device not found" and the phone stays on with the black screen.
Click to expand...
Click to collapse
Do you have the right drivers installed? You can check here: http://forum.xda-developers.com/showthread.php?t=728929
Another very stupid question, just to cover all bases - your phone is plugged into the computer, correct? When you install the new drivers, try plugging the phone into a different USB port on the computer than you've been using, so it will hopefully pick up the new drivers without much extra effort.
If that doesn't help, just keep trying the command while the phone boots up. Maybe you'll get lucky and it will work. Sorry I don't have any real solution for you :\
I'm fairly sure I have the right drivers, otherwise I wouldn't be able to root in the first place. Yes, the phone is plugged in also. I'll try a different USB port and see what happens...
Update: Trying different USB ports does not help.
I traded an HTC One yesterday for an ATT S4 and played with the phone all day. Seemed fine. Only issue I found was the volume UP rocker didn't work so well. Down is fine but UP seemed to stick. Last night I went to turn it off and charge it up. Changed my mind and wanted to play some more. So when I turned it back on it went straight into recovery and will not boot past it. Everything I try to do it says error no command. The guy didn't seem to know much about phones and didn't mention it so I don't think it's rooted but I'm new to Samsung so I don't know. The recovery says Android System Recovery (3e) also at the bottom it says #manual mode#
Applying multi-CSC-
Applied CSC-code:ATT
Successfully applied multi-csc-
So I have no idea what's going on and need some help.
Thanks in advance
Sent from my HTC One using xda premium
power and volume up will boot you into recovery mode.
You need to get that volume up "un stuck"
tdevaughn said:
power and volume up will boot you into recovery mode.
You need to get that volume up "un stuck"
Click to expand...
Click to collapse
I'm in recovery and the volume UP just flat out doesn't work anymore. It looks to me as if I got bamboozled. But I don't get it because everything worked fine earlier. I had turned it on and off and everything. The only thing I can figure is something happened when I was downloading the drivers to my computer and had my phone plugged in. I think that's about when the issue started. I don't remember much from last night but that sounds about right. I'm running the Odin thing trying to return to stock
And I don't think it worked. Is there a way to find out if this thing is rooted or anything while I'm stuck in recovery?
Sent from my HTC One using xda premium
I installed Asphalt 8 on the G2 only to find out the graphics settings only go up to low. I looked for a fix, and found I could get access to high graphics by changing the model in the build.prop file. I think I must've entered another model nuumber for a supported phone wrong somehow, rebooted and now it's in a bootloop with the LG Logo. Can I change the build.prop WITHOUT wiping it and installing a fresh stock ROM? I'm rooted and have TWRP & Busybox.
check the location of build prop then crate a buildprop cwm zip. U can reuse one fron another device. However put in correct buildprop and correct location of this on device in the script, then flash though recovery. It should boot then. Edit it in notepad++ though.
Sent from my LG-D802
That'd be great, except I don't know how to get to twrp! I can't get a usb connection either.
Sent from my Nexus 4 using xda app-developers app
To clarify, I have TWRP installed of course, but how do I get it without using adb commands, etc.
Sent from my Nexus 4 using xda app-developers app
that I also dont know as I am not rocking custom but stock.
in many threads there speak about how to get into recovery. Go search at least the kernel thread where you got it from
Sent from my LG-D802
transfo47 said:
To clarify, I have TWRP installed of course, but how do I get it without using adb commands, etc.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Try holding Power+Volume Up.
If that fails, go to download mode by holding Volume Up while you insert your USB cable. Follow the instructions here http://forum.xda-developers.com/showthread.php?t=2432476
hamisgood said:
Try holding Power+Volume Up.
If that fails, go to download mode by holding Volume Up while you insert your USB cable. Follow the instructions here http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
I fear that during a boot loop there is little you can do.
And, as the battery cannot be removed, you need to wait for the battery to die! Then you power on to TWRP.
Power + Volume Down until the LG logo disappears and appears again. Let go of Power+Vol Down for a moment and press them back again. Should bring you to a white screen asking if you want to factory reset your phone. Press Power button to confirm and it should then bring you to recovery.
Read the updated post
Sent from my Nexus 4 using xda app-developers app
I've done something bad to my phone (tried to do a factor reset from within TWRP) and now I'm trying to get out of a boot loop myself... When I do the Power+Down trick to rest, it doesn't safely enter recovery and wait for me to do stuff, it launches some sort of recovery/reset script and reboots into my boot loop again.
Anyone know what I'm doing wrong? I was on stock firmware, rooted, with TWRP 6.3.2.1.
elreydetodo said:
I've done something bad to my phone (tried to do a factor reset from within TWRP) and now I'm trying to get out of a boot loop myself... When I do the Power+Down trick to rest, it doesn't safely enter recovery and wait for me to do stuff, it launches some sort of recovery/reset script and reboots into my boot loop again.
Anyone know what I'm doing wrong? I was on stock firmware, rooted, with TWRP 6.3.2.1.
Click to expand...
Click to collapse
Me too but I'm on CWM 6.0.4.4 I don't get that part " it launches some sort of recovery/reset script and reboots into my boot loop again." but it constantly goes in circles
Pat
I Just want to get my Build.prop file back
pfeckert said:
Me too but I'm on CWM 6.0.4.4 I don't get that part " it launches some sort of recovery/reset script and reboots into my boot loop again." but it constantly goes in circles
Pat
I Just want to get my Build.prop file back
Click to expand...
Click to collapse
You don't have to wait until your battery dies in order to shut down from a bootloop. If you hold all three buttons down, it will force shut down your phone. Not sure how long you have to hold it, but I believe you hold until after the LG logo disappears for the second time. It worked for me yesterday after I bootlooped my phone when I mistakenly enabled Thermal Daemon Mitigation instead of High Temperature Property in the Hidden Menu (don't ever do that). I'm not rooted, so I'm not sure if the function still works the same, but if you can get into TWRP after the phone is shutdown, then I believe that's the only way to do it.
I seem to be another victim of this issue. I was attempting to update my recovery (TWRP 2.6 installed) on my Verizon S4 via TWRP's app. It failed, so I figured I might try it from recovery. I attempted to boot into recovery, but it is stuck at the Samsung "custom" screen and the blue "RECOVERY BOOTING......" text is in the top left corner. I can leave the device alone for several minutes and it never goes into recovery. It does get very hot though, and occasionally it will reboot on its own. If I hook it up to my PC and then put in the battery, it will vibrate as if it is going to boot, then it vibrates again in 3 seconds and does this endlessly with nothing coming up on the screen. Without being able to get into recovery or have my desktop recognize the device, I'm not sure what to do. Any ideas before I chuck this brick?
Are you able to get into download mode (volume down, home button, power)? If you're able to, the device is not bricked and, using Odin, you can update TWRP to 2.8.4.
I've found that the app isn't working all that well. For the last few updates I've had to use Odin to update TWRP.
Strephon Alkhalikoi said:
Are you able to get into download mode (volume down, home button, power)? If you're able to, the device is not bricked and, using Odin, you can update TWRP to 2.8.4.
I've found that the app isn't working all that well. For the last few updates I've had to use Odin to update TWRP.
Click to expand...
Click to collapse
Ah ha, you are correct. I actually tried a variation of this (I think with volume up?) but it just attempted to go into recovery again. At the download screen I just told the phone to boot into the OS and all seems well. I'll look into updating TWRP via Odin and see if I have any joy, but at least I have a working phone again. Thanks for the help.:good:
When you update, do NOT try to use TWRP 2.8.5.0. It's bugged on the S4. Use 2.8.4.0 instead.
Thanks, good advice!
Looks like my recovery is toast. Doing some research, I never used Odin as my phone had the old MDK baseband. Sites tell me not to use Odin, so I followed the instructions on TWRP's site using Terminal Emulator and 2.8.4.0: http://teamw.in/project/twrp2/181 Everything seemed to go well, so I attempted to reboot into recovery, but now I get some warning/error about unauthorized software, turn off your phone and take it to Verizon, etc.
Sounds like I need to try again, but I'm not sure what my options are now.
I didn't even see you had a Verizon S4 until you mentioned it. Verizon encrypts the bootloader as a matter of course, and thus installing TWRP is not possible. You should however be able to restore the official firmware with Odin, and from there, follow the root guides at http://forum.xda-developers.com/galaxy-s4-verizon to get yourself back up and running.
mine get to the point where i select volume up, i see the android bot and message do not turn off target, and it shuts down. what do i do?