So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
swiftd3v said:
So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
Click to expand...
Click to collapse
anything yet?
swiftd3v said:
So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
Click to expand...
Click to collapse
What do you mean by "the device isn't found"?
wenyendev said:
What do you mean by "the device isn't found"?
Click to expand...
Click to collapse
The error I’m getting is “fastboot: usage: unknown device target recovery”
I am experiencing the EXACT same thing. No matter what box program Im using , nothing works! crazy. Please help. Id be happy with a factory reset. Atleast then I could get past the FRP.
Wow, I have not encountered that error yet.
I could only guess that it might be a problem of recovery.
How did you install your current recovery if not from fastboot?
diamant3 said:
The error I’m getting is “fastboot: usage: unknown device target recovery”
Click to expand...
Click to collapse
you're using fastboot reboot recovery?
Hey any update on this? I can say I've come across the same issue where their seems to either be no recovery or a corrupt one.
One thing I want to point out is (at least with the TracFone) that when I put the device in fastboot, and have wondershare tune go running, it displays the device as a Sony Xperia. The program still isn't able to connect to the device for me to attempt a reboot into recovery. It also reads the device as two other devices.
I'm hoping someone has encountered these findings and may also have a dump of the stock rom.if so I may be able to begin rooting for at least fix the recovery issue.
TaigaDaReck said:
Hey any update on this? I can say I've come across the same issue where their seems to either be no recovery or a corrupt one.
One thing I want to point out is (at least with the TracFone) that when I put the device in fastboot, and have wondershare tune go running, it displays the device as a Sony Xperia. The program still isn't able to connect to the device for me to attempt a reboot into recovery. It also reads the device as two other devices.
I'm hoping someone has encountered these findings and may also have a dump of the stock rom.if so I may be able to begin rooting for at least fix the recovery issue.
Click to expand...
Click to collapse
Also I'm going to use my Linux system to see if I get any results. Let me know if you've tried it as well.
fastboot oem unlock/fastboot flashing unlock has been blocked in the boot loader, only hope for root is another brom exploit like mtkclient or a temp root privilege escalation exploit
luridphantom said:
fastboot oem unlock/fastboot flashing unlock has been blocked in the boot loader, only hope for root is another brom exploit like mtkclient or a temp root privilege escalation exploit
Click to expand...
Click to collapse
Were you able to get fastboot to recognize the device?
Which OS are you testing on if you are?
TaigaDaReck said:
Were you able to get fastboot to recognize the device?
Which OS are you testing on if you are?
Click to expand...
Click to collapse
you need to use a special mtk boot mode script you can download here #101
Code:
computer:~ user$ python3 ~/Downloads/mtk-bootseq.py FASTBOOT /dev/tty.usbmodem14100
b'READYTOO'
Boot sequence sent
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
testing on android 12, jan5 2022 update build 02US_1_030
luridphantom said:
you need to use a special mtk boot mode script you can download here #101
Code:
computer:~ user$ python3 ~/Downloads/mtk-bootseq.py FASTBOOT /dev/tty.usbmodem14100
b'READYTOO'
Boot sequence sent
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
testing on android 12, jan5 2022 update build 02US_1_030
Click to expand...
Click to collapse
Hey thanks for the response.
So far I've been able to get the device to read in fastboot but I'm still unable to unlock the bootloader since as your saying it's definitely..."gimped" haha. I'll checkout the script and do some tests to see what I get.
TaigaDaReck said:
Hey thanks for the response.
So far I've been able to get the device to read in fastboot but I'm still unable to unlock the bootloader since as your saying it's definitely..."gimped" haha. I'll checkout the script and do some tests to see what I get.
Click to expand...
Click to collapse
if you're curious you can always reach out to this guy, he's able to get prototype boot loaders and stuff: https://twitter.com/Hikari_Calyx
might even know how to get test points to force it into brom for mtkclient
Related
Hi,
I've now spent quite a few frustrating hours trying to root my Alcatel 1c (model 5003D, running Android 8.1 Go) and nothing seems to work. A short overview of some of the rabbit holes I've gone down:
Root tools
Started with the obvious: root tools. In short, none that I ran work. There's a couple I haven't tried because the instructions were mostly in Russian and some googling turned up quite a few mentions of them containing malware, but other than that I've pretty much tried all the major ones.
Flashing images via fastboot
Naturally, the next place I turned was the awesome resource that is this forum. This thread gave me plenty of hope, but I was soon flummoxed by my device's fastboot mode for which a bunch of the normal features are either broken or are simply not implemented. Some examples of things that should work (and indeed work on other Alcatel phones, notably, it seems, ones that are not based on Spreadtrum) but didn't:
Code:
~/D/platform-tools > ./fastboot oem unlock
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
Code:
~/D/platform-tools > ./fastboot oem unlock-go
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
Code:
~/D/platform-tools > ./fastboot oem unlock-go --wipe
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
Code:
~/D/platform-tools > ./fastboot flashing unlock
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed
(note the spelling error in the error message...)
Code:
~/D/platform-tools > ./fastboot flash recovery ../recovery.img
Sending 'recovery' (28266 KB) OKAY [ 1.582s]
Writing 'recovery' FAILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')
fastboot: error: Command failed
That last one was particularly intriguing, as it suggests there is a Flashing Lock Flag that can be unlocked. I tried all of the fastboot commands that seemed relevant but couldn't find any way of setting that flag or even figuring out if it actually exists. I even rand the boot.img through strings to see if I could find something interesting, but didn't turn up anything.
Just to be clear, before doing all this I set the phone to Developer Mode and checked the "OEM unlocking" feature.
Flashing tools
I tried various tools with which it's possible to flash phones. A lot of them use fastboot under the covers which doesn't work (see above). Some of them don't but didn't work on my phone all the same, for various reasons:
SPD flash tool - After yet more Googling I stumbled upon the SPD flash tool,built specifically to flash Spreadtrum-based devices. I downloaded the latest version, installed all of the necessary USB drivers and tried to flash the phone with the stock ROM. No dice. The tool fails to connect to the device via the USB2Serial thing that it uses to communicate. No idea what's going on or why it won't work, and haven't yet mustered the courage to dive into the source code. Of course, if I do get it to work, then I have to figure out how to actually root the device using this tool. I'm guessing it will involve unpacking the ROM (a PAC file), modifying the recovery.img to a TWRP (or similar), repacking it and flashing the result. I've only managed the unpacking so far, no clue as to the other 2 steps. BTW, the SPD flash tool site als has a "factory" and a "research" tool, besides the "upgrade" tool that I tried. Unless I'm missing something, all three seem to be exactly the same (save for the color scheme).
Alcatel Mobile Upgrade S - Installs just fine and then allows you to choose your phone out of a dropdown... that doesn't include my model.
Sugar MTK/QCT - Installed it and the necessary drivers but it can't find my phone, no matter what I try. Also, I keep reading that it needs login credentials (wut?)
Conclusion: argh!
So, nothing so far. Since it's a Spreadtrum phone it has an engineering mode that can be explored with an APK I found in this thread. Nothing in the settings it reveals appears to be of any help though. I also contacted the makers of the AIO Alcatel toolkit to see if they had any ideas, but after I explained the situation one of them concluded "Hmmm. New one on me". Needless to say I also tried searching this forum for more tips, but googling 'site:forum.xda-developers.com "5003D"' returns no hits.
For now, I'm forced to conclude that there is a lot of really awesome tooling out there created by some very talented people, but none of it works on my phone. As of yet the 5003D appears pretty unrootable. If anyone has any tips to help me along or point me in the right direction, I would be very appreciative.
bump
bump
Then type the command to show the device
fastboot -i 0x1bbb devices
Execute the next command which will show device info including bootloader status (e.g. locked).
fastboot -i 0x1bbb oem device-info
This command is to unlock the bootloader on Alcatel device
fastboot -i 0x1bbb oem unlock
Repeat Step and you should see “Device unlocked: true”
To reboot normally type:
fastboot -i 0x1bbb reboot
Done
This command is to unlock the bootloader on Alcatel device
fastboot -i 0x1bbb oem unlock
Click to expand...
Click to collapse
I've tried that a bunch of times in an bunch of different ways, and unfortunately that doesn't work for this particular phone.
lotus118 said:
I've tried that a bunch of times in an bunch of different ways, and unfortunately that doesn't work for this particular phone.
Click to expand...
Click to collapse
Rooting your phone's Android does NOT require you fiddle around with its boot-loader. Forget trying to make use of Fastboot.
So how would I go about this without using fastboot?
lotus118 said:
So how would I go about this without using fastboot?
Click to expand...
Click to collapse
1. Open Windows command prompt and input the following comand
Code:
adb devices
2. Start the ADB sideload in your phone's recovery
3. Then input the following command in the Windows command prompt
Code:
adb sideload <filename.Zip>
where <filename.zip> must of course be the real full filepathname of ZIP to get flashed
EDIT: I was able to unlock my bootloader by just trying to use the fastboot "unlock bootloader" command several times. Thanks a lot SubwayChamp for helping me through this, I was also able to root my phone. Wasn't able to install a custom recovery, though.
I have a Multilaser H phone. It is a phone from a national brand, "Multilaser" here in Brazil.
For some reason, Multilaser does not want to provide the bootloader "unlock.img" file.
For context, the Multilaser H is just a white label of the Lenovo Z6 Lite/Lenovo K10 Note.
I downloaded the Z6 Lite unlock bootloader file and it has an "unlock_bootloader.img". I tried running the Z6 Bootloader Unlocker on the Multilaser H but it just didn't work. I really want to flash a custom ROM on my phone and I've tried all sorts of things, even trying to sideload another ROM but with the locked bootloader it's impossible. And no, I can't just buy a new phone, unfortunately. This one is more than capable of running Android 10 or even 11 but Multilaser just does not release it so I'm stuck on 9.
Is there any way to make that "unlock_bootloader.img" file that the Z6 Lite tool uses to unlock the phone for MY phone? Like, generate it? Because apparently the company doesn't want to provide it for us. The stock ROM I have here does have the "recovery.img" file.
Can I unlock my bootloader or somehow make a file similar to unlock_bootloader.img that allows me to do that? I have no idea how it works exactly but I'm assuming the "unlock.bootloader.img" is specific for the Z6 Lite and allows it to unlock the bootloader.
Here's how the Z6 Lite Tools folder looks like by the way
{
"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"
}
AlNexus said:
I have a Multilaser H phone. It is a phone from a national brand, "Multilaser" here in Brazil.
For some reason, Multilaser does not want to provide the bootloader "unlock.img" file.
For context, the Multilaser H is just a white label of the Lenovo Z6 Lite/Lenovo K10 Note.
I downloaded the Z6 Lite unlock bootloader file and it has an "unlock_bootloader.img". I tried running the Z6 Bootloader Unlocker on the Multilaser H but it just didn't work. I really want to flash a custom ROM on my phone and I've tried all sorts of things, even trying to sideload another ROM but with the locked bootloader it's impossible. And no, I can't just buy a new phone, unfortunately. This one is more than capable of running Android 10 or even 11 but Multilaser just does not release it so I'm stuck on 9.
Is there any way to make that "unlock_bootloader.img" file that the Z6 Lite tool uses to unlock the phone for MY phone? Like, generate it? Because apparently the company doesn't want to provide it for us. The stock ROM I have here does have the "recovery.img" file.
Can I unlock my bootloader or somehow make a file similar to unlock_bootloader.img that allows me to do that? I have no idea how it works exactly but I'm assuming the "unlock.bootloader.img" is specific for the Z6 Lite and allows it to unlock the bootloader.
Here's how the Z6 Lite Tools folder looks like by the way
View attachment 5457515
Click to expand...
Click to collapse
Do you mean you tried something like this? https://www.gizdev.com/twrp-root-lenovo-z6-youth/ running the bootloader_unlock.bat? What does unlock_bootloader.img do?
Try with these commands apart to know the bootloader status
fastboot oem device-infoor fastboot getvar unlocked
Maybe you can try with simple commands to unlock it, in case you are wrong and the OEM doesn't care bootloader being unlocked:
fastboot oem unlock or fastboot oem unlock-go or
fastboot flashing unlock You should enable USB debugging and OEM unlock toggle must be available under this section, otherwise neither of those will work.
And if this device totattly rebranded from the Z6 Lite, or it has a MediaTek processor?
SubwayChamp said:
Do you mean you tried something like this? https://www.gizdev.com/twrp-root-lenovo-z6-youth/ running the bootloader_unlock.bat? What does unlock_bootloader.img do?
Try with these commands apart to know the bootloader status
fastboot oem device-infoor fastboot getvar unlocked
Maybe you can try with simple commands to unlock it, in case you are wrong and the OEM doesn't care bootloader being unlocked:
fastboot oem unlock or fastboot oem unlock-go or
fastboot flashing unlock You should enable USB debugging and OEM unlock toggle must be available under this section, otherwise neither of those will work.
And if this device totattly rebranded from the Z6 Lite, or it has a MediaTek processor?
Click to expand...
Click to collapse
When I try those commands it just says "Waiting for device..." and there's nothing on my phone. The FastBoot screen is identical to the Z6 Lite one. And the device is totally rebranded apparently, maybe something there and here, but it has the same CPU, RAM and storage.
AlNexus said:
When I try those commands it just says "Waiting for device..." and there's nothing on my phone. The FastBoot screen is identical to the Z6 Lite one. And the device is totally rebranded apparently, maybe something there and here, but it has the same CPU, RAM and storage.
Click to expand...
Click to collapse
OK, we're just trying to figure it out if your device can be really unlocked or not, so you need to walk through these steps to be sure.
"Waiting for device..." means that your device is not being detected, you need to install properly the fastboot drivers for Lenovo otherwise you can´t do what you need, the first step is this. With your device on, enable USB debugging in developer options, and unlock OEM toggle, when you enabled USB debugging you will see a pop-up message asking for "allow always", then tap on it.
As per to know if the model is identical you should download an app from Google Play, something like Device Info and see the specs, if this device has MediaTek instead of Qualcomm there could be a workaround.
SubwayChamp said:
OK, we're just trying to figure it out if your device can be really unlocked or not, so you need to walk through these steps to be sure.
"Waiting for device..." means that your device is not being detected, you need to install properly the fastboot drivers for Lenovo otherwise you can´t do what you need, the first step is this. With your device on, enable USB debugging in developer options, and unlock OEM toggle, when you enabled USB debugging you will see a pop-up message asking for "allow always", then tap on it.
As per to know if the model is identical you should download an app from Google Play, something like Device Info and see the specs, if this device has MediaTek instead of Qualcomm there could be a workaround.
Click to expand...
Click to collapse
I installed the drivers. Here is the output of the 3 commands:
Code:
PS C:\Users\alnexus> fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
PS C:\Users\alnexus> fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.002s
PS C:\Users\alnexus> fastboot flashing unlock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
It says "unlocked: no". Also it is Qualcomm, SDM710.
EDIT: Yeah it's probably impossible to unlock. Damn it, why do companies do this? Lock us in this crappy system and we can't even install another OS? I bought the phone, let me do whatever I want with it.
AlNexus said:
I installed the drivers. Here is the output of the 3 commands:
PS C:\Users\alnexus> fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
PS C:\Users\alnexus> fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.002s
PS C:\Users\alnexus> fastboot flashing unlock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
It says "unlocked: no". Also it is Qualcomm, SDM710.
EDIT: Yeah it's probably impossible to unlock. Damn it, why do companies do this? Lock us in this crappy system and we can't even install another OS? I bought the phone, let me do whatever I want with it.
Click to expand...
Click to collapse
And is there an OEM unlock toggle? If not or even being one, if OEM doesn't want to be unlocked there’s not much to do.
And what happen running the unlock.bat from the Z6 lite now that you installed properly the fastboot drivers?
Also check what is in the unlock.bat script, open it with Notepad++ and see which command is executed.
SubwayChamp said:
And is there an OEM unlock toggle? If not or even being one, if OEM doesn't want to be unlocked there’s not much to do.
And what happen running the unlock.bat from the Z6 lite now that you installed properly the fastboot drivers?
Also check what is in the unlock.bat script, open it with Notepad++ and see which command is executed.
Click to expand...
Click to collapse
Yes, there is an OEM unlock toggle. I enabled it.
Great idea, I'll try that, but my hopes are absolutely 0.
Here's the UNLOCK BOOTLOADER.bat (unlock.bat) script content:
Code:
@echo off
TITLE Bootloader Unlocker
color 3f
CLS
ECHO. ============================================================================
echo.
echo. Press any key
echo.
echo. ============================================================================
pause >nul
CLS
adb devices
echo.
echo Reboot mode bootloader
echo.
adb reboot bootloader
CLS
echo.
echo Firmware bootloader...
echo.
echo.
fastboot flash unlock unlock_bootloader.img
pause
CLS
echo.
echo Unlocking bootloader...
echo.
echo.
fastboot oem unlock-go
pause
CLS
echo.
echo Unlock complete, wait for reboot
echo.
fastboot %* reboot
pause
Yeah, didn't work ):
AlNexus said:
Yeah, didn't work ):
View attachment 5458091
Click to expand...
Click to collapse
WHAT
I TRIED USING THE UNLOCK BOOTLOADER COMMANDQ MULTIPLE TIMES AND IH AVE UNLOCKED THE BOOTLOADER
I hope it doesn't brick my phone now lol. Sorry, I couldn't contain my excitement...
AlNexus said:
WHAT
I TRIED USING THE UNLOCK BOOTLOADER COMMANDQ MULTIPLE TIMES AND IH AVE UNLOCKED THE BOOTLOADER
I hope it doesn't brick my phone now lol. Sorry, I couldn't contain my excitement...View attachment 5458109
Click to expand...
Click to collapse
When I try using that it just hangs on "downloading 'boot.img"...
Should I wait?
When I tried fastboot flash recovery twrp.img it said sending 'recovery' and said FAILED (remote: Requested download size is more than max allowed)
AlNexus said:
View attachment 5458111
When I try using that it just hangs on "downloading 'boot.img"...
Should I wait?
When I tried fastboot flash recovery twrp.img it said sending 'recovery' and said FAILED (remote: Requested download size is more than max allowed)
Click to expand...
Click to collapse
it seems that sometimes when I try using "fastboot flash recovery twrp.img" it just "restarts" the phone. The phone goes to a splash screen and it says in the top corner "press any key to shutdown" and disconnects from the computer. "fastboot boot" just hangs on downloading 'boot.img'.
Oops, that just happened with fastboot boot too.
and it showed the splash screen with "press any key to shutdown" in the corner
AlNexus said:
it seems that sometimes when I try using "fastboot flash recovery twrp.img" it just "restarts" the phone. The phone goes to a splash screen and it says in the top corner "press any key to shutdown" and disconnects from the computer. "fastboot boot" just hangs on downloading 'boot.img'.
Oops, that just happened with fastboot boot too.
View attachment 5458129 and it showed the splash screen with "press any key to shutdown" in the corner
Click to expand...
Click to collapse
You also could try fastboot flashing unlock_critical
First, be sure to get the firmware at hands, in case something goes wrong.
Regards the TWRP version, are you sure it is for your device?
Maybe you need to port from the Z6 Lite, making minimal changes.
In a different approach, you could patch your boot image with Magisk and flash it to the boot partition.
"Too many links..." error is probably that you have attached to your PC more than one Android device/emulator/USB hub or something, check that, end the process with adb kill-server and restart again with adb start-server or go straight to the command, ADB will start automatically.
SubwayChamp said:
You also could try fastboot flashing unlock_critical
First, be sure to get the firmware at hands, in case something goes wrong.
Regards the TWRP version, are you sure it is for your device?
Maybe you need to port from the Z6 Lite, making minimal changes.
In a different approach, you could patch your boot image with Magisk and flash it to the boot partition.
"Too many links..." error is probably that you have attached to your PC more than one Android device/emulator/USB hub or something, check that, end the process with adb kill-server and restart again with adb start-server or go straight to the command, ADB will start automatically.
Click to expand...
Click to collapse
I'll try that. I don't know how to port but I don't think it should be too hard. Thanks for the tips, I'll also try to patch my boot image.
AlNexus said:
I'll try that. I don't know how to port but I don't think it should be too hard. Thanks for the tips, I'll also try to patch my boot image.
Click to expand...
Click to collapse
Patching the boot image doesn't work either. Stuck on "sending 'recovery' forever. I had also gotten
Code:
fastboot flash recovery magisk_patched.img
Sending 'recovery' (65536 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
before. I'll try with another USB cable. Wonder if it could be the drivers; I have already installed the device drivers from Google and Lenovo.
I had a different output on Linux, but Magisk App doesn't say "Installed".
EDIT: I tried to flash "twrp.img" (I know it's dangerous without a backup) and it said the same thing, except the phone doesn't seem to have TWRP installed.
It says finished but nothing actually happens or changes in the phone.
EDIT 2: When I try fastboot boot recovery.img it says FAILED (remote: 'unknown command')
AlNexus said:
View attachment 5458349
Patching the boot image doesn't work either. Stuck on "sending 'recovery' forever. I had also gotten
Code:
fastboot flash recovery magisk_patched.img
Sending 'recovery' (65536 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
before. I'll try with another USB cable. Wonder if it could be the drivers; I have already installed the device drivers from Google and Lenovo.
Click to expand...
Click to collapse
I guess you patched it the boot image from your stock ROM, then it is to flash it to the boot partition, not to the recovery partition, the usage would be fastboot flash boot patchedboot.img this is to achieve root, if rooted you could do more things.
I'm assuming that you opened the fastboot commands from within the directory where there are the images files.
SubwayChamp said:
I guess you patched it the boot image from your stock ROM, then it is to flash it to the boot partition, not to the recovery partition, the usage would be fastboot flash boot patchedboot.img this is to achieve root, if rooted you could do more things.
I'm assuming that you opened the fastboot commands from within the directory where there are the images files.
Click to expand...
Click to collapse
Yes, I did.
You saved my day. Thanks a lot, I got it rooted by using fastboot flash boot magisk_patched.img. Having root is infinitely better than having nothing.
I should mark the whole topic as "solved" now. Thanks so much
AlNexus said:
Yes, I did.
You saved my day. Thanks a lot, I got it rooted by using fastboot flash boot magisk_patched.img. Having root is infinitely better than having nothing.
I should mark the whole topic as "solved" now. Thanks so much
Click to expand...
Click to collapse
Good to hear that.
Now you can follow with searching these topics:
- How to back up android partitions. (to get the complete images -firmware- so you can restore it if something goes wrong). This is just an example: https://github.com/for2ando/dump-android-partitions
- How to port TWRP recovery for my device, from the Z6 Lite can be used as base. Something like this: https://forum.hovatek.com/thread-26277.html
And lastly, to change for a different featured ROM:
- How to flash a GSI.
hi I have an alcatel 1b 5002d I would like to root it but I always have this error and it does not unlock the bootloader
C: \ sdk> fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
with any fastbooot command it is the same error, only with fastboot devices it gives me the serial, I have already installed all the drivers, I would not know how to do anything else if someone has some solution app like kingroot do nothing I have no security screen locks, drivers installed, developer options unlocked oem and usb debugging
roberto167 said:
hi I have an alcatel 1b 5002d I would like to root it but I always have this error and it does not unlock the bootloader
C: \ sdk> fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
with any fastbooot command it is the same error, only with fastboot devices it gives me the serial, I have already installed all the drivers, I would not know how to do anything else if someone has some solution app like kingroot do nothing I have no security screen locks, drivers installed, developer options unlocked oem and usb debugging
Click to expand...
Click to collapse
Hello and good morning, @roberto167
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
roberto167 said:
hi I have an alcatel 1b 5002d I would like to root it but I always have this error and it does not unlock the bootloader
C: \ sdk> fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
with any fastbooot command it is the same error, only with fastboot devices it gives me the serial, I have already installed all the drivers, I would not know how to do anything else if someone has some solution app like kingroot do nothing I have no security screen locks, drivers installed, developer options unlocked oem and usb debugging
Click to expand...
Click to collapse
Is that your phone? https://forum.xda-developers.com/c/alcatel-1.8103/
joke19 said:
È il tuo telefono? https://forum.xda-developers.com/c/alcatel-1.8103/
Click to expand...
Click to collapse
mine is model 1b with 2gb ram and android 11
assuming you have enabled OEM unlocking in developer options, try
fastboot flashing unlock
aIecxs said:
assuming you have enabled OEM unlocking in developer options, try
fastboot flashing unlock
Click to expand...
Click to collapse
as said already done and gives me the said error, enter fastboot mode
fastboot oem unlock
FAILED (remote: 'unknown command')
did you actually notice the difference between what I wrote and what you did?
aIecxs said:
did you actually notice the difference between what I wrote and what you did?
Click to expand...
Click to collapse
also given that command and also
fastboot flashing unlock
so what was the error message then
seems unlocking is disabled in aboot therefore no common unlock method will work. at least there is a working firehose programmer for that device, so you can dump boot.img off the eMMC and try to modify with AIK and Magisk (AVBv2 signing required)
source
aIecxs said:
seems unlocking is disabled in aboot therefore no common unlock method will work. at least there is a working firehose programmer for that device, so you can dump boot.img off the eMMC and try to modify with AIK and Magisk (AVBv2 signing required)
source
Click to expand...
Click to collapse
it seems very complicated as a procedure, being never done
usual error message looks like this
jorgen.bumajnikov said:
I'm trying to unlock phone’s bootloader using
Code:
fastboot flashing unlock
, but getting error message:
Code:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.021s
Checked fastboot devices command and it found my device connected.
Click to expand...
Click to collapse
but your error sounds hopeless
FAILED (remote: 'unknown command')
So if you're looking for easy solution you're reading the wrong section.
Nevertheless you could give a last try
Code:
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb flashing unlock
aIecxs said:
usual error message looks like this
but your error sounds hopeless
FAILED (remote: 'unknown command')
So if you're looking for easy solution you're reading the wrong section.
Nevertheless you could give a last try
Code:
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb flashing unlock
Click to expand...
Click to collapse
even if it appears with the command fastboot devices, with these commands it remains waiting for any devices
Alcatel 1B Stock ROM / SIM unlock / etc....
ALCATEL 1B MEGATHREAD ( veken/seoul/TCL L7)...
forum.xda-developers.com
"UNLOCKING BOOTLOADER / ROOTING
For now, it is not possible... However mentions of secret key is spread all around the phone partitions (mainly abl file)
So if you have any experience editing bootloaders you can unlock...."
I bought the Asus ZenFone 8 Flip with the bootloader unlocked, it is not running a custom ROM. How do I lock the bootloader? Thank you
Try this with fastboot:
fastboot oem lock
However, this won't restore your warranty and you won't receive updates, since surely who has unlocked your device has used the official bootloader unlock tool which registers your serial number
maicol07 said:
Try this with fastboot:
fastboot oem lock
However, this won't restore your warranty and you won't receive updates, since surely who has unlocked your device has used the official bootloader unlock tool which registers your serial number
Click to expand...
Click to collapse
how do I go about something like that? I would only like to be on official software so how will I not be able to receive updates?
Kiribro02 said:
how do I go about something like that? I would only like to be on official software so how will I not be able to receive updates?
Click to expand...
Click to collapse
You won't get OTA updates, but you can still update manually downloading the zip from Asus website.
Unfortunately that's the price if you unlock the device (not only for Asus, a lot of other manufacturers (i.e. Sony) do this too)
maicol07 said:
You won't get OTA updates, but you can still update manually downloading the zip from Asus website.
Unfortunately that's the price if you unlock the device (not only for Asus, a lot of other manufacturers (i.e. Sony) do this too)
Click to expand...
Click to collapse
interesting... So I don't know how to lock the bootloader precisely. So I download the latest firmware from the Asus website, plug the phone into the computer run fastboot then what? Am I missing something?
Kiribro02 said:
interesting... So I don't know how to lock the bootloader precisely. So I download the latest firmware from the Asus website, plug the phone into the computer run fastboot then what? Am I missing something?
Click to expand...
Click to collapse
No, just follow these steps:
Make a backup of your phone!! Unlocking/Locking the bootloader erases all your data partition (so all your stuff will be gone!)
Install ADB on your PC if you don't have it (check how to install it: https://www.xda-developers.com/install-adb-windows-macos-linux/).
Plug in your device via USB with Debug USB setting enabled (in Developer Settings)
Open a terminal prompt on your PC
In the terminal run adb devices. If you see your device I the list then you're fine. Otherwise, you have mistaken something in the previous steps.
Run adb reboot fastboot (or adb reboot bootloader if it doesn't work) to reboot into fastboot mode
Run fastboot oem lock to lock the bootloader
Run fastboot reboot to reboot the system
Your device is now locked!
DISCLAIMER:
I'm not responsible of any data loss, damages and/or bricks you make to your device(s) by following this guide!
Click to expand...
Click to collapse
To update the system when a new version is out, since you won't receive OTAs:
Go to Zenfone 8 Flip support page: https://www.asus.com/Mobile/Phones/ZenFone/Zenfone-8-Flip/HelpDesk_Download/
Choose Android as OS and scroll down to "Firmware"
Download the latest zip
Put it in the internal storage (in the root directory, not inside another folder!)
Two paths:
If you put the zip from PC via USB simply unplug the USB cable
If you downloaded the zip and put it manually via file manager from the phone reboot the system
A notification should pop out, notifying you there is a firmware package to install!
Just follow the notification message and you'll be done!
Hey so I installed adb and ran the phone under fastboot but when I run fastboot oem lock all it says in the windows powershell is < waiting for any device >
Kiribro02 said:
Hey so I installed adb and ran the phone under fastboot but when I run fastboot oem lock all it says in the windows powershell is < waiting for any device >
Click to expand...
Click to collapse
Oh that's an issue I have all the times with Asus devices. There's a simple one-time fix though: just install the official Asus ADB drivers.
Download them from this page (I know it's the smaller Zenfone 8 page, but they work with every Asus device): https://www.asus.com/it/Mobile/Phones/ZenFone/Zenfone-8/HelpDesk_Download/
Choose your windows version (for 10 and 11 choose 8.1)
Download the USB driver
Extract the archive somewhere in your PC
Open Device manager in your PC (search it in start menu) while the phone is connected via USB and in fastboot mode
You'll notice an unknown device with a yellow/orange warning icon at the top of the devices list. Right click on it and choose Update drivers.
Choose "Search driver in the PC" (the second option (don't choose the first one since it searches the driver automatically on Windows update))
Choose the folder you extracted
Click "Next"
Drivers should be installed and fastboot should recognize your device (to test run the command: fastboot devices)
Sorry for the late reply, but I didn't get any notification from XDA
there were two options for drivers android adb and android composite adb drivers I selected the composite one but it doesn't seem like it was installed
Kiribro02 said:
When I try to update the drivers it says that windows was unable to install your and then it says the device.
Click to expand...
Click to collapse
Do you installed the drivers when the phone is in fastboot mode?
Also, I've noticed some steps are not clear (and one is doubled), I'll clean it
Kiribro02 said:
there were two options for drivers android adb and android composite adb drivers I selected the composite one but it doesn't seem like it was installed
Click to expand...
Click to collapse
Try all the two, I don't remember which one works (I think the Composite worked for me), but try also with the other ones
Hi,
I've bought a second hand zenfone 8 flip. After Hard Reset I have to enter the old PIN to continue. The problem is the seller doesn't have the PIN and is not willing to take the phone back. ASUS is not willing to help because I bought it second hand.
I already flashed with raw firmware, but this is still coming up.
Any ideas? Should I start a new thread?
b4rbaar said:
Hi,
I've bought a second hand zenfone 8 flip. After Hard Reset I have to enter the old PIN to continue. The problem is the seller doesn't have the PIN and is not willing to take the phone back. ASUS is not willing to help because I bought it second hand.
I already flashed with raw firmware, but this is still coming up.
Any ideas? Should I start a new thread?
Click to expand...
Click to collapse
Hi, yes you should create a new thread since it's a different topic
It's not working for me, please help:
C:\platform-tools>fastboot devices
M4AIB760******* fastboot
C:\platform-tools>fastboot oem lock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
So, as you can see, the driver is installed correctly as I get an answer from fastboot devices, but then the OEM lock doesn't work.
Are there any other ways to re-lock it?
Thank you!
wyktron said:
It's not working for me, please help:
C:\platform-tools>fastboot devices
M4AIB760******* fastboot
C:\platform-tools>fastboot oem lock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
So, as you can see, the driver is installed correctly as I get an answer from fastboot devices, but then the OEM lock doesn't work.
Are there any other ways to re-lock it?
Thank you!
Click to expand...
Click to collapse
@wyktron can you try this? This worked with my Zenfone 6 some years ago, it might be the same for ZF8 Flip, due to Asus customization:
Bash:
fastboot oem asus-back
maicol07 said:
@wyktron can you try this? This worked with my Zenfone 6 some years ago, it might be the same for ZF8 Flip, due to Asus customization:
Bash:
fastboot oem asus-back
Click to expand...
Click to collapse
@maicol07 thanks for the quick reply, here's what I got:
C:\platform-tools>fastboot oem asus-back
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
same error message
wyktron said:
@maicol07 thanks for the quick reply, here's what I got:
C:\platform-tools>fastboot oem asus-back
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
same error message
Click to expand...
Click to collapse
Try this one:
Code:
fastboot oem asus-csc_lk
maicol07 said:
Try this one:
Code:
fastboot oem asus-csc_lk
Click to expand...
Click to collapse
@maicol07 seems like any oem command shows this error, here's what I got:
C:\platform-tools>fastboot oem asus-csc_lk
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem get-sn
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem get-imei1
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem
fastboot: usage: empty oem command
C:\platform-tools>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
at this point, crying is my only option
what else can I try? I can't use key features like google pay because of that
thanks again for your support!
wyktron said:
@maicol07 seems like any oem command shows this error, here's what I got:
C:\platform-tools>fastboot oem asus-csc_lk
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem get-sn
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem get-imei1
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem
fastboot: usage: empty oem command
C:\platform-tools>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
at this point, crying is my only option
what else can I try? I can't use key features like google pay because of that
thanks again for your support!
Click to expand...
Click to collapse
As mentioned here check if you have enabled Debug USB and OEM unlock in developer options and try to reboot into bootloader (with either fastboot reboot bootloader or adb reboot bootloader)
maicol07 said:
As mentioned here check if you have enabled Debug USB and OEM unlock in developer options and try to reboot into bootloader (with either fastboot reboot bootloader or adb reboot bootloader)
Click to expand...
Click to collapse
@maicol07 there's no OEM unlock in my developer options, only the USB debugging (which is already on)
besides this oem method, is there another way to lock it? perhaps through the zenfone flash tool (I have it installed and it detects my phone, but never used it)
Greetings. I'm using a Xiaomi Mi A3 (laurel-sprout). It's been not so easy to unlock the bootloader, but once done, I just can't bootthe recovery using the command fastboot boot twrp.img Booting FAILED (remote: 'unknown command') fastboot: error: Command failed I have double checked that I'm not in fastbootD and that my bootloader is unlocked. What could be the case?
manolius148 said:
Greetings. I'm using a Xiaomi Mi A3 (laurel-sprout). It's been not so easy to unlock the bootloader, but once done, I just can't bootthe recovery using the command fastboot boot twrp.img Booting FAILED (remote: 'unknown command') fastboot: error: Command failed I have double checked that I'm not in fastbootD and that my bootloader is unlocked. What could be the case?
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...omi-mi-a3-laurel_sprout.3987759/post-80625495
NOSS8 said:
https://forum.xda-developers.com/t/...omi-mi-a3-laurel_sprout.3987759/post-80625495
Click to expand...
Click to collapse
Thank you so much for your answer. By doing this, I get no error (in fact, I'm flashing it before) but anyway twrp does never boot. I have even tried the command ./fastboot reboot recovery to no avail.
So far, it's been impossible to set the TWRP up.
manolius148 said:
Thank you so much for your answer. By doing this, I get no error (in fact, I'm flashing it before) but anyway twrp does never boot. I have even tried the command ./fastboot reboot recovery to no avail.
So far, it's been impossible to set the TWRP up.
Click to expand...
Click to collapse
"fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)"
Did you do this?
NOSS8 said:
"fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)"
Did you do this?
Click to expand...
Click to collapse
Of course, that was my first attempt
manolius148 said:
Of course, that was my first attempt
Click to expand...
Click to collapse
I don't have this device so difficult to help you more, post your problem on the TWRP Thread.
Could be an active partition problem.