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 >-<
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 have a early version of the Vibrant that I have rooted and installed Roms over.. T-Mo sent me a refurb because I was complaining about the poor GPS locks.. we wanted to see if another Vibrant would do better... unfortunately it doesnt...
Today I started adding a ROM to the new phone and it went haywire on me... wouldnt go into Recovery, hard time going into Download mode... literally 2 hours later after a scary Orange explanation mark on the screen did it finally cooperate and I ODIN'd the stock rom back on... turns out the stock rom wouldnt get passed the Galaxy S screen... so then I was about to get into recovery and reinstalled Obsidian since the zip was still on the card... now I can go in and erase everything off the internal memory... should I just return it and keep my early version... my original phone never acted up like this
if you wanna sell it... PM me
JD76 said:
I have a early version of the Vibrant that I have rooted and installed Roms over.. T-Mo sent me a refurb because I was complaining about the poor GPS locks.. we wanted to see if another Vibrant would do better... unfortunately it doesnt...
Today I started adding a ROM to the new phone and it went haywire on me... wouldnt go into Recovery, hard time going into Download mode... literally 2 hours later after a scary Orange explanation mark on the screen did it finally cooperate and I ODIN'd the stock rom back on... turns out the stock rom wouldnt get passed the Galaxy S screen... so then I was about to get into recovery and reinstalled Obsidian since the zip was still on the card... now I can go in and erase everything off the internal memory... should I just return it and keep my early version... my original phone never acted up like this
Click to expand...
Click to collapse
Tell them to send you a new one. I'd be fine with a refurb phone if everything worked. but if it doesn't then what's the point of the exchange?
JD76 said:
I have a early version of the Vibrant that I have rooted and installed Roms over.. T-Mo sent me a refurb because I was complaining about the poor GPS locks.. we wanted to see if another Vibrant would do better... unfortunately it doesnt...
Today I started adding a ROM to the new phone and it went haywire on me... wouldnt go into Recovery, hard time going into Download mode... literally 2 hours later after a scary Orange explanation mark on the screen did it finally cooperate and I ODIN'd the stock rom back on... turns out the stock rom wouldnt get passed the Galaxy S screen... so then I was about to get into recovery and reinstalled Obsidian since the zip was still on the card... now I can go in and erase everything off the internal memory... should I just return it and keep my early version... my original phone never acted up like this
Click to expand...
Click to collapse
Change it, it could be defective
Since the replacement didn't show improvement on gps, If you still have your original phone, keep it and send the refurb back...
Sent from my SGH-T959 using XDA App
They sent me refurb unit too. I sent it back. xP
Thanks everyone.. Im back to my old one... I went back to stock J16 with a lag fix and a MobileAP mod on it...
If you didn't flash JFD you're doing it wrong. All you will get is a refurbished phone. They're not giving out new ones.
I have 7 days to return it so im testing out every froyo ROM out before I give it back squeeky clean...lol
Blame people who get replacements for issues that exist in every phone at the software level for the refurbs.
I got two brand new exchanges in a row, though.
Ok so my phone was bricked and Ive been trying these past few days to fix it with odin. Odin doesnt work on my computer though. Today I connected it and odin started to work and it started to flash, it got to the factoryfs part and then froze, so I disconnected it.
Now my phone won't enter download mode and it won't turn on anymore.. what can I do?
EDITL: So i got into the sprint store and tell them that some update made my screen turn off and it wouldnt turn back on/nor charge. They were working on it for like an hour then they came to me and said that i have to pay 35$ then i can pick up a new one on tuesday. Yay and I was able to ad insurance because I didnt have it before.
I'd try just taking it back to Sprint and tell them that you were performing an OTA update and it just died in the middle of it and you don't know what to do.
Is your battery charged? Because it should at least power on
Sent from my SPH-D700 using Tapatalk
hayabusa1300cc said:
Is your battery charged? Because it should at least power on
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Im not sure but it doesnt charge even if I plug it into the wall =( And yeah ill try to go to the sprint store tomorrow, if they question me about rooting should I deny everything? Can they check if the phone is rooted?
Yeah, just play dumb and act like you don't know what happened with it, and it just went blank during an OTA update. They can't see if the phone is rooted or not as far as I'm concerned, but if you bring it to a Sprint repair shop, I'm pretty certain that they won't know.
Actually just try pulling the battery for 3 minutes,then download mode should work,then re-odin...This has happened to me 3 times,really thought it was bricked the first time.
Sent from my Frankenstein FROYO ROM using XDA App
ecooce said:
Actually just try pulling the battery for 3 minutes,then download mode should work,then re-odin...This has happened to me 3 times,really thought it was bricked the first time.
Sent from my Frankenstein FROYO ROM using XDA App
Click to expand...
Click to collapse
same thing happened to me when i first started flashing roms with this phone.. just give it alittle time, plug it in with the battery to make sure its getting a charge and it should boot back into download mode.
kalico17 said:
same thing happened to me when i first started flashing roms with this phone.. just give it alittle time, plug it in with the battery to make sure its getting a charge and it should boot back into download mode.
Click to expand...
Click to collapse
I did that and nothing happens, it doesnt charge anymore i think. Im pretty sure its hard bricked now :/
The Sprint store is going to try another battery first before they throw the towel in on the phone. If that doesn't work then yes play dumb and do exactly as previously stated by @brianhuangbh.... "Was doing an OTA and it just froze". Good luck and let us know what they said
sasha101 said:
Ok so my phone was bricked and Ive been trying these past few days to fix it with odin. Odin doesnt work on my computer though. Today I connected it and odin started to work and it started to flash, it got to the factoryfs part and then froze, so I disconnected it.
Now my phone won't enter download mode and it won't turn on anymore.. what can I do?
Click to expand...
Click to collapse
same thing happened to me, that i ended up getting another phone. anyway i was fooling around with my brick epic when i decided to put in a fully charged battery in. nothing happened but i noticed after a while that the phone was warm. i pulled the battery then waited a couple of minutes then put it back in and held the power and 1 button and what do you know, it went to download mode. i used Odin CORRECTLY this time and now it works. when using odin make sure reboot is the only box checked and that u start Odin first then plug the epic in.
So i went to the sprint store and everything turned out good
Awesome congrats hopefully the new phone doesn't act up on ya if you decide to root lol
Sent from my SPH-D700 using XDA App
tphillips78 said:
Awesome congrats hopefully the new phone doesn't act up on ya if you decide to root lol
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Im gonna stay away from rooting haha, came too close this time. Plus my computer refuses to co-operate with odin so i cant unbrick it.
Good stuff if u do decide to root feel free to pm me if u have questions. The people of xda were very helpful to me so I'm returning the favor lol.
Sent from my SPH-D700 using XDA App
Need to take my phone back to att for a faculty gps and after reading around here i found out it might hard brick it.
Well i didn't hard brick, but i am stuck on boot loop.
Any help?
It goes to the att boot animation, then goes back to the Motorola logo one...
I used a File called 2.3.4_pudding_preroot or something like that.
I had a similar problem once and re flashing fixed it, which ill try when i get home from errands, but i wanted to post and ask for suggestions i til I get back to try it.
Im gonna stop at an att store and see if they can give me a replenished one, but i doubt that...
There is probably a thread related to this somewhere too, but im posting from Tapatalk so its hard to look around. Lol
Thanks in advance!
Sent from my Xoom using Tapatalk
Sent from my Xoom using Tapatalk
At&t will refer you to Motorola ...I had the same problem with my ATRIX gps too and actually hard bricked it in the processes if returning to stock just tell them when updating the rom your phone died ...they will overall send you a new one
Sent from my MB860 using XDA App
yokozuna82 said:
At&t will refer you to Motorola ...I had the same problem with my ATRIX gps too and actually hard bricked it in the processes if returning to stock just tell them when updating the rom your phone died ...they will overall send you a new one
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Is there a number for motorola warranty you have? How do I start the process?
Sent from my Xoom using Tapatalk
Just left the att store. There is apparently a DSC (device support center) about 10 miles from here and they'll just replace the phone on the spot. Hopefully they won't say anything about the 'unlocked' text.
Let you know what happens
Sent from my Xoom using Tapatalk
In recovery mode wipe the cache then factory reset. Don't restart the system. Pull the battery out and place it back without touching the power button, it might happen when putting the battery cover back on.
Reflash the desire. sbf file as you normally do with the latest version of MotoHelper and RsdLite program that you can find. Make sure your battery have enough charge for next flash attempt.
The above instructions are what I would do in your circumstances. Please make sure the. sbf is exactly same version as what is on your handset. If the flashing .sbf has higher version then it will be safe.
Good Luck!
CSharpHeaven said:
In recovery mode wipe the cache then factory reset. Don't restart the system. Pull the battery out and place it back without touching the power button, it might happen when putting the battery cover back on.
Reflash the desire. sbf file as you normally do with the latest version of MotoHelper and RsdLite program that you can find. Make sure your battery have enough charge for next flash attempt.
The above instructions are what I would do in your circumstances. Please make sure the. sbf is exactly same version as what is on your handset. If the flashing .sbf has higher version then it will be safe.
Good Luck!
Click to expand...
Click to collapse
Ok got it running at the att store and was able to download GPS status and i compared the performance to the xoom's GPS status. He saw how the GPS just couldn't lock on so he said hell swap it out for me. Waiting on the replacement now
Sent from my Xoom using Tapatalk
Got a new phone. GPS works. Gonna have to sbf again for Unlock and pre root now. Hopefully this one will work out. Lol...
Is there a way to Unlock and root without sbf??
Sent from my Xoom using Tapatalk
razorseal said:
Ok got it running at the att store and was able to download GPS status and i compared the performance to the xoom's GPS status. He saw how the GPS just couldn't lock on so he said hell swap it out for me. Waiting on the replacement now
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Good to hear that. Please make sure you will read the following thread once you got your new Atrix. I get GPS lock in the UK within seconds. I even managed to get GPS lock indoors. A must for every handset really.
http://forum.xda-developers.com/showthread.php?t=1239713
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