Is there a way to do this? I've gone through forums, and haven't seen anything concrete.
ericerk said:
Is there a way to do this? I've gone through forums, and haven't seen anything concrete.
Click to expand...
Click to collapse
If you're S-OFF (if not you can gain it by using Sunshine you can do an RUU, that will take you back to about as stock as you can get e.g stock firmware, stock ROM, stock recovery stock etc.
This thread will tell you most of the things you'd need to do.
I highly advise against attempting to go S-ON or re-locking your bootloader as S-ON has a high probability of failure and or bricking your device.
My personal recommendation would be to just take the RUU and if if I remember correctly you can make your ***UNLOCKED*** tag falsely show ***LOCKED*** instead, not sure though so if that interests you just Google it or ask.
EDIT: Here is the link to the tutorial on setting your UNLOCKED tag to LOCKED. Warning though I have not tested this or heard of anyone testing it so DO THIS AT YOUR OWN RISK.
S1L3nTShaDoWz said:
If you're S-OFF you can do an RUU, that will take you back to about as stock as you can get e.g stock firmware, stock ROM, stock recovery stock etc.
This thread will tell you most of the things you'd need to do.
I highly advise against attempting to go S-ON or re-locking your bootloader as S-ON has a high probability of failure and or bricking your device.
My personal recommendation would be to just take the RUU and if if I remember correctly you can make your ***UNLOCKED*** tag falsely show ***LOCKED*** instead, not sure though so if that interests you just Google it or ask.
EDIT: Here is the link to the tutorial on setting your UNLOCKED tag to LOCKED. Warning though I have not tested this or heard of anyone testing it so DO THIS AT YOUR OWN RISK.
Click to expand...
Click to collapse
I need to to return this device to Verizon.
ericerk said:
I need to to return this device to Verizon.
Click to expand...
Click to collapse
As far as I know they do not care if your phone is S-OFF or unlocked, only that it is running the stock firmware, ROM & recovery. Reason behind this is some of their phones are manufactured and shipped already S-OFF on 'accident', so as long as you do the RUU you should be perfectly fine, at least that is what everyone has said thus far.
S1L3nTShaDoWz said:
As far as I know they do not care if your phone is S-OFF or unlocked, only that it is running the stock firmware, ROM & recovery. Reason behind this is some of their phones are manufactured and shipped already S-OFF on 'accident'. So as long as you do the RUU you should be perfectly fine, at least that is what everyone has said thus far.
Click to expand...
Click to collapse
Are you willing to risk $800 bucks on this?
ericerk said:
Are you willing to risk $800 bucks on this?
Click to expand...
Click to collapse
Your risk not mine, if you're unsure then read through some other threads until you feel confident enough or wait for another person to answer.
& Sorry if I made you a bit unconfident with my last post, I have never had to return another phone to them so all I'm offering you is what I know and or have read from others who have done what you want to do. I'm quite sure that will work as many other people have claimed it worked for them but as with anything I could be wrong which is why I did not include a "*100% GUARANTEED!*" sign. Just offering support, always do your own research too, just as I had done to find that out.
S1L3nTShaDoWz said:
Your risk not mine, if you're unsure then read through some other threads until you feel confident enough or wait for another person to answer.
& Sorry if I made you a bit unconfident with my last post, I have never had to return another phone to them so all I'm offering you is what I know and or have read from others who have done what you want to do. I'm quite sure that will work as many other people have claimed it worked for them but as with anything I could be wrong which is why I did not include a "*100% GUARANTEED!*" sign. Just offering support, always do your own research too, just as I had done to find that out.
Click to expand...
Click to collapse
Bummer there's no official RUU's floating out there.
ericerk said:
Bummer there's no official RUU's floating out there.
Click to expand...
Click to collapse
I can vouch for the RUU I'm gonna link further in this post, I recently used it and successfully RUU'D my phone to stock.
http://www.droidviews.com/restore-verizon-htc-one-m8-to-stock-rom-with-ruu/2
ericerk said:
Are you willing to risk $800 bucks on this?
Click to expand...
Click to collapse
YOU have already done that the moment you modded your phone lol
S1L3nTShaDoWz said:
I can vouch for the RUU I'm gonna link further in this post, I recently used it and successfully RUU'D my phone to stock.
http://www.droidviews.com/restore-verizon-htc-one-m8-to-stock-rom-with-ruu/2
Click to expand...
Click to collapse
That's my ruu they link to. Stay on xda and get less shady stuff ?. Below is my thread on it..
http://forum.xda-developers.com/showthread.php?t=2727831
Amazing what some sites will do...
dottat said:
That's my ruu they link to. Stay on xda and get less shady stuff ?. Below is my thread on it..
http://forum.xda-developers.com/showthread.php?t=2727831
Amazing what some sites will do...
Click to expand...
Click to collapse
Since it's your RUU, is this RUU returning us to stock or stock-rooted?
tdnookhd said:
Since it's your RUU, is this RUU returning us to stock or stock-rooted?
Click to expand...
Click to collapse
Stock rooted.
Related
So recently my phone started having issues with the wireless and bluetooth, I've asked a few times on XDA-Developers on what might be causing this problem, but no one seems to know.
I've finally decided to do a warranty job on it, as no amount of ROM, radio, or kernal flashing is fixing it.
I'm up to rebranding my phone, and I was wondering if anyone had a copy of the stock HTC Sensation Telstra ROM, and anything else I may need apart from that when doing a warranty job?
There is a stock RUU listed in this thread
http://forum.xda-developers.com/showthread.php?t=1074559
I have flashed it before.
That Telstra RUU installs with the greatest of ease
You will also need to S-ON your phone. Find the guide in the stickies at the top of the dev forum and read, read, read before you start. Those that don't read the instructions end up with an expensive paperweight
tlgerdes said:
There is a stock RUU listed in this thread
http://forum.xda-developers.com/showthread.php?t=1074559
I have flashed it before.
Click to expand...
Click to collapse
Yeah, that one didn't work for me sorry mate.
http://forum.xda-developers.com/showpost.php?p=22179503&postcount=193
ReeF666 said:
Yeah, that one didn't work for me sorry mate.
Click to expand...
Click to collapse
When you say it didnt work, do you mean you couldnt download it or couldnt flash it?
tlgerdes said:
When you say it didnt work, do you mean you couldnt download it or couldnt flash it?
Click to expand...
Click to collapse
Greatly sorry about the fuss, it just required me to try it over and over again about 20 odd times before it finally worked. It also requires you to take yourself to the Bootloader via ADB.
ReeF666 said:
Greatly sorry about the fuss, it just required me to try it over and over again about 20 odd times before it finally worked. It also requires you to take yourself to the Bootloader via ADB.
Click to expand...
Click to collapse
Glad you got it going
Hi All,
OK, bootloader is unlocked, I am working on recovery, so the next challenge is....................S-OFF!!! Aw, f%@ck, I thought i had my life back...
I invite all users with ideas and/or knowledge to jump in and tell me what they think I am doing right and what makes me a moron. I have no pride, so lay it on me.
I will post progress reports in Post #2.
Anyway, here's to getting this done quickly.
Steve
Moderator Edit
This Thread has been moved back to the development section in an effort to put an end to the off topic discussion.
Given the size of this thread I'm going to suggest that you USE the Search thread feature located at the top to make sure your suggestion or idea has not been attempted already.
ANY OFF TOPIC POSTS WILL BE DELETED!
Progress Reports
Just starting out...
One More
This is just in case...
Excellent.
JSLEnterprises said:
Excellent.
Click to expand...
Click to collapse
Thought I'd get out of your thread and the root thread....
sk806 said:
Thought I'd get out of your thread and the root thread....
Click to expand...
Click to collapse
I had to send another message to red not to reopen the think tank thread (title would have been edited obviously), but to still go ahead with the cleanups... lol
Sorry if I'm totally off base here but I do believe reading on XDA somewhere that with the HTC One series phones when you unlock the bootloader it locks the phone from being able to flash recoverys.
This is the reason why I have waited to do the bootloader unlock I didnt want to screw myself from ever being able to flash custom roms.
you have to use this unlock method for the bootloader so why would it screw anything else up? It opens up all possibilities, not close them.
killathenoob said:
Sorry if I'm totally off base here but I do believe reading on XDA somewhere that with the HTC One series phones when you unlock the bootloader it locks the phone from being able to flash recoverys.
This is the reason why I have waited to do the bootloader unlock I didnt want to screw myself from ever being able to flash custom roms.
Click to expand...
Click to collapse
Nope. I have flashed CWM recovery at least 4 times on an international One X AFTER unlocking the bootloader. I wish that were it....
I think you may be thinking of firmware, which is a real mess, because unlocking your bootloader can set your CID to "none", and thus, you can't flash different firmware (i.e., an EU firmware on an Asian phone)...not that that would matter for these carrier-branded phones...
Good job and great progress. Unfortunately, none of us AT&T users can join in on the fun.
killathenoob said:
Sorry if I'm totally off base here but I do believe reading on XDA somewhere that with the HTC One series phones when you unlock the bootloader it locks the phone from being able to flash recoverys.
This is the reason why I have waited to do the bootloader unlock I didnt want to screw myself from ever being able to flash custom roms.
Click to expand...
Click to collapse
If that was completely true, then the Tegra 3 model's would not have cwm recovery... yet they do.
We just havent figured out a working method for ours.
JSLEnterprises said:
If that was completely true, then the Tegra 3 model's would not have cwm recovery... yet they do.
We just havent figured out a working method for ours.
Click to expand...
Click to collapse
i think what Killathehnoob is trying to say is that its only the ROGERS version of the ONE X that when unlocking the BLer HTC has somehow lock the other partitions so that custom recoveries and kernels are not able to be flashed to the phone...which essentially could be the case because all they said they will "unlock" the BLer...BUT they never said they would NOT do anything else in the process. maybe its a possibillity that has been over looked...just THINK TANKING is all
LNKNPRKFN said:
i think what Killathehnoob is trying to say is that its only the ROGERS version of the ONE X that when unlocking the BLer HTC has somehow lock the other partitions so that custom recoveries and kernels are not able to be flashed to the phone...which essentially could be the case because all they said they will "unlock" the BLer...BUT they never said they would NOT do anything else in the process. maybe its a possibillity that has been over looked...
Click to expand...
Click to collapse
I understand what you mean
I wonder if the fact that its new proprietary qualcomm chip is the reason why its being 'limited'... so we may have to rethink the whole initialization process.
we cant even get to the point that the logcat is able to start logging. So we're flying blind.
We've extended the time between loading to the soft reboot after the flash... but that doesnt tell us much.
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
killathenoob said:
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
Click to expand...
Click to collapse
Interesting. I think the lack is fastboot boot is what they are referring to. This would prevent custom kernel development on an s-off device, but should still allow flashing of insecure stock boot images, as with the int. HOX, althoug i read it again, anf maybe they are talking about more than that. I am not sure that the article is saying that there is something different with the Rogers version vs other versions, but it seems like there may be, and obviously with the Att version. I think I will spend a day just reading, trying to pick other devs' brains, and start fresh...thanks for the input.
Steve
sk806 said:
Interesting. I think the lack is fastboot boot is what they are referring to. This would prevent custom kernels being flashed on an s-off device, but should still allow flashing of insecure stock boot images, as with the int. HOX. I am not sure that the article is saying that there is something different with the Rogers version, but it seems like there may be, and obviously with the Att version. I think I will spend a day just reading, trying to pick other devs' brains, and start fresh...thanks for the input.
Steve
Click to expand...
Click to collapse
The 'fastboot boot' command works however, its how we got root in the first place.
... delegated to a Nigerian prince. Send money.
killathenoob said:
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
Click to expand...
Click to collapse
Here is the actual rootzwikk article
http://rootzwiki.com/news/_/articles/dear-htc-can-we-have-our-phones-back-r709
JSLEnterprises said:
The fastboot boot command works however, its how we got root in the first place.
... delegated to a Nigerian prince. Send money.
Click to expand...
Click to collapse
Whoa, very interesting. I was certain it did not on the Int one x.
JSLEnterprises said:
The 'fastboot boot' command works however, its how we got root in the first place.
... delegated to a Nigerian prince. Send money.
Click to expand...
Click to collapse
Just to be clear, you are not referring to fastboot flash boot, right?
Edit, nevermind, jut looked at Paul's post, it is fastboot boot. Wow.
killathenoob said:
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
Click to expand...
Click to collapse
Again thanks for this. Back to the drawing board!!!!
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.
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!
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.)