for whatever reason, i wasn't able to put this into the development thread (that's already growing incredibly long and tedious to dig through). but i felt this should be out there for people to see in the case that they have the same problem.
just got my sprint v20 this morning. and like a true XDA lurker, i went straight for the root.
process went fine up until the part where you run step3.bat while in fastboot mode.
phone rebooted. straight to LG screen. stayed there for an hour.
tried a few battery pulls, adb device checks (showed offline most of the time, but sometimes would show 'device'), adb reboot recovery (froze), pull battery to turn phone off hold volume down and plug cable in.
nothing was working, straight to LG screen every time
then i dug around and came across where some models of phones would have a way to reflash the stock firmware from a pc program. dug into that and had no luck (.kga file not available for sprint phones yet)
then what finally worked. unplug phone, turn it off (battery pull), hold volume down, hold power button, as soon as phone turns on let off power button and hold again.
boom, straight into twrp. was able to flash my rom and the SU binary from there.
static on first boot (as described) lasted a little while before i heard the standard first start voice over, where i was able to turn the screen off with the power button, and back on to get a fully working screen.
everything works great now. hope this information helps at least someone with that everpresent lump in their stomach when they think they've screwed up their phone. . maybe this can be moved to the right place if a mod deems necessary.
Related
help i9000 after flash, doing loop of at&t logo, can not enter download mode,
when plugged in screen goes black.
!! if anyone can help please do not hesitate, mostly appreciated.
Try to hold the Down+Menu+Power combination while INSERTING the battery into the device.
i try that seem to have no response and when unplugged from usb it loop at&t logo
or plugged in usb screen goes black and no response seem from pressing buttons
I had a similar problem as most phones in Canada seem to have Download/Recovery mode disabled, and here is what worked for me.
Grab something like One Click Un Root (all models), and click one click un root (obviously phone has to be on and plugged into the computer).
This should automatically reboot you into Recovery Mode!
All you have to do is "wipe data/factory default" or something like that (should be the third option).
As it states, you will loose all your data, but at least you will have a functionning phone!
did it work?
Hi. I have similar problem. Can anybody give instruction what can I do?
I have this problem too. Please help somebody
Add me to the list. Bell Galaxy S, went to unlock my phone the screen went black. Now it will not boot into the OS, the galaxy S splash screen displays then nothing. The menu and back button light up, thats all. ****[email protected]@
I have not rooted or anything.
Of course my download mode does not work.. Going to try this one click root thing if I can find it.
NOT HAPPY
This is not working. Probably because the phone is not in USB debugging mode as I can't change it... Is there any other way to get the phone into recovery mode?
**** me
i had the same thing happen to me the other day with my bell galaxy s and my phone wont do the 3 button combo trick. i left my phone plugged in to a wall charger for a while until the back of the phone became a little warm. i pulled the battery and then left the power cord plugged in and put the battery back in. i held the volume down and enter button until the battery charging indicator showed up, then i also pressed and held the power button until the boot animation started (this is the blue moving swirl and music, not the galaxy s splash scree) and then i let go of the power button. it took a few attempts at this before it actually worked, but eventually it will go into download mode at which time you can open the odin app, then plug in the usb cable and flash your phone that way. it did seem to make a difference if the back of the phone (around the camera area) was warm. if i let go of the power button while the music was playing and the phone did not enter download mode i would keep all 3 buttons pressed until it shut down again, then i would only let go of the power button while the phone initiated the charging screen, then once the battery logo was displayed i would hold the 3 buttons again and would just keep doing this until it went into download mode. i have flashed it at least 5 times today and i have been able to do this each time.
i also had an issue where odin would not recognize my phone was plugged in and windows would show a message saying the usb device was not recognized. i left the phone plugged in and while in download mode i pressed the volume up, enter button and power button until the phone went blank and when the galaxy s logo showed up i let go of the power button and the phone would go into recovery mode and then the usb drivers would be installed. i would then do the 3 button combo for download mode and odin would work fine. it took several attempts but it does work. i hope this helps you guys
If I hold all three buttons the splash screen does not come on, it just keeps looping the Galaxy S logo until I let go of the power button....
xZeDgEx said:
If I hold all three buttons the splash screen does not come on, it just keeps looping the Galaxy S logo until I let go of the power button....
Click to expand...
Click to collapse
That's what mine did too, several times in a row and then it worked. For some reason it only works after the battery is charging for a bit and the back becomes warm. then it works at will
No luck. I am probably screwed getting it exchanged now too as I am passed the 14 days from Best Buy.
the on click thing doesn't work, if your phone is already bricked.
also it is not the phone's fault for not working, the phone was working properly before you tried the hacks.
whenever you do these kind of things you know you are entering into the "not supported" "not covered by warranty" zone.
in the worse case scenario, if you can no enter download mode to recover your phone, it'll be to take the phone back to bell and claim warranty on it, and prentent you don't know what happened to it.
xZeDgEx said:
Add me to the list. Bell Galaxy S, went to unlock my phone the screen went black. Now it will not boot into the OS, the galaxy S splash screen displays then nothing. The menu and back button light up, thats all. [email protected]@
I have not rooted or anything.
Of course my download mode does not work.. Going to try this one click root thing if I can find it.
NOT HAPPY
Click to expand...
Click to collapse
AllGamer said:
the on click thing doesn't work, if your phone is already bricked.
also it is not the phone's fault for not working, the phone was working properly before you tried the hacks.
whenever you do these kind of things you know you are entering into the "not supported" "not covered by warranty" zone.
in the worse case scenario, if you can no enter download mode to recover your phone, it'll be to take the phone back to bell and claim warranty on it, and prentent you don't know what happened to it.
Click to expand...
Click to collapse
Its my fault??
I did not hack my phone. Its not rooted, I did nothing to it.
By "unlock" I meant exactly that, unlock as in swiping the screen to unlock it.
The more I search the net the more posts I find of Galaxy S phones randomly bricking...
on the original message sounded more like you went to Unlock the phone, as in SIM unlock the phone using any of the tools available out there, and there has been already several people which had the same problem.
if you go back to Bell for an exchange, you better not use the word "unlock" rather use Swipe
as the message on the phone "swipe the screen to unlock"
there are no known issue about this causing the phone to brick.
if that is what happened to you, you should have started a new topic for people to help you, instead of hijacking the topic from the OP, as your issue is different from OP, the OP actually screwed up because he/she flashed the wrong ROM to the i9000
... anyways, Does it work if you reboot the phone?
I have rebooted the phone about 100 times. The phone crashed when I unlocked it to check a text I received. (not hacked). Has not booted up properly since. I have found many others with the same issue who have also not hacked/rooted/unlocked/ their phones.
Waiting on Best Buy to call me back. I am so pissed right now, I have been bragging to my friends and co-workers how awesome this phone is, one has already picked one up, I hope his doesn't brick too. Not recommending it to anyone anymore..
did you load a lot of MP3 to the phone?
can you boot into Recovery Mode?
in the recovery mode you can wipe the Cache and wipe the data
that should make your phone work normal again
it'll be best to open a topic to help you trouble shoot your interesting issue, as it's the first i've hear that you get a black screen after Swiping out of the lock screen
I can't get into recovery mode. I have tried every button combination I have found. I had about 2 GB of music on the phone. I also installed the Android SDK to try ADB, but since the phone is not in USB debugging mode it does not see it.
xZeDgEx said:
I can't get into recovery mode. I have tried every button combination I have found. I had about 2 GB of music on the phone. I also installed the Android SDK to try ADB, but since the phone is not in USB debugging mode it does not see it.
Click to expand...
Click to collapse
on the other topics relating to the 3 button not working.
have you tried the heating up method?
or the plugging the battery in, when all 3 buttons are pressed? (of course for this one you will need help from a friend, unless you are very skilled at keeping the 3 button on hold meanwhile able to slide in the battery in with out a 3rd hand)
First off I am running 4.2.2 on MF3 with root. I have no custom ROM, recovery or any other modules. This literally just happened 30 minutes ago. I've tried searching everything to no avail. My screen randomly went black (after setting it down for 15 seconds) and now it won't work. When I take out the battery and stick it back in the initial pop up is the Samsung name with an unlocked lock that says custom, this will pop up regardless if I press and hold the power button or do anything, which hasn't happened before. After that screen nothing happens as normal. I have tried to boot into download mode and I can get to the initial "WARNING" screen and then get into the download screen with the Android alien and before anything can happen it will go black. So this leads me to believe that is it either crashing or failing after the initial 20-30 seconds of boot sequence. I will also mention that when I have the USB cable plugged into both a computer and a wall outlet that it wont do anything even after i take out the battery and put it back in, try to boot into download, or just hold the power button. The computer won't even recognize that a device has been connected. When it is unplugged I can do what I previously mentioned. Please if someone can help me I would greatly appreciate it. I am really worried that because I have my device rooted I won't be able to take it in for warranty and get it replaced. Any help is greatly appreciated! Thanks in advanced!
Same happened to my phone
The exact same thing seems to be happening with my phone, however, my phone was not rooted. After installing KitKat (4.4.2) the phone was acting a bit weird and, all of a sudden, the screen went black. Can't turn it back on since then. The welcome screen comes up only after I put the battery in. After that it is completely unresponsive. I am also able to see the download mode warning before the phone goes off on its own, and the same thing happens for the recovery mode. I see the 'recovery booting' message, but then the phone turns off.
AT&T is has replaced my phone, but I wanted to get my data before sending the damaged phone back. As stated above, the phone is not recognized by my computer, so I can't access the data through USB. The guys at AT&T could not help me with the data recovery. If anyone could help me with this, I would greatly appreciate it.
D
Hey,
This is my first time posting here and really using the site. I have the Sprint Galaxy S4 and just updated to the SlimKat official build 7 and had no initial problems. A day later it starts to reboot constantly and would stay on for a couple minutes. Now it is stuck in a bootloop and will shut off even when going into download or recovery mode. When plugged into a computer the computer won't even recognize the phone and the phone will not turn on. The only time the phone will even start to boot is when it is not plugged into wall/computer and on battery. I have no idea what to do now.
That's a tough one. Usually with a soft brick, if you can make it to recovery, your phone can be saved but since you can't... I hope you get it working!
Sent from my SPH-L720 using XDA Free mobile app
puresublimie said:
Hey,
This is my first time posting here and really using the site. I have the Sprint Galaxy S4 and just updated to the SlimKat official build 7 and had no initial problems. A day later it starts to reboot constantly and would stay on for a couple minutes. Now it is stuck in a bootloop and will shut off even when going into download or recovery mode. When plugged into a computer the computer won't even recognize the phone and the phone will not turn on. The only time the phone will even start to boot is when it is not plugged into wall/computer and on battery. I have no idea what to do now.
Click to expand...
Click to collapse
Go to sprint galaxy s4 thread. All answers there. You need Odin 3.09 then stock ng2 tar. To flash through computer.
Sent from my SPH-L720 using XDA Free mobile app
I already have odin and the tar files for stock. When plugged into my computer it will not even register that it is connected and so I can't use odin to flash it.
The same thing is happening to me. I get to the Galaxy S4 splash screen, then it shuts off. Even if I try to boot into recovery
I'm going to pile on in here as I seem to be having a similar issue. I had my S4 (not rooted, stock rom) on my dock streaming google music. A phone call came in and the phone started vibrating like crazy and wouldn't stop. The screen shut off and the phone was still vibrating. Finally it stopped and was shut off. When I try to start it a few things happens. It will sometimes boot to my lock screen and the screen goes black and I think it is powered off. Sometimes it will get past the lock screen and then die shortly after. After like 2 or 3 times of that it won't even boot. It loads the Samsung screen but never gets to the Sprint screen or boots. If I leave it for some time shut off with battery out it will go back to booting to the lock screen then dying etc... When I press the buttons to get into recovery it says recovery is loading and then the screen goes black. I swapped batteries and that didn't do anything. I tried pressing the menu button or the home button to try and boot safe mode and it just loads normally not that I think that would help anyway.
Any ideas on things I can try next? What is this odin thing? Would that work for me?
---------- Post added at 07:09 PM ---------- Previous post was at 06:16 PM ----------
Ok... I can get into recovery now and will try a factory reset. Are you sure you are going into recovery correctly. Apparently I was not. Hold volume up power and menu button and when the phone vibrates let go of power only.
Before I do a hard wipe is there any way to get data off the internal memory from recovery mode?
So I got a custom recovery installed, reinstalled stock rom, things worked ok for awhile. Then it started random reboots every 10 mins or so. Now it is back to instant crashing and rebooting. Any idea what could be the issue? I'm assuming at this point it is hardware related. Why can recovery and download mode run consistently without crashing but when an os is fired up it has issues? If it was a hardware issue shouldn't it not work across the board?
So I had Sprint replace my phone on the 8th. I have been using my same batteries (1 stock 1 Anker) and chargers (some stock some not) without issue the past 5 days. I rooted and installed xposed and some modules (original broken phone was never rooted and was completely stock). Things were going great until tonight when it started reboot looping exactly like the old phone. I switched battery and same proble. After I took the battery out and left it out awhile it fired back up but I'm afraid the problem will return. Is it possible that the battery or charger randomly are causing damage to the phone? I only have 14 day warranty on this replacement and need to figure this out.
So things were going well for awhile and then the reboot loops started up again. I did some digging and read that apparently Samsung phones are notorious for sticking power buttons and the symptoms were exactly what I was experiencing. I watched some videos online how to open the phone and clean out the power button but it didn't make a difference. I then read that squeezing the connector for the power button with a pair of pliers sometimes does the trick. Not for me. So finally since I'm not under warranty, have no insurance, and the phone wasn't working anyway, I just ripped the white plastic part of the power button right off. Well, that seemed to do the trick. Phone immediately fired back up without issue and has been going strong. I glued a small thin piece of plastic where the old one used to be and I am back in action. If my little plastic piece solution eventually fails or breaks off I will consider soldering on a new button but so far so good.
If you have tried everything else, and are looking for last resort, try cleaning the power button with some alcohol, and if that fails, rip off that power button! Here is the video that gave me the idea: https://www.youtube.com/watch?v=3Glllc7bEJs and here are some other power button videos: https://www.youtube.com/results?search_query=s4%20power%20button&search_type=&aq=f&oq=
A friend has an S4 GT-I9505. It was bought second hand few months ago.
Lately it has been acting up. Shutting down randomly but now it won't turn back on. We sometimes manage to get it back on, but no always.
It isn't the battery since I have inserted my battery into the phone and it still won't turn on. It won't turn on even when connected to the charger.
We figured it might be the power button so we took it to a guy to check it out. The guy took the phone apart looked at the button and said the button is ok.
He put the phone back together and it somehow worked without problems for a few days (up until now).
He said that the phone might be shorted somewhere. The thing that led him to that conclusion is that he noticed that when inserting the battery the phone would try turn on without pressing the power button.
He also said the boot might be dead because the phone won't go into recovery nor into download mode. Even if it manages to boot into them, it will turn off almost immediately sometimes.
The phone is running 5.0.1 GPE custom rom with Googy-Max kernel. No tweaks or mods.
I know this sounds a lot like a hardware problem. The only thing that makes me have doubts is that it works occasionally without any problems.
He looked at the power button. Honestly it's no surprise he didn't find anything wrong with the power button because the problem with the power button is inside the tiny metal casing making up the button, and it's something that can't be seen.
Get a second opinion from someone other than the guy you took this to. However, I believe this to be a power button issue, easily fixed by replacing the button.
As I said, He took the phone appart, took the motherboard-logic board, whatever you want to call it, out and looked at it. He also took that tiny metal casing that forms the power button out, leaving a tiny white "something" exposed. I guess that's what you're talking about
But I really hope you're right and it's the power button.
Edit: We were the whole time there while he took the phone apart and looked at it. So we saw everything he did. And he didn't do anything special except take it apart and put it back together and it somehow worked for a few more days.
I guess it really is the button. I managed to change the rom, kernel, bootloader. The phone booted up. I pressed the button once to lock the screen but nothing happened. 1 second after that the boot menu appeared. The next second the phone shut down and now it won't turn on again. Except for a brief moment to show the S4 screen and then turns off again.
I had an alarm app give me an alarm last night but I was busy in another app and dismissed the alarm in a way that the sound was still going. The only thing I thought to do was to do a reboot of the phone. I gave it a few minutes and when I pulled it from my pocket I noticed that it had not rebooted. So I held the power button for a few seconds and waited for that vibrate then the "Custom" screen.
Nothing.
Held the power button for about 30 seconds.
Nothing.
Good battery, at least 75% before this happened. No sweat. I have a spare battery that I know is 100%. When I put that one in, the phone immediately did a vibrate and gave me the "Custom" screen. Then dead. Power button did nothing.
Pulled the battery and upon insertion, I got that vibrate again. But this time I held Volume+ and I get that tiny blue bootloader message at the top of the screen for a half a second. Then dead. Tried it again and this time did Volume-, this time I got download mode for half a second. Then dead.
Tried all this with power plugged in and get even less. Nothing.
Connected it to a PC (OEM cord straight into the motherboard) and got nothing. No charging LED, no sound from the PC upon plugging. Nothing new showed up in Device Manager.
Did I just do the "Low Effort Brick" method just by rebooting? I have had this thing for a few years, running CWM then TWRP. Several ROMs in the past, xposed, done it all and never once even had a boot loop. Now I have a brick because I rebooted a phone that had been VERY stable for weeks (on Dan's GPE ROM)?
I am not so concerned about the device, I actually ordered a LG G4 already. What I REALLY want is the autobackup of Tasker that is in the internal storage. I know I have a TiBu of everything on the microSD and a TWRP is on there too. But both are a few days old and I have made many changes to Tasker in the past few days. Tasker updates a backup every time you leave the app, so I know I have a very recent file in there. But how do I get it?
It's not bricked. The power button on some S4's are janky. Mine did the same thing for a while. You can try smacking the power button on the corner of a desk or something but otherwise either just keep pulling the battery and trying, try opening it and cleaning the switch, or try replacing the switch.
It's hardware issue with power button. I've got the same issue with my S4. The only solution is to replace the button.
Good advice. Found a few YouTube videos that are pretty close the issue that I have. I shall do some work on this this weekend. Thanks for taking the time to respond!
Hell yeah. Effin HELL YEA. Found a few YouTube walk through videos and got down to the switch. Using my ever-awesome Simpson 260, I was able to determine that the power switch was bad. I exercised it a few dozen times and then it went open. Roughed everything back together (without screws) and got a boot.
Immediately made a TiBu of everything. I will also make a TWRP as soon as that is done. Now I have to source a power switch. I should have no problem replacing the switch. I have a fantastic solder station at work and a 20X magnifier. This shall be my crutch until the LG G4 arrives.
Thanks again for the advice. Proof again that this is a real community.
Side note: I went to AT&T to get my old Vivid back into action to replace my S4. When I mentioned that the device was rooted, they replied with some statement that my "jailbreaking" the device is what caused the failure. I asked if she knew what rooting was, and she said "yeah...jailbreaking". I asked her if she knew what an "unlocked bootloader" was and she just glazed over, mouth open. When I told her that the device has been rooted for years with no problem, she insisted that the problem happened when I "jailbroke" it.