I rooted my moto x a while ago. But went back to stock. To try and get OTA updates working, I tried flashing the factory image. Now, when I click on the wifi bar, it goes to on and then back to off in a millisecond. I have tried seemingly everything. HELP!
Related
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)
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
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
thebullfrog said:
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
Click to expand...
Click to collapse
You might try and flash the stock kernel which should not allow any under/over clocking or under/over volting. Otherwise flash back to stock using the manual way here http://forum.xda-developers.com/showthread.php?t=1907796 or download the Nexus 7 toolkit and use it to do the same.
Try WugFresh's Nexus Root Toolkit. It has an option to go back to stock if you're soft-bricked.
Well I just did a factory restore/wipe (because Im SO looking forward to setting everything up again...) and it made zero difference. I'll try the stock kernel if someone could point me in the right direction to find a copy of it.
NVM found it. I'll give it a shot.
Ummmm okay then. I had my N7 turned off while looking for a solution to this fiasco. I picked it up so I could flash the stock kernel, and it had turned itself back on. Not only that, but it was fully booted up. Granted it's back to the initial setup after doing a factory restore, but there we go. It automagically fixed itself. Now to spend a couple hours putting everything back how it was. Yay.
Protip children: Always. Be. Nandroiding.
HELP! I've been using my LG G2 for around 3 months with mo problems at all. I'm rooted with Janjan's custom rom. This morning my phone froze, so i rebooted it. From then on i could not connect to my mobile network as well as Wifi networks. I can see the phone is also scanning the media files, and i cannot open any programs. The phone then restarts itself after about 20 seconds. If i turn the screen off, i cannot turn it back on.
I have already tried restoring to a backup i had on CWM, but the same thing happens.
Has anybody experienced this before? Any suggestions on what to do????
Thanks!
**Edit.
Was able to snap this pic before it rebooted on me again. The "Error" message, stays on even if i exit Settings.
Flash back to stock using this method http://forum.xda-developers.com/showthread.php?t=2432476
But before you try to return to stock, make sure you completely wipe the device in CWM.
MalignantQuechnitlan said:
Flash back to stock using this method http://forum.xda-developers.com/showthread.php?t=2432476
But before you try to return to stock, make sure you completely wipe the device in CWM.
Click to expand...
Click to collapse
hey thanks for the reply. I've tried returning it to stock. Wiped cache and factory reset in CWM, and followed the tutorial to return to stock.
After the phone restarted, it showed stock boot animation and is totally stock now.
BUT the problem is still there. My phone continues to reset itself every 10-20 seconds, and still cannot connect to any networks.
djlpio said:
hey thanks for the reply. I've tried returning it to stock. Wiped cache and factory reset in CWM, and followed the tutorial to return to stock.
After the phone restarted, it showed stock boot animation and is totally stock now.
BUT the problem is still there. My phone continues to reset itself every 10-20 seconds, and still cannot connect to any networks.
Click to expand...
Click to collapse
Hmm, that is odd. Do you have a back up of the phone before you changed anything? i.e. a stock backup?
because it seem you may have wiped your EFS partition by accident.
No i don't have any backups, The only back up i had was a stable version of the ROM i was using. And it seems like when i reverted back to stock, all the files in the internal memory is erased as well.
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.