lost lte after OTA update - Motorola Droid RAZR

So after my wife complaining how annoyed she is with the OTA request popping up every 12 hours, i decided to get her phone to accept. She was on a 4.0 version of AOKP, so i safeboot restored her stock rom and uninstalled safeboot.
the update went well but now she has no 4g and cannot send any emails. Is there a fix for this? I found one thread where people said there is no fix as somehow the hardware got corrupted (apparent happened to a lot of people). Some people were lucky and were still under warranty and others just bought a new phone or got one from ebay. Well shes just over a year so the warranty is out of the question, and we cant really afford a new phone at the moment.
This is kinda bull**** as she had an LG ally before this that broke with an OTA and verizon refused to do anything about it.
Hopefully there is some workaround.

vaeevictiss said:
So after my wife complaining how annoyed she is with the OTA request popping up every 12 hours, i decided to get her phone to accept. She was on a 4.0 version of AOKP, so i safeboot restored her stock rom and uninstalled safeboot.
the update went well but now she has no 4g and cannot send any emails. Is there a fix for this? I found one thread where people said there is no fix as somehow the hardware got corrupted (apparent happened to a lot of people). Some people were lucky and were still under warranty and others just bought a new phone or got one from ebay. Well shes just over a year so the warranty is out of the question, and we cant really afford a new phone at the moment.
This is kinda bull**** as she had an LG ally before this that broke with an OTA and verizon refused to do anything about it.
Hopefully there is some workaround.
Click to expand...
Click to collapse
my friend can you try doing rsd lite with fastboot files again like a clean install of the jb update using fastboot files and see if that helps or not. sometimes the ota is corrupted but the fastboot install fixes them. try and let me know thanks

Related

Leak was worst mistake ever!

I know its been hashed a thousand times, and this thread can be deleted if its too redundant. I regret thoroughly getting the 2.1 leak on my wife's phone. I love my rooted eris and ELB rom has made it absolutely functional and keeps getting better with constant updates and feedback, while my wife's eris is stagnant and hopeless. Constant dropped calls, and sound outages, and I cannot get a replacement because Verizon's system doesn't show it on 2.1 so until it is (which cant be done because we cant get the OTA when you have the leak) they wont even consider sending a refurb. To make matters worse, even if I could get a refurb, they are coming shipped with 2.1 that cant be rooted. At least if I got a refurb and the problems continued we would be able to complain enough to get a discounted upgrade maybe. I don't think anyone is working on this issue anymore as the phone has been left behind in the dust without root, and I don't blame them. I would too if I was a dev. I will NEVER NEVER install another leaked ROM. I will always be patient enough to wait for root. Yeah Frisco you were right, and all the others that waited patiently. Sigh OK done venting. Now to go "accidentally" drive over my wife's phone and pay the damn insurance.
I too regret installing the leak, however I have had none of the problems you have described. My phone may be a bit sluggish at times, but I've never had a dropped call since I've gotten the phone, or any other problems for that matter. Sorry to hear your having ask these problems though.
-------------------------------------
Sent from my HTC Droid Eris using Swype. Gone Google!
I didn't have any problems whatsoever with getting a refurb while I was on leak. I called them up and mentioned having a couple of the common problems(I actually did have issues), told the guy that I had done the factory reset and it hadn't helped and the new phone was on the way. Sorry to hear that's not how it happened to work for you. Did they specifically say they could tell she wasn't on the OTA? I'm surprised they were able to tell with the similarities between the two versions. Maybe you can try and install the OTA manually on hers and A) see if it helps in general, or B) see if Verizon can tell she has the regular version then.
http://forum.xda-developers.com/showthread.php?t=695593
As far as I know, you cannot upgrade to the ota if you are running one of the leaked roms because of the hboot version.
-------------------------------------
Sent from my HTC Droid Eris using Swype. Gone Google!
orkillakilla said:
As far as I know, you cannot upgrade to the ota if you are running one of the leaked roms because of the hboot version.
-------------------------------------
Sent from my HTC Droid Eris using Swype. Gone Google!
Click to expand...
Click to collapse
Acutally you can go OTA from one of the leaks, just not root from a leak. Now going OTA does not change the hboot version of the leaks, so even with the OTA you cannot leak. But if for some reason you want the OTA instead of a leak ( and with V3 leak they are the same anyway) follow this link http://forum.xda-developers.com/showthread.php?t=695593 make sure to read it all, but from what I have read and understand that is the offical OTA release that can be manually installed on the phone, so if it ever needs to go back to verizon they cannot hit you for having unoffical software on the phone
Ah, this I did not know, but very useful. Thanks for posting the link.
-------------------------------------
Sent from my HTC Droid Eris using Swype. Gone Google!
If you want root that bad, you can do like I did. I had Leakv1 on my phone and just went ahead and loaded the new RUU OTA update onto it. Found someone on Craigslist that was willing to sell an eris that had the OTA on it for like $150 and ship it to me. Rooted it, then put my old phone on ebay for auction. It sold for like $170 with free shipping. Everyone came out happy and I got a rooted phone and like $10 in my pocket.
Be careful when buying phones on craigslist/ebay/etc. and look out for those Bad ESNs.
Anyway, just another option for ya...

Should I unroot?

Should I unroot my Eris...sending it back to Verizon on Monday. Do they check for that, considering the number of people receiving replacements, has anyone ever had a problem with that?
mswilson2007 said:
Should I unroot my Eris...sending it back to Verizon on Monday. Do they check for that, considering the number of people receiving replacements, has anyone ever had a problem with that?
Click to expand...
Click to collapse
Most people attempt to. There have been reports from people in the past that went both ways - some reporting getting charged, and some reporting having returned a rooted phone with no problems.
Hopefully if someone got popped for it recently, they will speak up - a lot of times people are reluctant to talk about negative experiences.
In any event, there is a newly released ROM that makes unrooting the same level of effort as installing any other ROM - give it a shot and report back your results.
bftb0
I sent my rooted Eris to Verizon a few weeks ago because my old one had the trackball issue, Verizon didn't say anything about it. I think it might depend on what type of problem your phone has. My guess would be that there's more of a chance for them to say something about it if you have a software issue rather than a hardware issue, just a thought.
I've sent two back so far, one rooted and one un-rooted. I sent the rooted one back a couple of months ago and never heard anything about it. I would have to agree that it would depend on if it was a hardware or software issue.

WARNING T-Mobile NOT helpful! BEWARE OF UPDATE!

To get to the point, people DON'T UPDATE YOUR VIBRANTS and T-MOBILE HANDLES THE ISSUE HORRIBLY! Obviously this is not a universal problem, but if you do happen to be one of the lucky ones that bricks their phone with the update there is no saving it (at least with the help of T-mobile).
I just got off of the phone with tech support and they were less than helpful. After the regular punching in numbers, talking to two different people, and trying to re-boots that everyone with half a brain have tried, they informed me that they would replace the phone but I had to PAY for shipping. While I realize this is a normal policy when it comes to random malfunctions, which may or may not have been the users fault, this is absolutely ridiculous when the problem is 100% their fault. Seriously, T-mobile ships a top of the line phone that has some major flaws and inactivated software (media hub), then breaks the phone with it's official update, and somehow this is MY responsibility to pay to get fixed? The rep even asked if I at this point wanted to add insurance so next time I wouldn't have to pay for shipping and if I wanted to pay extra for expedited shipping! They were trying to make an add-on sale while fixing an issue THEY caused!
That's not even the end of it, because I was so irritated they sent me to a "loyalty specialist" (who sounded like a used car salesman). He rambled on about how he would waive the shipping fee (he made it sound like he just saved my first born child). I told him I appreciated that but it didn't fix the fact that T-Mobile was not handling the issue well. When a large number of phones break from an issue originating from the provider they should either 1) have re-furbished phones (or even set aside new phones if necessary) to replace these broken phones as they come up or 2) offer free over night shipping of the replacement phone. He told me that these options were too expensive for T-Mobile, and that if I like I could sign up for either of their two insurance plans, as they would allow me to do an in-store replacement (he later noted that one of them was only available within the first 14 days of owning the phone...). I couldn't believe they were trying to another add-on sale! The best part being, I later called around to all my local T-Mobile owned stores and none of them have the Vibrant available for in-store replacement (and never have).
So the Cliff-Notes of my rant:
1) DON'T UPDATE YOUR VIBRANT
2) If you did brick your phone, make sure to complain and they should refund the ridiculous shipping charge
3) If you don't own a Vibrant and are thinking about it consider the following (Don't let it stop you, just consider it):
- Still on 2.1, when Nexus One has been on 2.2 for months (and the Galaxy S 2.2 official ROM has been leaked so it does exist in some form.) => Meaning updates are super scarce and extremely late.
- T-Mobile is selling a good phone with many flaws, and their first attempt to fix it bricked many phones (do a google search I am not the only one).
- While it may be better than other companies, T-Mobiles customer service is FAR from flawless
P.S. My phone was completely stock (so please don't mention how I did this with a lag fix, etc.). I waited at least 15 mins before I pulled the battery, before which I had noted the T-Mobile sound starting without the animation (seems like a timing issue or something). And finally, I realize this is a duplicate post to many others but I want people to find this info (not be at the bottom of a really long thread) to get the word out how T-Mobile deals with their errors.
I hate when people mess with their phones then get angry at a company for "breaking" their phone. Im running stock rom with root and also got bricked, but, I manned up and knew I was in the wrong and accepted what happened. I didn't put the blame on TMo, because completely untouched vibrants that I was aware of had no issues with this OTA. If you added functionality to it after the fact that it wasn't originally on there before when you initially purchased it; then its YOUR fault that it bricked, NOT T-mobiles. Take some responsibility and stop crying.
Had the same problem but this is a pretty fix using Odin.
If you install an update from an OTA T-Mobile should be held responsible
I don't know about you guys but when you have been a customer for 10+ years, T-Mobile will pretty much suck your balls.
Either way, if you guys rooted it, then that takes the fault from T-Mobile to you. You changed the phone. The update was designed for a pristine un-edited Samsung Vibrant, if you changed anything in the system by rooting or flashing it is your fault for changing the equation. T-Mobile is NOT at fault for your actions.
Yeah why warranty the phone when you can just ODIN and fix it yourself? Do a xda search. If you're gonna use xda to complain at least use it to solve your own problems as well. Unless your phone is hardware locked it is 100 % fixable.
Sent from my SGH-T959 using XDA App
starkiller86 said:
I hate when people mess with their phones then get angry at a company for "breaking" their phone. Im running stock rom with root and also got bricked, but, I manned up and knew I was in the wrong and accepted what happened. I didn't put the blame on TMo, because completely untouched vibrants that I was aware of had no issues with this OTA. If you added functionality to it after the fact that it wasn't originally on there before when you initially purchased it; then its YOUR fault that it bricked, NOT T-mobiles. Take some responsibility and stop crying.
Click to expand...
Click to collapse
P.S. My phone was completely stock (so please don't mention how I did this with a lag fix, etc.). I waited at least 15 mins before I pulled the battery, before which I had noted the T-Mobile sound starting without the animation (seems like a timing issue or something). And finally, I realize this is a duplicate post to many others but I want people to find this info (not be at the bottom of a really long thread) to get the word out how T-Mobile deals with their errors
Did you not read that part?
I bricked two stock Vibrants with the update. The second one failed during Mini-Kies update and was hardware locked.
It is a known issue according to the Tech guy that I spoke to while getting my replacement.
First phone wouldn't power on after failure, second phone was hardware locked so un-fixable.
No, no.
This happened to me, I had a rooted phone I had uninstalled the inflight internet, etc on it and hadn't overclocked or anything like that. Phone kills itself. I went to the tmo store and they only make you pay for shipping if you take the overnight option.
PROTIP - DON'T ASK FOR EXTRA SPEEDY SHIPPING AND THEY'LL PAY FOR IT.
so i guess we are just SOL for the data on the phone? I just lost an entire vacation of pictures. I had not had a chance to root this phone either. this is ****ing awesome.
dechire said:
so i guess we are just SOL for the data on the phone? I just lost an entire vacation of pictures. I had not had a chance to root this phone either. this is ****ing awesome.
Click to expand...
Click to collapse
I guess this is just an example of "store your pictures on the external SD card"
Then if you brick it you can still get your pictures back ....
watcher64 said:
I guess this is just an example of "store your pictures on the external SD card"
Then if you brick it you can still get your pictures back ....
Click to expand...
Click to collapse
Word. That's one of the first things I did when I got the phone and was playing with the features. Switched it from phone storage to memory card.
Sorry to hear you lost photos.
Protip: Pay the damn overnight shipping fee...it'll be deducted from your bill (flex pay) which makes it free: )
Sent from my SGH-T959 using XDA App
Here is the business side
If I am T mobile every time some person has a problem and I offered free shipping, the Every moron would be shipping the device back for Any problem. Way way costly, so that is not going to happen. If you Really believe the phone is factory defective then, pay the shipping and move on. If you messed with it at all then the burden to resolve is yours and be honest about that. Remember the reason people are in here is to customize the phone and improve it. Like the XDA mantra sez.......... It is not just the result... but the journey....
Like one of the other posts stated:
If you rooted it, then that takes the fault from T-Mobile to you. You changed the phone. The update was designed for a pristine un-edited Samsung Vibrant, if you changed anything in the system by rooting or flashing it is your fault for changing the equation. T-Mobile is NOT at fault for your actions.
Gr8gorilla said:
First phone wouldn't power on after failure, second phone was hardware locked so un-fixable.
Click to expand...
Click to collapse
There is a hardware lock fix now, you really should flash that before you do anything else. Yeah, you run the risk of bricking with the hardware unlock, but it's probably a safer bet than flashing away.
dechire said:
so i guess we are just SOL for the data on the phone? I just lost an entire vacation of pictures. I had not had a chance to root this phone either. this is ****ing awesome.
Click to expand...
Click to collapse
If you Odin it with the JI6 update, you might still be able to get a working system out of it. Worth a shot to see if you can get it without having to flash to stock first (which will wipe).
With all the time you spent with tech support, you could have found the thread that delineates how to fix your phone and update through odin. Its very easy and, frankly why be on a developers forum when you are not willing to tinker around a bit.
Sent from my SGH-T959 using XDA App
dechire said:
so i guess we are just SOL for the data on the phone? I just lost an entire vacation of pictures. I had not had a chance to root this phone either. this is ****ing awesome.
Click to expand...
Click to collapse
As long as the phone still powers on you can still use ADB Pull and save the data from the /sdcard folder. This update isn't a totally bricking the phone (at least it didn't mine) just making the display and inputs not work. To quote Billy Crystal: "He's only MOSTLY dead"
Odin was really simple to reflash the stock ROM and then I was able to do a nandroid restore from there.
The T-Mobile OTA update left my phone only booting to the vibrant screen, but it was a pretty simple fix with Odin. The hardest part was getting the proper drivers installed in windows!
Mini kies wouldnt even let me update,so I rooted and flashed bionix 1.8,works great.**** tmo.
Fyi to the people with hardware lock. I did the update on my gf's phone which was hardware locked and it failed. The phone would only boot to the vibrant screen. The good news is the ota update unlocks the hardware because her phone is able to get into recovery and download mode even thought the update failed. The point is don't worry if ota fail on you because you can just use odin to fix it since it unlocks the download mode.
Sent from my SGH-T959 using XDA App
mr2t32 said:
Fyi to the people with hardware lock. I did the update on my gf's phone which was hardware locked and it failed. The phone would only boot to the vibrant screen. The good news is the ota update unlocks the hardware because her phone is able to get into recovery and download mode even thought the update failed. The point is don't worry if ota fail on you because you can just use odin to fix it since it unlocks the download mode.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
If the update even gets that far...

Samsung has my softbricked rooted I527 Mega

Well everybody my Mega is there at Samsung in Plano, TX hopefully getting reflashed or repaired or whatever the hell they're gonna do to it. Hopefully it's FUBAR and they can't tell it's been rooted lol.
Sub'd. I need to know how this goes, because I am getting sick of not having my phone work. I don't trust them, but my distrust is being outweighed by my massive lack of patience.
cbass said:
Sub'd. I need to know how this goes, because I am getting sick of not having my phone work. I don't trust them, but my distrust is being outweighed by my massive lack of patience.
Click to expand...
Click to collapse
The lack of patience is why I didn't wait more than a day before sending it lol. I'll keep ya posted for sure. If it works, i'll tell you exactly what I did to mess it up as bad as I did.
I think you'll be fine. Like three years ago when I was a android rookie I had brick my vibrant and couldn't figure out how to fix it. It was rooted and bricked and I couldn't fix it so I said **** it and I sent it to samsung on the hopes they wouldn't discover my unlawfulness. Well two weeks after I got it back fresh in a new box. Perfectly fixed.
Also one time I had an iPhone 3gs that was jailbroken but the screen was broken and wouldn't recognize any touching on it. So I just handed it to the guy and he couldn't slide to unlock it to check it out so they gave me a refurbished one without even checking if I had messed with it. Got lucky on both days I guess haha :good:
Samsung warranty
I sent mine out monday morning,got there today.Its already fixed and being sent out today,should be back by monday.I soft bricked mine trying to achieve root and it wouldn't boot passed the samsung galaxy mega statup.They fixed with just a stock firmware update,which I could of done myself if I had the stock odin firmware tar file,o well at least it ffixed and ill have it back within 7 days,not bad thought it would take at least two weeks
gubbilo144 said:
I sent mine out monday morning,got there today.Its already fixed and being sent out today,should be back by monday.I soft bricked mine trying to achieve root and it wouldn't boot passed the samsung galaxy mega statup.They fixed with just a stock firmware update,which I could of done myself if I had the stock odin firmware tar file,o well at least it ffixed and ill have it back within 7 days,not bad thought it would take at least two weeks
Click to expand...
Click to collapse
Oh nice! How the hell is yours fixed and all the way back to you? I even called to expedite mine lol.
PhilupBlunts said:
I think you'll be fine. Like three years ago when I was a android rookie I had brick my vibrant and couldn't figure out how to fix it. It was rooted and bricked and I couldn't fix it so I said **** it and I sent it to samsung on the hopes they wouldn't discover my unlawfulness. Well two weeks after I got it back fresh in a new box. Perfectly fixed.
Also one time I had an iPhone 3gs that was jailbroken but the screen was broken and wouldn't recognize any touching on it. So I just handed it to the guy and he couldn't slide to unlock it to check it out so they gave me a refurbished one without even checking if I had messed with it. Got lucky on both days I guess haha :good:
Click to expand...
Click to collapse
Yeah but back then I dont think samsung had the counter flash... If you send a phone witch is brick and wont go to download mode is possible they will never find out but it is obvious that if JTAG works it was not a hardware issue
Christogq said:
Oh nice! How the hell is yours fixed and all the way back to you? I even called to expedite mine lol.
Click to expand...
Click to collapse
Any updates? I'm really not stoked on how long this entire process is taking, and I'm not even the guy whose phone they have!
cbass said:
Any updates? I'm really not stoked on how long this entire process is taking, and I'm not even the guy whose phone they have!
Click to expand...
Click to collapse
Maaaaaaan I've been checking on this crap every day lol. On Friday afternoon I got a call saying that my LCD was damaged and had to be replaced. That fee was $200, but I raised hell for like 30 minutes telling them to just use my old LCD because it still worked and I just wanted my phone reflashed. Needless to say, my LCD was replaced free of charge and that I should have my phone back by Friday 11-1-13 or before. This was on Friday and I called yesterday and they couldn't tell me anything because there were no updates in the system. I checked today and still no updates in their system.
Side note: Did you see a message in Kies saying that the firmware was now available for our device? I swear I saw something to that effect the last time I got on my computer. Would that help you out at all?
ODIN flashable firmware is my last hope, i suspect it will work, but only time will tell. I keep searching, checking sammobile, but nothing yet.
I'm to the point where I am holding off on buying car mods to do this winter because I have a sinking feeling I will be buying a new phone in the near future.
cbass said:
ODIN flashable firmware is my last hope, i suspect it will work, but only time will tell. I keep searching, checking sammobile, but nothing yet.
I'm to the point where I am holding off on buying car mods to do this winter because I have a sinking feeling I will be buying a new phone in the near future.
Click to expand...
Click to collapse
Just checked on my phone and it should be shipping back to me today so I hope like hell i'll get it tomorrow. I honestly think you'll be ok. Two of the CSRs mentioned to me that they reflash the devices before they even inspect them.
Christogq said:
Side note: Did you see a message in Kies saying that the firmware was now available for our device? I swear I saw something to that effect the last time I got on my computer. Would that help you out at all?
Click to expand...
Click to collapse
There is a new firmware update, but it's not supported by AT&T due to the locked bootloader.
Send it on!!!!!!
cbass said:
ODIN flashable firmware is my last hope, i suspect it will work, but only time will tell. I keep searching, checking sammobile, but nothing yet.
I'm to the point where I am holding off on buying car mods to do this winter because I have a sinking feeling I will be buying a new phone in the near future.
Click to expand...
Click to collapse
Hey i got my phone back. It took 8 business days, but because i was refuising to pay for the lcd repair. I have my phone back. They reflashed it at no charge and all that. They told me they do that before they inspect anything. I would imagine your would be reflashed and returned fairly quickly.
Christogq said:
Hey i got my phone back. It took 8 business days, but because i was refuising to pay for the lcd repair. I have my phone back. They reflashed it at no charge and all that. They told me they do that before they inspect anything. I would imagine your would be reflashed and returned fairly quickly.
Click to expand...
Click to collapse
Nice to hear and it works likes it should again. :good:

Bootlooping after Lollipop update

Here's the background: rooted my Kyocera Brigadier last June with King Root. Installed Titanium Backup and used it to delete Verizon's bloatware from the system. I did not make backups of the programs I deleted. Phone has run great, except the last few months would not notify me when voice mail messages were left for me. In November started getting notices for updating system to Lollipop. I've been exiting out of the notice half a dozen times a day ever since. Finally, three nights ago decided to do the update. Charged battery to 100%, backed up programs and settings with Titanium backup, and tried to delete King Root. There was no option to uninstall the app in App Manager, so I disabled and re-started phone. Checked phone for root with Root Checker, found it was no longer rooted, and initiated the update. After an hour, phone would vibrate, display "Powered by Android" then the "Kyocera" splash screen, then go black, and go through the cycle all over again. I plugged the phone in to keep it charged, and let it run the cycle over night without trying to interrupt it in case the update was taking longer than expected. Next morning, same thing - vibrate, splash screens, black screen, repeat. So, I have found that I can get the phone into stock Recovery, and I have executed the "factory reset", and "clear cache" commands. Phone still does the bootloop routine. Does anyone have any suggestions on how to rescue my phone?
Same thing happened to me last night! So aggravating! I've been searching all day and found nothing for this phone. There's not much support since the bootloader is still locked down. Couldn't find a stock rom or anything otherwise we might be able to flash it through fastboot. I think we may just be screwed unless Verizon will replace it. Probably gonna try to get a replacement tomorrow. :crying:
A guy at the Verizon store fiddled with it yesterday for 1/2 an hour, mostly going into Recovery and doing the same things I already tried. They said, "sometimes these old phones aren't compatible with the new software", then offered to sell me a new phone. I asked, and they said that there is no service place to send the phone for repair, Verizon just treats these units as disposable. Break it and it's time for a new one, at your own cost, even if it's Verizon's update that broke it. I'll be checking with Verizon support to see if the guys in the store were mistaken about repairs, but I suspect they know what they are talking about. I may fiddle with the "Software Update Assistant" (I found on the Verizon website) later this evening, and see if it will work with the phone in Recovery.
Is there a way to permanently disable the OTA notification?
giltwist said:
Is there a way to permanently disable the OTA notification?
Click to expand...
Click to collapse
I'm not sure. You could check under Settings > System Updates to see if there's a disable option under there.
OlafTheOx said:
A guy at the Verizon store fiddled with it yesterday for 1/2 an hour, mostly going into Recovery and doing the same things I already tried. They said, "sometimes these old phones aren't compatible with the new software", then offered to sell me a new phone. I asked, and they said that there is no service place to send the phone for repair, Verizon just treats these units as disposable. Break it and it's time for a new one, at your own cost, even if it's Verizon's update that broke it. I'll be checking with Verizon support to see if the guys in the store were mistaken about repairs, but I suspect they know what they are talking about. I may fiddle with the "Software Update Assistant" (I found on the Verizon website) later this evening, and see if it will work with the phone in Recovery.
Click to expand...
Click to collapse
I would definitely talk to tech support, I chatted with a Verizon rep because I had to activate an older phone because of this problem and they said that would be the best option. I'm not totally confident in the knowledge of a lot of Verizon store employees. I think if this happens because of their update then it should be their responsibility to replace or repair the phone free of charge and if we complain loud and long enough then we might get somewhere. As for the "Software Update Assistant" is that a downloadable program? I checked on the Verizon website and I'm having a hard time locating it if it is. From what I read it looks like it's something that starts up when you plug the phone in but of course it would have to be working already. Also, I don't think this phone has a download mode which would allow the computer to pick it up as a USB device. I know if you boot it into the bootloader it will show up as Android Bootloader Interface so maybe we can do something from there. I couldn't get mine to show up while in recovery mode. Maybe if someone can get a copy of the Verizon firmware update we can flash the update through ADB.
OlafTheOx
I found the upgrade assistant on my computer actually so no need for the link. If you need the program, PM me and I'll send it to you somehow. Maybe you can do something with it. I messed up my recovery mode so I can't boot into it to see if it will work but it's not doing anything in the bootloader. If you happen to have a copy of your recovery.img that would be amazing. If you can fix yours and then make a copy of the recovery.img that would be much appreciated. Let me know.
Update:
After some research, I discovered DMClient is the app that handles OTA updates on our phone. Froze it in Titanium Backup (Pro needed). Boom. No more annoying OTA notifications.
giltwist said:
Update:
After some research, I discovered DMClient is the app that handles OTA updates on our phone. Froze it in Titanium Backup (Pro needed). Boom. No more annoying OTA notifications.
Click to expand...
Click to collapse
Could you possibly make a copy of your recovery image? I can't seem to find anything of any use for this phone on any forums.
leblanca7x said:
Could you possibly make a copy of your recovery image? I can't seem to find anything of any use for this phone on any forums.
Click to expand...
Click to collapse
I have a TWRP-made backup of my recovery, if that would help? I made it by fastbooting (NOT FLASHING) the TWRP build found here:
https://basketbuild.com/devs/Captain_Throwback/Kyocera_E6782/TWRP/KK
PM me and I can give you a temporary dropbox link.
I need the stock rom or some sort of file to restore my Brigadier. Please PM me with links. And what program do I use to load the rom into this phone?
Well, if anyone is interested, my phone is up and running. I wound up sending it to the Kyocera repair center in Texas. They took about 3 weeks to make the repair and ship it back to me. They installed Lollipop (along with all the Verizon bloatware). It appears that they did the repair under warranty, which surprised me, since I bought the phone used last summer. No invoice to pay. Cost me $20 to insure and ship it by UPS. The info on how to send it in is at this address https://www.kyoceramobile.com/support/repairs/united-states/faq/ Be warned, they were not very communicative about it. I got one email to acknowledge receipt of the phone, then it just showed up one day by FedEx. No paperwork in the box, just the phone. Not complaining, mind you, just try not to get too anxious while waiting if you send your phone in.
What version of Lollipop do you have now? I'm curious if it is the last... I was about to send my broken phone to repair center last year but decided to fix it myself... Now it's fully working without their help. LP without bloatware and with root. Good choice...
Sent from my E6782
Obsy said:
What version of Lollipop do you have now? I'm curious if it is the last... I was about to send my broken phone to repair center last year but decided to fix it myself... Now it's fully working without their help. LP without bloatware and with root. Good choice...
Sent from my E6782
Click to expand...
Click to collapse
Android version: 5.1.1
Software version: 2.906VZ
I've been getting prompts to update the firmware again. The prompts started 2 days after I got my phone up and running. Apparently, the repair center didn't have the latest version of Verizon's OS. The update prompts are for Software version: 2.955VZ according to Verizon's support website. Not sure if I'll try to root the phone any time soon, so I'm tempted to go ahead and do the update, hoping for the best since I haven't screwed with the system yet. I may try rooting with Kingroot again, if the unrooted experience turns out to be as aggravating as I expect it will be.
Anybody brave enough to try Flashfire to install the OTA (possibly) more safely?
Hi, i have the problem after my try to upgrade android version through assistant. My phone constantly tries to launch but cant, could you help me? what should i do? im not from usa.. maybe someone could send me a android version wich works for this phone, and it possible to install it? need your advise
OlafTheOx said:
Well, if anyone is interested, my phone is up and running. I wound up sending it to the Kyocera repair center in Texas. They took about 3 weeks to make the repair and ship it back to me. They installed Lollipop (along with all the Verizon bloatware). It appears that they did the repair under warranty, which surprised me, since I bought the phone used last summer. No invoice to pay. Cost me $20 to insure and ship it by UPS. The info on how to send it in is at this address https://www.kyoceramobile.com/support/repairs/united-states/faq/ Be warned, they were not very communicative about it. I got one email to acknowledge receipt of the phone, then it just showed up one day by FedEx. No paperwork in the box, just the phone. Not complaining, mind you, just try not to get too anxious while waiting if you send your phone in.
Click to expand...
Click to collapse
HeLLO, my friend tell me please the address and contacts of this servise center or maybe list of it. i have bootloop after trying updayting through verizon software update. And im in Ukraine now
All the information you need to send your phone in for service is at this webpage:
https://www.kyoceramobile.com/suppor...ed-states/faq/

Categories

Resources