in the Developer menu has enabled "Unlock OEM".
I run the following commands in adb, and get the following errors:
fastboot flashing unlock =
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed
fastboot oem unlook =
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
fastboot flash recovery recovery.img =
Sending 'recovery' (14100 KB) OKAY [ 0.599s]
Writing 'recovery' F**AILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')**
fastboot: error: Command failed
{
"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"
}
Please help.
Thanks
+1, same thing happening to me, halp
shraga1 said:
in the Developer menu has enabled "Unlock OEM".
I run the following commands in adb, and get the following errors:
fastboot flashing unlock =
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed
fastboot oem unlook =
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
fastboot flash recovery recovery.img =
Sending 'recovery' (14100 KB) OKAY [ 0.599s]
Writing 'recovery' F**AILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')**
fastboot: error: Command failed
Please help.
Thanks
Click to expand...
Click to collapse
So we could not be able to root this tablet?
Im not even able to let the tablet and the pc communicate together. In adb devices there is no devices, i think is a drivers problem.... i cannot see the mmc of the tablet in my computer....
simone81 said:
Im not even able to let the tablet and the pc communicate together. In adb devices there is no devices, i think is a drivers problem.... i cannot see the mmc of the tablet in my computer....
Click to expand...
Click to collapse
which drivers have you installed?
pabloluih said:
which drivers have you installed?
Click to expand...
Click to collapse
I did connect the tablet to the pc, the problem was in the cable, now i can enter in fastboot but i dont know wich command to use to unlock the bootloader, i tried fastboot oem unlock and it give me as a result failed because unknown command. I hope there will be a way to root it because its very good device. The drivers i used are available online here https://www.getdroidtips.com/root-teclast-p80x-4g/
Go on youtube and find "Teclast Root Process for Android Tablet"
I haven't found a solution but thought this might help.
I thought this might be of some use - however on their website putting in the P80X ID doesn't yield any firmware.
Perhaps you guys can make heads and tails of it.
How do you even get in the developer menu? The usual build number clicking doesn't seem to work on the P80X
ttps://forum.hovatek.com/thread-32287.html
Explained in detail on this site.
few__ said:
ttps://forum.hovatek.com/thread-32287.html
Explained in detail on this site.
Click to expand...
Click to collapse
Thanks for the reply with information. I managed to unlock the bootloader shortly after i posted the message. I'm currently still stuck on flashing a patched magisk boot.img to it.
/edit: Funny, i posted the reply a few hours before i managed to flash a patched and signed boot.img
delete
null
mainframe_cn said:
Thanks for the reply with information. I managed to unlock the bootloader shortly after i posted the message. I'm currently still stuck on flashing a patched magisk boot.img to it.
/edit: Funny, i posted the reply a few hours before i managed to flash a patched and signed boot.img
Click to expand...
Click to collapse
how did you unlock the bootloader?
mainframe_cn said:
Thanks for the reply with information. I managed to unlock the bootloader shortly after i posted the message.
Click to expand...
Click to collapse
That's great and all, but HOW?
Remember, forums are not only for you, but for others too. Share your knowledge!
Related
Hey,
I have unlocked the bootloader in Honor 7C (LND-L29). (dcunlocker)
I was looking on the internet and I can not find anywhere.
twrp does not work on this phone. It can not be installed by the command flash recovery twrp.img
How do you install root? Kingroot does not work
remkac96 said:
Hey,
I have unlocked the bootloader in Honor 7C (LND-L29). (dcunlocker)
I was looking on the internet and I can not find anywhere.
twrp does not work on this phone. It can not be installed by the command flash recovery twrp.img
How do you install root? Kingroot does not work
Click to expand...
Click to collapse
Sup,
Before proceeding, enable "manufacturer mode" on your phone. This is done by entering in dial pad code *#*#2846579#*#* select "Project Menu", "Background settings", "USB ports settings", "Manufacture mode". Then connect it to PC and Hisuite for drivers.
flash TWRP made by Augustoandro, flash Supersu
Greetz
Leak1337 said:
Sup,
Before proceeding, enable "manufacturer mode" on your phone. This is done by entering in dial pad code *#*#2846579#*#* select "Project Menu", "Background settings", "USB ports settings", "Manufacture mode". Then connect it to PC and Hisuite for drivers.
flash TWRP made by Augustoandro, flash Supersu
Greetz
Click to expand...
Click to collapse
{
"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"
}
fastboot flash recovery TWRP_Honor7C_LND-L29.img
target reported max download size of 534773760 bytes
sending 'recovery' (4896 KB)...
OKAY [ 0.144s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.183s
remkac96 said:
fastboot flash recovery TWRP_Honor7C_LND-L29.img
target reported max download size of 534773760 bytes
sending 'recovery' (4896 KB)...
OKAY [ 0.144s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.183s
Click to expand...
Click to collapse
Ok, have you tried the multitool? MultiTool Honor 7
Step by step Tutorial look if you have done everything and try it with the tool. Tutorial
Leak1337 said:
Ok, have you tried the multitool? MultiTool Honor 7
Step by step Tutorial look if you have done everything and try it with the tool. Tutorial
Click to expand...
Click to collapse
We managed to install, but internal memory in twrp does not work.
After several attempts to repair twrp. The system does not turn on in the phone. He is now trying to install the rom from the new version using Huawei eRecovery
I also tried to upload the twrp from this topic: https://4pda.ru/forum/index.php?s=&showtopic=909546&view=findpost&p=78962423
After uploading by multitool, it does not even turn on twrp.
If someone has uploaded root on this phone, let them write in what way. I've tried many options and still nothing of it.
Sorry my bad english.
remkac96 said:
I also tried to upload the twrp from this topic: https://4pda.ru/forum/index.php?s=&showtopic=909546&view=findpost&p=78962423
After uploading by multitool, it does not even turn on twrp.
If someone has uploaded root on this phone, let them write in what way. I've tried many options and still nothing of it.
Sorry my bad english.
Click to expand...
Click to collapse
All twrp installed by me does not load internal memory.
Can uh tell me how you unlocked the bootloader?
Hey man, its great to hear this first of all that you successfully unlocked the bootloader,
Please tell how you unlocked it.
Thanks in advance for you help.
So I tried to flash android 10 so that I could flash android 10 roms but twrp kept giving me the ok but not actually installing the OS eventually I got stuck on fast boot (IDK why twrp is gone might have done something wrong in the process). So now Im trying to flash the stock rom on my Mi A3 but it wont work, using miflash gives me the miss matching image and device error which may mean the rom is not the right version (dl'ed rom is version 10.3.13, the version of my Mi A3 should be 10.3.14) but Im not sure if that's whats causing the error and I also cant find a zip for version 10.3.14 to test my guess. Hopefully someone can help me because I'm stumped on what to do.
Problem Solved Thanks @Valiko89
*Keep in mind you need to unlock the bootloader first ('fastboot falshing unlock' and 'fastboot falshing unlock_critical')
get the latest ver. fastboot rom according to your region (global/europe) then extract the TGZ, its an archive > inside you'll find another archive but TAR > extract it to and point miflash to that extracted folder
{
"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"
}
This is what I did in the past 48H hours to get back to stock:
Valiko89 said:
Well that was almost 48H wild ride
lol looks im too dumb to run adb shell as root cuz after adb shell I always got 'not found' also couldn't find the actual up to date ota on 4pda
So I got slightly older ver. ota gave up on the tune2fs step and headed on extracting the system.img from the payload.bin then flashing it blindly using 'fastboot flash system system.img' and when done got thrown back to yesterday - no phone at all just plain xiaomi logo yayyy fml!
But! on the same 4pda I stumbled upon the latest V10.3.17.0.PFQEUXM Fastboot recovery, and after poking around the web re-flashing the whole damn thing with the stock fastboot rom seemed like not such a bad idea at this point of my frustration.
By now the whole a/b slot tuned into one huge salad in my head so I went for sure and this is what I did:
1. boot to fastboot manually
2. 'fastboot flashing unlock' (holding vol down to return back to fastboot)
3. 'fastboot' flashing unlock_critical (holding vol down to return back to fastboot)
4. 'fastboot --set-active=a'
5. flashed the extracted tar folder with MiFlash and holding vol down near finish to return back to fastboot
6. 'fastboot --set-active=b'
7. flashed the same extracted tar folder again with MiFlash and holding vol down near finish to return back to fastboot
8. 'fastboot flashing lock_critical'
9. 'fastboot reboot'
And hooray! It booted to latest updated rom will have to wait for next OTA update to see if it works at all :cyclops:
Click to expand...
Click to collapse
Valiko89 said:
*Keep in mind you need to unlock the bootloader first ('fastboot falshing unlock' and 'fastboot falshing unlock_critical')
get the latest ver. fastboot rom according to your region (global/europe) then extract the TGZ, its an archive > inside you'll find another archive but TAR > extract it to and point miflash to that extracted folder
This is what I did in the past 48H hours to get back to stock:
Click to expand...
Click to collapse
Thanks, Although I already have my bootloader unlocked. I'll try flashing using the latest version
Edit: I just realized that when I initially flashed I had it set to lock the bootloader.....
Edit2: fastboot is weird
PS C:\Users\AJY\Downloads\Compressed\platform-tools_r29.0.6-windows\platform-tools> .\fastboot.exe devices
47f092a82f41 fastboot
PS C:\Users\AJY\Downloads\Compressed\platform-tools_r29.0.6-windows\platform-tools> .\fastboot.exe flashing unlock
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
PS C:\Users\AJY\Downloads\Compressed\platform-tools_r29.0.6-windows\platform-tools> .\fastboot.exe flashing unlock
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
PS C:\Users\AJY\Downloads\Compressed\platform-tools_r29.0.6-windows\platform-tools> .\fastboot.exe flashing unlock_critical
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
Akubane said:
Thanks, Although I already have my bootloader unlocked. I'll try flashing using the latest version
Edit: I just realized that when I initially flashed I had it set to lock the bootloader.....
Edit2: fastboot is weird
PS C:\Users\AJY\Downloads\Compressed\platform-tools_r29.0.6-windows\platform-tools> .\fastboot.exe devices
47f092a82f41 fastboot
PS C:\Users\AJY\Downloads\Compressed\platform-tools_r29.0.6-windows\platform-tools> .\fastboot.exe flashing unlock
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
PS C:\Users\AJY\Downloads\Compressed\platform-tools_r29.0.6-windows\platform-tools> .\fastboot.exe flashing unlock
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
PS C:\Users\AJY\Downloads\Compressed\platform-tools_r29.0.6-windows\platform-tools> .\fastboot.exe flashing unlock_critical
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
Click to expand...
Click to collapse
This one "FAILED (Write to device failed (Unknown error))" was weird.. have you tried a different usb cable and/or port?
Valiko89 said:
This one "FAILED (Write to device failed (Unknown error))" was weird.. have you tried a different usb cable and/or port?
Click to expand...
Click to collapse
Yeah, actually despite those errors I was able to flash stock rom. Its just those errors are really wierd.
Glad I was able to help by solving my own issue
Hi, so I successfully installed TWRP from here, everything went well until this point. I flashed a more stable EU rom and then tried to flash Magisk, but when I rebooted it just went to fastboot mode.
Now everytime I try to turn it off or go back into TWRP it just goes to fastboot mode.
I have tried to flash using MiFlash but I can't seem to get the right thing to flash apparently.
When trying to reinstall TWRP
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 4.498s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.503s
{
"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"
}
Zelyric said:
View attachment 5448807
Click to expand...
Click to collapse
Getting Mismatched image error in fastboot when trying to flash stable/developer ROM.
Hello.. Which fastboot rom is correct for my mido Device.. i downloaded Both Stable and Developer version both giving mismatched image error.. tried flashing from mi flash tool, flashed in 1sec issue.. Please help , how am i suppose to flash...
forum.xda-developers.com
I hope it helps.
akins0405 said:
Getting Mismatched image error in fastboot when trying to flash stable/developer ROM.
Hello.. Which fastboot rom is correct for my mido Device.. i downloaded Both Stable and Developer version both giving mismatched image error.. tried flashing from mi flash tool, flashed in 1sec issue.. Please help , how am i suppose to flash...
forum.xda-developers.com
I hope it helps.
Click to expand...
Click to collapse
Reading on that post I saw that there are issues with Ryzen powered computers, and I indeed have a Ryzen CPU. Really hopes this helps, thanks for showing me regardless - ill keep you updated!
@akins0405
Zelyric said:
@akins0405
Click to expand...
Click to collapse
Try flashing you stock boot img
akins0405 said:
Try flashing you stock boot img
Click to expand...
Click to collapse
Where do I find that?
Zelyric said:
Where do I find that?
Click to expand...
Click to collapse
You have it in fastboot stock rom
Zelyric said:
Where do I find that?
Click to expand...
Click to collapse
Try to transfer the rom to the system partition
akins0405 said:
Try flashing you stock boot img
Click to expand...
Click to collapse
adb doesn't show my device under adb devices but fastboot devices does show it..
MTP also is disabled
Zelyric said:
adb doesn't show my device under adb devices but fastboot devices does show it..
Click to expand...
Click to collapse
Flash in fastboot stock boot img, can you do it
akins0405 said:
Flash in fastboot stock boot img, can you do it
Click to expand...
Click to collapse
fastboot flash b boot.img
Sending 'b' (196608 KB) OKAY [ 4.817s]
Writing 'b' FAILED (remote: '(b_a) No such partition')
fastboot: error: Command failed
nevermind, i understood the partition wrong.
fastboot flash boot boot.img
Sending 'boot_a' (196608 KB) OKAY [ 4.558s]
Writing 'boot_a' OKAY [ 0.707s]
Finished. Total time: 6.103s
what now?
Zelyric said:
@akins0405
Click to expand...
Click to collapse
Try firstly erasing your recovery partition with fastboot erase recovery
Somehow I have managed to fix it on my own, thank you for your response regardless @akins0405 @SubwayChamp.
Here's how I fixed it for the people wanting to know:
I flashed boot.img via fastboot, I have no clue if it had effect on what I did afterwards but I think it might.
I moved the folder of all the files to my main C:\ directory, and then tried to flash using MiFlash and it worked.
I'm trilled to have it back in a ''working'' state
Zelyric said:
Somehow I have managed to fix it on my own, thank you for your response regardless @akins0405 @SubwayChamp.
Here's how I fixed it for the people wanting to know:
I flashed boot.img via fastboot, I have no clue if it had effect on what I did afterwards but I think it might.
I moved the folder of all the files to my main C:\ directory, and then tried to flash using MiFlash and it worked.
I'm trilled to have it back in a ''working'' state
Click to expand...
Click to collapse
I'm glad you made it, hello
I have a Unisoc UMS512 chipset device.
I can't unlock bootloader.
I do this link : https://forum.hovatek.com/thread-32287.html
But I take this error.
"
downloading 'unlock_message'...
OKAY [ 0.001s]
unlocking bootloader...
FAILED (remote: Unlock bootloader fail.)
finished. total time: 0.101s
"
What should I do ?
Please help me, Thanks
(Sorry my bad english)
{
"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"
}
UP UP UP. I need a help
I have unlocked my Motorola G20 with Unisoc T700 chipset with fastboot easily - without signature.bin. Then I had to follow instructions on the device to unlock. Try another USB 2.0 port and another cable too.
BASKAN53 said:
I have a Unisoc UMS512 chipset device.
I can't unlock bootloader.
I do this link : https://forum.hovatek.com/thread-32287.html
But I take this error.
"
downloading 'unlock_message'...
OKAY [ 0.001s]
unlocking bootloader...
FAILED (remote: Unlock bootloader fail.)
finished. total time: 0.101s
"
What should I do ?
Please help me, Thanks
(Sorry my bad english)
View attachment 5516217
View attachment 5516219
Click to expand...
Click to collapse
try out my post to see if it helps
Alldocube T803 Smile_1 Bootloader unlock w/ Unisoc T310
All files can be downloaded from the iplay40 tread. MUST use iPlay40 fastboot version or else it will fail using commands. Download install SpreadTrumTools-20200317.apk run command -- adb shell getprop ro.serialno Enter the serial you get from...
forum.xda-developers.com
Thread is up
I have same issue when I try to unlock bootloader of Infinix hot 11 unisoc t610 processor phone ..
Can someone help me out with this...
srinidroid said:
I have same issue when I try to unlock bootloader of Infinix hot 11 unisoc t610 processor phone ..
Can someone help me out with this...
Click to expand...
Click to collapse
I also have this device, did you find anything new aboutt unlocking?
jovisense said:
I also have this device, did you find anything new aboutt unlocking?
Click to expand...
Click to collapse
No :/
BASKAN53 said:
No :/
Click to expand...
Click to collapse
Hm i noticed that the icons on status bar is very close to edge, do u know any workaround?
BASKAN53 said:
UP UP UP. I need a help
Click to expand...
Click to collapse
Robyn_232 said:
I have unlocked my Motorola G20 with Unisoc T700 chipset with fastboot easily - without signature.bin. Then I had to follow instructions on the device to unlock. Try another USB 2.0 port and another cable too.
Click to expand...
Click to collapse
can you tell me pls how you have unlocked the bootloader of your unisoc without signature.bin?
By using fastboot.
fastboot flashing unlock_bootloader
I used this command:-
$ fastboot oem get_identifier_token
And got this in return:-
(bootloader) Identifier token:
(bootloader) 30303231364437303141323630393233
(bootloader) 313041413031424e
OKAY [ 0.022s]
Finished. Total time: 0.023s
What should I do next?
at next forget about what you have done and type: fastboot flashing unlock_bootloader
this is how i did it...
Robyn_232 said:
at next forget about what you have done and type: fastboot flashing unlock_bootloader
this is how i did it...
Click to expand...
Click to collapse
tried that didn't work
enable oem unlocking in developer settings
Robyn_232 said:
enable oem unlocking in developer settings
Click to expand...
Click to collapse
Don't you think I did it?
Got the same problem, seems like private key not working anymore for new devices
vanelizarov said:
Got the same problem, seems like private key not working anymore for new devices
Click to expand...
Click to collapse
What did you try?
I'm trying to root my motorola g6 plus but when I run the command
fastboot oem get_unlock_data
I get this response:
(bootloader) 'get_unlock_datas' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.007s
I do notice here that up on top of the response it says that it doesn't recognise 'get_unlock_datas' which is certainly not what i typed, i typed 'get_unlock_data'
Okay so I took a break from writing this and tried to type the command in manually instead of having it copied from motorola's website, only this time it worked. However, the next time I tried writing it manually I got the same message just that instead of it saying 'get_unlock_datas' it said, 'get_unlock_da'.
I guessed that my machine was having trouble understanding what I was typing and sometimes thought I typed 'da' or 'datas' instead of 'data'.
So I did what I thought would fix it and typed the command in until it worked, and it did.
I did however run into a couple more errors like this one:
(bootloader) slot-counttas: not found
(bootloader) slot-suffixes: not found
(bootloader) s: not found
...
(bootloader) 'get_unlock_da' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.003s
On maybe my 10th try of copy pasting the code I finally succeeded, I would like to know why I don't get my desired response when typing 'fastboot oem get_unlock_data'. Keep in mind I am very new to rooting.
(Don't mind my bad grammar I figured you'd still be able to understand what i'm writing and this isn't an exam.)
iwanttoroot said:
I'm trying to root my motorola g6 plus but when I run the command
fastboot oem get_unlock_data
I get this response:
(bootloader) 'get_unlock_datas' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.007s
I do notice here that up on top of the response it says that it doesn't recognise 'get_unlock_datas' which is certainly not what i typed, i typed 'get_unlock_data'
Okay so I took a break from writing this and tried to type the command in manually instead of having it copied from motorola's website, only this time it worked. However, the next time I tried writing it manually I got the same message just that instead of it saying 'get_unlock_datas' it said, 'get_unlock_da'.
I guessed that my machine was having trouble understanding what I was typing and sometimes thought I typed 'da' or 'datas' instead of 'data'.
So I did what I thought would fix it and typed the command in until it worked, and it did.
I did however run into a couple more errors like this one:
(bootloader) slot-counttas: not found
(bootloader) slot-suffixes: not found
(bootloader) s: not found
...
(bootloader) 'get_unlock_da' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.003s
On maybe my 10th try of copy pasting the code I finally succeeded, I would like to know why I don't get my desired response when typing 'fastboot oem get_unlock_data'. Keep in mind I am very new to rooting.
(Don't mind my bad grammar I figured you'd still be able to understand what i'm writing and this isn't an exam.)
Click to expand...
Click to collapse
You need to connect the device with a USB-HUB. A direct connection over USB in fastboot mode is possible, but you are not able to run any command. Don't ask me why, but it works. Just try it.
WoKoschekk said:
You need to connect the device with a USB-HUB. A direct connection over USB in fastboot mode is possible, but you are not able to run any command. Don't ask me why, but it works. Just try it.
Click to expand...
Click to collapse
Do you mean one of those USB extender things like this?
{
"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"
}
iwanttoroot said:
Do you mean one of those USB extender things like this? View attachment 5724301
Click to expand...
Click to collapse
yes, that's exactly what I mean.
WoKoschekk said:
yes, that's exactly what I mean.
Click to expand...
Click to collapse
Okay thanks I'll try
WoKoschekk said:
yes, that's exactly what I mean.
Click to expand...
Click to collapse
I have now successfully rooted my motorola g6 after 2 years of struggles, thank you.
WoKoschekk said:
You need to connect the device with a USB-HUB. A direct connection over USB in fastboot mode is possible, but you are not able to run any command. Don't ask me why, but it works. Just try it.
Click to expand...
Click to collapse
You, sir... are a genius! thank so much!
But i also have a problem. When i go to the fastboot on cellphone it gets a black screen.. i still could send the commands to unlock the boatloader, but now i cant get to install the twrp or magisk.. i dont know if its a outdated fastboot os something. Can u guys help me?
alexestanislau said:
But i also have a problem. When i go to the fastboot on cellphone it gets a black screen.. i still could send the commands to unlock the boatloader, but now i cant get to install the twrp or magisk.. i dont know if its a outdated fastboot os something. Can u guys help me?
Click to expand...
Click to collapse
Fastboot mode is only a UI for some bootloader commands. The known screen with the green Robot is only a .png file stored in your logo.bin. Did you modify your logo.bin (boot logo)?
WoKoschekk said:
Fastboot mode is only a UI for some bootloader commands. The known screen with the green Robot is only a .png file stored in your logo.bin. Did you modify your logo.bin (boot logo)?
Click to expand...
Click to collapse
Actually the cellphone wasnt mine until yesterday.. I dont know if they changed anything previously.. but there is no menu at all, just black screen