This issue is SOLVED, please go to the thread by qpop for full details on what to do:
http://forum.xda-developers.com/showthread.php?p=9523168#post9523168
There were problems permarooting and S-OFF on the latest batch of Desire Zs (shipped by Vodafone UK, BelCompany Netherlands, and others).
Stock details of the device:
HTC Desire Z, PC 10110, branded Vodafone UK
---------------------------------------
VISION PVT SHIP S-ON
HBOOT-0.85.0005
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010,20:10:38
---------------------------------------
Android Version 2.2
Baseband version 12.28b.60.140eU_26.03.02.26_M
Kernel version 2.6.32.21-g9d69527, [email protected] #1, Fri Oct 29 14:49:32 CST 2010
Build number 1.34.161.6 CL273326 release-keys
Software number 1.34.161.6
Browser version WebKit 3.1
---------------------------------------
Model number: HTC Desire Z A7272
Device serial number: SH0BCRT#####
Product number: 99HLW041-00 B (under battery)
Following the hard work of those in the #G2ROOT room in IRC, and the support of PaulOBriens Visionary apk, we are happy to say this issue is solved. Please do consider providing scotty2 with a donation, I know I will
For convenience I'm uploaded the relevant RUU to my domain and will do the same with any other relevant files posted. These can be found at http://ryanmacg.co.uk/Zroot
hope this helps
Currently same problem with HTC Desire Z bought in Amsterdam, Netherlands yesterday at BelCompany (unbranded).
some data seem to be different though:
kernel: 2.6.32.21-gd2764ed [email protected] #1 Tue Oct 26 16:04:03 CST 2010
build-number: 1.34.405.5 CL273327 release-keys
Software-number: 1.34.405.5
Regards,
David
shorty2k5 said:
Currently same problem with HTC Desire Z bought in Amsterdam, Netherlands yesterday at BelCompany (unbranded).
some data seem to be different though:
kernel: 2.6.32.21-gd2764ed [email protected] #1 Tue Oct 26 16:04:03 CST 2010
build-number: 1.34.405.5 CL273327 release-keys
Software-number: 1.34.405.5
Regards,
David
Click to expand...
Click to collapse
Just spoke to someone on irc who had some issues rooting with the same kernel version, did you try rage or visionary? He said that Rage worked but visionary wouldn't
I tried them both in order to get a permanent root, but I was not able to permanently root - neither via visionary nor rage. Only the temp. root on bootup with visionary is working as expected.
What's the IRC channel you're talking about? Maybe I can support you in any kind of way.
Regards,
David
shorty2k5 said:
What's the IRC channel you're talking about? Maybe I can support you in any kind of way.
Click to expand...
Click to collapse
We should first check if it is the same problem. Could you please come into #G2ROOT on freenode and I will guide you through using wpthis and dmesg so we can see what is happening. If it is the same issue that is certainly of interest to us
Here you go...
This is off my Bell Desire Z running on the euro 1.34.405.5
S'Off and permarooted.
Hope this helps.
(change x to t)
hxxp://www.megaupload.com/?d=NUTHQ1NR
shorty2k5 said:
Currently same problem with HTC Desire Z bought in Amsterdam, Netherlands yesterday at BelCompany (unbranded).
some data seem to be different though:
kernel: 2.6.32.21-gd2764ed [email protected] #1 Tue Oct 26 16:04:03 CST 2010
build-number: 1.34.405.5 CL273327 release-keys
Software-number: 1.34.405.5
Click to expand...
Click to collapse
The only different thing there from my phone is the "CL273327" bit. Not sure if that is significant. But the kernel version is exactly the same, which I suspect is more important.
I'm not sure this thread really wants to turn into a general "I've got problems with perm root" thread ?
evilive27 said:
Here you go...
This is off my Bell Desire Z running on the euro 1.34.405.5
S'Off and permarooted.
Click to expand...
Click to collapse
I don't think that's what they need though ?
skitzophrenick said:
Currently we need someone else with a successfully permarooted and S-OFF Desire Z who can roll back to 1.22.405.1 and dump partitions 3 and 5.
Click to expand...
Click to collapse
steviewevie said:
I don't think that's what they need though ?
Click to expand...
Click to collapse
OOPS!!! sorry
evilive27 said:
OOPS!!! sorry
Click to expand...
Click to collapse
Don't suppose you'd be willing to roll back to .1 at all?
steviewevie said:
The only different thing there from my phone is the "CL273327" bit. Not sure if that is significant. But the kernel version is exactly the same, which I suspect is more important.
Click to expand...
Click to collapse
I assume you have also been unable to permroot/S-OFF with this?
steviewevie said:
I'm not sure this thread really wants to turn into a general "I've got problems with perm root" thread ?
Click to expand...
Click to collapse
Definitely not, though its worth noting shorty2k5s model as a non-Vodafone unit with the same difficulty. Am updating main post to reflect this
skitzophrenick said:
I assume you have also been unable to permroot/S-OFF with this?
Click to expand...
Click to collapse
Me ? Yes, I've permarooted my phone, using the "rage" method. It's not a Vodafone-branded one though.
My ROM is 1.34.405.5 CL273326, kernel 2.6.32.21-gd2764ed
I downloaded the Voda RUU from post 2.
If this helps, I'm unpacking it.
The Vodafone 1.22.405.1 firmware is SEP 26 (!!!) - one month older than the OCT 26 generic euro firmware.
I will upload the kernel later,along with and other important stuff you require.
gtrab said:
I downloaded the Voda RUU from post 2.
If this helps, I'm unpacking it.
The Vodafone 1.22.405.1 firmware is SEP 26 (!!!) - one month older than the OCT 26 generic euro firmware.
I will upload the kernel later,along with and other important stuff you require.
Click to expand...
Click to collapse
It's not the VF RUU but skitz managed to debrand back to it so we need to compare the files that you get compared to the one he currently has
Really appreciate it.
gtrab said:
I downloaded the Voda RUU from post 2.
If this helps, I'm unpacking it.
The Vodafone 1.22.405.1 firmware is SEP 26 (!!!) - one month older than the OCT 26 generic euro firmware.
I will upload the kernel later,along with and other important stuff you require.
Click to expand...
Click to collapse
As RyanMacG points out this is the debranded RUU im currently running on my VF Desire Z. If you have a rooted, S-OFF Desire Z we would really appreciate it if you downgraded to this RUU and dumped the partitions noted in post #1. Would that be possible?
I see from #G2ROOT that scotty is on the case, which is great.
I still find it very hard to believe that Vodafone/HTC have done anything special on a ROM dated Oct 29 (well before permanent root/NAND unlock was achieved) to deliberately mess things up for us. Probably more an accident or other weird occurrence ?
I have a permarooted/S-OFF'd DZ. How easy is it for me to flash this old RUU to help you guys out ? I also don't want to get stuck in a bad place lol.
I don't mind doing it if it's going to be straightforward. I need to know how to do it so that I can easily get back to where I am now, e.g. hopefully I can restore a Nandroid backup of my current ROM ?
steviewevie said:
I have a permarooted/S-OFF'd DZ... I also don't want to get stuck in a bad place lol... hopefully I can restore a Nandroid backup of my current ROM ?
Click to expand...
Click to collapse
Awesome, thanks. Well in theory you shouldnt have any problems restoring a backup but the RUU does replace the radio, hboot, recovery, system, etc. so if you want everything exactly as they are you would need to do a few things first. I would recommend looking for a suitable RUU to match your setup when you rooted, that way you get to keep radio and anything else that you left stock, and it wouldnt hurt to run TitaniumBackup incase nandroid doesnt work out and it needs a reinstall.
Then you can "upgrade" back to this to redo the permaroot and S-OFF. The current stats for the 1.22.405.1 RUU are below, providing they are all older than your current setup *fingers crossed* I cant see any reason why you shouldnt be able to root again afterwards
HBOOT-0.85.0002
Radio-26.02.00.24_M2
Sep 17 2010,17:13:27
Baseband: 12.26.60.1301U_26.02.00.24_M2
Kernel: 2.6.32.21-gfbe0094, [email protected] #1, Sat Sep 25 02:34:14 CST 2010
Build number: 1.22.405.1 CL261471 release-keys
The method for downgrading is described in http://forum.xda-developers.com/showthread.php?t=832503 and you can get the 1.22.405.1 RUU from either post #6 (multiupload) on that thread or directly from RyanMacGs server on post #2 here. You use the same method to upgrade later except you dont have to change anything in the misc partition, just dump it to the microSD and HBOOT.
So I need to go through the Gold Card stuff ?
Hello again XDA,
since I suddenly really need the money I spent on my Desire today for family reasons, I want to return it tomorrow
It's a German 2.2 Froyo Desire, unlocked, T-Mobile branded, stock ROM.
Nothing done to it besides running unrEVOked, which rooted the Desire and flashed a useless Clockwork recovery. Useless because it's a Erasesize 40000 Desire and everything in Clockwork gives an error.
I looked for RUUs but I haven't found anything regarding German T-Mobile ones...
Here's the info from the stock ROM:
Android version: 2.2
Baseband Version: 32.49.00.32U_5.11.05.27
Kernel version: 2.6.32.15-gd96f2c0 [email protected] #1
Build Number: 2.12.110.4 CL264529 release-keys
Software number: 2.12.110.4
Browser version: WebKit 3.1
Hardware info:
BRAVO PVT4 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010,17:52:18
Erasesize 40000
So how can I safely unroot it?
It's really urgent, any help is greatly appreciated!
there isn't any german T-MO RUU. if you want to return it your best chance is to try to downgrade by using this guide http://forum.xda-developers.com/showthread.php?t=832659
and then try to obtain the OTA by checking for new updates.
SkyDX said:
Hello again XDA,
since I suddenly really need the money I spent on my Desire today for family reasons, I want to return it tomorrow
It's a German 2.2 Froyo Desire, unlocked, T-Mobile branded, stock ROM.
Nothing done to it besides running unrEVOked, which rooted the Desire and flashed a useless Clockwork recovery. Useless because it's a Erasesize 40000 Desire and everything in Clockwork gives an error.
I looked for RUUs but I haven't found anything regarding German T-Mobile ones...
Here's the info from the stock ROM:
Android version: 2.2
Baseband Version: 32.49.00.32U_5.11.05.27
Kernel version: 2.6.32.15-gd96f2c0 [email protected] #1
Build Number: 2.12.110.4 CL264529 release-keys
Software number: 2.12.110.4
Browser version: WebKit 3.1
Hardware info:
BRAVO PVT4 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010,17:52:18
Erasesize 40000
So how can I safely unroot it?
It's really urgent, any help is greatly appreciated!
Click to expand...
Click to collapse
Hello SkyDX,
did you manage to solve your problem?
Hi,
I know there are topics solving the similar problems but I decided to create a new thread because I've never found an answer for me...
I have my desire originaly from T-Mobile from the Czech republic and I've debranded it to WWE (2.29.405.2) and HBoot is 0.93.0001. Now my desire restarts quite often so I want to get it for warranty repair but I have to get TMO software. I'm really not familiar with all the stuff about the flashing etc. I provide this info:
from boot:
BRAVO PVT3 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
Android: 2.2,
Baseband version: 32.49.00.32U_5.11.05.27,
Kernel version: 2.6.32.15-gf5a401c [email protected]#1,
Build number: 2.29.405.2 CL263770 release-keys,
Software number: 2.29.405.2
I already know when I want to use RUU to change soft with the same third number (405, otherwise I get error 140??) but I need to load TMO with the third number 110. How I can achieve that? Is there any posibility to return from WWE to TMO brand? Tnx
ADD: I've tried RUU:
RUU_Bravo_Froyo_TMO_AT_2.12.112.1_Radio_32.46.00.32U_5.10.05.17_2_release_143754_signed.exe
RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed.exe
x.xx.110.x is T-Mobile UK and the only RUU to leak is that one you've linked above. you might have to downgrade to a lower HBOOT to get it working (and that RUU is for AMOLED screens only)
Tnx. So I have to find out how to downgrade to 0.83 (the original state) and I don't know if I have AMOLED or not. There was a tutorial by comparing the background of my display to black but still don't know. Is in the phone any other clue to get know what type of a display I have?
ADD: Hmm, I think I have SLCD because when I changed the rom for the first time, display left black after starting.. so maybe this is the clue
ADD2: Should I use this guide to downgrade or this is not the golden path? http://forum.xda-developers.com/showthread.php?t=768256&highlight=revoke
Only US customers use CDMA - if you have a SIM card you're GSM
yep, I've already read it and now performing downgrade... we'll see.
ADD: Android: 2.1-update 1,
Baseband version: 32.41.00.32U_4.08.00.09,
Kernel version: 2.6.29-0cb9f166 [email protected]#1,
Build number: 1.21.405.2 CL174215 release-keys,
Software number: 1.21.405.2
HBoot 0.83.0001
Should I try use RUU to load the TMO rom now?
How I can realise if the RUU is for AMOLED or SLCD? Now I have a simple quest: load a T-Mobile rom for a SLCD display...
The reason that works is due to it being OK with SLCD screens, the T-Mobile RUU might flash now but you may end up black screening your handset
EddyOS said:
The reason that works is due to it being OK with SLCD screens, the T-Mobile RUU might flash now but you may end up black screening your handset
Click to expand...
Click to collapse
But when I bought the phone it was branded T-Mobile. Ok, what should I do to load it and be ok with the highest probability?
Nothing you can do, there isn't a newer RUU leaked from T-Mobile UK
EddyOS said:
Nothing you can do, there isn't a newer RUU leaked from T-Mobile UK
Click to expand...
Click to collapse
I decided to use the one from AT and it works so I have TMO soft in my phone and ready for warranty repair. (hope)
Thanks for all your patience and we'll see.
Hello,
I recently got a Wildfire S A510b which is branded. (It says Telstra and Next just after HTC screen on boot-up and has a TelstraOne app which is what I suppose branded means, right?)
When I load up the bootloader this is what shows up:
MARVEL PVT SHIP S-OFF RL
HBOOT-1.03.0000
MICROP-0451
RADIO-7.46.35.08
Jun 2 2011, 16:17:50
It's running Android 2.3.3 with HTC Sense 2.1
Build number: 1.52.841.2 CL72061
Baseband version: 47.10.35.3029H_7.46.35.08
Kernel version: 2.6.35.10-g105f9bd
With this, would I be able to debrand my phone and then update to 2.3.5 and finally root it?
I saw this thread: http://forum.xda-developers.com/showthread.php?t=1142529
Would this work? Seems like the ROM is a European one but I have Australian phone. I also saw there was a more recent ROM:
http://shipped-roms.com/download.ph...5.3032H_7.49.36.01M_release_209754_signed.zip
Would this be better and is it 2.3.5?
Thanks in advance
c0mputeRb0y
I hope this is in the right forum, if not I do apologize. Please move if need be.
I friend of mine needs a phone for a few months until he is ready for an upgrade so I offered him my inc2. Unfortunately I have not touched it in over a year and a half and wanted to do a little upgrade on it. Here is what is current.
Android: 2.2.1
BaseBand: 20.23W.30.0803U_0.99.01.0225_2
Kernel: 2.6.35.9-gdd66b2f [email protected] #1
Build: 1.34.605.4 CL341571
Software: 1.34.605.4
Recovery:
AlphaRev vivo_w XB ship S-OFF RL
HBOOT-6.13.1002
Radio-0.99.01.0225_2
eMMC-boot
I want to Upgrade to IncrediblyParanoid rom. What do I need to do to make this happen as far as baseband, kernels ect. Sort of need the steps to do it not the details of how. I should be able to figure that out but if you like that is fine also.
Thanks in advance
Ray