Related
I bought used Rezound and figured I'd unlock the bootloader using HTCDev.com
I go through all the steps and at the last part after I enter the token I get this:
Unlocking Bootloader Failed!
Sorry it didn't work out. Here's why:
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: 173.
Error Reason: Check Rule Fail with exception.
I noticed the top of the screen on my phone says ***RELOCKED***
Is there not a way to unlock it once its relocked?
diablo2jz said:
I bought used Rezound and figured I'd unlock the bootloader using HTCDev.com
I go through all the steps and at the last part after I enter the token I get this:
Unlocking Bootloader Failed!
Sorry it didn't work out. Here's why:
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: 173.
Error Reason: Check Rule Fail with exception.
I noticed the top of the screen on my phone says ***RELOCKED***
Is there not a way to unlock it once its relocked?
Click to expand...
Click to collapse
no, you can unlock it once it's relocked. Most of us that have taken the OTA by RUUing had to unlock and relock . So, I would go through the process again , just check and double check the steps. I had an issue where it failed 8 straight attemtps and it turned out I was actually copying a space in the code..once I removed the space it went right through.
I made sure I wasn't copying the spaces, tried again and took a screen shot.
Gave same error
diablo2jz said:
I made sure I wasn't copying the spaces, tried again and took a screen shot.
Gave same error
Click to expand...
Click to collapse
It has let me redo the HTC Dec steps with my phone multiple times. I finally figuired out once you get the unlock.bin file you can always reuse it. I do what is stopping you. :/
Sent from my ADR6425LVW using XDA App
Yeah I googled the heck out of everything I could think of and searched XDA and found almost nothing.
Guess I'm just lucky
diablo2jz said:
I made sure I wasn't copying the spaces, tried again and took a screen shot.
Gave same error
Click to expand...
Click to collapse
Maybe a dumb question, but your not including "please cut the following " part in it when you submit are you ?
Nope only pasted what I have highlighted in post 3.
Not to mention I have purposely copied them or some stuff out, and get a normal error to the extent of "You're token is to long, or to short" ect.
Same issue
Error Code: 173.
Error Reason: Check Rule Fail with exception
Anyone else getting this?
diablo2jz said:
Nope only pasted what I have highlighted in post 3.
Not to mention I have purposely copied them or some stuff out, and get a normal error to the extent of "You're token is to long, or to short" ect.
Click to expand...
Click to collapse
Sorry, no idea then ..
So wait, where did you get this phone? Is it possible the old owner unlocked it, relocked it, then sold it? If so, anybody know if he will be able to unlock since he probably doesn't have the original key?
Comicazy said:
Is it possible the old owner unlocked it, relocked it, then sold it?
Click to expand...
Click to collapse
That is correct. I had no idea but that's what I realized.
If I can't I'm going to sell this damn thing for a Nexus.
Unlocking Bootloader Failed! 173
I am getting the same error. I just activated the phone yesterday and have tried the process on a PC and a Mac now. Are the token identifiers supposed to change every time? I noticed that every time I type the command fastboot oem get_identifier_token I get a different token. I read some other posts where they were having problems and it ended up being a hardware issue. Any thoughts?
timothydye79 said:
I am getting the same error. I just activated the phone yesterday and have tried the process on a PC and a Mac now. Are the token identifiers supposed to change every time? I noticed that every time I type the command fastboot oem get_identifier_token I get a different token. I read some other posts where they were having problems and it ended up being a hardware issue. Any thoughts?
Click to expand...
Click to collapse
I have unlocked and relocked my phone 2 times now, and got a different token and identifier every time, so it shouldn't matter if he has the original unlock token or not.
mjh68 said:
I have unlocked and relocked my phone 2 times now, and got a different token and identifier every time, so it shouldn't matter if he has the original unlock token or not.
Click to expand...
Click to collapse
but if you want to re-unlock you can re use the same unlock bin file without generating a new token. If you make a new token your bin file is invalidated.
https://twitter.com/#!/Jmz_Software/status/164817446841221120
known issue now
diablo2jz said:
I bought used Rezound and figured I'd unlock the bootloader using HTCDev.com
I go through all the steps and at the last part after I enter the token I get this:
Unlocking Bootloader Failed!
Sorry it didn't work out. Here's why:
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: 173.
Error Reason: Check Rule Fail with exception.
I noticed the top of the screen on my phone says ***RELOCKED***
Is there not a way to unlock it once its relocked?
Click to expand...
Click to collapse
if you've bought a used rezound, that means the person
who sold probably unlocked the phone first.
why not ask that person for the unlocked token he used?
con247 said:
but if you want to re-unlock you can re use the same unlock bin file without generating a new token. If you make a new token your bin file is invalidated.
Click to expand...
Click to collapse
Ah, gotcha .. I had already deleted the first token so didn't have a choice hehe
This is an issue with the website, not the phone. I'm dealing with the same bull****.
I had the same problem. I relocked to get the update and could not unlock. I don't know what the fix is. Fortunately I saved the file from the first time I unlocked and it worked fine.
diablo2jz said:
I made sure I wasn't copying the spaces, tried again and took a screen shot.
Gave same error
Click to expand...
Click to collapse
You know, I don't know if that's sensitive info but you may want to black some of that out just in case since it pertains to your particular device. Probably doesn't matter but I always opt for the safe route since I'm a paranoid android.
EDIT: Looks like HTC fixed the issue and people are getting their unlock codes now.
http://forum.xda-developers.com/showthread.php?t=1475864&page=2
Done (http://forum.xda-developers.com/showthread.php?t=2158836)
Can you explain me what is this? Unlocking your htc phone? Unlocking what bootloader, kernel or network restrictions?
i don't need google, my wife knows everything
uglyjohny said:
Can you explain me what is this? Unlocking your htc phone? Unlocking what bootloader, kernel or network restrictions?
i don't need google, my wife knows everything
Click to expand...
Click to collapse
it's unlock code to unlock bootloader for your HTC Android phone.
After unlock bootloader, you can root your HTC phone.
And after that you can install any custom rom you want.
And do many many amazing things.
I tried this but got error 170
Error Code: 170.
Error Reason: CID Not Allowed.
You havn't by any chance had it repaired have you? cause if the motherboard is changed you cant unlock it.
Perhaps this will help me, I just got a new 3vo yesterday and the damn site wont send the email.
<<<< Identifier Token Start >>>>
800F6B84A62EB5D2F49B887A9FD1F717
DAF1D2A8838398E2701D53834D31F72A
3B487DF4547332B2078777E30A144D0E
F9AE9ED1DAB94CF6A8D3AB09F8A803BF
6657E6F616F1524D8BF0ECD91C24761E
BB52054503862229E87EC441E230A367
BC94914C2AA99EED63317B856FFBF96F
8C7F5103E4355900FCD35F4396BCA7F6
EE22270F75521ABF60EA405B527B2B26
61A9B8E398DA1794D61ABEAAC0FAAAB3
B48931C70FFA87680EB8D35200FF326E
0D5F859269F9B9F41C8A2E701272D732
99043D4BA83DE4966D80674EE36D7D87
00C814BB6E22B3A6E5AAB0DA4017B172
C6144604EA396B14111BB58B0FEA2D90
9653BA8E88C0D807D893EB0D1CDCE755
<<<<< Identifier Token End >>>>>
Please and thank you [=
This new code worked no problem. the previous one is giving error
Edit: I've zipped the file because it wasn't allowing me to upload .bin file
BUT
EM|NEM said:
This new code worked no problem. the previous one is giving error
Edit: I've zipped the file because it wasn't allowing me to upload .bin file
Click to expand...
Click to collapse
do it work with all CID?
spritz2o said:
do it work with all CID?
Click to expand...
Click to collapse
As long as you provide the correct cid for your phone it should. word of caution it doesnt like spaces so make sure there are no spaces before or after any of the text.
crimsy wrote an excellent guide to unlock root and soff your phone check it out: http://forum.xda-developers.com/showthread.php?t=1813818 :good:
spritz2o said:
do it work with all CID?
Click to expand...
Click to collapse
You have to use your OWN unlock code. the one i posted was only for Shponglized.
Its very easy to get your own token but sometimes htcdev doesnt send the code to an email or you may be experiencing problems with the site. In that case post your Identifier token here so that someone else can generate the unlock code for you.
I have an x10a, and I have for a while. But, its getting old, and boring. I wanted to spice it up with a custom ROM, namely Cyanogenmod. But going through the steps, xflashtool doesn't seem to want to play ball, informing me that "Your phone bootloader cannot be officially unlocked".
I've flashed it before, but only back to stock. This time I want something new.
Now, I've googled around and I've found a few pieces of information about this, but nothing concrete, and certainly nothing very in-depth.
I need to know;
- Does this mean that my attempts at a custom ROM are just at a halt completely? Too bad for me, try a different phone?
- If not, can I force the bootloader to be unlocked, and will it remove my ability to use the radio capability in the phone? (as I have read in a few places now), because my phone isn't a lot of good without the ability to do phone things.
- If I can force it, how, and are there any downsides?
and bonus round;
- Why are there certain phones that just can't have the bootloader unlocked.
Cheers in advance guys, I'd really like to hear some good news about this, but anything is better than what I have at this point.
AzzaMan said:
I have an x10a, and I have for a while. But, its getting old, and boring. I wanted to spice it up with a custom ROM, namely Cyanogenmod. But going through the steps, xflashtool doesn't seem to want to play ball, informing me that "Your phone bootloader cannot be officially unlocked".
I've flashed it before, but only back to stock. This time I want something new.
Now, I've googled around and I've found a few pieces of information about this, but nothing concrete, and certainly nothing very in-depth.
I need to know;
- Does this mean that my attempts at a custom ROM are just at a halt completely? Too bad for me, try a different phone?
- If not, can I force the bootloader to be unlocked, and will it remove my ability to use the radio capability in the phone? (as I have read in a few places now), because my phone isn't a lot of good without the ability to do phone things.
- If I can force it, how, and are there any downsides?
and bonus round;
- Why are there certain phones that just can't have the bootloader unlocked.
Cheers in advance guys, I'd really like to hear some good news about this, but anything is better than what I have at this point.
Click to expand...
Click to collapse
1st: you still can flash custom rom, look for the one that have stated (for locked bootloader)
2nd: yes you can, there is testpoint method (correct me If I'm wrong)
3rd: no afaik
Bonus: because there are carrier locked, or just plain damn unlucky
Sent from my GT-P3110 using xda app-developers app
TakuyaZ said:
1st: you still can flash custom rom, look for the one that have stated (for locked bootloader)
2nd: yes you can, there is testpoint method (correct me If I'm wrong)
3rd: no afaik
Bonus: because there are carrier locked, or just plain damn unlucky
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Champion. Cheers for the lightning fast reply, didn't expect to hear back for a day or two. I'm gonna begin my search for a copy of cyanogenmod for x10's that are for locked bootloaders. This should be fun
AzzaMan said:
Champion. Cheers for the lightning fast reply, didn't expect to hear back for a day or two. I'm gonna begin my search for a copy of cyanogenmod for x10's that are for locked bootloaders. This should be fun
Click to expand...
Click to collapse
Cyanogen mod cant be installed in locked bootloader, due to cm require an custom kernel
Sent from my GT-P3110 using xda app-developers app
TakuyaZ said:
Cyanogen mod cant be installed in locked bootloader, due to cm require an custom kernel
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Damn it... Any suggestions for a good alternative? I'd like something either really fancy, or really low RAM and Battery usage.
TakuyaZ said:
...
Bonus: because there are carrier locked, or just plain damn unlucky
Click to expand...
Click to collapse
My X10i is carrirer locked, and I could unlock the boot loader without any problems.
The problem with those who lose their radio capability, is, as I suspect it to be, because they tried SIM-unlock their devices with third party methods in a way that are not supposed to be done. (A "bad" hack method of some kind). Once they unlock the boot loader, they lose that poor third party hack, and the device reverts back to a SIM-locked state. Since most of the people who do SIM-unlock their devices, uses a different carrier, will also lose the radio because of the carrier/SIM lock.
One can safely unlock the boot loader if:
* The device remains SIM-locked and haven't been touched by poor, unknown SIM-lock hacks.
* The device isn't SIM-locked in the first place. (Device was delivered in an unlocked state)
* The device is SIM-unlocked with the proper method, where one get proper unlock codes from their original carrier matched with the IMEI code.
SysGhost said:
One can safely unlock the boot loader if:
* The device remains SIM-locked and haven't been touched by poor, unknown SIM-lock hacks.
* The device isn't SIM-locked in the first place. (Device was delivered in an unlocked state)
* The device is SIM-unlocked with the proper method, where one get proper unlock codes from their original carrier matched with the IMEI code.
Click to expand...
Click to collapse
My phone was delivered locked to... Vodaphone? I think. I unlocked it a long time ago. But, I unlocked it by given them my IMEI, and getting the unlock code from them. So, as legit as it gets really. I am still not allowed to just unlock my bootloader. Based on what I've seen in this thread, and a couple of other places, if I force the bootloader to unlock by "less sturdy" means, I should be fine with my sim-unlock, or be able to just contact them again and get a new unlock code.
So, this Testpoint method that TakuyaZ mentioned, anyone able to point me in the right direction for that or an alternative? I can't seem to find a decent tutorial anywhere.
AzzaMan said:
My phone was delivered locked to... Vodaphone? I think. I unlocked it a long time ago. But, I unlocked it by given them my IMEI, and getting the unlock code from them. So, as legit as it gets really. I am still not allowed to just unlock my bootloader. Based on what I've seen in this thread, and a couple of other places, if I force the bootloader to unlock by "less sturdy" means, I should be fine with my sim-unlock, or be able to just contact them again and get a new unlock code.
So, this Testpoint method that TakuyaZ mentioned, anyone able to point me in the right direction for that or an alternative? I can't seem to find a decent tutorial anywhere.
Click to expand...
Click to collapse
What method did you try to unlock the bootloader with? As far as I know your SIM-unlocked status shouldn't be affected at all, as it is properly unlocked, with the radio accepting all carriers. (Radio part of the device is semi-isolated from the rest of the system)
Try this method, and you should be fine: (But I cannot promise anything. If you do try it, you're on your own.)
http://forum.xda-developers.com/showthread.php?t=1253277
It's the method I used on a few X10i devices. Works on SIM-locked devices (They'll remain SIM-locked after, as it should be), as well as unlocked devices that previosly has been SIM-locked, but unlocked with the proper codes from the carrier. They remained SIM-unlocked after unlocking the boot loader. Good news that is.
So if you really know that your device has been properly SIM-unlocked with codes delivered from the carrier that locked the device in the first place, you should be fine. A.f.a.i.k, the only ones that lost their radio on their devices, are the ones who used improper third party hacking methods to SIM-unlock their devices.
Warning: If you are not 100% sure about what method that has been used to SIM-unlock your device. Stop. And turn back.
Alright, attempting the method posted above, I have hit a snag. I then proceeded to hit the same snag over and over again, trying minutely different methods.
My problem is with the qsd8250_semc tool.
The most I can get out of it is;
"
Process requires standard 2.x android firmware.
Press any key to continue...
Getting ROOT rights.
error: protocol fault (no status)
error: device not found
error: device not found.
Waiting...
"
Any suggestions? At this point I've tried the methods listed on the sites below, but nothing is working.
http://forum.xda-developers.com/showthread.php?t=1253277
http://www.modaco.com/topic/346145-how-toguideunlock-x10-bootloader-permanently/
AzzaMan said:
Alright, attempting the method posted above, I have hit a snag. I then proceeded to hit the same snag over and over again, trying minutely different methods.
My problem is with the qsd8250_semc tool.
The most I can get out of it is;
"
Process requires standard 2.x android firmware.
Press any key to continue...
Getting ROOT rights.
error: protocol fault (no status)
error: device not found
error: device not found.
Waiting...
"
Any suggestions? At this point I've tried the methods listed on the sites below, but nothing is working.
http://forum.xda-developers.com/showthread.php?t=1253277
http://www.modaco.com/topic/346145-how-toguideunlock-x10-bootloader-permanently/
Click to expand...
Click to collapse
Did you try with Flashtool? Don't use the newest version, you need 0.9.10 release. From http://androxyde.github.io/ There is a thread on here some where ill inbox you the link if I find it.
But it is easy as to do. By memory I think you click the padlock in flashtool to root phone then click on the plugins and you have the option to unlock boot loader with a click. Not sure if you have to add recovery first? Get the older version of flashtool though.
I'm sure someone will remember and help :good:
Found this http://forum.xda-developers.com/showthread.php?t=1254087
Hey mate this is the thread I used http://forum.xda-developers.com/showthread.php?t=1821750
doodownunda said:
Did you try with Flashtool? Don't use the newest version, you need 0.9.10 release. From http://androxyde.github.io/ There is a thread on here some where ill inbox you the link if I find it.
But it is easy as to do. By memory I think you click the padlock in flashtool to root phone then click on the plugins and you have the option to unlock boot loader with a click. Not sure if you have to add recovery first? Get the older version of flashtool though.
I'm sure someone will remember and help :good:
Found this http://forum.xda-developers.com/showthread.php?t=1254087
Hey mate this is the thread I used http://forum.xda-developers.com/showthread.php?t=1821750
Click to expand...
Click to collapse
The only things needed on the X10 part is it to have original (Stock) firmware with Android 2.1 or 2.2, with the original 2.6.29 kernel.
Also one need to enable debugging over USB (Debug Bridge) in the developer settings. And lastly need the drivers installed if using Windows. (Which I assume is the case here)
Once that's done, it should all work.
I've written a Linux script if anyone needs it. Still need the other files from the original qsd8250.7z toolset from the_laser's thread. See attached files.
Place qsd8250_semc.bash in the same director as qsd8250_semc.cmd, then execute it.
One also need Linux-version of the adb command, and in the system PATH variable.
UPDATE 11/25/2013 - scotty1223 posted a method by which you can change your UNLOCKED flag back to LOCKED which then re-enables the fingerprint senser. I'd recommend to just avoid HTCDev.com for unlocking and go straight to this thread: http://forum.xda-developers.com/showthread.php?t=2540004
On a personal note:
It makes sense really. Your fingerprint is like a unique password that you cannot change so HTC is doing everything prudent to protect that password for you. I don't see a problem with this personally.
On a technical note:
I believe the TZ partition (mmcblk0p11) has a check for whether the device is LOCKED, UNLOCKED, or RELOCKED. If it is anything other than LOCKED then the fingerprint scanner is automatically disabled.
I believe there are two possible ways to re-enable the fingerprint scanner:
Issue the command fastboot oem lock from the bootloader then run a factory RUU for your carrier
Hex edit the TZ partition to remove the unlock check, then fastboot oem lock and subsequently unlock the device again
The first method would most likely require that you also flash the stock recovery from fastboot before relocking.
The second method would require S-OFF to function as it is very unlikely that mmcblk0p11 is writable with S-ON.
I am by no means an expert with HBOOT or TZ so I may be way off base here, but that's how I see it right now. I'll see if I can get a warning posted in the threads about the fact that unlocking the bootloader with HTC Dev method will disable the fingerprint scanner.
yes ... pretty sad situation here... dont want to lock it again at the moment ... maybe i will relock it when i found a good rom ( i hope there will be roms for this phone, mike wont do one )
damn its a great phone !!
B-Man2005 said:
yes ... pretty sad situation here... dont want to lock it again at the moment ... maybe i will relock it when i found a good rom ( i hope there will be roms for this phone, mike wont do one )
damn its a great phone !!
Click to expand...
Click to collapse
relocking didn't work for me
I can confirm relocking dosent enable it.
Odd HTC would put a check on that function there....
Sent from my EVO using Tapatalk
@navalynt i have an app which also does not work after boot-loader unlocking.
This app is "Du Transport" and it is an app which is used to replace smart cards in pubic transport. This requires a special sim from the telecom provider and with this SIM as authentication the app uses NFC to replace the smart cards.
i think it goes back to the secure partition which you talked about. your solution logically makes sense that it's a bug in the firmware/hboot or where ever which needs to be fixed rather than these individual apps fixed.
This should have also behaved the same way as in HTC One.
For the s-off solution, do you think we could we just reuse the tools/scripts which were created for HTC One?
Has someone here contacted HTC or know if HTC/HTCDev are aware or working on this issue?
---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------
I am not sure if this is a bug or that's the way it is meant to work. we could possibly contact HTC/HTC Dev for a fix about it if we are sure it is a bug. i have read that HTC dev's attitude is bad but we could possibly contact the service center managers and demand a new phone under warranty.
I am not worried warranty and BL unlocks as i have dealt with such a situation before.
Hello
So the solution to make it enable state again is to flash a RUU ?
so i contacted HTC customer care via the website and i got this response.
Thank you for contacting HTC support.
As per your mail, we understand that after unlocking the bootoader of your HTC One Max, the finger print sensor is not working.
In this regards, we request you to please visit our nearest service-center to resolve the issue.
We would like to inform you that as, you have manually rooted and installed customized OS, the warranty of your device may get void, kindly provide us with the device details like IMEI or Serial number and your location so we can direct you to the service-center accordingly.
You can get the IMEI number by dialing *#06# or you can get the Serial number or IMEI number on the invoice or you can find the IMEI number or Serial number on your HTC handset box as well.
Please read the disclaimer given below:
Disclaimer: Unlocking your device allows you to install custom Operating Systems (“OS”) onto your device. Custom OS’s are not tested as thoroughly as your original OS, and unlocking your device may void all or parts of your warranty. HTC disclaims any and all liability for proper functioning of your device after the bootloader has been unlocked and for data lost in the unlocking process. To prevent unauthorized access to your data, unlocking the bootloader will delete all personal data from your device including applications, text messages and personalized settings.
Click to expand...
Click to collapse
Send you to service center to have RUU flashed.... Has nothing to do with custom OS... I'd hit up Jason and Mo from HTC on Twitter.... likely get a better logical response there.
Sent from my EVO using Tapatalk
sgt. slaughter said:
Send you to service center to have RUU flashed.... Has nothing to do with custom OS... I'd hit up Jason and Mo from HTC on Twitter.... likely get a better logical response there.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Yeah thanks, that's what i am thinking of doing... i was wondering if there is going to be some kind of solution to this issue or we just have to live without root ? it's not only fingerprint sensor which seem to stop working... its some kind of secure flag/partition which goes bonkers on BL unlock i have a very similar issue with another app after BL unlock.
Paul O'Brien of Modaco confirmed that HTC is aware of the issue and he raised it with HTC
has anyone with s-off tried setting the bootloader back to "locked" (not "relocked") to see if that fixes it?
I would try it but the only one max I have access to belongs to my dad and he's considering returning it and getting something else so I can't do anything that could cause problems with returning it.
hotaru2k3 said:
has anyone with s-off tried setting the bootloader back to "locked" (not "relocked") to see if that fixes it?
I would try it but the only one max I have access to belongs to my dad and he's considering returning it and getting something else so I can't do anything that could cause problems with returning it.
Click to expand...
Click to collapse
We don't have definite guides of making it to "locked" yet.
Given that our device is almost the same as HTC One, i am guessing methods of HTC One might work.
I found this on the HTC One forum - http://forum.xda-developers.com/showthread.php?t=2497712
Woot woot! it worked!!!
I removed my TAMPERED flag and also set it to LOCKED and the fingerprint scanner works!
Thanks to @scotty1223 for this! i would let scotty1223 to post the commands and make a thread for resetting the flags.
If this is true, this would be amazing.
JohnnyGipsy said:
If this is true, this would be amazing.
Click to expand...
Click to collapse
Yes it does work mate, works well! you would need S-Off and would need to follow the commands for locking and unlocking
pradeepvizz said:
Yes it does work mate, works well! you would need S-Off and would need to follow the commands for locking and unlocking
Click to expand...
Click to collapse
Than post the commands, please.
JohnnyGipsy said:
Than post the commands, please.
Click to expand...
Click to collapse
oh well, All credits to @scotty1223
My phone is a T6UL, I had provided the dump of my partitions to Scotty, which the dev worked on.
The commands that worked for me is the same as
http://forum.xda-developers.com/showthread.php?t=2477792
and
http://forum.xda-developers.com/showthread.php?t=2475914
i would suggest to hold on to your patience till Scotty makes a thread, just in case.
standard disclaimer : this might brick your phone, me nor scotty would not be responsible.
I can confirm it's working. My phone is now s-off and I have a working fingerprint sensor.
Gesendet von meinem HTC One mit Tapatalk
I'm having issues unlocking the boot loader on the Moto E 2nd 4G LTE (XT1527) can anyone else confirm this phone can be unlocked?
I've gone through all the steps and it tells me this is not a unlockable phone even though I know that there is a CyanogenMod port for
this model.
I'm in the US, is there anything else besides having a supported unlockable phone, that can cause them to flip you the bird when it
comes to unlocking?
I'm going to call their tech support tomorrow, but it would be nice to have a confirmation before I get on the phone with them.
Also failing that has anyone discovered a force-able unlocking method for these phones yet? =/
This phone is unlockable. I found an AIO script on HTCMania. It unlocks the bootloader, flashes recovery, roots the phone and flashes any stock ROM you like.
People here in XDA don't like AIO's, also the script is in spanish.
Thank you very much.
I'll see if I can find it on HTCMania and see if I want to use it.
Would it be against the rules for you to post the link for me?
I've taken a look at the script, it just opens the motorola website for pasting the code with motorola's website.
It still does not solve the problem that Motorola ("Spits something green") won't unlock the boot loader.
It is not a bootloader crack unfortunately. =/
If someone knows of a non-motorola approved bootloader crack its what I'm looking for at the moment.
One that does not contain paste your code into Motorola's website for approval and subsequent refusal.
A extra thanks would go if it contains pictures of monkies using or otherwise defecating on the motorola logo during the cracking process.
Never mind I forgot about the posts below when I posted this about bootloader unlocking and bounties for a crack unlock, I'll follow these threads.
dreyeth said:
Never mind I forgot about the posts below when I posted this about bootloader unlocking and bounties for a crack unlock, I'll follow these threads.
Click to expand...
Click to collapse
But what exactly is the problem with your device? I really don't know what have been the struggles of others, but the thread on HTCMania says the script works for any edition. If you need any help with the translation, I can help with the critical parts or anything specific you want..
By the way, just to make sure, the script is the one made by Alkalinorap
atomomega said:
But what exactly is the problem with your device? I really don't know what have been the struggles of others, but the thread on HTCMania says the script works for any edition. If you need any help with the translation, I can help with the critical parts or anything specific you want..
By the way, just to make sure, the script is the one made by Alkalinorap
Click to expand...
Click to collapse
You're familiar with the motorola approved unlocking process right?
It just forwards you through the motorola approved booting processing, it just opens the page and helps you copy
the code to motorola.
I think your probable lucky and don't have a US edition of the Moto E or have service with a US phone provider,
or maybe the unlocker tool on the motorola website knows I'm in the US or something and won't unlock my phone.
The spanish script just does the same thing only does it through a shell script that opens windows for you to
paste unlock codes and send them to motorola for approval just like the standard motorola approved unlocking process.
It doesn't provide a means to unlock the bootloader if motorola decides they're going to flip you the bird.
It does not work if motorola will not approve your unlock process.
I have a XT1527 which I made the mistake of activating to cricket (at&t) before unlocking.
I don't know if they would have let me unlock my bootloader on my XT1527 before, but they
may have refused me the right after hooking up my cricket service to it.
May they both spontaneusly burst into flames and meet a screaming end.
Thanks for the offer on translating it, I got through script pretty easy I ended up using google translate to get through it.
I had already tried doing the standard unlock process.
Unless there is a second spanish script somewhere else on the page that does something different.
Accidental double post, I must have been tired when I posted this.
I'm confirming my own thread that unlocking should work on a XT1527 (unlocked) that you receive from the factory rather then used.
I've had issues getting the website to accept my code even had to have a motorola employee from their forums reformat my code for me (I tried their
data scrub tool and it didn't work) and finally it works.
XT1527 should be unlockable though, and mine was after the code was formatted correctly.
That doesn't mean you're not going to have the same trouble I did though.
dreyeth said:
I'm confirming my own thread that unlocking should work on a XT1527 (unlocked) that you receive from the factory rather then used.
I've had issues getting the website to accept my code even had to have a motorola employee from their forums reformat my code for me (I tried their
data scrub tool and it didn't work) and finally it works.
XT1527 should be unlockable though, and mine was after the code was formatted correctly.
That doesn't mean you're not going to have the same trouble I did though.
Click to expand...
Click to collapse
Cool to know you were able to do it!! :good: