Develop Bugs

[Q] How to flash a stock Desire Z ROM on G2?

Hi guys,
So , is this possible? I hear that they are not exactly the same inside?
Thank you.

It is possible if you have the true radio s-off with gfree, although some of the key might not work, you'd have to find and push a fix for the key mapping in order for it to work properly, but if you want Sense just load Virtuous rom, its a great sense based rom with all the features of the Desire Z, its based off the Egypt release for the Desire Z, minus all the headaches of remapping keys.
Sent from my HTC Vision using XDA App

Thanks very much man.

Hi,
I'am also interested in this because i've flashed the g2 rom on my DZ and cant flash back to stock rom. I think the problem is that in Settings -> About Phone -> Phone Identity -> Model Number now stands Tmobile G2 instead of Desire Z.
Is there anyway of fixing this because i cant flash a RUU nor a PC10IMG. The bootloader posts me on a PC10IMG "lack of heap".

kreni said:
I'am also interested in this because i've flashed the g2 rom on my DZ and cant flash back to stock rom. I think the problem is that in Settings -> About Phone -> Phone Identity -> Model Number now stands Tmobile G2 instead of Desire Z.
Is there anyway of fixing this because i cant flash a RUU nor a PC10IMG. The bootloader posts me on a PC10IMG "lack of heap".
Click to expand...
Click to collapse
What version of hboot is on your phone ? I wonder if it is the G2 or the DZ hboot.
Sent from my HTC Desire Z

Hi, i have the 0.76.2000 hboot version. ive tryed to flash through the pc10img and fastboot but this posts me "fastboot flash system system.img
sending 'system' (571388 KB)... FAILED (remote: data length is too large)
finished. total time: 0.005s"

kreni said:
Hi, i have the 0.76.2000 hboot version. ive tryed to flash through the pc10img and fastboot but this posts me "fastboot flash system system.img
sending 'system' (571388 KB)... FAILED (remote: data length is too large)
finished. total time: 0.005s"
Click to expand...
Click to collapse
Ok, so that's the G2 hboot that you have. That will be using the G2 partitioning. Which is I think why you are getting that "too large" error when flashing a DZ ROM.
Sent from my HTC Desire Z

I also flashed my DZ with a G2 rom, because I wanted to unroot and followed this guide:
"addictivetips.com/mobile/how-to-unroot-t-mobile-g2-htc-desire-z-complete-guide/"
I didn't give it much a thought, because it seemed suitable for the Desire Z, but now I have a G2 rom.
My hboot version is 0.82 and everytime I try to flash with 1.34 or 1.72 (extracted from the RUU) I get the "Lack of heap!" error...
Does someone has a guide or advice how I can get my stock rom back? I can't use a custom rom, because I want to send my device back to get the hinge fixed.
I realy would appreciate any helpfull advice!
Sorry for my bad English...

I got the exact same problem as vLum but what i did after is reroot with gfree method , and then put a custom rom on it to get rid of the G2 , is there anyone proffesional enough who can help us with this issue.
We would all appreciate it!
Thanks

[Q] no system installed ... Update fail !

hi,
trying to unroot, un-alpharev, un everething to take phone to warranty fix (gps not working anymore).
ive run the RUU, but HBOOT wasnt 'fixed'. so then i extracted rom.zip, renamed it to PB99IMG.zip and put to root of sdcard but when updating through hboot the position BOOTLOADER is BYPASSED (all others are OK).
how to remove alpharev text bootloader ? how to unroot ? (my hboot is 6.93.1002)
EDIT:
please check this post : http://forum.xda-developers.com/showpost.php?p=16044493

Do you have a CDMA phone? The latest HBOOT version is 0.930001

oh, should have said that before - this is GSM phone
my question is to:
-load stock recovery
-load stock hboot
-remove 'alpharev' on hboot
-to s-on

First Downgrade ur HBOOT, from alpharev.nl
then flash RUU

with PB99IMG_DOWNGRADE from ALPHAREV site i get HBOOT 6.93.9999....

Use Fastboot commander to flash downgrade image
reboot bootloader, thn u get "ALPHAREV UNLOCKED"[ on bootloader screen.
next you can run RUU/I]

If you flash this, you will be on older boot ver
http://alpharev.nl/PB99IMG_downgrade.zip

no change...
still on hboot screen i have :
--- Alpharev ---
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
...

Have you flashed RUU????

yes, i did - no change.
when flashing 'downgrade' from alpharev im getting hboot ver 6.93.9999 so i flashed with hboot-stock from alpharev so i get 6.93.1002...but how to get 0.92/0.93 ?

Getting out of mind now
well, now i can only say l try downgrading froyo 2.2 to 2.1.
or w8 fr others suggestion

ok...any guide? will give it a try...
also a question - why , when installing PB99IMG (full) through HBOOT i get BYPASSED on downloader ? how can I (we) switch it to OK ?

Ok first flash the stock bravo HBOOT, then flash the downgrader (all in fastboot), then run the RUU and you will be a-okay. Try running the RUU from your PC instead of the PB99IMG if it doesn't work that way.

gekko44 said:
yes, i did - no change.
when flashing 'downgrade' from alpharev im getting hboot ver 6.93.9999 so i flashed with hboot-stock from alpharev so i get 6.93.1002...but how to get 0.92/0.93 ?
Click to expand...
Click to collapse
Wow just wow...
10 people tell you to follow 2 simple steps and you do something completely different. No wonder it went wrong, never should have rooted in the first place.
Do as follows and i promise you it'll work:
1. flash downgrader hboot either via "fastboot flash hboot downgraderhboot.img" or by using the PB99IMG.zip containing it from alpharev.(it will and should still say 6.93.1002)
2. flash the ruu by putting the extracted PB99IMG.zip on and let the downgrader hboot flash it
Can give you the technical reasons for why everything you have done is wrong, but i won't bother.

ok....i flashed with stock bravo HBOOT, then flashed the downgrader (all in fastboot) and then run RUU.....
got HBOOT 0.83.0001, NO alpharev.....but...RUU failed to finish update (error 140) and have no system at all...all i can is to get to hboot menu....
@mortenmhp
im a noob not an expert. thanks for helping me feeling like an idiot...
EDIT:
when trying to update trough PB99IMG i get :
Main Version is older !
Update Fail!

gekko44 said:
ok....i flashed with stock bravo HBOOT, then flashed the downgrader (all in fastboot) and then run RUU.....
got HBOOT 0.83.0001, NO alpharev.....but...RUU failed to finish update (error 140) and have no system at all...all i can is to get to hboot menu....
@mortenmhp
im a noob not an expert. thanks for helping me feeling like an idiot...
Click to expand...
Click to collapse
np exactly what i was going for....
0.83 is very old (from android 2.1 rom) and error 140 is a bootloader version error which indicates that you are not allowed to downgrade. Get the newer ruu instead as advised all over this forum(version is 2.29.405)
Also sorry for being harsh, but I've personally explained this exact problem 2-3 times and seen plenty of others trying to do the same, so i know there are several topics explaining it just fine if you bothered to search properly.

ok...used newest RUU (RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed) , extracted rom.zip, changed name to PB99IMG.zip, put to sdcard...now i get CID INCORRECT...ehhh....searching this (and some other) forums all the time... damn...i really feel stupid....
gonna try with goldcard.....tomorrow morning....got enough of this for today...thanks everyone for their time and effort....hope the GC will do the stuff..

bah sure u downloaded the right file and not one for cdma or t-mobile eg.?
Also please boot to fastboot and plug it via usb and enter "fastboot oem boot" find the line that says CID and type the output here.
You should also be able to compare the cid of your device from above to a file in the PB99IMG.zip
edit: also your device might be branded meaning it will have another CID and it wont allow you to install the wwe one. Then you'll have to either find one for your carrier or make yourself a goldcard(allowing you to install the wwe ruu anyway).

Did what You suggested , got:
... INFO[ERR] boot image does not exist!!!
OKAY
...
EDIT:
downloaded 3rd from this list forum.xda-developers.com/showthread.php?t=695667

mortenmhp said:
Wow just wow...
10 people tell you to follow 2 simple steps and you do something completely different.
No wonder it went wrong, never should have rooted in the first place.
Click to expand...
Click to collapse
Did you forget your chilax-pills today?
Where you born with all that knowledge, as the only one in the world? No...?
Well then... everybody is at a different level of knowledge in here...
so please take your chilax-pills, go get laid, or whatever you need,
and try talking a little bit more kindly to people,
instead of bashing them with "Im soooo good - and you`re sooo stupid" attitude,
or just dont help! No need to trash people like that!
Have a nice day.

[Q] hboot 1.03.0003 problem

Hello guys.
As I can see - my problem is unique and almost noone has solved it, but I won't give up.
Okay, let's start from the beginning.
I had stock firmware with 2.29 OS version (no matter to write all the numbers of version, just 2.29). In order to have something newer and with new HTC Sense, I managed to get the Cool3D RunnyMede v7 firmware on my phone.
Like in many tutorials I went on htcdev.com and used to unlocking bootloader. I followed all the steps and finally got the unlocked butloader, but with s-on (I saw no matter on it, as I do now).
Downloaded the clockwork mod, I proceeded to flash my phone, and after some problems I had the custom firmware. Okay, all is good, but what the problem? Problem was that I could not use anything of phone's functions, just had no service. Okay, it was the radio problem. It was caused by that fact that while s-on, I upgrade the firmware but not radio (but it was in archive with firmware too).
Cause I had s-on I had no chance to flash my radio.
S-on was caused by htcdev RUU updater, that made my phone having hboot 1.03.0003.
Now I have no firmware, just clockworkmod 2.5.0.7, s-on and hboot 1.03.0003.
When I try to setup official RUU I have the 140 error, it means that in ROM that I try to set up is lower version of hboot that I have. When I try to replace it on my hboot (extracting it from the hboot updater) I get error 132, it means CID problem, but in android-info.txt in ROM's file I have the same, that on my phone.
Can anyone help me, or I just have to write to HTC Support, and after having no answer break my phone about the nearest wall?..

Check bortak's troubleshooting guide (see my sig).

Thanks, but I've seen it for many times, don't know what can help me...
Maybe goldcard?.. Anything else?

Hi there is a way how to downgrade your 1.03 hboot in resources of bortak's guide or you can find it here
after downgrade you can run revolutionary to get s-off and flash your preferred radio

Hey guy, it looks helpful as nothing I've seen before; thank you; I'll write about the result.

It works.)
Thanks a lot.

Can't downgrade
I have an HTC Desire
S-ON
Bravo PVT4
HBOOT: 1.03.0003
MI CROP-05-1d
TOUCH PANEL-SYNT0101
RADIO-05.11.05.27
And I need a goldcard to be able to downgrade it to 1.02.0001 and I can't get it anywhere, all I've got is the CID 00B100DC08D480804734305553445303 but the website I went to is not working anymore to get the IMG. PLEASE help!

Hi Lagevae
Lagevae said:
It works.)
Thanks a lot.
Click to expand...
Click to collapse
i have the same problem. but the link that give kotag82. not help me, i cant open a USB debugging connection. I like to now how you got to work.

likeadracula said:
i have the same problem. but the link that give kotag82. not help me, i cant open a USB debugging connection. I like to now how you got to work.
Click to expand...
Click to collapse
Follow this guide:
http://forum.xda-developers.com/showthread.php?t=1550397

abaaaabbbb63 said:
Follow this guide:
http://forum.xda-developers.com/showthread.php?t=1550397
Click to expand...
Click to collapse
i tried that link to... i have install clockworkmod and works fine but Cooldroid_Revolution_v9.0 firmware stuck at second htc logo and all ather firmwares that i managed to install. Ruu give error 155. The problem is that i cant access to firmware to use USB debugging for Downgrade the hboot.. and when I tried ι take lot of errors.. looks like dead and .. If someone now how to start USB debugging without the firmware from fastboot it could to samething..

likeadracula said:
i tried that link to... i have install clockworkmod and works fine but Cooldroid_Revolution_v9.0 firmware stuck at second htc logo and all ather firmwares that i managed to install. Ruu give error 155. The problem is that i cant access to firmware to use USB debugging for Downgrade the hboot.. and when I tried ι take lot of errors.. looks like dead and .. If someone now how to start USB debugging without the firmware from fastboot it could to samething..
Click to expand...
Click to collapse
What about this one?
http://forum.xda-developers.com/showthread.php?p=24039156

abaaaabbbb63 said:
What about this one?
http://forum.xda-developers.com/showthread.php?p=24039156
Click to expand...
Click to collapse
Yes the same problem.. at the step 8.. i dont now what to do.. i dont now if i need to use GoldCard my cid is HTC_N34 and i cant change it..

[Q] updated to HBOOT 1.36 From 1.31 but now my phone RELOACKED

hi,
i updated my hboot from 1.31 to 1.36 with
http://forum.xda-developers.com/showthread.php?t=1924003
after all the procces (i didnt fully understand him) im now standing with hboot 1.36 but I see RELOCKED above and I cant get inside the Recovery.
I got some error in the procces but still now its 1.36.
now how do I unlock my phone again?

Like you did the first time ! Or if you kept the unlock token.bin file you could unlock it with fastboot command !

Orong89 said:
hi,
i updated my hboot from 1.31 to 1.36 with
http://forum.xda-developers.com/showthread.php?t=1924003
after all the procces (i didnt fully understand him) im now standing with hboot 1.36 but I see RELOCKED above and I cant get inside the Recovery.
I got some error in the procces but still now its 1.36.
now how do I unlock my phone again?
Click to expand...
Click to collapse
Go to www.htcdev.com and Register yourself on the site.
Select 'unlock bootloader'.
Under select your device : select 'all other supported models'
And then follow the guide step by step
Sent from my unlocked HTC One X using XDA premium.

anks257 said:
Go to www.htcdev.com and Register yourself on the site.
Select 'unlock bootloader'.
Under select your device : select 'all other supported models'
And then follow the guide step by step
Sent from my unlocked HTC One X using XDA premium.
Click to expand...
Click to collapse
If his bootloader says "relocked" it means that he already unlocked it, so he's got the unlock binary. No need to use HTCdev again...

Orong89 said:
hi,
i updated my hboot from 1.31 to 1.36 with
http://forum.xda-developers.com/showthread.php?t=1924003
after all the procces (i didnt fully understand him) im now standing with hboot 1.36 but I see RELOCKED above and I cant get inside the Recovery.
I got some error in the procces but still now its 1.36.
now how do I unlock my phone again?
Click to expand...
Click to collapse
in my personal opinion waiting for the sense 4.1 is BS. i tried it today, ok its good, better than ICS of course, but cm rules dude. i was trying to take cm10 off because it has some fast battery draining issues in my personal opinion. but dude cm is fast, very reliable and when i tried sense again today, i was confused. the best thing of sense is its camera. Unique in my opinion, and the syncing. try cm10

litmeister said:
in my personal opinion waiting for the sense 4.1 is BS. i tried it today, ok its good, better than ICS of course, but cm rules dude. i was trying to take cm10 off because it has some fast battery draining issues in my personal opinion. but dude cm is fast, very reliable and when i tried sense again today, i was confused. the best thing of sense is its camera. Unique in my opinion, and the syncing. try cm10
Click to expand...
Click to collapse
I have the same issue and now when I tried to type:
fastboot flash unlocktocken Unlock_code.bin
it says:
sending 'unlocktocken' (0 KB)...
OKAY [ 0.154s]
writing 'unlocktocken'...
FAILED (remote: not allowed)
finished. total time: 0.368s
I can't manage to remove the "FAILED (remote: not allowed) " .
Does anyone can help me ?

Spell token correctly
Sent from my HTC One X using xda premium

Sent from my HTC One X using xda premium

[Q] I can't flash CWM recovery on s-off HOX, advice?

I've been following the steps provided here and am stuck at step 8 where I am unable to flash a custom recovery (i.e. CWM) no matter what i do!
I've tried rebooting the computer; resetting the phone and trying another computer but no go. I have s-off and SuperCID (11111111).
I'd like to know what else i should try? What am I doing wrong? Is this a driver problem?
I had issues with flashing the firmware also (actually flashing anything in general), but i just changed my CID to 11111111 and so was finally able to update the hboot (currently 1.39) and software (currently 3.17.728.1)
The error message i get when trying to flash the recovery through fastboot is :
sending 'recovery' (5742KB)...
OKAY [ 0.759s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.970s
I haven't unlocked my bootloader before flashing recovery because i assumed with a s-off HOX you didn't need to?
Please i need some advice as the ROM I started with (ARHD) is wiped out!

Remote not allowed is an error that pops up indeed when the bootloader is locked, just unlock it via the HTC dev site and flash again.
And your assumption is right but it does not seem to work in your case.

Yeah. With S-OFF, you can probably set it back to **LOCKED** state when needed.
Sent from my One X

Of course It's that simple! :s
Mr Hofs said:
Remote not allowed is an error that pops up indeed when the bootloader is locked, just unlock it via the HTC dev site and flash again.
And your assumption is right but it does not seem to work in your case.
Click to expand...
Click to collapse
Ok I'll try that right now, cheers.

Thanks, but no touch on ARHD 18.1
Thanks for that, it all worked out But I had the same issue that some people have with the touch screen not working, at all!
So I've just flashed the very first nandroid backup listed here since my original CID was HTC_023 and am now running on a stock android 4.1.1 Sense ROM.
It seems to be a problem with HTC_023 devices. These two threads (1) (2) discuss this issue further if anyone is interested.
So far there seems to be no progress in getting a custom ROM working with touch according to them, i think?

Odp: [Q] I can't flash CWM recovery on s-off HOX, advice?
Jam0rama said:
Thanks for that, it all worked out But I had the same issue that some people have with the touch screen not working, at all!
So I've just flashed the very first nandroid backup listed here since my original CID was HTC_023 and am now running on a stock android 4.1.1 Sense ROM.
It seems to be a problem with HTC_023 devices. These two threads (1) (2) discuss this issue further if anyone is interested.
So far there seems to be no progress in getting a custom ROM working with touch according to them, i think?
Click to expand...
Click to collapse
You might want to check this topic
http://forum.xda-developers.com/showthread.php?t=2120714