Related
I have a defective HTC Desire and need to unroot to send in for repair. There is still no RUU for the BravoC (CDMA) with US Cellular. Is there a way to unroot it? It says that the S-ON tool in the unrevoked wiki does not work with the CDMA Desire, but is coming soon. Can anyone please help!
Were you able to find a solution?
No luck yet. I tried the unrevoked irc channel but no one was there. Is there anyone out there that might be able to help? I would love to get this thing fixed. I would gladly paypal someone a couple bucks for some beer if they can get me un-rooted!
Flash to alltell ruu and you are unrooted. Only problem is your boot screen will have alltell. No big deal though...most don't notice
Sent from my Desire CDMA using Tapatalk
The Altell RUU has a newer radio than the USCC radio. Is this an issue for when I send it back for repair?
You guys are refering to these CDMA RUU's right?
original XDA:
http://forum.xda-developers.com/showthread.php?t=695667
CDMA
RUU_Desire_C_Verizon_WWE_1.12.605.1_R_release_sign ed_with_driver.exe
RUU_Desire_C_Verizon_WWE_1.17.605.1_release_signed _with_driver.exe
RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe
which one?
Izeltokatl said:
You guys are refering to these CDMA RUU's right?
original XDA:
http://forum.xda-developers.com/showthread.php?t=695667
CDMA
RUU_Desire_C_Verizon_WWE_1.12.605.1_R_release_sign ed_with_driver.exe
RUU_Desire_C_Verizon_WWE_1.17.605.1_release_signed _with_driver.exe
RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe
Click to expand...
Click to collapse
How do u know which one 2 choose and why do they say Verizon?
I was able to apply the recently released USCC foryo update downlaoed from teh HTC support website and used the instructions here: http://forum.xda-developers.com/showthread.php?t=880268
I needed to use the PB99IMG.zip method since I had issues with running the .exe under Windows for some reason. My only issue is that I am stil set to S-OFF and I need to send a phone in for repair. Do I need to be S-ON to not get charged for the full price of the phone and how can I get there? Thanks!
msternig said:
I was able to apply the recently released USCC foryo update downlaoed from teh HTC support website and used the instructions here: http://forum.xda-developers.com/showthread.php?t=880268
I needed to use the PB99IMG.zip method since I had issues with running the .exe under Windows for some reason. My only issue is that I am stil set to S-OFF and I need to send a phone in for repair. Do I need to be S-ON to not get charged for the full price of the phone and how can I get there? Thanks!
Click to expand...
Click to collapse
I just sent my phone in to US Cellular with it still being set to S-OFF. I did unroot by applying the RUU froyo download. When I called service they did not ever ask me about rooting / s-off but did ask me about other things that would void the warranty. It makes me feel like they will accept the return as is. I will keep you posted once they officially take my returned phone.
I need the US cellular RUU but i cant download it from the website, it takes me back to the support page when i click on download... any1 got the file? n can dropbox it or something??
TIA
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
OKAY, so I was shipped 2 models, wasn't sure why, anyways Rogers wanted me to ship one of them back, I did so. All is well for about 2 weeks, now I've been trying to root it, and I managed to get to the bootloader and some other things, but while I went into recovery it just said 'This build is for developement purposes only Do not distribute outside of HTC without HTC's written permission. Failure to comply may result in legal action' and it wouldn't start up into the recovery to get to superuser or whatever. It just had a logo with that on it... Is this my cells problem or could it be a problem with the recovery? Thank you in advance! Also I know this is for AT&T but there is no where else to ask for help :?
Call Rogers and tell me about it if you are having issues. tell them what is says and im sure they will send you a new phone. And this forum is for both, Att and Rogers.
ibCONNOR said:
OKAY, so I was shipped 2 models, wasn't sure why, anyways Rogers wanted me to ship one of them back, I did so. All is well for about 2 weeks, now I've been trying to root it, and I managed to get to the bootloader and some other things, but while I went into recovery it just said 'This build is for developement purposes only Do not distribute outside of HTC without HTC's written permission. Failure to comply may result in legal action' and it wouldn't start up into the recovery to get to superuser or whatever. It just had a logo with that on it... Is this my cells problem or could it be a problem with the recovery? Thank you in advance! Also I know this is for AT&T but there is no where else to ask for help :?
Click to expand...
Click to collapse
If you haven't installed a custom recovery image, definitely call Rogers. If you *HAVE* installed a custom recovery image, this is normal, and do NOT call Rogers, as they obviously won't support modded software.
Also, this forum is indeed for the Rogers One X as well, so you're posting in the right place. It kinda upset me when they changed the forum title from One XL to AT&T One X. Occasionally people give me flak for posting about my device, being all "yo bro, we're talking about the AT&T model if you haven't noticed."
It's the exact same hardware, save for the branding. The software is only slightly different. I imagine once we get some Rogers updates and a greater ability to flash custom ROM's and kernels, most of the ROM's will be based on Rogers, since AT&T has blocked some things like toggling LTE and stock tethering.
How much does CID exactly matter on updates?
I'm on HTC One S S4 HTC_017.
The device should receive updates like an unbranded device would.
Not really sure what it has to do with much, but I must have a rare device or something because I have yet to receive the 4.0.4 update. :/
Answer any of them, you don't have to know all of them.
Can anyone help me with these following questions,
1) Does anyone have this CID?
2) Is there a reason why I'm not receiving the update? (Don't tell me to check the about>software updates>check now, i do that all the time and i've already tried *#*#checkin#*#*)
3) Will I even receive Jelly Bean when it comes out? (I NEED Google Now, and there's no way I'm rooting my device.)
I have the carrier i wireless.
Produced for BrightStar Inc.
I have a Telus evita phone on 4.1.1. I was wondering if I could flash the German O2 or T-Mobile OTA to receive 4.2.2. My phone is SuperCID and S-OFF. Phone is currently stock because I ran a RUU then updated to 4.1.1. Will I lose my data if I flash the OTA?
Thanks
dx99 said:
I have a Telus evita phone on 4.1.1. I was wondering if I could flash the German O2 or T-Mobile OTA to receive 4.2.2. My phone is SuperCID and S-OFF. Phone is currently stock because I ran a RUU then updated to 4.1.1. Will I lose my data if I flash the OTA?
Thanks
Click to expand...
Click to collapse
I would just flash TWRP back onto the phone, then flash Turge's stock T-Mobile Sense 5 ROM posted in Development. Install the 2.15 firmware if you experience signal drops or random reboots.
My typical recommendation is to stay away from official OTAs if you are modded.
I just don't want to flash anything on my phone that's not official. That's why I'm asking, I want to keep my phone stock and just get an official update not a rom from another source.
Your phone is already far from stock, with SuperCID and S-off. You're already down the rabbit hole. And putting an OTA for another version is also not going to be "stock" or "official" for your phone.
The stock ROM is just from the OTA dump, completely unmodified (not even rooted, in fact). Its what is on my phone, and is running great.
Running the OTA might be risky. OTA does not necessarily have all the components. For instance, the T-Mobile 5.05 OTA does not have all the hboot modules. It assumes you are coming for the most recent T-Mobile RUU or OTA. So depending on what is currently on your phone, you can brick.
In theory, I think what you are proposing will work if you RUU to the most recent T-Mobile Germany RUU, than T-Mobile Germany Sense 5 OTA.
But again, you're making it more complicated than need be. What is exactly the issue with "unofficial" ROMs? If you don't trust the devs here, you would not have done SuperCID and s-off to begin with.
It's not that I don't trust the devs I just want to use official carrier updates. I know my phone isn't stock what I meant is using stock/original files from carriers. So even though my phone is from Telus and I used a RUU from them to get back to stock firmware I can flash a T-Mobile RUU over top of it then use their OTA afterwards?
dx99 said:
So even though my phone is from Telus and I used a RUU from them to get back to stock firmware I can flash a T-Mobile RUU over top of it then use their OTA afterwards?
Click to expand...
Click to collapse
Yes, the only thing stopping the RUU from running would be the carrier ID check and hboot version check (might be some other checks). But since you have s-off, all security checks are bypassed by definition.
Alright, would there be any issues with the fact that I'm on 4.1.1 and going backwards in firmware first? Since most RUU are 4.0.
dx99 said:
Alright, would there be any issues with the fact that I'm on 4.1.1 and going backwards in firmware first? Since most RUU are 4.0.
Click to expand...
Click to collapse
Now that you mention it, it looks like you would have to run the most recent RUU from T-Mobile Germany (3.17.111.1) then run two OTAs (3.17.111.2, and then finally 5.08.111.2). Run them out of sequence, and you risk a brick.
RUUs can be installed out of sequence, but there isn't one for 5.08.
I retract my former idea to RUU then OTA. I can't personally recommend such action upon further consideration. Its more complicated than I originally thought. I go back to my former statement, in that you are making this much more complicated than it should be. You are actually creating a higher risk of bricking your phone due to some imagined fear of "unofficial software".
redpoint73 said:
Now that you mention it, it looks like you would have to run the most recent RUU from T-Mobile Germany (3.17.111.1) then run two OTAs (3.17.111.2, and then finally 5.08.111.2). Run them out of sequence, and you risk a brick.
RUUs can be installed out of sequence, but there isn't one for 5.08.
I retract my former idea to RUU then OTA. I can't personally recommend such action upon further consideration. Its more complicated than I originally thought. I go back to my former statement, in that you are making this much more complicated than it should be. You are actually creating a higher risk of bricking your phone due to some imagined fear of "unofficial software".
Click to expand...
Click to collapse
So then its not possible to use the T-Mobile RUU and OTA on my Telus phone?
dx99 said:
So then its not possible to use the T-Mobile RUU and OTA on my Telus phone?
Click to expand...
Click to collapse
I think its possible, but its needlessly complicated and possibly risky. If you do it wrong, you might brick.
I don't personally recommend it, and its my personal opinion that you don't have a particularly valid reason for going that route when simpler methods exist. So if you proceed, its at your own judgement and you take all responsibility if something goes wrong.
If it does manage to work so you think there might be compatability issues with the play store or region specific things?