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
Related
Just jumped ships from sprint and got my facinate. Today rooted with one click and tried installing clock work. Thmanage rom manager. All seems well then suddenly my phone freezes for ten minutes I have to do a battery pull. Phone wont boot in anyway or form now. No lights or signs of life other than if I hold the power button as long as its pressed. A device labeled SEC S5PC110 Test B/D appears in device manager. And that'd all it will do. Thinking about exchanging it tomorrow afternoon. Just letting the community know what happened to me any thoughts as how or what happened might be able to help future mishaps
I'd try doing an odin flash. Just search the forums for the step by step. If u can get the phone into flash mode.
Yeah dude, definitely try Odin. Did you try flashing cwm from within ROM manager? I ask because that doesn't work for our phones yet, and it wouldn't surprise me if that could cause problems. I would use Odin to flash it back to stock, and then use the very thorough guide on here on how to get cwm going.
Sent from my SCH-I500 using XDA App
hilarious post title.. good luck tho man. my only word of advice (tho it won't help u now) is to run back ups before you do anything major
illtema said:
hilarious post title.. good luck tho man. my only word of advice (tho it won't help u now) is to run back ups before you do anything major
Click to expand...
Click to collapse
Hard for him to do a backup when he got bricked installing CWM LOL
Possibly bootlocked.
Newer Fascinates seem to be locked. Don't know if there is any way to tell which you've got without attempting a modification of the system....which would of course, result in the above nastiness....
I would think that if newer fascinates were boot locked, so would mesmerizes and I first flashed the stock files for Verizon on my phone then went to elements zinc (which is awesome BTW) installed voodoo 1200 kernel and everything is working great for me. Could just be that he got a bunk phone or something
PhoenixPath said:
Possibly bootlocked.
Newer Fascinates seem to be locked. Don't know if there is any way to tell which you've got without attempting a modification of the system....which would of course, result in the above nastiness....
Click to expand...
Click to collapse
I'm thinking it's just Noob users who are bootlocked...
My phone is only a week old everything went fine root,cwm...
wisconsinated said:
I would think that if newer fascinates were boot locked, so would mesmerizes
Click to expand...
Click to collapse
Why would you think that? Same hardware!=same software...or we'd all be running USC's kernel/ROM.
Could just be that he got a bunk phone or something
Click to expand...
Click to collapse
Could be...which is why I said "possibly" instead of "definitely".
Couldn't get to the flash mode even to use odin, went back today and bestbuy swapped it out for me thinking I just got a bad phone, I could also shake the thing and hear raddling with the usb door shut to so im not really surprised. The new one seems to be working better already, eill try root tonight,
Jwahlg said:
I could also shake the thing and hear raddling with the usb door shut
Click to expand...
Click to collapse
Volume toggle. I bet the new one does it.
good day.
chopper the dog said:
Volume toggle. I bet the new one does it.
good day.
Click to expand...
Click to collapse
He's right, the volume rockers rattle like a sumbitch.
Sent from my SCH-I500 using XDA App
My Fascinate is just twp weeks old and One Click and CWM worked just fine for me. BTW I am running JTs super clean rom. Lovin this phone!
Sent from my SCH-I500 using XDA App
This is why manufacturing companies are locking down phones now. That phone wasn't bricked it could have easily been fixed. OP. Please read and try to learn what u r doing. As well try to have a semi understanding of how u can fix ur phone if u mess it up. I would bet that your phone could have been up and running in 15 minutes.
Sent from my SCH-I500 using XDA App
ksizzle9 said:
This is why manufacturing companies are locking down phones now. That phone wasn't bricked it could have easily been fixed. OP. Please read and try to learn what u r doing. As well try to have a semi understanding of how u can fix ur phone if u mess it up. I would bet that your phone could have been up and running in 15 minutes.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
x10
This is counter development long term.
I further submit that in the future, all root processes require a ten question exam on the users knowledge to work.
Sent from my SCH-I500 using XDA App
Mine crashes sometimes. Even with all original OS. I just pull the battery and all is good.
My volume rocker doesn't rattle, so there is that plus.
Sent from my SCH-I500 using XDA 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
I've had my HTC 10 about a month. I was running NuSense Marshmallow by Santod040 and I had run the "NoRedText_aboot_firmware zip" to get rid ot the red text. Still, things were running well.
I then updated to the Nougat version of NuSense and the firmware and again things were running well. But the red text was back so I decided to get rid of the red text again. That is where things went wrong.
I didn't realize that there was a "new version" of the "NoRedText_aboot_firmware zip" and I tried to flash the same one.
I got an error message about it being the version prior to the update then the phone shut down. Now it wont power up.
Am I totally screwed? Is there a way to fix this? HELP... :crying:
Are you S-Off? Does your computer see it?
@dottat
acbrocksit said:
I've had my HTC 10 about a month. I was running NuSense Marshmallow by Santod040 and I had run the "NoRedText_aboot_firmware zip" to get rid ot the red text. Still, things were running well.
I then updated to the Nougat version of NuSense and the firmware and again things were running well. But the red text was back so I decided to get rid of the red text again. That is where things went wrong.
I didn't realize that there was a "new version" of the "NoRedText_aboot_firmware zip" and I tried to flash the same one.
I got an error message about it being the version prior to the update then the phone shut down. Now it wont power up.
Am I totally screwed? Is there a way to fix this? HELP... :crying:
Click to expand...
Click to collapse
Try charging with oem stock charger and cable overnight.
If it starts to take a charge, prepare a blank SDcard with
2PS6IMG_PERFUME_WL_M60_SENSE80GP_VZW_VERIZON_WWE_1.85.605.8_Radio_1.0.C010141xxxx.zip or similar. Rename it 2PS6IMG.zip with only one .zip at end. Try and boot with volume down and power.
With any luck, you'll get enough charge on it to allow you to do this software install.
Hard Brick
I did ask Santod and he said it is hard bricked. I flashed the wrong aboot image and now the phone does nothing, no power, no response from any combination of button presses, the computer does not see it. I don't know of anything else that might work.
I'm going to try to see if HTC can fix it, if not then I may use it for parts because the phone looks great. So I may try to get a beat up phone with a busted screen and swap out the guts.
Pretty sure this is what I've been talking about folks.
Stop messing with custom aboots.
Sent from my HTC6545LVW using Tapatalk
Bricked / aboot
dottat said:
Pretty sure this is what I've been talking about folks.
Stop messing with custom aboots.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Yeah, I read your info and warning about it after the fact.
acbrocksit said:
Yeah, I read your info and warning about it after the fact.
Click to expand...
Click to collapse
Yep...Moreso posting for anyone who sees this as further warning.
Sent from my HTC6545LVW using Tapatalk
I did the same thing trying to downgrade my firmware. Same exact thing happened. So I got it replaced by Verizon with the warranty, and they accepted it, I just said that I was trying to update it and that it won't turn on now. They haven't noticed that I did it, and I doubt they'll be able to get it to boot without flashing complete stock.
Spinkness said:
I did the same thing trying to downgrade my firmware. Same exact thing happened. So I got it replaced by Verizon with the warranty, and they accepted it, I just said that I was trying to update it and that it won't turn on now. They haven't noticed that I did it, and I doubt they'll be able to get it to boot without flashing complete stock.
Click to expand...
Click to collapse
So Verizon accepted your bricked phone? No issues?
Sent from my HTC6525LVW using Tapatalk
I sent mine to HTC to see what they would charge me (repair center in USA). I didn't say what happened, just that it wouldn't turn on. I don't think that they looked very close at it. They just sent me a refurbished phone, no charge.
But I won't mess with the red text again. It's really not worth the risk.
acbrocksit said:
I sent mine to HTC to see what they would charge me (repair center in USA). I didn't say what happened, just that it wouldn't turn on. I don't think that they looked very close at it. They just sent me a refurbished phone, no charge.
But I won't mess with the red text again. It's really not worth the risk.
Click to expand...
Click to collapse
They didn't even ask why Verizon wouldn't warranty it?
Sent from my m8wl using Tapatalk
Evocm7 said:
So Verizon accepted your bricked phone? No issues?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Sorry about the delayed response!!!
Yes they accepted it with no issues. Been a few months now and still nothing bad from them. The people at Verizon don't even have the knowledge to revive a hard bricked phone. At least not the people I've ever been able to speak to. But either way, it's not worth the hassle for them. They'll just part it, toss it, or send it back to HTC, where they will either part it or toss it. So yeah, no worries about sending Verizon a rooted/s-offed/bootloader unlocked phone. I've done it more times than I can count, and they've never found out.
Spinkness said:
Sorry about the delayed response!!!
Yes they accepted it with no issues. Been a few months now and still nothing bad from them. The people at Verizon don't even have the knowledge to revive a hard bricked phone. At least not the people I've ever been able to speak to. But either way, it's not worth the hassle for them. They'll just part it, toss it, or send it back to HTC, where they will either part it or toss it. So yeah, no worries about sending Verizon a rooted/s-offed/bootloader unlocked phone. I've done it more times than I can count, and they've never found out.
Click to expand...
Click to collapse
No problem. I called Verizon and even though it was dead, they were still able to communicate with the phone while I was talking to them on another phone. The power led was flashing red and then she said the phone wasn't under warranty because there was custom software. I ended up sending it to HTC where they sent me a refurb with a bad mic then the second one I have now is fine. So after a month and $40 worth of shipping charges, I have a working 10 again. I honestly don't think HTC cares about rooted phones and the time it would take to diagnose what actually happened in our down grade brick wouldn't be worth it for them.
Sent from my HTC6545LVW using Tapatalk
If it's under warranty, make a claim. Verizon will tell you to ship it back to another location where all they do is refurbish the phones for subsequent resale. You will likely get a replacement refurb. The refurbisher has absolutely no clue what you have done; they handle these things in bulk and I have not once ever heard of a phone under warranty being "refused" because an end user did something stupid. Which, as @dottat says, is what flashing an edited aboot to get rid of the red text is, by the way. Stupid.
I *like* the red-text, frankly. It reminds me whether I'm running pure stock boot and recovery or not while I'm flashing updates, etc.
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
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.