Database Info

Is it possible to unlock bootloader by using an app on the device? + few other [Q]

Hello, i am still preparing my device for Lolly-pop flashing, and i am reading instructions everywhere on the web. I have a couple of questions i wanted to ask before i proceed doing anything else.
First one, one of the hardest things to do is unlocking the boot-loader i think. There are many different ways to do that, and everyone looks very complicated, so i have no idea how should i do that. Longest instructions are usually the safest but have the biggest chance of messing things up.
Anyhow, due to my device being rooted, i looked in Play Store for other options and found this app https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Can i just use that to unlock my bootloader? And as far as i understand, it will wipe my data as soon as i do that right?
Second one, how do i make sure my USB drivers are working correctly? When i put my phone in bootloader mode and plug it in my Windows 7 laptop, it detects the device as some Bootloader device (cant remember exact name). So is that meant to be like that?
Third one, are there any other easy methods for simply unlocking and locking the bootloader that doenst need some SDK downloading?I have an old android app dev sdk in my pc, can i use that? Can that be done only using the .zip image provided by google?
And just to confirm, are these instructions i have made for myself , are they correct? Will that work?
1) Unlock bootloader using the rooted app from play store.
2)Download and extract the .zip file to a folder on my pc desktop.
3)Put the phone in the bootloader mode, vol-up+vol-down+pwr.
4)plug it in my pc
5)run the flash-all script from the folder on desktop
6)not sure what is supposed to happen now, but i assume the device is going to power on?
7)when the device starts, turn it off, go in bootloader mode, then in recovery and wipe data/factory and cache.
8)somehow lock the bootloader, i do not yet know how will i do this, any tips?
Also there are videos on youtube but most of them are <1 year old, using old instructions i think.

1) yes that app will unlock the bootloader. It needs root though. It does not wipe data. Only fastboot unlock method wipes data for security.
2) click the guides link in my signature. Read then "adb and fastboot. What is it?" Thread. This will tell you how to configure everything properly.
3) use the app in 1 of fastboot. See above, SDK not required.
4) unless you're rooted step 1 will be done with fastboot.
All the guides and info threads you'd ever need are in my signature

rootSU said:
1) yes that app will unlock the bootloader. It needs root though. It does not wipe data. Only fastboot unlock method wipes data for security.
2) click the guides link in my signature. Read then "adb and fastboot. What is it?" Thread. This will tell you how to configure everything properly.
3) use the app in 1 of fastboot. See above, SDK not required.
4) unless you're rooted step 1 will be done with fastboot.
All the guides and info threads you'd ever need are in my signature
Click to expand...
Click to collapse
Ok so i can unlock the bootloader with that app. But i will not be able to lock it again, because i will lose root access after the flashing right?
I tried searching the thread you mentioned, but i cant find it. I tried using both search engines, in google and in forum. And i dont think there is link to the thread in your signature. Could you send me a link please?
I do not understand the 3) 4) . To which question are you replying?
Sorry for the massive confusion
EDIT: I just found the thread, looks like a lot of useful information!

nikssims said:
Ok so i can unlock the bootloader with that app. But i will not be able to lock it again, because i will lose root access after the flashing right?
I tried searching the thread you mentioned, but i cant find it. I tried using both search engines, in google and in forum. And i dont think there is link to the thread in your signature. Could you send me a link please?
I do not understand the 3) 4) . To which question are you replying?
Sorry for the massive confusion
EDIT: I just found the thread, looks like a lot of useful information!
Click to expand...
Click to collapse
Are you rooted now? Do you have a custom recovery?

rootSU said:
Are you rooted now? Do you have a custom recovery?
Click to expand...
Click to collapse
I am rooted but i do not have custom recovery
Edit: Plus also while going through those instructions i downloaded an app on my pc that installed usb drivers, adb, and fastboot. http://forum.xda-developers.com/showthread.php?t=2588979
As far as i understand, i have no need to download the huge SDK thing.
Edit 2: I tried running the adb and fastboot without having anything plugged in my pc, and it opened a cmd and some lines appeared and it shut it self off. Is something messed up? I have a very old android app dev sdk in my pc somewhere, could that be conflicting in some way?

nikssims said:
I am rooted but i do not have custom recovery
Edit: Plus also while going through those instructions i downloaded an app on my pc that installed usb drivers, adb, and fastboot. http://forum.xda-developers.com/showthread.php?t=2588979
As far as i understand, i have no need to download the huge SDK thing.
Edit 2: I tried running the adb and fastboot without having anything plugged in my pc, and it opened a cmd and some lines appeared and it shut it self off. Is something messed up? I have a very old android app dev sdk in my pc somewhere, could that be conflicting in some way?
Click to expand...
Click to collapse
How did you "run" adb and fastboot?

rootSU said:
Are you rooted now? Do you have a custom recovery?
Click to expand...
Click to collapse
bump

nikssims said:
bump
Click to expand...
Click to collapse
Rather than bumping (which is againt the rules within 24 hours btw), why not simply answer my previous question?

rootSU said:
Rather than bumping (which is againt the rules within 24 hours btw), why not simply answer my previous question?
Click to expand...
Click to collapse
Oh sorry, i posted the bump at the same time as you did reply me. Sorry
rootSU said:
How did you "run" adb and fastboot?
Click to expand...
Click to collapse
I simply clicked on the .exe files just to see what happens. It might be meant to work like that, i don't know. I just didn't want to risk plugging in my phone just to test adb and fastboot things.
Also couple of questions about this
Code:
Method 1. Easy method.
★Power off your phone.
★Boot it in fastboot by pressing and holding Power Button + Volume Down at the same time.
★Connect your phone to your PC through your USB cable.
★Execute the flash-all.bat script (for Windows) or flash-all.sh(for MAC and LINUX) in the folder where you extracted the factory images.
**!!** For MAC: You'll have to edit the flash-all.sh, and add "./" before every fastboot command.
★Wait for everything to flash.
★After everything finished, select "Recovery" using the volume buttons.
★When a small dead Android appears, press Power Button + Volume UP.
★Select "Wipe data/factory data reset"
★Reboot. Your phone should be stock.
So, when L comes out, i simply extract it on my desktop, and run the flash-all.bat thing, while having my nexus connected to pc while in the "fastboot" mode?
Also, do i need to wipe only the data/factory or do i need to wipe the cache too?
And will the flash-all.bat lock my bootloader? Or is that even needed?
Edit: Reading other threads all around the internet gives so many different kinds of answers, that i do not understand what should i do. One site says that bootloader can be left unlocked, other says that it must be locked. Then there are thousands of different ways to lock it, and each one looks complicated.

nikssims said:
Oh sorry, i posted the bump at the same time as you did reply me. Sorry
I simply clicked on the .exe files just to see what happens. It might be meant to work like that, i don't know. I just didn't want to risk plugging in my phone just to test adb and fastboot things.
Click to expand...
Click to collapse
You should read my "adb and fastboot. What is it?" thread. That is not how you use adb or fastboot.
nikssims said:
So, when L comes out, i simply extract it on my desktop, and run the flash-all.bat thing, while having my nexus connected to pc while in the "fastboot" mode?
Click to expand...
Click to collapse
Correct. Or you can just fastboot flash the system and boot.img manually (again, see my thread)
nikssims said:
Also, do i need to wipe only the data/factory or do i need to wipe the cache too?
Click to expand...
Click to collapse
If you use the flash-all.bat, it will overwrite your data with a blank userdata.img
nikssims said:
and will the flash-all.bat lock my bootloader? Or is that even needed?
Click to expand...
Click to collapse
No.... And yes if you're not going to have a custom recovery on there, locking your bootloader secures the device - providing you have a Pattern or PIN lock.
nikssims said:
Reading other threads all around the internet gives so many different kinds of answers, that i do not understand what should i do. One site says that bootloader can be left unlocked, other says that it must be locked. Then there are thousands of different ways to lock it, and each one looks complicated.
Click to expand...
Click to collapse
If you're going to be rooted, you can simply lock it with the app you mentioned in your first post. Or using fastboot. Try to avoid threads all over the internet. Everything you need is here on XDA.

Ok, that seems to be it for now. Now i will wait for the release of android L image, which seems to have been delayed untill 12 nov.
Thank you for your support!

Unlocking the bootloader is VERY easy. All you must do is have either the entire have android SDK installed, or you just need the platform tools(adb and fastboot). Once you have those, you either navigate to the folder where adb/fastboot is -or- add them to your path variable. Reboot your device into bootloader/fastboot mode, by turning phone off. Hold volume down/power at the same time, and your phone will now be in fastboot mode. Open command prompt and type in "fastboot oem unlock" (without the quotes). Thats it. Your device will ask you to confirm that you want to do this. Select yes. Use volume up/down to navigate through any prompts. Be aware, though, that this will perform a factory reset on device, which means it deletes personal files/apps. No big deal. You basically cannot brick a nexus device. If you need help, PM me.

bynarie said:
Unlocking the bootloader is VERY easy. All you must do is have either the entire have android SDK installed, or you just need the platform tools(adb and fastboot). Once you have those, you either navigate to the folder where adb/fastboot is -or- add them to your path variable. Reboot your device into bootloader/fastboot mode, by turning phone off. Hold volume down/power at the same time, and your phone will now be in fastboot mode. Open command prompt and type in "fastboot oem unlock" (without the quotes). Thats it. Your device will ask you to confirm that you want to do this. Select yes. Use volume up/down to navigate through any prompts. Be aware, though, that this will perform a factory reset on device, which means it deletes personal files/apps. No big deal. You basically cannot brick a nexus device. If you need help, PM me.
Click to expand...
Click to collapse
So if i place the fastboot.exe on my desktop, and then open the command prompt and type "cd desktop", and then "fastboot oem unlock". That should unlock my fastboot right? I just tried doing that without having any devices plugged in and it gave me a text <waiting for devices> in cmd.
I do not understand the part that you mean by navigating to the folder, you mean i have to navigate to the folder where i have fastboot.exe right?
If all that is correct, after i do all the flashing i have to do the same thing i did now, just use command "fastboot oem lock"?

nikssims said:
So if i place the fastboot.exe on my desktop, and then open the command prompt and type "cd desktop", and then "fastboot oem unlock". That should unlock my fastboot right? I just tried doing that without having any devices plugged in and it gave me a text <waiting for devices> in cmd.
I do not understand the part that you mean by navigating to the folder, you mean i have to navigate to the folder where i have fastboot.exe right?
If all that is correct, after i do all the flashing i have to do the same thing i did now, just use command "fastboot oem lock"?
Click to expand...
Click to collapse
I would suggest wherever you have fastboot AND adb located, put the folder in your path variable so you dont have to worry about it and you just open cmd and type fastboot or adb.. And you do not need to lock the bootloader back unless a) your taking device in for warranty repair or b) selling device. If you plan on keeping the device, just leave bootloader unlocked. That way you can play around with roms, recoveries and whatever else. Oh, and you need to have both fastboot.exe and adb.exe. First of all if your using fastboot when your device is loaded into android it doesnt work. It has to be in FASTBOOT MODE. Which means turning off device. Hold power + vol down. Then it will look like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then you can run "fastboot oem unlock" or "fastboot oem lock", or any other fastboot command. This is how we flash a custom recovery, which i definitely recommend. Here is a link to download TWRP recovery http://techerrata.com/browse/twrp2/hammerhead. Download the latest version(2.8.1.0), rename it to twrp.img and open cmd prompt and run fastboot flash recovery twrp.img - this will give you your recovery program. Then use vol up/down to navigate to recovery.

bynarie said:
I would suggest wherever you have fastboot AND adb located, put the folder in your path variable so you dont have to worry about it and you just open cmd and type fastboot or adb.. And you do not need to lock the bootloader back unless a) your taking device in for warranty repair or b) selling device. If you plan on keeping the device, just leave bootloader unlocked. That way you can play around with roms, recoveries and whatever else. Oh, and you need to have both fastboot.exe and adb.exe. First of all if your using fastboot when your device is loaded into android it doesnt work. It has to be in FASTBOOT MODE. Which means turning off device. Hold power + vol down. Then it will look like this
IMAGE
Then you can run "fastboot oem unlock" or "fastboot oem lock", or any other fastboot command. This is how we flash a custom recovery, which i definitely recommend. Here is a link to download TWRP recovery http://techerrata.com/browse/twrp2/hammerhead. Download the latest version(2.8.1.0), rename it to twrp.img and open cmd prompt and run fastboot flash recovery twrp.img - this will give you your recovery program. Then use vol up/down to navigate to recovery.
Click to expand...
Click to collapse
Thank you, that is a lot of useful information! I don't think i will install custom recovery though, because i simply want to update my device to Android L and keep it unrooted. Just completely stock android L. The reason i am doing it this way is because i messed my device up a bit using the towelroot and softkeyz app, and i doubt i will get android L over OTA.

nikssims said:
So if i place the fastboot.exe on my desktop, and then open the command prompt and type "cd desktop", and then "fastboot oem unlock". That should unlock my fastboot right? I just tried doing that without having any devices plugged in and it gave me a text <waiting for devices> in cmd.
I do not understand the part that you mean by navigating to the folder, you mean i have to navigate to the folder where i have fastboot.exe right?
If all that is correct, after i do all the flashing i have to do the same thing i did now, just use command "fastboot oem lock"?
Click to expand...
Click to collapse
This was all covered in my adb and fastboot thread. If you follow what I wrote there, there is no need to put things in the same folders or cd etc.

nikssims said:
Thank you, that is a lot of useful information! I don't think i will install custom recovery though, because i simply want to update my device to Android L and keep it unrooted. Just completely stock android L. The reason i am doing it this way is because i messed my device up a bit using the towelroot and softkeyz app, and i doubt i will get android L over OTA.
Click to expand...
Click to collapse
No problem! You are free to do as you want. Remember, people here at XDA are here to help you. Do not think you're asking a dumb or repeat question. If you need to know, ask. If you need any more help I will do my best. I would suggest a custom recovery though because it makes re freshing system and other things really simple. It gives you lower level access to the system than a apk app would. But, do as you wish. You will learn more as you go. I started out as a total n00b, just like everyone does. Eventually I messed my stuff up so bad i HAD to fix it LoL! Hang around IRC #xda-devs and the xda site if youd like to learn more. I think XDA is the most valuable resource ive ever seen for ANY community. I love it here. Anyway, have a nice day!

rootSU said:
This was all covered in my adb and fastboot thread. If you follow what I wrote there, there is no need to put things in the same folders or cd etc.
Click to expand...
Click to collapse
Ah yes indeed, i simply open the cmd and i can type commands instantly there without having to do that "cd" navigation part. That is great thanks!

bynarie said:
No problem! You are free to do as you want. Remember, people here at XDA are here to help you. Do not think you're asking a dumb or repeat question. If you need to know, ask. If you need any more help I will do my best. I would suggest a custom recovery though because it makes re freshing system and other things really simple. It gives you lower level access to the system than a apk app would. But, do as you wish. You will learn more as you go. I started out as a total n00b, just like everyone does. Eventually I messed my stuff up so bad i HAD to fix it LoL! Hang around IRC #xda-devs and the xda site if youd like to learn more. I think XDA is the most valuable resource ive ever seen for ANY community. I love it here. Anyway, have a nice day!
Click to expand...
Click to collapse
Thank you for you help!

One more thing. If you are ever interested in flashing a recovery, check out my GUI tool that does this for you. Just clicking buttons and selecting correct file. http://forum.xda-developers.com/general/general/project-droidtool-fastboot-adb-utility-t2928176

Sharp Aquos S2 (SS2) and (SAT) dev thread

Authors don't take any responsibility's for any damage to your device of for loosing of guarantee.
Please link all information from this thread when you post outside of XDA.
DO NOT UPGRADE VIA OTA TO ANDROID OREO (8) (firmware 2000+) OTHERVISE YOU WILL BE NOT ABLE TO FLASH THOSE ROMS, UNLOCK OR TO DO ANYTHING NON OFFICIAL, UNLESS YOUR BOOTLOADER IS UNLOCKED
Models description:
SS2- 4gb/64gb
SAT -6gb/128 gb
DONT MESS!
Dedicated to XDA users!
Drivers and OST portable (don't use other versions of OST) press launcher.exe to install
Official S2 oreo updates:
Before you go
If you are on Android 7 after update to Android 8, you will be not able to unlock bootloader for free!
Firmwares for Service downloader:
Oreo SAT (CN) SAT-2140-0-00CN-B01
Oreo SS2 (CN) SS2-2140-0-00CN-B01
Oreo SS2/C10 (EU) SS2-2140-0-00E0-B02
Can be downloaded here: https://fih-firmware.hikaricalyx.com/sharp_en.html
To be flashed via this cracked OST 6.2.8 (note that you have to unlock bootloader and bootloader critical to be able to flash): here
Instruction: SAT owners - how to go back to stock Oreo 8.0 by @paulzie
SAT - full 2080WW http://dl.sharpmobile.com.tw/update/S2/SAT-2080-0-00WW-B02-update.zip
SAT -update from 135F to 2080WW http://dl.sharpmobile.com.tw/update/S2/SAT-2080-0-00WW-B02-135F-0-00WW-B01-update.zip
SS2-update from 135F to 2080WW http://dl.sharpmobile.com.tw/update/S2/SS2-2080-0-00WW-B02-135F-0-00WW-B01-update.zip
SS2- full 135FWW update http://dl.sharpmobile.com.tw/update/S2/SS2-135F-0-00WW-B01-update.zip
Click to expand...
Click to collapse
Guys I don't support official updates!!!!
Instruction how to get back from offical SAT/SS2 oreo WITH UNLOCKED BOOTLOADER:
-Download twrp from here https://forum.xda-developers.com/showpost.php?p=76412381&postcount=288
-Flash twrp from fastboot: "fastboot flash boot filename.img"
-Get Bootloader_oldservice.zip for you model from here https://forum.xda-developers.com/showpost.php?p=76412178&postcount=287
-flash zip from TWRP.
-now you are able to flash OST ROMS after reboot.
Click to expand...
Click to collapse
CUSTOM ROMS:
@S2/S3 Trebled 5.3 (Android 10)
@SS2(only unlocked) LINEAGE PROJECT
@SS2(only unlocked) Trebled v3.3
@SS2(only unlocked) AICP ROM
HOT! @ SS2/SAT (need unlocked)v3 Unified treble ROM project based on SIUI from Sharp S3 Oreo
Updates to Unified treble ROM project
@ SS2 (need unlocked) First custom ROM based om 135E_WW flashing via OST (only SS2(4gb/64gb))
Click to expand...
Click to collapse
FOR SAT AND SS2- OFFICIAL BASED ROMS (FOR OST) (for unbricking and downgrading. incl 9008 mode) :
@ SS2 135E_WW ROM flashing "from box" and unbricking via OST
@ SAT 127E_CN ROM flashing "from box" and unbricking via OST
Click to expand...
Click to collapse
RECOVERY:
There is no universal recovery, cos each version of rom include different kernel builds, if we use one twrp version (with for example version of 135E), wifi will work only in 135E and F versions.
So better wait for Oreo updates custom rom finals that will use same kernel and vendor versions.
Click to expand...
Click to collapse
BOOTLOADER UNLOCK:
@C10 Bootloader unlock guide
@SS2/SAT Bootloader unlock (if you have unlockcode.bin)
1. Get installed ADB/Fastboot driversand cmd - you can use OST portable (above)
2. Enable Developer optionsin android and usb debugging. Reset phone to fastboot (downloadmode) by "adb reboot bootloader" or by buttons combination..whatever.
3. Cpy unlockkey.bin to fastboot folder and type" fastboot flash unlock unlockkey.bin". You should have response "OK".
4. use fastboot-android.exe from SUT (OST portable folder). Type command " fastboot-android flashing unlock_critical". If its ok - phone screen should give a message about Bootloader unlock.
5. Enter fastboot again (download mode) and type" fastboot flash unlock unlockkey.bin". You should have response "OK".
6. Type command " fastboot oem unlock-go". If its ok - phone screen should give a message about Bootloader unlock.
7. Now you can use my OST nb0 roms to flash via SUT.
@SS2/SAT Bootloader unlock (for Android 7.1)
Download and extract attached zip (SS2- Sharp_ss2_boot_unlock_files.zip, SAT -Sharp_sat_boot_unlock_files.zip) . Manage to run windows cmd. Adb and fastboot drivers installed as mandatory,
1. Enter fastboot mode: connect usb, power off prone or restart same time pressing VOLUP + POWER, on Logo release power button. You have to see "Download mode" on screen (same thing you can do it from android with adb command: "adb reboot bootloader")
2. First of all check if you have tryes left in device-type:
"fastboot.exe oem cert_timecount get"
When is 0 you will be not able to unlock (unless you make changes) so STOP HERE! and visit here
if >0 then go to step 2.
2. Enter cmd in console: "fastboot getvar productid" -> you will get 16 digits serial number
3. Convert serial number to md5 hash ( you can to here https://www.md5hashgenerator.com/)
4. Enter cmd in console: "fastboot oem dm-verity [md5 hash generated from serial number (without quotes)]-> you should see "OK" response if you done it ok.
5. Flash this bootloader. Enter cmd in console: "fastboot flash abl unlock.elf"
6. Reboot to download mode again - enter cmd: "fastboot reboot-bootloader"
7. After reboot, enter in cmd:"fastboot oem unlock" - Get screen with unlocking!
8. Get unlock to flash critical (bootloader) partitions: "fastboot oem unlock_critical" - now you can use fastboot flash abl (or xbl) files.
Note: after accepting unlock popup on screen all data on phone will be erased!!!
When you have unlocked device repeat step 2 with commands
"fastboot.exe oem cert_timecount set 100"
I recommend to type above command each time you use fastboot, because each command used in fastboot makes this value less than before, and if it reaches 0, you will be not able to do anithing with most oem commands
You can relock bootloader anytime by cmd: fastboot oem lock
Happy rooting!
@ Backup and restore phone partitions via Dl Mode 9008 (model SS2)
@SS2 Root
BEFORE YOU GO UNLOCK BOOTLOADER!!!
Via Magisk manager https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Patched Magisk Boot.img from 135E https://drive.google.com/open?id=1m65Hq4BXlFTfzsr6wzf3zoZsIKGuK_PK
Patched Magisk Boot.img from 135F https://drive.google.com/file/d/1Ob5xVB8CNyv9k8mqgn49cqOjk1M37HJZ/view?usp=sharing
Instructions:
1) Flash patched boot: fastboot flash boot nameofpatchedbootfile.img
2) After reboot install Magisk Manager.apk
@Unbrick (alternative methode) (only model SS2(4gb/64gb)):
QPST backup I made from ss2 135C rom. https://drive.google.com/file/d/1q9elokuWhj_hKPNYi0LguJhCzZWHc-Md/view
NOT NEEDED. FLASH ANY OST ROM FOR UNBRICK.
Backup is for 4gb/64 model not for 6gb/128gb
@SS2/SAT Enter manually HS-USB 9008 mode on Sharp (Not working on Oreo!!): NOT NEEDED. FOLLOW UNCLOCK BOOTLOADER AND TYPE: fastboot oem reboot-edl WITH SERVICE BOOTLOADER FLASHED
You have to own DLOAD usb cable (with button) or make yourself one, where green+black wire can be cut together.
Methode 1
1. Enable Developer settings in Android and USB debugging
2. Connect usb mod cable (don't cut wires together yet).
3. On pc in adb type: "adb reboot edl"
4. SAME TIME when you pressed enter after above command, cut green+black wires on USB.
5. Release wire, if you have done it on time, you will get HS-USB Diagnostics 9008 device in Device Manager.
Methode2
1. Open phone cover
2. Disconnect battery
3. use usb cable and cut green+black together
4. Connect battery
5. Release wires, you will get HS-USB Diagnostics 9008 device in Device Manager
Methode3 (if you have unlocked loader) SS2
fastboot oem reboot-edl
@fastboot OEM commands:
Many thx to^
@Argoin for SAT service files and possibility of unlock. He bought it, so if you mind to thank him PM for his paypal.
@hikari_calyx for SS2 service files and also for bootloader unlock developing for FIH mobile devices .
@lolyinseo for rooting and working on project
@Шпунтик for bootloader unlock
All users helping and working on project

sharp aquos s2
una domanda cambia qualcosa con questa rom???

giuseppe1976milo said:
una domanda cambia qualcosa con questa rom???
Click to expand...
Click to collapse
questa è la Rom di unbricking

English please guys !
Use the online translator if you have difficulties with English
Forum Rules
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).
Click to expand...
Click to collapse
now please edit your posts and add the English translation

Yep, we have a 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"
}

lolyinseo said:
Yep, we have a root
Click to expand...
Click to collapse
Manual of root, please.

Seavovk said:
Manual of root, please.
Click to expand...
Click to collapse
Stop pushing. Be patient.
Before, bootloader needs to be unlocked. I dont have device now, but another guy will write an automated script for this procedure.
As soon is done, there will be manual for unlocking, then comes rooting.

It's so wonderful to see root on sharp s2!
That would make this phone more powerful!!

This is great! Any chance we will be able to unlock the 6/128GB (SAT) version, too?

meissner.t said:
This is great! Any chance we will be able to unlock the 6/128GB (SAT) version, too?
Click to expand...
Click to collapse
probably no!
There is need loader for this version of phone, very small chance 0,01 % we find it.
But unbricking from 9008 is possible! (not with attached files) have to do.

tks boss, I waiting a detailed guide for root

nvhung.ps said:
tks boss, I waiting a detailed guide for root
Click to expand...
Click to collapse
Use guide from Magisk, its working.
I have added 135E boot patched by magisk.
I don't have even time to power on sharp

I think I also need to buy an Aquos S2 (Codename SS2) to investigate further

hikari_calyx said:
I think I also need to buy an Aquos S2 (Codename SS2) to investigate further
Click to expand...
Click to collapse
There is S3 coming, with same hardware but new design and fingerprint on back cover.
Old s2 programmer will be usable

heineken78 said:
S3 is coming, with the same hardware, but with the new design and a fingerprint on the back cover.
Old S2 programmer will be usable
Click to expand...
Click to collapse
We are waiting for new events!

heineken78 said:
Bootloader unlock Sharp Aquos s2 (only model SS2(4gb/64gb))
Download and extract attached zip. Manage to run windows cmd. Adb and fastboot drivers installed as mandatory,
1. Enter fastboot mode: connect usb, power off prone or restart same time pressing VOLUP + POWER, on Logo release power button. You have to see "Download mode" on screen (same thing you can do it from android with adb command: "adb reboot bootloader")
2. Enter cmd in console: "fastboot getvar productid" -> you will get 16 digits serial number
3. Convert serial number to md5 hash ( you can to here https://www.md5hashgenerator.com/)
4. Enter cmd in console: "fastboot oem dm-verity [md5 hash generated from serial number (without quotes)]-> you should see "OK" response if you done it ok.
5. Flash this bootloader. Enter cmd in console: "fastboot flash abl unlock.elf"
6. Reboot to download mode again - enter cmd: "fastboot reboot-bootloader"
7. After reboot, enter in cmd:"fastboot oem unlock" - Get screen with unlocking!
Note: after accepting unlock popup on screen all data on phone will be erased!!!
You can relock bootloader anytime by cmd: fastboot oem lock
Happy rooting!
Upd Root Sharp Aquos s2 (only model SS2(4gb/64gb))
BEFORE YOU GO UNLOCK BOOTLOADER FIRST!!!
Via Magisk manager https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Boot.img from 135C https://drive.google.com/open?id=1NyOvOGDn8R-Db2_b_PTJtu7XYWbJScGm
Patched Magisk boot 135E -ready for Magisk https://drive.google.com/open?id=1m65Hq4BXlFTfzsr6wzf3zoZsIKGuK_PK
Unbrick Sharp Aquos s2 (only model SS2(4gb/64gb)) in 9008 mode:
QPST backup I made from ss2 135C rom. https://drive.google.com/file/d/1q9elokuWhj_hKPNYi0LguJhCzZWHc-Md/view
Backup is for 4gb/64 model not for 6gb/128gb
Enter manually HS-USB 9008 mode on Sharp (SS2/SAT):
You have to own DLOAD usb cable (with button) or make yourself one, where green+black wire can be cut together.
I use this cable
Methode 1
1. Enable Developer settings in Android and USB debugging
2. Connect usb mod cable (don't cut wires together yet).
3. On pc in adb type: "adb reboot edl"
4. SAME TIME when you pressed enter after above command, cut green+black wires on USB.
5. Release wire, if you have done it on time, you will get HS-USB Diagnostics 9008 device in Device Manager.
Methode2
1. Open phone cover
2. Disconnect battery
3. use usb cable and cut green+black together
4. Connect battery
5. Release wires, you will get HS-USB Diagnostics 9008 device in Device Manager
Methode3 (if you have unlocked loader)
fastboot oem reboot-edl
Many thx to @hikari_calyx for useful files for community.
Click to expand...
Click to collapse
hi friend please show me how to inter HS-USB Diagnostics 9008 mode. I already do Method 1 but not work. I don't understand step 4.

Wow! It's really a great news for my Sharp S2, I'll try to root it some time later. Thanks you so much @heineken78 !!
BTW, where did you buy this phone? I think it only sold in Mainland of China and Taiwan, am I right?

Good Job! That's really good news,thanks a lot!:good:

pcgg said:
BTW, where did you buy this phone? I think it only sold in Mainland of China and Taiwan, am I right?
Click to expand...
Click to collapse
jd.ru 156$ with delivery to Russia
jd.com

snart said:
jd.ru 156$ with delivery to Russia
jd.com
Click to expand...
Click to collapse
Cool!! I never know JD can do that... $156 includes the freight? That's even cheaper than here!

Verizon LG G710VM Qfil Bootloader unlock, Root and Relock Bootloader

This May Work With Other Devices As Well.
Prerequisites:
Starting from Bootloader Locked Stock Verizon.
CrossFlash to G710ULM11g.kdz: LG G710U | LG G7 ThinQ | Version: G710ULM11g_01_NAO_US_OP_1112 | Firmware for Region: BPT from UNITED STATES - Lg-firmwares.com (lg-firmwares.com)
Fastboot works on the G710ULM11g.kdz no need to erase laf.imgs.
See the 2 links below for crossflashing threads.
(There are 2 ways to crossflash).
1. Use LGUP, Partition DL and Refurbish is you want the kdz on both a and b slots: https://mega.nz/#!kCpHBaia!xZmico6MYL1T07ffuc8z6cCbs5oU4pKEz5VG-AwfvV0
2. Power Shell Command line Crossflashing thread: https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
Files required to unlock bootloader while crossflashed to the ULM11g.kdz V35eng file and firehose file for Qfil. https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
Zip contains Stock G710VM21b stock boot_a and boot_b img and Magisk patched boot_a and boot_b imgs. https://www.androidfilehost.com/?w=files&flid=322268
Latest Verizon kdz LG G710VM | LG G7 ThinQ | Version: G710VM21b_04_0812 | Firmware for Region: VRZ from UNITED STATES - Lg-firmwares.com (lg-firmwares.com)
NOTE: Some links are from other helpful threads so thank whoever wrote them.
To successfully unlock the bootloader while on the crossflashed 11g,
Setup Device then go into Developer options and Enable the OEM Unlock toggle and enable usb debugging in the phone.
Now Let's Begin:
1. Switching the phone to EDL modeopen device manager):
Turn off the phone, then hold the vol- and power buttons together and repeatedly press the vol+ button until you see device in device manager as "Qualcomm HS-USB QDLoader 9008". then release buttons. If you don't succeed at first keep trying.
2. Using QFIL:
Install the QPST package, launch Qfil, in the program window select:
(1) Select port to which the device is connected
(2) Storage type UFS
(3) select build type: Flat
(4) Select programmer: prog_ufs_firehose_Sdm845_lge.elf
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Load v35eng.img to abl_a partition:
in the upper left menu, select Tools, then partition manager , look for abl_a in the window that opens , Right click abl_a, select manage partition data, then use the V35eng.img overwrite the abl_a with load image.
4. Reboot into Fastboot to Unlock the bootloader:
Leave EDL mode by holding the volume down and power for about 10 seconds. Phone will restart. Turn off phone disconnect usb and hold vol- and plug in usb. (phone should boot into fastboot like the picture).
Now we need platform tools unpacked to any folder convenient for you, launch the shell by pressing the shift + right mouse button and choosing to open the power shell window here .
Use the command : "fastboot oem unlock" without quotes
Use the command: "fastboot reboot" without quotes
That's Everything the bootloader is unlocked.
Crossflash back to Stock G710VM21b.kdz and root or crossflash to android 10 kdz to install custom roms.
To Root stock 21b use EDL mode for Qfil to load the magisk patched 21b boot.imgs to boot_a and boot_b reboot and install magisk.apk then it should update to latest magisk zip.
***NOTE*** ​
Only use this part of the guide if you are relocking bootloader. This locking bootloader procedure may work for other devices use at your own risk.
***Do not uninstall magisk with the magisk uninstall button. Just go into download mode and crossflash to ULM11g. If you use the uninstall button in magisk manager you will brick your device.**
To relock bootloader:
Cross Flash back to ULM11G, setup phone, enable Developer options, enable USB debugging. (Enable OEM unlock) should be greyed out don't worry).
Platform-tools and issue powershell commands:
1. PS C:\Program Files\platform-tools> adb devices
List of devices attached
LMG710ULM******** device
2. PS C:\Program Files\platform-tools> adb reboot bootloader
3. PS C:\Program Files\platform-tools> fastboot oem lock
(bootloader) Erasing userdata and cache OKAY [ 0.492s]
Finished. Total time: 0.592s
4. PS C:\Program Files\platform-tools> fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.004s
To confirm locked bootloader:
Enable developer options again and you will see (Enable OEM Unlock) Unchecked.
***Profit Bootloader is locked***[/QUOTE]

I just cross flashed and rooted the G710ULM20d for my LG710VM Verizon. This method should work on any phone that is cross flashed. I only used Qfil no twrp.

Can someone write this up in a more noob friendly way?

Is 'adb debugging in ULM11g', the same as 'USB debugging' under developer options?
My phone currently has Oreo (8.1) installed and is model no. LMG710ULM
Dishe said:
Can someone write this up in a more noob friendly way?
Click to expand...
Click to collapse
Yeah, totally lost me at
When you hear the disconnect sound, immediately hold volume down (only volume down) to enter fastboot right away (if it don't work just let the phone boot up and go into adb and command prompt and type fastboot reboot bootloader.
2. When you've entered fastboot, execute this command:
Click to expand...
Click to collapse
I guess we're supposed to have ADB cmd window open on the PC, similar to 3:30 of the following video:
/watch?v=wp4Rb0INxvU
OP then mentions the following
Once bootloader is unlocked you can cross flash back to Verizon Pie kdz. Make the backup for whatever slot your using a or b.
Click to expand...
Click to collapse
This doesn't make any sense, since he didn't revert to Oreo, to install the v35eng.img
Edit: It seems he's referring to the original abl_a/abl_b files, this post talks about distinguishing the 2
3. Installed magisk manager and patched boot_a.
Click to expand...
Click to collapse
It seems Magisk apk needs to be executed directly on the phone, then it'll do it's thing from there
/watch?v=m4f21ZCGJuk
Edit: here are my images of the steps to patch boot_a and boot_b
imgur.com/a/E4Abu4t
You must manually navigate to the directory with your LG, press and hold then select 'share' file, so it can appear in Windows explorer; filenames will be the same so you have to do this twice.
File size of each file went from 64 MB to 23.1 MB
After patching boot_a and boot_b with QFIL, the red question mark will change into a green check mark, when you boot up again.
But yeah, none of this makes any sense without some sort of image or video. Thank you for the guide though.
There are 5 main files that should be backed up 'just in case'
i.imgur.com/uqk2Cwb.png
Edit: consider backing up abl_b as well.
The phone's on a GSM network. I as able to uninstall facebook directly from the phone, and then use ADB shell to remove the app manager/system facebook files as well.

paxar331 said:
Is 'adb debugging in ULM11g', the same as 'USB debugging' under developer options?
My phone currently has Oreo (8.1) installed and is model no. LMG710ULM
Click to expand...
Click to collapse
Yes you need it enabled to use adb.

Just to let everyone know, once you upgrade to Pie, QFIL can not be used to place files onto the partition, but to read or erase.

paxar331 said:
Just to let everyone know, once you upgrade to Pie, QFIL can not be used to place files onto the partition, but to read or erase.
Click to expand...
Click to collapse
Sorry to disagree with you but you are incorrect. Qfil can load any file you want as well as restore a backup file. Boot_a, abl_a, laf_a, and so on.

ik this phone is so cool
---------- Post added at 04:57 AM ---------- Previous post was at 04:52 AM ----------
netookska05 said:
Sorry to disagree with you but you are incorrect. Qfil can load any file you want as well as restore a backup file. Boot_a, abl_a, laf_a, and so on.
Click to expand...
Click to collapse

I am so lost on this....
(Don't mean to rude as I understand a lot of work put into the community is voluntary and kindness, but I got to this thread from a comment on the previous one and still not understanding).

Unlocking the Verizon LG G710VM bootloader with QFIL may work with other devices
edit

nik322 said:
(Don't mean to rude as I understand a lot of work put into the community is voluntary and kindness, but I got to this thread from a comment on the previous one and still not understanding).
Click to expand...
Click to collapse
What's going on?

It doesn't work to lock the bootloader, I get red case

HimikoMw said:
It doesn't work to lock the bootloader, I get red case
Click to expand...
Click to collapse
What version of phone do you have? (Dual SIM what?)
Did you flash the Android 8 ulm11g.kdz and boot into fastboot and enter the fasboot OEM lock command and fastboot reboot?

netookska05 said:
What version of phone do you have? (Dual SIM what?)
Did you flash the Android 8 ulm11g.kdz and boot into fastboot and enter the fasboot OEM lock command and fastboot reboot?
Click to expand...
Click to collapse
It's the G710EM Latin American version, flash the kdz G70ULM11g and reboot to fastboot with the command (adb reboot bootloader), from there once in fastboot mode, execute the command (fastboot oem lock), and then (fastboot reboot), and it showed me red case

HimikoMw said:
It's the G710EM Latin American version, flash the kdz G70ULM11g and reboot to fastboot with the command (adb reboot bootloader), from there once in fastboot mode, execute the command (fastboot oem lock), and then (fastboot reboot), and it showed me red case
Click to expand...
Click to collapse
How did you unlock bootloader?
Was it with the official way generating your unlock key?

netookska05 said:
How did you unlock bootloader?
Was it with the official way generating your unlock key?
Click to expand...
Click to collapse
for that model there is no official unlocking, so I unlocked it by the unlock they published first.
flashing the G71011g and installing the v35 abl(https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-bootloader-unlock-g7-thinq-t-t3963568), that was the method I used that time, it was the only way there was.

HimikoMw said:
for that model there is no official unlocking, so I unlocked it by the unlock they published first.
flashing the G71011g and installing the v35 abl(https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-bootloader-unlock-g7-thinq-t-t3963568), that was the method I used that time, it was the only way there was.
Click to expand...
Click to collapse
Then flashing back to the 11g and enabling debugging should have worked. Once you issued all commands it should have rebooted minus the bootloader unlock screen you get booting up and then went back into phone into developer options and turned off OEM unlock switch.

netookska05 said:
Then flashing back to the 11g and enabling debugging should have worked. Once you issued all commands it should have rebooted minus the bootloader unlock screen you get booting up and then went back into phone into developer options and turned off OEM unlock switch.
Click to expand...
Click to collapse
yes but after executing all the commands, it doesn't start me and only remains in red case.
My theory is that in some G7 when flashing a kdz the safetynet passes both in (ctsProfile, as in basicIntegrity), which allows the bootloader to lock again, in my case when flashing either any KDZ, only passes me (basicIntegryty), which causes the bootloader does not lock properly, and causes the red case, that's what I think, I've tried several ways to lock the bootloader but always leads me to red case.

HimikoMw said:
yes but after executing all the commands, it doesn't start me and only remains in red case.
My theory is that in some G7 when flashing a kdz the safetynet passes both in (ctsProfile, as in basicIntegrity), which allows the bootloader to lock again, in my case when flashing either any KDZ, only passes me (basicIntegryty), which causes the bootloader does not lock properly, and causes the red case, that's what I think, I've tried several ways to lock the bootloader but always leads me to red case.
Click to expand...
Click to collapse
When you crossflaahed to 11g did you use command line or lgup partition do? Are you stuck at the red case now?

netookska05 said:
When you crossflaahed to 11g did you use command line or lgup partition do? Are you stuck at the red case now?
Click to expand...
Click to collapse
Try this guide for your red case problem. https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841

3A Locked Bootloader No OS Installed

Can't OEM Unlock, can't fastboot flashing unlock, can't boot to recovery, can't fastboot flash boot boot.img, can't fastboot flash recovery recovery.img (like twrp) due to bootloader locked
Is there any way to flash this thing and make it work? Otherwise I'm just gonna throw it on ebay dumb cheap

KaptinBoxxi said:
Can't OEM Unlock, can't fastboot flashing unlock, can't boot to recovery, can't fastboot flash boot boot.img, can't fastboot flash recovery recovery.img (like twrp) due to bootloader locked
Is there any way to flash this thing and make it work? Otherwise I'm just gonna throw it on ebay dumb cheap
Click to expand...
Click to collapse
Enable dev options(settings>about phone>build number>tap it 7 times).
Go into settings>system>advanced>dev options>oem unlocking, click the toggle.
While still in dev options scroll down a little and enable usb debugging.
Plug your phone into your pc.
if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
Open up command prompt type into the cmd window
adb reboot bootloader
The phone will reboot into fastboot mode.
Now type into the cmd window
fastboot devices
See if it lists a device, if not you need to install the drivers I linked to. If you had to install the drivers try the fastboot devices command again after installing them, it should list the device now.
type in
fastboot flashing unlock
You will then have to use the phone to select yes to the unlock. you use the volume keys to select and the power button to confirm.

mulperi said:
Enable dev options(settings>about phone>build number>tap it 7 times).
Go into settings>system>advanced>dev options>oem unlocking, click the toggle.
While still in dev options scroll down a little and enable usb debugging.
Plug your phone into your pc.
if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
Open up command prompt type into the cmd window
adb reboot bootloader
The phone will reboot into fastboot mode.
Now type into the cmd window
fastboot devices
See if it lists a device, if not you need to install the drivers I linked to. If you had to install the drivers try the fastboot devices command again after installing them, it should list the device now.
type in
fastboot flashing unlock
You will then have to use the phone to select yes to the unlock. you use the volume keys to select and the power button to confirm.
Click to expand...
Click to collapse
You didn't read my post title or post at all... There's no OS on the device. Its not possible to get into the system to enable OEM unlock. Can't fastboot flashing unlock, doesn't work, can't send via OTA ADB Sideload as it fails around 10%.
Everything you stated above, I tried

How To Guide Lock+Unlock Bootloader - Xiaoxin Pad Pro 2021 [TB-J716F]

How To Lock and Unlock Bootloader - Xioaxin Pad Pro 2021 - TB-J716F
Since I found out that the Tablet supports Project Treble I'm trying to get a GSI-ROM running on it.
Currently with many trial and error I got LiR-ROM to boot.
The first step is to unlock the Bootloader so I thought I will share the process here.
Your data will be deleted while unlocking, try it at your own risk.
Unlock Bootloader manually
Requirement: PC with ADB Fastboot
1. Go to Settings -> System -> About Phone, tab on it until developer settings are enabled.
2. Go to Developer Settings and enable "USB Debugging" and "OEM Unlocking".
3. Open Console and enter "adb devices". Allow USB-Debugging if tablets asks.
4. Enter command "adb reboot bootloader".
5. Write down the serial number shown on the bootloader screen
You can either get the unlock image via this link "http://cdn.zui.lenovomm.com/developer/tabletboot/[your sn number]/sn.img" or via the webseite
5. Go to the ZUI Unlock Website and request the unlock image
{
"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"
}
6. You should get a mail where you can download a file called "sn.img".
7. Flash the image with fastboot "fastboot flash unlock sn.img"
8. Enter command "fastboot oem unlock-go", bootloader will unlock now.
9. Restart with "fastboot reboot".
Done, your bootloader should be unlocked now.
Lock and Unlock Bootloader with Batchscript
I recently found a batch script for lenovo devices in an chinese forum and translated it.
It's easy and convenient to use. For unlocking you still need the sn.img from the ZUI Unlock Website.
Download BatchScript​

Thanks a lot for your contribution! Mine was unlocked when I received it but it's good to see some guides here.

What is the opposite process, to close the bootloader? Does Widevine L1 recover after closing the bootloader? In the case of doing so, can the bootloader be opened again?

@sakun-ice Sorry, I can't tell you that, sind I haven't tried it now. But I think it should be possible.
Currently I'm trying to get a Custom ROM running, if it doesn't work, I will try to install Stock ROM and lock bootloader again. If it happens, I will post it here.

Tropaion said:
@sakun-ice Sorry, I can't tell you that, sind I haven't tried it now. But I think it should be possible.
Currently I'm trying to get a Custom ROM running, if it doesn't work, I will try to install Stock ROM and lock bootloader again. If it happens, I will post it here.
Click to expand...
Click to collapse
Thank you very much, I hope you can install a custom rom and this tablet will not be forgotten, since it is one of the most powerful compact tablets.

@sakun-ice I got LineageOS to run on it today, but it still has 2-3 bugs.

Helloi received one unlocked with a globaoe fw without ota's and i flashed the cn one and took the boot.ipg and patched it with pagisk for root and when flashing it via fastboot the device reboots to fastboot everytipe 1nd had to reflash the fw via edl , i did flashed vbmeta img with the known command o disable verification but no success same thing again. Can anyone plz tell me how to root that crap , it was intended to root use only and took over xiaomi pad pro just because the xiaomi needs 7 days of waiting before unlocking , plz help guys .thx so much i can buy a couple beers for the helper

I'm able to flash back to China stock rom but i can't lock the bootloader.
i have placed the sn.img in both the batchscript folder and platform tools
Tried the batch script :
"
Please select your device status:
1. Fully booted
2. Fastboot mode
Status: 2
Start locking bootloader, don't disconnect device from PC!
FAILED (remote: Command not supported in default implementation)
Finished. Total time: 0.016s
FAILED (remote: Unrecognized command flashing lock)
Finished. Total time: -0.000s
If prompt says "OKAY", locking was successfull.
Use the volume keys to select "LOCK BOOTLOADER", press power key to confirm.
Done!
Press any key to continue . . .
"
Powershell :
"
PS C:\Users\weeteck\Downloads\platform-tools_r31.0.3-windows\platform-tools> ./fastboot flash lock sn.img
Sending 'lock' (5 KB) OKAY [ 0.000s]
Writing 'lock' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
"

@zeroflame15 Did install the driver correctly? For locking you don't need the sn.img, only for unlocking. And did you use the LockBootloader Script?

hmm..i'm not sure if i install the driver correctly. what should be shown in device manager? i did follow PHRS guide and installed the ADB driver but there is this !Android under Other Devices.
Any other driver that i need to install?
And should i be in bootloader mode or fastboot mode to run the command? I run the command at fastboot moder i will get the error above. If i run at bootloader mode will stuckedd at <waiting for device>

@zeroflame15 You have to be in bootloader mode. <waiting for device> is propably the driver.

Tropaion said:
@zeroflame15 You have to be in bootloader mode. <waiting for device> is propably the driver.
Click to expand...
Click to collapse
i have installed all the ADB driver mentioned in this section. Is there a lenovo driver? or any settings within the tablet need to be set to?
thanks for the help

zeroflame15 said:
i have installed all the ADB driver mentioned in this section. Is there a lenovo driver? or any settings within the tablet need to be set to?
thanks for the help
Click to expand...
Click to collapse
Try to connecting in another usb port with other usb cable.

zeroflame15 said:
i have installed all the ADB driver mentioned in this section. Is there a lenovo driver? or any settings within the tablet need to be set to?
thanks for the help
Click to expand...
Click to collapse
Check out this post:
Post in thread '[Solved] Re-locking bootloader - no fastboot commands working' https://forum.xda-developers.com/t/...stboot-commands-working.4330019/post-85755663
It can be a bit tricky to get the commands working because it's not always clear if you need to be in fastboot or bootloader.
This worked for me:
Reboot to bootloader by entering "adb reboot bootloader"
After that try "fastboot flashing lock"

Thanks @zxcv88
After installing the lenovo USB driver, the !Android in Other devices was updated.
LenovoUsbDriver_v1.1.34
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Boot into bootloader mode and "fastboot flashing lock" runs without any issue
Appreciate all for the advise and help! Appreciate ~

zeroflame15 said:
Thanks @zxcv88
After installing the lenovo USB driver, the !Android in Other devices was updated.
LenovoUsbDriver_v1.1.34
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Boot into bootloader mode and "fastboot flashing lock" runs without any issue
Appreciate all for the advise and help! Appreciate ~
Click to expand...
Click to collapse
sorry zeroflame15..... 2 question.... from (fake) global to china stock :
1 flash china
2 lock bootloader
right?
and most important.....lock bootloader is a "must" or is a choice?
if i dont lock bootloader i haven not ota and L1 ? im interested only in OTA updates....not l1 widevine...
thanks

fazioso said:
sorry zeroflame15..... 2 question.... from (fake) global to china stock :
1 flash china
2 lock bootloader
right?
and most important.....lock bootloader is a "must" or is a choice?
if i dont lock bootloader i haven not ota and L1 ? im interested only in OTA updates....not l1 widevine...
thanks
Click to expand...
Click to collapse
Sort of yes.
Initially after flash to stock china rom, i was able to OTA. But subsequent check for updates will get error saying devices is rooted.
After locked bootloader, tried OTA again and indeed there is another new updates.
Saw some chinese video for those who wanted the rooted status and also to perform OTA updates, they are using magdisk to hide the root.

zeroflame15 said:
Sort of yes.
Initially after flash to stock china rom, i was able to OTA. But subsequent check for updates will get error saying devices is rooted.
After locked bootloader, tried OTA again and indeed there is another new updates.
Click to expand...
Click to collapse
thanks!
its seems most difficult to lock/unlock bootloader that flash rom.....
but you need ZUI Unlock Website also for lock? cause seems need only for unlock...right?

No need for lock. Like what others have mentioned. Just a single line command and it works as long you got the right drivers installed.

Tropaion said:
How To Lock and Unlock Bootloader - Xioaxin Pad Pro 2021 - TB-J716F
5. Go to the ZUI Unlock Website and request the unlock image
View attachment 5432885
6. You should get a mail where you can download a file called "sn.img".​
Click to expand...
Click to collapse
my friend ....i have a unlocked bootloader ,cause for now i have the fake global....want to change in china stock....
but i ask anyway to the zui unlock website the sn.img in case i need in future.....
just a question.... after many hours or days i will receive the sn.img file? pass 10 minutes and nothing yet