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

HTC Acquire??

G

GiantsFan808

Lurker
Hi all. I'm a noob to this android development thing so forgive me if I sound naive or posted in the wrong place...I've successfully rooted an Alcatel OE thanks to these forums but that was cake compared to trying to root this HTC Acquire of mine. I've googled and search for days and I just cant seem to find anything that works. I've unlocked the bootloader thus far but thats as far as I can get. Any input on this will be appreciated, thanks.
 
Welcome to the forums, GiantsFan808!
I'm digging myself and the best I can come up with is that the Acquire is "very" similar to the EVO Design 4G/Desire S/Hero S/Kingdom. We do have an admittedly dated thread on rooting the ED4G, but I really can't comment on whether it would work with the Acquire:
http://androidforums.com/evo-design...43-xda-root-acs-htc-super-tool-v3-frigid.html
What version of Android are you running and what method did you use to unlock the bootloader?
 
Thanks for the quick reply! The link you provided, is there a method for linux? My device is a Kingdom hboot ver 1.26.0000 ROM 2.12.557.11 Android ver 2.3.4 unlocked bootloader via htcdev website
 
Yeah, I don't see too much on rooting the Acquire, either...

It looks like someone already reported that Gingerbreak didn't work (that would have been my first suggestion), but it wouldn't hurt to try again? :dontknow:

There's a ton of old root options that you could try, though: Z4 root, Super OneClick, zergRush.

You should certainly read and research them before trying--not having your device makes it a little hard to expressly recommend one.

Best of luck! :thumbup:
 
GiantsFan808,

Okay, just to reinforce what breadnatty already posted, this site HTC EVO Design 4G, Kingdom, Acquire specs and pictures leak | Android and Me says:

A full RUU for the HTC Kindgom was leaked and the build.prop file confirmed some rumored specs and revealed new details. This leaked version of the Kingdom is being called the HTC Acquire for Alltel, but Sprint fans should also pay attention because the Kingdom is rumored to become HTC EVO Design 4G later this year.
Click to expand...

So, if that's true, you might best search for the HTC EVO Design 4G rooting threads like this one:

[GUIDE]How to Root Boost Mobile HTC EVO Desi
 
scary alien said:
Yeah, I don't see too much on rooting the Acquire, either...

It looks like someone already reported that Gingerbreak didn't work (that would have been my first suggestion), but it wouldn't hurt to try again? :dontknow:

There's a ton of old root options that you could try, though: Z4 root, Super OneClick, zergRush.

You should certainly read and research them before trying--not having your device makes it a little hard to expressly recommend one.

Best of luck! :thumbup:
Click to expand...

Yes i've tried super-one click and one called superboot, both to no avail...at that point i was tired of following random tutorials on the other mentioned options. Thank you for your follow-up reply and I'll post my results...Thanks again!
 
HEYYY! Thank you so much for your help...i went over the guides again like you suggested, then followed your idea about the recovery.img...turns out trying to flash the image was the problem... using fastboot with the "soft boot" command that you outlined in your last post worked like a charm, booted me into the cwm recovery, and from there allowed me to install the su binary downloaded to the sd card. I rebooted, downloaded superuser and busybox from the Play Store, installed busybox, opened superuser and checked the automatic root access option, rebooted once more and now I got root! Still looking on the web for a confirmed root for this exact device but I still cant seem to pinpoint any posts that have the exact specs as mine...strange.

>>>> there were some minor bumps along the way, but nothing that prevented me from ultimately gaining root access <<<<

***First two tries at soft booting---FAILED (status read failed (Timer expired))
***The link to the su binary download provided above is no longer working/missing---http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip---so i got mine from here
>>> su-bin-3.0.3.2-efghi-signed.zipDownload
***SuperSU doesnt work for my device for some reason, so uninstalled and replaced it with Superuser...

Thanks again for your replies, I'm very satisfied with the advice I was given along with the surprisingly fast response time...Keep up the good work!
 
^^^ Awesome! :) :party:

Re. the timeout for fastboot, were you using a USB 3.0 port perchance? I've had similar issues (under Windows) when trying to use fastboot on a USB 3.0 port (switching to USB 2.0 fixed the timeout issue).

Also, I was able to download the http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip and saved a copy just in case, but glad you found a working alternative :thumbup:.

I suggested doing the soft boot since that wouldn't change your device--it would just load the bootable image into memory without flashing (didn't want to add any issues :p).

Anyway, very happy that you're successfully rooted--that's pretty cool :).

Cheers and hope you'll hang around with us here at AF!
 
Scary Alien,

I checked and yes i was using usb 3.0, and I'm feeling awkward that I didnt know there was any differences between ports lol...
The su binary link, every time i click on it it brings me to an error screen that says SERVER NOT FOUND...in my naivete, I figured it the prob was with the host. I'll check my proxy and firewall settings later...
Now im pondering switching usb ports and trying to flash, just to see it first hand and get a better understanding of the difference in ports and flashing/soft booting...So if I understand you correctly, flashing is like a "permanent" download, whereas soft-booting would be a "temporary" download, and not written to phone? Kind of like booting up a live cd?
 
No worries about the 2.0 vs. 3.0 thing...that only caught me when I got a new PC a while back and the light bulb finally clicked on for me that my fastboot issues may have been port related.

Yes, the fastboot boot <bootable.img> will not flash and will simply load-up the bootable.img file into memory vs. what happens when you flash (write) it where it stays permanently.

Having the fastboot boot soft-boot option is a nice option to have in your back pocket and is only (usually) available when your bootloader is unlocked. I often don't ever flash a recovery but simply use the soft-boot option--however, that's not an option if you don't have a PC and fastboot available and you'd have to resort to using a different means of flashing (i.e., via the flash_image utility, etc.).
 
You must log in or register to reply here.
Back
Top Bottom