Database Info

Unlocking bootloader in LYF LS-4008 help

{
"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"
}
Respected everyone,
My phone model is LYF LS-4008 manufacturer - fortuneship .... All the drivers are correctly install i.e, Adb, fastboot....and m trying to unlock is the bootloader for twrp and rooting purposes but m failed.... When I type adb devices it shows serial number then I type adb reboot bootloader my phone reboots to fastboot then I type fastboot devices then it shows serial number but when I type fastboot oem unlock or fastboot oem unlock-go on minimal software it only goes on loading and nothing happens in cmd and also in my phone it doesn't for unlock bootloader yes or no as you can see on the above image .....what to do sir please help me....
Thank you..

psusanta056 said:
Respected everyone,
My phone model is LYF LS-4008 manufacturer - fortuneship .... All the drivers are correctly install i.e, Adb, fastboot....and m trying to unlock is the bootloader for twrp and rooting purposes but m failed.... When I type adb devices it shows serial number then I type adb reboot bootloader my phone reboots to fastboot then I type fastboot devices then it shows serial number but when I type fastboot oem unlock or fastboot oem unlock-go on minimal software it only goes on loading and nothing happens in cmd and also in my phone it doesn't for unlock bootloader yes or no as you can see on the above image .....what to do sir please help me....
Thank you..
Click to expand...
Click to collapse
Vivo y51

No my model is LYF LS-4008

Fix ADB Unauthorized No RSA Problem 100% Working

i have been searching but no method worked until i found this and tried on many pc's and devices, it worked like a charm, i have made a video and explained in the easy way so everyone can do it.Here is the video tutorial and below is the written guide..https://youtu.be/Uv42aVXCV-c
{
"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 COMMAND WILL FIX THE UNAUTHORIZED ISSUE WHEN YOU DONT GET RSA POP UP, SO
PUT YOUR PHONE IN TWRP AND CONNECT TO PC BEFORE EXECUTING THIS COMMAND IN CMD OR TERMINAL OTHERWISE IT WILL NOT WORK,
IF YOU CANT UNDERSTAND THE GUIDE THEN YOU CAN TAKE HELP FROM VIDEO LINK ABOVE.
This method will fix your adb unauthorized problem.
Here is the command
FIRST COMMAND
for linux
cd ~/.android && adb push adbkey.pub /data/misc/adb/adb_keys
SECOND COMMAND
adb reboot
for Windows
cd c:/users/YOURUSERNAME/.android && adb push adbkey.pub /data/misc/adb/adb_keys
CHANGE THE USERNAME WITH YOURS!!! in windows command
FOR EXAMPLE cd c:/users/waleed/.android && adb push adbkey.pub /data/misc/adb/adb_keys
STEPS WINDOWS
1- REBOOT INTO RECOVERY TWRP
2- CONNECT PHONE TO PC
3- GOTO CMD AND APPLY THIS COMMAND
STEPS LINUX
1- REBOOT INTO RECOVERY TWRP
2- CONNECT PHONE TO PC
3- GOTO TERMINAL AND APPLY COMMAND

Worked! But I suggest you remove that immodest wallpaper of unveiled woman.

unlock bootloader on alcatel v1 5001D 2019

How unlock bootloader on alcatel v1 5001D 2019?When i use fastboot oem unlock command or fastboot flashing unlock on adb i get this error:
Rec_002
Watch "Rec_002" on Streamable.
streamable.com

Fastboot is not standardized, means Fastboot isn't equal Fastboot: how it's implemented depends on OEM/Carrier, it's not always the version as with a bootloader based off the latest AOSP code.
And most OEMs/Carriers nowadays have implemented their own version. Thus you can't expect that the Fastboot commands / options listet and described on hundreds of websites as also here on XDA are working.
Unlocking device's bootloader must be granted by OEM/carrier: have you checked this?
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
Only if returned value is 1 it's supported.
BTW: Fastboot and ADB are 2 totally different things, don't confuse them.

Thats what i get when i type code.
{
"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"
}

For me it looks that ADB isn't got enabled on phone by you: Android Settings -> Developer options -> Allow USB debugging -> ON

Actually Allow Usb Debbuging and OEM Unlock are both on.

If not done yet, install the Android USB Driver provided by OEM for this Android device, too

Already done that.

Questions about fastbootd

Hello everyone! I encountered an issue, that is new for me, and I want to know more information. I tried to flash a MTK device that now has Android 10 installed with Android 11 to test it out, out of curiosity. I installed the Treble App on my device and it shows me all the information about what image should I chose and how to flash it. But I saw a new detail that made me curious. It said to use fastbootd instead of fastboot, or during the flashing I would get the error that the partition does not exist. Now I get a doubt... I checked the Android page about the new installation of GSI images on Android 10 devices, but it doesn't explain that much. Should the fastbootd be activated by the manufacturer or do I hve to activated somehow? Because as it says on the Android page if I give the command in ADB " adb reboot bootloader" the device should open directly fastbootd without entering recovery, which my device doesn't do it... So what is the "mystery" about the new dynamic partitions and the fastbootd? Regards and thanks in advance!
{
"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"
}

Code:
adb reboot bootloader
became obsolete starting with Android 10
You have to run
Code:
adb reboot fastboot
fastboot reboot fastboot
More info here:
Moving Fastboot to Userspace | Android Open Source Project
source.android.com

jwoegerbauer said:
Code:
adb reboot bootloader
became obsolete starting with Android 10
You have to run
Code:
adb reboot fastboot
fastboot reboot fastboot
More info here:
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Thank you very much for your reply! I'm gonna test it to see if it works!

[Help] Fastboot mode.

I am unable to get into fastboot mode on my At&t Motivate 2. I do have OEM unlock, but when I use adb reboot fastboot, or hold the power key + up vol. It get's stuck on the screen saying => FASTBOOT mode... I am not sure what I am doing wrong (if I am). It's model number is EA211002. It stays on this screen no matter how long i leave it.
{
"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"
}

Be happy, you sucessfully entered Fastboot mode. Now direct Fastboot on PC per Windows CMD and/or PowerShell what action(s) to perform.
Fastboot Commands List and Cheat Sheet with Explanation
Fastboot is a command-line tool for Android. You can execute Fastboot commands to flash and boot factory and TWRP recovery images.
technastic.com

I have the same phone does anyone have the stock firmware ?

also where did you get the fastboot drivers for it? can you sent them to me ? please @jwoegerbauer @Synaronel

@IXDevoXI
Latest ADB and Fastboot drivers you can obtain here:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com

I finally figured out the whole fastboot thing with this phone lol and which one you need to be in and so forth it is the most confusing phone I’ve ever tried to root but now I’m left with that stupid dm-verity corrupt issue