Database Info

[Completed] Phone inoperable did nothing but followed steps.

Ok so I am unsure if someone is filtering out OLD topics but i keep coming across FORUM posts from people and it seems like they are getting no help or being referred to NON existent topics.
I just recently bought a HTC ONE M8 H/K from sprint. I have had android for a decade and am seriously tired of the ROOT it people. so I figured why not no down falls and everyone says it is easy. Well I am Murphy last name law and you people have not seen or know the things I am about to post
I recently spent over 32 hours watching video and preparing for ROOTING. I unlocked phone got Pilz touch recovery and everything worked fine. I even got CWM and SUPERSU and Busy box. all of which needed OTHER files to work properly. Again a few forced quits everything was fine.
I wanted to Switch to TWRP and the install didnt go through. however now I have BOOTloop. trust me this is the tip of the berg at this point.
Just short of finding NO help after another 24hrs binge session on the CPU and just shy of RUNNING MY PHONE OVER WITH A DAMN CAR>
I get oh so simple easy fix and the only posts I see are FIXED IT!!! so that helps me approximately as much as my phone helps me make phone calls currently.
After the boot loop SEVERAL friends versed in this so called ROOTING (which I still find to be a hoax and not actually possible by any means at this point and time.) and no one has any clue. Tried flashing ROMS RUU's everything comes back to NO will not work.
Then it brings me to the STOCK RUU config for the HK M8 which seemed like it was going to work through ADB flash but guess what. 2 hrs idle NOTHING. after that The recovery program dropped out and boot loader only stated RUU in the menu. (something never before logged in a forum or post as I can tell) after many attempts to do GOD KNOWS WHAT WITHOUT ANSWERS as i was about to smash my beautiful gold phone into a dozen tiny peices and claim accident the Recovery came back to...... You guessed it NOTHING. All directories are UNMOUNTED and cannot be mounted.
I am stuck. Seriously you all fix my phone or help i am willing to send gifts because I am out 700$ now on this nice paperweight but everything and everyone tells me. OH SO SIMPLE you have recovery it aint no thang.
Well guess what it is and I am tired of being so PISSED OFF for something that was so automated.
Again I am Murphy and what you attempt to get me to follow will come up with some REALLY weird repercussions I will post back.
Please oh mighty gods of ruining my life. Spare me this one thing I will never ask for another again.
How do I get my phone to just WORK, Simple. Right?

Hi there! I think I found a thread that can get you back on track. Please read every word carefully and follow every step. If you have further trouble or want to clarify anything, please ask in the thread. They know the device best and can help you I'm sure.
http://forum.xda-developers.com/showthread.php?t=2503646
I'm afraid that is the extent of what we do in the XDA Assist Section. We are guides...pointing people in the right direction when they can't find what they are looking for. Unfortunately we don't do hands on support in this section, so as I said....if you need a further hand, I am sure someone in the thread I linked can help.
And make sure anything you download and flash is for your model. And as always, do a Nandroid backup in recovery... before flashing anything new....it can be a lifesaver to help restore you when you hit trouble.
Good luck!

Details
Let me re iterate.
All guides are demanding S-Off (cannot as I cannot acess phone apps to do so)
All guides need HOME access for apps to modify certain things
I cannot:
Push packet through adb as they are unreadable
Get past boot screen
Recovery is only 40% operational with visibilty of phone only working sometime.
Cannot flash
Cannot push
Cannot fastboot
Cannot see device on CPU as it is stuck in recovery
ALL DIRECTORIES in /SDCARD have been removed
No Firmware
No RUU
No img
As far as I can tell.....Phone is empty and cannot be populated with anythin. I did manage to get SuperSu pushed through and installed. But how do I open it?
No ROOT access as well in the recovery.
I followed ALL STEPS of EASY guides even downloaded one button app that runs it all for me. Can't talk to phone does not see it in ADB.
The other guide I went to was helpful but I have already attempted all of those things.
With an empty phone NO DATA and no ability to get ADB to even run data over cable I am baffled.
I did exactly like the 500 guides i read said.
1) bootlock unlock
2)instal recovery (Philzmod)
3) get CWM (retrieved from playstore) Need a .zip to run in ADB
Phone worked fine until I changed from Philz mod to TWRP which never took place. Philz mod still runs but TWRP said it installed.
Now I have a completely worthless empty phone and I have cried about a tub worth of tears over the 700 i will be dropping over the next year for a piece of metal.
Oh and 99.9% of time if ADB DOES do something either no directory once pushed, cannot read or cannot FIND/Open directory stating BAD installation aborted I NEED a better recovery

I understand your frustration. Not a fun situation at all.
As I said, XDA Assist is here to help navigate the website. Not to troubleshoot I'm afraid.
The purpose of XDA Assist... http://forum.xda-developers.com/showthread.php?t=2764768
The very best place to ask for help in your situation is right here, in the Q&A section for your device... http://forum.xda-developers.com/showthread.php?t=2764768
The people there know your device best. Start a thread that's to the point, polite and accurate....what is exactly wrong, and the exact steps you took to get there. And hopefully help will follow.
Hope it can be solved for you!

[Completed] Is it possible to flash over a ROM to Android?

Hello
First of all, let me explain the situation:
My phone is the Oneplus One, currently with no OS, the reason being - because i wanted to re-root my phone after the Oneplus updated (this update was a while ago) either way many problems occurred and i figured the easiest way to re-root my device is to simply wipe it, and try again on a clean slate.
I attempted to wipe my phone, but did it the complete wrong way. Instead of using the OS's wiping strategy, i may of used the recovery's one instead, doing so i clean swooped the OS right off my phone.
At the moment, the phone has no OS installed - nor is the phone rooted. The phone isn't capable of passing files over through usb debugging because the computer doesn't recognise it no more. (It did have usb debugging turn't on). Of course i need to reinstall an OS on the phone. The TWRP recovery is working fine. But i do not know how to do it. I looked up things such as mounting, didn't really understand the vague explanations given by the helpers of this forum (i am slow haha :silly. If someone is able to point me in the right direction in how to simply put an OS back into the phone some how i would be grateful.
I did read up on one post that suggested making a system.img placing the OS inside and flashing it over using fastboot mode. Which brings me to the question. Is it possible to use command to install an OS on my Oneplus whilst in fastboot mode

RazorCJ123 said:
Hello
First of all, let me explain the situation:
My phone is the Oneplus One, currently with no OS, the reason being - because i wanted to re-root my phone after the Oneplus updated (this update was a while ago) either way many problems occurred and i figured the easiest way to re-root my device is to simply wipe it, and try again on a clean slate.
I attempted to wipe my phone, but did it the complete wrong way. Instead of using the OS's wiping strategy, i may of used the recovery's one instead, doing so i clean swooped the OS right off my phone.
At the moment, the phone has no OS installed - nor is the phone rooted. The phone isn't capable of passing files over through usb debugging because the computer doesn't recognise it no more. (It did have usb debugging turn't on). Of course i need to reinstall an OS on the phone. The TWRP recovery is working fine. But i do not know how to do it. I looked up things such as mounting, didn't really understand the vague explanations given by the helpers of this forum (i am slow haha :silly. If someone is able to point me in the right direction in how to simply put an OS back into the phone some how i would be grateful.
I did read up on one post that suggested making a system.img placing the OS inside and flashing it over using fastboot mode. Which brings me to the question. Is it possible to use command to install an OS on my Oneplus whilst in fastboot mode
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
Sorry to hear about your trouble but fortunately there is an XDA area dedicated to the OnePlus One at http://forum.xda-developers.com/oneplus-one . I suggest you post your question with all relevant details in the friendly Q&A forum there at http://forum.xda-developers.com/oneplus-one/help where the experts familiar with your device will be best able to guide you.
Good Luck!

[Completed] How do I unbrick my phone?

First of all, I'd like to say that I know very little about how Android, electronics or mobile phones work in general, so everything I've done has been from internet tutorials. Please don't use any jargon as I probably won't know what you mean. ELI5.
A few days ago, I tried to root my phone and it didn't work. As a result the phone went into a boot loop and I didn't know how to fix it. The long and short of it was that I ended up flashing the stock firmware onto my phone and basically doing a complete factory reset. After some time trying this I managed to get the phone to start up and I was able to access the interface and all that. Unfortunately, my WiFi wasn't working (the button would simply turn off whenever I turned it on) so I had no way to download the most recent updates or apps or anything like that. After following several tutorials on how to fix this, such as flashing the modems and bootloader, I still wasn't having any luck. So I tried something that proved to cause even more problems - I tried to install a new kernel. Now my phone won't even boot past the logo. I probably didn't install the right one, but what can I say, it's not very clear which one I need.
Now I'd like to point out that as a layman who just wants his phone to work again, half of the time I don't understand what I'm doing or whether or not I'm doing it right. In other words, I realise that I've probably messed up my phone, but what can I do? I can't take it to a technician because I don't have the money for that, I can't buy a new phone for the same reason and I can't phone up and ask for a replacement because the warranty expired ages ago and I don't have the original documents here.
I've installed the Team Win Recovery Project on my phone and I have Odin installed on my PC as well.
TLDR; yes, I know I'm an idiot and I don't appreciate you telling me. I'd like to reset my phone to how it was before - the normal firmware, the normal kernel and all that, but I'd still like to have root access and keep the TWRP recovery mode too.
Model: Samsung Galaxy S4 GT-I9505
Model name: GALAXY S4 LTE
Country: UK
Version: Android 5.0.1
You'll probably need more information, so if you do just let me know and, if possible, where I can find it.

I have some good news. I managed to flash the firmware again and now I can access the phone again. However, the WiFi problem persists. I've tried looking on the internet for a solution, but I can't find one. I've tried flashing the modem and all that stuff, but it still doesn't work.
Oh, and by the way, I no longer have TWRP and I don't think I have root access anymore either (I had to do a data partition wipe as well).

I'd really appreciate a reply from someone. I've tried everything, but to no avail.

einwaliser said:
First of all, I'd like to say that I know very little about how Android, electronics or mobile phones work in general, so everything I've done has been from internet tutorials. Please don't use any jargon as I probably won't know what you mean. ELI5.
A few days ago, I tried to root my phone and it didn't work. As a result the phone went into a boot loop and I didn't know how to fix it. The long and short of it was that I ended up flashing the stock firmware onto my phone and basically doing a complete factory reset. After some time trying this I managed to get the phone to start up and I was able to access the interface and all that. Unfortunately, my WiFi wasn't working (the button would simply turn off whenever I turned it on) so I had no way to download the most recent updates or apps or anything like that. After following several tutorials on how to fix this, such as flashing the modems and bootloader, I still wasn't having any luck. So I tried something that proved to cause even more problems - I tried to install a new kernel. Now my phone won't even boot past the logo. I probably didn't install the right one, but what can I say, it's not very clear which one I need.
Now I'd like to point out that as a layman who just wants his phone to work again, half of the time I don't understand what I'm doing or whether or not I'm doing it right. In other words, I realise that I've probably messed up my phone, but what can I do? I can't take it to a technician because I don't have the money for that, I can't buy a new phone for the same reason and I can't phone up and ask for a replacement because the warranty expired ages ago and I don't have the original documents here.
I've installed the Team Win Recovery Project on my phone and I have Odin installed on my PC as well.
TLDR; yes, I know I'm an idiot and I don't appreciate you telling me. I'd like to reset my phone to how it was before - the normal firmware, the normal kernel and all that, but I'd still like to have root access and keep the TWRP recovery mode too.
Model: Samsung Galaxy S4 GT-I9505
Model name: GALAXY S4 LTE
Country: UK
Version: Android 5.0.1
You'll probably need more information, so if you do just let me know and, if possible, where I can find it.
Click to expand...
Click to collapse
Hi
We have a dedicated help section for the S4, you'll need to start a new thread and ask there, providing as much info as you can:
http://forum.xda-developers.com/galaxy-s4/help
A [HELP THREAD] Galaxy S4 | Ask any question | Noob friendly thread is also available for you if you dont want to start a new thread.
Good luck.

engloa said:
Hi
We have a dedicated help section for the S4, you'll need to start a new thread and ask there, providing as much info as you can:
http://forum.xda-developers.com/galaxy-s4/help
A [HELP THREAD] Galaxy S4 | Ask any question | Noob friendly thread is also available for you if you dont want to start a new thread.
Good luck.
Click to expand...
Click to collapse
Hi engloa,
It's OK, I've fixed the problem now; I installed a different ROM and now it works fine. Thanks anyway though.

Revive Soft Bricked Device through Identical 2nd? (LG l21g Destiny Tracfone)

Long story short:
How do i get my current working android device to revive an identical soft-bricked device. More challenging than you think: there is no boot menu accessible in the devices. Which means the only other choice is to use a usb connection to a PC to perform all tasks, i.e. create a rom system image backup of the working device, then use that to restore the system onto the soft-bricked one.
So is there a way to revive the s/bricked device with a rom image of the working twin?
The long story:
After using the super-sume app, my device got softbricked. Phones of my type are uncommon and are therefore not worked on by the android hacker community as much as flagship devices are. And little is known or discovered about them. So after doing more research, i've sadly come to know that there are other users here and there, having suffered the same problem as I. But enough about that.
As far as i've read and come to understand, i would need to re-flash the firmware to bring it back from it's softbrick issue easiest/safest way.
Though am not sure how the android platform would work. With PCs, i could restore a messed up system from a cloned image. What i need to confirm is if the firmware is separate from the OS (roms i believe) the same way device drivers are separate from the windows OS on PCs.
So am not sure if flashing firmware is enough and would need to stock rom too. Or is the rom considered both firmware and OS all in one?
I mentioned "restore from a clone image backup" because I have another, exact same model of my softbricked device, that functions still properly.
So i wonder if there is a way that i could use my working device to revive the soft-bricked one. In the sense that i would need to make a system image copy of my working one, to restore onto the s/bricked one.
What the problem looks like when starting the phone:
As for the softbrick appearance, the phone boots into the LG logo screen and is frozen there. It doesn't quite look like it's boot looping since the screen Never fades to black quickly just to come right back. It's just frozen there. This recovery mode screen is the only other thing i can get to besides the frozen LG screen: https://wcrates.files.wordpress.com/2015/03/lg-g3-recover-mode.jpg
I've come to learn (but may need correction on) that Tracfone devices are deliberately handicapped in a way i've never seen before. That is, their devices have no other boot type of menu besides the Recovery Menu (found before os begins boot) that is basically a factory reset. It just deletes all user data and resets system settings so that the phone works like it would at first when right out of the box. For the s/bricked device, that screen can be accessed, though executing that just resorts to the frozen boot screen again. If there is a boot menu to backup/restore from, clear cache, install from zip and what not, then please enlighten me. Because as i've tried everything, the tracfone-devices have nothing compared to non-tracfone-devices
So in order to install an updated rom, i may need to get into a type of system boot menu from where i would be able to select the option to install a rom or update it and what not. To some degree i assume that connecting the device through USB to a computer, one may do the same rom installation action through the PC, but it's in cases like these where i would need the help of and expert's first hand experience with such things or ways.
I don't mind if you want to leave a link to some tutorial some other guy has made that may closely related to (if not exactly) to help solve this issue. But i do prefer to get into contact with someone who i can report to with how the solution process is progressing. Mostly because me being a noob at this point of my android experience, but am confident since i've done this with pc's a lot.
I'm still trying to figure out what most of the android community speaks of when it comes to methods of backing up their stock roms and what kinds of software on PC or apps on the device are needed to accomplish a worthy backup. I do realize i'd need ADB and what other LG device compatible PC software out there. Here is a link where i think firmware files can be found, but since it's all in Chinese, i'm not sure how reliable the site is/can be. It's been about a month since i contacted some of their users. At this point it seems like they're no hope:
http://mobile.gaodi.net/Firmware-669539-1-1.html
I hope that i can find success so that i can post it up to help others who are in the same situation as me, and also for the many more who may yet fall into this situation.
Any help will be greatly appreciated.
Thanks.
Device: LG l21g (aka lgl21g) Destiny (model) by TracFone
Android: 5.0.1

Proper OS cleanup of new OnePlu7 Pro

Hi Everyone,
Living in Japan, we have no official channel to purchase a OnePlus handset here.
Really wanted to get a OnePlus 7 Pro as I felt it is the best model on the market as of today.
Knowing that, I got mine on Amazon Japan from a HK online shop which had very good reputation.
Now, the problem is these phones always come already opened as they say they need to confirm operation before sending it.
I have been reading news and article about this where we see more third party companies flash their roms with malware/ransomeware already built in...
In these situation, the best way to clean the phone is to do a full re-install of the OS.
I did review a bunch of article on XDA and it seems that now, due to the A/B partition setup, we can't just use official OnePlus image to load from the fastboot easily.
We have to rely on community provided too and stock rom to be able to do so....
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Sorry if I sound paranoid. Ideally, I understand the best thing to do was to buy directly from Oneplus and work a way to have it shipped to Japan but thought it would be interesting for me to learn more about android.
With previous Oneplus, it was easier as they were provided this type of official file for recovery but they stopped...
Thank you again for your time and hopping to learn more about how new android setup works.

Is the bootloader locked? Is Widevine (Netflix HD) certification still there? You can check these things to see if the phone has been tampered with.

brissoukun said:
Hi Everyone,
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Thank you again for your time and hopping to learn more about how new android setup works.
Click to expand...
Click to collapse
Good questions. Before you start, check the model number of your device through Settings > About. I'm assuming it's the international/global/unlocked version (GM1917).
With regard to question 1, a full build downloaded from the link you provided should contain every part of the OS, and flashing it through local update should overwrite anything that was there before. Before flashing, I would perform a full data wipe through recovery like you mentioned.
Q2: There is an MSM tool that will completely flash a system image for the OP7 Pro. I don't think they're generally intended for public use but they always get leaked anyways. They write an image (in the case of OnePlus, a .ops file) to the phone using a PC and USB connection. Here is a link to a thread which contains the MSM tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Download the tool for the model of your phone (probably the international, firmware GM21AA), and extract its contents into a directory. In order for the tool to work, you need the OnePlus USB drivers installed on your PC. Plug the phone into your PC with it on, and enable USB file transfer. Open File Explorer and you should see a drive labeled "OnePlus drivers" or similar. Open it and run the driver setup executable file. You'll also need ADB to make your phone reboot into a mode that will allow the tool to perform its tasks. Here is a guide to installing ADB:
https://www.xda-developers.com/what-is-adb/
Once you've set that up, make sure the phone is plugged into the PC and the MSM tool is open. Make the phone boot into edl mode by typing
Code:
adb reboot edl
and once it says Connected next to a COM port in the tool, press start. Don't interrupt the process until it completes the download and the status message turns green. The phone should automatically reboot. This method is arguably more risky than using the local upgrade option, so do it at your own risk.
Q3: Make sure that OEM unlocking is turned off in developer settings and that the bootloader is locked (if the bootloader is unlocked, you'll see a yellow warning message after you power on the device from a power off state). Without an unlocked bootloader it would be pretty difficult to make any deep modifications to the device.

Hi @Zocker1304 and @TManchu,
Please let me thank you very much first for your kind and detailed reply, this is really welcome.
@Zocker1304:
I checked using the ADB/Fastboot connection that indeed, the Bootloader is locked so, that looks good.
Also installed (using a separate Google account) DRM Info app to confirm that the Widevine is properly installed and at L1 level which indeed again, looks good.
@TManchu
Thank you again for your very detailed reply! This was exactly what I needed as information.
I did already exactly as mentioned for the #1 so, it looks I should be good now with a proper rom from OnePlus (and did a full wipe in the Recovery boot mode)
For #2, I think I will skip that since as you rightly said, with #1, it should be fine so, prefer to keep with the recommended step.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:

brissoukun said:
.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:
Click to expand...
Click to collapse
No problem! I’ve just done some reading and from what I understand, re-locking the bootloader on anything other than a completely stock ROM will result in a bricked phone. I believe this is due to the way Android handles data encryption. If what you’ve heard is true, being able to lock your bootloader on a custom ROM would be great for device security. However, should something go wrong with the ROM having a locked bootloader might make it more difficult to fix.

I know that there are ways to sign system and boot images so that you can lock the bootloader with them installed, but I think that would still show a warning though I'm not sure.
Anyways, if all the build dates and numbers in the system info are correct, the firmware should be stock and as long as the bootloader is locked too, I don't believe you can tamper with that.

Hi Gents,
Thank you very much for the answer to the thread and much appreciated.
Apologies for not getting back to you all earlier as yesterday was family day...haha!
Well, since things looked good on the OS and the build, I went ahead and started to use the phone properly setting up my accounts. It did give me some incentive to get all my sensitive accounts setup with 2FA so that in case I get hacked with my passwords in the future...they would still need the 2fa (using Google Authenticator).
I did check also all system apps/running process and didn't see anything shady.
Just for reference, here were the type of articles I was refering too for the OS being plagued with malware even out of the box:
Page_theverge.com/2019/6/6/18655755/google-android-malware-triada-ota-rom-ads-spam-oem (sorry gents, new account, cannot put links yet)
However here, it seems it is due to lax review from the maker to third party tools which were including malware...
To have the same level on the oneplus I bought from the HK shop, they would have needed access to OnePlus Dev team to inject the malware in official image (knowing anyway I have re-installed a new image from the local update).
Otherwise, I was reading on the web about the fact to relock the bootloader with a custom roam and there seems to have a lot of messages but not concrete steps. It seems it depends a lot on phone model and brand.
When you are checking
Page_gizmochina.com/2019/06/10/relock-bootloader-oneplus-7-pro/
This is where you can read at the end:
"The above method only works if OnePlus 7 Pro is running on stock recovery and stock firmware. The ability to relock devices running custom recovery is expected in the next few weeks. "
That was published last month so, not sure if they got this to work on the OnePlus 7 pro yet.
So that's it, I am now using my new device which looks to work great and hopefully, won't get any bugs down the road.
I appreciate you taking the time to get back to me and will continue to learn about android.:good: