AAHK S-OFF failure, phone bricked. Help appreciated!

[CrazyTom49]

Hi all,

I've been planning to install jellytime on my all stock desire hd.

I ran aahk, it downgraded to frodo fine, and installed clockworkmod recovery.
I proceeded to open up cwm once it had finished, wipe the data, cache, and sd card, as recommended. Copied the jellytime_rc30.zip file onto the phone, then ran the update utility in cwm.

It said it ran successfully, so I rebooted the phone, only to find it hangs at the white screen with htc logo.

Opening up hboot, and it appears the phone is still s-on:

ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.03.02.6_M
eMMC-boot
Apr 12 2011,00:55:45

So I tried running the aahk again. However, it couldnt detect the device in hboot or fastboot (usb debugging not enabled etc). I tried opening up cwm on the phone with it plugged in, and it gets to the main menu, but running "1 - Hack Ace" gives the following output:


[Select and press Enter]1


ls: /sdcard/PD98IMG.zip: No such file or directory
rm: can't remove '/sdcard/PD98IMG.zip': No such file or directory
* server not running *
111 KB/s (4359771 bytes in 38.133s)
/sbin/sh: pm: not found
121 KB/s (19240 bytes in 0.155s)
92 KB/s (4564992 bytes in 48.025s)
99 KB/s (3737600 bytes in 36.650s)
91 KB/s (557962 bytes in 5.931s)
30 KB/s (9796 bytes in 0.309s)
128 KB/s (572752 bytes in 4.353s)
128 KB/s (134401 bytes in 1.025s)
36 KB/s (13968 bytes in 0.377s)
Setting up for Froyo restore....
124 KB/s (3002368 bytes in 23.456s)
113 KB/s (2998272 bytes in 25.834s)
110 KB/s (284576 bytes in 2.512s)
95 KB/s (284668 bytes in 2.918s)
1 file(s) copied.
Kernel version is Froyo... Using psnueter to temproot...
Failed to set prot mask (Inappropriate ioctl for device)
* server not running *
************* PROBLEM PROBLEM PROBLEM ************
** SD card is either damaged or not mounted.
** Are you sure Charge Only mode is DEFAULT
** and not just switched on? READ THE EFFEN MANUAL
************* PROBLEM PROBLEM PROBLEM ************
ECHO is off.
ECHO is off.
Press any key to continue . . .


I've also tried installing the hboot windows drivers, as the device was only detected as android 1.0 in device manager:
But "adb devices" still gives no output when in hboot (fastboot detects the device though). Can't post the link to the drivers I installed; if anyone has any for hboot 0.85.0024 I can try those.

Any ideas? I'm slightly frustrated that I've managed to mess up my phone, and I don't know how to return it to how it was (Gingerbread with Sense 3.0).

If more information is needed then just let me know. Any help would be greatly appreciated!

 

[bananagranola]

So, you are S-ON with CWM installed, and hanging on the HTC splash? Was your boot loader unlocked? It sounds like it was...

If so, you can't run AAHK; I believe it only works on locked phones. You need to fastboot flash the ROM's boot.img each time you flash a ROM. Or you could relock and run AAHK.

And it doesn't sound like a messed boot loader from flashing a froyo on top of a phone shipped with gingerbread, but just for fun, what did your phone ship with and what version of android was it on when you ran AAHK?

 

[yumm91]

sounds like he is running the aahk only once.. when it is downgraded, instead of running it again to s-off and everything, he installed the cwm right away and trying to flash custom rom..
Sent from my Desire HD using xda app-developers app

 

[bananagranola]

sounds like he is running the aahk only once.. when it is downgraded, instead of running it again to s-off and everything, he installed the cwm right away and trying to flash custom rom..
Sent from my Desire HD using xda app-developers app

But if he's only downgraded without an unlocked boot loader, how is he installing CWM? I'm not sure, but I think that's not possible...

 

[glevitan]

Hi all,

I've been planning to install jellytime on my all stock desire hd.

I ran aahk, it downgraded to frodo fine, and installed clockworkmod recovery.
I proceeded to open up cwm once it had finished, wipe the data, cache, and sd card, as recommended. Copied the jellytime_rc30.zip file onto the phone, then ran the update utility in cwm.

It said it ran successfully, so I rebooted the phone, only to find it hangs at the white screen with htc logo.

Opening up hboot, and it appears the phone is still s-on:

ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.03.02.6_M
eMMC-boot
Apr 12 2011,00:55:45

So I tried running the aahk again. However, it couldnt detect the device in hboot or fastboot (usb debugging not enabled etc). I tried opening up cwm on the phone with it plugged in, and it gets to the main menu, but running "1 - Hack Ace" gives the following output:


[Select and press Enter]1


ls: /sdcard/PD98IMG.zip: No such file or directory
rm: can't remove '/sdcard/PD98IMG.zip': No such file or directory
* server not running *
111 KB/s (4359771 bytes in 38.133s)
/sbin/sh: pm: not found
121 KB/s (19240 bytes in 0.155s)
92 KB/s (4564992 bytes in 48.025s)
99 KB/s (3737600 bytes in 36.650s)
91 KB/s (557962 bytes in 5.931s)
30 KB/s (9796 bytes in 0.309s)
128 KB/s (572752 bytes in 4.353s)
128 KB/s (134401 bytes in 1.025s)
36 KB/s (13968 bytes in 0.377s)
Setting up for Froyo restore....
124 KB/s (3002368 bytes in 23.456s)
113 KB/s (2998272 bytes in 25.834s)
110 KB/s (284576 bytes in 2.512s)
95 KB/s (284668 bytes in 2.918s)
1 file(s) copied.
Kernel version is Froyo... Using psnueter to temproot...
Failed to set prot mask (Inappropriate ioctl for device)
* server not running *
************* PROBLEM PROBLEM PROBLEM ************
** SD card is either damaged or not mounted.
** Are you sure Charge Only mode is DEFAULT
** and not just switched on? READ THE EFFEN MANUAL
************* PROBLEM PROBLEM PROBLEM ************
ECHO is off.
ECHO is off.
Press any key to continue . . .


I've also tried installing the hboot windows drivers, as the device was only detected as android 1.0 in device manager:
But "adb devices" still gives no output when in hboot (fastboot detects the device though). Can't post the link to the drivers I installed; if anyone has any for hboot 0.85.0024 I can try those.

Any ideas? I'm slightly frustrated that I've managed to mess up my phone, and I don't know how to return it to how it was (Gingerbread with Sense 3.0).

If more information is needed then just let me know. Any help would be greatly appreciated!

OK, first, frodo is in the lord of the rings and not in HTC phones. He is busy trying to get rid of Sauron, so I don't think he is downgrading your phone...

Second, the kit does not downgrade to froyo, if it did you would be probably saying that your phone takes ages to boot. Your kernel version is actually froyo, but probably not your Android version.

Third, downgrading does not mean that you are S-OFF, rooted and SuperCIDed. Just means that you are downgraded. As the manual says, you need to re run the Hack kit again after the downgrade.

Fourth, It is not possible to flash CWM being S-ON unless you have you bootloader unlocked, but in that case, it is impossible to run the Hack Kit, so there is something there that makes no sense.

Fifth, you need to flash a RUU to get a working phone again. You probably have the goldcard in your device, but not sure thou until you try flashing a RUU.

Last, You can run the Hack Kit from fastboot usb..and from there flash a RUU. Boot in fastboot, plug the phone (you should see fastboot usb in red in the phone, if you see HBOOT USB PLUG, then press power), open a cmd as admin in the location where hack kit is and then type:

hack-ace.cmd fastboot

When the menu pops up, choose to flash a RUU. Any of those should flash with no problem if your goldcard is fine...:good:

 

[CrazyTom49]

For now I've run the official RUU from shipped-roms.com just so I can have a working phone again, so its now back to stock without cwm etc. I'll give this another go this evening anyway.

I had run the aahk twice; once to downgrade to a froyo rom (which booted into android fine), and again to install cwm and root the phone, s-off etc (the kit needs froyo in roder to root). The second run wiped android and installed cwm, just didn't s-off apparently.

I've never unlocked the bootloader using htc-dev before. How would I go about making sure it is locked?

Also, I'm assuming I couldnt runt he aahk again because I wiped the partition that tells it to have usb-debugging on. How can I avoid doing that again? Ideally I'd like to be able to run it without an HTC ROM installed, as obviously this is wiped when running the kit.

Finally, I could run it from linux this time, as I've got a dual boot set up. Would that help in this situation? (It is recommended in the kit manual)

Thanks for the responses

 

[glevitan]

For now I've run the official RUU from shipped-roms.com just so I can have a working phone again, so its now back to stock without cwm etc. I'll give this another go this evening anyway.

I had run the aahk twice; once to downgrade to a froyo rom (which booted into android fine), and again to install cwm and root the phone, s-off etc (the kit needs froyo in roder to root). The second run wiped android and installed cwm, just didn't s-off apparently.

I've never unlocked the bootloader using htc-dev before. How would I go about making sure it is locked?

Also, I'm assuming I couldnt runt he aahk again because I wiped the partition that tells it to have usb-debugging on. How can I avoid doing that again? Ideally I'd like to be able to run it without an HTC ROM installed, as obviously this is wiped when running the kit.

Finally, I could run it from linux this time, as I've got a dual boot set up. Would that help in this situation? (It is recommended in the kit manual)

Thanks for the responses

Ok, there are some things that make no sense. Do you mind if I have a look at your device over teamviewer?? you can not flash CWM with out being S-OFF...it wouldn't write a partition...

 

[CrazyTom49]

Ok, there are some things that make no sense. Do you mind if I have a look at your device over teamviewer?? you can not flash CWM with out being S-OFF...it wouldn't write a partition...

What's teamviewer? And I dont have CWM any more, its all back to stock

 

[bananagranola]

What's teamviewer? And I dont have CWM any more, its all back to stock

Teamviewer lets him see what's on your computer.

So. Step by step. What, exactly, with details, have you done so far?

 

[glevitan]

What's teamviewer? And I dont have CWM any more, its all back to stock

Teamviewer is a remote control program so I can connect to your PC. I need to check what is going on with the Hack kit...

 

[CrazyTom49]

Teamviewer lets him see what's on your computer.

So. Step by step. What, exactly, with details, have you done so far?

Currently, the desire hd is back to how it was before I started messing around with it. That is, running stock gingerbread with sense 3.0, bootloader locked (AFAIK), S-ON, no CWM recovery installed. HBOOT output is:

ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Sep 7 2011, 19:06:24

Running "adb devices" with the phone on hboot lists no devices, although windows device manager shows it as "Android Phone > Android ADB Interface" (possibly because I've got the wrong windows drivers installed for hboot).

Running "fastboot devices" with the phone on fastboot lists it as shown, and device manager shows it as "Android USB Devices > My HTC".

Running "adb devices" with the phone booted into android (usb debugging on / charge only), lists the device as expected, and device manager shows it as "Android USB Devices > My HTC".


The phone is a couple of years old, initially shipped with froyo, but was upgraded OTA to gingerbread (the frodo confusion is because I've just been setting up an htpc with xbmc 12, aka frodo).

I wanted to upgrade it to run the jellytime android 4.1 rom. This meant I needed to install clockworkmod recovery and root the phone.

I used aahk as detailed in the first post to do this, running it once initally to successfully downgrade the phone to a froyo rom. I booted into this just long enough to ensure 'usb debugging' was enabled and charge only, then ran the aahk again to do the root process.

It appeared to work ok, so I used cwm to "wipe data/factory reset", "wipe cache", and "wipe sdcard". I then mounted the sdcard using cwm, and copied the jellytime rom zip onto the sd card. I then used cwm to "install zip from sd card", which cwm apparently completed without any problems.

I rebooted the phone, and tried to run the jellytime rom, but it just hung at the white htc boot screen (left it for at least 5 minutes). Rebooting the phone into hboot, I noticed it was still listed as S-ON at the top.

I then tried to run aahk (for a third time) from windows, with the phone in hboot and fastboot modes, only to have it fail to detect it both times (note that I didn't know you had to run "hack-ace.cmd fastboot" at the time).
I opened up cwm on the phone, and aahk detected it when in this menu. However, the hack kit failed to run correctly, giving the output detailed in the first post.

At this point I posted the OP above.

I tried running the option to return the phone to stock RUU using aahk again. However, this also didn't work correctly (I didnt make a note of the output, sorry).

Getting a bit worried at this point, I downloaded the .exe utility from shipped-roms.com to return the phone to stock. This also couldnt detect the phone from hboot, but it did from fastboot, and took about 45 minutes to return the phone to the state it is in currently (where everything seems to work as before).


Unless there is a particular reason why not, I'm going to try running the aahk from linux twice again this evening; hopefully it will all work as intended this time

 

[CrazyTom49]

Also I'd rather not give remote access to someone I don't know, sorry. I'll go through any steps you want to talk me through though if it will help

EDIT: I think I was in the same situation as this guy - http://forum.xda-developers.com/showpost.php?p=36016162&postcount=12 - but can't get adb working from hboot, so couldn't run aahk again as he was advised

 

[CrazyTom49]

Ok, ran aahk again in windows, seemed to work this time.

Currently has android 2.3.3 installed and working ok, sense 2.1.
Kernel 2.6.35.10-gd2564fb
Baseband version 12.56.60.25U_26.10.04.03_M

hboot gives:

***** AAHK *****
ACE PVT ENG S-OFF RL
HBOOT-0.85-2425
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Apr 12 2011,00:55:45

CWM seems to be working as before too. Not sure why exactly it didnt work last time, I haven't done anything differently. Although clockworkmod recovery is now v5.0.2.7, I'm fairly sure it was 4.something last time I tried it.

So just to confirm, to install jellytime, I "wipe data/factory reset", "wipe cache partition", "wipe sdcard" (optional). Then copy the rom zip file onto the sd card from windows, and choose "install zip from sd card" in cwm?

 

[CrazyTom49]

Cracking stuff, got jellytime running fine too. Not sure what went wrong with the aahk previously, but glad I've got it sorted now.

I've also just realised that I did actually do a CWM backup before I wiped everything the previous run, i.e. immediately after aahk had finished running for the second time, when I thought it was successful. If anyone's interested in what went wrong for bug testing purposes or whatever, let me know and I'll stick it on dropbox to share (the whole backup folder is ~700mb though)

 

[Gregory Ernest]

peanut butter question time

Cracking stuff, got jellytime running fine too. Not sure what went wrong with the aahk previously, but glad I've got it sorted now.

I've also just realised that I did actually do a CWM backup before I wiped everything the previous run, i.e. immediately after aahk had finished running for the second time, when I thought it was successful. If anyone's interested in what went wrong for bug testing purposes or whatever, let me know and I'll stick it on dropbox to share (the whole backup folder is ~700mb though)

I ran the aahk, wiped and loaded the new JellyTime ROM on without a hitch, have superuser, goldcard, everything looked ACE (hehe), but:

my Euro DHD phone, which claims to be quad/dual band, is only pulling EDGE here in North America, so I thought I'd drop the Inspire 4G baseband into it, only to find (WHAT!) that the device is still S_ON... so my question is: HOW HAVE I GOTTEN THIS FAR without actually achieving S_OFF and what to do at this point?

i.e. am I running the AAHK [or alternatively just doing the linux command roll] again, and why?

 

[bananagranola]

Did you unlock the bootloader and then run AAJK on top of it? AAHK doesn't work on an unlocked bootloader.

 

[glevitan]

I ran the aahk, wiped and loaded the new JellyTime ROM on without a hitch, have superuser, goldcard, everything looked ACE (hehe), but:

my Euro DHD phone, which claims to be quad/dual band, is only pulling EDGE here in North America, so I thought I'd drop the Inspire 4G baseband into it, only to find (WHAT!) that the device is still S_ON... so my question is: HOW HAVE I GOTTEN THIS FAR without actually achieving S_OFF and what to do at this point?

i.e. am I running the AAHK [or alternatively just doing the linux command roll] again, and why?

European DHD will never have 3G in the states as it has different frequencies from the Inspire 4G and that is a hardware issue and not software.

 

[Gregory Ernest]

... I think that's not possible...

I did run AAHK twice (first to downgrade firmware, then to finish the unlock process), and everything went according to plan. That is what is troubling - the device was TOTALLY opened, Goldcarded, flashed in the new bootloader - and now it appears to have been reversed somehow. It shouldn't be possible, right?

I just need a way to crush this last problem before I get RAW POWER, but figuring out how it happened is the first step. Any ideas are very welcome.

--

To make it perfectly clear: I want to flash a new baseband (the one what fires the Inspire4G's radio) and have found that I need to REGAIN S_OFF; I am running JellyBean JT4.2 v 6.1 and the tools I see are for Froyo etc. so I am here with outstretched hands. thanks!

 

[Gregory Ernest]

GEEEE fi

... That is what is troubling - the device was TOTALLY opened ... and now it appears to have been reversed somehow. It shouldn't be possible, right?

Unless of course I selected to return S_ON before I flashed my JT_42 on, but I can't imagine being that stoopid, seeing as the Effing Manual clearly states that step is for stock and not mod... going to run gfree on it's lonesome - DOES THIS SOUND ADVISABLE? My baseband is still vers. 26.03.02.26, but will the tool have any issues with my Kernel (3.0.62_JellyTime_42_R5_g8e08b63-dirty) ??

(This is loads of fun, btw)

 

[heywheelie]

When did you run aahk? It hasn't worked for 3 days.