Database Info

[SOLVED] Rooting Nexus S <recovery wont stick>

I missed out something i think.
I have my sdk, with those files.
I went to cmd and type the commant
bla bla bla
fastboot devices >>> no error, means connected
fastboot oem unlock
>>>> it is connected but why it still waiting for my device?
I added the path to the system too, but still cant get rid of
I search the net and I cant get the solution.
Any idea anyone?

What drivers did you install? And yes, I read the "fastboot devices"

installed everyhing...
samsung adb + google package
samsung driver
pdanet

Phone has to be in bootloader mode?
Sent from my Nexus S using XDA App

yup.. it is in volume up + on mode.

If you plug your NS in and look in the Device Manager, do you see an unknown device with the question mark? If so, you should try to manually install the driver located in android-sdk-windows\extras\google\usb_driver
And when you issue the command
Code:
fastboot devices
It should display your NS device id, not just a blank line.

melvinchng said:
installed everyhing...
samsung adb + google package
samsung driver
pdanet
Click to expand...
Click to collapse
"samsung" driver... no
you use the drivers obtained from the Android SDK or PDAnet
Pretty much what suksit said.

Try pdanet! Last place i go y find drivers
Sent from my Nexus S using XDA Premium App

I tried sdk driver, pdanet driver. I can't unknown driver, it is listed as android. Means my phone is found by computer
I have android 2. 3. 4. Does it effect?
Sent from my Nexus S using XDA Premium App

Just curious, did you enabled the option in Settings > Applications > Development > USB debugging?
In Device Manger it should say something like "Android Composite ADB Interface"

I enabled it too... maybe I will try to reinstall and root it via my XP in VM.
I rooted my wildfire with this pc last time, maybe the drive mixed up.
Sent from my Nexus S using XDA Premium App

Just noticed that your location is in Malaysia. Could it happen that you have the i9023 (SLCD) model? If that's the case then I think you should try this.

Ya, I bought slcd set.
I will try it tomorrow at night and report back to you guys.
--------------------------------
It is really strange. Tried everything and won't work.
Pdanet detected my device that it is connected to computer, but it just show wait for device.
----------------------------------------
Edit: my full charge is 95%, it is normal right?
Sent from my Nexus S using XDA Premium App

melvinchng said:
Ya, I bought slcd set.
Edit: my full charge is 95%, it is normal right?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yeah thats normal, Samsung did some weird battery calibration thing!
However people here have found to get 100% or close to it.
When charging just leave screen on for 1 hour and have tethered wifi On, so far im charging full up to 98%, just waiting to squeeze in the last 2%.....could take awhile.
and yeah the 95% charge is normal. heres a explanation in further detail
Your battery gauge is lying to you (and it's not such a bad thing)

make sure u have following dlls in fastboot folder
AdbWinUsbApi
AdbWinApi

j0l6 said:
make sure u have following dlls in fastboot folder
AdbWinUsbApi
AdbWinApi
Click to expand...
Click to collapse
i have these in tools. and still waiting for device.
anyone any idea?

I forgot to tell you guys that my windows is 64-bit
Sent from my Nexus S using XDA Premium App

Try this or this then (the latter is quite hard to read anyway, I think they messed up the code formatting)

Unlocked bootloader!
thanks!
Sent from my Nexus S using XDA Premium App

melvinchng said:
I haven't root yet.
After I root, my storage and Rom will be wipe? So I need to install new Rom?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Rooting will add su binary and Superuser app to your NS. But your data will be wiped (both on phone and SD card) when you unlock the bootloader -- it's the same as doing a factory reset. However, your system partition will not be affected so no need to install new ROM if you prefer using stock.

[Q] Sensation (Pyramid) Bricked after Revolutionary (its not batt. drain)

i was trying to s-off the sensation with Revolutionary and it normally give error 2 or 3 times
Waiting for fastboot
waiting for the fastboot again
at this point for unknown reasons revolutionary crashed and my phone stucked to QUALCOM BOOTLOADER mode now i can not boot the phone even in bootloader mode(just a blank screen with backlight ON) but computer can recognise it as QCOM QD LOADER and asking for drivers (similar to HD2 brick problem when we flash the non-tmob with t-mob rom)
please see the picture attached and suggest something

do you have drivers installed , i suggest you re- install theme and see..

i can not boot the phone bro not even Bootloader mode

Download the official rom from here
http://forum.xda-developers.com/showthread.php?t=1074559
And try to flash the stock rom....

How to flash ROM? when its not detected as ANDROID OR HTC on PC?

You do have modified drivers installed right?

No Not at all i have 2 systems in both it been detected as QCOM QD i think i need to fix it via JTAG

What does adb devices say?
Sent from Mars

y0 said:
No Not at all i have 2 systems in both it been detected as QCOM QD i think i need to fix it via JTAG
Click to expand...
Click to collapse
Then you need to download modded drivers and run ruu.

Bro
what will it say if the handset is not detected as ANDROID service?Of course its not connecting
when i insert cable and battery to the phone it just lit its backlight (screen remains blank) no matter what button combination i try (VOL DOWN+POWER) or Simply i press power button screen remain blank it just backlights and detected as QUALCOM BL MODE on PC

Have you pulled the battery?

Modded drivers? Just use the drivers from revolutionary website and you'll be fine.
You didn't have HTC sync installed did you?

tinky1 said:
Have you pulled the battery?
Click to expand...
Click to collapse
yes Revolutionary show
waiting for FASTBOOT again (crashed itself)
after that i pulled out the battery
Sdobron said:
Modded drivers? Just use the drivers from revolutionary website and you'll be fine.
You didn't have HTC sync installed did you?
Click to expand...
Click to collapse
No modded drivers atall i am using this
(http://goo-inside.me/tools/HTCDriver3.0.0.007.exe) .
Actually when phone goes to proper bootmode than only it will ask for proper drivers but here the question is it is in some special mode how to get it out or bypass this
i wonder how many of you seen same problem in HD2 when wrongly flashed its detected as QUALCOM CDMA TECHNOLOGIES bla bla remember?

Send it back to htc. You probably didn't successfully s=off. So just tell them one day it died and would never turn back on. Even if they can tell you did something to it, they'll just send it back to you. Youre no worse off.
Sent from my LG-P999 using XDA App

It's detecting the phones processor oO.. Quite strange..
Sent from my HTC Sensation Z710e using xda premium

Have you asked the Revolutionary guys for their advice? I'd of said they are your best chance.
Sent From My HTC Sensation using Xda premium App

Your bootloader seems to be corrupted! Why you pull the battery? Revolutionary give back errors many times and it works with ot without this messages!
Its your own error ask htc to Pay for repair! Not tell it wont turn on and you dont do anything this is not fair!
You pulled the Battery in bootloader flashing process... just stupid!
Its not detecting the Phones processor its detecting the Chipset debug mode!
We could fix your phone in this mode but we dont have a command list!

y0 said:
yes Revolutionary show
waiting for FASTBOOT again (crashed itself)
after that i pulled out the battery
No modded drivers atall i am using this
(http://goo-inside.me/tools/HTCDriver3.0.0.007.exe) .
Actually when phone goes to proper bootmode than only it will ask for proper drivers but here the question is it is in some special mode how to get it out or bypass this
i wonder how many of you seen same problem in HD2 when wrongly flashed its detected as QUALCOM CDMA TECHNOLOGIES bla bla remember?
Click to expand...
Click to collapse
Same was at the Desire Qualcom CDMA technologies but the phones was turning on! Only USB was bricked! And there was an easy fix (flashing the misc partition) this could not help here.

Try running revolutionary from linux

HannoSLM said:
Try running revolutionary from linux
Click to expand...
Click to collapse
Why do you think it help?
if the bootloader dont start ADB and fastboot wil not work! And Revolutionary need working fastboot and adb!!
Bootloader is corrupted... he pulled the battery while the writing process!

[Q] Cant get S-OFF?

Im using the revolutionary method i get my beta key.
when i run the program it type in my beta key, and it accepts it and the comes up with ''zerging root. . . this might take a minute or so. . .'' but nothing happens and it stays like this. is it supposed to boot into bootloader or something? i have usb debugging enabled. and im on htc sync mode.

Did you install USB driver on rev site? Happenned to me when I try rooting it.
Sent from my HTC Sensation 4G using XDA Premium App

Shouldn't be in Sync mode, just connect it in charging mode

Ive tried what both of you have suggested but its still the same? is usb debugging supposed to be on or off?

USB Debugging = ON
Seriously, read the guide - http://forum.xda-developers.com/showthread.php?t=1192300

EddyOS said:
USB Debugging = ON
Seriously, read the guide - http://forum.xda-developers.com/showthread.php?t=1192300
Click to expand...
Click to collapse
Thats the guide im following and its not working. My galaxy s2 was a piece of cake to install a custom rom on
it works perfectly up to the point when i type in the beta key? which i know im doing it correctly.
it just hangs there? also when i boot into fastboot it has ***LOCKED*** at the top in pink, so does this mean i need to unlock my bootloader first?

No, it gets replaced with 'Revolutionary' once done.
Try a different USB port/PC

Just calm down and take a break, then re read the instruction. You must miss something
Sent from my HTC Sensation 4G using XDA Premium App

still no luck, and i have no idea why accept this sort of thing always happens to me ive managed to root a desire z in the past so this shouldnt be a problem on my laptop because it worked fine before?

This what comes up

We know what's coming up, that's normal. Have you tried a different USB port/PC at all?
I take it you're using Windows 7. If so, run your DOS prompt as an Administrator

dav08094194 said:
This what comes up
Click to expand...
Click to collapse
Your phone gonna reboot into HBoot a few time to get root. Are you seeing your phone reboots?
Sent from my HTC Sensation 4G using XDA Premium App

EddyOS said:
We know what's coming up, that's normal. Have you tried a different USB port/PC at all?
I take it you're using Windows 7. If so, run your DOS prompt as an Administrator
Click to expand...
Click to collapse
Yeah windows 7 and ive tried all 3 usb ports. not sure what DOS Prompt is but im running the program as administrator anyway.

Then I suggest trying a different PC. Although, have you always tried it as Admin? Funnily enough it worked for me once I STOPPED using Administrator rights

EddyOS said:
Then I suggest trying a different PC. Although, have you always tried it as Admin? Funnily enough it worked for me once I STOPPED using Administrator rights
Click to expand...
Click to collapse
got it to work in the end. i had to install windows 7 on my linux ubuntu pc

[Q] Am i bricked ?

Hi All,
i rooted my phone using what i thought was the right img file, but i can only assume it was the wrong file as i can now do nothing, i can boot into the Moto symbol, i can get to the droid with the warning triangle and into the fastboot section but i can no longer detect it when connected to the usb...
can anyone suggest a fix or am i screwed ??
thanks for any help

Try reflashing it with my tool, using unbrick feature, maybe you need fastboot drivers, just download it from sdk
Sent from my awesome ICS Xoom with xda Premium HD

cheers xxlordxx
ill give that a go, which drivers do i need to install for the fastboot ?
i downloaded the google usb driver package via the SDK last time, but it seems they are not firing up when i connect the tab.

TheWhiteDragon said:
cheers xxlordxx
ill give that a go, which drivers do i need to install for the fastboot ?
i downloaded the google usb driver package via the SDK last time, but it seems they are not firing up when i connect the tab.
Click to expand...
Click to collapse
If you can boot, you are not bricked - just start over with the root process using the correct image.

hey guys,
i have downloaded LAIOT but im not sure its detecting the pad, currently im getting
Searching For Device
List Of Devices
(Nothing listed)
on the pad
Starting Fastboot Protocol Support

tried doing the same using the different modes.
on Pad
Starting RSD Protocol Support
Same result on LAIOT

Recovery -
Same result.
this has all been done on a windows 7 laptop,
i have a linux laptop, will i get any more success using that with the google driver ?

just had a brain wave, checked device manager - i have an unknown device detected.. thats where the sodding thing has been hiding...
any ideas what drivers i need to get the dam thing detected correectly ?
just going to try using the default google ones from the SDK.

TheWhiteDragon said:
just had a brain wave, checked device manager - i have an unknown device detected.. thats where the sodding thing has been hiding...
any ideas what drivers i need to get the dam thing detected correectly ?
just going to try using the default google ones from the SDK.
Click to expand...
Click to collapse
Try a diff USB cable - download drivers from MOTOROLA website get this file - MotoHelper_2.1.32_Driver_5.4.0.exe
Okay here we go....
first thing let your xoom stuck on M logo.
Then hold power+volume up.
while power up press volume down to get firstboot.(make sure your PC and xoom know each other.)
You will see some text firstboot bla bla bla on left, top of screen.
Second thing open window cmd.exe
then type ...
cd /AndroidSDK/tools (where ever your adb.exe is located)
fastboot flash boot boot.img (the right boot image)
fastboot flash system system.img
fastboot erase cache
fastboot reboot
wait for reboot. You should see splash screen and you smile on your face.

TheWhiteDragon said:
hey guys,
i have downloaded LAIOT but im not sure its detecting the pad, currently im getting
Searching For Device
List Of Devices
(Nothing listed)
on the pad
Starting Fastboot Protocol Support
Click to expand...
Click to collapse
I need to fix it then...
Sent from my awesome ICS Xoom with xda Premium HD

thanks Mjamocha
ill give it ago tomorrow, sorry been flat out at work.
ill also try xxlords again on another machine just incase its the drivers on the laptop which are the problem.

XxLordxX said:
I need to fix it then...
Sent from my awesome ICS Xoom with xda Premium HD
Click to expand...
Click to collapse
sorry guys i have been flat out at work, SCCM deployment is taking a while to learn & play with.
but im back now and hopefully unbuggering my phone
i am going to redo all the bits you guys suggested on my PC rather than Craptop.
hopefully ill have more joy, ill let ya know how i get on 8)

What about using RDS?

woot im back
Thanks guys, just needed a fresh machine to do it on, think the craptop was a bit confused with the drivers.

TheWhiteDragon said:
woot im back
Thanks guys, just needed a fresh machine to do it on, think the craptop was a bit confused with the drivers.
Click to expand...
Click to collapse
Glad you got it going!

Had a similar problem where I had a boot loop and adb didn't recognise my device, but I could still put it into fastboot or recovery with power + vol down.
What I did was boot the Xoom so that it was stuck at the Moto logo, connected to the PC and queued up the fastboot command (fastboot flash boot boot.img) so the command window said "Waiting for device...", then reset the Xoom and manually put it into fastboot again at which point it picked up the queued command and started flashing.

No fastboot device

Hello all.
I reboot to bootloader, in fastboot mode. The intention is to update radio from img.
Problem - though shows that USB is connected, windows does not detect the device.
Not detect = no android device at all. Anyone else had this?

girtsn said:
Hello all.
I reboot to bootloader, in fastboot mode. The intention is to update radio from img.
Problem - though shows that USB is connected, windows does not detect the device.
Not detect = no android device at all. Anyone else had this?
Click to expand...
Click to collapse
Firstly this is in the wrong forum and should not go here.
Secondly have you installed the drivers for your phone by installing HTC Sync first and then have you set up adb and fastboot properly?

Sorry for the wrong forum.
Drivers are there with all the needed IDs, the problem really is no device detected - that is, the device menu doesn't even refresh when connected in fastboot.
Kavrocks said:
Firstly this is in the wrong forum and should not go here.
Secondly have you installed the drivers for your phone by installing HTC Sync first and then have you set up adb and fastboot properly?
Click to expand...
Click to collapse

No need to install HTC sync. The drivers can be found here:
http://www.modaco.com/topic/346331-htc-desire-s-usb-driver/
Make sure you have the SDK installed as well
Sent from my Desire S using Tapatalk 2

I never install htc sync. I have the right drivers, and in fact they can be enabled for any device with just adding the right IDs though this is not the issue. The device is not detected.
dan-fish said:
No need to install HTC sync. The drivers can be found here:
http://www.modaco.com/topic/346331-htc-desire-s-usb-driver/
Make sure you have the SDK installed as well
Sent from my Desire S using Tapatalk 2
Click to expand...
Click to collapse

Reboot 2.Power+vol.up 3.reboot recovery 4.nandroid
Sent from my Desire S using xda app-developers app

No-one else ever experienced this? Well nice to be unique then, for my Desire S anyway.

why won't u try htc sync

Solved myself. Apparently fault of the cable or usb port. Adb worked but not fastboot. Switched cable, all ok.
girtsn said:
No-one else ever experienced this? Well nice to be unique then, for my Desire S anyway.
Click to expand...
Click to collapse