The latest OTA update has made my phone useless as a
phone, as it now gets no mobile reception...
Is there a way to reverse this upgrade?
My other option is a custom ROM, but i would prefer to stay stock at the moment if at all possible.
you can always run an RUU - One that doesnt contain the update
I was just educating myself on RUUs.
does it matter which one i run? i think my phone is unlocked/unbranded (i bought it second hand) but i'm not sure
EDIT: Nevermind, i checked my baseband against the list of RUUs and found that it is in fact unbranded. Now i know which one to get... just need FileFsctory to let me get it...
which is it you need ? Chances are there's a mirror somewhere
found a mirror, thanks
back to start... i tried to install the 1.53 version and it game an error 140 (bootloader)
I think its because the OTA updated the bootloader !
you cannot downgrade using RUU unless you have S-OFF
Well, i guess i'll have to root and install a custom ROM.
Thanks for the help!
what part do you want to revert ? The radio update ? Cause if so, there is a way to do this
Yeah, the radio. When i was 0.15 radio it worked, now with 0.16 it doesn't
Ok have a look at this http://forum.xda-developers.com/showthread.php?t=1684477
I dont think you have to have CWM installed on your device, You just need it on your PC, So you can boot into it.
Thanks! can't seem to find a 0.15 radio though
kuroyume_cl said:
The latest OTA update has made my phone useless as a
phone, as it now gets no mobile reception...
Is there a way to reverse this upgrade?
My other option is a custom ROM, but i would prefer to stay stock at the moment if at all possible.
Click to expand...
Click to collapse
OP does know the consequences of rooting devices right? It avoids your warrenty.
So just want to make sure, do you not get reception anywhere or only at certain area? If the former, it may indicate a fault on your phone caused by the update and you should not deal with it by rooting cos there is a chance rooting and downgrading may not fix it then you would have no where to go. The right move IMO, is to take the phone back to point of sale and demand an exchange. Most of users like me do not have such problem after update.
Just to remind, if you know what you are doing, by all means.
Sent from my HTC One S using XDA
kuroyume_cl said:
Thanks! can't seem to find a 0.15 radio though
Click to expand...
Click to collapse
extract it from an ruu
h.han said:
OP does know the consequences of rooting devices right? It avoids your warrenty.
So just want to make sure, do you not get reception anywhere or only at certain area? If the former, it may indicate a fault on your phone caused by the update and you should not deal with it by rooting cos there is a chance rooting and downgrading may not fix it then you would have no where to go. The right move IMO, is to take the phone back to point of sale and demand an exchange. Most of users like me do not have such problem after update.
Just to remind, if you know what you are doing, by all means.
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
The point of sale is a few thousand kilometers away
No warranty in my country, so i have to figure this out by myself
I have rooted and installed roms on previous phones, but this one seems more... complicated
azzledazzle said:
extract it from an ruu
Click to expand...
Click to collapse
how? (sorry about all of this, but never had an HTC before)
kuroyume_cl said:
how? (sorry about all of this, but never had an HTC before)
Click to expand...
Click to collapse
Look here http://www.freeyourandroid.com/guide/extract-rom-from-ruu once extracted the rom.zip, open it up and take out the radio.img.
put it in the place where you keep all your adb stuff. and flash it using the method linked a few posts back
Went though the whole process but baseband version still reads 0.16xxxxxxxx
It doesn't seem to have worked
Well, at this point i'm fairly certain i need to rollback my radio, as i installed CM9 and still no cell signal. I checked and it had the same baseband as the 1.78 ROM.
Related
has anybody tried downloading the stock rom from this thread:
http://forum.xda-developers.com/showthread.php?t=1178082
then renaming it to pg59img.zip, putting it onto the root of your sd card, turning off the phone and holding the power and vol dn buttons and letting it flash that way?
then, just follow normal procedure for s off and root that is also posted here in the forums.
i'm pretty sure the package overwrites the hboot, also, unless this is disabled with the new version.
would somebody try that and let me know?
S off is permanent l. Even if you flash a newest bootloader
What I meant was that there seems to be some people having trouble obtaining s off and maybe rooting with the latest hboot/update. If you were to simply roll it all back by flashing a pg59img file from that stock rom, it would put it back to a workable state. Correct? I don't have the latest update/hboot and I already have s off so I cannot test myself.
Sent from my myTouch_4G_Slide using XDA App
Pretty sure someone(s) reported it not working like that, because the version is too far out of date and fails the check.
I wish I had one S-ON so I could play too.
Blue6IX said:
Pretty sure someone(s) reported it not working like that, because the version is too far out of date and fails the check.
I wish I had one S-ON so I could play too.
Click to expand...
Click to collapse
yep, i remember people with S-ON not being able to downgrade with the RUU.
looking back thru the inital update thread, jonnycat26 threw out the suggestion of possibly using a goldcard to get past the S-ON..... any possibility of this at all? i don't know a whole lot about that process, but i did use it on my friend's dad's Inspire 4G. i'll do a little reading and see what exactly the idea behind it is.
Blue6IX said:
Pretty sure someone(s) reported it not working like that, because the version is too far out of date and fails the check.
I wish I had one S-ON so I could play too.
Click to expand...
Click to collapse
DRAT!!! I feared something like that. Well, it was worth a shot anyway. What about writing/pushing with adb?
Sent from my myTouch_4G_Slide using XDA App
hi guys simple question bc my software is still 1.73.502.1, all i've done is root my device so i can grab some apps and get titanium backup to uninstall some bloatware.
my question is there's lots of talk about 1.85 and i'm wondering why i haven't gotten the auto-update yet. can you confirm its bc at&t hasn't sent the 1.85 OTA update yet, and not bc i rooted my device thus negating any auto software updates? sorry if this is a dumb question.
There are no OTA updates as of yet. Those on 1.85 are on it because they ran the leaked RUU.
Unless you know what you're doing don't bother updating to .85 because you can lose all root/bootloader/CID to let you do as you please because theres no current exploit. Its also been reported by people [and me] that you get lower CPU benchmark scores via Quadrant for example, although a faster / snappier phone. A couple people have also said its more sluggish now for them but I believe thats based on what they have running [I use one home screen + no widgets].
thank you very much. will an unlocked boot and s-off phone still receive updates as well from AT&T both software and android updates?
chillsen said:
thank you very much. will an unlocked boot and s-off phone still receive updates as well from AT&T both software and android updates?
Click to expand...
Click to collapse
We won't know for sure what will happen until AT&T releases it.
Best practice is to not OTA update until the devs have had a crack at it and we know what's what.
iElvis said:
We won't know for sure what will happen until AT&T releases it.
Best practice is to not OTA update until the devs have had a crack at it and we know what's what.
Click to expand...
Click to collapse
thank you for that key info. will not be ota'ing until xda squad cracks it alllll!
Basically ... NO!
chillsen said:
hi guys simple question bc my software is still 1.73.502.1, all i've done is root my device so i can grab some apps and get titanium backup to uninstall some bloatware.
my question is there's lots of talk about 1.85 and i'm wondering why i haven't gotten the auto-update yet. can you confirm its bc at&t hasn't sent the 1.85 OTA update yet, and not bc i rooted my device thus negating any auto software updates? sorry if this is a dumb question.
Click to expand...
Click to collapse
Basically, once you root your phone, or change the CID, you will never again be able to get OTA up-dates. Sorry.
Peter
P.S. Then again, I could be wrong ... but that's what I've been led to believe.
Is it safe to assume, that if people who flashed leaked ruu's don't get ota's then some of the devs will release ruu's of the newest ota's ?
Sent from my HTC One X using XDA
PeterHTC said:
Basically, once you root your phone, or change the CID, you will never again be able to get OTA up-dates. Sorry.
Peter
P.S. Then again, I could be wrong ... but that's what I've been led to believe.
Click to expand...
Click to collapse
That would make the existence of this app a bit hard to explain, then.
All this info going around is very confusing for me...Basically i started on 1.73 (rooted)....ran 1.82 (rooted)....ran 1.85 (stuck).....anything i can do?.....i never unlocked any bootloader....i just liike the idea of root to get rid of bloat......
I know the feeling
patstock11 said:
All this info going around is very confusing for me...Basically i started on 1.73 (rooted)....ran 1.82 (rooted)....ran 1.85 (stuck).....anything i can do?.....i never unlocked any bootloader....i just liike the idea of root to get rid of bloat......
Click to expand...
Click to collapse
Same with me - waiting for root for 1.85 - nothing much we can do at this point! Sounds like there are quite a few of us stuck in Limbo.
Just keep watching the forums and waiting for Root!
Mike
Not really ...
iElvis said:
That would make the existence of this app a bit hard to explain, then.
Click to expand...
Click to collapse
Not really. That app is not compatible with the ONE X.
Peter
PeterHTC said:
Not really. That app is not compatible with the ONE X.
Peter
Click to expand...
Click to collapse
So you're suggesting that the root = no OTA is One X (or HTC) specific? Where did you hear that?
FWIW, I've got that app installed and it successfully saved a su copy.
PeterHTC said:
Not really. That app is not compatible with the ONE X.
Peter
Click to expand...
Click to collapse
Sorry, but you are wrong. If you are rooted and nothing else, you CAN and will receive OTA updates, for most devices. I've heard many accounts of people being rooted and then updating OTA and losing root, and getting it back after a while after a new exploit was found. Now, if you use custom ROMs or anything, that changes things, but just rooting doesn't do anything. Think about it, you aren't changing the ROM or the way it connects to AT&T's servers. You are just exploiting a vulnerability and gaining root access. Now, AT&T may have found a way to detect root, but as far as I know they don't and with only a root, OTA updates can be installed. Although any post-root modification might screw that up.
i had plenty of battery life and was on 2.20 4.0.4 update prior to installing this OTA. now my phone wont even turn on after i did the update nor will it charge and have the light come on.. any ideas?
Let me guess. You had supercid??
Sent from my HTC One X using Tapatalk 2
if supercid gives problems on the at&t ota, then you should of been s-off cause i did ota fine with s-off and supercid.
idk i havent really heard of it but maybe. anyway to fix this now or ?
no fix
ps3kev said:
idk i havent really heard of it but maybe. anyway to fix this now or ?
Click to expand...
Click to collapse
SuperCID is when you changed the CID on your phone to 1111111 when/if you tried to root your phone. Here's a brief explanation by another XDA poster.
gol_n_dal said:
Certain things, e.g. RUUs, need to have the correct Carrier ID on the phone in order to install via the bootloader or recovery using the PG58IMG.zip process. The Latest Firmware packs for example are grouped together into sets, this is to allow you to install them if you don't have SuperCID. If you have got SuperCID you can install any of them as all the CID checks pass.
Another reason to change the CID if to allow you to install a generic RUU instead of the one that came with the phone, this allows you to remove the bloatware. For example I'm on Vodafone and I installed the generic Euro RUU purely to get rig of the Vodafone crap that came pre-installed.
The process to change it back is identical to the way you write the SuperCID just using your original CID (mine for example is VODAP001). IIRC HTC__01 is the generic CID
Click to expand...
Click to collapse
Unfortunately, I am on the same boat you are, I did not change my CID from 1's back to it's original and the update bricked my phone. It own't power on or boot into anything, I'm crossing my fingers that the AT&T store will believe me when I say "I don't know what happened, can you fix it?" and give me a new phone.
enduser76 said:
SuperCID is when you changed the CID on your phone to 1111111 when/if you tried to root your phone. Here's a brief explanation by another XDA poster.
Unfortunately, I am on the same boat you are, I did not change my CID from 1's back to it's original and the update bricked my phone. It own't power on or boot into anything, I'm crossing my fingers that the AT&T store will believe me when I say "I don't know what happened, can you fix it?" and give me a new phone.
Click to expand...
Click to collapse
It is not known if super-cid causes issues with doing an OTA! I have super-cid and s-off, and I applied the AT&T OTA without any problems after using the 2.20 RUU to go back to stock. It may be that super-cid causes issues if you are not s-off, but I don't think anyone really knows if it is definitely the presence of the super-cid that is causing the problems. It could be, but given that some people don't have any problems, it could be anything.
tlazarus said:
It is not known if super-cid causes issues with doing an OTA! I have super-cid and s-off, and I applied the AT&T OTA without any problems after using the 2.20 RUU to go back to stock. It may be that super-cid causes issues if you are not s-off, but I don't think anyone really knows if it is definitely the presence of the super-cid that is causing the problems.
Click to expand...
Click to collapse
S-off is precisely the reason you didn't brick. S-off by definition means that all security checks are bypassed, including CID check.
redpoint73 said:
S-off is precisely the reason you didn't brick. S-off by definition means that all security checks are bypassed, including CID check.
Click to expand...
Click to collapse
Hmm so if I had S-Off and Supercid and update via OTA sent directly from att not flashed any other way I will be ok?
romy134 said:
Hmm so if I had S-Off and Supercid and update via OTA sent directly from att not flashed any other way I will be ok?
Click to expand...
Click to collapse
If you were S-Off and SuperCID then the OTA should not affect you.
But. WHY are people wanting the stock OTA? It's causing issues because some people don't know if it's going to brick their phones. Please just wait until custom ROMs come based on the OTA. It's much much much easier
redpoint73 said:
S-off is precisely the reason you didn't brick. S-off by definition means that all security checks are bypassed, including CID check.
Click to expand...
Click to collapse
Yup, now I (and hopefully people who read this thread) know better for next time.
I'm happy to report that AT&T swapped out my HTC One X for a new one and 4.1.1 is pretty sweet! I'm going to wait a while before unlocking and next time I'll make sure to have S-off
I found this thread useful, in that it gave me "closure" after trying desperately to revive my bricked phone for an hour. Got some Z's and woke up to a new phone - they couldn't turn it on at the AT&T service center and gave me a few examples of what could've happen. One of them was "using third party rom's" but they didn't accuse me of anything, they replaced my phone and I was on my way.
I seriously don't get why anyone updates ota. We have a flashable rom typically with a day
Sent from my HTC One X using xda premium
The_Zodiac said:
I seriously don't get why anyone updates ota. We have a flashable rom typically with a day
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
for the other images other then system that get updated, and with s-off now we don't really get screwed by anything so you might as well see if latest gives any improvements.
enduser76 said:
Yup, now I (and hopefully people who read this thread) know better for next time.
I'm happy to report that AT&T swapped out my HTC One X for a new one and 4.1.1 is pretty sweet! I'm going to wait a while before unlocking and next time I'll make sure to have S-off
I found this thread useful, in that it gave me "closure" after trying desperately to revive my bricked phone for an hour. Got some Z's and woke up to a new phone - they couldn't turn it on at the AT&T service center and gave me a few examples of what could've happen. One of them was "using third party rom's" but they didn't accuse me of anything, they replaced my phone and I was on my way.
Click to expand...
Click to collapse
People never listen or read up till its to late
Sent from my HTC One X using xda premium
enduser76 said:
Yup, now I (and hopefully people who read this thread) know better for next time.
I'm happy to report that AT&T swapped out my HTC One X for a new one and 4.1.1 is pretty sweet! I'm going to wait a while before unlocking and next time I'll make sure to have S-off
I found this thread useful, in that it gave me "closure" after trying desperately to revive my bricked phone for an hour. Got some Z's and woke up to a new phone - they couldn't turn it on at the AT&T service center and gave me a few examples of what could've happen. One of them was "using third party rom's" but they didn't accuse me of anything, they replaced my phone and I was on my way.
Click to expand...
Click to collapse
were you honest or did you scam at&t cause that just makes at&t want to make security tougher and hurts other more preve people.
DvineLord said:
were you honest or did you scam at&t cause that just makes at&t want to make security tougher and hurts other more preve people.
Click to expand...
Click to collapse
The guy at the service station didn't really ask me anything other than "what's wrong with your phone?" and I replied "it's not turning on." he said ok and plugged it into his machines and said he was going to run some tests and to take a seat. Five minutes later he said it's not turning on and he's going to replace it, I asked him what could've happen and he gave a few examples (including third party roms, etc) but that it could have been anything from a corrupt file to dropping it on the floor.
The_Zodiac said:
I seriously don't get why anyone updates ota. We have a flashable rom typically with a day
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
For me personally, I couldn't get most of the ROM's to work properly, if at all. I kept getting errors like " com.google.process.gapps has stopped working" or something similar and I'd have no phone service (for example) which is why I went back to stock.
DvineLord said:
were you honest or did you scam at&t cause that just makes at&t want to make security tougher and hurts other more preve people.
Click to expand...
Click to collapse
Not true and they are the scammers btw.
Sent from the HOXL dimension of S-OFF
c5satellite2 said:
Not true and they are the scammers btw.
Sent from the HOXL dimension of S-OFF
Click to expand...
Click to collapse
at&t customer service and even technical support have been badass for me last few years only issue is 110 bucks for my phone bill which imo should ive me the right to do whatever i want with my service and my phone without having to pay for tethering or getting throttled ever imo and cheaper early upgrades.
So I have used TMOUS rom for ALONG time and recently decided to switch to use Cyanogen being a fan of it form other platforms.
While on the TMOUS rom I had 4g connectivity in my area about 90% of the time with the occasional drop into 3g here and there. It always displayed a 4g image in the top.
When I switched to Cyanogen that pretty much stoped. It always says 3g and is slow as hell. every once in awhile it will say H+ but not for long. MOST of the time it is constantly switching between 3g/4g/edge then shutting off.
Now im not sure if its a rom problem or not, but its making me want to switch back to a TMOUS rom.
Any suggestions would be great!
Edit: Just for clairification, I am S-On
I have this problem as well. I even ran the ruu back to stock and it is still happening. Please and thank you!
cp101 said:
I have this problem as well. I even ran the ruu back to stock and it is still happening. Please and thank you!
Click to expand...
Click to collapse
Damn, this scares me.... any solution anyone?
I'm thinking it might be a hardware error at this point. I might just "lose my phone" or just flash to stock and return it, this is preposterous.
cp101 said:
I'm thinking it might be a hardware error at this point. I might just "lose my phone" or just flash to stock and return it, this is preposterous.
Click to expand...
Click to collapse
Unfortunately, it doesn't seem to be a hardware problem
I have been trolling the net for weeks but have not found a solution yet.
I've posted in threads here but no solution.....
My issues started when I went to CM ROM - I used to have great 4g all the time before I went to custom rom (I was on stock TMO US) .. Now no matter what I do, I am not able to get 4G again.... it's really irritating...
I've tried a bunch of custom ROMS.. I am on 1.13 HBOOT and S-ON .. .. CID = HTC__001 (originally my CID was stock TMO US CID whatever that is but now its not that.. I don't wan to run RUU because I don't have TMO US CID and dont want to brick my phone)
You can set your CID back easily with the All in One ToolKit found here.http://www.hasoon2000.info/getdownload.php?file=One%20S/One_S_All-In-One_Kit_v4.0.rar
That is not the problem, unfortunately. It just doesn't make much sense, whatever the problem is; and especially considering after a full RUU restock. That has always fixed whatever mess I have created in the past.
This rom should fix your problem. Dont forget to clear storage from bootloader. It will erase everything thoug. And follow the steps under show contents link.
http://forum.xda-developers.com/showthread.php?t=2250573
cp101 said:
You can set your CID back easily with the All in One ToolKit found here.http://www.hasoon2000.info/getdownload.php?file=One%20S/One_S_All-In-One_Kit_v4.0.rar
That is not the problem, unfortunately. It just doesn't make much sense, whatever the problem is; and especially considering after a full RUU restock. That has always fixed whatever mess I have created in the past.
Click to expand...
Click to collapse
I not sure if its a CID problem. The only thing I ever did was upgrade to the newest Hboot and load in the CM rom. even going back to the TMOUS rom does not fix the problem.
Its so bad, and never on 4g that im considering getting a new phone.
bnd10706 said:
I not sure if its a CID problem. The only thing I ever did was upgrade to the newest Hboot and load in the CM rom. even going back to the TMOUS rom does not fix the problem.
Its so bad, and never on 4g that im considering getting a new phone.
Click to expand...
Click to collapse
I'm in the same boat, friend. I've tried literally everything suggested, I'm just wondering what exactly happened in the flashing of the Maximus rom. The worst part being is that I GET 3g/H and then it drops back to E. It's so strange. The only thing I've not done is contact Tmobile about it, and i highly doubt that they would throttle my bandwidth without contacting me in some form or fashion.
cp101 said:
I'm in the same boat, friend. I've tried literally everything suggested, I'm just wondering what exactly happened in the flashing of the Maximus rom. The worst part being is that I GET 3g/H and then it drops back to E. It's so strange. The only thing I've not done is contact Tmobile about it, and i highly doubt that they would throttle my bandwidth without contacting me in some form or fashion.
Click to expand...
Click to collapse
my phone is still under warrenty. Im wondering if i am able to revert back to stock without them knowing if I can get a phone replacement.
From what I've read, it's doable; even with an unlocked phone. But I'd really like to know what in the dev's source code made this happen... it's a bit ridiculous.
jenenser83 said:
This rom should fix your problem. Dont forget to clear storage from bootloader. It will erase everything thoug. And follow the steps under show contents link.
http://forum.xda-developers.com/showthread.php?t=2250573
Click to expand...
Click to collapse
I just wanted to say, that I did this and it worked!
I did this the first time, but i just flashed the rom with a full wipe.
This time what I did was go into TWRP and erased everything....and I mean everything except TWRP.
After that i flashed the rom and boot.img and everything works great. 4g all the time again!
Sucks that im back on an older version of jellybean, but oh well
bnd10706 said:
I just wanted to say, that I did this and it worked!
I did this the first time, but i just flashed the rom with a full wipe.
This time what I did was go into TWRP and erased everything....and I mean everything except TWRP.
After that i flashed the rom and boot.img and everything works great. 4g all the time again!
Sucks that im back on an older version of jellybean, but oh well
Click to expand...
Click to collapse
Can you take me through the steps you took to achieve all of this? Thanks.
cp101 said:
Can you take me through the steps you took to achieve all of this? Thanks.
Click to expand...
Click to collapse
So what I did first was go into TWRP and selected wipe. Inside wipe i selected EVERYTHING, every little box. Then Wiped it.
This left nothing on the phone but the recovery. I then loaded on SuperSU from TWRP. I download the stock TMOUS rom that was posted earlier in this post.
In TWRP I mounted it and hooked it to computer and transfered the rom over.
Once the rom was on I did the install of the rom.
I rebooted the rom into bootloader.
Once in bootloader i put it into fastboot.
I had previous extracted the boot.img from the rom.
I sent the boot.img over via fastboot which restarted the phone.
Once it got all started up. No issues. I am on 4g 99% of the time now.
Im thinking the issue was definatly based in the CM rom.
Since this worked I wanted to test things out since my phone was pretty much stripped of everything.
I tried out Viper rom and a couple of other non CM based roms, and I have had no issues.
IM back on teh TMOUS rom though. Wifi calling will win over when i go overseas.
Thanks, but it did not work for me. It is a hardware issue on mine. Thanks again
cp101 said:
Thanks, but it did not work for me. It is a hardware issue on mine. Thanks again
Click to expand...
Click to collapse
Must be.
I did find something out though doing all my research. Did you ever at any point update the radio? TMobile uses some frequencies that some companies dont use.
It is my understanding that some of these roms are packed with radios that are generic and thus ment for multi carriers.
Not sure if thats your issue, but might want to look into.
Its nice being back on 4g though.
bootloader currently showing....
Bootloader info:
*** LOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-1.14.005
RaDIO-1.13.50.05.25
OpenDSP-v29.1.0.45.0622
eMMC-boot
Nov 21 2012,12:17:41
Software Number
2.35.531.12 710RD
Android
4.04
much thanks
the RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe found here is the latest one released for unbranded devices afaik.
alltho itll downgrade your radio as it seems...
Dolour said:
the RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe found here is the latest one released for unbranded devices afaik.
alltho itll downgrade your radio as it seems...
Click to expand...
Click to collapse
That one won't work. He has a T-Mobile US phone (SKU 531) and is a S-ON user. The RUU you linked is for the SKU 401. You can't change your SKU with S-ON.
@20twins10: Try this RUU. It should set your phone back to stock. You can update it afterwards to the latest version by using the OTA function in "settings>about". If the RUU doesn't work as expected you should turn off your internet connection, your firewall and you antivirus software, boot your phone to fastboot mode and try again.
Flippy498 said:
That one won't work. He has a T-Mobile US phone (SKU 531) and is a S-ON user. The RUU you linked is for the SKU 401. You can't change your SKU with S-ON.
Click to expand...
Click to collapse
well, the site linked allso contains the TMO ruus available, didnt figure from the bootloader info its a branded device.
Dolour said:
well, the site linked allso contains the TMO ruus available, didnt figure from the bootloader info its a branded device.
Click to expand...
Click to collapse
I know that. Guess where I found the TMOUS ruu.
Flippy498 said:
I know that. Guess where I found the TMOUS ruu.
Click to expand...
Click to collapse
well gj then i suppose.
a word of warning tho: updates messing with the hboot version seem to have a tendency to bork your mmcblk0p20, causing you to end up on edge only(im trying for weeks now,
to get my hands on a WORKING image for unbranded eu devices, without any luck).
so make sure to pull a backup to be able to revert!
Dolour said:
well gj then i suppose.
a word of warning tho: updates messing with the hboot version seem to have a tendency to bork your mmcblk0p20, causing you to end up on edge only(im trying for weeks now,
to get my hands on a WORKING image for unbranded eu devices, without any luck).
so make sure to pull a backup to be able to revert!
Click to expand...
Click to collapse
I actually never faced such a problem. And I upgraded and downgraded my One S's fimware a lot during the last three years. (But I think this is going too much off topic. So let's leave it at that. )
@20twins10: I just noticed that your bootloader is still locked. (I guess I have missed that info earlier.) So your phone seems to be untouched in terms of bootloader unlocking and rooting. That actually makes me wonder why you don't use the OTA function in settings>about?
Flippy498 said:
I actually never faced such a problem. And I upgraded and downgraded my One S's fimware a lot during the last three years. (But I think this is going too much off topic. So let's leave it at that. )
Click to expand...
Click to collapse
well, considering the 30+ pages long thread on this forum, regarding the issue, i wouldnt exactly call it OT, just bc youve been lucky until now.
btw, you dont, by "chance" *cough*, have one of the above mentioned mmcblk0p20's for unbranded, european devices handy(or could dd one if you find a couple minz)?
Dolour said:
well, considering the 30+ pages long thread on this forum, regarding the issue, i wouldnt exactly call it OT, just bc youve been lucky until now.
btw, you dont, by "chance" *cough*, have one of the above mentioned mmcblk0p20's for unbranded, european devices handy(or could dd one if you find a couple minz)?
Click to expand...
Click to collapse
But as far as I know the problems arose after people S-OFFed their phones and/or downgraded their hboot using a ruu. (Haven't checked that thread for over a year.) And neither of these processes has anything to do with this topic. So let's continue this discussion via PM.
Flippy498 said:
But as far as I know the problems arose after people S-OFFed their phones and/or downgraded their hboot using a ruu. (Haven't checked that thread for over a year.) And neither of these processes has anything to do with this topic. So let's continue this discussion via PM.
Click to expand...
Click to collapse
well it happened to me after doing a simple factory reset, no s-off, not even root, it definetly isnt related to hboot 2.16 or s-offing at all.
therefore i consider the suggestion of backing everything up before doing any changes to the OS pretty important, and totally on-topic.
hey guys thanks for all the responses. i need to get some time to sit and read them. i've been busy with work and school and was not able to get time back to xda till now.. just a quick update: i was able to adjust my driver files and get fastboot to recogonize my phone, i did get my bootloader unlocked and twrp flashed.. as far back as i can remember ive never used OTA's and always go about it . i guess ive always come to the conclusion an ota dl will get you on the hot list if you are out of warranty or conretact type deal..
but either way.. there is progress on my end. my wife runs a couple apps that require 5.0 or better so i'd like to get that to work for her.. she'll ***** when she needs to re-enter her pw's though.. cant wint.. much thanks..
20twins10 said:
hey guys thanks for all the responses. i need to get some time to sit and read them. i've been busy with work and school and was not able to get time back to xda till now.. just a quick update: i was able to adjust my driver files and get fastboot to recogonize my phone, i did get my bootloader unlocked and twrp flashed.. as far back as i can remember ive never used OTA's and always go about it . i guess ive always come to the conclusion an ota dl will get you on the hot list if you are out of warranty or conretact type deal..
but either way.. there is progress on my end. my wife runs a couple apps that require 5.0 or better so i'd like to get that to work for her.. she'll ***** when she needs to re-enter her pw's though.. cant wint.. much thanks..
Click to expand...
Click to collapse
I don't know what you mean with "getting on the hot list". (Sorry English isn't my mother tongue.)
Actually the unlock process and the flashing of TWRP was completely unnecessary. Before you should start flashing any custom files you need to upgrade to the latest firmware. Many of the android 5 custom roms won't work if your firmware is too old. Just flash the RUU and then install the OTAs. (Since you flashed TWRP you now must use the RUU whereas it's been optional at the point where you started this thread.)