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
Related
hey everyone,
lately i've been having problems with flashing the stock 1.34 PC10IMG.zip file.
and below i will show you what is exactly going on.
i found the exact problem that i have , 2 other people got the exact same problem.
""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 thought it would work, 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)but everytime when i see the sd loading I get the "Lack of heap!" error...""
That is exactly what i did, i also got the same boot version , but what i did after that is reroot , and put a custom rom on my phone. , i get the same lack of heap error...
What i've also tried is to flash through the pc10img and fastboot but then i will get a message"fastboot flash system system.img
sending 'system' (571388 KB)... FAILED (remote: data length is too large)
finished. total time: 0.005s"
So that ended up as a failure.
Anyone any idea how to fix this very complicated issue, hopefully some experienced people can help me! , i would really appreciate it allot!!!
First, wrong forum. Second, you're going to have to clean up your problem description a bit, I have no idea where you're at in the process or what exactly is wrong other than trying to flash a rom on a device that it is not intended for.
Hi
I tried to use RUU for get stock froyo and erase s-off.
Got goldcard, after tried to install RUU and it's stuck.
hboot was cm7r2 , after it i got stock.
Now i get error 131.
Please help me !
hey search..there is an other thread opened just few threads down your..
i saw it, but still it not helped me =(
btw, only because im good, read alpharev.nl...u need to flash the damn downgrader hboot, then and ONLY then u can flash the RUU
name.vic said:
i saw it, but still it not helped me =(
Click to expand...
Click to collapse
so u open a new one??????????? Its called spam!
Ask in the same thead the next time
Sorry for spam =(
I still get same message 131.
And now my screen don't work .
Some suggestions ?
name.vic said:
Sorry for spam =(
I still get same message 131.
And now my screen don't work .
Some suggestions ?
Click to expand...
Click to collapse
what steps u did?
131 mean wrong ruu i think
in fastboot i flashed downgrade, restart , and now black screen. but fastboot commands still works, i can load recovery via cmd
C:\android-sdk-windows\tools>fastboot flash hboot bravo_downgrade.img
sending 'hboot' (512 KB)...
OKAY [ 0.085s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.140s
Click to expand...
Click to collapse
My desire is dead =(
When i connect usb i hear the sound of connection, nothing else =(
up
(10 simbols)
it's not dead!! you just flashed an AMOLED RUU for your SLCD phone. (you flashed an old RUU that's incompatible with your phone)
http://forum.xda-developers.com/showthread.php?t=831734 fix is here.
I tried to downgrade, but it stuck on this
Android 2.2 (froyo) to 2.1 downgrade utility
============================================
v2.3b
For more information, see thread:
http://forum.xda-developers.com/showthread.php?t=768256
Press ctrl-c to exit this utility.
Waiting for device. Ensure USB debugging is enabled.
* server not running *
* daemon not running. starting it now *
* daemon started successfully *
Click to expand...
Click to collapse
What i do wrong?
Thanks
You didn't go to alpharev.nl They have a HBOOT Downgrader that would allow you to flash the 2.3 update, You are now going backwards, flashing RUUs for AMOLED instead of SLCD
Sent from my HTC Desire using XDA App
Just flashed RUU 2.3.3 from HTCdev, it works !
if ur desire is dead and didnot open again
by any way not open
go to HTC AND tell them u did factory reset and that happend they will change it for u
Your Desire is not dead, its just not up yet. If like me, you keep getting 131 error when trying to put a stock rom on,"I did the same as you, tried to put stock rom on a cm7 hboot" then try the upgrade to 2.3.3 Gingerbread RUU from HTC. worked for me. then I unrooted by the revolutionary method.
Hi,
Please can someone help.
I have a desire which was originally Vodafone. I rooted, s-off, clockwork recovery etc and have been running custom roms for ages (Though I don't flash at all often.
I tried to bring it back to stock and flashed an original Vodafone ROM through RRU. It seemed to work but errored at the end. Now I am stuck.
I have no screen display at all. If I press power the phone vibrates once but nothing else. no splash screen, nothing. Pressing "back+power" doesn't do anything either.
If I load a stock RRU it used to run through but give me a Cust ID doesn't match error 131. I have now made a goldcard and now I get a bootloader 140 error. I have tried to use androidflasher but that reports I am now s-off so fails.
RUU reports I have image 2.33.161.2 now trying to change to 1.0.2.10 (although I have tried a number of wwe and vodafone RRUs
rru goes through bootloader. erasing user data and sending signature but then fails to the 140 bootloader version error
Is it the conflict of coming from custom roms or just that it will not downgrade to a lower rom? does anyone have a higher rom? Please help. I can't even get anything on the screen to know I am in bootloader although RRU obviously thinks I am
Please help. What are my next steps. I am now totally lost!
Thank you
Did u flash alpharev downgrader before flashing the ruu?
Sent from my HTC Desire
jmcclue said:
Did u flash alpharev downgrader before flashing the ruu?
Sent from my HTC Desire
Click to expand...
Click to collapse
No, That was the big stupid move! and I think what trashed it. That and the not having a Goldcard.
I have however finally solved it. I put in the goldcard and flashed rru from the HTC developers site.
http://forum.xda-developers.com/showthread.php?t=1772499
That fixed it. I guess it was complaining that the Vodafone version I had flashed badly was of a higher version number than the other one I was trying to fix with.
Took all day but finally got there.
Thanks for the reply
Cool, glad it works now
Sent from my HTC Desire
First off all you flashed amoled ruu to slcd device, or the opposite.
Once more, nobody wants to search the forum to see experience of other people ans simply use 2.3 RUU.
Sent from my HTC Desire using Flashes and Thunders
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
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