Database Info

[Q] How to deBRAND HTC Mozart from T-Mobile?

I have HTC Mozart with latest MANGO update from ZUNE!!
It is from Germany, T-MOBILE with all their apps and addons I don't need here in Bosnia!!! BTW, it SIM Unlocked!!!
How, if possible, to make it run with ORIGINAL HTC WP7.5 Mango!!!???
I searched for T-Mobile MANGO ROM but it nowhere to be found,
all I have available on NET is older ROMS from T-Mobile but I am afraid to BRICK my device if I try DOWNGRADING it from Mango to older BOOTS such as 1.28 or 1.30!
Any solution to this, I would appreciate your help!!!

The capital letters and explamation marks don't actually make it easier to help you, BTW.
If you're trying to de-brand the phone, why would you want a T-Mobile-branded ROM? You just want a stock HTC ROM. It has to be for the correct phone, but tht's about it.
If your bootloader (SPL) is already on version 5, you may have a problem replacing the ROM. If you're on 4.5 or lower, you should be able to flash any official ROM without damaging the device.

ok, thanks

Hey all,
First of all I want to say I am glad that I found this forum and community. I think you really can help me out with my (futher) questions.
Since my Telekom branded HTC Mozart won't get the tethering update I am on the search to debrand my HTC Mozart.
I already read that it is essential to have the right SPL Version, now when I enter the bootloader mode I get following data:
PD67100
SPL-4.5.XXXX.X
Now I have a few Questions:
1. Do I need to check other data before starting to debrand the Phone?​2. Will I get further Updates via ZUNE after I debranded my Phone?​3. What are the main reasons to
a. leave it branded?
b. debrand the Phone?​4. Are there some issues with apps form the Marketplace after the debrand?​
And last but not least:
5. Where can I find a working debranded ROM?​
I would really be thankful for any kind of hints and help
Best regards
WPeter7

@WPeter7:
1) Well, you need to make sure that you're getting an unbranded (open market) ROM, and you need to make sure that your ROM matches your hardware. You also need to back up pictures/movies/music/whatever if you have any on the phone that aren't already on the PC.
2) Yes, official ROMs will continue to receive updates.
3) Leaving it branded lets you access carrier-specific features, like TMO's MyAccount app. It also is simply les hassle, and you don't have to lose all your data (which will hppen if you flash a ROM). Unbranding the phone means you remove all carrier customizations, and may receive updates earlier (because the carrier doesn't need to test and customize them).
4) No, not if it's an official ROM and the region is correct (i.e. if you can access apps now and you use the same primary WLID, you'll be able to access them again). However, you'll probably lose access to carrier-specific apps, as mentioned above.
5) Go look in the forum or wiki section specific to your phone. There should be a list of official ROMs. Alternatively, check this thread: http://forum.xda-developers.com/showthread.php?t=1254384

[Q] HTC Desire S - Vodaphone UK Android 2.3.5 & Sense 3.0 update?

Hi there, I currently own an HTC Desire S, the information for it is below:
Android version:
2.3.3
HTC Sense version:
2.1
Software number:
1.28.401.1
Operator name:
vodaphone UK
I haven't yet recieved the Android 2.3.5/Sense 3.0 update. I have tryed searching for updates and checking in using that checkin dial code. I'm just wondering if there's anyway to install this official update onto my phone with minimal risk? I've looked around the forums but can't find exactly what i'm looking for (or I just can't find it!).
Thanks!

I think that you have got the same software version 1.28.401.1 that I had until recently.
I would like to have used to OTA update route but basically got tired of waiting.
I believe that the OTA update was targetted (certainly at first) specifically at those people who already received the previous (troublesome) update to 1.47.
I believe this explains why we didn't get the update.
I loaded the RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed from the development section here and it works a treat. No problems.
The only thing that puzzles me is that my phone is very definitely unbranded and not operator locked, whereas you mention Vodaphone. (If your phone was locked to Vodaphone I would have expected a different software version).
Anyway, if your phone is unlocked like mine, I would certainly recommend using the RUU.
- Steve

fasty said:
I think that you have got the same software version 1.28.401.1 that I had until recently.
I would like to have used to OTA update route but basically got tired of waiting.
I believe that the OTA update was targetted (certainly at first) specifically at those people who already received the previous (troublesome) update to 1.47.
I believe this explains why we didn't get the update.
I loaded the RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed from the development section here and it works a treat. No problems.
The only thing that puzzles me is that my phone is very definitely unbranded and not operator locked, whereas you mention Vodaphone. (If your phone was locked to Vodaphone I would have expected a different software version).
Anyway, if your phone is unlocked like mine, I would certainly recommend using the RUU.
- Steve
Click to expand...
Click to collapse
Thanks very much for your reply.
Yeah, unfortunately my phone is in fact locked to Vodaphone, and I couldn't find the equivalent update that you listed for unlocked phones.

i have a vodafone as well on the same firmware and never got it.
from what i hear the update was pulled due to instability so if you didnt receive it already i very much doubt you will untill a new version is released.
i gave up waiting and went to endymion 3.5

Biogeneric said:
Yeah, unfortunately my phone is in fact locked to Vodaphone, and I couldn't find the equivalent update that you listed for unlocked phones.
Click to expand...
Click to collapse
Are you sure it's locked?!
I thought that software version was for the generic european unlocked version.
Someone else help me here - can the same software number apply to both operator locked and unlocked phones?

fasty said:
Are you sure it's locked?!
I thought that software version was for the generic european unlocked version.
Someone else help me here - can the same software number apply to both operator locked and unlocked phones?
Click to expand...
Click to collapse
i can confirm the htc euro ruu DOES NOT WORK ON VODAFONE BRANDED DEVICES. it bricked my phone and took a whole lot of work to downgrade back to the old hboot to get it working again. the only way to install this version on a voda desire s is via goldcard.it will just give you a cid error and brick your device

djisgod said:
i can confirm the htc euro ruu DOES NOT WORK ON VODAFONE BRANDED DEVICES. it bricked my phone and took a whole lot of work to downgrade back to the old hboot to get it working again. the only way to install this version on a voda desire s is via goldcard.it will just give you a cid error and brick your device
Click to expand...
Click to collapse
Completely agree, great care needed !
But my point was, the software version1.28.401.1 reported by Biogeneric appears to be the same as I had until recently on my unbranded phone.
I thought that if his phone was locked to Vodaphone, wouldn't it have a different software number? Or can the operator lock the phone to their network without changing this software version away form the "generic" one?
- Steve

I'm with Vodaphone, and it says my network is "vodaphone UK" so i'm assuming it's locked! How am I supposed to find out without putting a different networks Sim in?

Biogeneric said:
I'm with Vodaphone, and it says my network is "vodaphone UK" so i'm assuming it's locked! How am I supposed to find out without putting a different networks Sim in?
Click to expand...
Click to collapse
Mine (which recently had the same software version and in NOT operator locked) simply says the name of whatever SIM card you insert.
I suspect your phone may be unlocked, but I'd like feedback from a more experienced developer before suggesting that you load the RUU! We don't want any nasty accidents
By the way, I've just loaded RUU for 2.10.401.8 and it's looking good so far...

Okay, I tried putting in an Orange sim card and setting the network to Orange and it appears to all work (well, I had signal on it, and the network was stated as "Orange"). So i'm assuming my phone is in fact unlocked then?
If so, great news! Am I all clear to update to that unlocked version then? Anyone got a link to the newest one? (Not any mods etc. just the standard update!).
Thanks all!

Biogeneric said:
Okay, I tried putting in an Orange sim card and setting the network to Orange and it appears to all work (well, I had signal on it, and the network was stated as "Orange"). So i'm assuming my phone is in fact unlocked then?
If so, great news! Am I all clear to update to that unlocked version then? Anyone got a link to the newest one? (Not any mods etc. just the standard update!).
Thanks all!
Click to expand...
Click to collapse
I believe that the most recent RUU is RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_225161_signed.exe
in the "Shipped Desire S ROM Collection" :
http://forum.xda-developers.com/showthread.php?t=1002506
I loaded this last night and not experienced any problems so far.
Be warned that this will wipe all existing data on your phone, so make sure that you have got everything saved. In some respects, this is a good thing because you are sure of getting a completely fresh install.
I can't see any reason why this shouldn't work for you, but I wouldn't feel bad if you got a second opinion
-Steve

fasty said:
I believe that the most recent RUU is RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_225161_signed.exe
in the "Shipped Desire S ROM Collection" :
http://forum.xda-developers.com/showthread.php?t=1002506
I loaded this last night and not experienced any problems so far.
Be warned that this will wipe all existing data on your phone, so make sure that you have got everything saved. In some respects, this is a good thing because you are sure of getting a completely fresh install.
I can't see any reason why this shouldn't work for you, but I wouldn't feel bad if you got a second opinion
-Steve
Click to expand...
Click to collapse
Okay thanks very much! I'll try updating it via that ROM tonight - hopefully I won't brick it!
Does anyone know if updating the phone using this method voids the warranty?
Also, how do I actually install that update to my phone? Seen a few tutorials scattared around but some are for different things and I don't want to mess it up! (Easiest/quickest method please, if there is one ha!)
Thanks a lot for your help Steve!

Biogeneric said:
Okay thanks very much! I'll try updating it via that ROM tonight - hopefully I won't brick it!
Does anyone know if updating the phone using this method voids the warranty?
Also, how do I actually install that update to my phone? Seen a few tutorials scattared around but some are for different things and I don't want to mess it up! (Easiest/quickest method please, if there is one ha!)
Thanks a lot for your help Steve!
Click to expand...
Click to collapse
I expect that doing almost anything other than the "official" OTA update theoretically voids warranty. But perhaps more important, if it all went horribly wrong, could anyone detect that you were fiddling with it
If you returned a phone rooted or S-off, then it's asking for trouble.
The discussed RUU is a signed update that does not invoke S-off or root the phone so should not create an "obvious" problem.
The way I updated my phone was as follows:
- I already had HTC Sync installed on my PC
- Fully charged phone
- Downloaded the RUU file to folder on hard disk
- Temporarily disabled my antivirus
- Temporarily disabled standby power saving option on PC
- Connected the phone as normal and selected the option on phone to do Sync
- I let the phone completely finish sync
- I ran the RUU on the PC and followed the simple instructions.
- It took about 10 minutes with no user intervention required.
I don't know if the whole HTC Sync thing is necessary, it was on my PC anyway and the procedure has worked OK for me.

I can now confirm this has all worked for me. no problems so far!
Thanks for all your help fasty! Very much appreciated.

Biogeneric said:
I can now confirm this has all worked for me. no problems so far!
D
Click to expand...
Click to collapse
Great news! Be sure to thank "Football" because he is the one that has done the hard work making these ROMs available.

Hi not sure if posting in correct thread but I am on O2 and also have the 1.28.401.1 software and just been informed by HTC my phone is unbranded despite coming straight from O2. Has anyone received the update whilst being on 1.28.401.1? Am i wasting my time holding out for an OTA update?

RUU
Sent from my HTC Desire S using xda premium

[Q] not another "when am i getting ics?" thread

just wondering how i will get the update.... as i understand it its up to the carriers to push the update. my phone is stock from virgin but i am unlocked to use rogers, who will push it to me?

I'm on rogers as well. If I were you, I'd just root it and install ICS or run the RUU. I say this because warranty with HTC is a pain especially since we can't send it through rogers for warranty. Warranty is pretty much pointless/a huge hassle! But I'm pretty sure you can just run the RUU when it's released, so manual instead of automatically. Maybe I'm wrong and if I am someone can correct me!

[Q] Has anyone with T-Mobile Germany managed to SUPERCID?

I have a S4 Phone branded to T-Mobile Germany (CID: T-MOB101).
I have take the Jellybean OTA update, and I'm trying to SUPERCID with the method here: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911 but without success.
So the question is:
Has anyone with T-Mobile Germany managed to SUPERCID? And with what bootloader-ROM?

yep - no problem. It was one of the early bootloaders, 1.06 or 1.09. as my device now is one year old.

rootrider said:
yep - no problem. It was one of the early bootloaders, 1.06 or 1.09. as my device now is one year old.
Click to expand...
Click to collapse
Unfortunately I have take the 3.16.111.7 OTA update with 2.15 bootloader. Every time I modify the mmcblk0p4 partition to take supercid, but after the rebooting the system recovers the original one. I supose HTC has lock something (at least for the branded phones).

I've read about your problem in one of the threads here.
You might possibly need a t-mobile DE simcard to change CID successfully according to your problem. We could try that. If you want, I could buy a prepaid one and send it to you this week. You can send it back to me afterwards.
If this won't help, you can send me your device and I'd try to s-off it with my simcard here.
Out of interest, could you tell me the first six digits of your device serial? Something like HT23FW... Settings ->Info -> Identity

rootrider said:
I've read about your problem in one of the threads here.
You might possibly need a t-mobile DE simcard to change CID successfully according to your problem. We could try that. If you want, I could buy a prepaid one and send it to you this week. You can send it back to me afterwards.
If this won't help, you can send me your device and I'd try to s-off it with my simcard here.
Out of interest, could you tell me the first six digits of your device serial? Something like HT23FW... Settings ->Info -> Identity
Click to expand...
Click to collapse
Thank you for your kindly offer. But I don't think has something to do with the sim. I think has to do with 2.15 bootloader and branded phones.
My serial is HT26BW...... The phone was came with 4.0.3. But unfortunately I didn't try to supercid early enouph.

taxtax said:
Thank you for your kindly offer. But I don't think has something to do with the sim. I think has to do with 2.15 bootloader and branded phones.
My serial is HT26BW...... The phone was came with 4.0.3. But unfortunately I didn't try to supercid early enouph.
Click to expand...
Click to collapse
So your phone was manufactured in Taiwan 2012/June/11.
This means it was basically sold with ICS. Bootloader version 2.15 came with the JB update in December last year. So this means that the preowner of that phone must have changed the device to SCID or any other CID that was able to receive the JB OTA and install it. T-Mobile DE never offered JB for it's devices so far.
To sell it he returned to the stock CID and possibly messed up the device serial. That might be a reason for your efforts don't work. So lets assume your'e on the wrong serial.
Now you should check the devices serial (IMEI) e.g. with Phone Explorer and in the Info -> Phone Identity and compare it to that one in mmcblk0p4. Else enter *#06# for checking IMEI.
--- edit
I read the OP again. How did you manage to get the JB OTA update with your CID T-MOB101?

rootrider said:
So your phone was manufactured in Taiwan 2012/June/11.
This means it was basically sold with ICS. Bootloader version 2.15 came with the JB update in December last year. So this means that the preowner of that phone must have changed the device to SCID or any other CID that was able to receive the JB OTA and install it. T-Mobile DE never offered JB for it's devices so far.
To sell it he returned to the stock CID and possibly messed up the device serial. That might be a reason for your efforts don't work. So lets assume your'e on the wrong serial.
Now you should check the devices serial (IMEI) e.g. with Phone Explorer and in the Info -> Phone Identity and compare it to that one in mmcblk0p4. Else enter *#06# for checking IMEI.
--- edit
I read the OP again. How did you manage to get the JB OTA update with your CID T-MOB101?
Click to expand...
Click to collapse
I bought the phone new in Christmas (S4 with T-MOB101 cid).
As I said it was with the 4.0.3 and the same day I taked the 4.0.4 OTA update.
At 1 February I taked the jellybean OTA update (version 3.16.111.5)
And at 28 February I taked a minor OTA update (version 3.16.111.7)
I have the OTA updates if you want them.

Thanks for your information. I am wondering about that you could get the JB OTA Update with that CID. You could still check if your IMEI is right, but I'm running out of ideas...

[Q] HTC One (M7_UL) Stock RUU Installation Issues

Hi,
As you've already imagined, I'm not any god-alike person in XDA. I don't know a lot about android developing. Yes, I am an amateur. (Although not a beginner) I'm just in a bit of trouble here and would love to have someone to help me.
Anyway, I've been using an HTC One [(M7_UL), (PN0710000)] for about 3 weeks now. And I've already tortured it a lot (not physically! ) I've unlocked the bootloader, installed CWM custom recovery, installed the 2.17.401.1 stock ROM posted by mike1986. (believe me, this guy is awesome!!)
Now I want to get back to COMPLETELY STOCK so that I can get OTA updates again and remove the "TAMPERED" mark from my device's bootlocker menu. So I relocked my bootloader, downloaded an RUU (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe) and tried to install it. The interesting part is, this RUU is for "x.xx.401.x" based devices only. But mine was a SIM-Unlocked Vodafone UK (x.xx.161.x) based device out of the box. So, As I imagined right from the beginning, I couldn't install this RUU. I got the "ERROR [131]: CUSTOMER ID ERROR". But I also noticed that the .401 and the .161 variants have many similarities. Such as they are both M7_UL devices and their model numbers are same too (PN0710000). Honestly, I don't like Vodafone (I don't know why I bought it from them) and right now, I want the PURE STOCK ROM, not any career-branded ROM. So, I though if it was possible for me to install a "x.xx.401.x" based RUU in my device. And if it is possible in any way (there SHOULD be a way, right?), how do I do it? Please help me. And if you need any other information in order to answer my question, I'm ready to answer.
Thanks a lot....