I need a way to unlock the bootloader tab11 blacview_row - Android Q&A, Help & Troubleshooting

I need a way to unlock the bootloader tab11 blacview I have tried all the commands for fastboot oem unlock and fastboot flashing unlock and all of them failed I need help to unlock the bootloader and root
{
"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"
}

Use a computer with ADB
[TOOL][WINDOWS] ADB & Fastboot++ | February 2023
NFO: • Versions: Installer, Portable & ADBKit • Android Debug Bridge & Fastboot updated to latest v1.0.41 (Version 34.0.0-9570255, February 2023) Features: • Installation Folder chooseable (Installer) • Desktop & Start Menu Shortcuts (Installer)...
forum.xda-developers.com

joke19 said:
Use a computer with ADB
[TOOL][WINDOWS] ADB & Fastboot++ | February 2023
NFO: • Versions: Installer, Portable & ADBKit • Android Debug Bridge & Fastboot updated to latest v1.0.41 (Version 34.0.0-9570255, February 2023) Features: • Installation Folder chooseable (Installer) • Desktop & Start Menu Shortcuts (Installer)...
forum.xda-developers.com
Click to expand...
Click to collapse
The same problem did not work, it appears to me after writing the opening command, an unknown command

U enable OEM unlock over Developer options and usb debugging

joke19 said:
U enable OEM unlock over Developer options and usb debugging
Click to expand...
Click to collapse
Yes, of course, I activate the Allow unlock bootloader and flash usb errors

joke19 said:
U enable OEM unlock over Developer options and usb debugging
Click to expand...
Click to collapse
I found this method, but the last step, when I understand it well, is where to get the vbmeta file from to flash it on the version of my device, especially as it is according to what its owner said that he tested it on the linux system and he has no idea if it works on Windows. If you know the vb.meta file, please let me know. What is his job and where did he get it?

Related

[SHARE][APP][WIN-TOOL] ADB Screenshot from both Android OS and Recovery!

Note: I'm just sharing the work of the XDA Member majdinj
Here's a brief introduction :
majdinj said:
ADB Screen Shot (OS & Recovery)​
{
"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"
}
What does this tool do?
Simply, it takes screen shot through adb shell action and pull the resulted image file directly to your computer, then it removes all traces from android device.
From which android screen this tool is capable to take picture from?
From both android OS and Recovery mode.
What are the basic binaries used in this tool?
- The built in screencap binary for taking screen shots from Android OS.
- fb2png binary for taking screen shots from Android Recovery mode. This binary is developed by Kyan.ql (You can visit the project page from here).
How can I use this tool?
It is simple:
1) Make sure you have turned on your device USB debugging mode.
2) Connect your device to your computer by USB cable.
3) Run the tool by clicking on ScreenCap.bat
​4) After taking screen shot, it will be saved in ScreenCapture folder.
Credits:
- Google for ADB engine.
- Kyan.ql for fb2png binary.
Download:
- View attachment 2349228 | @ 25-Oct-2013
- View attachment 2236447 | @ 5-Sep-2013
Change-logs:
Code:
[B][U]v1.10 @ 25-Oct-2013[/U][/B]
- Fixed syntax to support new cmd versions
[B][U]v1.00 @ 5-Sep-2013[/U][/B]
- The first release.
Click to expand...
Click to collapse
Original Thread : http://forum.xda-developers.com/showthread.php?t=2433256
Credits : majdinj
Click to expand...
Click to collapse
What about pressing the thanks button!
im added function Screenrecord and run successfully sent to u
https://app.box.com/s/x933wyk2ukkkgduhadv5
can u test and continues developer?

[solved] I'm trying to flash a new kernel and I'm having some issues

I'm trying to flash lamma sweet kernel http://forum.xda-developers.com/g4/development/kernel-llama-sweet-kernel-t3286514 on a LG g4 h811 running Resurrection remix.
I've had nothing but trouble doing this with 2 builds.
It sends me to fastboot however I can't remember that fastboot said,
heres what fastboot says
FASTBOOT MODE
PRODUCT_NAME - msm8992_p1_two_us
VARIANT - msm8992_p1_two_us Toshiba 32GB
HW VERSION - rev_10
BOOTLOADER VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - LGH811[omitted]
SIGNING - production
SECURE BOOT - disables
LOCK STATE - locked
[1400]
[1450] Fastboot mode started
Click to expand...
Click to collapse
I have sence then done the following
1) tries to get into fastboot using all methods available to me.
a) using the button combo
b) using my reboot menu
c) using adb
All the above methods simply reboot the device. so I'm thinking I don't have fastboot anymore.
My setup.
- I'm using a LG g4 h811 on T-Mobile
- I use twrp as my recovery
- My bootloader is unlocked
- my developer options have allow oem unlock enabled
- I'm running official running Resurrection Remix http://forum.xda-developers.com/g4/development/rom-resurrection-remix-5-6-0-lg-g4-t3287313
- Here's my about phone
{
"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"
}
- my selinux set to is permissive (so i can use Viper4android)
If I've left anything out let me know and I will edit it on here.
Edit: right now I think my my main issue is i cant access fastboot.
My ultimate goal is to flash lamma sweet kernel.
edit 2:
i am now on resurection remix official (not blackjubels edition) post edited to reflect that.
-----
Sent via Tapatalk from my LG G4 running Resurrection Remix
heres what fastboot says afet i flash llama sweet kernel (any version)
FASTBOOT MODE
PRODUCT_NAME - msm8992_p1_two_us
VARIANT - msm8992_p1_two_us Toshiba 32GB
HW VERSION - rev_10
BOOTLOADER VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - LGH811[omitted]
SIGNING - production
SECURE BOOT - disables
LOCK STATE - locked
[1400]
[1450] Fastboot mode started
Click to expand...
Click to collapse
this is verbatim except for the serial number, which i omitted all of it but the model number.
thius was in fact caused by a locked bootloader, solved

[TOOL][RIVA] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

This is the Xiaomi Redmi 5A's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Install APKs
Uninstall APKs
Take a Screenshot
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​
I want to specify that this tool can't bypass Xiaomi Bootloader Unlock procedure but all others function are working
Can we install twrp without bootloader unlock
sadaf06 said:
Can we install twrp without bootloader unlock
Click to expand...
Click to collapse
https://forum.xda-developers.com/xiaomi-redmi-5a/how-to/bypass-bootloader-lock-redmi-5ariva-t3772381
Is any Linux version (say, Ubuntu) available for this app???
anggaalfian32 said:
Nice info bro
Click to expand...
Click to collapse
@anggaalfian32 can you please check your PM inbox and get back to me?
Thanks!
strongst
Forum Moderator
pinakighosh1983 said:
Is any Linux version (say, Ubuntu) available for this app???
Click to expand...
Click to collapse
Nope

Device says bootloader unlocked but OEM unlock option can enabled and disabled ?

I have a Redmi Note 3 (INDIAN VARIANT Kenzo/Snapdragon variant running on Marshmellow 6.0.1 with MIUI Global 10.2) on which I performed an bootloader unlocking procedure via the tool XiaoMiTool V2 from xdahttps://forum.xda-developers.com/android/software-hacking/tool-miunlocktool-unlock-bootloader-t3782444 since the official method kept denying me for some reason
I also want to let you know that during the procedure i left the oem unlocking option disabled (off) and ran the tool
So after the device's bootloader was unlocked (ss attached)
{
"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"
}
I noticed that the OEM unlocking option was still active (meaning I can flip the button and it will just ask for the pass and warn me and enable the option: again ss attached)
Isn't supposed to grayed out ?
So my question is is my device properly unlocked? OR Did I mess up with procedure ? I know i could dial *#*#7378423#*#* (which doesn't work in miui devices) or using fastboot method mentioned here https://android.stackexchange.com/questions/73567/how-to-check-if-your-bootloader-is-unlocked and i got like
What does this mean ?
Any help is highly appreciated and thank you in advance
Once you enable the OEM unlocking in Developer options, in Android's system file build.prop the unlock ability flag is set to 1, what basically is requirement to start the bootloader-unlock procedure, what typically is carried out via Fastboot.
Typically you run
Code:
fastboot OEM get-bootinfo
to check if the bootloader is unlocked.
jwoegerbauer said:
Once you enable the OEM unlocking in Developer options, in Android's system file build.prop the unlock ability flag is set to 1, what basically is requirement to start the bootloader-unlock procedure, what typically is carried out via Fastboot.
Typically you run
Code:
fastboot OEM get-bootinfo
to check if the bootloader is unlocked.
Click to expand...
Click to collapse
Thank you for your prompt reply but i ran this command and it said incorrect command (meaning no such command)
monstervishnu said:
Thank you for your prompt reply but i ran this command and it said incorrect command (meaning no such command)
Click to expand...
Click to collapse
Implementations of Fastboot are different. Some subcommand may be supported, others not: that depends on OEM/Carrier.

Doogee S88 pro - <waiting for device> during fastboot commands

Hello everyone!
This is my first post here so I hope everything I try to explain is according to the rules as far as I read it.
I need to root my Doogee S88 pro mobile since I need test and develop some AR stuff. The standard apps are not accesible by the playstore so I need to bypass that. For doing that I need to root my phone (this is what I read at least).
So... I installed the doggee usb drivers from their website for my phone, usb debugging is activated and OEM is activated as well. I downloaded the most recen platform tools and the usb-cable should be fine since I find the phone with
Code:
adb devices
I execute the following commands:
Code:
adb devices
adb reboot bootloader
fastboot devices
I get the small Fastboot text in the lower left corner. Then if I try to execute
Code:
fastboot flashing unlock
or
fastboot flashing unlock-critical
I only get back <waiting for device>
As said I installed the usb drivers provided by doogee. But: In the device manager I can see the following:
{
"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"
}
Also I periodically (every 10 seconds) hear the sound as if a usb-device is disconnected. Afterwards the device manager refreshes the list.
So... it is a driver issue? I tried updating the drivers but picking manually the folder where driver files are located leads to no result. Automatic search as well. If it is a driver issue - where can I get the appropriate driver files? Thank you for any hint.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Unfortunately that didnt help either. Dunno... What I did was: I switched to my Lnux OS and over there it worked out of the box (only needed to install adb and fastboot from repositories).

Categories

Resources