yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Android Development] Ventrik101:
So I currently have LightNHB flashed. Since WinMo wont work via USB until I check that one option (forget off hand) I can't establish a USB connection to flash my phone. I tried putting the RAPHIMG.nbh into my SD cards root but that also didn't work, during the boot it said there were no images to flash.

So I removed the Android OS files and reformatted my SD card then places the img file into the root again, and again no image was found.

How would I fix this issue? I cannot seem to flash my phone back to a different WinMo rom.
[Touch Pro, Fuze Android Development] Ventrik101:
Got into LightNHB and it has no settings for the USB, it's all in ITA and only one thing I could find in the menus and it gives an error that the file cannot be found. Talk about bare-bones, no wonder I couldn't get this to connect to USB, I don't think it has the ability to.

Ideas?
[Touch Pro, Fuze Android Development] R^7Z:
Pull the battery, SIM(if you have one) and microSD card out.

Press and hold the volume down button while plugging in the USB cord and it should take you to the tri-color screen.

If you haven't already let go of the volume down button, do so now.

You should be ready to flash another ROM!

:cool:

n-Joie!
[Touch Pro, Fuze Android Development] Ventrik101:
Didn't know I could be like that but, sadly, error 260; followed to the letter :/

I can't get it to recognize .nbh. When I was able to get into the WinMo of LightNBH it seems it's WM5? CDMA? On my GSM phone... I know my version is dual CDMA and GSM. Though I use the latter.

It has HardSPL because Tri-colour screen says 1.90.OliNex
[Touch Pro, Fuze Android Development] arrrghhh:
Can you get it to recognize USB in said bootloader mode? You should be able to flash from your PC using bootloader mode...
[Touch Pro, Fuze Android Development] Ventrik101:
No, from what I can gather LightNBH doesn't have the stock USB connection info included in WinMo. Settings > Connections was empty. In fact all of it is empty (settings), I couldn't get to my SD card to run cab files to give me control over my phone.

Is there anyone else running the LightNBH flash that can confirm this? I can't even establish a USB line within Android.
[Touch Pro, Fuze Android Development] arrrghhh:
Hrm, I figured bootloader mode would be separate from WinMo entirely... so not having usb drivers in WinMo should effect it.

So you're saying when you're in bootloader mode, and you plug in USB it still just says "serial"?
[Touch Pro, Fuze Android Development] Ventrik101:
It doesn't even say serial.

RAPH100
SPL-1.90.OliNex
MicroP-Raph (LED) v13
MicroP-Raph (KEY) v5
PSOC-Raph STAGE_CVT v0x36

That's all my boot-loader says and I didn't think drivers had any effect here but as it sits I get an error 260 unable to connect from the ROM updater's that came with Monfro, TAEL, and Energy, as well as Task_29.
[Touch Pro, Fuze Android Development] arrrghhh:
Erm... It should definitely say "Serial" near the bottom. Give it 10 secs or so...

When you plug into USB, that should convert to say USB...
[Touch Pro, Fuze Android Development] jianC:
Did you remember to rename the .nbh file into "RAPHIMG.nbh"? You could also use a sd card adapter or another device that has working usb storage that takes micro sd cards and then drag the .nbh file on the sd card via another device.
[Touch Pro, Fuze Android Development] ksjuggalo:
See what happens when we get in a hurry? At least that's how i ended up with Litenbh on my TP stuck in a boot loop.

I tried the PWR + VOL DN while soft resetting. No luck. Then i was going to try holding those 2 buttons while plugging it in to USB, I was holding the buttons as i unplugged it. It jumped to the serial screen as soon as i unplugged it.

I'm sure you have gotten this fixed or a new phone by now, but in case ur as broke as me, and still playin with a TP cause you HAVE to.

Maybe this will help. Hold power + volume down while plugging/unplugging it from the PC. Might get lucky like i did.

I know it says Development discontinued, but the TP is old enough that the info i'm looking for is getting buried. Most d/l links i find are dead now, so i'm getting jumpy on the clicker finger.

But I for one think this link and the file itself needs to be taken down. I know it's only 2 of us so far, but dangit what a pain!!!

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

EDIT: Wow i didnt realize this thread was that old also.

Alltel Touch Pro (yeah it's old, and the keyboard doesn't work)

Using Updated Alltel ROM from HTC site.
[Touch Pro, Fuze Android Development] R^7Z:
Hmmm...

FroYo thread

Gingerbread thread

And yes, this are continuing projects... :)

Please read the first few posts before attempting anything. It's really does not hurt to try but your experience may vary slightly if you don't know what you are doing. :D

On that note, I am PMing the thread OP/forum mod to see if there is a way to link to the continuing project threads.

Actually the first post in that thread that you make mention of, has a link to the continuing project.. heh :rolleyes:
[Defy General] crazyVII:
hey guys...

another question from a new motorola defy multi-touch-keyboard user :=P

is there anyway to switch the language quickly...?

currently i use more locale2, but it also at least takes sever clicks until the language is changed... and it has the side effect that the whole OS changes the language.. which brings some lags...^^;)

so any advices? did i miss something?

thanks a lot,

cV
[Defy General] rockx0:
UP.
[Nexus S Android Development] Koush:
First, reboot into your bootloader/fastboot mode. (Volume + Power Up, or adb reboot bootloader)

Then, install this recovery:

http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.0-crespo.img

Then boot into Clockwork recovery and install the Superuser zip file (adb reboot recovery, or from fastboot choose recovery):

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

To install a rooted/insecure boot image (adb has root, THIS IS OPTIONAL, THE ABOVE STEPS ALREADY GOT YOU ROOT):

http://koush.tandtgaming.com//samsung/herring/rootboot.img

ROM Manager support is coming shortly. If you like my work, you can support me by buying any one of my Market apps :)
[Nexus S Android Development] mazodude:
Wow Koush, that was fast

Thanks
[Nexus S Android Development] gregounech:
Congratulations Koush, you're da best !
[Nexus S Android Development] Superfrag:
Awesome! Thanks.
[Nexus S Android Development] hansmrtn:
Radical! Gonna root mine now!
[Nexus S Android Development] ogdobber:
you are awesome:D
[Nexus S Android Development] gregounech:
Supercurio was 5 minutes faster, in fact you're slow :rolleyes: :D

http://xdaforums.com/showpost.php?p=9866570&postcount=33
[Nexus S Android Development] johoja:
Awesome, I guess that's the benefit of 'pure google' don't need any gimmicks to get root, and custom roms :)
[Nexus S Android Development] sheek360:
Verified, was able to root my friends with this method. Thank you.

I can't believe that its root process was really this simple, like the n1s.... I wonder if google is actually okay with us rooting our phones...
[Nexus S Android Development] b16a2smith:
Jesus, your a god among nerds/geeks and porn stars.
[Nexus S Android Development] cantIntoCode:
That was fast! Great work guys :)
[Nexus S Android Development] moskuito:
That's awesome! Thanks man!

Can't wait for my friend to come back from US with a couple of these flaming babies... guess we'll be already having a CM build for them by that time :)
[Nexus S Android Development] Arcarsenal:
Never would have thought I would have your code running on my Nexus S and on my Dell Venue Pro - you're the man Koush and thanks for all your work.
[Nexus S Android Development] supercurio:
To be honest I did just now, i messed up permissions earlier ;) − excitement −

shoot, again a small little error ^^
[Nexus S Android Development] rajendra82:
Since you created an img file, can you tell me how I peep inside the img files that are part of the leaked Nexus S firmware?

http://xdaforums.com/showthread.php?t=875608
[Nexus S Android Development] Koush:
I've had root/recovery for a few hours; I just didn't want to release anything that was broken and thus make me potentially liable for thousands of phones :) Just covering my ass.
[Nexus S Android Development] DAGr8:
lmao cant we just all get along , what we need now is a nice port kk thx ..
[Nexus S Android Development] gregounech:
Well, now port the 2.3 Rom to Galaxy S.

NOW1!

:D :rolleyes:
[Nexus S Android Development] Rigolox:
Koush, Supercurio well done. Both are great.

NaCl u2
[Nexus S Android Development] DAGr8:
more like yesterday ??

pretty please ?
[Nexus S Android Development] plmiller0905:
Double Post ...sorry
[Nexus S Android Development] dinan:
So I do everything up to the part where I flash the superuser zip... it flashes successfully in clockwork but I still don't have root (and no superuser app shows up)? Am I missing something?
[Nexus S Android Development] zdiddy14:
Same thing happened to me. It was too hard to get it to work through adb. Just go to recovery, mounts and storage, and mount system. Then go back and install the zip again. Worked for me:D
[Nexus S Android Development] dinan:
Ah yea, the mounts and storage for mounting system was what it was, thanks!

I also flashed the rootboot img... dunno what it does lol, will it be an issue?
[Nexus S Android Development] shaolinmastr:
Followed this guide and had my friends Nexus S unlocked and rooted in no time.

http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
[Nexus S Android Development] TheBiles:
So is anyone else having problems flashing files in recovery? I couldn't flash the su .zip or the GAPPS .zip (screwed up my Market and needed to fix it). It tells me that the flash was successful, but when I reboot nothing has changed. I got root by manually copying and chmoding the su file then installing Superuser from the Market.

Edit: Do I have to manually mount the system in recovery each time? This makes ROM Manager useless.
[Nexus S Android Development] jroid:
There are no remount issues, you just need to know the commands:

mount -o rw, remount /dev/block/mmcblk0p2 /system

Sent from my Nexus S
[Nexus S Android Development] AndrewGoldy:
Excellent! Going to try this once mine arrives!

I'm currently an iPhone fanboy, but am changing!
[Nexus S Android Development] Smokexz:
This sounds nooby... but is there a simpler method? Maybe a one click root? I know people say that something has changed in gingerbread to disable this one click method, but is there another one in the works?
[Nexus S Android Development] poulosjr:
Root for me is definitely inconsistent and unroots after reboot
[Nexus S Android Development] nxt:
Rom Manager support is out, along with a new version 3.0 of ClockworkMod.

http://xdaforums.com/showthread.php?t=880333
[Nexus S Android Development] Darrien13:
does that mean roms are about to start comming :D

Time to root my phone :cool:
[Nexus S Android Development] coco135:
Thank you, thank you, thannnnkkkk youuuu. after 2 hours it's finally working.

your instruction and video are great
[Nexus S Android Development] poulosjr:
So I'm assuming if we go into recovery perform a cache wipe and data factory reset that clears root because I had superuser permissions after following theunlockr step by step video I tried installing the updated market it was force closing I performed a backup prior just to be safe I had to restore and lost root :( is there a permanent root in the works??
[Nexus S Android Development] swbca21:
I put the

recovery-clockwork-herring.img

file on the Nexus S SD-Card. The file was not found when I selected "Recovery". The phone locks up into a Triange/? symbol until I pull the battery.

I see that every one else get its . . what am I missing ?

I have my Vibrant in Root and performed many root tasks . . so I am not as dumb as I sound, I hope.

Thanks
[Nexus S Android Development] TheBiles:
Sorry, bro. It doesn't get much simpler than this.

Then you didn't do it correctly. You're either rooted or you aren't. There is not "temporary root" on the Nexus.
[Nexus S Android Development] mosby:
market issues

I followed all instructions no problem rooting but now the market download tab does not work and I am wondering if anyone else has this issue because if it is not recognizing my downloads will have to find and reinstall every time their is an update and is this because I unlocked the bottom loader or just a one off problem help if you can thanks
[Nexus S Android Development] theimpaler747:
Stuck this due to it's usefulness ;)
[Nexus S Android Development] belair56:
Hit menu, it is there.
[Nexus S Android Development] foxehkins:
I did the oem unlock, I have the recovery image from the first post and can flash things through it but clockwork is telling me there is an error running privileged commands =\

edit* had the wrong superuser flashed. gg ^^'
[Nexus S Android Development] helfone:
Im sorry, but got a noob question.

"To install a rooted/insecure boot image (adb has root, THIS IS OPTIONAL, THE ABOVE STEPS ALREADY GOT YOU ROOT):"

What is a rooted/insecure boot image and what benefits does it give?
[Nexus S Android Development] mazodude:
none. all it does is make adb root
[Nexus S Android Development] nxt:
LOL LOL LOL!

Sorry but that is actually dumb. You don't just put the .img file on your sd card and expect the recovery to work, you HAVE TO FLASH IT.
[Nexus S Android Development] Cheeze[iT]:
After its rooted, whats the easiest way to flash again back to wipe and keep the root? I just like to come from a fresh install while keeping the root. Is there a stock image to flash yet?
[Nexus S Android Development] TheBiles:
Just boot into recovery and select "factory reset."
[Nexus S Android Development] Xandlinger:
That's not how you "install" .imgs

You have to put that file into your androidsdk/tools folder (same place where fastboot.exe is) and then in cmd put "fastboot flash recovery recovery-clockwork-herring.img" Assuming that you have unlocked your bootloader, anyway.

...I think. I suppose I did it correctly since I have root ; ;
[Nexus S Android Development] Cheeze[iT]:
Ok, now something weird is happening... my phone is either stuck or something and I can't wake it. It requires a battery pull for it to work again. Trying to isolate the problem, first is removing setcpu... any other suggestions?

Rooted by following the steps, then clockwork and flashed the recovery to clockwork.
[Nexus S Android Development] Michael.B.:
I had this as well but attributed it to setting the setcpu down to 1000 and 1000 while screen was off.
[Nexus S Android Development] Cheeze[iT]:
This defeats why I would use it. So I just removed it. No issues any more.
[Nexus S Android Development] jroid:
you can't set down the cpu to 1000 and 1000 that's the max cpu power. :rolleyes:
[Nexus S Android Development] brian6685:
Anyone have a link to the stock recovery for future purposes? Or will relocking the bootloader put it all back?
[Nexus S Android Development] mirzahodzic:
Amazing, thanks!
[Nexus S Android Development] ajftl:
cant pass the unlock boot loader

adb stays on waiting for device foreever after i push fastboot orm unlock

anyone?

C:\android-sdk-windows\tools>fastboot oem unlock

< waiting for device >
[Nexus S Android Development] Xandlinger:
It isn't seeing your device in fastboot, is my guess.

Do the driver steps that is in the second half of the first post, then do

"fastboot devices" and see if your device is shown. Once it lists in device, then do "fastboot oem unlock" and it should work.
[Nexus S Android Development] Lou2serious:
Has anyone manage to root using ubuntu 10.04?? ADB doesn't recognize my phone so maybe editing the UDEV rules may help.
[Nexus S Android Development] Michael.B.:
On 10.10, should be about the same. See here: http://www.jaduncan.com/2010/01/nexus-one-adb-access-on-ubuntu-karmic.html
[Nexus S Android Development] jroid:
Well I didn't root with Ubuntu but I did manage to install adb on Ubuntu 10.10 today. So yea add the 51.android.rule in etc/udev/rules.d and make sure to change the id vendor== "04e8" (which is samsung) in the file then chmod a+r the file to make it executable and restart udev. Should be good to go then.

Sent from my Nexus S
[Nexus S Android Development] Lou2serious:
I edited the rules.d but not luck still says ???????????? no permissions
[Nexus S Android Development] jroid:
You have to set the file executable
[Nexus S Android Development] Lou2serious:
Yea, I did just like you said and I also restarted udev but still no luck. I think I'm just gonna redo everything. My problems started when I updated my sdk to the newest version.
[Nexus S Android Development] jroid:
Right click on the file, properties, make sure its executable, and it has read/write permissions. Also on adb in /tools. Other than that idk

Sent from my Nexus S
[Nexus S Android Development] Lou2serious:
Thanks for your help, adb recognizes it now. I restarted udev again and then typed sudo -s, then started adb. And I'm able to see my device now. Thanks again you really helped me get this solved!
[Nexus S Android Development] poulosjr:
I lose root whenever I do a restore from clockwork so I'm thinking it may by temp root and not permanent root, is this correct or am I wrong??
[Nexus S Android Development] Koush:
Updated with a new recovery!
[Nexus S Android Development] brian6685:
Higher then 3.0.0 or is that the one your talking about? And btw, any chance of you putting an option in Rom Manager to resort back to stock recovery? :)
[Nexus S Android Development] smelian:
I did every thing now got root and recovery but can't install superuser tried to install from recovery and market but still not working
[Nexus S Android Development] Michael.B.:
Manually push the apk and the su file while setting the chmod to 6775 on su
[Nexus S Android Development] yungfresh:
I finally unlocked the bootloader and installed clockword mod, but I held off on the superuser permission because I was reading that it didn't work well with certain rooted apps. I know the latest one is the one used for Froyo. Did anybody flash the superuser and has had no problems?? Should I wait for the gingerbread version of su?
[Nexus S Android Development] smelian:
I didn't understand Can u explain please I'm using window 7 I don't use su

I installed it but it don't work. Installed super user from market and recovery but annotated working I think cuz it is for froyo not Gingerbread
[Nexus S Android Development] brian6685:
Anyone have the rootboot.img in anykernel zip format to flash? I am at work and don't have access to fastboot atm.
[Nexus S Android Development] ScotchtapeLoser:
boot into recovery and mount /system/ then install superuser.apk... I believe there was detailed info on post 54
[Nexus S Android Development] irishrally:
I just flashed the recovery image on in the OP and it appears to be the same as 3.0.0.0. I'm not sure what the "crespo" part mean.
[Nexus S Android Development] brian6685:
What is "crespo"?
[Nexus S Android Development] :
Crespo is the hardware name for the NS (e.g. Dream -> G1). According to Google, crespo is a word in Italian, Portuguese, and Spanish.
[Nexus S Android Development] ommx:
some Noob! question here as i'm very new to Nexus family (been using HTC),

well will i be able to get OTA update via this root method? as the new update just been release today and i'm getting my Nexus S today, so i need some advice,

thank you
[Nexus S Android Development] Michael.B.:
Did you use the rootboot.img from above? If so probably not. IF you did, then check out here for the stock one: http://xdaforums.com/showthread.php?t=884416

After that you can update in Rom Manager to 2.3.1.
[Nexus S Android Development] ommx:
If i do all the thing except flash the "insecure" img, will i be able to get OTA ? and will i lose "root" after OTA?
[Nexus S Android Development] Luxferro:
Anyone having an issue with recovery replacing it self with stock after flashing to CWR, re-rooting after 2.3.1 update?

I have root, but it keeps replacing my recovery.

edit: figured how how to stop it from replacing recovery.

rename /etc/install-recovery.sh... this script replaces recovery back to stock on bootup.
[Nexus S Android Development] pksen88:
Hopefully you guys can help me out. I can fastboot flash recovery.img and get the writing recovery OKAY command. When I try to turn my to recovery i keep getting the stock recovery even though the clockwork recovery should have been on their.

What am i not doing?
[Nexus S Android Development] pksen88:
I think that this happens to me. Refer to my post above. Can you elaborate on what to rename?
[Nexus S Android Development] Luxferro:
well in order to prevent your recovery from returning to stock, you need to use root explorer, or another method to rename the following file:

/etc/install-recovery.sh

rename it to something like install-recovery.sh.old

now when you phone boots, it won't be able to run that script to replace your recovery.

That's all there is to it. It's that simple. Root explorer is a file explorer with root access. When you browse to the file, click the button to enable read-write access in root explorer, and then long press on the filename and rename it.
[Nexus S Android Development] pksen88:
For some reason it is not letting me rename the file. I tried using the android mate app and super manager.
[Nexus S Android Development] poulosjr:
so im noticing the one negative about rooting is that i can not recieve the OTA updates even by doing the *#*#checkin#*# option!!?? or is it not going to push the OTA because of having the bootloader unlocked?? is it best to keep the bootloader locked!??
[Nexus S Android Development] distortedloop:
Are you sure it's (/etc) mounted as R/W? Some apps don't mount that way automatically (Root Explorer requires you to push a button at the top of the screen). I'm not familiar with the two apps you mentioned and how they operate.

I just renamed mine using Root Explorer without issue.
[Nexus S Android Development] yungfresh:
Help!! Now I know I'm rooted. I unlocked my bootloader, flashed CWM 3.0 and installed the Superuser (ef) and even installed Rom manager and gave it permission. But for some reason almost every other rooted app I download and try to use it says that my phone isn't rooted?? I'm using a Nexus S. Anybody had similiar issues and resolved it? Thanks for all responses.
[Nexus S Android Development] Michigan Jason:
Please help

Ok, I am not a newb to the forum, but am to the NS. I managed to get the bootloader unlocked, however I cannot get the recovery installed.

I have tried the steps and just get a "cannot load" xxxx.img error.

Any help?

EDIT: apparently you need to type .img LMFAO thanks ne ways
[Nexus S Android Development] :
Question:

What happens if you Unlock bootloader, load custom recovery & rom, and then lock the bootloader again?

Can you still flash use the custom recovery, or does locking the bootloader do another wipe of the device?
[Nexus S Android Development] DKYang:
Go into recovery > mount and storage > select mount /system

Then in command prompt/terminal do:

adb shell

cd /system/bin

chmod 6775 su

Reboot phone. More info in this post: http://xdaforums.com/showpost.php?p=9869957&postcount=52
[Nexus S Android Development] DKYang:
Thanks to you, I found about Super Manager. Nice little app. :)

In order to rename the files you have to change the permissions. Go to the directory where the script is located. Press menu and select the top most option (something about changing permissions to R/W). Once you've done that select the R/W option. Then now you can edit the file.
[Nexus S Android Development] vapor311:
Would this not all be easier if the flashable file contained the update in it?

I want to go to 2.3.1 but every time I try to put it in I lose everything. It still wont update either. This part of the process is all very confusing to me.

I went back to Nexus S Standard Rom which was advised. Then tried to run the update zip it showed to run...then went to put my image back in and it still shows 2.3.0.

Im very lost lol