Develop Bugs

[Q] DHD android most beginner know how

Finally I got my DHD, the time where everything is rolling out, from perm root, to recovery...
The good thing, I'm very happy with my DHD, the bad thing, I'm not familiar yet with android system.
I revised a lot of android and DHD threads, and I faced many new terminologies that belong to android where I like to have explanation for each.
Please let me understand the following issues the beginner way, allowing me to maybe make a simple guide answers for most new android users coming from winmo.
I-General questions:
1-DHD should be multitouch. Then why games like Gameloft are not multitouch like on ipod or iphone?
2-What are the buttons combinations for the different operations like hard reset & boot loader?
3-I read that android can’t share internet via USB for those with no WIFI at home or office. As I knew it’s due to ad hoc issue so it's impossible to get internet via USB cable from desktop. When I plugged my DHD, I choose internet pass through and I got internet on my DHD, is it a new feature implemented in DHD only, or is it a 2.2 update that will work on other devices?
4-Winmo gives the choice to install applications on either the device or SD card. Android have nothing like this, so when I install applications, where do they go, and is there a workaround to put everything on SD card, or maybe give choice to where to install?
5-My DHD comes with an 8 GB mini SD card where there are some folders and files on it. Are they necessary to run the system, what if I replaced this card with another formatted one, what will happen, or what if I format this card?
II-System info:
1-Baseband version (is it like the radio in winmo?)
2-Kernel version (is it one kernel for the entire device? Does it updates like rom or like radio?) e.g. (kAmMa's OC&GOV&BFS Kernel - Performance and Stability. Is this a rom or just kernel that will update some parts of the rom without losing data on the device?)
3-Build number (is this the firmware?) e.g. (i have 1.32.405.3 CLxxxxxx release-keys, what does release keys means?)
4-Software number (or this is the firmware?)
III-OTA ACE with radio:
1-OTA (is it a rom, does it mean over the air, if yes what does that mean? Can we update OTA with no root?)
2-ACE
On winmo (HD2), I know HSPL will let me unlock ISPL so I can install any custom or cooked rom, languages and applications...
For android, as far as I know there is no one click solution. From what I understand to do everything in android with no restrictions u need to do the followings:
IV-How to root Desire HD install h-boot (S-Off) and Clockwork recovery?
Please identify which one is just a process that we do it once in order to unlock it, which is a boot loader run application and which one is an android application:
1-Root (is it what gives access to the root folders of the system that maybe are hidden by default or encrypted?)
2-Hboot
3-S-off (is it security off? if yes, it is security off for what? installing applications, or read write to some encrypted partitions?)
4-Clockwork (is it something necessary to do in order to install custom rom, no adds, backup and so on, or is it something totally independent and related only to unlock the speed of the CPU where you can leave it intact if you won’t play with the CPU speed?)
5-Recovery (from what I understand it seems that recovery is a system shell command like dos or more like bios for android but named as recovery, what can we do with the recovery other than recovering the device?)
6-Recovery image (is it a rom backed on the form of image and provided by developers, so we can install it directly on the device using only the recovery shell?)
V-More things to know about:
1-What is adb?
2-What is busybox?
2-What is fast boot?
3-What is eMMC write?
4-What is ext2 or ext4 (is it like the partition type of the SD card based on UNIX system? if yes, why should we change or modify this ext)
5-Rom manager (is it a desktop pc application or android device application? is it something like I can put the RUU file of the rom on my SD card and using the rom manager I can install the rom from there, nothing more nothing less?)

vuedesprit said:
Finally I got my DHD, the time where everything is rolling out, from perm root, to recovery...
The good thing, I'm very happy with my DHD, the bad thing, I'm not familiar yet with android system.
I revised a lot of android and DHD threads, and I faced many new terminologies that belong to android where I like to have explanation for each.
Please let me understand the following issues the beginner way, allowing me to maybe make a simple guide answers for most new android users coming from winmo.
I-General questions:
1-DHD should be multitouch. Then why games like Gameloft are not multitouch like on ipod or iphone?
2-What are the buttons combinations for the different operations like hard reset & boot loader?
3-I read that android can’t share internet via USB for those with no WIFI at home or office. As I knew it’s due to ad hoc issue so it's impossible to get internet via USB cable from desktop. When I plugged my DHD, I choose internet pass through and I got internet on my DHD, is it a new feature implemented in DHD only, or is it a 2.2 update that will work on other devices?
4-Winmo gives the choice to install applications on either the device or SD card. Android have nothing like this, so when I install applications, where do they go, and is there a workaround to put everything on SD card, or maybe give choice to where to install?
5-My DHD comes with an 8 GB mini SD card where there are some folders and files on it. Are they necessary to run the system, what if I replaced this card with another formatted one, what will happen, or what if I format this card?
II-System info:
1-Baseband version (is it like the radio in winmo?)
2-Kernel version (is it one kernel for the entire device? Does it updates like rom or like radio?) e.g. (kAmMa's OC&GOV&BFS Kernel - Performance and Stability. Is this a rom or just kernel that will update some parts of the rom without losing data on the device?)
3-Build number (is this the firmware?) e.g. (i have 1.32.405.3 CLxxxxxx release-keys, what does release keys means?)
4-Software number (or this is the firmware?)
III-OTA ACE with radio:
1-OTA (is it a rom, does it mean over the air, if yes what does that mean? Can we update OTA with no root?)
2-ACE
On winmo (HD2), I know HSPL will let me unlock ISPL so I can install any custom or cooked rom, languages and applications...
For android, as far as I know there is no one click solution. From what I understand to do everything in android with no restrictions u need to do the followings:
IV-How to root Desire HD install h-boot (S-Off) and Clockwork recovery?
Please identify which one is just a process that we do it once in order to unlock it, which is a boot loader run application and which one is an android application:
1-Root (is it what gives access to the root folders of the system that maybe are hidden by default or encrypted?)
2-Hboot
3-S-off (is it security off? if yes, it is security off for what? installing applications, or read write to some encrypted partitions?)
4-Clockwork (is it something necessary to do in order to install custom rom, no adds, backup and so on, or is it something totally independent and related only to unlock the speed of the CPU where you can leave it intact if you won’t play with the CPU speed?)
5-Recovery (from what I understand it seems that recovery is a system shell command like dos or more like bios for android but named as recovery, what can we do with the recovery other than recovering the device?)
6-Recovery image (is it a rom backed on the form of image and provided by developers, so we can install it directly on the device using only the recovery shell?)
V-More things to know about:
1-What is adb?
2-What is busybox?
2-What is fast boot?
3-What is eMMC write?
4-What is ext2 or ext4 (is it like the partition type of the SD card based on UNIX system? if yes, why should we change or modify this ext)
5-Rom manager (is it a desktop pc application or android device application? is it something like I can put the RUU file of the rom on my SD card and using the rom manager I can install the rom from there, nothing more nothing less?)
Click to expand...
Click to collapse
Congratulations. You win the "most questions asked in a single post" award.
Sent from my Desire HD using XDA App

That is a ridiculous amount of questions, and the thread is in completely the wrong area of the forum. I'm sure you'd find the answer to pretty much all your questions if you looked hard enough, but to answer the one about multi-touch. It is multi touch and all the games I've played from your example 'Gameloft' are multi-touch, so I don't know what you're smoking buddy, but ease off.

1. Inb4 "search".
2. Wrong forum.
3. No really, try searching. At least 30% of that is googleable.
Sent from my Desire HD using XDA App

Ok guys, thank you all for your replies, and yes I knew that a war and flames will go on here, but seriously if you think this is ridiculous or newbie or most dumb questions, do not turn the way of the thread or flame me, my intentions are to make this as a one small guide for most new androids functions, it's not a bad thing to do, in fact I will learn as much as other new users here, no one is asked to answer all those ridiculous questions, just answer what you know about, guys please take it seriously and easy, saying look harder will not help the thread, it may help me personaly, but be sure that I did a lot of search, and it will not hurt to put everything in one place, and as you can see, I answered most of the questions up to what I gathered, you can correct me about my answers, put your thoughts or not answer at all, but please be constructive here, and if you all think that i'm in the wrong forum, or asking too much, or asking ridiculous questions, please moderator feel free to do what you think is better for the forum.
Sorry guys for bothering you. Thank you for your response.
N.B.: just to be more accurate, I tried the prince of persia pre installed on the phone by the dealer, and it was not multi touch, so you cant walk and use any of the right actions at same time.

@vuedesprit: Good thread, and thanks for taking all the criticism from the more experienced users.
@all chimers chiming the "use search, wrong forum" tune: c'mon guys, there's at least 2 of us reading this thread going, it's about time all this information got consolidated into one place! The easier it is to find this information, the easier it would be for more of us to get engaged in the process and thus further development, enhancement and adoption.
While our "friendly" mod is doing his best to keep the forums clean, they're as fragmented as ever and from time-to-time, it becomes necessary to consolidate the information into a single thread. I'm sure most of you started some place too and remember the time not so long ago when it was difficult to find even the most basic info? I think by sharing your knowledge, you will gain a much better following and the platform will gain much better adoption.
My 2 cents worth anyways...I've had my DHD for 3 days now and I too am struggling to perform even the most basic tasks.

We really need a questions and answers sub forum

Fair enough, maybe my first comment was a bit rash, but I didn't mean to appear rude. I shall try to answer some questions here:
GENERAL.
1. From my own experience all games advertised as multitouch are exactly that. I don't know about the version of PoP that you have installed from carrier, but I do find that odd.
2. Hard reset is a little perverse with the new "fastboot" hibernation feature that HTC have implemented. You have to go to MENU>SETTINGS>APPLICATIONS and disable "fastboot" (this is where confusion may arise as this is not the bootloader fastboot that allows images to be flashed)!! Now when you hold down the power button and get the option to power off, you will properly power off the phone. Next if you hold "VOLUME DOWN" and "POWER" buttons you will reboot into HBoot, from here the VOLUME UP/DOWN keys navigate the menu and POWER selects menu options.
3. Not sure about this one.
4. Since the release of FROYO you can go to MENU>SETTINGS>APPLICATIONS>MANAGE APPLICATIONS then select any app and move to either SD or to phone memory.
5. The folders on the SD card are mostly generated by the phone when you first insert it. The user guide and HTC sync software are there to move onto your PC for safe keeping. If you insert a freshly formatted SD card, the phone will make fresh folders such as DCIM for pictures, etc...
SYSTEM INFO.
1. Baseband is radio software.
2. Kernel is the linux kernel that is running below Android, this can be updated separately from the main ROM, radio etc. HOWEVER CAUTION IS ADVISED AS CERTAIN KERNELS WILL NEED NEW MODULES FOR HARDWARE TO FUNCTION CORRECTLY as you will see from the wifi modules bundled with the OC kernels.
3. Build number pertains to HTC's internal software version classification (some are built specific for carriers) they are generally released via RUU (ROM Update Utility aimed at windows) or OTA (Over The Air update received on phone [again sometimes carrier specific]). Release keys pertains to the fact that the firmware has been signed by HTC (I think).
4. Software number, basically as above.
OTA ACE with Radio.
1. As Above.
2. ACE: internal HTC name for Desire HD (also reportedly known as "SPADE")
ROOT DESIRE HD ETC.
Most of what you have written is pretty much correct.
MORE THINGS TO KNOW ABOUT.
1. http://developer.android.com/guide/developing/tools/adb.html
2. http://www.busybox.net/about.html
3. http://android-dls.com/wiki/index.php?title=Fastboot
4. eMMC write basically means that you can write to the internal phone (normally protected) memory such as /SYSTEM, this is what S-OFF allows you to do whenever you want. However, the modules that allow the ENG HBoot image to be flashed are what really accomplish this in the first place so theoretically you could just run that module every time you wanted to write to /SYSTEM but that would become very tedious very quickly. I can't really explain further, as I don't have the knowledge.
5. EXT2 or EXT4 are filesystem structures just like FAT, FAT16, FAT32, NTFS, HFS+ etc, EXT4 is newer and more advanced than EXT2 and therefore is more efficient. (kinda general but you get the idea. NEWER=BETTER)
6. ROM manager, find this in the android market, it is free, you install it on your phone and with the addition of clockworkmod it gives you the ability of flashing ROMs etc. USE WITH CAUTION.
I hope that this answers or clarifies most of what you have asked or said, please feel free to cut and paste any of this info into your first post so that we can actually consolidate this.
P.S. I too am a complete android noob and this is my first android phone, I have picked this info up mainly from this forum so all credit for information goes to XDA-DEVELOPERS.COM and not me.
Cheers,
Dok

berek9999 said:
congratulations. You win the "most questions asked in a single post" award.
Sent from my desire hd using xda app
Click to expand...
Click to collapse
+1111111111^2

1-DHD should be multitouch. Then why games like Gameloft are not multitouch like on ipod or iphone?
Click to expand...
Click to collapse
an application must support multitouch and other gestures. eg, opera doesnt support multitouch (ie you cant zoom in and out) but the browser that comes with the DHD does.
2-What are the buttons combinations for the different operations like hard reset & boot loader?
Click to expand...
Click to collapse
boot loader = turn phone off. then, volume down + power on.
4-Winmo gives the choice to install applications on either the device or SD card. Android have nothing like this, so when I install applications, where do they go, and is there a workaround to put everything on SD card, or maybe give choice to where to install?
Click to expand...
Click to collapse
application must support running from /sdcard. When you install an app go to settings -> Applications -> manage applications. From here you can uninstall or move apps to the sdcard. Bear in mind if you have not rooted your phone you may not be able to uninstall some apps (eg amazon reader).
5-My DHD comes with an 8 GB mini SD card where there are some folders and files on it. Are they necessary to run the system, what if I replaced this card with another formatted one, what will happen, or what if I format this card?
Click to expand...
Click to collapse
some application data is stored on your sdcard, and apps are stored here if you have moved them by using the steps above. if you change sd cards this info is unavailable to the app but the app should still work. any settings you had need to be redone.
2-Kernel version (is it one kernel for the entire device? Does it updates like rom or like radio?) e.g. (kAmMa's OC&GOV&BFS Kernel - Performance and Stability. Is this a rom or just kernel that will update some parts of the rom without losing data on the device?)
Click to expand...
Click to collapse
the kernel is not part of a rom or the radio. It is stored in the boot partition in the emmc (where fastboot(aka hboot)/splash images/boot(kernel)/recovery/ are all stored). It is generally included with but not required by a custom rom. ie, a custom rom builder may choose to include a specific kernel with his rom but it is not mandatory.
1-OTA (is it a rom, does it mean over the air, if yes what does that mean? Can we update OTA with no root?)
Click to expand...
Click to collapse
yes, you can do OTA HTC updates. but, there are no custom (non signed) updates delivered OTA. An unrooted rom will not be able to flash non signed updates (or roms).
How to root Desire HD install h-boot (S-Off) and Clockwork recovery?[/U][/B]
Click to expand...
Click to collapse
there is a good thread here - http://forum.xda-developers.com/showthread.php?t=841076.
Please identify which one is just a process that we do it once in order to unlock it, which is a boot loader run application and which one is an android application:
1-Root (is it what gives access to the root folders of the system that maybe are hidden by default or encrypted?)
Click to expand...
Click to collapse
android application. eg, visionary+.
2-Hboot
Click to expand...
Click to collapse
hboot is also known as bootloader. it is the white screen with the skating androids when you do the volume-down + power combination when switching on your phone.
3-S-off (is it security off? if yes, it is security off for what? installing applications, or read write to some encrypted partitions?)
Click to expand...
Click to collapse
s-off stands for security off. you can check the status by doing the volume-down + power combo. At the top it will either say s-on or s-off. If you have s-on then your bootloader (hboot), boot (kernel) /system (android) and recovery (eg clockworkmod) partitions are all read only.
4-Clockwork (is it something necessary to do in order to install custom rom, no adds, backup and so on, or is it something totally independent and related only to unlock the speed of the CPU where you can leave it intact if you won’t play with the CPU speed?)
Click to expand...
Click to collapse
clock work is the recovery partition. you have 3 possible options before loading android when you do the volume-down + power on combo. hboot, then either fastboot or recovery. fastboot and recovery are both ways to flash images to your phone although through different ways (fastboot uses the fastboot command on your pc to send the image, recovery uses .zip's on your /sdcard). clockworkmod is a custom recovery image which you need to flash after achieving s-off. it's also where nandroid backups can be done. if you select recovery before doing this you will get the phone + red triangle icon. thats the stock recovery. the clockworkmod is the green menu selection one.
5-Recovery (from what I understand it seems that recovery is a system shell command like dos or more like bios for android but named as recovery, what can we do with the recovery other than recovering the device?)
Click to expand...
Click to collapse
see above.
6-Recovery image (is it a rom backed on the form of image and provided by developers, so we can install it directly on the device using only the recovery shell?)
Click to expand...
Click to collapse
clockwork mod can backup your phone's partitions (boot/userdata/system) so that if you mess up installing a rom you have a way to recover. this is known as a nandroid backup.
1-What is adb?
Click to expand...
Click to collapse
adb is android debug something. It is a way to send commands to the android operation system from your pc (either windows or linux). eg, you can run a single command, or run a shell (terminal session). it is part of the android sdk under tools.
2-What is busybox?
Click to expand...
Click to collapse
busybox is a single executable whihc runs under the android OS that provides standard linux commands (eg, ls, rm, cd) to any application. it is so that a script writer does not need to know the partiticular rom you have and then cater for it, but only that you have a certain version of busybox. eg, busybox 1.17.1 provides the same commands whether it is on a leedroid rom or a cyanogen rom.
2-What is fast boot?
Click to expand...
Click to collapse
fastboot is a way to flash images to your phone. it is accessed via hboot. you need the fastboot exe from the htc developer site. it can flash the boot (kernel), recovery (eg clockworkmod) and the radio (i think).
3-What is eMMC write?
Click to expand...
Click to collapse
the emmc is the storage device which holds hboot, fastboot, recovery, /system, /userdata and (not sure about this one) radio. when you switch on your phone the emmc is read-only due to the s-on flag being set by hboot. you need to flash the engineering hboot which does not set s-on when you switch your phone on.
4-What is ext2 or ext4 (is it like the partition type of the SD card based on UNIX system? if yes, why should we change or modify this ext)
Click to expand...
Click to collapse
ext2 and ext4 are linux file system types. eg, windows is ntfs, linux has ext2/3/4 and others.
5-Rom manager (is it a desktop pc application or android device application? is it something like I can put the RUU file of the rom on my SD card and using the rom manager I can install the rom from there, nothing more nothing less?)
Click to expand...
Click to collapse
rom manager is an android app available on the market place to help with the flashing process. it can flash recovery partitions (as long as your phone is s-off), make nandroid backups (as long as you have clockworkmod & s-off). it can also flash custom roms. it does not flash these from within the android OS (afaik) but it will reboot into (not sure on this one) the recovery partition and leaves it instructions to flash a particular rom.

This thread is amazing!!
We had a lot threads like this in the HTC Blackstone Board of pocketpc.ch....
Hope to get more threads like this in every device category....
Thumbs up
Perhaps Threadstarter can write the answers in the first post...??

50chickens said:
an application must support multitouch and other gestures. eg, opera doesnt support multitouch (ie you cant zoom in and out) but the browser that comes with the DHD does.
boot loader = turn phone off. then, volume down + power on.
application must support running from /sdcard. When you install an app go to settings -> Applications -> manage applications. From here you can uninstall or move apps to the sdcard. Bear in mind if you have not rooted your phone you may not be able to uninstall some apps (eg amazon reader).
some application data is stored on your sdcard, and apps are stored here if you have moved them by using the steps above. if you change sd cards this info is unavailable to the app but the app should still work. any settings you had need to be redone.
the kernel is not part of a rom or the radio. It is stored in the boot partition in the emmc (where fastboot(aka hboot)/splash images/boot(kernel)/recovery/ are all stored). It is generally included with but not required by a custom rom. ie, a custom rom builder may choose to include a specific kernel with his rom but it is not mandatory.
yes, you can do OTA HTC updates. but, there are no custom (non signed) updates delivered OTA. An unrooted rom will not be able to flash non signed updates (or roms).
there is a good thread here - http://forum.xda-developers.com/showthread.php?t=841076.
android application. eg, visionary+.
hboot is also known as bootloader. it is the white screen with the skating androids when you do the volume-down + power combination when switching on your phone.
s-off stands for security off. you can check the status by doing the volume-down + power combo. At the top it will either say s-on or s-off. If you have s-on then your bootloader (hboot), boot (kernel) /system (android) and recovery (eg clockworkmod) partitions are all read only.
clock work is the recovery partition. you have 3 possible options before loading android when you do the volume-down + power on combo. hboot, then either fastboot or recovery. fastboot and recovery are both ways to flash images to your phone although through different ways (fastboot uses the fastboot command on your pc to send the image, recovery uses .zip's on your /sdcard). clockworkmod is a custom recovery image which you need to flash after achieving s-off. it's also where nandroid backups can be done. if you select recovery before doing this you will get the phone + red triangle icon. thats the stock recovery. the clockworkmod is the green menu selection one.
see above.
clockwork mod can backup your phone's partitions (boot/userdata/system) so that if you mess up installing a rom you have a way to recover. this is known as a nandroid backup.
adb is android debug something. It is a way to send commands to the android operation system from your pc (either windows or linux). eg, you can run a single command, or run a shell (terminal session). it is part of the android sdk under tools.
busybox is a single executable whihc runs under the android OS that provides standard linux commands (eg, ls, rm, cd) to any application. it is so that a script writer does not need to know the partiticular rom you have and then cater for it, but only that you have a certain version of busybox. eg, busybox 1.17.1 provides the same commands whether it is on a leedroid rom or a cyanogen rom.
fastboot is a way to flash images to your phone. it is accessed via hboot. you need the fastboot exe from the htc developer site. it can flash the boot (kernel), recovery (eg clockworkmod) and the radio (i think).
the emmc is the storage device which holds hboot, fastboot, recovery, /system, /userdata and (not sure about this one) radio. when you switch on your phone the emmc is read-only due to the s-on flag being set by hboot. you need to flash the engineering hboot which does not set s-on when you switch your phone on.
ext2 and ext4 are linux file system types. eg, windows is ntfs, linux has ext2/3/4 and others.
rom manager is an android app available on the market place to help with the flashing process. it can flash recovery partitions (as long as your phone is s-off), make nandroid backups (as long as you have clockworkmod & s-off). it can also flash custom roms. it does not flash these from within the android OS (afaik) but it will reboot into (not sure on this one) the recovery partition and leaves it instructions to flash a particular rom.
Click to expand...
Click to collapse
Thank you very much.

[Tutorial][Marvelc]How To Solve Common Marvelc Issues

Marvelc Problem Solving​We all have problems with our Marvelc, so why isn't there a guide for it? There is.
If you're having issues, check out my guide at http://teamblueridge.com/marvelc-problem-solving/ for how to fix the most common issues.
You don't have to live with a hard-to-manage Marvelc anymore.

Changelog:
May 24, 2012 10:12 PM EDT
Added a link to vbhtt's tutorial for solving different brick types.
July 19, 2012 8:04 AM EDT
Revised guide to say that all Marvelc HBOOTs can be S-OFF'd.
August 7, 2012 3:48 PM EDT
Revised to say how to fix <remote: not allowed>
Explain issues with Three-Vibe Brick
August 7, 2012 4:59 PM EDT
Link to guide on Team BlueRidge site.

Three Vibe Brick
So far, no 100% guaranteed method has been found to cure the infamous three-vibe brick. Your phone is presently in Qualcomm Diagnostics Mode
Click to expand...
Click to collapse
I have posted a tutorial to unbrick a wfs, and i also posted how to get out of the three vibe brick. I don't know if it really works (because i don't have a marvelc) but a user has reported it working.

vbhtt said:
I have posted a tutorial to unbrick a wfs, and i also posted how to get out of the three vibe brick. I don't know if it really works (because i don't have a marvelc) but a user has reported it working.
Click to expand...
Click to collapse
I apologize. I heard that in some cases, not even that could fix it. I meant to say that there is not a fix that works in 100% of scenarios (my three-vibe could not be rectified without the use of JTAG, which I did not want to get into here.)

kalaker said:
I apologize. I heard that in some cases, not even that could fix it. I meant to say that there is not a fix that works in 100% of scenarios (my three-vibe could not be rectified without the use of JTAG, which I did not want to get into here.)
Click to expand...
Click to collapse
There's no need to apologise my friend I was not trying to tell you that you are wrong, i was trying to help you!!!!

vbhtt said:
There's no need to apologise my friend I was not trying to tell you that you are wrong, i was trying to help you!!!!
Click to expand...
Click to collapse
Oh! I understand that! I was just trying to provide a common method that I had read. I understand you weren't saying I was wrong. I was actually about to add something about your tutorial, but I had another project I was working on.
Yes, my goal is that this can be a place to help most Marvelc users solve most of their problems with as many alternatives as possible while still being fairly noob-friendly.
Thank you for reminding me of your tutorial as it slipped my mind while I was writing this in the beginning!

Hi I read your thread and I can some what understand it Hopefully you can shed some light on my situation My marvelc htc wfs is stuck at the white htc screen and won't go any farther I've flashed and reflashed roms ive always formatted data and other necessary items like I should. I did flash one rom that worked but wasn't happy with it, it worked fine but was going for cm7 now that I've read at least 100 posts I come to understand its not to reliable anyway and was just wanting anything to work stock rom would be great I understand I may need to update my CWM my current version is 5.0.2.6 I've read 5.0.2.8 was more stable for the wfs but I have no clue how to flash it when I currently have no rom on my phone. this is what my hboot says currently
***unlocked***
marvelc evt1 ship s-off RL
HBOOT-1.09.0000
Microp-0354
Radio-0.94.00.0824
Hopefully the info will help you out. any help would be so grateful thanks

CoLlisiionZz said:
Hi I read your thread and I can some what understand it Hopefully you can shed some light on my situation My marvelc htc wfs is stuck at the white htc screen and won't go any farther I've flashed and reflashed roms ive always formatted data and other necessary items like I should. I did flash one rom that worked but wasn't happy with it, it worked fine but was going for cm7 now that I've read at least 100 posts I come to understand its not to reliable anyway and was just wanting anything to work stock rom would be great I understand I may need to update my CWM my current version is 5.0.2.6 I've read 5.0.2.8 was more stable for the wfs but I have no clue how to flash it when I currently have no rom on my phone. this is what my hboot says currently
***unlocked***
marvelc evt1 ship s-off RL
HBOOT-1.09.0000
Microp-0354
Radio-0.94.00.0824
Hopefully the info will help you out. any help would be so grateful thanks
Click to expand...
Click to collapse
What you need to do is download ClockWork Mod 5.0.2.8 from http://download.clockorkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvelc.img and then rename it to recovery.img. If you're on Windows, put it into the same directory as your ADB and fastboot commands. Next, you'll need to put your phone in fast boot mode. Go into HBOOT and choose "Fastboot" by scrolling with the volume keys and selecting with the power key.
Connect your phone to your computer.
Next, depending on the OS of your computer, launch Command Prompt (Windows) or Terminal (Linux/Mac). Navigate to the directory with recovery.img. Now type: fastboot flash recovery recovery.img and then power off your phone when it's done.
Now boot into recovery. Go to HBOOT and choose recovery. Now, get on your computer and find a ROM that you like (something fairly stable). Download it. Find Simon's super wipe. Download it.
Connect your phone to your computer (if you removed it earlier).
In recovery, scroll to Mounts and Storage. Go to USB Connect or something similar (it will be near the bottom). Then on your computer, place your desired rom and the super wipe. Remove the phone from your computer and choose "Go back" on your phone. Go back to the main menu.
Backup.
Flash the super wipe. Then flash your ROM.
Go back to the main menu and reboot.
Sent from my NookColor using XDA

Great!! thanks this seems legit I will try this as soon as I get to my PC uhm I have windows btw and have no clue how to put the cwm into my adb / fastboot directory but I will search more about it when possible thanks for your help

Well, if you're on Windows, you should have a directory like C:\Android\ or something like that.
If you're on a Mac just do:
Code:
fastboot flash recovery /path/to/recovery.img
If you want to have the file anywhere on Windows, you still need to have fastboot somewhere and then do the same command I just typed above.
For more instructions, follow the instructions in the guide under "I can't flash a custom recovery"

Ok In your tutorial you say "go to the folder "tools" and launch "android". Download "Android SDK Platform-Tools" " when I try to launch android nothing happens only a black cmd: box will appear for a split second then goes away. The android I'm trying to launch in the tools folder is a Windows Batch File is this the correct file?

CoLlisiionZz said:
Ok In your tutorial you say "go to the folder "tools" and launch "android". Download "Android SDK Platform-Tools" " when I try to launch android nothing happens only a black cmd: box will appear for a split second then goes away. The android I'm trying to launch in the tools folder is a Windows Batch File is this the correct file?
Click to expand...
Click to collapse
Do you have Java installed? http://www.java.com/en/download/manual.jsp
Also, you should get the JDK: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1637583.html
See if that works.

kalaker said:
Do you have Java installed? http://www.java.com/en/download/manual.jsp
Also, you should get the JDK: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1637583.html
See if that works.
Click to expand...
Click to collapse
I downloaded java and the JDK file installed etc
Tried unzipping the sdk file again then went to the android tried to launch and same result I'm on (windows 7 64x bit).
I downloaded something when I was searching forums that kind of sounded like the file I'm suppose to be downloading the platform tools but there called android tools instead here's the files in it below
adb
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot
Do you think this is the same thing? I've flashed roms on the Optimus V before so I am a little familiar with the platform tools but when i downloaded them last time I just have to go into SDK manager.

CoLlisiionZz said:
I downloaded java and the JDK file installed etc
Tried unzipping the sdk file again then went to the android tried to launch and same result I'm on (windows 7 64x bit).
I downloaded something when I was searching forums that kind of sounded like the file I'm suppose to be downloading the platform tools but there called android tools instead here's the files in it below
adb
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot
Do you think this is the same thing? I've flashed roms on the Optimus V before so I am a little familiar with the platform tools but when i downloaded them last time I just have to go into SDK manager.
Click to expand...
Click to collapse
That's what you want. Move them into a folder at the root of your hard drive (C:\) called "Android". (C:\Android\)

Okay great!! I went ahead and tried doing some command prompts and this is what I typed
I'm in the android file it currently says
C:\Android>
I tried typing "adb reboot bootloader" and it says
*daeon not running. starting it now on port 5037 *
*daemon started successfully *
error: device not found
now my phone is connected to my PC its in fastboot mode it says in red on my phone FASTBOOT USB so I know for sure it's connected is there something wrong?

CoLlisiionZz said:
Okay great!! I went ahead and tried doing some command prompts and this is what I typed
I'm in the android file it currently says
C:\Android>
I tried typing "adb reboot bootloader" and it says
*daeon not running. starting it now on port 5037 *
*daemon started successfully *
error: device not found
now my phone is connected to my PC its in fastboot mode it says in red on my phone FASTBOOT USB so I know for sure it's connected is there something wrong?
Click to expand...
Click to collapse
You're already in the bootloader. Fastboot is the bootloader, or at least part of it. You have use fastboot commands in fastboot.

kalaker said:
You're already in the bootloader. Fastboot is the bootloader, or at least part of it. You have use fastboot commands in fastboot.
Click to expand...
Click to collapse
Okay that's what I kind of thought so I tried typing fastboot flash recovery recovery.img
and it says
error: cannot load 'recovery.img'
it is placed in the same directory as the tools are too.
---------- Post added at 06:10 PM ---------- Previous post was at 06:05 PM ----------
Okay nvm I tried something and it worked!!!
I went and re downloaded your CWM on your tutorial and deleted the one I renamed and didn't rename it this time just kept it the way it was I then tried flashing it and success I'm now going to reboot my hboot and see if it worked but also I was searching forums and google but could not come across simmons super wipe... I will keep looking though but if you have time maybe throw a link on a post for me but thanks for helping me I hope it goes smooth from now on

CoLlisiionZz said:
Okay that's what I kind of thought so I tried typing I was searching forums and google but could not come across simmons super wipe... I will keep looking though but if you have time maybe throw a link on a post for me but thanks for helping me I hope it goes smooth from now on
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1598143
I'm glad to hear you got it working!

A thought just occured that I may have overlooked in my many (unsuccessful) attempts of curing a sent-to-me 3 vibe...
Correct me if I'm wrong on this, but sd needs to be made a goldcard; so that PG76IMG.zip will auto-load...
Been a long time since I attempted but I don't remember if I checked the sd to make sure it was goldcard'd. I will go charge it up and test this new theory tomorrow (still sitting in a side-basket at work). Sometimes my mind takes a minute to put ALL the pieces together
Rob
Sent from my Marvelc using Tapatalk 2

insink71 said:
A thought just occured that I may have overlooked in my many (unsuccessful) attempts of curing a sent-to-me 3 vibe...
Correct me if I'm wrong on this, but sd needs to be made a goldcard; so that PG76IMG.zip will auto-load...
Been a long time since I attempted but I don't remember if I checked the sd to make sure it was goldcard'd. I will go charge it up and test this new theory tomorrow (still sitting in a side-basket at work). Sometimes my mind takes a minute to put ALL the pieces together
Rob
Sent from my Marvelc using Tapatalk 2
Click to expand...
Click to collapse
Right, a Goldcard (unless one is S-OFF or ENG) will be required. However, achieving a goldcard requires ADB access to your phone. (The Simple GoldCard tool reads a file in /proc/*/*/ I believe to get the CID required for goldcard.) Now, ADB access is quite difficult with a bricked phone as you cannot boot into Android (or recovery) and to get S-OFF you would need to borrow the HTC Wildfire S (it MUST be a Wildfire S) to get the goldcard required.
Even with what I just said, depending on how bad your phone is bricked (Flashing a GSM RUU, for example), you may have a 100% bricked radio, thus resulting in an entirely bricked HBOOT not allowing you flash a PG76IMG.zip.
Another idea I have is that the Marvel is a PG761**** for the model number, and an incorrect RUU is the most common brick for Marvelc. What may be an issue is that the Marvelc is a PG762**** model number. The current files we have for un-bricking are Marvelc, but the android-info.txt for modelid says PG762000, therefore a GSM HBOOT (especially a locked, RUU HBOOT) would not take that file as it is for Marvelc.
What I think would be necessary is: a goldcard + a PG76IMG.zip with a GSM android-info.txt, but Marvelc radio, ROM, HBOOT, etc.
This is my idea on how we may need to do this. However, as the GSM HBOOT cannot get S-OFF without XTC-Clip which we can't use due to a lack of SIM card slot.
To get a 100% working-in-all-methods 3-Vibe Brick Recovery Method, we are waiting for the people in the S-OFF thread to get a full software S-OFF. However, even with that, we may still have issues...
I have spent a lot of time thinking about this, actually. (I'm a planner; not a dev :crying: so I can't be of much help with the dev part.) However, if it ever becomes a Team BlueRidge project to fix this type of brick (or a project by any group) I will be happy to plan (but not test just yet).
Since now we're moving into a very difficult and not-so-noob-friendly as I am intending for this thread to be, it may be a good idea to either start a new brainstorming thread or to PM or IRC or something.
Anyway, those are my thoughts.

[Q] HTC Desire HD

I have been true some web sites and have not found a solution for this problem. I have a HTC Desire HD, sow called HTC ACE, I got it from Orange UK, Android Version 2.3.5, HTC Sence Version 3.0 With Software 3.13.61.5, and I would be pleased to debrand this machine, but always come to the same decision I cannot duet yet, I would like to receive some suggestions on how to debrand it, I will try everything and after that right everything I have done until be successful, thank's

PauloMHAlmeida said:
I have been true some web sites and have not found a solution for this problem. I have a HTC Desire HD, sow called HTC ACE, I got it from Orange UK, Android Version 2.3.5, HTC Sence Version 3.0 With Software 3.13.61.5, and I would be pleased to debrand this machine, but always come to the same decision I cannot duet yet, I would like to receive some suggestions on how to debrand it, I will try everything and after that right everything I have done until be successful, thank's
Click to expand...
Click to collapse
Before you do anything — Make a backup
Don't forget to back up your data. If you have synced the device with a Google account, then the contacts, calendar, Gmail, & select other Google-related data will not be lost and will come back after the next sync. However, you should backup anything you want to keep that is not stored on the SD card:
SMS/MMS messages,
Call Log,
Bookmarks,
Applications; use Titanium Backup or the Astro File Manager, for example,
Any application data not on the SD card.
It would also be a good idea to backup everything stored on the SD card in the rare case the SD card must be formatted to resolve any major problems.
MyBackup Root, SMS Backup & Restore, and Call Backup & Restore are all free applications that can assist with backing up your data.
Downgrade to an exploitable Firmware
AT&T Inspire 4G: Firmware Downgrade: Froyo, Gingerbread
HTC Desire HD: Firmware Downgrade: Froyo, Gingerbread
Rooting the HTC Ace
WARNING: ROOTING THE HTC ACE WILL VOID THE WARRANTY.
Before you begin, if VISIONary is installed on the HTC Ace, uninstall it before continuing.
You will need ADB on the computer to root the HTC Ace and to flash the necessary files for radio S-OFF. Follow the Android SDK guide, to get the ADB shell on the computer.
Download busybox, the ClockworkMod Recovery, the Engineering HBoot, gfree 0.7, psneuter, root_psn, Superuser package:
busybox: Download
md5: 25c5db694c987995909cc3166d4f01b0
ClockworkMod Recovery: Download
md5: 072a643b0aba983a4b9994db0e113c5e
Engineering HBoot: Download
md5: b2c8834905bfa2349f5223077493140a
gfree 0.9: Download
md5: 2dd45594b1ecb084401d428432f87010
psneuter: Download
md5: 89c2dec8d72d87b4c669f44dd31c8d17
root_psn: Download
md5: c8fe38ef55eb8951def9ff17b2eb99c1
Superuser package: Download
md5: 43d9a40b63e916635d5ad7ca32433fab
Unzip the zip files and copy the contents to the same folder as adb (the /platform-tools folder within the Android SDK folder).
Connect the HTC Ace to the computer via USB.
Make sure USB debugging is enabled on the HTC Ace by checking Settings » Applications » Development » USB debugging.
On the computer, open terminal and run the following commands:
adb push busybox /data/local/tmp/
adb push gfree /data/local/tmp/
adb push hboot-eng.img /data/local/tmp/
adb push psneuter /data/local/tmp/
adb push recovery-clockwork-5.0.2.3-ace.img /data/local/tmp/recovery.img
adb push root_psn /data/local/tmp/
adb push su /sdcard/
adb push Superuser.apk /sdcard/
adb shell
chmod 755 /data/local/tmp/*
/data/local/tmp/psneuter
NOTE: You will drop out of the shell after this command. Restart the shell using:
adb shell
cd /data/local/tmp
./gfree -f -b hboot-eng.img -y recovery.img
As it is very important that the hboot was installed correctly gfree calculates md5sums of the partition. It will calculate the following 3 checksums
md5sum #1 - checksum of partition 18 before the installation
md5sum #2 - checksum of the hboot image that should be installed
md5sum #3 - checksum of partition 18 after the installation
The messages that you what to see are either/or
md5sum #1 == md5sum #2 - the hboot image is already installed -> skipping installation
md5sum #3 == md5sum #2 - the hboot image was successfully installed -> OK!
If you get a different error message you should run for help at then DO NOT REBOOT and join #G2Root on Freenode for further help.
If gfree worked correctly continue with:
./root_psn
sync
reboot
The HTC Ace is now rooted with S-OFF, the Engineering HBoot & the ClockworkMod Recovery. Continue to the next section.
Flashing CyanogenMod
If the {{{device}}} has been rooted, unlocked, etc. through steps other than the method described above or running a custom ROM other than CyanogenMod and you are having issues flashing or booting CyanogenMod, it is recommended the {{{device}}} be returned to stock & start over with the full instructions provided above.
Method via Recovery
Download the [[Devices Overview#{{{device}}}|latest version]] of CyanogenMod.
Optional: Download the Google Apps for the device.
Place the CyanogenMod update.zip file on the root of the SD card.
Optional: Place the Google Apps .zip on the root of the SD card also.
Boot into the ClockworkMod Recovery.
Once the device boots into the ClockworkMod Recovery, use the side volume buttons to move around, and either the power button or the trackball to select.
Optional: Select backup and restore to create a backup of current installation on the {{{device}}}.
Select the option to Wipe data/factory reset.
Then select the option to Wipe cache partition.
Select Install zip from sdcard.
Select Choose zip from sdcard.
Select the CyanogenMod update.zip.
Optional: Install the Google Apps by performing steps 7 - 9 again and choosing the Google Apps update.zip.
Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, and select the Reboot system now option. The {{{device}}} should now boot into CyanogenMod.
Method via ROM Manager
Launch RomManager.
Optional: Choose the first option in the app, Flash ClockworkMod Recovery to update to the latest version.
Select the Download ROM option from the main menu in the ROM Manager.
Select the CyanogenMod option, and then choose the latest version of CyanogenMod from the menu.
Optional: When you select the latest version of CyanogenMod, check the Google Apps option.
Once the ROM is finished downloading, it asks if you would like to Backup Existing ROM and Wipe Data and Cache.
If Superuser prompts for root permissions check to Remember and then Allow.
The {{{device}}} will now reboot into the recovery, wipe data and cache, and then install CyanogenMod. When it's finished installing it will reboot into CyanogenMod.
:crying:
I have try that was another fail lol...

PauloMHAlmeida said:
I have been true some web sites and have not found a solution for this problem. I have a HTC Desire HD, sow called HTC ACE, I got it from Orange UK, Android Version 2.3.5, HTC Sence Version 3.0 With Software 3.13.61.5, and I would be pleased to debrand this machine, but always come to the same decision I cannot duet yet, I would like to receive some suggestions on how to debrand it, I will try everything and after that right everything I have done until be successful, thank's
Click to expand...
Click to collapse
GUIDE] Downgrade from 3.13 (Sense 3.0) roms
This guide is for phones shipped with froyo and updated to the 3.x firmware! For phones shipped with gingerbread (even the lower versions) please read attn1's posts in this thread!
With the Sense 3.0 upgrade HTC patched against fre3vo, so we can no longer temproot to use misc_version on that firmware. Lucky us, a new exploit was issued @rootzwiki. This exploit was tested at #g2root (freenode) and was able to temproot a 3.13.161.3 firmware version.
The usual disclaimer applies: Everything you do is your responsibility, no one can be held accountable for the state you put yourself and/or your phone into.
If you meet troubles search for help at IRC: freenode, #g2root
make sure your phone is in 'charge only' mode and the 'fast boot' feature is turned off.
What you need:
tacoroot
misc_version NOTE: you need THAT version of misc_version. Earlier versions would not work.
flashgc for a goldcard
1.32 PD98IMG.zip
put all files in your platform-tools directory (unzip misc_version and tacoroot.sh)
Code:
adb push tacoroot.sh /data/local/tmp/tacoroot
adb push misc_version /data/local/tmp/
adb push flashgc /data/local/tmp/
adb push PD98IMG.zip /sdcard/
NOTE: the last command will take a long time
After all files are pushed you have to run tacoroot:
Code:
adb shell
chmod 755 /data/local/tmp/*
/data/local/tmp/tacoroot --setup
This command will reboot the phone to recovery. Once it is done, use vol up/power then choose 'reboot' to reboot the phone. After it boots (it will bootloop, that's expected):
Code:
adb shell
/data/local/tmp/tacoroot --root
this command will kick you out of adb shell, so we need to return there and see the # sign of root access, after which we can change the main version and create a goldcard:
Code:
adb shell
cd /data/local/tmp
./misc_version -s 1.00.000.0
./flashgc
./tacoroot --undo
After these commands are done, the phone should get rebooted by tacoroot. After it boots, boot to bootloader to flash the 1.32 firmware:
Code:
adb reboot bootloader
Once in bootloader, use the vol buttons to go to 'bootloader' and the power button to execute. The rom will flash. Enjoy!
Credits:
the tacoroot team
skorgon for flashgc
Donate to RevSkills and EFF!
fail againnnnnn:crying:

PauloMHAlmeida said:
I have been true some web sites and have not found a solution for this problem. I have a HTC Desire HD, sow called HTC ACE, I got it from Orange UK, Android Version 2.3.5, HTC Sence Version 3.0 With Software 3.13.61.5, and I would be pleased to debrand this machine, but always come to the same decision I cannot duet yet, I would like to receive some suggestions on how to debrand it, I will try everything and after that right everything I have done until be successful, thank's
Click to expand...
Click to collapse
use this
http://forum.xda-developers.com/showthread.php?t=1377119

For the last few days I have try new software
Z4root No chance another fail...

for debrand use latest RUU, WWE version.. no branded
for rooting use advanced ace hack kit

The Advanced Ace Hack Kit – for HTC Desire HD and HTC Inspire
failed..........

new Advanced Ace Hack Kit system
I just found a new chance and I'm trying it
with new Advanced Ace Hack Kit system, I found it at http://tau.shadowchild.nl/attn1/?p=74
was Posted on July 26, 2012
The Advanced Ace Hack Kit – for HTC Desire HD and HTC Inspire
AAHK will work on Inspires on AT&T’s latest ROM, 3.20.502.52 only after following the steps outlined here: http://tau.shadowchild.nl/attn1/?p=88 .
Warnings:
If your PC environment is not ready to run this kit, there is a good chance your device will not boot properly until you fix your PC or switch to another and re-run the hack kit from the partial boot. READ THIS ENTIRE POST and READ THE EFFEN MANUAL! There is no substitute for READING for COMPREHENSION
Do NOT use earlier versions Ace Hack Kit (12.x and lower) on Inspire or DHD devices shipped with Gingerbread.
Do NOT attempt to downgrade a Inspire or DHD shipped with Gingerbread with a Froyo RUU.
Do NOT attempt to install earlier ENG HBOOTs on these models. AAHK now has Hboots that safely support fastboot image flashing.
Doing this WILL severely degrade bootloader performance on Inspires and DHDs and causes issues trying to install RUUs. In other words, it WILL jam you up. (Note: Issue confirmed on later DHDs – ignore at your own risk).
Sense 3, including those with RELOCKED HTC BOOTLOADERS (NOTE: NOT UNLOCKED – MUST BE LOCKED OR RELOCKED) is auto-detected in hack step. Option is given to download a GB RUU and downgrade or abort. This WILL wipe data.
#include <std_disclaimer.h>
/*
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because you can’t tether. Please
do some research if you have any concerns about features included in this
TOOL before running it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
*/
(Disclaimer borrowed heavily from cyanogenmod)
Features:
COMPLETELY INTEGRATED/INVISIBLE GOLD CARD PROCESS
Custom AAHK Bootloaders support popular ENG S-OFF functions for both Sense 2 and Sense 3 partition layouts
Only ONE menu step – HACK ACE
No ROM downgrade required (only radio/kernel) for devices not running sense 3
The original ROM is retained (except when downgrade from Sense3-GB is required)
No wiping data for devices not running sense 3
Rom is fully functional (yes, inc wifi)
Fully rooted with insecure boot image (supports adb remount for rw system)
Busybox manager app installed
Radio S-Off, superCid & carrier sim unlock
Correct Radio is automagically restored for HSPA+ operation
Clockworkmod Recovery included
All known Inspire/DHD builds supported
Easy return to stock for SOME builds (See the Effen Manual – not all carrier RUUs are available)
Notes:
Please do NOT run the hack step if you are already S-OFF AND are running a custom ROM. It’s pointless, and while it won’t brick you, you can get jammed up a bit. This is for stock devices only.
You MUST read the ENTIRE EFFEN MANUAL in order to run the hack kit.
Do NOT try to run this from a VM – particularly VirtualBox. You WILL get jammed up and may wind up flashing an RUU to recover, losing data in the process.
After kernel downgrade – video is lost on boot – this is okay as adb is working and can be used to finish the process. If the process fails, it can be restarted once the PC environment is corrected. When the process completes successfully, everything is restored and fully working.
Youtube videos are neat demos, but they make poor guides. READ THE EFFEN MANUAL. “There is no substitute for reading for comprehension.” – GenePoole
Make sure you extract the hack kit to your pc maintaining the directory structure in the archive you downloaded. The docs will be in the root directory of the unarchived kit, as will the scripts. READ THE EFFEN MANUAL.
I can’t believe that so many people are asking where the effen manual is. THE EFFEN MANUAL IS IN THE EFFEN HACK KIT.
This kit should work fine on HTC Inspire and HTC Desire HD Software versions below 3.06.405.1 which require the radio/kernel downgrade before a root exploit is available.
Windows Prep:
IMPORTANT – disable all malware (Antivirus detection etc) detection before unarchiving the hack kit. Keep it off thoughout the hack kit processes. Many Windows malware detection programs report false positives, deleting or binding critical files required by the process.
IMPORTANT – Remove or disable all services and daemons you can, particulary anything Apple, blackberry, PDAnet, Microsoft Mobile, anything USB not required for this task, any resource hogs. Also disconnect all un-needed USB devices and USB HUBs.
Remove HTC Sync and drivers.
Only after completing the above steps, install the drivers contained in the Hack Kit (see the Effen Manual) BEFORE plugging in the phone.
Connect the phone to the computer via a USB port connected to the system board – not a front panel port or a hub or extention port.
Verify successful android device driver installation in device manager.
Issues during downgrade:
IMPORTANT: BEFORE SWITCHING FROM DISK DRIVE TO CHARGE ONLY MODE, ALWAYS EJECT THE SDCARD WITH PC SOFTWARE TO FLUSH WRITE BUFFERS AND AVOID CORRUPTING THE SDCARD.
model ID incorrect update fail – this is because your goldcard is not working.
READ THE EFFEN MANUAL. Reading is fundamental.
Download:
Note: AAHK filename uses ddmmyyyy naming convention.
aahk-11092012.zip
md5: 5727960aa167b305b8f3561ffbbb1360
viperbjk is with Revskills, and his contribution is key to finally allowing one step processing where a goldcard is required. The entire process is now one menu step. A second step will be required to clear your conscience –
DONATE to:
Revskills.
and/or
Electronic Frontier Foundation
Note: No money has been accepted for the AAHK or support of the AAHK by myself or anyone working with me on it.
If you have read this post and the effen-manual and get stuck during processing,
help is available in IRC at http://webchat.freenode.net/?channels= – aahkSupport
Yes, there are stupid questions.
Questions that will get you immediately kickbanned from the IRC channel with no further explanation:
Q: Do I need to flash a ROM after the hack kit is finished?
A: Kickban. The hack kit is a complete, one step process. If it finishes correctly, you are finished. What part of “fully functional” is vague?
Q: Do I need to flash a radio after the hack kit is finished?
A: Kickban. The hack kit is a complete, one step process. If it finishes correctly, you are finished. What part of “fully functional” is vague?
Q: The options menu has options to flash radios. Do I need to flash a radio?
A: Kickban. What part of “optional” is vague? This option is to make it easy for people who may have flashed another radio and want to flash back to these particular radios.
Q: Do I need to plug in the phone?
A: Kickban. If you know how to enable usb debugging without a USB connection, then I’ll change this policy. In the meantime, asking such a question just makes me think you have not read anything and/or have dedicated yourself to being an idiot.
Q: What’s the best ROM?
A: Kickban. The whole point of this is to give YOU control and allow YOU to decide. Yes, we prefer CM7 and I think it’s the only real Android choice available, but don’t ask us to think for you. If you don’t see that pretty much everything else is either ripped off or HTC Non-Sense, then you haven’t done your homework and that’s okay. Just don’t ask, because in the end, it’s YOUR choice.
Q: Facebook doesn’t work.
A: Kickban. This has nothing to do with anything but Facebook. Go ask Facebook, not us.
Q: I can’t find the pass key.
A: Kickban. Really? Then you did not really read the Effen Manual. If you really did, then you would not ask. Really.
Q: My phone won’t boot – how do I fix my HBOOT?
A: Kickban. We’ve been warning people not to flash Froyo Hboots (Including HTC ENG ones) on devices shipped with GB for going on a year now. If you do this and screw up, it’s not our fault and you’re on your own.
This IRC channel is for people who read, attempt and get stuck because of PC issues or an occasional bug introduced with a new feature. It’s not for people to troll those who dedicate their time for support without any compensation by asking a series of mindless, inane questions and observations for attention. We’re too busy for that – even if we have nothing to do. It’s beyond annoying and you will be kickbanned without warning. Read, search, think, try, then ask.
The people in #aahkSupport have been helping noobs without compensation for over a year now, with generally very good results and a generally good nature, despite being abused by some on almost a daily basis.
Thanks to:
Revskills for their fantastic gold card algorithym
GenePoole for the kickass android goldcard binary based on above
agrabren for fre3vo, the Gingerbread temproot used
scotty2 for finding the vold exploit and the author of psneuter
Guhl for misc_version and gfree
hyuh for misc_version revisions and Hboots with ENG features
jcase for taco root
shad0wf0x for his windows scripting contributions
ktilcu for DOC contributions
anthony1s for his review and unique perpective
neolobster for his generous file hosting
The > 150,000 downloaders of the hack kit, most of whom seem to get though it without issue.
and they have amazing feedback's, lets try it now....

sow far as I see he dues everything you just need to site back and wait, look's amazing.........
new Advanced Ace Hack Kit system
thanks for the new development!
let's see in a hour time how he dues lol

PauloMHAlmeida said:
sow far as I see he dues everything you just need to site back and wait, look's amazing.........
new Advanced Ace Hack Kit system
thanks for the new development!
let's see in a hour time how he dues lol
Click to expand...
Click to collapse
Well, don't forget that you also need to read the "effen manual!"

I have not forget to read it but is a fail....
thanks for telling me that but I found the solution for all S-ON HTC...
and for the Hboot lol
is a big journey I made on the last months, and I have put some staff all together and got it made lol
just wait for my next post how to duet....

look for my next post
There's no need to make the phone S-OFF (like some people say).

PauloMHAlmeida said:
look for my next post
There's no need to make the phone S-OFF (like some people say).
Click to expand...
Click to collapse
With S-ON your bootloader is locked.
And without ENG S-OFF you can't change the radio.
S-OFF is necessary for me
And btw... i don't know what you do..
But with the Hack Kit i've rooted about 15 DHDs in my circle of friends.
Some devices with problems. But after manually downgrade with RUU no problems at all.

I'm finish here Just look for my next publication Thanks

fr34kde said:
With S-ON your bootloader is locked.
And without ENG S-OFF you can't change the radio.
S-OFF is necessary for me
And btw... i don't know what you do..
But with the Hack Kit i've rooted about 15 DHDs in my circle of friends.
Some devices with problems. But after manually downgrade with RUU no problems at all.
Click to expand...
Click to collapse
There's no need to make the phone S-OFF (like some people say).
Disable fast/quick reboot (Settings » Power » Fastboot)
Download all
Fastboot commander.zip http://www.mediafire.com/download.php?xsu7c3m981o9gb8
Google.zip http://www.mediafire.com/download.php?cm9pdoh2g9mkgvb
Superuser-3.1.3-arm-signed http://www.mediafire.com/download.php?kzpbhq13jb085s8
Android ultimate toolbox pro http://www.mediafire.com/download.php?6m5w39zmb6ph8gq
Recovery.img http://www.mediafire.com/download.php?grl8wsjzxihhfwf
Update http://www.mediafire.com/download.php?dzkww8zaq7sxhae
Fastboot.bin http://www.mediafire.com/download.php?bhzth13p4kvow4v
Copy in to the root of your sd card after been formatted
Google.zip + Update.zip + Superuser-3.1.3-arm-signed.zip
On your pc create a new folder on C: and name it HTC for easy access and copy in to the folder
Recovery.img + fastboot binary
Install on your PC
Fastboot commander.zip + Android ultimate toolbox pro
Start rooting
Unlock bootloader: http://htcdev.com/bootloader/
Put the phone in Fastboot USB mode (Turn off, hold Volume Down + Power)
fastboot oem get_identifier_token
fastboot flash unlocktoken Unlock_code.bin (file from email)
Install ClockWorkMod recovery the recovery.img from my link our use android ultimate box to flash recovery
fastboot flash recovery recovery.img
Make a backup
Start clockworkmod recovery (Fastboot mode, Recovery)
Select backup and restore
Select backup
Go to your mobile start it as Fastboot and go to recovery
You go in to Clockworkmod Recovery V5.0.2.7 from the Ace Hack Kit
On the top is the menu with + and – buttons just scrool in to advanced and press power
Select “Wipe Dalvik Cache”
Then select “Wipe Battery Stats”
Then select “And go back”
Then select “Wipe data/Factory reset”
Then select “Wipe cache Partition” (Now you have cleaned all the old staf from your mobile)
Now let’s start rebuild the HTC
Select "apply update from sdcard"
Then select "Yes - install update.zip" to confirm
Then select "install zip from sdcard"
Then select “google.zip”
Then select "Yes - install google.zip" to confirm
Then select "install zip from sdcard"
Then select "su-3.0-efgh-signed.zip"
Then select "Yes - install su-3.0-efgh-signed.zip" to confirm
Then go back to your pc for the files you have download and unzip update and copy Boot.bin to the file you created C:\HTC
o Flash boot.img trough fastboot:
o fastboot flash boot boot.img
o Reboot
• Done
• You should have now a white screan from HTC for at least 5 minutes and after will sart the new room, just let it on for a couple minutes and you will see the sucess….
All my files are at http://www.mediafire.com/?al6dsdcd6c02f
Enjoy it, next I will say how to sort google play problem I found it easy lol…

PauloMHAlmeida said:
[....]
Unlock bootloader: http://htcdev.com/bootloader/
[....]
Click to expand...
Click to collapse
And thats the point.
You do what S-OFF does through HTC-Tool.
Now u unlocked the bootloader and your warranty is gone because your device is registered now.
Why should anyone go the complicated way if there is an easy way?

Firts have 2 types of waranty, 1st the manufactors warranty. That runs off 3 years after your purchase, 2nd the software warranty... And HTC have take off that point on the warranty, now you can unlock our relock the bootloader from your HTC with out lost of your warranty... By the way that's the reason HTC created HTC devoluppers web page...
And if you want to understand that just read all my post's. Changing our due hboot s-off make you lost warranty lol....
Sent from my HTC Desire HD A9191 using xda app-developers app

Unlocking Your Bootloader
HTC is committed to listening to users and delivering customer satisfaction. We have heard your voice and starting now, we will allow our bootloader to be unlocked for 2011 models going forward. We plan on releasing the updates that will allow you to unlock your bootloader in the coming months, please keep an eye on this website for more details on which devices will be adding this feature. We are extremely pleased to see the energy and enthusiasm from our fans and loyal customers, and we are excited to see what you are capable of. HTC eagerly anticipates your innovations.
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty. Please note that unlocking your bootloader does not mean that you will be able to unlock the SIM lock. Unlocking your SIM lock is at the discretion of your operator/carrier and is not part of the bootloader unlocking scope.
Our devices have been designed with our hardware and software specifications in mind and unlocking the bootloader will change the software and may cause unexpected side effects. It is impossible for HTC to ensure the proper functioning of your device after this. In the worst case scenario, it is possible that your device may be physically damaged due to overheating or the behavior of your device might be altered including, but not limited to, hearing aid compatibility (HAC) and specific absorption rate (SAR) values.
Some content on your device may also be invalidated and cannot be accessed any more because of invalid DRM security keys. This includes content that you may have purchased through a 3rd party vendor and through HTC. Furthermore, although you will still be able to receive updates to your device via FOTA (“firmware over the air”), we do not guarantee that updating your device via FOTA will not render your device unusable. Please understand that you will not be able to return your device to the original state and going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader. HTC bears no responsibility if your device is no longer usable afterwards.
HTC is committed to assisting customers in unlocking bootloaders for HTC devices. However, due to some of our carrier customers concerns, certain models with specific restrictions may not be able to be unlocked. Please refer to our list of supported devices to see if your device is eligible for unlocking the bootloader.
We strongly suggest that you do not unlock the bootloader unless you are confident that you understand the risks involved. This is a technical procedure and the side effects could possibly necessitate repairs to your device not covered under warranty. If you are still interested in unlocking the bootloader, and you understand the consequences both to your device and to your warranty, then you may refer to the following pages where we have provided the unlocking instructions.
Un lo c k Bo o tlo ad er
Unl oc k th e pos s ib ilit i es wit h to ta l cu s t omi zat io n
Unlock Bootloader
Frequently Asked Questions Preview Unlock Process
Supported Devices
Select “All other supported models” if you cannot find your phone in this list. Devices launched after 9/2011 will be shipped with the unlock capability. Please check back often for updates on the unlock status of additional devices.
------- Select Your Device ------
Beg i n Unl o ck Bo ot l o ad er
* Indicates HBOOT update required.
HTC is committed to assisting customers in unlocking bootloaders for HTC devices. However, certain models may not be unlockable due to operator restrictions. We continue to work with our partners on this, check back often for ongoing updates about unlockable devices.
Copyright © 2012 HTC Corporation. All rights reserved. Terms of Use Privacy Policy About HTCdev HTCDev Affiliates Follow Us Comments - Tell HTCdev what YOU want.

[Q] Help problem With Htc Desire Z Rooting

Looked over forum and could not see this problem talked about. And hope someone please can help?
Following last part of this guide:
"cyanogenmod.org/w/Install_CM_for_vision"
"1. As it is very important that the hboot was installed correctly gfree calculates md5sums of the partition. It will calculate the following 3 checksums
md5sum #1 - checksum of partition 18 before the installation
md5sum #2 - checksum of the hboot image that should be installed
md5sum #3 - checksum of partition 18 after the installation
2. The messages that you what to see are either/or
md5sum #1 == md5sum #2 - the hboot image is already installed -> skipping installation
md5sum #3 == md5sum #2 - the hboot image was successfully installed -> OK!
3. If you get a different error message then DO NOT REBOOT and join #G2Root on Freenode for further help.
4. If gfree worked correctly continue with: "./root_psn" "sync" "reboot"
Hboot image install ok and md5sum numbers confirm this (all other software and steps ok up to this point), but do not think I did step 4. HTC now will only boot to white screen with HTC on it.
And I can not talk to it with ADB shell. I can hold down Volume - & Power butter to get to "Hboot" and if I plug in USB at this point it is asking for Andriod 1 driver. Can anyone tell me how finish rooting from this point and move on to installing Android Open Kang Project (As wanted 4 ICE or similar open to suggestions).
Also seem I need to install ROM Manager app as Nandroid backup as will not work from ClockworkMod Recovery at the moment.

After flashing the new bootloader you essentially reformatted your system wiping out your os, right now flash a new ROM via recovery (no need for ROM manager right now, well ever really) follow this guide if your not sure what to do
http://forum.xda-developers.com/showthread.php?p=31249070
Be sure to thank rizzo izzo!
You also may consider changing your radio/recovery or hboot, see here if you do
http://forum.xda-developers.com/showthread.php?p=27796375
Sent from my Nexus 7 using xda premium

Sorted
demkantor said:
After flashing the new bootloader you essentially reformatted your system wiping out your os, right now flash a new ROM via recovery (no need for ROM manager right now, well ever really) follow this guide if your not sure what to do
http://forum.xda-developers.com/showthread.php?p=31249070
Be sure to thank rizzo izzo!
You also may consider changing your radio/recovery or hboot, see here if you do
http://forum.xda-developers.com/showthread.php?p=27796375
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks that worked fine. Did not want to go any further until I was sure I would not make things worse.

[FIX] FED-Patcher v7 (ForceEncrypt Disable Patcher)

Hello everybody,
I created a tool for the nexus 9 that gets rid of the ForceEncrypt flag in a generic way (meaning it should work no matter what rom you are on). It does that by patching the currently installed boot.img.
Background
The Android CDD (Compatibility Definition Document) suggests that all devices SHOULD enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. FDE comes at a price. Encryption takes time because some component has to de- and encrypt the stuff on the disk at some point and in the case of the nexus 9 (aka flounder) it's the CPU's task. Even though the nexus 9's CPU has 2 pretty fast cores you can still easily feel the difference between FDE in the on- or off-state. The I/O is faster and boot-times take only half as long. (I did not do any measurements)
There is an ongoing discussion about this topic in cyanogenmod's gerrit. Although it's a fun read it is pretty clear that this exchange of views is not going anywhere near a useful outcome.
Because performance is important to me and my tablet does not need the extra security I created the FED-Patcher (ForceEncrypt Disable Patcher)
How does it work?
FED-Patcher is a simple flashable ZIP that is supposed to be run in a recovery that has busybox integrated (like TWRP or CWM). This is what it does:
Checks if your device is compatible
Dumps the currently installed boot.img.
Unpacks the dump of your currently installed boot.img. The unpacking process is done via a self-compiled, statically linked version of unmkbootimg.
It patches the filesystem tables which include the force-encrypt flags. This process will change "forceencrypt" to "encryptable".
Then it patches the filesystem tables to not use dm-verity. This is done by removing the "verify" mount-parameter.
Creates a new boot.img. The unpacking process is done via a self-compiled, statically linked version of mkbootimg.
Flashes the modified boot.img
Supported devices
HTC Nexus 9 WiFi (flounder)
HTC Nexus 9 LTE (flounder_lte)
Motorola Nexus 6 (shamu)
Version History
v1 - Initial version with HTC Nexus 9 WiFi (flounder) support
v2 - Added Motorola Nexus 6 (shamu) support
v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
v4 - Added support for signed boot-images
v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
What do I need to make this work?
A supported device (Your nexus 9)
An unlocked bootloader
An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
A recovery that includes busybox (TWRP, CWM)
How do I use it?
Make a thorough, conservative backup of your data if there is any on your device
Go into your recovery (TWRP, CWM)
Flash fed_patcher-signed.zip
If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.
How do I know if it worked?
Go into your "Settings"-App. In "Security", if it offers you to encrypt your device it is unencrypted. If it says something like "Device is encrypted" it indeed is encrypted.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is it dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
Screenshot
Scroll down to the attached thumbnails.
Credits
* pbatard for making (un)mkbootimg (dunno if he is on xda)
* @rovo89 for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.

Thanks for creating this! In theory, would this work for the Nexus 6 as well? It would seem like it's a similar process.

itlnstln said:
Thanks for creating this! In theory, would this work for the Nexus 6 as well? It would seem like it's a similar process.
Click to expand...
Click to collapse
Hey there,
yes, it would probably work because the process itself is pretty generic. The only real difference between devices is the device-path for the boot-partition as well as the path(s) for the fstab-file(s) inside the boot.img. Nothing that cannot be done - but I don't have a device for testing. If you feel adventurous I can do a nexus6 (shamu) version for you for testing. I will double check so it should not eff up your device .
EDIT: Not to forget, the nexus 9 is a 64bit device. mkbootimg as well as unmkbootimg are compiled for 64bit. I have to rebuild those two programs for 32bit to make them work for 32bit devices.

If you have time for a N6 build, that would be great. If not, it's not a big deal since there seems to be more support for that device.

itlnstln said:
If you have time for a N6 build, that would be great. If not, it's not a big deal since there seems to be more support for that device.
Click to expand...
Click to collapse
Well, it's pretty much done. Do you want to test a version that does not actually flash anything but do everything else - just to see if it works correctly?

Absolutely!

itlnstln said:
Absolutely!
Click to expand...
Click to collapse
Alright, here you go!
If no error occurs there will be the already modified boot.img file in your temp-directory of your nexus 6. You can send me this file to be completely sure that everything went according to plan. Here is the adb-command:
Code:
adb pull /tmp/fed_patcher/boot-new.img
If all goes well I will upload the new version with nexus 6 (shamu) support tomorrow.
Good night!

gladiac said:
Alright, here you go!
If no error occurs there will be the already modified boot.img file in your temp-directory of your nexus 6. You can send me this file to be completely sure that everything went according to plan. Here is the adb-command:
Code:
adb pull /tmp/fed_patcher/boot-new.img
If all goes well I will upload the new version with nexus 6 (shamu) support tomorrow.
Good night!
Click to expand...
Click to collapse
Thanks! It seemed to work OK. Here's the boot image.

itlnstln said:
Thanks! It seemed to work OK. Here's the boot image.
Click to expand...
Click to collapse
Thanks for your help! I just updated the flashable ZIP in the first post. Enjoy

gladiac said:
Thanks for your help! I just updated the flashable ZIP in the first post. Enjoy
Click to expand...
Click to collapse
You're the best! Thanks!

I noticed in op it says "4 pretty fast cores". This puppy only has 2 cores. Just throwing it out there for readers that don't know. I'm sure it was just a minor oversight.
Sent from my Nexus 9

madbat99 said:
I noticed in op it says "4 pretty fast cores". This puppy only has 2 cores. Just throwing it out there for readers that don't know. I'm sure it was just a minor oversight.
Sent from my Nexus 9
Click to expand...
Click to collapse
Hi,
you are right, thanks. I just fixed the text in the op.

Hey everybody,
I will enable support for the Nexus 9 LTE (flounder_lte) this afternoon in FED-Pather v3. If you want other devices to be supported please tell me. Is there a list of android devices that have forced encryption?

So this works great, leaving device unencrypted. But anyone having issues with apps crashing? Most especially Google Play Services?

femmyade2001 said:
So this works great, leaving device unencrypted. But anyone having issues with apps crashing? Most especially Google Play Services?
Click to expand...
Click to collapse
This problem is new to me. My patch only modifies the boot-image so that it does not enforce encryption. It is merely a flag in fstab that gets changed and should not have anything to do with crashing apps. Anyway, do you have a logcat?

Hey everybody,
v3 is here with HTC Nexus 9 LTE (flounder_lte) support!
Enjoy

I'm getting an error with my N9 (WiFi). When I try flashing in TWRP, it throws this error:
! Unpacking failed
=> unmkbootimg return value: 0
E: Error executing updater binary in zip...
All I did was go into fastboot, flash the updated image for LMY48M, then go into TWRP to flash the fix. I even went back into fastboot to try re-flashing the boot.img.

itlnstln said:
I'm getting an error with my N9 (WiFi). When I try flashing in TWRP, it throws this error:
! Unpacking failed
=> unmkbootimg return value: 0
E: Error executing updater binary in zip...
All I did was go into fastboot, flash the updated image for LMY48M, then go into TWRP to flash the fix. I even went back into fastboot to try re-flashing the boot.img.
Click to expand...
Click to collapse
Hi, sorry to hear that. I will have a look into the boot.img that gets shipped with LMY48M. Not sure what is going on here.

itlnstln said:
I'm getting an error with my N9 (WiFi). When I try flashing in TWRP, it throws this error:
! Unpacking failed
=> unmkbootimg return value: 0
E: Error executing updater binary in zip...
All I did was go into fastboot, flash the updated image for LMY48M, then go into TWRP to flash the fix. I even went back into fastboot to try re-flashing the boot.img.
Click to expand...
Click to collapse
Alright - unmkbootimg fails because the boot.img that google ships has 256 Bytes of extra data (it is probably signed or something) at the beginning. If you strip that off it works correctly:
Code:
dd if=boot.img of=boot-stripped.img bs=256 skip=1
Well, this was unexpected. But nothing that cannot be dealt with. I will make my flashable ZIP search for the offset of the boot.img-signature inside the dumped boot.img and strip of the preceding data. The rest of the process should work as usual.

itlnstln said:
I'm getting an error with my N9 (WiFi). When I try flashing in TWRP, it throws this error:
! Unpacking failed
=> unmkbootimg return value: 0
E: Error executing updater binary in zip...
All I did was go into fastboot, flash the updated image for LMY48M, then go into TWRP to flash the fix. I even went back into fastboot to try re-flashing the boot.img.
Click to expand...
Click to collapse
Hi @itlnstln,
I just made a new version which should do the trick. I tested the new functionality to the best of my knowledge. If the script fails for some reason it wont flash anything - so the probability for actual damage is very low. Do you feel adventurous xD?
Please tell me if it worked for you or not.