I tried downloading something in my developer options and it seemed to work, but when my phone restarted I got a message saying, "your device is corrupt. It Can't be trusted and will not boot". The message seems to be in some sort of boot loop, (keeps restarting with the same message). Is there any way I can fix this without sending my phone in to One Plus? I purchased the phone inside of a Metro store.
{
"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"
}
If your phone is from T-Mobile or Metro, check out this forum post to recover your phone: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4324431/
If your phone was factory unlocked, contact OnePlus for a repair. The easiest way to tell if your phone is a carrier device or not is to check the back of the phone. If there's an IMEI engraved on the back of the phone, it's a T-Mobile or Metro phone. If there's not IMEI engraver, its factory unlocked.
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked variant.
edale1 said:
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked var
Click to expand...
Click to collapse
Yeah that was it! Lesson learned. Thank you!
Thats how I managed to mess up my phone and is currently bricked for several months .. no msmdownload for the unlocked .. please try and get a remote session with the oneplus tech guys .. and share if possible
Hold up a second here. If you have tried to relock the bootloader (which will result in the device is corrupt and will not boot message) try this:
Hold down all 3 buttons (Vol+ Vol- and power) for about 8 seconds or so. As soon as the device vibrates quickly release the power button. When you do, the device should be in fastboot. If you are in fastboot you should now be able to connect it to the PC and type the command fastboot oem unlock. This will now attempt to unlock the bootlaoder. Chances are you have previously unlocked the bootloader and have attempted to relock it. Doing so will cause this error message on the UNLOCKED version of the device.
This will wipe the data but return the device to an unlocked state but not completely bricked on stock firmware. Go through the normal prompts to start the device and you should be good.
Remember, if you have fastboot its not COMPLETELY bricked. Not yet anyways.
I had this happened on my OnePlus Nord 200 5g literally the next day after I got it from Metro at T-Mobile. Phone updated as it should but restarted with the same message you received. They tried to accuse me of putting a virus on the phone which did not make any sense and after going through insurance who couldn't accept the claim for "software damage" ... I contacted one plus and had them remote view my laptop with downloaded tar files and had a technician try to reinstall them back to its original factory condition but to no luck. Metro being a franchise company, has the loophole not accepting returned merchandise even under the return policy stated on the receipt, and customer service technically has no control or power over any particular franchise Metro store. I suggest the only answer I had after 2 weeks of frustration from contacting everyone I possibly could to writing corporate, I finally had a CSR tell me to just get a warranty exchange at any Metro store in which I did in two days later I received a new phone which actually works this time so I would suggest just doing the warranty exchange in order to get yourself a workable phone. Hope that helps. \m/
edale1 said:
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked variant.
Click to expand...
Click to collapse
I did this exact thing. Mine is the oem unlocked variant. Is contacting oneplus support still the only option? It's on the metro/tmobile network if that matters. I really fcked up here with dsu loader. Pretty desperate right now for a fix. Please.
superspecialgueststar said:
I did this exact thing. Mine is the oem unlocked variant. Is contacting oneplus support still the only option? It's on the metro/tmobile network if that matters. I really fcked up here with dsu loader. Pretty desperate right now for a fix. Please.
Click to expand...
Click to collapse
You can try the MSM Tools and see if it works, if not, then yes, OP Support is your only option.
edale1 said:
You can try the MSM Tools and see if it works, if not, then yes, OP Support is your only option.
Click to expand...
Click to collapse
Thanks, I downloaded msm tools and there are msm tools included in https://www.terabox.com/web/share/link?surl=7fjfMJSEcdl5zCjPT92IKA
for
dre8t_10_O.05_210713.tar.bz2 -can someone point me to the stock firmware I should be using msmtools error device not match image. Can I use the ~3gb ota zips?
Taking a break and then going to look for a guide for MSM tools.
edit - as an additional point of confusion, my bootloader was unlocked, I was rooted with magisk patched upstream boot.img. Did this happen because I did not know about uninstalling magisk and installing magiosk to the inactive slot? My bootloader is still unlocked, but flashing boot backups etc does not get me out of fastboot loop, and unable to verify boot image error when I try to fastboot boot twrp or orangefox.
You're past the point I can help with, maybe someone else has some more advice for you?
Thanks. And technical support turns out is the only way and sending it in is the only way for the oem unlocked version. I requested a remote session and ended up being told the files aren't working so they can't do a remote session. If they arent working how are they going to flash my device lol...who knows.
Superspecialgueststar,
The released MSM tool is only for the carrier variant and cannot be used for the unlocked variant. There is cryptographic security in place to restrict its use.
You can still fix your unlocked device, just use an unbrick guide for the unlocked version.
[GUIDE] How to unbrick your Nord N200 5G (ALL VARIANTS) or switch bootable slot (REQUIRES UNLOCKED BOOTLOADER)
I've seen alooot of issues lately of people "bricking" their Nord N200's without a method of unbricking (at the time of writing, only T-Mobile variant has MSMTool) I've noticed a reoccurring theme. i myself am guilty of doing it and not...
forum.xda-developers.com
or use my unbrick experience and advice
Un-bricking my Nord N200
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system...
forum.xda-developers.com
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
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
Hi everyone, I accidentally locked my phone after I tried to remove the bootloader warning message that booted up everytime I turned on my phone. Now it says that my phone is corrupted in red and I can only boot to fastboot mode. My device is now locked and customer support told me that I needed to go to a OnePlus repair shop. The problem is that I don't live in the US. If anyone can help me I'll be appreciated.
twomad said:
Hi everyone, I accidentally locked my phone after I tried to remove the bootloader warning message that booted up everytime I turned on my phone. Now it says that my phone is corrupted in red and I can only boot to flashboot mode. My device is now locked and customer support told me that I needed to go to a OnePlus repair shop. The problem is that I don't live in the US. If anyone can help me I'll be appreciated.
Click to expand...
Click to collapse
Can you access fastboot? Is the bootloader unlocked or did you lock the bootloader
Kenora_I said:
Can you access fastboot? Is the bootloader unlocked or did you lock the bootloader
Click to expand...
Click to collapse
yes. i can access fastboot mode. Windows recognizes my device when I enter "fastboot devices". I accidentally locked the bootloader while running Pixel Experience 12 GSI and now it says "your device is corrupt. It can't be trusted and will not boot".
twomad said:
yes. i can access fastboot mode. Windows recognizes my device when I enter "fastboot devices". I accidentally locked the bootloader while running Pixel Experience 12 GSI
Click to expand...
Click to collapse
Try to unlock it again with fastboot flashing unlock
Kenora_I said:
Try to unlock it again with fastboot flashing unlock
Click to expand...
Click to collapse
{
"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"
}
twomad said:
View attachment 5587563
Click to expand...
Click to collapse
this is what is says in Fastboot:
-PRODUCT NAME - holi
-VARIANT - SM_ UFS
-BOOTLOADER VERSION -
-BASEBAND VERSION -
-SERIAL NUMBER - eb375f3e
-SECURE BOOT - yes
DEVICE STATE - locked
twomad said:
this is what is says in Fastboot:
-PRODUCT NAME - holi
-VARIANT - SM_ UFS
-BOOTLOADER VERSION -
-BASEBAND VERSION -
-SERIAL NUMBER - eb375f3e
-SECURE BOOT - yes
DEVICE STATE - locked
Click to expand...
Click to collapse
You'll have to try get into EDL mode, but there's no MSM tool released for the unlocked varient of this phone only the T-Mobile varient
Kenora_I said:
You'll have to try get into EDL mode, but there's no MSM tool released for the unlocked varient of this phone only the T-Mobile varient
Click to expand...
Click to collapse
exactly. I tried to follow this guide https://forum.xda-developers.com/t/...le-slot-requires-unlocked-bootloader.4401113/ but it's only applicable to bricked phones that have bootloader unlocked
twomad said:
exactly. I tried to follow this guide https://forum.xda-developers.com/t/...le-slot-requires-unlocked-bootloader.4401113/ but it's only applicable to bricked phones that have bootloader unlocked
Click to expand...
Click to collapse
Yeah unfortunately you're stuck here, without the MSM tool
You could try calling One Plus customer support, explain there are no OP repair shops locally, and request a remote session to fix it.
It's been a while since anyone tried, you might luck out and they could have the MSM tools for the unlocked variant now. (PLEASE share them if they do, they'll send you a link to download the MSM tools ahead of time for the remote session)
Barring that, they'll probably want you to mail the phone in to get it fixed.
edale1 said:
You could try calling One Plus customer support, explain there are no OP repair shops locally, and request a remote session to fix it.
It's been a while since anyone tried, you might luck out and they could have the MSM tools for the unlocked variant now. (PLEASE share them if they do, they'll send you a link to download the MSM tools ahead of time for the remote session)
Barring that, they'll probably want you to mail the phone in to get it fixed.
Click to expand...
Click to collapse
I was actually looking into this for the OnePlus 10 Pro but it seems unlikely but who knows?
A remote session is how we got the T-Mobile MSM tools. It's just every time someone's tried with the Unlocked variant, they've been told the remote support team doesn't have access to the MSM tools for the Unlocked variant. As I said, it's been a while since the last attempt, so there's a chance they may have gotten it by now.
edale1 said:
You could try calling One Plus customer support, explain there are no OP repair shops locally, and request a remote session to fix it.
It's been a while since anyone tried, you might luck out and they could have the MSM tools for the unlocked variant now. (PLEASE share them if they do, they'll send you a link to download the MSM tools ahead of time for the remote session)
Barring that, they'll probably want you to mail the phone in to get it fixed.
Click to expand...
Click to collapse
yeah, I emailed OnePlus and they immediately told me to send the phone for repair. I emailed them again so that they can provide me an MSM tool so let's see how it goes.
twomad said:
yeah, I emailed OnePlus and they immediately told me to send the phone for repair. I emailed them again so that they can provide me an MSM tool so let's see how it goes.
Click to expand...
Click to collapse
Hopefully it will work, the talk about the unlocked version of the MSM tool has kind of died down for around 2 months or so. (On this forum, at least)
Sorry if I missed something and am plucking at brain cells that have already been plucked, but has anyone tried EDL mode and emmcdl.exe with the available firehose? Its not as straight forward to do being as the n200 is UFS amd not EMMC, but it should still be do'able. Its how I managed to get my brick back to fastboot... For that matter, the UFS provisioning xml is available for QFil. You'd have to determine which storage make you have (samsung or toshiba).... Just a thought
the.real.p3y0t3 said:
Sorry if I missed something and am plucking at brain cells that have already been plucked, but has anyone tried EDL mode and emmcdl.exe with the available firehose? Its not as straight forward to do being as the n200 is UFS amd not EMMC, but it should still be do'able. Its how I managed to get my brick back to fastboot... For that matter, the UFS provisioning xml is available for QFil. You'd have to determine which storage make you have (samsung or toshiba).... Just a thought
Click to expand...
Click to collapse
Thing is we don't have the firehose, otherwise it would be easy with qfil
biff_train said:
Hopefully it will work, the talk about the unlocked version of the MSM tool has kind of died down for around 2 months or so. (On this forum, at least)
Click to expand...
Click to collapse
"About your query, we would like to inform you that, currently, we are unable to perform a remote session for OnePlus Nord N200, in this case, we request you to send the device to the serviceable region to get it repaired." I'm screwed
twomad said:
"About your query, we would like to inform you that, currently, we are unable to perform a remote session for OnePlus Nord N200, in this case, we request you to send the device to the serviceable region to get it repaired." I'm screwed
Click to expand...
Click to collapse
Yeah they did that for the OnePlus 10 Pro as well
Kenora_I said:
Thing is we don't have the firehose, otherwise it would be easy with qfil
Click to expand...
Click to collapse
Firehose should be right inside the (extracted) OPS and common to the variants, but I believe OPlus firehoses are encrypted and can't simply be used with QFIL.
AndyYan said:
Firehose should be right inside the (extracted) OPS and common to the variants, but I believe OPlus firehoses are encrypted and can't simply be used with QFIL.
Click to expand...
Click to collapse
Yeah, we tried it but it's not loading actually
hello, i am faced with the decision to get the tmobile OnePlus N20 or the N200.
I am abandoning samsung after years of being disappointed by not being able tto do witthg my phone what i choose.
I want a device i can root and tinker with and modify as i please.
so im looking at these 2 phones and obviousl the n20 wins according tto tthe specs. butt i would like tto know if anyone has been able tto roott this device yet? or do yyou foresee any major obsttacles to unlocking the boottloader? i dont wantt to be stuck yet again with a device tthat i cant mod the way i want. i would like tto eventually be able to run kali or some custom roms on it. i need a device that i can mosl replace my lapttopwith. i cant afford tthe f;lagship pohone rightt now or i would go witth tthat. if anyone has an suggestions or info i would greatly appreciate it.
also i know these are supposed tto have to be sim unlocked first but i saw in anotther thread on anotherdevice i believe it was an OPO something but there was a script hat got rid of tthe services/apps that prevented unlocking the booloader while sim locked.
does anone know if the same script could be run on this device or will i have to sim unlock i?
The unlocked variant can be rooted as easily as any, as long as you get a copy of its boot image. The TMo variant (which you're after) has yet to get its bootloader unlock token.
To me, having high refresh rate is paramount, so N20 omitting that is a critical flaw. Plus, having tried GSIs on both, I felt N20 was weirdly stuttery/unresponsive for its specs.
PsYk0n4uT said:
hello, i am faced with the decision to get the tmobile OnePlus N20 or the N200.
I am abandoning samsung after years of being disappointed by not being able tto do witthg my phone what i choose.
I want a device i can root and tinker with and modify as i please.
so im looking at these 2 phones and obviousl the n20 wins according tto tthe specs. butt i would like tto know if anyone has been able tto roott this device yet? or do yyou foresee any major obsttacles to unlocking the boottloader? i dont wantt to be stuck yet again with a device tthat i cant mod the way i want. i would like tto eventually be able to run kali or some custom roms on it. i need a device that i can mosl replace my lapttopwith. i cant afford tthe f;lagship pohone rightt now or i would go witth tthat. if anyone has an suggestions or info i would greatly appreciate it.
also i know these are supposed tto have to be sim unlocked first but i saw in anotther thread on anotherdevice i believe it was an OPO something but there was a script hat got rid of tthe services/apps that prevented unlocking the booloader while sim locked.
does anone know if he same scrip could be run on his device so as no o have o wai il i sim unlock i?
Click to expand...
Click to collapse
Get the n20 over the n200 if the final price difference is less than $60.
The n200 is a bad device for its specs because oneplus has no interest in optimizing the OS for its low end phones with 4gb ram, because oneplus has only two devices with 4gb ram: the n100 and n200. Oneplus put an OS designed for 6gb/8gb ram with mid-high end cpus on the N200 which has only 4gb ram and lower end cpu, and as a result, the N200 performs like a Motorola phone with 2gb/3gb ram.
Similarly speced Motorola phones perform much better than oneplus.
Ironically, if you update the N200 to android 12, the system will say the phone has a snapdragon 855 cpu, while it has a low end snapdragon 480 cpu. So basically oneplus software engineers just put an OS designed for high end phones onto the low end N200 without any optimization, and even forgot to change the cpu model name.
If you buy the carrier tmo/metro version, you need to obtain unlock token bin to unlock the bootloader, and you need to sim unlock first to enable OEM unlock or you can use the disabling Qualcomm uim app trick.
googlephoneFKLenAsh said:
Get the n20 over the n200 if the final price difference is less than $60.
The n200 is a bad device for its specs because oneplus has no interest in optimizing the OS for its low end phones with 4gb ram, because oneplus has only two devices with 4gb ram: the n100 and n200. Oneplus put an OS designed for 6gb/8gb ram with mid-high end cpus on the N200 which has only 4gb ram and lower end cpu, and as a result, the N200 performs like a Motorola phone with 2gb/3gb ram.
Similarly speced Motorola phones perform much better than oneplus.
Ironically, if you update the N200 to android 12, the system will say the phone has a snapdragon 855 cpu, while it has a low end snapdragon 480 cpu. So basically oneplus software engineers just put an OS designed for high end phones onto the low end N200 without any optimization, and even forgot to change the cpu model name.
If you buy the carrier tmo/metro version, you need to obtain unlock token bin to unlock the bootloader, and you need to sim unlock first to enable OEM unlock or you can use the disabling Qualcomm uim app trick.
Click to expand...
Click to collapse
Care to elaborate on what this Qualcomm uim app trick happens to be?
So I went with the n20. Actually seems to be a pretty decent phone other than the fact that it shipped with a 7 digit serial so I can't get an unlock token. Been back and forth with OnePlus trying to get it resolved but they always just tell me they will email a response within a few days. Their last response was to add a zero before the serial. But doing so just gives me an error that the serial/unlock code don't match. Hopefully I can get this taken care of and get the bootloader unlocked. OEM unlock was easy peasy to get with the debloat script found elsewhere in the opo threads here
Actually I have to say this is one of the better performing devices that I've owned. Similar to some of the flagship phones I've had. Only the refresh rate I guess would be a turn off for some though it doesn't bother me at all.
N20 of course
6/128 can make big difference from N200
Due to limit of response time, 90Hz IPS may not be better than 60Hz AMOLED
695 is like 750 according to Geekbench
PsYk0n4uT said:
So I went with the n20. Actually seems to be a pretty decent phone other than the fact that it shipped with a 7 digit serial so I can't get an unlock token. Been back and forth with OnePlus trying to get it resolved but they always just tell me they will email a response within a few days. Their last response was to add a zero before the serial. But doing so just gives me an error that the serial/unlock code don't match. Hopefully I can get this taken care of and get the bootloader unlocked. OEM unlock was easy peasy to get with the debloat script found elsewhere in the opo threads here
Click to expand...
Click to collapse
Oem unlock means sim unlock or bootloader unlock?
eagle3489 said:
Oem unlock means sim unlock or bootloader unlock?
Click to expand...
Click to collapse
in short, bootloader unlock.
OEM stands for Original Equipment Manufacturer. It refers to the manufacturer lock on the bootloader. It is a security feature to keep you from accidentally bricking your device by tampering with the system images/files or malware from being able to modify or tamper with your system. This is why SafetyNet fails when you root and many banking apps and games check SafetyNet at the beginning of execution to make sure that your running a secure system before they allow an app to open. There are some ways to get around that by hiding root/magisk with Xposed modules(LSposed) etc... Some methods work for some apps and others dont. Make sure you have everything backed up before doing any modifications to your system because its easy to brick your device(make it unbootable/nonfunctional)
I havent found a way to SIM unlock without going through the carrier. There are services out there that claim to be able to SIM unlock your device for a fee, and many have been reviewed by other members. I have not personally ever used one. But here Im referring to unlocking the bootloader so that the system on the device can be modified (rooted, non-stock ROMs, system tweaks/mods)
ScarletWizard said:
I have the n20 and was able to unlock boot loader and root with still being carrier locked.
Click to expand...
Click to collapse
Yeah, mine is rooted tooted and reasdy to be booted and is sitll carrier locked and not paid off..
ScarletWizard said:
Post your t mobile bill. Here is mine View attachment 5772795
Click to expand...
Click to collapse
{
"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 read your posts and decided on the N20 as well and I must say this is an AWESOME little phone.
It came with the stock July OS. I have read many of the posts on here but I'm sort of stuck. I can't seem to figure out how to get a copy of the original OS. Read some options saying if i couldnt get a copy I could try to make one using twrp but that went down a dead end and I am back to square one. I have enabled developer mode, debug over usb, and set the setting to allow oem unlock and I'm kind of stuck at this point. My goal is to root this thing so that I can get call recording working like my older phones.
jonathandeath said:
I read your posts and decided on the N20 as well and I must say this is an AWESOME little phone.
It came with the stock July OS. I have read many of the posts on here but I'm sort of stuck. I can't seem to figure out how to get a copy of the original OS. Read some options saying if i couldnt get a copy I could try to make one using twrp but that went down a dead end and I am back to square one. I have enabled developer mode, debug over usb, and set the setting to allow oem unlock and I'm kind of stuck at this point. My goal is to root this thing so that I can get call recording working like my older phones.
Click to expand...
Click to collapse
File folder on MEGA
mega.nz
ScarletWizard said:
I brick my n20 daily trying exposed modules and I restore everytime using my boot.img backup
Click to expand...
Click to collapse
You should seriously flash this before anything and it'll save you from bootloop
Thank you so much! I am downloading now.
This is the one I picked up just for reference. 8 digit serial number on this model.
I disabled automatic updates and had the oem bootloader unlocked as well as all playstore options for updates disabled and this morning the phone updated itself without warning to the august update. It started talking about upgraded to android s and i factory reset it hoping it would roll everything back, but nope. Stuck on stupid August Update. I just wanted to get root back on it with call recording and lock down all android os updates.
ScarletWizard said:
Where do you find these zips. I haven't seen that in any repo
Click to expand...
Click to collapse
Hours and hours of shospelessly searching the bowels of th einternet my good man.
DrScrad said:
You should seriously flash this before anything and it'll save you from bootloop
Click to expand...
Click to collapse
How do I flash this first? I am starting fresh again tonight and want to do it right.
Gotcha,
So I have chosen to begin this portion with the following.
Disable DM-Verity or Android Verified Boot without TWRP
In this tutorial, we will show you the steps to disable DM-Verity or Android Verified Boot (AVB) without using TWRP Recovery.
www.droidwin.com
First step is to get a stock image file. However I have not been able to make a copy of my stock rom nor the current stock rom on my Phone now which is now on August patch 2022-09-05. I have downloaded several copies but there have been posts saying not to use just any version of stock rom so I'm trying to make sure i'm doing this right.
I am also on
Build Number CPH2459_11_A.08
Basebane version Q_V1_P14
Kernel version 5.4.147-qgki-g26211b5d5105
Hardware version CPH2459_11
I have the following files downloaded to work with.
I'm thinking of using this one.
Inside the following files can be found
If this is all right then I will try to continue with this portion of their instructional.
Does this sound about right?
Hi colleagues, I am looking for a copy to restore the partition for the LVM600TM30a model it is possible that the software will see the imei number, which is now invisible will you help me ?
someone will help me with this partition copy for my model
I just joined this community out of curiosity. I was a technical guy working for LG for over 8 years in mobile computing.
Having given my background info, let me say this that what you are seeking to restore (the IMEI plus network bands) is extremely difficult. First of all, nobody is going to give your phone the duplicate identity of their device. Period! Second, your phone is permanently locked with no operating bands. Reading through your earlier messages in this forum here is where you stand: You should buy a new phone. This one is done with! By wiping out all the partitions, you practically killed the device. If you were able to get into download mode then you could have gotten the partitions back BUT not the heart of the phone i.e., IMEI and operating bands.
Other users in this forum have already advised you the dead-end you have hit.
You will be surprised how many times I have seen some user trying to be curious and destroying their phones in the process. Your phone, for example, was working fine and then you tried to flash an unrelated firmware on it. I wonder what was the reason for doing that. Even if you were able to flash the intended firmware, it was going to give you problems because the operating frequencies would not be there.
The only option that you have is to try the MTK engineering mode app to regenerate the IMEI and operating bands. It is not guaranteed to resolve your issue but is the only option you got.
Good luck!
Since you worked in Lg, maybe you will know if sending the imei to the Lg service to repair the imei number makes sense?
LG will not honor the service you are requesting. Here is why:
1. You have unlocked the bootloader and rooted the device.
2. By deleting the partitions, you have lost the device IMEI and operational bands. That is intended misuse.
Neither of these factors are suggested by LG. So your warranty is out of the picture as well as any factory services you may seek.
I don't want the LG company to repair my phone under warranty because the warranty has expired. I just want to repair my software, of course I will be charged for this service
You are mistaking what he is clearly telling you. LG has NOTHING TO DO WITH YOUR PHONE. You have voided the usage conditions by manipulating the hardware.
Speaking for a lot of forum members, you need to put your situation to rest! You screwed up your phone permanently. Deal with it!
I contacted the LG service on the chat, I have to contact the service and send them a phone in to software repair, which I will also do on Monday
Just deal with your problems yourself, man! You have saturated this board to the hilt.
thieftime1980 said:
Hi colleagues, I am looking for a copy to restore the partition for the LVM600TM30a model it is possible that the software will see the imei number, which is now invisible will you help me ?
Click to expand...
Click to collapse
Is it a TMobile model? If yes there is a good chance it's possible to fix the IMEI.
I love how the other guy here trying to tell you to fix the IMEI with a mediatek engineering app lol
yes this is the t-mobile model I sent it to the Lg service yesterday I hope the LG service is able to fix it
>>I love how the other guy here trying to tell you to fix the IMEI with a mediatek engineering app<<
Instead of flaming a guy who is trying to give insight, it will be much better if you could provide info regarding how to recover IMEI from a deleted partition. Talking in vague terms does not help anyone including OP.
Leronex_1 said:
Is it a TMobile model? If yes there is a good chance it's possible to fix the IMEI.
I love how the other guy here trying to tell you to fix the IMEI with a mediatek engineering app lol
Click to expand...
Click to collapse
I have myself recovered phones' IMEI as well as operating bands using the MTK app. The problem is there are so many fake MTK engineering apps circulating. You sarcasm is amusing. Obviously you are not so well aware of mobile computing. Quite frankly, I challenge you to show us your way of recovering an IMEI/bands for a phone whose entire credentials have been wiped out. Enough said!
Commander_Bond said:
I have myself recovered phones' IMEI as well as operating bands using the MTK app. The problem is there are so many fake MTK engineering apps circulating. You sarcasm is amusing. Obviously you are not so well aware of mobile computing. Quite frankly, I challenge you to show us your way of recovering an IMEI/bands for a phone whose entire credentials have been wiped out. Enough said!
Click to expand...
Click to collapse
Dude I mean, come on you can do better than that. It says MTK=Mediatek and v60 is not Mediatek kekw But apparently you are a "technical guy" who "worked" with LG although for some reason you don't know what mtk actually stands for and for what CPU manufacturers this term is used lol.
Again if it is a TMobile device there is a good chance to recover the IMEI, dm me if you are interested.
That’s the irony. Even if it is originally designed for Mediatek, it DOES work for some other non-Mediatek phones. Just to open your eyes, check out some videos on YouTube! If you read earlier post, he had said that there is no guarantee that it will work for the OP’s V60. It works like a charm on LG K51, Q series.
BTW, I am still waiting to see your IMEI recovery procedure for a deleted partition! Back your claim and let us be the judge.
Royaltiger said:
That’s the irony. Even if it is originally designed for Mediatek, it DOES work for some other non-Mediatek phones. Just to open your eyes, check out some videos on YouTube! If you read earlier post, he had said that there is no guarantee that it will work for the OP’s V60. It works like a charm on LG K51, Q series.
BTW, I am still waiting to see your IMEI recovery procedure for a deleted partition! Back your claim and let us be the judge.
Click to expand...
Click to collapse
Guys you're all tripping, wtf. K51 is helio p22.
As to the imei recovery, flash the experimental tmobile image, flash 08s4 v600n efs partitions, change imei in hidden menu, reflash tmobile firmware and done.
Please elaborate on your suggested process. Where do you get the "experimental" image for V60 T-Mobile? I am assuming that you are suggesting to flash the efs partition in the download mode using LGUP partition mode?
Audio_Lover said:
Please elaborate on your suggested process. Where do you get the "experimental" image for V60 T-Mobile? I am assuming that you are suggesting to flash the efs partition in the download mode using LGUP partition mode?
Click to expand...
Click to collapse
I can only flash it with medusa, i told in my previous message to DM me if anyone is interested.
{
"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"
}
Its a srf file so only flashable with my medusa box
The problem with your solution is that it is available only to you (or with individuals who have Medusa). The restricted access does not make it a viable option.
Commander_Bond said:
LG will not honor the service you are requesting. Here is why:
1. You have unlocked the bootloader and rooted the device.
2. By deleting the partitions, you have lost the device IMEI and operational bands. That is intended misuse.
Neither of these factors are suggested by LG. So your warranty is out of the picture as well as any factory services you may seek.
Click to expand...
Click to collapse
This is total bs! I know for fact that the LG service center in Ft Worth, TX will work on anything for money. Locked BL, unlocked BL, cross flashed, it doesn't matter! If you can tell 'em what your imei was or what you think it was they will slap it on a machine, reload the software to the lastest spec (I think it takes them all of 10 minutes) be it AT&T, Tmob, Verizon, whatever. Don't tell me they won't because I had to send'm a lmv600at model that I screwed up! That's the reason I learned how to use Bkerler EDL utility and created these posts so I along with a lot of other people here wouldn't have to pay LG $42 plus shipping for a software reload.
LMV600AM Restore/Ugrade Guide
This restore process is intended for the AT&T V60 (lmv600am) model and will WIPE your data so back it up if you want to keep it! This process will restore the lmv600am to original factory state for the AT&T v60 v20q build (a11). I’ve dumped all...
forum.xda-developers.com
LMV600TM Restore/Ugrade Guide a12
This restore process is intended for the Tmob V60 (lmv600tm) model and you must WIPE your data so back it up if you want to keep it! This process will restore the lmv600tm to the state directly after the ota upgrade to the a12 v30b build. I’ve...
forum.xda-developers.com
All that being said, anyone who erases their imei info deserves what they get. I know!