Wrong engineering HBoot - G2 and Desire Z Q&A, Help & Troubleshooting

I was bored so I was reading through the DZ /G2 wiki. It says that there are different hboot for the DZ AND G2, I have a DZ with the G2 hboot. Does it matter?
I rooted in November and have never had any issues using fastboot or flashing radios and the like so I guess that it doesn't.
Sent from my HTC Desire Z using XDA Premium App

If its not broke don't mess with it. Messing around with the bootloader can get you bricked. You shouldn't have any problems since both phones are the exact same hardware.

mejorguille said:
If its not broke don't mess with it. Messing around with the bootloader can get you bricked. You shouldn't have any problems since both phones are the exact same hardware.
Click to expand...
Click to collapse
That's exactly what I thought people would say.
But why does the wiki say you should use different ones for different phones?
Sent from my HTC Desire Z using XDA Premium App

cjward23 said:
That's exactly what I thought people would say.
But why does the wiki say you should use different ones for different phones?
Sent from my HTC Desire Z using XDA Premium App
Click to expand...
Click to collapse
Does it matter if it works? Amazing
Sent from my HTC Vision using XDA Premium App

Spastic909 said:
Does it matter if it works? Amazing
Click to expand...
Click to collapse
Just because it has worked so far doesn't mean it always will. The HBOOT for the Desire Z and the G2 are different due to the partitioning on the phones. The Desire Z has an additional partition defined, causing the system and userdata partitions to be slightly smaller than on the G2.
All of the custom ROMs so far have been designed to fit within the smaller partition size, so it shouldn't really matter for them. If you were still on stock though, you could theoretically run into problems. For example, if you have a Desire Z that is still running the stock ROM, flash to the G2 HBOOT, and then do an OTA update one day that doesn't contain an update to the HBOOT (which would correct the partition map), you could potentially run into problems due to the partitions not being correct. It's an unlikely scenario, but it could happen (using the Desire Z HBOOT on a G2 would probably be worse since any updates would expect the system partition to be bigger than it is---flashing the system partition then could overwrite part of the adjacent partition then).
This is why it's normally better to stick with the HBOOT defined for your phone though. Probably safe in your scenario though (i.e., G2 HBOOT on Desire Z isn't as dangerous and if you have the engineering HBOOT to begin with, you probably are rooted or using a custom ROM, so OTA updates aren't an issue).

ianmcquinn said:
Just because it has worked so far doesn't mean it always will. The HBOOT for the Desire Z and the G2 are different due to the partitioning on the phones. The Desire Z has an additional partition defined, causing the system and userdata partitions to be slightly smaller than on the G2.
All of the custom ROMs so far have been designed to fit within the smaller partition size, so it shouldn't really matter for them. If you were still on stock though, you could theoretically run into problems. For example, if you have a Desire Z that is still running the stock ROM, flash to the G2 HBOOT, and then do an OTA update one day that doesn't contain an update to the HBOOT (which would correct the partition map), you could potentially run into problems due to the partitions not being correct. It's an unlikely scenario, but it could happen (using the Desire Z HBOOT on a G2 would probably be worse since any updates would expect the system partition to be bigger than it is---flashing the system partition then could overwrite part of the adjacent partition then).
This is why it's normally better to stick with the HBOOT defined for your phone though. Probably safe in your scenario though (i.e., G2 HBOOT on Desire Z isn't as dangerous and if you have the engineering HBOOT to begin with, you probably are rooted or using a custom ROM, so OTA updates aren't an issue).
Click to expand...
Click to collapse
Cool thanks for the detailed answer.
So I decided to flash the correct hboot for my phone, the flash went ok but when I booted into recovery I got the same errors that I lot of people have been having. I re flashed the G2 hboot and everything is good again.
But we obviously have a quite serious problem with the DZ hboot and lots of members are getting semi bricked phones.

Related

[Q] Radio Downgrade without wipe/RUU-reset? (AMOLED-Desire, HBOOT 0.80.000, S-ON!)

Hey folks,
is it somehow possible to downgrade the radio to an older one without wiping or resetting the whole phone via RUU?
I just tried to flash an older one over the current radio image and it doesn't seem to work
Why do I want to downgrade anyways?
My phone crashs all the time. Especially when it's connected to the original charger from HTC (1000mA) and I try to use an app. Or when I use several apps at the same time, when not charging.
It could be the hardware-failure, everybody is talking about lately...
BUT I found out that everything is fine with the performance and stability of the phone, when I am using it in airplane-mode.
Everything was fine a few month backs, when I was using some older radios and ROMs.
The crashs seem to be somehow connected to mobile data usage (2g/3g). I've heard that some radios might be "better" in some regions as others. I'm from Germany, so maybe this is causing the instabilities.
I thought it is worth a try, before complaining hat HTC ​
Starting situation:
rooted AMOLED Desire (HBOOT 0.80.000 + S-ON)
AmonRa Recovery v2.0.1
Redux v1.1.1
vorkKernel 2.6.37.2 (CFS, SVS)
Radio 32.54.00.32_5.14.05.17
Thank you guys
You need to use the radio zips from recovery when you are s-on.
Sent from my HTC Desire using XDA Premium App
Most likely to be hardware failure. Send it to HTC for motherboard change. Search for desire overheating and rebooting on its own in the forums and see if symptoms match. Had mine replaced
Sent from my HTC Desire using XDA App
TheGhost1233 said:
You need to use the radio zips from recovery when you are s-on.
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
have done that, but it doesn't affect any downgrade.
How have you exactly done it? And you sure you didn't get any errors in recovery?
Sent from my HTC Desire using XDA Premium App
Downloaded old radio from the thread here on xda
copied to SD
booted into AmonRa Recovery
flashed the zip directly from sd
no erros, flashing susscessful (something like that displayed)
selected "reboot phone"
As always the normale procedure...
except that this time the ROM was booted after leaving the recovery, instead of the regularly shown "radio-installation-box-logo"...
tinky1 said:
Most likely to be hardware failure. Send it to HTC for motherboard change. Search for desire overheating and rebooting on its own in the forums and see if symptoms match. Had mine replaced
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
The phone is running since two days straight without any crash and exceptional battery life, heavy usage...the only downside...mobile data is deactivated.
Does nobody know how to downgrade the radio?
Thanks.
Actually after trying the senventh Radio (no ****!) I succeeded
The only downgrade was possible with the "32.44.00.32U_5.09.05.30_2" radio.
And since then my phone is running stable again! Amazing
spaboleo said:
Actually after trying the senventh Radio (no ****!) I succeeded
The only downgrade was possible with the "32.44.00.32U_5.09.05.30_2" radio.
And since then my phone is running stable again! Amazing
Click to expand...
Click to collapse
Great! Glad you don't have to send it away.
Sent from my HTC Desire using XDA App

GB OTA and the new hboot 0.82.0008- lots of questions

I haven't flashed the new hboot yet. I'm currently running CM7 and have the eng hboot 0.76.2000 with s-off.
As promised, here are the questions:
1) Has anyone flashed the new hboot and tried to restore a custom rom?
2) If I flash the new hboot (0.86.0008) will I be able flash back to the eng hboot?
3) What are the differences between the two? I usually use cwm/recovery, but if I need the hboot, I would like to be able to flash all the partitions. Is this still possible with the SHP version?
4) the nb0 files seem like I could flash them via "flash hboot" and skip the zip or disk destroy. Does this make anyone nervous?
5) I lost track of all the rooting going on... I rooted with gfree before there was a version number. Is there a root method that unlocks even more?
Thanks in advance... I've been playing with the ASUS transformer lately which has an unlocked, unbrickable bootloader, so I know I should slow down before getting to flash happy with hboot.
Why do you want to flash a new hboot? Something wrong with your device or something?
Sent from my HTC Desire Z using XDA Premium App
This is one of those "If it ain't broke, don't fix it" things.
Sent from my T-mobile G2 using Tapatalk
The more you tell me not to do it, the more I want to flash it!
I'm just curious....
Same as u gee one, I wanna know. If no one ever tried new things cause what we had was "good enough" we would be years behind in progress in about every level of life.
Sent from my HTC Vision using XDA Premium App
Stick with the ENG HBOOT -- it has more of the fastboot commands enabled.
I think we all plan on sticking with eng hboot. Still doesn't answer the question about what is different with the new one.
Sent from my HTC Vision using XDA Premium App
Hboot changes are typically to add security (i.e., take away your freedom), not add new features or make anything better. Unlike the radio, it will NOT affect performance. This is just a bootloader, like GRUB or LILO. Once it hands the CPU off to the Linux kernel, its life is over. As long as it does that correctly, there is no reason to change it.
Thank you 234 I think that is the kind of answer we were looking for I would hit thanks but am on the mobile app.
Sent from my HTC Vision using XDA Premium App
I have flashed the htc desire hboot on the G2 and so far I'm still able to flash any rom for both the G2 and the htc desire .
Sent from my T-Mobile G2 using XDA Premium App
What "features" are missing from the existing hboot? If it aint broke dont fix it, definately a case of theres a new version must flash it must be better, think will stay on my old boring hboot that does what i need it to do until the wiki is updated.
Sent from a htc desire z
Hold my beer, I'm gonna flash the new hboot!
There's nothing wrong with hboot- I'm just asking about what differences there are. I never asked if it was better. I understand that it's not an engineering hboot, but I don't know what features are "missing" from it. This is the exactly the question that I'm asking. I know that flashing a new hboot will not increase my battery life or improve my radio reception. I know that flashing hboot can be dangerous and lead to bricked devices. I know that flashing hboot will not solve world hunger, resolve the world debt crisis, or bring peace in the Middle East.
I think if I asked about a new ROM, people would just tell me to flash it and find out for myself.
Flashing hboot can be dangerous and possibly brick your device. I do not recommend it. This thread is for entertainment purposes only!
gee one said:
There's nothing wrong with hboot- I'm just asking about what differences there are. I never asked if it was better. I understand that it's not an engineering hboot, but I don't know what features are "missing" from it. This is the exactly the question that I'm asking. I know that flashing a new hboot will not increase my battery life or improve my radio reception. I know that flashing hboot can be dangerous and lead to bricked devices. I know that flashing hboot will not solve world hunger, resolve the world debt crisis, or bring peace in the Middle East.
I think if I asked about a new ROM, people would just tell me to flash it and find out for myself.
Flashing hboot can be dangerous and possibly brick your device. I do not recommend it. This thread is for entertainment purposes only!
Click to expand...
Click to collapse
No offence buddy but why do you want to flash a new hboot then? You mention different ways to root but as far as I am aware the wiki is the "official" recommended way, will stick with what Ive got until such times as the wiki recommends changing my hboot,that is the only guide to rooting that I need.
I never said I wanted to flash it. I just asked what was different about it. What changed from the old stock hboot? Maybe the partition layout is different and there is more memory allocated to data? I don't know, hence the questions.
As some people have asked, if it ain't broke, then why fix it? Then why would HTC/T-Mo change it? I'm just curious about the changes.
I agree, for most users, they would never need hboot. The zipped up roms and radios are just fine for flashing in recovery.
sent from my cyanogen(mod) vision
I agree with you. There's nothing wrong with wanting to know what does the new hboot do. Furthermore, the only thing "wrong" with knowing more is that you get more awesome stuffs, kinda painful isn't it?
And, "if it ain't broke, then why fix it", why are we using HTC Vision here, not Nokia 1100, or better yet, smoke signal?
Holy thread resurrection, Batman !
Sent from my Desire Z running CM7.
He's got a good point though.

[Q] Flashing Cyanogenmod 7 to my DHD, is my research correct?

Basically what it says in the title. I have a Desire HD with Android 2.3.5 installed, and I want to flash Cyanogenmod 7.1 (With google apps) to it. I've had a good look at all the resources available and I think I know what I need to do, I'm a little apprehensive though as I'm new to this so would somebody mind checking the resources I have found to see if I have the right steps?
First of all I've checked in About Phone -> Software Information and found that my Software Number is 3.12.405.1. So from what I've read this means I'll have to downgrade my firmware before I can root.
That lead me to this guide: Here
If I follow that guide carefully as well as this one here, I will end up with a phone that has firmware 1.32, is rooted, has Radio S-OFF and also has clockworkmod recovery installed.
From there, I can then follow this guide here to install the latest version of Cyanogenmod either using Recovery, or the ROM manager. Simple, right?
Does this sound about right? Or am I missing something incredibly obvious that will break my phone, or make life a lot easier?
Any help would be greatly appreciated, thanks!
Sounds good to me although you could try this http://forum.xda-developers.com/showthread.php?t=952352
One click root and s-off once you follow everything and have the right setup to run the tool. Very easy and quick.
Sent from my HTC Desire HD A9191 using xda premium
yvibes said:
Sounds good to me although you could try this http://forum.xda-developers.com/showthread.php?t=952352
One click root and s-off once you follow everything and have the right setup to run the tool. Very easy and quick.
Sent from my HTC Desire HD A9191 using xda premium
Click to expand...
Click to collapse
Thanks! That looks good, although I'm not very confident about this little warning.
Doing this WILL severely degrade bootloader performance on Inspires (and likely DHDs) and causes issues trying to install RUUs. In other words, it WILL jam you up. (Note: Issue now confirmed on later DHDs - ignore at your own risk).
Click to expand...
Click to collapse
Am I reading this correctly, following this method WILL degrade my bootloader performance? Or will that only happen if I perform the hack incorrectly?
You are reading it wrong. What has happens especially with us inspire users(American dhd) is that if your phone was shipped with gb, installing the Eng bootloader(Eng soff) causes issues. Makes the phone take 15 min to boot. Its possible to fix but its a long pita. I only seen a couple people with dhd have this issue so and others not.
Regular soff is all you need, just you can't use fastboot to flash say radios, its done in a different way
marsdta said:
You are reading it wrong. What has happens especially with us inspire users(American dhd) is that if your phone was shipped with gb, installing the Eng bootloader(Eng soff) causes issues. Makes the phone take 15 min to boot. Its possible to fix but its a long pita. I only seen a couple people with dhd have this issue so and others not.
Regular soff is all you need, just you can't use fastboot to flash say radios, its done in a different way
Click to expand...
Click to collapse
Yup exactly that
Sent from my HTC Desire HD A9191 using xda premium
Just follow these his guide and video, works perfectly. www.xda-developers.com/android/how-to-root-the-htc-desire-hd/
The only difference is that after instead of flashing the rom suggested you can flash cm 7.1 www.download.cyanogenmod.com/?type=stable&device=ace
No risks no problems with bootloader.

[Q] Problem identifying the G2/Desire Z

okay so i've been given a used g2/desire z but the problem is i cannot figure out if it's a g2 or a desire z because no where on the phone it says t mobile but the back plate has a g2 carved on it (the back could have been replaced). Now i looked at some pics of the G2 it clearly says t-mobile on top It's running froyo 2.2 with the build number of 0.90.xxx.x. This stopped me from rooting the phone since i didn't have a way of finding out what this damned thing is. Secondly i tried checking for updates it keeps searching for updates and nothing happens and thirdly if it's a g2 it must be unlocked cause i'm using an other carriers sim. There is no HTC Sense on the phone no shining suns no flip clock or is it just that the version is so old that sense wasn't invented yet ?plus if i went ahead with the desire z method of rooting if what i have is a g2 would i brick my phone ?
I had the same question they are the same the DZ is the international version of the G2 it has a little more memory I believe. And all roms are safe to flash on either device. Some roms like sense need to have the DZ hboot. Simple to install and it gives you a little more ram which is needed for certain roms
Sent from my SGH-T959V using XDA
the only real difference is the stock rom and the hboot/spl
boot on your phone and see what hboot you have (hold volume down while powering on) and you will know if its considered a g2 or dz
there isnt more ram in the dz just a larger partition for the system which is needed to flash certain roms (sense) it truley wont matter which one you have now and you will only need to change the hboot from g2 to dz if you want these roms. there would be no reason to change from dz hboot to g2.
coldeyes1 said:
okay so i've been given a used g2/desire z but the problem is i cannot figure out if it's a g2 or a desire z because no where on the phone it says t mobile but the back plate has a g2 carved on it (the back could have been replaced). Now i looked at some pics of the G2 it clearly says t-mobile on top It's running froyo 2.2 with the build number of 0.90.xxx.x. This stopped me from rooting the phone since i didn't have a way of finding out what this damned thing is. Secondly i tried checking for updates it keeps searching for updates and nothing happens and thirdly if it's a g2 it must be unlocked cause i'm using an other carriers sim. There is no HTC Sense on the phone no shining suns no flip clock or is it just that the version is so old that sense wasn't invented yet ?plus if i went ahead with the desire z method of rooting if what i have is a g2 would i brick my phone ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=26990743&postcount=2
(QUOTE) there isnt more ram in the dz just a larger partition for the system which is needed to flash certain roms (sense)
Thanks my bad that's what I meant to say.
Sent from my SGH-T959V using XDA
so i checked my bootloader and the hboot version is 0.78.1000 now as Pnut pointed me to this post http://forum.xda-developers.com/showpost.php?p=26990743&postcount=2 where the say this 0.76.2000>G2 so am i right in assuming that what i have is the G2 and it is safe to go ahead with this method of rooting http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Rooting ?
it would be safe even if you had the dz. if you want to understand the phones a bit more look @ the xda wiki on the vision, just go to wiki tab on the top of the screen, the htc phones on the right find the g2/dz aka vision. you ll understand more, same guide for rooting as cyanogens but more of an explanation
Sent from my HTC Vision using xda premium
so i read the wiki as you said demkantor and i came to the hboot part so here's what it is
1.1. engineering hboot
Download the appropriate HBOOT for your phone:
T-Mobile G2: vision.hboot-0.76.2000.zip (md5sum 7669AE12DC2FAA10AE555A164980EFD0)
HTC Desire Z: vision.hboot-0.84.2000.zip (md5sum 2CE1BDD5E4C1119CCFCECB938710D742)
Note that the md5sums are for the actual hboot img contained within the zip file, not the for the zip file itself. Note also that the dz, g2, and dhd each use their own version of the engineering boot, as the phones are partitioned differently. (If you have previously installed the wrong HBOOT for your phone, you may need to reflash everything after partition 18 .
According to this it's my choice on which hboot version i want to flash ?
well if you like sense roms id go dz as you have the larger system partition otherwise go with g2, its not a big deal so long as you flash a rom afterwards. this will not cause a brick but if you change your emmc partition the current rom will not be able to boot after you are rooted. thats ok you want to flash a new rom anyhow.
Sent from my HTC Vision using xda premium

Hboot questions

Ok have a question for you smart guys. I havnt found an answer to it even looking through the forums (mind you I'm on the phone on edge so I may have well missed it) but is there anything listing the pros and cons of both the dz and g2 ones? Also if you flash a rom on the wrong hboot is it the end of the world?
Sent from my G2 running a random rom.
end of the world? of course not, end of your phone? no not that either. if you have the g2 hboot and you flash a custom rom that is to larger to fit on the spcae allocated to system (mostly sense roms) well then it wont boot. not broken just need to flash something else. if you have the dz hboot and you flash a rom "meant" for the g2, no biggie it will flash and work just fine.
the main difference is the size of the system partition, the dz has a larger one and it steals that extra bit of memory from cache and data (no big deal) if you want to be able to flash any rom for the vision just make sure you have the dz hboot and your good.
HERE you will find some info on how to flash it, this is more or less a thread on how to use fastboot i made recently but it will have all the downloads needed as well as a fairly in depth explanation on how to. you can flash your new hboot straight from your bootloader but i dont like this method for a few reasons further explained in the thread
hope this helps
Demkantor thanks for the reply. I read through the post and can't get it to work through the pc way (issues on my pc, sometimes I poke at stuff I probably shouldn't ). I booted into the bootloader option through the power menu and it says s-off and desire. Does that mean I allready have the dz hboot?
Sent from my G2 running the random rom of the day.
can you write down everything on your hboot screen
Sent from my HTC Vision using xda premium
Ok here goes
Vision pvt eng s-off
Hboot-0.76.2000 (pc1010000)
Microp-0425
Radio-26.02.01.15-m2
Emmc-boot
Aug 20 2010,16:51:01
Hopefully the actual caps didn't matter because I forgot to write them down.
Sent from my G2 running the random rom of the day.
no you have the g2 hboot still, maybe write down the steps you were trying to take and what the problems (or errors you got) were. this generally is easy to figure out. actually do you want to write it the thread I linked you to, my toutorial skills aren't great so if you have some questions others probably do too
Sent from my HTC Vision using xda premium
I appreciate the offer of help and I will definatly take you up on it. I think the problems I am having are caused by my laptop. Tried hacking on the distro I have installed and I'm all but positive that's what is causiing. Soon as I get a moment and can boot and nuke it I will try again then stalk you in the other thread.
Sent from my G2 running the random rom of the day.

Categories

Resources