[Unlock ] Official Unlock via HTCdev!

ledrocnoc · 13th June 2012, 02:25 AM

HTC Status ROM version problem

I have an AT&T HTC Status that I am trying to unlock and I can't even get on first base... I am not a total newbie as I have previously successfully unlocked and rooted a Nexus One, Nexus S and Galaxy Tab (all running CM7).

I read most of the posts in this thread and couldn't find a solution to my problem. So here we are:

When I first tried to run the RUU my HTC Status had the following configuration:

Android: 2.3.3
HTC Sense 2.1 (don't think is matters)
Software Number (I assume it's the ROM version): 1.23.502.1
Build Number: 1.23.502.1 CL84153

I downloaded the RUU (PH0613000_Chacha_hboot_1.10.0000.exe) for the Cingular USA model because it had a matching ROM number to my HTC Status.

When I tried to run the RUU, I got an ERROR [190] ROM IS NOT UPDATED error saying that my ROM was not supported that I ought to wait for a new ROM (via OTA I assumed).

So I restarted the HTC Status and ran the HTC OTA Update utility and got the following configuration:

Android: 2.3.5
HTC Sense 2.1 (don't think is matters)
Software Number (I assume it's the ROM version): 2.14.502.2
Build Number: 2.14.502.2 CL291102

Re-ran the RUU (still using the T-Mobile version) and got the same error ERROR [190] ROM IS NOT UPDATED but with a message asking me to upgrade to 1.23.502.1

Any pointers?

Thanks.

Talebs · 13th June 2012, 06:20 PM

Quote:

Originally Posted by ToadFootNS

you can unlock bootloader using xtdev site, just skip the first step! I just unlock my girlfriends phone which was ota updated to the llatest version. it is 1.54.401.3

I did it too!! by skipping First step!

ledrocnoc · 07:58 PM

Quote:

Originally Posted by Talebs

I did it too!! by skipping First step!

Ok, I skipped the first step (Unlocking using the RUU from HTCDev) and went directly to the xtdev site DooMLoRD root. I ran the DoomMLoRD tool and I am getting some errors. Here is a dump of the results:

--------------------------------------------------------------------------------------------------------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
357 KB/s (23060 bytes in 0.063s)
--- correcting permissions
--- executing zergRush

[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[+] Found a GingerBread ! 0x00000118[*] Scooting ...[*] Sending 149 zerglings ...[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
433 KB/s (1075144 bytes in 2.422s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
38 KB/s (439 bytes in 0.011s)
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 20664 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
--------------------------------------------------------------------------------------------------------------------------------------------------------------

So it looks like it is failing to set the right permissions.

Could it be that the exploit be closed on this latest version (again, my HTC Status is running 2.14.502.2 CL291102

Any ideas?

Thanks.

Talebs · 13th June 2012, 08:54 PM

Quote:

Originally Posted by ledrocnoc

Ok, I skipped the first step (Unlocking using the RUU from HTCDev) and went directly to the xtdev site DooMLoRD root. I ran the DoomMLoRD tool and I am getting some errors. Here is a dump of the results:

--------------------------------------------------------------------------------------------------------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
357 KB/s (23060 bytes in 0.063s)
--- correcting permissions
--- executing zergRush

[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[+] Found a GingerBread ! 0x00000118[*] Scooting ...[*] Sending 149 zerglings ...[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
433 KB/s (1075144 bytes in 2.422s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
38 KB/s (439 bytes in 0.011s)
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 20664 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
--------------------------------------------------------------------------------------------------------------------------------------------------------------

So it looks like it is failing to set the right permissions.

Could it be that the exploit be closed on this latest version (again, my HTC Status is running 2.14.502.2 CL291102

Any ideas?

Thanks.

Don't use doomlord tool it won't work.... just follow these easy instruction here http://forum.xda-developers.com/show...hp?t=1452173to install cwm and superuser and you will be rooted!

ledrocnoc · 13th June 2012, 09:41 PM

Quote:

Originally Posted by Talebs

Don't use doomlord tool it won't work.... just follow these easy instruction here http://forum.xda-developers.com/show...hp?t=1452173to install cwm and superuser and you will be rooted!

Thanks for the pointer, but unfortunately it's not working either. When I do "fastboot flash recovery recovery.img" I get (even after performing a "Factory Reset"):

-----------------------------------------------------------------------
sending 'recovery' (4186 KB)...
OKAY [ 6.165s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 6.867s
-------------------------------------------------------------------------

Then when I try to get into the Recovery mode I get device image with a red triangle and exclamation point overlayed.

Which pretty much brings me back to square one...

As a summary, here is what I have been through so far:

Phone:

HTC Status (AT&T)
Android: 2.3.5
HTC Sense 2.1 (don't think is matters)
Software Number (I assume it's the ROM version): 2.14.502.2
Build Number: 2.14.502.2 CL291102

Steps taken:

HTC Dev stuff:

Downloaded the RUU (PH0613000_Chacha_hboot_1.10.0000.exe) for the Cingular USA model because it had a matching ROM number to my HTC Status.

When I tried to run the RUU, I got an ERROR [190] ROM IS NOT UPDATED error saying that my ROM was not supported that I ought to wait for a new ROM (via OTA I assumed).

DooMLord

Failed (here)

rajeshrakky · 28th June 2012, 01:58 PM

I Unlocked and rooted HTC Chacha indian rom

i am struggling with HTC customer care for getting new OTA update for the new version to unlock through HTC DEV...

i get negative reply from HTC...

3 days back i spend the whole day to break the rules...

i try to downgrade chacha to lower firmware
http://forum.xda-developers.com/show....php?t=1320392

first i create a gold card used many steps and tools all failed atlast used "goldcardtool 0.0.7" and created gold card.

after that i download "ruu_chacha_htc_asia_wwe_1.57.707.2_radio_47.23.35 .3033h_7.51.35.19_release_228383_signed.zip" from the forum copied to the memory card

after that i look for temporary boot using "Vivid-Root-3-windows" but the gold card failed to boot i tried many time using adb shell. used both Vivid-Root-3-windows and doomlord v4 same time i didnt know what happen i get "#" in adb shell. i reboot the mobile and install cm7 by rename the recovery as PH06img.zip..

miracle it got installed with out any question...........

from gold card using recovery i install rom the asia rom.. it reboot once and installs fully.

now i have Asia rom installed now i login to htcdev and download PH0611000_Chacha_hboot_1.10.0000 for asia rom and install it..

now i can able to run fastboot command got token and got mail attachement of "unlock.bin"

after reboot

"MY CHACHA WAS UNLOCKED"""""" yAHOOooooooooooooooooooooooooooo

after that rooted using doomlord , installed busy box all superuser programs get rights and binares are updating

sorry for my bad english

---------- Post added at 06:28 PM ---------- Previous post was at 06:20 PM ----------

Quote:

Originally Posted by ledrocnoc

Thanks for the pointer, but unfortunately it's not working either. When I do "fastboot flash recovery recovery.img" I get (even after performing a "Factory Reset"):

-----------------------------------------------------------------------
sending 'recovery' (4186 KB)...
OKAY [ 6.165s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 6.867s
-------------------------------------------------------------------------

Then when I try to get into the Recovery mode I get device image with a red triangle and exclamation point overlayed.

Which pretty much brings me back to square one...

As a summary, here is what I have been through so far:

Phone:

HTC Status (AT&T)
Android: 2.3.5
HTC Sense 2.1 (don't think is matters)
Software Number (I assume it's the ROM version): 2.14.502.2
Build Number: 2.14.502.2 CL291102

Steps taken:

HTC Dev stuff:

Downloaded the RUU (PH0613000_Chacha_hboot_1.10.0000.exe) for the Cingular USA model because it had a matching ROM number to my HTC Status.

When I tried to run the RUU, I got an ERROR [190] ROM IS NOT UPDATED error saying that my ROM was not supported that I ought to wait for a new ROM (via OTA I assumed).

DooMLord

Failed (here)

i also get these errors but i restart and went to bootloader usb mode i can able to get # icon when i use adb shell

i push cm7 recovery.img at that time

kinki · 01:58 AM

HTC Dev not working

The website is not responding when I click on Unlock bootloader! Any workarounds for Chacha. I found some for other models, but not sure which one works.
Edit: Never mind it works now after so many attempts, did they bug the site on purpose? But now the email to unlock is taking forever to reach me....
Edit 2: Yay I'm done! I skipped the 1st step, also note that the fastboot, adb files were not were HTC Dev says SDK would save them. Had to search my computer for them and finally used the temp root ones I had downloaded. Now let me find how to remove these annoying stock apps...
Thank y'all this site is great!

MEAKU15 · 5th August 2012, 11:42 PM

i've got a question, let say the latest RUU file on htcdev is 1.57.707.2 but your phone version is 1.57.707.3, how on earth are you to proceed to unlock your bootloader, i've search for many days now and i can't find an answer or do i just have to wait for HTC to provide an update??

elbatross · 6th August 2012, 03:06 PM

Quote:

Originally Posted by MEAKU15

i've got a question, let say the latest RUU file on htcdev is 1.57.707.2 but your phone version is 1.57.707.3, how on earth are you to proceed to unlock your bootloader, i've search for many days now and i can't find an answer or do i just have to wait for HTC to provide an update??

Same problem here mate.
Rooted a Desire, Galaxy S2 and a Galaxy S3 before. But this a hard one.

ethancottier · 2nd September 2012, 04:54 PM

Just thought you might wanna add that people with software version 1.33 can't upgrade their HBOOT with the HTCDev RUU :/ they need to install the asian rom 1.57 with a goldcard

I had to do that unfortunately before I got anywhere :/