Hello everyone,
I received an OTA update last night for my phone for Android Lollipop. If I had known better, I wouldn't have updated it.
Since the update, my screen doesn't timeout or lock, it just restarts. If I press the power button to turn the screen off, it restarts. I can either shut the phone off completely or keep the screen on, which obviously kills the battery pretty quick.
I tried doing factory reset already, issue is still there. I tried wiping cache partition, same issue.
At this point, I would really like to downgrade to KitKat. Is that possible? And if so, how? I'm on a Vodafone UK contract. My phone is not unlocked.
Any other solution that might help. I don't know what else to do. Please help.
rosesor said:
Hello everyone,
I received an OTA update last night for my phone for Android Lollipop. If I had known better, I wouldn't have updated it.
Since the update, my screen doesn't timeout or lock, it just restarts. If I press the power button to turn the screen off, it restarts. I can either shut the phone off completely or keep the screen on, which obviously kills the battery pretty quick.
I tried doing factory reset already, issue is still there. I tried wiping cache partition, same issue.
At this point, I would really like to downgrade to KitKat. Is that possible? And if so, how? I'm on a Vodafone UK contract. My phone is not unlocked.
Any other solution that might help. I don't know what else to do. Please help.
Click to expand...
Click to collapse
sounds like your phone is broken ..return it if it's Locked and never rooted
Finally fixed
In the end, I had to unlock the bootloader, root the phone and flash a customer ROM (Android Revolution). It worked! Now, I can finally switch my screen off without the phone restarting!
Thanks,
Rose
rosesor said:
In the end, I had to unlock the bootloader, root the phone and flash a customer ROM (Android Revolution). It worked! Now, I can finally switch my screen off without the phone restarting!
Thanks,
Rose
Click to expand...
Click to collapse
you also lost your warranty in the process. If it had not worked you would have been stuck paying for a repair
I'm happy it worked out for you
Related
After the forced AT&T software update, my WiFi will not turn on. I will go into WiFi settings, press the toggle button, and it will grey out and get stuck on "Turning on WiFi". I have tried wiping both caches, and I have replaced the bcmdcm.ko under system\lib\modules with bcm4330.ko, which was the one from the stock ROM. Nothing has worked and this problem persists. I am rooted and my bootloader is unlocked. Is there anything short of doing a full factory reset that can fix this problem?
Please post in the appropriate section.
Thread moved to Q&A
Sent from my Nocturnalized One XL using Forum Runner
Bigluc said:
After the forced AT&T software update, my WiFi will not turn on. I will go into WiFi settings, press the toggle button, and it will grey out and get stuck on "Turning on WiFi". I have tried wiping both caches, and I have replaced the bcmdcm.ko under system\lib\modules with bcm4330.ko, which was the one from the stock ROM. Nothing has worked and this problem persists. I am rooted and my bootloader is unlocked. Is there anything short of doing a full factory reset that can fix this problem?
Click to expand...
Click to collapse
Have you tried flashing the boot.img via fastboot? That seems to help a lot of people.
ronnie498 said:
Have you tried flashing the boot.img via fastboot? That seems to help a lot of people.
Click to expand...
Click to collapse
Ok I've googled around alot and looked on this forum but I can't find a boot.img anywhere that isn't modified. Can you point me to the stock boot.img?
My mom has a Vivid and her phone has been doing this ever since the update was pushed down by AT&T. Since she lives 1000 miles from me, I didn't root her phone, and leaving it stock, the only thing that ended up working was a factory reset. The other thing that was happening after the update was every boot would go through the "Optimizing application 1 of x..." message like it does after the update. I get the impression that whenever she performed the mandatory AT&T update, something didn't go correctly, which is why her Wi-Fi was permanently stuck in this "Turning on Wi-Fi" state. It seems to be working perfectly now, and we no longer see the "Optimizing..." message either when the phone reboots. Now I won't have to do remote tech support when she flies back home next week
tonemand said:
My mom has a Vivid and her phone has been doing this ever since the update was pushed down by AT&T. Since she lives 1000 miles from me, I didn't root her phone, and leaving it stock, the only thing that ended up working was a factory reset. The other thing that was happening after the update was every boot would go through the "Optimizing application 1 of x..." message like it does after the update. I get the impression that whenever she performed the mandatory AT&T update, something didn't go correctly, which is why her Wi-Fi was permanently stuck in this "Turning on Wi-Fi" state. It seems to be working perfectly now, and we no longer see the "Optimizing..." message either when the phone reboots. Now I won't have to do remote tech support when she flies back home next week
Click to expand...
Click to collapse
I think this is my next step. I tried flashing boot.img, but that didn't work. Does anyone have any other solutions short of this?
Bigluc said:
Ok I've googled around alot and looked on this forum but I can't find a boot.img anywhere that isn't modified. Can you point me to the stock boot.img?
Click to expand...
Click to collapse
There's a link to one in the thread for Kozmik Kernel.
Bigluc said:
After the forced AT&T software update, my WiFi will not turn on. I will go into WiFi settings, press the toggle button, and it will grey out and get stuck on "Turning on WiFi". I have tried wiping both caches, and I have replaced the bcmdcm.ko under system\lib\modules with bcm4330.ko, which was the one from the stock ROM. Nothing has worked and this problem persists. I am rooted and my bootloader is unlocked. Is there anything short of doing a full factory reset that can fix this problem?
Click to expand...
Click to collapse
it could just be a problem with the kernels, i was experiencing this even before the update.
Are you on a cusotm rom and/or custom kernel?
wifi will not turn on
y Rogers HTC Raider is unlocked and S-ON. I flashed MIUI 2.8.17 and now I can't turn on wifi, google play won't connect and I cannot boot into recovery mode, it just stays at he HTC screen. How do I fix this?
AshleyPem28 said:
y Rogers HTC Raider is unlocked and S-ON. I flashed MIUI 2.8.17 and now I can't turn on wifi, google play won't connect and I cannot boot into recovery mode, it just stays at he HTC screen. How do I fix this?
Click to expand...
Click to collapse
Did you install the kernel? If you're s-on you need to fastboot flash the kernel image.
Sent from my HTC Raider using xda premium
I recently acquired a Nexus 6 last month. Everything was fine until I got the new 5.1 update notification. I decided to let it download overnight.
The next morning I unlocked my device to find that I couldn't even do that, because pressing the numbers for the pin code did nothing!
Turning it off by holding the power button (the power off option on screen didn't work) only restarted the device. Restarting didn't fix the issue.
Please help! :crying:
cerealtendencies said:
I recently acquired a Nexus 6 last month. Everything was fine until I got the new 5.1 update notification. I decided to let it download overnight.
The next morning I unlocked my device to find that I couldn't even do that, because pressing the numbers for the pin code did nothing!
Turning it off by holding the power button (the power off option on screen didn't work) only restarted the device. Restarting didn't fix the issue.
Please help! :crying:
Click to expand...
Click to collapse
Flash factory using wug's toolkit
http://forum.xda-developers.com/showthread.php?t=2947452
jiv101 said:
Flash factory using wug's toolkit
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
USB debugging isn't on, so the toolkit wasn't able to identify my device.
How do I turn on usb debugging from a computer? The screen is completely unresponsive so I can't get past my lockscreen
cerealtendencies said:
I recently acquired a Nexus 6 last month. Everything was fine until I got the new 5.1 update notification. I decided to let it download overnight.
The next morning I unlocked my device to find that I couldn't even do that, because pressing the numbers for the pin code did nothing!
Turning it off by holding the power button (the power off option on screen didn't work) only restarted the device. Restarting didn't fix the issue.
Please help! :crying:
Click to expand...
Click to collapse
I had a similar issues with my first Nexus 6 I bought. It worked find for a whole day and then one morning I wasn't able to unlock it and my touch screen wasn't working anymore. Did not flash anything on it-it was 100% stock. I have the feeling you may have the same problem. I am not sure 100% but you may need to contact Motorola for replacement.
jiv101 said:
Flash factory using wug's toolkit
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
So I managed to unlock bootloader and flash stock via fastboot mode and the device booted up after erasing was done.
The welcome screen appeared and the screen was still unresponsive, I couldn't press anything
I'm worried Motorola's warranty won't cover my device since I bought it from Saudi and I'm currently living in Sudan.
I have an upcoming trip to Malaysia, I'm wondering if I should take it with me there and try to fix the issue.
So here's my story: my phone was JellyBean. I didn't tinker with it, didn't root, just used some launchers. It upgraded to KitKat. I kept using it, even though I liked JellyBean better. Then one month ago it froze and stopped responding even to physical buttons. I managed to restart it, but it wouldn't go past the intel logo. Somehow I got it to go past it and give me like two seconds on before it would freeze and become unresponsive again, so I got to enter safe mode (all following instructions on the internet, which buttons to hold to manage to get into safe mode). Once in safe mode, I deleted every app that had been recently updated or installed, one at a time, trying to turn my phone on each time, until I finally deleted facebook (that enourmous blue monstrosity taking all that internal space), and the phone seemed normal. I re-installed the other apps I had uninstalled, then one day later, it froze again. Now it wouldn't go past the intel logo. Only then I gave up and used RSDLite to re-install the firmware - BUT! The firmware I managed to find was JB, but I had been wanting to downgrade for some time, anyway, so I unlocked the bootloader and flashed JellyBean. And it worked. I was proud. Then one month later, today, it froze again. I can do the same procedure, and lose all my data again, but I fear the problem will remain unsolved and it will freeze/crash/explode one month from now. Can someone help me figure out what my problem is, or give an alternate solution to try?
TL;DR:
my razr i was stuck on the intel logo screen, I unlocked the bootloader and flashed JB, it worked, one month later it is now stuck on the WARNING BOOTLOADER UNLOCKED screen. Please help thank you.
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
-Vatsal
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.
Re:
alfadog77 said:
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.
Click to expand...
Click to collapse
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?
Enalay527 said:
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?
Click to expand...
Click to collapse
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk
aaldiar said:
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I updated it ota then on Samsung kies with the latest firmware. Everything works fine except the power off issues.
I think this is a common 5.0.1 issue, same thing started happening to me after update. Gotta wait for update or back to 4.4.4.
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
I would recommend downloading the full DOK2 firmware. You can find it in the below linked thread. Make sure you use the newest version of ODIN to flash it 3.10.7.
It should give the phone aq complete clean install of the firmware. Kies sometimes can be janky. It you are going to get rid of the phone the best is to do a full ODIN flash.
http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!
notufatjesus said:
I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!
Click to expand...
Click to collapse
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.
I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....
tony yayo said:
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.
Click to expand...
Click to collapse
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me
Willy318is said:
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me
Click to expand...
Click to collapse
Not really sure. Mine was never rooted. I've heard of plenty of people sending their rooted phones in with no problem.
thiennvbk said:
I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....
Click to expand...
Click to collapse
Make sure you are using the ODIN version 3.10.7 if you are using an older version of may be what caused the issue.
If you did use the newest Odin, then I would factory reset your device, but into twrp and wipe everything but external SD Card, boot back into download mode and flash the firmware again. Most likely a few files for messed up during your Odin flash and it messed up the process. Also make sure you are using the USB cord that came with the device.
I found the fix for this mmc_failed. Making a new thread for this.
---------- Post added at 06:11 AM ---------- Previous post was at 05:38 AM ----------
http://forum.xda-developers.com/showthread.php?t=3277144
Here's is the fix. Don't forget to hit Thanks button
I have a stock AT&T G6, got it when the phone first came out, and I haven't touched the firmware. Update after update, no problems.
Finally this morning my phone had enough - I performed a system update. However during the reboot, the phone froze for 30 minutes on the AT&T logo. Nothing changed.
Reset phone, nothing changed, 15 minutes no change. Reset phone to recovery mode - wipe cache - reset phone. Same thing - stuck at AT&T logo.
Finally I had enough - I did a full Factory reset. AT LAST! After 8 painful minutes stuck at the AT&T logo, my phone came to life and welcomed me to my new phone (FML).
So here I am with a freshly loaded copy of my new Nougat 7.0 software on my AT&T Build ( NRD90M.G920AUCS6EQF1 ) and I am desperately trying to run every possible data recovery option possible.
I WANT to recover my photos and SMS messages before I start using my phone. But I can't - every app I've run shows no results. Everything I'm seeing shows I need to root this phone to make it work.
Unfortunately I have no clue htf to do that. Every instruction I find online does not include my build version. My phone is turned off and not used until I recover this data. I would appreciate any help I can get in recovering this data!
Cassetti said:
I have a stock AT&T G6, got it when the phone first came out, and I haven't touched the firmware. Update after update, no problems.
Finally this morning my phone had enough - I performed a system update. However during the reboot, the phone froze for 30 minutes on the AT&T logo. Nothing changed.
Reset phone, nothing changed, 15 minutes no change. Reset phone to recovery mode - wipe cache - reset phone. Same thing - stuck at AT&T logo.
Finally I had enough - I did a full Factory reset. AT LAST! After 8 painful minutes stuck at the AT&T logo, my phone came to life and welcomed me to my new phone (FML).
So here I am with a freshly loaded copy of my new Nougat 7.0 software on my AT&T Build ( NRD90M.G920AUCS6EQF1 ) and I am desperately trying to run every possible data recovery option possible.
I WANT to recover my photos and SMS messages before I start using my phone. But I can't - every app I've run shows no results. Everything I'm seeing shows I need to root this phone to make it work.
Unfortunately I have no clue htf to do that. Every instruction I find online does not include my build version. My phone is turned off and not used until I recover this data. I would appreciate any help I can get in recovering this data!
Click to expand...
Click to collapse
No known root for current builds to my knowledge. Don't know if anyone is still picking away at it, but I wouldn't hold my breath. Development on this device has been almost silent for many months.
dandrumheller said:
No known root for current builds to my knowledge. Don't know if anyone is still picking away at it, but I wouldn't hold my breath. Development on this device has been almost silent for many months.
Click to expand...
Click to collapse
Pretty much what I've figured. Sounds like I'll just have accept they're lost and move on. Thx