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
Related
In December of last year, I had my friend root and install CyanogenMod onto my Mytouch 3G Slide. Everything was working fine until I wanted to update my ROM and tried to boot my phone into recovery mode to make a NANDroid backup. A screen with a picture of a phone and a red exclamation point inside a triangle would appear, and I'd have to pull the battery out to restart the phone.
Then, I tried to access the bootloader by holding the volume down and power buttons. After some loading, it asked me if I wanted to update. Not knowing what it was asking, I said no, and tried to access the actual recovery menu, but the same screen showed up.
I tried again, this time accepting the update. Now, when my phone boots, the stock mytouch splash screen appears and the phone does nothing from there.
At this point, what would be the best solution? Is my phone just bricked, or is there a way to restore it to the stock firmware/recover CyanogenMod?
EDIT: For clarification, I can still access the bootloader, where I have four options: Fastboot, Recovery (See problem above), Clear Storage, and Simlock.
EDIT 2: I left it on the splash screen and discovered that it seems to have just thrown my phone into a stock factory state, running 2.1-update 1. Not sure if it's still rooted.
Hi guys, reasonable newbie here. My Galaxy S2 has stopped displaying anything after the initial logo. In fact it seems to turn the phone off as you can make repeated attempts to boot it within a few seconds.
I started by flashing an insecure sgs2 kernel from this site with odin, then used s2root.
I then played around with rom managed but found it wouldn't boot into clockworkmod (orange exclamation mark in a white triangle every time) I booted into it manually and started trying to flash cm7 which I had downloaded earlier.
I wiped the data etc and flashed the cm7 zip (plus the google apps zip). Rebooted and got into cm7 with everything seeming fine.
Next I thought I should probably flash back to the stock version of the insecure kernel. I rebooted the phone but got distracted and didn't start it up in download mode, I looked just in time to see the normal logo (with the yellow insecure triangle) and then nothing....just blank.
I tried rebooting afew times and nothing, even after yanking the battery. Then I tried getting back into clockworkmod to reflash cm7. Nope, same thing happens.
I can still get back into download mode but nothing I flash makes the slighest difference. Tried reflashing clockworkmod, insecure and stock kernels of various versions but I'm stuck.
This is almost a new phone and I can't believe I've already killed it I would be so grateful for any tips, I've included as much info as I can think of from the top of my head but I will do my best to answer anything you gurus might need.
Again, very grateful for any help...I don't want to have to explain to Orange how I've managed to brick this after 4 days
Ok after trying over and over again to get into recovery mode, it booted into the original (3e) recovery. I've just flash cwmod to it again and have just flash cm7.
After reading some posts about cyanogenmod sometimes not flashing correctly first time, I did it twice (and it did indeed take longer the second time) and twice for google apps.
Next I'll try to get back to the stock kernel. This is where it went wrong before but i'll cross my fingers.
Edit: Well, multiple reboots didn't cause a problem but flashing the stock kernel back does kill the handset again. I'm sure this stuff is all obvious to those with experience I guess I'll have to sit with an insecure kernel and the yellow triangle for the forseeable future. On a side note, s2root doesn't see the phone connected with cm7 (yes usb debugging was turned on). I'm hoping that it is pre-rooted but I haven't tested that yet.
Hi all,
I rooted my gf's nexus s a while ago to get the ics update faster.
A few weeks ago she updated it to jelly bean via ota.
Now for some reason my girl decided to do a factory reset few days ago
But now i want to unroot it and it's not working
when i go into recovery mode i get the android mascot laying down with an open stomach, but with a ! mark in a traingle
(i wanted to show a picture but the forum is preventing me from doing so)
anyone any idea what to do ?
EDIT: after trying to get into the recovery several times, the phone just died
it doesn't turn on anymore
what do i do now ?
lol it could be bricked if it wont turn on. the picture of andy laying down and an exclaimation point means you dont have a custom recovery installed. if she did a factory wipe and has the ota, the phone is most likely no longer rooted. you can just relock the phone and its like it never happened
Sent from my Nexus S 4G
alright
i just couldn't connect the phone anymore to my pc to lock it
found it weird...
anyway it's now to the shop as i couldn't get it working anymore
it went from 81% to 0% in seconds after disconnecting from the pc
after that it wouldn't turn on anymore
[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.
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.