Related
I did not create "it", but the unlock tool is here: link
I am really looking forward to the first ROMs
I just saw that and not sure (afraid) to try it yet 'couse I just got mine TFP. It will break all agreement with ASUS.
Please post any results and experiences.
Nice
Sent from my Transformer Prime TF201 using xda premium
Anyone tried it yet? Lol.
mutiny said:
Anyone tried it yet? Lol.
Click to expand...
Click to collapse
and what do you think?
allready running with unlocked bootloader
I just read the other threads (I should have before asking --lol) and I've come to the conclusion that right now, at least for me, it's not worth unlocking yet. Here are my reasons:
1. There are zero development on the Prime as of now, so why unlock besides to void warranty?
2. If you do unlock and knock-on-wood something happens to your Prime before we get CM9 or other roms, what do you do?
3. Unless you're a dev or someone who is fairly knowledgeable/confident in your rom-development skills, what are you going to do with your unlocked Prime?
Are there any advantages I'm missing? I'm not sure if anyone agrees with me, but that's how I feel right now. Note that I am not at all gun shy about dumping my warranty for the real good stuff. Like many here, all Android phones I've ever owned, including my entire family's Android phones and tablets (also my other tablet --a Xoom) are rooted with custom roms and recoveries.
I advised those who don't develop or don't know much about rooting to not try this. There are just too many "what-ifs" against this method. For example, what if someone comes up with a way to unlock that doesn't go through Asus? By some miracle, if that happens, everyone who uses Asus' unlock will have a very iffy device with no warranty coverage whatsoever. Just a thought.
mutiny said:
I just read the other threads (I should have before asking --lol) and I've come to the conclusion that right now, at least for me, it's not worth unlocking yet. Here are my reasons:
1. There are zero development on the Prime as of now, so why unlock besides to void warranty?
2. If you do unlock and knock-on-wood something happens to your Prime before we get CM9 or other roms, what do you do?
3. Unless you're a dev or someone who is fairly knowledgeable/confident in your rom-development skills, what are you going to do with your unlocked Prime?
Are there any advantages I'm missing? I'm not sure if anyone agrees with me, but that's how I feel right now. Note that I am not at all gun shy about dumping my warranty for the real good stuff. Like many here, all Android phones I've ever owned, including my entire family's Android phones and tablets (also my other tablet --a Xoom) are rooted with custom roms and recoveries.
I advised those who don't develop or don't know much about rooting to not try this. There are just too many "what-ifs" against this method. For example, what if someone comes up with a way to unlock that doesn't go through Asus? By some miracle, if that happens, everyone who uses Asus' unlock will have a very iffy device with no warranty coverage whatsoever. Just a thought.
Click to expand...
Click to collapse
Right this minute, it's not necessary to unlock. However, my guess is that in less than a day we'll have a ClockworkMod version for the prime and you will need an unlocked bootloader to utilize it. This will allow you to make a full backup of your device (stock) and have a good backup plan should you run into issues in the future with an OTA, etc. The roms will be coming very soon.
Video about it is here!
http://www.youtube.com/watch?v=YBY6GY8G5lg&hd=1&list=PLFA87501087653A16
I'm gonna do it! I want to install Ubuntu on mine. Please watch the video, and subscribe if you liked it!
CWM Recovery is already out too
http://forum.xda-developers.com/showthread.php?t=1510983
does anyon know yet what "SERVICES" they blocked with the unlock, i read somewhere a LOOOONG time ago that they were going to block certain services when they released the bootloader unlock
If I remeber correctly, you're not able to use google music with an unlocked bootloader, because of the DRM security.
Bart1981 said:
If I remeber correctly, you're not able to use google music with an unlocked bootloader, because of the DRM security.
Click to expand...
Click to collapse
I'm not sure about that since I use it on my Galaxy Nexus with an unlocked bootloader.
ASUS’s reason for locking the bootloader was simply to comply with DRM protected content. Which a fair response. Not really something many of really are interested in any ways with services like Netflix and Google Music though.
Click to expand...
Click to collapse
source
Not shure though if they mean with 'comply' if you're not able to use it anymore with an unlocked bootloader.
edit:
Here's some more info about unlocking the bootloader and the DRM content.
Regarding the bootloader, the reason we chose to lock it is due to content providers' requirement for DRM client devices to be as secure as possible. ASUS supports Google DRM in order to provide users with a high quality video rental experience. Also, based on our experience, users who choose to root their devices risk breaking the system completely. However, we know there is demand in the modding community to have an unlocked bootloader. Therefore, ASUS is developing an unlock tool for that community. Please do note that if you choose to unlock your device, the ASUS warranty will be void, and Google video rental will also be unavailable because the device will be no longer protected by security mechanism.
Click to expand...
Click to collapse
Bart1981 said:
If I remeber correctly, you're not able to use google music with an unlocked bootloader, because of the DRM security.
Click to expand...
Click to collapse
You can't use the movie rental service I know that but never heard anything about music
Does this wipe the tablet like when unlocking the nexus?
Sent from my Transformer Prime TF201 using Tapatalk
since some people don't do research
please before you start.. and if you have root
Code:
adb logcat > output.txt
when all **** is done, please upload it to a pastebin or send it to me in a private message..
p.s. you can do this when you have adb set up or in the terminal from the device itselve.
Cm9 is booted on the Device!
Now a little waiting for the custom roms and probably a proper dual boot solution with windows just for the hell of it. Things are looking great so far with CWR already a go. I love the devs here.
Asus delivers in the end. Cheers.
The obvious question that I haven't seen asked yet...will it be possible to develop a tool to lock your bootloader again? If the bootloader can be unlocked with an apk file, there should at least be hope to lock it again by reversing whatever the apk did.
With all the new hacks coming out, I wanted to know, has the bootloader been successfully unlocked? Is sum1 working on it?
NOpe
Umm,how come? forgive me,i really dont understand what the complication is.
xyancompgeek said:
Umm,how come? forgive me,i really dont understand what the complication is.
Click to expand...
Click to collapse
We've all been waiting patiently for you to come along and show us how it's done !!
he he he
+1
LOL........could sum1 give me a technical reason?
xyancompgeek said:
LOL........could sum1 give me a technical reason?
Click to expand...
Click to collapse
Could I politely suggest that you have a browse through the forum, there are many references to the "unlock bootloader" issue. have a read - very educational I found.
sure. only thing I've known is that sony has somehow locked the bootloader and nobody knows how to get into fastboot. but what do these terms mean?
xyancompgeek said:
sure. only thing I've known is that sony has somehow locked the bootloader and nobody knows how to get into fastboot. but what do these terms mean?
Click to expand...
Click to collapse
IF you don't know what those terms mean then why are you complaining that someone hasn't done the work that you yourself can't do????
TLR summary
- sony have locked this thing down super tight. If you want to know more, read up.
- this device has a small install base
- small number of users = even smaller number of devs to throw at a very difficult problem (compared to say samsung or even HTC or motorola devices)
hence.....
If you want the technical reasons for why the bootloader is locked, you need to really read up and understand everything about bootloaders. They are very complex, and very device-specific and therefore very difficult to unlock when a manufacturer specifically protects them. I don't think we even have a proper partition dump for the Tablet, so it will be quite some time before we see any development in that.
It's worth elaborating that there is no magical unlock() function built in to the bootloader. They are complex, they are poorly documented (outside of Sony) and they are not made to be unlocked by users. In the past, I've found Samsung's slightly easier to work with at this level, but they're still fiendishly difficult.
You only have to check out the code used in ASUS's bootloader unlocking tool they released a while ago to see how complex this can be without manufacturer support.
So I've spent all day reading a hundred threads and the only method I see of obtaining root access to the HTC Droid Incredible 4G is by using HTCDev or the "Toolkit" that basically uses HTCDev. However, when submitting my token to HTCDev, I get an Error Code 160, MID not allowed.
I just want root access ONE TIME so I can install con247's 3 button remap and access a couple of system files. Please help, anyone, anyone at all.
More than likely this is caused by not selecting the token correctly. You have to select the entire code or it errs like that. I think you are just missing some of it when you copy paste it.
*Madmoose* said:
More than likely this is caused by not selecting the token correctly. You have to select the entire code or it errs like that. I think you are just missing some of it when you copy paste it.
Click to expand...
Click to collapse
I've tried about 5 times. I'm entering it correctly. Here it is in fact:
<<<< Identifier Token Start >>>>
B2A05C7741C458F3D079579F8D3043DA
75EA84AE6220B297F6FF4587EC2F29F7
ADF287C3225041EA46F4667E8D8710D1
EE78461F6AD30D6FFFEF9857F3F8AD45
A61014878C282D6E177874A6765F2486
2EC06F9A84FD38A7272E3434BB90EAEA
AA83B56E590527D5D9CD47C8ADA27A23
2BF17D20C0E6C4888E2A6ABA7E6AF7DD
70B575F9B2DC94C5A1E1CFFE78ADEFF8
7C3FFB7A33324431CF04C14AB632CC95
746CE75814FE3F4F819C2467A68AA8B9
C1258F81CA11619631BD06199CC63BC6
E7321A78DFC681CC18E3BEFEC4D04451
16E9DEBC3E8D11E5C8A20D45B454835F
30C9E1F5DCEE5132CDAE812074067D56
FA13B210947BFFD5B9F112659ED0EE19
<<<<< Identifier Token End >>>>>
The response is:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 160.
Error Reason: MID Not Allowed.
Can someone just send me their Unlock_Code.bin by any chance? I've done a google search on this error code and it seems some people with the htc one x get the same thing. Something about the phone not being supported by Verizon or HTC for unlocking? If this is true Im curious how everyone else is able to get root access on the Incredible 4G? Because i'm pretty sure it's available only on Verizon in the US.
Unlock codes are unique to your phone. Someone else's would not work.
You wouldn't happen to have another phone plugged in would you? I have one I use at work that just plays music over speakers and I've run into issues with fastboot choosing the other phone.
*Madmoose* said:
Unlock codes are unique to your phone. Someone else's would not work.
You wouldn't happen to have another phone plugged in would you? I have one I use at work that just plays music over speakers and I've run into issues with fastboot choosing the other phone.
Click to expand...
Click to collapse
No, this is the only phone connected. And I've tried this about 10 additional times with no success. I've done both the exact directions on HTCDev and I've also used the "HTC Droid Incredible 4G Toolkit" that someone here has developed. Both give me tokens, and each time I enter the token, it fails out with the same error code.
I was able to get into HBOOT and then select "recovery" on the phone itself, however. Is it possible to apply the 3 button remap (http://forum.xda-developers.com/showthread.php?t=1758752) using this method, without any htcdev or root? If so I guess that'd be good enough for now. All I want to do is get rid of the stupid 3-button strip on the bottom of most apps. The 3 button remap replaces the "Recent Apps" with the menu button.
moelost said:
No, this is the only phone connected. And I've tried this about 10 additional times with no success. I've done both the exact directions on HTCDev and I've also used the "HTC Droid Incredible 4G Toolkit" that someone here has developed. Both give me tokens
Click to expand...
Click to collapse
Are they the same token?
PonsAsinorem said:
Are they the same token?
Click to expand...
Click to collapse
No. It provides a different token every time I run it. No matter what token I get and submit to htcdev, it fails. here is an article from someone regarding the same error they get with htc onex
well i cant post urls yet.. the article is here:
androidspin DOT COM /2012/05/04/att-htc-one-x-bootloader-gets-locked-up-and-says-no-root-for-you
moelost said:
No. It provides a different token every time I run it. No matter what token I get and submit to htcdev, it fails. here is an article from someone regarding the same error they get with htc onex
well i cant post urls yet.. the article is here:
androidspin DOT COM /2012/05/04/att-htc-one-x-bootloader-gets-locked-up-and-says-no-root-for-you
Click to expand...
Click to collapse
Sorry to but in but when i had both my hox's i used the same unlock_code.bin file and it allowed me to unlock it :/
Sent from my GT-N7000 using Tapatalk 2
Well i'm starting to become really desperate. The AT&T OneX folks seem to have found a workaround as they have the same issue with htcdev. I'm wondering if I could possibly do this method they explain here:
http://forum.xda-developers.com/showthread.php?t=1709424
and would it work for the Incredible 4G? They should be both running the newest version of Sense. But I have a feeling this would be a bad idea. Sigh.
Thought this was worth bringing over from the Screen Discoloration thread since *Madmoose* asked a very pertinent question:
*Madmoose* said:
Hehe, not to thread-jack but can you have them look into why people aren't able to unlock via the HTCDev tool any more
Click to expand...
Click to collapse
Urban Strata said:
Please expect an official statement from HTC on this tomorrow or Wednesday at the latest. Thanks!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
moelost said:
I've tried about 5 times. I'm entering it correctly. Here it is in fact:
<<<< Identifier Token Start >>>>
B2A05C7741C458F3D079579F8D3043DA
75EA84AE6220B297F6FF4587EC2F29F7
ADF287C3225041EA46F4667E8D8710D1
EE78461F6AD30D6FFFEF9857F3F8AD45
A61014878C282D6E177874A6765F2486
2EC06F9A84FD38A7272E3434BB90EAEA
AA83B56E590527D5D9CD47C8ADA27A23
2BF17D20C0E6C4888E2A6ABA7E6AF7DD
70B575F9B2DC94C5A1E1CFFE78ADEFF8
7C3FFB7A33324431CF04C14AB632CC95
746CE75814FE3F4F819C2467A68AA8B9
C1258F81CA11619631BD06199CC63BC6
E7321A78DFC681CC18E3BEFEC4D04451
16E9DEBC3E8D11E5C8A20D45B454835F
30C9E1F5DCEE5132CDAE812074067D56
FA13B210947BFFD5B9F112659ED0EE19
<<<<< Identifier Token End >>>>>
The response is:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 160.
Error Reason: MID Not Allowed.
Can someone just send me their Unlock_Code.bin by any chance? I've done a google search on this error code and it seems some people with the htc one x get the same thing. Something about the phone not being supported by Verizon or HTC for unlocking? If this is true Im curious how everyone else is able to get root access on the Incredible 4G? Because i'm pretty sure it's available only on Verizon in the US.
Click to expand...
Click to collapse
the identifier token on the top should not be submitted, and the one at the bottom, just the numbers and letters in the code
Aldo101t said:
the identifier token on the top should not be submitted, and the one at the bottom, just the numbers and letters in the code
Click to expand...
Click to collapse
Actually, you're supposed to include the <<< >>> lines as well
*Madmoose* said:
Actually, you're supposed to include the <<< >>> lines as well
Click to expand...
Click to collapse
ok, i've never submitted that, but who know's.
They might be blocking it now
I hope they aren't but they might be.
con247 said:
They might be blocking it now
I hope they aren't but they might be.
Click to expand...
Click to collapse
it looks like they are...i think there have been similar situations where a device "worked" just using other supported devices for awhile, until that was blocked
and then typically *support* comes at a later date (which is crap)
id like to be hopeful for an soff solution like lazypanda, but theres no way to ask them to work on the inc 4g, since they dont allow those questions in their irc
dbrits said:
Thought this was worth bringing over from the Screen Discoloration thread since *Madmoose* asked a very pertinent question:
Click to expand...
Click to collapse
Wow. Thanks! I sure hope there is some good news regarding this. Crossing fingers.
con247 said:
They might be blocking it now
I hope they aren't but they might be.
Click to expand...
Click to collapse
Hey con! You told me I had some reading to do and you'd be surprised how much I've learned over the last two days.Thanks for getting me started. I was probably about one or two days too late in trying to root this thing; they probably JUST started blocking it.
So the OneX guys found a workaround, someone created a root.bat that roots the phone without the need for HTCdev. Is this something that can be applied or created for the Inc4G? I have a feeling this will be the only solution soon.
moelost said:
Hey con! You told me I had some reading to do and you'd be surprised how much I've learned over the last two days.Thanks for getting me started. I was probably about one or two days too late in trying to root this thing; they probably JUST started blocking it.
So the OneX guys found a workaround, someone created a root.bat that roots the phone without the need for HTCdev. Is this something that can be applied or created for the Inc4G? I have a feeling this will be the only solution soon.
Click to expand...
Click to collapse
Right now he doesn't have our phone. But should have it by tomorrow. Give him some time to give it the "once-over". Hopefully he can come up with a solution that will work. Don't really think he can answer your question until he has the phone in front of him.
Well I got a pretty nonsense reply from HTC support today regarding the htcdev error issue.
In regards to this device this device is fairly new and is not yet supported by the dev site. I apologize but I do not have a ETA as to when that would be available to be a supported device. What I would suggest would be to keep checking back and when this becomes a option it will be posted there.
Click to expand...
Click to collapse
Yeah, which is nonsense because it obviously worked for everyone before.
moelost said:
Well I got a pretty nonsense reply from HTC support today regarding the htcdev error issue.
Yeah, which is nonsense because it obviously worked for everyone before.
Click to expand...
Click to collapse
I honestly think the tool was made available by HTC and Verizon told em to pull it. Now they are kind of handcuffed by Verizon. That's why it was available and now it isn't. But the last thing HTC wants to do is piss Verizon off, so they are preparing a public statement that doesn't point fingers. But I doubt this tool will be made available any time soon. We have some peeps looking into unlocking it without the HTC tool. Have patience, it'll come.
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.
I want to unlock the bootloader of my G5, but I am scared a bit of voiding my warranty if some problems come up in future (it's only been a bit more than 24 hours with G5). I've heard of unofficial way of getting the unlock code and I've heard stories of people relocking their bootloaders, but I am not sure.
So, if and how can I relock H850 bootloader?
And where can I find that unofficial way of unlocking it? (I know that it costs some money. However, google didn't help me.)
ashirviskas said:
I want to unlock the bootloader of my G5, but I am scared a bit of voiding my warranty if some problems come up in future (it's only been a bit more than 24 hours with G5). I've heard of unofficial way of getting the unlock code and I've heard stories of people relocking their bootloaders, but I am not sure.
So, if and how can I relock H850 bootloader?
And where can I find that unofficial way of unlocking it? (I know that it costs some money. However, google didn't help me.)
Click to expand...
Click to collapse
There is no unofficially way to unlock the bootloader, when You ask for the unlock.bin to LG the warranty you'll lose the warranty, so even if You relock it (which is possible) LG will anyway know trough the device id and the imei which Smartphone are locked and which are not.
They cannot void your warranty just based on the fact you requested the unlock.bin
As for how to unlock there is plenty of information about it in threads here, just read it. As for an unofficial way of unlocking - the fact that you couldn't find anything in google leads me to believe it either does not exist or is a recent discovery in which case I'd wait since it will find its way here sooner or later once it's validated.
I remember browsing through reddit and xda three days ago and in some thread people were discussing the ways of unlocking G5. One person said that if official way doesn't work (because only h850 is supported on LG website), you can buy unlock *stuff* (file or code, I don't remember) on this other website for 1.99 or 0.99. Others said they will try and after trying they were really happy because it worked.
I'm not sure where it was, but I think it was on XDA. Could it have been removed by mods?
xswistaqx said:
They cannot void your warranty just based on the fact you requested the unlock.bin
As for how to unlock there is plenty of information about it in threads here, just read it. As for an unofficial way of unlocking - the fact that you couldn't find anything in google leads me to believe it either does not exist or is a recent discovery in which case I'd wait since it will find its way here sooner or later once it's validated.
Click to expand...
Click to collapse
This in theory, the practise is different, there are reports on both cases in xda, so it's better to report the worst case.
ashirviskas said:
I remember browsing through reddit and xda three days ago and in some thread people were discussing the ways of unlocking G5. One person said that if official way doesn't work (because only h850 is supported on LG website), you can buy unlock *stuff* (file or code, I don't remember) on this other website for 1.99 or 0.99. Others said they will try and after trying they were really happy because it worked.
I'm not sure where it was, but I think it was on XDA. Could it have been removed by mods?
Click to expand...
Click to collapse
There was nothing like this on xda, maybe a simple thread where users tried to find a different way to unlock the bootloader