Related
I've made S-off with Revolutionary method to upgrade my Radio, after I've made the upgrade I'm still having issues with my signal, so I'm thinking to send the phone in warranty, but I can't manage to do the S-off.
Do you have any solutions?
Alternate way to restore your phone to S-ON and stock
Hi,
I've spent the last few days digging through the internet, looking for ways to get my Desire S back to S-ON after AlphaReveX S-OFF. The reason? I need to send it in for repair due to a birth defect.
I thought I'd share the path which turned out to be successful. Remember that there's always a risk that your phone will end up bricked as a result of procedures like this. I take no resonsibility for bricked devices, this is just a statment saying what worked for me. Good luck.
My initial setup was AlphaReveX S-OFF with Clockworkmod Recovery and LBC Mod. As the ARX HBOOT can't be overwritten by the HTC update program, it has to be replaced by a HBOOT that can. Luckily I found this thread in which Igl0 provides a pretty much tailor made HBOOT for this purpose:
http://forum.xda-developers.com/showpost.php?p=15493125&postcount=1.
The only problem: It couldn't be flashed in the bootloader (it would just return the message "parsed .."). After this I tried flashing through ADB, but for some reason it didn't work either. My third attempt was more fruitful - I successfully flashed engHBOOToverARX.img through fastboot (HTC drivers required which you probably already have).
Just to keep things simple I've made a zip which contains the files needed (except HTC drivers) to perform this flash. This guide assumes that you have already tried other methods and are familiar with related terms.
1. Connect phone to PC and navigate to fastboot
2. Download and extract the compressed folder attached to this post
3. I've composed a simple .bat (called "Click This") that will open a cmd prompt
and execute the command: fastboot flash hboot engHBOOToverARX.img.
4. Restart and enter HBOOT.
Click to expand...
Click to collapse
If the file was transferred and flashed correctly, the header text in HBOOT should now read "ENG HBOOT ...".
Now you can go ahead and flash a HTC stock RUU. It will overwrite other customisations such as a custom recovery. The HTC Update failed on my first attempt (file: RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release), but luckily I found another RUU that worked (RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed). You can browse this great collection to find one that suits you: http://forum.xda-developers.com/showthread.php?t=1002506.
As my first RUU installation failed partially, I was left with only the stock HBOOT and a non working recovery. Though, I found out that I could perform the next HTC Update attempt while in fastboot, and it was successful this time.
Cheers
Maarten
Thank you very much for the answer, I'll try this way. but before this can you tell me please if this will be a problem the fact that now I have a stock branded Orange ROM? When I did the S-off I didn't changed the ROM, I only changed my radio.
Thanks !!!
More questions....I'm afraid
sebysebu said:
Thank you very much for the answer, I'll try this way. but before this can you tell me please if this will be a problem the fact that now I have a stock branded Orange ROM? When I did the S-off I didn't changed the ROM, I only changed my radio.
Thanks !!!
Click to expand...
Click to collapse
You need to provide more information and details like Settings->About Phone-> Software info Radio (Baseband),Build Number,Kernel etc
If you know what radio version you had on your phone when you got it and what you have now that would be useful.
As I believe what you're saying is that you still have the same ROM version (ORANGE) as your phone came with, but you've simply changed radio and S-OFF'd!?
Do you have a custom recovery installed ie CWM (clock work mod)?
Having a branded ROM shouldn't effect your signal reception...
sebysebu said:
Thank you very much for the answer, I'll try this way. but before this can you tell me please if this will be a problem the fact that now I have a stock branded Orange ROM? When I did the S-off I didn't changed the ROM, I only changed my radio.
Thanks !!!
Click to expand...
Click to collapse
Okay. I'm afraid I don't have the competence to answer that!
ben_pyett said:
You need to provide more information and details like Settings->About Phone-> Software info Radio (Baseband),Build Number,Kernel etc
If you know what radio version you had on your phone when you got it and what you have now that would be useful.
As I believe what you're saying is that you still have the same ROM version (ORANGE) as your phone came with, but you've simply changed radio and S-OFF'd!?
Do you have a custom recovery installed ie CWM (clock work mod)?
Having a branded ROM shouldn't effect your signal reception...
Click to expand...
Click to collapse
Now I have: Radio : 3805.06.02.03_M
Build number : 1.47.401.4
Kernel : 2.6.35.10
Before I don't know what radio I had.
Yes, I have the same ROM version (ORANGE) that camed with the phone, and I'd simply changed the radio after S-off by Revolutionary
I don't have any custom recovery installed.
Regards,
Thanks!!!
Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster
sunster00 said:
Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster
Click to expand...
Click to collapse
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout
jags_the1 said:
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout
Click to expand...
Click to collapse
Hi mate thanks for offering advice and help. I have not had to use your method as I decided to give the HTC bootloader unlock code one final try before proceeding to your rescue plan and all of a sudden it was successful again. I got into recovery and did a nandroid restore so am back online again, but have nevertheless made note of your method in case I become stuck again in the future. Thanks anyway for your reply! :good:
OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.
beppomarx said:
OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.
Click to expand...
Click to collapse
First, what phone do you have? We will need the first five lines of your bootloader to help you later.
If all you need right now is to try and recover the files and you are on windows, here is a freeware file recovery program I've used in the past. You will need to be able to mount your sd card in TWRP.
http://www.softpedia.com/get/System/Back-Up-and-Recovery/Recuva.shtml
Once you get that done, you do have some problems to work through (Android Revolution Rom is not for our phone.)
beppomarx said:
OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.
Click to expand...
Click to collapse
Ok, first, you're all over the place. Why did you install a radio+RIL when it explicitly tells you not to? It's actions like this that get people like you into a lot of trouble and destroys phones.
Secondly, there is no Android Revolution HD for this device. I believe you have the HTC One XL / at&t One X (Evita) judging from your post, but like I said there's no ARHD ROM for the Evita, only for the HTC One X (Endeavoru). This leads me to believe that you're jumping between the two device forums, very bad idea, none of the stuff from the Endeavoru forum is compatible with our phone.
You're lucky the ROM install stopped otherwise you would have bricked your phone. Long story short, you have no OS because the ROM install didn't complete, you have a corrupt boot partition because you flashed the ARHD boot.img which isn't compatible. In future do not stray outside our device forum for any reason at all. Here's our forum main page, bookmark it:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Next. Performing a factory reset in TWRP recovery does not wipe user data (images/music etc). I'm not sure what you've done but the factory reset in recovery wasn't it. A factory reset performed in the bootloader does however corrupt the sd card, so never do a factory reset from the bootloader.
You might have a chance at saving some of your data using a data recovery tool in Windows. You'll need to mount usb storage in TWRP for Windows to access the sd. Do not under any circumstances do any writing to the sd card before you attempt to save your data.
In conclusion, you've made numerous mistakes with your device. You need to slow down a bit and educate yourself a bit better, a lack of knowledge when it comes to modifying devices is a very dangerous thing.
Please post the first five lines of your bootloader.
Sent from my Evita.
i could have sworn i got the android revolution rom from the att one x forum but i suppose not....
ok guys thanks so much so far i will pick up again after work today.
bootloader says:
TAMPERED
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT-1.09.000
RADIO-0.19as.32.09.11_2
OpenDSP-v34.1.0.45.1219
eMMC-boot
Apr 2 2012,21:08:24
I'm 99.9% i was s-off before this all...
There isn't and never has been an Android Revolution ROM in this forum. It's kinda easy to make the mistake, the forums are named similarly.
I'm 99.9% sure you weren't s-off before all this. A phone can't change the security status without you doing it manually. It just can't happen. Did you actually go through either the Facepalm or Rumrunner s-off processes?
Well, you definitely have the Evita (HTC One XL / at&t One X) so make sure you stay within the forum I linked to earlier.
Good luck with attempting to recover your data, I hope you get at least some of it back.
Sent from my Evita.
Ok so as far as mounting my sd card in twrp, there's something up with my screen touch input I think... I am not able to click that particular box in the 'mount' menu. It seems like that part of the screen was not clickable when installing roms and such but once I get into android everything works perfectly.
Is there a way to rotate the screen in twrp?
Also by looking at my bootloader info once I get my sd card mounted and recovered best as I can, what is my best plan of action? Re-lock and flash a stock att ruu and begin from scratch or what? Or just try and load a correct radio and rom? I'm not a complete newbie I know I made a foolish mistake but I have done this quite a few times playing on the inspire, cha-cha, my kids nabi 2 tablets and on this att one x. This is the first time I have gotten really stuck in probably 35 flashes. Just this time I might be over my head...
To be honest I've never tried rotating the screen while in recovery, so I'm not sure about that. Exactly which recovery type (CWM/TWRP) and version number are you using?
I think your best plan of action would be to run an RUU, this will bring everything back to the way it should be. You're lucky in the sense that you're still on quite an early firmware version, so you should have a couple of RUU options. One thing to be careful of though, absolutely do not run a jb RUU if you have SuperCID, it will brick your device. SuperCID + s-on + jb RUU = brick. We should check your CID just in case, connect your phone in fastboot mode and issue this command:
Code:
fastboot oem readcid
Sent from my Evita.
beppomarx said:
i could have sworn i got the android revolution rom from the att one x forum but i suppose not....
Click to expand...
Click to collapse
There is absolutely no ARHD ROM for EVITA. You've made a grave error, and as timmaaa mentioned, you are lucky your phone isn't a paperweight now.
EVDEAVORU is partitioned completely differently from EVITA, so all bets are pretty much off on whether your data is still intact or not. The ROM itself may have overwritten your data. Also, if you happened to do a factory reset in hboot instead of TWRP (as you mentioned) this will corrupt the SD card on modded EVITAs (known issue, and somewhat common error).
Your best bet is to get the phone back up and running using timmaaa instructions. Then see if the files are still on the SD. If the data files aren't easily visible, you can also try data recovery programs to see if they can be salvaged (sometimes corrupted files get dumped to a temp folder, or otherwise recoverable).
But I wouldn't hold my breath on recovering the files. This is what always puzzles me (why folks never back their data, then freak out when its gone of damaged). If your data is important to you, its important enough to back up. And there are so many easy methods to do so (with built-in cloud backup apps and whatnot) yet so many folks neglect to do that. And all you are left with is regret when things do south. Its pretty much a no-brainer to backup anything important to you when modding the phone. I'm puzzling why so many folks never do it.
So since I have the 1.09.000 hboot i am going to download and install this:
1.85.502.3
File Timestamp: 25/05/12
Publically Seen: 06/06/12
Android: 4.0.3
Kernel: 3.0.8-01155-gca24d1e
hboot: 1.09.0000
radio: 0.17.32.09.12_10.86.32.08
adsp: 28.1.0.32.0504
wcnss: 1031120A
tp_syn3202: 3.0_PR1100755
tz: 001.031.511
sbl1: 001.031.503
sbl2: 001.031.501
sbl3: 001.031.502
OTA: OTA_Evita_UL_Cingular_US_1.85.502.3_R2_NEW_NFCPHON ESTORAGE-1.73.502.1_release_263287jkmeqj8u75z409z9.zip
RUU: RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17. 32.09.12_10.86.32.08L_release_262092_signed.exe (Download)
Source: evita-ics-crc-3.0.8-271616b.zip
is this my best bet? I am going to try and check my CID status right now just need to download the android SDK and get that going...
**EDIT**
my CID is 11111111. is that superCID?
**EDIT**
looking for a way to remove superCID. If i just go S-off am i OK to run a RUU or should I keep looking to change my CID back?
**EDIT**
just downloaded WinDrid HTC One XL Toolkit and seems to be up and running fine. my plan so far is to S-off and run the RUU I posted above but I will wait for someone to chime in before I do anything else.. I feel like I am on the edge here and don't want to brick it... I can't find any way so far to return my CID but from what I read if I am S-off it should keep me safe.
S-off won't work unless you're able to boot into a ROM. I'd forget about using a toolkit for now, it completely bypasses some much needed learning, and doesn't always work anyway. I believe all you need to do is relock your bootloader and then run the RUU.
Sent from my Evita.
Ok I will look into how to re-lock that after work today. Can anyone else confirm this? Not that I don't trust you but wording it like 'I believe this will work' makes me ask again...
I'm 99.99% sure it's only the jb and above RUU that you need to worry about while s-on and SuperCID.
Sent from my Evita.
timmaaa said:
I'm 99.99% sure it's only the jb and above RUU that you need to worry about while s-on and SuperCID.
Click to expand...
Click to collapse
ICS RUUs are free of the S-on and SuperCID bug. Plenty of folks have flashed that RUU (such as 2.20) with SuperCID with no issue.
so I am going to relock the bootloader, it's as simple as 'fastboot oem lock'? that's it? before doing so should i bother s-off first? here's my plan of action:
s-off
relock bootloader
run 2.20.502.7 ruu
unlock bootloader again
install twrp
load custom rom
that should work correct?
If you s-off first, I believe you do not need to relock the bootloader to run the RUU. Just s-off, then run the RUU.
As I've previously mentioned, you won't be able to get s-off unless your phone will boot a ROM. The above process looks right.
Sent from my Evita.
got back to stock just fine, now to work my way back to modded. You guys are the best thank you a million.
Please hit the thanks button on any post that you've found helpful on XDA.
Sent from my Evita.
Remember also to either s-off or change cid back to normal, it will assist in the future if you get in a jam like this.
Although s-off and flashing a rom for a different phone(like you did) may have ended up much worse as some of the checks that likely saved you will be disabled.
At very least do not OTA/RUU update to Jellybean while you are s-on and supercid!
Background:
I recently bought an HTC One S for testing purposes & received it with the following specifications.
HTC ONE S[4] unlocked, s-off with cid -1111111 / stock tmobile / jelly bean
Unfortunately, it came with with the infamous wifi / bluetooth error.
At first I thought it was an hardware issue but after opening it up and examining it, I came to the conclusion that its software based and probably caused by a bad flash.
---
It took me about 2-3 days to fix this issue which included flashing ruu's, firmwares, hboots, recoveries, radios & infinite s-on / s-off / locked / unlocked / cid variations.
What is the Wifi + Bluetooth error?
When you try to turn on Wifi or Bluetooth from the settings, it just states that its turning on but then that quickly turns into "error".
Basically, your Wifi and/or Bluetooth are messed up and non-functional due to a bad flash.
The Fix
--- Step 1 ---
You need an all in one utility for the HTC One S - I used the following one,
[TOOL] HTC One S All-In-One Toolkit v4.0
You can download it by clicking [Link removed, I didn't know it wasn't allowed on XDA - Sorry, you will just have to do the steps manually via fastboot / cmd or find a kit on your own] It's pretty easy to do manually, just look for a fast boot tutorial, there are more than a few floating around.
--- Step 2 ---
I received the phone with supercid 111111 which I changed to stock T-MOB010 using the all in one tool and then flashed the proper carrier RUU for my cid (RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02 _10.18.31501S.08L_release_262073_signed.exe)
You will now need to flash the very first RUU available for your specific One S model / 1.53 is ideal, if you don't have access to that then maybe 1.78 might do the trick.
- Preparation -
(Important) You need: Locked bootloader, stock cid and the very first RUU.exe that was released for your device - In my 7 tests so far, the 1.53 ruu has always worked eventually. (read the 3rd post for an example on this)
Boot up into the bootloader by holding power + volume down.
You can lock the bootloader, change back to stock cid from the All in One tool while booted up in fastboot.
CID LIST + Help: http://forum.xda-developers.com/showthread.php?t=2139447
RUU's: http://forum.xda-developers.com/showthread.php?t=2200930
--- Step 3 ---
(Locked & Stock Cid)
Boot into fastboot, run the 1.53 (1.78?) RUU.exe
Success? Then go ahead and perform the next step in order!
--- Step 4 ---
power up the phone with an activated sim card with data.
during the initial set up, select use mobile data option instead of Wifi
Finish the set up using mobile data
power down the phone, remove sim
boot into recovery & clear cache
(power + volume down into bootloader
select recovery, let it fully go into recovery
in recovery press power+volume up
select clear cache from the drop down menu
Reboot)
Do not insert the sim back yet
--- Final Step: The Fix ---
Go into settings & hit the wifi on switch only once and leave it
Now, it will attempt to turn the wifi and it will either turn on or after a few attempts the phone will reboot...
If it does reboot on its own it will seem like it is stuck in a boot loop but don't panic - it's not.
It will do a few loops and then boot back into sense and your wifi will work.
------------
Hope it works for you and make sure you follow the steps exactly as I listed them because that is the variation that worked for me and six other devices with the same exact problem. This also fixed not having 4G / hspa on one of the devices but there are two extra steps needed to fix that issue.
From the research I collected, it seems this issue is caused by a specific ota update from tmobile that was released a while back.
Just a friendly tip, your not allowed to use hasoon2000's toolkit for certain reasons (not sure why myself) but it was banned by xda moderators so you should probably remove it before you get reported
dd98 said:
Just a friendly tip, your not allowed to use hasoon2000's toolkit for certain reasons (not sure why myself) but it was banned by xda moderators so you should probably remove it before you get reported
Click to expand...
Click to collapse
Thanks for the heads up, I will remove the download link. I was also wondering why there were no links on the official thread since it had so many hits. I've been using his kits with success since the sensation =\
Also, I fixed another wifi problem on another one s for someone. I followed with the same steps.
But, this time... After the very last few steps (flashing 1.54 ruu, etc...) once I finally turned the wifi on, it sent the phone into a boot loop for 45 minutes (usually its just 10-20 minutes max) it eventually fixed its self.
I think that the RUU + stock recovery in the initial release has a unique file check system that automatically runs when it encounters a crash on the first boot and just goes crazy until it gets done fixing all the abnormalities.
So, don't panic or give up if your phones just looping for a long time, just leave it plugged in for as long as you can. Specially after if it starts looping when you turn the wifi on for the very first time.
nSavage said:
Background:
Hope it works for you and make sure you follow the steps exactly as I listed them because that is the variation that worked for me and six other devices with the same exact problem. This also fixed not having 4G / hspa on one of the devices but there are two extra steps needed to fix that issue.
From the research I collected, it seems this issue is caused by a specific ota update from tmobile that was released a while back.
Click to expand...
Click to collapse
Please, can you tell me which extra steps needed to fix 3g/4g issue? I only can connect 2g. Thanks.
I take place here, maybe i will test this theory soon.
I guess the devices can be s-off through this process, true?
edit:It was other problem, seems it's working.
never ending bootloop
nSavage said:
Background:
I recently bought an HTC One S for testing purposes & received it with the following specifications.
HTC ONE S[4] unlocked, s-off with cid -1111111 / stock tmobile / jelly bean
Unfortunately, it came with with the infamous wifi / bluetooth error.
At first I thought it was an hardware issue but after opening it up and examining it, I came to the conclusion that its software based and probably caused by a bad flash.
---
It took me about 2-3 days to fix this issue which included flashing ruu's, firmwares, hboots, recoveries, radios & infinite s-on / s-off / locked / unlocked / cid variations.
What is the Wifi + Bluetooth error?
When you try to turn on Wifi or Bluetooth from the settings, it just states that its turning on but then that quickly turns into "error".
Basically, your Wifi and/or Bluetooth are messed up and non-functional due to a bad flash.
The Fix
--- Step 1 ---
You need an all in one utility for the HTC One S - I used the following one,
[TOOL] HTC One S All-In-One Toolkit v4.0
You can download it by clicking [Link removed, I didn't know it wasn't allowed on XDA - Sorry, you will just have to do the steps manually via fastboot / cmd or find a kit on your own] It's pretty easy to do manually, just look for a fast boot tutorial, there are more than a few floating around.
--- Step 2 ---
I received the phone with supercid 111111 which I changed to stock T-MOB010 using the all in one tool and then flashed the proper carrier RUU for my cid (RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02 _10.18.31501S.08L_release_262073_signed.exe)
You will now need to flash the very first RUU available for your specific One S model / 1.53 is ideal, if you don't have access to that then maybe 1.78 might do the trick.
- Preparation -
(Important) You need: Locked bootloader, stock cid and the very first RUU.exe that was released for your device - In my 7 tests so far, the 1.53 ruu has always worked eventually. (read the 3rd post for an example on this)
Boot up into the bootloader by holding power + volume down.
You can lock the bootloader, change back to stock cid from the All in One tool while booted up in fastboot.
CID LIST + Help: http://forum.xda-developers.com/showthread.php?t=2139447
RUU's: http://forum.xda-developers.com/showthread.php?t=2200930
--- Step 3 ---
(Locked & Stock Cid)
Boot into fastboot, run the 1.53 (1.78?) RUU.exe
Success? Then go ahead and perform the next step in order!
--- Step 4 ---
power up the phone with an activated sim card with data.
during the initial set up, select use mobile data option instead of Wifi
Finish the set up using mobile data
power down the phone, remove sim
boot into recovery & clear cache
(power + volume down into bootloader
select recovery, let it fully go into recovery
in recovery press power+volume up
select clear cache from the drop down menu
Reboot)
Do not insert the sim back yet
--- Final Step: The Fix ---
Go into settings & hit the wifi on switch only once and leave it
Now, it will attempt to turn the wifi and it will either turn on or after a few attempts the phone will reboot...
If it does reboot on its own it will seem like it is stuck in a boot loop but don't panic - it's not.
It will do a few loops and then boot back into sense and your wifi will work.
------------
Hope it works for you and make sure you follow the steps exactly as I listed them because that is the variation that worked for me and six other devices with the same exact problem. This also fixed not having 4G / hspa on one of the devices but there are two extra steps needed to fix that issue.
From the research I collected, it seems this issue is caused by a specific ota update from tmobile that was released a while back.
Click to expand...
Click to collapse
I get this never ending bootloop when installing 1..53 or 1.78 Ruu.. i have the exact same problem.. i have tried evrything please help me.. i cant even boot into 1.53 Ruu..
I've just been given a Sensation with a cracked glass, and I was wondering whether to spend the cash for a replacement screen, when I noticed that I couldn't connect to my wifi network. I choose Settings > Wi-Fi, and for a long while it prints "Turning Wi-Fi on...", and then the message displayed is simply "Error". Some details about the phone:
Code:
Z710a (Telstra network in Australia)
Android 4.0.3
PYRAMID PVT SHIP S-OFF RL
HBOOT: 1.27.0000
RADIO: 11.23.3504.07_M2
OpenADSP: v02.6.0.2226.00.0131
eMMC: boot
From the GetRIL app:
Code:
RIL: 4.0.0024HMQ
Baseband: 11.69A.3504.00P_11.23.3504.??? Some numbers off-screen
Recommended baseband: 11.72.3504.00_11.23.3504.08_M2
**Note that I don't necessarily understand all of that, but I have managed the wire trick to get S-OFF (just cos I thought I needed to), and unlocked the phone with HTC's unlock process. I can manage fastboot, but I don't know a lot of other stuff - like recovery images for example.
Questions:
Is this wifi error likely to be a hardware thing, or is it because of the mismatch of the RIL and baseband, or something similar? (Buying more parts just might make it not worth fixing).
Will loading another ROM possibly fix it? (I don't know how to load another ROM).
Other issues:
I am not with Telstra, so can I easily convert to Z710e?
Cheers, please be gentle, I am a newbie.
Ben
george.jetson said:
I've just been given a Sensation with a cracked glass, and I was wondering whether to spend the cash for a replacement screen, when I noticed that I couldn't connect to my wifi network. I choose Settings > Wi-Fi, and for a long while it prints "Turning Wi-Fi on...", and then the message displayed is simply "Error". Some details about the phone:
Code:
Z710a (Telstra network in Australia)
Android 4.0.3
PYRAMID PVT SHIP S-OFF RL
HBOOT: 1.27.0000
RADIO: 11.23.3504.07_M2
OpenADSP: v02.6.0.2226.00.0131
eMMC: boot
From the GetRIL app:
Code:
RIL: 4.0.0024HMQ
Baseband: 11.69A.3504.00P_11.23.3504.??? Some numbers off-screen
Recommended baseband: 11.72.3504.00_11.23.3504.08_M2
**Note that I don't necessarily understand all of that, but I have managed the wire trick to get S-OFF (just cos I thought I needed to), and unlocked the phone with HTC's unlock process. I can manage fastboot, but I don't know a lot of other stuff - like recovery images for example.
Questions:
Is this wifi error likely to be a hardware thing, or is it because of the mismatch of the RIL and baseband, or something similar? (Buying more parts just might make it not worth fixing).
Will loading another ROM possibly fix it? (I don't know how to load another ROM).
Other issues:
I am not with Telstra, so can I easily convert to Z710e?
Cheers, please be gentle, I am a newbie.
Ben
Click to expand...
Click to collapse
you can use whatever custom rom you want
just flash first a custom recovery
i suggest 4ext recovery
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot command
the command is fastboot flash recovery recovery.img
fastboot reboot bootloader
after flashing a custom rom check if wifi is working
Thanks for the tips, Installed 4EXT and then CM12.1 but WiFi still not working.
I get some messages at HBOOT though, which might help explain something?
Images PG58DIAG.zip (and .nbh I think), and PG58IMG.zip (and some others like .enc...) are not found. What are these?
george.jetson said:
Thanks for the tips, Installed 4EXT and then CM12.1 but WiFi still not working.
I get some messages at HBOOT though, which might help explain something?
Images PG58DIAG.zip (and .nbh I think), and PG58IMG.zip (and some others like .enc...) are not found. What are these?
Click to expand...
Click to collapse
every time you are entering bootloader it is always scanning your sdcard for some files
nothing to worry
now try this
flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums (important)
rzr86 said:
now try this
flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums (important)
Click to expand...
Click to collapse
Thank you again!
Well that was exciting. Had to change the CID to supercid, then installed the new firmware without trouble. Accidentally rebooted into CM12, but after 10 minutes of not actually booting into it, I ripped out the battery and sdcard and tried again, this time booting into the bootloader.
Then, cleared the firmware from the sdcard, wiped cache, data, internal storage, and finally rebooted in CM12.
After updating apps, it booted into setup routine, where it tried again to turn on WiFi, but failed. Message appeared "Unfortunately, Bluetooth share has stopped".
I'm getting the feeling this might be a hardware problem!
Thanks for your help so far, do you think there's more I can try? I'm willing to go on with it still, if you are
george.jetson said:
Thank you again!
Well that was exciting. Had to change the CID to supercid, then installed the new firmware without trouble. Accidentally rebooted into CM12, but after 10 minutes of not actually booting into it, I ripped out the battery and sdcard and tried again, this time booting into the bootloader.
Then, cleared the firmware from the sdcard, wiped cache, data, internal storage, and finally rebooted in CM12.
After updating apps, it booted into setup routine, where it tried again to turn on WiFi, but failed. Message appeared "Unfortunately, Bluetooth share has stopped".
I'm getting the feeling this might be a hardware problem!
Thanks for your help so far, do you think there's more I can try? I'm willing to go on with it still, if you are
Click to expand...
Click to collapse
try to lift up gently the pins which are responsible for wifi in the back cover
rzr86 said:
try to lift up gently the pins which are responsible for wifi in the back cover
Click to expand...
Click to collapse
I tried this early on, just after I got the phone, but I don't know if I did it enough. It might break the pins I suppose. Perhaps there's a way to test with a multi-meter?
Perhaps I can test the radio flex cables with a multi-meter too?
george.jetson said:
I tried this early on, just after I got the phone, but I don't know if I did it enough. It might break the pins I suppose. Perhaps there's a way to test with a multi-meter?
Perhaps I can test the radio flex cables with a multi-meter too?
Click to expand...
Click to collapse
I'm going to go extreme now and try the heat gun reflow method on the wifi chip. This phone was probably dropped a few times, so it's possible the solder is cracked. I've not got much to lose really.
Still looking for ways to test the cables with a multi-meter though.