Develop Bugs

S-on AND Root

I've been posting here and there around here lately but thought I'd get a cleaner, more focused thread going for those of us who used HTC's unlock tool and want root.
I managed to get the bootloader unlocked with HTC's tool and installed SU and clockwork onto my Inc2 but I think I'm having problems because I'm still S-On instead of S-Off.
So, what do we do next after unlocking the bootloader? I'm under the impression that because I'm S-On still, I can flash a custom ROM, but not only the ones with the stock kernel intact. This would be why Sabotage was able to install, but Mik wouldn't. Still only a theory, though.
ANY HELP PLEASE!!!

Kayak83 said:
I've been posting here and there around here lately but thought I'd get a cleaner, more focused thread going for those of us who used HTC's unlock tool and want root.
I managed to get the bootloader unlocked with HTC's tool and installed SU and clockwork onto my Inc2 but I think I'm having problems because I'm still S-On instead of S-Off.
So, what do we do next after unlocking the bootloader? I'm under the impression that because I'm S-On still, I can flash a custom ROM, but not only the ones with the stock kernel intact. This would be why Sabotage was able to install, but Mik wouldn't. Still only a theory, though.
ANY HELP PLEASE!!!
Click to expand...
Click to collapse
There are 2 options to flash a custom ROM that has a custom kernel on an unlocked bootloader.
1. Instead of booting to recovery mode directly, you need to boot in Fastboot mode and issue the command:
Fastboot boot [path to custom recovery.img]
This will boot you into recovery mode using the custom recovery image. Then you can flash a custom ROM with a custom kernel correctly.
2. Extract the boot.img from the custom ROM zip file and copy it to your SDK tool directory.
Then boot into recovery mode and flash the custom ROM. Next you must reboot into bootloader mode and enter Fastboot mode. Enter the following command:
Fastboot flash boot [path to the boot.img file].
Try either option 1 or option 2. You do not need to do both.
Hope this helps.

tpbklake said:
There are 2 options to flash a custom ROM that has a custom kernel on an unlocked bootloader.
1. Instead of booting to recovery mode directly, you need to boot in Fastboot mode and issue the command:
Fastboot boot [path to custom recovery.img]
This will boot you into recovery mode using the custom recovery image. Then you can flash a custom ROM with a custom kernel correctly.
2. Extract the boot.img from the custom ROM zip file and copy it to your SDK tool directory.
Then boot into recovery mode and flash the custom ROM. Next you must reboot into bootloader mode and enter Fastboot mode. Enter the following command:
Fastboot flash boot [path to the boot.img file].
Try either option 1 or option 2. You do not need to do both.
Hope this helps.
Click to expand...
Click to collapse
Tried option 1 and when I go to select install zip from sd card after booting to cwm the phone restarts. Trying option 2 now...

Option #2 won't work since I get stuck at the HTC screen when trying to load a custom ROM.

Kayak83 said:
Option #2 won't work since I get stuck at the HTC screen when trying to load a custom ROM.
Click to expand...
Click to collapse
How did you try to reboot into bootloader from recovery once the ROM was flashed. Once I get into recovery I connect the phone with a USB cable and then type
Adb reboot bootloader
This will boot you into HBOOT straight from recovery and should prevent the hang at the HTC.

Ok. Let's start fresh and complete:
1- Plug phone into computer.
2- select HTC sync on phone
3- open cmd and get to sdk
4- type "adb reboot bootloader"
5- phone should reboot to HTC's recovery thing
now what?
I have cwm installed already.

Kayak83 said:
Ok. Let's start fresh and complete:
1- Plug phone into computer.
2- select HTC sync on phone
3- open cmd and get to sdk
4- type "adb reboot bootloader"
5- phone should reboot to HTC's recovery thing
now what?
I have cwm installed already.
Click to expand...
Click to collapse
Just select Charge Only, not HTC Sync.
Once you type adb reboot bootloader you should get the HBOOT screen and it should show FASTBOOT USB.
At this point you should enter Fastboot commands from you PC command prompt.
So you said you tried fastboot boot [path to recovery.img file] and it did boot you into recovery, right? Then you should be able to flash the custom ROM and reboot normally when the install is complete.
For option 2 once you are in recovery mode flash the custom ROM and then when it is finished connect the phone with the USB cable and at the command prompt you should be able to type adb devices and it will respond with your device id.
If it does, then type adb reboot bootloader and it will take you back to the HBOOT screen. From there you would then enter the following Fastboot command:
Fastboot flash boot [path to boot.img file]
Then Fastboot reboot

tpbklake said:
Just select Charge Only, not HTC Sync.
Once you type adb reboot bootloader you should get the HBOOT screen and it should show FASTBOOT USB.
At this point you should enter Fastboot commands from you PC command prompt.
So you said you tried fastboot boot [path to recovery.img file] and it did boot you into recovery, right? Then you should be able to flash the custom ROM and reboot normally when the install is complete.
For option 2 once you are in recovery mode flash the custom ROM and then when it is finished connect the phone with the USB cable and at the command prompt you should be able to type adb devices and it will respond with your device id.
If it does, then type adb reboot bootloader and it will take you back to the HBOOT screen. From there you would then enter the following Fastboot command:
Fastboot flash boot [path to boot.img file]
The Fastboot reboot
Click to expand...
Click to collapse
I'm able to fastboot into cwm. But when I go to select install zip from sd card via the phone controls (volume up/down/power), the phone reboots.

Kayak83 said:
I'm able to fastboot into cwm. But when I go to select install zip from sd card via the phone controls (volume up/down/power), the phone reboots.
Click to expand...
Click to collapse
Which version of CWM are ou using. I use CWM 5.0.2 and it works fine.

SUCCESS. Thanks for your help!

Glad you got it goin!
Sent from my ADR6350 using xda premium

Kayak83 said:
SUCCESS. Thanks for your help!
Click to expand...
Click to collapse
Which option did you have success with?

dumb question but...
how do you find the path to your custom recovery?

mza929 said:
dumb question but...
how do you find the path to your custom recovery?
Click to expand...
Click to collapse
You determine what the path is when you download the recovery image to your PC. The best place to download or copy it to is the same folder you run adb.exe and fastboot.exe from.

tpbklake said:
You determine what the path is when you download the recovery image to your PC. The best place to download or copy it to is the same folder you run adb.exe and fastboot.exe from.
Click to expand...
Click to collapse
great thank you... i was thinking i had to use a path to the recovery on my phone's storage not my PC's...

Can someone link me to a cwm recovery that works. I'm having the reboot issue after selecting choose file from SD card.
Sent from my dinc2 using XDA App

mza929 said:
Can someone link me to a cwm recovery that works. I'm having the reboot issue after selecting choose file from SD card.
Sent from my dinc2 using XDA App
Click to expand...
Click to collapse
You should look for and use CWM 5.0.2

Kayak83 said:
I've been posting here and there around here lately but thought I'd get a cleaner, more focused thread going for those of us who used HTC's unlock tool and want root.
I managed to get the bootloader unlocked with HTC's tool and installed SU and clockwork onto my Inc2 but I think I'm having problems because I'm still S-On instead of S-Off.
So, what do we do next after unlocking the bootloader? I'm under the impression that because I'm S-On still, I can flash a custom ROM, but not only the ones with the stock kernel intact. This would be why Sabotage was able to install, but Mik wouldn't. Still only a theory, though.
ANY HELP PLEASE!!!
Click to expand...
Click to collapse
OK maybe I am missing something here. Do you actually have full root? If you do, how did you get it? I don't know how to get the su binary and busybox installed. I have unlocked my bootloader using the htc supertool and I don't have root, which is keeping me from installing CWM or anything root related for that matter. I have not seen any instructions on how to root this thing since the unlock tool became compatible 3 days ago. But maybe I have missed something.
Thanks for any help.

Still cant get rom to boot... however, i have been able to fastboot into custom recovery and complete the flashing process...
Now i am just stuck at the HTC screen after reboot.
Any suggestions?
Thank you all so far. You have been most helpful.
***** update ***** I finally got it after fast booting into recovery, flashing rom, and then extracting boot.img from that rom and flashing it via fastboot.

mza929 said:
Still cant get rom to boot... however, i have been able to fastboot into custom recovery and complete the flashing process...
Now i am just stuck at the HTC screen after reboot.
Any suggestions?
Thank you all so far. You have been most helpful.
***** update ***** I finally got it after fast booting into recovery, flashing rom, and then extracting boot.img from that rom and flashing it via fastboot.
Click to expand...
Click to collapse
Yes good job. The last part is the key to getting a custom ROM installed. Glad it worked for you.
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
hackweed said:
OK maybe I am missing something here. Do you actually have full root? If you do, how did you get it? I don't know how to get the su binary and busybox installed. I have unlocked my bootloader using the htc supertool and I don't have root, which is keeping me from installing CWM or anything root related for that matter. I have not seen any instructions on how to root this thing since the unlock tool became compatible 3 days ago. But maybe I have missed something.
Thanks for any help.
Click to expand...
Click to collapse
After you have an unlocked HBOOT, you need to flash CWM recovery image in FASTBOOT mode. Once you have CWM installed, you can install the latest SU-3.0.xx.zip to root your current ROM and then you can installl and use root programs like ROM Manager, Busybox, Titianium Backup, etc. or you can install a rooted custom ROM.

How to push files in fastboot or Recovery?

Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?

Adb push in a custom recovery or you can reflash your ROM
Sent from my Galaxy Nexus using Tapatalk 2

JB has been known to get stuck at "google" for 10min or so. Did you wait long enough?
good day.

RevengeFNF said:
Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?
Click to expand...
Click to collapse
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it

Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
Confirmed working, and a BAZILLION times faster than the chrome browser.

Zector said:
Confirmed working, and a BAZILLION times faster than the chrome browser.
Click to expand...
Click to collapse
??? chrome browser can flash roms?
10chars

Does it work with CWM?
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
I tried this and it said "insufficient permissions for device" in ADB. My phone randomly rebooted and gets stuck on the boot logo, but everything on my sdcard got deleted. I have a Verizon Galaxy Nexus if that helps

If it's only the kernel causing problems, the easiest would be to run "fastboot flash boot <name of boot.img here>" from fastboot?(the original boot.img from the rom he's using would be found inside the zip file)
But if you screwed something else up in the process, you may need to flash the entire rom again from the recovery. If you are using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer, and if you are using twrp, they have an option to sideload(under advanced), where you can connect you phone to your pc and run "adb sideload <name of rom.zip file here>" and it will install it right away.

mortenmhp said:
using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer
Click to expand...
Click to collapse
this will not work, not with cwm nor with twrp, at this point; likely, it will never work as we don't have removable storage.

Then just use the sideload, it works quite well for me.

mortenmhp said:
Then just use the sideload, it works quite well for me.
Click to expand...
Click to collapse
Or just 'adb push rom.zip /sdcard/', or if that doesn't work, 'adb push rom.zip /data/media'.
Sent from my i9250

in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave

GruiaNovac said:
in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave
Click to expand...
Click to collapse
adb works fine with TWRP if you have updated adb drivers/adb daemon.
guess fastboot flashing images also eludes you.
so no, you're not in the grave.
*note* thanks for necroing a thread from December.

No, in bootloader its fine.
And apparently (if It wasn't a fluke) I think i booted normally , and having no rom it just stood there, and adb worked.
that saved me
TWRP dissapoints . have to look for replacement

stuck in recovery
so Im stuck in a similar situation
before installing a ROM which instructed to wipe the device, i did so, in fact i over did it.. wiped data/cache/davlik/system and internal storage
the same storage which had the ROM that i was supposed to install after wiping it.
I felt very dumb, but now stuck with the bootloader / fastboot / and TWRP recovery .. the TWRP recovery version i have HAS the adb sideload feature
which i've tried to install the Cyanogen ROM using ./adb sideload filename.zip , which hasnt work for Cyanogen but worked for the GApps after that ( I thought that was kinda weird).
the sideload command goes thru the sending of the entire ROM to the phone, but it never installs correctly..
NOW im stuck
any suggestions or help on how i can do it with what appears to me to be as fastboot / adb side load / and recovery options"??
thank you very much in advance
=====
update
=====
solved my problem... mounting the partition turns on full ADB to push the files onto the drive and install them using the recovery software

Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
you just saved my life... and my phone

[Q] please help

i'm having bootloop after installing 17/02/2013 CM10.1 rom on my gsm gnex. the issues are:
1. i don't have any previous working cm10 rom saved in phone's sdcard.
2. can't get adb working, maybe because i never enabled usb debugging mode before.
fyi, i have never flashed any other roms, just CM roms. please assist..

Go into recovery and transfer a new Rom download to your phone if you have a computer. There is an option to transfer files inside recovery.

eqjunkie829 said:
Go into recovery and transfer a new Rom download to your phone if you have a computer. There is an option to transfer files inside recovery.
Click to expand...
Click to collapse
that requires adb (adb_sideload- correct me if i'm wrong).. my adb is not working.. can't boot to android.. can't find a way to enable usb debugging mode.. so no adb..

Do you have a custom recovery or experience with fastboot? Boot a recovery image via "fastboot boot recoveryname*.img", and adb is enabled.

bodh said:
Do you have a custom recovery or experience with fastboot? Boot a recovery image via "fastboot boot recoveryname*.img", and adb is enabled.
Click to expand...
Click to collapse
i don't have custom recovery, but i know how to get into fastboot. please explain how to ""Boot a recovery image via "fastboot boot recoveryname*.img"""

[email protected] said:
i don't have custom recovery, but i know how to get into fastboot. please explain how to ""Boot a recovery image via "fastboot boot recoveryname*.img"""
Click to expand...
Click to collapse
Attached is clockworkmod touch recovery for gsm galaxy nexus, maguro. Phone in bootloader mode, open a terminal, cd to directory of fastboot and where you move this file to, type fastboot devices to verify device is connected, then "fastboot boot CWMT6023.img", without the quotes of course. This will temporarily allow you to use clockworkmod recovery, and thus adb, without having it on your device once you have selected "reboot now".
And if that didn't help, try consulting http://forum.xda-developers.com/showthread.php?t=1626895, since i'm thinking you haven't used fastboot in a terminal, but only know it's 'mode', and may need help with drivers.
You also might want to consider just straight out flashing cwm recovery, since YOU NEED TO MAKE BACKUPS!

[email protected] said:
i don't have custom recovery, but i know how to get into fastboot. please explain how to ""Boot a recovery image via "fastboot boot recoveryname*.img"""
Click to expand...
Click to collapse
If u don't have a custom recovery how did u flash cm10?
Sent from my Galaxy Nexus using xda premium

Esteway.619 said:
If u don't have a custom recovery how did u flash cm10?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
sorry, i got cwm. but what does fastboot have to do with cwm? i can't use cwm to restore because files can't be sent from computer to it.
as of fastboot in terminal, it seems the phone not connected to computer. is there anything has to do with my drivers? "fastboot device" command shows <waiting for device>

I gave you that link to set up drivers more than anything else. If you already have cwm, boot to it and now you can adb push a rom.zip to your sdcard and install it, wipe caches and perhaps a factory reset [if you're changing to a different rom], OR, you can first try and wipe cache and advanced, dalvik cache to see if that fixes the bootloop.

1. Why didn't you make a backup?
2. Why didn't you make sure you know how to get out of this situation before flashing new ROMs?
3. Search as there are LOTS of tutorials on how to use adb to side load a new ROM via CWM

EddyOS said:
1. Why didn't you make a backup?
2. Why didn't you make sure you know how to get out of this situation before flashing new ROMs?
3. Search as there are LOTS of tutorials on how to use adb to side load a new ROM via CWM
Click to expand...
Click to collapse
I know how to use the adb to sideload a new ROM, thank you.
But please read my earlier post, in order to use adb, usb debugging mode must be enabled in android settings.
Mine is disabled, and i can't enable it now.

[email protected] said:
I know how to use the adb to sideload a new ROM, thank you.
But please read my earlier post, in order to use adb, usb debugging mode must be enabled in android settings.
Mine is disabled, and i can't enable it now.
Click to expand...
Click to collapse
If you think that then you have no idea on how adb works...
That is ONLY applicable when Android is running. As it's not, it's irrelevant...

[email protected] said:
I know how to use the adb to sideload a new ROM, thank you.
But please read my earlier post, in order to use adb, usb debugging mode must be enabled in android settings.
Mine is disabled, and i can't enable it now.
Click to expand...
Click to collapse
ADB should work in your custom recovery regardless of USB debugging being enabled or disabled.
I can't tell you how many times I have rebooted into recovery, wiped, then realized I forgot to put a file on my sdcard that I wanted to flash. I then use adb to push the file(s) from within the recovery.
Edit: I really need to refresh prior to responding.

so i can't get adb working because of the driver? thats why i got "waiting for device" when pushing file to phone?
edit: i've installed all the required drivers, it's not my 1st time doing it. MAYBE, this computer never connected to my gnex before, as i've formatted it a few days ago. So the gnex driver was not properly installed.. Is it possible?

If that version of cm 10 is for 4.2.2., then i think you may have an issue accessing adb without first getting the rsa verification, even in recovery (but im not sure). Looks like your only other option would be to fastboot flash stock images. And of course it sounds like driver issues, especially if your fastboot is not even working. Again, that link I posted will get you back up and running. http://forum.xda-developers.com/showthread.php?t=1626895

[q] *help* need to salvage sd card

My current situation: Rooted phone with unlocked bootloader and CWM. No rom loaded on the phone. No roms on SD card. Is there anyway to flash a rom on my device in my current predicament?

Persianity said:
My current situation: Rooted phone with unlocked bootloader and CWM. No rom loaded on the phone. No roms on SD card. Is there anyway to flash a rom on my device in my current predicament?
Click to expand...
Click to collapse
I know you can do it from your computer through fastboot. Or you could mount your phone on your computer, move a ROM from the computer to the phone, and flash it from recovery.

bananagranola said:
I know you can do it from your computer through fastboot. Or you could mount your phone on your computer, move a ROM from the computer to the phone, and flash it from recovery.
Click to expand...
Click to collapse
I tried connecting it via ADB but since there is no ROM loaded on my phone, USB Debugging is inactive. Is there a way for me to connect it without enabling USB Debugging?

Boot into fastboot. ADB works there. Push your rom to /sdcard and flash it via recovery
adb push location_of_downloaded_rom /sdcard/
Click to expand...
Click to collapse
Another alternative is sideloading it if you have TWRP

Persianity said:
I tried connecting it via ADB but since there is no ROM loaded on my phone, USB Debugging is inactive. Is there a way for me to connect it without enabling USB Debugging?
Click to expand...
Click to collapse
ADB debugging option in settings only pertains to a booted Operating System
iLeopard said:
Boot into fastboot. ADB works there. Push your rom to /sdcard and flash it via recovery
Another alternative is sideloading it if you have TWRP
Click to expand...
Click to collapse
fastboot and recovery are different things
adb does not work in fastboot
fastboot does not work in recovery
adb push will work in recovery

Pirateghost said:
ADB debugging option in settings only pertains to a booted Operating System
fastboot and recovery are different things
adb does not work in fastboot
fastboot does not work in recovery
adb push will work in recovery
Click to expand...
Click to collapse
Right, once again getting terms confused. I was in the same situation last week and went in circles between fastboot and recovery and you are correct, adb push does work in recovery.

iLeopard said:
Right, once again getting terms confused. I was in the same situation last week and went in circles between fastboot and recovery and you are correct, adb push does work in recovery.
Click to expand...
Click to collapse
Thank you both for your help. I did not want to go through Odin and wipe my SD card. Love!!!!

[Q] Stuck on flashing

I accidentally deleted the files inside internal storage via TWRP->Delete Internal Storage. And voila!
I already used 1-click restore and I got stuck at sending 'system' for 3hrs++ and also tried NRT Flash Stock + Unroot mode and also stuck at flashing.
What else can I do?

ren_sk8er said:
I accidentally deleted the files inside internal storage via TWRP->Delete Internal Storage. And voila!
I already used 1-click restore and I got stuck at sending 'system' for 3hrs++ and also tried NRT Flash Stock + Unroot mode and also stuck at flashing.
What else can I do?
Click to expand...
Click to collapse
Try using ADB Sideload. (Google it please). It should work with your problem as long as you have the drivers on your computer and ADB installed.

thor6577 said:
Try using ADB Sideload. (Google it please). It should work with your problem as long as you have the drivers on your computer and ADB installed.
Click to expand...
Click to collapse
What will i put on the ADB Sideload? i already have the stock google factory image. What should I put there? thanks!

ren_sk8er said:
What will i put on the ADB Sideload? i already have the stock google factory image. What should I put there? thanks!
Click to expand...
Click to collapse
Here is a guide that sfhub posted on how to use ADB sideload for stock 4.3 flo ROM JSS15Q version (latest).
http://forum.xda-developers.com/showthread.php?p=44882205#post44882205
Follow the instructions on there and you should be fine

thor6577 said:
Here is a guide that sfhub posted on how to use ADB sideload for stock 4.3 flo ROM JSS15Q version (latest).
http://forum.xda-developers.com/showthread.php?p=44882205#post44882205
Follow the instructions on there and you should be fine
Click to expand...
Click to collapse
I still have a problem, I cannot transfer file through adb sideload(temporarily boot to TWRP using WugFresh's NRT). I think root privilege has something to do with this because when I type adb root it says locked.
Fastboot is not also my option now. because I'm stuck at sending system..
--- I thought my stock recovery is not working geez. haha! I just rape the vol up and power button and the wild stock recovery appeared! yeaah! I'm now sending update.zip via adb sideload. after 2 days!!!! yeaah!

ren_sk8er said:
I still have a problem, I cannot transfer file through adb sideload(temporarily boot to TWRP using WugFresh's NRT). I think root privilege has something to do with this because when I type adb root it says locked.
Fastboot is not also my option now. because I'm stuck at sending system..
--- I thought my stock recovery is not working geez. haha! I just rape the vol up and power button and the wild stock recovery appeared! yeaah! I'm now sending update.zip via adb sideload. after 2 days!!!! yeaah!
Click to expand...
Click to collapse
Arrggh. ADB Sideload sending always stops at 58%. Any tips?

FINALLY! After !()#@()# years.;D haha! I've updated to stock via ADB Sideload with the right OEM USB Cable. Yeaah!:>