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
Related
{
"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).
Hi,
I've searched for instructions but can't find my situation.
I'd like to unroot, go back to LG stock, and lock bootloader so I can sell my LGv30 US998.
I have the actual US998 from B&H (not one that's been converted from something else).
Current build is: US99820a with March 1, 2018 Security.
Can someone let me know the procedure? I believe I'd like to go to the latest Oreo version "h" I think.
PS. I've tried to install LGUP tool, LG Flash Tool and none of them seem to detect my phone on Windows 10 from https://lgflash.com/download/ There are so many versions of all of these programs I don't know which one is correct. I've also installed the LGMobileDriver_WHQL_Ver_4.5.0.exe
So, some links to LGUP that actually works would be great.
Thanks
glhelinski said:
Hi,
I've searched for instructions but can't find my situation.
I'd like to unroot, go back to LG stock, and lock bootloader so I can sell my LGv30 US998.
I have the actual US998 from B&H (not one that's been converted from something else).
Current build is: US99820a with March 1, 2018 Security.
Can someone let me know the procedure? I believe I'd like to go to the latest Oreo version "h" I think.
PS. I've tried to install LGUP tool, LG Flash Tool and none of them seem to detect my phone on Windows 10 from https://lgflash.com/download/ There are so many versions of all of these programs I don't know which one is correct. I've also installed the LGMobileDriver_WHQL_Ver_4.5.0.exe
So, some links to LGUP that actually works would be great.
Thanks
Click to expand...
Click to collapse
follow instructions from ChazzMatt's thread, they have LG UP dual linked and the instructions to flash kdz
Thanks. He has lots of threads. Do you have a link?
I believe it's the one/main thread he maintains on how to root/unlock the phone. You'll have to do some thinking on how to go "backwards" from there, but the software and steps are all in there.
Generally speaking, it's NOT recommended to relock the BL because if the phone isn't 100% stock ROM, I believe you could end up bricking or bootlooping. I think you can leave the BL unlocked and just KDZ flash US998 and leave it unrooted (no Magisk, etc). This should look "stock" to anyone who cares to have a stock-specific phone anyway.
I'm concerned a buyer wouldn't like the opening "corruption. lock the bootloader" screen. My assumption is locking the bootloader would get rid of that... Does anyone know if that's true?
glhelinski said:
I'm concerned a buyer wouldn't like the opening "corruption. lock the bootloader" screen. My assumption is locking the bootloader would get rid of that... Does anyone know if that's true?
Click to expand...
Click to collapse
Yes, re-locking the bootloader will get rid of the warning screen. Just make sure you are 100% complete stock (all partitions) before you re-lock it. Otherwise the phone may brick itself.
Also, make sure you remove your Google account in the OS before you wipe/re-flash the phone. Otherwise it will trigger FRP and require the new user to enter the previous username and password.
I might be in the same boat here, would love to know how to just return to stock and relock bootloader (for someone who didn't make an initial backup)
How about these steps:
1) Make sure you have working ADB on your computer, including latest LG USB drivers.
2) Boot into the OS and remove your account using Settings -> General -> Accounts -> (select Google account) -> Remove account. This prevents Android's Factory reset Protection from kicking in, which otherwise would require the previous account to be re-entered after wiping the phone.
3) Go to ChazzMatt's US998 Pie KDZ thread and download and install LGUP exactly as described under How to Install Dev Patched LGUP towards the bottom of post #2. Remember to thank Chazz.
4) Download the KDZ for your current OS version (Oreo or Pie) either from the relevant KDZ ROM thread in the V30 ROM sub-forum or from LG-firmwares.com. Verify its MD5.
5) Enter Download mode: With the phone off, hold Vol Up, and plug in the USB cable that is connected to your PC.
6) Assuming you manage to get into Download mode, launch LGUP and make sure it detects the phone.
7) Flash the KDZ you downloaded using LGUP Refurbish mode. If you're on a custom ROM and/or if you want to do a particularly thorough job, you may consider FIRST flashing Nougat using LGUP Partition DL mode, THEN flashing back up to Oreo or Pie, again using Partition DL Mode.
8) After LGUP (hopefully) completes flashing the KDZ unplug the cable and let phone reboot.
9) Once (hopefully) you're booted into the OS, tap Settings -> General -> About phone -> Software info- > Build number until Developer Options are enabled.
10) Enable Settings -> General -> Developer Options -> Enable OEM unlock.
11) Turn phone off and unplug the cable.
12) With phone off, enter fastboot mode by holding Vol Down and plug in the USB cable that is connected to your PC.
13) In ADB window on computer, enter fastboot devices to verify ADB is working.
14) In ADB window, enter fastboot oem lock to re-lock the bootloader.
15) Use fastboot keys to reboot phone into OS. See that it works.
16). Run Settings -> General -> Reset -> Factory data reset. Do NOT use Master Reset (button dance) or the new user might trigger FRP/kill switch (although shouldn't happen if you removed the account previously and didn't enter it again).
17) Done. Hand off the phone to its new user.
These steps were written off the top of my head. If anybody sees glaring mistakes or omissions, then please let me know.
Note: Some carrier models cannot readily get into fastboot mode. For those you will need to convert back to stock US998 to re-lock the bootloader (using Frankenstein like when you first rooted) and THEN convert back to the carrier firmware (again using Frankenstein).
Thank you
TheDannemand said:
How about these steps:
1) Make sure you have working ADB on your computer, including latest LG USB drivers.
2) Boot into the OS and remove your account using Settings -> General -> Accounts -> (select Google account) -> Remove account. This prevents Android's Factory reset Protection from kicking in, which otherwise would require the previous account to be re-entered after wiping the phone.
3) Go to ChazzMatt's US998 Pie KDZ thread and download and install LGUP exactly as described under How to Install Dev Patched LGUP towards the bottom of post #2. Remember to thank Chazz.
4) Download the KDZ for your current OS version (Oreo or Pie) either from the relevant KDZ ROM thread in the V30 ROM sub-forum or from LG-firmwares.com. Verify its MD5.
5) Enter Download mode: With the phone off, hold Vol Up, and plug in the USB cable that is connected to your PC.
6) Assuming you manage to get into Download mode, launch LGUP and make sure it detects the phone.
7) Flash the KDZ you downloaded using LGUP Refurbish mode. If you're on a custom ROM and/or if you want to do a particularly thorough job, you may consider FIRST flashing Nougat using LGUP Partition DL mode, THEN flashing back up to Oreo or Pie, again using Partition DL Mode.
8) After LGUP (hopefully) completes flashing the KDZ unplug the cable and let phone reboot.
9) Once (hopefully) you're booted into the OS, tap Settings -> General -> About phone -> Software info- > Build number until Developer Options are enabled.
10) Enable Settings -> General -> Developer Options -> Enable OEM unlock.
11) Turn phone off and unplug the cable.
12) With phone off, enter fastboot mode by holding Vol Down and plug in the USB cable that is connected to your PC.
13) In ADB window on computer, enter fastboot devices to verify ADB is working.
14) In ADB window, enter fastboot oem lock to re-lock the bootloader.
15) Use fastboot keys to reboot phone into OS. See that it works.
16). Run Settings -> General -> Reset -> Factory data reset. Do NOT use Master Reset (button dance) or the new user might trigger FRP/kill switch (although shouldn't happen if you removed the account previously and didn't enter it again).
17) Done. Hand off the phone to its new user.
These steps were written off the top of my head. If anybody sees glaring mistakes or omissions, then please let me know.
Note: Some carrier models cannot readily get into fastboot mode. For those you will need to convert back to stock US998 to re-lock the bootloader (using Frankenstein like when you first rooted) and THEN convert back to the carrier firmware (again using Frankenstein).
Click to expand...
Click to collapse
not sure if you can help. i asked chaz as well but haven't received a resolution. i've done this but the phone at aroud >10 says that it needs to enable oem unlock to move forward with fastboot commands. except that this option is greyed out in the dev options. says phone is bootloader is already unlocked and doesn;t give option to enable it?? sigh i have tried 4 versions nougat and oreo ... none worked... any ideas??
johnp357 said:
not sure if you can help. i asked chaz as well but haven't received a resolution. i've done this but the phone at aroud >10 says that it needs to enable oem unlock to move forward with fastboot commands. except that this option is greyed out in the dev options. says phone is bootloader is already unlocked and doesn;t give option to enable it?? sigh i have tried 4 versions nougat and oreo ... none worked... any ideas??
Click to expand...
Click to collapse
I've heard of this before, where OEM Unlock was greyed out in the Developer Settings menu. I believe the answer was you have to wait a few days and it will change. But that's very frustrating when you're trying to get this phone back to stock.
Just to make sure I understood you correctly: You have tried booting into fastboot and run "fastboot oem lock" even with OEM Unlock greyed out, right? Otherwise definitely try that.
I am afraid I don't have any other suggestions.
@ChazzMatt: I remember you posting about this one time. Do you have more to add?
TheDannemand said:
I've heard of this before, where OEM Unlock was greyed out in the Developer Settings menu. I believe the answer was you have to wait a few days and it will change. But that's very frustrating when you're trying to get this phone back to stock.
Just to make sure I understood you correctly: You have tried booting into fastboot and run "fastboot oem lock" even with OEM Unlock greyed out, right? Otherwise definitely try that.
I am afraid I don't have any other suggestions.
@ChazzMatt: I remember you posting about this one time. Do you have more to add?
Click to expand...
Click to collapse
yes. i have tried it anyway but the pc says waiting for devices. it does not recognize it since oem unlock isn't triggered.. doesn't work....sigh
johnp357 said:
yes. i have tried it anyway but the pc says waiting for devices. it does not recognize it since oem unlock isn't triggered.. doesn't work....sigh
Click to expand...
Click to collapse
Understood. Question: Did you flash KDZ with Refurbish or Partition DL? Maybe one of them will clear this state and the other won't. But DON'T go experimenting with other LGUP modes!
Also, you could try a Factory reset and/or Master Reset (button dance) and see if that clears it.
If none of that works, you may have to just wait it out.
Edit: I googled around a bit. It seems Factory reset, then letting the OS connect to the internet (enable WiFi) can make the difference. Try googling as there are many references to this.
TheDannemand said:
Understood. Question: Did you flash KDZ with Refurbish or Partition DL? Maybe one of them will clear this state and the other won't. But DON'T go experimenting with other LGUP modes!
Also, you could try a Factory reset and/or Master Reset (button dance) and see if that clears it.
If none of that works, you may have to just wait it out.
Edit: I googled around a bit. It seems Factory reset, then letting the OS connect to the internet (enable WiFi) can make the difference. Try googling as there are many references to this.
Click to expand...
Click to collapse
i tried both refurbished and partition dl.. i may start tinkering with the others but people have warned against some so i'm hesitant of trying it... this really sucks.. need to return it to VZ on a trade in and running out of time
johnp357 said:
i tried both refurbished and partition dl.. i may start tinkering with the others but people have warned against some so i'm hesitant of trying it... this really sucks.. need to return it to VZ on a trade in and running out of time
Click to expand...
Click to collapse
Why can't you wipe it and return it to VZ like that? They don't care if it's rooted, bl unlocked, etc. They're going to wipe it when they get it and try to resell it regardless, why do their job for them?
ldeveraux said:
Why can't you wipe it and return it to VZ like that? They don't care if it's rooted, bl unlocked, etc. They're going to wipe it when they get it and try to resell it regardless, why do their job for them?
Click to expand...
Click to collapse
i read somewhere that rooting a phone violates their terms and makes it invalid as a trade in...
johnp357 said:
i read somewhere that rooting a phone violates their terms and makes it invalid as a trade in...
Click to expand...
Click to collapse
It voids whatever warranty existed between you, Verizon, and LG, but I haven't seen anything about trade ins. Where'd you read that?
johnp357 said:
i tried both refurbished and partition dl.. i may start tinkering with the others but people have warned against some so i'm hesitant of trying it... this really sucks.. need to return it to VZ on a trade in and running out of time
Click to expand...
Click to collapse
Did you try a Factory reset from the menu, then setup phone again with WiFi enabled? Heck, possibly even entering you Google account during setup and let it sync, if that's what it takes. As long as you perform a Factory reset from the menu to remove your account before trading it in.
@ldeveraux is probably right that Verizon won't care. But I am cautious person too when it comes to these things, and would prefer to trade in the phone in a clean state. Just in case the person you end up dealing with is a nitpick.
TheDannemand said:
Did you try a Factory reset from the menu, then setup phone again with WiFi enabled? Heck, possibly even entering you Google account during setup and let it sync, if that's what it takes. As long as you perform a Factory reset from the menu to remove your account before trading it in.
@ldeveraux is probably right that Verizon won't care. But I am cautious person too when it comes to these things, and would prefer to trade in the phone in a clean state. Just in case the person you end up dealing with is a nitpick.
Click to expand...
Click to collapse
i did try the factory reset. both from within and the buttons. and connected with wifi. didn't work... sadly. removing my account is not an issue. every time I install 1 of 4 diff nougat or oreo kdz in lgup, I put skip in the login so it doesn't have my info anymore... resetting doesn't really do it. messing with the date like others have suggested didn't either.
johnp357 said:
i did try the factory reset. both from within and the buttons. and connected with wifi. didn't work... sadly. removing my account is not an issue. every time I install 1 of 4 diff nougat or oreo kdz in lgup, I put skip in the login so it doesn't have my info anymore... resetting doesn't really do it. messing with the date like others have suggested didn't either.
Click to expand...
Click to collapse
That is indeed puzzling. I did this twice on my old H932 before sending it in for warranty, and never saw that problem.
I am sorry I don't have more suggestions to offer
I saw the other thread on unlocking the T-Mobile variant, so I thought I'd document my experience unlocking the version bought directly from the OnePlus store.
WarningsThis guide applies exclusively to OnePlus Nord N200 5G phones bought from the USA OnePlus online store.
It may work for other carrier-unlocked Nord N200 5G phones. However, I haven't tested them.
As always, this voids your warranty.
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about this process before following it. YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will not help you.
Click to expand...
Click to collapse
In addition, this adds an unremovable warning screen from the bootup process. After unlocking your device, the device will show a warning screen on every bootup for 5 seconds. It will read as follows:
The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device:
g.co/ABH
PRESS POWER KEY TO PAUSE BOOT
Click to expand...
Click to collapse
As a last note, if successful, this will wipe your device. Backup all data you care about.
Prerequisites1. A OnePlus Nord N200 5G bought from the USA OnePlus store, running OxygenOS 11.
2. A computer with the `fastboot` android platform tool set up and working.
You can download a package containing fastboot from https://developer.android.com/studio/releases/platform-tools.
3. A usb-C cable to plug the phone into the computer.
Steps1. Enable developer settings.
Go to Settings -> About phone. Tap "Build number" 5 times until it brings up a prompt to enter your device password. Enter it.
On success, it will bring up a note saying "You are now a developer!"
2. Enable OEM Unlocking
Go to Settings -> System -> Developer Options. Tap "OEM Unlocking" and follow prompts.
3. Reboot into fastboot
Long-press the power button, then select "Restart". As the phone is restarting, hold down the volume down and volume up buttons.
The phone should now be showing a text interface. You can select different options with the volume buttons, and use the power button to select.
3. Unlock using fastboot
Connect the phone to the computer.
In a command prompt on the computer, use the following fastboot command:
Bash:
fastboot devices
Verify that your device is connected, and the serial code matches the "SERIAL NUMBER" shown on the screen of the phone. For instance, my device shows as:
Code:
$ fastboot devices
SERIAL_NUMBER_REDACTED fastboot
And on my phone screen, it shows "SERIAL NUMBER - SERIAL_NUMBER_REDACTED".
Once you've verified this, use the following command to unlock the device:
Reminder: THIS COMMAND WIPES YOUR DATA. All data on the phone will be erased by this.
Bash:
fastboot oem unlock
If successful, the computer will output this:
Code:
$ fastboot oem unlock
OKAY [ 0.042s]
Finished. Total time: 0.042s
On the phone, you will see a prompt for unlocking the device. Read it, and follow the instructions. Use the volume up/down buttons as up/down arrow keys, and the power button as "OK" or "Enter".
After you've confirmed you want to unlock the device, your phone will reboot several times, and erase all data. Once it's done, you'll be rebooted into the operating system.
4. Confirm the unlock worked
To confirm the unlock worked, reboot into fastboot mode again.
On the screen, the bottom row should now read "DEVICE STATE - unlocked".
Congrats! You've unlocked your device. Once someone builds a custom recovery or ROM, you'll be able to use fastboot to flash it to your device.
So does this mean you can now pull the files someone would need to start on a custom recovery and/or a custom rom or at least majisk?
alarmdude9 said:
So does this mean you can now pull the files someone would need to start on a custom recovery and/or a custom rom or at least majisk?
Click to expand...
Click to collapse
Unfortunately, this doesn't let you pull any files from the device. All it does is allow you to flash a custom recovery, ROM, or boot.img once someone develops one.
With that said, I have started researching steps for porting TWRP to the device.
Edit: since this is the only place I've mentioned it, might as well give an update. I'm giving up on porting TWRP for now - I think we really will need binary blobs, or a lot more hacking on things and finding a similar device. And given that our device is the first wave of devices with the sm4350 platform.... I think our best bet is OnePlus releasing binary blobs.
I've taken notes on everything I've been trying at https://github.com/daboross/android_device_oneplus_holi_notes, if anyone's interested.
Man that stinks. I was hoping we could have at least gotten the files needed for majisk.
2 alternate ways to get into fastboot mode:
ADB:
The command
'adb reboot bootloader'
will restart the device in fastboot mode.
Advanced Reboot:
In the developer options, turn on 'Advanced Reboot'.
Hold the power button for a few seconds to bring up the power off/restart dialog.
At the top right corner will be 3 dots, tap them, select 'bootloader' from the resulting dialog.
The phone will reboot into fastboot mode.
alarmdude9 said:
Man that stinks. I was hoping we could have at least gotten the files needed for majisk.
Click to expand...
Click to collapse
I'm thinking it'll be a chain reaction as soon as we have *anything*.
Like, if we get magisk, we'll quickly be able to then pull the stock ROM and recovery and use those to build TWRP.
Or if someone can build TWRP, we can use that to pull boot.img and get magisk working, and pull the stock ROM and get a custom ROM built.
Or if someone can port a custom rom (though I imagine this is harder than the above two - probably impossible without binary blobs?) - we can include root in it, then use that to grab boot.img and the recovery image.
As soon as we get *any* control which gives us root access or otherwise unimpeded access, we should be able to do everything.
daboross said:
I'm thinking it'll be a chain reaction as soon as we have *anything*.
Like, if we get magisk, we'll quickly be able to then pull the stock ROM and recovery and use those to build TWRP.
Or if someone can build TWRP, we can use that to pull boot.img and get magisk working, and pull the stock ROM and get a custom ROM built.
Or if someone can port a custom rom (though I imagine this is harder than the above two - probably impossible without binary blobs?) - we can include root in it, then use that to grab boot.img and the recovery image.
As soon as we get *any* control which gives us root access or otherwise unimpeded access, we should be able to do everything.
Click to expand...
Click to collapse
i dont specialize in oneplus phones but maybe you could somehow get the stock rom and extract the boot.img file to then patch with magisk or the recovery.img whatever it is
areallydumbperson said:
i dont specialize in oneplus phones but maybe you could somehow get the stock rom and extract the boot.img file to then patch with magisk or the recovery.img whatever it is
Click to expand...
Click to collapse
The hard part is "somehow get the stock rom".
As soon as we can get that, everything else will indeed be possible.
daboross said:
The hard part is "somehow get the stock rom".
As soon as we can get that, everything else will indeed be possible.
Click to expand...
Click to collapse
maybe try to intercept an update package download
How to Capture OTA Update URL for your Android (2 Methods)
In this guide, you will learn how to capture OTA update URL for your Android device. We have provided two methods to help you capture the OTA URL with or without PC. OTA updates are standard among all…
www.thecustomdroid.com
ota updates usually have all the partitions it need like boot.img
areallydumbperson said:
maybe try to intercept an update package download
How to Capture OTA Update URL for your Android (2 Methods)
In this guide, you will learn how to capture OTA update URL for your Android device. We have provided two methods to help you capture the OTA URL with or without PC. OTA updates are standard among all…
www.thecustomdroid.com
Click to expand...
Click to collapse
I think the thread has been deleted now, but someone did do that for the Metro variant. I believe there was also a grab for the T-Mobile variant.
Unfortunately, both of those OTA updates were partial updates, and are useless without an original ROM image. I've also been watching for an update to my OnePlus non-carrier-variant, but no updates have been pushed at all.
I think it's not a bad idea. Just unfortunately all the updates so far have been partial, and since a new version of android is a ways away, I think they will continue to be partial updates, still useless.
Aw that sucks if only someone was on a firmware before oxygenos 11
areallydumbperson said:
Aw that sucks if only someone was on a firmware before oxygenos 11
Click to expand...
Click to collapse
Ah, but the device shipped with OxygenOS 11!
There have been so few updates since the device was released a little over a month ago. No OxygenOS 10 firmware ever existed for it.
Is the N200 directly bought from oneplus dual sim?
It seems like the device has the space/pins for second sim but disables dual sim via software.
Check on youtube for "N200 teardown" and the motherboard likely has space/pins for second sim.
BTW: does the unlocked version of N200 have FM radio? Can you install app "NextRadio" and see if it works?
GSMArena lists the N200 as dual sim with FM radio.
googlephoneFKLenAsh said:
Is the N200 directly bought from oneplus dual sim?
It seems like the device has the space/pins for second sim but disables dual sim via software.
Check on youtube for "N200 teardown" and the motherboard likely has space/pins for second sim.
BTW: does the unlocked version of N200 have FM radio? Can you install app "NextRadio" and see if it works?
GSMArena lists the N200 as dual sim with FM radio.
Click to expand...
Click to collapse
I'm not sure if it's dual sim or not, but it doesn't look designed to be. There's only one IMEI listed in settings, and while the SIM tray is long enough for two different SIM cards, the second one is filled in with plastic and you'd have to modify it to put a SIM card there.
Here's a picture of the front and back of the SIM tray:
{
"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 nextradio app does not work.
daboross said:
I'm not sure if it's dual sim or not, but it doesn't look designed to be. There's only one IMEI listed in settings, and while the SIM tray is long enough for two different SIM cards, the second one is filled in with plastic and you'd have to modify it to put a SIM card there.
Here's a picture of the front and back of the SIM tray:
View attachment 5376771
The nextradio app does not work.
Click to expand...
Click to collapse
The motherboard may have pins for second sim card.
Maybe like the t-mobile version of oneplus 6T, we just need to replace the sim card tray and flash compatible firmware to enable dual sim function.
Even with one IMEI, both sim cards can still work simultaneously like the T-Mobile oneplus 6T. People have reported two sims work on t-mobile simultaneously or on two different carriers on t-mobile oneplus 6T with one imei.
daboross said:
I'm not sure if it's dual sim or not, but it doesn't look designed to be. There's only one IMEI listed in settings, and while the SIM tray is long enough for two different SIM cards, the second one is filled in with plastic and you'd have to modify it to put a SIM card there.
Here's a picture of the front and back of the SIM tray:
View attachment 5376771
The nextradio app does not work.
Click to expand...
Click to collapse
I'm surprised the radio app doesn't work. There is a default package installed with a radio app, and the original phone (A91?) comes with an fm radio.
Can someone explain if they really switched the camera modules? I can't find any info on what the specific camera module is, plus the a54 (oppo) has a 48 mp camera versus the 13 mp in the n200. It seems like they really wouldn't switch the cameras on a phone so similiar, but who am I?
Fishwithadeagle said:
Im surprised the radio app doesn't work. There is a default package installed with a radio app, and the original phone (A91?) comes with an fm radio.
Click to expand...
Click to collapse
What is the default package? I can't find any on my device that looks like it'd be a radio app.
Here's a screenshot of NextRadio. To be clear, I have done no debugging to see if I could get it to work. I just installed it via the play store and opened it.
Fishwithadeagle said:
Can someone explain if they really switched the camera modules? I can't find any info on what the specific camera module is, plus the a54 (oppo) has a 48 mp camera versus the 13 mp in the n200. It seems like they really wouldn't switch the cameras on a phone so similiar, but who am I?
Click to expand...
Click to collapse
I'm not against discussing this here, but I think you may have more luck with a new Question thread specifically for this question. I'm not an expert on phone hardware.
daboross said:
Ah, but the device shipped with OxygenOS 11!
There have been so few updates since the device was released a little over a month ago. No OxygenOS 10 firmware ever existed for it.
Click to expand...
Click to collapse
Have you tried downloading full ROM of OxygenOS11 using the Oxygen Updater app?
jilebi said:
Have you tried downloading full ROM of OxygenOS11 using the Oxygen Updater app?
Click to expand...
Click to collapse
Thanks for referring to that!
Unfortunately, I downloaded the app, and there's only one update channel available - "Stable". No option to select between Incremental and Full on this device. Screenshot of this below:
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
CHANGELOG:
Guide v1.0 - Warn that Lineage cannot be flashed on A12 firmware.
Guide v1.1 - Update guide for flashing Lineage after complete conversion and updates so phone is fully converted first.
There are THREE firmware versions for the N200.
DE2118 - Carrier infected phones for T-Mobile and MetroPCS in US.
DE2117 - Retail US OEM firmware that is 100% compatible with US carriers and fully supports 5G, 4G, 3G (gone), 2G, VoLTE, and VoWIFI.
This guide is intended to remove the carrier virusware that the carrier uses to wipe/spy on the user as well as branding bloat like the bootup/shutdown graphic/sound.
DE2117AA - International version of the phone. This has a different modem/firmware, supports 2 sim cards, and is NOT compatible with US N200 hardware.
WARNINGS:
1. Do NOT flash Intl. DE2117AA firmware or use msmtool for DE2117AA on any US phone or you will no longer make/receive voice or text calls until you flash back to US firmware with Fastboot Enhance!
2. You must NOT stop the guide after you flash DE2117 onto the first slot as the phone will NOT be fully converted until it takes the OTA update to Android 12 and one more to C_17.
If you go to the about screen before the Android 12 OTA update, you will still see DE2118.
3. A You should take ALL OTA updates to Android 12 C_17 and then follow the root guide for Dummies if you want to test drive the latest and very stable current OEM firmware.
B Flash back to DE2117 Android 11 final with my downgrade guide to go back to the final Android 11 DE2117 US before you install current N200 Lineage.
Lineage requires you to be on Android 11 or it will soft brick when you flash Lineage boot.img.
4. Finally, I have had enough people use my N200 guides that they are proven to work very well, but I take no responsibility if you abort the flashing process or skip parts of the guide and manage to boot loop/brick your phone!
However, I will work with you to get you going again. This phone cannot be fully bricked with the Qualcomm chipset and EDL recovery mode. You will create a full backup of your phone in the guide, so you can restore it 100% even if you walk away and your cat manages to fully wipe the entire firmware area of the phone with Fastboot Enhance.
PREREQUISITES: (see other guides)
1. You must have your boot loader unlocked.
2. Request and receive your unlock token from OP website to unlock boot loader.
(This takes exactly one week from requesting on Oneplus Website until OnePlus delivers the unlock token.)
If your phone is still sim subsidy locked and you cannot move the "OEM unlocking in dev options to on as it's greyed out, follow steps (20-24) to bypass this and turn on OEM unlocking so you can get unlocking code without being sim unlocked.
3. Install latest Android Platform Tools installed on PC. Currently v33.0.3
Old versions platform tools will cause fastboot commands to FAIL!!
4. Fastboot Enhance tool
Download and unzip folder into working directory.
This tool is Windows only and requires .net framework 4.5 (can be ran in VM with enough free ram for experienced linux users) This tool also needs a good amount of ram as someone with a old Windows 7 machine with very limited ram had the program hang when unpacking the firmware. They then switched to a newer machine resolved the issue.
5. Backup your phone data as this guide will wipe your phone in the process.
I recommend you put a MicroSD card in your N200 and select MicroSD card as backup location in Swift/APP Manager as all data on MicroSD will survive a phone wipe/reset.
A. The most simple backup tool is Swift Backup with a rooted phone to save all your app, data, phonebook, texts, and wifi passwords for easy restore after you are converted, upgraded and re-rooted.
B. For power users I highly recommend using App Manager to back up your apps.
The App Manager instructions are worth reading like a book as this tool is very complex and powerful.
This tool will backup APK source files/splits, internal/ext data/obb and media/cache, app permissions, battery savings,data usage, Magis khide status, SSAID, rules set up in App Manager. It will also import backups fromOAndBackup, Titanium and Swift (3.0-3.2) and keep multiple version backups of same app.
It's also an Interceptor, Manifest viewer, Scanner (API key from virus total), Enhanced Package installer with version upgrade/downgrade information and library add/remove info on install, Usage, Log viewer with colors/filters, App explore and much more.
-----------------------------------------------------------------------------------------
Begin GUIDE
-----------------------------------------------------------------------------------------
1. Place your phones unlock key into Platform Tools directory.
(You can download it again by logging into OnePlus site and going to this page.)
2. Download Tmobile/MetroPCS OnePlus MSMtool for V11.0.1.7 and unzip to working folder of your choice.
3A. Download FINAL Android V11 Update Image .
If installing Lineage,You MUST flash Lineage boot.ini from Android 11 or you WILL go into a soft boot loop from Android 12!
3B. If you are going to re-flash your phone that is already flashed to DE2117 and on A12 due to a bad update (in a soft boot loop) or installed other A12 rom and need to flash back, Download Full US OEM A12 C_16 Update Image and keep as .zip file and place in working folder instead.
(See Downgrade Guide if you are already running US OEM A12 and want to go back to A11 to install Lineage.)
4. Go to working folder you unzipped msmtool and open folder "dre8t_10_O.07_211014_repack"
5. A. Execute program as Administrator "MsmDownloadTool V4.0.exe" if your running Windows 10 or 11.
B. Execute program as administrator "MsmDownloadTool V4.0_Win7.exe" if your running Windows 7.
6. At login prompt, change user type to:
"User Type: Others" & Hit Next button.
7. At main page of MsmDownload Tool hit "F8"
A new window will pop-up that is called Firehose Readback:
(Ignore my crazy Windows theme colors - Yours will look different)
{
"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. Locate Password box at bottom of pop-up and enter lowercase password: oneplus
9. Make sure the box is still active window and hit <cntrl-a> and every box in the list will then become checked.
10. hit OK to close box.
11. Click new "Read Back" button.
13. Place phone in special EDL recovery mode:
A. Since ADB is working, it is easier to simply open your Android Platform tools folder in Explorer and type cmd in location box to open dos prompt and type:
C:\platform-tools>adb reboot edl
B. You can turn phone off and then hold both volume buttons down and power on to force phone into EDL mode if phone is not working properly.
NOTE: When phone is in EDL mode the screen on the phone will be BLANK.
This is NORMAL.
14. As soon as the command is entered switch back to MSMtool window and watch it make a FULL backup of your phone including all firmware (slot a/b) and phone identifying information areas. When this is complete your phone will reboot.
15. Go to root of system drive (Default C:\) in explorer and sort files by date (Double Click on the Date Modified) and move all the new files just created ending in .bin, .img, .elf, and .mbn to a folder and name it to identify this exact phone if you have more than one N200 and store in a safe place like a USB flash drive. You can zip the folder first to save space.
See: Firehose backup files.txt attached for full list.
Do NOT share this backup with anyone online as they can clone your phones IMEI/SN with this PRIVATE backup data!
16. Re-run msmtool again. It will remember user type option: others. Click Next.
17. This time at main screen simply press start. and place phone in EDL mode as in step 13.
18. Watch the tool flash V11.0.1.7 firmware and most importantly the older fastbootd that is proven to perform the conversion firmware flash.
(Phone will reboot wiped/locked and in out of box condition.)
19. Do phone setup offline without entering wifi and as soon as you are out of setup turn off data to prevent phone from starting to download firmware update from OTA.
20. Goto Settings -> About Device -> Version -> build number and click until developer again.
21. Goto Settings -> System Settings -> Developer Options and turn on USB debugging and then exit settings.
22. Go back to dos box and send command to remove software that prevents OEM Unlock from being turned on:
C:\platform-tools>adb shell pm uninstall --user 0 com.qualcomm.qti.uim
23. On Phone: Go to Settings -> System Settings -> Developer Options
Turn ON "OEM Unlocking"
24. Go back to dos box and type:
C:\platform-tools>adb reboot fastboot
25. Send your unlock code to phone again.
(Assuming the file is called unlock_code.bin)
C:\platform-tools>fastboot flash cust-unlock unlock_code.bin
26. Unlock Bootloader:
C:\platform-tools>fastboot oem unlock
27. Follow on screen directions and phone will unlock bootloader, erase data and enter new phone setup again.
Do steps 19-21 again (developer/adb debugging on) and step 24 (Reboot to fastboot)
Now visually verify your phone is in Fastboot mode and unlocked.
28. Go to working folder in explorer and open folder "Fastboot_EnhanceV1.3.0" and execute "FastbootEnhance.exe"
29. On Fastboot Visualization tab, Double click on your device that will be shown.
30. Now you have two tabs, "Basic Properties" and Partitions.
31. Click on Partitions tab and scroll to bottom of the partitions list and verify that there are none that end in "_cow"
(They are creeated when you do OTA upgrades. They are left over and need to be deleted if present otherwise there may not be enough room to write new image.)
32. Highlight EVERY file ending in "_cow" and click the erase button.
They are always at the bottom of the list.
Repeat until there are NO files ending in "_cow"
33. Click the button bottom left corner called "Reboot to Fastbootd"
34. Your phone willl now reboot into special fastbootd mode.
35. Click English on phone to see this. Do NOT click any other options on phone.
36. Tick the box on right Show Logs to watch it's progress. A log box will pop up. Drag it over to the side to watch.
37. Tick the box Ignore Unknown Partitions
(fastbootd will NOT flash over newer modem firmware with older, if flashing older firmware and required for flash to still work)
38A. Click Flash Payload Bin box and select file "DE2117-A11-Final-OnePlusN200Oxygen_10.O.11_OTA_011_all_2203021426_downgrade_66cde69fe1e342db.zip" from working directory.
38B. For Android 12 USS OEM Reflash-Restore, Select file "(US_RETAIL_A12_C_16_FULL_ROM)DE2117_11.C.15_0150_202205192325.zip"
39. Click Flash Payload bin button.
It will unpack all the partitions from the .zip file first.
It will then delete old partitions and re-create partition with new required size and flash each .bin file of firmware one at a time automatically.
40. WAIT.....Watch the log output window and DO NOTHING until complete.
A. Fastboot Enhance will unpack all the partitions from the .zip file first.
B. It will then delete old partitions and re-create partition with new required size and flash each .bin file of firmware one at a time automatically.
41. When process is finished click "Reboot to recovery" button.
42. on phone, tap English.
43. on phone, tap "wipe data" and follow prompts to wipe and restart.
You will now boot up on US OEM DE2117 Android 11 Final.
WARNING: Do NOT stop the guide at this point, as your phone is not fully converted yet!
If you go to about info you will still see DE2118 and the boot area and other slot is still on carrier firmware! (Even if you are going to install Lineage, you must continue OTA upgrades to Android 12 C_17 and then downgrade to Android 11 afterwards)
44. Perform system setup with wifi and go to settings -> about device and perform system update and you will update to A12 (C_16) and proceed to second partial OTA update to latest OTA (C_17) before following the root guide for dummies
WELL DONE MY GOOD SIR!
Thanks for the thorough write-up for this dummy! So once this procedure is completed I can assume that everything that works for the DE2117 (like LineageOS) will be OK for a DE2118?
My fastboot enhance keeps stopping once i select the payload.bin to flash
I have all the correct files but it seems like windows keeps stopping the program from continuing further...
So say you run through this guide, everything goes correctly and you end up with a DE2117. Is it for all intents and purposes a DE2117 or would you still run the DE2118 MSM Tool should you run into a problem and need to reset?
Maatt_OG said:
My fastboot enhance keeps stopping once i select the payload.bin to flash
I have all the correct files but it seems like windows keeps stopping the program from continuing further...
Click to expand...
Click to collapse
Are you seeing anything in the log window?
What is the error message Windows is giving you, and how is it stopping the program?
It sounds like you have Windows issues.
Are you running this in a VM or under very low memory conditions?
You may want to refresh your Windows installation.
Link575 said:
So say you run through this guide, everything goes correctly and you end up with a DE2117. Is it for all intents and purposes a DE2117 or would you still run the DE2118 MSM Tool should you run into a problem and need to reset?
Click to expand...
Click to collapse
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone is for all practical reason a US OEM. Your IMEI is still in the T-mobile/MetroPCS range so the OP will not give you credits for registering a new OEM phone at Red Cable Club and will say that IMEI is invalid.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
scanman0 said:
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone s for alll practical reason a US OEM. Your IMEI is still in the Tmobile range so OP site login will not give you register credit for registering new phone at store.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
Click to expand...
Click to collapse
it says extracting files in the log but i have eeven waited and ignored the windows pop up error saying , Program has stopped working, we will let you know if theres a solution, but it doesnt proceed any further.
AND... DO NOT USE MSM TOOL AFTER CONVERTING. modem and core-nhlos and a few other partitions are a bit different along with the hardware versions and all and youll bootloop.
scanman0 said:
Are you seeing anything in the log window?
What is the error message Windows is giving you, and how is it stopping the program?
It sounds like you have Windows issues.
Are you running this in a VM or under very low memory conditions?
You may want to refresh your Windows installation.
Click to expand...
Click to collapse
as for memory, i am running pretty low tbh....
scanman0 said:
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone s for alll practical reason a US OEM. Your IMEI is still in the Tmobile range so OP site login will not give you register credit for registering new phone at store.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
Click to expand...
Click to collapse
I see thanks for that. So one more follow up, I'm not even sure if you would know this but I installed Lineage 19 on my DE2118 and after that About phone states its a 2117. I'm assuming this is just because that's what this ROM was made for and it's not actually converting to a DE2117. I did MSM after Lineage and had no problems going back to stock DE2118.
scanman0 said:
13. Place phone in special EDL recovery mode:
Click to expand...
Click to collapse
This dummy had never seen EDL mode before and because my MSMDownload tool for Win7 seemed to require running as administrator the tool did not automatically connect so all I saw was a black screen in Step 14.
We shall not talk about how long nor how many different reboot combinations were required for me to understand that I needed to run the tool as administrator and that the black screen was normal. Really funny.
Even funnier was that I never did find the backup files after the Download was complete. Not on C:, not on D:, none found with the Explorer search function. Somehow I made them vanish even after your careful description.
katooom said:
Even funnier was that I never did find the backup files after the Download was complete.
Click to expand...
Click to collapse
And the only reasonable explanation for this is that among my many confused attempts to make things work this was the time that I did not actually do the backup, just pressed the start button. I would hate to think that I made such a ridiculous blunder but what else could it be. Oh my .....
Maatt_OG said:
as for memory, i am running pretty low tbh....
Click to expand...
Click to collapse
You need to have enough memory free for the program to unpack the .zip file in ram. If Windows is crashing the process with "program is not responding" then your pc (or is it a vm?) does not have enough memory.
Link575 said:
I see thanks for that. So one more follow up, I'm not even sure if you would know this but I installed Lineage 19 on my DE2118 and after that About phone states its a 2117. I'm assuming this is just because that's what this ROM was made for and it's not actually converting to a DE2117. I did MSM after Lineage and had no problems going back to stock DE2118.
Click to expand...
Click to collapse
Lineage has one build that is compatible with both versions and reports that either is DE2117.
katooom said:
This dummy had never seen EDL mode before and because my MSMDownload tool for Win7 seemed to require running as administrator the tool did not automatically connect so all I saw was a black screen in Step 14.
We shall not talk about how long nor how many different reboot combinations were required for me to understand that I needed to run the tool as administrator and that the black screen was normal. Really funny.
Even funnier was that I never did find the backup files after the Download was complete. Not on C:, not on D:, none found with the Explorer search function. Somehow I made them vanish even after your careful description.
Click to expand...
Click to collapse
I have updated the guide to reflect that you need to run as administrator on Windows 7 and to run the windows 7 .exe file.
I have only tested under Windows 10 and Windows 11 and the program demanded administrator mode to run.
The msmtool always dumps to the root of the working system boot drive that is usually C:
I made a screen shot of the F8 windows as you must select the boxes and place the password to place the tool in the backup mode.
I never said in the guide to look at the phone when in EDL mode as the screen is black.
I have updated the guide to inform people that are not familiar with EDL mode to expect that it is blank.
This is the reason I had people go to EDL mode with the pc with adb is the fact that it is a blank screen mode and people can be confused if the phone is in EDL or off.
I cannot tell by your condescending comments if you actually did the F8 procedure correctly to place msmtool in backup mode.
There is no indicator before it starts (other than the window closing without an error) and the tool will indicate as shown in the screenshot that it is "Reading back <Partition name>" as it reads the partitions from the phone.
If you simply press start as you implied you "tried" the tool will flash the phone to default factory state and NOT do a backup.
You do realize I wrote this guide to try to help people and cannot test every possible configuration as I don't have Windows 7 anymore.
People with your poor attitude is the reason there are fewer hand holding guides present on XDA.
scanman0 said:
Lineage has one build that is compatible with both versions and reports that either is DE2117.
Click to expand...
Click to collapse
Got it, thanks.
scanman0 said:
People with your poor attitude is the reason there are fewer hand holding guides present on XDA.
Click to expand...
Click to collapse
Whoa, I have to apologize for making you think that I was in any way critical or dissatisfied! I was merely making fun of myself for messing up the process in spite of how well you explained it. I actually hoped that you would be amused by my errors and the silly reasons that I made them. It is deeply upsetting to me to have offended someone who puts so much effort into helping. I can only apologize again for expressing myself so poorly.
@scanman0 Dumb question probably, but after completing this, would it be possible to downgrade to Android 11 OEM?
rcartaz09 said:
@scanman0 Dumb question probably, but after completing this, would it be possible to downgrade to Android 11 OEM?
Click to expand...
Click to collapse
Nothing dumb about this question!
I have updated the guide to INCLUDE converting to last Android 11 US OEM Firmware
And put warning to only install Lineage with Android 11 firmware.
I also posted a separate downgrade guide so people will not miss this fact if they already upgraded to Android 12 and want to install Lineage:
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
After completing this, would it be possible
scanman0 said:
Nothing dumb about this question!
I have updated the guide to INCLUDE converting to last Android 11 US OEM Firmware
And put warning to only install Lineage with Android 11 firmware.
I also posted a separate downgrade guide so people will not miss this fact if they already upgraded to Android 12 and want to install Lineage:
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
Click to expand...
Click to collapse
You are awesome! Thank you!