[Q] Installed OTA 4.4 Update on my Rooted HTC One and now it's stuck on "No Command"
Hey All,
I tried searching for a solution to my problem and I couldn't find it. I am hoping you can help me.
I have a T-Mobile HTC one that I rooted and put the Stock Google Edition on back in August of this year. It's worked beautifully. Two nights ago, I received a 4.4 OTA update and I went to install it right away. Sometime during or after installation, the screen went black and was showing the Android guy with his chest open and a ! inside a red rectangle. It said "Error" then "No Command". I rebooted the phone a few times and when nothing changed, I ended up (in a moment of frustration and panic) wiping the cache and the partition and doing a factory reset. Now, I'm still in the same place as when I initially saw the "No Command" screen except 4.4 isn't on my phone anymore due to all the wiping and resets. The computer (mac) won't recognize the phone connection when I connect it to USB.
Is there anything I can do? I don't think T-Mobile would be much of help since I rooted the device.
Thanks in advance for your help.
Related
ok so i get the OTA and hit install now. it reboots and gets to the box with the arrow coming out and loads all the way and then goes to a screen with n android and an exclamation point and is stuck there. so i tried the manual update and got stuck rebooting over and over. long story short i have now wiped phone completely and yet clockwork mod stays there. i can not update and now have a reset phone so i am not very happy. would reverting to stock recovery help? thanks for the tips and help guys
Hi
I got an issue after receiving an OTA update for my Nexus S. It was an official update asking my if I would like to install it. I choose yes and the device booted. It began to install and suddenly the triangle with exclamation mark popped up.
Since then, the phone only boots up randomly. Mostly if stays at a logo saying "google" in middle of the screen. No more Nexus bootup color game.
Is there any way to get this phone back to stock without being an expert?
It is a Nexus S 9020
I9020XXKD1
Kernel 2.6.35.7-ge382d80 android [email protected] #1
GRJ22
It was stock rom 2.3.4 and rooted at the time of the update
Any help is appreciated.
Regards
Martin
I am in the same ship Martin. Updated it to the 2.3.6 from 2.3.4 when I got the OTA. It was working fine, then the screen just stopped responding. It gets stuck at the google colour game now, and the screen turns off after some time. However, if I plug in the usb power charger, the screen lights up again, and the colour game proceeds a bit, then the screen turns off again. if i pull out the usb charger then, the screen lights up again. its been crazy since morning.
im sure that if we reset it, we can get it to work. but in my case i have been unable to do that. can someone tell us how to format/reset our nexus S?
Think I got it sorted.
Running 2.3.6. now, rooted. No loss of data for whatever reason.
What I did.
First of all, in one of those moments were the device was up, i copied a stock 9020T rom 2.3.6 on the sdcard.
In recovery mode, SDcard was never available. While reading through endless threads I found a recovery rom image called 5023_green.img
I had nothing to loose, so i flashed it using fastboot. A started in recovery and I got full access to my SDcard. I updated from full stock rom 2.3.6 I loaded to the SDcard earlier. Since then, no more issues. Surprisingly here I would have expected loss of root and wipe of all data. But this did not happen. All data is there in its place.
Cheers
Martin
Hey guys.
I'm new in the Android world and bought an LG G2 back in november.
I had originally intended to custom install cyanogenmod or KitKat 4.4 to replace stock rom, but I couldn't find a way to install a custom recovery, and was only able to root my device via Kingo Android Root.
A while later I saw an update that popped up, and not knowing any better I clicked install. It was about 114MB. That was about 3 days ago, and my LG G2 has been stuck in a bootloop ever since.
When I try to turn it on the LG logo shows up, then it says "secure booting error"and "Cause: boot certification verify" on the top left corner of the screen in white text.
I tried doing a hard reset, but that didn't work. I don't have a custom recovery so that I can clear the cache and data or something. So pretty much I have a bootlooped phone with no custom recovery, I can't do a hard reset, and it's Sprint and everything's new so it's harder to find a fix.
Does anyone here know of a way I can fix this? It would be much appreciated.
Thanks in advance
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
somesortofthing said:
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
Click to expand...
Click to collapse
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
ShapesBlue said:
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
Well, can I somehow get my phone into working order? Because it's as good as bricked right now.
I got a small 10 mb update for my Marshmallow. I downloaded that and after it was done, while installing an error came. i switched off my phone thinking it would start properly. Then it got stuck on the colored balls/dots that come before the welcome screen. I tried switching on and off but no success.
Then I did a factory reset and after everything was done and i thought the phone would get switched on, but it again got stuck on those colored balls. Now the phone is not getting switched on..
Plesae help..!!!
parthkaura said:
I got a small 10 mb update for my Marshmallow. I downloaded that and after it was done, while installing an error came. i switched off my phone thinking it would start properly. Then it got stuck on the colored balls/dots that come before the welcome screen. I tried switching on and off but no success.
Then I did a factory reset and after everything was done and i thought the phone would get switched on, but it again got stuck on those colored balls. Now the phone is not getting switched on..
Plesae help..!!!
Click to expand...
Click to collapse
Is it rooted or non rooted? Stock recovery? Probably you can flash the latest image files (except userdata) and check if it is working.
You can go through the guides on how to flash image files from the sticky posts.