I have the phone in Bootloader mode (holding down power and volume down keys). I have all the required software installed. I use the command prompt to get my token and copy the info into the requisite slot in the HTC website window and when I hit the continue button I get an error message "Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work"
I have tried multiple times on two different computers. Always the same error. It is 7:30 pm EDT. I need help cuz I may be running out of time.
DiggerG said:
I have the phone in Bootloader mode (holding down power and volume down keys). I have all the required software installed. I use the command prompt to get my token and copy the info into the requisite slot in the HTC website window and when I hit the continue button I get an error message "Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work"
I have tried multiple times on two different computers. Always the same error. It is 7:30 pm EDT. I need help cuz I may be running out of time.
Click to expand...
Click to collapse
You aren't copying it right. Read the instructions and ensure you are only copying the information it wants
Sent from my HTC One using xda premium
Finally got it to work, but I'm not sure what I did differently. Put Command prompt window next to website window and that did it, but don't know why. Anyhow I have my email.
And I'm unlocked!!!
mine is stuck at waiting for device after i put in the command. Is there anyway anyone can send me the fastboot, adb, and adbwinapi.dll they used? I'm wondering if mine just isn't the right one but they should be. also i have the phone hooked up first and then go into fastboot and it says fastboot usb before i type in the command
thanks for any help
What do you mean "Stuck waiting for device after I put in the command"? If you pm me an email address, I can send the files tonight when I return from work.
DiggerG said:
What do you mean "Stuck waiting for device after I put in the command"? If you pm me an email address, I can send the files tonight when I return from work.
Click to expand...
Click to collapse
I type in "fastboot oem get_identifier_token" and then it displays waiting for device but doesn't do anything after that I waited for 30 minutes the first time and it stayed saying that. Ok I'll PM it now thank you
brom66an6 said:
I type in "fastboot oem get_identifier_token" and then it displays waiting for device but doesn't do anything after that I waited for 30 minutes the first time and it stayed saying that. Ok I'll PM it now thank you
Click to expand...
Click to collapse
The device isnt connected properly to the computer. Make sure you open your command prompt in the android folder and have the files within the same folder (i did this on OS X)
And then check to make sure you the computer recognizes the phone with
fastboot devices
You should see your device listed if it is connected properly.
brom66an6 said:
I type in "fastboot oem get_identifier_token" and then it displays waiting for device but doesn't do anything after that I waited for 30 minutes the first time and it stayed saying that. Ok I'll PM it now thank you
Click to expand...
Click to collapse
Did you install the HTC Sync Manager or install the HTC USB drivers from another source? Your phone won't be detected until you have the drivers installed. (I'm assuming you're using a Windows computer)
brom66an6 said:
mine is stuck at waiting for device after i put in the command. Is there anyway anyone can send me the fastboot, adb, and adbwinapi.dll they used? I'm wondering if mine just isn't the right one but they should be. also i have the phone hooked up first and then go into fastboot and it says fastboot usb before i type in the command
Either need htc drivers or your not in fastboot usb/bootloader
thanks for any help
Click to expand...
Click to collapse
If your getting that error, you have fastboot and adb but you haven't installed htc drivers yet.
If you don't have fastboot/adb files you will get a unknow command error.
Sent from my SPH-L710 using Tapatalk 2
*edit - I got it taken care of now i uninstalled and reinstalled the drivers and it worked this time. Thank you everyone for the help.
has anyone received the "Error Code (10) A request for the USB descriptor failed" error message? i can't get my laptop to seen my device in fastboot mode. i've installed/uninstalled the HTC drivers but no change. weird part is that i can communicate with my device via ADB when booted normally. any suggestions would be appreciated.
Waiting (and waiting) for device
18th.abn said:
If your getting that error, you have fastboot and adb but you haven't installed htc drivers yet.
If you don't have fastboot/adb files you will get a unknow command error.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I'm having exactly the same issue as brom66an6. fastboot starts, but never proceeds from "waiting for the device". If this is a driver problem, what drivers need to be installed on the phone?
what next??? I have the identifier token..
DiggerG said:
And I'm unlocked!!!
Click to expand...
Click to collapse
Great for you, I can't wait to get there myself.
It was late last night and I was one click away, but wan't sure how long until the next break stop would be, so I went to bed.
Now, I cannot recall what I was supposed to do. Can anyone please shed some light on the next instructions, I can no longer access these as I believe it was shown when you click to continue??
I have all the files/drivers and token placed in the same location on my drive and as a guess I've also copied the token .zip file to the SDcard on my HTC One X (vodafone stamped
I really wished they have a removable battery and media card support!! I have just purchased a new battery from eBay that proclaims a new chip on it that prevents overcharging. So that should be interesting, since the HTC charger is not a switching charger like my BlackBerry ones were.
What I want:
ROOT
a new clean/fast/efficient ROM, was thinking clockworkmod.
Since I have zero experience and limited time to troll through forums these days, I am really finding it hard to find a REALLY simple step by step guide to perform this. I know, it's not a simple proccess, I know, but perhaps just the steps in a efficient, simple list, overlooking stuff like backups etc, but perhaps a TIP to mention it would be a good idea as the next step will wipe everything etc
Thanks if you're still reading and perhaps WERE at my stage once before.
I'm sure custom ROMs are a personal preference, but any bad points about ROMs would probably be better than selling the good points.
CWM should be fine for my first attempt???
MANY thanks in advance for your time.
Steve.
[EDIT]
I'm now unlocked!!!!
I found the website that I was following, it is fantastic and just the right amount of simple for me.
Check it out...
www*droid-now*com/2013/08/htc-one-unlocking-bootloader-installing-custom-recovery-and-root/
Amazing Thanks..
DiggerG said:
Finally got it to work, but I'm not sure what I did differently. Put Command prompt window next to website window and that did it, but don't know why. Anyhow I have my email.
Click to expand...
Click to collapse
That sounds stupid... but it works, worked for me...
hi
i am trying to unlock the bootlaoder for my new htc m9
after i got the unloch_code, i receive this msg in cmd
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.038s
please help
what is missing ?
Can someone answer this
My htc one x9 gets recognized by my laptop everything works well
Lequired software is installed properly
And i try to type in fastboot devices and my phone appears to be in fastboot
But when i type fastboot oem get_identifier_token it says FAILED(remote:unknown command)
Finished.time:0.005
Plz im begging for help
Mine struck after the entry of code fastboot OEM get_identifier_token and my device is already detected and it's showing three dots "..." And that's it
Related
Anyone know why it won't generate a token for me? I feel like I'm making a stupid mistake here, but it reboots to fastboot, tells me to copy the ID token and paste it into the HTC page. Makes sense, but there's no token to copy?
tekhna said:
Anyone know why it won't generate a token for me? I feel like I'm making a stupid mistake here, but it reboots to fastboot, tells me to copy the ID token and paste it into the HTC page. Makes sense, but there's no token to copy?
Click to expand...
Click to collapse
Are you requesting the token from the command prompt while connected but not active sync. I think the command is fastboot get_identifier_token or whatever is on the HTC dev site. Then the in the command prompt it will suddenly display like 17 lines of code ..it will have a start and a stop..
mjh68 said:
Are you requesting the token from the command prompt while connected but not active sync. I think the command is fastboot get_identifier_token or whatever is on the HTC dev site. Then the in the command prompt it will suddenly display like 17 lines of code ..it will have a start and a stop..
Click to expand...
Click to collapse
Yeah, I just did it in the command line. HTC Super Tool is supposed to just run the script for you, but it didn't seem to work for me. The get identifier command worked just fine.
i had the same problem so i ran it manually
i did exactly every steps that show. but how come when i submit.
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: 140.
Error Reason: Token Decryption Fail.
Help!!!!!!!!!!!!!!!!
try going thru the whole process again, gettin the token and make sure u copy the "<<<<<<<<" too
Make sure you copy your token identifier in a notepad and delete "info" on the left side.
This should be posted in Q&A section.
<<<< Identifier Token Start >>>>
82520115AFCD5337DCDC6485A6D7D4B8
376D2DF9939BF47E6378597AFD70F7DF
451558E2810941B9D81C93F5DDC9EF95
3479EA6AD52893243D92159DB9CE811B
04C0CDF6110E7A639ABA2594AF8B554C
2EA1C220CBF75B9920AB072A839819C7
1F439E0D2A48068759FD2F2FB378C758
758CBE0CAE55F316C6BE8B0084209B5B
54C150522AD3F3265C053B6911BA6F14
23C2B5B88BC74AB3792A0704B6563F11
62D6B0BACB741AE287F9FDAD7C022CF5
B691FAEB0C4C2E79B82012695A1B5298
C29F5B396397047A77007643C9ADE588
61F90A391B7AC0945E264CA500C978AB
F03F42FE9A3E7584508FEA909CD2D82F
135C461490BE1978ED2A8DD814C37535
<<<<< Identifier Token End >>>>>
this how i copy.
dt53444 said:
<<<< Identifier Token Start >>>>
82520115AFCD5337DCDC6485A6D7D4B8
376D2DF9939BF47E6378597AFD70F7DF
451558E2810941B9D81C93F5DDC9EF95
3479EA6AD52893243D92159DB9CE811B
04C0CDF6110E7A639ABA2594AF8B554C
2EA1C220CBF75B9920AB072A839819C7
1F439E0D2A48068759FD2F2FB378C758
758CBE0CAE55F316C6BE8B0084209B5B
54C150522AD3F3265C053B6911BA6F14
23C2B5B88BC74AB3792A0704B6563F11
62D6B0BACB741AE287F9FDAD7C022CF5
B691FAEB0C4C2E79B82012695A1B5298
C29F5B396397047A77007643C9ADE588
61F90A391B7AC0945E264CA500C978AB
F03F42FE9A3E7584508FEA909CD2D82F
135C461490BE1978ED2A8DD814C37535
<<<<< Identifier Token End >>>>>
this how i copy.
Click to expand...
Click to collapse
That looks correct. So you already got your Unlock_code.bin?
<<<< Identifier Token Start >>>>
82520115AFCD5337DCDC6485A6D7D4B8
376D2DF9939BF47E6378597AFD70F7DF
451558E2810941B9D81C93F5DDC9EF95
3479EA6AD52893243D92159DB9CE811B
04C0CDF6110E7A639ABA2594AF8B554C
2EA1C220CBF75B9920AB072A839819C7
1F439E0D2A48068759FD2F2FB378C758
758CBE0CAE55F316C6BE8B0084209B5B
54C150522AD3F3265C053B6911BA6F14
23C2B5B88BC74AB3792A0704B6563F11
62D6B0BACB741AE287F9FDAD7C022CF5
B691FAEB0C4C2E79B82012695A1B5298
C29F5B396397047A77007643C9ADE588
61F90A391B7AC0945E264CA500C978AB
F03F42FE9A3E7584508FEA909CD2D82F
135C461490BE1978ED2A8DD814C37535
<<<<< Identifier Token End >>>>>
this is how i copy
still got same error!!!
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
i got it people. Thank you
What was the problem?
I'm facing the same issue
Make sure you aren't selecting the empty column just to the left of the token identifier. There is a single vertical line to the left that sometimes gets selected if your not carefull. I am willing to bet that this is your problem.
Mine is getting to this point:
c:\Android>fastboot oem get_identifier_token
< waiting for device >
and then just sits there. Is this because I rooted before doing HTCDev?
Will
shellguy said:
Mine is getting to this point:
c:\Android>fastboot oem get_identifier_token
< waiting for device >
and then just sits there. Is this because I rooted before doing HTCDev?
Will
Click to expand...
Click to collapse
i rooted before htc dev so that shouldn't b your problem also read this thread cause alot of ppl are having a difficult time selecting the token
I get
C:\Users\mark\Downloads\android-sdk_r12-windows\android-sdk-windows\platform-too
ls>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
and it just sits there. Only way to end it is to unplug phone. RUU'ed and updated htc sync then went through the whole process again and still nothing.
ummm am i an idiot..but i dont see the evo 4g lte listed on htcdev...which one are ya'll selecting
dahray02 said:
ummm am i an idiot..but i dont see the evo 4g lte listed on htcdev...which one are ya'll selecting
Click to expand...
Click to collapse
At the bottom "All Other Supported Models"
shellguy said:
Mine is getting to this point:
c:\Android>fastboot oem get_identifier_token
< waiting for device >
and then just sits there. Is this because I rooted before doing HTCDev?
Will
Click to expand...
Click to collapse
Make sure you have the proper drivers installed if not adb wont communicate with the phone.
Sent from my EVO using xda premium
durandetto said:
Make sure you have the proper drivers installed if not adb wont communicate with the phone.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I used the same PC to root the device too, but that was done via script.
Will
I'm having a problem as well. I got my Unlock code email. I downloaded it and put it in the Android file I created. Highlighted folder, shift+right click, got my cmd prompt, copied and pasted the fastboot flash unlock token...... and got this:
C:\Android>fastboot flash unlocktoken Unlock_code.bin
error: cannot load 'Unlock_code.bin'
C:\Android>
I don't remember having any issues when I did my Evo3d????????
FIXED: Had to actually type command. DO NOT copy and paste
shellguy said:
I used the same PC to root the device too, but that was done via script.
Will
Click to expand...
Click to collapse
Do you have adb installed?
Did you put in the path in your environment variables?
Do you have have HTC sync or disk drive disabled?
Is USB debugging on?
Lastly, computer OS? sometimes its just easier to use xp than w7.
If the answer to the first 4 questions were all yes, it should work...
What? XP is kicking my a$$! When I'm on a friends win7 PC, it finds drivers right away. Hell, I still can't even get XP to recognize my device storage to put my music on my phone (adb sees my device just fine and fastboot commands dont work either). Driving me nuts.
sent from my Evo LTE, usually.
Hey everyone,
So I've been having a problem with my Z Ultra that I haven't been able to solve for a number of weeks now.
The service menu on my C6833 specifically says that the bootloader is unlockable, as shown here:
(imgur) com/OO9549 (sorry, XDA won't let me post links yet. ><)
However, when I try unlocking using Sony's official instructions (and using FlashTool) - I get the following:
fastboot -i 0x0ffce oem unlock 0x(my key here)
...
FAILED (remote: Command did not succeed)
finished. total time: 0.027s
I've copied/pasted the key, I've typed it out manually, they all get me the same error. I'm running Windows 8.1 (finally managed to get the drivers installed), yet this also happened on a Windows 7 machine. I've been racking my brain, but I can't find ANYTHING that'll help. The last time I tried, I gave up trying to unlock the bootloader and installed the DualRecovery for locked bootloaders, which ended up bricking my phone and I had to flash back to stock.
Help! I just want to be able to install custom roms again! D:
Hmm, that's strange. I've googled a bit and you're not the first xperia owner with this issue. Some say that updating or re-flashing the ROM will fix it. Which version are you running?
LordManhattan said:
Hmm, that's strange. I've googled a bit and you're not the first xperia owner with this issue. Some say that updating or re-flashing the ROM will fix it. Which version are you running?
Click to expand...
Click to collapse
I've re-flashed the ROM a few times on different versions. I'm currently on 4.2.2 - 14.1.B.2.257.
Mandersoon said:
Hey everyone,
So I've been having a problem with my Z Ultra that I haven't been able to solve for a number of weeks now.
The service menu on my C6833 specifically says that the bootloader is unlockable, as shown here:
(imgur) com/OO9549 (sorry, XDA won't let me post links yet. ><)
However, when I try unlocking using Sony's official instructions (and using FlashTool) - I get the following:
fastboot -i 0x0ffce oem unlock 0x(my key here)
...
FAILED (remote: Command did not succeed)
finished. total time: 0.027s
I've copied/pasted the key, I've typed it out manually, they all get me the same error. I'm running Windows 8.1 (finally managed to get the drivers installed), yet this also happened on a Windows 7 machine. I've been racking my brain, but I can't find ANYTHING that'll help. The last time I tried, I gave up trying to unlock the bootloader and installed the DualRecovery for locked bootloaders, which ended up bricking my phone and I had to flash back to stock.
Help! I just want to be able to install custom roms again! D:
Click to expand...
Click to collapse
I had the same problem when I tried to unlock.
Tried 5 times and then was finally successful. Ensure that you have typed out the commands correctly. Don't copy and paste as that wont work.
Are you getting the same error in Flashtool?
Sent from my C6833 using Tapatalk
LordManhattan said:
Are you getting the same error in Flashtool?
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
I can't be sure as it was 3/4 months ago. Kept having issues, and I gave up. Then came back and after many attempts it worked. It was incorrect commands i was typing. 0 or O may have been the problem, or no space where they should be one.
If it says command failed then it sounds like you have the command correct, but the key is incorrect or the format of your input after the command is incorrect.
Also... are you rooted? Root first then try agian
hamdogg said:
I can't be sure as it was 3/4 months ago. Kept having issues, and I gave up. Then came back and after many attempts it worked. It was incorrect commands i was typing. 0 or O may have been the problem, or no space where they should be one.
If it says command failed then it sounds like you have the command correct, but the key is incorrect or the format of your input after the command is incorrect.
Also... are you rooted? Root first then try agian
Click to expand...
Click to collapse
I have copied/pasted, as well as typing out the commands. This has happened with Flashtool as well as in the command prompt.
And the phone is rooted.
EDIT:
I figured out the problem. I ended up using flashtool for the whole process. Windows 8.1's Driver Signature Verification NEEDS to be turned off. I ended up getting a new unlock code from Sony and that worked.
Mandersoon said:
I have copied/pasted, as well as typing out the commands. This has happened with Flashtool as well as in the command prompt.
And the phone is rooted.
EDIT:
I figured out the problem. I ended up using flashtool for the whole process. Windows 8.1's Driver Signature Verification NEEDS to be turned off. I ended up getting a new unlock code from Sony and that worked.
Click to expand...
Click to collapse
Hi Mandersoon,
I am in same problem and do you have any link or email to get new Unlock code from sony?
Thanks.
Encountered this on my first try. Then on the second attempt, it went through.
i had the same problem, it said "FAILED (remote: Incorrect format for unlock data. Should be on the form "0x)" so I did exactly as it said - added "0x" before my code and it worked!
I just removed "0x" from the unlock code given by sony, it worked like a charm. :good:
I dont know why.
BlackCatAlex said:
i had the same problem, it said "FAILED (remote: Incorrect format for unlock data. Should be on the form "0x)" so I did exactly as it said - added "0x" before my code and it worked!
Click to expand...
Click to collapse
can you please share the code i cant understand where to add 0x. i am facing the same issue. reply ASAP
Do not share the code/key. That's your unique key.
@psylbaba: it says "added "0x" before my code", so I assume he means 0x in front of the key when you're unlocking in Flashtool.
I just.....removed 0x and the <> in my code and it worked like a charm. Curious. (XZ1 user here)
Hi, found this thread when I was trying to unlock a Xperia z2, for me worked removing only the <> like this: fastboot oem unlock 0x"CODE"
Right click, administrator mode
Hey guys! Im having trouble unlocking my HTC One M9 (Sprint) with htc Dev.
I downloaded Android sdk, installed platform tools, i open command prompt window inside the platform tools folder
and I type adb devices, and it shows my device number and that it is connected. I reboot my phone into download mode, and I
type fastboot oem get_identifier_token and instead of showing me the token number i get
C:\Users\Rudy Molina\Desktop\platform-tools>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Users\Rudy Molina\Desktop\platform-tools>
I have no clue what to do.
I have tried it many times moved the folder around. uninstalled htc sync manager sdk manager and reinstalled. i get the same thing every time.
I recently did the ota update, not sure if that has something to do with it. So im now running
Android 5.1 sense 7
Please help me out. Im thinking about installing an RUU to have Android 5.0 and then trying the htc dev unlock.
I'm not sure but might have something to do with Android's Anti-Theft protection. Try disabling all security on the phone including and pin codes or lock screens, reboot and try again. Doesn't look like a driver issue
rmolina06 said:
Hey guys! Im having trouble unlocking my HTC One M9 (Sprint) with htc Dev.
I downloaded Android sdk, installed platform tools, i open command prompt window inside the platform tools folder
and I type adb devices, and it shows my device number and that it is connected. I reboot my phone into download mode, and I
type fastboot oem get_identifier_token and instead of showing me the token number i get
C:\Users\Rudy Molina\Desktop\platform-tools>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Users\Rudy Molina\Desktop\platform-tools>
I have no clue what to do.
I have tried it many times moved the folder around. uninstalled htc sync manager sdk manager and reinstalled. i get the same thing every time.
I recently did the ota update, not sure if that has something to do with it. So im now running
Android 5.1 sense 7
Please help me out. Im thinking about installing an RUU to have Android 5.0 and then trying the htc dev unlock.
Click to expand...
Click to collapse
Go to Settings - developer options and check box next to Allow OEM unlock first.
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Klown80 said:
Go to Settings - developer options and check box next to Allow OEM unlock first.
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
.......IT WORKED!!!!!!! lol I cant believe i didnt see that. Thank you soo much!!
rmolina06 said:
.......IT WORKED!!!!!!! lol I cant believe i didnt see that. Thank you soo much!!
Click to expand...
Click to collapse
Glad to hear you got it sorted. Welcome to XDA by the way.
Sent from my A0001 using XDA Free mobile app
Guys, I have the same problem rmolina06.
However, the phone does not start.
Is there a way to disable this thing, from fastboot?
: Pianto:
Unlock bootloader problem Sprint HTC One m9
Hi,
I also have a brand new Sprint HTC One M9 and am trying to unlock the bootloader.
I seem to have the exact problem which you had and also learned to enable the OEM unlock setting. However i still have a problem with the next step which is to submit the token ID on the htcdev.com site. Everything in the process works until I submit the token to htcdev. I get an error regarding an invalid token or wrong token length message each time i try it.
Can you let me know if you have succeeded and if so did you have to perform any additional steps.
Thanks
Tiernan
littlebam said:
Hi,
I also have a brand new Sprint HTC One M9 and am trying to unlock the bootloader.
I seem to have the exact problem which you had and also learned to enable the OEM unlock setting. However i still have a problem with the next step which is to submit the token ID on the htcdev.com site. Everything in the process works until I submit the token to htcdev. I get an error regarding an invalid token or wrong token length message each time i try it.
Can you let me know if you have succeeded and if so did you have to perform any additional steps.
Thanks
Tiernan
Click to expand...
Click to collapse
I have seen before where when I copy my token from the cmd prompt, it will put spaces on every line screwing up the token hence kicking out an error. Try pasting it into notepad first and delete any extra spaces before submitting.
I had trouble "marking" my token as well, highlighted way too much. I looked into the properties of edit and unchecked something about word wrap and it was all good. Sorry I can't remember the particulars or the terminology.
I am trying to buy a Sprint phone today (possibly the Htc one M9). Is it still possible to unlock bootloader through the HTC website? And if so, must the phone be completely paid off?? I really do not want to deal with any Samsung phones since I have had my At&t GS4 with locked bootloader for 2 years. Is there any roms or good mods for this phone yet?
There is no good roms for either the Note 5, s6, or Edge plus so if HTC allows unlocking bootloader to allow for a custom recovery than I would think the development will be good over time unlike any locked down samsung phone. Any advice on a good phone?
cyrusalmighty said:
I am trying to buy a Sprint phone today (possibly the Htc one M9). Is it still possible to unlock bootloader through the HTC website? And if so, must the phone be completely paid off?? I really do not want to deal with any Samsung phones since I have had my At&t GS4 with locked bootloader for 2 years. Is there any roms or good mods for this phone yet?
There is no good roms for either the Note 5, s6, or Edge plus so if HTC allows unlocking bootloader to allow for a custom recovery than I would think the development will be good over time unlike any locked down samsung phone. Any advice on a good phone?
Click to expand...
Click to collapse
yes, u can unlock via htcdev.com anytime...I do know of one good ROM
I ordered a Redmi note 4 through Amazon India, came out alright, all properly sealed and everything but one thing caught my attention is that on developer settings the phone unlock status says it's already unlocked! How can this be possible?
That's weird. Did you call a customer service centre? If I'd receive such product my first though would be to confirm if the Mido I got is a refurbished one or 1st hand. And even if it's one, then the Xiaomi guys should have relocked it... Maybe it's a software bug, try restarting. And the ultimate way to confirm is to use your PC, and you know the rest I hope.
Well, if you feel you can replace it (maybe) talk to amazon guys and confirm if they cover such thing in their replacement policy. Good luck.
MayankMathur said:
That's weird. Did you call a customer service centre? If I'd receive such product my first though would be to confirm if the Mido I got is a refurbished one or 1st hand. And even if it's one, then the Xiaomi guys should have relocked it... Maybe it's a software bug, try restarting. And the ultimate way to confirm is to use your PC, and you know the rest I hope.
Well, if you feel you can replace it (maybe) talk to amazon guys and confirm if they cover such thing in their replacement policy. Good luck.
Click to expand...
Click to collapse
How to check if it's refurbished via PC?
Maybe you have RN4x, it is default unlocked... You can check your box, if it is with chinese language you have 4x, if you have with english lang. it is RN4 Global version and it is locked default...
Edit: also check if it is Snapdragon 625 version or maybe it is MTK?
Sent from my Redmi Note 4x
kurogami95 said:
How to check if it's refurbished via PC?
Click to expand...
Click to collapse
You have to check if the bootloader is really unlocked or not. For this download this zip - https://drive.google.com/open?id=13Sjej5zIJPm_yiJQOVR4rEocwbhDc9oh
Unzip in pc and inside the platfrom-tools folder hold shift and right click.
In the menu it should say, open command prompt here or open powershell here.
click on the provided item (whatever of both it shows)
now, boot your device in fastboot by switching it off and holding down the power and volume down. Once the fastboot mode is open, connect your device via cable to your pc.
Now if you opened a command prompt window then type in -
Code:
fastboot devices
This command will show the connected fastboot devices. If nothing is printed on screen on executing command, then try reconnecting.
then type -
Code:
fasboot oem device-info
But if you have powershell then type in
Code:
.\fastboot devices
and
Code:
.\fastboot oem device-info
This will return some data and now you have to check the first two parameters saying "device tampered" and "device unlocked".
If device unlocked says true, then that means someone had actually used the device before. and if device tampered says true, then definetly someone has tested out your device, by doing all kinds of stuff like installing roms etc.
Use the mi flasher and flash the most current xiaomi rom. Your rom is probably a vendor rom, which is bad.
MyNameIsRage said:
You have to check if the bootloader is really unlocked or not. For this download this zip - https://drive.google.com/open?id=13Sjej5zIJPm_yiJQOVR4rEocwbhDc9oh
Unzip in pc and inside the platfrom-tools folder hold shift and right click.
In the menu it should say, open command prompt here or open powershell here.
click on the provided item (whatever of both it shows)
now, boot your device in fastboot by switching it off and holding down the power and volume down. Once the fastboot mode is open, connect your device via cable to your pc.
Now if you opened a command prompt window then type in -
This command will show the connected fastboot devices. If nothing is printed on screen on executing command, then try reconnecting.
then type -
fasboot oem device-info
But if you have powershell then type in
But if you have powershell then type in
.\fastboot devices
and
This will return some data and now you have to check the first two parameters saying "device tampered" and "device unlocked".
If device unlocked says true, then that means someone had actually used the device before. and if device tampered says true, then definetly someone has tested out your device, by doing all kinds of stuff like installing roms etc.
Click to expand...
Click to collapse
Thanks for making it easy for me. ?
Sometimes sellers unlock bootloader to flash other roms version. It's usually on online selling where there is Chinese roms on devices and buyers want global version.
As allready ppl stated, check by adb fastboot to see if its really unlocked.
Sent from my Redmi Note 4 using Tapatalk
MyNameIsRage said:
You have to check if the bootloader is really unlocked or not. For this download this zip - https://drive.google.com/open?id=13Sjej5zIJPm_yiJQOVR4rEocwbhDc9oh
Unzip in pc and inside the platfrom-tools folder hold shift and right click.
In the menu it should say, open command prompt here or open powershell here.
click on the provided item (whatever of both it shows)
now, boot your device in fastboot by switching it off and holding down the power and volume down. Once the fastboot mode is open, connect your device via cable to your pc.
Now if you opened a command prompt window then type in -
Code:
fastboot devices
This command will show the connected fastboot devices. If nothing is printed on screen on executing command, then try reconnecting.
then type -
Code:
fasboot oem device-info
But if you have powershell then type in
Code:
.\fastboot devices
and
Code:
.\fastboot oem device-info
This will return some data and now you have to check the first two parameters saying "device tampered" and "device unlocked".
If device unlocked says true, then that means someone had actually used the device before. and if device tampered says true, then definetly someone has tested out your device, by doing all kinds of stuff like installing roms etc.
Click to expand...
Click to collapse
Please can you help me? I got a Xiaomi Mi A1 and I noticed the bootloader was already unlocked, when I relock it the phone refuses to come on because I found out that "device tampered" is saying true. Please how can I get it back to false? Thank you
chuckychux said:
Please can you help me? I got a Xiaomi Mi A1 and I noticed the bootloader was already unlocked, when I relock it the phone refuses to come on because I found out that "device tampered" is saying true. Please how can I get it back to false? Thank you
Click to expand...
Click to collapse
You should contact xiaomi for this. And the seller from which you bought it. Because 98% of companies aren't allowed to sell phones with unlocked bootloader. Just leave it as it is. Tampering it by yourself would mean that you yourself did something to phone, which u haven't (not much, what u did is ok) . So getting in touch with the company and the provider would be a better option.
---------- Post added at 07:42 AM ---------- Previous post was at 07:41 AM ----------
chuckychux said:
Please can you help me? I got a Xiaomi Mi A1 and I noticed the bootloader was already unlocked, when I relock it the phone refuses to come on because I found out that "device tampered" is saying true. Please how can I get it back to false? Thank you
Click to expand...
Click to collapse
Or you can just unlock the bootloader once again to possibly make the phone functional
MyNameIsRage said:
You should contact xiaomi for this. And the seller from which you bought it. Because 98% of companies aren't allowed to sell phones with unlocked bootloader. Just leave it as it is. Tampering it by yourself would mean that you yourself did something to phone, which u haven't (not much, what u did is ok) . So getting in touch with the company and the provider would be a better option.
---------- Post added at 07:42 AM ---------- Previous post was at 07:41 AM ----------
Or you can just unlock the bootloader once again to possibly make the phone functional
Click to expand...
Click to collapse
I have unlocked it again and it's working again, but my problem now is that I can't get Ota updates on my phone and is there a way I can change "Device tampered" from true to false? Thank u
chuckychux said:
I have unlocked it again and it's working again, but my problem now is that I can't get Ota updates on my phone and is there a way I can change "Device tampered" from true to false? Thank u
Click to expand...
Click to collapse
Did u install twrp? If no then flash fastboot rom
MyNameIsRage said:
Did u install twrp? If no then flash fastboot rom
Click to expand...
Click to collapse
I didn't install twrp, if I flash with fastboot will it be locked? And how will I do it
chuckychux said:
I didn't install twrp, if I flash with fastboot will it be locked? And how will I do it
Click to expand...
Click to collapse
Most probably yea. Also you should report this in mi a1 forums as well. And you can google to find instructions for flashing update via fastboot.