Database Info

[TOOL] schlexedeeler Tool V2 [ONLY ICS!] * ROOT Acer Iconia A210 [NOT USE ON JB!!]

{
"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"
}
lieckedeeler & schlex2010
aka SCHLEXEDEELER
ONLY USE THIS TOOL IF YOU HAVE AN ICS VERSION (4.0.4)
WE ARE NOT RESPONSIBLE FOR BRICK OR ANY OTHER ERRORS ON YOUR TABLET
WE ARE NOT RESPONSIBLE FOR BRICK OR ANY OTHER ERRORS ON YOUR TABLET
ONLY USE THIS TOOL IF YOU HAVE AN ICS VERSION (4.0.4)
- Root incl. su & busybox binary (install Superuser from Play Store)
- permanent RW on system folder
- adb root shell
- DVB-T USB support (schlexedeeler Kernel 1.1+)
- CWM Recovery with touch
Click to expand...
Click to collapse
DOWNLOAD SCHLEXEDEELER TOOL V2
=============================================================================================================================
If you want flash back stock kernel or/and stock recovery and stock bootanimation.zip
First step: Copy stcok bootanimation.zip to /system/media
Second step: Flash stock kernel & recovery
It is stock recovery and kernel out of ICS 4.0.4​​​
Download stock bootanimation.zip
Click to expand...
Click to collapse
Download Tool to flash stock kernel & stock recovery
Click to expand...
Click to collapse
Password for the 7zip files:
iknowtherisk!​
Click to expand...
Click to collapse

Thank you! Going to try this as soon as i get to my a210.

.... Placeholder ....

And you can just press the 3 point?, Only root, the kernel does not need to unlock me ....

Probably not. It dumps a CWR image to /dev (overwriting the factory recovery?), which is boot, so you have to be unlocked.
CWR is used to mount /system (rw) so that adb can push Superuser and some other binaries.
I got stuck, after loading up CWR. My Windows 7 (x64) couldn't recognize my A210 while CWR was running. Downloaded USB drivers through the Android SDK, and the Acer USB drivers, but neither of them did any good i continued with the rooting process (so that it could clean up after itself) but nothing got pushed to /system (which is no surprise, seeing my tablet was unrecognized). So, now i have an unlocked bootloader, no root, and i'm unable to get into recovery... nothing happens, if i hold volume down, while powering on. I have to press the reset button, to restart it properly.
Could it be that there are no drivers for Windows 7 x64?
Edit: ok, i've read through the topic at android-hilfe.de, and got it working (had to manually install the driver). Now i have root! Thank you!

help for dummies
deleted

deleted

does it give a instruction for this tool, it would be great
Greets

Is anyone working on a ROM or MOD for the Iconia A210 ?
Sent from my A210 using xda app-developers app

Hey 4.1.1 To have?

Alexey71 said:
Hey 4.1.1 To have?
Click to expand...
Click to collapse
What exactly is your question?
I don't know if it will work with 4.1.1, because I do not have 4,1.1 on my tablet! You have?

I get everything back to its factory state, or even be the standard kernel?

Alexey71 said:
I get everything back to its factory state, or even be the standard kernel?
Click to expand...
Click to collapse
Sorry for OT:
Please learn english, or use a better translater tool for your questions!
You use this tool at your own risk, so please stop bugging me with private messages AND forum posts!

Hy everybody
I tried to root my A210 yesterday using your program. But I point out some difference between what happen and the "how to".
First, I didn't have 4 option when I start the tool. I just have the bootloader option and a root option.
Following the "how to", I first activated the open mode to boot.Then, I choose the second choice (root) and that's when it didn't follow the "how to" document. My A210 did restart and boot to a*SCHLEXEDEELER edition but it never ask me to restore my data. And when it get restarted, everything was as it were.I also didn't have all the part about installing the driver because my PC still detect the tab as "adb interface".
I aldo never had the section about mount and unmount system.
Then the*SCHLEXEDEELER tool ask me if I wanted to install the custom recovery. As I was pretty scared of what might happened, I answered "no". So the tool ended.
I cheched on my tab but I was still not root so I did all that stuff again but choose "yes" instead of "no" for the custom recovery.The*SCHLEXEDEELER tool printed out many lines but one caught my attention.
It was something like :"data\tmp\cwm[...].img : no such file or dir".there is a file called "cwm[...].img" (the [...] is because I don't recall the exact name) in the folder in wich there is the*SCHLEXEDEELER tool.
But I didn't suceed in making it finding this file.
And when I checked whether I'm root or not, it turns out that I wasn't.
Any ideas or suggestion?
Still, thanks a lot for your job.

Tab acer A210 user said:
Hy everybody
I tried to root my A210 yesterday using your program. But I point out some difference between what happen and the "how to".
First, I didn't have 4 option when I start the tool. I just have the bootloader option and a root option.
Following the "how to", I first activated the open mode to boot.Then, I choose the second choice (root) and that's when it didn't follow the "how to" document. My A210 did restart and boot to a*SCHLEXEDEELER edition but it never ask me to restore my data. And when it get restarted, everything was as it were.I also didn't have all the part about installing the driver because my PC still detect the tab as "adb interface".
I aldo never had the section about mount and unmount system.
Then the*SCHLEXEDEELER tool ask me if I wanted to install the custom recovery. As I was pretty scared of what might happened, I answered "no". So the tool ended.
I cheched on my tab but I was still not root so I did all that stuff again but choose "yes" instead of "no" for the custom recovery.The*SCHLEXEDEELER tool printed out many lines but one caught my attention.
It was something like :"data\tmp\cwm[...].img : no such file or dir".there is a file called "cwm[...].img" (the [...] is because I don't recall the exact name) in the folder in wich there is the*SCHLEXEDEELER tool.
But I didn't suceed in making it finding this file.
Click to expand...
Click to collapse
FIRST OF ALL you don't read the thread correctly:​
The "How to" of Heroturtle is NOT for V2.0 Final Edition!! Do not use that "how to" !!​
So here is what the tool do if you select root:
Start your device into bootloader (fastboot mode)
Flash boot.img to your device via fastboot
Pushing binary files like su and busybox to your tablet
READY!
It's important that you have install all drivers correctly!
The 4 points are from the Versions before and are not necessary anymore now.
If you have done the root process, you must install SuperUser from the PlayStore! After that you have root!
Use only schlexedeeler Tool V2... You are confusing something and write about things that no longer exist in the new version!!! No restore my data. etc...

Sorry for my bad English
schlexedeeler Kernel 1.1, Not mount USB - NTFS format....

ok, got it.
I will try to install super user tonight and see if it's good.
I'll write a message to keep you inform about that.
thank you for your quick and pertinent reply

Tab acer A210 user said:
ok, got it.
I will try to install super user tonight and see if it's good.
I'll write a message to keep you inform about that.
thank you for your quick and pertinent reply
Click to expand...
Click to collapse
If not, please let me know, then we will find a solution for you, but I think if you do only that, what the tool tell you, you're on the right way :good:

Alexey71 said:
Sorry for my bad English
schlexedeeler Kernel 1.1, Not mount USB - NTFS format....
Click to expand...
Click to collapse
I will talk to lieckedeeler... Maybe he have a solution for that.

Minor Update 2.01:
* correct some missspellings
* correct adb command for flashing CWM recovery

[NO ROOT] [ALL DEVICES] Unlock PATTERN/PASSWORD/PIN without root

Hello everyone,
This thing has happened with all of us that our phone got locked and we don't know the pattern/password/PIN or either we ran out of our chances to enter it ( I hate those small kids ). So here's how you can unlock your device without factory reset. It should work on all devices with any android version (except the ones with locked bootloaders). You don't require root for this.
The pattern is stored in /data/system/gesture.key and password/PIN is stored in /data/system/password.key. So, what I did is, I just deleted the "gesture.key" and "password.key" files.
Here's the updater-script
Code:
ui_print("Mounting /data");
run_program("/sbin/busybox", "mount", "/data");
ui_print("Removing saved pattern/password/pin...");
delete("/data/system/gesture.key");
delete("/data/system/password.key");
ui_print("Unmounting /data");
run_program("/sbin/busybox", "umount", "/data");
THINGS REQUIRED
1) minimal adb and fastboot tool installed
2) PC with fastboot drivers for your device installed (Check your device forum for fastboot drivers for your device)
3) Custom recovery image for your device. You can use any custom recovery, but twrp and cwm are preferred.
You can search in your device forum for custom recoveries.
WHAT TO DO
1) Download the zip from the attachments and place it on your device.
2) Put the recovery.img for your device in "minimal adb and fastboot" folder on your pc.
2) Open your device in fastboot mode. (Search your device forum for this)
3) Press "Shift + Right Click" in adb and fastboot folder, and choose "open command window here"
4) Now type "fastboot devices" in the cmd window to check your device. If it says, no device found then you have not installed fastboot drivers correctly.
5) Now, type "fastboot boot recovery.img" (you must use the exact name of the recovery image you downloaded or you can rename it to recovery.img)
6) Your device will reboot into recovery.
7) Now select "Install zip" and choose the UNLOCK_PHONE_BY_SASUKAY.zip on your device.
8) Reboot your device.
Done!!
Now the next time you boot, you can enter any "more than 3-dot" pattern, if it asks. You can set new pattern or whatever, now.
:silly:
I made a video to show how easy it is :-

Cool....

skype
can we get connected on skype plss unlock my device

hari2829 said:
can we get connected on skype plss unlock my device
Click to expand...
Click to collapse
This tutorial is totally noob friendly. I've tried to explain everything. If you still get stuck somewhere, pm me.
:silly:

Is that working Samsung devices?
- Marhaba Mobile's -

FaizanChauhaan said:
Is that working Samsung devices?
- Marhaba Mobile's -
Click to expand...
Click to collapse
This will work for all the device having the gesture.key and password.key files in /data/system/ directory. I'm sure it'll work on any phone with any rom. (But, you can never be 100% sure with Samsung devices )

I have a similar problem - thanks for the tips!

Talking Head said:
I have a similar problem - thanks for the tips!
Click to expand...
Click to collapse
Did it worked for you..?

You can also unlock your phone without installing any tool or app.
Try this some easy steps to unlock your forgotten pattern lock/PIN/Password.

I dread this, so thanks for the tips!

jhonwright56 said:
You can also unlock your phone without installing any tool or app.
Try this some easy steps to unlock your forgotten pattern lock/PIN/Password.
Click to expand...
Click to collapse
Brother, this won't work if you don't have internet connection and can't access the quick toggle menu.

thank you cool

najeebzoom said:
thank you cool
Click to expand...
Click to collapse
Happy to help

Video tutorial showing the complete process added
:-B :silly:

Help me pls. I manually deleted "gesture.key" and "password.key" via twrp when i deleted it it has a red line says your kernel does not support something like that but it still deleted because i can see that the "gesture.key" and "password.key" vanishes. Then i restarted my phone but still it wants to confirm my gmail. My phone is SGY-5360 samsung HELP please. THANK YOU!

Confirmed! Working on Lenovo X2 Vibe-EU!

for this method does usb debugging be enabled?

Didn't work with android 9 on htc u12+

sasukay said:
Video tutorial showing the complete process added
:-B :silly:
Click to expand...
Click to collapse
Hey mate, can you help me out fixing my phone. its Coolpad note 3 and its locked.
I tried your method listed above but when I type fastboot devices in CMD, it says "waiting for device" and nothing happens.
{
"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"
}
I dont know if my device bootloader is locked or not, I can get into fastboot yellow warning thing & USB debugging is off...... Please help, I will buy you a coffeee..

Joshua95869 said:
for this method does usb debugging be enabled?
Click to expand...
Click to collapse
Can anyone please answer this question?

[Root] Telcast X80 Plus root

{
"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"
}
Tutorials and the tools are not my work, so I don't take any credit. However, the tutorial is come from China. I combine my experience and translate them as much as I can to english.
Instructions:
First, download the root files (at the bottom of this post) accroding to your tablet model (at the back of your tablet) and install the driver in the computer.
Please install in the following order:
1) iSocUSB-Driver-Setup-1.2.0.exe
2) IntelAndroidDrvSetup1.5.0.exe
3) PhoneFlashTool_5.3.4.0_win32.exe
Pay attention to the following points
a) you must install those driver in the above order
b) Don't change the install location of those driver
c) Close your antivirus software to avoid unknow problem
Then, go to Settings>Developer Options>USB Debugging. Enable OEM Unlock and enable USB Debugging Mode
Now, connect your X80 Plus to the computer,
Open a Command Prompt window in "Root X80 Plus H6C3" folder (To open a Command Prompt window in any folder, hold down the shift key and right-click on the folder) and enter the following command
Code:
adb reboot bootloader
Press Enter
Wait for the device to enter fastboot mode
Code:
fastboot oem unlock
Press Enter to unlock the oem and enter the following command
Code:
fastboot flash boot boot.img
Press enter to flash the kernal, then enter the following command
Code:
fastboot reboot
This command will restart your tablet.
It is normal that tablet reboot 3 to 4 times automatically, just wait for it. (turn on the tablet yourself if the tablet do not reboot automatically)
After your device is on, check that Wifi and bluetooth works or not. (Wifi and Bluetooth may not works with the replaced kernal, just perform a factory reset)
If everything is ok, enter the following command
Code:
root.bat
Wait for the Command Prompt until it stuck at this command, "adb shell su --daemon"
Now, disconnect the tablet and reboot it manuly
After the device was booted up, Supersu already become a part of system app.
Open Supersu now, it will notify that the SU binary needs to be updated. You must need to install the binary once, but you will fail at 100%(unless there is a miracle, and your tablet is root successfully, congratulations)
Close Supersu and reconnect the tablet, enter the following command again.
Code:
root.bat
Now the command prompt should run all of the command smoothly and Supersu should have no message about the SU binary update !!
Therefore, if your Supersu shows nothing (works properly), your tablet is rooted, thats amazing.
If Supersu keep notifing, please enter the following command again and wait for it to boot up automatically until Supersu have no message about the binary update.
Code:
root.bat
Note that this root method are not stable yet
Known issues:
1) Old version of Titanium Backup was unable to execute the SU command
2) LBE are not 100% compatible with this root
Post reply if you have any requires or problem.
Stock Rom for X80 Plus just in case you need them, and the instruction will be translated later
H6C3 and H5C5
Root files: H6C3 and H5C5
Sorry for my bad english

Hi and thanks for sharing.
Is there a custom recovery to install?
I would like to install xposed framework, but don't know how to install the zip file...
Thanks

thanks and your thread on teclast's forum where the link was crash, please repair.

Thanks a lot

Can someone confim that this method works?

Jeconxis said:
thanks and your thread on teclast's forum where the link was crash, please repair.
Click to expand...
Click to collapse
You can try to flash xposed using flashify!

woody4165 said:
Hi and thanks for sharing.
Is there a custom recovery to install?
I would like to install xposed framework, but don't know how to install the zip file...
Thanks
Click to expand...
Click to collapse
Working hard on it now

hahaha1111 said:
Working hard on it now
Click to expand...
Click to collapse
looking forward to this!

Thaaanks a lot @hahaha1111 !!! I tried that on my all new H6C4 received this morning with your H6C3 files and anything is working perfectly !!! Many thanks again !!!
BTW: Any way to update SuperSU binary then?

I tried your method on my H5C6 and it worked beautifully. Thank you!

where can I use the file?
I download the file named X80 plus-win10_20160108.7z from the link. what is this, and where can I use it?

hahaha1111 said:
Working hard on it now
Click to expand...
Click to collapse
Hi @hahaha1111
any news on custom recovery?
I would like to install xposed framework, but cannot be done without custom recovery, is it correct?
Thanks

woody4165 said:
Hi @hahaha1111
any news on custom recovery?
I would like to install xposed framework, but cannot be done without custom recovery, is it correct?
Thanks
Click to expand...
Click to collapse
Hiatus

H6C4
Great! It works perfectly on H6C4.
Thanks!
Regards

RoroTiti said:
Thaaanks a lot @hahaha1111 !!! I tried that on my all new H6C4 received this morning with your H6C3 files and anything is working perfectly !!! Many thanks again !!!
BTW: Any way to update SuperSU binary then?
Click to expand...
Click to collapse
It's updated from play market with no problem.
May be it is my particular problem ( kernel 3.14.37 firmware assembly ver 3.03.20161109) but.....
WARNING TO H6C4 OWNERS! SD Card becomes unusable with this rooting files. Any SD Card after rooting recognized as 0,9 Mb size and you can't access files on it. You can't use SD Card reader too.
Please report if you do not encounter this issue.

Hi.
I'm stuck on "adb push SUfiles/Superuser.apk /data/superuser" command in root.bat
I've done all the previous steps without problems.
Before executing root.bat I have set again Usb Debug and OEM Unlock, is it correct?
Sometimes I get stuck on "adb remount"
What can I check?
Thanks
Woody

Doogee S68 Pro - Fastboot commands not working

Hi. So i have this issue. My brother has this phone (Doogee S68 Pro) and like a month ago almost every app in the system started to crash. Even 3rd party apps. I tried to update Android System WebView but it was already on latest version so i tried to opt-in to beta versions and no difference here. He also did make a factory reset through recovery mode and the problem still persists. So resetting the device to factory mode doesn't solve this issue. So i told him i could flash a custom ROM to see if that solves the problem. Only custom ROM for that device i could find was LineageOS 17.1. So i unlocked OEM, enabled USB debugging and adb commands work. Only issue is that when i access fastboot and type "fastboot devices" the command line doesn't output any text. It just send the command and nothing happens. Not even "waiting for any device". Only when i type some random stuff like "fastboot erjsifjes" then it says "waiting for any device". I also tried to install universal adb drivers, but the device shows up as Kedacom USB Device in device manager without any yellow exclamation mark or anything. It just shows up like it's properly installed and it works. But when i try to type any fastboot command other than "fastboot devices" it says "waiting for any device". I'm lost. I tried every possible way to make this work but no luck. What am i doing wrong? I disabled driver verification in Windows 10 (idk how it's named in english i'm using czech version but you know what i mean), so the drivers were installed properly. Is there any way how i can bypass the fastboot? I was looking in the recovery menu and there's a method to install "update" via ADB. So can i unlock bootloader this way? Help me please i don't know what to do now. I'm lost...

{
"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"
}
adb commands work in system but not in fastboot

To get Fastboot working install the Doogee USB Driver suitable to your phone:
Doogee S68 Pro USB Driver for Windows (Official Mobile Driver)
Download the official Doogee S68 Pro USB Driver for your Doogee Mobile. We also provide all other Doogee Mobile drivers for free.
gsmusbdriver.com

Uhhh. I don't wanna disappoint you but i have already tried to install them. Both of the drivers included there . That was actually the first thing i tried. When the official drivers didn't work i tried installing universal ADB drivers, still same issue. Anyway i decided to buy a new phone. This piece of s*** is outdated anyways. If the apps didn't crash i wouldn't tried to flash custom ROM which i can't anyways.

Stupid question : Your phone is in Fastboot mode when you try the Fastboot commands right ?!
Are you using the latest version of the ADB and Fastboot Tools ?
You could try installing the following tool : https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Make sure you use a USB 2.0 port if possible!
If not then try a USB Hub between the phone and the PC or Laptop
Other things you could try :
- Use Windows 7 instead of anything newer.
- Use a Linux distro instead of Windows for the ADB and Fastboot part.
Good luck!

Update:
I got in touch with Doogee support and their technician. The problem was in trying to flash ROM in fastboot mode. They provide me SP Flash Tool which is used to flash ROMs, recovery, bootloader, etc. But the device needs to be turned off. This is kinda new for me, 'cause every time i was flashing ROMs or anything, i was doing it in fastboot mode with fastboot commands. The SP Flash Tool worked. Kinda. It allowed me to flash stock ROM successfully but it didn't solve the crashing apps issue. So yeah. I managed to progress further but still not the result i was hoping for. Still wanting to flash LineageOS 17.1 based on Android 10 in a hope that it'll solve my problem. When i tried flashing TWRP recovery straight up made for Doogee S68Pro with SP Flash Tool, it shows "Red State" message (see attachment) while booting the system (not able to enter recovery mode). Any ideas how to disable "verified boot"? I am able to access recovery through adb commands from system, however it enters the stock recovery menu, not TWRP which i did flashed. What am I doing wrong?

nero355 said:
Stupid question : Your phone is in Fastboot mode when you try the Fastboot commands right ?!
Are you using the latest version of the ADB and Fastboot Tools ?
You could try installing the following tool : https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Make sure you use a USB 2.0 port if possible!
If not then try a USB Hub between the phone and the PC or Laptop
Other things you could try :
- Use Windows 7 instead of anything newer.
- Use a Linux distro instead of Windows for the ADB and Fastboot part.
Good luck!
Click to expand...
Click to collapse
Yup.
- Device was in fastboot mode while typing fastboot commands. But not a single response from console.
- ADB and Fastboot was downloaded before creating this topic so i assume it was the latest version. Downloaded straight up from official Google page.
- Tried every single USB-C cable that i found, combined with every single USB port on my computer. (that took some time but need to be checked)
- To assure it was not my desktop PC what was potentially the problem, i also tried my brothers desktop PC with totally different HW components and operating system (his was W10, mine W11).
- I was thinking of creating dualboot system on my PC with W11 (primary) and W7 (secondary for this purpose) to try if that was the issue. (still open possibility)
- Same answer above

The drivers ( adb & fastboot ) you downloaded from Google are to be used with Google devices: you have to make use of the relevant drivers provided by DOGEE.

CaptainFedora said:
Update:
Still wanting to flash LineageOS 17.1 based on Android 10 in a hope that it'll solve my problem. When i tried flashing TWRP recovery straight up made for Doogee S68Pro with SP Flash Tool, it shows "Red State" message (see attachment) while booting the system (not able to enter recovery mode). Any ideas how to disable "verified boot"? I am able to access recovery through adb commands from system, however it enters the stock recovery menu, not TWRP which i did flashed. What am I doing wrong?
Click to expand...
Click to collapse
From : https://www.getdroidtips.com/lineage-os-17-1-doogee-s68-pro-android-10/
This should be the way : https://www.getdroidtips.com/twrp-recovery-doogee-s68-pro/
So no VBmeta.img needed it seems ?!

Yes! I was using the method mentioned in the first link. Never found that second link you provided. It looks very promising! I'm gonna try it in this week and post report. Man, that would be awesome.

You have to modify the usb driver .inf file. Add this rows to end of [Google.NTamd64] section:
;Doogee S68 Pro
%SingleBootLoaderInterface% = USB_Install, USB\VID_0E8D&PID_201C
%SingleAdbInterface% = USB_Install, USB\VID_0E8D&PID_201D&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E8D&PID_2006&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
Need a computer restart (shif+Restart in start menu) and have to switch off the signed drivers recommandation.

Hi ksanci ,and thank you very much it is work for me

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