Hey People, I am in Uk, got myself at&t one x, was sick of at& t crapware, so got rooted, changed CID to supercid, then relocked and flashed asia firmware 1.88 using RUU in fastboot mode. now device works perfectly, I even have UK apn's, but it showed me system update of 2.23 when i tried to install it fails.
what i want to know is there a workaround this, whats happening?, is there anyone else crazy enough to try this!!:silly:
why dont you just flash one of the 2.23 roms we have out?
Related
Guys,
I have found a definite issue regarding trying to debrand and flash the 2.3.4 OTA update to my Bell debranded sensation...Here are my steps and results...
1. Performed Revolutionary on shipping Bell Canada Sensation
2. Changed CID to 11111111 via fastboot.
3. Flashed generic UK 1.35.401.1 software via RUU file.
4. Downloaded 2.3.4 OTA update.
5. Try to install the OTA update.zip from recovery, it errors out with Status 7 error. No matter what CID I use, I always get this error status 7.
6. Change CID to HTC__E11 to try and get the OTA update automatically, Downloads and then gives me a "variant system software" error when it goes to install. I've never heard of or seen this error before.
7. Run Revolutionary again and then flash the update.zip. It appears to successfully flash, but when the phone reboots, all I get is a black screen. the phone makes noises and appears to be functioning somewhat, but screen is black.
8. I am now thinking, great, I just bricked my phone...
9. Reboot into hboot. It still shows Bootloader of 1.17.0011, which is strange because the OTA is supposed to update it to 1.18.0000.
10. I then change the CID to 11111111 and reflash with the 1.35.401.1 RUU and thank god the phone is back to working condition.
It appears that there is either a hardware difference or something really low level that is being changed with this new update and it might not work properly with the different radio from the Bell Canada version with the 850/1900 radio, but I don't understand why flashing to the 1.35.401.1 RUU works fine. If anyone else can shed any light on this or give me any hints, I would appreciate. I thought my experiences might help the devs out there further understand the new OTA and the Sensation software/hardware. My end goal is to have the most up to date stock unbranded software installed on my Sensation. I am using with AT&T if anyone is wondering.
Y2J
y2jdmbfan said:
Guys,
I have found a definite issue regarding trying to debrand and flash the 2.3.4 OTA update to my Bell debranded sensation...Here are my steps and results...
1. Performed Revolutionary on shipping Bell Canada Sensation
2. Changed CID to 11111111 via fastboot.
3. Flashed generic UK 1.35.401.1 software via RUU file.
4. Downloaded 2.3.4 OTA update.
5. Try to install the OTA update.zip from recovery, it errors out with Status 7 error. No matter what CID I use, I always get this error status 7.
6. Change CID to HTC__E11 to try and get the OTA update automatically, Downloads and then gives me a "variant system software" error when it goes to install. I've never heard of or seen this error before.
7. Run Revolutionary again and then flash the update.zip. It appears to successfully flash, but when the phone reboots, all I get is a black screen. the phone makes noises and appears to be functioning somewhat, but screen is black.
8. I am now thinking, great, I just bricked my phone...
9. Reboot into hboot. It still shows Bootloader of 1.17.0011, which is strange because the OTA is supposed to update it to 1.18.0000.
10. I then change the CID to 11111111 and reflash with the 1.35.401.1 RUU and thank god the phone is back to working condition.
It appears that there is either a hardware difference or something really low level that is being changed with this new update and it might not work properly with the different radio from the Bell Canada version with the 850/1900 radio, but I don't understand why flashing to the 1.35.401.1 RUU works fine. If anyone else can shed any light on this or give me any hints, I would appreciate. I thought my experiences might help the devs out there further understand the new OTA and the Sensation software/hardware. My end goal is to have the most up to date stock unbranded software installed on my Sensation. I am using with AT&T if anyone is wondering.
Y2J
Click to expand...
Click to collapse
I would venture to guess you're not aware that you should probably not (at least not now), do an official FOTA/OTA on an unauthorized S-OFF Sensation.
The official HTC 2.3.4 OTA that came out a few days ago, LOCKS your device. It puts it back into an S-ON state.
Unless something has changed, if you have S-OFF via Revolutionary....stay far away from official HTC updates.
Something has changed...revolutionary now supports the new "locked" bootloader!
Hoggles said:
I would venture to guess you're not aware that you should probably not (at least not now), do an official FOTA/OTA on an unauthorized S-OFF Sensation.
The official HTC 2.3.4 OTA that came out a few days ago, LOCKS your device. It puts it back into an S-ON state.
Unless something has changed, if you have S-OFF via Revolutionary....stay far away from official HTC updates.
Click to expand...
Click to collapse
I'm well aware that the the official HTC 2.3.4 OTA locks the device. As long as I have a debranded Sensation running the latest and greatest firmware/software, that is all I am looking for. And now that Revolutionary works on the new HBOOT there shouldn't be much trouble getting back to the original shipping software. I still am curious as to what is causing this "Error Status 7" error code.
So how can I update my sensation with s-off?
A bug in me from being updated.
That would really interest me too! don't want to be S-ON again to make this update. Another question (maybe off topic): how can i update to new S-OFF version 04pre4? I'm now on 03pre7.
Hi
I have the exact same problem as yours, what can we do to update it?
Same on Swisscom-branded phone
I tried the OTA on my swisscom phone, it reboots and I get an exclamation mark with a blue droid. Waited 10 minutes just in case, but no change.
Removed battery and rebooted. Phone still ok, but not updated obviously.
I'm not sure it will remove S-OFF, but I don't care, HTC provides an official procedure for that and we have what we need.
But I need this update to work on my rooted, S-OFF stock sensation. Will try again anyway...
EDIT: I tried going into recovery and manually flashing the OTAxx.zip file, but it gave me an assert_failed: check_cid!? Though I never changed the phone CID! So why propose me an update on my phone if it's the wrong one??? Not sure I want to change the CID of my phone now.
hey guys, im gonna return my one s to tmobile in a few days and my phone was rooted and had the bootloader unlocked. so i locked up the bootloader again and ran the tmobile US ruu but for some reason my build number says 1.53.531.16_R2 CL47441 and someone said the STOCK ROM for original TMOUS is 1.53.531.16 CL47441. notice there is a R2 in my ruu and it doesnt have that on the stock tmobile rom which is weird. just wondering if that is gonna matter when i send it back to tmobile (customer service). it looks like the stock tmobile rom. it has all the bloatware and crap that comes with the phone stock. also i cant seem to get the ota update or even manually install it myself neither which is odd.
I have a desire s, s-on, hboot 2.00.0002, radio 3822.10.08.04_M. It was bought in UK.
I currently have the Vanilla ICE v2.0 rom installed, however there are some features that are really annoying me, and I would like to try the official HTC ics update.
I have been to htcdev and downloaded the ICS RUU (after selecting WWE as the region).
However, when I run it it bombs out, with error 155, and suggests I download the correct version.
From what I can see on here, I've been told that the WWE version should be correct version for UK, is this correct?
I did try downloading Endymion 3.5, and installing that onto my phone, however when I boot my phone, it keeps saying that the phone, messaging and pretty much everything has crashed! I tried running the RUU with that installed, and it got as far as trying to send the rom over, however it failed. Unfortunately, I cannot remember the exact error. It *may* have either been 155 or 175.
I have since read this thread -> http://forum.xda-developers.com/showthread.php?t=1655832 about re-locking the bootloader, however I have not yet managed to restore my phone to stock.
I am currently downloading a rom from here -> http://forum.xda-developers.com/showthread.php?p=31345345&highlight=link#post31345345 in the hopes it will work.
Does anyone know if you HAVE to have either a stock rom, or an older rom, in order to run the ruu?
I tried re-locking the bootloader, and running the
RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed
file I downloaded, however it got as far as updating the signature, and failed saying I need to get the right version.
Can someone PLEASE help.
How can I downgrade my phone to stock gingerbread, and why is the WWE ruu not working on my o2 (uk) branded phone?
check this out: http://forum.xda-developers.com/showthread.php?t=1318919&highlight=skanob
I need some major help, good folks of XDA. I've purchased this HTC One S from a guy who got it from Fido; naturally it was locked to Fido. I was planning on giving it to my girlfriend who is with Telus. I used cellunlocker.net to unlock the phone to find out that it didnt work with Telus. It would pick up signal then lose signal, pick up signal and lose signal every 10 seconds or so. I thought if I put a custom ROM on it might get me signal so I unlocked bootloader, rooted and put Viper ROM on it but it turns out it still wouldn't pick up network on Telus. So I decided to try it on my network, Rogers, and it picks up network but only 2G!!! Now my One S has the stable CM10 on it with baseband 1.08ts.50.02.16_10.08e.50.04L, unlocked bootloader with s-on, hboot 1.06, radio - 0.16.31501s.02
Here are the solutions I have tried so far to this problem;
-Tried to install multiple RUU both with ROGER001 CID and Super CID:11111111 and I couldn't install any of the RUUs, kept getting Error 155 with Rogers RUU and Check CID errors with other RUUs.
-Used to have 1.13 hboot but downgraded to 1.06 so I could change basebands and everytime I flash a different baseband, nothing changes after reboot.
-There is a recent jellybean rogers ota update zip but I dont know how to install it
please someone help!!! Thank you in advance and even more if my problem ever gets solved
Wrong forum for this kind of question. Have you tried flashing the telus radio? Also modifying the build.prop with the telus settings might help. Odd that you're having that issue on Rogers since Fido is the same network. Sounds like someone may have sold you a dud...
Sent from my HTC One S using xda premium
alltubetone said:
Wrong forum for this kind of question. Have you tried flashing the telus radio? Also modifying the build.prop with the telus settings might help. Odd that you're having that issue on Rogers since Fido is the same network. Sounds like someone may have sold you a dud...
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Just asking, why is this the wrong (forum) as you say cuz this forum handles all devices does it not and I don't see anything wrong with his post?
SuperCID lets you flash any RUU, that error is most likely down to the bootloader being unlocked so if you really want to run a RUU then you want SuperCID and the lock the bootloader then run the RUU and also before you start the RUU be in fastboot mode first.
Darknites said:
SuperCID lets you flash any RUU, that or is most likely down to the bootloader being unlocked so if you really want to run a RUU then you want SuperCID and the lock the bootloader then run the RUU and also before you start the RUU be in fastboot mode first.
Click to expand...
Click to collapse
I did fastboot oem lock before flashing and got the same results; rather frustrating
alltubetone said:
Wrong forum for this kind of question. Have you tried flashing the telus radio? Also modifying the build.prop with the telus settings might help. Odd that you're having that issue on Rogers since Fido is the same network. Sounds like someone may have sold you a dud...
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
is it possible for a dud phone to have only 2g working and not get 3g?
dpk0875 said:
I did fastboot oem lock before flashing and got the same results; rather frustrating
Click to expand...
Click to collapse
Try hex editing mmcblk0p23 .... There is a method here for flashing RUUs that is discussed in the development forum in the sticky for downgrading your bootloader.... Try the hex edit, and then lock and then flash.
You could also try flashing a different baseband radio. For Canada, I didnt get the best reception from 1.08. You can d/l new baseband radios either for your phones radio partition or for CM10 (which uses a different location). There is a thread with radios collected in them in the development section.
I would try flashing a different radio before the RUU... The RUUs will upgrade your bootloader and then you cant flash new radios and other partition on SENSE seperately (ie ROMS wont flash properly and you will need to fastboot the boot.img every time)...
Funny , I unlocked my Original Fido One S to use it on Wind and it works perefectly. It should work on Telus ...have you tried inputting telus apn and restarting the phone after?
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
tlazarus said:
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s :
- you don't need to root your phone to add apn . I can add T-Mobile apn just fine after I flashed ruu.
- ruu.exe can't run if you bootloader is unlocked.
Sent from my HTC One X using XDA Premium HD app
tritran18518 said:
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s : you don't need to root your phone to add apn .
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Thanks - that answers my RUU questions as far as going back to stock using RUUs. I assume the same applies to other carrier's RUUs, i.e. Telus/Asia. What about using an OTA on a phone with Super-CID?
redpoint73 said:
A factory reset or running the RUU will not change the CID.
SuperCID doesn't prevent you from getting the AT&T OTA (although root and unlocked bootloader will).
Click to expand...
Click to collapse
^^
jiggamanjb said:
^^
Click to expand...
Click to collapse
Okay, I think that answers my questions. No problems with using a RUU, AT&T or otherwise, as long as it is for the XL. Stuck on my current radio unless I use a RUU. And I need to relock my bootloader before applying a RUU, although I can unlock it after. I will lose root, however. Thanks!