Jump to content


Photo

08 Aug GRJ22 colour revert: Superboot - rooting the Nexus S

- - - - -

  • Please log in to reply
91 replies to this topic

#61
ectole

ectole

    Newbie

  • Members
  • Pip
  • 5 posts
  • Devices:HTC Desire
Well, my problem is that i applyed superboot 2.3.3 in a nexus s which had received the 2.3.4 ota update. Now, it won´t boot anymore. I have Clockworkmod installed but i just can´t upload anything to my phone cause i just can´t activate the usb debug mode since it won´t boot. My question is if there´s anything i can do to fix this or if i have to wait to 2.3.4 superboot and if that might solve this problem. Thank you all gays!

  • 0

#62
Mr.Clark

Mr.Clark

    Ninja

  • MoDaCo Gold
  • PipPipPipPip
  • 336 posts
  • Gender:Male
  • Location:UK
  • Devices:Nexus 4, Nexus 7 2013
If you can boot into Clockwork, you should be able to mount the SD card so that it can be seen by a computer. You can drop files onto that, then unmount it and the phone can see them again, so you can flash from them.

I can't remember the exact options as my phone has picked up a nasty habit of replacing CWM with the default recovery every chance it gets.

  • 0

#63
ectole

ectole

    Newbie

  • Members
  • Pip
  • 5 posts
  • Devices:HTC Desire

If you can boot into Clockwork, you should be able to mount the SD card so that it can be seen by a computer. You can drop files onto that, then unmount it and the phone can see them again, so you can flash from them.

I can't remember the exact options as my phone has picked up a nasty habit of replacing CWM with the default recovery every chance it gets.


thanks for answering!

On clockwork i can see Mounts and Storage Menu, from which it goes:

mount/sdcard as you said

When i hit it, the pc sounds like a new drive is coming but explorer won´t show it.

Am I doing something wrong?

by the way, my ns is GT-i9020T

  • 0

#64
Mr.Clark

Mr.Clark

    Ninja

  • MoDaCo Gold
  • PipPipPipPip
  • 336 posts
  • Gender:Male
  • Location:UK
  • Devices:Nexus 4, Nexus 7 2013
How long did you wait? Mine takes ages... try dismounting, then remounting too.

  • 0

#65
ectole

ectole

    Newbie

  • Members
  • Pip
  • 5 posts
  • Devices:HTC Desire

How long did you wait? Mine takes ages... try dismounting, then remounting too.


It worked! I just hit the option "mount usb drive" on clockwork mode and the computer was able to see the device, then i copied a backup image to clockwork/backup/ folder (i guess this is the right path) and restored it.

Thanks for your help, i really appreciate it!

  • 0

#66
Heintraag

Heintraag

    Regular

  • Members
  • PipPip
  • 67 posts
  • Devices:Google Nexus S
Does anyone have news on a superboot for the 2.3.4. GRJ22 Android version?

  • 0

#67
J.F.Gratton

J.F.Gratton

    Newbie

  • Members
  • Pip
  • 2 posts
  • Devices:Nexus S & Motorola XT-720
  • Twitter:@grattojf
Well, it seems that I've screwed up as well...

I'm coming from the iPhone world where jailbreaking a phone is quite easy. Android rooting seems to be, as well, but I guess I missed a few things.

Basically I'm on 2.3.4 and used superboot on it. The phone is now bricked and don't know how to factory reset it on 2.3.3 or 2.3.4. I don't care about losing data (well, it's already done with the fastboot oem unlock, anyway). I just need a working phone :-)

I read you people talking about GRJ22 and such. Where does that ID come from ?

Any help would be appreciated. It is said that one should learn from his errors. Boy, will I learn from this one ! :o

<EDIT:
I must correct myself: the phone is not bricked as I can get on fastboot/recovery. It just won't boot.
The phone was vanilla (gingerbread, unrooted, etc). From the fastboot, how can I revert it to either 2.3.3 or 2.3.4 ?
/EDIT>

<RE-EDIT:
Most if not all solutions offered required some custom recovery as CWM, which 1- should have been installed beforehand and 2- required root access, and since my problem started when I tried to root my NS, I figured I was stuck.

I went to my retailer, and managed with some fancy arguments to get a new phone free of charge :D
Case closed for now; I'll await the next update from Paul.

Well, I've learned something: the bootloader is quite important on NS. On iPhone I could use BL 3.6 or 4.9 without bothering. Here, each BL seems to be version-specific. I've learned that, so I'm not *the* ultimate newbie anymore :D
/EDIT>

Edited by J.F.Gratton, 09 June 2011 - 01:49 AM.

  • 0

#68
Provolino

Provolino

    Newbie

  • Members
  • Pip
  • 25 posts
The problem was you user Superboot for 2.3.3 on a device with 2.3.4 (we need an update from Paul about that).

Anyway, if you can power the phone in bootloader, you can still flash recovery using fastboot commands so don't worry next time ;)

  • 0

#69
J.F.Gratton

J.F.Gratton

    Newbie

  • Members
  • Pip
  • 2 posts
  • Devices:Nexus S & Motorola XT-720
  • Twitter:@grattojf

The problem was you user Superboot for 2.3.3 on a device with 2.3.4 (we need an update from Paul about that).

Anyway, if you can power the phone in bootloader, you can still flash recovery using fastboot commands so don't worry next time ;)


Ho... see how new I'm to Android. I wasn't aware that I could use fastboot commands to recover from a borked bootloader. I figured it was because Superboot wasn't written for GRJ22 that I got into that predicament. Anyway, I got a new phone now, I for sure won't make the same -dumb- mistake twice :-)

-- Jeff

  • 0

#70
rtimms

rtimms

    Newbie

  • Members
  • Pip
  • 9 posts
  • Devices:Asus epad tf101
Ok looking at my Nexus S its GRJ22

Is there one i can use above

Thanks

  • 0

#71
Chamb'

Chamb'

    Newbie

  • Members
  • Pip
  • 2 posts

  • 0

#72
gulao

gulao

    Newbie

  • Members
  • Pip
  • 2 posts
  • Devices:zte blade
Hi Paul;
Nice work.
Any chance this GR140 version may work on my new nexus S
Gingerbread version 2.3.3
baseband version I9023XXKB3
Kernel version 2.6.35.7-g1d030a7
android-build@apa28#1
build number gr154
Thanks

  • 0

#73
Chamb'

Chamb'

    Newbie

  • Members
  • Pip
  • 2 posts

Hi Paul;
Nice work.
Any chance this GR140 version may work on my new nexus S
Gingerbread version 2.3.3
baseband version I9023XXKB3
Kernel version 2.6.35.7-g1d030a7
android-build@apa28#1
build number gr154
Thanks


No, It will not work, I also made the GRI54 superboot, all versions of one click root are here: http://www.megaupload.com/?f=Z5BQXS41

  • 0

#74
gulao

gulao

    Newbie

  • Members
  • Pip
  • 2 posts
  • Devices:zte blade

No, It will not work, I also made the GRI54 superboot, all versions of one click root are here: http://www.megaupload.com/?f=Z5BQXS41


Thanks a lot, you're the Man

  • 0

#75
PaulOBrien

PaulOBrien

    It's My Party

  • Founder
  • PipPipPipPipPipPip
  • 36,369 posts
  • Gender:Male
  • Location:Norwich, UK
  • Devices:All the Nexus!
  • Twitter:@paulobrien
Topic brought up to date with the latest release.

P

  • 0

You can follow me on Twitter - http://twitter.com/paulobrien / Follow MoDaCo on Twitter - http://twitter.com/modaco

Want to donate? MoDaCo is raising money for the Multiple Sclerosis society.

Posted Image


#76
Oysterman

Oysterman

    Newbie

  • Members
  • Pip
  • 21 posts
  • Gender:Male
  • Location:Vienna
  • Devices:Samsung/Google Nexus S
Houston - i have a Problem.

I bought a Nexus S yesterday and just tried to get root access using Pauls latest creation.

My Phone was already on GRJ22.

First i unlocked the bootloader - absolutely no Problem there.
Phone showed as "unlocked" in Fastboot.

After that i applied the superboot img by "- WINDOWS - double click 'install-superboot-windows.bat'"

I could not read the text that popped up, it went by so fast.

But now i am stuck at the google logo and an open lock beneath and nothign more is happening.
When i pull the battery i can get to fastboot but nothing more.

Help. I tried to repeat installing the superboot now twice, even went from my notebook to my desktop PC - no change.
Phone is bricked.

What can i do ???

edit: The following information is shown in Fastboot screen :
Product Name - Herring
HW Version - REV 52
Bootloader Version - I9020XXKA3
Baseband Version - I9020XXKD1
Carrier Info - EUR
Serial number - 303011CE306F6....
LOCK STATE - UNLOCKED

edit 2:

I ran the bat file again - this time in console to see the message

D:\superboot>fastboot-windows.exe flash boot boot.superboot.img
sending 'boot' (3024 KB)... OKAY
writing 'boot'... OKAY

D:\superboot>fastboot-windows.exe reboot
rebooting...

after that i am stuck

Edited by Oysterman, 09 August 2011 - 03:05 PM.

  • 0

#77
PaulOBrien

PaulOBrien

    It's My Party

  • Founder
  • PipPipPipPipPipPip
  • 36,369 posts
  • Gender:Male
  • Location:Norwich, UK
  • Devices:All the Nexus!
  • Twitter:@paulobrien
Did you try the 'other' GRJ22 superboot?

I just re-tested on my Nexus S and it's booting OK...

P

  • 0

You can follow me on Twitter - http://twitter.com/paulobrien / Follow MoDaCo on Twitter - http://twitter.com/modaco

Want to donate? MoDaCo is raising money for the Multiple Sclerosis society.

Posted Image


#78
Oysterman

Oysterman

    Newbie

  • Members
  • Pip
  • 21 posts
  • Gender:Male
  • Location:Vienna
  • Devices:Samsung/Google Nexus S

Did you try the 'other' GRJ22 superboot?

I just re-tested on my Nexus S and it's booting OK...

P


Yes i tried both versions.

Could it be an issue with my Win7 64 bit or the USB drivers ?

Since i got no error msg i don´t think so.

Edited by Oysterman, 09 August 2011 - 03:10 PM.

  • 0

#79
Oysterman

Oysterman

    Newbie

  • Members
  • Pip
  • 21 posts
  • Gender:Male
  • Location:Vienna
  • Devices:Samsung/Google Nexus S
Problem solved - my Phone ist working again.
BUT: I was not able to fix it with the images here.
Could it be that this is not working with the 9023 (SLCD) ?

I went over to xda developers and used the "one klick root" toolset
which resulted with a working clockworkmod recovery image.
After that i was able to flash a custom ROM.

  • 0

#80
Heintraag

Heintraag

    Regular

  • Members
  • PipPip
  • 67 posts
  • Devices:Google Nexus S
Any news on the new 2.3.4. superboot?

  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users