Database Info

[Q] Fastboot and locking problems

hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?

Are you in the bootloader? (Phone off -> Vol. Up + Power -> fastboot oem lock).
Also, does the command "fastboot devices" show your device?

The USB connector socket at the phone might not make a proper contact with the USB plug. Make sure they connect properly. You may try another cable, or have a look at your USB socket and compare it to another. Check out particularly the little horizontal part in the USB socket.
Make sure you're in bootloader/fastboot mode before attempting to connect in fastboot. Fastboot cannot detect your phone, make sure your udev related settings are appropriate. Check on a Linux PC: https://source.android.com/source/initializing.html Configuring USB Access section.
If after this your phone will not be recognized by fastboot, please post the output of the following command (as root), after seconds after connecting the phone in fastboot mode:
Code:
tail /var/log/messages

Harbb said:
Are you in the bootloader? (Phone off -> Vol. Up + Power -> fastboot oem lock).
Also, does the command "fastboot devices" show your device?
Click to expand...
Click to collapse
fastboot does not show my device. I go into bootloader using adb reboot bootloader because my stupid power button wont work, thats why i want to sent it in to get fixed.

If drivers are properly installed this might not be working because the power button is stuck in or something. Not sure what to try to sort it out if that's the case.

mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
1 - Boot your phone into fastboot mode.
2 - open cmd in your pc.
3 - write: cd \"name of the file where your fastboot is in your pc", and then press enter.
4 - write: fastboot oem lock
5 - press enter and it's done!

bjuderas said:
1 - Boot your phone into fastboot mode.
2 - open cmd in your pc.
3 - write: cd \"name of the file where your fastboot is in your pc", and then press enter.
4 - write: fastboot oem lock
5 - press enter and it's done!
Click to expand...
Click to collapse
if you read the first post it says that fastboot doesnt work

mikeydubbs said:
if you read the first post it says that fastboot doesnt work
Click to expand...
Click to collapse
Sorry, didn't read it right!
And I'm sorry, but I don't know the solution for your problem!

have you tried using a different usb port on your pc?
sent from my dark iced, skanky, t11 infused ns4g

p1gp3n said:
have you tried using a different usb port on your pc?
sent from my dark iced, skanky, t11 infused ns4g
Click to expand...
Click to collapse
yeah i have and i tried using my laptop, and ubuntu 11.10
this sucks so much

i sent my phone in for a broken power button as well. I couldn't even get into the bootloader to relock it so i sent it with an unlocked bootloader. they still fixed it.

shahravi94 said:
i sent my phone in for a broken power button as well. I couldn't even get into the bootloader to relock it so i sent it with an unlocked bootloader. they still fixed it.
Click to expand...
Click to collapse
so do you think as long as its not rooted they wont care?

yup! i flashed a stock image so it was unrooted and sent it in. they fixed it up for me

If you are using Linux you might need su permissions!
Try:
sudo fastboot oem lock

mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Hi, I know this thread is old but I was having the same problem relocking my nexus 4 after installing stock Android 4.4.3 KitKat.
I'm using Nexus Root Toolkit, I don't know what tools you're using to lock your nexus S boblem ut this very easy to use it downloads the drivers and what ever you need to lock, unlock or flash stock and custom roms for any Nexus device.
So my problem was that I would launch OEM Lock on Nexus Root Toolkit and it would detect the device, reboot in Fastboot mode and it would proceed just fine but after saying "Launching TWRP.... something" it would reboot the phone and say to me "Waiting for device" untill it would time out.
I found out that when the program(NEXUS ROOT TOOLKIT) asked me to download a TWRP IMG files, I said no everytime because I didn't think I'd need it. So after trying 5 times, I allowed it to download it and i retryed to OEM Lock it and MAGIC!
Somewhere in the process of Locking the rom it is going to need the TWRP File so allowing the program to download it solved it for me.
I don't know if this will help you or if you still have the same phone, but if you do have use Nexus Root Toolkit and download all it asks and you'll be fine.
Good Luck.

"waiting for device" forever when "fastboot oem unlock:
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
I have the same exact problem.
ADB works fine when the phone is up & running, so I am suspecting a driver compatibility problem when the phone is in "FASTBOOT MODE".
I tried to install the "Universal Naked Driver 0.73 (Compatible with Nexus 5, 4, 7, 10 and S)" but Windows 7 64-bit refuses to pick it up. I use the Device Manager method which shows (when the phone is in "FASTBOOT MODE"):
Code:
"Other Devices
> Android 1.0"
When the phone is up & running, Device Manager shows it as:
Code:
"Android USB Devices
> SAMSUNG Android Composite ADB Interface"
Any idea how to proceed from here?
-----
Update: After a day went by, I searched Google some more and found a thread that describes exactly my problem:
http://forum.xda-developers.com/nexus-s/help/nexus-s-root-windows-requests-android-1-t878579
Which led me to:
http://forum.xda-developers.com/nex...oader-nexus-s-t875580/post9861928#post9861928
Which led me to:
http://pdanet.co/a/
I am rushing to try this now...
-------
Success!
~> fastboot oem unlock
...
OKAY [ 18.734s]
finished. total time: 18.734s
Click to expand...
Click to collapse

nunojpg said:
If you are using Linux you might need su permissions!
Try:
sudo fastboot oem lock
Click to expand...
Click to collapse
It helped. Thanks!

mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Well before trying to Relock the device see whether its connected or not. Type this command fastboot devices and hit enter see whether it shows some no. As in a reply if not that means the deivce isnt connected. If the device is connected type this command to relock your device fastboot oem lock and hit enter. Check on your device screen The Lock status will be changed to LOCKED.
If Helped Click Thanks
---------- Post added at 03:30 PM ---------- Previous post was at 03:27 PM ----------
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Well before trying to Relock the device see whether its connected or not. Type this command fastboot devices and hit enter see whether it shows some no. As in a reply if not that means the deivce isnt connected. If the device is connected type this command to relock your device fastboot oem lock and hit enter. Check on your device screen The Lock status will be changed to LOCKED.
If Helped Click Thanks

[Q] Fastboot does not work

I have been trying to flash Clockwork Mod Recovery through fastboot, but it's not working. I boot into the bootloader (Power + Vol Dwn), and then into the second bootloader menu (Vol Dwn instead of Vol Up when prompted to go into recovery). When I get the 3 icons (Android Cold Boot, Fastboot USB Protocol, Wipe), I select Fastboot, and the tab displays "Starting Fastboot USB Download Protocol" but nothing happens from here. Is there a problem with the bootloader? Is there a way to replace the bootloader or the fastboot protocol?

gaxiolafm said:
I have been trying to flash Clockwork Mod Recovery through fastboot, but it's not working. I boot into the bootloader (Power + Vol Dwn), and then into the second bootloader menu (Vol Dwn instead of Vol Up when prompted to go into recovery). When I get the 3 icons (Android Cold Boot, Fastboot USB Protocol, Wipe), I select Fastboot, and the tab displays "Starting Fastboot USB Download Protocol" but nothing happens from here. Is there a problem with the bootloader? Is there a way to replace the bootloader or the fastboot protocol?
Click to expand...
Click to collapse
It was saying the same for me too,but just go ahead and flash...it will work just fine.

Pretoriano80 said:
It was saying the same for me too,but just go ahead and flash...it will work just fine.
Click to expand...
Click to collapse
I've tried like 10 times, twice I left it plugged in for about 4 hours, and nothing flashed. When I put "fastboot -i...." in the command prompt, I get "<waiting for device>" and nothing happens, and I can't type anything else.

gaxiolafm said:
I've tried like 10 times, twice I left it plugged in for about 4 hours, and nothing flashed. When I put "fastboot -i...." in the command prompt, I get "<waiting for device>" and nothing happens, and I can't type anything else.
Click to expand...
Click to collapse
Oh,check if the drivers are installed corectly.Some users reported the same issue like yours in the CWM recovery thread and some of them managed to fix it,have a look in that thread.

Pretoriano80 said:
Oh,check if the drivers are installed corectly.Some users reported the same issue like yours in the CWM recovery thread and some of them managed to fix it,have a look in that thread.
Click to expand...
Click to collapse
I've tried everything in that thread. The command window still hangs at <waiting for device>
I downloaded drivers from 4 different places, still nothing. I just flashed the .30 update downloaded directly from Asus, and ran the Debugfs root method again, still nothing. At least now I don't have TWRP! I will just wait until there is another method for flashing CWM, since I'm not seeing any official ROMs I want to flash at the time, anyway.
Thanks for taking the time to reply.

I have also been trying to flash CWM as a custom recovery on my TF700t. I have never done this before so please bear with me. I unlocked my device, turned on usb debugging, plugged it into the computer, on the computer I have fastboot installed and I have 6.0.4.7-NonTouch.img in the fastboot folder. I held down power and volume down until I saw RCK, Android, Wipe Data, and in the top left in tiny print it says starting fastboot USB download protocol. I then opened my command prompt and typed in "cd C:/Fastboot" and it brought up fastboot but when I type "Fastboot devices" to check if I am connected it does not give my serial number but it also does not say device not found. when I check my computers devices it says that I have an unspecified device named fastboot connected with all the drivers up to date. And so I typed in "fastboot -i 0x0B05 flash recovery 6.0.4.7-NonTouch.img" and it says it is sending "Recovery" eleven thousand ish KB but it never actually finishes. Am I doing something wrong that it is not recognizing my device properly? Please Help. Thanks in advance.

Titanium318 said:
I have also been trying to flash CWM as a custom recovery on my TF700t. I have never done this before so please bear with me. I unlocked my device, turned on usb debugging, plugged it into the computer, on the computer I have fastboot installed and I have 6.0.4.7-NonTouch.img in the fastboot folder. I held down power and volume down until I saw RCK, Android, Wipe Data, and in the top left in tiny print it says starting fastboot USB download protocol. I then opened my command prompt and typed in "cd C:/Fastboot" and it brought up fastboot but when I type "Fastboot devices" to check if I am connected it does not give my serial number but it also does not say device not found. when I check my computers devices it says that I have an unspecified device named fastboot connected with all the drivers up to date. And so I typed in "fastboot -i 0x0B05 flash recovery 6.0.4.7-NonTouch.img" and it says it is sending "Recovery" eleven thousand ish KB but it never actually finishes. Am I doing something wrong that it is not recognizing my device properly? Please Help. Thanks in advance.
Click to expand...
Click to collapse
Sounds like you don't have the right drivers installed on your PC. With it connected to the PC in fastboot open your device manager - what does it say - any transformer or adb devices with yellow question marks?

sbdags said:
Sounds like you don't have the right drivers installed on your PC. With it connected to the PC in fastboot open your device manager - what does it say - any transformer or adb devices with yellow question marks?
Click to expand...
Click to collapse
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..." then "OKAY [3.523s]" then "writing 'recovery'..." then "OKAY [2.493s]" then "finished. Total time: 6.016s" I then typed "fastboot -i 0x0b05 reboot" and it said "rebooting..." then "finished. total time: 0.548s" When it said this my tablet did not reboot it froze (instead of a green flashing square around RCK it just showed a solid green square) so eventually I just held down the power button till it restarted and booted into fastboot then selected RCK. it showed a little android with his front open and a spinning triangle and said updating then it showed the android flat on his back said error and a triangle with an exclamation point inside. Should I retry sending the recovery?
---------- Post added at 09:25 PM ---------- Previous post was at 09:12 PM ----------
Titanium318 said:
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..." then "OKAY [3.523s]" then "writing 'recovery'..." then "OKAY [2.493s]" then "finished. Total time: 6.016s" I then typed "fastboot -i 0x0b05 reboot" and it said "rebooting..." then "finished. total time: 0.548s" When it said this my tablet did not reboot it froze (instead of a green flashing square around RCK it just showed a solid green square) so eventually I just held down the power button till it restarted and booted into fastboot then selected RCK. it showed a little android with his front open and a spinning triangle and said updating then it showed the android flat on his back said error and a triangle with an exclamation point inside. Should I retry sending the recovery?
Click to expand...
Click to collapse
I believe its the original cable but I bought my tablet used. I double checked all my connections. And I used a different port. After trying again I realized that the tablet is actually freezing when I send the recovery before I even try to reboot. Do I need to root my device or is it possible to have a custom recovery unrooted?

Titanium318 said:
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..." then "OKAY [3.523s]" then "writing 'recovery'..." then "OKAY [2.493s]" then "finished. Total time: 6.016s" I then typed "fastboot -i 0x0b05 reboot" and it said "rebooting..." then "finished. total time: 0.548s" When it said this my tablet did not reboot it froze (instead of a green flashing square around RCK it just showed a solid green square) so eventually I just held down the power button till it restarted and booted into fastboot then selected RCK. it showed a little android with his front open and a spinning triangle and said updating then it showed the android flat on his back said error and a triangle with an exclamation point inside. Should I retry sending the recovery?
---------- Post added at 09:25 PM ---------- Previous post was at 09:12 PM ----------
I believe its the original cable but I bought my tablet used. I double checked all my connections. And I used a different port. After trying again I realized that the tablet is actually freezing when I send the recovery before I even try to reboot. Do I need to root my device or is it possible to have a custom recovery unrooted?
Click to expand...
Click to collapse
Rooting won't help here. You have unlocked it first right?

sbdags said:
Rooting won't help here. You have unlocked it first right?
Click to expand...
Click to collapse
Yes I unlocked it using the asus unlocker tool

Titanium318 said:
Yes I unlocked it using the asus unlocker tool
Click to expand...
Click to collapse
I tried a touch version and also a flashable zip both locked up my tablet the same as before. While my tablet is frozen after attempting to send the recovery I re-entered fastboot devices and it replied "????????????? fastboot" What does this mean?

Titanium318 said:
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..."
Click to expand...
Click to collapse
11.7 MB? Where did you get this recovery?

_that said:
11.7 MB? Where did you get this recovery?
Click to expand...
Click to collapse
This is where I downloaded CWM: http://d-h.st/YLd. So I switched and tried TWRP and it sent to my device and it did not freeze this time. It showed a blue loading bar at the bottom. I rebooted and opened RCK and TWRP opened successfully. I then Told my system to backup to my removable SD card. After it finished I tapped the reboot system button that came up. I opted not to root my device by installing superSU. I then downloaded Cromi-x to my tablet from here: http://forum.xda-developers.com/showthread.php?t=2425383 choosing the deodex option. Ithen followed the rest of the instructions and everything works great Thank you so much for your help!

Titanium318 said:
This is where I downloaded CWM: http://d-h.st/YLd.
Click to expand...
Click to collapse
Did you really expect a recovery for the Nexus 5 to run on the TF700?
Flashing stuff for different devices can just not work, as in your case, or it can turn your tablet into an expensive paperweight. Consider yourself lucky.

Root for MetroPCS/T-Mobile LG Stylo 2 Plus Android 7.0 Nougat ( LGMS550 & LGK550 )

Root for MetroPCS/T-Mobile LG Stylo 2 Plus Android 7.0 Nougat ( LGMS550 & LGK550 )
Everything you need to root your LG Stylo 2 Plus running on Android 7.0 is packed into Stylo2.zip for convenience
If the link ever goes down send me a private message, I'll have a few backups of this laying around.
This method works on MetroPCS (LGMS550) and T-Mobile (LGK550) phone models.
Stylo2.zip​(35.6mb)
VirusTotal Scan
Click to read the guide​
Before doing anything, on your computer you need to extract Stylo2.zip to your Desktop, and install:
minimal_adb_fastboot_v1.4.1_setup.exe (Install this into the Stylo2 folder)
PhoneDrivers.exe
1. Enable Developer Options on your phone, and navigate to the Developer Options page.
Enable OEM unlock
Enable USB debugging
Enable File Transfer
Place no-verify-opt-encrypt-5.1.zip and SuperSU.zip onto your external sd card.
2. After placing the two zip files into the root of your sd card
Enable Charging mode
Authorize your computer for USB debugging
3. Launch MAF32.exe from the Stylo2 folder
(This is Minimal ADB and Fastboot)
4. In the window that pops up type:
adb devices
It should look like this:
PS C:\Users\Hyperion\Desktop\Stylo2> adb devices
List of devices attached
LGMS55010ca1cf1 device
PS C:\Users\Hyperion\Desktop\Stylo2>
5.Boot into the bootloader by typing
adb reboot bootloader
PS C:\Users\Hyperion\Desktop\Stylo2> adb devices
List of devices attached
LGMS55010ca1cf1 device
PS C:\Users\Hyperion\Desktop\Stylo2> adb reboot bootloader
PS C:\Users\Hyperion\Desktop\Stylo2>
6. Next you will be unlocking the bootloader
(This will erase everything on the Internal Storage)
In the PowerShell window you will need to type:
fastboot oem unlock
PS C:\Users\Hyperion\Desktop\Stylo2\Stylo2> fastboot oem unlock
...
(bootloader) Erasing userdata and cache
OKAY [ 12.386s]
finished. total time: 12.389s
PS C:\Users\Hyperion\Desktop\Stylo2\Stylo2>
Your data should now begin to wipe.
7. Once finished with the data wipe, you will need to flash the recovery.img to your device.
In the PowerShell window you will need to type:
fastboot flash recovery recovery.img
It should look like this:
PS C:\Users\Hyperion\Desktop\Stylo2> fastboot flash recovery recovery.img
target reported max download size of 262144000 bytes
sending 'recovery' (15588 KB)...
OKAY [ 0.508s]
writing 'recovery'...
OKAY [ 0.406s]
finished. total time: 0.918s
PS C:\Users\Hyperion\Desktop\Stylo2>
This is where it can get tricky.
8. Turn your phone off.
Unplug your USB cable
Take out your battery
Put your battery back in
Read next step before turning your phone back on
9. You will now need to boot into TWRP, which isn't the most fun thing to do.
(This process begins after the screen prompt that says your phone can't be authorized has already came up.[if it pops up at all])
Get comfortable with this process before attempting it.
Hold Vol Down + Power (Don't let go)
Once you see the LG Logo let go of the power button briefly
Press the power button while still holding Vol Down
Don't let go until a white Factory Reset screen comes up.
Select Yes, then on the next screen select Yes again
(This should boot you into the flashed TWRP Recovery Image)
If you do not boot into TWRP, repeat Process 1-8 until success
(excluding unlocking your bootloader, once unlocked it does not need to be unlocked again.)
10. Assuming you are in the TWRP menu, you will need to wipe the device again.
Navigate to WIPE in the top right
Follow on screen instructions to wipe the device
Click Reboot, and choose Recovery
It wouldn't be a bad idea to make a Backup at this point
11. Once back at the TWRP menu again, you will need to start flashing .zip files.
Click Install
Click Select Storage in the bottom left
Select no-very-opt-encrypt-5.2.zip
Swype to confirm Flash
Press back until at the TWRP main menu again
Click Install
Select SuperSu.zip
Swype to confirm Flash
Some people have had better luck flashing no-very-opt-encrypt after flashing supersu. (I can not confirm this)
12. Reboot to system, let the thing boot loop a couple times at the MetroPCS screen
Cross your fingers until your phone boots up
Download a Root Checker
Check your root access.
If all went well your MS550/K550 running Android 7.0 Nougat should be rooted
I hope it went well xD
-Mike​
Thanks to:
Danielhammons1/Reemitch (For notifying me about a missing step between steps 4 and 5)

I tried this, but when I typed " fastboot oem unlock", all I got was (waiting for device).

i am stuck at fastboot oem unlock it doesnt do anything will you please contact me at [email protected]

wellsweb said:
I tried this, but when I typed " fastboot oem unlock", all I got was (waiting for device).
Click to expand...
Click to collapse
I believe between number 4 and 5, so at 4.5 you must enter the command "adb reboot bootloader" in order to enter fastboot mode.

some help please, stuck on step 4
I have done everything exactly as described in the instructions, when i type abd devices in the cmd prompt i get the following message:
PS C:\Users\gunda\Desktop\Stylo2> adb devices
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb devices
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\Users\gunda\Desktop\Stylo2>
any suggestions or idea as to what is the problem?
thanks

cruba001 said:
I have done everything exactly as described in the instructions, when i type abd devices in the cmd prompt i get the following message:
PS C:\Users\gunda\Desktop\Stylo2> adb devices
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb devices
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\Users\gunda\Desktop\Stylo2>
any suggestions or idea as to what is the problem?
thanks
Click to expand...
Click to collapse
That was completely my bad! I forgot I had setup adb and fastboot differently than in this guide, I updated the above post to reflect what you should actually be doing xD Thanks for catching that!~

Can i do this even though im an update behind?

Th3Joker2496 said:
Can i do this even though im an update behind?
Click to expand...
Click to collapse
I don't see why not, give it a shot, if it messes up let me know. I'll make a TWRP full system backup for you if it doesn't.

Dark Bulbasaur said:
I don't see why not, give it a shot, if it messes up let me know. I'll make a TWRP full system backup for you if it doesn't.
Click to expand...
Click to collapse
thx for the offer but instead i updated the phone lol im about to go through with the rooting process
---------- Post added at 01:57 AM ---------- Previous post was at 01:27 AM ----------
Hey i got stuck on step 5 it just stays saying <waiting for any device>
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
so i got past step 5 but now it says error:cannot load 'recovery.img'

Please help me lower fw lg stylo 2 plus ms550. thank you
---------- Post added at 04:00 PM ---------- Previous post was at 03:57 PM ----------
Please help me unlock my bootload. ms550

Th3Joker2496 said:
thx for the offer but instead i updated the phone lol im about to go through with the rooting process
---------- Post added at 01:57 AM ---------- Previous post was at 01:27 AM ----------
Hey i got stuck on step 5 it just stays saying <waiting for any device>
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
so i got past step 5 but now it says error:cannot load 'recovery.img'
Click to expand...
Click to collapse
Let's try directing the command towards the file instead of trying to launch it like normal. Just replace " E:/Phone/recovery.img " with what ever directory your recovery.img is in. I'll attach a photo for a better example.

Dark Bulbasaur said:
Let's try directing the command towards the file instead of trying to launch it like normal. Just replace " E:/Phone/recovery.img " with what ever directory your recovery.img is in. I'll attach a photo for a better example.
Click to expand...
Click to collapse
im so lost bro you have skype?

I got the message: "encryption was unsuccessful, the password is correct but the data is corrupt"
And then I have a button that says "reset" and that's it. When I click reset I'm taken back to TWRP. I don't know what to do from here. Am I bricked?

Th3Joker2496 said:
thx for the offer but instead i updated the phone lol im about to go through with the rooting process
---------- Post added at 01:57 AM ---------- Previous post was at 01:27 AM ----------
Hey i got stuck on step 5 it just stays saying <waiting for any device>
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
so i got past step 5 but now it says error:cannot load 'recovery.img'
Click to expand...
Click to collapse
How did you get past part 5 ?...Just stuck at WAITING FOR DEVICE

BlackGTNinja said:
How did you get past part 5 ?...Just stuck at WAITING FOR DEVICE
Click to expand...
Click to collapse
I went into the earlier comments and saw someone say to do "adb reboot bootloader" before step 5 and it worked but i couldnt do anything past that it just reset my phone so if u try this stuff just make sure to backup your phone incase

Th3Joker2496 said:
I went into the earlier comments and saw someone say to do "adb reboot bootloader" before step 5 and it worked but i couldnt do anything past that it just reset my phone so if u try this stuff just make sure to backup your phone incase
Click to expand...
Click to collapse
Reflash TWRP on CMD and remove the battery and run twrp like in the instructions. Afterwards go to wipe, select format in TWRP and type "yes" (after you type "yes" the storage will be wiped. Nothing in internal storage.) and reboot to TWRP (make sure you got a sd card or computer to install rom). After the format, install rom. I don't know how to root on stock. Running LOS 64bit 7.1.2 on my Stylo 2 Plus.

Th3Joker2496 said:
I went into the earlier comments and saw someone say to do "adb reboot bootloader" before step 5 and it worked but i couldnt do anything past that it just reset my phone so if u try this stuff just make sure to backup your phone incase
Click to expand...
Click to collapse
It was the Android Fastboot drivers was not configured right,I had to go to Device Mangager and Manually update drivers to Bootloader interface
http://visualgdb.com/KB/usbdebug-manual/

I hv searched for many websites and they said you should unlock bootloader to go further.
But on lg stylo 2 plus bootloader can't be unlocked it is not available on website .
Can anyone suggest me what i should do to forcefully unlock my bootloader.

xpurge1 said:
I got the message: "encryption was unsuccessful, the password is correct but the data is corrupt"
And then I have a button that says "reset" and that's it. When I click reset I'm taken back to TWRP. I don't know what to do from here. Am I bricked?
Click to expand...
Click to collapse
no you're not. just go into twrp, format data, mount the device, move the folders, and try flashing SuperSU BEFORE no verity.

I can't seem to flash the recovery. OEM is unlocked and everything else is correct but when i go to the step to flash, it tells me it cant be flashed.

[HOW-TO] Root BNTV450 Nook 7 (ST16C7BNN) using Magisk.

Root your "Barns & Noble Nook 7" BNTV450 using Magisk's Patch Boot Image File option.
BE CAREFUL!
There are always risks involved when you start messing around with a device.
If something goes wrong, you may end up with a non-working "bricked" device.
This is especially true when you start flashing partitions. (In this case boot.)
Disclaimer
I am not responsible for your non-working "bricked" devices.
I have a few of my own.
Requirements
Barns & Noble Nook 7" BNTV450
A computer with working adb and fastboot
USB cable
WiFi connection
Magisk Manager (Link below)
Stock boot image (Link below)
Tested on:
BNTV450-v1.0.2-20161230 Security patch October 5, 2016
BNTV450-v2.0.4-20170927 Security patch August 5, 2017
BNTV450-v2.0.5-20170110 Security patch November 5, 2017 ota update
macOS 10.13.x
Windows 7 Pro
Steps
Unlock bootloader
Boot Magisk patched boot image
Pull stock boot and recovery images from device
Use Magisk to patch pulled stock image
Test and flash new patched boot image
Notes:
Google updates were needed to get everything working correctly.
PlayServices and WebView
Mac users. As with some other devices, I had to unplug and plugin the USB cable between some of the fastboot commands.
fastboot flash boot patched_boot.img and fastboot boot bntv4-recovery.img
Magisk:
There have been a lot of changes in Magisk since I originally used it to root.
Way too many to mention so, just the basics that apply to this device.
Newer versions of Magisk use the Download directory instead of creating and using the MagiskManager directory.
Some apps search for this directory and used it to determine if the device is rooted.
If you previously used Magisk to root and have a MagiskManager directory, you will want to delete it.
To update Magisk Manager.
Use the update option, it will download and install the newest version.
To update Magisk.
The safest way is to patch the boot image again. Test and flash.
The Direct Install option works but, may lead to a non-desirable outcome.
To uninstall Magisk.
Test boot your original boot image to make sure it works.
Check with Magisk Manager, it should say Magisk not installed.
If so, then flash your stock boot image back using fastboot.
If your stock boot image will not boot, then you are stuck with Magisk patched boot images.
Hardware Keys:
Power and Volume Up = Recovery Mode
Power and Volume Down = Factory Mode
It will show on the bottom Left (Sideways on the top left) Detecting boot mode. With bootloader unlocked it flashes this message very fast so you might not see it.
I still can not produce the same results continuously across mine. The newer ones, that came with v2.0.5 seem to work but, the older ones still it's a 50 % chance if I can get it to work. The bricked ones, do not seem to register the key combo on boot.
Files Needed
Magisk
xda Magisk forum. Link
Magisk and MagiskManager Official github downloads. Link
Boot Images
Magisk patched boot image downloads. Link
Stock recovery and boot image downloads. Link
Credits and Thank You:
@topjohnwu - The creator and brilliant mind behind Magisk.
Everyone who has helped me learn through the years.
Last edited 23.Sep.2018

"QUICK" Guide - BNTV450 Nook 7
Unlock Bootloader
THIS WILL VOID YOUR WARRANTY.
Unlocking the bootloader WILL wipe and Factory Reset your device. Make sure to copy, backup and logout of everything before you begin.
Note: adb and fastboot need to be installed and working.
On device
Go to Settings - About and tap on the build number seven times to enable Developer options.
Go to Settings - Developer options and Enable OEM unlocking and USB debugging
Connect to computer and Allow USB debugging?
On computer
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot flashing unlock
On device
Follow the prompts on the device.
Unlock bootloader?
If you unlock the bootloader,you will be able to install custom operating system software on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.
To prevent unauthorized access to your personal data,unlocking the bootloader will also delete all personal data from your phone(a "factory data reset").
Press the Volume UP/Down buttons to select Yes or No.
Yes (Volume UP):Unlocking(may void warranty).
No (Volume Down): Do not unlock bootloader.
After it returns to fastboot mode, use the power button to turn off, unplug it from computer and then turn on.
It will reboot a few times, including an Erasing... screen.
Once device reboots, run through the initial setup.
Note: Sometimes mine would get stuck on the nook .... animation screen. Give it a few minutes (I wait at least 5 minuets) then power off and power back on.
Note: You will now have the annoying boot delay and "Orange State" message.
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds

"QUICK" Guide - BNTV450 Nook 7
Root using Magisk.
MagiskManager 6.0.0 Download
Magisk 17.2 patched v2.0.5 Download
Using Magisk Manager and the provided Magisk patched boot image.
Note: When booting an image from "fastboot", you should not see the initial "orange boot" screen.
Make sure to grant permission if and when prompted on device.
Some of the adb and fastboot commands may require input on the device.
On device
Go to Settings - About and tap on the build number seven times to enable Developer options.
Go to Settings - Developer options and Enable USB debugging
Connect to computer and Allow USB debugging?
On computer
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot m172_v205_boot.img
Wait for device to boot then.
Reminder. Make sure to grant permission if and when prompted on device.
Code:
adb install -r MagiskManager-v6.0.0.apk
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/bntv4-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/bntv4-recovery.img"
adb pull /sdcard/bntv4-boot.img
adb pull /sdcard/bntv4-recovery.img
Test the images you just made.
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot bntv4-recovery.img
Wait for device to boot into recovery mode then.
On device
In Stock Recovery use the volume down key to highlight Reboot to bootloader and press the power button.
Wait for device to boot into fastboot mode then.
On computer
Code:
fastboot boot bntv4-boot.img
Wait for device to boot then.
On device:
If you haven't setup WiFi, do so now.
Open MagiskManager
Tap on Install
Select Install
Select Patch Boot Image File
Tap on Internal storage
- Note: If Internal storage is not displayed. Tap on the 3-dot menu (upper right corner) and select Show SD card.
Scroll down and tap on bntv4-boot.img
When Magisk is done patching the image file, select CLOSE
You can close MagiskManager as well.
Copy and test your Magisk patched boot image.
On computer
Code:
adb pull /sdcard/download/patched_boot.img
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot patched_boot.img
On device
Open MagiskManager
Note: You should see that Magisk is installed and active.
To do a quick check.
On Computer
Code:
adb shell
[email protected]:/ $su
[email protected]:/ #exit
[email protected]:/ $exit
If it worked, and you are ready to say goodbye to stock Non-root.
Code:
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot boot bntv4-recovery.img
Once it's booted into Recovery, unplug the device.
On device
In Stock Recovery use the volume down key to highlight Wipe cache partition and press the power button.
-- Wiping /cache...
Formatting /cache...
Cache wipe complete.
Then with Reboot system now highlighted press the power button.
You are now rooted and running Magisk.
Last edited 23.Sep.2018
Links to my shell logs.
Unlock bootloader. Pastbin
Root. Pastbin

volume button does not react
Hi
unlocking does not work
As mentioned in the other discussion, the volume up button does not seem to react and so the unlocking does not work. Also one user suggested using the reset button after pressing the volume up button for the unlock; that also does not work for me
Do u have any other suggestions to unlock ?;

arrmusic said:
Hi
unlocking does not work
As mentioned in the other discussion, the volume up button does not seem to react and so the unlocking does not work. Also one user suggested using the reset button after pressing the volume up button for the unlock; that also does not work for me
Do u have any other suggestions to unlock ?;
Click to expand...
Click to collapse
I never ran into this problem. So short answer - No.
Can you point me to that other discussion?
What do you get if you run fastboot oem lks
fastboot oem unlock is supported on this device. You could give that command a try and see if there is a difference.
Not sure what you have tried.
I would start with "Factory Reset" in stock recovery. Skip through the initial setup and try again.
Note: Developer option menu has a toggle at the top, make sure it is turned On.
Sent from my BNTV450 using XDA Labs

Volume up button not recognised while fastboot unlock
Hi
Here is the discussion thread that I was referring to where people are stuck with unresponsive volume up button for fastboot unlock
https://forum.xda-developers.com/nook-7/help/nook-rootable-t3510289
I didn't do the factory reset. So maybe I will do that and see if it works.

unlock not working
Hi
Just to further update you on your reply; i did a factory reset and tried to unlock the bootloader but i get to the same problem; the volume button does not respond; so stuck with the message 'press the volume up button to unlock the bootloader'
I did the fastboot oem lks and that commands executes well and it gives me a OK output.
Cheers & New year greetings!

Any update on the unlock issue
Hi
Is there any update on the unlock issue i reported some time back? My last update on this was executing the command => 'I did the fastboot oem lks and that commands executes well and it gives me OK output.'
not sure if my last update was interpreted in the right way; it does nothing when i type fastboot oem lks except saying it is OK (which i suppose is the expected output of fastboot oem lks). So i do not know how to get around the volume keys not being recognised to go further in unlocking
I still can not use the volume keys for the unlock as it does not seem to react. just stuck a bit on this

@arrmusic I guessed it it looked more like this.
Code:
fastboot oem lks
...
(bootloader) lks = 1
OKAY [ 0.000s]
finished. total time: 0.000s
lks = 0 would be unlocked.
I am looking for a way to un-brick these. I think that may be the best way to correct the button problem also.
What os version are you running? (BNTV450-vx.x.x-20xxxxx)
What do you get when you run fastboot flashing get_unlock_ability ?
Tested a few things tonight.
I was NOT able to re-lock the bootloader on either of my rooted devices.(BNTV450-v2.0.4)
Found some more inconsistencies with power and volume key boot combinations. (Among other things.)
"FAILED (remote: not support on security)" apparently is not just for unlocked devices.
Sent from my BNTV450 using XDA Labs

not able to unlock yet
Hi
Many thanks for your reply.
I seem to have the software version v1.0.2;
I tried to find by googling v2.0.4 but i am not able to find that security update anywhere to download; do you have the v2.0.4 file? can i have it somehow?
I ran the commands u had mentioned in your previous reply.
fastboot flashing get_unlock_ability
...
(bootloader) unlock_ability = 16777216
OKAY [ 0.012s]
finished. total time: 0.012s
fastboot oem lks
...
(bootloader) lks = 1
OKAY [ 0.004s]
finished. total time: 0.008s

What is the origin of the boot.img?
What is the origin of the boot.img? I'd rather not just flash something without knowing where its come from.

74178951237895321 said:
What is the origin of the boot.img? I'd rather not just flash something without knowing where its come from.
Click to expand...
Click to collapse
v2.0.3 boot came from a supposed "N" rom for this device and was the first boot image I was able to make bootable. It was still API 23 "M" by the way.
I would have to find and unpack the original file to see what I edited to make it bootable.
All others are "dd" copies from my own device(s).
I am working on updating the OP and the "Quick Guide"
Boot Images
Download Magisk 15.3 patched v2.0.5 (Preferred and current boot image.)
Sent from my ford using XDA Labs

Scatter file for Mediatek MT8163, opening the tablet
Can you post the scatter file for the Mediatek MT8163?
I've been trying to make my own image dumps for the Nook 7, but have run into an issue where the device won't stay in a readable mode for SP Flash Tools long enough while the battery is still connected. So, the solution for most phones is to disconnect the battery and have it powered over USB only so that it won't go past the preloader and into the charging mode.
But I can't get the darned thing open! My phone has a similar style housing and I had to use a suction cup on the glass while prying at the edges to gain access. But for the Nook 7 its just not working.
Edit: This started while trying to soft load TWRP to make the image dumps. When I do
Code:
fastboot boot twrp.img
It tells me that the kernel address lies outside of memory. Its possible to supply an address to load it at with the fastboot command which you are supposed to learn from the scatter file. I found what I thought was a valid MT8163 scatter file but using the address found within did not fix the issue.
I forgot you mentioned that you didn't pull the original image from your device yourself. I've been trying to root this without relying on images from others. Your latest guide to pulling and modifying your own boot.img is a decent enough middle ground for me to use. Thanks.

@74178951237895321
Sent from my Nexus 7 (2013) using XDA Labs

I was able to get a successful root by following the steps in this thread in combination with those mentioned in this one. ipdev, just to satisfy my curiosity, where did you find this "N rom" image?

ipdev said:
So we hit a snag using Magisk 15.4+ to patch a stock boot image on this device.
Click to expand...
Click to collapse
So, I was dumb and went through with updating Magisk without checking this thread first, and now my tablet's stuck in a bootloop that I can't seem to get out of. @ipdev, do you have any ideas on how this happened/how to get out of it? The tablet can't get past the "Orange state your device has been unlocked etc. etc." screen, and I can't get it to boot into recovery either (using Power+Volume Down, is the combination something else on this tablet?). fastboot won't discover it either, probably because it reboots within seconds and never gets to a point where it could be recognized. I'm thinking of letting it bleed out until its battery dies (unfortunately, the battery is soldered and glued in, so I can't just disconnect it), and checking on it in the morning to see if it will be cooperative enough to let me flash the modified Magisk image.

@saagarjha
I have a few in the same condition. As you noticed, the battery is soldered in so the best you can do is disconnect the screen. (Connector to the right of battery.)
One of these days, I was going to try sp flashtools to see if I could recover one of mine. (I'm not sure if it works with these.)
Sent from my Nexus 5 using XDA Labs

I let the tablet run out of battery and then plugged it back in again and it immediately got stuck in the same bootloop, so it looks like it's actually bricked rather than just pretending. I think SP Flash Tools is the way to go at this point; we'd have to find a functioning preloader driver and scatter file to do that, however. It might be possible to simulate disconnecting the battery by shorting the battery's leads, but I'm not sure if this would work (or is even safe to do).

I was having trouble with unlocking the boot loader on my v1 launch version of this Nook. Recently I dropped it and got a new one via the replacement plan - this one was marked 'v2', came with a 2.x firmware that I wasn't able to even get on my launch Nook 7.
Anyway, this one unlocked without any problems. Thought this might be helpful to anybody having trouble unlocking the bootloader. Consider the revision of the Nook you have. Maybe the solution here is flashing the v2 firmwares to the v1? Hard to say.

unable to unlock
So I did "adb reboot bootloader" and the tablet rebooted and says "=> FASTBOOT mode..." on the screen.
I then did "fastboot flashing unlock" on the computer. Nothing happened on the device and my computer says "< waiting for device >". Could anyone please let me know what I did wrong? Thank you very much.

[HOWTO]Unlock bootloader/root for most G7's except T-Mo via EDL Mode (EASIER METHOD)

Hi everyone!!
IMPORTANT:NEVER SELECT ERASE OR FORMAT PARTITIONS IN LGUP. IT WILL MESS WITH YOUR IMEI
Im making a new guide to unlock your bootloader/root your device. Its easier to do a little bit risker but if you do it slowly you wont mess up your phone and in the event you do you can always recover it. Remember to FOLLOW ALL THE STEPS or you may end up messing up your phone, The best thing is, you dont need to downgrade to even unlock the bootloader!!
DISCLAIMER: I AM NOT RESPONSIBLE IF YOUR PHONE BRICKS! YOU ARE FOLLOWING THIS GUIDE AND ITS YOUR CHOICE TO DO IT OR NOT TO DO IT AND YOURE THE ONE DOING IT. I JUST WANT TO HELP OTHERS OUT.
If you cant for some reason access fastboot even flashing the v35 file, use this guide: https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031 it says verizon but i think most of the models of the g7 cant acess fastboot so you can try this.
Requirments:
-A PC
-USB Cable to connect your phone of course
- V35 ABL
--The LG FIrehose file
- QPST/QFIL
-9008 drivers FOLLOW THIS GUIDE!! To install drivers properly IF WINDOWS DOESNT INSTALL THEM AUTOMATICALLY!!
-ADB PLATFORM or someway to access fastboot via cmd
-PATIENCE!!
Steps.
Download the V35 abl,LG Fire house file, download and install qppst and install the 9008 drivers (WUNDOWS 10 should automatically do it for you) If not, download it and install them.
Boot into edl mode via connecting your phone to the pc then turning it off. Hold Vo- and power and keep pushing the vol+ button multiple times when it turns off.
Go into device manager and check if its detected. to check open up device manager and check Ports and it should say Some port 9009 Qualcomm or something like that (IF theres a question mark, exclamation mark or it says qhusb bulk even after you install the drivers, make sure you disable driver signature enforcment on windows and install the drivers again. Theres multiple ways to do it just google on how to disable driver signature enforcment windows 10. Same with windows 7/8,)
Run as administrator qfil and select flat build,.
--Programmer Type: Load the firehose file
-- On the top go to configuration and where it says Device type, make sure you change it to ufs.
-- Click ok to save and exit
At this point qfil should be detecting your port . If not there should be a select port button next to it on top.
Go to Tools then Partition Manager
A window should pop up with all the partitions. If you get a shara failed error, make sure your drivers are installed correctly and try rebooting into edl again once more. To do that just hold vol - and power until the lg logo comes up and then keep holding vol - and power again and once it turns off again just do the edl combination again.
Search for abl_a and right click on it. First do Read Data, it should take only a couple of seconds Then Load Image and load the v35 image. It should say GPT Finished or something like that at the log with no errors.
Reboot holding volume - and power for like 20-30 seconds until the lg logo comes up Then hold the down button to boot into fastboot or it will automatically boot into fastboot depending on what version of android you are on.
Open the folder where your adb tools are, then hold shift +Right Click in the folder and open powershell. Type and enter CMD
Enter: Fastboot oem unlock it should output with OKAY, If it gives you unknown command, try a USB 2.0 port and then turn off your phone and while its booting up enter the command before you boot into fastboot. Once thats done dont close the window yet!!
Once thats done you can now restore your other abl so you can boot back into android. To do that run %appdata% in the search bar or in the run window by holding the windows button and pressing the R button. Then you should be in C:\Users\{YOUR USERNAME}\AppData\Roaming
Open up the Qualcomm folder --> QFIL --> COMPORT#
There should be a ReadData Blah blah.bin in there. Drag and drop that in the folder where your adb tools are
then go back to the window i told you not to close (The powershell/cmd window) then do fastboot flash abl_a (The file name with ReadData) without the ( ).
Now you can turn off the phone vial holding volume - and power and then reboot into android!! You should get a bootloader unlocked or a cannot be checked for courrption message! Congrats your bootloader is unlocked!!
To root: Just back up your boot image via and then find it in %Appdata% put it in your phone then use magisk manager to patch the boot file and then take that boot file and then flash it to boot_a via edl.
I tried my best to write this guide and sorry for my grammatical mistakes. Ill be helping people unlock/root their bootloaders for free during this covid time as well. If you want to donate you can always tell me but its not necessary.
Ill try making a video as soon as i can.

Nice guide,
Will I able to use this guide to root my G7 verizon version ? (G710VM)
Thanks ?

nyolai said:
Nice guide,
Will I able to use this guide to root my G7 verizon version ? (G710VM)
Thanks
Click to expand...
Click to collapse
Should be in theory

nyolai said:
Nice guide,
Will I able to use this guide to root my G7 verizon version ? (G710VM)
Thanks
Click to expand...
Click to collapse
Yes and no. Yes it will unlock the bootloader but the problem with verizon there is no fastboot unless you erase the laf imgs.
Which is why in my guide I use the crossflashed ULM11g it has fastboot and the oem unlock enable button which makes it easier to issue the "fastboot oem unlock" command.
Give it a try and if your not good at doing this with qfil will brick your device. If you run into issues try my guide.
https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031

netookska05 said:
Yes and no. Yes it will unlock the bootloader but the problem with verizon there is no fastboot unless you erase the laf imgs.
Which is why in my guide I use the crossflashed ULM11g it has fastboot and the oem unlock enable button which makes it easier to issue the "fastboot oem unlock" command.
Give it a try and if your not good at doing this with qfil will brick your device. If you run into issues try my guide.
https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031
Click to expand...
Click to collapse
Ill add your link to my thread.

Awesomeslayerg said:
Requirments:
-A PC
-USB Cable to connect your phone of course
- V35 ABL
-The LG FIrehose file
- QPST/QFIL
-9008 drivers
-ADB PLATFORM or someway to access fastboot via cmd
-PATIENCE!!
Click to expand...
Click to collapse
All the links to files redirect to "Unbrick G7" file.

I m stuck in this step
A window should pop up with all the partitions. If you get a shara failed error, make sure your drivers are installed correctly and try rebooting into edl again once more. To do that just hold vol - and power until the lg logo comes up and then keep holding vol - and power again and once it turns off again just do the edl combination again.
always got Shara failed error.
Has windows 10 and tried all possibilities.
The driver not detected automatically so installed manually. Please Help

TigerV said:
I m stuck in this step
A window should pop up with all the partitions. If you get a shara failed error, make sure your drivers are installed correctly and try rebooting into edl again once more. To do that just hold vol - and power until the lg logo comes up and then keep holding vol - and power again and once it turns off again just do the edl combination again.
always got Shara failed error.
Has windows 10 and tried all possibilities.
The driver not detected automatically so installed manually. Please Help
Click to expand...
Click to collapse
Do you have ELF File for the programmer> The one included in the zip file? Sorry i didnt include the ABL Ill update the zip soon Do you get an exclmation mark or something on the ports in devnice manager?

Awesomeslayerg said:
Do you have ELF File for the programmer> The one included in the zip file? Sorry i didnt include the ABL Ill update the zip soon Do you get an exclmation mark or something on the ports in devnice manager?
Click to expand...
Click to collapse
Thanks for your update.
Yes I m using the same ELF file from zip.
The driver not installed automatically so I have installed it manually via device manager and thn no exclamation mark. But somehow its not work. Tried many time but the same issue

Can you please update the link of 9008 driver and guide? Its not working (may be bad link)

TigerV said:
Can you please update the link of 9008 driver and guide? Its not working (may be bad link)
Click to expand...
Click to collapse
Fixed it. Make sure whenever you close qfil or everythime you get that error just reboot into edl mode again.

****.. Unlocked bootloader. Lost Widewine L1. Relocked bootloader again. but Widewine L3 is available. Anyway to get it back to L1. I remember My pixel and Op6 could get back Widewine L1 after relocking bootloader again.

Awesomeslayerg said:
Fixed it. Make sure whenever you close qfil or everythime you get that error just reboot into edl mode again.
Click to expand...
Click to collapse
Thanks somehow I manged for get edl and flashed the image.
Now getting another issue. when I do "Fastboot oem unlock" its say
FAILED (remote: unknown command)
finished. total time: 0.002s
tried will all method with different PC, Different USB and all as mentioned in the main post, but no luck.

TigerV said:
Thanks somehow I manged for get edl and flashed the image.
Now getting another issue. when I do "Fastboot oem unlock" its say
FAILED (remote: unknown command)
finished. total time: 0.002s
tried will all method with different PC, Different USB and all as mentioned in the main post, but no luck.
Click to expand...
Click to collapse
From ecperince just keep doing that. Nut before entering fastboot put the command in and press enter then reboot directly into fastboot. Kerp doing it unt you see the orsnge unlocked bootloader on your g7 screen

Hey op or whomever can help point me in the right direction: when looking at used/refurbished g7's which models should I ask sellers about or steer away from like the LMG710R (I know the LMG710TM is a no go, what about the Sprint unlocked for GSM and what's there code if I want to avoid them?)?
Thanks.

the v35abl file is not avaliable

wente said:
the v35abl file is not avaliable
Click to expand...
Click to collapse
here is the same link from main post (that link has some hyperlink issue)
https://androidfilehost.com/?fid=1899786940962574206

Would this work on LG710N (korean) ??

Once the bootloader is unlocked with this method DRM is lost forever. Even relocking the bootloader will not bring Widewine certification to L1. I am back to stock with locked bootloader. Widewine is at L3.

Awesomeslayerg said:
From ecperince just keep doing that. Nut before entering fastboot put the command in and press enter then reboot directly into fastboot. Kerp doing it unt you see the orsnge unlocked bootloader on your g7 screen
Click to expand...
Click to collapse
have tried many many time and all possible way but no luck
---------- Post added at 06:25 PM ---------- Previous post was at 06:23 PM ----------
coolrevi said:
Once the bootloader is unlocked with this method DRM is lost forever. Even relocking the bootloader will not bring Widewine certification to L1. I am back to stock with locked bootloader. Widewine is at L3.
Click to expand...
Click to collapse
re-lock and stock flash also not in bring back to L1? I can not even unlock my boot-loader. stuck at "fastboot oem unlock" and its not working, tried all possible way