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] Phone boots very slow! Huge problem!

My problem is when I turn on the phone, the Google logo stays stuck and after unknown minutes boots in with the software animation, but very slow! First a little history of my upgrades with this phone.
My friend bought me Nexus S T-mobile version for US 6 mounts ago, and the phone was with Gingerbread 2.3.4. After reading many post from here, I decided to upgrade because I can't upgraded 2.3.6 OTA. After many hours I finally upgraded it to 2.3.6.
Then ICS came out, and again, I upgraded to 4.0.3. Then, a few weeks ago, I got the 4.0.4 OTA notification. Happily I taped yes. And then before two days ago, my phone just died. I don't know how.
I have 115 installed application, no music inside, no ROOT - just pure stock. I was in my college room and I left my phone on the desk right in front of me and after few minutes when I looked at the phone, the Google logo was there. I didn't give the phone to anyone to picks or anything. When I get home, I turn the phone on and still the Google logo just was there doing nothing and like I said before, after unknown minutes the phone boots in with very slow animation of the ICS software. I decided to install Clockwork Mod recovery 5.0.2.0 and root the phone. After reading many tutorials I installed CWM recovery successfully. Then I tried to downgrade to 2.3.4 and successfully I did that to.
Now after doing all this things to this phone, after so many hours in pain, the phone is nothing like one week ago. The booting is very slow, the animation is veryyy slow, and I don't know what to do anymore... I think this is hardware problem.
Please help me solving this problem, I really expect someone here to know what is the problem and will help me in anyway. I'm desperate, and I don't know what to write here to tell you how desperate and sad I am...
Thank you in advance.
p.s. sorry for any grammar mistakes.

http://forum.xda-developers.com/showthread.php?t=1572307&highlight=factory+images

yeah, definitely flash the factory images, you'll have to reflash cwm after though

Do you reboot that often... that this is a problem?
I don't know how much time mine takes to boot... I don't remember the last time I've rebooted it ...
That's why changing boot animations, for me, is stupid... you only get to see them once in 6 months(worst case scenario)?!

muldy said:
Do you reboot that often... that this is a problem?
I don't know how much time mine takes to boot... I don't remember the last time I've rebooted it ...
That's why changing boot animations, for me, is stupid... you only get to see them once in 6 months(worst case scenario)?!
Click to expand...
Click to collapse
not if youre a crackflasher(flash stuff often). i see my boot animation 5+ times daily, if not much more

Yeah.. I forgot that...
When I had the Htc Magic, I used to flash it a LOT
I like Stock, the auto-updates...

dewaffelhaus8 said:
yeah, definitely flash the factory images, you'll have to reflash cwm after though
Click to expand...
Click to collapse
I flash with the official images from here and I reflashed cwm.
muldy said:
Do you reboot that often... that this is a problem?
I don't know how much time mine takes to boot... I don't remember the last time I've rebooted it ...
That's why changing boot animations, for me, is stupid... you only get to see them once in 6 months(worst case scenario)?!
Click to expand...
Click to collapse
I don't reboot that often, my phone itself reboots... I need to fix that problem, the slow booting, restarting, slow software... I need to know is it a hardware problem or software, because I did everything related to software problems...

[Q] 4ext Stuck at "Installing update..."

Hello, I was reflashing a ROM (Sultan's CM10.2 w/ PMEM) but it seems to be stuck on Installing update...
It's been going for about 30 minutes now, much longer than the other times I've flashed it.
My question is, since it clearly isn't going anywhere, is it safe to remove the battery to start over again? I don't want to brick it.
(Not sure what went wrong, I think my SD card's going bad. I've flashed a few roms before successfully including this one, and I'm S-OFF'd and rooted already)

GoodOlTarvis said:
Hello, I was reflashing a ROM (Sultan's CM10.2 w/ PMEM) but it seems to be stuck on Installing update...
It's been going for about 30 minutes now, much longer than the other times I've flashed it.
My question is, since it clearly isn't going anywhere, is it safe to remove the battery to start over again? I don't want to brick it.
(Not sure what went wrong, I think my SD card's going bad. I've flashed a few roms before successfully including this one, and I'm S-OFF'd and rooted already)
Click to expand...
Click to collapse
HI
Greetings
i assume you have made a nandroid backup as if somthing goes wrong thats the thing which will help you
secondly you can try again just remove the battery and try againg
do a clean installation

Alright then. I took out the battery and reflashed it and nothing bad happened.
Thanks.

[KERNEL] Stock Modded Kernel for k2_u/k2_ul/k2_plc_cl [15/04/2014]

Hi people,
here is stock kernel extracted from One SV k2_u/k2_ul/k2_plc_cl version but with modded ramdisk.
I put this thread into general section but as soon as sources are out this will be moved into Original Development section and it will be replaced by my new kernel.
Features:
- Unsecured kernel
- init.d support
- Persistent ADB enabled
Instructions:
- Run "fastboot flash boot boot.img" command.
- Reboot & Enjoy!
DOWNLOAD for k2_u
DOWNLOAD for k2_ul
DOWNLOAD for k2_plc_cl
Make a nandroid backup first!
Credits:
- old.splatterhand
- eduardog131 for stock k2_plc_cl kernel
Enjoy!
xpirt

Will this help for a 4.2.2 rom?

GtrCraft said:
Will this help for a 4.2.2 rom?
Click to expand...
Click to collapse
Sorry this should be on One SV general section and I reported but anyone moved yet. @Ghost
It's stock kernel for One SV btw.
xpirt

Hi,
Can you mod k2ul version kernel?

@xpirt
Would you be willing to make a tutorial on here as to how you did this, the requirements needed to accomplish it, and what to check for, as well as the changes which must be made for such a modification? I am asking this so many will learn and as well take the idea and possibly grow from it by coming up with even better ideas in the future. Without the knowledge or know how then this will only keep people in the dark and nobody wins from this. You don't have to make a tutorial, but if you were to do so it would be very much appreciated friend.
Sent from my C525c using XDA Premium 4 mobile app

If someone gives me stock k2_ul kernel I can mod it as well.
@Modding.MyMind I modded it with cygwin kitchen, you can unpack any kernel and edit its ramdisk. The file modded is default.prop.
xpirt

Added k2_ul version! @bataya
xpirt

@xpirt
I know you have the mod, but what about write protection for this kernel for those who are S-On?
Sent from my C525c using Tapatalk

Modding.MyMind said:
@xpirt
I know you have the mod, but what about write protection for this kernel for those who are S-On?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I made the module for now.. a stock kernel with write protection disabled will come with my custom kernel too one day, but now I'm busy with something else..
xpirt

xpirt said:
I made the module for now.. a stock kernel with write protection disabled will come with my custom kernel too one day, but now I'm busy with something else..
xpirt
Click to expand...
Click to collapse
No worries man. Handle your priorities .
Sent from my C525c using Tapatalk

Added modded k2_plc_cl kernel, thx to @eduardog131 for stock kernel.
xpirt

Will this let people use rom toolbox to change the notification icons like wifi icon cell signal icon and so forth?

SnakeFist2005 said:
Will this let people use rom toolbox to change the notification icons like wifi icon cell signal icon and so forth?
Click to expand...
Click to collapse
Not this, this is the kernel. To use toolbox a deodexed system + root/busybox should be enough.
xpirt

Experiment went awry!!!! Ended with a nice surprise!!!
So this is a an interesting story. I have tried many ways to finish flashing the OTA's after I have implemented the RUU. None seemed to work. I was missing a key step pull out the firmware.:silly: duh. Im still a very real noob here and learning on my own. And I was on github the other day browsing and searching and there was a put an uncompiled SE supported string for a kernel of our dear phone the PLC. So grabbed and immediatly started browsing reading and learning placing things here and their....I learn hands on, not from stories or guides. Well things quickly went wrong like many of you reading this are thinking and I wound up with a big paper weight hahahaha. No biggie I got 4 different nandroids that I have compiled and the RUU right I am good.
NO SO FAST nandroids wont flash something about error 23 or 24. RUU I ran 4 times deleted re downloaded and ran again nothing. Again I am still not in panic mode I have enough hardware on my computer to makeshift something to get the RUU to download. I dont know how this happened somehow in the midst of my scramble to get my phone back I had put in an old hboot radio and ics boot img. See my phone has never run ics before. So now I was staring at drivers failing cause their is no OS RUU isnt working nandroids wont work. My phone is down and my computer when I take it to work has no internet. I went through my archives and found the data for the binaries and the data for an ics rom but it was bare bones but heck I had no other choice. So I through the old firmware mixed with bits of the newer kernel.
I booted from recovery with adb to oem-78 which I believe is the updater portion of RUU. I ran the the firmware from their I first relocked bootloader before I did this. I did not take the first time/ flush the zip and run it again took like a charm. I then went back to fastboot flashed TWRP 2.6 instead of my normal 2.7 just cause I wanted to booted into recovery no problem. While in recovery I flashed the ICS stock rom like the firmware did not take. No worries ran it again and worked the second time. then wiped cache and dalvic flashed superSU 2.0.2 which was bought from play store and donated for zip thanks btw. and busybox X. booted into bootloader rebooted bootloader like a dozen times and flashed the ICS boot img. twice seems like the theme hear.
K bear with me I know I am long winded. Tried booting into the system after another dozen times rebooting bootloader. finally gave up went back to recovery reflashed ICS rom only once and then did busybox and SU another time for good measure. I did an avance wipe of dalvic and cache this time. booted straight to system and put the phone down came backe 20 min later it was working I played around it was glitch bad but working. I let it be for another 30 min. Came back rebooted a couple times and went to recovery to instantly backup as all mine where now worthless. When I got home I noticed it wouldnt receive wifi signal after playing around I downloaded the latest OTA for the 4.1.2 JB and the 4.5 sense update. Pulled the firmware flashed that after replacing the HBOOT with an old version and then found my other SD card and pulled a bunch of saved stuff off and found a stock JB 4.5 sense rom. flashed like above steps basically to the amount of reboots. lol. I finally got it to boot and within the hour I am running a smooth JB 4.1.2 sense 4+ OS thats what android tuner says my Hboot however says
Unlocked
K2_PLC_CL PVT SHIP S-OFF RL
CID 11111111
HBOOT 1.01.0000< oldest one i've seen lol.
Radio 1.12.00.0208
OpenDSP- v 10.2.0268.0401
eMMC-boot
Feb 8 2013, 16: 29: 40:-1
As u see no line for OS and well no os and no data associated with eMMC just the boot. Everything seems to run way way way smoother now thought even before I started messing around. No lag perfect signal. My call problems gone only thing is my batt percent and my mms but those are pre existing problems I am working on.
My kernel says I am the 3.4 variation. On my phone and in all my apps. Except rom tool box it says I am 3.2
I wrote this hopefully a true dev can take what I did and come up with something amazing that can be used across the board of the ONE SV users.Thanks oh some how my toggle switches all turned orange in bootloader and all my highlited things in the rom turned green dont know how that happened either. :fingers-crossed:

Fant0m3 said:
So this is a an interesting story. I have tried many ways to finish flashing the OTA's after I have implemented the RUU. None seemed to work. I was missing a key step pull out the firmware.:silly: duh. Im still a very real noob here and learning on my own. And I was on github the other day browsing and searching and there was a put an uncompiled SE supported string for a kernel of our dear phone the PLC. So grabbed and immediatly started browsing reading and learning placing things here and their....I learn hands on, not from stories or guides. Well things quickly went wrong like many of you reading this are thinking and I wound up with a big paper weight hahahaha. No biggie I got 4 different nandroids that I have compiled and the RUU right I am good.
NO SO FAST nandroids wont flash something about error 23 or 24. RUU I ran 4 times deleted re downloaded and ran again nothing. Again I am still not in panic mode I have enough hardware on my computer to makeshift something to get the RUU to download. I dont know how this happened somehow in the midst of my scramble to get my phone back I had put in an old hboot radio and ics boot img. See my phone has never run ics before. So now I was staring at drivers failing cause their is no OS RUU isnt working nandroids wont work. My phone is down and my computer when I take it to work has no internet. I went through my archives and found the data for the binaries and the data for an ics rom but it was bare bones but heck I had no other choice. So I through the old firmware mixed with bits of the newer kernel.
I booted from recovery with adb to oem-78 which I believe is the updater portion of RUU. I ran the the firmware from their I first relocked bootloader before I did this. I did not take the first time/ flush the zip and run it again took like a charm. I then went back to fastboot flashed TWRP 2.6 instead of my normal 2.7 just cause I wanted to booted into recovery no problem. While in recovery I flashed the ICS stock rom like the firmware did not take. No worries ran it again and worked the second time. then wiped cache and dalvic flashed superSU 2.0.2 which was bought from play store and donated for zip thanks btw. and busybox X. booted into bootloader rebooted bootloader like a dozen times and flashed the ICS boot img. twice seems like the theme hear.
K bear with me I know I am long winded. Tried booting into the system after another dozen times rebooting bootloader. finally gave up went back to recovery reflashed ICS rom only once and then did busybox and SU another time for good measure. I did an avance wipe of dalvic and cache this time. booted straight to system and put the phone down came backe 20 min later it was working I played around it was glitch bad but working. I let it be for another 30 min. Came back rebooted a couple times and went to recovery to instantly backup as all mine where now worthless. When I got home I noticed it wouldnt receive wifi signal after playing around I downloaded the latest OTA for the 4.1.2 JB and the 4.5 sense update. Pulled the firmware flashed that after replacing the HBOOT with an old version and then found my other SD card and pulled a bunch of saved stuff off and found a stock JB 4.5 sense rom. flashed like above steps basically to the amount of reboots. lol. I finally got it to boot and within the hour I am running a smooth JB 4.1.2 sense 4+ OS thats what android tuner says my Hboot however says
As u see no line for OS and well no os and no data associated with eMMC just the boot. Everything seems to run way way way smoother now thought even before I started messing around. No lag perfect signal. My call problems gone only thing is my batt percent and my mms but those are pre existing problems I am working on.
My kernel says I am the 3.4 variation. On my phone and in all my apps. Except rom tool box it says I am 3.2
I wrote this hopefully a true dev can take what I did and come up with something amazing that can be used across the board of the ONE SV users.Thanks oh some how my toggle switches all turned orange in bootloader and all my highlited things in the rom turned green dont know how that happened either. :fingers-crossed:
Click to expand...
Click to collapse
so are you saying that you flashed this kernel?
what exactly do you want a dev to do? i think, by reading what you said, that what you did was, try to compile a kernel with bits and pieces, and when you flashed it, it didnt work? so you tried to restore a backup that you also 'compiled'(?), which failed as well. you then flashed an older hboot which allowed your update to take.... the downgrade to update has stumped lots, including me. its basically the process of manual updating. these phones are all different because the partitions are in different locations in the device. and certain varients have no sim card slot. the radios are running "different channels" etc...
sorry for continuing off topic..

Thanks for the kernel and all your work

[Q] Reboots 30 into loading ROM

From the beginning.
Unlocked
EVITA PVT SHIP S-ON RL
HBoot 1.14.002
Radio 0.19as.32.09.11_2
OpenDSP v29.1.0.45.0622
eMMC-boot
June 11 2012, 14:36:28
Click to expand...
Click to collapse
I was running a ViperRom my camera light was staying on, I tried everything to get it to turn off. I decided it been a few month it was time to get a new ROM anyways. I tried installing Gummy Nightly's was having problem with the install read about getting a different version of TWRP so I updated to 2.6.3.0 I believe I had 2.1.0.0. Gummy still won't work, so I changed plans and want for the Viper XL Rom 4.2.0 this led to a bootloop not getting past the Viper splash screen. I thought I might as well just with one of my backup. So, i wiped and loaded a backup. This is the problem, it will load up the ROM for about 30 seconds before the icon all appear it will reboot. I've now been working on this for 2 days. I've went through each post and tried the advice each person was given, I've tried to Flash a different Rom, the Viper Rom I had when I had the Camera Light Issue, each time I get about 30 second into the Rom Load and reboot. (One of the ROMs would let me access the SDCARD0 but found a work around that.) I've let the phone sit charged for 2 hours looping. I've turn it off and let it sit charging. The next thing I'm going to try to to downgrade the TWRP. If anyone can give me some advice, something new and different to try that would be great. Thanks!
Cheers
xDrFirefly

talked to one of my buddy and said the downgrade would be pointless so, i'm trying to flash a stock rom at the moment.

When you changed to TWRP 2.6.3.0 was it the official version or the unofficial modified version?
Sent from my Evita

Recovery: Custom TWRP 2.6.3.0 w/selinux support

And what errors did it give you when trying to install Gummy?
Sent from my Evita

The install failed. I tried it multi times, and even d/l it again to see if that would make a difference. Nope.
Here is what i've done so far. I factory reset everything. Found a stock rom flashed it on. For the two hours I used it seemed to work fine. I then flashed CleanRom everytime I would open Ti Backup the phone would reboot. I flashed another ROM, was getting the signal drop snagged the Beastmode Kernel it keep failing everytime I tried to flash it. Factory Wiped EVERYTHING again. Flashed the Stock, then Flashed ViperXL (then went to bed) in the morning still had signal bars, so far had two reboots, one when I was uninstalling apps using Manage apps feature, and another time when I was in the Venom HUB app. But at the moment the phone seems to be working. The battery life is ****. In the 30 mins I've had the phone unplug i've down to 89% and all I did was delete a few apps, and move some stuff to the home screens. Hopefully it will get better with time.
Side Note: To anyone reading this. I got the AT&T HTC XL preorder. I doubt I will ever do that again. In all the years I've been flashing and messing with phone. ( My first phone I messed with was a Sidekick ) I've never had so much trouble as I had with this phone. ( HTC Tilt, Fuze and Tilt 2 never had this kinda problem ) a friend of mine whom waited a year to get the XL has never had any of the problem I've had. Just my thoughts. Thanks and I hope I won't have to be asking anymore question.
When, I have more time and such I'm going to try to flash Gummy. If I get the same error message for it or anything else I will post it here.
Cheers
-Dr FF

I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita

You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.

jacobas92 said:
You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.
Click to expand...
Click to collapse
I will try this. Sounds like a very logical plan.

timmaaa said:
I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita
Click to expand...
Click to collapse
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".

xdrfirefly said:
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".
Click to expand...
Click to collapse
Computer always says no for a reason. You need the right recovery installed to flash KitKat ROMs, you also need to check the md5 of every ROM you download before you flash it. What I'm saying is there's no reason Gummy wouldn't install if you have done everything correctly.