Unlocking BootLoader :
Requirements:
1. Huawei Mediapad M5 lite ( not region specific).
2. Minimal ADB Tools.
3. Four Credits in DcUnlocker website. (Costs mere 4 euro).
4. DcUnlocker Software
5. Backup of your personal data.
Procedure.
1. First you need to enable usb debugging setting. Connect the tablet to PC in file transfer mode, navigate to Settings -> System -> About Tablet, tap build number multiple times till you get message "You are a developer now" . Now navigate back to System, you will see developer options setting in the menu. Enable "usb debugging" and OEM unlock options in developer options.
2. Download the minimal adb tools zip (link above) and install it your pc.
3. Connect your tablet to pc with usb debugging enabled and open command prompt in the adb folder ( Shift Right click ). In the Command prompt window type
Code:
adb devices
and you will see a device connected in the output. Then type
Code:
adb reboot bootloader
, your device gets rebooted into fastboot mode and you will see message "Bootloader Locked". ( Don't close the command prompt window yet).
4. To Unlock BootLoader you have to go to DcUnlocker website (link above Step 3). There select New user account and your username any then your email and in credits click on " how much do I need " and select third option " Force Huawei Android bootloader unlock (old method) " you will be charged 4 euros. (IMPORTANT: note down to password after creating account)
5a. After successfully creating account download the Dc Unlocker Software ( Step 4) and install it in your PC.
5b. Open the dialer on your phone and enter *#*#2846579#*#* select “Background settings”, “USB ports settings”, “Manufacture mode”.
6. Open Dc Unlocker Software and connect the tablet in fastboot mode to the pc.
On the left side menu
Select Manufacturer -> Huawei Phones
Select Model -> Auto detect
and click on the search icon your device will be dectected in fastboot mode.
7. Click on Server on the right side menu enter your username and password and click on Check login, you will see your username and credits in the output window below.
8. Now click on the Read bootloader code (Unlocking -> Read bootloader code) in the right side menu and wait for the code in the output window. Once you get the Bootloader code note it down.
9. Now open the switch back to command prompt window in your pc, type
Code:
fastboot oem unlock [I]your-unlock-code[/I].
You will be prompted to select Yes/No in the tablet to unlock bootloader, select yes using volume buttons.
10. You have succesfully Unlocked your bootloader, your device gets factory resetted automatically and reboots.
Relocking BootLoader :
Requirements:
1. Unlocked Huawei Mediapad M5 lite ( not region specific).
2. Minimal ADB Tools.
3. Bootloader code ( obtained from unlocking from above guide).
4. Backup of your personal data.
Procedure.
1. First you need to enable usb debugging setting. Connect the tablet to PC in file transfer mode, navigate to Settings -> System -> About Tablet, tap build number multiple times till you get message "You are a developer now" . Now navigate back to System, you will see developer options setting in the menu. Enable "usb debugging" and OEM unlock options in developer options.
2. Download the minimal adb tools zip (link above) and install it your pc.
3. Connect your tablet to pc with usb debugging enabled and open command prompt in the adb folder ( Shift Right click ). In the Command prompt window type
Code:
adb devices
and you will see a device connected in the output. Then type " adb reboot bootloader ", your device gets rebooted into fastboot mode and you will see message "Bootloader UnLocked".
4. Type
Code:
fastboot devices
and you will see a device connected in the output. Then type
Code:
fastboot oem relock [I]your-unlock-code[/I].
5. You have successfully relocked your bootloader, your device gets factory resetted automatically and reboots.
Delete
Just a warning for anyone who bought a cheap M5 Lite at amazon's Black Friday anywhere in Europe with model BAH2-W19C431, as opposed to the older BAH2-W19C432: The unlocking process described above doesn't work any more. Even though DC Unlocker requests 15 cr instead of 4 cr, the unlocking process fails with the following message:
"Factory reset protection Erase start
Fastboot command fail!"
Even though the tablet is obviously still locked, the 15 cr are removed from the account, so you'll have to ask for a refund.
As a slight sidenote, no. 5b of your unlocking procedure should actually be no. 1b, as you obviously can't set the USB connection to Manufacture Mode if you're already in fastboot mode.
Also on WiFi-only tablets there's no dialer, therefore you'll have to use the tablet's calculator and enter ()()2846579()() to get to the configuration menu instead.
@ j04nd03
I guess you are wrong.
I also bought one of the cheap M5 Lite at amazon's Black Friday offer. Code:431.
I can definitely confirm that sadiqkarur´s unlock method is working on 431 with the amount of 4€.
At first i also stuck on the 4€ --> 15€ price rise in the DC unlock tool.
The solution in my case was to install the HUAWEI software package HiSuite to have the right working drivers in the background.
Before installing the Suite the DC unlock tools only found "general" Huawei device by 15€, and after install the description giude worked very well.
Thanks to sadiqkarur, and sorry for my bad english.
At
It was Friday the 29th evening, there was no reply to this thread from @j04nd03 yet.
I tried this guide, i had the first problem in point 5b because I had to look for the calculator solution somewhere else and also because I obviously can't do the calculator procedure if i'm already in fastboot mode (point 3).
Anyway, before going to fastboot I enabled the 'Manufacture mode', then went to fastboot. I paid 4 euro and it said it needed 15. I payed 11 more euros and the procedure failed. Exactly on that error. I asked for a refund.
The day after, Saturday, I read the reply from @j04nd03 and I said to myself "oh well, alright".. The refund arrived on saturday morning already, when the same owner of dc-unlocker replied me telling me that for this tablet there's nothing to do as the security patches locked down the device from being used on dc-unlocker.
Yesterday the 2nd of December I read the reply from @Honeytea. I uninstalled all the previous drivers, rebooted the pc, installed Hisuite drivers and rebooted again (it's usually best to reboot between driver installs) and still nothing. Dc-unlocker still does not give option of 4 credits.
So, if anyone's got a proper procedure this will help a lot, really a lot! No doubt the original procedure of #1 works, but.. something is probably missing.
FW version: BAH2-W19 8.0.0.230 C431
Thanks everybody!
EDIT: Thanks to the post below the unlock worked! :good: :good:
So i actually managed to unlock bootloader via DC-unlocker
FW version: BAH2-W19 8.0.0.230 C431
Procedure:
1: install Minimal ADB Tools.
2: install HiSuite and make all steps to connect tablet with PC.
3: download and install DC-unlocker,
Go https://www.dc-unlocker.com/buy
> select New user account
> type your desired Username and our E-mail
> next to the Credits click on "how much do I need?" and select third option "Force Huawei Android bootloader unlock (old method)"
> NOTE: You will be charged 4€ (IMPORTANT: note down to password after creating account)
4: Connect the tablet to PC in file transfer mode, navigate to Settings -> System -> About Tablet, tap build number multiple times till you get message "You are a developer now" .
Now navigate back to System, you will see developer options setting in the menu.
enable OEM unlock
enable USB debuggin while connected to PC, will ask you if always trust this device ... (for me didn't work at first shot as i didn't install HiSuite before)
5: Open Calculator app and type ()()2846579()()
select Background settings > USB ports settings > Manufacture mode
DO NOT REBOOT TABLET INTO FASTBOOT MODE
for some reason fastboot is changing manufacture mode to default settings and then DC-unlocker not working properely.
6: Open DC-unlocker, Click on Server on the right side menu enter your username and password and click on Check login,
you will see your username and credits in the output window below
select Huawei phones in manufacturer
select auto detect in model
click scan, you should recive something like this
Code:
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM3
Also ports in Aplication position will be selected by the program (COM3 in my case)
Select the same port in Diagnostic
Hit the Read bootloader code and this is what you should get:
Code:
Check account status
User : yournamehere
Credits left : 4
Activated features:
Software debugger
Unlock Auto detect (recommended) cost 4 cr
===================================================================
Reading bootloader code...
Bootloader code : your code will be here
7: copy your code and paste somwhere on notepad to be sure you not gonna lose it
8: open adb and type:
adb devices (to make sure your PC is connected to tablet)
adb reboot bootloader (your device will reboot into fastboot mode now)
9: when you are into fastboot mode type:
fastboot devices (just to make sure if PC is connected to tablet)
fastboot oem unlock drop your code here
You will be prompted to select Yes/No in the tablet to unlock bootloader, select yes using volume buttons.
10: You have succesfully Unlocked your bootloader, your device gets factory resetted automatically and reboots.
Sorry for some copy-pasting from original topic but this way it looks more complex.
Nice., thanks. I just received my tablet today. Will try this tomorrow.
EDIT:
Your tutorial worked very well, thank you. But in Step 8 I had to modify the adb command because I had 2 devices in the list (one beeing an emulator) , so it was:
adb -s DEVICE-ID reboot bootloader
And then I could continue as described.
My menus don't show a "OEM" option after developer mode, any idea?
Finally managed to unlock my device with this, THANKS!! Pretty much had given up on the device when Huawei stopped handing out unlock codes (never again will I buy Huawei)
Next step will be installing openKirin, seems like the device isn't officialy supported but I tried flashing it anyway. Not having much luck so far, device stuck in "booting device" even when formatting data.
Hello ,I have a mediapad M5 that's stuck in retail demo mode ... i followed all the steps from drumiec's post , but i have a problem at step 6 , the DC software doesn't show my bootloader code , but shows me this instead ,can someone help me ?
{
"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 just go the mediapad m5 lite and followed @drumiec directions and it perfectly worked! Thank you again for this.
---------- Post added at 01:37 AM ---------- Previous post was at 01:37 AM ----------
I just go the mediapad m5 lite and followed @drumiec directions and it perfectly worked! Thank you again for this.
Nivans62 said:
Hello ,I have a mediapad M5 that's stuck in retail demo mode ... i followed all the steps from drumiec's post , but i have a problem at step 6 , the DC software doesn't show my bootloader code , but shows me this instead ,can someone help me ?
Click to expand...
Click to collapse
which firmware is running your device?
also try to use different USB cable or different USB port
Maybe it's help to disable the Demo mode in the Developer Settings
---------- Post added at 05:35 AM ---------- Previous post was at 05:31 AM ----------
Unlook is work with the last description (no reboot to fastboot) and for 4Credits.
Only different: I've the LTE Version and instead of the calculator, the dialer must be use with the #*#* sequence from the first posting.
Additional a hint: USB debugging is at every reboot disabled automatically and must enabled every time once again.
On the DC Unlocker shop page, I can't buy 4 credits. I fill everything in as instructed but the web page says "All fields are required to fill" in red even though all of the fields are filled and the confirm button to make a payment is greyed out. I tried the site with Firefox and Chrome and the exact same thing happened with both. Am I missing something obvious?
The username must be at min 6?char. That was an issue, where I was stopped at the first time. After you reach the min. char lengh, the Red color is change to Green. Credits : you can insert direkt 4. Ive search the old Methode in the List, but after selection, the first pages pops up and in the field only the 4 was writen.
mad0701 said:
The username must be at min 6?char. That was an issue, where I was stopped at the first time. After you reach the min. char lengh, the Red color is change to Green. Credits : you can insert direkt 4. Ive search the old Methode in the List, but after selection, the first pages pops up and in the field only the 4 was writen.
Click to expand...
Click to collapse
I actually had to create a 7 digit username and then was able to purchase the 4 credits. Unfortunately, I got the unknown chipset error instead of the bootloader unlock code so the process didn't work for me anyway. Somebody else got the same error but if he was able to get around it I'm not sure how. Thanks for the reply.
Hopefully you have still the 4 credits.
If you connect the Tablet on the PC, the Hires Tool (right name?) start up automatically. Close the program and also kick it out via Taskmanager.
Go into the developer settings of the tablet and ensure that usb Debugging is still enabled.
Try with dcunlocker first of all, that the device is dedected. After that try read BL code in the the Diagnostic area
---------- Post added at 05:42 AM ---------- Previous post was at 05:39 AM ----------
Check also if the usb settings are still in Manufactor Mode (via dialer and *#*# code by a LTE devive)
mad0701 said:
Hopefully you have still the 4 credits.
If you connect the Tablet on the PC, the Hires Tool (right name?) start up automatically. Close the program and also kick it out via Taskmanager.
Go into the developer settings of the tablet and ensure that usb Debugging is still enabled.
Try with dcunlocker first of all, that the device is dedected. After that try read BL code in the the Diagnostic area
---------- Post added at 05:42 AM ---------- Previous post was at 05:39 AM ----------
Check also if the usb settings are still in Manufactor Mode (via dialer and *#*# code by a LTE devive)
Click to expand...
Click to collapse
Still the same error. Also tried the first method which didn't work because the device wasn't in manufacturer mode anymore after fastboot reboot. I think mine might be locked down since it's the US model and this method might only still work for the other models.
Use the second Methode.
The only different is, if you have the LTE Version, that you must use the dialer and not the calculator.
In case, if you use the dialer, you must insert the #*#*..... Code from the first posting.
Don't Boot into the Fastmode to read the Unlook Code.
Check if you habe an access via the Huawei App from the PC to the Tablet.
(An App will be installed on the tablet)
Let the phone connected on the PC.
Close the Huawei Programm on the PC and kick the program out of the memory,
Control after the Huawei App is closed:
that the USB manifacture Mode is enabled,
check in the Developer Settings,
that OEM Unlock,
and USB Debugging
is enabled.
USB Debugging during Charg only could be also enabled (I've make it)
Try out of the shell
adb devices (that you can See the device),
adb shell
and accept on the tablet, that this PC is trusted all time.
Close the command shell with adb
Start dcunlooker, Login with you Account on the Server,
Let dcunlooker dedect the right comport.
After dedecting the Com, selected the same Comport in the Tab one below for Diagnose.
After that selected in Diagnose "Read the Bootloader"
mad0701 said:
Use the second Methode.
The only different is, if you have the LTE Version, that you must use the dialer and not the calculator.
In case, if you use the dialer, you must insert the #*#*..... Code from the first posting.
Don't Boot into the Fastmode to read the Unlook Code.
Check if you habe an access via the Huawei App from the PC to the Tablet.
(An App will be installed on the tablet)
Let the phone connected on the PC.
Close the Huawei Programm on the PC and kick the program out of the memory,
Control after the Huawei App is closed:
that the USB manifacture Mode is enabled,
check in the Developer Settings,
that OEM Unlock,
and USB Debugging
is enabled.
USB Debugging during Charg only could be also enabled (I've make it)
Try out of the shell
adb devices (that you can See the device),
adb shell
and accept on the tablet, that this PC is trusted all time.
Close the command shell with adb
Start dcunlooker, Login with you Account on the Server,
Let dcunlooker dedect the right comport.
After dedecting the Com, selected the same Comport in the Tab one below for Diagnose.
After that selected in Diagnose "Read the Bootloader"
Click to expand...
Click to collapse
I still get the same Not Supported/Unknown Chipset error message. I did everything you suggested but when I type adb shell nothing shows up on my tablet.
Related
{
"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"
}
Setup, Preparation and Prerequisites
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
USB Debugging - On your nexus player go to Settings > About > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enter bootloader mode - Hold the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
Once you are in fastboot mode, the light below nexus player will be blinking constantly. You can verify by using "fastboot devices"
ADB Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components here
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal storage (pictures, music, etc.). Copy all important files off the nexus player onto a PC or upload them to a cloud.
Driver Installation
Go to Device Manager, find the Android device, and select Update Driver Software.
Select Browse my computer for driver software
Select Let me pick from a list of device drivers on my computer
Selecting show all devices
Clicking have disk
Finally selecting Desktop\android-sdk-windows\extras\google\usb_driver\android_winusb.inf as the driver
Alternative you can also download and install the Universal ADB Driver.
Downloads
Root:
Android 7.X:
- Coming Soon-
Android 6.X:
http://cord-cutters.wonderhowto.com/how-to/root-nexus-player-0160218/
http://androidflagship.com/16765-root-nexus-player-android-6-0-marshmallow
Android 5.X:
Download the SuperSU zip below. Extract the zip file and you will have (root.img) to platform-tools folder located on your desktop within the android-sdk-windows folder.
SuperSU (Forum Thread) or SuperSU (Direct link)
Information
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 2 main steps: Unlocking the Bootloader and Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the device in future.
Rooting: You can gain root booting up root.img
1. Unlocking Bootloader
Turn the nexus player off. Then go into bootloader mode by holding the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
Plug nexus player into your PC, then open a command prompt window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your nexus player serial number shows up you are good to go and may continue. If the nexus player is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the nexus player has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
OEM unlock twice
Code:
fastboot oem unlock
Code:
fastboot oem unlock
After you have done, please proceed onto the next section of the guide.
2. Installing a Custom Recovery
http://forum.xda-developers.com/nex...recovery-twrp-2-8-6-0-touch-recovery-t3114717
https://twrp.me/devices/asusnexusplayer.html
3. Rooting
Now that your nexus player has an unlocked bootloader, now this step is to gain root
Android 7.X
- coming soon -
Android 6.X
Require: TWRP, Custom boot.img and flashable supersu
(Refer to above link)
Android 5.0
Warning: This rooting guide is for Android 5.X only!
Boot (not flash) the root image which will give you root with the stock ROM
Confirm that you have downloaded the SuperSU zip from the downloads section above and you have extracted it and it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Make sure the nexus player is in bootloader mode
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot boot root.img
This will install SuperSU on your device, once the command has completed continue.
Open SuperSU and update the binaries.
Keep in mind that the first boot may take longer than usual.
Congrats! Your nexus player now has an unlocked bootloader, and is rooted.
==================================================
How to flash factory image for Nexus Player?
1) Download image file for your nexus player - https://developers.google.com/android/nexus/images
2) Boot your Nexus device into fastboot mode.
3) On your computer, use 7zip to extract the .tgz file you downloaded from the Android Developer website. Use 7zip a second time to extract the .tar file you extracted from the .tgz. When you’re done, you should have a folder with several files in it.
4) Copy all of these files and paste them in the platform-tools folder in the Android SDK on your computer. If you followed the above tutorial, this should be under the C drive, then under Program Files (x86) on Windows. Linux users, you know where you put it.
5) If you have not already done so, connect your Nexus device to your computer. ADB and Fastboot commands should already work at this point if you’ve been following along.
There are two flash-all files. If you’re in Windows, you’ll want to double click the one that has the gear logo and says “Windows Batch File” on the right. If you’re on Linux, you’ll want to double click the flash-all.sh.
At this point a box should pop up and you should see the installation taking place. While this is going on, do not unplug your device for any reason. Let it do its thing.
6) Once the installation process as finished, your device will automatically reboot and you can now safely disconnect your device from your computer.
==================================================
Credits:
- Chainfire (SuperSU and Rooting guide)
- Chromium (Easy to understand and detailed guide format)
- DevinWatson (USB driver guide)
- androidauthority (Flash firmware image guide)
Nice guide.
What about installing BusyBox?
I have a USB OTG cable but the adapter is female on the available USB side...I am not sure how to go about connecting my laptop/PC to the NP in order to perform ADB commands. Do I need a special cable or is there another way?
arecad said:
I have a USB OTG cable but the adapter is female on the available USB side...I am not sure how to go about connecting my laptop/PC to the NP in order to perform ADB commands. Do I need a special cable or is there another way?
Click to expand...
Click to collapse
Don't use the USB OTG cable, use a micro USB cable (same kind of cable that comes with android phones)
I cannot believe I missed that, how embarrassing. Thanks for the response, now I can follow this guide. I was thinking too hard about the OTG cable being a necessary piece of the puzzle.
I am able to get to the bootloader with no problems, I've got ADB and Fastboot installed on my PC, as well as the drivers. However ADB doesn't pick up my NexusPlayer even though fastboot does. Thoughts?
See Attachments
EDIT: Nevermind, I was expecting different responses from adb/fastboot. When in the bootloader adb will not confirm a connection, only fastboot. Sorry for being a noob...
xDragonZ said:
1. Unlocking Bootloader
[*] Turn the nexus player off. Then go into bootloader mode by holding the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
[*] Plug nexus player into your PC, then open a command prompt window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
[COLOR="red"]adb devices[/COLOR]
This command will list the connected devices. If your nexus player serial number shows up you are good to go and may continue. If the nexus player is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under adb devices.
Click to expand...
Click to collapse
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
midnightzak said:
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
Click to expand...
Click to collapse
AFAIK ADB is for Android, and Fastboot is for bootloader.
But i have the oposite problem. Mine NP is getting recognized useing ADB when normaly booted, but when i am in fastboot mode, fastboot isent working. I get no output when run 'fastboot devivces'. I have both tried to set the NP in fastboot mode by using the hiod button and plug in power, and with adb rebbot bootloader.
Any one have a clue why adb works, but not fastboot?
Double check to see if you have the latest version of fastboot. I have read that if you don't have the most up to date version the NP is not recognized.
Sleeepy2 said:
Double check to see if you have the latest version of fastboot. I have read that if you don't have the most up to date version the NP is not recognized.
Click to expand...
Click to collapse
+1 this.
goxboxlive said:
AFAIK ADB is for Android, and Fastboot is for bootloader.
But i have the oposite problem. Mine NP is getting recognized useing ADB when normaly booted, but when i am in fastboot mode, fastboot isent working. I get no output when run 'fastboot devivces'. I have both tried to set the NP in fastboot mode by using the hiod button and plug in power, and with adb rebbot bootloader.
Any one have a clue why adb works, but not fastboot?
Click to expand...
Click to collapse
Have you re-installed the Google driver when you are booted in the bootloader? The driver needs to install twice: once when booted into Android, and once when booted into the bootloader
ADB fastboot for Mac Quick Question??
Hey guys does anyone have any idea on how this can be done on a Mac....I know I know. When I initially plug in my Nexus player with the micro usb, nothing happens on my mac or the Nexus so i am guessing that the drivers are not installed. How would i go about getting these for the Mac? I have already downloaded the slim version of the ADB and Fastboot files with the platform tools into a folder on my desktop named Andriod, so i have these already. And i know that if you hold the button down on the nexus and plug the power in it brings up the bootloader screen. I just need help with the commands in terminal and where to access the drivers from. Also, on the Nexus the Developer options have already been enabled and USB debugging has been turned on. If anyone can help, It would be much appricated! Just started to use terminal commands so yes i am a noob in this department . Thanks agin in advance.
-Jason
MrBoostinduced said:
Hey guys does anyone have any idea on how this can be done on a Mac....I know I know. When I initially plug in my Nexus player with the micro usb, nothing happens on my mac or the Nexus so i am guessing that the drivers are not installed. How would i go about getting these for the Mac? I have already downloaded the slim version of the ADB and Fastboot files with the platform tools into a folder on my desktop named Andriod, so i have these already. And i know that if you hold the button down on the nexus and plug the power in it brings up the bootloader screen. I just need help with the commands in terminal and where to access the drivers from. Also, on the Nexus the Developer options have already been enabled and USB debugging has been turned on. If anyone can help, It would be much appricated! Just started to use terminal commands so yes i am a noob in this department . Thanks agin in advance.
-Jason
Click to expand...
Click to collapse
http://developer.android.com/sdk/win-usb.html
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. To start developing with your device, read Using Hardware Devices."
http://developer.android.com/tools/device.html
Sleeepy2 said:
http://developer.android.com/sdk/win-usb.html
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. To start developing with your device, read Using Hardware Devices."
http://developer.android.com/tools/device.html
Click to expand...
Click to collapse
Hey Sleepy2, I just did a brief read through and it states this:
Set up your system to detect your device.
If you're developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
If you're developing on Mac OS X, it just works. Skip this step.
If that is the case, what would you suggest doing next? Thanks again for helping!
MrBoostinduced said:
Hey Sleepy2, I just did a brief read through and it states this:
Set up your system to detect your device.
If you're developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
If you're developing on Mac OS X, it just works. Skip this step.
If that is the case, what would you suggest doing next? Thanks again for helping!
Click to expand...
Click to collapse
Open a terminal, navigate to the directory where you downloaded fastboot and go ahead with the commands shown in the first post. You will probably have to add a "./" in front of the commands given that you are on a mac, e.g.,
Code:
fastboot devices
becomes
Code:
./fastboot devices
I seem to be having the same problem as goxboxlive. I have tried installing the drivers about 100x tried on several computers and rebooted many a time. The only thing I can think of from the posts in here was to update fastboot but I dled the android studio and I would assume that has the latest version in there? Otherwise I couldn't find somewhere to download just fastboot from. Any help or recommendations or where I can dl the latest fastboot?
---------- Post added at 02:28 PM ---------- Previous post was at 01:57 PM ----------
Follow up. Got it to work. In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
knobbs said:
I seem to be having the same problem as goxboxlive. I have tried installing the drivers about 100x tried on several computers and rebooted many a time. The only thing I can think of from the posts in here was to update fastboot but I dled the android studio and I would assume that has the latest version in there? Otherwise I couldn't find somewhere to download just fastboot from. Any help or recommendations or where I can dl the latest fastboot?
---------- Post added at 02:28 PM ---------- Previous post was at 01:57 PM ----------
Follow up. Got it to work. In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
Click to expand...
Click to collapse
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
midnightzak said:
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
Click to expand...
Click to collapse
knobbs said:
In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
Click to expand...
Click to collapse
midnightzak said:
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
Click to expand...
Click to collapse
To avoid further confusion, I've updated the post since the OP hadn't yet.
midnightzak said:
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
Click to expand...
Click to collapse
efrant said:
To avoid further confusion, I've updated the post since the OP hadn't yet.
Click to expand...
Click to collapse
Thank you, saw your post that time and wanted to change it but keep forgetting.
Currently working on some basic developer app for Nexus Player.
xDragonZ said:
Thank you, saw your post that time and wanted to change it but keep forgetting.
Currently working on some basic developer app for Nexus Player.
Click to expand...
Click to collapse
It's all good, wasn't terrible let to figure out, and if you're developing even more for the Nexus Player, the more power to ya! Keep it up!
I got tired of ZenUI and I was searching for a method to install CM14. The problem all starts with my bootloader.
I've tried to find an unofficial way to do it and I couldn't find one specific for my phone.
The official one just retarts my phone, or it just tells that there's a network error. Something like that.
I hope I don't need to do downgrading.
Zenfone Selfie Z00UD (ZD551KL)
MMB29P.WW_user_21.40.0.1923. 20161027
Cristianrr said:
I got tired of ZenUI and I was searching for a method to install CM14. The problem all starts with my bootloader.
I've tried to find an unofficial way to do it and I couldn't find one specific for my phone.
The official one just retarts my phone, or it just tells that there's a network error. Something like that.
I hope I don't need to do downgrading.
Zenfone Selfie Z00UD (ZD551KL)
MMB29P.WW_user_21.40.0.1923. 20161027
Click to expand...
Click to collapse
Hello,
You may follow the instructions here.
Later once the configuration is done properly then you can connect your device and enable USB Debugging under the options.
1. Download Modaco Superboot file for Asus Zenfone Selfie Zd551kl from this link : http://downloadsafe.org/file/0YgX7 , and save them to your computer.
Tutorial Video : Easy Way To Download file = http://how-to-root.com/10
2. Once downloaded, extract it by right clicking and extract all.
3. On your device, click on Settings > Developer Options > Turn USB Debugging On.
4. Plug the device in to your computer via USB cable.
5. Open the superboot folder that we just extracted (until you see the folder with fastboot-windows inside it), then hold the shift key down on your computer and right click any blank area.
6. Now, select open command window here.
7. In the command prompt, type the following with hitting enter at the end of each line.
adb-windows reboot bootloader (and wait for the device to reboot) fastboot-windows oem unlock *If it gets stuck at waiting for device here, download and install PDANet on your computer, once installed, unplug then plug the device back in and see if that fixes it.
Once it runs the device should display a screen asking you if you are sure. Click yes using the volume buttons. The device will go back to the bootloader screen but say unlocked at the bottom.
Also here's the firmware needed to unlock bootloader for your reference https://forum.xda-developers.com/zenfone2/help/zd551kl-zenfone-selfie-unlock-t3271243
Regards
Vatsal,
Forum Moderator.
Vatsal said:
Hello,
You may follow the instructions here.
Later once the configuration is done properly then you can connect your device and enable USB Debugging under the options.
1. Download Modaco Superboot file for Asus Zenfone Selfie Zd551kl from this link : http://downloadsafe.org/file/0YgX7 , and save them to your computer.
Tutorial Video : Easy Way To Download file = http://how-to-root.com/10
2. Once downloaded, extract it by right clicking and extract all.
3. On your device, click on Settings > Developer Options > Turn USB Debugging On.
4. Plug the device in to your computer via USB cable.
5. Open the superboot folder that we just extracted (until you see the folder with fastboot-windows inside it), then hold the shift key down on your computer and right click any blank area.
6. Now, select open command window here.
7. In the command prompt, type the following with hitting enter at the end of each line.
adb-windows reboot bootloader (and wait for the device to reboot) fastboot-windows oem unlock *If it gets stuck at waiting for device here, download and install PDANet on your computer, once installed, unplug then plug the device back in and see if that fixes it.
Once it runs the device should display a screen asking you if you are sure. Click yes using the volume buttons. The device will go back to the bootloader screen but say unlocked at the bottom.
Also here's the firmware needed to unlock bootloader for your reference https://forum.xda-developers.com/zenfone2/help/zd551kl-zenfone-selfie-unlock-t3271243
Regards
Vatsal,
Forum Moderator.
Click to expand...
Click to collapse
I cannot skip the survey. The only one I get requires me to register my phone number. Is there any other download link?
Thank you
Do it on your own Risk I am not responsible for any kind of brick.
Your warranty will be void.
Install adb driver first on your PC.
1. Settings >> About phone >> Tap “Build Number” seven times. You will see “You are now a developer”
2. Hit the back button. You will now see a new option in Settings — “Developer Options”
3. Turn on the developer options
4. **In the Developer Options, Enable OEM Unlock (Allow bootloader to unlock)
5. **Enable USB debugging
6. Plug your phone to PC via USB cable
7. open Command Prompt with admin right on your pc and type adb devices.
8. You should then see a pop up request on your Infinix Zero 5 to give your PC USB debugging permissions. Go ahead and allow
9. Type again adb devices it will show your device in list in command prompt (like Some number)
10. Type adb reboot bootloader (your phone will reboot to fastboot mode (a dim black screen will appear))
11. Type fastboot oem unlock.
12. it will ask for permission press volume+ button to confirm and wait to complete. (done, it will erase all your data)
will take more time to reboot first time.
upto step 10 I can see as described, but nothing happens at step 11.
sanjiv204 said:
upto step 10 I can see as described, but nothing happens at step 11.
Click to expand...
Click to collapse
your driver not installed correctly.
when you enter in fastboot/bootloader mode just type fastboot devices.
if there it shows your device then only further cmd will work.
and it shows only if fastboot driver installed correctly.
Read this may help you; 1. https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
2. https://www.xda-developers.com/install-adb-windows-macos-linux/
thanks, you were right.
lalitjoshi06 said:
your driver not installed correctly.
when you enter in fastboot/bootloader mode just type fastboot devices.
if there it shows your device then only further cmd will work.
and it shows only if fastboot driver installed correctly.
Read this may help you; 1. https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
2. https://www.xda-developers.com/install-adb-windows-macos-linux/
Click to expand...
Click to collapse
I could get to the screen where it asks for the permission on the phone screen. But could not muster courage to go ahead. will try some other time once I have full backup.
Thanks again.
Hi, Thanks for the described process. As mentioned above, I am also unable to pass through point 11. I can see the dim screen on the mobile, but on fastboot command, it appears to wait for the device.
Your help is highly appreciated.
is there a way to remove this message after unlocking bootloader ?
orange state : your device has been unlocked
Earlier today I was alerted to https://www.cnblogs.com/yanhua-tj/p/15525593.html which has the actual firehose and steps to unlock! However it seems to be in Simplified Chinese so I'll translate it here for you.
The firehose is attached below.
DISCLAIMER: I am not responsible for any damages this may cause as I am merely translating the guide, I am not responsible for you bricking your device because of a missed step so read carefully,
Also, Please backup your data beforehand as this does wipe the phone. Also please note that if you are on android 11 LG Backup will not work after unlocking, neither does the LG Bridge tool.
***IF YOU WANT ANDROID 12, UPDATE BEFORE ROOTING, I HAVE CONFIRMED IT WORKS FINE***
Requirements:
Get QPST Here
Get the FIrehose Here
Engineering Bootloader Here
Adb and Fastboot Here
Qualcomm Drivers Here (When installing make sure to select wwan)
Frp with oem unlock bit set for Verizon Here Not for demo units!
Slight knowledge of the command line
A Brain
Steps:
If you already have it unhidden go to Developer Options under Settings -> System and enable OEM Unlock as well as USB Debugging. If you don't see Developer Options go to Settings => System => About Phone => Software Information and tap Build Number until it either asks you for your password or says you are a developer at the bottom. Verizon Users: You will not see the oem unlock option, we will fix this later in this guide.
2) Get it into 9008 Mode: (This may take several tries)
Make sure you are connected to your computer via USB.
Hold Volume Down and Power until it shuts off
Now here's the tricky part, as soon as the screen turns off, immediately start tapping volume up quickly, but do not let go of volume down and power, if you did it successfully you will see your screen is off but it appears either in Device Manager or Windows plays the Device Connected sound.
Open and Configure QFIL as shown below:
{
"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"
}
After that click Browse and select the Firehose you downloaded earlier
Next go to the Tools menu at the top then select Partition Manager (If this errors please reboot back into edl using the steps mentioned above!)
After that wait for QFIL to connect then a new window will pop up. FInd abl_a and abl_b, right click on each and click Manage Partition. First thing you want to do for each is click Read Data. This will back them up in case of anything going wrong. QFIl will tell you where it stores them. Then for each click Load Image and select the Engineering Bootloader you downloaded from before.
Once you get that done for both abl_a and abl_b click close on both the Raw Data Manager and Partition Manager and wait for QFIL to say Finish Reset to EDL in the logs at the bottom.
Now it's time to get into Fastboot.
Press and Hold Power and Volume Down for 9 seconds
Once you either see it disappear from QFIL or you hear it disconnect from your PC, let go of power, until you see Fastboot Mode on your Phone's screen.
Open the command prompt on your computer.
Once it's in fastboot verify if fastboot can see it by doing fastboot devices, if it can't see it troubleshoot here:
Check your USB Connection
Double check you installed the adb and fastboot stuff from earlier in the post
There may be a chance WIndows doesn't recognize it properly. So follow these steps:
Open Device Manager by doing Windows + X and clicking Device Manager
There may be an already open row that says Unknown Devies
Right click on android and select Update Drivers
Select Browse my computer for drivers
Select Let me pick from a list of available drivers
Select Android Device
Select Android Bootloader Interface
Click Ok on the pop up
Once that finishes double check the phone can be seen in fastboot devices
Now here comes the fun part, unlocking! Please make sure you have your data backed up.
If you are on verizon (and it's not a demo unit)
Make sure you downloaded the file from above for the unlocked frp
Do fastboot flash frp frp.img
Do fastboot reboot and let it boot into android once, no need to set it up
Reboot back to Fastboot using step 9
Do fastboot oem unlock
Select Unlock the Bootloader using volume down and power, your phone will wipe and reboot
On any other variant
Do fastboot oem unlock
Select Unlock the Bootloader, your phone will wipe and reboot
And that's it! Rooting guide will be on post 3.
If you have any questions or feel like this is too complicated, please don't hesitate to contact us {Mod edit}
Rooting with Magisk:
You need to have already done the unlock mentioned above
Go back to the guide and go all the way to the Partition Manager part, but don't flash anything.
Now find and right click boot_a, click Manage Partition Data, and click Read Data do the same for boot_b.
Wait for that to finish, when it does QFIL will tell you where it stored it.
Grab the file and place it somewhere as a backup.
Rename it to something like boot_a.img and boot_b.img
Either use an existing device with Magisk or restart your device and install the magisk app from Here (make sure to download the Magisk-v2x.x.apk)
Transfer the images you got to your phone in whatever method you'd like.
In the Magisk App where it says Magisk, click Install, then choose Select and Patch a File. Make sure to patch both boot images separately!
Wait for that to finish, after that transfer the modified image back to wherever you want to keep it. To make it easier rename it to something like MagiskPatchedBoot_a.img and MagiskPatchedBoot_b.img
Get into fastboot by Either:
Shutting the phone off, and holding volume down while plugging in the usb cable
Do adb reboot bootloader if you have adb debugging setup.
Now in the directory of your patched image do fastboot flash boot_a MagiskPatchedBoot_a.img and fastboot flash boot_b MagiskPatchedImage_b.img
Now do fastboot reboot and you're golden!
Misc Fixes:
Spoiler: Getting back the Fingerprint scanner after unlock NOT REQUIRED ON ANDROID 12 (Credits to Leronex_1)
Open the dialer and dial: ` *#546368#*600# ` | Verizon (V600VM): ##228378 (+ send)
SVC Menu > Handprint > HandID Logging = ON | ON VERIZON SKIP THIS STEP
Device Test > SAAT > Service Menu – Manual test > Optical Fingerprint test Complete the test and when a green circle shows tap it, when you see a button “pass” click it. At the end it should fail so just click the “fail” button when there is no “pass” button anymore. Start the test by clicking "start", then hold the green circle with your finger till the test finishes. On the last test it will fail so just click on "fail".
Repeat 3 times and try adding a fingerprint, if fingerprint still does not work just restart and retry again.
Spoiler: Making /system RW (Credits to Leronex_1 and lebigmac)
Download system systemrw_1.31d_BUNDLE.zip from https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/
Place folder systemrw_1.31d in /data/local/tmp on the phone
Place sysrw_repair_v1.31d on your linux machine
Go to adb shell, su and then do "chmod +x /data/local/tmp/systemrw_1.31d/systemrw.sh"
Then in adb shell do cd /data/local/tmp/systemrw_1.31d and do ./systemrw.sh size=15 or 20 and wait till its done
Go to the linux machine and cd to sysrw_repair_v1.31d from step 3
Connect adb with your phone and make sure to not accidentally disconnect it (This will take a while)
In the sysrw_repair_v1.31d directory, do sudo ./sysrw_repair.sh and make sure your Linux machine has at least 25gb Storage space, this process will take more or less 30 mins depending on how fast the machine is
When its done it should start flashing in fastboot automatically.
Spoiler: Enabling VoWifi on V600EA (Credits to Leronex_1)
Make sure to follow the guide to make /system rw or else you will end up in a non bootable system!
1. Add these lines below to your build.prop (First set permissions on the build.prop so you can write it)
Code:
Debug Options
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
# Radio Options
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
Make sure to set the Permissions back to chmod 600
2. Reboot, go to settings > Networks > Calls > Enable WIFI Calling
3. If it won't turn on by itself you might need to enter the Service menu and go to SVC Menu > VoWIFI > WIFI Calling Toggle = 1
Credit: Leronex (Discord), Leronex_1 (XDA)
Spoiler: Disabling rct (Credits to null-dev)
You must make /system RW using the guide above
1. adb shell, pm uninstall -k --user 0 com.lge.rctprovider
2. adb reboot bootloader, fastboot erase rct, Reboot to System
3. adb shell, pm uninstall -k --user 0 com.lge.srtc
4. Download and install the Magisk module: https://github.com/null-dev/lg-v60-rct-disable-magisk/raw/master/lg-v60-rct-disable-magisk.zip, then reboot the phone.
5. Delete /mnt/product/persist-lg/rct folder
Done, how to check if it is disabled? "Adb shell", "su" and "getprop | grep rct". If it shows nothing as output that means the service is not running. After that check the service menu *#546368#*600# > SVC Menu > LG RCT (Has to say Disabled)
Spoiler: Disable OTA Updates (Credits to Leronex_1)
Code:
adb shell pm uninstall -k --user 0 com.lge.lgdmsclient
On TMO After 20j:
Code:
adb shell pm uninstall -k --user 0 com.lge.android.atservice
adb shell pm uninstall -k --user 0 com.lge.gdec.client
adb shell pm uninstall -k --user 0 com.lge.lgfota.permission
adb shell pm disable --user 0 com.lge.pickme
Spoiler: Disable Smart doctor to save battery (Credits to Leronex_1)
Code:
adb shell pm disable --user 0 com.lge.phonemanagement
Spoiler: Crossflashing Guide (Credits to Leronex_1)
1. Download and install QPST, when installed launch it and select the firehose and Nand type e.g. UFS.
2. Download and install this LGUP from here: https://drive.google.com/file/d/1VxecFNYK2Lr7w1HVg-mNIGEoVa8CSHFt/view?usp=sharing . In the installer select "Install LG Drivers"
3. Put phone into edl mode, here is how: Hold Vol- and pwr, when the screen turns black keep holding them and Repeatedly press vol+ You will see "Qualcomm HS-USB QDLoader 9008" under "Ports (COM & LPT)" in device manager when it is in edl. If the screen shows anything after reboot, instantly retry again.
4. When it is in EDL Mode, open partition manager and make a backup of these partitions "FTM, OP_A OP_B, MODEM_A MODEM_B, SID_A SID_B.
5. After backing up, erase the same partitions "FTM, OP_A OP_B, MODEM_A MODEM_B, SID_A SID_B.
6. Now after erasing it is sort of important to not let it boot to android, and instead boot to download mode. Here is how: force reboot with vol- and pwr button. As soon as it disconnects from windows, Release the Vol- and Power buttons and hold Vol+ to get into Download Mode.
7. When it enters Download mode, open LGUP and select partition DL. Select your favourite V60 KDZ too.
8. Click on start, then it will prompt you to select partitions that can be flashed, select every partition EXCEPT "SID_A SID_B AND ABL_A ABL_B" then confirm. (NOTE: DO NOT CLICK "SELECT ALL" IT IS BUGGED AND WILL FLASH ALL PARTITIONS, EVEN IF UNSELECTED AFTER)
9. Let it install, after that you should be done, hidden menu won't work but you can install this apk to be able to enter hidden menu and fix the fingerprint on an unlocked bootloader. https://drive.google.com/file/d/1g-7BQ_Jlmi-5tpbMg383LaiYr5YjTmqQ/view?usp=drivesdk
Reserved Post #3
looks good
v60 demo unlock boot and root
THX!
Raify4 said:
v60 demo unlock boot and root
THX!
Click to expand...
Click to collapse
This doesn't work for the demo I should have clarified
crimsonrommer said:
This doesn't work for the demo I should have clarified
Click to expand...
Click to collapse
I tried on my demo unit and it worked
Is that the 601?
Raify4 said:
I tried on my demo unit and it worked
Click to expand...
Click to collapse
Note that the verizon variant has removed the OEM unlock option from developer options, so you'll need to flash an FRP partition with the OEM unlock bit already set.
Leronex and I kinda puzzled that one out.
manywelps said:
Note that the verizon variant has removed the OEM unlock option from developer options, so you'll need to flash an FRP partition with the OEM unlock bit already set.
Leronex and I kinda puzzled that one out.
Click to expand...
Click to collapse
Yeah issue is qfil doesn't see frp so we're trying to find a workaround
crimsonrommer said:
¿Ese es el 601?
Click to expand...
Click to collapse
back cover shows lm v601u
Leronex flashed a different V60's FRP (with the bit set) on my verizon phone and then the unlock worked smoothly.
He used Medusa which can flash the FRP partition independently though.
manywelps said:
Leronex flashed a different V60's FRP (with the bit set) on my verizon phone and then the unlock worked smoothly.
He used Medusa which can flash the FRP partition independently though.
Click to expand...
Click to collapse
Yeah I know, the issue is qfil doesn't see it
Would it still be possible to update after bootloader unlock, even if it's by LGUP?
Other than that, you guys rock! Thank you for providing the translations for us mere mortals to understand
vitalez06 said:
Would it still be possible to update after bootloader unlock, even if it's by LGUP?
Click to expand...
Click to collapse
Yep! Just make sure to use partition dl and uncheck abl_a and abl_b that way fastboot remains, and you can still extract your boot partition and root again
i get this error , help
kiory01 said:
i get this error , help
Click to expand...
Click to collapse
i dont see an error
crimsonrommer said:
i dont see an error
Click to expand...
Click to collapse
same for me, actually no error but after clicked on portion manager, there is popup window appeared saying make sure correct firehose file selected, clicked ok, then screen stuck there no partition manager window appeared yet nothing in log folder as well.
TLDR:
I bought a cheap Teclast P25T tablet with slim-to-no support for customization/modding/rooting/etc. I really would appreciate any help I could get and will be very responsive, listen intently, and be very descriptive in my feedback. I consider myself very tech-savvy, but I am no expert in coding/software modding/android modding/hacking in general. In fact, I would say I'm rather new to this realm, and that is why I have come to ask for help from THE BEST, the XDA community.
(Short) Device Specs and Options:
Manufacturer: Teclast
Model: P25T
ID: P9A6
USB debugging: Enabled
OEM unlocking: Enabled
Why I bought the Device:
I recently bought a new Android tablet rather impulsively I will admit, my purpose for the device was to disable the bootloader and root the tablet for fun, exploration, and ultimately boot a custom Linux operating system that has root privileges for providing defensive network security to prevent and identify threats on free local wifis. This is proving to be a significant challenge for a few reasons.
My Personal Objectives:
Unlock the bootloader
Gain superuser/root privileges
Install Kali and remove the current OS/ROM (not sure what it's called)
Spoiler: Current Project Status:
Current Project Status:
Found the manufacturer's official software/firmware download page: https://en.teclast.com/pages/firmwaredownload
The RevDev_Tool has a "config.ini" file with an option under [Language] for changing the software language.
Change "Selected=1" to "Selected=2"
*Note i have no idea how to use this tool and the tool was not able to identify my device was plugged in
Found the official youtube channel and a 5-year-old video where they show how to "flash" the device
Official page: https://www.youtube.com/@TeclastOfficial
Title: "Teclast Root Process for Android Tablet"
Multiple comments state that this video does not in fact show any actual rooting of the device shown, but rather a way to "flash"
The video shows software that does not appear to be in the manufacturer's firmware folder when I downloaded the files from the official firmware page. (I made sure to use my device "ID": P9A6)
The software in the video (SCP_Flash_Tool) I was able to track down: https://spflashtool.com/
I downloaded platform tools & SamFW_Tool
I can see the device under ./adb devices, but not ./fastboot devices
research indicates it's likely a driver issue.
I have attempted to solve the issue but am yet to do so, and now I likely need to uninstall drivers to get a clean install since I have several drivers installed.
./adb reboot bootloader
The device turns off, turns on to the booting screen, *stops* (I have waited up to 10 minutes)
I then need to turn the device on/off 3 times to get to boot up
Using SamFW Tool I rebooted into [FASTBOOT] Recovery and was greeted with the "No Command" text and the android on its back with the caution logo image that is common
Loading into custom boot settings via external buttons & factory reboot
nothing has worked that I have tried:
Turn device off, then hold volume down + Power, *device boots normally*
Turn the device off, hold both volume keys + plug it into the computer, *Device boots normally*
In settings, I was able to locate the Factory Reboot option and was able to reboot
The device loaded a custom reboot screen before loading into the user setup process
the device performed a factory reset successfully
Spoiler: (Long) Device Specs:
(Long) Device Specs: (SamFW Tool 4.6)
I (REDACTED) some of the info I believed to be private. let me know if any of this is relevant to assisting me.
Device information
Model : P25T_ROW
Brand : Teclast
Device name : P25T_Y_ROW
Product name : P25T_Y_ROW
CPU : rk30sdk
Platform : rk356x
CPU Arch : arm64-v8a
Serial number : (REDACTED)
Software information
Build : V1.00_20221212
Version : 20220914
Build date : Mon Dec 12 11:53:52 CST 2022
Fingerprint : Teclast/P25T_Y_ROW/P25T_Y_ROW:12/SQ1D.211205.016.A5/20220914:user/release-keys
Security patch : 2022-09-05
Android version : 12
Android SDK : 32
Device status
USB : mtp,adb
Timezone : Asia/Shanghai
Language : en-US
Device state : locked
Network type : Unknown
Android ID : (REDACTED)
Wifi Address : (REDACTED)
Root status
Shell SU : NO
Binary Magisk : NO
Binary SU : NO
App Magisk : NO
App SuperSU : NO
Spoiler: Developer Menu Screenshots:
Developer menu screenshots:
{
"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"
}
Comments:
Hello, XDA community, I am new to the forums and did my best to try to properly label my question thread, post in the correct forum, and provide relevant info in this description. If I should repost, or modify the thread to comply or better communicate my needs and question I would be more than happy to do so. I apologize if my terminology and knowledge make it difficult to understand what my needs are, but I will be carefully reviewing all replies and will make sure to take notes and incorporate all feedback into my understanding.
I'm not familiar with that device, sounds like a cheap Chinese knockoff.
Have you tried the standard ADB commands to unlock the bootloader?
If you haven't already, download SDK Platform Tools 33.0.3, you can find it here at the top of the thread. Do not use 34.x+ as there's some rather fatal issues.
Extract the Platform Tools folder, launch a command window in the folder (where you see adb.exe and fastboot.exe), connect your tablet via USB and run adb devices
If it has to start the daemon, simply run the command again, and ensure you've authorized ADB on your device (you should get a popup about authorizing the PC). You should see the serial number of your device appear under adb devices
Next, reboot to bootloader: adb reboot bootloader. If you can, post a photo of the screen with the serial number redacted. Try to command bootloader unlock: fastboot flashing unlock
You may also need to use fastboot flashing unlock-critical
You should get a message on the screen confirming you want to unlock the bootloader. Proceeding will wipe data.
Once the bootloader is unlocked, you would be able to flash custom images. The best way to root is to use Magisk; see these instructions. The easiest way will be to extract the factory firmware and look for boot.img; patch this in Magisk on the device, then reboot to bootloader again and flash the patched image to /boot.
V0latyle said:
I'm not familiar with that device, sounds like a cheap Chinese knockoff.
Have you tried the standard ADB commands to unlock the bootloader?
If you haven't already, download SDK Platform Tools 33.0.3, you can find it here at the top of the thread. Do not use 34.x+ as there's some rather fatal issues.
Extract the Platform Tools folder, launch a command window in the folder (where you see adb.exe and fastboot.exe), connect your tablet via USB and run adb devices
If it has to start the daemon, simply run the command again, and ensure you've authorized ADB on your device (you should get a popup about authorizing the PC). You should see the serial number of your device appear under adb devices
Next, reboot to bootloader: adb reboot bootloader. If you can, post a photo of the screen with the serial number redacted. Try to command bootloader unlock: fastboot flashing unlock
You may also need to use fastboot flashing unlock-critical
You should get a message on the screen confirming you want to unlock the bootloader. Proceeding will wipe data.
Once the bootloader is unlocked, you would be able to flash custom images. The best way to root is to use Magisk; see these instructions. The easiest way will be to extract the factory firmware and look for boot.img; patch this in Magisk on the device, then reboot to bootloader again and flash the patched image to /boot.
Click to expand...
Click to collapse
It is truly the CHEAPEST of the Chinese knockoffs . Regardless, I still spent $130 on the thing including the accessories and shipping. Also, I think there needs to be more documentation on how to mod these things even though its highly unadvised to purchase one lol. Also I'm just a stubborn SOB, so I want to try my best to crack this nut.
So yes, I had tried the standard adb commands. But I had not tried the specific version of Platform Tools you recommended until now. Here is some feedback on your reply.
Spoiler: Feedback and More info:
So I went and grabbed those Platform Tools to begin with then I launched Powershell from the Platform Tools directory. I first ran the "devices commands to see if I was able to fetch a device using "fastboot devices". Unfortunately I am still facing an issue with this device being assigned the wrong drivers. More on that below this image:
Then I ran the other suggested commands you provided:
Research indicates that the "< waiting for any device >" pause (even when device is connected) is a symptom of incorrect driver installations for the device in question. Specifically the "Android Bootloader Interface" model within the "android_winusb.inf" driver options.
Something odd about the device is that it is very determined to remain a "Portable Device"classification and even when I begin appending permissions from TrustedInstaller and deleting the non-windows drivers it remains in this classification. I have also tried uninstalling it from device manager, and from the printers and devices menu with no success of reassigning it as of yet.
Here are the specific drivers that are assigned to it currently:
As you will be reading this I am working to resolve this issue first. Until advised otherwise.
Updates on this process:
Driver Signature Enforcement has been disabled, pc rebooted with no effect for assigning "android_winusb.inf" adb drivers
Thank you for your time and consideration!
TheFuzzyFuzz said:
It is truly the CHEAPEST of the Chinese knockoffs . Regardless, I still spent $130 on the thing including the accessories and shipping. Also, I think there needs to be more documentation on how to mod these things even though its highly unadvised to purchase one lol. Also I'm just a stubborn SOB, so I want to try my best to crack this nut.
So yes, I had tried the standard adb commands. But I had not tried the specific version of Platform Tools you recommended until now. Here is some feedback on your reply.
Spoiler: Feedback and More info:
So I went and grabbed those Platform Tools to begin with then I launched Powershell from the Platform Tools directory. I first ran the "devices commands to see if I was able to fetch a device using "fastboot devices". Unfortunately I am still facing an issue with this device being assigned the wrong drivers. More on that below this image:
View attachment 5894161
Then I ran the other suggested commands you provided:
View attachment 5894163
Research indicates that the "< waiting for any device >" pause (even when device is connected) is a symptom of incorrect driver installations for the device in question. Specifically the "Android Bootloader Interface" model within the "android_winusb.inf" driver options.
Something odd about the device is that it is very determined to remain a "Portable Device"classification and even when I begin appending permissions from TrustedInstaller and deleting the non-windows drivers it remains in this classification. I have also tried uninstalling it from device manager, and from the printers and devices menu with no success of reassigning it as of yet.
View attachment 5894175
Here are the specific drivers that are assigned to it currently:
View attachment 5894179
As you will be reading this I am working to resolve this issue first. Until advised otherwise.
Updates on this process:
Driver Signature Enforcement has been disabled, pc rebooted with no effect for assigning "android_winusb.inf" adb drivers
Thank you for your time and consideration!
Click to expand...
Click to collapse
Yeah looks like you'd have to install the correct driver. ADB drivers are usually generic, fastboot drivers are device specific.
When you commanded the device to reboot to bootloader, what was on the device screen?
V0latyle said:
Yeah looks like you'd have to install the correct driver. ADB drivers are usually generic, fastboot drivers are device specific.
When you commanded the device to reboot to bootloader, what was on the device screen?
Click to expand...
Click to collapse
I get the standard boot screen, It stops on this screen and then does nothing. Also something else kind of weird is that it will refuse to boot back up if it is NOT plugged in to my computer. And even WEIRDER is that i have only been able to charge/data transfer with the factory cord it came with. Which is, concerning to say the least, and kind of perplexing:
Also, I think I just found the solution to the driver issue. I just need to figure out how to use this tool I found:
Device manager for Windows 10 / 8 / 7 / Vista / XP
DevManView is an alternative to the standard Device Manager of Windows, which displays all devices and their properties in flat table, instead of tree viewer.
www.nirsoft.net
It was recommended by this reference article:
Device Manager Alternative: 3 Picks You Didn't Know About
Looking for a device manager alternative? If so, explore our top three choices so you can have more variety next time you experience issues.
windowsreport.com