Good Day,
I recently tried to update my HTC One X (at&t) phone using the manual installation process as I am unable to do it OTA. I downloaded the RUU from HTC suport site and followed all the instructions but whenever the process reaches 29% in updating sysytemit gives me the error code (155) unkown error. The progress bar on the phone fills up green and at the end of the bar there is a small triangle with an exclamation mark at the end. That is not all when I unplug the phone it shows the HTC logo with four exclamation marks, one in each corner. And the phone doesn't turn on at all, no matter how much I try rebooting it. I have tried the installation process a number of times with the same result. How can I resolve this problem and How can I get my phone to turn on as normal. Please help me . I really love this phone my wife bought it for me just two months ago.
Yours Kindly
Roger Fontenelle
More info needed. Was the phone modified at all before you were doing this? Which RUU were you using? What were your bootloader details?
Sent from my Evita
Freakyfonty said:
Good Day,
I recently tried to update my HTC One X (at&t) phone using the manual installation process as I am unable to do it OTA. I downloaded the RUU from HTC suport site and followed all the instructions but whenever the process reaches 29% in updating system it gives me the error code (155) unknown error. The progress bar on the phone fills up green and at the end of the bar there is a small triangle with an exclamation mark at the end. That is not all when I unplug the phone it shows the HTC logo with four exclamation marks, one in each corner. And the phone doesn't turn on at all, no matter how much I try rebooting it. I have tried the installation process a number of times with the same result. How can I resolve this problem and How can I get my phone to turn on as normal. Please help me . I really love this phone my wife bought it for me just two months ago.
Yours Kindly
Roger Fontenelle
Click to expand...
Click to collapse
The bootloader is locked. I used the RUU from the HTC support site. I recently used this Ruu htc_one_x_RUU_2.20.502.7_att_us_08022012. I have gotten a little further the process now reaches 43% and says image update failure error 159.
Ok, but the question was has the phone been modified at all before? I guess you don't know what the bootloader details are/were?
Sent from my Evita
timmaaa said:
Ok, but the question was has the phone been modified at all before? I guess you don't know what the bootloader details are/were?
Sent from my Evita
Click to expand...
Click to collapse
The most I can get from this is Bootloader
(bootloader) cid: 11111111
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\FREAKYFONTY\Desktop\One_X_ATT_All-In-One_Kit_v3.0.1\One_X_ATT_All-In-On
e_Kit_v\data>
I used the All in one kit to get this infor version 3.0.1
This is what i get after i unplugged the phone
EVITA PVT SHIP S-OFF RL
CID 11111111
HBOOT-1.08.0000
RADIO-O.19as.32.09.11_2
OPENDSP-V29.1.0.45.0622
eMMC-boot
MAR 21 2012,16:01:09
RUU
Ok so the phone has been modified. Whatever you do, do not run any RUU higher than 2.20, it will brick your device. Do you happen to know what firmware version the phone was on before attempting to run the RUU? And what is the purpose of running the RUU?
Sent from my Evita
timmaaa said:
Ok so the phone has been modified. Whatever you do, do not run any RUU higher than 2.20, it will brick your device. Do you happen to know what firmware version the phone was on before attempting to run the RUU? And what is the purpose of running the RUU?
Sent from my Evita
Click to expand...
Click to collapse
RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radio_0.19as.32.09.11_2_10.105.32.25L_release_271865_signed
I ran this RUU and got it to work, thanks very much for attending to my post. Just t one question, how can i update this phone to the htc sense 4+ or jelly bean 4.1 and what do you mean by modified? My phone is unlocked that's how i got it out of the box. It's has at&t app on it but not registered to at&t as I am out of the US.
I'm not sure where you bought the phone, but it wasn't brand new. There are a few signs of this. Firstly, if the phone was brand new it would be on a much later/newer firmware/software version than it was. Next, the phone is s-off, the likelihood of the phone being shipped out of the factory like that is extremely low (I've seen only one case). Lastly, the phone has SuperCID (11111111 as opposed to CWS__001), the likelihood of the phone shipping out of the factory like that is also extremely low.
Does the phone have the HTC logo at the top of the screen or the at&t logo?
Sent from my Evita
timmaaa said:
I'm not sure where you bought the phone, but it wasn't brand new. There are a few signs of this. Firstly, if the phone was brand new it would be on a much later/newer firmware/software version than it was. Next, the phone is s-off, the likelihood of the phone being shipped out of the factory like that is extremely low (I've seen only one case). Lastly, the phone has SuperCID (11111111 as opposed to CWS__001), the likelihood of the phone shipping out of the factory like that is also extremely low.
Does the phone have the HTC logo at the top of the screen or the at&t logo?
Sent from my Evita
Click to expand...
Click to collapse
No actually the only time I see the at&t logo is when it's starting up and on the apps on the phone. Bought it on Amazon it said new
It's definitely a used phone, I hope you didn't pay too much for it. If you want to update it to 4.1 and Sense 4+ you can use the at&t 3.18 RUU, upon closer inspection of your bootloader details you have s-off so it's completely safe to do so. I didn't notice you had s-off earlier when I advised you not to do so, apologies for that.
Sent from my Evita
---------- Post added at 01:24 AM ---------- Previous post was at 01:18 AM ----------
EDIT: Actually, if you want Wi-Fi tethering/hotspot to work you should not use the at&t 3.18 RUU, use the HTC/Singtel/Starhub Singapore 3.17 RUU, you'll find it here:
http://forum.xda-developers.com/showthread.php?t=
Sent from my Evita
timmaaa said:
It's definitely a used phone, I hope you didn't pay too much for it. If you want to update it to 4.1 and Sense 4+ you can use the at&t 3.18 RUU, upon closer inspection of your bootloader details you have s-off so it's completely safe to do so. I didn't notice you had s-off earlier when I advised you not to do so, apologies for that.
Sent from my Evita
---------- Post added at 01:24 AM ---------- Previous post was at 01:18 AM ----------
EDIT: Actually, if you want Wi-Fi tethering/hotspot to work you should not use the at&t 3.18 RUU, use the HTC/Singtel/Starhub Singapore 3.17 RUU, you'll find it here:
http://forum.xda-developers.com/showthread.php?t=
Sent from my Evita
Click to expand...
Click to collapse
It's rather unfortunate that it's a used phone I put so much effort into research on this phone before I bought it. It was under the new section that why I purchased it my wife don't like buying used item especially phones. Paid $330US for it. So what you are saying to me is that as I have installed the ics on it version4.0 I can update using the link you privided. Here are the details of the phone.
Android Version 4.0.4
HtC Sense Version 4.0
Software number 2.20.502.7710RD
HTC SDK API LEVEL 4.23
HTC EXTENSION VERSION 403_1_GA_20
It is a shame, but as long as it all works ok I wouldn't worry too much. For some reason the whole link didn't post properly before so here it is again:
http://forum.xda-developers.com/showthread.php?t=1671237
That's the RUU Collection thread, you'll find links to many RUUs there, but the one that's probably best for you if you want 4.1 and Sense 4+ is the HTC/Singtel Singapore 3.17 RUU.
Android 4.2.2 and Sense 5 is available for our phones too now, you can take an OTA update after running the RUU to get that.
Sent from my Evita
timmaaa said:
It is a shame, but as long as it all works ok I wouldn't worry too much. For some reason the whole link didn't post properly before so here it is again:
http://forum.xda-developers.com/showthread.php?t=1671237
That's the RUU Collection thread, you'll find links to many RUUs there, but the one that's probably best for you if you want 4.1 and Sense 4+ is the HTC/Singtel Singapore 3.17 RUU.
Android 4.2.2 and Sense 5 is available for our phones too now, you can take an OTA update after running the RUU to get that.
Sent from my Evita
Click to expand...
Click to collapse
Thaks very much for your assistance, you have proven yourself invaluable by your contributuion towards my situation. Jus t one more question. As you have suggested. The HTc singetel Ruu that you suggested I use, would take me to Android 4.1 with HTC sense 4+ with no problems and then from there I can update ota for Android 4.2.2 with HTc Sense 5.
Taking an OTA on a modified phone can be somewhat risky, I don't have any first-hand experience but I believe you'd need to change your CID to the CID that the OTA is looking for, and have stock recovery. In my opinion it's probably a better idea to unlock your bootloader again, install TWRP recovery, and flash one of the many Android 4.2.2 Sense 5 ROMs we have available in our development section.
Part of the beauty of having the unlocked bootloader is that you can easily flash a different ROM if you decide you want a change. You'll have dozens of ROMs to choose from, from Sense to aosp. Plus many features that a stock phone just can't offer.
Sent from my Evita
Current OTA's will install correctly if:
1)s-off (required with supercid to prevent bricks but otherwise not required)
2)supercid (or valid cid for ruu/ota)
3)locked bootloader
4)RUU to desired base (this will also give you the correct recovery at the same time)
5)accept ota
Edit:
oh also:
6)I believe the mid should match unless you are s-off/supercid also.
Freakyfonty said:
It's rather unfortunate that it's a used phone I put so much effort into research on this phone before I bought it. It was under the new section that why I purchased it my wife don't like buying used item especially phones. Paid $330US for it.
Click to expand...
Click to collapse
Was it from Amazon directly, or a 3rd party that sells via Amazon? Either way, if it was explicitly describes as new (and not used or refurbished), I would contact the seller and seek at least a partial refund based on an incorrect or even fraudulent description. The phone is almost certainly used, as its SuperCID and S-off. And $330 is a lot to pay for a used AT&T One X. The going rate for this device used on eBay seems to be $200, give or take.
If such resolution by the seller is important to you, I'd advice looking into it before any further modification of the phone.
---------- Post added at 10:09 AM ---------- Previous post was at 10:06 AM ----------
timmaaa said:
Taking an OTA on a modified phone can be somewhat risky, I don't have any first-hand experience but I believe you'd need to change your CID to the CID that the OTA is looking for, and have stock recovery. In my opinion it's probably a better idea to unlock your bootloader again, install TWRP recovery, and flash one of the many Android 4.2.2 Sense 5 ROMs we have available in our development section.
Part of the beauty of having the unlocked bootloader is that you can easily flash a different ROM if you decide you want a change. You'll have dozens of ROMs to choose from, from Sense to aosp. Plus many features that a stock phone just can't offer.
Click to expand...
Click to collapse
I would agree with this. As long as you research and are comfortable with what root and unlocked bootloader mean, I'd say that having a modified phone is much better than returning to stock AT&T software.
redpoint73 said:
Was it from Amazon directly, or a 3rd party that sells via Amazon? Either way, if it was explicitly describes as new (and not used or refurbished), I would contact the seller and seek at least a partial refund based on an incorrect or even fraudulent description. The phone is almost certainly used, as its SuperCID and S-off. And $330 is a lot to pay for a used AT&T One X. The going rate for this device used on eBay seems to be $200, give or take.
If such resolution by the seller is important to you, I'd advice looking into it before any further modification of the phone.
Click to expand...
Click to collapse
I agree totally. The phone is definitely second-hand, not only is it SuperCID and s-off but it's also running an at&t ROM on a non at&t device. I'd be hounding for a partial refund.
Sent from my Evita
timmaaa said:
I agree totally. The phone is definitely second-hand, not only is it SuperCID and s-off but it's also running an at&t ROM on a non at&t device. I'd be hounding for a partial refund.
Sent from my Evita
Click to expand...
Click to collapse
I want to express my thanks profusely to you guys for helping me out with my problems. You'll are truly great thanks so much. Sorry can't find the thanks button (lol) must be going blind. Contacted the store will let you know what they say. Not very hopeful on a positive response especially in the refund department. THANKS AGAIN
Freakyfonty said:
I want to express my thanks profusely to you guys for helping me out with my problems. You'll are truly great thanks so much. Sorry can't find the thanks button (lol) must be going blind. Contacted the store will let you know what they say. Not very hopeful on a positive response especially in the refund department. THANKS AGAIN
Click to expand...
Click to collapse
3rd party seller on Amazon? If they don't offer any way to remedy the problem, threaten to escalate the issue and report them to Amazon as a fraudulent merchant.
If they are a reputable seller, they should make good on this. If they aren't reputable, no reason to play nice. Report them and give them negative feedback.
Freakyfonty said:
Thaks very much for your assistance, you have proven yourself invaluable by your contributuion towards my situation. Jus t one more question. As you have suggested. The HTc singetel Ruu that you suggested I use, would take me to Android 4.1 with HTC sense 4+ with no problems and then from there I can update ota for Android 4.2.2 with HTc Sense 5.
Click to expand...
Click to collapse
Hey Timaaa,
Can't seem to find the RUU that you suggested in the thread, Is it possible that you can send me the direct link to get the HTC/Singtel Singapore 3.17 RUU. Thanks a lot. The site doesn't seem to be working anymore or is not responding. busylawson.com shows problem locating page.
Related
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.
Starting with where I am now: my ATT One X is totally unresponsive. Power button held, Power plus either of the volume buttons held, nothing produces any response. When I plug it into a wall adapter, the charging LED doesn't light up. It is both looking and talking like a brick.
Here's how I got here, and I'm hoping someone may have some kind of suggestion .
I had been running Tachi91's original Sense JB ROM. TWRP recovery. I used the AT&T JB update RUU from HTC's site.
Before doing this, I rebooted to bootloader and re-locked the bootloader. After this, I seemed to be unable to reboot back into system, so I just ran the RUU while the phone was sitting in the bootloader (figuring that the first thing the RUU seems to have done in the past is reboot to the bootloader).
The RUU went through its usual lengthy, multi-reboot thing. No errors whatsoever, everything seemed totally fine. Clicked "Finish" at the end...and my phone's screen went black. I figured it was rebooting, but unless it's taken the past 40 minutes to reboot (which seems unlikely! ), something is obviously amiss. See beginning of post for what I've tried since and results.
Any suggestions?
http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
I fear the worst.
Sent from my HOX w/CM10.1 4.2.2 s-off
subarudroid said:
http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
I fear the worst.
Sent from my HOX w/CM10.1 4.2.2 s-off
Click to expand...
Click to collapse
...yeeeeah, total violation of item #1 on that list. And here I figured I was relatively safe with an RUU. Oops.
Thanks for pointing that post out to me. At least I know where I stand now! Better than sitting here making my thumbs go numb trying different power/volume combinations.
Why oh why do many people persist in thinking they don't need s-off??
Sent from my Nexus 7 using Tapatalk HD
Please help!
Hey, does any one know if there is any solution i can do myself? or do i have to send it to a jtag repair, because i just received it a month ago from a earlier brick. I just can not believe i bricked it again doing a RUU update. Thank you
buy a jtag
Nicobesso said:
Hey, does any one know if there is any solution i can do myself? or do i have to send it to a jtag repair, because i just received it a month ago from a earlier brick. I just can not believe i bricked it again doing a RUU update. Thank you
Click to expand...
Click to collapse
Could try the JET. Check the Development forum.
Hi all,
I have an AT&T One X. The bootloader is unlocked but is S-ON. I want to return this phone to as close as stock as possible. This phone is destined to go to another user who knows nothing of rooting and such so I don't care if it is rooted or not.
I understand I have to relock the bootloader to be able to flash an RUU right? Hboot is currently at 1.14.002, Radio is at 0.19as.32.09.11_2. TWRP 2.3.1.0 is installed.
The phone is currently running Cleanrom 6.5 and all works fine. I just want this back to as close to AT&T stock as possible so that the user I am giving the phone to will not have any problems.
If I relock the bootloader can I return this to stock via the most recent AT&T 3.18 RUU located here: http://forum.xda-developers.com/showthread.php?t=2191477 or is there something else I need to do first?
Thanks for all your help.
Tersanyus said:
Hi all,
I have an AT&T One X. The bootloader is unlocked but is S-ON. I want to return this phone to as close as stock as possible. This phone is destined to go to another user who knows nothing of rooting and such so I don't care if it is rooted or not.
I understand I have to relock the bootloader to be able to flash an RUU right? Hboot is currently at 1.14.002, Radio is at 0.19as.32.09.11_2. TWRP 2.3.1.0 is installed.
The phone is currently running Cleanrom 6.5 and all works fine. I just want this back to as close to AT&T stock as possible so that the user I am giving the phone to will not have any problems.
If I relock the bootloader can I return this to stock via the most recent AT&T 3.18 RUU located here: http://forum.xda-developers.com/showthread.php?t=2191477 or is there something else I need to do first?
Thanks for all your help.
Click to expand...
Click to collapse
You'll need to S-OFF first or you'll brick.
There's a howto on the original android development section.
exad said:
You'll need to S-OFF first or you'll brick.
There's a howto on the original android development section.
Click to expand...
Click to collapse
Just flash a stock rooted Rom. Most users won't even know it's rooted. And having a custom recovery (even if they don't know they have it) can help if there is ever an issue. S-off so in the future if there's a update it won't brick the phone.
Sent from my HTC One X using xda premium
31ken31 said:
Just flash a stock rooted Rom. Most users won't even know it's rooted. And having a custom recovery (even if they don't know they have it) can help if there is ever an issue. S-off so in the future if there's a update it won't brick the phone.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I agree, except for leaving it rooted. I would leave just the bootloader unlocked and S-OFF and RUU, this way the buyer doesn't get shocked or confused if an app asks for root access, but has the option to do whatever they want to their phone if they so decide.
exad said:
I agree, except for leaving it rooted. I would leave just the bootloader unlocked and S-OFF and RUU, this way the buyer doesn't get shocked or confused if an app asks for root access, but has the option to do whatever they want to their phone if they so decide.
Click to expand...
Click to collapse
I forgot about su access prompt. That could be a shocker lol
Sent from my HTC One X using xda premium
exad said:
I would leave just the bootloader unlocked and S-OFF and RUU.
Click to expand...
Click to collapse
I agree. Couple reasons (both related to RUU). If the new user for some reason needs to recover the phone, and runs the RUU (not unheard of, HTC support will sometimes direct customers to do this), that person will either:
1) Brick the phone, if its left as SuperCID and S-on
2) If S-on (but CID is changed back), and bootloader is left unlocked, the RUU won't run. The person will have no idea why, and will likely be stuck.
S-off solves both of these potential issues. If you are at all worried about the next user. I would S-off, then run the RUU to return the phone to stock. The only thing that would be "not stock" is unlocked bootloader and S-off. But neither of these will mean anything or affect a less experienced user.
I'm going to disagree with the above.
If this person knows nothing of rooting and doesn't care, you should give them a stock phone. Being s-off is a potential security risk that should only be taken by someone who a) knows about it, and b) knows what it means. If you're selling this phone, it's arguably deceptive to give them something with a lurking vulnerability.
iElvis said:
I'm going to disagree with the above.
If this person knows nothing of rooting and doesn't care, you should give them a stock phone. Being s-off is a potential security risk that should only be taken by someone who a) knows about it, and b) knows what it means. If you're selling this phone, it's arguably deceptive to give them something with a lurking vulnerability.
Click to expand...
Click to collapse
Fair point. Switching the phone back to the AT&T CID and locking the bootloader might be the best alternative. Then run the RUU to get it back on stock recovery and ROM.
Giving/selling the phone to an unsuspecting noob with SuperCID and S-on just seems like a bad idea. Worse than S-off.
iElvis said:
I'm going to disagree with the above.
If this person knows nothing of rooting and doesn't care, you should give them a stock phone. Being s-off is a potential security risk that should only be taken by someone who a) knows about it, and b) knows what it means. If you're selling this phone, it's arguably deceptive to give them something with a lurking vulnerability.
Click to expand...
Click to collapse
I've seen bricks after RUUing, even after changing the CID back to default.. It's a toss up I guess. Typically, when I sell my phone or hacked device, I just sell it as being hacked this way people know what they are getting into. Advertising as such has never hindered my ability to sell it either.
redpoint73 said:
Fair point. Switching the phone back to the AT&T CID and locking the bootloader might be the best alternative. Then run the RUU to get it back on stock recovery and ROM.
Giving/selling the phone to an unsuspecting noob with SuperCID and S-on just seems like a bad idea. Worse than S-off.
Click to expand...
Click to collapse
I didn't mean leaving it supercid--that is obviously a risk.
exad said:
I've seen bricks after RUUing, even after changing the CID back to default.. It's a toss up I guess. Typically, when I sell my phone or hacked device, I just sell it as being hacked this way people know what they are getting into. Advertising as such has never hindered my ability to sell it either.
Click to expand...
Click to collapse
That's kind of my point. Selling it rooted is fine, just represent it for what it is. You shouldn't give a modified phone to someone who doesn't know what that even means.
The phone is going to a friend who has a Pantech Burst currently. As someone mentioned I didn't want them to get a SuperSU prompt for root access and have no idea what that means. I tried a stock rooted rom but it kept rebooting. I did factory reset/data wipe and reloaded the rom twice but still kept doing it. I thought it odd too. Cleamrom is acting just fine though.
After hard bricking a Droid DNA which I don't know if it was due to being unlocked and such I'm starting to feel rooting and custom roms isn't for me anymore. The Droid DNA was replaced and the replacement was never unlocked (and since it has most recent software it couldn't be unlocked. Don't get me wrong, I love not running stock devices. It's such a great feeling to get rid of all that carrier added bloat that I most liked.
I've actually moved on from the DNA as well. I'm on a One now from AT&T as my primary phone. And I so hate all that AT&T bloat in there. It's all disabled but still seeing it there just sends chills down my spine.
So now I am not so sure what to do about the One X now. My original thought was RUU back to factory and relock the bootloader and keep S-ON. That way if someone did look they'd only see "RELOCKED".
Makes me miss the easy days when I used a Captivate and Note 1. Those were so easy to use custom roms on.
iElvis said:
I didn't mean leaving it supercid--that is obviously a risk.
Click to expand...
Click to collapse
Your previous post didn't explicitly say anything about that, one way or another. So I was just clarifying for the benefit of the OP. I knew what you meant, but wanted to make sure the OP did, too!
i got this pm and i thot it was worth everyone to see. while i do not recomend turning any device s on,a verizon device that is not unlockable via htcdev is of much more importance,as the only thing that can rescue it is a new enough,signed RUU.
it really is not worth the risk,i promise.
nicholi2789 said:
scotty1223 said:
nicholi2789 said:
Hey there, Sorry to bother you with a PM like a noob, but I just have a quick question for you. I have just received a Certified like new replacement M8 from Verizon because my original one had a manufacturer defect. My original one was S-OFF, rooted, with custom recovery and the latest firmware (1.55.605.2) from Verizon. I'm trying to get it back to as close to stock as possible so Verizon doesn't try and say I modified it and mak me pay for it. I already un-rooted it, flashed stock recovery, and took the latest OTA so my radios match my software version. Then I followed this thread: http://forum.xda-developers.com/showthread.php?t=2708571
to re-lock the bootloader and set the lock status flag. It says locked again in fastboot.
The only thing I have left is the S-OFF that displays in fastboot. I'm trying to find a way to reset that, or at least modify it so it shows S-ON. That way if by some weird chance a Verizon employee boots it to fastboot it will show completely stock and S-ON.
Now i've found this thread: http://forum.xda-developers.com/showthread.php?t=2475216 for resetting the S-OFF flag. I posted in it and asked if it would work on the M8 and nobody could give me an answer. XDA member brymaster5000 told me to ask you and that you could provide an answer.
So finally, my question is, will this fastboot command "fastboot oem writesecureflag 3" work to set my M8 back to S-ON? I know it works on the M7 but nobody can tell me for sure on the M8.
Thanks alot for your time.
Nick
Click to expand...
Click to collapse
I would very strongly recommend that you do not turn s on. Phones came s off ,so leaving out that way is not an issue.
Turning s on may open a can of worms that you cannot recover from,and then you're paying for a phone for sure.
As long as your stock rom, recovery and locked you're good to go
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
What do you mean phones came s-off? Verizon sent people m8s that already were s-off? It just seems like a super obvious indication that the device was modified. Your not the first person that has said that going back to s-on is a bad idea, so I will listen and not tempt fate. But iam curious, What can happen by doing that command that could cause such problems? And don't stock RUUs return you to s-on? Or do they just reset everything else but s-off?
Click to expand...
Click to collapse
before any phone is released,batches are sent off to testers and these devices are always s off. i have owned several factory s off devices,and there is no way of proving the phone you have did not come this way. further, large phone resellers are able to use factory htc diagnostic files to clear security data(sim lock,s off,cid/mid),wich again is a legitimate reason a phone is s off.finding s off in the bootloader is not by any means a "super obvious" indication of having been messed with.
turning the phone s on could cause the tampered flag to reset(we dont completely understand all the things that trip it) or you could end up locked into bootloader with a security warning if the boot,system or recovery are not stock enough. either of these things ARE super obvious indicators that you have messed with it,and tried to hide it.
in the case of the security warning,the only course of action is to:
1)run a signed ruu(wich must meet many criteria since youre now s on)
or
2)re-unlock the bootloader. as you know,using htcdev to unlock is not possible with vzw
an ruu does not change/update the partition where the secutity flag lives and thus will NOT turn you s on.
Thanks for the write up, this should help some users decide. Wish it was as easy as flashing a pit file in Odin . That's one of the main reasons I've yet to root/s-off. HTC devices still confuse me xD
Sent from my HTC6525LVW using Tapatalk
wtoj34 said:
Thanks for the write up, this should help some users decide. Wish it was as easy as flashing a pit file in Odin . That's one of the main reasons I've yet to root/s-off. HTC devices still confuse me xD
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Agreed great write up... in reference to rooting the m8 it is very easy with weak sauce app I also find the s-off to be easier as well compared to Sammy devices using Odin. with my s4 like with the m8 there was no need for a pc for root but weak sause app is easier then using commands in a terminal emulator. Just my two sense.
thunderbls said:
Agreed great write up... in reference to rooting the m8 it is very easy with weak sauce app I also find the s-off to be easier as well compared to Sammy devices using Odin. with my s4 like with the m8 there was no need for a pc for root but weak sause app is easier then using commands in a terminal emulator. Just my two sense.
Click to expand...
Click to collapse
You have missed the point... If you are locked into the bootloader with a security warning and s-on, you can not use weak sauce and firewater
Sent from my HTC One VX using Tapatalk
People need to realize that verizon reps and techs see hundreds of phones, they don't know the details of every device. The security and bootloader status is obvious to us because it's our device and we know everything about it. To a samsung person they won't know WTF your talking about.
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
l7777 said:
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
Click to expand...
Click to collapse
Not really... More later
Sent from my HTC One VX using Tapatalk
scotty1223 said:
Not really... More later
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
Yes, I misinterpreted the comment as general ease of use which makes me look like an idiot given the reason for the response.... my apologies and note to self read xda after nap lol.
l7777 said:
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
Click to expand...
Click to collapse
Not really... More later
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
the prollem is that the vzw cid/mid are blocked(by vzws request ) at htcdev. changing the cid and/or mid will let you get an unlock_code.bin that will officially unlock the bootloader,but this token is only good while the phone contains these same parameters. i.e., you cant get yourself a token,then change the cid and mid back to stock and have the "safety net" of a token in case of a catastrophic security warning. cid,mid,esn,etc must all stay same in order for the token to continue working.
Q:"well,what if i just leave the cid/mid at something different?"
A:that may work,but it may set the tampered flag if the phone realizes that those partitions no longer match. since the cid and mid live in write protected partitions,its also possible what once s is on and the phone starts checking things in its boot sequence,that the processor may freak out,and go into a "do not boot" mode when signitures do not match what they should. (read "do not boot" as: pretty affective hard brick only recoverable by jtag)
plus,even if the phone did boot,and did not set the tampered flag, the phone is not stock,and may fail OTAs or have other issues that may affect users the phone is sent back out to,or may give it away that you have modified it.
the fact is,that these phones are not checked very well,as was said above. the chance of it being noticed that the s off phone is even different than others is slim to none,and it is quite possible that the phone will make it back out into the wild as a refurb without any sort of refurbishing process. if you thot all phones were hooked to a master computer that completely reset things,checked hardware,flashed the newest firmware,and reset things like supercid,simlock and s off,youd be mistaken. due to this fact,it is my strong opinion that patched hboots(displaying incorrect info of locked and s on),or incorrect cid/mids are extremely unethical and should never be sent in to fraud htc or the carriers,espeically since it may affect other users. returning the phone to a stock,locked s-off state is honest,and will not affect a future users esperince. the device will OTA and funtion normally and the unsavy user will never even know they have a device that is special
hope that cleared it up some.
also,sorry if either of my replies earlier were rude,they were not intended to be,im only able to text to speech short replies while im at work.
scotty1223 said:
the prollem is that the vzw cid/mid are blocked(by vzws request ) at htcdev. changing the cid and/or mid will let you get an unlock_code.bin that will officially unlock the bootloader,but this token is only good while the phone contains these same parameters. i.e., you cant get yourself a token,then change the cid and mid back to stock and have the "safety net" of a token in case of a catastrophic security warning. cid,mid,esn,etc must all stay same in order for the token to continue working.
Q:"well,what if i just leave the cid/mid at something different?"
A:that may work,but it may set the tampered flag if the phone realizes that those partitions no longer match. since the cid and mid live in write protected partitions,its also possible what once s is on and the phone starts checking things in its boot sequence,that the processor may freak out,and go into a "do not boot" mode when signitures do not match what they should. (read "do not boot" as: pretty affective hard brick only recoverable by jtag)
plus,even if the phone did boot,and did not set the tampered flag, the phone is not stock,and may fail OTAs or have other issues that may affect users the phone is sent back out to,or may give it away that you have modified it.
the fact is,that these phones are not checked very well,as was said above. the chance of it being noticed that the s off phone is even different than others is slim to none,and it is quite possible that the phone will make it back out into the wild as a refurb without any sort of refurbishing process. if you thot all phones were hooked to a master computer that completely reset things,checked hardware,flashed the newest firmware,and reset things like supercid,simlock and s off,youd be mistaken. due to this fact,it is my strong opinion that patched hboots(displaying incorrect info of locked and s on),or incorrect cid/mids are extremely unethical and should never be sent in to fraud htc or the carriers,espeically since it may affect other users. returning the phone to a stock,locked s-off state is honest,and will not affect a future users esperince. the device will OTA and funtion normally and the unsavy user will never even know they have a device that is special
hope that cleared it up some.
also,sorry if either of my replies earlier were rude,they were not intended to be,im only able to text to speech short replies while im at work.
Click to expand...
Click to collapse
Excellent info, I wondered if the unlock token was tied to the cid/mid. My personal preference is once the phone is unlocked it stays that way. It's my device and I'll take the responsibility for whatever happens to it barring some kind of hardware defect.
l7777 said:
Excellent info, I wondered if the unlock token was tied to the cid/mid. My personal preference is once the phone is unlocked it stays that way. It's my device and I'll take the responsibility for whatever happens to it barring some kind of hardware defect.
Click to expand...
Click to collapse
I agree completely.
Sent from my HTC One using Tapatalk
scotty1223 said:
I agree completely.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Anyone at the point of "return" should at least trying running my RUUish zip from boot loader before even thinking about relocking or s-on.
?. Glad to see you throwing some support over here
Sent from my Nexus 7 using Tapatalk
dottat said:
Anyone at the point of "return" should at least trying running my RUUish zip from boot loader before even thinking about relocking or s-on.
?. Glad to see you throwing some support over here
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Lol I try and throw support wherever its needed
So far, no m8 ruus yet. Hopefully some start popping up.
As far as I'm concerned,back to stock sequence is this:
While still rooted:
-return cid/mid to.stock
-reset tampered
-lock bootloader
Then:
-run release keys ruu
-collect underpants
-???
-proffit!
When ruu is not available,restore stock boot,system and recovery from backups.
After that's done allow phone to ota to current
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
How do you reset tampered?
scotty1223 said:
Lol I try and throw support wherever its needed
So far, no m8 ruus yet. Hopefully some start popping up.
As far as I'm concerned,back to stock sequence is this:
While still rooted:
-return cid/mid to.stock
-reset tampered
-lock bootloader
Then:
-run release keys ruu
-collect underpants
-???
-proffit!
When ruu is not available,restore stock boot,system and recovery from backups.
After that's done allow phone to ota to current
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
Paulb787 said:
How do you reset tampered?
Click to expand...
Click to collapse
Search this forum for a thread. I'm at work, I can't link it at the moment
Sent from my HTC One VX using Tapatalk
scotty1223 said:
So far, no m8 ruus yet. Hopefully some start popping up.
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
sorta?
For those who stay s-off and have issues I put together an ruu of sorts that includes the ota firmware that will get users out of a sticky situation. ?
Between the two of us we can probably fix most software problems as long as users stay s-off once s-off!!!
Sent from my Nexus 7 using Tapatalk
Ha, it's funny that you posted our PM conversation. It's kinda embarrassing but at least I asked someone who knew before just doing it, messing it up, then screaming to the forums for help. And while i am by no means a beginner Android power user, HTC devices are just a little bit different than the Samsung devices I am used to. Though there is alot of good information in this PM conversation that alot more people should know. Glad it could be of use! And thanks for taking the time to reply to my PMs Scotty. I appreciate that.
nicholi2789 said:
Ha, it's funny that you posted our PM conversation. It's kinda embarrassing but at least I asked someone who knew before just doing it, messing it up, then screaming to the forums for help. And while i am by no means a beginner Android power user, HTC devices are just a little bit different than the Samsung devices I am used to. Though there is alot of good information in this PM conversation that alot more people should know. Glad it could be of use! And thanks for taking the time to reply to my PMs Scotty. I appreciate that.
Click to expand...
Click to collapse
I didn't mean to embarrass you. They were good questions I thot everyone should read. I should have asked you,and can edit them if you wish.
Sent from my HTC PG09410 using Tapatalk 2
scotty1223 said:
I agree completely.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Nah I wasn't really embarrassed. Haha. I just meant that it's slightly embarrassing that I knew so little about HTC devices, but not a big deal or anything. You were right to post it though, there is some good information there that will do lots of people good.
dottat said:
sorta?
For those who stay s-off and have issues I put together an ruu of sorts that includes the ota firmware that will get users out of a sticky situation. ?
Between the two of us we can probably fix most software problems as long as users stay s-off once s-off!!!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Definately a great rescue resource. I just want to make sure that folks understand that since it is unsigned,it will do them no good if they are s on,and stuck in bootloader with a security warning.
As you said,they must stay s off to benefit.(further supporting the point of this thread- don't turn s on)
Sent from my HTC PG09410 using Tapatalk 2
I was going to relock/S-On my defective M8 before returning it. I didn't have time though, and ended up just sending back only wiped and un-rooted, although I don't think /system was 100% stock. VZW sent me a text:
VZW FREE MSG: Thank You! The defective device you recently returned has been received by Verizon Wireless.
Click to expand...
Click to collapse
That was several weeks ago, haven't heard a thing since. I'm assuming they didn't care it was unlocked, or they are very slow at processing the devices.
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.)