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.
i try but the program doesn't unlock the bootloader. The smartphone go in fastboot mode but nothing happen
fer2503 said:
i try but the program doesn't unlock the bootloader. The smartphone go in fastboot mode but nothing happen
Click to expand...
Click to collapse
Once it's in fastboot, try doing the Unlock Bootloader command again. Sometimes the program gets stuck when the phone reboots then tries to do a command.
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.
fastboot boot
This is not working for me. Bootloader unlocked but I cannot go into the TWRP recovery.
Later I followed this thread: it both mentioned reason and solution as below.
If you boot into system without booting twrp once, the system overwrittes twrp with the stock recovery. If this happens to you, then boot into fastboot and boot twrp without flashing it with "fastboot boot <NAMEOFTHE.IMG>". Afterwards boot into bootloader from the recovery's reboot menu and flash twrp again
Click to expand...
Click to collapse
I successfully rooted the watch.
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.
not loading
win 7 64bit, it is not loading and crashing..
problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: AMVTCOVYVOYG4CJW4BOZUOCFK2NAVXGX
Problem Signature 02: 2.5.0.0
Problem Signature 03: 55ff894d
Problem Signature 04: PresentationCore
Problem Signature 05: 4.0.0.0
Problem Signature 06: 4ba2361f
Problem Signature 07: 13ce
Problem Signature 08: 7
Problem Signature 09: System.IO.FileLoadException
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: ba19
Additional Information 2: ba19cb920b085645c3e4b12657df4b92
Additional Information 3: 770c
Additional Information 4: 770ce0b63d515dfb5051b12f5c3687e7
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!
How can i root my sw3?
chikrron said:
How can i root my sw3?
Click to expand...
Click to collapse
it fails to unlock bootloader for me
daveyp187 said:
it fails to unlock bootloader for me
Click to expand...
Click to collapse
Me too
don't think this is working
daveyp187 said:
it fails to unlock bootloader for me
Click to expand...
Click to collapse
chikrron said:
Me too
Click to expand...
Click to collapse
MacSeoin said:
don't think this is working
Click to expand...
Click to collapse
Just go through this process..
Plug the SWR50 into the computer (be sure ADB Debugging is turned on), and type this in CMD:
Code:
adb reboot bootloader
The watch will reboot into Fastboot mode.
Then type this (yes, twice):
Code:
fastboot oem unlock
fastboot oem unlock
fastboot reboot
Now your bootloader is unlocked.
Ok, been playing around, seems my issue was windows 10 fastboot drivers. Android SDK and device manager sorted this, I didn't need to unlock the bootloader in the end, I just fastboot then hotboot recovery and push SuperSU and then flash it from recovery. Now rooted
crunchybutternut said:
Just go through this process..
Plug the SWR50 into the computer (be sure ADB Debugging is turned on), and type this in CMD:
Code:
adb reboot bootloader
The watch will reboot into Fastboot mode.
Then type this (yes, twice):
Code:
fastboot oem unlock
fastboot oem unlock
fastboot reboot
Now your bootloader is unlocked.
Click to expand...
Click to collapse
Tried this but always says <waiting for device>
You need to update your driver. Fastboot, stock recovery, twrp, and the running system all have slightly different drivers. Most packages include all the drivers, but some do not. It is notoriously annoying to get all the pieces to work right on Win 10.
Sent from my SM-T810 using Tapatalk
hi, i've got the last android wear update,and i'm trying to root the smartwatch with the windroid toolkit...but when i try to unlock the bootloader or flashing twrp recovey,the watch reboot in fastboot mode,and it gets stucked in it,doin' nothing...when i try to root the device,it goes in recovery mode,but there isn't any file to install,as suggested from the step to step guide of the windows program. i'm running windows 10..any suggestion on how to fix the problem..?
Unable to unlock?
I tried to unlock my sw3, but nothing changed after it says "Your bootloader is now unlocked"...
For those trying to use this app to unlock and root you SW3 please just have a look at
http://forum.xda-developers.com/sma...sony-smartwatch-3-marshmallow-mec24h-t3382450
and
http://forum.xda-developers.com/sma...ment/kernel-sony-smartwatch-3-kernel-t3353580
Full instructions are at the beginning of the thread..
Related
Q&A for [GUIDE][ROOT] Smartwatch 3 KNX01V
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE][ROOT] Smartwatch 3 KNX01V. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
HELP!?
XorZone said:
You have been warned!
Links:
Sony PC Companion
SWR50-rootboot.img@ mega.nz, md5 summ: e2c34b07faa415a6cbb95943649c7eba
Step 1:
Code:
[URL="source.android.com/source/building-devices.html#unlocking-the-bootloader"]Unlocked bootloader[/URL]
1. Enable adb debug
2. adb reboot bootloader
3. fastboot oem unlock (twice if requested)
4. fastboot format cache
5. fastboot format userdata
6. fastboot getvar all (and verify that it is)
7. fastboot reboot
Step 2:
Code:
Updated to the latest KNX01V
[URL="http://www.sonymobile.com/us/tools/pc-companion/"]Install Sony PC Companion[/URL] and use Supports Zone -> Accessories software update -> Smartwatch 3
Step 3:
Code:
Have Flashboot (Sony s1 flash) drivers installed just in case (Install Sony PC Companion and do update as indicated in previous step)
Step 4:
Code:
[COLOR="red"]BOOT [/COLOR][COLOR="Red"](DO NOT EVER FLASH IT!!!)[/COLOR] rooting boot.img
1. Download rooting kernel image (SWR50-rootboot.img)
2. Reboot into bootloader (adb reboot bootloader)
3. fastboot boot SWR50-rootboot.img
4. Wait till device reboots or sits in black screen for a while (1 min+ then reboot it by holding power 10+sec)
Step 5:
Code:
Verify by:
1. adb shell
2. su
3. you should see [email protected]:/ #
Step 6:
Code:
1. Let me know!
2. Use it, dive into GPS investigation or customizations, etc.....
Special thanks:
1. Justin Case for LG G Watch rooting method using LGGW-rootboot.img
2. osm0sis for Android Image Kitchen
{
"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"
}
Click to expand...
Click to collapse
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?
13noninja said:
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?
Click to expand...
Click to collapse
Sounds like your'e missing the right drivers. I'm sorry I don't have a link right now but it should be somewhere on the OP.
13noninja said:
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?
Click to expand...
Click to collapse
1. Download and install google usb driver: http://developer.android.com/sdk/win-usb.html
2. Check if you have adb driver in place: adb devices, if not - go into Device Manager and force missing driver to be "Android Composite ADB Interface".
To force it "Update Driver" -> "Browse My Computer" -> "Let me pick from a list ..." -> Select "Google, Inc." on left and "Android Composite ADB Interface" on the right.
Verify that you have adb access, by typing "adb devices", if needed confirm connection on the phone
3. Reboot to bootloader by typing "adb reboot bootloader", you should see "Running Fastboot" on watch screen.
4 Check "fastboot devices", you should see device id followed by fastboot word.
If not - go into Device Manager and force missing driver to be "Android Bootloader Interface" by followinf instructions for adb, but make sure to pick "Google, Inc." on left and "Android Bootloader Interface" on the right.
5. Verify fastboot working by executing fastboot devices.
6. Follow guide.
Got It
Thx XorZone and nobunnysapro, i found the missing drivers and got everything running smoothly.
I can not get my device to show up in adb devices and its driving me crazy. Tried windows 7/8/server 2012R2 ..lol
Now I have done my fair share of custom roms and bootloaders.
OG Droid
Nexus
Nexus 10
Asus Memo Pad (came from alarm company, and could only load one app...now its a full running tablet)
I am sure its a silly thing I have done or am missing...
Thoughts....ideas?..need more info?
Oh and ADB Debugging is on
I can't seem to get it working..
I have the drivers and ADB works fine, i can sideload stuff to watch and install apk and everything.
But when I write "adb reboot boatloader" it does just normal reboot. Can't get into fastboot mode.
Orvils said:
I can't seem to get it working..
I have the drivers and ADB works fine, i can sideload stuff to watch and install apk and everything.
But when I write "adb reboot boatloader" it does just normal reboot. Can't get into fastboot mode.
Click to expand...
Click to collapse
boatloader? I do not think sony included boat on board... JK
correct one is
Code:
adb reboot bo[B]o[/B]tloader
XorZone said:
boatloader? I do not think sony included boat on board... JK
correct one is
Code:
adb reboot bo[B]o[/B]tloader
Click to expand...
Click to collapse
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Sent from my SM-N910F using Tapatalk
Orvils said:
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
1. Are you doing it through USB connection and not over bluetooth?
2. What is your current build number/version in about menu?
Yes I'm doing everything with USB connection.
Build number is KNX01V
Sent from my SM-N910F using Tapatalk
Orvils said:
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Click to expand...
Click to collapse
Always check if adb in general works (may be driver probs in Win):
Code:
adb devices -l
(That's a lowercase L)
A guide for relocking the boot loader? I'm looking to go to lollipop for wear so I'd like to know how to go back to stock.
Fastboot OEM lock, and better reflash using Sony companion before.
I plan to try to get ota as is, then if it'll not work reflash using companion and then if it is still not upgrades I'll relock as last resort.
I have reinstalled Google USB drives over and over again manually and through SDK... When I try to manually point it to the right drivers I don't even get offered the right drivers.. I have google inc. Selected on the left but I dont see android composite or android bootloader interface...help would be much appreciated
Hello, any idea to make it work on lollipop? Thanks!
I have Sony Smartwatch 3 and want to install normal APK via Sideload and USB/PC (do not want to root my smartphone).
Is this possible and which SW i need to install on Windows PC?
Step by step guide (for noobs) would be great. Thanks
Gesendet von meinem SM-T310 mit Tapatalk
PhilZ Touch 6.59.0-CWM 6.0.5.1 Xperia T3[D5103] for Unlocked Bootloader Only
Head to the Main thread for full feature list
PhilzRecovery
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something.
I have tested maximum stuff and it works fine
{
"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"
}
Additional FEATURES :
Stock based kernel with RIC disabled
init.d support
THIS RECOVERY IS FOR DEVICE D5103 WITH UNLOCKED BOOTLOADER ONLY and Firmware version 18.1.A.2.25
How to Unlock bootloader
1. Unlock Bootloader (will void warranty)
2. Download Fast-Boot package & install adb & fasstboot drivers
3. Download the kernel package (d5103_philz.zip) extract & open command prompt here & run “fastboot devices”
4. fastboot mode
5. Power off device & Hold volume up button, connect your device.
6. Use this fastboot command to flash boot.img: fastboot flash boot boot_d5103.img
7. Now reboot using this command: fastboot reboot
8. Now enjoy one of the best custom recovery on Xperia T3
Now fixed "ro.product.device" is set to "D5103"
Fixed-D5103 Download
FAQ
Code:
How to enter in recovery mode ?
Answer : As soon as you see Sony logo on your Xperia T3 ,
repeatedly press volume down(vol -) button.
Credits :
Code:
[user=5722563]@Siddhesh.K15[/user]
[user=5722563]@Santosh M[/user]
Tested by
[user=1199111]@AMIGAnTOMEK[/user]
Very thanks, il tried this in the evening
Thank you Xenon1978 for this good job
How to reboot in recovery please ?
snouki said:
How to reboot in recovery please ?
Click to expand...
Click to collapse
when on booting with sony logo, press volume down repeatly
Bro anyone have some flashable good which will root my T3 D5102
Hi
Can someone help me?
I already tryed to flash this and when reboot phone stuck at SONY logo only.
Im rooted and unlocked. My phone is D5103? What do i do wrong?
Ok i see now something that is not as screenshoot. My phone is 4.4.2 not 4.4.4 but i did not get any update? I live in SWEDEN.
BTW i will download 4.4.4 and flash manually
recovery for 5.1.1
Hello,
as we are able now to boot on 5.1.1, how to have a working recovery ?
is it possible to have only TRWP in a recovery.img in order to flash the d5103 ?
Thank you for this nice stuff!
Can't Flash.
I start flashing, and thenn an error-Message.
C:\platform-tools>fastboot flash boot boot_d5103.img
sending 'boot' (16390 KB)...
OKAY [ 0.671s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.702s
i do it
but cmd write
<waiting for device>
dan15 said:
Hello,
as we are able now to boot on 5.1.1, how to have a working recovery ?
is it possible to have only TRWP in a recovery.img in order to flash the d5103 ?
Click to expand...
Click to collapse
How have you booted 5.1.1?
dolor.sy said:
i do it
but cmd write
<waiting for device>
Click to expand...
Click to collapse
you need to have ADB, fastboot and drivers updated.
Try this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Maybe I don't understand this for well yet.. I can't find a direct link to the recovery for my experia T3
Fixing the <waiting for device> in fastboot.
dolor.sy said:
i do it
but cmd write
<waiting for device>
Click to expand...
Click to collapse
[This is for the XPERIA D5103 T3]
First of all download the USB drivers for your phone:
I cannot post here the link because XDA does not allow me to do that. Anyway it's in the attachment. In the case this file is somehow deleted due to expiration and you still need the drivers go to Google and search with xperia t3 usb drivers and you'll find a website that starts with developer.sonymobile something and its title is as follow: Xperia T3 driver – Developer World. Extract the file.
[Method 1] Go to Device Manager and select the warning triangle and select Update Driver Software. Choose the folder that you extracted and after a bit of time the computer should now detect that your phone is connected.
[Method 2] This method assumes that you have the driver already installed but the computer does not link it to your phone. Go to Device Manager and select the warning triangle and select Update Driver Software. Then click in the Browse my computer for driver software. Now click the one that says Let me pick from a list of device drivers on my computer and choose the one that says Sony so0108.
Don't forget to power off device, hold volume up button and then connect your device. Then try to execute whatever you need with the fastboot command.
Kind regards
Luis Rocha
OllerLoewe said:
Can't Flash.
I start flashing, and thenn an error-Message.
C:\platform-tools>fastboot flash boot boot_d5103.img
sending 'boot' (16390 KB)...
OKAY [ 0.671s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.702s
Click to expand...
Click to collapse
Have similar problem.
Did You, or anyone else, found a solution?
Bootloader unlocked, drivers installed...
I have a problem
I flashed it and everything was successfull but I can't go into recovery. can you help me?
btw. my device is rooted and has bootloader unlocked.
DownloaderXD said:
I flashed it and everything was successfull but I can't go into recovery. can you help me?
btw. my device is rooted and has bootloader unlocked.
Click to expand...
Click to collapse
had the same problem at 1st but realize (in a upper post) that to enter recovery you have to power on your phone and just after the vibration, press quickly at multiple time the vol down button (not a single long press but a lot of quick short presses).... until you see the recovery screen...
I feel so blond moment.. I coud not find a recovery in you mega list for my T3 d5103. Am I wrong or there is no one in the list between all those names at the left side.
While trying to root my redmi 1s, i accidentally pressed a wrong button due to which it seemed like if recovery is no longer functioning.
The mobile is getting struck at mi logo and is not proceeding forward.
Pressing volume down+power button successfully opens fastboot screen. Earlier when I was connecting it to mi suite on pc, i was able to flash. But due to incomplete charged battery, flashing procedure stopped. After the recent windows update, mi pc suite is recognizing the android but is not able to flash it. It pops out a dialogue box saying "cant flash the device". Any idea what can i do now?
{
"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"
}
akshat2119 said:
While trying to root my redmi 1s, i accidentally pressed a wrong button due to which it seemed like if recovery is no longer functioning.
The mobile is getting struck at mi logo and is not proceeding forward.
Pressing volume down+power button successfully opens fastboot screen. Earlier when I was connecting it to mi suite on pc, i was able to flash. But due to incomplete charged battery, flashing procedure stopped. After the recent windows update, mi pc suite is recognizing the android but is not able to flash it. It pops out a dialogue box saying "cant flash the device". Any idea what can i do now?
Click to expand...
Click to collapse
If your phone boots into fastboot, then try installing twrp recovery and then flash the rom you wish.
vicky romero said:
If your phone boots into fastboot, then try installing twrp recovery and then flash the rom you wish.
Click to expand...
Click to collapse
but how to flash twrp via fastboot. i.e. which software would recognize fastbooting android?
akshat2119 said:
but how to flash twrp via fastboot. i.e. which software would recognize fastbooting android?
Click to expand...
Click to collapse
Flashing twrp is done by fastboot using adb tools. First install the USB drivers of your phone. You can simply google them. Then go to this link https://drive.google.com/open?id=0B_43Fi9T_yqvUy1jOWk0cnJyZEk
and download the four files in the adb folder. Now download the latest twrp image i.e, twrp 3.0.0-0 from this link
https://dl.twrp.me/armani/
keep the adb tools i.e, the four files you had downloaded and the twrp image in the same folder. Rename the twrp 3.0.0-0 to recovery.img. Now hold shift key and press right click on your mouse. From there select open command window here. Now open fastboot and connect your phone through Usb and type this code
Code:
fastboot devices
This is to check wheather your device is connected or not. If it's connected then it will show some code. After that type this code
Code:
fastboot flash recovery recovery.img
That's it twrp will be flashed right away. Then you can flash MIUI or any other custom rom.
Thank you
vicky romero said:
Flashing twrp is done by fastboot using adb tools. First install the USB drivers of your phone. You can simply google them. Then go to this link https://drive.google.com/open?id=0B_43Fi9T_yqvUy1jOWk0cnJyZEk
and download the four files in the adb folder. Now download the latest twrp image i.e, twrp 3.0.0-0 from this link
https://dl.twrp.me/armani/
keep the adb tools i.e, the four files you had downloaded and the twrp image in the same folder. Rename the twrp 3.0.0-0 to recovery.img. Now hold shift key and press right click on your mouse. From there select open command window here. Now open fastboot and connect your phone through Usb and type this code
Code:
fastboot devices
This is to check wheather your device is connected or not. If it's connected then it will show some code. After that type this code
Code:
fastboot flash recovery recovery.img
That's it twrp will be flashed right away. Then you can flash MIUI or any other custom rom.
Click to expand...
Click to collapse
A big thank you. I owe you for helping out. By the way after installing recovery I tried downloading rom(both armani which was earlier working and miui official). The script gets sideloaded successfully but again the operating system is not loading. ie mobile is still struck in bootloader
akshat2119 said:
A big thank you. I owe you for helping out. By the way after installing recovery I tried downloading rom(both armani which was earlier working and miui official). The script gets sideloaded successfully but again the operating system is not loading. ie mobile is still struck in bootloader
Click to expand...
Click to collapse
Flash this firmware before installing the rom. It'll fix the bootloops.
https://www.androidfilehost.com/?fid=24052804347850305
Thanks @fefifofum for this flashable zip.
I unlocked bootloader using official app by Asus but now I want to relock it to be able to install OTA updates if anyone have any idea on how to relock bootloader kindly guide me with the process thank you.
Bump
chandru.biradar2 said:
I unlocked bootloader using official app by Asus but now I want to relock it to be able to install OTA updates if anyone have any idea on how to relock bootloader kindly guide me with the process thank you.
Click to expand...
Click to collapse
You can't relock but you can manually install captured ota packages...
chandru.biradar2 said:
I unlocked bootloader using official app by Asus but now I want to relock it to be able to install OTA updates if anyone have any idea on how to relock bootloader kindly guide me with the process thank you.
Click to expand...
Click to collapse
Same
MithunBeats said:
Same
Click to expand...
Click to collapse
If you. Get it solution please text here because am also stuck with bootloader unlocked warning
Indercheeda said:
If you. Get it solution please text here because am also stuck with bootloader unlocked warning
Click to expand...
Click to collapse
Ok sir
[ZS620KL] Relock bootloader?
I saw that the following commands will be able to relock the bootloader of the ZS620KL device:
fastboot flashing lock
fastboot flashing lock_critical
Click to expand...
Click to collapse
But it seems that the command is showing a permission error.
{
"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"
}
Does anyone know how to elevate the permission to do bootloader relocking?
Relock
peter_betos said:
I saw that the following commands will be able to relock the bootloader of the ZS620KL device:
But it seems that the command is showing a permission error.
Does anyone know how to elevate the permission to do bootloader relocking?
Click to expand...
Click to collapse
Am also stuck on it
Cheeda212 said:
Am also stuck on it
Click to expand...
Click to collapse
Can you guys please share if you find a solution on how to lock the bootloader back?
Does this needs a key of some sort? I see other manufacturers using a key before being permitted to execute these commands.
Sent from my ASUS_Z01RD using Tapatalk
Anyone found solution to relock bootloder on 5z?
did anyone find solution to relock bootloader on 5z? Pls help
Try
Fastboot oem asus_lock
or
Fastboot oem asus_lock 2>&1
how to lock bootloader
How to lock bootloader easily?!
Karma6069 said:
How to lock bootloader easily?!
Click to expand...
Click to collapse
I don't think locking bootloader is possible in 5z. Atleast not in direct methods.
ajbash007 said:
I don't think locking bootloader is possible in 5z. Atleast not in direct methods.
Click to expand...
Click to collapse
Process to downgrade ASUS ZENFONE 5Z to pie.
I HAVE ATTACHED THE RELOCK BOOTLOADER ARCHIVE.
ENJOY!
Step 1: Download this firmware on pc from the given link - https://dlcdnets.asus.com/…/WW-ZS620KL-90.11.162.111-MR5-us…
Step 2: Extract in pc
Step 3: boot your phone in fastboot mode and connect your device to pc
Step 4: Click on "updateimg.bat" file and let it go on.
After completing your phone will reboot and you will have successfully downgraded to pie.
NOTE: BACKUP YOUR DATA FIRST.
This method works well! I tried it and it worked! And also, big thanks to all involved, helping us! I even tried the relock method and it worked!
Relock bootloader After you have downgraded as instructed!
Be sure to backup all your data!
https://t.me/ASUSZenfone5ZGroup/244677
-extract
-boot phone to fastboot mode
-run the Step3xxxxx.bat file
-done
NOTE
IT WILL WIPE YOUR INTERNAL DATA
AllenConstantine said:
Process to downgrade ASUS ZENFONE 5Z to pie.
I HAVE ATTACHED THE RELOCK BOOTLOADER ARCHIVE.
ENJOY!
Step 1: Download this firmware on pc from the given link - https://dlcdnets.asus.com/…/WW-ZS620KL-90.11.162.111-MR5-us…
Step 2: Extract in pc
Step 3: boot your phone in fastboot mode and connect your device to pc
Step 4: Click on "updateimg.bat" file and let it go on.
After completing your phone will reboot and you will have successfully downgraded to pie.
NOTE: BACKUP YOUR DATA FIRST.
This method works well! I tried it and it worked! And also, big thanks to all involved, helping us! I even tried the relock method and it worked!
Relock bootloader After you have downgraded as instructed!
Be sure to backup all your data!
https://t.me/ASUSZenfone5ZGroup/244677
-extract
-boot phone to fastboot mode
-run the Step3xxxxx.bat file
-done
NOTE
IT WILL WIPE YOUR INTERNAL DATA
Click to expand...
Click to collapse
After entering fastboot how to run it?
Download the archive to your PC, and follow the instructions given.
Relock bootloader After you have downgraded as instructed!
Be sure to backup all your data!
-extract
-boot phone to fastboot mode
-run the Step3xxxxx.bat file
-done
NOTE
IT WILL WIPE YOUR INTERNAL DATA
AllenConstantine said:
Download the archive to your PC, and follow the instructions given.
Relock bootloader After you have downgraded as instructed!
Be sure to backup all your data!
-extract
-boot phone to fastboot mode
-run the Step3xxxxx.bat file
-done
NOTE
IT WILL WIPE YOUR INTERNAL DATA
Click to expand...
Click to collapse
My Zenfone is on stock Android 9
After entering fastboot idk what to do
I do not get your point, man! Seriously! I described what you should do. Download the relock bootloader rar file, put it in your pc and follow the instructions given. Sorry, but a child can do it!
Hello,
Fist, I will say it, I am a total newbie in rooting. So, I followed one of the excellent guides here. Little by little, I begin to understand the process. So I have succeeded to root my pixel 6 pro using magisk.
Then, Android 13 has come. I think, pretty sure, that the bootloader need to be locked again to update. At least, I tried, I removed magisk and so the root, but the update fails.
Then I have reset the phone. Now I try to lock again the bootloader. However, withadb reboot bootloader, I cannot see the phone. fastboot devices shows nothing.
fastboot flashing lock stay on <waiting for any device>
Then I tried adb reboot fastboot. Here, the phone is found when I type fastboot devices. However fastboot flashing lock displays:
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
Click to expand...
Click to collapse
So, my questions:
1.) do I really need to lock the bootloader to update to android 13 ?
2.) what did I do as mistake ? I want to understand, especially if one day I need to sell the phone, I want to be able to lock again the bootloader. Is fastboot flashing lock the right command ?
Ralendil said:
Hello,
Fist, I will say it, I am a total newbie in rooting. So, I followed one of the excellent guides here. Little by little, I begin to understand the process. So I have succeeded to root my pixel 6 pro using magisk.
Then, Android 13 has come. I think, pretty sure, that the bootloader need to be locked again to update. At least, I tried, I removed magisk and so the root, but the update fails.
Then I have reset the phone. Now I try to lock again the bootloader. However, withadb reboot bootloader, I cannot see the phone. fastboot devices shows nothing.
fastboot flashing lock stay on <waiting for any device>
Then I tried adb reboot fastboot. Here, the phone is found when I type fastboot devices. However fastboot flashing lock displays:
So, my questions:
1.) do I really need to lock the bootloader to update to android 13 ?
2.) what did I do as mistake ? I want to understand, especially if one day I need to sell the phone, I want to be able to lock again the bootloader. Is fastboot flashing lock the right command ?
Click to expand...
Click to collapse
You don't need to do all of that to upgrade to android 13. You can read how to upgrade to android 13 here: https://forum.xda-developers.com/t/...-6-pro-bootloader-central-repository.4352027/
as well as here: https://forum.xda-developers.com/t/pixel-6-pro-easy-step-by-step-unlock-root-update.4361847/
it is a long thread with a lot of information, so I'll just give you an adlibbed version of how to upgrade
I read that you have removed root. You can re-root after upgrading. Make sure your bootloader is unlocked first.
First make sure you have the latest sdk platform tools version here: https://developer.android.com/studio/releases/platform-tools
Download the android 13 factory image here: https://developers.google.com/android/images
Extract the platform tools and the factory image, and make sure the flash-all.bat file is in the same location as adb.exe and fastboot.exe
If you want to keep your data, do this. If you don't want to lose your data and don't mind wiping your phone, skip this step and just run flash-all.bat in fastboot.
Edit the flash-all.bat file and remove the -w flag from the
Code:
fastboot update -w image-raven-tp1a.220624.021.zip
command. So it'll just be
Code:
fastboot update image-raven-tp1a.220624.021.zip
Save it, edit again just to double check that -w flag is gone. If it is, reboot your phone back into fastboot and run flash-all.bat.
It'll upgrade and do everything for you. You're on Android 13 now and your data is still intact.
Once your phone is booted, you can patch the boot image from the factory image you downloaded with Magisk and flash it in fastboot again by doing fastboot flash boot --slot=all (drag and drop patched boot.img here) OR type in the file name magisk_patched-xxxxxxxxxx.img. Then you will have root.
If you want to go back to complete factory with a locked bootloader, run Android Flash Tool from Google here: https://flash.android.com/welcome?continue=/back-to-public
Make sure "Wipe Device", "Lock Bootloader", and "Force Flash All Partitions" are checked.
You could always try the Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own). It's possible you could also take advantage of it's new option to flash only the 13 bootloader to both slots, and then will update the current slot to 13 completely.
Lughnasadh said:
FYI: Even though Android Flash Tool does not flash the whole image to both slots, they have added an option to flash the A13 bootloader to the inactive slot. This may be the easiest option to use when updating to A13 from A12.
Just to be clear, when updating to A13 from A12 a prompt will show up asking whether you want to also flash the bootloader to the inactive slot as well. It doesn't show up in the regular tick boxes.
{
"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"
}
Click to expand...
Click to collapse
FYI, you most definitely didn't need to re-lock the bootloader. Also, a pro tip for rooters. Once you unlock a device's bootloader, never ever re-lock it except in very rare circumstances. This didn't count as rare before you consult us.
I would have loved that it would be a solution.
It would allow me only to install android 12... and locking the bootloader make me affraid… I think I will never be able to unlock it cause I can’t use bootloader (see under)
For now, I try to make bootloader drivers working.
Every time I reboot to bootloader, the phone is not recognized by the computer and no adb/fastboot command can be used. So, I cannot use the flash-all.bat script.
Also, now when I use adb reboot fastboot the fastboot screen appears, then bootloader is loaded immediately...
I can’t believe I will spend several hours to be able to install that… I am stuck.
I tried to uninstall several drivers and reinstall drivers, but no changes... or yes a change. Now it is worst, Pixel 6 pro isn’t listed in device manager, and adb bootloader driver has disapear replaced by an adb driver line. Anyways, bootloader driver was never activated.
Edit: I should add that the update through the phone doesn’t work.
Don’t know why... the interface for google android flash tool changed... and now I was able to choose the version and I could flash the two slot with a13 bootloader.
Thanks for the idea...
Even if… I would love to understand why I did not succeed to install it...
Final edit: Android 13 has been successfully installed
Now, time to root it