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.
Hi, I am another noob on this forum and I have been looking around for a root for my htc one xl which was updated to the latest software version: 2.40.841.4.
I tried to unlock the bootloader through htcdev.com but it does no recognise the device after going through all those steps.
Can anyone please tell me how I can do this if it is possible. If not, is there anything I can do? I really badly want to root my device.
Thanks
Device info:
Career: Telstra
Android version: 4.0.4
Software version: 2.40.841.4
infectedprof said:
Hi, I am another noob on this forum and I have been looking around for a root for my htc one xl which was updated to the latest software version: 2.40.841.4.
I tried to unlock the bootloader through htcdev.com but it does no recognise the device after going through all those steps.
Can anyone please tell me how I can do this if it is possible. If not, is there anything I can do? I really badly want to root my device.
Thanks
Device info:
Career: Telstra
Android version: 4.0.4
Software version: 2.40.841.4
Click to expand...
Click to collapse
Did you use X-Factor root exploit to change your CID first?
He doesn't have to xfactor
Sent from my HTC One X using xda app-developers app
ImagioX1 said:
Did you use X-Factor root exploit to change your CID first?
Click to expand...
Click to collapse
Yep I tried that, but it just recognise the device. I installed htc sync and stopped all the background processes. Yet it's still not working.
area51avenger said:
He doesn't have to xfactor
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
What should I do then?
Thanks
change your cid back maybe? since only the at&t htc one xl needs to do supercid.
DvineLord said:
change your cid back maybe? since only the at&t htc one xl needs to do supercid.
Click to expand...
Click to collapse
How would I accomplish that?
Doesn't all he have to do is unlock his bootloader through HTCdev.com he has a good cid not att one so it'll work than he can flash a recovery than flash a Rom than have root
omario8484 said:
Doesn't all he have to do is unlock his bootloader through HTCdev.com he has a good cid not att one so it'll work than he can flash a recovery than flash a Rom than have root
Click to expand...
Click to collapse
Yes.
I suggest the OP try to re-install the HTC drivers, try a different USB port, even a different computer, if possible.
redpoint73 said:
Yes.
I suggest the OP try to re-install the HTC drivers, try a different USB port, even a different computer, if possible.
Click to expand...
Click to collapse
Sorry for the very late reply, but I did install all the drivers correctly. Tried it on my linux laptop and windows desktop, but still no success. I read all steps clearly to. But nothing is happening
And again I am on the latest software. I coincidently updated it when I received it without knowing there will be no root or exploits available for the software version yet.
Oh keep in mind that I am updated to the latest default software update.
infectedprof said:
And again I am on the latest software. I coincidently updated it when I received it without knowing there will be no root or exploits available for the software version yet.
Click to expand...
Click to collapse
I think you are still misunderstanding. No exploit is needed for any version of this phone aside from the US AT&T version.
All you need to do is unlock the bootloader, than either flash SU or flash a rooted ROM, in order to get root.
If you are having problems unlocking the bootloader, try a different USB port, and keep trying. I believe some folks have had to do it several times in order to get it to unlock.
Is adb able to see the device at all?
It is evident that the OP needs to read the tutorials that are available more closely.
1. Before you proceed any further, please make sure (130%) that your ADB and Android SDK folders are configured and set up properly. If those aren't set up properly, then you cannot proceed any further. Good way to check is to type in "adb devices" when you think you have everything set up.
2. Go to HTCDev.com and follow the instructions there closely. Read them first, print them, read them again, then execute it step by step. This will allow you to get your unlock token to have your bootloader unlocked. Remember, this will void your warranty.
3. Once you're unlocked, go to TWRP's homepage and download the latest version of TWRP. Do not use CWM as it is not recommended for the HOXL. Once you have that, push it to your device through fastboot to have a custom recovery.
4. Find a ROM that is compatible with the HOXL and flash through recovery. Remember to make a backup of your current stock ROM, in case you need it later.
Those are the steps in a nutshell. Again, keep reading and asking questions if you don't understand something. As long as they're educated questions, you shouldn't get any flak from the members here . Good luck!
I tried that and adb does not come up with any recognised devices.
infectedprof said:
I tried that and adb does not come up with any recognised devices.
Click to expand...
Click to collapse
As long as the usb port on your computer is picking up the phone, this usually indicates that your drivers aren't up-to-date. Try running HTC Sync again to make sure there aren't any new drivers or even check for a newer version of HTC Sync.
It says that all my drivers are up to date already.
You can use www.htcdev.com now, I just unlocked my bootloader yesterday
Cthdarren said:
You can use www.htcdev.com now, I just unlocked my bootloader yesterday
Click to expand...
Click to collapse
I'm sure he was waiting a few months for you to confirm that for him
Sent from my HTC One XL
How do these people even dig these threads out
Hello Everyone-
My apologies but, after reading page upon page of information, I am just more confused.
Has anyone found a method to unlock this bootloader yet - if even temporarily ?
All these terms ( TWRP, CWM, AOSP, etc.) just have my head spinning.
I am able to follow the steps to these processes, I just need to know which ones to follow.
Any help will be appreciated.
Thanks
Hell-On-Wheels said:
Hello Everyone-
My apologies but, after reading page upon page of information, I am just more confused.
Has anyone found a method to unlock this bootloader yet - if even temporarily ?
All these terms ( TWRP, CWM, AOSP, etc.) just have my head spinning.
I am able to follow the steps to these processes, I just need to know which ones to follow.
Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
The section for the model mentioned that you are looking for is in http://forum.xda-developers.com/moto-g/4g-development
If you find it all confusing at this point, I'd recommend the use of http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710 for now.
Is this toolkit standalone ?
Somcom3X -
Thanks for the direction. If I use your toolkit, does it contain everything needed ? Can I disregard the other programs/files I dl'd in previous unlocking attempts - for example :adb tools treiber, Android Studio, etc.
I gave it a quick test, but my device never appears. This is what I see :
Your device is:
If this is incorrect please exit this program
Press any key to continue . . .
The phone is in fastboot mode, USB debugging on. I previously installed the ADB drivers w/i the toolkit. Do I also need to run (m)fastboot, as well ?
What am I missing here ?
Hell-On-Wheels said:
Somcom3X -
Thanks for the direction. If I use your toolkit, does it contain everything needed ? Can I disregard the other programs/files I dl'd in previous unlocking attempts - for example :adb tools treiber, Android Studio, etc.
I gave it a quick test, but my device never appears. This is what I see :
Your device is:
If this is incorrect please exit this program
Press any key to continue . . .
The phone is in fastboot mode, USB debugging on. I previously installed the ADB drivers w/i the toolkit. Do I also need to run (m)fastboot, as well ?
What am I missing here ?
Click to expand...
Click to collapse
Could you try using a different USB port/computer? All of the commands have been automated.
Phone was recognized, program went thru the motions but..
Command prompt did what it was supposed to do, but it still asked to enter unlock code from Motorola site. I just continued hitting any key to continue. Bootloader still locked. What now ?
Hell-On-Wheels said:
Command prompt did what it was supposed to do, but it still asked to enter unlock code from Motorola site. I just continued hitting any key to continue. Bootloader still locked. What now ?
Click to expand...
Click to collapse
You need the unlock code from the Motorola site. You'll be better off replying in that thread for the toolkit.
Somcom3X said:
You need the unlock code from the Motorola site. You'll be better off replying in that thread for the toolkit.
Click to expand...
Click to collapse
I thought that this toolkit did away with that requirement. As I mentioned in my OP, I am working with a Cricket XT1045. Motorola does not give out unlock codes for these versions.
I will post in that other thread if anyone has found a workaround.
Thanks
Without an unlock code, your pretty much on your own. However, this might work in your case: http://forum.xda-developers.com/showthread.php?t=2792487
Using Windroid 3.1 to unlock moto g 2015 osprey, drivers installed and works perfectly on wife phone. On trying to unlock my phone i get error message.
Houston, we have a problem
An error has occured! a log file has been placed in the Logs folder.
The same error occurs whether oem locking is on or not. Also i am having communication fails when using fastboot, yet the phone is recognised and read to but not written.
Where would i find this log file please and any help offered i would be grateful.
bantamroberts said:
Using Windroid 3.1 to unlock moto g 2015 osprey, drivers installed and works perfectly on wife phone. On trying to unlock my phone i get error message.
Houston, we have a problem
An error has occured! a log file has been placed in the Logs folder.
The same error occurs whether oem locking is on or not. Also i am having communication fails when using fastboot, yet the phone is recognised and read to but not written.
Where would i find this log file please and any help offered i would be grateful.
Click to expand...
Click to collapse
Try adb and fastboot instead of Windroid
As I tried to explain in my post , this is not possible as the phone will not write the data sent. Thinking this is why windroid returns an error.
bantamroberts said:
As I tried to explain in my post , this is not possible as the phone will not write the data sent. Thinking this is why windroid returns an error.
Click to expand...
Click to collapse
Did you enable OEM Unlocking the Developer Options menu? Still required...
I would also recommend doing it manually, the commands are easy and the process is simple... if something goes wrong you can see exactly what fails. Tools like Windroid are not really useful for simple tasks like this.
done oem unlock in developer options but not manually as im unsure how. please elaborate.
bantamroberts said:
done oem unlock in developer options but not manually as im unsure how. please elaborate.
Click to expand...
Click to collapse
Gotta be 50 tutorials on-line, there is only one real, official way...
You need at least fastboot (you can get it from Minimal ADB & Fastboot)
Then follow the Moto official method which even using a tool you have to go through anyway to get the tokem
acejavelin said:
Gotta be 50 tutorials on-line, there is only one real, official way...
You need at least fastboot (you can get it from Minimal ADB & Fastboot)
Then follow the Moto official method which even using a tool you have to go through anyway to get the tokem
Click to expand...
Click to collapse
Done this, error message failed to get unlock data. remote failure.
bantamroberts said:
Done this, error message failed to get unlock data. remote failure.
Click to expand...
Click to collapse
So you have OEM Unlocking enabled in Developer Options and fastboot is still complaining?
What model and variant? Is this a carrier locked phone or a Moto retail version?
Sent from my MotoG3 using Tapatalk
acejavelin said:
So you have OEM Unlocking enabled in Developer Options and fastboot is still complaining?
What model and variant? Is this a carrier locked phone or a Moto retail version?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
its a xt1541 on tesco mobile and unlocked with sim code.
I can't find anything definitive about whether it's rootable or not
Same here i tried every root app possible and failed.
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
No need to flash TWRP: Booting into it is sufficient.
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
How did you unlock the bootloader?
sCriptKittY1987 said:
How did you unlock the bootloader?
Click to expand...
Click to collapse
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
Where did you find a tarp img for the LG k51?
sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
tarp image????? just follow the tutorial.
I meant TWRP recovery . After you've unlocked the bootloader where did you get a custom recovery to flash for the LG k51. From what I saw on Team Wins website, there isn't one.
Bhanu8082 said:
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Click to expand...
Click to collapse
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
sCriptKittY1987 said:
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
Click to expand...
Click to collapse
I doubt that's going to work, but let me know if it does. Carriers and manufacturers use a variety of sophisticated security schemes like requiring lengthy codes that only they can provide, etc to purposely make it very difficult to unlock bootloaders. Tmobile gave me a K51 for free. They apparently feel the have to pay for it by spying on me. I bought a moto g7 plus unlocked for $117 directly from Moto and put Lineage on it, no gapps Would love to use thie k51 though if anyone figures it out because it's more waterproof and bigger battery.
mgsgta3 said:
I can't find anything definitive about whether it's rootable or not
Click to expand...
Click to collapse
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
and let me guess my doofus luck im guessing no way to unlock it with out a P.C. like nuttin at all?
Absolutely no of the crap above works at all in any capacity especially sprint. Generic postings like hold volume down and power also doesn't work to go into fastboot so if you guys are following the advice of some of these guys don't because you'll drop more money on a new phone then you will unlocking it some variants verizon is one I think you have to call LG I know I spent 6 hrs on the phone with "tech support" aka "jokes with a screen to read from" to FINALLY get into touch with an engineer who told me the only way "NOW" to unlocked the bootloader is in his office which means it has to be depot to be unlocked which as of this moment lg is not doing that WILL change in the future that was 12/03/2020. Even running external adb with kali linux to hack it broke the bootloader and sends you into an infinite reboot loop
jwoegerbauer said:
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
Click to expand...
Click to collapse
This returns no value on a locked bootloader because even with Dev. Opt. Enables its still read only until bootloader is unlocked this is verified on two carriers k51's sprint and att. However it is unlockable we haven't found it and/or LG has not added this service to their site which is where you will get the info needed for the unlocked.
Oh my. You know you need to do all this from a computer, right? Can't do it in an Android terminal because fastboot commands are only valid in a phone's bootloader environment. And if you didnt know that then rooting and all of the dangers that come with it just isnt for you. But yes, it's rootable. So here you go anyway.
Reboot the phone to download mode.
Install LG's K51 usb drivers, and install adb and fastboot, on your computer.
Open a command prompt and type: fastboot oem unlock
If it does anything other than pat you on the back and tell you it's proud of you and how well you follow instructions, then go back and follow the effing instructions.
Otherwise, type: fastboot reboot.
Download magisk manager.
Do the magisk manager.
Use the LG flash tool on your computer to flash what you just did when you did the magisk manager.
And presto, you're rooted. Or I successfully left out enough info and you dont know how to use Google, leaving your device still not rooted. And thank god for that.
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Kenwoodquality69 said:
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Click to expand...
Click to collapse
Yo Ken,
So your K51 rooted?
If so, maybe you could provide a step by step?
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
TexasPride said:
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
Click to expand...
Click to collapse
O lord i hope this isnt true