[Screwed Up: I locked the Bootloader, Won't Boot, and Can't Unlock It]

On 5/8/2020 at 1:47 PM, D1ggs said:

As my engineer friends like to say, the job of an engineer is to make stuff that's idiot proof and the job of the universe is to make a better idiot.

In the case of this, the universe had a small victory.

 

This is the tool: http://files.nwwn.com/android/pro1/factory.html

This all started because a food truck I wanted to go to was only accepting Google pay. 

I relocked my bootloader while running LineageOS (using fastboot flash lock ). I was going to flash back to stock after I did this. However, after doing so the bootloader (screen that says START) on it would not accept any fastboot flashing commands. 

Anywho, with the help of FxTec and TDM, the issue is now resolved.

For those who stumble down this path like me, do not relock your bootloader when running custom firmware. You will get ample warnings before you are able to do so. 

If you do, contact FXTec Support for assistance.

Thanks team @Erik

I did this same exact thing for basically the same reason. How did you fix it? Please help.

[Pro1x is bricked, is there any way to save it?]

Not sure if this is the place but I screwed up. I was trying to go from Lineage to stock Android and misunderstood the instructions. I thought that it said that you simply have to lock the boot loader by running fastboot flashing lock. However after running this the phone will only boot into into bootloader or lineage recovery it will not boot into an operating system. If you try to run fasboot flashing unlock is says command failed unauthorized or something along those lines.  Is there a way to unlock without being able to enable developer options and usb debugging?

[Pro1x - really poor connectivity to both wifi and cellular.]

13 hours ago, Hook said:

That may very well be a Verizon thing. I had Verizon working for a while on my Pro 1 and I hit a point where, a little different, I could send texts but couldn't receive them.  My Pro1 on T-Mobile and my Pro1x on Ting work fine both in VA where I live and in CO Springs when I am visiting my son.

 

Sweet thanks for the info!

[Pro1x - really poor connectivity to both wifi and cellular.]

On 8/15/2024 at 11:36 AM, Hook said:

Yes, not really a LOS problem, so I moved your post here.  If the phone has poor connectivity, LOS won't change that.  It would be good to know more information such as where you live and what carriers you are using/have available. 

It's hit and miss.  Some Pro1xs work okay, other don't.  QA? Some networks work some don't? We don't know.  I'm lucky to have one that mostly works, although I still use it as a PDA. 

I am on Verizon in central Colorado. I did solder two of the spring connectors back on that I found were broken off at the same time that I replaced my battery. I did all that before/in order to get my phone to turn on for the first time. Just seems weird that I can take calls, make calls, and receive text but can not send a text. 

[Pro1x - really poor connectivity to both wifi and cellular.]

Not sure if I just missed it but my pro1x is running LOS 21. I don't know if it worked with stock android because I immediately installed UT then found that without VoLTE there is no point and installed LOS. My phone will receive text messages but will not send one. It always just says that the message failed to send tap to retry. Phone call connections are never very good either, though it sounds like that is normal for this phone.