Is there anyway to unlock the bootloader on this device.... each time i try to send the command :
PS D:\_DOOGEE S90 Pro_\ROOT> fastboot oem unlock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
is there any solution... i want to root my device but none of the tutorial i found on the web is working
thx
totallyfreak said:
Is there anyway to unlock the bootloader on this device.... each time i try to send the command :
PS D:\_DOOGEE S90 Pro_\ROOT> fastboot oem unlock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
is there any solution... i want to root my device but none of the tutorial i found on the web is working
thx
Click to expand...
Click to collapse
0. We answer the question, do we need it at all? If necessary, then why?
1. If the answer to the first item is positive, then go to the settings, to the "About phone" item, twist to the very bottom and poke at the "Build number" item many times, so we will unlock the "For Developers" menu.
2. We go back to the settings and go to the "System" section, there is the subsection "For Developers" we are looking for, go to it
3. Immediately we stumble upon the item "Factory unlocking", it is for the sake of it that we are doing all this now. We press, we agree with what they scare us.
3.1. Below is the item "Debugging via USB", we also click it, one day we will need it.
4. When flashing through adb, you will need to register the command below, and only after that do:
Code:
fastboot devices
If okay so the number Serial appears
Unlock
Code:
fastboot flashing unlock
See device screen and follow instructions.
TWRP 3.4.0: Doogee S96 Pro
yes all the things is done... oem unlock is turned on
usb debugging is turned on
PS D:\_DOOGEE S90 Pro_\ROOT> fastboot devices
S96PROEEA0000013829 fastboot
PS D:\_DOOGEE S90 Pro_\ROOT> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
totallyfreak said:
FAILED (remote: 'Unrecognized command flashing unlock')
Click to expand...
Click to collapse
If you followed 0~2 steps so need Update tool: Platform-Tools for Windows
i install the latest version and i still got this error message
is there anyone on the forum that already unlock bootloader on doogee s96 pro?
If fastboot is located in Android's user-space, what IDK because don't have your device, then IMO the correct command sequence is
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
fastboot flashing unlock
You need to turn on oem unlocking from developer option.
After that you can unlock bootloader. You need to flash mobile.
the oem is set to unlock eom... the usb debug is set on also... i still got this error message
PS D:\_DOOGEE S90 Pro_\ROOT> adb reboot fastboot
PS D:\_DOOGEE S90 Pro_\ROOT> fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 12.349s
PS D:\_DOOGEE S90 Pro_\ROOT> fastboot devices
S96PROEEA0000013829 fastboot
PS D:\_DOOGEE S90 Pro_\ROOT> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
PS D:\_DOOGEE S90 Pro_\ROOT>
totallyfreak said:
o oem está configurado para desbloquear o eom ... o usb debug também está ativado ... ainda recebo esta mensagem de erro
PS D: \ _ DOOGEE S90 Pro_ \ ROOT> adb reboot fastboot
PS D: \ _ DOOGEE S90 Pro_ \ ROOT> fastboot reinicializar fastboot
Reinicializando no fastboot OKAY [0.000s]
<esperando por qualquer dispositivo>
Finalizado. Tempo total: 12.349s
PS D: \ _ DOOGEE S90 Pro_ \ ROOT> dispositivos fastboot
S96PROEEA0000013829 fastboot
PS D: \ _ DOOGEE S90 Pro_ \ ROOT> desbloqueio de flashing de inicialização rápida
FALHA (remoto: 'Comando não reconhecido desbloqueio intermitente')
fastboot: erro: falha no comando
PS D: \ _ DOOGEE S90 Pro_ \ ROOT>
Click to expand...
Click to collapse
.
no its doogee s96 pro... my folder is wrong named... i run on android 10
totallyfreak said:
no its doogee s96 pro... my folder is wrong named... i run on android 10
Click to expand...
Click to collapse
My device has A10 too. I made simple steps to Unlock these:
In the device SO:
- OEM Unlock - select- USB Debugging - selectcmd command for know if adb work:
Code:
adb devices
If okay:
Code:
adb reboot bootloader
(or use the menu option).
The screen should show "FASTBOOT mode" at the bottom of the screen in small font:
cmd command for know if fastboot work:
Code:
fastboot devices
If okay:
Code:
fastboot flashing unlock
or
Code:
fastboot flashing unlock_critical
Read phone screen for instructions.You will have to press volume up key to continue to unlock.cmd command for reboot device:
Code:
fastboot reboot
Your device unlocked when you read the message in the device screen: Orange State
PS D:\_DOOGEE S90 Pro_\ROOT> fastboot devices
S96PROEEA0000013829 fastboot
PS D:\_DOOGEE S90 Pro_\ROOT> fastboot flashing unlock_critical
FAILED (Write to device failed (no link))
fastboot: error: Command failed
PS D:\_DOOGEE S90 Pro_\ROOT> fastboot flashing unlock_critical
FAILED (Write to device failed (no link))
fastboot: error: Command failed
PS D:\_DOOGEE S90 Pro_\ROOT> fastboot flashing unlock
FAILED (Write to device failed (no link))
fastboot: error: Command failed
PS D:\_DOOGEE S90 Pro_\ROOT> fastboot devices
S96PROEEA0000013829 fastboot
PS D:\_DOOGEE S90 Pro_\ROOT>
i realy dont know what to do... adb is installed correctly and the oem unlock and usb debug is checked
totallyfreak said:
PS D:\_DOOGEE S90 Pro_\ROOT> fastboot devices
S96PROEEA0000013829 fastboot
PS D:\_DOOGEE S90 Pro_\ROOT> fastboot flashing unlock_critical
FAILED (Write to device failed (no link))
fastboot: error: Command failed
PS D:\_DOOGEE S90 Pro_\ROOT> fastboot flashing unlock_critical
FAILED (Write to device failed (no link))
fastboot: error: Command failed
PS D:\_DOOGEE S90 Pro_\ROOT> fastboot flashing unlock
FAILED (Write to device failed (no link))
fastboot: error: Command failed
PS D:\_DOOGEE S90 Pro_\ROOT> fastboot devices
S96PROEEA0000013829 fastboot
PS D:\_DOOGEE S90 Pro_\ROOT>
i realy dont know what to do... adb is installed correctly and the oem unlock and usb debug is checked
Click to expand...
Click to collapse
Put the screenshot from your device:
- OEM Unlock and USB Debugging - - selected
Install Drivers: https://mega.nz/file/pGATVSrY#uOgE2wXIvQoNqcDoPEbiK5VWO9cqC0RhjL4WJE-WOkY
Try.
Maybe need more? Unzip adb&driver+installer.rar and install driver.
Use the adb from folder adb&driver installer\adb\ and try.
PS: Do not use fastboot reboot fastboot because it goes to fastbootD.
bootloader => fastboot <= this is a normal fastboot
fastbootD => advanced fastboot only for Super partitions
Ey,
I was triying to install TWRP, but I had many problems with Orange? or whatever and the fact that I wasn't able
to found any .img file to install TWRP. If someone can give me a link or a little help it would be amazing.
Thanks.
lopestom said:
0. We answer the question, do we need it at all? If necessary, then why?
1. If the answer to the first item is positive, then go to the settings, to the "About phone" item, twist to the very bottom and poke at the "Build number" item many times, so we will unlock the "For Developers" menu.
2. We go back to the settings and go to the "System" section, there is the subsection "For Developers" we are looking for, go to it
3. Immediately we stumble upon the item "Factory unlocking", it is for the sake of it that we are doing all this now. We press, we agree with what they scare us.
3.1. Below is the item "Debugging via USB", we also click it, one day we will need it.
4. When flashing through adb, you will need to register the command below, and only after that do:
Code:
fastboot devices
If okay so the number Serial appears
Unlock
Code:
fastboot flashing unlock
See device screen and follow instructions.
TWRP 3.4.0: Doogee S96 Pro
Click to expand...
Click to collapse
Ey,
Do you have a mirror link to the TWRP?
Because that one is 404... And i'm stuck in the process, I wasn't able to found it anywhere else on thi internet.
I will be very helpfull.
Thanks.
SrEstegosaurio said:
Ey,
I was triying to install TWRP, but I had many problems with Orange? or whatever and the fact that I wasn't able
to found any .img file to install TWRP. If someone can give me a link or a little help it would be amazing.
Thanks.
Click to expand...
Click to collapse
In bootloader unlocked that's message is normal. So only information Orange State show your device has bootloader unlocked. Now you can help totallyfreak unlocking bootloader with more instructions.
SrEstegosaurio said:
Ey,
Do you have a mirror link to the TWRP?
Because that one is 404... And i'm stuck in the process, I wasn't able to found it anywhere else on thi internet.
I will be very helpfull.
Thanks.
Click to expand...
Click to collapse
As you read in the post #2 TWRP 3.4.0;
Translate: READ - DOWNLOAD Files - FOLLOW Instructions.
Hi folks! I'm new here and Ihave a question about install TWRP on my Doogee S96 pro. In the past I rooted nearly all my phones...first Sony then some Xiaomi's.
Now I'm at the step to install TWRP via fastboot. The bootloader is unlocked and I see every time the orange state warning. If I install the TRWP image I see no failure. All is fine. But if I reboot to recovery I come to the stock recovery. I'm using the TWRP from here and nothing else I changed.
Is it possible I made a mistake for example I must rename the TWRP recovery.img? Or I must delete some user data?
And by the way...Doogee and updates. Anybody knows wheter android 11 is sheduled for the S96? Or is there a custom rom of Android 11?
I hope my question is clear!? I apologize in advance for any misunderstandings. Please ask me if i forgot some helpful information.
Greetings!
Hello again! Now TWRP is running. I tried with PowerShell. The first times I tried with "cmd".
But the next problem is the encryption in TWRP. How can I deactivate it?
Good night!
Mega-Flo said:
Hello again! Now TWRP is running. I tried with PowerShell. The first times I tried with "cmd".
But the next problem is the encryption in TWRP. How can I deactivate it?
Good night!
Click to expand...
Click to collapse
To decrypt a android phone, you usually have to reset to the original "non-encrypted" state, and then decide to not lock it with a code. Then do the installation process
I cant find any TWRP.
Related
Hi everyone.
I use adb to unlock my device (y6II) bootloader. When I type "fastboot oem unlock xxx" it says :FAILED (status malformed (1 bytes))
Is there anyway to solve the problem?
I am trying to unlock the bootloader for my device (it's a cheap Chinese phone) and then root using Magisk. The first problem is that OEM Unlock option is not available in developer options, so I got no choice other than try unlocking using fastboot. Now the second problem is that fastboot doesn't show anything at all. Normally there is a Fastboot written at the top left corner of the device but in my case there is no output but the blank screen, and I do verify that my device is in fastboot mode because when I do fastboot devices, it show's the output:
Code:
C:\Users\Mujtaba>adb devices
List of devices attached
Y3123A0310Q0100020953 device
C:\Users\Mujtaba>adb reboot bootloader
C:\Users\Mujtaba>fastboot devices
Y3123A0310Q01000209 fastboot
Since fastboot was responding (partially), I tried to unlock the bootloader using different commands but each time I get read/write failed error.
Code:
C:\Users\Mujtaba>fastboot oem unlock
...
FAILED (command write failed (Unknown error))
finished. total time: 5.011s
C:\Users\Mujtaba>fastboot oem unlock
...
FAILED (status read failed (Too many links))
finished. total time: 80.886s
Alas, I got the same results with fastboot oem unlock-go and fastboot flashing unlock as fastboot is not accepting (at least I think) any command except fastboot devices.
I read the official guide and there I found that:
Devices should deny the fastboot flashing unlock command unless the get_unlock_ability is set to 1. If set to 0, the user needs to boot to the home screen, open the Settings > System > Developer options menu and enable the OEM unlocking option (which sets the unlock_ability to 1).
Click to expand...
Click to collapse
My device supports unlocking bootloader because I've checked the build.prop file using adb shell getprop and it includes the properties stated below:
The ro.oem_unlock_supported property should be set at build time based on whether the device supports flashing unlock.
If the device suppports flashing unlock, set ro.oem_unlock_supported to 1. If the device doesn't support flashing unlock, set ro.oem_unlock_supported to 0. If the device supports flashing unlock, then the bootloader should indicate the lock status by setting the kernel command line variable androidboot.flash.locked to 1 if locked or 0 if unlocked.
For devices that support dm-verity, use ro.boot.verifiedbootstate to set the value of ro.boot.flash.locked to 0; this unlocks the bootloader if the verified boot state is orange.
Click to expand...
Click to collapse
Code:
C:\Users\Mujtaba>adb shell getprop
[ro.oem_unlock_supported]: [1]
[ro.boot.verifiedbootstate]: [green]
[ro.boot.flash.locked]: [1]
[sys.oem_unlock_allowed]: [0]
.
.
Someone on reddit did this to find the OEM unlock state, mine of course returned 0 as you can see above.
Code:
adb shell getprop sys.oem_unlock_allowed
Device Specs:
CPU: ARM Cortex-A-7 @ 1.20 Ghz
GPU: Mali-400 MP
Board: sp7731cea (Unisoc aka Spreadtrum)
Build: Q Infinity C_MP_26_01
Treble: NA
Seamless update (A/B): NA
So, is there any way to change it to 1 ?
Hello,
I'm trying to flash a custom a ROM for the first time but I'm facing some issues.
I'm using an Ubuntu 20.04 and my phone is an Asus Max Pro M1.
I can see my device with "adb devices" and I can boot in the bootloader with "adb reboot bootloader".
Then I can see my device with "fastboot devices". But when I'm trying another fastboot command (for example "flash recovery"/"flashing unlock"/"oem unlock") my terminal prompt is just hanging, I don't get any output. And it won't do anything until I restart my phone by pushing the power button, at that time it will just print three lines of logs telling me that the command failed.
Here is an example of what I get :
Bash:
[email protected]:~/Documents/Code/tel$ adb devices
List of devices attached
K3AXB762C86977F device
[email protected]:~/Documents/Code/tel$ adb reboot bootloader
[email protected]:~/Documents/Code/tel$ sudo fastboot oem unlock
...
FAILED (command write failed (Success))
finished. total time: 0.000s
Does anyone have an idea of what is happening ?
IMHO the typical command sequence is
Code:
adb devices
adb reboot fastboot
fastboot devices
fastboot <subcommand>
but I may err, as always ...
When name is the lpm file for asus zenfone, i want to change the script to automatically poweron device when charger connected
IMO it's far easier to achieve this by means of ADB and Fastboot IF Fastboot supports command oem off-mode-charge what you can verify with fastboot oem device-info command
Code:
adb reboot fastboot
fastboot reboot fastboot
fastboot flashing unlock <= ONLY IF BOOTLOADER NOT AREADY GOT UNLOCKED
fastboot oem off-mode-charge 0
fastboot reboot
this is a google translation sorry for mistakes.
I have a huawei p9 lite vns l31. i unlocked both frp and bootloader to try to root. I have installed the recovery revolution.
surely I made wrong maneuvers and now I find myself with this situation:
Bootloader unlocked
FRP lock
the operating system is blocked
when I try to start in recovery mode revolution appears for a few seconds and then the phone turns off and restarts with the message "your device is booting now" and remains blocked.
all the commands I send on the pc with fastboot returns me
"" C: \ adb> fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (22432 KB) ...
OKAY [0.552s]
writing 'recovery' ...
FAILED (remote: Command not allowed)
finished. total time: 0.561s ""
this is probably due to the blocked FRP?
Correct??
If this is the cause how can I unlock FRP ??
People typically remove all existing locks as also FRP before modding Android.
If phone is accessible by ADB you can try these ADB commands - one by one - to remove FRP lock:
Code:
adb devices
adb shell "am start -n com.google.android.gsf.login/"
adb shell "am start -n com.google.android.gsf.login.LoginActivity"
adb shell "content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1"
adb reboot