hello, as stated from the title i would kindly need your help in order to understand if-and-how Moto E6 Plus can be unlocked.
when i reboot the smartphone via adb (/adb reboot bootloader/) i can only see a simple barcode. unfortunately the upsaid barcode didn't help me. the barcode itself doesn't report any number/s or text. that said, on Motorola website i cannot really find any article about how-or-where i should be supposed to use that barcode.
by looking for info online, on XDA and reddit, some users suggested to type the following command/s:
fastboot flashing unlock_critical
(or)
fastboot oem get_unlock_data
shortly, i will always get an error "command not supported/command failed".
i have already been unlocking and flashing different smartphones (mostly Samsung and Huawei) with no problems. Moto E6 Plus doesn't seem to be that easy. please, if you know something, gimme some information. if the device is impossible to unlock for real, i will just stop bothering.
thanks ahead time for your dealing.
-redpillar
redpillar said:
hello, as stated from the title i would kindly need your help in order to understand if-and-how Moto E6 Plus can be unlocked.
when i reboot the smartphone via adb (/adb reboot bootloader/) i can only see a simple barcode. unfortunately the upsaid barcode didn't help me. the barcode itself doesn't report any number/s or text. that said, on Motorola website i cannot really find any article about how-or-where i should be supposed to use that barcode.
by looking for info online, on XDA and reddit, some users suggested to type the following command/s:
fastboot flashing unlock_critical
(or)
fastboot oem get_unlock_data
shortly, i will always get an error "command not supported/command failed".
i have already been unlocking and flashing different smartphones (mostly Samsung and Huawei) with no problems. Moto E6 Plus doesn't seem to be that easy. please, if you know something, gimme some information. if the device is impossible to unlock for real, i will just stop bothering.
thanks ahead time for your dealing.
-redpillar
Click to expand...
Click to collapse
Seems that if you see barcodes, the moto device cannot be unlocked.
There is some general moto bootloader unlocking info in my
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Seems that if you see barcodes, the moto device cannot be unlocked.
There is some general moto bootloader unlocking info in my
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I have same problem on moto e6s. Can you help solve this?
Mortyk said:
I have same problem on moto e6s. Can you help solve this?
Click to expand...
Click to collapse
//deteled by author - keep reading
redpillar said:
hello, as stated from the title i would kindly need your help in order to understand if-and-how Moto E6 Plus can be unlocked.
when i reboot the smartphone via adb (/adb reboot bootloader/) i can only see a simple barcode. unfortunately the upsaid barcode didn't help me. the barcode itself doesn't report any number/s or text. that said, on Motorola website i cannot really find any article about how-or-where i should be supposed to use that barcode.
by looking for info online, on XDA and reddit, some users suggested to type the following command/s:
fastboot flashing unlock_critical
(or)
fastboot oem get_unlock_data
shortly, i will always get an error "command not supported/command failed".
i have already been unlocking and flashing different smartphones (mostly Samsung and Huawei) with no problems. Moto E6 Plus doesn't seem to be that easy. please, if you know something, gimme some information. if the device is impossible to unlock for real, i will just stop bothering.
thanks ahead time for your dealing.
-redpillar
Click to expand...
Click to collapse
There is an unlocking guide in the guides section, but I'll still leave you the link to the xda post
[GUIDE] How to unlock bootloader in the Moto E6 Plus + Install TWRP, with Windows and Linux
Hello guys, in this guide I will tell you how to unlock the bootloader of the Moto E6 Plus. READ THE FULL GUIDE TO AVOID ERRORS IN THE PROCESS SINCE THIS UNLOCKING METHOD IS DIFFERENT FROM OTHER MOTOROLA PHONE. DISCLAIMER: /* * * Your warranty...
forum.xda-developers.com
LichtEstarossx said:
There is an unlocking guide in the guides section, but I'll still leave you the link to the xda post
[GUIDE] How to unlock bootloader in the Moto E6 Plus + Install TWRP, with Windows and Linux
Hello guys, in this guide I will tell you how to unlock the bootloader of the Moto E6 Plus. READ THE FULL GUIDE TO AVOID ERRORS IN THE PROCESS SINCE THIS UNLOCKING METHOD IS DIFFERENT FROM OTHER MOTOROLA PHONE. DISCLAIMER: /* * * Your warranty...
forum.xda-developers.com
Click to expand...
Click to collapse
indeed that topic is more recent than mine, that's why i totally miss that!
thank you very much! hugs!
Related
Can any developer please please help me out quickly? i'm out of time seriously I need help but quick.
I'm trying to unlock my device Redmi Note 3 Snapdragon varient. All the other commands like
* adb devices
* adb reboot edl
* fastboot devices
* fastboot oem device-info
everyone of it is working fine but when I write
* fastboot oem unlock-go
I get the above mentioned error.
Does anybody know the solution to it? Before answering please consider that other commands are working except this one, I didn't found any proper solution that's why posted the problem here and I already did revoke USB debugging permissions and turned it on again but that didn't helped.
So please give me a working solution as quick as possible or else any help is appreciable.
enable oem unlock in developer options
Enable OEM Unlock option in Developer Options.
caesar13th said:
enable oem unlock in developer options
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
superboy123 said:
Enable OEM Unlock option in Developer Options.
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Gurkirat_Singh said:
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Click to expand...
Click to collapse
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
superboy123 said:
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
Click to expand...
Click to collapse
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Gurkirat_Singh said:
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Click to expand...
Click to collapse
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
superboy123 said:
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
Click to expand...
Click to collapse
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Gurkirat_Singh said:
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Click to expand...
Click to collapse
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
Thanks for all the support and help you gave me.
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
caesar13th said:
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Gurkirat_Singh said:
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Click to expand...
Click to collapse
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
superboy123 said:
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
Click to expand...
Click to collapse
I appreciate your help but the post you gave me is for non-asian countries so it will not work for me. As you already know I'm an Indian so that's why. Are you an Indian, only asking cause in that way you may already faced the problems i'm having.
I'm only familiar with only 2 4G networks for now. One is Airtel 4G, what they say have FDD LTE network, I don't what that is, but that's why it's not working on my phone, I contacted them and they said that my phone doesn't support it, I don't know why cause it support much more LTE Bands other than any smartphone in that price range. Second is Jio 4G, my sim gets detected, shows network in manual selection but doesn't get registered on them. I see only the message of 'No Service' or 'Emergency calls only' when I insert it.
@Gurkirat_Singh
It worked for me.
I had the same problem!
superboy123 said:
@Gurkirat_Singh
It worked for me.
I had the same problem!
Click to expand...
Click to collapse
What worked for you and how? Can you please answer/clarify my questions/doubts please also?
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
superboy123 said:
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
Click to expand...
Click to collapse
OK I'll try when got time and will update you with the result.
Having trouble rooting my LG K40. I have the same problem as this person when trying to boot into fastmode: https:// youtu.be/yQ99lQv0rQk?t=26
You can find his post here explaining the process more in detail: https:// lgk20.com/root-lg-k40-lm-x420-bootloader-unlock-twrp/
MODEL #: LM-X420MM
Any help is appreciated,
Thanks in advance.
im having the same problem. i must have a proclivity towards phones with what seems impossible rooting methods. the first was the samsung j7 prime and now the lg k40 lmx420mm. ive gotten as for as adb reboot-bootloader, just restarts device, fastboot commands are either not recognized or i receive "waiting on device". Ive updated drivers, followed a diff. method found on reddit posted by jamesrascal (i cant post url here because of my newb status). Phone just stays stuck in firmware update. i feel as if ive exhausted all resources, any direction or help would be appreciated, im not educated on rooting ive been successful a few times on other phones and jailbroken some iphones, im mostly doing this to learn and teach myself so it isnt urgent but i need help to continue any further. thank you
Same problem for me. Because the device has good value for the money it would be nice someone can help us here.
Further this device seems to be full android treble conform I like to know how benefit from this circomstance.
I have LG K40 LM-X420EMW with dualsim.
Thanks for every hint!
@blanksus
IIRC an Android user can not unlock the bootloader without first OEM unlocking, because without this process the device will not accept the bootloader unlocking command.
jwoegerbauer said:
@blanksus
IIRC an Android user can not unlock the bootloader without first OEM unlocking, because without this process the device will not accept the bootloader unlocking command.
Click to expand...
Click to collapse
OK, but it is not possible to get into fastboot mode to enable the OEM unlocking. I marked the slider in developer option butz still there is no chance to get in fastboot mode.
After command "adb reboot bootloader" the device always reboots in normal system mode.
@baerenbisch
Once you enabled the OEM unlock on your Android, the “unlock ability” flag is set to 1, which allows you to use the
Code:
fastboot flashing unlock
command what unlocks device's bootloader.
BTW: Once you have enabled OEM unlock, it stays on. Even if you do a factory reset, it stays unlocked until the setting is manually altered again by going into the Developer options section.
jwoegerbauer said:
@baerenbisch
Once you enabled the OEM unlock on your Android, the “unlock ability” flag is set to 1, which allows you to use the
Code:
fastboot flashing unlock
command what unlocks device's bootloader.
BTW: Once you have enabled OEM unlock, it stays on. Even if you do a factory reset, it stays unlocked until the setting is manually altered again by going into the Developer options section.
Click to expand...
Click to collapse
Hm,
may be it is "allowed" to unlock but in the "LG K40 (LM-X420EMW) real world" it is not possible.
You dont reach fastboot mode which could enable using the order you proposed.
Device reboots into standard mode instead of wanted fastboot mode after sending "adb reboot bootloader"
I think thats the problem.
Code:
[email protected]:/# adb devices
List of devices attached
LMX4205P4TU4S4HEOJ device
[email protected]:/# adb reboot bootloader
[email protected]:/# fastboot flashing unlock
< waiting for any device >
^C
[email protected]:/#
OK, good news. One can get root with this method:
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Works for LG K40 (LM-X420EMW) Android 9 Kernel 4.9.117 Patch Level January 1, 2020 Build Nr. PKQ1.190522.001 Software-Vers. V20d-EEA-XX
baerenbisch said:
OK, good news. One can get root with this method:
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Works for LG K40 (LM-X420EMW) Android 9 Kernel 4.9.117 Patch Level January 1, 2020 Build Nr. PKQ1.190522.001 Software-Vers. V20d-EEA-XX
Click to expand...
Click to collapse
Temp root does sound nice, but what can you actually do with it. Can you change the OEM unlock key?
roycrt said:
Temp root does sound nice, but what can you actually do with it. Can you change the OEM unlock key?
Click to expand...
Click to collapse
Device can be bootloader unlocked now. MtkClient on github. I have the Harmony 3 bl unlocked and twrp for it
Can confirm, I was just able to unlock the bootloader with mtkclient and root with Magisk from there.
BenTheTechGuy said:
Can confirm, I was just able to unlock the bootloader with mtkclient and root with Magisk from there.
Click to expand...
Click to collapse
Please elaborate steps taken to unlock bootloader using mtkclient. Thanks
I wrote a guide as part of my porting of postmarketOS to my K40.
LG K40 (lg-mmh4x) - postmarketOS
wiki.postmarketos.org
So. I have an OPPO Reno 2Z CPH1951 and am having problems with unlocking the bootloader, I have emailed oppo support about it and they say just to enable OEM unlocking with 100% battery so I did that yet I still can't get into the bootloader.
I should say my phone is fully updated.
If anybody could help them please do.
Thanks
DM me on discord for faster reply
Discord: laykonlee2014#6866
Same here. CPH1951, ColorOS 7. I have enabled unlock bootloader from developers options. Then using
Code:
adb reboot bootloader
I get a message on the screen for one second
Code:
The serial is not match
fast oem unlock verify fail
And it boots normally. When I try to enter bootloader from recovery or using volume up button, it just boots without any message.
Can anyone help?
How to root oppo reno 2z please ?
Doulraa said:
How to root oppo reno 2z please ?
Click to expand...
Click to collapse
I don'w know. I was unable to boot to fastboot and unlock in order to and flash twrp or a rooted boot.img.
I also was unable to use MTK flashtool on this device to flash anything. None of the guides worked for this device.
Anyone managed to use MTK flashtool on any oppo reno 2 phone?
PassiveModding12 said:
...
If anybody could help them please do.
Thanks
DM me on discord for faster reply
Discord: laykonlee2014#6866
Click to expand...
Click to collapse
I'd appreciate if you share your knowledge and experience here in this thread instead by DM/PM. The latter doesn't help anybody else who has similar issues.
10. Help others if you can.
If you see posts from others where you can help out, please do so. This place exists because people are helping each other, and even if you are relatively new to the matter, there's probably quite a few people with less experience than you, who could benefit from what you've learned. Don't be shy.
Click to expand...
Click to collapse
Dimim said:
Same here. CPH1951, ColorOS 7. I have enabled unlock bootloader from developers options. Then using
Code:
adb reboot bootloader
I get a message on the screen for one second
Code:
The serial is not match
fast oem unlock verify fail
And it boots normally. When I try to enter bootloader from recovery or using volume up button, it just boots without any message.
Can anyone help?
Click to expand...
Click to collapse
i have the same problem but the code is
Code:
The serial is not match
fastboot_verify_fail
please help me (
I got a locked tracfone moto g play from a relatives. I try to flash twrp to use other roms. But when I try to unlock bootloader it said:
(bootloader) usage: fastboot oem unlock < unlock code >
FAILED (remote failure)
finished. total time: 0.080s
Does that mean I have to contact the carrier to unlock my phone so I can unlock booloader? And if it is, are there any ways to install twrp without unlock it? Pls help me?
Thank for reading!
Not the carrier but Motorola is who you have to contact. In fact the only thing you need to do is register your phone with Motorola. Follow the instructions as stated officially by Motorola in order to get your device ID and check if your device qualifies for an unlock code. Keep in mind this is not a network/carrier lock. This is for unlocking the phone's bootloader which is essential for rooting and flashing.
In regards to TWRP it may be a hit or miss with how you follow what you got to do based on the posts spread throughout this forum and whether you'll have a flawless experience with a fully functional TWRP, or you may have one of the phones manufactured with some slightly different hardware which winds up TWRP flashing OK but no touchscreen capabilities. Or you may not even get or need to flash it and get by just sideloading the image.
Honestly, reading thru all relevant threads will be your best interest. Check out the other like-design Moto G 2021 device forums as well for additional insight on how these devices behave, quirks and common issues, etc. Good luck and try to have fun doing this.
First of all, i need to say that my english is not the best since im from brazil, anyway that said, im trying to unlock my realme bootloader, ive already tried to use Deep test. But every time that i try to install the app i recive this error messange "An app with the same signature has already been installed", and i also have tried using ADB and Fastboot, but every time that i try to reboot my cellphone in fastboot, it only gives me a black screen and restarts the cellphone, if anyone know some way to resolve this, or know what to do, would help me a lot
It's possible that some fastboots have a timeout if you don't talk to them.
Are you sure that you're not getting fastboot at all?
Are you using Linux or Windows? lsusb or devmgmt.msc?
Renate said:
It's possible that some fastboots have a timeout if you don't talk to them.
Are you sure that you're not getting fastboot at all?
Are you using Linux or Windows? lsusb or devmgmt.msc?
Click to expand...
Click to collapse
im using windows, my primary suspect is that im in fact not getting to the fastboot at all
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016 I was surprised to not find this information in any of the forums. This is why I'm posting this thread to prevent further confusion and future xda-enthusiastic "Phone...
forum.xda-developers.com
Wow, 2016? And they haven't gone out of business yet?
aIecxs said:
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016 I was surprised to not find this information in any of the forums. This is why I'm posting this thread to prevent further confusion and future xda-enthusiastic "Phone...
forum.xda-developers.com
Click to expand...
Click to collapse
wow i didnt have read or found anything about this, but that gives me a little question, how do ppl actually flashs custom ROM's on realme phones?
you can unlock with official In-Depth Test apk
or
unofficial unlock method without fastboot (mtkclient)
aIecxs said:
you can unlock with official In-Depth Test apk
or
unofficial unlock method without fastboot (mtkclient)
Click to expand...
Click to collapse
When i try to use in-depth test says "Device incompatible"
of course that was just example possibility, I don't know if apk exist or unlocking seccfg works. do your homework
[DISCUSSION] A thread to collate and share what is known about unlocking fastboot on Oppo devices
Admin: Please move/delete this thread if it is in the wrong place or against the rules. I wanted to create a thread to discuss unlocking fastboot mode on Oppo devices in general, rather than discussing it in terms of any one device in...
forum.xda-developers.com
when i use Deep Test 1.0.1 it says that my device dosent suport deep test, when i try to install the 1.1.0 version thats happens
try this