I was updating some apps from the playstore and decided to check my voice mail by holding the 1 key in the dialer, but then my phone rebooted. Now, it won't boot past the TMO screen no matter what I do. I've tried wiping cache in recovery, and everything but a factory reset because I have a pin/fingerprint set up. I've heard that it will lock you out of your phone for 3 days if you factory reset from MM for security reasons, hence why I haven't done it. I can't find the firmware to sideload for the T-Mobile variant, can someone shed some light on this issue? It's rather annoying to have it softbrick for no reason, and not have the firmware to fix it. If someone has the firmware that would be great, or if they know how to fix it.
you can bypass FRP(the lock after reset). ive done this with about 5 s6 edges. I just bypassed one last night. i would assume it prolly works with the s7 edge also.
https://www.youtube.com/watch?v=ogMtWt7Znxw
t12icky0 said:
you can bypass FRP(the lock after reset). ive done this with about 5 s6 edges. I just bypassed one last night. i would assume it prolly works with the s7 edge also.
https://www.youtube.com/watch?v=ogMtWt7Znxw
Click to expand...
Click to collapse
I'm going to attempt a odin flash shortly since I found the firmware in the tmo subforum. Hopefully it works
Good luck
t12icky0 said:
Good luck
Click to expand...
Click to collapse
After a few "successful" flashes according to odin it finally booked correctly. It took it s long time to boot after the flash, so I'm glad it's working again. I would like to know what caused it to suddenly softbricked, I didn't do anything to cause an issue.
Not sure what happened today but everything been fine since I got my phone. Today after using bbc iplayer then going back to it from multi tasking menu everything froze up . .phone wen black and went off . .was scary to say least . .i held power and volume down for 7 seconds and it came back on. . . .nothing happen since . . .anyone know what that could have been?
PracticallyGeek said:
Not sure what happened today but everything been fine since I got my phone. Today after using bbc iplayer then going back to it from multi tasking menu everything froze up . .phone wen black and went off . .was scary to say least . .i held power and volume down for 7 seconds and it came back on. . . .nothing happen since . . .anyone know what that could have been?
Click to expand...
Click to collapse
Mine was similar except it got stuck on the tmo screen for over 10minutes before I called if softbricked.
Pilz said:
Mine was similar except it got stuck on the tmo screen for over 10minutes before I called if softbricked.
Click to expand...
Click to collapse
Did you do anything specific to flash? I'm trying to flash it but it fails
luisrcastillo said:
Did you do anything specific to flash? I'm trying to flash it but it fails
Click to expand...
Click to collapse
Are you using odin? I flashed all of the packages via Odin 3.10.7 I flashed the larger file (MD5 I think it was referred to as) and it succeeded every time according to Odin, but it took me 3 full flashes for it to boot fully.
Sent from my Nexus 6P using XDA Labs
Pilz said:
Are you using odin? I flashed all of the packages via Odin 3.10.7 I flashed the larger file (MD5 I think it was referred to as) and it succeeded every time according to Odin, but it took me 3 full flashes for it to boot fully.
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I was using an older version of Odin so trying with the same version as you it is now flashing as we speak. Thanks!
luisrcastillo said:
I was using an older version of Odin so trying with the same version as you it is now flashing as we speak. Thanks!
Click to expand...
Click to collapse
Hopefully it works for you, I just downloaded the latest one I could find and flashed away. It seems to be working fine now despite the first boot taking a while
Sent from my Nexus 6P using XDA Labs
Pilz said:
Mine was similar except it got stuck on the tmo screen for over 10minutes before I called if softbricked.
Click to expand...
Click to collapse
So you tried the power on and volume key method but it stuck on starting up? Looks like I got off lightly . . Wonder if it's a software thing like the camera problem people are experiencing
This happened to a lot of s6edge+ users in the beginning.
Still no idea what was causing it. Updates seen to have cleared it, however, every s6edge+ reboots/freezes at launch one in a while.
Pilz said:
I'm going to attempt a odin flash shortly since I found the firmware in the tmo subforum. Hopefully it works
Click to expand...
Click to collapse
where is this firmware you speak off
PracticallyGeek said:
So you tried the power on and volume key method but it stuck on starting up? Looks like I got off lightly . . Wonder if it's a software thing like the camera problem people are experiencing
Click to expand...
Click to collapse
Yes no matter what I did it would not boot pas the T-Mobile screen.
kappatau808 said:
where is this firmware you speak off
Click to expand...
Click to collapse
In the T-Mobile S7E subforum
Sent from my Nexus 6P using XDA Labs
Pilz said:
After a few "successful" flashes according to odin it finally booked correctly. It took it s long time to boot after the flash, so I'm glad it's working again. I would like to know what caused it to suddenly softbricked, I didn't do anything to cause an issue.
Click to expand...
Click to collapse
Well, consider yourself lucky. I had (in fact have) a Moto 360 which was bricked by Motorola at the last update and now it's sitting on my desk as a paperweight for more than a month.
Cst79 said:
Well, consider yourself lucky. I had (in fact have) a Moto 360 which was bricked by Motorola at the last update and now it's sitting on my desk as a paperweight for more than a month.
Click to expand...
Click to collapse
That sucks is it the gen 1 or 2? Moto support went downhill after I bought my Nexus 6 from back in 2014. I haven't bought a Moto product since then for that reason. Can you boot into this bootloader at all? I've flashed my Huawei watch before without an issue.
Sent from my Nexus 6P using XDA Labs
Pilz said:
That sucks is it the gen 1 or 2? Moto support went downhill after I bought my Nexus 6 from back in 2014. I haven't bought a Moto product since then for that reason. Can you boot into this bootloader at all? I've flashed my Huawei watch before without an issue.
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
It is Gen1. It is fixable via ADB, with a proper connection rig but my improvised rig resulted in a fried USB port on one of my computers after a successful connection, so I just gave up. I may one day buy a Chinese connection rig (there are some nice ones for sale) but the investment is just not worth it, I will probably get a Gear S2 and be done with Motorola, forever.
Cst79 said:
It is Gen1. It is fixable via ADB, with a proper connection rig but my improvised rig resulted in a fried USB port on one of my computers after a successful connection, so I just gave up. I may one day buy a Chinese connection rig (there are some nice ones for sale) but the investment is just not worth it, I will probably get a Gear S2 and be done with Motorola, forever.
Click to expand...
Click to collapse
I know this is a little off topic:
Motorola didn't make it easy due to their lack of pogo pins (even though most people don't like them). I'm not sure how it would fry a USB port, but anything can happen. I plugged my 6P into my Surface Pro 4's dock via an A-C cable and it windows said it was trying to pull to much current and shut off the port until I rebooted. Things happen for better or worse, but I prefer AW over Tizen due to the long term support, despite liking Samsung's rotating bezel.
Pilz said:
I'm going to attempt a odin flash shortly since I found the firmware in the tmo subforum. Hopefully it works
Click to expand...
Click to collapse
can you send a link where you found that tmobile firmware? I'm having the same issue of not being able to go past the white t-mobile screen
Related
i have a non-rooted HTC incredible, however it's stuck in an endless boot loop. I can enter recovery, but that's about it.
any suggestions as to what i can do?
hard reset may work
Sent from my Incredible using XDA App
i tried hard resetting it. this did not solve the problem.
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
jdkoreclipse said:
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
i am the second owner of the incredible, and apparently, the warranty only applies to the original owner.
Are you root?
When and how did this start happening?
jdkoreclipse said:
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Sounds like you got a bad one. Mine is perfect. No issues.
JaydenR said:
Sounds like you got a bad one. Mine is perfect. No issues.
Click to expand...
Click to collapse
im actually thinking of taking it back and getting a moto droid. i love the dinc, but it is poorly made.
Too bad i cant return, as i got it on release day. maybe if i can pick a good fight with the vzw guy, i could swap it out.
Sent from my Incredible using XDA App
JaydenR said:
Are you root?
When and how did this start happening?
Click to expand...
Click to collapse
i'm not rooted. i was just using the phone normally and then it randomly rebooted. now it's stuck in a loop.
do you guys think if i apply a manual non-rooted update it would fix the problem?
if yes, where can i get a link to download this?
RUU
You should try running any of the stock RUU's; maybe even the most recent one (although I make no warranty; and this is at your risk). Perhaps your reboot loop is a heat related issue due to a faulty radio which is working too hard.
http://www.shipped-roms.com/shipped/Incredible/
has the RUU's although it is not clear as to how long.
I am on my 2nd incredible; first one overheated and would then would do a 4-13 white screen / black screen / white screen / ... until it would move on.
theanswer said:
i'm not rooted. i was just using the phone normally and then it randomly rebooted. now it's stuck in a loop.
do you guys think if i apply a manual non-rooted update it would fix the problem?
if yes, where can i get a link to download this?
Click to expand...
Click to collapse
edit: post is useless.
Sent from my Incredible using XDA App
Try the RUU that was posted.
jdmba said:
You should try running any of the stock RUU's; maybe even the most recent one (although I make no warranty; and this is at your risk). Perhaps your reboot loop is a heat related issue due to a faulty radio which is working too hard.
http://www.shipped-roms.com/shipped/Incredible/
has the RUU's although it is not clear as to how long.
I am on my 2nd incredible; first one overheated and would then would do a 4-13 white screen / black screen / white screen / ... until it would move on.
Click to expand...
Click to collapse
these RUUs require the phone to be turned on though. i cant get past the boot screen
theanswer said:
these RUUs require the phone to be turned on though. i cant get past the boot screen
Click to expand...
Click to collapse
download the downgrade image. it will be found in the ota thread in the dev section.
Sent from my Incredible using XDA App
jdkoreclipse said:
download the downgrade image. it will be found in the ota thread in the dev section.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
just want to confirm, you want me to follow this:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
theanswer said:
just want to confirm, you want me to follow this:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
Click to expand...
Click to collapse
put this on the root of ypur sd card, boot into bootloader, and let the phone do the rest. YOU MAY LOSE ALL DATA
http://www.mediafire.com/?yum40znzwmmmtyl
Sent from my Incredible using XDA App
jdkoreclipse said:
put this on the root of ypur sd card, boot into bootloader, and let the phone do the rest. YOU MAY LOSE ALL DATA
http://www.mediafire.com/?yum40znzwmmmtyl
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
just tried this, and it did not solve the problem. any other suggestions?
thanks for the help btw, i really appreciate it.
theanswer said:
just tried this, and it did not solve the problem. any other suggestions?
thanks for the help btw, i really appreciate it.
Click to expand...
Click to collapse
ruu, hard reset, and stock img, that is it. Your dinc is hosed. I hope you have insurance??? (this is the part where you say yes)
Sent from my Incredible using XDA App
Welp
While it may not help you, it can't hurt to say. I was having huge reboot issues ... highest number was 13 initial white screen / black screen cycles. I could also NEVER get into Recovery (I could get into HBOOT but when I chose recovery, it would do TWO reboots, the second being full). A battery pull was usually needed.
However, the one thing that allowed me into recovery, etc., was to let the phone charge overnight to 100% and let it be. In the morning, the phone was charged and cool. At that point, I could easily get into recovery, start up, etc.
While I am sure you have tried this; just wanted to note to make sure your phone is cool and you did a battery pull for at least 10 minutes.
I too have this issue
I also have a stock incredible that I bought second hand, which when i bought it, I checked to make sure the device was ok. When I activated it like 2 minutes later it entered a reboot loop. I thought it might be a botched PRL so I went to the Verizon Rep (I met the seller at vz store) and he performed a forced activation. It continued the reboot loop so I took it home. I noticed that if I was outside or near a window, the phone would act normally. I used this discovery to root it and install a recovery. I flashed a few kernel/rom/radio combinations including stock rooted but there was no luck. I flashed back to RUU and it continued to reboot loop. The next day I reversed the activation back to my Eris. 20 minutes later the phone is perfect. I reactivated the device and it commenced rebooting immediately. I took it back to the store and they noted the same behavior. I'm pretty sure it's a faulty radio but since it wasn't activated on the original # they couldn't warranty it. They did tell me if the original owner activates it, they will warranty it so were gonna do that. I hope nobody else has this issue, but if you have this problem, try RUU, and if that doesnt fix it, it's likely hardware failure
I Can't believe this. I run a stock rom.
I got the update notice on my phone about 5 hours ago. I said, sure why not, I haven't modded my phone, shouldn't be any issues. WRong. Now its stuck on the black "Sumsung" boot screen. won't move!
suggestions...
Odin
10char
Have you tryed pulling the battery out and restarting
Sent from my GT-I9100 using XDA App
I second! That! Odin back?
Sent from my SPH-D700 using XDA App
You should pull battery and try again.
Sent from my SPH-D700 using XDA App
i've pulled the battery, try to restart. stays stuck on "Samsung" screen.
I can't get into recover (volume down + camera + power) either.
collegedude10 said:
i've pulled the battery, try to restart. stays stuck on "Samsung" screen.
I can't get into recover (volume down + camera + power) either.
Click to expand...
Click to collapse
Then you will have to Odin back to stock.
Sent from my SPH-D700 using XDA App
I had the same problem. Running stock and received the update notice and upon installing was stuck on the samsung screen. ODINed back to stock and tried the manual update with the same result, stuck on samsung screen.
Took the phone to sprint and got a replacement, said they couldn't get it to work on my phone either. Not only did they give me a new phone but I also got the box of goodies that comes with it too.
ToiletDuck555 said:
I had the same problem. Running stock and received the update notice and upon installing was stuck on the samsung screen. ODINed back to stock and tried the manual update with the same result, stuck on samsung screen.
Took the phone to sprint and got a replacement, said they couldn't get it to work on my phone either. Not only did they give me a new phone but I also got the box of goodies that comes with it too.
Click to expand...
Click to collapse
You might be on to something there.....
Sent from my SPH-D700 using xda premium
Sounds like the stock update failed to install your Kernel. Nice going sprint ^-^
You have two options; One. Follow this guide here. Or, go to sprint and tell them what happened and they should do odin flash it for you =)
Similar thing happened to my wife's Epic 4G yesterday morning. Instead of the stuck logo there was a bunch of error messages and finally I realized that there was some kind of backup program running. It was frozen and since I'm not up on Samsung I took it to the nearby Sprint service center. They futzed around with it for about an hour and said they had tried everything and there was nothing they could do since it was rooted - it was bricked and I should buy a new phone.
Not so fast Kimosabe!
I looked closer and figured out that the stuff I was looking at was a menu that could be scrolled with the volume keys and selected with the power button. That got it to reboot to the Samsung logo and no amount of battery removal or other manipulation would change that. So, off I went to another Sprint Repair facility a little further away. Success! After about 90 minutes they had it working with 2.3.5 loaded and my wife is very happy, the way wives should be.
I haven't checked but I doubt it's rooted anymore which is fine as she doesn't need any of the extended functions rooting offers anyway.
brobin111 said:
Similar thing happened to my wife's Epic 4G yesterday morning. Instead of the stuck logo there was a bunch of error messages and finally I realized that there was some kind of backup program running. It was frozen and since I'm not up on Samsung I took it to the nearby Sprint service center. They futzed around with it for about an hour and said they had tried everything and there was nothing they could do since it was rooted - it was bricked and I should buy a new phone.
Not so fast Kimosabe!
I looked closer and figured out that the stuff I was looking at was a menu that could be scrolled with the volume keys and selected with the power button. That got it to reboot to the Samsung logo and no amount of battery removal or other manipulation would change that. So, off I went to another Sprint Repair facility a little further away. Success! After about 90 minutes they had it working with 2.3.5 loaded and my wife is very happy, the way wives should be.
I haven't checked but I doubt it's rooted anymore which is fine as she doesn't need any of the extended functions rooting offers anyway.
Click to expand...
Click to collapse
If you can't flash your phone back to stock from a soft brick, you shouldn't be downloading things from here.
Sent from my SPH-D700 using xda premium
Same thing happened to my wifes Epic. It was stocked but rooted. Same as described in the first post. She got the text or message that her upgrade was ready, but after following the steps, her phone said it was up to date. After powering it off and then back on, it wouldn't get past the Samsung screen.
I tried everything. It wouldn't boot to recovery, only download mode. I had to odin it back to EC05. Then I upgraded it manually to Gingerbread with the official update.zip. Working great.
I never got the text on my phone that my upgrade was ready. I just manually updated to Gingerbread.
BTW. Battery on both phones has never been better.
Hope you got your phone working too.
Smoke.007
kennyglass123 said:
Then you will have to Odin back to stock.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Agree with Kenny! You should odin back to stock.
I to can verify . I had just gotten a new replace 3days before the update. When the update came out I ran it and bam stuck at the sammy screen . I tried to odin and that wouldn't even work . So took it to sprint service center and they said it was a no go for them . Would have to be replaced would even go to download . Called sprint and *****ed up a storm . They over nighted me another phone . 2 phone in 1 week. Pretty sure they hate me now but screw it . This was in no way user error . I've been seeing a few other case of similar issue.
On a side note . I've found that the best way to odin if it won't go into dl is by removing battery and sd plug in to usb with odin up and then press 1 and power button at the same time . But I think it only works on soft bricks in this case it might work not sure but worth a try.
Sent from my SPH-D700 using xda premium
I looked around if I'm correct some epics have a hardware reset just under the camera according to mystery emotions he has a post to restore it even on a solid brick. However it's. Been known to not be on every epic. I happen to have one woot!
Sent From my 1.4Ghz V6'd Legendary Epic >-<
Three mornings ago I woke up to find wifi couldn't start on my phone. Nothing I tried fixed it. It's a hardware issue. Verizon refused to fix it because I admitted it was rooted. The local repair shop is afraid of breaking the digitizer if they take it apart and besides, who knows what's wrong?
This is my last straw with Verizon. I have signed up with T-Mobile. My replacement Note 4 will be here today or tomorrow. I really loved this community. Yall are a great bunch of guys and I will miss you. But I refuse to take any more of Verizon's crap. I'll drop in to say Hi from time to time but for now I have to learn about the T-Mobile development community. Later.
Noooo. This is bitter sweet because you will enjoy yourself with all the Tmobile development. Frankly any Note 4 variant besides Verizon and AT&T you'll be happy. Good luck man and thanks for all your help.
jcip17 said:
Noooo. This is bitter sweet because you will enjoy yourself with all the Tmobile development. Frankly any Note 4 variant besides Verizon and AT&T you'll be happy. Good luck man and thanks for all your help.
Click to expand...
Click to collapse
Thanks man. You're one of the people who make XDA such a cool place. It ain't like this is goodbye forever. I'll be in here fairly often. Tapatalk keeps me notified of what goes on. See you later.
Sent from my SCH-I535 using Tapatalk
Sorry to hear you're leaving. You've been a great help to a lot of us. I share your feelings toward Verizon, they are just too big to care. So go on.... have some fun with the new toy....there's so much development over there... I'm actually over in the note4 snapdragon side more recently because I'm running all other than Verizon MM stuff. Anyways thanks Stuey for your contributions and help!
Sent from my SM-N920V using XDA-Developers mobile app
stueycaster said:
Three mornings ago I woke up to find wifi couldn't start on my phone. Nothing I tried fixed it. It's a hardware issue. Verizon refused to fix it because I admitted it was rooted. The local repair shop is afraid of breaking the digitizer if they take it apart and besides, who knows what's wrong?
This is my last straw with Verizon. I have signed up with T-Mobile. My replacement Note 4 will be here today or tomorrow. I really loved this community. Yall are a great bunch of guys and I will miss you. But I refuse to take any more of Verizon's crap. I'll drop in to say Hi from time to time but for now I have to learn about the T-Mobile development community. Later.
Click to expand...
Click to collapse
I'd be happy to do some low-level troubleshooting with you. That's a strange piece of hardware to fail, one that isn't very common. I think there might be something else going on.
ryanbg said:
I'd be happy to do some low-level troubleshooting with you. That's a strange piece of hardware to fail, one that isn't very common. I think there might be something else going on.
Click to expand...
Click to collapse
Nice.
Sent from my SM-N920V using XDA-Developers mobile app
ryanbg said:
I'd be happy to do some low-level troubleshooting with you. That's a strange piece of hardware to fail, one that isn't very common. I think there might be something else going on.
Click to expand...
Click to collapse
Ok. I reset it back to the condition it was when I got it. I odin'd the ANI1 modem and the ANJ5 stock restore. I don't know what else to do.
I don't have the new phone yet. Probably tomorrow evening or Monday. If I can fix it and don't decide to cancel TMo I could sell it. It shows a little wear around the USB port but other than that it's totally scratch free. It was always in an Otterbox case.
But I'd love to keep using it.
Sent from my SCH-I535 using Tapatalk
stueycaster said:
Ok. I reset it back to the condition it was when I got it. I odin'd the ANI1 modem and the ANJ5 stock restore. I don't know what else to do.
I don't have the new phone yet. Probably tomorrow evening or Monday. If I can fix it and don't decide to cancel TMo I could sell it. It shows a little wear around the USB port but other than that it's totally scratch free. It was always in an Otterbox case.
But I'd love to keep using it.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Just flash the full PBA1 tar first. Don't flash different bits and pieces, that could cause issues here.. Here's the link: Download
ryanbg said:
Just flash the full PBA1 tar first. Don't flash different bits and pieces, that could cause issues here.. Here's the link: Download
Click to expand...
Click to collapse
Isn't that going to overwrite the Dev Ed bootloader? I guess that's ok though because it's useless as a Developer Edition anyway right? And then I can do the unlock procedure.
It failed. It wants me to do the Verizon Software Repair Assistant. It probably failed because of the hardware issue right?
Update: On the second try it flashed and finished booting up. There were only 22 apps to optimize. Wifi still doesn't work. It did lose developer mode.
stueycaster said:
It failed. It wants me to do the Verizon Software Repair Assistant. It probably failed because of the hardware issue right?
Update: On the second try it flashed and finished booting up. There were only 22 apps to optimize. Wifi still doesn't work. It did lose developer mode.
Click to expand...
Click to collapse
We'll get DE back after you are stable. Uninstall Verizon Software Repair Assistant and Kies if you have it. To me, it looks like a USB/Driver/Software conflict going on preventing a successful flash. Try a different computer, and a different USB cable. Something is interrupting the write process.
I don't have access to another computer. Sometimes this computer does act up. That's M$ and their upgrade to W10 for you. Maybe after a fresh reboot?
I don't have the other stuff.
Update: Maybe I can borrow a computer. I don't know when though. I'll look into it.
stueycaster said:
I don't have access to another computer. Sometimes this computer does act up. That's M$ and their upgrade to W10 for you. Maybe after a fresh reboot?
I don't have the other stuff.
Update: Maybe I can borrow a computer. I don't know when though. I'll look into it.
Click to expand...
Click to collapse
That happened to me and I flashed back to stock full restore locked bootloader and that worked for me. My phone ended up craping out on me a couple weeks later< first i got a "failed to boot MMC read error" then when i tried to boot it, it as completely dead.
Dark_Plasma said:
That happened to me and I flashed back to stock full restore locked bootloader and that worked for me. My phone ended up craping out on me a couple weeks later< first i got a "failed to boot MMC read error" then when i tried to boot it, it as completely dead.
Click to expand...
Click to collapse
I flashed a ton of stuff through Odin and TWRP both. Everything seemed to flash correctly with the same result every time. Wifi wouldn't work. I can't help but think it's hardware. I think it baked this jumper wire that's right between the battery and the Wifi til it broke. Too many times heating it up by optimizing apps.
Sent from my SCH-I535 using Tapatalk
stueycaster said:
I flashed a ton of stuff through Odin and TWRP both. Everything seemed to flash correctly with the same result every time. Wifi wouldn't work. I can't help but think it's hardware. I think it baked this jumper wire that's right between the battery and the Wifi til it broke. Too many times heating it up by optimizing apps.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Sorry to hear that....hoped you could revive it. For sure these things get blistering hot! I've been flashing like crazy this past week thinking my phone is cookin! So I know what your saying could be the culprit. Still hoping you find a way!
Sent from my SM-N920V using XDA-Developers mobile app
My note 4 is completely stock. Never been rooted. About a month ago it began having difficulties where it would turn off then back on again. These would progressively happen more and more each day until eventually, it booted into download mode by itself. I looked things up and noticed that if you flashed the stock firmware back on it should work. I did this. It worked for a day until now where it went back into download mode and I tried to boot it normally and it goes straight to download each time. I tried reflashing the firmware but Odin fails every time. Tried multiple versions of Odin as well. Same outcome. Please help
Update
Phone will no longer power on in any state. Yet computer still recognizes it as a usb but cannot access it.
Hibernat said:
Phone will no longer power on in any state. Yet computer still recognizes it as a usb but cannot access it.
Click to expand...
Click to collapse
if your phone is not rooteed, then its not a subject to xda.
Xda is a forum about hacking its not a church.
it might be better to go a Samsung center. No?
Or post it in Facebook of Samsung!
I understand it is for rooted phones however it dealt with things people on this forum would have known about and I was hoping to get some help. However obviously it seems decently unwelcoming. Thanks for your lack of hospitality and help. Much appreciated
Rajada said:
if your phone is not rooteed, then its not a subject to xda.
Xda is a forum about hacking its not a church.
it might be better to go a Samsung center. No?
Or post it in Facebook of Samsung!
Click to expand...
Click to collapse
I don't remember XDA requiring users to have a rooted device. There are plenty of XDA forums and threads that have nothing to do with root. You don't have to be rude to a user asking for help with their device. I'm not a Moderator or a Recognized Developer/Contributor but, damn man, do you have to **** on someone's post when they're asking for help? Can you help the OP? Do you have any experience with his concern? I know alot about Android to where I can try and help people but I don't know everything and I don't post **** like that and try to drive someone away.
Sent from my Nexus 6 using XDA-Developers mobile app
Hibernat said:
My note 4 is completely stock. Never been rooted. About a month ago it began having difficulties where it would turn off then back on again. These would progressively happen more and more each day until eventually, it booted into download mode by itself. I looked things up and noticed that if you flashed the stock firmware back on it should work. I did this. It worked for a day until now where it went back into download mode and I tried to boot it normally and it goes straight to download each time. I tried reflashing the firmware but Odin fails every time. Tried multiple versions of Odin as well. Same outcome. Please help
Click to expand...
Click to collapse
Can you give me a little info about your device? What model number? What version of Android etc...
Sent from my Nexus 6 using XDA-Developers mobile app
Probably faultly hardware
Thanks
Thank you for all of the interest in helping me out. However, I recently opened up the phone to find out that a good chunk of the internals are burned from something frying. Amazing I didn't notice heat or electrical smoke when it happened. I'm guessing when Odin3 failed it was due to the frying cutting off a path. Unfortunately, I just need to get it replaced.
Hibernat said:
Thank you for all of the interest in helping me out. However, I recently opened up the phone to find out that a good chunk of the internals are burned from something frying. Amazing I didn't notice heat or electrical smoke when it happened. I'm guessing when Odin3 failed it was due to the frying cutting off a path. Unfortunately, I just need to get it replaced.
Click to expand...
Click to collapse
Well, that stinks. Too bad it was unrecoverable. Good luck on getting a new device.
Sent from my Nexus 6 using XDA-Developers mobile app
Outside of rooting to flash custom Roms is there an official way to downgrade. Nougat is junk. Both of my phone's will not hold a charge more than a couple hours and have issues waking up from sleep, and a myriad of other issues I have with the update.
If not I'll have to smash these and hope for a non updated model upon replacement.
https://forum.xda-developers.com/showthread.php?t=3549458
Sent from my SM-G935V using Tapatalk
Yeah I saw that, I've yet to get Odin to recognize my phone. I guess I'm going to have to try another PC.
Do any of those have the update function killed?
xjman said:
Outside of rooting to flash custom Roms is there an official way to downgrade. Nougat is junk. Both of my phone's will not hold a charge more than a couple hours and have issues waking up from sleep, and a myriad of other issues I have with the update.
If not I'll have to smash these and hope for a non updated model upon replacement.
Click to expand...
Click to collapse
I think problem is with some app you have. Check this first then try to downgrade. Or try clean install by downgrading to APK1 and OTA to BQA6.
If you have problem with phone not recognised by PC, maybe you have problem with hardware it self. Go and exchange. Nougat for me holds battery about 25% longer.
Clicking from Edge of Galaxy
Yeah resetting the phones was my first step. They do it without any other app installed.
I'm just going to have to mess with Odin until my driver's accept the phone. It's been ages since I've had to mess with it, and it js just frustrating
xjman said:
Yeah resetting the phones was my first step. They do it without any other app installed.
I'm just going to have to mess with Odin until my driver's accept the phone. It's been ages since I've had to mess with it, and it js just frustrating
Click to expand...
Click to collapse
Did you yet Princes Odin?
Sent from my SM-G935V using Tapatalk
What? I haven't messed with it since Saturday. I'll update when I get a chance. Today was the first nice day since a storm wed that downed a bunch of junk in my yard, and damaged the roof to my barn.
I likely could have bad drivers or the wrong version of Odin. I've not used Odin since the days of the Samsung moment.
xjman said:
What? I haven't messed with it since Saturday. I'll update when I get a chance. Today was the first nice day since a storm wed that downed a bunch of junk in my yard, and damaged the roof to my barn.
I likely could have bad drivers or the wrong version of Odin. I've not used Odin since the days of the Samsung moment.
Click to expand...
Click to collapse
Try Princes Odin* sorry, autocorrect messed me up.
I have it here https://mega.nz/#!CwQhVCqb!yq_p3ZsUB8kXTSxlhK8XFG6MZRhx7cH3XzSiw36_wc0
Try it with the 4APK1 Firmware. Hope this works.
Sent from my SM-G935V using Tapatalk
Well my problem as escalated on one phone. Now any time I plug it in to charge it tells me moisture detected. Never been wet, never been damp.
Yeah I think I'm just going to move on to different phones. I'm not a fan of the bugs I've encountered on both, and they don't inspire confidence in longer term ownership. Thanks for the help folks.
And now the second phone has the same issue.
There is no way this is hardware related. Is anyone else having issues with theirs. I find it extremely hard to believe two phones having identical issues after an update is coincidence.
Standard OTA update to BQA6 with no problems.
xjman said:
Yeah I saw that, I've yet to get Odin to recognize my phone. I guess I'm going to have to try another PC.
Do any of those have the update function killed?
Click to expand...
Click to collapse
norbarb said:
I think problem is with some app you have. Check this first then try to downgrade. Or try clean install by downgrading to APK1 and OTA to BQA6.
If you have problem with phone not recognised by PC, maybe you have problem with hardware it self. Go and exchange. Nougat for me holds battery about 25% longer.
Clicking from Edge of Galaxy
Click to expand...
Click to collapse
Anytime I had an Odin issue it was because of USB drivers. I uninstalled all USB drivers from that device the (complex way) and then everything worked properly. It would seem if I switched USB ports it would work again, then not long after that I would run out of USB ports. I would have to uninstall the drivers manually and reinstall them.
Sent from my SAMSUNG-SM-G935A using Tapatalk