Hello,
today to my utmost rage i accepted system update, as i never had problems with getting the phoned rooted etc. after updates. But little did I know it was emui 5.0 along with android 7.0 update which pretty much rekt me.
The details of my phone:
HUAWEI VNS-L21
VNS-L21C09B336
kernel 4.1.18-g5e26674
Can provide more if needed.
The only thing I did was to get TWRP through SRKTool from here, xda, and rooting through it. And it worked flawlessly to my needs.
After the update I lost twrp, so without searching back then i tried to get it back through SRKTool to no avail. Downloaded newer SRKTool, same thing.
Then I started searching for more information regarding how to root my phone, during which I found out that I'm PHONE Unlocked FRP locked at fastboot.
And of course my "Disable OEM lock" in developer options is greyed out.
I tried p9toolkit from here, I tried command syntaxes in adb's fastboot, everything with USB debugging, nothing did anything. I can't flash either new TWRP or Revolution Recovery because the FRP lock isn't letting me flash anything, and for some reason i can't relock bootloader. I have correct unlock code, command line syntaxes just failed and p9toolkit produced errors saying that my unlock code is wrong (which is not true, I checked at huawei's site) or my phone is locked/unlocked depending on me trying to lock it or unlock it.
Even the built in recovery fails to get the package when I try to restore with it.
The boot message that "my device can't be trusted" is of course still present.
Feeling defeated I did a factory reset along with both wipes, hoping that'll let me change OEM lock in dev options and will clean the phone of many root related settings, but OEM lock is still greyed out.
Basically it seems the phone is locked in some kind of limbo of having bootloader unlocked but locked when you try to flash anything, because of FRP, and I can't relock to unlock FRP...and so on.
I would be extremely grateful if someone could help with sorting this out, basically I only want root, but it's just a mess overall.
Did you already try to dload an UODATE.APP file? If not:
1) create a folder on your external SD card named DLOAD
2) Download your firmware's update.zip file and extract it
3) put the extracted update.app file in the dload folder
4) boot phone with volume up + volume down + power
5) this will relock bootloader, install stock Android, stock recovery, stock boot (basically make every single thing stock) do you can start over again by rooting nougat!
I did not try it because I have no idea how to find the correct firmware for my phone, I have used the firmware finder from xda but the amount of results pretty much overwhelmed me so I didn't try anything with it, as i would probably get my situation worse.
EDIT: i found this site http://hwmt.ru/oth/HWFF/info/view.php?find_model= and there is update.zip of seemingly the same version as mine, is this the correct file http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v87119/f2/full/update.zip?
Hi all
I got my hands on a P9 lite running nougat, not locked to any mobile network.
I want to root it, and followed some threads on here to make this happen. I managed to unlock the bootloader, and transfered TWRP img on the device. Next step would be to reboot in recovery mod to flash it, but said recovery mode only give me the option to connect to wifi/a server.
eMUI 5.1 is running on the device as far as I know. I'm quite probably missing something here, anyone could point me in the right direction?
Dev mode activated, USB debug mode on, OEM unblocked, bootloader unlocked. Next and final step is to transfer the img locally, restart in recovery to then flash it. But no no, too simple
Many thanks
Tetsuo308
I've been using custom ROMs for a while on my A2017G but decided to get back to stock. Before doing all the bootloader unlocking/rooting etc I backed up my original firmware (Nougat, B09). So I reinstalled the original firmware that I had backed up but somehow lost TWRP in the process (the bootloader is still unlocked). I then used Axon 7 Toolkit to re-install TWRP. Unfortunately I cannot get to bootloader mode through Android Recovery as it reboots normally. Axon 7 toolkit gives me the following notice 'If your device rebooted normally then your device has no access to fastboot. Follow the miflash instructions for the bootloader unlock option to restore your device's fastboot mode'. The thing is the phone is bootloader unlocked so I don't need to unlock again.
Basically, I cannot install TWRP through bootloader mode. I also tried adb-fastboot tool from my Pc but same thing happens, phone reboots normally.
What I really wanted is bring back the phone to full stock, including re-locking the bootloader.
I also want to have the bootloader re-locked again before selling the phone.
Any help/ suggestions much appreciated.
Good lord, don't use the Q&A mode for a simple question. XDA Labs opens it on a browser window
Follow Controllerboy's guide, but only the part where he installs TWRP with axon7tool. After that, boot into TWRP and follow raystef66's guide on how to get rid of the 5 seconds screen. That'll give you fastboot. Then flash a full stock system, stock recovery, and you'll probably be safe enough to relock
But I'd ask the next owner if he/sge actually cared on having the bootloader unlocked. Relocking it is risky as $hit you know.
Sorry, am kind of new and was not sure which way to post my comment. Thank you for responding and the advice. I managed to install full stock, actually downgraded to Marshmallow so I can get to fastboot/bootloader mode now. Thanks again.
You can still have bootloader mode on Nougat if you follow raystef66's guide. Plus it will hide the 5 secs screen
Actually I discovered I can't get into Fastboot mode from stock marshmallow so guess it's back to nougat with raystef66's guide.
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
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