Database Info

[Q] PLEASE HELP!!! Cannot Boot Nexus S!!

Hi everyone,
I'm sorry I'm quite new to this, and I'm afraid I've gotten myself somewhat stuck with my Nexus S. Yesterday I managed to root it, install superuser, as well as clockwork mod. Today I wanted to try a new rom and after some attempts, it seems I no longer have any working roms on my phone. After much searching with no luck, I turn to you guys for your expertise.
So I am able to see fast boot upon pressing the volume up and power buttons, and am certainly able to choose recovery and get into clockwork mod. Within clockwork mod I can mount USB storage, so I can transfer roms to the internal SD card. I've tried 3 or 4 roms, some say they install correctly, others not, and after trying to boot after any installation I simply get stuck at the google screen with the lock image at the bottom. The only things I have "deleted" is wiped the data and cache. I have no idea, but I think I may have erased the bootloader image or something else that I should not have that is required.
I have a i9020a model (non-4g model I believe), can you pleeeeeeeeeeeeeaaaassee help me!! I just want to get back to gingerbread 2.3.6, and my phone back up and running the way it was. I've become quite nervous after some searching with some saying a resistor mod is needed on the hardware!!

Your okay cause you can get into fastboot and recovery so don't worry. Maybe the rom you downloaded is not for your phone. Did you make a nandroid backup before flashing the rom? If yes then go into backup and restore from clockwork recovery to go back to stock.
Sent from my A500 using Tapatalk

If you can get to recovery, just flash the stock image FOR YOUR PHONE. Then you can go through and reroot..don't worry, you'll get the hang of it.
Sent from my Nexus S using Tapatalk

So my phone is not "bricked" as they say?? I'm not in big trouble?
I did not make a nandroid backup What kind of image am I looking for and how do I install it on the phone? I know my phone is of the variant i9020a, but how am unsure of how much more specific I should be looking for.
Looking at the following post: http://forum.xda-developers.com/showthread.php?t=1063664.
Should I try installing the Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader option?

Choose the latest 9020a version of the FULL ROM, which is what you have already have eyes on.

I've tried installing the file I mentioned above, but I get a status 7 error when trying to install, and the install is aborted.
Could I get some more assistance please? Can anyone point me to a correct, full rom? Or perhaps I'm installing it incorrectly, could someone be so kind to outline the correct steps to a proper install?
Edit: I think the above mentioned file is for a GSM model, I'm sure I have the CDMA version.
Also, somewhat good news. I managed to install the oxygen rom, but for the 4g version and installed fine with no errors, but I have no service. What does this indicate, as I still want to restore back to a factory version (non-4g) of gingerbread 2.3.6.

What CWM version do you have? Is it 3.0.0.0?
Also, if you have no service, it's likely that you downloaded a ROM with an incorrect radio.
Edit:
If you have CWM 3.0.0.0, make sure to download the latest version, found in this thread: http://forum.xda-developers.com/showthread.php?t=988686 (use 5023-cyan.img). You flash this the same way you did CWM previously, though in the terminal make sure you type out the 5023-cyan.img file name.
Next, download the stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1063664. Simply look for your phone version, and you'll find the correct software variant.
Maybe you've fixed your phone already; if not, I hope this helps!
I wish you the best of luck. Oh, and through problems like these, you come to learn a lot more about your phone. That's what I've found, at least.

At the thread you mentioned above there is a version with a different radio, you might want to give that one a try.
You also said that you only wiped data and cache, so maybe you should do a full wipe before. Not doing that can sometimes lead to problems.
Sent from my Nexus S using XDA App

To be brief, the phone is up and running as brand new! Thank you so very much everyone. It seems the error was with CWM, as I was able to install and boot a 4g oxygen rom on my phone, I went into rom manager, and at the bottom of the list was an option to upgrade to 5.x. Installed the CWM update, wiped everything and was able to install the factory rom, no issues, and everything works just as I remember
I have most certainly learned more about my phone, and I am going to look at it as a rather stressful learning experience rather than a mistake on my part.
But a sincere thanks to everyone once again, I posted this at like 4am here and had a response within a few minutes, I was pulling my hair out haha!

Flashing to stock rom will help you out. You can get stock roms from Internet simply by searching in Google...
Sent from my Nexus S using XDA App

[Q] Can't flash back to stock

I've downloaded the stock image directly from the Motodev site for my MZ604. It successfully flashes boot.img. When I try to flash system.img, it just hangs. I thought maybe I was rushing it before giving up but I left it going for a couple of hours this morning with no luck. I'm happy with cwm and running ics roms but this is puzzling me as to why I can't get back to stock. My stock recovery img got trashed last month so recovering back to stock isn't an option. Any suggestions?

More specifically, I get a successful send of system.img, the hang up happens while writing.

I know this may not help you but have u tried downloading the file another time and compare the md5 between the file.. If they are the same then i have no idea mine was able to write correctly.. If they are different download it a 3rd time and see which one is truly correct.?
Sent from my mind control device

Downloaded from another site and got the same results. I kept rebooting the xoom and repeatedly tried flashing and it finally went through. For some reason, I had to do the same thing for recovery and userdata. It's back to stock and working normally now.
ps now i'm about to root again and flash a nightly lol. I just couldn't understand why it did the same thing last month when i tried to revert to stock and gave up. I was determined to figure it out today.

Awesome to hear! Flash away lol
Sent from my mind control device

[Q] NexusS (i9020T) hard bricked, at which step did I go wrong?

Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.

I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk

I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA

Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.

Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.

I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though

I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).

I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.

Help - constant Samsung Logo on boot

HELP!, I have been very lucky in the past and have had very few issues rooting and applying different themes, kernels etc. but the fact is I have little idea of what I am doing. For some reason I can't explain I tried to load the ninja rom to get FP5, ( and I did not back up before I tried to install it. because I am that stupid). Not sure what happened but I got stuck in a Samsung logo boot loop. I read where someone else had similar issues and got going again by putting Tweaked 2.2 over top after a clearing data etc so I tried that. Now when I boot I get the Samsung logo and it just sits there. I have rebooted several times, battery pulls, mounted everything and I still get the same frozen logo.
I would like any file I can load from CWM or Odin to get me back up. I will go back to stock if need be but I am not sure what I need to get back to stock FP1 to start again from there. or stock FP5 or whatever.
I have cleared data already so whatever gets me working I will try
I found a video with instructions to to EP4 but I thought that might be a little too far back. I know how to use CWM and Odin, I am just not sure what I need to get to stock, or any good working version, starting from my current state.
(Seached for FP1 stock but mostly found discussions of "upcoming" OTA and the EP4 videos.)
Thanks

fsuinnc said:
HELP!, I have been very lucky in the past and have had very few issues rooting and applying different themes, kernels etc. but the fact is I have little idea of what I am doing. For some reason I can't explain I tried to load the ninja rom to get FP5, ( and I did not back up before I tried to install it. because I am that stupid). Not sure what happened but I got stuck in a Samsung logo boot loop. I read where someone else had similar issues and got going again by putting Tweaked 2.2 over top after a clearing data etc so I tried that. Now when I boot I get the Samsung logo and it just sits there. I have rebooted several times, battery pulls, mounted everything and I still get the same frozen logo.
I would like any file I can load from CWM or Odin to get me back up. I will go back to stock if need be but I am not sure what I need to get back to stock FP1 to start again from there. or stock FP5 or whatever.
I have cleared data already so whatever gets me working I will try
I found a video with instructions to to EP4 but I thought that might be a little too far back. I know how to use CWM and Odin, I am just not sure what I need to get to stock, or any good working version, starting from my current state.
(Seached for FP1 stock but mostly found discussions of "upcoming" OTA and the EP4 videos.)
Thanks
Click to expand...
Click to collapse
Take a look this, you have many FP1 stock roms (debloated/deodex/root etc..) http://forum.xda-developers.com/showthread.php?t=1560117

thanks for the links.
now I can't mount the SD card. Maybe that's why it is stuck in the first place. I know I have run into this before but can't recall what I did to get it mounted.

Fiddled around with USCC Galaxy S6: Boot Loops, process com.google.process.gapps...

1. TWRP is up
2. baseband G920R4TYU2BOF7/HW version G9020R4.02
3. No Mods
4. Rooted
So I tried flashing the Vader ROM, I was getting boot loops at the language selection screen. I go back and restore from backups my original stuff. Boot back up and now I'm getting the lovely "process.com.google.gapps has stopped" error. I'm assuming that I may need to find gapps for 5.1.1? I also tried flashing XtreStoLite ROM with the Aroma add on. Everything seemed to be working great with the exception of the data and no signal, which I am to assume is because I'm not using the correct carrier-specific stuff.
Go to download the stock ROM for my phone, and I keep getting an error as well. Odin won't flash it. One thing that I noticed is that the stock rom was 5.0.2 where when I got the phone 3 days ago it came with 5.1.1.
At this point, I'd like to be able to get it back to stock if possible. I jumped the gun and started flashing all sorts of things without checking to see if it would even for with a USCC galaxy s6. Any help would be much appreciated.

UPDATE: Problem seems to have resolved itself with the last restore. no more problems with gapps. However I am curious as to if any of these custom roms will work with a USCC variant