Database Users

[Discontinued]

Download and Install LG United Mobile Driver
Download and Install LG Mobile Support Tool​
Boot your phone into download mode:
Put your G2 into download mode by switching it off, hold the Volume up button and insert the usb cable into the phone; wait for the drivers to finish loading if doing it for the first time.​
Start the LG Mobile Support Tool and click on Options -> Upgrade Recovery
{
"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"
}
It should now download the firmware (about 2gb) and flash it - this may take some time.
This is needed if you stuck in a bootloop after the flash is done:
Factory reset (this wipe your data and sdcard):
1. Turn the phone off.
2. Press and hold the Power and Volume down button.
3. When the LG logo pops up let go for a second and press the combo again.
4. You'll be prompted to press the Power button 3 times to wipe the device.​

I would hate to have to use this, but wow what a good find. Thanks for contributing.
Sent from my LG-D800 using Tapatalk 4

Just got my g2. About to root install twrp etc. This is exactly what I was looking for. Thanks for posting.
Sent from my LG-D801 using XDA Premium 4 mobile app

For anyone putting in dashes with the imei number, dont it wont work with em.

Just wanted to notify that this method made my 32gb D802 a 16 gb one!

karstensson said:
Just wanted to notify that this method made my 32gb D802 a 16 gb one!
Click to expand...
Click to collapse
I used this method last night and it didnt mess with the storage at all. They don't even have a 16gb G2 so who knows. Also are you sure you are not mistaken cause this method doesnt wipe data.

x714x said:
I used this method last night and it didnt mess with the storage at all. They don't even have a 16gb G2 so who knows. Also are you sure you are not mistaken cause this method doesnt wipe data.
Click to expand...
Click to collapse
I know it does'nt wipe data, but it reflashes recovery, and in my case something went wrong. But Lg DO sell D802 as a 16 gb model!

Can anyone using this method please post results. Just wondering if there is more success with this method as opposed to the other method. Thanks.

Saved my bacon today!

karstensson said:
Just wanted to notify that this method made my 32gb D802 a 16 gb one!
Click to expand...
Click to collapse
I don't understand how could this be, you downloaded the specific firmware for your device (using your serial number)...
Can't you just try to flash it again ?

Noam23 said:
I don't understand how could this be, you downloaded the specific firmware for your device (using your serial number)...
Can't you just try to flash it again ?
Click to expand...
Click to collapse
I have reflashed it 5 times The problem was that it asked for some kind of password the first time (not the pin). So I did a factory reset. Now even TWRP says that my storage is 10.66 gb :/

karstensson said:
I have reflashed it 5 times The problem was that it asked for some kind of password the first time (not the pin). So I did a factory reset. Now even TWRP says that my storage is 10.66 gb :/
Click to expand...
Click to collapse
Which password exactly ? when ? in the process of flashing ? the OP mentions no stage in which you need to give password...
What are you going to do now ? your device is not rooted, so you can replace it under warranty, no ?

Noam23 said:
Which password exactly ? when ? in the process of flashing ? the OP mentions no stage in which you need to give password...
What are you going to do now ? your device is not rooted, so you can replace it under warranty, no ?
Click to expand...
Click to collapse
It did not say what the password was for, just asked for it. It came up after the phone had booted, but before i could see the lockscreen. I will wait a couple of weeks, to check if someone else gets the same problem, or if it is fixable. Otherwise i will hand it in on the warranty since there are not traces of root.

karstensson said:
It did not say what the password was for, just asked for it. It came up after the phone had booted, but before i could see the lockscreen. I will wait a couple of weeks, to check if someone else gets the same problem, or if it is fixable. Otherwise i will hand it in on the warranty since there are not traces of root.
Click to expand...
Click to collapse
Why should a password appear at that stage ???
If you went through all of the flash process successfully, booted successfully and only then did a factory reset (when you saw that password), I see no reason to blame the factory reset that you did. This is something to do with the flash process. Maybe this is kind of a punishment that LG unleash on those who use this process ? seriously, why on earth would anyone try to flash his LG2, if it wasn't to get rid of root ? I also don't understand how the password went away after you did hard-reset, since the device was "hard-reset" when you did that flash. You said that you re-flashed about 5 times, did that password appear after each of those 5 times ?

karstensson said:
Just wanted to notify that this method made my 32gb D802 a 16 gb one!
Click to expand...
Click to collapse
Same issue here.
I also got the question after I used the software to enter my encryptionkey. Wich I didnt have.
So I had to hardreset from the recoverymenu (volume down + pwr), then I suddenly had 10.77GB left instead of 26.77GB or something similar.
Annoys me pretty darn much at the time beeing!
I did use my IMEI, not my serialnumber and model. I'll try to use the serial and model this time around, and see if there are any differences at all in doing so.
And yes, it does say 32GB on the back. So we're not mistaken it for a 16GB-model
And it does say that the model is the 32GB when I check the hardware-info on the android itself.
Maybe this has something to do with me using the adbcommand for mounting storage incorrectly?
I thought however it would be reset when I used the LG Mobile Support Tool to hardreset everything though.

Will this work with the AT&T model D800?
Also does this remove all traces of root to the point where you get your warranty back?

what was the solution to this...

Does this work with the TMO versions?

The windows application keeps getting a Windows error and closing shortly after the process begins. Any tips?

I would prob stay away from this if i was anyone else....Because it must be messing people phones up and changing the storage capacity

Editing "software can't be checked for corruption" message from unlocking bootloader?

Editing "software can't be checked for corruption" message from unlocking bootloader?
I have rooted, modded, etc. my OnePlus 5 but that required me to unlock my bootloader. When you do that, it causes an ugly message to appear for 5 seconds at boot. I want to keep this message so I have 5 seconds to go into Recovery, Fastboot, etc and so myself and others will be aware that the bootloader is unlocked. However, I could make a much better design, maybe even add a changing countdown number until boot.
However, I don't know how to change it.
Does anyone know how to edit the "software can't be checked for corruption" message?
{
"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'm surprised this hasn't been changed as a couple of other phones have had this removed months ago...
I have an Axon 7 and that was solved a few weeks after it came about. There are fewer devs there than working on the One+ phones and we still have this undesirable boot screen every time we boot up...

keeganjk said:
I have rooted, modded, etc. my OnePlus 5 but that required me to unlock my bootloader. When you do that, it causes an ugly message to appear for 5 seconds at boot. I want to keep this message so I have 5 seconds to go into Recovery, Fastboot, etc and so myself and others will be aware that the bootloader is unlocked. However, I could make a much better design, maybe even add a changing countdown number until boot.
However, I don't know how to change it.
Does anyone know how to edit the "software can't be checked for corruption" message?
Click to expand...
Click to collapse
I don't think u can change it. It's becoming more and more common on phones now. There are some able to change on phones but with OnePlus I don't think so.

the_rooter said:
I don't think u can change it. It's becoming more and more common on phones now. There are some able to change on phones but with OnePlus I don't think so.
Click to expand...
Click to collapse
Can't flash with fastboot out something?

keeganjk said:
Can't flash with fastboot out something?
Click to expand...
Click to collapse
Explain? Alittle

the_rooter said:
Explain? Alittle
Click to expand...
Click to collapse
IDK, that's why I'm asking.

keeganjk said:
IDK, that's why I'm asking.
Click to expand...
Click to collapse
The screen u see is telling u that the bootloader is unlocked and that with that showing u can flash twrp, roms and root the phone. U can't flash factory imsges unless the bootloader screen that u see is showing .

ultramag69 said:
I'm surprised this hasn't been changed as a couple of other phones have had this removed months ago...
I have an Axon 7 and that was solved a few weeks after it came about. There are fewer devs there than working on the One+ phones and we still have this undesirable boot screen every time we boot up...
Click to expand...
Click to collapse
I don't want to GET RID of it, I just want to EDIT the image.

keeganjk said:
I don't want to GET RID of it, I just want to EDIT the image.
Click to expand...
Click to collapse
I really don't think u can. It's built I believe right in the bootloader or aboot . Maybe someone with more knowledge can confirm. But I believe it's there the way it is.

the_rooter said:
I really don't think u can. It's built I believe right in the bootloader or aboot . Maybe someone with more knowledge can confirm. But I believe it's there the way it is.
Click to expand...
Click to collapse
Again, this HAS been removed from the Axon 7... It doesn't sit there for 5 minutes with a blank screen then boot, it boots up as per normal without displaying the Bootloader unlocked" screen...

ultramag69 said:
Again, this HAS been removed from the Axon 7... It doesn't sit there for 5 minutes with a blank screen then boot, it boots up as per normal without displaying the Bootloader unlocked" screen...
Click to expand...
Click to collapse
Completely different phone. Not possible with OnePlus.

Some phones have the image in a separate partition on the flash memory.
These are easy to hack (although Google has made it harder to do that recently, with checksums).
For others, the image is embedded in the bootloader. Hacking the bootloader is very risky as any mistake will end up with a brick.
OP5 is the latter.
You can change the OS boot picture. You can change the OnePlus logo that's displayed first. But not that warning. I even think the warning is mandated by the Android certification process.

Bricked phone. Being a massive dumbass

Hey. I've bricked my Huawei P10 lite, literally just for the sole reason alone that I'm an idiot. I was in the process of relocking/unrooting when I did a massive choke - I've relocked the bootloader and IMMEDIATELY closed the goddamn tab. I haven't written the code down anywhere. When I've rebooted my phone, I discovered I have exactly 0 ways of doing a wipe, since the TWRP was obviously gone.
Hitools returns that the phone cannot be recovered due to not being supported.
Recovery? There isn't one. eRecovery always returns "failed to get.." yatta yatta yatta, It's not working.
The only thing currently reacting to my commands is fastboot. And, being the mr. obvious, I cannot push files onto the phone through fastboot to restore it by the full package, which was pretty much my only option at this point.
There aren't any replacement motherboards available for the P10 lite on eBay or pretty much anywhere else I could think of.
If there exists any good soul that can tell me if this is in any imaginable way reversible without getting a cracked screen phone and swapping the motherboards, PLEASE, PLEASE, do tell me.
{
"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"
}
Thank you.

INB4 anyone asks - No, I don't have the numbers to generate the code again either. At least not the serial id, i think.

EvESpirit said:
INB4 anyone asks - No, I don't have the numbers to generate the code again either. At least not the serial id, i think.
Click to expand...
Click to collapse
Did u tryed to flash original firmware by the dload method?
You don need unlocked boatloader for that. I already save my p10 few times.

hdemary said:
Did u tryed to flash original firmware by the dload method?
You don need unlocked boatloader for that. I already save my p10 few times.
Click to expand...
Click to collapse
How can I flash the original firmware? I can't even flash a recovery. The bootloader is l o c k e d, and the only thing I can access is fastboot. How am I supposed to push the files into the phones in fastboot???

EvESpirit said:
How can I flash the original firmware? I can't even flash a recovery. The bootloader is l o c k e d, and the only thing I can access is fastboot. How am I supposed to push the files into the phones in fastboot???
Click to expand...
Click to collapse
Man if you can't even google dload method to find out how to return to stock you r screwed.
But anyways i will help you with that: http://lmgtfy.com/?q=huawei+p10+lite+dload+method

I DO NO HAVE A WAY TO PUSH THE REQUIRED FILES INTO THE DEVICE FOR THE REASONS OF LOCKED BOOTLOADER, NO RECOVERY AND NO WAY TO BOOT INTO THE SYSTEM. If you would kindly tell me how tf would it work from an OTG flash device, go ahead. Spoiler alert: It won't
MOD EDIT: Mind your language

EvESpirit said:
I DO NO HAVE A WAY TO PUSH THE REQUIRED FILES INTO THE DEVICE FOR THE REASONS OF LOCKED BOOTLOADER, NO RECOVERY AND NO WAY TO BOOT INTO THE SYSTEM. If you would kindly tell me how tf would it work from an OTG flash device, go ahead. Spoiler alert: It won't
Click to expand...
Click to collapse
Man as your post title says, you really are a massive dumbass, if you at least try to help your self with the link i send you u will see that dload method dont need to boot into system, no need for recovery and no need for unlocked boatloader, only an sd card with a folder that have original firmware for your variant.
But as you rude keep your phone as a brick.
Regards!

EvESpirit said:
I DO NO HAVE A WAY TO PUSH THE REQUIRED FILES INTO THE DEVICE FOR THE REASONS OF LOCKED BOOTLOADER, NO RECOVERY AND NO WAY TO BOOT INTO THE SYSTEM. If you would kindly tell me how tf would it work from an OTG flash device, go ahead. Spoiler alert: It won't
MOD EDIT: Mind your language
Click to expand...
Click to collapse
Mind your language my friend.
This is an official caution for you.
If you have any doubts, check the FORUM rules

EvESpirit said:
>mfw mods ignore somebody attacking someone first and call me out for using bad language+edit the comment, yet still leave the actual swear happen without deleting
OMEGALUL so relevant
@hdemary If you would kindly learn to read. For the third time I'm telling you that ThErE Is No Way For Me to PUSH the FILES to the PHONE. I do not have an unlocked bootloader nor a functioning recovery AND NO DEVICE to put them on. Also nice OP dodge, but I guess that's just them being unbiasedly biased.
Click to expand...
Click to collapse
My last post in this thread.
Why u ask for help in the first place if you won´t accept?
Have fun with your bricked device!
Best of the best Regards! :angel:

Well, seems this thread has run its course
Thread closed

Bought a Samsung Tab A SM-T387V, apparently has doordash on it, how can I wipe it and use it as a normal tablet?

EDIT 2022-06-30: FOUND A RELIABLE SOLUTION FOR MY NEW T307U TABLET! May work for other models! https://forum.xda-developers.com/t/...e-it-as-a-normal-tablet.4316969/post-87091297
Original post from 2021-08-09 below:
Following this thread to no avail: https://forum.xda-developers.com/t/doordash-knox-customized-tablet-unable-to-remove.3890522/
Setup requires an internet connection, at which point it sets up MobiControl:
{
"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"
}
My friend's an IT so he set up Meraki for me which I can enroll in instead of MobiControl, but a minute later this pops up:
I still have access to the settings but cannot enable USB Debugging.
I flashed a combination file which got me to the "factory binary" where I can unlock OEM and enable USB Debugging, but I don't know where to go from here:
I flashed a stock ROM, but that doesn't get rid of doordash and MobiControl during setup.
Please help!

Which Android version did you flash? Did you finally get rid of MobiControl?

XDA.Samsung said:
Which Android version didn't you flash? Did you finally get rid of MobiControl?
Click to expand...
Click to collapse
I solved this. Basically, I accidentally bricked the tablet, which I assume is what caused Samsung Knox to fail and thus Mobi Control didn't try installing on a fresh flash of Android 8.1. Fuller story below:
After 3 days straight of trying to reset the tablet, including flashing the combo file, trying anything I can think of, re-flashing the stock rom and seeing if the problem is gone, I finally fixed it.
What ended up happening was, while re-flashing the stock rom on my 4th attempt, I flashed the AP but not one of the other things (I guess CP?) which resulted in the tablet getting bricked.
Long story short, I held both volume buttons and power to boot into a blue download mode (as opposed to a black one via holding power down + volume and selecting download mode, since the volume down + power nor the volume up + power combos weren't working) and flashed the stock rom to it properly.
Upon setup, I was still required to set up wi-fi, but it didn't attempt to install mobicontrol! I've been using the tablet normally since. Who would have known accidentally bricking the tablet was all I needed to do!

genesisboy4 said:
I solved this. Basically, I accidentally bricked the tablet, which I assume is what caused Samsung Knox to fail and thus Mobi Control didn't try installing on a fresh flash of Android 8.1. Fuller story below:
After 3 days straight of trying to reset the tablet, including flashing the combo file, trying anything I can think of, re-flashing the stock rom and seeing if the problem is gone, I finally fixed it.
What ended up happening was, while re-flashing the stock rom on my 4th attempt, I flashed the AP but not one of the other things (I guess CP?) which resulted in the tablet getting bricked.
Long story short, I held both volume buttons and power to boot into a blue download mode (as opposed to a black one via holding power down + volume and selecting download mode, since the volume down + power nor the volume up + power combos weren't working) and flashed the stock rom to it properly.
Upon setup, I was still required to set up wi-fi, but it didn't attempt to install mobicontrol! I've been using the tablet normally since. Who would have known accidentally bricking the tablet was all I needed to do!
Click to expand...
Click to collapse
Good to know. Congratulation. Does it still show secured by knox on boot screen?

I had no luck. I can't flash anything, got error "MDM mode, can't download ".

XDA.Samsung said:
Good to know. Congratulation. Does it still show secured by knox on boot screen?
Click to expand...
Click to collapse
Yes, it does.
XDA.Samsung said:
I had no luck. I can't flash anything, got error "MDM mode, can't download ".
Click to expand...
Click to collapse
Make sure you're using the right version of odin for your tablet and you're flashing the right version of android.

genesisboy4 said:
Yes, it does.
Make sure you're using the right version of odin for your tablet and you're flashing the right version of android.
Click to expand...
Click to collapse
Which version of Odin did you use?

XDA.Samsung said:
Which version of Odin did you use?
Click to expand...
Click to collapse
Odin3_v3.13.3

genesisboy4 said:
Odin3_v3.13.3
Click to expand...
Click to collapse
After tried 5 versions of Odin, include 2 different v3.13.3, finally got a good news. I can flash T387v firmware Andriod 8.1 and 9. But the bad news is I cannot brick it, no matter flashed only AP or BL. I tried to flash with T387W or T387T firmware, I got PIT error messages.
Which version of firmware were you using?

XDA.Samsung said:
After tried 5 versions of Odin, include 2 different v3.13.3, finally got a good news. I can flash T387v firmware Andriod 8.1 and 9. But the bad news is I cannot brick it, no matter flashed only AP or BL. I tried to flash with T387W or T387T firmware, I got PIT error messages.
Which version of firmware were you using?
Click to expand...
Click to collapse
I think I installed android version SM-T387V_1_20200520121029_yelpqjg66y_fac.

genesisboy4 said:
I think I installed android version SM-T387V_1_20200520121029_yelpqjg66y_fac.
Click to expand...
Click to collapse
Thank you. It looks like it's Android 9. Did you update it to Android 10?

XDA.Samsung said:
Thank you. It looks like it's Android 9. Did you update it to Android 10?
Click to expand...
Click to collapse
It's Android 8.1. If that file I mentioned is 9, then it's not the one I flashed, but was instead on my to-do list of troubleshooting steps. I was going to try flashing Android 9 and 10 but I got it working with 8.1 so I'm keeping it on that. Plus, the newer the android, the more secure Samsung Knox will be, so it will be harder breaking it.

Any idea where you downloaded it from? I cant seem to find a link.

quiqsilverr said:
Any idea where you downloaded it from? I cant seem to find a link.
Click to expand...
Click to collapse
Android 10: https://samfrew.com/download/Galaxy__Tab__A__/1hjk/VZW/T387VVRU3CUI2/T387VVZW3CUI2/

"The fact that it has MobiControl installed suggests it's a company device, and is therefore administered by that company's IT department. It's probably going to be difficult to remove MobiControl unless you talk to that IT department about it."
The above is a quote I found regarding Knox and the MobiControl app. Which tells me that this thread, although likely unintentional, is violating XDA Forum Rule #9:
9. Don't get us into trouble.
Don't post copyrighted materials or do other things which will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably shouldn't do it here either. This does not mean that we agree with everything that the software piracy lobby try to impose on us. It simply means that you cannot break any laws here, since we'll end up dealing with the legal hassle caused by you. Please use common sense: respect the forum, its users and those that write great code.
Click to expand...
Click to collapse
XDA does not wish to be held liable for circumventing device security regardless of intent of the user, which is why I'm closing this thread.
-Regards: Badger50

Question URGENT! Nothing Phone stuck in fastboot after DSU loader

{
"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"
}
Hi. i was curious about the DSU loader so i installed it and rebooted. But it started bootlooping then showed the "system is corrupt" message. After that it rebooted and only went into fastboot after that, Im a bit panicked since the phone is only a couple hours old and I forgot to unlock the bootloader. if anyone knows how to fix this itd be appreciated.

I did quite a lot of flashing and rooting and as far as I know, there should be an option withing fastboot to reboot to bootloader. But I am not aware of the Nothing recovery image.
When in bootloader, you can then unlock the device with fastboot commands via command line.
Have you tried any of that?

miris83 said:
I did quite a lot of flashing and rooting and as far as I know, there should be an option withing fastboot to reboot to bootloader. But I am not aware of the Nothing recovery image.
When in bootloader, you can then unlock the device with fastboot commands via command line.
Have you tried any of that?
Click to expand...
Click to collapse
sadly doesnt work since oem unlocking is off, and i cant access the os. it seems its in slot b right now, but i cant switch slots due to a locked bootloader.
any ideas would help

why use DSU?if you are stupid in this matter? say goodbye to the phone

Curiosity got the best of me. I used DSU cause I thought I would be able to keep it locked

Seaman228 said:
why use DSU?if you are stupid in this matter? say goodbye to the phone
Click to expand...
Click to collapse
Why do you trash the topic with anything but any attempt for help? Drop the keyboard and take a walk.

Someone had to say it

miris83 said:
Why do you trash the topic with anything but any attempt for help? Drop the keyboard and take a walk.
Click to expand...
Click to collapse
Trash? I told the truth, if you're crying I'm sorry

You really forgot rule 1 in android modding.
Unlock.
The.
****ing Bootloader.

Seaman228 said:
Trash? I told the truth, if you're crying I'm sorry
Click to expand...
Click to collapse
And even more trash ... You are a waste of time, man.

gordonsosig said:
View attachment 5711879Hi. i was curious about the DSU loader so i installed it and rebooted. But it started bootlooping then showed the "system is corrupt" message. After that it rebooted and only went into fastboot after that, Im a bit panicked since the phone is only a couple hours old and I forgot to unlock the bootloader. if anyone knows how to fix this itd be appreciated.
Click to expand...
Click to collapse
As I see it now, this might be your best bet at this point: https://forum.xda-developers.com/t/...t-centre-and-staff-14-september-2022.4492645/
The staff is pretty friendly. I already reported some bugs and it was just fine.

Use "fastboot getvar current-slot" to get your current slot then switch to the other slot with "fastboot --set-active=a" or "fastboot --set-active=b" I believe those commands work even with a locked bootloader.

Seaman228 said:
why use DSU?if you are stupid in this matter? say goodbye to the phone
Click to expand...
Click to collapse
it's Nothing's fault for screwing up their DSU implementation. On a locked bootloader it should either boot the DSU image (like Pixel), or reject it and boot back to normal system. In NO CIRCUMSTANCES it should BRICK the device like this
Google didn't mention the best way to install the Android 12 Beta on Pixel phones
DSU is the best way to install the Android 12 Beta release on Pixel phones, but Google totally neglected to mention it.
www.xda-developers.com
As you have locked bootloader and no OEM unlock, it's essentially a hard brick since no MSM tool is available. Take it to the service center ASAP.

nguyenlucky said:
it's Nothing's fault for screwing up their DSU implementation. On a locked bootloader it should either boot the DSU image (like Pixel), or reject it and boot back to normal system. In NO CIRCUMSTANCES it should BRICK the device like this
Google didn't mention the best way to install the Android 12 Beta on Pixel phones
DSU is the best way to install the Android 12 Beta release on Pixel phones, but Google totally neglected to mention it.
www.xda-developers.com
As you have locked bootloader and no OEM unlock, it's essentially a hard brick since no MSM tool is available. Take it to the service center ASAP.
Click to expand...
Click to collapse
sadly i live in switzerland so there isnt any service center i can get to. so either we find a solution or the phone collects dust on my shelf

nguyenlucky said:
As you have locked bootloader and no OEM unlock, it's essentially a hard brick since no MSM tool is available. Take it to the service center ASAP.
Click to expand...
Click to collapse
On the other hand the MSM tool may exist only as an internal tool which they might provide on request in such situations. As you pointed out in the article, they messed up the implementation. To be honest, I wonder how this may have happened in the first place - to boot into mode which should not be available with the booloader unlocked. And given the company has a past link with OnePlus and OnePlus does have an MSM tool ...
Unless @gordonsosig asks the support, he will not know.

Have a look here : https://forum.xda-developers.com/t/nothing-phone-1-flashing-utilities.4478457/
And there : https://forum.xda-developers.com/t/help-to-developers.4484061/

I also went into this issue with disabled OEM Unlock. My phone was repaired for free in the customer care because I had an warranty. I wrote an email about this issue to the producer because I think it should not be possible to hard brick the phone by playing with developer options. I hope they will fix it.
And I think moderator should pin this thread to be always on top, because people should see the varning, this can save users from bricking their phones.

kuba3351 said:
I also went into this issue with disabled OEM Unlock. My phone was repaired for free in the customer care because I had an warranty. I wrote an email about this issue to the producer because I think it should not be possible to hard brick the phone by playing with developer options. I hope they will fix it.
Click to expand...
Click to collapse
where do i send it? is it in person or mail in? any help is appreciated

I returned my phone into the place where I buy it, and they sent it to the customer care. There is an official website: https://pl.nothing.tech/ so I think you can find an information about how to send your phone or use an Contact us link and I think they will help you.

kuba3351 said:
I returned my phone into the place where I buy it, and they sent it to the customer care. There is an official website: https://pl.nothing.tech/ so I think you can find an information about how to send your phone or use an Contact us link and I think they will help you.
Click to expand...
Click to collapse
guess im ****ed. already contacted them but i bought the phone from ebay so they said just contact ebay