Database Users

Revert back to locked state after unofficial unlock (Redmi note 3 pro/SD)

Hi All, I have unlocked the bootloader the unnofical way and i am on global 7.1.7.0(LHOMICL) with twrp and root.
I now have recieved the official sms to unlock from xiaomi.
Already i had to open the phone 3 times to get into edl mode. I really dont wont to open the phone agian.
When i try to unlock the tool answers no need to unlock. I think this is because i flashed the adapted emmc_appsboot.mbn and boot.img thru fastboot.
Do i have to change te rom to another version before i try thru edl or fastboot? What is the best procedure to official unlock now because i read a lot of bricks if they try to revert back to original state.
Can some one give me a detailed guide? Thanx in advance.

You need to flash a fully stock edl ROM on top of your current setup.
This will wipe out your hacked bootloader and throw the original (still locked) one back onto your device.
Then just unlock as usual. I did the procedure myself today already as I got my unlock notification today as well.

Ok thnx for the info. I have changed this global rom 7.1.7.0 in great extend and dont wont to lose this setup.
So can I backup my current setup with twrp with the hacked bootloader.
Flash the complete global 7.1.7.0 in edl mode. Unlock with the unlock tool.
Root the rom and install twrp.
After this can i restore the backup with the hacked bootloader with twrp?
I dont know how the unlock tool of xiaomi works, so i could leave the official bootloader in place when i do the restore with twrp and only replace system and data partition or can i flash all the parts back with twrp to keep the unlock?
Wich procedure will keep the official unlock in place or will this unlock stick always?

davegrond said:
Hi All, I have unlocked the bootloader the unnofical way and i am on global 7.1.7.0(LHOMICL) with twrp and root.
I now have recieved the official sms to unlock from xiaomi.
Already i had to open the phone 3 times to get into edl mode. I really dont wont to open the phone agian.
When i try to unlock the tool answers no need to unlock. I think this is because i flashed the adapted emmc_appsboot.mbn and boot.img thru fastboot.
Do i have to change te rom to another version before i try thru edl or fastboot? What is the best procedure to official unlock now because i read a lot of bricks if they try to revert back to original state.
Can some one give me a detailed guide? Thanx in advance.
Click to expand...
Click to collapse
Plz could you help me and tell me where you got the hacked unlocked bootloader cause I bricked my redmi note 3 pro snap dragon and only only fastboot is available and when I try to flash it I get the message device locked boot locked can not flash and plz hobe me a detaild link and downloads and how to flash also I did not get the unlock code and how to get the locked one back z original plz help best regards

Plz indeed to know how to hack the bootloader cause I bricked my phone and I need to make it life

MrColdbird said:
You need to flash a fully stock edl ROM on top of your current setup.
This will wipe out your hacked bootloader and throw the original (still locked) one back onto your device.
Then just unlock as usual. I did the procedure myself today already as I got my unlock notification today as well.
Click to expand...
Click to collapse
please give a detailed tutorial how to do it. I am now in AOSP with unofficially unlocked bootloader. How to relock it again to unlock officially?

Relock Bootloader
I see many asking how to Relock Bootloader, especially those who had unlocked unofficially.
The steps to be followed are following:
(1) Turn on USB debugging for your phone;
Go to Settings -- About Phone --> Touch 7 times on "MIUI version" to Enable Developer Options.
Now go to Settings - Additional Settings - Developer Options --> USB debugging.
Enable USB Debugging and Connect to PC.
(2) Download Fastboot ROM (file extension .tgz or .tar) from
Code:
http://en.miui.com/a-234.html
(3) Boot into EDL
adb devices (to check it's connected)
adb reboot edl
(4) Use MI Flash Tool to Flash the Fastboot ROM
PS: It is assumed that person knows how to get drivers installed for phone if not already, use ADB command as well as know MI Flash Tool basics.
@BRoy_98 @ioosis @davegrond : hope this helps.
@MrColdbird Thanks for the tip

BRoy_98 said:
please give a detailed tutorial how to do it. I am now in AOSP with unofficially unlocked bootloader. How to relock it again to unlock officially?
Click to expand...
Click to collapse
Thx
Sent from my Redmi Note 3 using XDA-Developers mobile app

Unable to relock
Someone please let me know how to relock the bootloader.
I tried flashing the global rom using flash tool but still it says unlocked when i check it from fastboot mode.

anwar08 said:
Someone please let me know how to relock the bootloader.
I tried flashing the global rom using flash tool but still it says unlocked when i check it from fastboot mode.
Click to expand...
Click to collapse
On MiFlash, select folder of Fastboot ROM, then click on Advanced, and in fastboot script select flash_all_lock.bat. After it, close MiFlash then open it again and check in advanced if flash_all_lock.bat comes selected. If yes, close advanced box and flash ROM. Don't forget to close and open MiFlash after choose flash_all_lock.bat script, it's important step. And you can do it in Fastboot mode, don't need to go to EDL mode to flash the ROM.

andersonaragao said:
On MiFlash, select folder of Fastboot ROM, then click on Advanced, and in fastboot script select flash_all_lock.bat. After it, close MiFlash then open it again and check in advanced if flash_all_lock.bat comes selected. If yes, close advanced box and flash ROM. Don't forget to close and open MiFlash after choose flash_all_lock.bat script, it's important step. And you can do it in Fastboot mode, don't need to go to EDL mode to flash the ROM.
View attachment 3854529 View attachment 3854530 View attachment 3854531 View attachment 3854532
Click to expand...
Click to collapse
Am using the 32 bit beta version and there is no Advanced option

anwar08 said:
Am using the 32 bit beta version and there is no Advanced option
Click to expand...
Click to collapse
see if it's in Configuration.

warranty
does rooting redmi note 3 void warranty bcuz it has a locked bootloader and cannot root without unlocking it ????
and can we lock bootloader again for warranty claims ????
plzz help ???
ty.

Why can't we directly update the device..
Like after flashing miui ROM (7.1)then installing (8.1)....will the bootloader get locked....
?....somebody have any idea place help out

Q. Can the device be rooted without voiding warranty?
A. Yes, by unlocking the BL unofficially.
Q. Once rooted and on MiUI, can I update using Updater?
A. No! You'll lock your BL and end up in a bootloop. Instead, use the updater to download the zip file, reboot into recovery (TWRP or ZCX) flash the zip first and then the universal boot.img patched/lazy flasher and reboot to system.

I followed the method mentioned in the replies to relock the bootloader, i.e, flashed the fastboot rom in edl mode
But for some strange reason, when I entered the fastboot mode and checked whether the bootloader is locked or not by "fastboot oem device-info", it said "Device Unlocked: True"
The main problem came when I booted into the ROM; It broke all kinds of wireless connections. The wifi malfunctioned, the phone wouldn't read the SIM cards etc.
Is there a solution? Please help
Thanks

b29 and need to root

Hello. Just got my a7 today and I am glad to say that I have Verizon and my phone is perfect. But I tried the unlock bootloader adb sideload that requires b20. It fails. Also trying the update from b18 to b20 didn't work either.
So am I able to root from b29? What should I do or where should I look for answers?
Thanks

canezila said:
Hello. Just got my a7 today and I am glad to say that I have Verizon and my phone is perfect. But I tried the unlock bootloader adb sideload that requires b20. It fails. Also trying the update from b18 to b20 didn't work either.
So am I able to root from b29? What should I do or where should I look for answers?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165

And this work also with new B29? I read so many here and at the end i was totaly confused, some write B29 isnt rootable at this moment and new bootimage needed, some write yes... no really clear guide with B29.

tasar said:
And this work also with new B29? I read so many here and at the end i was totaly confused, some write B29 isnt rootable at this moment and new bootimage needed, some write yes... no really clear guide with B29.
Click to expand...
Click to collapse
A new bootimage is only needed if you want to root B29 without unlocking the bootloader.
Use tenfar's tool to flash only TWRP recovery, flash the modified fastboot I linked, fastboot oem unlock, flash SuperSU 2.65.

xtermmin said:
A new bootimage is only needed if you want to root B29 without unlocking the bootloader.
Use tenfar's tool to flash only TWRP recovery, flash the modified fastboot I linked, fastboot oem unlock, flash SuperSU 2.65.
Click to expand...
Click to collapse
I am still unclear regarding precise steps needed to unlock my bootloader. And ZTE took down the previous method request for improvement I think I read...
Is this what you mean?:
1. "Use tenfar's tool to flash only TWRP recovery"
http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
2. "flash the modified fastboot I linked"
http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Problem is I am stuck on 1. I installed the Quallcomm drivers and wwlan as instructed, however, my windows doesnt display any comm devices and nothing from Qualcomm. So I am unable to backup my phone onto my computer, which is priority no.1.
** clarification ... I feel more comfortable using linux but the tools are windows so I am dual booting into windows. I might be missing a simple step regarding my phone device manager....

canezila said:
I am still unclear regarding precise steps needed to unlock my bootloader. And ZTE took down the previous method request for improvement I think I read...
Is this what you mean?:
1. "Use tenfar's tool to flash only TWRP recovery"
http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
2. "flash the modified fastboot I linked"
http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Problem is I am stuck on 1. I installed the Quallcomm drivers and wwlan as instructed, however, my windows doesnt display any comm devices and nothing from Qualcomm. So I am unable to backup my phone onto my computer, which is priority no.1.
** clarification ... I feel more comfortable using linux but the tools are windows so I am dual booting into windows. I might be missing a simple step regarding my phone device manager....
Click to expand...
Click to collapse
Did you power off the phone and hold vol up + vol down and then plug in the usb ?

canezila said:
I am still unclear regarding precise steps needed to unlock my bootloader. And ZTE took down the previous method request for improvement I think I read...
Is this what you mean?:
1. "Use tenfar's tool to flash only TWRP recovery"
http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
2. "flash the modified fastboot I linked"
http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Problem is I am stuck on 1. I installed the Quallcomm drivers and wwlan as instructed, however, my windows doesnt display any comm devices and nothing from Qualcomm. So I am unable to backup my phone onto my computer, which is priority no.1.
** clarification ... I feel more comfortable using linux but the tools are windows so I am dual booting into windows. I might be missing a simple step regarding my phone device manager....
Click to expand...
Click to collapse
Your phone has to be in edl mode to see it as a comm on windows. adb reboot edl
I used the b27 to install twrp with axon7root.exe then used twrp unlock bootloader but couldn't fastboot on windows had to switch to linux.

Careful about rooting and unlocking bootloaders if you can't even follow really detailed instructions!

thjoca3 said:
Did you power off the phone and hold vol up + vol down and then plug in the usb ?
Click to expand...
Click to collapse
That is what I missed. I have used Motorola phones (N6, motox, droid maxx, x2, X) and just wasn't familiar with that combo.
I am now rooted, Unlocked and all is great! Thanks for your help.
Sent from my ZTE A2017U using XDA-Developers mobile app

c7j8d9 said:
Your phone has to be in edl mode to see it as a comm on windows. adb reboot edl
I used the b27 to install twrp with axon7root.exe then used twrp unlock bootloader but couldn't fastboot on windows had to switch to linux.
Click to expand...
Click to collapse
I finished on Ubuntu, too. Now I am excited to see what, if substratum works...
Sent from my ZTE A2017U using XDA-Developers mobile app

chanter100 said:
Careful about rooting and unlocking bootloaders if you can't even follow really detailed instructions!
Click to expand...
Click to collapse
Douche
Sent from my ZTE A2017U using XDA-Developers mobile app

canezila said:
Douche
Sent from my ZTE A2017U using XDA-Developers mobile app
Click to expand...
Click to collapse
Since we are name calling now, you DOO DOO head!!! lol

chanter100 said:
Since we are name calling now, you DOO DOO head!!! lol
Click to expand...
Click to collapse
It was said in fun, glad you took it that way. [emoji12]
Sent from my ZTE A2017U using XDA-Developers mobile app

canezila said:
That is what I missed. I have used Motorola phones (N6, motox, droid maxx, x2, X) and just wasn't familiar with that combo.
I am now rooted, Unlocked and all is great! Thanks for your help.
Sent from my ZTE A2017U using XDA-Developers mobile app
Click to expand...
Click to collapse
So, for those of us whonhave not yet taken "the plunge", do you mind detailing the exact steps that finally worked for you? These multiple threads have a variety of trials, errors & successes..TIA

I play pokemon go so do not want to root the phone.. unless there is a way to hide the root from the app.

Hello,
Guys I've been reading for hours (feels like I'm running in circles) lol
I just got the Axon 7 and I'm not able to figure out how to get it fully working with Verizon, And I'm not getting any help from ZTE or Verizon.
Can anyone point me in the right direction?
I'm to the point where I'm ready to send it back.

DJRobBlaze said:
Hello,
Guys I've been reading for hours (feels like I'm running in circles) lol
I just got the Axon 7 and I'm not able to figure out how to get it fully working with Verizon, And I'm not getting any help from ZTE or Verizon.
Can anyone point me in the right direction?
I'm to the point where I'm ready to send it back.
Click to expand...
Click to collapse
Stick your active Verizon SIM into Slot 1, turn on A7, enable Data Roaming on Slot 1, manually set APN (if desired), done.

chanter100 said:
I play pokemon go so do not want to root the phone.. unless there is a way to hide the root from the app.
Click to expand...
Click to collapse
Magisk Root = Systemless root enabling bootloader and system hide so safetynet api cannot view that information
Does it work? Probably, do I know? No. I am in the process of getting my B29 bootloader unlocked and rooted.

c7j8d9 said:
Your phone has to be in edl mode to see it as a comm on windows. adb reboot edl
I used the b27 to install twrp with axon7root.exe then used twrp unlock bootloader but couldn't fastboot on windows had to switch to linux.
Click to expand...
Click to collapse
You said you used B27 to install TWRP but, was your phone already upgraded to B29? That is the key of the OP.

How to lock bootloader on latest stock oreo (A2017G)?

I am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL

Spooderman46 said:
I am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL
Click to expand...
Click to collapse
I'm not even sure if you can lock the bootloader in stock+ Oreo, but it should be possible. What you can do is go back to MM (MM B10 should be fine), then use a fastboot package for MiFlash (such as A2017U_FASTBOOT_UNLOCK_EDL, it works even though you have a G) or maybe check if EDL Tool has an option to install fastboot, i don't remember.
The other way around it is not locking it and just using a modified bootloader to conceal the 5 second screen. Good enough for sending the phone with warranty. If you'll sell it you might be able to sell it for more if the bootloader is unlocked

Choose an username... said:
I'm not even sure if you can lock the bootloader in stock+ Oreo, but it should be possible. What you can do is go back to MM (MM B10 should be fine), then use a fastboot package for MiFlash (such as A2017U_FASTBOOT_UNLOCK_EDL, it works even though you have a G) or maybe check if EDL Tool has an option to install fastboot, i don't remember.
The other way around it is not locking it and just using a modified bootloader to conceal the 5 second screen. Good enough for sending the phone with warranty. If you'll sell it you might be able to sell it for more if the bootloader is unlocked
Click to expand...
Click to collapse
Thanks I checked the Axon 7 Toolkit and turns out it does have fastboot unlock as part of the process of unlocking the bootloader. Though it techinically doesn't support Oreo I chose the nougat one and it still did the trick albeit with another hardbrick, once locking the bootloader I had to wait for the battery to drain again before I could get into EDL and flash back to Oreo. Very painful proccess, would not recommend, should have just used your method of going back to marshmallow locking then updating again. Thanks anyway mate, the help was much appreciated.

Spooderman46 said:
Thanks I checked the Axon 7 Toolkit and turns out it does have fastboot unlock as part of the process of unlocking the bootloader. Though it techinically doesn't support Oreo I chose the nougat one and it still did the trick albeit with another hardbrick, once locking the bootloader I had to wait for the battery to drain again before I could get into EDL and flash back to Oreo. Very painful proccess, would not recommend, should have just used your method of going back to marshmallow locking then updating again. Thanks anyway mate, the help was much appreciated.
Click to expand...
Click to collapse
I never mentioned the axon7toolkit. That one is finicky, I don't recommend it. I was talking about EDL Tool (you might even find it if you google it), it's here in the ROMs, kernels, development section.

Spooderman46 said:
I am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL
Click to expand...
Click to collapse
you need to flash original stock rom for your device trough edl. (rom your device came from factory,you need B11 marshmallow)
then boot into system,unlock developer options.Allow oem unlock and turn on usb debugging.Now connect phone to laptop and check the dialogue on your phone that ask for usb debug.Unplug phone.
When you did this you want to flash TWRP trough EDL.
Now boot in TWRP and flash UnlockbootloaderPackage from DrakenFX.
Reboot system.
Now turn off your device and boot into fastboot,connect your phone with laptop and open ADB terminal on your laptop or use Axon7toolkit.
In terminal enter fastboot oem lock,or in axon7toolkit choose lock bootloader.
Your bootloader is now locked.
PS: you dont need locked bootloader to recieve ota's,and make sure you are on the firmware your device came shipped with!!
You need a locked bootloader to get rid of the warning message ( dont flash any mod package that claims it delete the warning page)

Predatorhaze said:
you need to flash original stock rom for your device trough edl. (rom your device came from factory,you need B11 marshmallow)
then boot into system,unlock developer options.Allow oem unlock and turn on usb debugging.Now connect phone to laptop and check the dialogue on your phone that ask for usb debug.Unplug phone.
When you did this you want to flash TWRP trough EDL.
Now boot in TWRP and flash UnlockbootloaderPackage from DrakenFX.
Reboot system.
Now turn off your device and boot into fastboot,connect your phone with laptop and open ADB terminal on your laptop or use Axon7toolkit.
In terminal enter fastboot oem lock,or in axon7toolkit choose lock bootloader.
Your bootloader is now locked.
PS: you dont need locked bootloader to recieve ota's,and make sure you are on the firmware your device came shipped with!!
You need a locked bootloader to get rid of the warning message ( dont flash any mod package that claims it delete the warning page)
Click to expand...
Click to collapse
Repeatedly posting the exact same thing in every thread will only get you banned again, you sure you want that?

SaintZ93 said:
Repeatedly posting the exact same thing in every thread will only get you banned again, you sure you want that?
Click to expand...
Click to collapse
Sorry

Bricked Verizon VS995 in Fastboot loop

Hi,
I’ve got an older Verizon LG V20 that’s been bricked. I hid it in a drawer for the past year or so, and stumbled across it again. If I can get this fixed, I’d love to update it and give it as a gift to an older friend who has a 6 yr old crap android phone. But first, some history…
-bought used in great shape and rooted with Dirty Santa to run on TMobile. I don't recall which ROM I used, but it was very stock minus the carrier apps. My wife had a chance to go to Italy, so we bought a 3rd party european SIM with 30 days of data and voice from Three UK. Short story is that the phone never recognized the SIM, but she used it to take some great pics during her stay.
-once back in the US, I decided to try a different ROM and I think I flashed the wrong files or something… it’s my fault but I honestly can’t recall if I loaded a Samsung image instead, or what exactly happened.
Currently, the phone boots ONLY into fastboot mode. ADB does not recognize the device, and I’m thinking that I’ve lost TWRP Recovery since I can’t enter Recovery Mode at all.
If I do hold Vol Down + Power, I get a Hard Reset menu, but nothing in there helps.
I tried using LGUP, but the device is "not recognized."
I’m at a loss as to what to do at this point. If there IS a way to un-brick this, I think it would make a great phone for a good friend.
If anyone has any suggestions, I’d love any ideas that you may have. I tried looking to see if any other threads cover this, but I’m not seeing anything with specifics or pointers to How-Tos. If I missed the relevant links, I’d appreciate being pointed to them.
Also…
-if I can return to Stock condition, I can then unlock the bootloader and flash a more current ROM again. Would I need to pick a new radio so it better matches TMobile vs the Verizon setup it originally came with?
thanks for reading!
motionmonk

Since you can get to fastboot why not flash a twrp to see if you will get recovery

0x0null said:
Since you can get to fastboot why not flash a twrp to see if you will get recovery
Click to expand...
Click to collapse
When I run fastboot in Terminal, I get a blank response-- that is, a simple carraige return with no info listed.
This is on a fresh Win10 install with the latest Platform Tools package (Justt adb & fastboot) from the Android Studio website.
Are there other drivers that I need? When I installed LGUP, I did install the LGMobileDriver_WHQL_Ver_4.1.1.exe installer as well.
-motionmonk

motionmonk said:
When I run fastboot in Terminal, I get a blank response-- that is, a simple carraige return with no info listed.
This is on a fresh Win10 install with the latest Platform Tools package (Justt adb & fastboot) from the Android Studio website.
Are there other drivers that I need? When I installed LGUP, I did install the LGMobileDriver_WHQL_Ver_4.1.1.exe installer as well.
-motionmonk
Click to expand...
Click to collapse
That is bad, can you try it ona windows 7 PC?

0x0null said:
That is bad, can you try it ona windows 7 PC?
Click to expand...
Click to collapse
I could... I need to find my Win7 install disks for an old laptop.
I'll report back by tomorrow.
I don't do this often... what makes WIndows 7 a better method than Win 10?
-motionmonk

motionmonk said:
I could... I need to find my Win7 install disks for an old laptop.
I'll report back by tomorrow.
I don't do this often... what makes WIndows 7 a better method than Win 10?
-motionmonk
Click to expand...
Click to collapse
issues with drivers

It took longer than I thought to find my Win7 installers... I'm in the middle of the reinstall now.
I plan to load the Android Platform Tools, LG Mobile Drivers, LGUP framework... is there anything else I should install?
thanks for any suggestions; I don't root often at all and am rusty at this
-motionmonk

Win 7 update
Ok, I've installed WIN7, Android Platform Tools (just ADB & Fastboot), LG drivers and LGUP.
Now when I do the fastboot command, I get a true response:
fastboot devices
VS995aa11a111 fastboot (where a=letters, 1=numbers)
YAY!
So at this point, if I load a TWRP.zip, would I be able to boot into Recovery, instead of fastboot mode?
I checked the official TWRP website, and the latest is TWRP 3.2.3-0.
EDIT: I looked in the LG Section, and it appears that there is not an official TWRP for the LG V20. Is that right?
Having gotten to the point where the laptop recognizes the phone, I really don't want to make a dumb mistake :silly:
thanks for getting me this far!
-motionmonk

motionmonk said:
Win 7 update
Ok, I've installed WIN7, Android Platform Tools (just ADB & Fastboot), LG drivers and LGUP.
Now when I do the fastboot command, I get a true response:
fastboot devices
VS995aa11a111 fastboot (where a=letters, 1=numbers)
YAY!
So at this point, if I load a TWRP.zip, would I be able to boot into Recovery, instead of fastboot mode?
I checked the official TWRP website, and the latest is TWRP 3.2.3-0.
EDIT: I looked in the LG Section, and it appears that there is not an official TWRP for the LG V20. Is that right?
Having gotten to the point where the laptop recognizes the phone, I really don't want to make a dumb mistake :silly:
thanks for getting me this far!
-motionmonk
Click to expand...
Click to collapse
There is no official twrp build for the V20, search for Phoenix's unofficial twrp thread
Sent from my LG-H910 using XDA Labs

cnjax said:
There is no official twrp build for the V20, search for Phoenix's unofficial twrp thread
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Thank you cnjax... I think I got it now:
recovery-twrp-vs995-2018-10-18

Now that I have the TWRP Installer, I connect the phone (in perma-fastboot mode), and verify that it is connected by using fastboot devices. I get a recognition string in reply. So now I move on...
-rename recovery-twrp-vs995-2018-10-18.img as TWRP.img
-move TWRP.img to my platform-tools folder
-issue flashing command fastboot flash recovery TWRP.img
Here's what I get:
Sending 'recovery' (25984 KB)
OKAY [ 0.889s]
Writing 'recovery'
FAILED (REMOTE: 'unknown command'}
Finished. Total time: 1.092s
I'm pretty sure I have the syntax correct, and the TWRP.img file is being recognized, but -something- isn't working.
Have I missed something here?
thanks for any suggestions,
motionmonk

fastboot help pages
motionmonk said:
Now that I have the TWRP Installer, I connect the phone (in perma-fastboot mode), and verify that it is connected by using fastboot devices. I get a recognition string in reply. So now I move on...
-rename recovery-twrp-vs995-2018-10-18.img as TWRP.img
-move TWRP.img to my platform-tools folder
-issue flashing command fastboot flash recovery TWRP.img
Here's what I get:
Sending 'recovery' (25984 KB)
OKAY [ 0.889s]
Writing 'recovery'
FAILED (REMOTE: 'unknown command'}
Finished. Total time: 1.092s
I'm pretty sure I have the syntax correct, and the TWRP.img file is being recognized, but -something- isn't working.
Have I missed something here?
thanks for any suggestions,
motionmonk
Click to expand...
Click to collapse
Hi
I'm just a noob but I am interested in the problem you are having and am following it to see what comes up with it.
There is a good fastboot thread here:
https://forum.xda-developers.com/showthread.php?t=2277112
On the first page you have options to wipe before flashing - i.e. system, boot, data, RECOVERY etc,
Maybe give those pages a read while waiting for someone more knowledgeable to fix your phone...
Since you are not sure what happened maybe the modem was affected which I think is bad...
I think doing a "fastboot getvar all" might give you a status of what you are dealing with .... since it gives you versions
of things...
Anyhow, good luck reviving the phone - "rooting" for you haha!
---------- Post added at 10:33 PM ---------- Previous post was at 10:05 PM ----------
This link might also be a good read
https://forum.xda-developers.com/v20/how-to/guide-lg-v20-to-life-t3827732

secondhand2 said:
There is a good fastboot thread here:
https://forum.xda-developers.com/showthread.php?t=2277112
. . .
I think doing a "fastboot getvar all" might give you a status of what you are dealing with .... since it gives you versions
of things...[/url]
Click to expand...
Click to collapse
secondhand2,
THX for the links! Those were very helpful!
No need to call yourself a noob... I think I outrank you in that department at this point!
I did try your suggestion of fastboot getvar all, and found something interesting...
when I did the command it returned (bootloader) unlocked:no
which I thought was WEIRD, since the phone -was- unlocked with a custom ROM before I messed things up.
I have attached a screenshot to this msg with the full info report.
So now I'm wondering if that's why my previous attempt at flashing TWRP failed?
Does this mean I have a soft-brick or a hard-bricked phone at this point?
I"m learning more through everyone's help and input, but I'm still lost as to where to go from here.

Hi,
I have a US996 and I unlocked it using the lg web site - they send a bin file that you can use to unlock the phone.
There are different exploits on different versions of V20 phones. THere are also versions of Nougat that have an anti rollback that stop you from going from a recent OTA update back to an older one that can be exploited to get root. For example, on the US996 I have., if I had bought it and it had been patched with 10p (not 100% sure which version was the cutoff point) even if the phone was unlocked, I might not be able to get root. So the versions of the ROMs/firmware are imnportant. As it happened I had the 10f version so rooting was possible - but I followed the threads on this site for my specific phone and stuck to STOCK rom's.
So I'm not sure about what ROM you have - i..e which version of the vs995 is rootable after you unlock the phone. And the unlocking method to use - I'm not familiar with dirty santa or lafsploit (might not have spelled that correctly). There is a tool called LGUP and a good thread on that below that I was reading but it is long read which is good for learning.
I can only point you to some threads - but unlocking is the next hurdle.
You might also want to use the latest TWRP and Magisk if you do get to root the phone. I used PHOENIX591's TWRP
- there is a good thread on that. https://forum.xda-developers.com/v2...-t3720239/post78529520?nocache=1#post78529520
Sorry I can't help you more with this - you do need to get the phone unlocked first. Some of these things are very device specific
I'm still keeping an interested eye on this...
Here is the other thread
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
Good Luck!

secondhand2 said:
Hi,
I have a US996 and I unlocked it using the lg web site - they send a bin file that you can use to unlock the phone.
There are different exploits on different versions of V20 phones. THere are also versions of Nougat that have an anti rollback that stop you from going from a recent OTA update back to an older one that can be exploited to get root. For example, on the US996 I have., if I had bought it and it had been patched with 10p (not 100% sure which version was the cutoff point) even if the phone was unlocked, I might not be able to get root. So the versions of the ROMs/firmware are imnportant. As it happened I had the 10f version so rooting was possible - but I followed the threads on this site for my specific phone and stuck to STOCK rom's.
So I'm not sure about what ROM you have - i..e which version of the vs995 is rootable after you unlock the phone. And the unlocking method to use - I'm not familiar with dirty santa or lafsploit (might not have spelled that correctly). There is a tool called LGUP and a good thread on that below that I was reading but it is long read which is good for learning.
I can only point you to some threads - but unlocking is the next hurdle.
You might also want to use the latest TWRP and Magisk if you do get to root the phone. I used PHOENIX591's TWRP
- there is a good thread on that. https://forum.xda-developers.com/v2...-t3720239/post78529520?nocache=1#post78529520
Sorry I can't help you more with this - you do need to get the phone unlocked first. Some of these things are very device specific
I'm still keeping an interested eye on this...
Here is the other thread
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
Good Luck!
Click to expand...
Click to collapse
You're incorrect arb hasn't been incremented on the 996
Sent from my LG-H910 using XDA Labs

Hi cnjax
The thread I used discussed arb but from what I remember it was never clear how to know which arb ( 0 or 1 ) a particular update was at. Are you saying there is never an increment for the us996?
Thank you for clarifying

secondhand2 said:
Hi cnjax
The thread I used discussed arb but from what I remember it was never clear how to know which arb ( 0 or 1 ) a particular update was at. Are you saying there is never an increment for the us996?
Thank you for clarifying
Click to expand...
Click to collapse
Was just pointing out that through the 996 oreo release lg hasn't incremented arb on the 996
Sent from my LG-H910 using XDA Labs

Hi cnjax
It is a bit difficult to read everything n get a clear picture sometimes. I'm hoping you would clarify something
If TWRP is not installed and the phone is unlocked but not rooted which method could be used to install oreo 20f?
Would you be forced to install 10f (nougat) to root and install twrp first before moving on to oreo?
In this scenario I assumed nougat was on the phone originally and it seems the phone is locked from the fastboot info given...but let's say it gets unlocked
Is there a method to install oreo first instead of starting with nougat and version 10f? If there is that would be awesome
Thank you!

secondhand2 said:
Hi cnjax
It is a bit difficult to read everything n get a clear picture sometimes. I'm hoping you would clarify something
If TWRP is not installed and the phone is unlocked but not rooted which method could be used to install oreo 20f?
Would you be forced to install 10f (nougat) to root and install twrp first before moving on to oreo?
In this scenario I assumed nougat was on the phone originally and it seems the phone is locked from the fastboot info given...but let's say it gets unlocked
Is there a method to install oreo first instead of starting with nougat and version 10f? If there is that would be awesome
Thank you!
Click to expand...
Click to collapse
If his bootloader is locked he'll need to downgrade, root and unlock the bootloader with dirty santa, flash updated twrp, flash a rom and magisk
Sent from my LG-H910 using XDA Labs

Post #71 about dumping contents/partitions with lgup seems a good idea -
Then I would try fastboot oem unlock to see what happens but not sure if that can break the bootloader or not. I think you would be in a deeper hole if it went south on you. I'm not sure if doing fastboot oem unlock can be risky at this point

Lg v20 h91820h t-mobile bootloader cannot be unlocked - android 8 oreo

UPDATE:
I successfully unlocked the bootloader, flashed twrp, rooted, updated kernel and roms, tweaking gpu cpu for performance in pubg etc, greenify, flashify, power nap everything.
xposed framework take you in bootloop for this device.
now i am on kernel mk2000, superv20 rom, h91810u, 7 nougat.
if in future anyone feels any problem i am always here.
remember: linus is your friend for this device, and windows 10 suck.
and
sudo $(which fastboot) did miracles for me....
old post:
Hello everyone.
i am new here and i am sorry in advance if i did something wrong. i will come directly to the point.
model number: LG V20 T-MOBILE VERSION, H91820H, NON USA, Currently on oreo android 8.
we are not talking about any kind of roms kernels roots or anything here. just a simple question. " can this model's boot loader be unlocked ? like ever ? or not "
cause i have tried everything, when i say everything i mean everything. followed several posts on internet videos on you tube posts on XDA, tried using multiple PCs, multiple data cables, multiple drivers but for some reason i don't know what, this model's boot loader cannot be unlocked.
THE ERROR:
<WAITING FOR DEVICE> till eternity.
what i have done till now ?
1. lg drivers installed.
2. adb drivers installed with adb fastboot files.
3. updating legacy android adb interface driver, done.
4. went in to boot loader then connected the data cable and updated driver, done.
5. usb debugging oem unlock options activated, done.
6. restarted pc multiple times to update drivers, done.
we all know all it takes is 3 easy commands to unlock bootlaoder
adb reboot bootloader
fastboot oem unlock
fastboot reboot
but in my case i always stuck at 2nd command. waiting for device is shown and nothing happens.
then i ran command, adb devices>> it shows
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
LGH9182bfc6bdc device
next i put the command, fastboot devices and nothing is shown i just go to the next line... c:\adb>
so this is for sure that my device is not connected to the fastboot.
now my only question is, can this device bootloader unlock or not ? so that i stop pushing my limits.
any help will be appreciated.
regards.

X_BlackBurn_X said:
Hello everyone.
i am new here and i am sorry in advance if i did something wrong. i will come directly to the point.
model number: LG V20 T-MOBILE VERSION, H91820H, NON USA, Currently on oreo android 8.
we are not talking about any kind of roms kernels roots or anything here. just a simple question. " can this model's boot loader be unlocked ? like ever ? or not "
cause i have tried everything, when i say everything i mean everything. followed several posts on internet videos on you tube posts on XDA, tried using multiple PCs, multiple data cables, multiple drivers but for some reason i don't know what, this model's boot loader cannot be unlocked.
THE ERROR:
<WAITING FOR DEVICE> till eternity.
what i have done till now ?
1. lg drivers installed.
2. adb drivers installed with adb fastboot files.
3. updating legacy android adb interface driver, done.
4. went in to boot loader then connected the data cable and updated driver, done.
5. usb debugging oem unlock options activated, done.
6. restarted pc multiple times to update drivers, done.
we all know all it takes is 3 easy commands to unlock bootlaoder
adb reboot bootloader
fastboot oem unlock
fastboot reboot
but in my case i always stuck at 2nd command. waiting for device is shown and nothing happens.
then i ran command, adb devices>> it shows
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
LGH9182bfc6bdc device
next i put the command, fastboot devices and nothing is shown i just go to the next line... c:\adb>
so this is for sure that my device is not connected to the fastboot.
now my only question is, can this device bootloader unlock or not ? so that i stop pushing my limits.
any help will be appreciated.
regards.
Click to expand...
Click to collapse
Are you following this > https://r.tapatalk.com/shareLink/to...3&share_fid=3793&share_type=t&link_source=app
[ROOT] - lafsploit - H918 (any version up to and including 20h) - now n00b friendly
Sent from my HD1907 using Tapatalk

Thanks for thanks for replying on a short notice I have seen this post there is no reason to follow any of the post because the very first stage is to unlock the bootloader but as I cannot unlock the bootloader there is no point in following any of the posts my problem is what ever way I follow I am unable to to unlock the bootloader in fact what I can see is whenever I try to type in command ADB devices IC e my phone but when I type fastboot devices nothing happens it's like my phone is not in the fastboot that is why why I cannot unlock the bootloader I have tried every possible step mentioned on the internet and on various forums I also go through some videos on YouTube those guys follow the same steps and unlock their bootloader but my device cannot unlock for some reason so if you lovely people can help me out and figure out what exactly I am doing wrong as I have followed every step of unlocking the bootloader I've installed all the drivers I have updated all the drivers I have done exactly e all three steps which has been asked but still no luck thank you

clsA said:
Are you following this > https://r.tapatalk.com/shareLink/to...3&share_fid=3793&share_type=t&link_source=app
[ROOT] - lafsploit - H918 (any version up to and including 20h) - now n00b friendly
Sent from my HD1907 using Tapatalk
Click to expand...
Click to collapse
To be very precise after following the first step while unlocking the bootloader in the second step when we type fast boot devices it should show some hexadecimal numbers and it should confirm us that our device is in the fastboot mode but in my case whenever I type this command nothing happens that means my device is not recognised to go in the bootloader this is the main problem there is no point in following any of the posts if you cannot complete the very first stage of unlocking your bootloader if you can figure out what exactly is the problem I will be thankful to you because I have followed every step possible I've updated every ADB drivers LG drivers but nothing is helping out as even before starting the procedure of unlocking the bootloader my device is not going in the fast boot also I noticed one thing when I try to go inside the bootloader screen before that in my device manager it is shown as composit device but after that I think it gets disconnected fastboot oem unlock cannot work as it gives a message of waiting for the device after going are using the command ADB reboot bootloader so my problem is the command fastboot oem unlock is pretty useless as it waits for the device and it's stuck there forever please help me out if you can I will be thankful to you regards

X_BlackBurn_X said:
To be very precise after following the first step while unlocking the bootloader in the second step when we type fast boot devices it should show some hexadecimal numbers and it should confirm us that our device is in the fastboot mode but in my case whenever I type this command nothing happens that means my device is not recognised to go in the bootloader this is the main problem there is no point in following any of the posts if you cannot complete the very first stage of unlocking your bootloader if you can figure out what exactly is the problem I will be thankful to you because I have followed every step possible I've updated every ADB drivers LG drivers but nothing is helping out as even before starting the procedure of unlocking the bootloader my device is not going in the fast boot also I noticed one thing when I try to go inside the bootloader screen before that in my device manager it is shown as composit device but after that I think it gets disconnected fastboot oem unlock cannot work as it gives a message of waiting for the device after going are using the command ADB reboot bootloader so my problem is the command fastboot oem unlock is pretty useless as it waits for the device and it's stuck there forever please help me out if you can I will be thankful to you regards
Click to expand...
Click to collapse
Did you downgrade to software version H91810P? Because that should be the first thing you have to do to get everything else to work afterwards.

C D said:
Did you downgrade to software version H91810P? Because that should be the first thing you have to do to get everything else to work afterwards.
Click to expand...
Click to collapse
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.

X_BlackBurn_X said:
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.
Click to expand...
Click to collapse
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
...
(bootloader) ----------------------------------
(bootloader) Device-ID
(bootloader) F3D7DE171C893D55082EAE38270125EF
(bootloader) DA7CB3E78B1DB5709A2CA8********
(bootloader) ----------------------------------
OKAY [ 0.060s]
finished. total time: 0.060s
D:\fastboot>fastboot reboot
rebooting...
finished. total time: 0.008s
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot getvar unlocked
unlocked: no
finished. total time: 0.003s
Click to expand...
Click to collapse

X_BlackBurn_X said:
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.
Click to expand...
Click to collapse
As clsA said, flashing firmware does not require an unlocked bootloader.
Look at parts 1 and 2 of the other step by step guide here:
https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258

clsA said:
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
Click to expand...
Click to collapse
Thanks for the solution. May be this is it. All the time i have been doing it wrong.
Solution : flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP.
I will downgrade from 20h to 10p now and will give you feedback on this soon. Thanks a ton for showing a noob like me the right direction to work.

X_BlackBurn_X said:
Thanks for the solution. May be this is it. All the time i have been doing it wrong.
Solution : flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP.
I will downgrade from 20h to 10p now and will give you feedback on this soon. Thanks a ton for showing a noob like me the right direction to work.
Click to expand...
Click to collapse
No problem the link @C D posted above seems to have all the working links for you

clsA said:
No problem the link @C D posted above seems to have all the working links for you
Click to expand...
Click to collapse
well we have a new problem now.
lgup error 0x2bc invalid command response code = 0x80000202 at 4 percent while flashing.
did i just brick my phone now ? as it says dont unplug until you are done and we have been getting same error again and again.
used the provided kdz file flashing as an upgrade.

ok so the new problem is... may be i was trying to flash h91810p naugaut on to a oreo h91820h
and if i am not wrong at this stage i messed up pretty bad my phone is stuck in donwload mode wont boot up and i need to flash back 20h again to get out of this mess. can anyone hlp me ....
i just wanna know h91810p downgrading from 91820h is possible or not ? cause one is naugaut and one is oreo.

UPDATE:
i was flashing wrong h91810p thats why it was showing error. on another website i got the file compatible to my phone t mobile version and flash was successful.
now i am on h91810p software version andriod 7.
problem UPDATE:
i still cant unlock bootloader. same problem as before downgrading from h91820h.
adb devices shows device.
adb reboot bootloader
fastboot devices gives no result.
phone cannot enter in fastboot mode. the problem still remains the same even after changing the software.
kindly help guys

clsA said:
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
Click to expand...
Click to collapse
hello clsA
"
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
after this it only says waitng for device"
now i am on h91810p as i was instructed. can you please help.
its all happening the same way it was happening when was on h91820h.
fastboot devices cannot be found.
once it reboots in bootloader then it should detect a fastboot device but it doesnot and adb is also lost there.
kindly help.

NEW UPDATE:
my lg v20 now on software h91810p is actually a T MOBILE version. and when i researched more about it i found out T MOBILE deliberately locks the boot loader of many devices and its unlockable.
possible work around can be if the software version installed on your phone can some how be an international version of your ROM, then only you can unlock the bootloader else none of your commands will work. now i am trying to flash this phone using an international ROM version if i succeed i will update. but according to my knowledge flashing other roms other than t mobile ones will definitely give errors in LGUP.

X_BlackBurn_X said:
NEW UPDATE:
my lg v20 now on software h91810p is actually a T MOBILE version. and when i researched more about it i found out T MOBILE deliberately locks the boot loader of many devices and its unlockable.
possible work around can be if the software version installed on your phone can some how be an international version of your ROM, then only you can unlock the bootloader else none of your commands will work. now i am trying to flash this phone using an international ROM version if i succeed i will update. but according to my knowledge flashing other roms other than t mobile ones will definitely give errors in LGUP.
Click to expand...
Click to collapse
Do not flash another model's firmware onto the H918! Doing so will permanently brick your phone. The H918 in particular is incompatible with all other variants' software. Also, flashing H918 firmware onto any other model will also brick that phone.

C D said:
Do not flash another model's firmware onto the H918! Doing so will permanently brick your phone. The H918 in particular is incompatible with all other variants' software. Also, flashing H918 firmware onto any other model will also brick that phone.
Click to expand...
Click to collapse
hello
thanks for the reply.
i know we cannot flash any other phones firmware on to this model.
i was thinking of flashing specifically lg v20 h91810p international stock firmware, one is t mobile and one is international stock rom of same model.
cause t mobile is not allowing me to unlock the bootloader but an international stock rom will.
i have seen people doing on t mobile on youtube videos i dont know how they are doing it.
my problem is :
" as in message sent to various senior on this topic"
LG V20 H91810P, T MOBILE BOOTLOADER CANNOT BE UNLOCKED
HELLO
can you please help me out on a quest to unlock my bootloader of lg v20 h91810p. i have downgraded from h91820h to h91810p and still all the adb commands fail to make my phone go in to fastboot mode. i just cannot enter in fastboot mode,
adb devices shows my device
|but fastboot devices in bootloader mode doesnot show my device at all.
updated all the drivers used multiple pcs usb ports but no luck at all.,
what am i possibly doing wrong can you please help me out? i will be thankful to you.
on a side note i think t mobile has lockedd my bootloader so that i canoot unlock it,
regards

X_BlackBurn_X said:
hello
thanks for the reply.
i know we cannot flash any other phones firmware on to this model.
i was thinking of flashing specifically lg v20 h91810p international stock firmware, one is t mobile and one is international stock rom of same model.
cause t mobile is not allowing me to unlock the bootloader but an international stock rom will.
i have seen people doing on t mobile on youtube videos i dont know how they are doing it.
my problem is :
" as in message sent to various senior on this topic"
LG V20 H91810P, T MOBILE BOOTLOADER CANNOT BE UNLOCKED
HELLO
can you please help me out on a quest to unlock my bootloader of lg v20 h91810p. i have downgraded from h91820h to h91810p and still all the adb commands fail to make my phone go in to fastboot mode. i just cannot enter in fastboot mode,
adb devices shows my device
|but fastboot devices in bootloader mode doesnot show my device at all.
updated all the drivers used multiple pcs usb ports but no luck at all.,
what am i possibly doing wrong can you please help me out? i will be thankful to you.
on a side note i think t mobile has lockedd my bootloader so that i canoot unlock it,
regards
Click to expand...
Click to collapse
Did you make the Linux USB boot stick
Are you following the guide at all?
PART 3: CREATING A BOOTABLE LINUX USB USING FWUL
DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.
https://androidfilehost.com/?w=files&flid=214529
DOWNLOAD RUFUS FROM BELOW AND INSTALL
https://rufus.akeo.ie/
INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.
INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)
NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED
THIS WOULD MAKE YOUR PC RUN LINUX OS
TYPE PASSWORD AS linux AND ENTER
Sent from my HD1907 using Tapatalk

clsA said:
Did you make the Linux USB boot stick
Are you following the guide at all?
PART 3: CREATING A BOOTABLE LINUX USB USING FWUL
DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.
https://androidfilehost.com/?w=files&flid=214529
DOWNLOAD RUFUS FROM BELOW AND INSTALL
https://rufus.akeo.ie/
INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.
INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)
NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED
THIS WOULD MAKE YOUR PC RUN LINUX OS
TYPE PASSWORD AS linux AND ENTER
Sent from my HD1907 using Tapatalk
Click to expand...
Click to collapse
thanks again for the showing me the right direction. i was talking about unlocking the bootloader in step 1.
i will go through your links and try to study this.
just one more question.
does this method unlocks the bootloader ?
if yes please reply yes i will be thankful to you.
i will follow this step now.
regards

X_BlackBurn_X said:
hello clsA
"
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
after this it only says waitng for device"
now i am on h91810p as i was instructed. can you please help.
its all happening the same way it was happening when was on h91820h.
fastboot devices cannot be found.
once it reboots in bootloader then it should detect a fastboot device but it doesnot and adb is also lost there.
kindly help.
Click to expand...
Click to collapse
Why does adb show your device as a 997 which is the Sprint variant
Sent from my LG-H910 using XDA Labs