Develop Bugs

[Q] Could I flash Dezire Z ROM to my T-mobile G2

Hi folks,
I have a question for you.
I have just received my T-Mobile G2 HTC Android phone.
I am so happy i it, but I so get used to HTC Sense ROM. And for sometime I am returning to Belarus.
Here is my steps.
1. Make device SuperCID.
2. Unlock, so I could you use Belarussian SIM cards.
3. Flash Desire Z stock rom.
4. Done
But here is a question:
Is it safe to flash Desire Z ROM to T-mobile G2.
As I could guess, they have different radio images (US and Europe) or I might be wrong?

Do not post questions in the DEVELOPMENT section, use QnA or General next time!!!!!
*AFAIK*.... If you are super CID + full radio s-off then you can use RUU's from other regions. But why bother. stick to custom and carry on flashing through recovery.
also,... Radios can be used in other regions than those intended by HTC, for instance some people are using the radio from the Egypt ROM in the UK will noticeable improvement in signal.

The radio images are not a problem.
The only thing I'm unsure about is the way the G2 and DZ are partitioned differently. This isn't a problem for custom ROMs, but if you flash a complete ROM/RUU it will include the hboot too. So I would love to know if you can flash the hboot too and that will mean your partitioning will be adjusted, or whether perhaps flashing the wrong hboot will brick your phone. Though I am not asking you to experiment for me, because of the risk involved !
I wouldn't have thought the ROM flash would actually re-partition the storage, but I'd be interested to find out.
Sent from my HTC Desire Z

wileykat said:
Do not post questions in the DEVELOPMENT section, use QnA or General next time!!!!!
*AFAIK*.... If you are super CID + full radio s-off then you can use RUU's from other regions. But why bother. stick to custom and carry on flashing through recovery.
also,... Radios can be used in other regions than those intended by HTC, for instance some people are using the radio from the Egypt ROM in the UK will noticeable improvement in signal.
Click to expand...
Click to collapse
Is there is any Custom ROM for DZ, that I can simply apply for G2?

[email protected] said:
Is there is any Custom ROM for DZ, that I can simply apply for G2?
Click to expand...
Click to collapse
As far as I am aware, none of the custom ROMs are specific, and any of them should work fine on the G2 and DZ. So you should find some Sense custom ROMs in the dev forum that you can use, if that's what you want.
Sent from my HTC Desire Z

Radios

I have read the guides/tutorials but there are still a few things i don't understand.
The guide says the radio boosts the phone's signals, so why are there so many to choose from? Which one do i need and what is the difference?
I have rooted and S-OFF'd my phone. i'm not sure what the next step is. is it installing a new radio or rom? how do i know which rom to install or is it just trial and error?
Also, what is ENGINEERING HBOOT?
Thanks

NthZ said:
I have read the guides/tutorials but there are still a few things i don't understand.
The guide says the radio boosts the phone's signals, so why are there so many to choose from? Which one do i need and what is the difference?
I have rooted and S-OFF'd my phone. i'm not sure what the next step is. is it installing a new radio or rom? how do i know which rom to install or is it just trial and error?
Also, what is ENGINEERING HBOOT?
Thanks
Click to expand...
Click to collapse
Radios, for the most part, are trial and error; some work best in certain regions, others best in other regions. As for ROMs, look through what each offer and choose the one you like the best.
Sent from my T-Mobile G2 using XDA App

Isn't there any more info at all on this though? Like which ones work better for which areas and carriers. Or does the carrier even matter?
Sent from my HTC Desire Z

[Q] Not only debranding, but enabling direct OTA from HTC

Hi, I regret to say I am a noob. I have read around for the past few days and have a general idea of rooting and flashing ROMs.
I have a branded T Mobile DHD and I not only want it debranded, but I want it to function as if T Mobile never touched it. That is, I want to be able to debrand it once and then receive OTA updates direct from HTC when they are released (all the way up to the eventual ICS).
I have two main questions. One, can I replace the T Mobile ROM with the Stock HTC one without root and without a custom recovery (that is, installing the stock ROM using the stock recovery -renaming it update.).
Two, do I need to change the CID to HTC__001 to enable future OTA updates?
There may be things I have missed. Please point me in the right direction if this is the case, cause the info I've found isn't as specific as I'd like it.
Thank you!

Unfortunately not sure if there is such a thing. I have rooted and used custom ROMS and in the end went back to my providers RUU. I find even though some bloat ware the software is fast enough bug free and battery life is very good. Search the net maybe find your answer there.
Sent from my SPH-P100 using xda premium

rzgomba said:
Unfortunately not sure if there is such a thing. I have rooted and used custom ROMS and in the end went back to my providers RUU. I find even though some bloat ware the software is fast enough bug free and battery life is very good. Search the net maybe find your answer there.
Sent from my SPH-P100 using xda premium
Click to expand...
Click to collapse
I should have clarified, I'm using a T Mobile DHD off ebay with a 3 sim. The reason I want to have a clean DHD is primarily so I can be free from waiting on T Mobile for updates. The reason I want to be clean and have OTA direct from HTC is because I've always been happy with stock, unbranded ROMs.
Thanks though.
Is there no way of completely restoring the DHD to a purely unbranded state so that it functions as a factory bought one?

I read this
"If you're coming from a branded ROM and just want to debrand, you can stop here. By reverting back to an unbranded 2.2 ROM, you will now be able to receive OTA update straight from HTC without any network bloatware. You can continue with the root process, but it is not recommended you download OTA updates when rooted."
on androidforums, the thread "How to root and install a custom ROM on the Desire HD" (I can't post links)
Which is what got me thinking about debranding and leaving it there, but reading up about CID and OTAs I got confused, wouldn't mine still be T Mobiles and not HTC__001 after downgrading? It'd be great if someone could explain how simply reverting back using a goldcard results in successful HTC OTAs.
Or I could just root the phone and install HTC WWE ROMs as they appear online.
What would be best?

You would have to gain root/soff/supercid first after that you just simply flash the unbranded ruu.

It should be doable, I would imagine all it takes is setting the proper CID/MID and flashing a WWE RUU, and never rooting/installing custom recovery.

Hunt3r.j2 said:
It should be doable, I would imagine all it takes is setting the proper CID/MID and flashing a WWE RUU, and never rooting/installing custom recovery.
Click to expand...
Click to collapse
Could I use the Advanced Ace Hack Kit to give me those permissions, then using the Kit revert it to a WWE RUU?
If not, I'll try rooting then installing a RUU separately. I know how to install ROMS from zip files through recovery, how do I install a stock exe RUU on a rooted phone?

Reverting back to son unbranded to me would be an unnecessary step. This is what I would do.
1)use the hack kit to get supercid/soff
2) flash the unbranded ruu
3)done
To flash an ruu, you would simply just run the program from your PC with your phone connected

[Q[ Questions on RUU

Hey Guys,
I just had some questions regarding RUU's and sort of trying to understand them.
Do RUU's update everything that normal custom ROM's cannot, i.e. like the OTA's? So updating drivers and hboot etc?
Main reason is that if it does update everything then on the next big update I would probably want to do an RUU install even if it means loosing all data.
With regards to the RUU do I need all three of the following:
- Stock ROM
- Stock Recovery
- Locked bootloader
Or do I need JUST a locked bootloader?
Thanks

Yes you will get updates if you flash a ruu and ruu 's are pure stock ruu's are used when we need to put the stock Rom back on our device when we need to send it in for repair's and also when we prefer the stock Rom over a custom Rom I my self prefer custom Rom over a stock Rom and sometimes when a custom Rom isnt performing the way it should some people will simply go back to stock by flashing a ruu
Sent From My Viper S 1.2.0 with true s off by alpha revolutionary

jslim38 said:
Yes you will get updates if you flash a ruu and ruu 's are pure stock ruu's are used when we need to put the stock Rom back on our device when we need to send it in for repair's and also when we prefer the stock Rom over a custom Rom I my self prefer custom Rom over a stock Rom and sometimes when a custom Rom isnt performing the way it should some people will simply go back to stock by flashing a ruu
Sent From My Viper S 1.2.0 with true s off by alpha revolutionary
Click to expand...
Click to collapse
Thanks, my main reason is actually not to say on an RUU but I was hoping to install an RUU, get all the updates to my firmware and drivers, then unlock bootloader again and install a custom ROM.

They should be updated by a custom rom. Only thing that isnt touched is the HBOOT i think. But reflash stock recovery relock the bootloader then run the ruu.

Flashing an RUU first if available is the way to go personally
Sent from my HTC One X using xda premium

I readin a lot on here and I read somewhere updateing with ruu updates hboot and hboot is some sort of security so updateing it could make getting s-off harder
Sent from my HTC One X using xda premium

Updating the HBoot means adding more layers of security, which imo is not something we enjoy here on XDA
Personally, I prefer going with a custom ROM that is almost like stock (preferably ARHD) which with every update brings the improvements brought to us by HTC and even more.
Also with ARHD for example, upgrading from one version to a newer one rarely requires you to wipe all your data which is very annoying imo.

I've been on Custom roms since I had my phone so I had missed the OTA update for 1.xxx.11 and the 2.xx versions, now with the a big 3.xx version on the horizon, my main concern is if my Custom ROM's are not updating some critical firmware drivers and such that would have benefitted my phone.
Tbh it's still not clear to me what Custom ROM's cannot update, at first I thought it was just the HBOOT but then I read on a recent thread that apparently things like GPU drivers and other essential hardware firmware drivers may not get updated either which sounds like a big deal. Hence I was thinking with the release of 3.xx I should do an RUU install just to be sure and then go ahead to a Custom ROM.
I understand that having my HBOOT updated could mean S-OFF is harder but the way things are, it doesn't look like were any close to getting it either, who knows maybe even a future HBOOT update might have an easier S-OFF is HTC decide to relax it a bit from consumer pressure?

When developers get their hands on new RUUs they base their custom Roms on them, and therefore you will get the new updates in terms of drivers and other software related things.
Also, kernels bring new improvements as they are updated, and developers also build their ROMs on these kernels. However, you can flash custom kernels separately if you find one that has additional "improvements" you like.
In short, custom ROMs that are maintained/updated regularly (ARHD is one of the best imo) is all you need to stay up to date with all the new improvements.
The only reason I ever download any RUU is in case something went wrong with my phone, and I wanted to temporarily return to stock.

Ah right, I was thinking more of the S-ON security restriction not letting custom ROM's fully update everything except radio, kernel and ROM but RUU's are given the full access to update everything?

iq-dot said:
Ah right, I was thinking more of the S-ON security restriction not letting custom ROM's fully update everything except radio, kernel and ROM but RUU's are given the full access to update everything?
Click to expand...
Click to collapse
I don't think there is consensus on what can be updated and what cannot.
Here's my take: an OTA has access to everything, as does an RUU, but the point is that they flash signed images, and the phone will allow signed images to be flashed (subject to matching CID, etc.).
It's possible to flash kernel with the boot.img, and also possible to flash kernel modules, which means that drivers can be updated.
It's possible to flash "radios" (often as part of the ROM), and there is an app to get updated RILs, so it would seem that the RIL has not been confused with the radio. However, since the bootloader appears to get the radio version from a text file, rather than the radio, there's some doubt as to whether the radio is really updated (since the bootloader disagrees).
Obviously we can unlock and gain access to flashing unsigned recovery, boot (kernel/ramdisk) and ROM images.
Outside of this, it's not impossible that there are areas of the phone that still require flashing of signed images, such as for firmware updates of other bits of hardware not previously mentioned (speculatively: lower level bits of "radio", cpu microcode, gpu firmware, etc.), which may or may not be flashable with an RUU (or maybe even an OTA). However, there is nothing in an RUU that cannot be done with tools we already have, so if there was a "fastboot flash cpu_microcode" option, somebody would have found it. I haven't looked at full list of fastboot commands, but I don't recall coming across anything like that.

xbiggyl said:
When developers get their hands on new RUUs they base their custom Roms on them, and therefore you will get the new updates in terms of drivers and other software related things.
Also, kernels bring new improvements as they are updated, and developers also build their ROMs on these kernels. However, you can flash custom kernels separately if you find one that has additional "improvements" you like.
In short, custom ROMs that are maintained/updated regularly (ARHD is one of the best imo) is all you need to stay up to date with all the new improvements.
The only reason I ever download any RUU is in case something went wrong with my phone, and I wanted to temporarily return to stock.
Click to expand...
Click to collapse
There are some parts of the firmware/drivers that custom ROMs cannot change so flashing an RUU first does have it's benefits to get a true experience of a custom ROM

EddyOS said:
There are some parts of the firmware/drivers that custom ROMs cannot change so flashing an RUU first does have it's benefits to get a true experience of a custom ROM
Click to expand...
Click to collapse
Do you know what, specifically?

I don't, no, it's just a personal preference I suppose. I updated to the 2.17 RUU (UK unbranded) and then went onto a custom ROM based on the same RUU so I know everything is compatible. Whether it has any real affect I don't know but seeing as Mike used to have 'firmware' packages for other HTC handsets it would lead me to believe he would with the One X if we had S-OFF

EddyOS said:
Mike used to have 'firmware' packages for other HTC handsets it would lead me to believe he would with the One X if we had S-OFF
Click to expand...
Click to collapse
...there are a lot of masked partitions, eh? Who knows.

A lot of the partitions were listed in the S-OFF thread but as to what they actually contain/do is open to discussion - it could be a custom ROM it's own is enough but without S-OFF we'll never really know

EddyOS said:
There are some parts of the firmware/drivers that custom ROMs cannot change so flashing an RUU first does have it's benefits to get a true experience of a custom ROM
Click to expand...
Click to collapse
Have you read anywhere of any improvements offered exclusively by RUUs or you're simply speculating?
I know some partitions (that appeared to be in the HOX) are not accessible by Custom Roms, but has anyone ever claimed to have experienced an improvement in any way by flashing an RUU that people flashing custom Roms haven't?
Sent from my HTC One X using Tapatalk 2

Should I update to Marshmallow?

Good day, guys.
I recently bought a HTC Desire Eye (eye_tuhl) and I was wondering if I should update the phone first to Marshmallow before rooting it? I read through the development threads and it seems that people have difficulty with regard to the Marshmallow firmware. I am planning to flash S.ROM and the patch after rooting.
Also, after rooting, which ROMs are available for flashing for my variant, if I'm going to stay S-ON? I read that some ROMs have problems with S-ON phones. I also wanted to confirm that the Minis Reloaded Kernel also works in S-ON, provided that it will be flashed using a PC and is used with a ported ROM from M8.
I am sorry if the questions seem redundant, I got confused with the whole variant/firmware/S-ON snafu coming from devices which were relatively easy to understand (HTC Sensation, Xperia ZR)
Thank you very much in advance.

jamesmalit3 said:
Good day, guys.
I recently bought a HTC Desire Eye (eye_tuhl) and I was wondering if I should update the phone first to Marshmallow before rooting it? I read through the development threads and it seems that people have difficulty with regard to the Marshmallow firmware. I am planning to flash S.ROM and the patch after rooting.
Also, after rooting, which ROMs are available for flashing for my variant, if I'm going to stay S-ON? I read that some ROMs have problems with S-ON phones. I also wanted to confirm that the Minis Reloaded Kernel also works in S-ON, provided that it will be flashed using a PC and is used with a ported ROM from M8.
I am sorry if the questions seem redundant, I got confused with the whole variant/firmware/S-ON snafu coming from devices which were relatively easy to understand (HTC Sensation, Xperia ZR)
Thank you very much in advance.
Click to expand...
Click to collapse
Its a long time since I flashed new ROM on my Desire, so I'm not sure about some info (already forget a lot), sorry for that.
But here is it
1) You can't update your firmware to custom one with S-On phone, only using OTA or RUU. But you may need to do that.
(for every Android version you need correct firmware)
2) Some people had problems with installing kernels on S-On devices also.
3) Even if you succed with flashing ROM, you may have problems with it. For example, enormous battery drain (I've this, it was just horrible), mobile data not working, NFC, etc.
So, i think the best way in this situation is OTA.
Please, correct me if i'm wrong.