Database Info

[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.

[Q] kernel flashing problems

Ive looked just like the rules stated. Yet i can not find out a reason to my problem. Im no noob whenit comes to flashing kernels and roms. with that being said here goes. I have jst aquired a Nexus S. I traded it for my old iphone 4 felt good to be back to android. anyways I have Kangy-U loaded up and ready to go just flashed it yesterday. today I figured after some resarch I would flash Air kernel. after I flashed it through recovery (CM) it goes through the proces and says it s flashed. I boot back into kangy and look under settings and find Its still stock. I tried again, same problem. by this point I figured bad download redownloded same problem. so I then figured ok they are just not playing nice together. I trie a different one. this time cyans stock universal still same problem.
Is there a step Im missing?

Have you posted over in the thread for the ROM? Never heard of a kernel not flashing like that with the recovery saying the flash was successful.
Sent by pocket technology

Try reflash the rom, just a guess.
Sent from a sandwich using my Nexus S

ya i reflashed everything wiped data system cache boot. then it worked. I do know CM can be weird sometimes. all is figured out. thanks guys.

It kood just be the kernel
Sent from my Nexus S 4G using xda premium

[Q] Imo Lean Kernel, CWM and OTA

Will I need to flash the stock kernel back on my phone to take the OTA or will it work with Imo's kernel? I tried to reflash the boot.img from my nandroid and wifi was not working, so I reflashed Imo's kernel and wifi works again and I am sitting in a holding pattern. I'd rather not have to ODIN back to full stock because I only have access to PC's at work and don't really have time in the day at work to be doing stuff like that while there.
Also can I just download EZ Recovery and flash the stock recovery?
Phone is rooted, unlocked, CWM with Casual and Imo's Lean Touchwiz kernel. TIA

What exactly makes you want the update? If it's the radio (which imo is the only reason to consider the OTA) then just get the radio and flash it in CWM.

i already have the radios flashed but I've had this weird issue that seems to only happen after flashing the kernel but has only happened on a few occasions mainly on the weekends at my daughter's 2 soccer games to be exact. Camera and video have acted weird, first was video controls were upside down, had to reboot a few times for it to fix and just yesterday everything I shot shows fine in gallery but when I go to import into Instagram the pics are all rotated 90 degrees.
I can't afford to have data issues which is the reason I haven't installed a custom ROM since I use my phone for work quite a bit. Figured go back to stock kernel, take OTA to clean out any weird issues that would linger and wait for either official JB or for ROMs to get solid on data issues.

mav3rick478 said:
Also can I just download EZ Recovery and flash the stock recovery?
Phone is rooted, unlocked, CWM with Casual and Imo's Lean Touchwiz kernel. TIA
Click to expand...
Click to collapse
Yes, but remember if you don't already have the OTA notification nothing with come just because you removed the custom recovery. If you've already received that notification then disregard this post.
Sent from my SCH-I535 using xda app-developers app

Thanks Snoop, been getting the OTA notification for 2 weeks now. I thought originally after it failed because of CWM it disappeared but woke up a few mornings to my phone being in CWM asking if i wanted to install the OTA and thinking to myself, "good god how long has my screen been on?!"

mav3rick478 said:
Thanks Snoop, been getting the OTA notification for 2 weeks now. I thought originally after it failed because of CWM it disappeared but woke up a few mornings to my phone being in CWM asking if i wanted to install the OTA and thinking to myself, "good god how long has my screen been on?!"
Click to expand...
Click to collapse
No problem. If you still notice weird issues then Odin to an older firmware and accept the OTA from there.
Sent from my SCH-I535 using xda app-developers app

[Q] CWM on One XL

Is it still a big "no no" to use CWM on the XL? I remember when I first got this phone we were not supposed to use it? From what I can tell all the ROM's still say flash in TWRP. The thing is I prefer using ROM Manager especially considering ive paid for it. GooManager is a just a bit lacking to me. If i do have to use TWRP it's not such a big deal, but since I'm getting a replacement phone it might be the perfect time to switch back.
I'm looking at using this one (http://forum.xda-developers.com/showthread.php?t=2240660).
Thanks guys.

kyleallen5000 said:
Is it still a big "no no" to use CWM on the XL? I remember when I first got this phone we were not supposed to use it? From what I can tell all the ROM's still say flash in TWRP. The thing is I prefer using ROM Manager especially considering ive paid for it. GooManager is a just a bit lacking to me. If i do have to use TWRP it's not such a big deal, but since I'm getting a replacement phone it might be the perfect time to switch back.
I'm looking at using this one (http://forum.xda-developers.com/showthread.php?t=2240660).
Thanks guys.
Click to expand...
Click to collapse
Using software flashers isn't a great idea. (IE not flashing directly from within recovery)
TWRP seems to have more working features than CWM.

You can use it if you want, but beware that it may not work as well as TWRP. I'd use TWRP unless you absolutely can't. It works a lot better on this phone anyways.
Sent from my evita

That version of CWM is very stable, at least it was when I was using it. The only negative was that Viper ROM wouldn't flash with it because it terminates the install if TWRP isn't installed, unless it's been changed. Other than that I had no problems with Phil's CWM whatsoever. It's not your typical CWM. The way the touch interface works is different than TWRP and kinda cool. It will also restore TWRP backups, which is a nice feature. I only switched back to TWRP because it was the only recovery image I had on my computer after I ran the 3.18 RUU and I was too lazy to download it again, lol.
Sent from my One X using Tapatalk 2

I've been using the "official" CWM, ever since TWRP 2.4 and 2.5 were having so many problems: http://forum.xda-developers.com/showthread.php?t=2148909
Everything on this CWM release seems to work fine for me. I know everything on TWP 2.6 is working fine, I just haven't bothered to go back to it.
Notions that CWM is a "big no no" is based on very outdated info. This dates from back when CWM was not an official release, just a hacked port that caused some serious (and difficult to resolve) issues for some folks.

I use cwm also since twrp was giving me dramas.
I find cwm is more compatible with things.

I've never used CWM personally, I never saw a point as everything has worked for me with TWRP (provided I stuck with 2.3.3.1 until 2.6 came out). I guess it's just personal preference. I've only gone by other's posts in terms of things people have said, not being able to mount or wipe SD card or not being able to charge in recovery. But there certainly is a bug going from certain versions of CWM to TWRP causing FC on Dialer.

The only problem I've found with TWRP 2.6 so far is that it was far too easy for me to wipe my sd card accidentally today. Using advanced wipe and moving a little too fast. No backup either. Whoops.
Sent from my Evita

[Q] Error mounting sd card in CWM

Okay so I've been all over this site and linked to many other articles to proceed and hope to fix my issue but nothing seems to be working for me. To get you guys up to speed it's a SGH-T959V and I started out with having jelly bean 4.0 on it then upgraded to 4.2.2 which I occurred an issue with that and had to revert to getting gingerbread flashed back on. It's been a little while since I've done so and kinda forgot how I did it. I've read about using odin and heimdall but no luck getting my phone to connect with either of those programs.
Recently upgraded to 4.4.2 slimkat which was working good (still some bugs, since it's weekly) and had TWRP recovery on it. Problem started as I was starting the process to flash the new update of 4.4.2 and I created a back up and recovery for it prior to flash but now its gone. During the flash of the new update it had occurred some error and now went to Semaphore CWM Recovery v6.0.4.5 and has a bunch of errors to it and I cant even format or mount an sd card. I've tried using a couple different sd cards same issues. I can boot into download mode no issues.
Anyone be able to help me out? I am pretty stumped on this one and have tried many things to get it to work. Also are there any programs I could use besides odin and heimdall to flash a different version of CWM or TWRP via usb?
Thanks guys let me know if I left anything out or if you have questions to help me out better.

Hey guys, here are a couple of pictures of what it looks like while in CWM and what its saying.

Hey guys never mind, I already figured out what I was doing wrong. All I needed to do what open a file I downloaded in this thread to get it back to stock gingerbread. Now I am going to do some more flashing to get it back to 4.4.2 slimkat. Thanks