Database Info

[Q] Prevent CWM start from Bootloader?

With CM7 installed I am able to start CWM from bootloader by selecting "RECOVERY". Clockworkmod recovery itself has full adb support, so everyone who has stolen / found my Nexus S can gain full root access via USB simply by rebooting into CWM.
Is there a way to prevent this? Or a CWM version without adb support?
I'm worried about my google/dropbox/mail account - is adb root access for everyone with a simple USB cable a security issue?

I don't it's a good idea, but if the recovery partition contains only recovery, then you can format the recovery partition to prevent from booting it. Then keep your bootloader locked, so the only way to get access to the phone is to unlock the bootloader, which will wipe the phone clean.
Don't try it unless you are 100% sure though, I've read another guy whose brother formatted every partition in the phone, and the phone became bricked with no fastboot mode as well. I don't know which partition contains fastboot mode.

[Q] Can't access root and Google apps

I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.

SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!

I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?

Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.

Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?

Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.

Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.

Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.

1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.

3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.

Where do I go to get the recovery image?

The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.

Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.

Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.

There isn't a link...

Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.

It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.

I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.

I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.

Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back

[Q] JuopunutBear - Can't remove, help

Okay,
New sensation xe (Euro), CWM recovery, unlocked but not S-Off. Will only boot to HBOOT, Recovery, and its favorite, JuopunutBear. This thing will not go away. Happened when I tried the "Wire Hack". Phone boots to it unless I boot to HBOOT. Tried ....
Not ncessariliy in this order:
Wiping phone with 3 different wiping programs.
ControlBear.exe -r
Fastboot - most options
Flashing 2 different ROMs
Using Andriod Commander manually deleted every file and folder on the phone.
Others that i can't rememmber.
Two questions:
1. Is there somewhere on the file system that is totally hidden from wiping programs?
2. In the beginning, before I new what I was doing (1 week ago), I renamed a lot of files to update.zip. recovery.zip, PGxxIMG.IMG. Could I somehow be loading Juopunutbear back to the system when I reboot? If so, remedy?
Any help would really be appriciated, as I have spent days trying to work this out on my own.
Thanks!

JuopunutBear REMOVED FIXED
I got the same problem i check online and i was supposed to keep trying with the cable until it was successfull. I didnt wait that long and did exactly what you did, went to recovery and formated everything installed roms etc, none of which worked. Now as a result of all this JuopunntBear will definantly not work.
HERE IS HOW I FIXED AND GOT IT BACK UP AND RUNNING.
While trying the live CD method I downloaded a .zip file with contained the original unrooted Sprnint ROM and renamed it to PG86IMG.zip(~400mb) and placed it in the root directory of the SDCARD using CWM recovery card mount and went to fastboot menu which looked for this file and loaded the original sprint.
BEFORE YOU COPY THE FILE TO THE SD CARD YOU MUST RELOCK YOUR HBOOT you probably unlocked it while rooting the phone at some point. because if the hboot is UNLOCKED then the update will not extract and apply.
SO YOU MUST RELOCK BY: going to fast boot menu and sending the following relock command using command prompt in windows command prompt: fastboot oem lock
(this is similar to what is in the root instructions. google and find the files need to root the phone so that you can send the fastboot oem lock command (or anyother command in fastboot mode) to the phone using command prompt)(you can also use these to root the phone again once its up and running)
if in the process you cant get to the CWM recover etc you can use the command prompt and send unlock hboot and send" fastboot flash recovery xxxx.img " command to install the recovery console and access the SD card( root instructions and files http://htcevohacks.com/htc-evo-3d-hacks/how-to-root-evo-3d-2-08-651-2-and-later-htc-unlock-method/).
After this your phone will be just as if it was on the first day you got it.
HERE IS THE FILE I RENAMED AND LOADED. THERE ARE INSTRUCTIONS TO THIS
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209 <-- THIS IS THE FILE WHICH WILL FIX EVO3D CDMA FIRST FILE ON THE PAGE
http://forum.xda-developers.com/showthread.php?t=1563342 <--- i was following these
riptide355 said:
Okay,
New sensation xe (Euro), CWM recovery, unlocked but not S-Off. Will only boot to HBOOT, Recovery, and its favorite, JuopunutBear. This thing will not go away. Happened when I tried the "Wire Hack". Phone boots to it unless I boot to HBOOT. Tried ....
Not ncessariliy in this order:
Wiping phone with 3 different wiping programs.
ControlBear.exe -r
Fastboot - most options
Flashing 2 different ROMs
Using Andriod Commander manually deleted every file and folder on the phone.
Others that i can't rememmber.
Two questions:
1. Is there somewhere on the file system that is totally hidden from wiping programs?
2. In the beginning, before I new what I was doing (1 week ago), I renamed a lot of files to update.zip. recovery.zip, PGxxIMG.IMG. Could I somehow be loading Juopunutbear back to the system when I reboot? If so, remedy?
Any help would really be appriciated, as I have spent days trying to work this out on my own.
Thanks!
Click to expand...
Click to collapse

riptide355 said:
Okay,
New sensation xe (Euro), CWM recovery, unlocked but not S-Off. Will only boot to HBOOT, Recovery, and its favorite, JuopunutBear. This thing will not go away. Happened when I tried the "Wire Hack". Phone boots to it unless I boot to HBOOT. Tried ....
Not ncessariliy in this order:
Wiping phone with 3 different wiping programs.
ControlBear.exe -r
Fastboot - most options
Flashing 2 different ROMs
Using Andriod Commander manually deleted every file and folder on the phone.
Others that i can't rememmber.
Two questions:
1. Is there somewhere on the file system that is totally hidden from wiping programs?
2. In the beginning, before I new what I was doing (1 week ago), I renamed a lot of files to update.zip. recovery.zip, PGxxIMG.IMG. Could I somehow be loading Juopunutbear back to the system when I reboot? If so, remedy?
Any help would really be appriciated, as I have spent days trying to work this out on my own.
Thanks!
Click to expand...
Click to collapse
i had same problem, i took the sdcard out of my phone and put it in my moms galaxy note and formatted, then i put it back in my phone and started it up normally so i get pounutbear then i ran controlbear again on my computer and did the wire-trick right from then everything went as it should

adb and ruu problems

Hi!
First of i got a Htc one S from sweden and have been using utb rom for the last weeks with CWR Touch. After hearing that Cyanigenmod 10 was not as buggy as i thought i decided to use it.
This is what i did:
Downloaded the rom with rom manger - the phone restarted and viped everythig and started to install. It then aborted because of something wrong with the file.
Now i dont have a rom on my phone and i cant acces my SD card where i got other roms waiting for me to install.
When i try to use any ADB commands like "adb devices" nothing shows up under devices.
I tried "adb kill-server" and "adb devices" still nothing. When i use "fastboot devices" my device shows. I have tried both Hboot and Fastboot.
I tried to use one guide i found where someone used "all in one toolkit" to go back to stock recovery, delete space, re-enter recovery but that did not work for me.
I tried to adb push roms to my phone but still, no luck because my phone cant be found.
I tried to use the software "quick adb pusher" and with it i could se my device show and i could acces the storage, but there is a folder named "error device not found".
I tried to use "all in one toolkit" so i atleast could get CWR back on my phone, it flashes and finds my device, but when i try to rebot to recovery nothing happens anymore.
Do anyone have a fix for this? 7h later and im out of ideas.....what ever small ammount of knowledge i have about this ended hours ago and google cant help me anymore.
I even tried to download a ruu to try and install it but keeps telling me its the wrong version and then the installation aborts.
i have htc sync and htc usb drivers.
I also downloaded....well atleast 15 diffrent drivers and tried them still no adb device found.
I tried to download android atk but it complains about me not having java runtime but i installed it.
Im using windows 7 x64 bootcamp and osx

aasterix said:
Now i dont have a rom on my phone and i cant acces my SD card where i got other roms waiting for me to install.
Click to expand...
Click to collapse
In fastboot you can flash boot images and recoveries.
You can only use ADB when booted (which you can't) or when in recovery.
If you are unable to mount /sdcard in recovery, check the sticky on how to fix unmountable sdcard. It's here in Q&A.
Once you can mount /sdcard in recovery, you can adb push roms to it. You have to be in recovery for that, not in fastboot. First flash the boot image for your rom from fastboot, then boot into recovery and push and flash the rom. Wipe your data and cache.
You can do this either on windows or osx but on osx you dont need drivers so you can't have the wrong ones.
Good hunting,
-Jobo

The CWM version shipped with all-in-one doesn't work. CWM doesn't mount the sdcard anyway. I'd suggest TWRP because it can mount the sdcard and also has other features that CWM lacks.
Just boot into bootloader and in fastboot:
fastboot flash recovery twrpfilename.img
Then do as jobo said within the recovery.
Sent from my HTC One S

Pheroh said:
CWM doesn't mount the sdcard anyway.
Click to expand...
Click to collapse
What I meant, and what I think aasterix meant as well, is not mount the sdcard onto your computer over usb, but just mount the sdcard onto the root filesystem in recovery on the device.
If that doesn't work, you have to fix that first using '[HOW-TO] Fix soft brick & error mounting sdcard'. Once you can mount /sdcard in recovery (any custom recovery will do) you're good to push and flash your favorite rom.

[Q] HTC One S can't mount sdcard nor use adb

Hi everyone,
I wanted to start using CM 11 on my HTC One S when I realized my firmware was too ancient to run it.
Following this thread , I managed to upgrade my firmware and reach the point where I could access my recovery but could no longer see my sdcard and could no longer mount it.
I've been searching hours for a solution, but no avail, and any solutions that involve adb commands do not work for me. When I run an adb devices command my device doesn't show up, however it does in fastboot.
Currently I'm on HBOOT 2.15, S-on. unlocked
Can anyone shed any light on this?
Thanks in advance!
Update: FIXED, I tried the method in this thread the CWM recovery from this fix allowed me to adb push my ROM and fastboot flash boot boot.img , even though the SD card didn't mount. Booted up phone and all worked Seems only this recovery allowed me to adb push.