yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] bertans:
Hi Adam,

thank you... you saved my phone and all my data stored in! :cool:

I'm a Windows user so I installed Ubuntu "inside" Windows, I follow all the steps pressing the two volume buttons during resurrection (in order to activate the download mode), then I reboot in Windows where Odin did the rest. :eek:

Merry Christmas! :D
[Nexus S Android Development] Rafael Cadina:
I'm not with my phone in hands now, but I'll check this solution when i get home. Just bricked my phone yesterday due to an update from gingerbread to ics. I can't see anything on my screen, even the keys are not working. I hope your solution does the trick. Thanks in advance.
[Nexus S Android Development] NO_ob:
Been trying this on a Nexus S from ebay i presumed was dead but it only seems to boot to the downloading screen from the galaxy s mode, I am unable to flash with heimdall or odin as it cant read the pit and I cant find a pit file anywhere
[Nexus S Android Development] szk5230:
good news ！ although my nexus s isn‘t a bricked

great job ！
[Nexus S Android Development] vbljj:
Hi guys, I need help! I tried this guide, but after I press Download Mode Button, it lights Home and Search buttons, but then when I do the combo for fastboot, these buttons lights down and nothing else. Please help!!!
[Nexus S Android Development] AdamOutler:
Are you using the S5PC110 (Nexus S) resurrector? There's several of them.

Anyways, you don't need to hold a key combo with UnBrickable Resurrector R40 and higher.
[Nexus S Android Development] vbljj:
Yes! So after it lights home and search buttons, what have I to do?

Sorry for bad english
[Nexus S Android Development] cyberalex88:
Use odin/heimdall to restore your device while in download mode if you're not able to use fastboot.
[Nexus S Android Development] vbljj:
You have pm :)

---------- Post added at 03:34 PM ---------- Previous post was at 03:19 PM ----------

I tried with odin but it didn't detect my nexus. It is still with home and search softkeys on
[Nexus S Android Development] bertans:
1) remove the battery;

2) insert the battery;

3) connect the phone (the tool must be already running when you plug your Nexus);

4) press the volume key (in the middle) and keep it pressed;

5) run the tool;

6) use odin (or anything you prefer).

ps. you can disconnect your phone, it will remain in download mode ;)
[Nexus S Android Development] AdamOutler:
Damn tinypic.com lost the image. I'll repost it tonight. If someone can get a screenshot of the resurrector in the initial state, that would be great.
[Nexus S Android Development] vbljj:
Sono in italiano, mi scuso se parlo in italiano con tutti gli altri, allora:

io su ubuntu ho usato il tool consigliato qui, si accendono i 2 led di home e search. Dopodiché io riavvio in windows, senza staccare il cavo, però se apro odin, non vede nulla. Cosa sbaglio?

I apologize for speaking in italian, but I'm in emergency
[Nexus S Android Development] bertans:
Follow the white rabbit... with a dictionary in your left hand! ;)

You have to put your phone in "download mode" and you achieve this status with row 4... :)

Keep us informed!
[Nexus S Android Development] Rafael Cadina:
I really suck at ubuntu... So far i couldn't install java and run ressurector because i can't even connect to wifi.... Can somebody teach me how to do id?
[Nexus S Android Development] ha9981:
Why are people bricking? How can I avoid doing the same?

I am on I9020T running ICS ROM by Koush. I want to update to more stable official release of ICS. Am I going to suffer the same fate? There is a lack of clear instructions on how to do it. Or maybe I can't find them? I asked around and nobody seems to clarify the step-by-step process.

here was my question:

http://xdaforums.com/showpost.php?p=20461823&postcount=57
[Nexus S Android Development] Rafael Cadina:
Can anybody post the java installer and tell me what to do next?

Thanks in advance

(Ubuntu already installed)
[Nexus S Android Development] vbljj:
Guys, I love you! I did it!!! Thank you very much! If one day you come to Turin in Italy, let me know, I'll offer you a beer :)
[Nexus S Android Development] AndroidUser00110001:
$ sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"

$ sudo apt-get update

$ sudo apt-get install sun-java6-jdk

Dont use the $...that just shows what to type at command prompt.

---------- Post added at 02:51 PM ---------- Previous post was at 02:49 PM ----------

I bricked my phone by developing my ROM. I mistakenly had the bootloader.img file write to my boot partition and the rest was history...

:)
[Nexus S Android Development] Rafael Cadina:
Ok... but i don't have access to the internet! Apt-get probably won't work...

What should i do then?
[Nexus S Android Development] AdamOutler:
You can do it with the stock ubuntu and no internet access. Just follow the directions in the first post. You don't need to do anything else

Also, I just restored the picture in the first post.
[Nexus S Android Development] Rafael Cadina:
Hi guys,

I've just downloaded java from http://javadl.sun.com/webapps/download/AutoDL?BundleId=58117 [for ubuntu 64-bits] and installed it on my pc via terminal with the following lines

>> cd directory of the file

>> chmod 755 filename.bin

>> sudo ./filename.bin

The installation was succesful. Even though, when i try to pick java from the app list to open jar files it doesn't show. I've also tried to run the .jar file by the terminal typing java -jar filename.jar but nothing happens...

Any help?
[Nexus S Android Development] Abaddon:
woot unbrickable mod nice! :)
[Nexus S Android Development] AdamOutler:
Not mod. Its only resurrection. I need a device to locate the mod. This is a lucky brick mode which allows similar functionality in failover condition.
[Nexus S Android Development] Rafael Cadina:
Finally unbricked my Nexus S!

Thank you very much AdamOutler... I'll give you some bucks for that!

Just some hints for those who are trying to unbrick Nexus S:

- Follow AdamOutler instructions

- After getting into bootloader via Resurrector reboot

- Choose Windows and don't disconnect Nexus S from USB

- After initializing Windows run fastboot via cmd

- download a rom like stock 2.3.6

- open zip and extract bootloader and boot / also download clockworkmod recovery

- put the files in tools folder

- run fastboot flash bootloader bootloader.img

- run fastboot flash boot boot.img

- run fastboot flash recovery nameofrecovery.img

- Attention: The order is very important! If you try to flash boot or recovery first you won't be able to fix the problem

- After choose recovery and flash the rom you like!

Any help pm me!
[Nexus S Android Development] AdamOutler:
I've been getting PMs asking for an explanation of what this is.. Is it BOOT, is it HBOOT??

The answer:

It's neither. The UnBrickable Resurrector leverages the power of the Hummingbird Interceptor Bootloader created by Team HummingMod's Rebellos. Rebellos has a very good understanding of the Hummingbird processor and its configurations. The way this bootloader works is injecting code directly into the processor

Here is a very high level overview:

processor tries to boot and fails.

Processor goes into a IROM failover mode. Normally, with UnBrickable Mod, we modify the processor's input to force this mode, it's not normally a failover. The bricks we are handling here are "lucky bricks"

Processor executes IROM USB download routine and asks for secure code then waits for the computer to respond

Computer sends HIBL and memory location to load HIBL.

HIBL is loaded into memory where it performs secure authentication with the processor

HIBL performs several diagnostic checks and displays UART output (if you're monitoring this)

HIBL makes decisions on how to initialize the processor based on charactoristics seen in the device registers

HIBL initializes the processor and much larger DRAM (System RAM)

HIBL calls back the IROM code used to download the HIBL, but this time it does not call back the security routines.

Processor executes IROM USB download routine but does not perform security checks

Computer sends modified SBL and a memory location.

SBL is loaded into the Memory location specified and executed

The SBL handles the vast majority of platform specific initialization... screen, storage and other things.

Modified SBL forces the device into Fastboot mode or allows Download Mode

System appears to be booted normally, however, if you unplug USB, the system will turn off immediately.

Hope that clears things up. It's not a kernel.
[Nexus S Android Development] ilnanny:
thanks for sharing

Inviato dal mio Nexus S I9023 usando Xda Premium.
[Nexus S Android Development] NYCguy2020:
Hi,will this work on the Sensation??! I have bricked mine after flashing a firmware zip.

Thanks!
[Nexus S Android Development] AdamOutler:
No. That's a qualcrap processor I think.
[Nexus S Android Development] bdpyo:
Ill ship you my NS for further testing and research, all you have to do is send it back with the alternative white housing w/unbrickable mod and in working order. :)
[Nexus S Android Development] mrhaley30705:
Will this revision also work on a Captivate, or does it need a different revision? Just curious, as I like to keep all of my "OH CRAP" apps up to date.

OH CRAP app= app defined as one that, while in the course of modding, saves your device from being flung against a wall in frustration.
[Nexus S Android Development] AdamOutler:
Yes. Captivate is the default option. I've expanded functionality.
[Nexus S Android Development] mrhaley30705:
OK, Thanks Adam. I've already changed the link in my Sig link thread.
[Nexus S Android Development] HiGGzZ:
just wanna say Ty to Adam for his tool... did brick my nexus S on last dec,18 (after flashing ICS) and unbricked it the day after thanks to ur tool.
[Nexus S Android Development] ericmky:
Device no Connected

Hi

I tried to use this tool, but i get this message

: «pixmap»,(gksudo:324): Gtk-WARNING **: Imposible encontrar el motor de temas en la ruta al _modulo: «pixmap»,failed to find device

Anyone can help me.

Thanks
[Nexus S Android Development] climbingbulli:
Hello,

@ericmky You have to mount your device (USB)

I've also one problem with your tool Adam.

After doing all your instructions, I got this error:

S3C64XX Detected!
=> found device: bus 001, dev 003
=> loaded 24576 bytes from /tmp/alexHeimdallOneClickD8D142ED/UnBrickPack/HIBL.bin
=> Downloading 24586 bytes to 0xd0020000
=> Data checksum d8dc
=> usb_bulk_write() returned 0
failed to write 24586 bytes

What can I do?

CU,

climbingbulli
[Nexus S Android Development] AdamOutler:
It looks like your device is not in the proper state, try removing the battery and trying again.
[Nexus S Android Development] cyberalex88:
I had similar errors with ubuntu virtualized on vmware fusion. Solved using another linux box.
[Nexus S Android Development] AdamOutler:
Yeah... you probly wont get it to work by virtualizing Linux. Windows is a crappy base. Linux is way more solid. You must boot Linux.
[Nexus S Android Development] bdpyo:
Bump
[Nexus S Android Development] FirmShark:
Just used this method to unbrick my Nexus S. After a **** ton of hassle (half a day) I eventually got my netbook dual-booting Win/Ubuntu and then having to mess about loads to get JRE running on Ubuntu.

After that was setup, the unbrick software worked perfect and straight away! Thanks so much!
[Nexus S Android Development] SaHiLzZ:
I am getting a device not found in the resurrector-rev 40.

Installed Ubuntu, not running from within windows.

Help?

Output of the terminal after plugging in the phone with both volume buttons connected

Also I get the following in resurrector:

SBL Injection Failure

(gksudo:4099): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",(gksudo:4099): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",(gksudo:4099): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",(gksudo:4099): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",failed to find device
[Nexus S Android Development] AdamOutler:
Dont hold the volume buttons. Follow the directions. Remove the battery. Replace the battery. Connect the device
[Nexus S Android Development] SaHiLzZ:
Should have said it earlier, I tried it without pressing anything, with pressing both buttons, and with pressing vol up + power to presumbly get into fastboot mode once finished.

Same response, with the above mentioned error.

I should also say that I don't know the circumstances of how this Nexus got bricked. It may or may not have been during the update process, but currently nothing lights up or vibrates when attempting to power it on.

Am I expecting a solution when it may not apply to this phone?
[Nexus S Android Development] qweasdfzxc:
Hi, thanks to this resurrection tool I was able to access the bootloader again. Now I don't know what I'm supposed to do. Should I use fastboot to flash a new bootloader.img? Or what else?

EDIT: I tried to flash a recovery image but when I select recovery from the bootloader the screen goes off and I have to go through the whole resurrection procedure again to access the bootloader.

EDIT 2: Managed to access the recovery using "fastboot boot recovery.img". Then I used cwm to restore a backup but when I reboot the phone it still goes off and I always need to use the unbrickable tool to get it working. I'm really lost right know, I don't know what to do.

EDIT 3: Finally my phone turned on (I manually flashed the boot.img inside my backup using fastboot) but if I turn it off again it needs the unbrickable tool to go back to life. What am I missing?

EDIT 4: My phone is alive! I decided to make a nice step-by-step guide of what I did in order to have my phone back, you can find it here.
[Nexus S Android Development] AdamOutler:
Yeah. If you're not seeing it identify on the resurrector, you're not going to get anything. It will identify itself as S5PC110 debug.
[Nexus S Android Development] johnkor:
I wonder does it work for SII ?
[Nexus S Android Development] AdamOutler:
no. not yet. and it will likely never work on the closed-hardware Skyrocket or the T-Mobile S2. I'm working on support for the i9100 and i777.
[Nexus S Android Development] GrandMstrBud:
Is mine bricked when I can still use the phone it's just when plugging it in I get nothing. I can once in a while get into downloader mode or fastboot and was able to do that and get CWM installed but this doesn't seem to work on a VM machine with Ubuntu. It finds it but does nothing. Just curious if this is what's been happening.
[Nexus S Android Development] HiTjTe:
HELP!!!

Friday my NS started to act weird, google maps and navigation started to behave awkward blurting out weird noises instead of navigation instructions. My NS became more and more instable with fc's and reboots. This morning I got random android processes fcing (android.process and android keyboard) and bootloops when rebooting. I tried restoring my back ups, which eventually worked but with the same processes fc'ing all the time. I then wipe everything but the sdcard and tried to reinstall the cybergr rom v8. Now the only thing my phone does is showing the screen with google logo, unlocked sign and a progress bar which finishes and then stays "full". My feeling says that something corrupted my sdcard, I didn't see any magnets but can't be sure. No recovery, no bootloader, no rom . Can anybody help or give me some direction to try and solve this, can I try for example the unbrickable linux tool in this android development section?

Any help will be highly appreciated...
[Nexus S Android Development] 3DDude:
So what i can do:

Get into android 4.0.3 stock (no root)

See the menu with reboot bootloader, reboot, recovery and power off.

Unfortunately --> Recovery -> not working :(

so i tried the tool and i get :

Interceptor Injection Complete. Injecting modified SBL

SMDK42XX,S3C64XX USB Download Tool

Version 0.20 (c) 2004,2005,2006 Ben Dooks <ben-linux@fluff.org>

SBL Injection Failure

Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",failed to find device

Anybody an idea how to resolve this?

I want my recovery back :P

Nvm used fastboot recovery to flash clockworkmod

I fixed the error by installing a theme package btw: but stilll wouldnt work with the recovery thing.. weird still :(
[Nexus S Android Development] coolfranz:
So your device is NOT bricked!

Your phone is DEFINITELY not bricked!!!

I assume that you have a i9023?

Then boot into recovery and illuminate your screen with a bright (led) flashlight then you should see the recovery.
[Nexus S Android Development] evolite:
There is a problem here. Linux is not ubuntu.
[Nexus S Android Development] AdamOutler:
Ok, so you want to be picky.. Ubuntu is the most supported Linux variant. over 50% of Linux developers use Ubuntu. You can make any version of Linux work with this... should i retitle it Xorg/Java tool for Bricked Nexus? Don't complain about rediculous stuff. It's a Linux tool and I'm telling people to use Ubuntu.

I'll have the UnBrickable mod up for GSM Nexus S in a couple of days. CDMA will never work but GSM is good to go..

If anyone knows of a complete fastboot package for i9020t, I could use it.
[Nexus S Android Development] lilredstang:
Is there a youtube video out how to unbrick?
[Nexus S Android Development] Androyed:
Does it HAVE to be Ubuntu? Because my computer (probably) can't run Ubuntu. There might be a solution but if I can use another version of Linux I would prefer that.

Also, is dual boot good enough, if I still keep my Nexus S in the USB port? Doesn't it lose it's power when you reboot?
[Nexus S Android Development] Superboy58:
My Nexus S looks to be bricked but I can access fastboot and download mod :confused:

The screen on the phone is always black and in fastboot, back and menu keys are lighted.

In download mod, lighted keys are home and search.

I can't see anything on my screen, no google logo, no fastboot android picture, and again nothing on download mod.

I can flash throught fastboot and odin but it does not change anything.

Also, there is no vibration during boot.

The screen is OK because I test it on an other Nexus S and it worked.

Is the memory/screen controller damaged? :(

Any idea? :)
[Nexus S Android Development] guille31794:
My NS doesn't turn on after a flash with odin, and now i try to resurrect it with the tool for linux, but phone is not detected.

Its bricked like a psp. Totally dead, only a little flash on screen when a i put de battery with usb conected.

Some idea? Maybe could be java? I used v6.20 instead 6.31

Greetings.
[Nexus S Android Development] Superboy58:
Start by that to be able to detect your phone using UnbrickableMod: http://xdaforums.com/showthread.php?t=1566475
[Nexus S Android Development] guille31794:
My phone is a i9023. It's the same work? And I haven`t enough experience and tools to do it :(
[Nexus S Android Development] Superboy58:
Same process for i9023, I've got thesame as you and it worked for me... without soldering iron (shame to me): I've used a little tweezers to pull of the resistor and to connect the two "locations" on the motherboard, I've taped a very tiny wire...

:D

The most incredible is that the resurrector detected my phone as S5PC110 and the ressurection worked :cool:
[Nexus S Android Development] AdamOutler:
be careful yanking a resistor off the board. Generally the solder is stronger than the pad's adherance to the board. If you pull up the pad with it, you're screwed.
[Nexus S Android Development] Superboy58:
Thanks for the tip Adam, it worked without problem for me but it would be useful later... :)

And if you could take a look at your PMs it would be great :o
[Nexus S Android Development] zaherrrr:
but i have on error

samsung is not connected?

men i instal the driver can u help me?
[Nexus S Android Development] FirmShark:
Having to do this again to my Nexus S. I am not sure what is going wrong this time but the program hangs for hours on end at the "injecting modified sbl" stage. Tried re-connecting at least 10 times and still having the same issue. Also tried some different things and if I press the download mode button again when it hangs, I get informed that the "device or resource is busy" error.

Has anyone had the same issue as this? Any solutions?

This is what the program is exactly showing when I try it.

Interceptor Injection Complete. Injecting modified SBL

SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <ben-linux@fluff.org>

S3C64XX Detected!
=> found device: bus 001, dev 006
=> loaded 1310720 bytes from /tmp/TempHeimdallOneClickF764C8BF/UnBrickPack/nexus_sbl.bin
SBL Injection Failure
usb_claim_interface: Device or resource busy
[Nexus S Android Development] AdamOutler:
that's odd. Try rebooting and unplug everything then try again. Make sure you entered your password correctly as well.
[Nexus S Android Development] FirmShark:
Just tried starting afresh and seeing if it would work but still nothing is happening. It is almost as if it is failing to write the sbl. Tried different cables and usb ports as well to check to see of any of them were being weird but still nothing :(
[Nexus S Android Development] FirmShark:
Does anyone have any idea how to fix this problem that I'm having?
[Nexus S Android Development] ali.md:
is this tools can help me ?

http://xdaforums.com/showthread.php?t=1555467

i look at my phone every day on my desk and ... :crying:

my phone turn back on after full wipe but storage freezed

for example when i copy file/ delete/ format / ... and turn usb storage off and on again (without restart) everything backed !!!!

storage locked and freezed or corrupted !
[Nexus S Android Development] djdeepblue:
Help please...

My screen doesn't show up anything, and i can't even enter fastboot mode.

I was on a JB rom, did the "reboot to recovery" option, but i didn't want to wait so i just did a battery pull. When i put the battery back in, the phone is dead. Nothing works...

I've tried this tool, but it doesn't detect my phone... maybe because i don't have that unbrickable hardware mod?

It doesn't make any sense... why did it died like this?
[Nexus S Android Development] FirmShark:
Another bump. Does anyone have a solution to this?
[Nexus S Android Development] e30andrew:
For anyone that believes their phone is bricked, I had a similar situation, so i figured id share what happened... maybe it will help someone.

about a month ago I was on a new CM9 rom, and I let my battery get all they way down to 0% and die. I didn't think it was a big deal, I'd just plug it in when i got home, and I did.

i plugged the phone in, and no response. No acknowledgement of a charger being connected, and It wouldn't turn on. So i let it sit for a bout 10 minutes, tried to power it on again, no dice. plugged my other phones in to make sure the USB cable wasnt shot, and it wasnt.

i let the phone sit on charge for another 30 minutes, then hit the power button, and still nothing.

After about 40 minutes of sitting on the charger, i finally pulled the battery, popped it back in, and hit the power button, and it finally powered up.

I've heard it described as the 'sleep of death' and that it happens on CM9/CM10 roms... just my experience.
[Nexus S Android Development] AdamOutler:
There is a hardware mod available but definitely try charging for an hour first.
[Nexus S Android Development] FirmShark:
Does anyone have a non modified sbl that I can try? Am I the only person who has had issues with injecting a modified sbl???
[Nexus S Android Development] AdamOutler:
Wrong thread.