Guys, is there anybody please, who can help me with getting Device ID through Fastboot? I can't get it alone without your help, trying it half a day without any success.
I am doing it step by step with LG official guide http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryId=CTULRS0702 , but I can't get much far.
My problem is, that when I am rebooting using "adb reboot bootloader", the device will reboot, after that, I type "fastboot oem device-id" and than, I am stucked at < waiting for any device >. Tried that on 2 WIN PCs and on 1 Macbook Pro, but without any luck, everywhere same thing happens...can you please help me, what can be wrong, what should I do differently or what am I doing wrong?
Thank you very much.
TomasDrabek said:
Guys, is there anybody please, who can help me with getting Device ID through Fastboot? I can't get it alone without your help, trying it half a day without any success.
I am doing it step by step with LG official guide http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryId=CTULRS0702 , but I can't get much far.
My problem is, that when I am rebooting using "adb reboot bootloader", the device will reboot, after that, I type "fastboot oem device-id" and than, I am stucked at < waiting for any device >. Tried that on 2 WIN PCs and on 1 Macbook Pro, but without any luck, everywhere same thing happens...can you please help me, what can be wrong, what should I do differently or what am I doing wrong?
Thank you very much.
Click to expand...
Click to collapse
Not sure why you need the device ID.
See the WTF bootloader unlock Instructions THREAD and unlock bootloader, install TWRP and root -- without having to receive permission from LG.
What you're trying to do (get unlock code from LG) is no longer necessary.
Since you already have H930, just go to that thread and fastboot flash the new_unlock.bin code provided.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Not sure why you need the device ID.
See the WTF bootloader unlock THREAD and unlock bootloader, install TWRP and root -- without having to receive permission from LG.
What you're trying to do (get unlock code from LG) is no longer necessary.
Since you already have H930, just go to that thread and fastboot flash the new_unlock.bin code provided.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Well, thank you for your reply..tried the step by step guide from the topic you mentioned, but my problem persits..there is some problem with my PC/phone/FASTBOOT command, because it looks like the PC can´t see the phone in the bootloader mode. I typed "adb reboot bootloader", it works well, but than, when I had to type "fastboot flash unlock new_unlock.bin", same < waiting for any device > on command line keep stucked and nothing more happened.
TomasDrabek said:
Well, thank you for your reply..tried the step by step guide from the topic you mentioned, but my problem persits..there is some problem with my PC/phone/FASTBOOT command, because it looks like the PC can´t see the phone in the bootloader mode. I typed "adb reboot bootloader", it works well, but than, when I had to type "fastboot flash unlock new_unlock.bin", same < waiting for any device > on command line keep stucked and nothing more happened.
Click to expand...
Click to collapse
In the WTF Instructions (Section 7) there are a dozen Trouble Shooting tips. Almost all deal with ADB issues.
Try another (different) source for ADB installation.
Try different USB port, different USB cable, different computer.
That's just a few. See the WTF Instructions Section 7 for all of them and try them all.
TomasDrabek said:
Well, thank you for your reply..tried the step by step guide from the topic you mentioned, but my problem persits..there is some problem with my PC/phone/FASTBOOT command, because it looks like the PC can´t see the phone in the bootloader mode. I typed "adb reboot bootloader", it works well, but than, when I had to type "fastboot flash unlock new_unlock.bin", same < waiting for any device > on command line keep stucked and nothing more happened.
Click to expand...
Click to collapse
There could be an issue with your fastboot drivers. I was also unable to get fastboot commandant to work on my laptop but it worked just fine on my desktop.
After getting root I did try a reinstallation of windows on my laptop and was able to get fastboot to work fine on my laptop though; so if all else fails, including reinstalling fastboot drivers a windows reinstall may help.
I used the adb and fastboot from here https://forum.xda-developers.com/showthread.php?t=2588979
So I figured out what the problem was: when using an original OEM USB-C cable from the box, everything worked great and now I am installing TWRP and trying to root phone...hoping that everything will go through without any problems. In the meantime, thank you all for your answers guys:
TomasDrabek said:
So I figured out what the problem was: when using an original OEM USB-C cable from the box, everything worked great and now I am installing TWRP and trying to root phone...hoping that everything will go through without any problems. In the meantime, thank you all for your answers guys:
Click to expand...
Click to collapse
So "different cable" was the answer.
Exactly
My phone is already rooted (mainly for Adaway), so now, I am 100% satisfied. Thanks a lot.
ChazzMatt said:
Not sure why you need the device ID.
See the WTF bootloader unlock THREAD and unlock bootloader, install TWRP and root -- without having to receive permission from LG.
What you're trying to do (get unlock code from LG) is no longer necessary.
Since you already have H930, just go to that thread and fastboot flash the new_unlock.bin code provided.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Me for example, I wouln't like to DOWNGRADE my phone - which is neccessary with the way you suggest.
For me changing USB port in the PC does nor help. And i'm using the original cable from the box.
Have the same problem.
Specs: Lg v30+ Lgh-H930DS rev 1.1
Martinezz123 said:
Me for example, I wouln't like to DOWNGRADE my phone - which is necessary with the way you suggest.
For me changing USB port in the PC does nor help. And i'm using the original cable from the box.
Have the same problem.
Specs: Lg v30+ Lgh-H930DS rev 1.1
Click to expand...
Click to collapse
Go HERE and read about rooting your V30:
ROOT Your LG V30!
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
Read POST #1.
It will give you an overview of what you need to do and direct you to the WTF Instructions thread.
If you read the that post or even the WTF Instructions, you would understand you are merely TEMPORARILY downgrading to early Oreo to have access to the WTF bootloader unlock exploit. After that you are urged to update back to newer firmware (at least last Oreo, if not Pie).
You are aggravating me. You keep posting in many old threads instead of going to the threads I keep telling you to go to.
Go read all my answers to your questions today and please post in relevant thread I am pointing you to over and over. Is there something about the attached screenshot you cannot read or comprehend? I have posted that link several times now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the WTF Instructions thread (Section 7) are over a dozen Touble Shooting tips. You have only mentioned two that I happened to reference here. The full list is in the WTF Instructions.
I understand uou are upset but I can't go through all the pages in a long therad to uncover one answer to a simple problem which sould be explained at the beggining in the first place.
Im' lookng for the simplest metod, and the one from LG seems the most easygoing.
Why can't I get the phone to show me its ID?
It's not the problem of that other topic isn't it?
Martinezz123 said:
I understand uou are upset but I can't go through all the pages in a long therad to uncover one answer to a simple problem which sould be explained at the beggining in the first place.
Im' lookng for the simplest metod, and the one from LG seems the most easygoing.
Why can't I get the phone to show me its ID?
It's not the problem of that other topic isn't it?
Click to expand...
Click to collapse
I'm upset because you're not listening. The answer is EASY.
Yes, it's easy to to bootloader unlock and root the H939DS. But you have to read the WTF Instructions and follow them.
I've given you the link several times.
ALL H930DS bootloader unlocked and rooted HAD to follow those WTF instructions, which I wrote. There is no other method.
Until you unlock your Bootloader and Root, any other questions you ask from any other thread than the WTF INSTRUCTIONS thread, I will ignore because that means you don't actually want help.
___
No one is asking you to go through an "entire thread" for instructions you need to read. If you think that, then you are failing to read basic sentences. You need to read the WTF INSTRUCTIONS and follow them. PERIOD.
_____
You don't need the Device ID whatsoever for bootloader unlock and root. So that's a totally irrelevant question. Which means you aren't paying attention to my answers.
____
I've answered your questions repeatedly and you are not following the simple answer being given.
Seems like you've just ignoed what I said bat anyway I'll manage it by myself.
thanks.
Related
Hey guys,
This one really has me stumped and I need some help. I have 5 Xiaomi Redmi Note 3 Pros - we're starting to use these at work. I bought two first to trial with, and they worked awesome on CM, and it was easy to unofficially unlock. I used this method. The next batch simply won't work with exactly the same process. I flash the device with 7.1.8.0 Global and the modified bootloader and whilst the flashing process goes OK, the device does not boot into MIUI afterwards. It flashes the MI logo twice, then shuts off. Plugging in the PC results in a blinking red light. Fastboot works, and I have been using that to reboot to EDL mode to try and fix it, but that's about it. Soft bricked.
So far I've tried both the original unofficial bootloader and the updated one from here and they both result in exactly the same behavior, both on Global ROM 7.1.8.0 and 7.3.6.0. Omitting this modified bootloader will result in the system being bootable on stock MIUI, but that's not what I want.
If I boot into fastboot and try to unlock the bootloader I get the following error: "FAILED (remote: oem unlock is not allowed)".
Has Xiaomi blocked unofficial unlocking or modified bootloaders via a hardware update? It's the only thing I can think of since I have two Xiaomi Redmi Note 3 Pros that worked flawlessly with this method (although I suspect they were slightly older stock). Is there any way around this? I have another 13 phones on the way and I don't really want to make 15 Mi accounts to unlock officially.
Why can't you unlock different phones on the same account?
razr96 said:
Why can't you unlock different phones on the same account?
Click to expand...
Click to collapse
Last time I checked it was one phone per month per account. Also, it takes ages, and doesn't always work (but neither does the unofficial unlock as I'm now discovering).
stephendt0 said:
Last time I checked it was one phone per month per account. Also, it takes ages, and doesn't always work (but neither does the unofficial unlock as I'm now discovering).
Click to expand...
Click to collapse
Well i can unlock an unlimited number of times on my account.
This is news to me... I'll try that then. Last time I tried official unlock it got to 50% and froze, so that's why I was trying to do the unofficial unlock. It also takes ages to get the code.
I'd still like to be able to unlock unofficially though.
stephendt0 said:
Hey guys,
If I boot into fastboot and try to unlock the bootloader I get the following error: "FAILED (remote: oem unlock is not allowed)".
Click to expand...
Click to collapse
I'm having the exact same issue!
I also tried to switch between stable MiFlash and XiaoMi Flash beta.
Yeah its really frustrating. I love these phones, but the bootloader unlock process is pure hell.
I found the solution:
Boot into a working ROM (e.g. 7.1.8 global)
1) Enabled Developer options
2) enable USB debugging
3) enable OEM unlocking (how could I miss this!?!)
After that you can flash the modified fastboot rom and unlock the bootloader.
Voila
I'll test this later and report back. I have a sneaky feeling it might not work...
Alright, an update.
Just before I went to do the unofficial unlock, I got a confirmation code saying that I am able to unlock officially. I tried this on one of my phones (China Dev ROM) and it worked great. I went to do the second one, and I got presented with this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Damn.
I then tried what you mentioned. Flashed stock 7.1.8.0, enable OEM unlock (it was enabled when I enabled dev options anyway...) and then rebooted to fastboot. I then tried to flash the emmc_appsboot.mbn file from fastboot... no luck. I get "FAILED (remote: device is locked. Cannot flash images)", which is no surprise since the device still has a locked bootlaoder. I then thought alright, well I have the ROM installed with OEM unlock enabled, lets try booting to EDL mode and flashing the ROM with the modified bootloader but without wiping data. I did that, and no luck - just flashes the Mi Logo twice and shuts off. Gah! There's something special about these phones. They must be running a new hardware revision that prevents modified bootloaders from being installed. The only way I can think of unlocking a bunch of phones is to create a heap of different Xiaomi accounts and use the official unlock method, but that is a major hassle!! Really frustrated about this situation. Anyone able to offer some insight?
stephendt0 said:
Alright, an update.
Just before I went to do the unofficial unlock, I got a confirmation code saying that I am able to unlock officially. I tried this on one of my phones (China Dev ROM) and it worked great. I went to do the second one, and I got presented with this error:
Damn.
I then tried what you mentioned. Flashed stock 7.1.8.0, enable OEM unlock (it was enabled when I enabled dev options anyway...) and then rebooted to fastboot. I then tried to flash the emmc_appsboot.mbn file from fastboot... no luck. I get "FAILED (remote: device is locked. Cannot flash images)", which is no surprise since the device still has a locked bootlaoder. I then thought alright, well I have the ROM installed with OEM unlock enabled, lets try booting to EDL mode and flashing the ROM with the modified bootloader but without wiping data. I did that, and no luck - just flashes the Mi Logo twice and shuts off. Gah! There's something special about these phones. They must be running a new hardware revision that prevents modified bootloaders from being installed. The only way I can think of unlocking a bunch of phones is to create a heap of different Xiaomi accounts and use the official unlock method, but that is a major hassle!! Really frustrated about this situation. Anyone able to offer some insight?
Click to expand...
Click to collapse
Hey, after you enabled OEM unlock in the options reboot to edl and flash the ROM with the modified emmc_appsboot.mbn. After its done reboot to fastboot (Power & Vol Down) and perform "fastboot oem unlock-go". Sorry that my instructions were not clear enough.
cetchmoh said:
Hey, after you enabled OEM unlock in the options reboot to edl and flash the ROM with the modified emmc_appsboot.mbn. After its done reboot to fastboot (Power & Vol Down) and perform "fastboot oem unlock-go". Sorry that my instructions were not clear enough.
Click to expand...
Click to collapse
I don't see why that would work. I'll give it a try tomorrow anyway... have you had this exact issue before? I haven't seen it mentioned before, I did a lot of Googling before I made this thread.
stephendt0 said:
I don't see why that would work. I'll give it a try tomorrow anyway... have you had this exact issue before? I haven't seen it mentioned before, I did a lot of Googling before I made this thread.
Click to expand...
Click to collapse
The setting to "enable OEM unlock" is stored somewhere where MiFlash doesn't write during flashing.
If it is not enabled you get the error described in your first post (FAILED remote: unlock is not allowed).
You still need to edl flash the modified bootloader to unlock. Good luck
IT WORKED.
Oh my gosh. I could have sworn the "enable OEM unlock" option was active the entire time I was trying to unlock the bootloader, but nope. I must have forgot the first time around. The guide doesn't mention that this is necessary, although the screenshot indicates that it was enabled for them. It must have been turned on by default on some phones and turned off on some other phones. That must have been it. For some reason I also thought the system would be able to boot up with the modified locked bootloader, so I thought there was a problem there when it turned itself off.
In the end it was really simple:
Boot into stock ROM, enable "Enable OEM Unlock"
Reboot to EDL mode.
Flash ROM with modified bootloader
Reboot to fastboot
Unlock bootloader
Alright, consider it solved. And I feel like a massive idiot. Thanks! At least if someone else has issues with this they can at least know now that it was something silly :silly:
Hey,
What was causing the problem? Im trying to unlock bootloader from couple of days and I have no idea what to do now. I checked dev settings and enable OEM unlock every time when im trying to flash ROM with modified bootloader and every time: (FAILED remote: unlock is not allowed).
Do all in 64 bit windows then go to advance option n select raw and patch then it will work
Not works on marshmallow works on lollipop
Apparently VIVO phones are the black horses of the hacking community because they are near impossible to root!
Also I'm new, I hope I'm posting in the right thread.
Now onto the details, I've been trying to root my phone lately and so far absolutely nothing is working at all! I've not seen anyone whatsoever on XDA to root this specific phone. Mostly V3 and Xshot series
I've tried every single rooting app there is, but I noticed that my efforts are worthless because my phone has an impenetrable bootloader! Of course I immediately head to the internet and found about ADB and Fastboot. Now I've been trying to confirm my suspicions about a locked bootloader by using the "device-info" command on ADB, then I get
Code:
<bootloader> unlock:false
.
Now since I was trying to unlock the bootloader and to this day I absolutely CANNOT bust through it. Whenever I use the "oem-unlock" command, it will always say "FAIL: check device or oem lock"
I forgot most of the commands I used on ADB, (first time using it, actually :silly: ) but the commands I used were normally the ones used to unlock a phone's bootloader.
Going to their forums, they always say that they do not allow their users to tamper with their devices and I was this close to giving up, but after going to the phone's recovery mode, I immediately see at the bottom "The Phone: not root" (yes that's what it exactly says, that's not my grammar) which means that it SHOULD be possible to root it in the first place, and because of that I have not stopped trying.
However every last method I tried failed and I am desperate enough to come here, to XDA forums where I learned to root my now 6+ year old Samsung Galaxy Y.
I really need your help, guys.
Nagazumi said:
Apparently VIVO phones are the black horses of the hacking community because they are near impossible to root!
Also I'm new, I hope I'm posting in the right thread.
Now onto the details, I've been trying to root my phone lately and so far absolutely nothing is working at all! I've not seen anyone whatsoever on XDA to root this specific phone. Mostly V3 and Xshot series
I've tried every single rooting app there is, but I noticed that my efforts are worthless because my phone has an impenetrable bootloader! Of course I immediately head to the internet and found about ADB and Fastboot. Now I've been trying to confirm my suspicions about a locked bootloader by using the "device-info" command on ADB, then I get .
Now since I was trying to unlock the bootloader and to this day I absolutely CANNOT bust through it. Whenever I use the "oem-unlock" command, it will always say "FAIL: check device or oem lock"
I forgot most of the commands I used on ADB, (first time using it, actually :silly: ) but the commands I used were normally the ones used to unlock a phone's bootloader.
Going to their forums, they always say that they do not allow their users to tamper with their devices and I was this close to giving up, but after going to the phone's recovery mode, I immediately see at the bottom "The Phone: not root" (yes that's what it exactly says, that's not my grammar) which means that it SHOULD be possible to root it in the first place, and because of that I have not stopped trying.
However every last method I tried failed and I am desperate enough to come here, to XDA forums where I learned to root my now 6+ year old Samsung Galaxy Y.
I really need your help, guys.
Click to expand...
Click to collapse
Can u plz give me ur num
I have Vivo Y55l (1603). I am unable to root this device
I have Vivo Y55l (1603). I am unable to root this device. Please tell me appropriate method for rooting this device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i unlock bootloader and flash twrp recovery
but not boot
guide :
qiurigao said:
View attachment 4129802
i unlock bootloader and flash twrp recovery
but not boot
Click to expand...
Click to collapse
Any chance you can tell me how you did this.
Rakesh37187 said:
Any chance you can tell me how you did this.
Click to expand...
Click to collapse
add my google talk: [email protected]
or QQ:1239120048
Same problem
Is there any way to root this phone or not?? Tried everything and every root app feeling so low please someone help *=*
OEM Unlock In Developers Options?
Did You Turn On The OEM unlock in Developers Option??
James480 said:
Did You Turn On The OEM unlock in Developers Option??
Click to expand...
Click to collapse
没有用
qiurigao said:
没有用
Click to expand...
Click to collapse
好的,我猜那么
qiurigao said:
没有用
Click to expand...
Click to collapse
Everyone plz join this Telegram Group for further development
Vivo y55
https://t.me/vivoy55Development
are you able to unlock it
Tandyeyd said:
are you able to unlock it
Click to expand...
Click to collapse
plzz tell me how to root vivo y55l (1603)
divu jadeja said:
plzz tell me how to root vivo y55l (1603)
Click to expand...
Click to collapse
y55 dont root
It offered to boot as flashed...if you tapped power, I suppose.
Would it just loop into the notice, and not boot the TWRP recovery if you pressed a hardware key (power, say?) Good effort, keep freeing the MSM8974!
Lugralunoogos said:
Would it just loop into the notice, and not boot the TWRP recovery if you pressed a hardware key (power, say?) Good effort, keep freeing the MSM8974!
Click to expand...
Click to collapse
yes
Unlock Vivo bootloader
Vivo phones bootloader can be easily unlocked with modified fastboot binary
Here's the xda thread with downloads
How to root vivo y71
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The LG G6 H870 for the European market and the USA carrier-free US997 can now be officially unlocked through LG's developer unlock program.
Your H870 is from outside Europe? You have a H871/2/3/etc or H870K/DS/etc? That's not a European H870, won't work. Your US997 tied to a carrier? Won't work.
Please read the FAQ and use the thread search feature before asking questions.
This thread is a work in progress and actively being updated.
LG Developer Unlock Site Here
Prerequisites:
European LG G6 H870 or USA carrier-free US997
Computer w/ADB & Fastboot. ADB/Fastboot for Windows here. ADB/Fastboot for Linux/OS X here.
Basic knowledge of ADB, Fastboot and Windows command prompt or Linux/OS X terminal.
Device IMEI. This 15-digit code can be found on your box, the settings menu or by dialing *#06#
LG developer account -- sign up for free by clicking the "Start Unlocking the Bootloader" button at the bottom of the LG site HERE.
Directions:
LG's official bootloader unlock directions can be found here but I've still rewritten the steps out below while revising some things and also adding steps for TWRP and root.
1. Enable USB-Debugging on your phone. USB-Debugging is required for the adb commands to work. To enable USB-Debugging, go to Settings >> About phone >> Software info and tap Build number until it says you are now a developer. Return to the previous screen, select Developer Options and enable USB-Debugging (this option may be greyed out if you have your USB cable plugged into your phone).
2. Enable OEM unlock on your phone. To enable OEM unlock, go to Settings >> Developer options and toggle/turn on Enable OEM Unlock.
3. Open CommandPrompt or Terminal and enter the following ADB command to reboot into the bootloader:
Code:
adb reboot bootloader
If ADB is not detecting your device try switching your phone's USB mode from Charging to MTP or PTP. If using Windows please make sure you've installed LG's USB drivers. You can download them HERE.
Alternatively, you may be able to boot into fastboot without ADB by powering off the phone then power the phone on while holding Volume UP (USB cable will need to be removed otherwise it may boot into LG Download Mode)
4. Once in the bootloader, use the following fastboot command to obtain Device ID:
Code:
fastboot oem device-id
Fastboot command will return a string. This is the Device ID which is needed to generate your unique unlock key.
Example :
Code:
$ fastboot oem device-id
(bootloader)-----------------------------------------------------------------
(bootloader) Device-ID
(bootloader) CD58B679A38D6B613ED518F37A05E013
(bootloader) F93190BD558261DBBC5584E8EF8789B1
(bootloader)-----------------------------------------------------------------
To generate your unlock key, you will need to paste together the 2 lines of output into one continuous string without "(bootloader)" or spaces. In the example above, the Device ID would be:
CD58B679A38D6B613ED518F37A05E013F93190BD558261DBBC5584E8EF8789B1
5. Copy Device ID and IMEI into the LG Developers Bootloader Unlock site and hit the confirm button. In a few moments the unlock.bin will be emailed to you. Download unlock.bin to computer.
6. While the phone is still in fastboot enter the following command to unlock the bootloader:
This will unlock your bootloader AND factory reset your device wiping all data!
You can use the LG Backup app or LG Bridge to backup and restore your data before unlocking the bootloader.
Code:
fastboot flash unlock unlock.bin
7. You can now reboot the phone and boot into your bootloader unlocked device! Enter:
Code:
fastboot reboot
8. Want TWRP or root?
For TWRP you will need to download the TWRP H870 image. Current unofficial TWRP build is available HERE. (thanks to @Rashed97)
For root you will need to download either SuperSU or Magisk and then flash either of the zips using TWRP.
Reboot back into the bootloader
Code:
adb reboot bootloader
(you'll have to first re-enable USB debugging since data was wiped after the bootloader unlock)
or power off again.. unplug the USB cable then power on the phone while holding Volume UP.
9. Flash TWRP:
Code:
fastboot flash recovery twrp.img
After flashing TWRP unplug the USB cable and power off the phone (hold volume down + power button).. continue holding until phone reboots...
As soon as you see the LG logo on the screen.. let go of the power button then quickly press it again (never letting go of volume down).
Keep holding until you see the Factory Reset screen. Click thru the factory reset screens using the volume buttons to move up/down and power button to select. Choose "Yes" twice until it boots into TWRP. Despite what the screen says it won't actually factory reset/wipe your data... as long as you've installed TWRP. If stock recovery is installed it WILL wipe data.
For TWRP to "stick" you must 1st boot into TWRP and not boot back into Android until after doing one of the following...
flashing SuperSU/Magisk
deleting the recovery-from-boot.p file from the /system directory
flashing the no-verity-opt-encrypt-4.1 or android-boot-repack zips
10. Now you can flash your root zip of choice.
Feel free to back up first.. but otherwise.. time to install SuperSU/Magisk. Reboot into system when finished.
Have fun and be careful.
FAQ:
Q: I have an H870 but it is not a European H870... can I unlock the bootloader?
A: No, this official unlock program is ONLY for the H870 model for countries in Europe just like LG did for the LG G4 and G5.
But... for about a 10 day span G4 devices from SE Asia worked with the official site and users received unlock.bin files.. despite that variant never showing up on the supported list. So you never know what can happen until you try and submit your device-id/IMEI into the LG Developer Bootloader Unlock site. :good:
Q: Will more devices be added?
A: Impossible to say what will happen in the future.. we must wait and see. The LG G5 bootloader unlock program was originally only open to the European H850 but months later the H840 G5SE and the USA RS988 G5 were added to the program.
Q: I can't get my phone to show up with ADB or Fastboot, watdo?
A: Make sure ADB/Fastboot is properly setup for your OS... udev rules setup in Linux.. LG USB drivers installed for Windows... OS X/MacOS just works. Also, confirm USB debugging is enabled.
ADB still not working?... try changing the phones USB modes.. from maybe charging to MTP.. or MTP to PTP.
Q: What happens to warranty if I unlock or root?
A: YMMV I suppose. The official LG site claims that warranty is void if damage is caused by the unlock. On the T-Mobile G6 there is now a bootloader unlock counter. I will assume this counter is also on the H870/US997, so it will be hard to hide the fact that you unlocked the bootloader. Please share any unlocked bootloader LG G6 warranty replacement stories in this thread.
Q: Can I re-lock the bootloader?
It IS possible to re-lock the bootloader with the the command: fastboot oem lock
You'll have to boot back into the bootloader (adb reboot bootloader) to issue the fastboot command.
Re-locking the bootloader WILL wipe data just like the unlock process. Use LG Backup app/LG Bridge or another backup method first if you want your data.
Flashing a KDZ in LGUP or LG Bridge will NOT relock the bootloader.
DO NOT re-lock the bootloader if you have a modified boot/system img... restore them to stock first or you will not be able to boot into android after the lock and need to flash a KDZ in download mode.
Q: So many words... yudodat?
A: Here is a video on how to unlock the G4... up until the 6minute mark it is step-by-step 100% the same as G6. Only slight difference is when you get to the TWRP/root steps. https://www.youtube.com/watch?v=O64GfQORCaE
Click to expand...
Click to collapse
y u quote OP?
Follow me on twitter for future updates on LG-related things - twitter.com/@utoprime
Find this thread helpful? Hit the Thanks button!
Feeling extra generous? Consider donating to me.
Thanks autoprime, keeping an eye out for us G6 owners in the rootless wasteland ☺
(As a VS988 owner I know I'm really stuck in purgatory, but can always hope ? It was time to finally upgrade from my G3 - you did awesome work on that phone, hugely appreciated by many.)
Donated.
Oh yeah. Real theming can start...
Sent from my LG-H870 using Tapatalk
Great news ! I was really missing adblock and Xposed DPI tweaks (with such a big screen)
Did someone already flash TWRP ?
Will try it out on a H870DS eventually and see if it works. Thank you very much!!!
Don't think there is TWRP at present, its coming though.
unlock.bin sitting in my Inbox...
Looks like TWRP will be available in a few days...
Big up to all !
So my guess is that the unlock.bin would be device specific?
I've got the H870, but from ZAF...
You guess right. The file is obtained from the LG Bootloader Unlock Site, and is based on your device-id.
What is the exact model you have in System Settings -> About -> Hardware info ?
Mine is just LG-H870.
Maybe you get the Euro version in ZA ?
zEar said:
You guess right. The file is obtained from the LG Bootloader Unlock Site, and is based on your device-id.
What is the exact model you have in System Settings -> About -> Hardware info ?
Mine is just LG-H870.
Maybe you get the Euro version in ZA ?
Click to expand...
Click to collapse
Mine also just says LG-H870
The IMEI is hardware bound right?
Edit: Reason i'm asking is that i've tried the site and says "Unfortunately, your device(South Africa, (SOUTH AFRICA) )does not support unlocking the bootloader."
I wonder if installing the EU firmware will work?
Awesome!
thanks a lot, is time to mod
Without twrp we haven't make nothing.......
Enviado desde mi LG-H870 mediante Tapatalk
Finally , I have an H870, how can I know if it's the European model?
tried it with the (h870s) and it said that the device is not supported, will it ever be supported?
What about root is it working?
Well this is brilliant news, just upgraded to the G6 and it'll arrive later today so looking forward to future roms for this device.
isaakmg said:
Without twrp we haven't make nothing.......
Enviado desde mi LG-H870 mediante Tapatalk
Click to expand...
Click to collapse
this is gonna be easy
scabs said:
Mine also just says LG-H870
The IMEI is hardware bound right?
Edit: Reason i'm asking is that i've tried the site and says "Unfortunately, your device(South Africa, (SOUTH AFRICA) )does not support unlocking the bootloader."
I wonder if installing the EU firmware will work?
Click to expand...
Click to collapse
Yes the IMEI is flashed somewhere in the hardware, and IMEI ranges are allocated by regions.
An EU firmware could work, but wouldn't change you IMEI.
Sorry for you, you'll have to wait for an unofficial way to unlock the bootloader if it is ever found...
Well, we EU LG G6 users may not get Quad-DAC, 64Gb of storage or wireless charging but we at least get this (which is better than anything).
This should take you from the LG "Unlock Bootloader" form through to a fully-functional rooted TWRP'd device. This process wasn't quite as well documented as I would like, so I decided to take a shot at it. I don't guarantee any of this; it's all at your own risk. All props should go to those who went first. I merely got lost trying to follow and so built a map.
Ideally you want an “external” microSD card for this.
This also assumes you have already filled out the LG form and received the unlock.bin file. If not, retrieve it from LG using the tricks in this thread.
You also will want the twrp-3.1.1-0-h930.img image or the US998 TWRP unofficial alpha based on it. (They're the same except for a properties file change.)
And you need the Android development tools installed. I'm assuming you've done that.
1. Back up everything. It’s all going away.
2. If running Android Studio or Helium Desktop, shut it down. Otherwise you may see adb version issues.
a. Side-note: Don’t trust Helium to let you restore your data. Look for “Helium ceases to recognize backups” at https://github.com/koush/support-wiki/wiki/Helium-Wiki - It’s simply the wrong tool for this job.
3. Before you begin, copy the following files to your External SD Card. Otherwise you’ll have to do it later or attempt an adb sideload:
a. Magisk-v15.3.zip
b. no-verity-opt-encrypt-6.0.zip
c. (Optional)LG-rctd-disabler-1.0.zip4. Ensure you’re in developer mode. If Settings doesn’t have Developer Options, go to Settings – About Phone – Software Info, click Build number 7 times.
5. As per the LG page, http://developer.lge.com/resource/mobile/RetrieveBootloader.dev , ensure Developer Options “OEM Unlock” and “USB Debugging” are enabled.
6. Connect to USB and switch to Photo Transfer Mode. (If you’re a normal user, you probably default to USB. You need Photo.)
7. On your PC, copy the unlock.bin file LG emailed you into your Android development tools directory (in my screenshots, sdk\platform-tools), and run:
adb devices
to ensure the device (and only the device) is listed. If it’s not listed, verify that Photo Transfer mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8. Reboot phone into Fastboot mode
adb reboot bootloader
You should hear the Windows sounds of USB devices going and coming. And the phone has an odd screen.
9. From the same directory (Android tools),
fastboot flash unlock unlock.bin
This takes only a few seconds to run.
10. Reboot with:
fastboot reboot
You will get entirely different start-up screens than normal. Including a warning that your device cannot be checked for corruption. (and a reference to http://g.co/ABH)
Your phone has now been hard reset.
11. Go through the initial phone setup options, to get to Android. Switch USB to Photo Transfer again.
12. You can verify that it’s unlocked either from the Developer Options – OEM Unlock is no longer available because it’s already unlocked, or by:
Installing TWRP:
1. Switch back to developer mode, USB debugging. (OEM Unlock is now not selectable, because it's on permanently.)
2. Switch USB to Photo again; default is charging.
3. As before, on your PC from the Android tools directory,
adb reboot bootloader
4. Fastboot flash recovery twrp-3.1.1-0-h930.img
5. This part is tricky… read the whole thing before starting.
a. Turn OFF the phone, using the volume key to change from Restart at the top to “Power off”.
b. Disconnect the USB cable
c. Holding both the Volume-Down and Power button, turn phone on.
d. As soon as the LG logo appears, continue pressing “Down” but release and re-press Power. Continue holding both until a menu appears.
e. Select to erase all data. You will be asked this several times; keep saying “Yes”.
f. Eventually you will boot into TWRP.6. Back up the system. This isn’t essential, but you’d be silly not to.
a. In TWRP, set system writable
b. Select “back up”. Note there’s no data, because that partition is encrypted.
c. Select the SD card (or USB; I use a micro SD card.)
d. Back it up. This will take around seven minutes.7. Turn off data encryption and install stuff… all in TWRP:
a. Wipe Data – Factory Reset
b. Wipe Data – Format Partition
c. Install – set storage to the External SD
d. Install the Magisk zip
e. Install the no-verity-opt-encrypt-6.0.zip
f. Install the LG-rctd-disabler-1.0.zip; this reduces LG root checks, which may impede performance.
g. Reboot – to SystemIf booting fails with an encryption error, did you format (b above) the partition? If not, reinstall TWRP (except you don't need to backup again) and do both the wipe and format.
You will now have to set up the phone again, but should have root (via Magisk.)
EDIT: This has been added to the steps above.
_______
Good write up, but please add the "don't check root" file. It would go into the section where you flash the no verity file.
LG-rctd-disabler-1.0.zip
https://build.nethunter.com/android-tools/lg-rctd-disabler/
Recently, we discovered a system module on many LG devices which scans for root access. Called*RCTD, the tool is activated whenever an LG phone running stock-based software has been rooted. This has led to device slowdowns (as the process never shuts down) and also has left some users feeling uneasy about it as well.
we can now disable this check with a simple application
Click to expand...
Click to collapse
A lot of people are already using it when flashing TWRP with the phone.
_____
ANOTHER EDIT:
After installing TWRP, it's a good idea to download TWRP Manager from the Play Store.
From that app, you can easily reboot into TWRP without doing the power/volume button dance. In the app's settings, change app start up screen to be reboot options. That way, every time you open the app, that's the immediate option you can choose.
Sent from my official carrier unlocked LG V30+ US998
Now that the US998 is unlocked and rooted. Has anyone tried to get that secret T-Mobile menu working to see if band 71 can be enabled?
ChazzMatt said:
Good write up, but please add the "don't check root" file. It would go into the section where you flash the no verity file.
Click to expand...
Click to collapse
I wasn't even aware of it! Good reason for the write-up.
US998?
Is this safe for US998? Just asking since the TWRP file says it is for H930.
One question. Works on every firmware or only on 10f?
crothlisberger said:
Is this safe for US998? Just asking since the TWRP file says it is for H930.
Click to expand...
Click to collapse
Yes. We're trying to get the V30 TWRP developer @jcadduonoto change the TWRP name and the description, but he's ignoring us right now. It's compatible with US998. Been proven many times.
If the TWRP developer would edit the thread title, op, and even the file properties it would eliminate a lot of confusion. For instance, doesn't need show H930 when plugged into your PC in TWRP mode. I don't have an H930, I have US998. It could easily say "V30" or "JOAN" (the LG code name for this device).
It's just the H930/H930G was placed on LG Developer Bootloader Unlock list back in December. We're playing catch up to them.
Sent from my official carrier unlocked LG V30+ US998
Dizzyrul3z said:
One question. Works on every firmware or only on 10f?
Click to expand...
Click to collapse
Some have problems with any other firmware than 10f on the H930, personally i dont have problems with 10f or 10v, didnt try 11m yet.
Dizzyrul3z said:
One question. Works on every firmware or only on 10f?
Click to expand...
Click to collapse
What's 10f? I have 10c.
This is my rooted US998 with TWRP.
Sent from my official carrier unlocked LG V30+ US998
Thanks
Thanks for gathering all this together. Was able to follow the steps last night and am up and running rooted now.
Additional information - As the guide states, it uses Magisk however SuperSU also works fine for root.
Thanks @Wotta for the write-up.
Disclaimer : And yes...Understand with different root comes advantages / disadvantages.
vinniej said:
Additional information - As the guide states, it uses Magisk however SuperSU also works fine for root.
Thanks @Wotta for the write-up.
Disclaimer : And yes...Understand with different root comes advantages / disadvantages.
Click to expand...
Click to collapse
That is good to know for anyone who doesn't like to use the one from the person who stole code from Chainfires hard work.
Do Wifi calling and HD voice and video work with the rooted US998? I have had the VS996 since late October and although I love the phone, I really miss having a rooted device (mostly for nandroid backups, but also for ad blocking).
Does this work for the V300L?
jake2447 said:
Thanks for gathering all this together. Was able to follow the steps last night and am up and running rooted now.
Click to expand...
Click to collapse
You're welcome. I'm glad it was clear.
BobberK said:
Does this work for the V300L?
Click to expand...
Click to collapse
Read paragraph #2 of the op:
Wotta said:
This also assumes you have already filled out the LG form and received the unlock.bin file. If not, retrieve it from LG using the tricks in this thread.
Click to expand...
Click to collapse
Are you able to get bootloader unlock.bin from the LG Developer Bootloader Unlock list website?
It's only for V30/V30+ that are eligible to do that.
I'm not being smart aleck. The US998 V30 is not officially listed as eligible (yet). But someone found a way to hack the dropdown list and still get US998 V30 unlock.bin. It works if you follow the right steps. The US998 V30+ SHOULD also work, but does not (yet).
So, the answer for you is probably no. But you'll have to try to get bootloader unlock.bin from the LG Developer Bootloader Unlock list website to know for sure.
Sent from my official carrier unlocked LG V30+ US998
This will not work on T-Mobile version right?
nofroyo said:
This will not work on T-Mobile version right?
Click to expand...
Click to collapse
See the answer immediately above your question. You need bootloader unlock.bin from LG.
Sent from my official open market LG US998 V30+
Will it work on Indian dual sim model i.e. H930DS. ?
Can't access TWRP
Hi guys,
I'm having a problem entering TWRP.
I unlocked my bootloader and "successfully" installed TWRP. But I can't get past step 5 (the tricky part). So after flashing TWRP I disconnect the phone from the PC and switch it off. Then as described in step 5 I access the part where I'm supposed to do the factory data reset. But once I hit yes for the second time the black-orange warning screen pops up immediately and after a few seconds the phone reboots to the normal software which is NOT completely reset.
So I just can't access the custom recovery TWRP no matter what I do or how often I try...
I would be very grateful for any help
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of incorrectly flashing your device.
Hey guys, similar to all of @Some_Random_Username's unbrick threads, here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N200 5G.
Important: This is only for the T-Mobile variant of the N200. This will not work on the factory unlocked variant and may or may not work for the Metro variant.
Downloads:
11.0.1.5.DE18CB
Original archive
Google Drive
7z format (thanks @edale1)
AnddoidFileHost
MEGA
zip format (thanks @nv270)
Rethink Files
Also available at https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Others" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Press and hold the volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
How can I check my device project ID?
Use getprop ro.boot.project_name. This however involve having ADB access or access to OxygenOS to use Termux or whatever terminal emulator you prefer.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
@Some_Random_Username for help getting files and for the mirror
@edale1 and @nv270 for repacking and mirroring the files
@nache2001 for testing the tool out on his device
OnePlus for the device and OS
@Nache and others who have the unlocked version from the oneplus store and have the bootloader locked and phone bricked .. This version will not work with your phone as i just tried it myself today .. hopefully someone gets a hold of the msmdowmload from the tech support ..
patiently waiting for the unlock
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
xentonix said:
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
Click to expand...
Click to collapse
My understanding is the T-Mobile MSM Tools will restore a T-Mobile variant phone to the state it was in coming from T-Mobile; meaning if you debloated the phone, the bloat will be back.
You can use the MSM Tools even with a locked bootloader.
If your bootloader is unlocked, I believe this will lock it. (it may SIM lock your phone again as well, unsure...)
I think the same unlock token will work, but I'm hesitant to say 'yes' without someone testing it first.
xentonix said:
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
Click to expand...
Click to collapse
1. Nope, this will revert your device back to the T-Mobile stock ROM, including all the bloatware. Thsi does not convert your device into an unlocked variant.
2. This works whether your bootloader is locked or unlocked. If your bootloader is unlocked, using this tool will lock it again, and you will need to unlock it by flashing unlock_code.bin again.
edale1 said:
My understanding is the T-Mobile MSM Tools will restore a T-Mobile variant phone to the state it was in coming from T-Mobile; meaning if you debloated the phone, the bloat will be back.
You can use the MSM Tools even with a locked bootloader.
If your bootloader is unlocked, I believe this will lock it. (it may SIM lock your phone again as well, unsure...)
I think the same unlock token will work, but I'm hesitant to say 'yes' without someone testing it first.
Click to expand...
Click to collapse
lzgmc said:
1. Nope, this will revert your device back to the T-Mobile stock ROM, including all the bloatware. Thsi does not convert your device into an unlocked variant.
2. This works whether your bootloader is locked or unlocked. If your bootloader is unlocked, using this tool will lock it again, and you will need to unlock it by flashing unlock_code.bin again.
Click to expand...
Click to collapse
Thank you!
I read an article that was bit unclear and pointed to this so I wanted to confirm.
Also, from everything else I gathered, there is still no way to flash Tmob variant with non Tmob rom?
I was interested to try LineageOS but that's not available also seems like.
Phone's too new still. I think we need the MSM Tools for all the variants available before someone can figure out how to flash one variant into another, and we currently only have the T-Mobile variant's MSM Tools.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
incoming August 176 patch
I have update installed.
You can use restore image on Magisk uninstall before you start. If you encounter problem, you can use original boot image and run "mock patch"
Install update and switch to Magisk when you're prompted to restart, and let Magisk to install in unused partition, and restart after finished
If you have problem with CTS after update, install riru from Magisk and download safetynet fix, and install in Magisk as well (you have to reboot twice)
I've successful restored my N200 phone several times using the MSM, but this most recent time it appears the process was interrupted and I get the following error when turning on the phone. I can not boot the phone back into EDL mode to run MSM tool again. Every 10 or so boots the phone will boot into fastboot instead of throwing the error. I tried flashing a backed up boot.img and super.img, but no luck getting past the error. Any way to recover?
automatic ddr failed
Thank you! I could only get this to work by:
Unplug phone
Open MSMDownloadTool, don't click start
Hold down volume up and down
Plug phone into USB 2.0 port
Release volume up and down, verify device shows up as QDLOADER in Device Manager
Click "Enum" in MSMDownloadTool
Click on the device in the list and click "Start"
I got bootloader unlock code. I need SIM unlock "One Plus Nord N200 5G" by Metro. Help me!
towardsdawn said:
Thank you! I could only get this to work by:
Unplug phone
Open MSMDownloadTool, don't click start
Hold down volume up and down
Plug phone into USB 2.0 port
Release volume up and down, verify device shows up as QDLOADER in Device Manager
Click "Enum" in MSMDownloadTool
Click on the device in the list and click "Start"
Click to expand...
Click to collapse
I bricked my phone late last night and found this forum & thread; my problem was that each time my computer kept showing my phone as "Kedacom" until I scrolled through and found this post.
You guys saved my ass AND saved me a trip to T-Mobile too! I owe you guys big time!
I successfully flashed a metro-pcs device using the tool in this thread. I bricked my device using the dsu loader in developer options. "Oem unlocking" is greyed out. Can anyone point me to a good bootloader unlocking tutorial for this devicel? Is it possible to use this tool with a rom that has already been rooted? Thanks,
Noob here. One thing to note: device was not recognized in the beginning. I held vol up/down at the same time and then plugged in device. Although the screen was black, the device was shown as "connected" and had no issues flashing. After 300 secs, voila!
bleezycheesy said:
I successfully flashed a metro-pcs device using the tool in this thread. I bricked my device using the dsu loader in developer options. "Oem unlocking" is greyed out. Can anyone point me to a good bootloader unlocking tutorial for this devicel? Is it possible to use this tool with a rom that has already been rooted? Thanks,
Noob here. One thing to note: device was not recognized in the beginning. I held vol up/down at the same time and then plugged in device. Although the screen was black, the device was shown as "connected" and had no issues flashing. After 300 secs, voila!
Click to expand...
Click to collapse
You can try this tutorial. It worked for me on Tmobile, no idea about MetroPCS. Key line is
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
MSMDownloadTool wipes the entire device and relocks the bootloader if it was unlocked, it doesn't care if you're rooted.
towardsdawn said:
You can try this tutorial. It worked for me on Tmobile, no idea about MetroPCS. Key line is
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
MSMDownloadTool wipes the entire device and relocks the bootloader if it was unlocked, it doesn't care if you're rooted.
Click to expand...
Click to collapse
Thanks for the reference. It worked!
why no have msm tool for global n200 be2117,
jasmok said:
why no have msm tool for global n200 be2117,
Click to expand...
Click to collapse
OnePlus doesn't seem to want to release it.
bleezycheesy said:
Thanks for the reference. It worked!
Click to expand...
Click to collapse
no it doesn't works on metro variant