i have recently flash the viper one s rom but for some reason i get 3g when i used to get 4g i live in miami anyway i think it has to do with the radio
android version:4.0.4
sense version:4.1
htc sdk api level:4.23
baseband version:0.16.31501s.6_2_10.22.31501s.10l
build #: 2.31.401.5 clb81535
how do i know which radio im using, what is the latest version, how to flash it without reverting to stock
randomnoob83 said:
baseband version: 0.16.31501s.6_2_10.22.31501s.10l
Click to expand...
Click to collapse
^^^That is your radio version.
The latest is 1.06es.50.02.31
You can flash radios without running RUUs or OTAs if your HBOOT version is older than 1.13
Thanks I have an older hboot but I can't seem to find a flashable zip only ruus and ota
Sent from my HTC One S using xda premium
randomnoob83 said:
i have recently flash the viper one s rom but for some reason i get 3g when i used to get 4g i live in miami anyway i think it has to do with the radio
Click to expand...
Click to collapse
Probably the Viper One S ROM isn't based on the TMOUS ROM. TMOUS ROMs show rel.99 3G, HSPA and DC-HSPA as 4G, this is by design/marketing. If it shows 3G when idle and H when active then all is working as intended. Confirm this by getting the speedtest.net app and checking download speeds, anything above 384 Kbps is HSPA.
Look at this post: http://forum.xda-developers.com/showthread.php?p=26312897#post26312897
You can extract those 3 images from the RUU or OTA.
In the RUU they are in the rom.zip. In the OTA they are in firmware.zip.
So its the same speeds as always just differenet icon?
Sent from my HTC One S using xda premium
Yes, speeds are same just incorrect icons
flashable zip:
http://forum.xda-developers.com/showthread.php?t=1684477&page=14
for hboot less than .13
Related
If you create a backup of your phone via clockwork, then flash a new radio and Rom. Then want to restore to the previous setup, do you have to flash the old radio.
How do I know which radio is current. I flashed one radio in my life on the incredible and want gingerbread sense 3.0 Rom but I'm paranoid.
Sent from my ADR6400L using xda premium
Addicted2Droid said:
If you create a backup of your phone via clockwork, then flash a new radio and Rom. Then want to restore to the previous setup, do you have to flash the old radio.
How do I know which radio is current. I flashed one radio in my life on the incredible and want gingerbread sense 3.0 Rom but I'm paranoid.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Yes. You have to flash the old radio in hboot to get it back.
How do I know which one I currently have and there's no problem flashing back to a previous radio?
Sent from my ADR6400L using xda premium
I have been reading good things about the .802 radio. I plan to install my 1st custom ROM along with this radio over the weekend.
Flashing radios on the Tbolt isn't as risky as it was on the dInc. I've flashed back and forth between newer and older radios 3 times in a day. It's a different process, but it's not that scary once you've done it. The link in my sig has instructions and links to all the radios.
Under About Phone/Software/More I have the following information:
Baseband version
1.48.00.0726w_2, 0.01.78.802w_3
I installed the new 802 radio to go with my NonS3ns3 (GB 2.11) ROM via by renaming
(802)PG05IMG.ZIP to PG05IMG.ZIP and installing it.
Did I update the CDMA and LTE radio or just CDMA? Is there a second file I need to install for the latest LTE radio?
EDIT: I little more reading on my part at http://forum.xda-developers.com/showthread.php?t=1048128 and I see that I have the latest CDMA and LTE radios from the 2.10.605.1 RUU
Curious if I should upgrade the CDMA radio to 1.48.00.0817 since its from the 2.11.605.0 RUU.
and I am still curious about the PRI info:
PRI Version is listed as:
1.41_002, 1.64.002
How is this information tied to the radio version?
Thanks for any guidance.
If I change my CID to SuperCID and then flash the updated Europe RUU(I'm on Virgin Canada), will that screw up my radio, signal, performance? Or will it be like having the 2.3.4 update?
it will be like running the 2.3.4 update, but i recommend the latest WWE RUU (if available) i DID run the 1.45 europe with no problems, then flashed a new rom and was right as rain
Solidus_n313 said:
it will be like running the 2.3.4 update, but i recommend the latest WWE RUU (if available) i DID run the 1.45 europe with no problems, then flashed a new rom and was right as rain
Click to expand...
Click to collapse
I saw one RUU That said Europe 1.45 and one that said Europe LE 1.47. Any idea on which one is the better to use?
Also will I still get H+ or just H?
Zehlek said:
I saw one RUU That said Europe 1.45 and one that said Europe LE 1.47. Any idea on which one is the better to use?
Also will I still get H+ or just H?
Click to expand...
Click to collapse
i still havent run teh latest 1.47, which i need to cuz i want to test the latest InsertCoin roms with peak performance and minimal issues...
i would assume that it would not cause any issues, and can always be rolled back by running an older update (no locked basebands, thankfully), but more than likely your phone performance will improve with the updated radio
Thanks a lot. I noticed I was only getting an H now instead of H+. I don't really have a data plan so I'm not to worried about it. It works better with the update. Thank you
It's because in the EU we don't have H+/4G - H is the highest icon you can get
EddyOS said:
It's because in the EU we don't have H+/4G - H is the highest icon you can get
Click to expand...
Click to collapse
Ok thanks
Sent from my HTC Sensation 4G using Tapatalk
So does that mean if I flashed the Tmous version. I wouldn't get any signal because T-Mobile uses AWS?
Sent from my HTC Sensation 4G using Tapatalk
These are flashable zips that will change your baseband (radio firmware). Google it See twistedxx's post quoted below if you have no idea what this means. If you have an HTC One X (Tegra 3) you're in the wrong place.
twistedddx said:
Radio = firmware
RIL(radio interface layer) = driver
Android = operating system
All 3 are "programs" that are running at different "levels", I have listed them from top to bottom in the order typically considered for how they interact. It is important to understand that a program is just code and how they interact is a philosophy programmers created and are now use to and not because it has to be set out that way.
In the case of the RIL, the API rarely/never changes so it is rarely/never updated.
The actual changes HTC make happen in the "Radio" program.
This is opposite to how say Windows/Nvidia tackle things. The firmware rarely/never changes and they make their changes in the "driver".
In Nvidia's case they do this because there is no standard way in x86BIOS/Windows for GPU firmware to be loaded from something as simple as the installed HDD, the firmware is actually written to chips on the card itself. It is just simpler to make all the code that gets changed inside the "driver" which is easily updated.
For our phones "radio" its trivial for the changes in code to happen at the "driver" level or the "firmware" level, HTC/Google decided they would stick changes in the "firmware". They did this because they created a separate partition for the radio so that they can protect it separately to the OS. Android typically means the phones OS should be open for tweaking, so it must be assumed the driver could easily be replaced.
Countries and Carriers have licensed spectrum to protect and transmitters must be licensed to use it, running custom radio code would break laws in many countries. This leads to the radio firmware being protected much more heavily than the OS itself.
It is because HTC is lazy and because we have awesome devs that we can replace the radio firmware at all. As far as HTC, Country communication regulators and carriers are concerned the user should NEVER be altering the radio software.
Radio:
radio(fancy code stuff) <-> ril(boring translator) <-> Android OS
Nvidia:
firmware(advanced fixed code that allows for flexible access) <-> driver(fancy code stuff and translator) <-> Windows
Note:
Radio is about wireless communications
Nvidia is about graphics processings. They are not similar technologies just some tech you may be familiar with.
PS. API = application programming interface.. and lets just say if you do not understand what that is.. I cant be arsed trying to explain that, go Google it.
Click to expand...
Click to collapse
If you're on the newer HBOOT (1.14) and insist on running a Sense based ROM use the Jet tool to downgrade to 1.09. This will allow you to write to the radio partition of the phone. Or just S-OFF (w00t!)
If you're running a CM 10.x ROM it doesn't matter what HBOOT you're on as the radio firmware is stored elsewhere (in a writable partition... /system to be precise).
Instructions:
1) Copy zip file to SD Card
2) Boot into Recovery (CWM or TWRP)
3) Flash
4) Reboot
Always take a Nandroid Backup in case something goes screwy!
Your bootloader will not show the correct baseband. I'm working on figuring out how the RUU updater handles the android_info.txt in the firmware.zip's
ethantarheels123 said:
I think maybe the op should add to the op that if you are running the official sense 5 4.2.2 builds, either telstra or tmobile germany, you SHOULD NOT be flashing the AT&T radios in the op, as they WILL cause data drops and reboots. Not quite sure about non-AT&T radios though...
Click to expand...
Click to collapse
These are radios for flashing in Sense OR CM 10.x builds after 7/15 nightly!!!. They don't include the RIL files.
CURRENTLY THE DROPBOX LINKS ARE DEAD, THEY'LL BE BACK SOON (Migrating everything over to dev host to avoid this situation in the future)
Rogers 1.73 (0.16a.32.09.06_10.81.32.14L):
ATT 1.73 & ATT 1.82 (0.16.32.09.19_2_10.79.32.08L) :
HTC ASIA HK 1.77 (0.16a.32.09.17_2_10.83.32.16L):
HTC TELSTRA 1.81 (0.17a.32.09.03_2_10.85.32.16L):
ATT 1.85 /1.82 (0.17.32.09.12_10.86.32.08L) : http://d-h.st/mgs - thanks to rburgman
HTC ASIA 1.88 (0.17a.32.09.16_2_10.88.32.17L):
ATT 2.09 (0.17a.32.09.24_2_10.91.32.19L):
HTC TELUS 1.91 (0.18a.32.09.01_2_10.94.32.20L):
HTC TELSTRA 1.89(0.18c.32.09.01_10.93a.32.20L):
HTC ROGERS 1.94 (0.18as.32.09.28_L_10.103.32.24L):
HTC ASIA 2.23 (0.19as.32.09.09_L_10.104b.32.25):
ATT 2.20 (0.19as.32.09.11_2_10.105.32.25): http://d-h.st/bZx
HTC O2 2.29 (0.19as.32.09.20_3_10.107.32.25): http://d-h.st/AKZ
HTC TELSTRA 2.40 (0.20os.32.09.15_10.113.32.28L): http://d-h.st/cMp
HTC 2.41 VODAPHONE (Thanks Turge!)(0.20os.32.09.10_2_10.113.32.28L): http://d-h.st/HCL
HTC Singtel-Telstra 3.17 (0.23as.32.09.29_10.128.32.34):
HTC TMobile-Germany 3.17 (0.24a.32.45.03_10.129.32.34): http://d-h.st/TDQ - thanks to coldrazor!
HTC ATT 3.18 (0.24p.32.09.06_10.130.32.34): http://d-h.st/Aez
HTC TELSTRA 3.17.841.9 (1.26a.32.45.19_10.134.32.34a): http://d-h.st/VoB
HTC VODAPHONE 3.17.162.7 (1.27a.32.45.15_2_10.135.32.34a): http://d-h.st/pGK
HTC VODAPHONE 3.17.162.8 (1.27a.32.45.28_10.135.32.34a): http://d-h.st/CIM
HTC TMobile-Germany 5.08 (1.31a.32.45.16_2): http://d-h.st/Z6X
HTC VodaPhone 5.06 (1.31a.32.45.16_2_10): http://d-h.st/hIM
PLEASE DO NOT USE ANY OF THE RADIOS BELOW IF YOU ARE ON RECENT VERSIONS OF ROMS. THERE ARE HERE FOR ARCHIVAL PURPOSES ONLY
RIL Files + Radio: (YMMV. RIL versions change from one release to the next. Turge is on Record as not supporting these for his ROMs)
HTC O2 2.29 (0.19as.32.09.20_3_10.107.32.25): http://d-h.st/8tn
HTC TELSTRA 2.40 (0.20os.32.09.15_10.113.32.28L): http://d-h.st/IJ4
HTC 2.41 VODAPHONE (Thanks Turge!)(0.20os.32.09.10_2_0.113.32.28L): http://d-h.st/KdE
HTC ATT 3.18 (Thanks to liamstears!)(0.24p.32.09.06_10.130.32.34): http://d-h.st/Maq
Radios for CM10.x based ROMs pre-7/15 builds (with radio in /system/etc/firmware)
TELSTRA 2.40 : http://d-h.st/vox
FIXED 2.41 VODAPHONE : http://d-h.st/0ah
O2 2.29 : http://d-h.st/gis
ATT 2.20 to revert back to stock cm10: http://d-h.st/R92
TELSTRA 1.89: http://d-h.st/yr4
Singtel-Telstra 3.17: http://d-h.st/UQa
TMOBILE GERMANY 3.17: http://d-h.st/645
ATT 3.18: http://d-h.st/DcT
HTC TELSTRA 3.17.841.9: http://d-h.st/Ewb
VODAPHONE 3.17.162.7: http://d-h.st/C9o
VODAPHONE 3.17.162.8: http://d-h.st/hKO
To Help decide which Radio is best for your area, try checking the Google Map: http://maps.google.com/maps/ms?ie=UTF&msa=0&msid=217917717250281685326.0004c262acfff78edb974
And please post your results to help other users out!!
possible to achieve soff since htc dev thinks its a rogers device?? rogers did achieve soff thrue htc dev right??? correct me if im wrong....
rpomponio said:
possible to achieve soff since htc dev thinks its a rogers device?? rogers did achieve soff thrue htc dev right??? correct me if im wrong....
Click to expand...
Click to collapse
I think only a handful did, mine didn't.
Sent from my HTC One X using xda premium
rpomponio said:
possible to achieve soff since htc dev thinks its a rogers device?? rogers did achieve soff thrue htc dev right??? correct me if im wrong....
Click to expand...
Click to collapse
I think over in the S=OFF Thread they've thrown around a few theories, I dont think any of them involved the radio partition.
The take away from this is that we've been able to flash images to partitions we didnt think we could without S=OFF (kernel, radio) so it might be a relatively moot point to achieve it. As far as ROM Development is concerned anyhow.
I think... could totally be wrong about all of that, though. =)
This is amazing man thank you!!
rpomponio said:
possible to achieve soff since htc dev thinks its a rogers device?? rogers did achieve soff thrue htc dev right??? correct me if im wrong....
Click to expand...
Click to collapse
Mine is a Rogers and didn't receive S-Off from HTC Dev.
any way you could make these for the AT&T radios? or at least point me in the right direction to find them?
Mosch26 said:
any way you could make these for the AT&T radios? or at least point me in the right direction to find them?
Click to expand...
Click to collapse
Looking for any one in particular?
When we get the kernel source, these forums will be buck wild
Sent from my HTC One X using xda premium
taylor.fowler said:
Looking for any one in particular?
Click to expand...
Click to collapse
the ones from 1.82 and 1.85 would be great!
Thanks for this, looking forward to att versions.
Sent from my HTC One X using Tapatalk 2
taylor.fowler said:
OK Folks, this is a CWM/TWRP Flashable zip to bring you back onto the Stock Rodgers Radio (Radio_0.16a.32.09.06). I'll add Asia and ATT versions if there's a demand for it (You can also just replace the radio.img file in the zip with whatever radio you want to flash).
Instructions:
1) Copy zip file to SD Card
2) Boot into Recovery
3) Flash
4) Reboot
Always take a Nandroid Backup in case something goes screwy!
https://www.dropbox.com/s/uje8r9erza80y0q/EVITA_Rodgers_Radio_0.16a.32.09.06.zip
Click to expand...
Click to collapse
great man. I'm on 1.73 ATT, any risk with flashing radio from either 1.82 or 1.85 ?
Do we have the ability to flash radios from the One S or does it have to be a S4 One X??
ge3kswag said:
Do we have the ability to flash radios from the One S or does it have to be a S4 One X??
Click to expand...
Click to collapse
This will most likely result in a brick
Sent from my HTC One X using XDA
First off thank you for this, I have been wanting my default rogers radio since upgrading to at&t 1.85 RUU. I have been questioning if there Is any difference in reception on my device.
Now, Please don't take this the wrong way, I am not trying to sound like an as!, but Rogers Canada does not have a "d" in Rogers. Again I realize this is a little petty, but I felt the point should at least be raised. Again, I am more then grateful that you have done this. Thanks again.
Sent from my HTC One X using Tapatalk 2
Zarboz said:
This will most likely result in a brick
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Or in one x getting hspa+ on T-Mobile lol.. jk
HTC oneSies
Please make one for ATT 1.85. I have been on 1.82 and didn't want to relock to RUU. I have been hoping for something like this for awhile now! Please good sir, may I have just a little more radios please, I haven't flashed anything in three long days.
rpomponio said:
possible to achieve soff since htc dev thinks its a rogers device?? rogers did achieve soff thrue htc dev right??? correct me if im wrong....
Click to expand...
Click to collapse
Why are you so adamant on achieving S-OFF now that were bootloader unlocked and we can flash full ROMS with the ability to flash the boot.img and flash the radios from within recovery there is absolutely nothing more that you need except for HTC to release the source. Once HTC releases the Source we can start getting custom kernels and AOSP ROMS can get moving.
Can someone post the ATT 1.73 radio ?
am uploading the ones for 1.82 and 1.85 now (it'll take a while)
Crappyvate said:
Can someone post the ATT 1.73 radio 0.16.32.09.01_3_10.79.32.08L ?
am uploading the ones for 1.82 and 1.85 now (it'll take a while)
Click to expand...
Click to collapse
Thanks...I'm like the other guy. Unlocked and on 1.73 running CleanRom 2.5...don't wanna relock to try the newer radio.
Hi guys, I have a Tmous device, but I changed it to supecid and installed 2.21 official ruu.. I'm not sure if it's network related but my signal seems worse..my hboot is 1.14..can I re flash the 1.78 tmous ruu if I change my Cid back to tmous? Will that change back my radio? and what radio do you guys recommend in my region? TIA!
Sent from my HTC One S using xda app-developers app
Can't downgrade. Impossible. Going to have to live with it since you have a higher hboot.
Sent from my HTC One S running ViperOneS!
As suggested in your thread in developers forum, try the radio from the new 2.31 update the radio reception wifi and phone has significantly improved!:victory:
I can't install the newest radio changed Cid to htc__y13 but ota won't install, says tampered os.. When I try running stock 2.21ruu, it won't install over htc_y13
Sent from my HTC One S using xda app-developers app
I found the cause of the problem.. My preferred network type is wcdma preferred.. When I changed it to wcdma/gsm/lte it finally finds the 3g signal in my room that my phone used to use when in 1.78 ruu.. Problem is, the setting won't stick and reverts back to wcdma preferred when I leave the screen.. Any fix pls??
Sent from my HTC One S using xda app-developers app
Change this line in build prop
ro.ril.hsdpa.category=24
It = 14 on 2.21 RUU. There are 2 locations.
T-MobileUS HTC One S running Stock Rooted 2.21.
fmedrano1977 said:
Change this line in build prop
ro.ril.hsdpa.category=24
It = 14 on 2.21 RUU. There are 2 locations.
T-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
I tried this before, but couldn't seem to notice any difference.. What does this exactly do mate? TIA!
Sent from my HTC One S using xda app-developers app
cyriantherockstar said:
I tried this before, but couldn't seem to notice any difference.. What does this exactly do mate? TIA!
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Well it's the same number in the stock T-Mobile Rom and I believe it has to do with the DL speed capabilities.
T-MobileUS HTC One S running Stock Rooted 2.21.
CWM/TWRP flashable zip for Sense made from rip of WWE 3.16.401.9 OTA.
Radio 1.15.50.05.29_10.30.50.08L
Can be flashed on any S-OFF device; any carrier, any location
(Sense) (Radio Only) http://www.mediafire.com/?lahi47imjcep4b9
(AOSP) (Radio Only) http://www.mediafire.com/?pd1p7iv8unxx7x4 by jamus28
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Recommended for T-Mobile US Sense Users
(Sense) (1.15 Radio + TMOUS Wi-Fi Partitions + TMOUS RCData) MUST edit build.prop to match below or problemz! http://www.mediafire.com/?ph8yzqu3qvbm9l1
Code:
ro.ril.hsdpa.category=24
ro.ril.hsupa.category=6
ro.ril.hsxpa=4 (MUST CHANGE)
ro.ril.fast.dormancy.rule=2
ro.ril.radio.svn=19 (MUST CHANGE)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE: Only tested on S-OFF, recommended to unlock or stay away from this flash!
Hey !
Tested on my French HTC S-ON Hboot 1.06 and its ok.
Thanx !
Tested and approuved on my One S HBOOT 2.15 S-OFF !
Radio 1.15.50.05.29 in the bootloader
With twpr 2.5.0.0 may cause Brick?
Thanks! Testing on spanish phone..
Thanks for this. I really like having individual zips per radio. Your last zip worked flawlessly so ill try this one too.
Cheers!
echó en Android
Thanks it works very good
Works great.
But I get full reception in an elevator that I used to get 0 before. Seems legit lol
usaff22 said:
Works great.
But I get full reception in an elevator that I used to get 0 before. Seems legit lol
Click to expand...
Click to collapse
It shows that or it actually has full reception? Sounds interesting. And you're on a non-Sense ROM?
jujusito said:
With twpr 2.5.0.0 may cause Brick?
Click to expand...
Click to collapse
No, not usually a brick situation.
At least not more likely than when flashing any other radio on any other recovery.
mobile post
Thanks!
Sent from F.E.M.A. Region 9
Phantom Pt. II said:
It shows that or it actually has full reception? Sounds interesting. And you're on a non-Sense ROM?
Click to expand...
Click to collapse
Not sure. I'll try tomorrow. Running ViperOneS 2.2.0.
Awesome - will test it tomorrow, 6 hour car drive in germany
Sent from my HTC One S using xda app-developers app
What does WWE stand for? And is this a later version than the T-Mobile that was released a short time ago? This only works on Sense?
Thanks!
instylz said:
What does WWE stand for? And is this a later version than the T-Mobile that was released a short time ago? This only works on Sense?
Thanks!
Click to expand...
Click to collapse
WWE means World Wide European (I think) and yes it's a higher-numbered version than the recent TMOUS release. The zip in the OP is only for sense.
OP edited with AOSP zip by jamus28
Sent from my HTC One S using Tapatalk 2
bigmoew said:
WWE means World Wide European (I think) and yes it's a higher-numbered version than the recent TMOUS release. The zip in the OP is only for sense.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
1.15 seems to load picures faster. I'm on a TMO US carrier and both new, 1.13 & 1.15 seem to have major improvements. I will not run a speed test but overall less hang ups on YouTube and browser apps.
echó en Android
Evil-Monkey said:
1.15 seems to load picures faster. I'm on a TMO US carrier and both new, 1.13 & 1.15 seem to have major improvements. I will not run a speed test but overall less hang ups on YouTube and browser apps.
echó en Android
Click to expand...
Click to collapse
Yeah, I've been doing speed tests on both and have been getting better speeds with them, slightly more with 1.15. Tmous user here.
Sent from my HTC One S using Tapatalk 2
bigmoew said:
Yeah, I've been doing speed tests on both and have been getting better speeds with them, slightly more with 1.15. Tmous user here.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Yeah I would do them but every speed test uses 30-40 mbs. When i had the 5 gig plan I wouldn't care but I downsized to 2gigs when I switched to Simple Mobile. I used to do three to five test and then do an average of every radio I would try. I flashed your 1.13 with the rcdata and then 1.15. Im gonna stick with 1.15. Did flashing 1.15 replace WiFi partitions and rcdata from previous 1.13? Or did doing them in that order give me a hybrid?
echó en Android
bigmoew said:
OP edited with AOSP zip by jamus28
Click to expand...
Click to collapse
It works for s-on device too, right?
Sent with HTC ONE S
Evil-Monkey said:
Yeah I would do them but every speed test uses 30-40 mbs. When i had the 5 gig plan I wouldn't care but I downsized to 2gigs when I switched to Simple Mobile. I used to do three to five test and then do an average of every radio I would try. I flashed your 1.13 with the rcdata and then 1.15. Im gonna stick with 1.15. Did flashing 1.15 replace WiFi partitions and rcdata from previous 1.13? Or did doing them in that order give me a hybrid?
echó en Android
Click to expand...
Click to collapse
You have the same setup as me; the 1.13 WiFi partitions and rcdata with the 1.15 radio.
RCData is just as network dependant as the radio - the TMOUS rcdata is more preferable than any other when on TMOUS network so that shouldn't be changed unless TMO produces another one.
The OTA update that brought 1.15 didn't have any WiFi partitions or rcdata, so we're good with the ones we have.
dave il barbaro said:
It works for s-on device too, right?
Sent with HTC ONE S
Click to expand...
Click to collapse
Dunno, try and let us know.
Sent from my HTC One S using Tapatalk 2