On my second HD2, I had missed flashed the it, forgetting to flash it with HSLP first, so not surprisingly, It bricked. 1st the LED wouldn't even come on when plugged in. After accidentally leaving it plugged in for about 2 days, I noticed the light cam back on.
After trying to boot it, It only stayed at the Tmo splash screen over and over...so I decided to just leave it at the screen, Hours went by, and it stay a that horrible pink stick together screen. Then I fail asleep.
This morning I mistakenly picked it up thinking it was my other one, and to my surprise, I hit the power button, and it was working normally, even had the custom ROM. So I re-flashed everything correctly this time, and BAM, another HD2 up and running.
Maybe this set and forget technique will work for others sometime. IDK...lol
Related
I had my phone to schedule a soft reset every night at 1am. Woke up this morning, pressed a button to wake it up and nothing, button lights came on nothing else, waited, pressed again exactly the same. Pulled the battery and rebooted, got to the Launching HTC Sense prompt, phone rebooted and doing so in a loop until I pulled the battery again. Have now reflashed back to the stock tmobile uk rom, that I think was developed by a four year old, and it's working. I really don't want to stick with this but again don't want to be flashing my phone every 3 weeks, in two minds whether to drive to tmo headquaters and shove it up someones arse
I'm currently using Artemis 9- best rom I've used. It and radio 2.06 seem to be an excellent combo for me. I'm in London.
Agree totally that the stock Tmob UK rom was pretty shocking. Was fine as long as you never installed anything, or left Sense!
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=
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.
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.
Hey everyone,
last week my s10+ screen turned half white when i was outside with my dog.
It started a couple months ago with a black spot on the left of my screen. I thought it wasn't a big problem as it wasn't in the middle of the screen.
Last week I was taking a walk with my dog, I checked my phone for a football match kickoff time and put the phone back in my pocket. I later checked my phone again and noticed half of my screen was white.
The screen did react to swiping and even the fingerprint scanner worked. I went to KPN (which is the phone carrier I use) and explained the whole situation. They told me I had to reset my phone to factory settings. When I got home I tried to reset my phone however when I pressed the reset button my phone would just restart without deleting anything. So after a bit of googling I tried flashing stock firmware. I made sure it was the latest one and made sure it was for my phone. The flashing finished but now my screen doesnt work at all. I tried the booting into download mode methods however I cant get any screen output ever since I flashed that stock firmware. The phone does vibrate when I start it up and it does connect to my pc.(S10 folder pops up, but its empty) I also tried ADB however the phone doesnt show in the devices list. (probably because USB-Debugging has somehow turned off). I did root my device with magisk a couple months ago and i'm afraid I somehow bricked it when i tried flashing stock firmware on it.
Is there any way for me to get into download mode to try another stock firmware?
Note: I dont have any screen output at all, so I have to do everything blindly.