[Root] HTC A9

FatKris

Senior Member
Jan 29, 2013
165
14
0
No bugs at this time, I did all of this on a mac
Really? I know I rooted my m8 on my Mac, but that was a long time ago. I've since forgot how to abd and fastboot. I know it's not difficult I'll just look around YouTube. But I don't see my boot.img right now anyway. I can wait, I'm keeping my a9 so I'm in no rush. Thanks for the info though, good to know I don't need to go to Best Buy to get a PC only to return it the next day. :)
 

jcase

Retired Forum Moderator / Senior Recognized Develo
Feb 20, 2010
6,331
15,766
0
Sequim WA
Thanks for the screenshot tip :) I was actually unable to access my device so i wouldnt have been able to use that screenshot.

Everything is working fine and and I am rooted.

I formatted the data in recovery and rebooted and it did. Followed the instructions to root and was successful. Ive attached my build.prop Can you tell me what the issue was?

Many thanks for all the support.
Issue was taht /data did not get formatted
 

FatKris

Senior Member
Jan 29, 2013
165
14
0
I'm trying to abd in terminal but I keep getting error: device not found. I've for debugging on, I unlocked the boot loader through HTC and on the device. Any ideas any one? I'm on a Mac.

---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------

adb devices shows list of devices and its blank

---------- Post added at 10:46 PM ---------- Previous post was at 10:44 PM ----------

I don't need drivers do I?

---------- Post added at 10:56 PM ---------- Previous post was at 10:46 PM ----------

Ugh, never mind. Sorry with the he dumb questions.

---------- Post added at 11:17 PM ---------- Previous post was at 10:56 PM ----------

Okay, now I have a real question, adb is showing my device as offline. Any advice?
 

JontyJonty

Member
Nov 10, 2005
49
2
0
A9 UK Sim Free


[Disclaimer]
Not my fault or anyone's fault but your own if this does anything bad. If it breaks your phone, prevents you from calling 911 etc. By downloading, installing or continuing in anyway, you agree to accept full responsibility for any negative outcome. Read this whole page before starting. Backup your important files before starting, this will wipe data.

This is based on Chainfire's systemless root from http://forum.xda-developers.com/app...arshmellow-t3219344/post63197935#post63197935.

If you appreciate this, please considering donating to Chainfire, and either donating to beaups and myself at [email protected] or purchasing a copy of our SunShine s-off application, which we hope to bring support to the A9 with soon from http://theroot.ninja

Instructions:
Download the zip below for your phone/firmware. If not listed, please post your build.prop and stock boot image, I will make one when time allows. Please ensure the version number in the zip name matches the version in your build.prop.

For example "a9-att-635081.3.zip and
[email protected]_hiaeul:/ $ getprop ro.build.fingerprint
htc/hiaeul_00502/htc_hiaeul:6.0/MRA58K/635081.3:user/release-keys

Unlock your phone with htcdev.com

Boot into download mode (adb reboot download)

Unzip the appropriate zip file, and fastboot flash boot <bootimage name>
for example fastboot flash boot a9-att.img

Boot into bootloader (fastboot reboot-bootloader)

Factory reset your device, you must do this as the custom boot image disables encryption for the time being.

Flash a custom recovery (https://basketbuild.com/devs/Captain_Throwback/One (A9)/Recovery/TWRP).

Boot into your custom recovery

If /data is not mounted, mount it (mount /dev/block/mmcblk0p62 /data)

unzip su.zip
push su.img to /data/su.img (adb push su.img /data/su.img)

Reboot into android

unzip Superuser.zip
Install Superuser.apk (adb install superuser.apk)

You are done.

[Requesting Model/Carrier/Firmware Support]
a) be confident with adb and fastboot
b) have a good understanding of english(im sorry, i really do with I knew other languages, dont want a mishap due to a language barrier)
c) and backup all your important data
d) PM me

[Carrier/Firmware list]
ATT - ro.build.fingerprint=htc/hiaeul_00502/htc_hiaeul:6.0/MRA58K/635081.3:user/release-keys - a9-att-635081.3.zip
EE - ro.build.fingerprint=htc/hiaeuhl_00401/htc_hiaeuhl:6.0/MRA58K/635503.7:user/release-keys - a9-ee-635503.7.zip
Please find attached my build.prop. I have a A9 UK sim free handset.
 

Attachments

Captain_Throwback

Recognized Developer
Aug 22, 2008
20,079
22,348
203
The Nothing
FYI

I posted an updated TWRP at the link in the OP that fixes the USB connection issues. Besides decryption (which isn't supported in TWRP because HTC uses proprietary encryption), TWRP should now be working 100%. I'll be submitting my device files soon for official inclusion, and probably starting an official TWRP thread as well.
 

FatKris

Senior Member
Jan 29, 2013
165
14
0
I have the US factory unlocked version. ro.build.fingerprint
htc/hiaeul_00617/htc_hiaeul:6.0/MRA58K/639737.5:user/release-keys
 

JontyJonty

Member
Nov 10, 2005
49
2
0
Ok so ive managed to brick my A9. Ive managed to delete the os, can get to both TWRP and download mode, have tried flashing two A9 ruu but gives a security failure message. I think the only way to fix this is to get s-off.. might be waiting a while for that to happen... Anyone with any other ideas please let me know. All help is appreciated. Am willing to pay for s-off.
 

Captain_Throwback

Recognized Developer
Aug 22, 2008
20,079
22,348
203
The Nothing
Ok so ive managed to brick my A9. Ive managed to delete the os, can get to both TWRP and download mode, have tried flashing two A9 ruu but gives a security failure message. I think the only way to fix this is to get s-off.. might be waiting a while for that to happen... Anyone with any other ideas please let me know. All help is appreciated. Am willing to pay for s-off.
If you build a ROM from the dump Llabtoofer posted, you could just flash that so at least you have something (unless you have a different variant).
 
  • Like
Reactions: JontyJonty

jollywhitefoot

Senior Member
Jul 21, 2014
2,147
899
0
Nashville
Ok so ive managed to brick my A9. Ive managed to delete the os, can get to both TWRP and download mode, have tried flashing two A9 ruu but gives a security failure message. I think the only way to fix this is to get s-off.. might be waiting a while for that to happen... Anyone with any other ideas please let me know. All help is appreciated. Am willing to pay for s-off.
First off, it's not bricked. Bricked means it does nothing...no download mode, no recovery, just a blank screen. You have simply wiped your system partition and have no OS to boot to.

So, in download mode, find the OS line (for example, 1.11.617.5). This will tell you what RUU you can use.

Next, go to this thread and see if there's a matching RUU for your version.
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344

If no RUU exists yet, you might have to wait until HTC, or your carrier release one. Or wait until someone posts a recovery-flashable ROM.
If you are in the US, HTC puts their RUUs here:
http://www.htc.com/us/support/rom-downloads.html

If an ruu does exist that matches, place it in your fastboot folder, put the phone in download mode and flash it using "fastboot flash zip NAMEOFROM.zip"

If the RUU is over 2 GB, you'll need to find "htc_fastboot.exe" and use it instead of regular fastboot.exe. There should be several threads in the M9 section with links to htc_fastboot download. The commands are the same as with fastboot.exe.
 
Apr 6, 2011
24
4
0
Thanks for your great work jcase. I would like to help out with my version, but I can't figure out how to pull the boot.img.

I have the US Unlocked version
build.prop:
htc/hiaeul_00617/htc_hiaeul:6.0/MRA58K/639737.5:user/release-keys

cat /proc/partitions and MTK tool seem to indicate that the boot.img is in block 60 (mmcblk0p60), but I can't pull from the dev block without su...

If someone can tell me what to do here, I will happily provide the boot.img for my model.
 
  • Like
Reactions: jbea007

jollywhitefoot

Senior Member
Jul 21, 2014
2,147
899
0
Nashville
Thanks for your great work jcase. I would like to help out with my version, but I can't figure out how to pull the boot.img.

I have the US Unlocked version
build.prop:
htc/hiaeul_00617/htc_hiaeul:6.0/MRA58K/639737.5:user/release-keys

cat /proc/partitions and MTK tool seem to indicate that the boot.img is in block 60 (mmcblk0p60), but I can't pull from the dev block without su...

If someone can tell me what to do here, I will happily provide the boot.img for my model.
He should have this one already.
 
  • Like
Reactions: FatKris

techlogik

Senior Member
Aug 23, 2006
1,852
304
83
US unlocked version. Unlocked bootloader.

[email protected]_hiaeul:/ $ getprop ro.build.fingerprint
getprop ro.build.fingerprint
htc/hiaeul_00617/htc_hiaeul:6.0/MRA58K/639737.5:user/release-keys


So same here, will stand by and wait.
 
Last edited: