My girlfriend's Legend had a notification for an OTA today, and after it installed, wifi doesn't seem to work, giving the message "Wifi is unable to start". A factory reset did nothing to help.
My gf's Legend had the same problem after a OTA update, tried everything except rooting it. Finally i took it back to the dealer which had it replaced immediately since it was only 2 days old.
try to factory restore several times. Once I had to do 7 factory restore just to get the ringtone working.
I had the wifi-problem, too.
Fixed it by running the RUU again (maybe you need a goldcard for that)
Related
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Have you tried the 2.2.1 leak? This gives you a new kernel and bootloader.
Stoogie said:
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Click to expand...
Click to collapse
If the phone is not rooted when you take it into the Verizon store then you will be fine. I would ensure that any traces of root have been removed from the SD card (apps that require root, etc). As long as the phone is stock when they see it then it will be fine. I have had to do this several times with roms and root access.
Can't you just SBF it? I'm fairly new to the X but I've had to SBF rescue my D1 and D2 multiple times.
OOOPS didn't read the SBF part...
If it is still hosed after an SBF install I would guess that you have a hardware issue and need to replace the phone.
Stoogie said:
I'm having a problem with my Droid X using the 2.2 Froyo update. My phone was rooted using 2.1 when I updated to 2.2 and I started getting this problem. If my phone turns off then when it tries to turn back on it will get "stuck" at the Motorola logo screen. I say "stuck" because I discovered I can still use my phone, I can unlock it, open things, turn it off, it works except it only shows the boot up screen. I can get around this by leaving my battery out for several minutes, then it will boot up fine. I've already tried several things to fix my phone but nothing has worked. What I've tried so far:
Unrooting my phone
Rerooting my phone
flashing a "stock" 2.2 SBF
reset to factory defaults
I'm out of ideas except for trying to get my phone replaced by Verizon. So my question is what's left for me to try? Otherwise, will I be able to return my phone to verizon despite it being rooted at one point? Thanks in advance if anyone can help me out here.
EDIT: I noticed my phone didn't have this problem if my SD card was removed, so I tried reformatting it but that hasn't solved anything either...
Click to expand...
Click to collapse
It's a known issue with 2.3.15. gmanapps, the guy that created the hdmi app in the market said it was the video driver not loading up in time because of some code changes Motorola made; but supposedly it's fixed in 2.2.1. I suggest you don't upgrade to 2.2.1 until there is a full sbf.
I get stuck on the "M" logo 7 times out of 10 after every reboot; I just hold the power button down until the pop-up window comes up (of course I can't see it) and guess where the shutdown press is on the screen to power off the phone, and then power on again after a minute or two. This trick usually works.
Check it out here:
https://supportforums.motorola.com/message/256095#256095
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
zero313 said:
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
Click to expand...
Click to collapse
at least you are getting something OTA
Ditto
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
seanfrisbey said:
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
Click to expand...
Click to collapse
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Same thing here
When I bought this device 3 weeks ago, I rooted it with z4root. Not too long after an update disabled z4root on the tablet.
I thought no big deal, but then today comes and I the OTA update won't work.
Anyone more experienced than me have any ideas of how to get this update applied properly?
Me too. Update failed to install. Not sure why. I have also tried unrooting.
FloatingFatMan said:
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Click to expand...
Click to collapse
I'm confused, if I froze an application, didn't unfreeze it but did a factory reset...wouldn't that resolve the issue?
ok so i woke up this morning and my a500 notified me the there was an update available so as you can imagine I was very happy to finally have this, so i updated and when it was done it said update successuful but when I checked it still said 3.01......WTF
Not rooted ever..
Those interested in getting back their OTA, properly backing up their original ROMS or restoring them, please follow the tutorials in this thread:
Going back to stock TUTORIAL
Be helpful and provide your firmware if you have a backup so we can build a database for those who don't.
Be sure to report what is working and what is not working for you once you've tried the tutorials!
Unlike the 14 threads on these matter I take the responsibility as OP to upgrade my original post as firmwares and new info becomes available.
Let's create a focused troubleshooting and tutorial thread,
Thanks.
I'm rooted via gingerbreak and the update worked fine while still rooted. It did break root. Just had to re-apply gingerbreak and all is good, back to root with latest update.
gingerbreak worked with official 3.1 ?
it didn't work with 'leaked' 3.1 ?
OTA
Ok after long night and hours of research i found out a lot.
1 if you have modded ad hoc in wpa_supplicant file recover the original file
2 if you have modded the phone.apk and telephoneyprovider.apk to save battery this is the reason why you won't get the update.
i put these files back and instantly got an update, i mean the exact second i set those back
i can't believe this my updates keep failing to install. FING POS i tried everything, factory reset
i have tried everything, even factory reset, it fails while installing after reboot
acer support are a bunch of retards, they don't even know they sell tablets????????
need help i can't upgrade, it fails every time
does anyone know where the install logs are
the log is \cache\recovery\last-log
Oklahoma City, OK noon CST
First attempt failed:
Changed the wpa_supplicant back to original and all went smooth the second time
I never changed anything and it failed.
**Edit: I rebooted my devices and left it completely alone after unzip and it rebooted into recovery mode and seems to be installing **
I had the same problem, It was pretty disheartening.... but I unrooted my device, re-booted and tried again and SUCCESS!!!
But now I can't get it to re-root using gingerbreak... HELP!
SUCCESS!
Ok. I got OTA update 4.010.08 (122.71 MB) this morning. It failed.
So I unrooted my device. Re-started it and tried again... SUCCESS!
I tried using Gingerbreak to root it again. FAIL!
So I used this: http://forum.xda-developers.com/showthread.php?t=1138228
SUCCESS!
Hope this helps those of you who are having problems.
No need to unroot nor go to stock.
I had the same issues. Then I simply used Acer Recovery to install stock recovery and everything worked fine.
Ceger
Acer Recovery?
Did Acer Recovery come with the tablet?
I tried the update numerous times over the last 4 days. Most of the time the download would fail, which I put down to my slow internet connection and overloaded Acer servers. But about 5 times it would finish downloading and then error out on install with a message about the update being invalid. I tried rebooting several times during this process. I have never rooted the tablet and only have a few apps installed as it was a recent purchase.
Finally it worked when I ejected the external SD card and rebooted. It may be a coincidence, but anyone else who gets the "invalid update" warning during install on an unrooted device may wish to try this prior to the download/install.
Hi all,
I'm hoping someone may be able to help me. Here's the situation:
A few weeks ago, I updated and rooted my SGS4 to 4.4.2 using Odin. Worked alright, but kept getting random restarts. Did a factory reset, and all was good.
A few days ago, PlayStore had an update for SuperSU, so I applied it. The random restarts returned, so I considered doing a factory reset, but found that Titanium Backup wasn't allowing me to do any new backups because I had insufficient space. I didn't really - I had plenty of space. A little googling lead me to here: http://forum.xda-developers.com/showthread.php?t=2675778
I followed the instructions, rebooted my phone, and was bombarded with [app] has stopped working right away. Thinking this was no good, and I had somehow messed something important up, I did a factory reset anyway with the hopes of just restoring back to my backups from a few weeks ago.
Things got even worse - I'm now stuck on the Samsung welcome screen, where it wants me to put in my wifi password, but Myscript Resource Manager keeps failing, making the keyboard disappear. I now have no way to get back into my phone.
The TL;DR version:
I factory reset my phone, but can't get past the 'Enter Wifi Password' part of setting it up becuase Myscript Resource Manager keeps failiing.
Things I've tried:
* Wiping Cache data
* Factory Resets (again)
* Reflashing my phone with the 4.4.2 update that worked for me a few weeks ago
Does anyone have any other ideas?
The only way was to reflash from Odin, fresh firmware. Download different version of your firmware, other than the one you stated. And reflash back with Odin, make sure your steps using Odin is correct.
Thanks for the reply. I finally got it working after my third time flashing it and formatting the cache a few times. Scary stuff!
Alas, the sporadic reboot still continues, so I'll have to work out how to fix that problem again now.
Thanks again.
Simpler fix from at&t device support center
c0dewana said:
Hi all,
I'm hoping someone may be able to help me. Here's the situation:
A few weeks ago, I updated and rooted my SGS4 to 4.4.2 using Odin. Worked alright, but kept getting random restarts. Did a factory reset, and all was good.
A few days ago, PlayStore had an update for SuperSU, so I applied it. The random restarts returned, so I considered doing a factory reset, but found that Titanium Backup wasn't allowing me to do any new backups because I had insufficient space. I didn't really - I had plenty of space. A little googling lead me to here: http://forum.xda-developers.com/showthread.php?t=2675778
I followed the instructions, rebooted my phone, and was bombarded with [app] has stopped working right away. Thinking this was no good, and I had somehow messed something important up, I did a factory reset anyway with the hopes of just restoring back to my backups from a few weeks ago.
Things got even worse - I'm now stuck on the Samsung welcome screen, where it wants me to put in my wifi password, but Myscript Resource Manager keeps failing, making the keyboard disappear. I now have no way to get back into my phone.
The TL;DR version:
I factory reset my phone, but can't get past the 'Enter Wifi Password' part of setting it up becuase Myscript Resource Manager keeps failiing.
Things I've tried:
* Wiping Cache data
* Factory Resets (again)
* Reflashing my phone with the 4.4.2 update that worked for me a few weeks ago
Does anyone have any other ideas?
Click to expand...
Click to collapse
I just had the same problem, spontaneously, from an unidentified source. Went to my carrier's, AT&T, local Device Support Center on a Sunday at noon, and one of the techs fixed the problem in under 3 minutes, impressively simply.
You will have to keep clicking OK when the error message repeatedly appears to continue with this process. That is normal.
Go to Settings > Application Manager > (scroll right to: ) ALL > (scroll down to: ) My Script Resource Manager (which should not be running) > Turn Off
Problem solved without Factory Reset. She impressed me and saved me a lot of time.
Hey guys,
My wifes Tab 4 recently did the OTA update to Lollipop (5.0.1) and has been having a problem ever since. After being in use for a few minutes after the update it suddenly locked up and rebooted itself. Thought nothing of it at first, but then it did it again, and now randomly reboots all the time, sometimes after only a minute of use. I've tried clearing the cache partition and factory reset, neither gave any improvement. Then i figured maybe the OTA download was the probblem so i flashed it back to Kitkat using Odin and all worked fine again for a few days. I turned off the OTA update checke and she was perfectly happy with it again.......
......until it downloaded the update all over again.
Before allowing it to update again i connected it to the PC and did the update via Kies instead. All seemed to be fine for about 5 minutes and then started rebooting. Again, cleared cache and factory reset. Again no improvement.
Then tried flashing the update via Odin again. Still no improvement.
I'm drawing a blank on this one. I've tried everything I can think of and still not been able to solve this one. The only thing i've been able to figure out so far is that for whatever reason it doesn'T randomly reboot if its connected to the PC via USB...............
Anyone got any ideas how to sort this?? Samsung have offered to take it in for repair and I'Ve been offered a refund from the retailer, but I'd rather avoid those options if possible.
Thanks!
I have the same problem and nobody Knows. I will back to kitkat. let me know if you fixed. sorry for my english im cuban.
I just got an OTA update and from VNS-L21C432B160 to B370 which was around 1.94GB but I wanted to make a clean install so I removed superSu from the app did a factory reset first then went back to update where it now showed something around 1.24GB. So I went through with the update everything seemed fine until I couldn't find the Dual-Sim manager. I went to About Phone section and noticed that my build number was NRD90M test-keys. How can I get a clean C432B370 from this point on?
Same thing hapened to me.
After update, strange build, but no BT functionality and no file explorer. Contacted Support, told to do Factory reset. Now gets interesting.
Factory reset failed after 6%, now im stuck with device with no keyboard?!? Basicaly, i can just recieve call's.
And to top it up, PC dont see device, cant upload anything on SD card to try 3 button update etc.
Before I have downgraded from N to MM because of camera problem, to do so, I had flashed Dual Sim OEM per instructions, I can think that that is causing some problems.
Targyen said:
Same thing hapened to me.
After update, strange build, but no BT functionality and no file explorer. Contacted Support, told to do Factory reset. Now gets interesting.
Factory reset failed after 6%, now im stuck with device with no keyboard?!? Basicaly, i can just recieve call's.
And to top it up, PC dont see device, cant upload anything on SD card to try 3 button update etc.
Before I have downgraded from N to MM because of camera problem, to do so, I had flashed Dual Sim OEM per instructions, I can think that that is causing some problems.
Click to expand...
Click to collapse
Same thing happens to me with factory reset, fails at 6% boots back like it performed a factory reset. I'm greeted with the first time welcome screen. No keyboard no file explorer no updater. I managed to dictate apkmirror on chrome and downloaded gboard and esfile manager. And I lost my SD card to perform a 3 button method. Can I do the 3 button without an sdcard? Maybe using the internal storage?
EDIT: Well I did the 3 button method and failed at verification. Anyone can help me how do I get out of this?
EDIT 2: Back to MM with this tut https://forum.xda-developers.com/huawei-p9lite/how-to/tutorial-rollback-n-to-mm-c432-devices-t3563955 and downloading B370 thorugh the official updater again
EDIT 3: Everything went smoothly and after, I even got B380 OTA.
EDIT 3.5: Did a factory reset after B380 and everything is working.