Search results

You are running an application in the background that kills the ADB server of the AAHK2. Locate and terminate it before starting AAHK2.

RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65. 6 0.29_26.14.04.28_M_release_225512_rooted.zip

This explains a lot! Run the AAHK2 with USB-Debugging on from Android System - not fastboot. Then run the main script - not the "...fastboot" script and select '1'. Read the instructions you get from the script very carefully! I'm looking forward for your progress!

So, do that and try again. If that doesn't work (again), attach the complete output (in spoiler tags) and I'll help you personally upcoming week!

I've read that before, but as long as the bootloader has the "***UNLOCKED***" at the top - it can't work...

Relock it with "fastboot oem lock". Then give it another try!

Execute the command in fastboot mode, copy the output to a text editor, search and remove both strings. Then post the output. If you see the output, you'll understand!

The very first line at the top in hboot and all green written lines. Punctilious. Mask your Serial and IMEI before posting it. (Just curiosity: Where are you from?)

Bafteam Please post your HBoot-Status and anonymized output of fastboot getvar all.

Then I see no problems and you won't loose anything. It only flashes an other modded hboot.

The only thing is to disable BOS via the "SkipBOSDescriptorQuery" registry entry to get the fastboot mode working with new Windows versions (8.1 and higher). Switch the DHD into fastboot mode. When your Windows runs the fastboot mode driver correctly (check device manager), just run the...

In many cases (software depending) you will definitively need it In the other cases: If anything doesn't work as intended and the vol down button has a hardware defect - you have a brick. I wouldn't try it without a working button...

It's only temporary disabled. After a reboot, it's enabled as before. That's very rare. :) Just report, if something's down and you need it. I don't check it - but if requested - of course will upload them again! Right. That's doing the same. I only recommend using the µSD method to make...

I recommend using "old" µSD cards <=8GB.

Just use another µSD card. The one you're using is not compatible obviously. Format it, restore your device using that one and the correct ruu and give it another try.

ze7zez The vendor id of the DHD definitely is "0FF0" - not "0FFF". So hacktrix2006 was right. (Checked with Microsoft Message Analyzer and proven to work.) Phiber

Flash the RUU contained in this Archive via HBoot: re_twrp_2.8.6.1_ra_26_17_14_11_m.zip (It's from my KitKat-Kit I made for a german forum.) Notice that the old AROMA-Installer used by some old ROMs is not compatible with the new TWRP versions. Phiber

Checked it - Links are all up.

Copy the "PD98IMG.zip" as ZIP-File to the root folder of the sd card and switch into hboot. The hboot should find the file and ask you to update automatically.

Your device is unlocked via htcdev. You have to prepare your device via the option 'h' in main menu before you can start the unlock process. Phiber

The unlock method performed by AAHK2 removes the sim-lock, too.

The AAHK2 is just for the Desire HD/4G. That's the successor of yours... Phiber

This is how to solve the issue from windows 8.1 up: In "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags" create the key "0BB40FF00100". In this key create a binary value named "SkipBOSDescriptorQuery" with value "01 00 00 00". Reconnect DHD and it will be recognized correctly. Phiber

Your problem is: The temproot fails. (citation: "[-] Hellions with BLUE flames !") I'd unlock the device via htcdev first and then let the AAHK2 prepare it for another try. (Choose the prepare option in main menu.) Then it should work as intended. Phiber

bullghost Could you add a command line based (print contents & extract) usage?

Post the full script output in a spoiler.

I don't think so but can't guarantee that because Kingston won't be the real manufacturer. In this case (Kingston isn't known as brand with bad quality), I'd give it a try. Phiber

Just have a look at #1585. Phiber

Mergescripts I published my scripts at GitHub under MIT license: lg-mergescripts Phiber

I wrote a merging script today, which handles both image files but I not yet figured out what the second part contains. Can you describe that a little bit more? ---------- Post added at 01:14 AM ---------- Previous post was at 01:01 AM ---------- Update: The bytes are necessary! Unmerged...

Merging? robalm: I had a look at the cust.img. When I extract the stock kdz, I get two files belonging to it, similar to the unmerged system.img. Your cust.img consists of one of the source files - don't they have to be merged, too? Phiber

Great! And less work for me... :D

The radio downgrade fails, whyever - let's have a date... :) Phiber

Ah! Now all makes sense. :D After the first run - the script did a downgrade only (and told you that). Then you had to run the script again to let it do the *real* magic. Maybe that's your "issue"... Have another try (maybe twice again) and report or post the output if it isn't successful. Phiber

Which one is flashed doesn't matter but since you've still a custom recovery remaining on the device, something's definitely wrong! :p That's flashed only to get a compatible rom state to get the '1' working correctly. Because your device is branded, the PD4 is the only one which can be flashed...

You don't have to do that. When this step would have been successful, there is no custom recovery or root. That's because you should try option 'h' first. Just to make sure, that there's no htc unlock. You're right, that tries to flash the unbranded GB2 and does a relock. Conflicts can't...

Choose option 'h' first, then retry. When it'll be unsuccessful again, post the script output of option '1'.

Then you probably didn't use the recovery for flashing. That's bad - never do that! Write a PM to me with your time zone and when you have time for recover.

The AAHK2 flashed TWRP as custom recovery for you. You use that to flash custom ROMs and Gapps if needed. Wipe system and data partition first, then install the custom ROM. Phiber

There is definitely something wrong with your connection. Just try another cable and don't touch the device while processing!

That's the right next step. If that fails, we'll need a remote date. :) I'm curious about it. Phiber

Exactly! The md5 checksum is verified before writing it to the sd card. After mounting the sd card or connecting the card reader, choose "Format..." in the context menu of the drive. There you can choose capacity, file system and allocation unit size. The allocation unit size has to be set to...

The hboot doesn't recognize the files on your sd card. In most cases, it's just the wrong file system of the sd card. Mount it, format it with FAT32 (4KB sector size), safe remove, unmount. Then try again. Everything else is already checked by the script. Phiber

That's a complete weird behavior of your hboot - S-Off devices should accept the zips and allow flashing specific partitions - no matter if there's a htcdev-unlock or not. I want to have a look at it on my own remotely. If you want, contact me via PM with the city you come from and your local...

That's the next thing: Unlocking the device via HTCdev and repeating the steps.

Just try the rest of the commands.

Of course you have to be in fastboot mode before starting with the fastboot commands. Then the 'reboot-bootloader'-command will work, too. It was self-evident for me - sorry for that. :eek:

You won't need to do anything other than I posted. There's no reason to run the aahk, too. [emoji6] Phiber

Weird infos... Download "HTC WWE 3.12.405.1 with ROOT - GPS FIX(Radio: 12.65.60.29/26.14.04.28 M)" from OP. Extract twice and place the "hboot_7230_Ace_2.00.2728_110907.nb0" in the folder, containing your fastboot.exe. Then execute:fastboot flash hboot hboot_7230_Ace_2.00.2728_110907.nb0 and...

I think, it's a bit offtopic - but why not... The DHD is nearly unbrickable. If there's no hardware fault, it can be recovered by user without problems as long as hboot is intact. Let's start: First try to get fastboot access: Switch into fastboot mode, install drivers, connect usb and post...