• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Help with getting SU and JB

DVSGUY

Lurker
Apr 27, 2013
9
5
I am trying to get my HTC Amazes (I have 3 I am trying to set up for my family)to be able to load custom JB Roms.

I updated the phone to ICS.

Then I unlocked the Bootloader using HTC Unlock

Then I used JuopunutBear to S-OFF and unlock the carrier with the wire trick. I maybe should have done SU before this?

The phones are working fine with this and are SIM unlocked, but I have heard JB will help with power draw (and be more fun).

The boot menu now looks like:

**** LOCKED ******
RUBY PVT SHIP S-OFF RL
HBOOT-1.93.0002
OpenADSP-v02.6.0.2226.00.0202
eMMC-boot
Mar 15 2012,21:46:51

I am trying to get SU so I can use ROM Manager to load in a JB Rom and have the ability to change ROMs easily.

I put SuperSU.zip (from extracted All-In-One kit V5.1) onto my SD card (it wouldn't work from the kit itself) , and try to go into recovery from this menu. It goes from circle of green arrows to a red triangle with exclamation mark (is this normal?). I go past this with up volume and power.

I get a menu
Android system recovery <3e>
Reboot....
Apply Update from external storage
Wipe data.....
Wipe cache.....
apply update from cache

but in the middle of the screen it has:

E:Can't open /cache/recovery/command

I pick Apply Update from external storage
and it opens the directory of my SDcard.

I pick SuperSU.zip and get:

Install /sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.

Is my recovery messed up, or is my SuperSU.zip messed up? I don't want to brick my phones by doing something wrong at this point.
 
I am trying to get my HTC Amazes (I have 3 I am trying to set up for my family)to be able to load custom JB Roms.

I updated the phone to ICS.

Then I unlocked the Bootloader using HTC Unlock

Then I used JuopunutBear to S-OFF and unlock the carrier with the wire trick. I maybe should have done SU before this?

The phones are working fine with this and are SIM unlocked, but I have heard JB will help with power draw (and be more fun).

The boot menu now looks like:

**** LOCKED ******
RUBY PVT SHIP S-OFF RL
HBOOT-1.93.0002
OpenADSP-v02.6.0.2226.00.0202
eMMC-boot
Mar 15 2012,21:46:51

I am trying to get SU so I can use ROM Manager to load in a JB Rom and have the ability to change ROMs easily.

I put SuperSU.zip (from extracted All-In-One kit V5.1) onto my SD card (it wouldn't work from the kit itself) , and try to go into recovery from this menu. It goes from circle of green arrows to a red triangle with exclamation mark (is this normal?). I go past this with up volume and power.

I get a menu
Android system recovery <3e>
Reboot....
Apply Update from external storage
Wipe data.....
Wipe cache.....
apply update from cache

but in the middle of the screen it has:

E:Can't open /cache/recovery/command

I pick Apply Update from external storage
and it opens the directory of my SDcard.

I pick SuperSU.zip and get:

Install /sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.

Is my recovery messed up, or is my SuperSU.zip messed up? I don't want to brick my phones by doing something wrong at this point.

You cant use the stock recovery.
Use Hasoons tool to flash 4ext recovery then youll be able to flash zips.
http://forum.xda-developers.com/showthread.php?t=1493905
 
  • Like
Reactions: scotty85 and DVSGUY
Upvote 0
It doesn't work. I get:

sending 'recovery' (6348 KB)...
OKAY [ 1.304s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.625s

I think I may need to unlock the bootloader again? But elsewhere it says don't use HTCdev unlock once you have S-Off.

I tried manually using "fastboot boot 4ext.img" (from the recoveries directory) to get into 4ext recovery mode to install SuperSU.zip, but I get a similar remote:not allowed message.

I have done more research and read:
*check your hboot screen. if you allready have an htc compatible hboot, then skip ahead to the next step,you dont need this.if you have a pink **locked** at the top of the hboot screen,then it is compatible with htcdev. if you dont have a compatible hboot,then download the RUU for the new hboot. right click it,and run as administrator. plug in your phone when prompted to. it will ugrade your hboot to the htcdev unlock compatible version.

So since my **** LOCKED **** is pink is it OK to use HTCdev unlock again even if I am S-Off? Did running ControlBear to get S-Off somehow make my phone locked again?

Sorry for the Noob questions.
 
Upvote 0
It doesn't work. I get:

sending 'recovery' (6348 KB)...
OKAY [ 1.304s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.625s

I think I may need to unlock the bootloader again? But elsewhere it says don't use HTCdev unlock once you have S-Off.

I tried manually using "fastboot boot 4ext.img" (from the recoveries directory) to get into 4ext recovery mode to install SuperSU.zip, but I get a similar remote:not allowed message.

I have done more research and read:
*check your hboot screen. if you allready have an htc compatible hboot, then skip ahead to the next step,you dont need this.if you have a pink **locked** at the top of the hboot screen,then it is compatible with htcdev. if you dont have a compatible hboot,then download the RUU for the new hboot. right click it,and run as administrator. plug in your phone when prompted to. it will ugrade your hboot to the htcdev unlock compatible version.

So since my **** LOCKED **** is pink is it OK to use HTCdev unlock again even if I am S-Off? Did running ControlBear to get S-Off somehow make my phone locked again?

Sorry for the Noob questions.

Yes unlock your devices and then try flashing the recoveries.
 
  • Like
Reactions: scotty85 and DVSGUY
Upvote 0
Upvote 0
i also like 4 ext recovery. as the others have said,dont use rom manager,or any other recovery control app. they are all an app,in a working rom,and as such,will not always be available to you. bad flashes happen. wether the rom has errors,or is missing pieces due to a bad download,if you hang on a splash screen or get stuck in a boot loop,the way to fix the issue is IN recovery,not in 4ext control or rom manager.

also,dont forget to always make a backup of a good working rom if you want to try another. :)
 
Upvote 0
Thanks for your comments, I decided to use 4Ext. It is very slick - touch screen even!

It's probably a good thing I went that way, I am having a very annoying problem with android keyboard stopping working. I think I have to wipe things clean and reinstall Roms again. I did a wipe data and cache and dalvik before and after the Rom install but that hasn't helped.
 
  • Like
Reactions: scotty85
Upvote 0
Thanks for your comments, I decided to use 4Ext. It is very slick - touch screen even!

It's probably a good thing I went that way, I am having a very annoying problem with android keyboard stopping working. I think I have to wipe things clean and reinstall Roms again. I did a wipe data and cache and dalvik before and after the Rom install but that hasn't helped.

What rom are you running?
 
  • Like
Reactions: scotty85
Upvote 0
Performing a format - system, then re-installing the ROM and gapps fixed things up.
I am running cm-10-20130421-NIGHTLY-ruby with gapps-jb-20121011-signed.

I am not sure if gapps-jb-20130301-signed would be OK to use - it says for use with Android 4.2.2, the ROM info show it as 4.1.2.

You should try flashing the GAPPS that are in the threads original post.
Or just flash the latest 4.1.2 gapps
Goo.im Downloads - Downloading gapps-jb-20121011-signed.zip
 
  • Like
Reactions: scotty85
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones