Database Users

My phone bricked by HTC update

Anyone else been bricked by the HTC update?
If so what kind of response did you get from Sprint? Any suggestions for dealing with them?
The current state of my phone... completely dead, it will not turn on.. connecting it to a pc doesnt show a device is connected..

Try taking out the battery for a little bit. If that doesn't work, just take it back to Sprint. They'll give you a replacement Evo or a loaner for the time being until a new shipment comes in.

They might think you bricked it through rooting.
Not sure on there policies.. Let us know

sorry about ur issue but i have to hand it to u bro.. congratulations on using the word "bricked" correctly regarding the status of ur phone.. for god knows how long ppl have been calling their phone bricked if their volume button stopped working.. im gonna go celebrate with a cheesecake!

Engadget confirmed 10 minutes ago that the OTA has been halted, its happening to lots of people I guess
Sent from my PC36100 using XDA App

http://www.phonenews.com/sprint-aborts-evo-4g-update-amid-concerns-of-failed-updates-11567/

Mine went as smooth as butter. Phone is much better as well.

Mine went good as well. No issues, and phone is much more responsive. I guess it pays to not root.

My stock EVO update was scary. It took between 10 and 15 minutes. It seemed to be in an endless boot loop. It rebooted about 4 times and it finally worked on the 5th. At some point I thought, "if it boots again, I'm pulling the battery." At the end, the voicemail icon was replaced by an error message. I trashed it and reinserted the original icon. There was no indication or hour glass or something letting me know the process was normal. It really seemed like something was wrong.
I can understand if some customers aborted the process pulling the battery, thus bricking their phones. I don't think it would be their fault.

I think a lot of phones were bricked because of user error. A lot of people probably pulled their batteries. I do agree that there should be some kind of indication that the update was still in progress. I'm rooted and I haven't updated yet since I already get amazing battery life.

Uh oh.
Sprint pulled the update.

My condolences to those that have been bricked.
FYI - my update went very smooth. Stock EVO, unrooted. Did not make the mistake of accepting yesterday's update twice though ;-)

What did Sprint said about your phone, will they exchange it?

bricked mine yesterday.
Made the mistake of running the patch twice. Being used to windows I like to patch first and ask questions later.
Learned my lesson.
1st patch went through smoothly. Everything was great except a few widgets need to be reloaded. Got prompted for a new patch in the afternoon and ran that without checking xda first. And that was all it wrote.
Called Sprint last night and tech on the phone knew exactly what happened to the phone and made an appointment for me this morning to get it exchanged. He said a lot of people are calling in about the same issue. Since it's within the 30 day period he informed me that I will be getting a brand new replacement.
Went to the store this morning and confirmed my phone is DOA. and *suprise* no phone in stock. They indicated they will be order me a new phone. The MOD also told me there are five people showed up last night with bricked evo's.
Called Sprint again after the visit. They are looking for another phone I can use in the mean time.
Not impressed with HTC at this point.

if you rooted your phone, then tried to apply this update, your screwed.
It will brick.
Good luck returning it. Not covered by insurance when you tinker with it.
If you do get a new phone, don't be surprised to see a big bill once they look at what you reprogrammed later on.

kthejoker20 said:
if you rooted your phone, then tried to apply this update, your screwed.
It will brick.
Good luck returning it. Not covered by insurance when you tinker with it.
If you do get a new phone, don't be surprised to see a big bill once they look at what you reprogrammed later on.
Click to expand...
Click to collapse
don't know who you're talking to but my phone is completely stock. (unrooted)

kthejoker20:
The reason it bricked was because of double updating, not because of rooting it.
kennyc1:
With that said, sorry for your trouble. Hope you get a new one soon!

AssassinsLament said:
kthejoker20:
The reason it bricked was because of double updating, not because of rooting it.
kennyc1:
With that said, sorry for your trouble. Hope you get a new one soon!
Click to expand...
Click to collapse
Thanks, the only saving grace of this whole fubar is that having heard some horror stories about Sprint's CS before. I was treated very well by everyone I spoke with so far.
Fingers crossed.

kthejoker20 said:
if you rooted your phone, then tried to apply this update, your screwed.
It will brick.
Good luck returning it. Not covered by insurance when you tinker with it.
If you do get a new phone, don't be surprised to see a big bill once they look at what you reprogrammed later on.
Click to expand...
Click to collapse
I was rooted with unrevoked. Ran Update everything went smooth just lost root. Did not update twice. baseband 2.05.00.06.10 software 1.47.651.1

My phone was not rooted... I havent really seen a point to do it yet... (i did root when I had a hero)
I went to the sprint store, it took about 30-40 min to get a new phone..
But now I want to update it... just a bit concerned about updating it (for good reason lol)

HTC incredible endless boot loop

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

brick?

i was running fission rc1 on my d2g, used frm to download stock d2g deodexed blah blsh, flashed it, stuck on motorola m screen. cant get it to boot to bootstrap recovery for ****. only regular recovery...i could cry
edit: omg im gonna throw up. please tell me theres something i can do.
EDIT: ok...so if it is bricked and i have the $1.99 or $2.99 insurance, whatever....can i get it replaced...and if not, what if hypothetically speaking...it was smashed by a car...could i then get it replaced?

I am no expert, but lets try this, start the phone and as soon as the M appears, immediately pull the battery, and the put back in and start the phone. Lets see if the phone goes into ClockworkMod, and if it does, you can do a restore. Let me know how you make out.
MICP1480

no luck dude. thanks tho
EDIT: just got off the phone with verizon, theyre sending me a new one. wasnt hard at all, i played dumb and acted like bootloader mode was a whole new world to me, she had me wipe the data and reboot, of course i had already done that to no avail so of course it didnt work this time either, she put me on hold and talked to a tech and then came back and said they'd send out a new one.

botnryan said:
no luck dude. thanks tho
EDIT: just got off the phone with verizon, theyre sending me a new one. wasnt hard at all, i played dumb and acted like bootloader mode was a whole new world to me, she had me wipe the data and reboot, of course i had already done that to no avail so of course it didnt work this time either, she put me on hold and talked to a tech and then came back and said they'd send out a new one.
Click to expand...
Click to collapse
They will check your phone to make sure there is no ROM's and that it is not rooted as that voids the warranty.

This just means moto needs to release the sbf for the D2G so we can fix them instead of moto/verizon getting a bunch of returned devices.
Sent from my DROID2 using XDA App

miketoasty said:
They will check your phone to make sure there is no ROM's and that it is not rooted as that voids the warranty.
Click to expand...
Click to collapse
really? and how will they know if its all messed up and wont even boot? plus i did a data and cache wipe of the phone thru the regular recovery, will that not kinda wipe away anything incriminating? Not to mention the last rom i flashed was the stock d2g rom, just deodexed and such

When you flash a custom ROM or root the phone, evidences remain in /system which survives data wipe.
It is another question how would they see that if phone is not booting.
If you sent it in already and you do not receive a nasty 600 dollar invoice in the following days/billing cycle stating you have voided the warranty, then they really do not check.
I guess all they do is to flash the oh-so-desired-by-everyone stock SBF and sell it as refurb or give it as replacement phone.

leobg said:
When you flash a custom ROM or root the phone, evidences remain in /system which survives data wipe.
It is another question how would they see that if phone is not booting.
If you sent it in already and you do not receive a nasty 600 dollar invoice in the following days/billing cycle stating you have voided the warranty, then they really do not check.
I guess all they do is to flash the oh-so-desired-by-everyone stock SBF and sell it as refurb or give it as replacement phone.
Click to expand...
Click to collapse
i havent sent it in yet as ill be recieving the replacement tomorrow...any ideas on how to prevent this? could a good strong magnet wipe the memory completely?

botnryan said:
i havent sent it in yet as ill be recieving the replacement tomorrow...any ideas on how to prevent this? could a good strong magnet wipe the memory completely?
Click to expand...
Click to collapse
without the sbf to get back in there isn't really much you can do. The stuff is on there and you don't have a way to get back in.
try to get into recovery by:
pulling battery (or powering down phone)
while completely off plug in to wall via charging cable
turn on phone while connected to power (if you get the battery screen press power again)
you should hopefully be in recovery (not sure if this method works on D2 G but it does wonders for the D2 but it's worth a try.)
unless you really flashed crazy and messed up recovery theoretically bootstrap should be there unless completely wiped it.

newk8600 said:
without the sbf to get back in there isn't really much you can do. The stuff is on there and you don't have a way to get back in.
try to get into recovery by:
pulling battery (or powering down phone)
while completely off plug in to wall via charging cable
turn on phone while connected to power (if you get the battery screen press power again)
you should hopefully be in recovery (not sure if this method works on D2 G but it does wonders for the D2 but it's worth a try.)
unless you really flashed crazy and messed up recovery theoretically bootstrap should be there unless completely wiped it.
Click to expand...
Click to collapse
dude i tried that with both usb and wall charger, no luck either way, i flashed stock d2g deodexed blah blah rom over fission rc1 and this happend. totally blows my mind. got my replacement today, super glad to be back away from the eris lol

botnryan said:
dude i tried that with both usb and wall charger, no luck either way, i flashed stock d2g deodexed blah blah rom over fission rc1 and this happend. totally blows my mind. got my replacement today, super glad to be back away from the eris lol
Click to expand...
Click to collapse
Just checking I didn't see you tried that specifically glad you got your replacement now you know to be very careful as the sbf isn't out yet.

sorry if that last post came off harsh lol, didnt mean it to, read it again and was like geez dude chill (at myself). So im really hoping they dont charge my ass for this, but i dont see how theyre going to know. if you flash an sbf, does it unroot it? Because, if thats what they do to phones like mine, then they wont know i had it rooted/rom'd right?

botnryan said:
sorry if that last post came off harsh lol, didnt mean it to, read it again and was like geez dude chill (at myself). So im really hoping they dont charge my ass for this, but i dont see how theyre going to know. if you flash an sbf, does it unroot it? Because, if thats what they do to phones like mine, then they wont know i had it rooted/rom'd right?
Click to expand...
Click to collapse
Yeah SBF put's it back to stock from factory software. Unless they have another way of getting in and see what was in there they won't know much unless after they SBF they can pull the residual data in data or cache but I don't think they will go to that extent only if D2 G's start dropping like flies.
If they would just release the SBF for us we could have fixed your phone in 15 minutes and it wouldn't have cost them anything at all.

newk8600 said:
Yeah SBF put's it back to stock from factory software. Unless they have another way of getting in and see what was in there they won't know much unless after they SBF they can pull the residual data in data or cache but I don't think they will go to that extent only if D2 G's start dropping like flies.
If they would just release the SBF for us we could have fixed your phone in 15 minutes and it wouldn't have cost them anything at all.
Click to expand...
Click to collapse
alrights, thanks man. i feel they probably wont be able to find anything out but im still going to use up my 10 day period i have to send the phone in just in case the sbf is magically released in that time period.

My Note 4 died. Goodbye Yall.

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

Moto Z Force Droid - Updated, then gets HOT, Bootloops...

FYI...This is my daughter's phone, and I am new to MOtorola.
Phone Information
Android version: 8.0.0
Security Patch: July 1, 2018
Configuration Version: F16.MOT.XT165.0.0
Baseband: M8996_1239.53.01.126.29.01R GVS
Kernel Version: 093.18.7Lperfg4966e91
BUild # OCLS27.76-69E
Symptoms
Gets HOT
When try to reset, nothing happens
When try to hook to Wifi, none of the SSIDs show up
Daughter said it was boootloop, but when I brought it home to work on, it is not bootlooping right now
I did try to boot to recovery, and found the screen in the first attachment when I select recovery
Then I selected ********* and get what is shown in the sideways attachment (I did rotate it on the PC, but it rotated back down here). I find it interesting in the second/sideways picture it says Baseband not found.
I was able to get a boot loop going, but I think that was due to low battery. I was also able (before the boot loop) to get it to boot into the OS. That was when I found I could not factory reset, or attach to wifi.
I found a post on here about using the Software Update - Software Upgrade/Repair assistant, and was thinking about going down that path.
Sound like a good idea?
What if I want to downgrade to V7x?
While waiting for thoughts here, I'm charging the phone, and plan to search more for threads about this type of problem, and maybe about how to downgrade to 7.
Thanks in advance...

I "NEVER" do over the air updates any more!!!
Too easy for the network to go down during the update!
Then the device operating code is not all there!
Use the insurance and get it replaced. Trying to fix it is a waste of time! Per my experience!
Kd
Sent from my XT1650 using Tapatalk

kidc4 said:
I "NEVER" do over the air updates any more!!!
Too easy for the network to go down during the update!
Then the device operating code is not all there!
Use the insurance and get it replaced. Trying to fix it is a waste of time! Per my experience!
Kd
Sent from my XT1650 using Tapatalk
Click to expand...
Click to collapse
She wasn't spending on insurance. Hasn't had problems over the years, so decided it wasn't worth the $.
I'm trying the repair from the option I listed. IT appeared to be going, downloaded and all. But it's been sitting on Installing for several minutes now, and it is remaining at 0% completed. So, I'm becoming skeptical it will work.

Best bet is to take to the verizon store or sprint and have the operating system reloaded...
Her stuff is backed up in the cloud. Once the os is reinstalled then reload her stuff to the phone.
The store can reload the os via a hard line with no chance of data loss. They may have to send it in to reinstall the os. But, I would insist on it! You bought the phone there and use their network. It is partly their fault and should not give you any grief over reloading the operating system...
Kd
Sent from my XT1650 using Tapatalk

Well, no good.
I want to downgrade to NCLS26.118-23-13-6-1. But I'm having trouble finding the file to download. Just finding dead links.
If anyone has a tip on where to find it, I'd love to hear it.

kidc4 said:
Best bet is to take to the verizon store or sprint and have the operating system reloaded...
Her stuff is backed up in the cloud. Once the os is reinstalled then reload her stuff to the phone.
The store can reload the os via a hard line with no chance of data loss. They may have to send it in to reinstall the os. But, I would insist on it! You bought the phone there and use their network. It is partly their fault and should not give you any grief over reloading the operating system...
Kd
Sent from my XT1650 using Tapatalk
Click to expand...
Click to collapse
She took it to Verizon, and they told her it couldn't be fixed. I don't think they wanted to bother with it. It was boot looping...which I think was just because of discharged battery. ONce I charged it a bit, I was able to boot, but have all the other issues.
I just ran it through repair that said it was successful, but still can't see any WiFi. ATM the phone is deactivated, as she had to get something to get calls. I wouldn't think that Wifi would stop if it's deactivated.
I agree with your comments about they should do it, but at this point, I think we're past that. I'm now trying to get it operational as a backup device.

ewingr said:
She took it to Verizon, and they told her it couldn't be fixed. I don't think they wanted to bother with it. It was boot looping...which I think was just because of discharged battery. ONce I charged it a bit, I was able to boot, but have all the other issues.
I just ran it through repair that said it was successful, but still can't see any WiFi. ATM the phone is deactivated, as she had to get something to get calls. I wouldn't think that Wifi would stop if it's deactivated.
I agree with your comments about they should do it, but at this point, I think we're past that. I'm now trying to get it operational as a backup device.
Click to expand...
Click to collapse
Look on line for full os file for the phone then hook it to the laptop or desktop and install from the computer via micro USB...
That may work. Best of luck!
Kd
Sent from my XT1650 using Tapatalk

kidc4 said:
Look on line for full os file for the phone then hook it to the laptop or desktop and install from the computer via micro USB...
That may work. Best of luck!
Kd
Sent from my XT1650 using Tapatalk
Click to expand...
Click to collapse
That's what I"m trying to do. I've been looking for NCLS26.118-23-13-6-1 for a half hour. All references to a download for it are dead links. I'm going to post a question to see if anyone can provide a link.

It's done for...
Well, I think I have found why Verizon shooed her out the door. The bootloader is locked, and given that, you can't even install any rom on it at all I guess. Not even the original rom.
I finally found a rom that might work. But after then trying a couple tools in the forums I found, it didn't work.
ON the second tool I found, there was someone asking if it worked for the Force, and someone said no, and that it would never work, because Moto has it locked down.
The first tool even had an optoin to pull the text to take to Moto to get the unlock code (although it didn't work...I had to use a fastboot cmd)...and Moto said it is not unlockable.
I guess it's just good for the trash bin.
Leaves me glad I'm not on Verizon, nor Motorola.
I appreciate the help and input you folks have supplied me. Hopefully this thread will help someone else, maybe prevent them from spending hours to a wasted project.

ewingr said:
Well, I think I have found why Verizon shooed her out the door. The bootloader is locked, and given that, you can't even install any rom on it at all I guess. Not even the original rom.
I finally found a rom that might work. But after then trying a couple tools in the forums I found, it didn't work.
ON the second tool I found, there was someone asking if it worked for the Force, and someone said no, and that it would never work, because Moto has it locked down.
The first tool even had an optoin to pull the text to take to Moto to get the unlock code (although it didn't work...I had to use a fastboot cmd)...and Moto said it is not unlockable.
I guess it's just good for the trash bin.
Leaves me glad I'm not on Verizon, nor Motorola.
I appreciate the help and input you folks have supplied me. Hopefully this thread will help someone else, maybe prevent them from spending hours to a wasted project.
Click to expand...
Click to collapse
No over air updates!
Period!
Kd
Sent from my XT1650 using Tapatalk

kidc4 said:
No over air updates!
Period!
Kd
Sent from my XT1650 using Tapatalk
Click to expand...
Click to collapse
That's what I gather, which getting up this morning and thinking about it, leaves me confused.
So, do they never update the phone? If so, how? And, then, why did 8.0 get put on this (which borked the phone)?
Thanks again, everyone.

ewingr said:
That's what I gather, which getting up this morning and thinking about it, leaves me confused.
So, do they never update the phone? If so, how? And, then, why did 8.0 get put on this (which borked the phone)?
Thanks again, everyone.
Click to expand...
Click to collapse
To stop updates!
Click Motorola update services
Then stop!
It is under apps and you must engage system applications view!
The screen shots will help...
Whenever you reboot you must go back in and turn it off!!! You run out of battery it will reboot when you power it back up!
Once I stopped over air updates! Had zero problems!
Kd
View attachment 4588278
Sent from my XT1650 using Tapatalk

I had issues with the latest update, as many others have (just check Verizon forums). It's known to kill the phone. Bluetooth, WiFi, Sim detection, battery.
Motorola knows of the issue and is asking users to contact them directly for service. You might try that. I personally has Verizon honor warranty because I still owe 2 payments and have been paying for device protection. I got a new phone FedEx the next day. There's no way I'll allow this new phone to accept the latest update.