Related
Hey, I'm kind of a noob here. Where do I get fastboot.exe from? Im stuck on step 11 in the "[UNLOCK] AT&T Bootloader Unlock Through HTC-Dev" thread
you need to download the android sdk, it has it in there as stated in the htcdev unlocking instructions
Thanks, I was able to get it to work once the one click unlock tool was posted.
Sent from my HTC One X using Tapatalk 2
Stupid questions but I can't seem to find simple answers:
a) do I need to be on a specific FW version or have a specific bootloader to unlock?
b) how do I tell what version I have?
c) does/can this get rid of the "tampered" on the bootloader screen?
d) does/can this give us full S-Off?
I'm assuming you're on the HTCDEV part because if you're not using the tool and you're asking this question you're doing it wrong.
that being said, it should come in the android SDK, if it doesn't then just copy the exe file out of the tool folder that you unzipped.
Edit, I see you already got it answered.
---------- Post added at 10:43 AM ---------- Previous post was at 10:39 AM ----------
xeper said:
Stupid questions but I can't seem to find simple answers:
a) do I need to be on a specific FW version or have a specific bootloader to unlock?
b) how do I tell what version I have?
c) does/can this get rid of the "tampered" on the bootloader screen?
d) does/can this give us full S-Off?
Click to expand...
Click to collapse
a) do I need to be on a specific FW version or have a specific bootloader to unlock?
--- i did it on 1.7, although I think 1.82 works
b) how do I tell what version I have?
--- settings > about phone > Software
c) does/can this get rid of the "tampered" on the bootloader screen?
----- absolutely not, look at the screenshots on the OP in the dev section
d) does/can this give us full S-Off?
-----no
HydroSkillet said:
I'm assuming you're on the HTCDEV part because if you're not using the tool and you're asking this question you're doing it wrong.
that being said, it should come in the android SDK, if it doesn't then just copy the exe file out of the tool folder that you unzipped.
Edit, I see you already got it answered.
---------- Post added at 10:43 AM ---------- Previous post was at 10:39 AM ----------
a) do I need to be on a specific FW version or have a specific bootloader to unlock?
--- i did it on 1.7, although I think 1.82 works
b) how do I tell what version I have?
--- settings > about phone > Software
c) does/can this get rid of the "tampered" on the bootloader screen?
----- absolutely not, look at the screenshots on the OP in the dev section
d) does/can this give us full S-Off?
-----no
Click to expand...
Click to collapse
Thanks for the info.
Another couple of dumb questions:
Will we ever be able to get rid of that "tampered" notice?
How does that notice effect me should my phone, say, fall and break its screen or have some other hardware-related failure? (I'm a klutz)
What does SuperCID mean and how does that effect me?
xeper said:
Thanks for the info.
Another couple of dumb questions:
Will we ever be able to get rid of that "tampered" notice?
How does that notice effect me should my phone, say, fall and break its screen or have some other hardware-related failure? (I'm a klutz)
What does SuperCID mean and how does that effect me?
Click to expand...
Click to collapse
Maybe, who knows on the "tampered" and yea you void your warranty so if you are afraid of hardware failure then don't do it, or but insurance on it. That's what I have, if I brick it cost me 100.00 rather than 600.00.
"Waiting for device"
Every attempt and different ways always brings me to that part. I have does the oneClick supercid program and I've even gone through the HTCDEV website 6 times now. after it reboots into boot loader mode and I direct it to the folder with the 3 files in it through cmd and I get to the final step to where it says "Waiting for device" trying to get the cid codes for my phone and nothing. I am at the end of my ropes of how to unlock codes. if anyone can help me or walk me through via text or video I would be so happy. I just want this thing finally unlocked and over with.
I take it your on this step?
11. Type "dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4" and hit enter. To test if it worked restart the phone into fastboot (type "adb reboot bootloader" and hit enter) and once the bootloader screen comes up type "fastboot oem readcid" and hit enter. It should read "11111111".
12. Next type "fastboot oem get_identifier_token" and hit enter. Leave that up on your screen and go to HTCdev.com. Follow the instructions from there. Choose "All other supported models" from the dropdown menu.
If so, Step 11 is kinda tricky worded after you type the command to reboot the device. Just don't even wait put the second line in "fastboot oem readcid" the batch file will wait for the phone. I hope this helps ya I had the same problem before And booted the phone back up and tried again but last time I just rebooted with the command then right after than put in the second command.
xeper said:
Thanks for the info.
Another couple of dumb questions:
Will we ever be able to get rid of that "tampered" notice?
How does that notice effect me should my phone, say, fall and break its screen or have some other hardware-related failure? (I'm a klutz)
What does SuperCID mean and how does that effect me?
Click to expand...
Click to collapse
Devs will find a way to remove tampered label once we find S-OFF. After the device has been "tampered", if your phone breaks and you send it to HTC warranty, they will not replace your phone if you have flashed a custom ROM on it. How they know you've flashed a custon ROM, I'm not sure.
SuperCID is the development CID designed to work on HTC phones. It allows you to unlock your bootloader through HTCDev.com. It also allows you to flash RUUs, because RUUs check CIDs on phones to determine whether the RUU is a valid ROM for your phone. However, it has been said this is hit/miss.
Don't take my exact word for it, use GOOGLE.COM.
I waited for the one-click tools, and I'm glad I did.
Forgot to mention
my Main computer is my iMac and I have a windows 7 laptop I switch to for my flashing/rooting etc... because I am not good with terminal or adb steps after a few seizures I've had recently. So shell stuff is completely useless to me. I can follow the steps on the briefmobile website then I have the HTCDEV account. but still at a lost.. for some reason.
I never got a 1111111 or whatever message
It just went straight to "Waiting for/on device" I tried again even attempted somewhat the hex edit way. but I never saw any "CW__111" or whatever in the file that I threw into HxE I think that was the hex program I used on my laptop. To frustrated to check in other room. I even kept looking at 210 section and nothing. So I'm not sure what is going on that won't let me unlock. Maybe I'll check youtube to see if there is a video on unlocking the bootloader.
hazmatik said:
It just went straight to "Waiting for/on device" I tried again even attempted somewhat the hex edit way. but I never saw any "CW__111" or whatever in the file that I threw into HxE I think that was the hex program I used on my laptop. To frustrated to check in other room. I even kept looking at 210 section and nothing. So I'm not sure what is going on that won't let me unlock. Maybe I'll check youtube to see if there is a video on unlocking the bootloader.
Click to expand...
Click to collapse
You should just use the one-click Super-CID tool in the Developers section, it's much faster and hassle free.
Thanks but that option never succeeded
I finally got it to unlock and get past that "Waiting for device issue" it seems even though I had my device plugged in and all the android and HTC drivers installed, it never registered that it could sense android 1.0 plugged in. so I had to manually right click and force it to install the drivers and it finally found device. low and behold it clicked and I got my email instantly right afterwards. So now I need how on installing CWM any ideas how to? be I am wanting to try out Team nocturnal's Rom for a little bit to see what it has to offer. Thanks for comment also by the way.
please help me. i dont know what to do with this cell... anyhow i managed to get it into this screen...
it would keep restarting after displaying htc quietly brilliant.
i have no idea what was done to this cell as i got it lying around in my closet.
What do you mean you got it lying around in my closet? You don't know what you did to it in the past?
Sent from my Evita
no actually my cousin might have screwed up my cell and kept it back...
timmaaa said:
What do you mean you got it lying around in my closet? You don't know what you did to it in the past?
Sent from my Evita
Click to expand...
Click to collapse
Well I think the first thing you should do is talk to your cousin and find out exactly what he did to the device, then you can report back here.
Sent from my Evita
is there any other way through which we can come to know what can be done??? such as an odin thing which i used to do in my samsung note 1 or 3???
timmaaa said:
Well I think the first thing you should do is talk to your cousin and find out exactly what he did to the device, then you can report back here.
Sent from my Evita
Click to expand...
Click to collapse
To know what needs to be done I need to know the history of the device. Odin is Samsung only, there is no HTC equivalent. Who got the phone to this point, you or your cousin? You need to find out what he's done.
Sent from my Evita
Well, one problem is that the screen is cracked.
Seriously though, the phone for some reason or other cannot load into the OS, and is stuck in bootloader. Other than that, not much else can be determined if you don't know the history of what was done.
pvirus86 said:
is there any other way through which we can come to know what can be done??? such as an odin thing which i used to do in my samsung note 1 or 3???
Click to expand...
Click to collapse
Nope. You need to know the history of the device. There is an HTC-specific recovery utility. But running it on a device with unknown history can brick the phone permanently. Particularly since the device is definitely tampered (as shown on the first line of the screen).
Also, the phone's IMEI is personal information, and should not be posted on the internet. You should edit the photo to hide the IMEI.
Unlock your bootloader. Sometimes if you have custom installed or fragments of a custom ROM on the device it will boot directly into your bootloader. After unlocking your bootloader you can install a recovery image and sideload a ROM.
yes i asked my brother and he is saying he doesnt remember what he had done to it... if anyone can show me a way to do something ill try it... or else should i take it to some shop to get it fixed.... which would cost me... but first i wanted to get my hands over d expert advise of u all
Return the phone to stock and never let your brother touch any electronic device of yours again.
Sent from my Evita
but can you let me know to revert it to stock. and will i have to do it from windows 7 or my mac os wud work???
pvirus86 said:
but can you let me know to revert it to stock. and will i have to do it from windows 7 or my mac os wud work???
Click to expand...
Click to collapse
This phone is in a dangerous state.. Running the RUU in this state could brick the phone (make it permanantly unusable without a jtag). Though typically that is how one would return a phone to stock.. to be honest, the safest thing to do would be to unlock the bootloader, flash a rom, S-OFF and then return it to stock. If these seem like foreign terms to you, you have a lot of reading to do. Your phone is in a tough spot right now ESPECIALLY not knowing the history regarding what was done. You would need the bootloader unlock token to reunlock that phone if you don't have it, there's very little chance of safely returning that phone to stock.
pvirus86 said:
yes i asked my brother and he is saying he doesnt remember what he had done to it...
Click to expand...
Click to collapse
Brother or cousin, or both? It seems you don't even know who has been messing with your phone. And the person(s) messing with it don't have a clue what they are doing. So its no wonder the phone is in the state it is.
Agree with above that RUU is risky. Better to s-off the phone first.
Thank u all for the prompt replies, I have played with Samsung but not with HTC. But I can try to unlock the bootloader n turn d s-off. Can I get an step guide for HTC. The thing was I have many cellphone that I buy and use it very rarely. Majority I use is my note 3.
pvirus86 said:
Thank u all for the prompt replies, I have played with Samsung but not with HTC. But I can try to unlock the bootloader not turn d s-off. Can I get an step guide for HTC. The thing was I have many cellphone that I buy and use it very rarely. Majority I use is my note 3.
Click to expand...
Click to collapse
There are detailed instructions available at htcdev for unlocking your bootloader. Once you've done that you need to flash a custom recovery, then you can flash root, then you can get s-off. Check my How-To Guide For Beginners thread, the link is in my signature.
Sent from my Evita
pvirus86 said:
Thank u all for the prompt replies, I have played with Samsung but not with HTC. But I can try to unlock the bootloader n turn d s-off. Can I get an step guide for HTC. The thing was I have many cellphone that I buy and use it very rarely. Majority I use is my note 3.
Click to expand...
Click to collapse
Every device manufaccturer/model has different root methods. If you want to root the phone, you have to put the time in to learn the correct process. There is no shortcut. You won't find a step-by-step guide for the entire process, because of the different carrier version and firmware updates (root method, etc. differs for each). But all the resources you need are sticky at the top of either this Q&A forum section, or General section.
hi i tried to get to unlock the bootloader from the HTCDEV site. first of all the HTC ONE X wasnt on the list so i selected other supported devices
then followed the steps and got the following error
Error Code: 160.
Error Reason: MID Not Allowed.
now what does this mean??
That means you have the original CID still, which means you should be able to run the 3.18 RUU without any problems. Check your CID by issuing this fastboot command:
Code:
fastboot oem readcid
Sent from my Evita
yes i had issued this command after finding it in one of the websites and this was the result which i got
cid: CWS__001
or cid: c??__001
i forgot the exact two letter after C. i think it was CWS
You have the original at&t CID. That means you can run the 3.18 RUU without having to unlock the bootloader and get s-off first.
Sent from my Evita
Plzzz help!!!!!!!!!!!!!!!!!!!!!!
you can't
K.V.K said:
Plzzz help!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
well my friend sry but you can't restore this code
most of devices like samsung,motorola etc they have.... lets say a key for the bootloader(is the door) and this key if you root your device
breaks and the half key stays inside the door hole to reminds you that the key is broken(the devicesis root/unlockbootloader).
so if you root any motorola device the code state goes
automatically 2 and stays like this,you can flash again the stock rom and relock the bootloader sure
but the code stays 2 for ever.
i hope to help you
moto g XT1541 stock rom 6.0.1 lockbootloader
bromoxitos said:
well my friend sry but you can't restore this code
most of devices like samsung,motorola etc they have.... lets say a key for the bootloader(is the door) and this key if you root your device
breaks and the half key stays inside the door hole to reminds you that the key is broken(the devicesis root/unlockbootloader).
so if you root any motorola device the code state goes
automatically 2 and stays like this,you can flash again the stock rom and relock the bootloader sure
but the code stays 2 for ever.
i hope to help you
moto g XT1541 stock rom 6.0.1 lockbootloader
Click to expand...
Click to collapse
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
yeap
acejavelin said:
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
Click to expand...
Click to collapse
YEAAA we say the same think,but i use an othey way to say it.
i say in the end you can relock the bootloader (more or less) when i say this i mean that you put some partitions back in boot loader
so when you flash the stock rom you can take any ota update,but the main bootloader is unlock always.
i know that form my old moto g2gen, moto x2013!!!
bromoxitos said:
YEAAA we say the same think,but i use an othey way to say it.
i say in the end you can relock the bootloader (more or less) when i say this i mean that you put some partitions back in boot loader
so when you flash the stock rom you can take any ota update,but the main bootloader is unlock always.
i know that form my old moto g2gen, moto x2013!!!
Click to expand...
Click to collapse
You could relock the bootloader on older Motos, but not anymore... Actually, it can be relocked but it will never report as locked or relocked, it will always be reported as unlocked. I don't how to be more plain in describing this.
And yes, you can take an OTA when unlocked, as long as you have a stock ROM and recovery and your bootloader is the correct version for your ROM. If your bootload and ROM are out of sync (ie. you have a Marshmallow bootloader and a Lollipop ROM), if your bootloader and ROM are out of sync, you could potentially get into a hard bricked situation.
ohh!!
acejavelin said:
You could relock the bootloader on older Motos, but not anymore... Actually, it can be relocked but it will never report as locked or relocked, it will always be reported as unlocked. I don't how to be more plain in describing this.
And yes, you can take an OTA when unlocked, as long as you have a stock ROM and recovery and your bootloader is the correct version for your ROM. If your bootload and ROM are out of sync (ie. you have a Marshmallow bootloader and a Lollipop ROM), if your bootloader and ROM are out of sync, you could potentially get into a hard bricked situation.
Click to expand...
Click to collapse
not any more? damn....yea we say the same think,sry for my english,yea i khow what you talking about i brick my moto x like this!!! any way.
ty for the new info about bootloader.
you was 100%
were you a clear,thanks a lot,and i hope to help him
Once I sent my hard bricked phone to Motorola. I had unlocked the bootloader and done the stupid mistake of sideloading an older version and upgrading to a newer, but still older version. When it came back, it said it was Status Code 0.
Wonder how they did it.
yagyaxt1068 said:
Once I sent my hard bricked phone to Motorola. I had unlocked the bootloader and done the stupid mistake of sideloading an older version and upgrading to a newer, but still older version. When it came back, it said it was Status Code 0.
Wonder how they did it.
Click to expand...
Click to collapse
They flash the eMMC chip (internal storage chip) directly... If you could get the right image you could possibly do it yourself with a few hundred to thousand dollar investment in a proper JTAG flashing unit.
Key would be getting the right Image, this would be far more than just a normal stock fastboot image, and is probably generated on the fly per device due to differences in serial number, IMEI, etc. These types of images don't get leaked out.
acejavelin said:
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
Click to expand...
Click to collapse
ok so what if you have never root unlocked, did nothing but use as intended to be.. never trying to do anything to it. wtf would i have a code 2 status then? care to sum that up for me.. cause 100% my situation.
wiytboi said:
ok so what if you have never root unlocked, did nothing but use as intended to be.. never trying to do anything to it. wtf would i have a code 2 status then? care to sum that up for me.. cause 100% my situation.
Click to expand...
Click to collapse
You unlocked the bootloader... It doesn't matter if you actually changed anything else or not. Once it's been done, this status code can never go back to 0. If the status code is 2 and you didn't unlock the bootloader, then someone else did.
acejavelin said:
You unlocked the bootloader... It doesn't matter if you actually changed anything else or not. Once it's been done, this status code can never go back to 0. If the status code is 2 and you didn't unlock the bootloader, then someone else did.
Click to expand...
Click to collapse
No I didn't.. I don't even know how to.. I just found out about recovery mode.. Wait wait before i say that.. How do you unlock boot loader? Turning developer mode on? Going to recovery menu? I've never hard reset it.. Just soft or doing new device. You said it could work fine for a while then shirt out? Like guy I bought from did and then I bought used for couple years and then went tits up?
wiytboi said:
No I didn't.. I don't even know how to.. I just found out about recovery mode.. Wait wait before i say that.. How do you unlock boot loader? Turning developer mode on? Going to recovery menu? I've never hard reset it.. Just soft or doing new device. You said it could work fine for a while then shirt out? Like guy I bought from did and then I bought used for couple years and then went tits up?
Click to expand...
Click to collapse
You unlock the bootloader with a series of steps that includes submitting a code to Motorola and getting an unlock code back... Performing it forces a factory reset as well. It's not something you can do by accident.
The issue with Status Code 2 was that an official update could have detected that and refused to update properly or done something worse... That never happened.
If everything is working fine, the status being 2 isn't important, it just means the previous owners had unlocked the bootloader and likely rooted or otherwise modified the phone.
Hey everyone,
I got my new Honor 8 and as with my previous OnePlus One I just need root.
It's not that complicated to find descriptions how to unlock the bootloader (and loose the warranty), relock it and even get the "locked" status again without (https://forum.xda-developers.com/showpost.php?p=70177996&postcount=7) and with DC Unlocker (https://www.dc-unlocker.com/how-to-lock-bootloader-from-relocked-to-locked) in case I understood everything right.
But the important qustion of course is if one (for example Huawei) can see that its relocked. So first, what does it say if you get the status over the command prompt? And even if it's "locked" there is there any other way you can see?
I don't expect a warranted answer but maybe someone who is firm with android coding or what ever can at least say what he thinks?
Thanks a lot!
If you relock it with a fastboot command then yeah. But if you use a rollback package to return to emui 4.1, everything gets wiped in a way that makes the bootloader status "locked"
Could please someone at least check the first question with his unlocked phone?
Edit: Didn't see your reply and don't now how to delete mine... Thanks anyway!
sysak said:
If you relock it with a fastboot command then yeah. But if you use a rollback package to return to emui 4.1, everything gets wiped in a way that makes the bootloader status "locked"
Click to expand...
Click to collapse
That means after unlocking bootloader and relock bootloader with these steps, i have back my warranty?
Sorry for my bad english..
Silencer3007 said:
That means after unlocking bootloader and relock bootloader with these steps, i have back my warranty?
Sorry for my bad english..
Click to expand...
Click to collapse
As far as i know yeah, unless there is some secret way for them to know it. If you unlock the bootloader with a code and then lock it again it will show the bootloader status as "relocked" in fastboot mode, indicating that the device was tampered with in the past. But the "locked" status you get in the rollback process is the same as on a phone that was never modified. I found this "trick" accidentally when restoring a bricked phone using the rollback package and think it's pretty handy.
sysak said:
As far as i know yeah, unless there is some secret way for them to know it. If you unlock the bootloader with a code and then lock it again it will show the bootloader status as "relocked" in fastboot mode, indicating that the device was tampered with in the past. But the "locked" status you get in the rollback process is the same as on a phone that was never modified. I found this "trick" accidentally when restoring a bricked phone using the rollback package and think it's pretty handy.
Click to expand...
Click to collapse
Not sure if u'll read this. When I was stuck in the same issue somewhere around July 2017 I was devastated and thought if I were to relock my bootloader how to do so without it saying relocked (If you do it by fastboot it will 100% say so). I tried the rollback method on seeing this and u sure r right. It says LOCKED and looks as though my phone was never tampered with ?.
I came across this thread researching abt something and though I'd thank you!
Sent from my Honor 8 using XDA Labs
I lock bootloader on Verizon Google Pixel when my device have TWRP and i have brick! Device Loading up to logo Google on 1 sec and reboot. Fastboot work, but i don't unlock bootloader. In recovery is don't enter. Please help me!
https://forum.xda-developers.com/pixel/how-to/psa-read-relocking-bootloader-t3494614 ....very important advice. With my limited knowledge NEVER relock unless you have signed OEM images correctly reloaded into device before locking.
kkjb said:
https://forum.xda-developers.com/pixel/how-to/psa-read-relocking-bootloader-t3494614 ....very important advice. With my limited knowledge NEVER relock unless you have signed OEM images correctly reloaded into device before locking.
Click to expand...
Click to collapse
There is still no solution to this problem? ((
Unlock again.
lafester said:
Unlock again.
Click to expand...
Click to collapse
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"
Groh12 said:
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"
Click to expand...
Click to collapse
Put the phone in fastboot mode, then run `fastboot flashing unlock` from a PC. If it says unlocking not allowed, you're out of luck, it's a brick now. Never lock your phone without being 100% stock on both slots
Groh12 said:
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"
Click to expand...
Click to collapse
No idea. I've never relocked unless I am completely stock and take at least one ota first to make sure, along with full factory resets before and after updating.
There are others here that claim they where able to unlock again and save their phones though so maybe it's possible.
lafester said:
No idea. I've never relocked unless I am completely stock and take at least one ota first to make sure, along with full factory resets before and after updating.
There are others here that claim they where able to unlock again and save their phones though so maybe it's possible.
Click to expand...
Click to collapse
In this topic https://forum.xda-developers.com/pi...bootloader-t3540772/post77016940#post77016940 man has unbrick Pixel XL, but i think that method will work on Pixel.