Database Info

[TOOL] WinDroid Toolkit | Unlock | Root | Flash | Install | One S

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.

Looks really good... Thus is exactly the kind if tools which gonna make customs ROMs more popular and our life's easier!
The GUI looks awesome!
Cheers for that!

Well done, this is great work!! I cant use it myself as I use a mac for my music production but I wish this was about when I was using windows. Would have made life much easier. :laugh:

EDIT: Thread re-opened.

Great Tool, should help new users who are uncomfortable with fastboot and adb.
Any instructions for new users?
Like do you need to have your phone in bootloader mode <fastboot usb> plugged into pc?
Or when your phone is on, do these commands automatically reboot to bootloader and run?
If so, should the user have usb debugging enabled in settings menu?

tivofool said:
Great Tool, should help new users who are uncomfortable with fastboot and adb.
Any instructions for new users?
Like do you need to have your phone in bootloader mode <fastboot usb> plugged into pc?
Or when your phone is on, do these commands automatically reboot to bootloader and run?
If so, should the user have usb debugging enabled in settings menu?
Click to expand...
Click to collapse
All the buttons are pretty self-explanatory. Almost all of the buttons automatically reboot to the necessary mode, and tell the user if something is needed of them, such as enabling USB Debugging, choosing a file, etc.

WindyCityRockr said:
All the buttons are pretty self-explanatory. Almost all of the buttons automatically reboot to the necessary mode, and tell the user if something is needed of them, such as enabling USB Debugging, choosing a file, etc.
Click to expand...
Click to collapse
Looks like a great tool for noobs look forward to some feedback I'll gladly pass on to such when I know all functions work! good job man!

Just like the all-in-one tool, but just simpler and looks pretty much more user-friendly. I'll try this tool with my friend's One S. Thanks to the OP. Great job! :thumbup:
Edit: and it'll be much more awesome if it'll have options like, s-on (from s-off), unroot, and relock bootloader.

Good morning.
Here I am, a totally newbie in the world of modding.
I bought the One S last year, and is still completely stock.
I would like to install a rom, but I don't know in which order should I press those buttons in the toolkit.
Thanks in advance

Hello guys, thats pretty much the best tool around ! Big regards to the dev. But I have a problem , i have HTC one s s4 and wanted to unlock bootloader, everything is fine until i have to press the unlock bootloader button , it says that cant find the device .. hmm whats wrong , its connected , it says fastboot USB is on .. so .. any help ?

beerfly said:
Hello guys, thats pretty much the best tool around ! Big regards to the dev. But I have a problem , i have HTC one s s4 and wanted to unlock bootloader, everything is fine until i have to press the unlock bootloader button , it says that cant find the device .. hmm whats wrong , its connected , it says fastboot USB is on .. so .. any help ?
Click to expand...
Click to collapse
just a thought have you put the unlock_token into the toolkit folder where adb & fastboot are?

rustykwak said:
just a thought have you put the unlock_token into the toolkit folder where adb & fastboot are?
Click to expand...
Click to collapse
Yes i did ...i noticed that when i select and press reset to bootloader command, the cmd window appwears, do whats supposed to do, when i need to use another command, I need to close this window, so I can use the tool, if not, the tool cannot be used as it is unactive while the cmd window is open ...hmmm. it says device offline , i updated all adb stuff, everything is alright .. only when i choose to unlock bootloader option it loses connection with my phone , no matter that fastboot usb is shown on bootloader status screen..
Fixed it after managed to find the command line and did it manualy
Sent from my HTC One S using xda premium

beerfly said:
Yes i did ...i noticed that when i select and press reset to bootloader command, the cmd window appwears, do whats supposed to do, when i need to use another command, I need to close this window, so I can use the tool, if not, the tool cannot be used as it is unactive while the cmd window is open ...hmmm. it says device offline , i updated all adb stuff, everything is alright .. only when i choose to unlock bootloader option it loses connection with my phone , no matter that fastboot usb is shown on bootloader status screen..
Fixed it after managed to find the command line and did it manualy
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
ok so when you extract the files in the zip on to your desktop leave the files in place dont remove the application out of folder with the data file folder the tool uses leave the app and data folder in its folder.
---------- Post added at 08:08 PM ---------- Previous post was at 08:04 PM ----------
Dont know if it would work better to put the phone into bootloader mode then fastboot usb mode then run the tool?

I wanna use this to s-off but trying to run tool i get this error.

RichieRich84 said:
I wanna use this to s-off but trying to run tool i get this error.
Click to expand...
Click to collapse
You need to install the latest .NET framework from here.

Thats a nice tool you got there. Definitely should be put in general section once the full guide has been written.

At last, this phone is gonna be rooted... but... when i put the Device Identifier Token in the dev. page of HTC, it's doing something, followed by a blank page and nothing else. Don't even get the email with the unlock code.. what to do?
-=SOLVED=-
If you don't get a response from HTC or a blank page.
goto:
http://forum.xda-developers.com/showthread.php?p=47215003#post47215003

I keep getting "error device not found" i installed the drivers and everything.

fusk said:
I keep getting "error device not found" i installed the drivers and everything.
Click to expand...
Click to collapse
Same here, ADB can't detect the device..

adb android not support on security

Hello, when im trying to change charge mode with command "fastboot oem off-mode-charge" i got message
Minimal ADB and Fastboot>fastboot oem off-mode-charge disable
...
FAILED (remote: not support on security)
finished. total time: 0.013s
Phone is unlocked (checked in fastboot getvar all unlocked: yes)
Phone is Alcatel 1x 2019 with android 6.0
Anyone can help me with it?

I also have the same problem with Hotwav (wheatek) H1 device. Unlocked the bootloader, but when trying to disable off-mode-charge I get the same error. Maybe there is some security setting that needs to be disabled first?

You both are speaking of FASTBOOT, and not of ADB as cited in this theads header.

Yes, but this is changed in fastboot, no? It should work, bu doesn't

I get the same error. And when I enter "adb devices" I get "1023456789ABCDEF unautorized". "fastboot devices" does not show anything

To fix this "unauthorized" error you
1. Revoke USB Debugging on phone
If the device is shown as unauthorized, go to the developer options on the phone and click "Revoke USB debugging authorization" .
2. Restart ADB Server:
Then restarted adb server
Code:
adb kill-server
adb start-server
3. Reconnect the device
The device will ask if you are agree to connect the computer id. You need to confirm it.
It is now authorized!

Doesn't change the original problem. The device appears as "0123456789ABCDEF", and setting "boot on charge" fails with cryptic error message "remote: not support on security". Typical chinese error message.
I am stuck. Can anyone help me? I bought this phone (Soyes XS12) to use it as a GPS car tracker, but what use is it if it doesn't automatically boot when charged.
{
"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"
}

time2fly said:
Doesn't change the original problem. The device appears as "0123456789ABCDEF", and setting "boot on charge" fails with cryptic error message "remote: not support on security". Typical chinese error message.
I am stuck. Can anyone help me? I bought this phone (Soyes XS12) to use it as a GPS car tracker, but what use is it if it doesn't automatically boot when charged.
View attachment 5899259
Click to expand...
Click to collapse
First of all: The command fastboot is for fastboot. The command adb is for adb. When booting into fastboot then adb doesn't work.
To use it in your car as GPS tracker. With an additionally mobile connection? Or only pure GPS? Where is the phone? Somewhere outside the car on the top or well hidden inside the glove box?
Let's assume your phone is able to get a GPS signal. How to track it?

Forget all the GPS info. I just want the phone to boot when I connect it to the charger. I know of the difference between adb and fastboot. I was just experimenting which tool could detect my device. While adb can, fastboot can't, because "0123456789ABCDEF" is obviouslly not a valid device id.

Looking at it, this seems intentional from manufacturer's side. They can enable it and you updated firmware if you pay a large sum of money. I've tried all the tricks and hacks mentioned in this forum – nothing helped. I don't know why these Chinese phones are so "secured". Trying to force businesses to pay when they discover that something rarely used by ordinary people but essential for some business project is disabled in the stock firmware?

Well, I don't consider "boot on charge" as rarely needed. Everyone who goes to bed at night and uses his phone as an alarmclock needs this. It's not understandable that this is not an option in the settings. And we're talking about Android 9 here!

0123456789ABCDEF instead of serialno indicates that is either a fake/clone device or someone has tinkered with that device already. most likely usual fastboot commands won't work. if you have possibility to root that device you can modify the para partition and set off-mode-charge manually.

time2fly said:
Forget all the GPS info. I just want the phone to boot when I connect it to the charger. I know of the difference between adb and fastboot. I was just experimenting which tool could detect my device. While adb can, fastboot can't, because "0123456789ABCDEF" is obviouslly not a valid device id.
Click to expand...
Click to collapse
Try fastboot oem help to see the available options/features. Maybe there is another corresponding option that needs to be enabled.

alecxs said:
0123456789ABCDEF instead of serialno indicates that is either a fake/clone device or someone has tinkered with that device already. most likely usual fastboot commands won't work. if you have possibility to root that device you can modify the para partition and set off-mode-charge manually.
Click to expand...
Click to collapse
Yes, that was my backup strategy. But how do I root it? There is no TWRP version for the Soyes XS12, and I have no other knowledge of how to root phones. I can seem to send adb commands, but not fastboot.

either with WwR MTK v2.51 beta + SP Flash Tool or with mtkclient. your first goal: dump the para partition or the ROM/boot.img off the phone while in preloader mode. once you have it, you can modify it or root the phone.
mtk-su could also work.

There is nothing you can do even if you root the phone. The system partitions cannot be mounted in r/w mode.

don't need to mount system rw on systemless-root.

Flashing for beginners!

Hi Guys,
I hope I'm in the right place here !? if not, I apologize, I'm new here
so, after finally unlocking the bootloader, I plan to change my Poco x3 (MIUI Global 12.0.7) to RR 10. In the past I have already changed Rome to LineageOS 10 on my old Leeco Le Pro 3. Now, after browsing the forum, I am very confused! how many things there are to consider! (I bricked my Leeco through a wrong TWRP installation, so I'm very careful). Decrypt (?), Clean / dirty Flash etc. were never an issue back then. Does anyone of you have a simple step-by-step description suitable for beginners of what should / must be observed (preferably in German)! Many thanks in advance!
H0rdak

Start here: https://telegra.ph/How-to-install-Poco-x3-ROM-10-14

Hi Pnin, thanks for the quick help! One question: what do you recommend for the first flash: clean or dirty?! Thx H0rdak

First must always be clean; dirty is only for updates (and sometimes, not even then).

pnin said:
Start here: https://telegra.ph/How-to-install-Poco-x3-ROM-10-14
Click to expand...
Click to collapse
Outdated. There is no need to boot to system after flashing ROM. Reboot to Recovery -> Flash Magisk & Gapps THEN reboot to system.

What about on Pixel 5. I want to flash ProtonAOSP And it says just flash as if you would the stock image, bc there is no TWRP for GP5. So does that mean I just use the flash-all command or fastboot boot ProtonAOSP.zip file? I'm confused as a motherF

hello people, thank you very much for the quick help! here you really get help! after pnin's execution, a few more questions have arisen:
1. is it really necessary to install gapps?
2. why orangefox and not TWRP? In the RR thread, twrp is recommended ?!
3. Which recovery is the most suitable (3.4.0-15 or 3.5.0-0 ???) - what are your experiences?
4. Is a special decrypt program necessary (in some youtube tutorials such a program is used)

1. Optional
2. Your call: OF appears to be a more polished product for the PX3 (some people reported isues with TWRP)
3. ...
4. ?

Thank you guys, and special thanks to Pnin! I have now decided to use OF as a recovery! Unfortunately the whole thing is a bit more difficult than I thought it would be. The problem: my pc doesn't recognize the phone! When I enter the adb command "adb devices", the x3 is not displayed ?! Any ideas?! Thanks in advance!!

drivers, drivers, drivers, check your device manager in windows, if there is an unrecognized device while your phone is connected to pc/notebook, that's the problem you need to solve

thanks jeryll, I feel a little stupid right now because I can't do it! there are dozens of sites offering drivers for the poco (i don't want to post any here). do you or someone have a link ?! it is a simple exe file right? !! sorry i'm a bit ashamed but i really have problems with that!

H0rdak said:
thanks jeryll, I feel a little stupid right now because I can't do it! there are dozens of sites offering drivers for the poco (i don't want to post any here). do you or someone have a link ?! it is a simple exe file right? !! sorry i'm a bit ashamed but i really have problems with that!
Click to expand...
Click to collapse
check this

thank you for your tireless help! but it still doesn't work! But when I enter the adb command this time this message comes up:
C:\adb> adb devices
* deamon not running. starting it now on port 5037 *
???

H0rdak said:
thank you for your tireless help! but it still doesn't work! But when I enter the adb command this time this message comes up:
C:\adb> adb devices
* deamon not running. starting it now on port 5037 *
???
Click to expand...
Click to collapse
this simply tells you that adb deamon is starting, because it was not running before...
check your device manager after you connect your phone to pc/notebook and look for this (picture is just an example)
{
"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"
}
if you see yellow triangle somewhere after you connect your phone and it was not there before, that means you don't have installed correct drivers
I need to know if you have installed recovery already, if not, you can not install it via adb, only via fastboot mode and your phone must be switched to fastboot mode (restart your phone and before it show initial screen hold volume down button until you see picture bellow)
with this on your phone screen connect your phone to your PC/notebook and check your device manager and look for devices with yellow triangle, if you see one you need to install correct driver for your device (for example try to start mipcsuite it *should* react and try to install correct drivers)
if you don't have yellow triangle in device manager try to type in cmd window
Code:
fastboot devices
if your phone is recognized you will see something like this
then you can continue with flashing orange fox recovery (download flashable zip with ofox recovery and extract recovery.img preferable to directory with fastboot app installed)
in cmd window type
Code:
fastboot flash recovery recovery.img
fastboot boot recovery recovery.img
if everything goes well after reboot you should be in orangefox recovery

WOW! this detailed description really helps me !!!! First of all: No, I haven't installed any recovery yet, I thought that could only be done via adb! Unfortunately, as you have described well, I see an orange triangle.
I have installed this mi-suite program but I cannot access the phone there either - it tells me that I have not installed any drivers, but does not give me the opportunity to do so ;-(
thx for your help greetings
H0rdak

people, i need help quickly! I don't know how, but I have now entered the "Poco-Recovery 3.0 mode" and have the option to select under Reboot / Wipe Data / Connect with Mi Assistance what should I do???

people, i need help quickly! I don't know how, but I have now entered the "Poco-Recovery 3.0 mode" and have the option to select under Reboot / Wipe Data / Connect with Mi Assistance what should I do???

H0rdak said:
people, i need help quickly! I don't know how, but I have now entered the "Poco-Recovery 3.0 mode" and have the option to select under Reboot / Wipe Data / Connect with Mi Assistance what should I do???
Click to expand...
Click to collapse
calm down, and choose Reboot (don't select Wipe data it will factory reset your device and you will loose eveything on your internal storage)

Pfewww .... everything is okay now Phone boots normally! Thx jeryll! no idea how that could happen. had a little flashback like with my Leeco; - /!
Okay, I think it depends on the drivers. All the pages I've looked at, however, only offer me strange drivers (like "POCO x3 Quallcomm driver" or things like that). Xiaomi's homepage doesn't offer any drivers at all - at least I can't find any there!
Jeryll, can you tell me what these drivers are called and where you can get them from? Many, many thanks in advance H0rdak

try this (untested, but looks legit)

ZS670KS rawprogram() and patch0

Dear all, my ZS670KS-2A014EU Asus Zenfone 7 flip has bricked. As well known now, an update in Android has caused some issue to his motherboard and I got the dump loop. Now it sticks on bootloader loop. Unfortunately I have never set an oem unluck and all flash via adb or fastboot have been run unsuccessfully. I have only one shot: put the phone in EDL and QFIL for flashing it.
Now: i miss the firers files *.mbn and the
rawprogram() and patch0 fire.I have also tried to use Python GPT tool to create partition.xml (from gpt_both0.bin) but I have got a parse error! I'm desperate!! Might someone of you, please support me giving more indications how to operate? Thanks in advance!

read in proper section for your device.
test points
ROM
prog_firehose_ddr_lp5.elf.E
EDL tool for creating rawprogram0.xml
if fastboot is working you can try to flash with unofficial Asus Flash Tool first. it may also possible to boot into EDL mode from fastboot.
Code:
fastboot oem enter-dload

aIecxs said:
read in proper section for your device.
test points
ROM
prog_firehose_ddr_lp5.elf.E
EDL tool for creating rawprogram0.xml
if fastboot is working you can try to flash with unofficial Asus Flash Tool first. it may also possible to boot into EDL mode from fastboot.
Code:
fastboot oem enter-dload
Click to expand...
Click to collapse
Thanks for your support.
I have tried
fastboot oem enter-dload
But it doesn't work.
An AFT is stucked in "Disconnected" process --> not working.
Finally I follow the original process with EDL and as before I'm stucked in point 4) creating the rawprogram () and patch0. The python job is blocking in this edl --serial and fhloadparse newstuff Loaders. It shows error that edl and fhloadparse are not known commands.
Any additional instructions?
Thanks in advance. BR

you can pass the loader directly from each cmd line
https://forum.xda-developers.com/t/4548939/post-88104871
or find the fhloaderparse in tools directory
https://forum.xda-developers.com/t/4531349/post-88029447

too many errors on python commands...I changed namesadding py (edl.py), changed the path, system variables...I followed all instructions in the link but I got " edl.py The system cannot execute the specified program". I will try under linux if it goes better than windozzz. Let's see

I have tried livecd and even Rom2Box too but I had no luck, I have several error "ssd.bin"missed.. etc. I was able to do rowprogram but I'm not sure if it's correct (i got several warnings). Ijust need to 2 files: rawprogram() and patch0. Can somebody provide me them fot my ZS670KS-2A014EU Asus Zenfone 7 flip? Thanks. BR.

no xml files needed for linux. what is the exact command that failed, and what error message?

You can always try my native Windows EDL client. http://www.temblast.com/edl.htm
The command arguments are different, but simple enough.
Editorial: This mania for rawprogram.xml is overblown.
Those stupid files are so much blah-blah-blah.
You only need to know 1) what file goes to 2) what partition.
"Lemme see, where would a recovery.img go?"
Disclaimer: Ok, if you were programming this in a factory and you want to program GPT and everything else without even reloading the GPT, this makes some marginal sense when you have a million to do.

Renate said:
You can always try my native Windows EDL client. http://www.temblast.com/edl.htm
The command arguments are different, but simple enough.
Editorial: This mania for rawprogram.xml is overblown.
Those stupid files are so much blah-blah-blah.
You only need to know 1) what file goes to 2) what partition.
"Lemme see, where would a recovery.img go?"
Disclaimer: Ok, if you were programming this in a factory and you want to program GPT and everything else without even reloading the GPT, this makes some marginal sense when you have a million to do.
Click to expand...
Click to collapse
Hi Renate, I got the error message "this app can not run on your pc"...
even with PowerShell:
edl.exe /l
Program 'edl.exe' failed to run: The specified executable is not a valid application for this OS platform.At line:1
char:1
+ edl.exe /l
+ ~~~~~~~~~~.
At line:1 char:1
+ edl.exe /l
+ ~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: ) [], ApplicationFailedException
+ FullyQualifiedErrorId : NativeCommandFailed
I have tried with Windows7 compatibility mode but nothing to do.
How to proceed?
Thanks.

pingolaido said:
Hi Renate, I got the error message "this app can not run on your pc"...
Click to expand...
Click to collapse
That is very stange. It's the type of error when the file is not even recognized as an executable.
Maybe the download was bad, grab a new copy.
http://www.temblast.com/download/edl.exe
Size=139,776
MD5=c106d7c6f742ec592e3b0636da756317
Mmm, don't you have to do .\edl.exe in PowerShell?
I don't use it.

Renate said:
That is very stange. It's the type of error when the file is not even recognized as an executable.
Maybe the download was bad, grab a new copy.
http://www.temblast.com/download/edl.exe
Size=139,776
MD5=c106d7c6f742ec592e3b0636da756317
Mmm, don't you have to do ./edl.exe in PowerShell?
I don't use it.
Click to expand...
Click to collapse
Hi,
I'm using the windows CMD prompt with Admin grants but I got the following error message:
C:\>edl.exe /l
Found EDL 9008
Could not open device
Could it be that device is locked? As I explaned since begining of the post, "USB debuging" was not enable in Android setting.
Any sugestions how to proceed? Thanks.

pingolaido said:
I'm using the windows CMD prompt with Admin grants but I got the following error message:
Click to expand...
Click to collapse
Your Qualcomm virtual com port drivers are stealing the interface.
Uninstall them and install the Zadig driver as per my EDL webpage.

Thanks for your prompt reply. I'm able to connect but I got this:
Found EDL 9008
Resetting Sahara
Could not write device
I think it's related to oem lock which I'm not able to unlock. Any further advices?

pingolaido said:
Could not write device
Click to expand...
Click to collapse
Do a clean reset back to EDL mode.
Sahara is balky, but it doesn't know anything (or care) about OEM anything.

I have cleaned all Qualcomm and Samsung drivers, re-instal Zadig WCID drivers (as in photo below), I have also put the phone in EDL modus hardwarly (pin connectors) but still got:
Found EDL 9008
Resetting Sahara
Could not write device
{
"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"
}

sorry,after 2 restarts it works... windows!!! I let you know

question about loaders: in the link of EDL.com there are loader in the folder "asus_wingtech" for Asus Zenfone ZS630KL, ZS660KL, zenfone_ares but not for my ZS670KS. Which shall I use? Thanks. BR

pingolaido said:
Which shall I use?
Click to expand...
Click to collapse
You may just have to try a few.
Loaders work for multiple models.
You can use my qcomview.exe to see which with qcomview.exe /m random_loader.bin
If a loader fails to load, you have to start over with fresh EDL mode.
Also, you can't disconnect the USB cable during EDL mode, replug it and expect it to work without another reset.
This is all a limitation of the Sahara implementation, not of the EDL client.

What about if I use prog_firehose_ddr_lp5.elf from raw stock rom? shall it work?

pingolaido said:
Shall it work?
Click to expand...
Click to collapse
I wouldn't know. Be careful. I saw some post about DDR specific loaders where some had the wrong voltage.
Why don't you (why didn't you?) post the HWID and Hash that edl printed out?

Question How can I root the Motorola Edge 30?

All i can find are tutorials for the Neo and Pro versions of this device. Can this version be rooted? How?

recovery sideload+magisk

alekksander said:
recovery sideload+magisk
Click to expand...
Click to collapse
Hey, thanks for the reply. I'm still new, can you elaborate? Maybe possibly link a tut? Appreciate it regardless.

alekksander said:
recovery sideload+magisk
Click to expand...
Click to collapse
What is recovery sideload?

useroso987 said:
What is recovery sideload?
Click to expand...
Click to collapse
Well, don't get me wrong, but if that's all unknown to you ... you'd better don't root your device ;-).
The risk to brick your device or open unforseen security wholes is quite too large, you'd better read some tutorials about flashing roms and customizations before trying to get into the world of Magisk.
Cheers
Kurt

Kurt Krummbein said:
Well, don't get me wrong, but if that's all unknown to you ... you'd better don't root your device ;-).
The risk to brick your device or open unforseen security wholes is quite too large, you'd better read some tutorials about flashing roms and customizations before trying to get into the world of Magisk.
Cheers
Kurt
Click to expand...
Click to collapse
Well, i've been reading past days...
I've installed Delta Magisk through adb on Lineage OS 20. It was quite a fast and interesting process!
Thank you.

Kurt Krummbein said:
Well, don't get me wrong, but if that's all unknown to you ... you'd better don't root your device ;-).
The risk to brick your device or open unforseen security wholes is quite too large, you'd better read some tutorials about flashing roms and customizations before trying to get into the world of Magisk.
Cheers
Kurt
Click to expand...
Click to collapse
Instead of being helpful you give some strange lessons it seems to me that you are useless here. If someone asks you politely for help, explain it to them. Every phone unlocks differently.

Kasjopea73 said:
Instead of being helpful you give some strange lessons it seems to me that you are useless here. If someone asks you politely for help, explain it to them.
Click to expand...
Click to collapse
Well, i tried to figure out, that not knowing the basics of running the phones recovery and using sideload is a bad starting point to open root access on the device.
Kasjopea73 said:
Every phone unlocks differently.
Click to expand...
Click to collapse
Well, that's not the core of my answer and i do not disagree ... just wanted to prevent a newbee from bricking his device and not beeing able to recover ;-) or walking around with a spy-phone recording and sharing his whole live-data with someone who should not know anything of it at all.
@Kasjopea73 : if you volonteer to answer request like "i tryied to root and bricked my device" in personal chat, then it's ok ... i've seen too many chats on other devices beeing flooded by those kind of requests, rendering these chats useless for developers who tried to exchange information on fixing problems.
Ciao
Kurt

Kurt Krummbein said:
Well, i tried to figure out, that not knowing the basics of running the phones recovery and using sideload is a bad starting point to open root access on the device.
Well, that's not the core of my answer and i do not disagree ... just wanted to prevent a newbee from bricking his device and not beeing able to recover ;-) or walking around with a spy-phone recording and sharing his whole live-data with someone who should not know anything of it at all.
@Kasjopea73 : if you volonteer to answer request like "i tryied to root and bricked my device" in personal chat, then it's ok ... i've seen too many chats on other devices beeing flooded by those kind of requests, rendering these chats useless for developers who tried to exchange information on fixing problems.
Ciao
Kurt
Click to expand...
Click to collapse
The best thing to do is not to write anything anymore, you are no help here and it is better to disappear. This is a forum for development, not for throwing obstacles under someone's feet. Rooting this phone is trivial, just extract the boot.img from the rom you are using, not from any other, and in magisk make a patch, instructions you will find below the post. If you don't know what is going on don't write nonsense to anyone.

Instructions Steps: Unlock Bootloader and Root​Platform Tools:
For Windows:​
Download File: Download
For macOS​
Download File: Download
For Linux​
Download File: Download
At first, you need to connect your device to PC via USB cable.
Next, head over to the platform-tools folder, then you have to type in CMD in the address bar and click enter. Command Prompt window will popup.
Now type the below command to boot your device into fast boot mode:
adb reboot bootloader
Next, you will need to get your device-specific unlock token. For that, execute the below command:
fastboot oem get_unlock_data
You will now get an alphanumeric character, that you have to copy all of the codes without the bootloader prefix. To follow this step, you may copy all the commands, paste it in a Notepad, and then delete the bootloader prefix. Further, make sure that there isn’t any space between any line of codes.
Now go to Motorola Unlock page and sign-in with your account. After this, copy that code and paste that into provided space. Then tap on the “Can my device be unlocked button”
Then, you will receive a Unique Key on your email. In normal scenerio, the code usually takes a few minutes to reach your email. But if not wait for few more minutes and you will get the code.
Go back the command prompt window and execute the below command. In the following command replace the UNIQUE_KEY with the key that you have received from Motorola.
fastboot oem unlock UNIQUE_KEY
Your bootloader is unlocked, after the whole process is done which will take few minutes. Now if your device doesn’t reboot to the system then you can use the below command to do it manually.
fastboot reboot
CONGRATULATIONS! YOU HAVE UNLOCKED THE BOOTLOADER OF YOUR DEVICE. NOW LET’S PROCEED TO ROOT THE DEVICE
2. ROOT MOTOROLA EDGE 30, PLUS ecc......​Thera are two ways root motorola edge plus: one is flashing SuperSu Zip with TWRP Recover and another one patching the boot.img file. Currerntly, there is no TWRP Recovery for motorola edge plus, so we will be choosing the latter (patching) option.
Instructions Steps:​
First download the stock firmware and extract the firmware file. Now search the stock boot file which would be named as boot.img. Copy this file to your Motorola edge plus.
Install Magisk Manager which you have downloaded earlier.
After installation, open magisk manager and tap on Install > Install > Select and Patch file (Here you have to select the boot.img file)
{
"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"
}
Magisk will start the patching process which will take just a few seconds.
After the patching process is done, you should see the magisk_patched.img in your internal storage’s Downloads folder.
Now you have to transfer magisk_patched.img to your platform-tools folder. Open CMD in this folder by searching “CMD” in the address bar and hit Enter.
Connect Motorola edge plus with PC via USB Cable and type the following command:
adb reboot bootloader
Now you have to flash magisk_patched.img and for that type the following command:
fastboot flash boot magisk_patched.img
The process will take only a few seconds. Once its complete, you may reboot your device via the following command:
fastboot reboot
Now you can open magisk manger and very the root as well.
CONGRATULATIONS! YOU HAVE SUCCESSFULLY ROOTED YOUR MOTOROLA EDGE PLUS.

There is another solution for making Root on Telegram groups. Unlock the bootloader and install TWRP then Magisk.

I did this as described, it works fine. I tried a couple of days with root and stock ROM but revert back to the original because of google wallet that didn't work suddenly.

hans3103 said:
I did this as described, it works fine. I tried a couple of days with root and stock ROM but revert back to the original because of google wallet that didn't work suddenly.
Click to expand...
Click to collapse
SafetyNet fix install