Link To Main Thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About
The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!
Download
WinDroid Toolkit
Changelog
Check out this document for current and past changelogs.
Supported Devices
Check out this spreadsheet for a list of currently supported devices.
Device not supported? Make a request here!
Contribute
Check out the source code on GitHub here.
Disclaimers
Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.
I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.
Reserved
Reserved.
Can your toolkit S-off One E8 ??
Thanks for the toolkit
this will definately help the e8 users. I have already unlocked bootloader and rooted so cant test that. will try to install kernel later with your toolkit
iamsuperuser said:
Can your toolkit S-off One E8 ??
Click to expand...
Click to collapse
The toolkit doesn't support S-OFF, but I'm looking at adding support for it in the future. I don't think the E8 has an official S-OFF method right now though, unless SunShine or Firewater work.
WindyCityRockr said:
The toolkit doesn't support S-OFF, but I'm looking at adding support for it in the future. I don't think the E8 has an official S-OFF method right now though, unless SunShine or Firewater work.
Click to expand...
Click to collapse
Sunshine works
Sent from my HTC One_E8 dual sim using XDA Free mobile app
not able to unlock bootloader
only a window opens up in my pc saying that bootloader is unlocked. otherwise, no prompt comes in my phone to unlock the bootloader. it says "locked" in bootloader mode.
WinDroid Universal Android Toolkit v2.1 Now Out!
I'm happy to announce that the WinDroid Universal Android Toolkit v2.1 update is now out! It's a complete code rewrite, with new features and support for 17 new devices! As always, reply with any comments you have or issues you're facing, and Happy Holidays to all!
Good day, if you include the item get s-off this is the first free tool like a Swiss army knife (all in one). And most importantly free.
s-off - htc one e8
Edit: Nvm.
When will be included s-off e8?
WinDroid Universal Android Toolkit v2.3 Now Out!
I'm happy to announce that the WinDroid Universal Android Toolkit v2.3 update is now out! It includes a bunch of new features, fixes and supported devices, so check it out and let me know what you think! :fingers-crossed:
You can download it here.
i have lost recovery
it seems i have lost recovery mode. i can only open fastboot but can not get into recovery mode. can you please help?
WinDroid Universal Android Toolkit v2.5 Now Out!
I'm happy to announce that the WinDroid Universal Android Toolkit v2.5 update is now out! As always, let me know what you think and report any bugs you encounter! :highfive:
You can download it here.
WinDroid Toolkit v3.0 Is Now Out!
WinDroid Toolkit v3.0 has been released! It's a huge update with a material redesign, major recode and support for 43 new devices!
You can out more specific changes in the changelog here.
You can download the new update here.
All versions before v3.0 will not have their files updated anymore since I've moved from hosting on BasketBuild to Amazon S3. Please update to v3.0 to ensure you're getting the latest recovery and root files!
HTC ONE E8 Sprint help
hi to all,
i try to unlock bootloader with this tool but when i choose the unlock_code.bin file that HTC send me, the device doesn't ask me anything. Windroid shows me a message for some seconds that says something like "your device will show a message asking for unlock. with volume button choose yes..." but the device continue shows only the fastboot usb screen.
After a few seconds windroid says that the operation was successfully and i can go to the step 2 (flash twrp).
I try to flash it but nothing happens (windroid shows a successfull message). If i reboot in recovery there is not twrp but the original one.
the fastboot screen continue to show the "locked" banner on top.
I'm already s-off with root permission, The device has android 4.4.2 on board (software version number 1.22.681.1).
any ideas?
Thanks and have a nice day.
fulrosa said:
hi to all,
i try to unlock bootloader with this tool but when i choose the unlock_code.bin file that HTC send me, the device doesn't ask me anything. Windroid shows me a message for some seconds that says something like "your device will show a message asking for unlock. with volume button choose yes..." but the device continue shows only the fastboot usb screen.
After a few seconds windroid says that the operation was successfully and i can go to the step 2 (flash twrp).
I try to flash it but nothing happens (windroid shows a successfull message). If i reboot in recovery there is not twrp but the original one.
the fastboot screen continue to show the "locked" banner on top.
I'm already s-off with root permission, The device has android 4.4.2 on board (software version number 1.22.681.1).
any ideas?
Thanks and have a nice day.
Click to expand...
Click to collapse
hi, I solved it few minutes ago using windroid and unlock_code.bin in a 'simple nested' folder like c:\windroid
In this 'simple' folder works good also adb and fastboot command.
hope this hint can help...
have a nice day.
fulrosa said:
hi, I solved it few minutes ago using windroid and unlock_code.bin in a 'simple nested' folder like c:\windroid
In this 'simple' folder works good also adb and fastboot command.
hope this hint can help...
have a nice day.
Click to expand...
Click to collapse
Sent from my HTC One E9s dual sim using XDA Labs
---------- Post added at 11:11 PM ---------- Previous post was at 11:09 PM ----------
Sent from my HTC One E9s dual sim using XDA Labs
Related
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016
I was surprised to not find this information in any of the forums.
This is why I'm posting this thread to prevent further confusion and future xda-enthusiastic "Phone Buyers" from Oppo's decision.
Oppo has of this year decided to "lock the access to its Bootloader".
By "access" i mean no way to access it with "adb reboot fastboot" and "adb reboot bootloader" and any "Bootup Button combination".
Its not only hitting new phones but also old phones.
All the latest ColorOS Firmwares will prevent you from accessing the Bootloader.
All Project Spectrum alpha/beta's for OLD and NEW phones will prevent you from accessing the Bootloader.
If you are using a custom rom and want to try out any of the above stock roms. Be !WARNED! you will lose access to the Bootloader!
They not only removed the access to the Bootloader but also removed the "fastboot binarys" itself.
If by chance you are able to access the Bootloader and want to use fastboot commands. All commands will result in "FAILED (remote: unknown command)"
I noticed this and raised questions in the official Oppo forum:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is the official reply:
I hope this helps enthusiastic users in their "phone choice".
For me access to the Bootloader and having fastboot commands are on top of the list when it comes to choosing a new phone.
Update:
It seems like that Oppo decided to bring back fastboot and the possibility to unlock the bootloader in their "Project Spectrum" ROM.
But apparently not in all devices!
ColorOS (The Stock ROM) is unaffected and remains with a defunct fastboot. Confirmed by Oppo R9 Plus users. Which is Oppo's latest Qualcomm based phone.
Thank God i didn't upgrade !
You can unlock the bootloader and access the fastboot by downloading the old version of the ColorOS.
Thanks.
Mulham82 said:
You can unlock the bootloader and access the fastboot by downloading the old version of the ColorOS.
Thanks.
Click to expand...
Click to collapse
this is only true for devices which had firmware releases in 2015. my Oppo R7S (European Version) for example was already shipped with a firmware that is hit by their new strategy. no old firmware to unlock the bootloader or access fastboot.
celoxocis said:
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016
I was surprised to not find this information in any of the forums.
This is why I'm posting this thread to prevent further confusion and future xda-enthusiastic "Phone Buyers" from Oppo's decision.
Oppo has of this year decided to "lock the access to its Bootloader".
By "access" i mean no way to access it with "adb reboot fastboot" and "adb reboot bootloader" and any "Bootup Button combination".
Its not only hitting new phones but also old phones.
All the latest ColorOS Firmwares will prevent you from accessing the Bootloader.
All Project Spectrum alpha/beta's for OLD and NEW phones will prevent you from accessing the Bootloader.
If you are using a custom rom and want to try out any of the above stock roms. Be !WARNED! you will lose access to the Bootloader!
They not only removed the access to the Bootloader but also removed the "fastboot binarys" itself.
If by chance you are able to access the Bootloader and want to use fastboot commands. All commands will result in "FAILED (remote: unknown command)"
I noticed this and raised questions in the official Oppo forum:
this is the official reply:
I hope this helps enthusiastic users in their "phone choice".
For me access to the Bootloader and having fastboot commands are on top of the list when it comes to choosing a new phone.
Click to expand...
Click to collapse
Thanks for the info, it´s something to keep in mind certainly.
Thank you for your effort in this. Any process on the r7s front?
Website signature
Yes , I got caught out by this
I purchased my R7s due to Oppo's previously root friendly attitude only to find I could not root when I had updated my phone to the latest version
I have expressed my displeasure to Oppo
this is exactly what happened to me when I purchased the R7S. I did my research before purchase and saw that all previous Oppo phones were unlockable using fastboot. when I bought the phone. fastboot binarys were removed in LK.
there has been alot of effort by xda-dev's to find a way to unlock the affected phones.
I can only say this much. a way has been found. which was used to put pressure on Oppo including all the incoming complains.
Im a project Spectrum beta tester and the good news is. that the project Spectrum beta roms have fully working fastboot binarys. which will allow an bootloader unlock.
if you look in the Oppo forum. you will see that I provided an official TWRP and am currently working on a CyanogenMod.
no need to give up or to pass on this mid-ranger at all. just patients
is there really no way to root the phone? i don't understand Chinese and in the original way i can't use the OPPO R9 Phone
If anyone can point me towards where to find older R7 PlusF firmware that would be great. Doesn't seem to be listed on oppo website anymore.
"R7plusfEX_11_OTA_005_all_201508180100"
Is available by host server aborts download at 100mb/1.3gb
Looks like I missed out this thread... Only recently I discovered such situation at Oppo forum. Very disappointed by this...
is there any way for unlocking fastboot for oppo a37 which only has coloros3.0.0 rom?
hamzachaudhry36 said:
is there any way for unlocking fastboot for oppo a37 which only has coloros3.0.0 rom?
Click to expand...
Click to collapse
Have you checked if you have fastboot access at all? Install minimal adb & fastboot enable debugging mode in developer options and issue the command "adb reboot fastboot".
If the phone simply reboots then Oppo has not included fastboot binarys for your device.
celoxocis said:
Have you checked if you have fastboot access at all? Install minimal adb & fastboot enable debugging mode in developer options and issue the command "adb reboot fastboot".
If the phone simply reboots then Oppo has not included fastboot binarys for your device.
Click to expand...
Click to collapse
Yeah phone simply reboots but is there any solution for flashing new fastboot bunarys on my device
hamzachaudhry36 said:
Yeah phone simply reboots but is there any solution for flashing new fastboot bunarys on my device
Click to expand...
Click to collapse
No unless an older ROM version had it and it was removed with an upgrade.
Try reverting to the oldest ROM version you can find and try again.
celoxocis said:
No unless an older ROM version had it and it was removed with an upgrade.
Try reverting to the oldest ROM version you can find and try again.
Click to expand...
Click to collapse
The problem is my phone got out with latest rom version .....
Is there any way to port fastboot binarys from some other rom to mine ....?????
There is a phone named Xaomi 2 Prime which has same specs(GPU, CPU and RAM) is there a way to port those files ....??
hamzachaudhry36 said:
The problem is my phone got out with latest rom version .....
Is there any way to port fastboot binarys from some other rom to mine ....?????
There is a phone named Xaomi 2 Prime which has same specs(GPU, CPU and RAM) is there a way to port those files ....??
Click to expand...
Click to collapse
NO!!! You will brick your phone!
Different manufacturer totally different signature's!
There is no way! Because Oppo locked it down!
You should have done research before buying a phone. If you wanted root, Xposed, custom ROM, etc
celoxocis said:
NO!!! You will brick your phone!
Different manufacturer totally different signature's!
There is no way! Because Oppo locked it down!
You should have done research before buying a phone. If you wanted root, Xposed, custom ROM, etc
Click to expand...
Click to collapse
Yeah i just bought it cuz people said it is the best phone in medium budget... and it is popular....
but if anything happens to my phone i won't be able to install even stock rom in it with PC....
can i atleast port twrp for my device to get root and randroid backup functions which i really want...?????
hamzachaudhry36 said:
Yeah i just bought it cuz people said it is the best phone in medium budget... and it is popular....
but if anything happens to my phone i won't be able to install even stock rom in it with PC....
can i atleast port twrp for my device to get root and randroid backup functions which i really want...?????
Click to expand...
Click to collapse
NO! Again! for TWRP to work you need an unlocked bootloader which you don't have and can't have because of Oppo removing fastboot!
Return your phone and get a different phone.
Avoid Oppo at all costs!
I suggest Asus Zenfone 2 it has all you want and even official CyanogenMod support!
It's close to the specifications of the a37f.
https://wiki.cyanogenmod.org/w/Z00L_Info
And stop using so many questions marks!
It only makes you look stupid.
celoxocis said:
NO! Again! for TWRP to work you need an unlocked bootloader which you don't have and can't have because of Oppo removing fastboot!
Return your phone and get a different phone.
Avoid Oppo at all costs!
I suggest Asus Zenfone 2 it has all you want and even official CyanogenMod support!
It's close to the specifications of the a37f.
https://wiki.cyanogenmod.org/w/Z00L_Info
And stop using so many questions marks!
It only makes you look stupid.
Click to expand...
Click to collapse
Thanks but it won't be refunded in my country. So i am stuck. I can get Samsung J5 2015 which is rooted and has many functions which i like from my brother in exchange of it but Oppo provides many functions which samsung does not like Oppo has almost no bloatwares, Built-in app locker, more ram, 4G, built-in customizations, and a camera that is the best.
Thanks for all the help. I just wanted to confirm, my friend said that we can make a port of twrp so i asked.
and i am an idiot and a noob so i use many question marks sometimes
Hey guys
Bought the 64 GB version yesterday, vitals are as follows
Moto turbo
Xt1225
Android 5.0.2 (took a small OTA maybe like 90mb, now states that it is up to date)
so like any other XDA regular, the first thing I did (after opening the box of course) was to try and unlock the bootloader
Powered it on, rebooted to fastboot and fired up motodev...where my happiness was converted to horror when it told me "YOUR DEVICE IS NOT ELIGIBLE FOR UNLOCK"
this is a huge bummer if not an outright deal breaker, as I use xposed, among other things I need root ,and I've seen people post twrp backups here from the Indian Variant, so people have at least that installed, so guys, what are my options?
How did you do it? Will sunshine work?
P.S. : I bought it yesterday but I think my retailer won't take "can't unlock bootloader" as a viable excuse to refund an otherwise functional device
Sent from my XT1225 using XDA-Developers mobile app
Doomrider said:
Hey guys
Bought the 64 GB version yesterday, vitals are as follows
Moto turbo
Xt1225
Android 5.0.2 (took a small OTA maybe like 90mb, now states that it is up to date)
so like any other XDA regular, the first thing I did (after opening the box of course) was to try and unlock the bootloader
Powered it on, rebooted to fastboot and fired up motodev...where my happiness was converted to horror when it told me "YOUR DEVICE IS NOT ELIGIBLE FOR UNLOCK"
this is a huge bummer if not an outright deal breaker, as I use xposed, among other things I need root ,and I've seen people post twrp backups here from the Indian Variant, so people have at least that installed, so guys, what are my options?
How did you do it? Will sunshine work?
P.S. : I bought it yesterday but I think my retailer won't take "can't unlock bootloader" as a viable excuse to refund an otherwise functional device
Sent from my XT1225 using XDA-Developers mobile app
Click to expand...
Click to collapse
Your device is eligible.
Do NOT use Sunshine.
I have no idea what "MotoDev" is. Go to the actual Motorola website and request an unlock code.
UNLOCK YOUR BOOTLOADER
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
You will need to install the Android SDK. http://developer.android.com/sdk/index.html
Also, install the latest Motorola USB Drivers on your desktop. https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Connect your phone to PC via USB cable. Go to the Motorola website and get the unlock code.
In the Windows command window, you will need to copy and paste the numbers back and forth. Do NOT try to type them by hand. That was my mistake. I also got an ineligible error message the first time, because it's like 70 character alphanumeric string. Very easy to make a typing mistake. I did.
If you don't know how to copy and paste to and from the Windows command window, use to Google to find out how.
ChazzMatt said:
Your device is eligible.
Do NOT use Sunshine.
I have no idea what "MotoDev" is. Go to the actual Motorola website and request an unlock code.
UNLOCK YOUR BOOTLOADER
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
You will need to install the Android SDK. http://developer.android.com/sdk/index.html
Also, install the latest Motorola USB Drivers on your desktop. https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Connect your phone to PC via USB cable. Go to the Motorola website and get the unlock code.
In the Windows command window, you will need to copy and paste the numbers back and forth. Do NOT try to type them by hand. That was my mistake. I also got an ineligible error message the first time, because it's like 70 character alphanumeric string. Very easy to make a typing mistake. I did.
If you don't know how to copy and paste to and from the Windows command window, use to Google to find out how.
Click to expand...
Click to collapse
Yess!! That did it[emoji2] turns out the site does not differentiate between "incorrect" and "ineligible"
Not finding the device on the supported devices list convinced me that the official route was closed
Turns out there were a couple of empty spaces in the key i copied, i recheked it manually after you confirmed it to be unlockable , thanks a ton[emoji1]
Motodev is what the motorola development portal was called back in 2013, when i unlocked my moto x first gen, now i guess they dropped the developer moniker and its just motorola
Thanks again
P.S. :nice they changed the bootloader warning background from white to black now
Sent from my SM-T705 using XDA-Developers mobile app
Doomrider said:
Yess!! That did it[emoji2] turns out the site does not differentiate between "incorrect" and "ineligible"
Thanks again
P.S. :nice they changed the bootloader warning background from white to black now
Click to expand...
Click to collapse
Great.
As for this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Go here and replace the unlocked bootloader warning. You'll see this below instead of the irritating warning notice.
[Moto Maxx] Black Motorola Logo On boot (bootlogo)
http://forum.xda-developers.com/moto-maxx/themes-apps/moto-maxx-black-motorola-logo-boot-t3065141
ChazzMatt said:
Great.
As for this:
Go here and replace the unlocked bootloader warning. You'll see this below instead of the irritating warning notice.
[Moto Maxx] Black Motorola Logo On boot (bootlogo)
http://forum.xda-developers.com/moto-maxx/themes-apps/moto-maxx-black-motorola-logo-boot-t3065141
Click to expand...
Click to collapse
My good man, thats TWO beers if we ever have the good fortune of meeting up[emoji16]
Cheers and thanks again
Sent from my SM-T705 using XDA-Developers mobile app
hi
MOD EDIT: LINK REMOVED
Per the forum rules:
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
THREAD CLOSED
I watched the same video. My phone came from Sprint with the bootloader already unlocked. Hmm
Sent from my Essential Phone using XDA Labs
Updated OP with important info regarding the vendor ID and fastboot not recognizing the PH-1
CRasH180 said:
I watched the same video. My phone came from Sprint with the bootloader already unlocked. Hmm
Click to expand...
Click to collapse
Interesting. The gf bought one from Sprint Saturday and the bootloader is locked.
Those having issues with adb or bootloader, may need to update drivers for such
Figured out my issue no worries
Just in case you were wondering, relocking your bootloader WILL wipe your device.
I updated my drivers and it is still not recognizing it in fastboot. Any suggestions?
mangordi8901 said:
I updated my drivers and it is still not recognizing it in fastboot. Any suggestions?
Click to expand...
Click to collapse
Which drivers are you using? I had to download the Google USB Driver and then manually select Bootloader from the the Driver Selection screen in Devices.
notjaykay said:
Which drivers are you using? I had to download the Google USB Driver and then manually select Bootloader from the the Driver Selection screen in Devices.
Click to expand...
Click to collapse
That's the one that I chose, the 11.0 version
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
oowaymike said:
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
Click to expand...
Click to collapse
Did you see my thread?
https://forum.xda-developers.com/es...nofficial-usb-drivers-essential-ph-1-t3678231
Sent from my PH-1 using XDA Labs
updating the drivers manually like in your thread did the trick. Thanks!
In case anyone is trying this on a Mac, you need
1: The latest SDK Platform-tools for Mac
2: cd to platform-tools in terminal and enter: ./adb devices
(I couldn't get my Mac to discover my phone at all in ADB until I used ./ before the command, which I never had to do with other phones.
I was able to discover the device in fastboot without these steps and ./, but only when entering the vendor id, and the unlock command failed with or without the id.)
3: Once you see your ADB device show in terminal, you should get the prompt on your PH1 screen to allow your Mac to access it.
4: You should now be able to reboot to fastboot from the terminal using: ./adb reboot bootloader
5: Check device again: ./fastboot devices
6:. Lastly: ./fastboot flashing unlock (vendor id was not needed for me)
Hope this helps.
notjaykay said:
Just in case you were wondering, relocking your bootloader WILL wipe your device.
Click to expand...
Click to collapse
Does unlocking bootloader wipe the device also? Thanks
treIII said:
Does unlocking bootloader wipe the device also? Thanks
Click to expand...
Click to collapse
Yes it does. It'll warn you too when you do the lock or unlock code.
Can anyone help?
PM1LHMA790900113 is what it says my device is
This is a sprint essential ph1
2.0.c4-M1.3. 1 baseband version
4.4.21-perf+
[email protected] #1 kernel version
Android version 7.1.1
BOOTLOADER WILL NOT UNLOCK
---------- Post added at 12:38 AM ---------- Previous post was at 12:36 AM ----------
oowaymike said:
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
Click to expand...
Click to collapse
Same problem... Can anyone help?
This is my problem...
CRasH180 said:
I watched the same video. My phone came from Sprint with the bootloader already unlocked. Hmm
Sent from my Essential Phone using XDA Labs
Click to expand...
Click to collapse
https://ibb.co/hCqviR
https://ibb.co/dwRqHm
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can anyone help? I cannot unlock my bootloader...
ampink7756 said:
https://ibb.co/hCqviR
https://ibb.co/dwRqHm
Can anyone help? I cannot unlock my bootloader...
Click to expand...
Click to collapse
Have you looked at the video by Chris Panton on unlocking your bootloader?
https://www.youtube.com/watch?v=_DNWCqSAAVM?
This video explains how to unlock your bootloader. There is also the post on Essential's official advice on unlocking the boot loader: https://forum.xda-developers.com/essential-phone/how-to/essential-bootloader-unlock-official-t3671997
Hope that helps,
CRasH180
This is the video I watched
oowaymike said:
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
Click to expand...
Click to collapse
CRasH180 said:
Have you looked at the video by Chris Panton on unlocking your bootloader?
https://www.youtube.com/watch?v=_DNWCqSAAVM?
This video explains how to unlock your bootloader. There is also the post on Essential's official advice on unlocking the boot loader: https://forum.xda-developers.com/essential-phone/how-to/essential-bootloader-unlock-official-t3671997
Hope that helps,
CRasH180
Click to expand...
Click to collapse
This is the video I used, but I believe the problem is that I'm using a sprint phone... Please see my other posts...
Hi everyone, I am selling my phone and would like to relock the phone and avoid having that message that appears every time I rebooot the phone..
Is it possiile to relock the phone without problems?
Could someone kindly show me how.
Thanks
Cheers
Make sure you flashed a full stock RUU first, just to make sure the software is absolutely original. Then you can do it via fastboot oem lock in download mode.
Sent from my HTC U12+ using XDA Labs
Hello friends,
I wanted to see if it worked.
I also want relock Bootloader. I have read that it can come to a software brick.
Thanks
Hollilightman said:
Hello friends,
I wanted to see if it worked.
I also want relock Bootloader. I have read that it can come to a software brick.
Thanks
Click to expand...
Click to collapse
what ever you do make sure you put on the original rom on, i made the mistake of doing it when I had a patched boot file and now it wont boot.
I'm not panicing just yet as from reading up I can just flash it using the SD card method. but i got to wait till I get home as i havent got a 16/32GB sd card with me.
Thank you.
just to be sure, this is what I need to do?
1. put an original RUU on your microSD card and rename it 2Q55IMG.zip. Then open the download mode and confirm the flashing.
2. then use "Fastboot OEM Lock" in download mode to lock the bootloader.
Did I understand it correctly?
Thanks
Hollilightman said:
Thank you.
just to be sure, this is what I need to do?
1. put an original RUU on your microSD card and rename it 2Q55IMG.zip. Then open the download mode and confirm the flashing.
2. then use "Fastboot OEM Lock" in download mode to lock the bootloader.
Did I understand it correctly?
Thanks
Click to expand...
Click to collapse
Yes, those instructions are correct.
Although I'm not entirely sure that will remove the message you're looking to remove but I might be wrong. Hopefully I am cause I intend to do the exact same thing as you.
Let me know how it goes
Thank you ,
But would be nice if someone could confirm, who has already done so with success ....
Hollilightman said:
Thank you ,
But would be nice if someone could confirm, who has already done so with success ....
Click to expand...
Click to collapse
Can confirm this is the way to do it, but make sure you put a stock rom on first as it doesn't like it if your boot is patched.
The message is phone is RELOCKED after its all done
HELP!!!
Hello again,
I have a problem. I have the
2Q55IMG_IMAGINE_UHL_O80_SENSE10GP_HTC_Europe_1.30.401.2_Radio_sdm845-000201b-1807311356_release_528110_signed_2_4.zip
renamed 2Q55IMG.zip on the SD card and flashed. I have UHL (Single SIM) HTC_034.
Then i use "Fastboot OEM Lock" in download mode to lock the bootloader.
I confirm the query with Yes.
After that I have a bootloop, can't get out of it...
What can I do?
Did it boot into the rom before you tried to relock the bootloader. Also I wonder if the rom you used was to early. I used 1.53.401 when I did it. I assume that is the same rom for single / dual sim htc_034 models.
I would be getting a more uptodate rom and reflash again via sd card method
bigAL99 said:
Did it boot into the rom before you tried to relock the bootloader. Also I wonder if the rom you used was to early. I used 1.53.401 when I did it. I assume that is the same rom for single / dual sim htc_034 models.
I would be getting a more uptodate rom and reflash again via sd card method
Click to expand...
Click to collapse
Thanks,
yes, I had rebooted.
I don't have a link for the 1.53.401. Single SIM. (See picture)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The bootloader now says (see picture)
When flashing the end was "8 RU_SGNATURE_FAIL" (see picture)
delete
Hollilightman said:
Thanks,
yes, I had rebooted.
I don't have a link for the 1.53.401. Single SIM. (See picture)
The bootloader now says (see picture)
When flashing the end was "8 RU_SGNATURE_FAIL" (see picture)
Click to expand...
Click to collapse
Hopefully someone will know the code I checked 5m4rph0n36guru s thread and that error code isn't listed.
I assume you have tried reflashing again.
bigAL99 said:
Hopefully someone will know the code I checked 5m4rph0n36guru s thread and that error code isn't listed.
I assume you have tried reflashing again.
Click to expand...
Click to collapse
right, just download the 1.21.401.4 and try it...
Edit:
it worked with RUU 1.21401.4. Apparently the RUU 1.30.401.2 is faulty. ;o)
5m4r7ph0n36uru said:
Make sure you flashed a full stock RUU first, just to make sure the software is absolutely original. Then you can do it via fastboot oem lock in download mode.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
just a dumb question. if i want to unlock later, i need to do the steps via htcdev with the unlock token; right?
Have you unlocked it yet?
Can you help me unlock it!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Apply for unlocking Mi devices
en.miui.com
Just follow the instructions and wait for one week before permission granted (if you are lucky).
inyellow said:
Apply for unlocking Mi devices
en.miui.com
Just follow the instructions and wait for one week before permission granted (if you are lucky).
Click to expand...
Click to collapse
Yes! i did it! Thank you supported!
I will wait for one weed.
I'm also wait for one week to unlock.
Hope we have many custom roms later.
ycq19zsc said:
I'm also wait for one week to unlock.
Hope we have many custom roms later.View attachment 5516997
Click to expand...
Click to collapse
I think there won't be a new rom within a month
Pimaxxx98 said:
I think there won't be a new rom within a month
Click to expand...
Click to collapse
I think so too... it's not that easy for developers to buy before global release.
Hi I'm trying to unlock the bootloader, but when I log in to the Xiaomi Unlock Tool, I never received the verfication code that's supposed to be sent via a text messages to my linked US phone number. Other text messages went through fine so either XIaomi didn't send the code or my carrier (AT&T) blocked it. I tried a few other numbers and none worked. Did you guys need to receive the text message to verify your account when using the Unlock Tool? If yes, did you use a Chinese phone number or something else? A tried 4 different US numbers and none of them could receive Xiaomi sms. Thanks for your help!
wincnd said:
Hi I'm trying to unlock the bootloader, but when I log in to the Xiaomi Unlock Tool, I never received the verfication code that's supposed to be sent via a text messages to my linked US phone number. Other text messages went through fine so either XIaomi didn't send the code or my carrier (AT&T) blocked it. I tried a few other numbers and none worked. Did you guys need to receive the text message to verify your account when using the Unlock Tool? If yes, did you use a Chinese phone number or something else? A tried 4 different US numbers and none of them could receive Xiaomi sms. Thanks for your help!
Click to expand...
Click to collapse
Tried another day and it worked
inyellow said:
Apply for unlocking Mi devices
en.miui.com
Just follow the instructions and wait for one week before permission granted (if you are lucky).
Click to expand...
Click to collapse
Hi! How do I know when it's passed time enough to unlock it? Do I have to verify from time to time on the tool?
Sorry but I must be doing something wrong and different from the way I always did unlock bootloader. In Android 12, With Vol down + power the cell phone enters a different screen "Bootloader" that always allowed unlocking.
mi unlock software does not allow clicking the unlock button, fastboot devices and adb devices commands do not work in this mode.... How to unlock with these changes?
molochgrifone said:
Hi! How do I know when it's passed time enough to unlock it? Do I have to verify from time to time on the tool?
Click to expand...
Click to collapse
Run the unlock tool again, it will tell you how many hours left. Normally it tells you that 168 hours left at the first successful attempt, it also tells you do not logout miui account or try to login another account on your phone. Just be patient.
inyellow said:
Run the unlock tool again, it will tell you how many hours left. Normally it tells you that 168 hours left at the first successful attempt, it also tells you do not logout miui account or try to login another account on your phone. Just be patient.
Click to expand...
Click to collapse
I checked, it ask me again to log in and now it ask if I want to unlock my phone like the first time, there is no timer
molochgrifone said:
I checked, it ask me again to log in and now it ask if I want to unlock my phone like the first time, there is no timer
Click to expand...
Click to collapse
Maybe your waiting period is over, follow the instructions on official FAQ page exactly.
https://c.mi.com/thread-2262302-1-0.html
.
jurarj said:
Sorry but I must be doing something wrong and different from the way I always did unlock bootloader. In Android 12, With Vol down + power the cell phone enters a different screen "Bootloader" that always allowed unlocking.
mi unlock software does not allow clicking the unlock button, fastboot devices and adb devices commands do not work in this mode.... How to unlock with these changes?
Click to expand...
Click to collapse
I have the same problem you solve it bro?
luiscedillo80 said:
I have the same problem you solve it bro?
Click to expand...
Click to collapse
you can open fastboot by power + (-)
then connect cap type C in to PC
Download anh intaller ADB driver xiaomi
You will show connection on screen PC
for anyone having issues to sign in to mi unlock tool and verification code doesnt arrive: go to your phone and your Mi account, Tap QR code and scan QR after clicking top right corner in sign in page of mi unblock tool. Worked for me.