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.
Related
Yesterday I sold my Hero and picked up an Evo. I got a call from the guy I sold it to today saying he couldn't activate it because I have it rooted with CM6. Do I just install one of the stock RUU to get it to work for him? Will doing that unroot the phone? I need to figure out how to get it to activate on Sprint for him.
Yes, this goes in Q&A but with CM6 the phone codes do not work and will be needed for activation, just run the stock RUU.
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?
The ear piece speaker on my One S broke, and I'm sending it into repair. I bought my phone unbranded from Phones 4U. Currently, I have this latest RUU loaded up:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
I believe this RUU is from Three, because it added a load of Three bookmarks to my browser.
In HBOOT, it does say "Relocked", but it doesn't say "Tampered", which I gather is the best you can get after rooting.
Considering the phone should be unbranded, should I try loading the most recent stock HTC RUU? I'm just worried they're going to point that out and refuse to repair :/
id like to know this too as i have an unbranded uk one s and im using the same RUU
jimnastics said:
The ear piece speaker on my One S broke, and I'm sending it into repair. I bought my phone unbranded from Phones 4U. Currently, I have this latest RUU loaded up:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
I believe this RUU is from Three, because it added a load of Three bookmarks to my browser.
In HBOOT, it does say "Relocked", but it doesn't say "Tampered", which I gather is the best you can get after rooting.
Considering the phone should be unbranded, should I try loading the most recent stock HTC RUU? I'm just worried they're going to point that out and refuse to repair :/
Click to expand...
Click to collapse
I don't think you need to load a new RUU. Your problem is a hardware related so they shouldn't bother about the OS on the phone as it's not related to the problem and the OS is an official HTC one anyway..
When I swapped my HOS there was an unofficial ROM (plus I installed my own and the CID was an Orange one). An O2 guru sent it to a repair centre and they accepted the phone even with the development notice at startup..
Your phone is ok by software but not ok by hardware. I see no reason why to refuse it..
It don't matter, I have sent one of my phones back rooted and unlocked before 2 times for hardware problems,..
when I was on sprint rooted, unlocked, they run the RUU to make sure its not software related, then they repair what needs to be repaired.
I called them back to say why did you upgrade my hboot, they said "they put it back to manufactor default stock rom, sprint, tmobile, att, they run the RUU first on any phone.
I would run an RUU they will charge you if its unlocked as it breaks their warranty. MAKE SURE ITS LOCKED AND STOCK in uk.
Any EU RUU should do the trick ! If it was originally carrier branded and you cannot find RUU for that carrier, Just change CID to HTC__001 and run an unbranded EU RUU.
Relocking the bootloader is a must! It takes 10 seconds so dont take no risks !
I bought a One S for my Mom on eBay to replace her water-damaged S2 - the listing said factory sealed, unlocked, brand new.
Dropped Bell Canada SIM card in, worked well for 2 months.
After a Bell OTA update, phone will not maintain a signal.
Bell looked up IMEI, said the phone belonged to Fido and was unlocked and activated by Rogers.
Ran Root Checker to see if it was rooted - sure enough, it had been rooted and I have the "this device does not have proper root access".
So I've been forced to try and figure this out, and I'd like to restore the phone to stock - I've read cbetso's great "Restore to Stock" post and looked through the AIO toolkit, but I don't know which "RUU to run". Fido? Rogers? Bell? Do I even need it? Everyone's issue seems very personal and specific to their carrier / etc. and I'd like to restore it.
Thanks.
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.84.631.9
HTC SDK API level: 4.11
HTC Extension version: HTCExtension_403_1_GA_4
Build number: 1.84.631.9 CL64348 release-keys
Telling by the software version it runs the Fido software. You would have to run a Fido RUU, but if you want to change it to unbranded HTC software you can change CID to HTC__001 and then run an unbranded RUU such as 2.31.401.5 (latest, Android 4.0.4 RUU)
usaff22 said:
Telling by the software version it runs the Fido software. You would have to run a Fido RUU, but if you want to change it to unbranded HTC software you can change CID to HTC__001 and then run an unbranded RUU such as 2.31.401.5 (latest, Android 4.0.4 RUU)
Click to expand...
Click to collapse
Thanks again. I have an unlock code for the device; my hope was to restore it back to the way it came from Fido and SIM unlock it for use with another carrier. I suppose I'll try the step-by-step process listed in the "restore" post I mentioned. After trying to figure this out for the past week, I truly appreciate the work of developers here in the forum.
So I've located an RUU for Rogers (which covers Fido in Canada, apparently) but it's for a 1.70 build. The one currently on the device, I believe is higher than that. I'd like to try the All in One Toolkit to bring the phone back to stock and then unlock it for use with Bell or Telus. If I run the Toolkit, and use cbetso's instructions from the "How to Return to Stock" post (after adding the stock recovery to the folder) - can I run the 1.70 Rogers RUU without issues? Thanks for the advice!
tykidd66 said:
So I've located an RUU for Rogers (which covers Fido in Canada, apparently) but it's for a 1.70 build. The one currently on the device, I believe is higher than that. I'd like to try the All in One Toolkit to bring the phone back to stock and then unlock it for use with Bell or Telus. If I run the Toolkit, and use cbetso's instructions from the "How to Return to Stock" post (after adding the stock recovery to the folder) - can I run the 1.70 Rogers RUU without issues? Thanks for the advice!
Click to expand...
Click to collapse
If you are on a higher software version than the RUU, unfortunately it's not possible unless you downgrade your HBOOT which is risky for people who are new to the whole unlock/root thing. If the software version is the same or less, go ahead.
usaff22 said:
If you are on a higher software version than the RUU, unfortunately it's not possible unless you downgrade your HBOOT which is risky for people who are new to the whole unlock/root thing. If the software version is the same or less, go ahead.
Click to expand...
Click to collapse
Thanks. I'm not new, I'm COMPLETELY new. Maybe I'll have to wait until the higher version come out for Rogers. Right now I have a virtually unusable phone, and although I don't know what I'm doing, I'd still like to try and get it back to stock. Can you point me in the direction of a good downgrade tutorial? I've looked around a bit but haven't seen anything I trust. Much appreciated.
Wondering, how I get back to stock for my girlfriends One Mini from T-Mobile Germany. The battery has quite strange problems and we want to give it to T-Mobile for service.
I think it won't be good, when the phone is with an International CID even if she bought it from T-Mobile with a T-Mobile CID, right? Flashing stock international would be no problem with S-Off (Just change CID and flash a stock international rom).
The main question is, can I change the CID to an international one, flash a stock rom, change CID back to T-Mobile one, make phone S-On and locked, flash stock recovery and update thorugh OTA? Will the phone get the T-Mobile OTA from then on?
Or do you think I should change the CID to an international one, flash stock, make it locked and s-on and give it to t-mobile?
Many questions but I hope I can get even one answer
Cheers,
Patrick
Klivarre said:
Wondering, how I get back to stock for my girlfriends One Mini from T-Mobile Germany. The battery has quite strange problems and we want to give it to T-Mobile for service.
I think it won't be good, when the phone is with an International CID even if she bought it from T-Mobile with a T-Mobile CID, right? Flashing stock international would be no problem with S-Off (Just change CID and flash a stock international rom).
The main question is, can I change the CID to an international one, flash a stock rom, change CID back to T-Mobile one, make phone S-On and locked, flash stock recovery and update thorugh OTA? Will the phone get the T-Mobile OTA from then on?
Or do you think I should change the CID to an international one, flash stock, make it locked and s-on and give it to t-mobile?
Many questions but I hope I can get even one answer
Cheers,
Patrick
Click to expand...
Click to collapse
Hi Patrick
I honestly don´t think you get an OTA update from T-mobile if you only change your cid.
For getting OTA´s the firmware and build number must match and also have to be T-mobile.
Even if you get an OTA it will fail through installation if both don´t match.
(Doesn´t matter T-mobile or not)
greet´s