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 ?
Related
Hello all, I've decided to root my T-mobile Froyo Desire at last.
I'm gonna use unrevoked using windows or maybe linux
and plan to install the LeeDroid ROM.
I understand I have to back up my RUU but don't know which one is mine.
Checked the shipped ROMs page
PHP:
http://shipped-roms.com/index.php?category=android&model=Bravo
and found 3 similar to mine. Which is the right one?
RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe
RUU_Bravo_Froyo_TELUS_WWE_2.25.661.2_Radio_32.49.00.32U_5.11.05.27_release_151557_signed.exe
PB99IMG_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.zip
My phone is:
baseband
32.49.00.32U_5.11.05.27
Kernel version
2.6.32.15-gd96f2c0
[email protected] #1
build number
2.12.110.4 CL274424 release-keys
thanks
I think it is this - RUU_Bravo_Froyo_TMO_AT_2.12.112.1_Radio_32.46.00.32U_5.10.05.17_2_release_143754_signed.exe
TMO probably stands for T mobile and the the build is pretty close, 2.12.110 ~ 2.12.112.1
Let someone correct me if I am wrong .
Thanks 3722
No further replies so I'm gonna have to assume you're right.
That isn't the right one, your RUU isn't available yet...the only ones available are:
http://shipped-roms.com/download.ph...io_32.30.00.28U_4.05.00.11_release_122755.exe
http://shipped-roms.com/download.ph...00.28U_4.06.00.02_2_release_127570_signed.exe
O...
So does that mean its unwise for me to root if my RUU isn't out?
If the 2 ones you've linked are the only ones around am I still OK to root and
not have problems with warranty?
Which one of the 2 is the correct one?
thanks
I wouldn't yet as you've likely got an SLCD screen and those 2 RUUs are for AMOLED only...
So I can't root without the safety net of the backup RUU?
I really need to root and make more space on internal memory using app2sd+
since the froyo version isn't good enough.
Such a shame that I'm now limited in the number of apps I install
thanks for the help anyway guys.
RUU updated?
Bumping my post from November just in case....
I noticed some updated RUUs on http://shipped-roms.com/shipped/Bravo/
So wondering if any are now the right ones for my desire so I can finally
root the phone and have a backup for the warranty?
baseband
32.49.00.32U_5.11.05.27
Kernel version
2.6.32.15-gd96f2c0
[email protected] #1
build number
2.12.110.4 CL274424 release-keys
thanks again
I'm in the same. Boat but decided to root anyway. Just use a wwe one if you really have to i doubt they will make a fuss Or do what I did albeit it was by accident, flash the amoled ruu which will kill the screen and report a screen issue along with whatever issue you have. Risky but worked for me once. Hope i don't need to send it off again
Sent from my HTC Desire using XDA App
there are still no uk tmobile leaked RUU's
its a risk you take
Suppose I'll just do as BashyUK I think.
Had the phone for a while now and unable to install all the apps
I'd like due to the low memory crap.
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.
Hi
My phone was bought from O2 last year and came supplied with 2.1
Since then I flashed it with a stock 2.2, now I'm looking to root etc so would like to have a RUU just in case.
Can anyone point me to the standard O2 2.1 & 2.2 RUU files ?
Also anyone got this RUU ( this is what I'm currently running ) :
BaseBand: 32.49.00.32U_5.11.05.27
Kernel: 2.6.32.15-gf5a401c [email protected] #1
Build: 2.29.405.2 CL263770 release-keys
Software: 2.29.405.2
Thanks
Why would you need the originals? Simple make a backup of the stock you're running now and you'll be fine. As soon as you root you'll loose warrenty anyway.
I'm running the Reflex Rom with the modified hboot - runs great!
martijndutch said:
Why would you need the originals? Simple make a backup of the stock you're running now and you'll be fine. As soon as you root you'll loose warrenty anyway.
I'm running the Reflex Rom with the modified hboot - runs great!
Click to expand...
Click to collapse
I should had sent you here: http://theunlockr.com/2010/06/07/how-to-unroot-the-htc-desire/
See your other post in ROM Development - I've posted it in there (2.29.405.5 is newer than yours so is needed instead of 2.29.405.2)
For reference, you don't have an o2 Desire but an unbranded Desire - if it was an o2 unit the software version would be x.xx.207.x
EDIT: This is a question and, as such, should be in the Q&A section
not having an o2 (or any) branded phone is normally a good thing in my opinion
2.29.405.5 is here: http://forum.xda-developers.com/showthread.php?t=869048
Turns out (s)he debranded going by their other thread.
To the OP - you don't need the 2.1 RUU as I've linked to the 2.2 one in your other thread
martijndutch said:
Why would you need the originals? Simple make a backup of the stock you're running now and you'll be fine. As soon as you root you'll loose warrenty anyway.
t=1054435"]Reflex Rom[/URL] with the modified hboot - runs great!
Click to expand...
Click to collapse
The RUU restore everything, after that you can get warranty again!
Thanks for all the replies.
Yes it an unbranded Desire..
I want the original O2 RUU just incase I had an issue and my goldcard failed !!
Just need to decide on CM7 or GingerVillian and suggestions are welcome.
albert_htc said:
Yes it an unbranded Desire..
Click to expand...
Click to collapse
It's actually DEbranded - if it was unbranded you wouldn't need a gold card to flash an unbranded RUU
rooted fine.
Thanks
Hi guys,
ive swapped (changed via Vodafone (DE)) my S-offed (unbranded) Desire Z.
Now i Got a Phone back witch is branded and S-ON (normal).
Im very annoyed to get root/s-off it/unbrand/OTA. I try any steps to Downgrade the phone but the way with the goldcard dont works for me. Other steps like Easy Radio or gfree are not working. Gfree tells everything went fine but no effect. Very frustrating.
Now i ask you for help. What should i do with this unrooted/S-ON brick ?
Data of the phone are:
VISION PVT SHIP S-ON
HBOOT-0.85.0008
MICROP-0425
RADIO-26.04.02.17_M2
eMMC-boot
Nov 17 2010,21:21:39
In the Phone:
Android Version: 2.2.1
Baseband: 12.28e.60.140f<u_26.04.02.17_M2
Kernel: 2.6.32.21 [email protected] #1
Build-Number: 1.72.161.1 CL296256 release-keys
Software-Number: 1.72.161.1
Browser-Version: WebKit 3.1
The igoldcard-method fails because "invalid CID" i tried 3 SD-Cards (8GB,2GB,1GB), but same failure.
What can i do. How should i start?
Please help me
Greez Nissl
nissl said:
Hi guys,
ive swapped (changed via Vodafone (DE)) my S-offed (unbranded) Desire Z.
Now i Got a Phone back witch is branded and S-ON (normal).
Im very annoyed to get root/s-off it/unbrand/OTA. I try any steps to Downgrade the phone but the way with the goldcard dont works for me. Other steps like Easy Radio or gfree are not working. Gfree tells everything went fine but no effect. Very frustrating.
Now i ask you for help. What should i do with this unrooted/S-ON brick ?
Data of the phone are:
VISION PVT SHIP S-ON
HBOOT-0.85.0008
MICROP-0425
RADIO-26.04.02.17_M2
eMMC-boot
Nov 17 2010,21:21:39
In the Phone:
Android Version: 2.2.1
Baseband: 12.28e.60.140f<u_26.04.02.17_M2
Kernel: 2.6.32.21 [email protected] #1
Build-Number: 1.72.161.1 CL296256 release-keys
Software-Number: 1.72.161.1
Browser-Version: WebKit 3.1
The igoldcard-method fails because "invalid CID" i tried 3 SD-Cards (8GB,2GB,1GB), but same failure.
What can i do. How should i start?
Please help me
Greez Nissl
Click to expand...
Click to collapse
Super tempted to FLAME YOU because you are clearly in the wrong section. If you have a question then PLEASE post in the RIGHT Section which is Q&A.
Also, you clearly haven't searched through the forum cause there are COUNTLESS forum threads about how to root your G2 or Desire Z. Including mine.
Just read the rules, post in the right sections and use the search function and you'll be fine.
Sorry man, but it seems that you didn't read my post carefully.
The goldcardmethod will not work. And it was YOUR tread i have found in my countless searches, and was the how to im followed. Believe me, i try since 5 days to make anything working for me.
pls move my tread and forgive me the "wrong section post".
Hi all
I realise that you get this...a lot...but I am seeing a lot of conflicting information. I am not completely new to rooting and have just received a Desire Z for my girlfriend from Vodafone DE.
I want to root and change Roms and, essentially, give her the same great experience that I had on my old Desire with CM7.
I initially saw the Visionary info, then Rage...most of them say to downgrade, some say not...etc.
I am looking for the best method to root (Preferably with S-OFF)
Code:
Phone Details:
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
Any suggestions would be very much appreciated.
Thanks
If you go to the wiki and follow the guide for the Htc Vision you should be ok, I see you are on version 1.34 so you should be able to root without downgrading
http://forum.xda-developers.com/wiki/HTC_Vision
Superb, thanks - I will give that a try