I have been working on this all day and I posted earlier but now the situation has changed.
Hardware-Original XOOM Verizon branded, 3G
Never updated to 4G, never rooted, build shows JZ054M.
Last night it went into a rebooting loop out of nowhere. Today I tried flashing it with a .sbf file that matched my build # using RSD Lite.
Now it just sits there and tries to boot up (colored squares).
I can get to the three choices-RSD, Fastboot, and Android Recovery (this last one takes me to a graphic of Andy on his back with an exclamation point and then it reboots itself).
Could someone please aid me in getting my baby back up and running?
I really appreciate it.
Related
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
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.
Sorry everyone... I tried one more time (my 5th attempt!) and it worked this time! I have no idea what happened with the earlier attempts. Thanks
Hello everyone. I'm having a problem with a Rogers Skyrocket here and hope someone can help. It was running a custom ROM, but I was given the task of returning it to stock. I don't recall which ROM was on it, but it worked nicely. I should have just kept it that way!
Thanks to vincom's super helpful posts, I got the info & file(s) needed to get this thing back to stock. I installed Odin 1.85, and extracted
I727RUXLF3_I727RRWCLF3_I727RUXLF3_HOME.tar.md5
from the zip. I started by doing a wipe/factory reset (from inside the custom rom) first, and rebooted to see that it showed the initial setup screen. Then pulled battery and booted the phone into ODIN mode. I made sure to kill Kies completely before connecting the phone to my laptop (WinXP). Then launched Odin, hit the PDA button, loaded up the above file, left the check-boxes as they were, and flashed. It was successful, and rebooted the phone.
The rogers logo appears, and the samsung galaxy bootanimation comes up, and it continues to animate.... forever (for the record, I waited 20 minutes, more than enough time). I can pull the battery and try to boot again but it still stays on the bootanimation. I'm not sure what else to do? I can still get into stock recovery or Odin mode. Can anyone help? Thanks
I've poked around the forum and not found what I need...so I'll venture a new thread.
Here's the deal. The other day after being at work all day, I came home and unlocked my tablet. A bunch of errors popped up right away about the launcher crashing and a few other things. I powered it down and turned it back on...and that's as far as I got. Every time I try to boot it gets stuck on the boot logo. I was able to boot into ClockworkMod Recovery mode and flashed xboxexpert's custom rom...but still no luck. The stupid thing won't boot and I'm out of ideas. Any help would be much appreciated. Thanks in advance!
Anybody got anything on this?
So I have had my S3 rooted for a long while. But the past few weeks it's been running a bit slower. This week it started randomly turning off. I thought it was my battery at first. But then when I tried to turn it back on it got stuck at the Galaxy s3 screen and would not get into the OS.
I tried to get into recovery, it froze on the splash screen. I made sure both were actually frozen by leaving it sitting there for 30 min to an hour.
Tried to flash using this thread: http://forum.xda-developers.com/showthread.php?t=1974114
It kept just sitting at writing NAND.
Now my phone says "Firmare Upgrade encountered an issue, please select recovery mode in kies and try again"
Kies will not connect my device. It sees it but will not complete the connection. I tried using the model and IMEI number to upgrade firmware but it still would not connect to do that.
More searching lead me to this: http://forum.xda-developers.com/showthread.php?t=2581166&page=11
But I can't get into OS or recovery so I don't think this would work.
Any suggestions on what I can do from here? I only really need the phone to work for a few more months. My old Droid incredible just doesn't cut it at this point.
Sorry to bump, but nobody has anything for this? I haven't really found any other options.
Your bootloader is fine so that thread won't help you. What was the last version of touch wiz that was on your phone before you ran into problems?