S-Off ~ What are the requirements to figure it out? - HTC One X+

Nothing changed since this thread opened, got a new question just jump to page 2
I am well aware that till now unless you have a developer phone with CID 11111111 you can't gain SuperCID which will make you able to S-Off your device (For those who are not aware what is S-Off , Its making the security on your bootloader "off" hence enabling you to flash your roms without the need to fastboot flash your boot.img)
But on a developer side, what do the devs need for the "Great Dream" of S-Off to be achieved for all of us?
Files, source codes , exploits. What exactly?
I am aware that this topic has seen the light of day more than once, but every time this topic is opened, no more than a week later its "dead". Why is it THAT impossible to figure out?
I am vaguely aware that it has something to do with the "Tegra 3" chip, but why? If it has something to do with the "Source Code" is there a class talking about security that the devs just removes from the equation then flashes it instead?
I am quite interested in this topic and I tried to look around, but I don't really know the process of what is actually going on under the hood. So Any general help/discussion is welcomed (and encouraged) . If anyone with any "IDEA" about how its done wanna join in (even if he isn't quite sure) or if a DEV from another device did it and can help please do. It's basically a GENERAL discusison that might help brainstorm some ideas .
As always, links to other threads explaining the whole process is welcomed, but just please don't reply with "IDK" because that's basically considered spam
I Also found this out : HTCDev.com uploaded a couple of source codes about their kernel : http://www.htcdev.com/devcenter/downloads which includes the HOX+ if that will be of any help.
Final words: I know that this thread won't probably magically just solve it, But it's just mostly for me and other users to learn
Edit: Since its not really a Q&A Section and more of a general discussion in my opinion so I posted it in general because I want all devs to just talk, since its not really an "Answer the question" thread. MODs you can move the thread if you find it in the wrong section, thank you.
~Ghandour

SuperCID is not a prerequisite to S-Off. Infact it's the other way round, you need to remove the security flag (S-Off) before you have the nessesary permission to modify your Carrier-ID. .
There are ways for end users to attain S-Off but it's either very pricey (Buying a SETool box/Card/Credits and using LGTool to S-Off) or very risky (Sending your phone to someone who already has the equipment to S-Off your phone and hope they dont steel it) lol
Sent from my HTC One X+ using Tapatalk

AndroHero said:
SuperCID is not a prerequisite to S-Off. Infact it's the other way round, you need to remove the security flag (S-Off) before you have the nessesary permission to modify your Carrier-ID. .
There are ways for end users to attain S-Off but it's either very pricey (Buying a SETool box/Card/Credits and using LGTool to S-Off) or very risky (Sending your phone to someone who already has the equipment to S-Off your phone and hope they dont steel it) lol
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
OH I forgot to mention, I am well aware that you can S-Off your device using expensive equipment (javacard) and so forth and so on, but this thread was meant for pure normal S-Off the old fashioned way, which you can do without any fancy equipment. Because I am sure that the other phones that can be "S-Off"ed don't really require you to buy all those tools. ^^

They can but it's alot harder for us because of our Tegra SOC's.
I've always wondered why we dont start a donation thread, we could raise the money for the equipment and give it to a trusted member to buy (Someone like lloir but with more time) Then the members who donated could send their phone to this trusted member and get it S-Off'd...
Sent from my HTC One X+ using Tapatalk

AndroHero said:
They can but it's alot harder for us because of our Tegra SOC's.
I've always wondered why we dont start a donation thread, we could raise the money for the equipment and give it to a trusted member to buy (Someone like lloir but with more time) Then the members who donated could send their phone to this trusted member and get it S-Off'd...
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
Well there is a thread about sending your phone to the US to an XDA Member with a java card somewhere around but that's not the point at all....
The thread was meant to understand why is it hard? Why can't it be achieved? What is the issue exactly? (From a developer's point of view)

I found this thread : http://forum.xda-developers.com/showthread.php?t=2057105
EDIT: This thread is helpful however the thread remains unsolved. What exploits do the dev try to find when trying to figure out a way to S-Off the device? Leaked DIAG zips ?
Because I am aware that the "S-ON" Policy is mostly only done by HTC. So How are other phones exploited? For example, the HTC One has a fully functional FULL S-OFF : http://forum.xda-developers.com/showthread.php?t=2473644
So Does this App contains the "Diag" zip found in the app or what? Any dev explanation would be helpful.

Attaining SuperCID
I attempted attaining SuperCID by combining this method with this information about the HOX+. It does not appear to have changed anything, so it looks like that part of the memory can't be modified, which probably rules out any method similar to that.

WindyCityRockr said:
I attempted attaining SuperCID by combining this method with this information about the HOX+. It does not appear to have changed anything, so it looks like that part of the memory can't be modified, which probably rules out any method similar to that.
Click to expand...
Click to collapse
Alright, So the issue we are talking about here is that the memory doesn't become saved. So the exploit basically will make it become saved.
So can't we talk about repeating the process over and over and over again till it actually works? Can't we remove the usb in the middle of the process and force a hard reboot?
Tell you what, I think i might try this out. Let's hope the phone keeps on running QQ
"Theoratically" speaking, what if we copy all that partition of the storage to our PC, format the partition then we push it. I know there will be a huge risk of break but in theory can this work without breaking the phone?

Ghand0ur said:
Alright, So the issue we are talking about here is that the memory doesn't become saved. So the exploit basically will make it become saved.
So can't we talk about repeating the process over and over and over again till it actually works? Can't we remove the usb in the middle of the process and force a hard reboot?
Tell you what, I think i might try this out. Let's hope the phone keeps on running QQ
"Theoratically" speaking, what if we copy all that partition of the storage to our PC, format the partition then we push it. I know there will be a huge risk of break but in theory can this work without breaking the phone?
Click to expand...
Click to collapse
Im willing to try whatever you want with my AT&T HOX+. Its a second phone that i dont use anyways. Just let me know what you want me to try. I would love S-OFF on it because then it might become useful to me.

m1ke420 said:
Im willing to try whatever you want with my AT&T HOX+. Its a second phone that i dont use anyways. Just let me know what you want me to try. I would love S-OFF on it because then it might become useful to me.
Click to expand...
Click to collapse
Well I admit that I don't have experience with development yet so I can't ask you to brick your phone with "false" claims So That's out of the question for me. HOWEVER, If any exploit is discovered since I have an international phone , AT&T will be required to test it as well.. But that's not for the near future on my part .. haha and generally speaking if any dev wants you to risk your phone before he risks his then he is not worthy imo.
Anyway back to topic:
Now for the general understanding @WindyCityRockr This post : http://forum.xda-developers.com/showthread.php?t=1671396 says that you pull a file edit it with HEX Code editor and then push it again. I read somewhere that someone changed the paritition setup so basically the "SDCard" became a whole different partition. Can you elaborate on what file you pulled and tried? Where to find it if the location changed?
EDIT: I found it in the root section /dev/block/ the mmc files are there
What I understand is that the "unlock_code.bin" gained from HTCDev makes you gain partial unlock, Did anyone try to edit that file? I mean Maybe the key answer lies in that file. Maybe if you can edit this file then you flash it maybe you gain S-Off?
Now generally speaking, if you are unlocked with S-ON, on other devices where you can use an app to gain S-Off, do you need to relock your bootloader and flash RUU and stock recovery before you try to S-Off your device? What will happen if you dont.
Anyway I will try to load up the file and inspect it abit then report back
Would be a pleasure if more devs join in.

Problem with S-Off on OneX/X+ exists because of different hardware between this phones and any other HTCs. For now there is no way to restore Your phone even with JTAG (tegra has disabled JTAG). No one know what is exactly needed to repair baseband/IMEI after direct flashing eMMC. We can restore phone, but baseband is still dead. We know also there are 3 chips needed to be paired. CPU, eMMC and XGold 626. If You change only one of them- phone has no IMEI, being SIM locked or boot only in bootloader. There is also problem with bootloader- is locked. That's why You can't totaly brick Your phone. There is no way to change anything in bootloader, so We can't S-off phone. Probably even with Java card. I have some diag files for OneX, but not working. We stuck. We need to know how to get SBK for Tegra 3

kwaku85 said:
Problem with S-Off on OneX/X+ exists because of different hardware between this phones and any other HTCs. For now there is no way to restore Your phone even with JTAG (tegra has disabled JTAG). No one know what is exactly needed to repair baseband/IMEI after direct flashing eMMC. We can restore phone, but baseband is still dead. We know also there are 3 chips needed to be paired. CPU, eMMC and XGold 626. If You change only one of them- phone has no IMEI, being SIM locked or boot only in bootloader. There is also problem with bootloader- is locked. That's why You can't totaly brick Your phone. There is no way to change anything in bootloader, so We can't S-off phone. Probably even with Java card. I have some diag files for OneX, but not working. We stuck. We need to know how to get SBK for Tegra 3
Click to expand...
Click to collapse
Alright, just let me comment or rather ask about some few points.
-I get that the international version and AT&T are different , one having LTE and the other dont, so does that mean that the S-Off here will be different between the international and the AT&T? If so, which is easier?
-You said if you change only one you become sim-locked, So did anyone succeed in changing one permenantly?
-There was a thread saying that you can make a backup of your IMEI folder and paste it , shouldn't that fix the IMEI issue?
-So you are saying even with a Java card and the original DIAGs we can't S-Off? How is that possible even though there are people who actually succeeded in doing so ?
So all these issues will be solved if we get the SBK? [Secure Boot Key] ?

Ghand0ur said:
Alright, just let me comment or rather ask about some few points.
-I get that the international version and AT&T are different , one having LTE and the other dont, so does that mean that the S-Off here will be different between the international and the AT&T? If so, which is easier?
-You said if you change only one you become sim-locked, So did anyone succeed in changing one permenantly?
-There was a thread saying that you can make a backup of your IMEI folder and paste it , shouldn't that fix the IMEI issue?
-So you are saying even with a Java card and the original DIAGs we can't S-Off? How is that possible even though there are people who actually succeeded in doing so ?
So all these issues will be solved if we get the SBK? [Secure Boot Key] ?
Click to expand...
Click to collapse
International and AT&T are different. International has Tegra3 CPU, AT&T is standard Snapdragon phone. It's just OneS in One X skin. So. probably for this last OneS S-Off solution should be working after some modifications. Need to ask some good devs. This version is also supported for JTAG flashing, IMEI repair etc.
Almost all HTCs has standard Qualcomm processors (even HTC One) and similar construction. International OneX is different. Completly different CPU (and GPU), different and locked by Nvidia bootloader. Security flags are in bootloader, so, We can't even touch it.
-I never heard about anyone who change any of this parts and bring phone to live. If anyone can do this- probably We can do everything else, incluging Bootloader security status changing (S-on/off)
-Yes, backup will help. But only if You still have original parts on Your PCB. If You change anything important- backup will not help You. To check how it's working We need to get 2 OneX with same version of SW, clean and not touched. Make backups and look inside. Mayby We can find differences and make solution for EFS repair. The sad things is 90% of broken OneX has HW problem, not SW.
- Still I have not Java card (White Card), but it's probably some universal device for new HTC models, but I'm affraid it can not work with International OneX, because of additional Tegra3 security. But mayby Java Card has some Tegra Security unlock instruction inside. Who knows
- I know some people just buy unlocked devices (for devs). Like I said before, I don't know how Java card is working, if it can disable Tegra security, then bootloader can be fully unlocked.
- Fater get SBK We can unlock bootloader, but for IMEI repair We need to understand OneX EFS construction, to know what should be change to see our IMEI and whole Radio back
For now I'm waiting for Z3X team progres on repair Nvidias HTC, they can directly flash eMMC, now, They're working on repair broken IMEI etc. That's the goal now.

Correction: ATT Model is Tegra 3
Sent from my HTC One X+ using Tapatalk 4

sixcarnage said:
Correction: ATT Model is Tegra 3
Sent from my HTC One X+ using Tapatalk 4
Click to expand...
Click to collapse
No way! http://www.gsmarena.com/htc_one_x_at&t-4614.php

AT&T One X has snapdragon cpu
AT&T One X"+" has Tegra3
Sent from my HTC One X+ using xda app-developers app

This is a One X+ thread go talk about One X elsewhere. AT&T One X+ is a Tegra 3 model.
Sent from my HTC One X+ using Tapatalk 4

sixcarnage said:
This is a One X+ thread go talk about One X elsewhere. AT&T One X+ is a Tegra 3 model.
Sent from my HTC One X+ using Tapatalk 4
Click to expand...
Click to collapse
Chillax bro, LoLzZzZ (so swag, i know) . Well Since both phones do have similar hardware, except the AT&T One X , So the ideas are joined. So even if you own a tegra 3 HOX, it's fine that you post here if you have something to say. I think he just misread the forum , its fine

Yeah, sorry, I was reading posts on HOX and HOX+ forums and just wrote on bad section. Sorry again, but HOX and HOX+ are similar phones. HOX+ has a little better CPU. S-off problem is same, Nvidia security is probably same. So, We still can't do anything.
I don't know much about programming, but if We can unlock bootloader via HTCdev, then must be some backdoor on Nvidia security, or mayby seucrity is disabled during bootloader unlocking operation. Mayby this is the way. Or mayby this part of bootloader security is somewhere else and Nvidia key not blocking this. I don't know. Any Dev is needed here.

Gotta love it when I resurrect an old thread (oh resurrect. Such a big word)
I've been wondering for quite a while about this question.
Turing on "Power saving" mode in the sense rom, turns down your CPU to 1.3GHZ, which means it UNDERCLOCKS your device. Correct me If I am wrong, if you are S-On you neither can underclock nor overclock your cpu . Right?
I know this has been thought by other great developers before, but is there no way to de-compile just the power saving function and inspecting to see how it gains the S-Off access? I mean the answer must be there.

Related

just got s-off? please read this.

ok,weve had s-off for a couple days now,and ive see quite a few questions on various threads that make me wonder why the posters even wanted s- off int he first place,other than following the crowd like lemmings. lots of "what do i do now,why is my hboot this or that..."
i feel all the new rooters need to see this:
please be careful!
you can now have complete control of your phone. you can chage whatever you want since its not doing ANY security checks at all. as such you have a much greater responsibility to know what your flashing and why,and that your files are 100% unmolested and uncorrupt.
please be aware that a bad bootloader or radio flash can and will brick your phone,possibly beyond recovery.
you do not any longer have the s-on safety net of htcdev.
im seeing alot of flip-flopping bootloaders around,and most folks dont even know why they want the eng hboot.please think about this.its risky-flashing a a new bootloader is prolly THE biggest risk you can take on your devices,as without a bootloader NOTHING will load. i.e.,you have a brick. if your current bootloader suits your needs(ie boots youre phone and supports the fastboot commands you regularly use) then why are you changing it?
s-off is awsome,i know but again,i just want all the noobs that have been asking various question to realize the the seriousness of having this privelege is. have fun flashing roms and slpash screens,but be extremely cautious/careful with the important parts of your device.
-make sure you know what your flashing,and why
-make sure you have an md5 summer and use it.
-if you just asked "whats an md5??" then learn it
-make sure you are comepletely comfortable with all procedures for things you do.
last and not least,please ask any questions BEFORE your phone makes a short lil buzz,shuts off,and wont come back on
A nice friendly reminder. I appreciate it Scotty and I think this should be stickied to avoid people bricking phones.
Sent from my ADR6425LVW
Someone had to say it.
I am of the opinion that if you cannot fully support your device on your own and do more than basic troubleshooting, you should not take the risks associated with modifying your firmware. I see posts from people who obviously can't handle basic troubleshooting and I am sure after the S-OFF announcement and instructions there are definitely some bricked phones out there, which Verizon is going to replace on their dime.
So I echo the OP ... Please be careful, and accept the consequences of your actions.
Great post Scotty. I'm glad you took the time to write that. Hopefully people will read it.
Checking md5 is super important.
Sent from my ADR6425LVW using XDA
Scotty, excellent info for everyone, not just the noobs, as some people don't realize they are still noobs.
Mods, this should be stickied when you get a chance.
Thank you for writing up this excellent post.
Something else that I think should be mentioned is that Verizon/HTC should not be eating the costs of these phones. If you decide to jump voltage on your phone and get stuck in a boot loop and then screw it up trying to fix it, then you need to step up and take responsibility, as the poster above mentioned. You don't have to tell Verizon you were s offing your phone, just tell them you tore it up. They will help you save some money one way or another if you talk to them, and if there's not an option for that hit up craigslist.
For those of you who may be reading this considering the pros and cons, I would wait until you actually need s off to do the process. And when and if you do it, don't do it when you are in a hurry. It's a short process but if you hit a snag and need to start over you do not want to be rushing or not paying attention.
Sent from my ADR6425LVW using xda premium
thanks for the posts,guys. i agree 100% if you screw up your own device trying to s-off it,or doing something stupid after,man up and pay for it. its not vzw or htcs fault.
CharliesTheMan,i espeically like your firmware download,i was planning to do something similar folks are so used to slapping on a new set of radios,they dont realize how important the rest of the firmware can be. the sensation guys have been using similar downloads for quite some time.
great guide,its exactly what we needed
A great way to check MD5 checksums is with AFV Android File Verifier. It works great and you do not have to check each file with a PC. I always download all of the files I flash from my phone, so using AFV make things much simpler.
Clay333 said:
A great way to check MD5 checksums is with AFV Android File Verifier. It works great and you do not have to check each file with a PC. I always download all of the files I flash from my phone, so using AFV make things much simpler.
Click to expand...
Click to collapse
I agree completely. If you download right to your phone,AFV is a great app. I also very highly recommend it.
Sent from my ADR6425LVW using XDA
Very helpful thank you. I'm one of those people who don't know what eng boot is lol
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
It is unfortunate that the stock hboot blocks fastboot commands unless you htcdev.com unlock again. That is the reason for the patched hboots. The S-OFF team I believe is working on a patched 2.11 hboot so the engineering hboot won't need to be used. So it will basically be the same as the 2.21 patched hboot they have for ICS.
Alright, so I am on gingerbread hboot, and have all of the files I need to s–off. After I get s-off, what steps do I need to take? I know this has been discussed, I and I am confident in my abilities, just want to do it right. Any help would appreciated. Thanks....
Sent from my ADR6425LVW using Tapatalk
Great info as always Scotty. People should know exactly what their getting into with S-Off and the consequences along with it. Going to add this to my FAQ.
Sent from my Htc Rezound
Follow me on twitter @lmrtech
I'm just curious. How could flashing wrong Radio brick the Phone ? Is there a technical reason for it ?
I've been flashing Radio on the Samsung Vibrant like crazy with all the radio even from AT&T without a hitch.
Thank you
Thanks Scotty, the main reason I did it was because I jammed something up and needed to do a fresh install anyway. I then assumed all of the upcoming roms will be prepared with s-off assumption. (not the best reason but I got through okay) I need to do my research on MD5 so I will take your advice. Best of luck to everyone else trying to get where they want to be, even if they don't need to be.
nbhnohome said:
I'm just curious. How could flashing wrong Radio brick the Phone ? Is there a technical reason for it ?
I've been flashing Radio on the Samsung Vibrant like crazy with all the radio even from AT&T without a hitch.
Thank you
Click to expand...
Click to collapse
Think of the radio like the bios on a main board. We've turned off the security check that makes sure the file is good. I beleive there is no signature check at all, so a corrupted download will still flash. A bad radio will leave you with a paper weight.
Sent from my ADR6425LVW using XDA
I am S-On with the GB firmware. If I don't S-Off, will I have problems down the road flashing new ROMs? I can I still flash the ROM, then fast boot the kernal?
k_flan said:
Think of the radio like the bios on a main board. We've turned off the security check that makes sure the file is good. I beleive there is no signature check at all, so a corrupted download will still flash. A bad radio will leave you with a paper weight.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
I though that Hboot (Bootloader???) acts as Bios. Anyway, be safe better than feeling regret
Thanks
k_flan said:
Think of the radio like the bios on a main board. We've turned off the security check that makes sure the file is good. I beleive there is no signature check at all, so a corrupted download will still flash. A bad radio will leave you with a paper weight.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Being technical here maybe, but a bad radio would technically just make you not have reception or data correct ? As long as your HBoot wasn't corrupted, you could flash the radios back. Big danger is if your flashing a different or corrupted Hboot right ? I am just trying to understand myself so not being argumentative just trying to get it straight with the way I understood it .

Evo 4G LTE 1.22.651.3 Root (EASY)

Anyone here on xda used this successfully??
re:
http://forums.androidcentral.com/ht...2777-evo-4g-lte-1-22-651-3-root-easy.html#anb
WTF do people take DEVs threads and post them on the her sites is beyond me. Rega's name want even mentioned. His thread was copied and pasted word for word. And the guy mentions its not his work and thanks to the guys who made it. Jezz, seriously irritates me. Not you lol. Here's the original thread you want http://forum.xda-developers.com/showthread.php?t=1690919
Msor people here used it including myself. I used it with the older version. But the dev is a cool dude. He'll help ya in any way he can.
Sent Blazing w/ Viper4G
reverepats said:
Here's the original thread you want http://forum.xda-developers.com/showthread.php?t=1690919
Msor people here used it including myself. I used it with the older version. But the dev is a cool dude. He'll help ya in any way he can.
Sent Blazing w/ Viper4G
Click to expand...
Click to collapse
Ah good to know.
So it works fine for partial ROOT - so you can flash ROMs etc?
Thanks.
ronnienyc said:
Ah good to know.
So it works fine for partial ROOT - so you can flash ROMs etc?
Thanks.
Click to expand...
Click to collapse
Yes this will set you up to do all that. . Best part is, that it wont report to HTC that you Unlocked your bootloader. The conventional way would report it to HTC and void your warranty. It will also ssh TWRP recovery and install SU and busy box. Please, just make sure you read the directions thoroughly. Make sure u have e the correct drivers and such. About e the directions you'll see all the requirements before running the MOD. Any troubles, just post your questions there. Rega's awesome. After you'll be all set to flash ROMs and such. There are a couple of limitations without S-Off but it doesn't sound like you wanna go to far.
Sent Blazing w/ Viper4G
Yes, I have used Rega's tool on other phones in the past. I just didn't know this was available for this 651.3 version on this phone.
Just started using the Evo LTE about a week ago, and I am hoping to instsall Mean ROM to make it a little more responsive
Also, my phone already says "TAMPERED."
Is there any way to get rid of that?
reverepats said:
Yes this will set you up to do all that. . Best part is, that it wont report to HTC that you Unlocked your bootloader. The conventional way would report it to HTC and void your warranty. It will also ssh TWRP recovery and install SU and busy box. Please, just make sure you read the directions thoroughly. Make sure u have e the correct drivers and such. About e the directions you'll see all the requirements before running the MOD. Any troubles, just post your questions there. Rega's awesome. After you'll be all set to flash ROMs and such. There are a couple of limitations without S-Off but it doesn't sound like you wanna go to far.
Sent Blazing w/ Viper4G
Click to expand...
Click to collapse
Im pretty new to android so forgive me, but im looking to unlock and root using this method but i see it uses htcdev.com.
am i incorrect in saying that going with htcdev.com method my warrant WILL be voided? or am i missing sumthing.
eddy0090 said:
Im pretty new to android so forgive me, but im looking to unlock and root using this method but i see it uses htcdev.com.
am i incorrect in saying that going with htcdev.com method my warrant WILL be voided? or am i missing sumthing.
Click to expand...
Click to collapse
Normally with HTCDev, you're giving them your personal information, like your name, in exchange for the unlock key. With Regaw's method, it randomizes one of a hundred names, so they never actually have your specific info on file.
fachadick said:
Normally with HTCDev, you're giving them your personal information, like your name, in exchange for the unlock key. With Regaw's method, it randomizes one of a hundred names, so they never actually have your specific info on file.
Click to expand...
Click to collapse
gotcha. thanks. one more dumb question, not really sure what s-on s-off is. and do i need to be s-off if i want to flash custom roms?
thanks again this community kicks a$$!
eddy0090 said:
gotcha. thanks. one more dumb question, not really sure what s-on s-off is. and do i need to be s-off if i want to flash custom roms?
thanks again this community kicks a$$!
Click to expand...
Click to collapse
To answer the easier question first, no, you don't have to be s-off to flash roms.
As to what it is and what it means, once you go to Regaw's thread, hit his name, go to his stats, and check out the link of threads that he's started. He did a pretty good write up on what s-off is, and what it means.
fachadick said:
To answer the easier question first, no, you don't have to be s-off to flash roms.
As to what it is and what it means, once you go to Regaw's thread, hit his name, go to his stats, and check out the link of threads that he's started. He did a pretty good write up on what s-off is, and what it means.
Click to expand...
Click to collapse
will do thanks much!
fachadick said:
Normally with HTCDev, you're giving them your personal information, like your name, in exchange for the unlock key. With Regaw's method, it randomizes one of a hundred names, so they never actually have your specific info on file.
Click to expand...
Click to collapse
I've not utilized this process, so I'm speaking from a position of ignorance. But, regardless of the name used, etc., it would seem to me that ANY method utilized will provided the IMEI/Serial # of the handset. This said, HTC will have a record that the phone was unlocked, and would still certainly have an ability to say it is not eligible for certain warranty claims.
Am I incorrect?
Joel
jbhorner said:
I've not utilized this process, so I'm speaking from a position of ignorance. But, regardless of the name used, etc., it would seem to me that ANY method utilized will provided the IMEI/Serial # of the handset. This said, HTC will have a record that the phone was unlocked, and would still certainly have an ability to say it is not eligible for certain warranty claims.
Am I incorrect?
Joel
Click to expand...
Click to collapse
no, you're not incorrect - HTC will have the devices information on file as part of the token, but they will not have your name and registration information. This does not prove that the phone was unlocked, only that the unlock information was requested for your phone. As an fyi also, the fine print states that htc specific warranty may be voided by unlocking, not that it will be.
jbhorner said:
I've not utilized this process, so I'm speaking from a position of ignorance. But, regardless of the name used, etc., it would seem to me that ANY method utilized will provided the IMEI/Serial # of the handset. This said, HTC will have a record that the phone was unlocked, and would still certainly have an ability to say it is not eligible for certain warranty claims.
Am I incorrect?
Joel
Click to expand...
Click to collapse
They will only have a record that you REQUESTED an unlock code. There is no way they can prove that you actually USED it, unless your device obviously says "UNLOCKED" or "RELOCKED" in the bootloader (which it invariably will until S-OFF is achieved for the new HBOOT).
Besides the fact that no one ever sends their device back to HTC for service, so it's not typically relevant anyway.
EDIT: Also see above
Captain_Throwback said:
Besides the fact that no one ever sends their device back to HTC for service, so it's not typically relevant anyway.
Click to expand...
Click to collapse
I just did. Sprint only has a 15 day warranty on phones now (unless you purchase the insurance.) And mine was a couple months old, with a borked antenna and dropping calls. So it is off to HTC for a warranty repair/replacement.
ronnienyc said:
I just did. Sprint only has a 15 day warranty on phones now (unless you purchase the insurance.) And mine was a couple months old, with a borked antenna and dropping calls. So it is off to HTC for a warranty repair/replacement.
Click to expand...
Click to collapse
I guess if you don't want to pay Sprint the $35 to have them fix it, then yes, you'd have to send it back to HTC, but if they determine there's nothing wrong with the phone, they just send it back to you unfixed, and at your expense. That's why I'm going to try and never send anything back to them .
reverepats I never took any credit it was not brought up on AC before so I was just trying to help people out because there was a lot of threads of people asking how to root the new update so i dont get why your mad about this? Far as being a word for word copy it was not so dont go there some things may be close but I put up a link to his thread and gave credit

[PSA]Public Service Announcement!!!!

Greetings! I hope you are having a fine day!
I am writing this to try to alleviate future issues for some of you.
Sunday night, I posted instructions for installing a certain update manually. Now, I am S-Off, and just assumed when I wrote it that anybody else flashing stuff like that would be too. This was apparently my mistake.
So in an effort to try to prevent future problems I am writing this, and hoping many of you will read it, and pay attention. Although I know that usually doesn't happen.
So, here we go:
If you are planning to manually flash anything other than a ROM, you should be S-Off. There is no excuse not to be, and no reason you shouldn't do it.
First, it's completely reversible. Second, it removes the "Unlocked" message from your phone.
It prevents the mainver older issue.
It lets you pretty much flash anything you want, whenever you want, as long as the phone is physically able. This means, if you flash something and it goes wrong, you can flash backwards to what you had before.
After S-Off, you DO NOT HAVE TO UNLOCK!!!!!! I cannot say this enough. S-Off is a step beyond unlocking. This is why we do it!
Reverting to S-On is as simple as flashing a full, released, OTA RUU and issuing a fastboot command to change the flag. Although the only reason I could see to do that is to return the phone.
If you aren't sure that a set of directions apply to you, ask first!
If you are following the directions, and something goes wrong, STOP!!!!!! Do not guess what to do, or try to go backwards unless you know for a fact it will work. Go online and ask for help. If you ask properly, somebody will help you. Some people live for the chance to help others.
When asking for help, say what you had before you started, what you were trying to do (with a link), what step you were on, and what the unexpected result was. POST THE EXACT MESSAGES!!!! Not an abbreviated version.
If a post does not specify that you need to be S-Off, read through the instructions before you start. If you see anything to do with a PH98IMG.zip file, or going into HBOOT, assume you should S-Off first. Simply to be safe.
I know this was all disjointed, but I was simply posting my responses to issues I see all too often that could easily have been avoided, or resolved much easier.
So, to sum up.
S-Off Your Phone!
Thank you!
D
.​
dsb9938 said:
So, to sum up.
S-Off Your Phone!
Thank you!
D
.​
Click to expand...
Click to collapse
Exactly. Plus educate yourself.
Sent from my ADR6425LVW using Tapatalk 2
also, to add on, if you want to revert to s-on, RUN AN RUU FIRST!!!!!! it will brick your phone if you s-on on a modified/unsigned hboot!! although it is reversible (as i did tonight...derp) it was annoying. also if you want a guide on how to unbrick a rezound bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device, i will gladly do it, all props to meadows btw
Thanks for the write up.
To be honest I am not sure what to do to update my firmware from that 100mb ota after reading that thread several times. Or if I even need to if I don't have a use for the gsm stuff. I am s-off though.
Edit: I forgot to mention, I am running ics firmware on the viper rom.
If I were a dev, I wouldn't include any options for s-on. It's simple to do, safe enough, and not scary at all.... It makes everyone's life much easier.
Nice thread, dsb9938, and right on point. Problem is, nobody reads. Nobody looks at the threads above and nobody searches. Alright, not nobody, but not enough people. The way I see it, if you are going to take the responsibility for manipulating the innards of your $200 handset, the least you could do is poke around for the right way to do things before just messing around and thinking Dad will buy you a new handset when you bork it. This Dad won't.
XDA is for people who take responsibility. If you can't handle that, please go play in someone else's sandbox.
If I had a dollar for every post in another current thread here that reflects users not reading posts only a page above, not checking stickies first, not using the search function, or just plain trolling, I could buy several Rezounds just to mess with and still have money left over for a Nexus 7.
/end rant
Sent into the innertubes from my Arnova 10 G2.
hgoldner said:
Nice thread, dsb9938, and right on point. Problem is, nobody reads. Nobody looks at the threads above and nobody searches. Alright, not nobody, but not enough people. The way I see it, if you are going to take the responsibility for manipulating the innards of your $200 handset, the least you could do is poke around for the right way to do things before just messing around and thinking Dad will buy you a new handset when you bork it. This Dad won't.
XDA is for people who take responsibility. If you can't handle that, please go play in someone else's sandbox.
If I had a dollar for every post in another current thread here that reflects users not reading posts only a page above, not checking stickies first, not using the search function, or just plain trolling, I could buy several Rezounds just to mess with and still have money left over for a Nexus 7.
/end rant
Sent into the innertubes from my Arnova 10 G2.
Click to expand...
Click to collapse
While everything you said is true, people just need to be nicer to each other. We are all here to help each other, no need to be mean about it. :highfive:
antp121 said:
also, to add on, if you want to revert to s-on, RUN AN RUU FIRST!!!!!! it will brick your phone if you s-on on a modified/unsigned hboot!! although it is reversible (as i did tonight...derp) it was annoying. also if you want a guide on how to unbrick a rezound bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device, i will gladly do it, all props to meadows btw
Click to expand...
Click to collapse
Lol that's in giant font on the s-off tutorial.
Yet you still failed.
Sent from my NeoMax Rezound
wlmeng11 said:
Lol that's in giant font on the s-off tutorial.
Yet you still failed.
Sent from my NeoMax Rezound
Click to expand...
Click to collapse
I ruu'd that morning. I was playing mw3 and I completely spaced. It's all good now so does it matter?
Sent from my ADR6425LVW using Tapatalk 2
OK so im s-off do i need to "fastboot oem lock" before updating to the latest RUU????
synisterwolf said:
OK so im s-off do i need to "fastboot oem lock" before updating to the latest RUU????
Click to expand...
Click to collapse
It kills me when people actually have no idea about things like that. I mean that's just common knowledge and could be found with a 5 minute Google search
AshtonTS said:
It kills me when people actually have no idea about things like that. I mean that's just common knowledge and could be found with a 5 minute Google search
Click to expand...
Click to collapse
Google?
Sent from my iPhone...
86shelby said:
If I were a dev, I wouldn't include any options for s-on. It's simple to do, safe enough, and not scary at all.... It makes everyone's life much easier.
Click to expand...
Click to collapse
With all due respect alienating any portion of your user base is generally not good. I'm not s-off but it's only because I haven't been around a pc that's got an internet connection. I appreciate how easy it is but there are still those of us that have life situations that haven't allowed for the whole process yet.
Sent from my ADR6425LVW using xda premium
Geoi1006 said:
With all due respect alienating any portion of your user base is generally not good. I'm not s-off but it's only because I haven't been around a pc that's got an internet connection. I appreciate how easy it is but there are still those of us that have life situations that haven't allowed for the whole process yet.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
You could download the stuff to your phone and transfer it via USB to your computer, or you could use tethering.
It's called being resourceful
I see you talking but all I'm seeing is talking down to people. Trying to decide where the constructive portion of this thread is.
Sent from my ADR6425LVW using xda premium
I agree more people need to read and remember the rules and posts like this as well. Thank you for posting this, however i do disagree with one thing. I recently upgraded my firmware to the ICS update OTA(not the ICS update itself but the update that was pushed shortly after) which updated my hboot to 2.27, Locked. All is fine until I needed to flash a boot.img because of boot manager. No big deal until I get a "remote not allowed" return on a fastboot flash boot boot.img command. For some reason I can not for the life of me create a flashable zip to be flashed in recovery, and I'm too lazy to take my sdcard out to put a PH98IMG.ZIP file on there to flash boot.img in bootloader. So I had to unlock my bootloader to perform the fastboot command needed to get my phone back. Until there is a patched hboot 2.27, you will need to unlock your bootloader, or downgrade to jb_hboot. Just my 2 cents...
Great post. Thanks for writing it up.
I tried numerous times to get s off, and it just didnt work for me. I dont have a land line or a spare phone so I am very dependant on my phone. I can't have it in non working phone.
I appreciate all the work the drvs do and all the people who help us out to make our phones top notch. However, I do like how the devs have s on and s off roms
I don't S-Off because brickings are always possible when S-Off, and S-On hasn't really inconvenienced me.
AshtonTS said:
You could download the stuff to your phone and transfer it via USB to your computer, or you could use tethering.
It's called being resourceful
Click to expand...
Click to collapse
Geoi1006 said:
I see you talking but all I'm seeing is talking down to people. Trying to decide where the constructive portion of this thread is.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
That's definitely talking down to people. It's a big wave of arrogance emitting from this thread. Keep in mind a lot of these dudes are young Btw.
Sent from my ADR6425LVW using xda premium
scy1192 said:
I don't S-Off because brickings are always possible when S-Off, and S-On hasn't really inconvenienced me.
Click to expand...
Click to collapse
Actually, bricking your phone, as unlikely as that is, is less likely when s-off since there are more options to recovery if you mess up.
D
.

Interesting Find About The Bootloader???

Hello, I have been scouring the internet for ways to help people unlock their Motorola Photon 4G that had the newest soak update which was 2.3.5 from Motorola directly. I admit, I didn't find jack and they say it's impossible... So I gave up searching and went into my think tank.
I did recently hear that Motorola gave the XOOM users the ability to unlock the bootloader via the internet or using some sort of software just like HTC did. Well, what if we did this.
We found a way to port the XOOM's OS, in that case which is ICS and then matched up the version information for the XOOM and made it available on our Photon 4G? Like we could somehow change the information and make our Photon's be recognized as a XOOM?
I can't guarantee this will some how magically free up our Photon from the dreaded bootloader lock. I am not near in developmental stage but maybe this kind of information will get us users free from this hassle once and for all. Using the XOOM bootloader unlock maybe somehow we can figure out what kind of information that software uses to identify the XOOM as a REAL XOOM. The real questions what I really have below:
1. Does it use a certain encryption or special keys?
2. Does it only see the software version?
3. Does it recognize a certain type of hardware chip?
4. Is it software or hardware type lock?
I mean we can do this, we have tons of users already with unlocked bootloaders and it sounds like to meet it is a software issue. We install an update from Motorola and bam... No more unlocked bootloader.
I mean we already know how to create kernels, custom roms, recoveries. Why not try this? What do we have to lose?
Thanks guys,
- JWT
Very interesting. I wish you the best of luck.
Sent from my MB855 using xda premium
R2DeeTard said:
Very interesting. I wish you the best of luck.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Thanks, I might try it later on when I start building my own custom ROMs for the Photon.
To answer your first question I'm pretty sure Motorola somehow sends you a special key. I think I read that somewhere.
Sent from my MB855 using xda app-developers app
FC809 said:
To answer your first question I'm pretty sure Motorola somehow sends you a special key. I think I read that somewhere.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
If we can somehow change and/or decrypt that key, we can use a 2.3.4 SBF.
JustWorksTechnology said:
If we can somehow change and/or decrypt that key, we can use a 2.3.4 SBF.
Click to expand...
Click to collapse
The only thing is I think your suppose to give your device ID, and then Motorola will send you a specific key for your phone (maybe). Something I found funny off the unlocking page.
WARNING: Motorola strongly recommends against unlocking the bootloader and/or modifying or altering a device's software or operating system. Doing so can have unintended, unforeseen, and dangerous consequences, such as rendering the device unusable, violating applicable laws, or causing property damage and/or bodily injury, including death.
Apparently you can die from unlocking your bootloader lol.
FC809 said:
The only thing is I think your suppose to give your device ID, and then Motorola will send you a specific key for your phone (maybe). Something I found funny off the unlocking page.
WARNING: Motorola strongly recommends against unlocking the bootloader and/or modifying or altering a device's software or operating system. Doing so can have unintended, unforeseen, and dangerous consequences, such as rendering the device unusable, violating applicable laws, or causing property damage and/or bodily injury, including death.
Apparently you can die from unlocking your bootloader lol.
Click to expand...
Click to collapse
We maybe then can try to incorporate that key into our bootloader somehow and then Motorola will see that we have a "fake XOOM". This is really interesting!
I hope one of you geniuses find a way to do it if it's possible.
Sent from my MB855 using xda app-developers app
FC809 said:
I hope one of you geniuses find a way to do it if it's possible.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
LOL I hope I can possibly be the first... Like I said, I am no where never becoming a developer but I am pretty bright at least I would say so myself. I fixed my first computer at the age of 15
Hey man your ahead of me. I don't even know all of the parts that make up a computer, and I'm about to start my first year of getting my degree in software engineering lol.
Sent from my MB855 using xda app-developers app
JustWorksTechnology said:
Hello, I have been scouring the internet for ways to help people unlock their Motorola Photon 4G that had the newest soak update which was 2.3.5 from Motorola directly. I admit, I didn't find jack and they say it's impossible... So I gave up searching and went into my think tank.
I did recently hear that Motorola gave the XOOM users the ability to unlock the bootloader via the internet or using some sort of software just like HTC did. Well, what if we did this.
We found a way to port the XOOM's OS, in that case which is ICS and then matched up the version information for the XOOM and made it available on our Photon 4G? Like we could somehow change the information and make our Photon's be recognized as a XOOM?
I can't guarantee this will some how magically free up our Photon from the dreaded bootloader lock. I am not near in developmental stage but maybe this kind of information will get us users free from this hassle once and for all. Using the XOOM bootloader unlock maybe somehow we can figure out what kind of information that software uses to identify the XOOM as a REAL XOOM. The real questions what I really have below:
1. Does it use a certain encryption or special keys?
2. Does it only see the software version?
3. Does it recognize a certain type of hardware chip?
4. Is it software or hardware type lock?
I mean we can do this, we have tons of users already with unlocked bootloaders and it sounds like to meet it is a software issue. We install an update from Motorola and bam... No more unlocked bootloader.
I mean we already know how to create kernels, custom roms, recoveries. Why not try this? What do we have to lose?
Thanks guys,
- JWT
Click to expand...
Click to collapse
the xoom is a nexus device, fastboot oem unlock does the trick, no special software needed.
the bootloader has to have the software to support this not just the tool. what that means is unless you plan on flashing the xoom bootloader (please dont do that) then your bypass for teh xoom isnt gunna mean anything. i could set the version strings and build.prop info all day long to whatever i wanted doesnt make my phone anything but a gnexus.
in order to get the token you have to enter your device key, i assure you they are gunna have a database so you cant just make one up. at which point the code they give you is only gunna match up with the device its paired to.
you wanna see if moto has any plans for photon officially any new updates (including the 2.3.5) try running fastboot oem get_unlock_data while in fastboot mode and see if you get an output. you do then there is a pretty damn good chance they are planning on adding support.
shabbypenguin said:
the xoom is a nexus device, fastboot oem unlock does the trick, no special software needed.
the bootloader has to have the software to support this not just the tool. what that means is unless you plan on flashing the xoom bootloader (please dont do that) then your bypass for teh xoom isnt gunna mean anything. i could set the version strings and build.prop info all day long to whatever i wanted doesnt make my phone anything but a gnexus.
in order to get the token you have to enter your device key, i assure you they are gunna have a database so you cant just make one up. at which point the code they give you is only gunna match up with the device its paired to.
you wanna see if moto has any plans for photon officially any new updates (including the 2.3.5) try running fastboot oem get_unlock_data while in fastboot mode and see if you get an output. you do then there is a pretty damn good chance they are planning on adding support.
Click to expand...
Click to collapse
Good point Shabbypenguin, but the whole point was missing. I wasn't planning on flashing the XOOM's bootloader but to imitate the XOOM's bootloader by somehow injecting a the token associated with the XOOM and their databases into our current bootloader... Either by an SBF flash with the current soak ota update.
Look I think moto is ready to release the tool to open the boot loader
h t t p s://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a

Rooting really annoying

Hello!
I have a htc evo 3d. With warranty and I don't want to loose it in any way because I want to root it.
The thing is... Why do you guys make it so complicated? Why are there so many steps they are not explained too well (put the files into c:/android --- which files, and why don't I have a c:android directory) I just cant work like this. Someone would say, google it... I have a life, I don't want to google every single thing I don't understand.
I rooted a nexus with ease, this is just insane.
Sorry, im just not impressed, tried to root it a lot of times, it always ended me loosing my temper. Worst manufacturer for unlocking. Allready unlocked a psp, a samsung, asus, ps3, wii...but this is just stupid..
Anyone wanna help me out? Give me a link to a good tutorial?
Or just let me dump the phone?
Thanks...
AW: Rooting really annoying
This is what q&a forum stands for...
Anyway:
If you only want root, the easiest way would be to follow the htcdev.com instructions to unlock the bootloader and flash a custom recovery afterwards. Then just flash a superuser.zip and you're done
(A+B from first link)
To avoid problems with flashing roms it might be useful to s-off your phone so that you can change your hboot
1 option is the wire trick (a,b,d )
http://forum.xda-developers.com/showthread.php?t=1743466
or follow this thread:
http://forum.xda-developers.com/showthread.php?t=2124142
Edit thread reported because of wrong forum
Will most likely move to q/a soon, just to let you know
Quantenhall said:
This is what q&a forum stands for...
Anyway:
If you only want root, the easiest way would be to follow the htcdev.com instructions to unlock the bootloader and flash a custom recovery afterwards. Then just flash a superuser.zip and you're done
(A+B from first link)
To avoid problems with flashing roms it might be useful to s-off your phone so that you can change your hboot
1 option is the wire trick (a,b,d )
http://forum.xda-developers.com/showthread.php?t=1743466
or follow this thread:
http://forum.xda-developers.com/showthread.php?t=2124142
Click to expand...
Click to collapse
And I can later unroot it and put it back to normal if there will be a hardware fail so I can send it to sevice?
Thanks for the links and stuff
AW: Rooting really annoying
If your phone is still working
http://forum.xda-developers.com/showthread.php?t=2136964
(If you did the s-off steps)
If you used htcdev they will always know that you unlocked your phone, but that seems to be worse than it actually is:
If you are not sending your phone to HTC directly, but to where you buyed it, they will most likely not look for that
If your phone is completely broken they can't proof that it was your fault (or they dont do it because its too much work) and if there are issues that have nothing to do with rooting, etc like a broken screen or similar they still have to repair it with warranty
(That's what I believe,but it might be difficult in some cases and different in some countries)
Quantenhall said:
If your phone is still working
http://forum.xda-developers.com/showthread.php?t=2136964
(If you did the s-off steps)
If you used htcdev they will always know that you unlocked your phone, but that seems to be worse than it actually is:
If you are not sending your phone to HTC directly, but to where you buyed it, they will most likely not look for that
If your phone is completely broken they can't proof that it was your fault (or they dont do it because its too much work) and if there are issues that have nothing to do with rooting, etc like a broken screen or similar they still have to repair it with warranty
(That's what I believe,but it might be difficult in some cases and different in some countries)
Click to expand...
Click to collapse
Well that is a problem... :S
If I send my phone, I send it to my mobile provider, then they send it to a authorised htc servicer...
I really don't care if I loose it, IF the phone would work like it should (this is my 2nd evo, the fist one visited the service 7 times, and the new ones 3D isnt working... :S )
Im gonna call them tomorrow and ask them how is it with the unlock...
Do I have to do the s-off?
I just want a stock android because sense is slow...
Maybe a link to a really simple android 4.0 + ?
AW: Rooting really annoying
No rom discussions on xda/evo forum, sry :/
The most used jb roms should be the ones from johnnyslt(cm10.1), helicopter88 (several aosp roms) and agrabren (4.1 , a bit outdated)
For 3d cam you have to use a sense rom
The gsm forum is full of roms, try them yourself
Without s-off some ROMs/kernel can make problems and you need it to change your hboot
This is needed because with some hboots (1.53 for example) you can't use ROMs that are not based on sense 3/3.6 (+viper afaik)
mrsofa said:
Hello!
I have a htc evo 3d. With warranty and I don't want to loose it in any way because I want to root it.
The thing is... Why do you guys make it so complicated? Why are there so many steps they are not explained too well (put the files into c:/android --- which files, and why don't I have a c:android directory) I just cant work like this. Someone would say, google it... I have a life, I don't want to google every single thing I don't understand.
I rooted a nexus with ease, this is just insane.
Sorry, im just not impressed, tried to root it a lot of times, it always ended me loosing my temper. Worst manufacturer for unlocking. Allready unlocked a psp, a samsung, asus, ps3, wii...but this is just stupid..
Anyone wanna help me out? Give me a link to a good tutorial?
Or just let me dump the phone?
Thanks...
Click to expand...
Click to collapse
I have a htc evo 3d. With warranty and I don't want to loose it in any way because I want to root it.
Click to expand...
Click to collapse
Sorry, but just unlocking your phone destroys it's warranty. So if you want your warranty, don't unlock it and root it.
The thing is... Why do you guys make it so complicated? Why are there so many steps they are not explained too well (put the files into c:/android --- which files, and why don't I have a c:android directory)
Click to expand...
Click to collapse
You are supposed to download the Android SDK files, and then drop them into C:\Android, like it says, easy enough for a 6 year old to do it.
--
Also, it's complicating so idiots don't break their phones or get screwed over by giving complete access to the phone with a simple click of a button in an application.
'Blu said:
You are supposed to download the Android SDK files, and then drop them into C:\Android, like it says, easy enough for a 6 year old to do it.
--
Also, it's complicating so idiots don't break their phones or get screwed over by giving complete access to the phone with a simple click of a button in an application.
Click to expand...
Click to collapse
Noone said where to put it... it just said, like it is normal to have the android sdk installed...
And htc is probably the only phone that has this procces so long and confusing
Just confess that youre a htc fan boy and cant confess a single fail.
Why does samsung or asus have the unlocking process much easyer then? And why can I still get my warranty on them if I lock them back up? I can just say that htc is the worst phone ever...
mrsofa said:
Noone said where to put it... it just said, like it is normal to have the android sdk installed...
And htc is probably the only phone that has this procces so long and confusing
Just confess that youre a htc fan boy and cant confess a single fail.
Why does samsung or asus have the unlocking process much easyer then? And why can I still get my warranty on them if I lock them back up? I can just say that htc is the worst phone ever...
Click to expand...
Click to collapse
Lol, I'm not an HTC fanboy at all, you're just, well, dumb. All you're doing is whining about how HTC phones are "hard" (they're not... lol) and the fact that you clearly void your warranty like it says when you're unlocking the phone. Just because the company is actually smart and does things right, doesn't mean they're bad. It just means you can't cope with how things really are and want everything to be perfect and dandy, but you can't have things your way some times.
'Blu said:
Lol, I'm not an HTC fanboy at all, you're just, well, dumb. All you're doing is whining about how HTC phones are "hard" (they're not... lol) and the fact that you clearly void your warranty like it says when you're unlocking the phone. Just because the company is actually smart and does things right, doesn't mean they're bad. It just means you can't cope with how things really are and want everything to be perfect and dandy, but you can't have things your way some times.
Click to expand...
Click to collapse
Didn't lost the warranty on the samsung and asus. The end.
Are you even sure about what you are saying?
http://forum.xda-developers.com/showthread.php?t=1766475
Dont even start saying that with a htc you can do it faster. This is a toolkit, a couple of clicks and youre done.
mrsofa said:
Didn't lost the warranty on the samsung and asus. The end.
Are you even sure about what you are saying?
http://forum.xda-developers.com/showthread.php?t=1766475
Dont even start saying that with a htc you can do it faster. This is a toolkit, a couple of clicks and youre done.
Click to expand...
Click to collapse
Well, I'm not going to bother with you at all . You're pretty arrogant for trying to keep the thought of all phones being the same. HTC is their own brand, they make their phones how they wish. If you're not smart enough to run a few lines in command prompt then don't keep trying because it looks like you're not even willing to try it out. I can tell you right now, that unlocking your phone is so simple it's not even funny, you're just not looking into it and worrying about it being easy.
'Blu said:
Well, I'm not going to bother with you at all . You're pretty arrogant for trying to keep the thought of all phones being the same. HTC is their own brand, they make their phones how they wish. If you're not smart enough to run a few lines in command prompt then don't keep trying because it looks like you're not even willing to try it out. I can tell you right now, that unlocking your phone is so simple it's not even funny, you're just not looking into it and worrying about it being easy.
Click to expand...
Click to collapse
Nope. Why make so many steps? Why waste half of my day for this? No thanks!
mrsofa said:
Nope. Why make so many steps? Why waste half of my day for this? No thanks!
Click to expand...
Click to collapse
Well, because that's how HTC wants it to be. Phones aren't simple anymore, get over that fact.
'Blu said:
Well, because that's how HTC wants it to be. Phones aren't simple anymore, get over that fact.
Click to expand...
Click to collapse
Htc isnt simple. Enogh now. Im gonna call htc service tomorow and find out how it goes...
mrsofa said:
Didn't lost the warranty on the samsung and asus. The end.
Are you even sure about what you are saying?
http://forum.xda-developers.com/showthread.php?t=1766475
Dont even start saying that with a htc you can do it faster. This is a toolkit, a couple of clicks and youre done.
Click to expand...
Click to collapse
No offense, but thats a nexus. It doesnot matter who manufactures the Nexus device, they all are so easy to unlock. Even if HTC makes one it would be easier....
and the methods change from one device to another even if they are from same manufacturer (if you are doing it the unofficial way ofc)
hey... plain and simple if you don't want to loose your warranty. LEAVE IT ALONE!. I have 3 HTC phones all unlocked, rooted and running custom roms. to me it was easy! i just read everything i could to make sure i understood. i watched videos and just did it. to me it sound like you are just scared (which is ok) but just leave it alone if it is that big of a deal!
jaredl45600 said:
hey... plain and simple if you don't want to loose your warranty. LEAVE IT ALONE!. I have 3 HTC phones all unlocked, rooted and running custom roms. to me it was easy! i just read everything i could to make sure i understood. i watched videos and just did it. to me it sound like you are just scared (which is ok) but just leave it alone if it is that big of a deal!
Click to expand...
Click to collapse
Yes im scared, when I see something and dont understand it...i just cant go like : wgatevery, lets try like this...
Anyway... called tge service, I loose warranty if I unlock it, but if I lock it back when the device needs service then its not a problem
My strategy, I read everything I can 3 times before I try it. I also read every problem and read the solutions so I know how to fix it. Once you do it, you will say, that was easy. Once you actually understand what every step does and means, your brain will capture the info easier and it will make sense. An remember, if you break it, chances are someone else has a fix for what you did because they did the same thing.
Sent from my PG86100 using xda premium
Tried with this: http://www.youtube.com/watch?v=eNoL_EPJH9I
I sent the code to htc, and got a unlock code and get this error:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
What? What?
There are like 5 steps. Don't tell me to try again, done it 5 times already.
Using win8 is this a problem?
You must be to stupid to follow the guides. I would say. Stop asking for help on rooting your evo. And stop talking sh*@ about the procces. Go and buy and buy an iphone they have jaibreak guide for dummies.
Sent from my PG86100 using XDA Premium App

Categories

Resources