Database Users

[Q] Is the new HTC EVO bootloader really locked??

I KNEED AN ANSWER TO THIS SUBJECT.
I have read some of the posts about the new EVO 4G update, and some of the people have complained about the new update has a locked bootloader.
I need to know is it really locked?
I downloaded a Android 2.3.3 update a couple of months ago, and it came with the new fastboot option enabled by default. With fastboot enabled, the phone boots much faster, but you would be locked out of the bootloader. That was only until you disabled it. Then it was business as usual getting into the bootloader (volume down + power button).
Now I hear that some of the people who have downloaded the latest (unrooted) EVO update have their bootloaders locked, while others were able to do a nandroid recovery to restore their phones after updating because the phone was still S-OFF. That would mean that the bootloader is still unlocked. How can a bootloader be both locked and unlocked.
Is the bootloader really locked by the update, or is it just temporarily locked because these people did not turn off the fastboot option in the settings, which does bypass the bootloader. Does anyone know, or how many people know the answer to this?

It's locked and not encrypted is what I believe.
Sent from my PC36100 using Tapatalk

novanosis85 said:
It's locked and not encrypted is what I believe.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Any sources for this information, or did I overlook a post?

how to access recovery after 2.3.3 update
1.Turn phone off. 2. Remove battery from phone. 3.Hold Volume button down and power button at same time for like 7 seconds. 4. That's it.

If you get a new EVO 4g with 2.3.3 yes it will be locked. HTC said all future devices will be unlocked that is why the EVO 4g is still locked.
The EVO 4g OTA and 2.3.3 out of the box is not encrypted just locked.
Source: me doing a lot of reading today.

Locked. Not encrypted.
I have a hunch that HTC meant to say that their bootloaders would no longer be encrypted rather than locked.

pharmteckCA said:
1.Turn phone off. 2. Remove battery from phone. 3.Hold Volume button down and power button at same time for like 7 seconds. 4. That's it.
Click to expand...
Click to collapse
When are you supposed to put the battery back in??? I'm confused

soxfan81 said:
When are you supposed to put the battery back in??? I'm confused
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"
}
Sent from my PC36100 using Tapatalk

If you were s off when updating, you will still be able to flash recoveries and roms etc. If you were s on and updated, your SOL for now.

exSD said:
Locked. Not encrypted.
I have a hunch that HTC meant to say that their bootloaders would no longer be encrypted rather than locked.
Click to expand...
Click to collapse
First of all, there isn't a phone out there with an encrypted bootloader. There are however cryptographically signed bootloaders. Huge difference.
Second, they did in fact say the bootloaders will no longer be locked.

Rakeesh_j said:
cryptographically
Click to expand...
Click to collapse
That's a crazy serious word right there.

mattykinsx said:
That's a crazy serious word right there.
Click to expand...
Click to collapse
+1 it makes me feel retarded.
HTC EVO = my best friend

I wonder if we can just OEM unlock it in fastboot?

RileyGrant said:
If you were s off when updating, you will still be able to flash recoveries and roms etc. If you were s on and updated, your SOL for now.
Click to expand...
Click to collapse
So, if someone's phone is still S-OFF after updating, and they could just flash another recovery, and then a ROM or backup, then how is the bootloader locked?

shortydoggg said:
So, if someone's phone is still S-OFF after updating, and they could just flash another recovery, and then a ROM or backup, then how is the bootloader locked?
Click to expand...
Click to collapse
Good question
Sent from my PC36100 using XDA App

shortydoggg said:
So, if someone's phone is still S-OFF after updating, and they could just flash another recovery, and then a ROM or backup, then how is the bootloader locked?
Click to expand...
Click to collapse
if your not S-OFF you can't.
asked and answered.

Alanmw86 said:
if your not S-OFF you can't.
asked and answered.
Click to expand...
Click to collapse
That did not answer the question.
The question was if your phone is S-OFF, then how is the bootloader locked, NOT WHAT YOU CANNOT DO IF YOUR PHONE IS NOT S-OFF. We already know that.
The reason I asked this question, is because some people have installed the latest update and rerooted their phones because the phones were still S-OFF. This would seem to suggest that the bootloaders are not locked.
If you do not turn off the fastboot option in the settings, or reset the battery, the bootloader will be bypassed, making it appear that the bootloader is locked when it may not be. I would like to know if anyone installed the latest (unrooted) update, and disabled the fastboot or reset the battery, and found that the bootloader is in fact locked.

My guess is that the update doesn't check your security bit, however it still prevents custom firmware from being loaded in that there isn't any mechanism available to load any custom firmware.
In other words, if your security bit is off already, and you update, you can still place a pc3600.img on your sdcard and have it flash that without it performing a signature check first.
However if your security bit is on at the time of applying the update, then you're a bit SOL, because prior to flashing the new image, it will perform a signature check.
Again, that is just my guess (haven't looked at the update as I've been using AOSP for a long time now.)

shortydoggg said:
That did not answer the question.
The question was if your phone is S-OFF, then how is the bootloader locked, NOT WHAT YOU CANNOT DO IF YOUR PHONE IS NOT S-OFF. We already know that.
The reason I asked this question, is because some people have installed the latest update and rerooted their phones because the phones were still S-OFF. This would seem to suggest that the bootloaders are not locked.
If you do not turn off the fastboot option in the settings, or reset the battery, the bootloader will be bypassed, making it appear that the bootloader is locked when it may not be. I would like to know if anyone installed the latest (unrooted) update, and disabled the fastboot or reset the battery, and found that the bootloader is in fact locked.
Click to expand...
Click to collapse
I had S-off and ran the OTA, no problem turning off the fast boot option and flashing either Clockworkmod or AmonRa. But I did have to switch to AmonRa in order to run the update, it wouldn't install with CWM.

tempe38 said:
I had S-off and ran the OTA, no problem turning off the fast boot option and flashing either Clockworkmod or AmonRa. But I did have to switch to AmonRa in order to run the update, it wouldn't install with CWM.
Click to expand...
Click to collapse
Does anyone who still has S-OFF and installed the new OTA have the new hboot version 2.16?

Read through noob guides but still having problems with the auto BL unlock

I've been thinking about it for a while but decided to give it a try today . The step that tells me to hold up I get but then how so I power down to activate fastboot ?
Sent from my Atrix-4G, stock 2.3.4 (rooted)

DopeHack said:
I've been thinking about it for a while but decided to give it a try today . The step that tells me to hold up I get but then how so I power down to activate fastboot ?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse
hold volume down button while booting up, then hold volume up after fastboot is selected to activate it.
after that, you use fastboot commands on your computer.

But I was using the automatic unlocker . I still need to put in commands myself?
Sent from my Atrix-4G, stock 2.3.4 (rooted)

DopeHack said:
But I was using the automatic unlocker . I still need to put in commands myself?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse
Did you ask in that thread?
Sent from my MB860 using xda premium

DopeHack said:
But I was using the automatic unlocker . I still need to put in commands myself?
Click to expand...
Click to collapse
I believe the automatic unlocker will pause and should give clear instructions ask you to do specific things that have to be done by a human (power down and reboot into certain mode, etc), you just need to follow these instructions. After that, you just hit enter to continue.
If you are unable to follow these instructions, probably it's too much for you...
To reboot into fastboot, for example: press the power button, to turn off the phone; then hold the volume down button, press the power button again, you'll see "Fastboot", then release volume down, press volume up, you enter the "fastboot" mode

Too much for me lol I know how to get to all the menus that its telling me to go to but nothing else happens. the guide said nothing about typing in anything which is why I choose it. Especially since the automatic root worked easy as pie ...
Sent from my Atrix-4G, stock 2.3.4 (rooted)

You want help, laugh when people who are trying to help say it might be too much for you, yet you provide us close to absolute no information.
What guide are you following? We might know, but it still is your job to provide a link.
What is the step you are stuck at?
Why, what isn't going according to plan? What do you see happening in your sceen / phone?
If you can't explain properly, provide some screenshots.
You say you can get to all the menus it tells you to, yet in the first step you can't seem to get into fastboot. Your speech is unclear and what you want is hard to understand.
My opinion is you aren't ready to unlock your bootloader. You know very little about your phone or how it works. That's the community's fault really, with all these automatic scripts, which are really nice if you know what you're doing, but end up promoting easy ignorance in people like you.
I just hope in a month or two you are not one of those writing "OMG, please, I arrempted to downgrade by SBF and know my phone won't boot, what gives???"
Read up on some information a learn how these things work. It is the best you can do. Owning an android device and modding it can be great fun, but it does require some effort on your part. If I were you, I would learn how to unlock my bootloader with pudding, just to understand what is actuallly going on.
Either that, or you can learn how to ask for help properly and politely. Your choice.
Also, wrong section, This is not Q&A.

My girlfriend was rushing me so I tried to type up something quick but I used this
http://forum.xda-developers.com/showthread.php?t=1182871
As you can see like I can see it does not say I need to type anything in the cmd (which I have seen in YouTube videos and isn't that hard) but thought hey automatic sounds good so I gave it a try I don't have any problems getting the phone to fast boot or rsd as I've used the stock recovery to clear cache in an attempt to fix something. The part I'm stuck at is step 6
You are right I don't know alot about android which is why I didn't start messing with my phone the day I got it but I've been all over this site (well the atrix at least) and YouTube.
I appreciate any help and sorry for the misplaced thread
Sent from my Atrix-4G, stock 2.3.4 (rooted)

DopeHack said:
My girlfriend was rushing me so I tried to type up something quick but I used this
http://forum.xda-developers.com/showthread.php?t=1182871
Click to expand...
Click to collapse
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think

So, let's see if I got this, you are having trouble at the part it says it should restart? Or before that? After you choose the number and press enter, what happens?
This could be a driver problem... If windows is not recognizing a device, it's common... Which windows are you using? I used to have some problems on XP and vista...

Newbleeto said:
So, let's see if I got this, you are having trouble at the part it says it should restart? Or before that? After you choose the number and press enter, what happens?
This could be a driver problem... If windows is not recognizing a device, it's common... Which windows are you using? I used to have some problems on XP and vista...
Click to expand...
Click to collapse
Right where it says it should restart and go into fastboot nothing happens I could hold that power button all day. I knew vista would bring an issue into the mix cause it never made the sound for connecting the phone but the SD cards show up
Sent from my Atrix-4G, stock 2.3.4 (rooted)

sanriver12 said:
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think
Click to expand...
Click to collapse
This is the one I read before thanks hopefully my girlfriend will disappear for a hour or two (she doesn't want me to ruin my phone) so I can work on it .
so with this one I can use fauxs 1.3 or 1.45Ghz kernal with cm7 I've been craving that ice cream sandwich ..
Sent from my Atrix-4G, stock 2.3.4 (rooted)

Computer is down for a while seems like it wasn't meant to be but Im still going to get it done
Sent from my Atrix-4G, stock 2.3.4 (rooted)

I actually had to use a Vista system to get this to work.
Now, when the instructions say it should "Restart", at that point, have you been in "Fastboot" yet? Have you been to the part where you have to enter your "Unique ID"?
This is important to know because throughout the bootloader-unlocking process the phone should be restarted a couple of times. It sounds like you have at least gotten through the part where it flashes "Pudding" but it sounds like you haven't done the "fastboot" part yet.
Are you referring to "Step 6" in the actual post or within the script? If the power button does not work then just pull the battery. As long as it is not in the process of doing something you should be fine.
I also want to point out that the program you are using only requires that you type in your Unique ID, everything else is automated, not to mention the file contains everything you need including adb, fastboot, RSDlite, Superuser, Pudding, and a working recovery so it makes it very easy for the end user to not have to find everything on their own. The script unlocks the bootloader, roots your phone, and flashes CWM recovery.
Either way, please provide more details if you are still having issues. Good luck.
DopeHack said:
Right where it says it should restart and go into fastboot nothing happens I could hold that power button all day. I knew vista would bring an issue into the mix cause it never made the sound for connecting the phone but the SD cards show up
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse

live4nyy said:
I actually had to use a Vista system to get this to work.
Now, when the instructions say it should "Restart", at that point, have you been in "Fastboot" yet? Have you been to the part where you have to enter your "Unique ID"?
This is important to know because throughout the bootloader-unlocking process the phone should be restarted a couple of times. It sounds like you have at least gotten through the part where it flashes "Pudding" but it sounds like you haven't done the "fastboot" part yet.
Are you referring to "Step 6" in the actual post or within the script? If the power button does not work then just pull the battery. As long as it is not in the process of doing something you should be fine.
I also want to point out that the program you are using only requires that you type in your Unique ID, everything else is automated, not to mention the file contains everything you need including adb, fastboot, RSDlite, Superuser, Pudding, and a working recovery so it makes it very easy for the end user to not have to find everything on their own. The script unlocks the bootloader, roots your phone, and flashes CWM recovery.
Either way, please provide more details if you are still having issues. Good luck.
Click to expand...
Click to collapse
I wasn't blaming vista I was just saying cause I've had problem with that is in the past.
I've basically done nothing haven't flashed or wiped my phone yet I was basically stuck at or around the first step cause it first asks for RSD protocol and then it says restart phone but the power button has no effect why in that mode nd when I pull the battery to manually put it in fast boot nothing happens nd I get some kind of batch error when it trays to get my unique id...
But got the computer back today so I'm gonna work on it again
Thanx for help ... will update you guys when I can

sanriver12 said:
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think
Click to expand...
Click to collapse
Actually, I followed the method you linked (old netbook running XP) and got a softbrick on the automatic reboot after flashing pudding. I was so busy watching RSD Lite do its thing that I didn't catch that my phone had actually rebooted; it selected fastboot mode on its own so I was able to issue the unlock command. It took.

"7.Plug your device into your computer. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…” The acronym 'NS' may be different for your device people!!"
its not doing this(i have rsdlite 4.5.5 because i cant find 5.5)
edit: got on to next problem

Thanks everyone
{
"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"
}
Sent from Atrix 4G running CM7 ICS Final @ 1.2Ghz

If cpu not recognizing ur device in fastboot try restarting ur cpu. If u updated drivers u have to restart the cpu before it will see ur device.
Sent from my MB860 using xda premium

REVERT TO STOCK & RELOCK BOOTLOADER FROM PUDDING (My experience how i did it)

Well i was needing revert my custom firmware and bootloader to stock (also relock bootloader)
but i was very afraid about you can revert uncloked bootloader if you do it with Pudding
http://forum.xda-developers.com/showthread.php?t=1136261
My atrix 4G (MB860) comes with the latest v4.5.145 (AT&T)
{
"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"
}
And I was running CF SuperLite_CM10_V8, with TWRP 2.6.3 Recovery
I decided to flash de SBF file running the risk of a brick, but i was reading this post
http://www.grupoandroid.com/topic/76554-downgrade-de-45145-a-141-y-unlock-bootloader/
If i get a soft-brick....
I use RSDLite 6.1.5 + MTK PATCH to flash
And 1ff-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-att-us-gas_na_olpsgbattspe_p012.sbf.gz as my flash file
And if you are reading this post it's because you allready have installed your MotoDrivers rigth?
(I do it from my Win 8 Computer, x64 system)
My Result? a MB860 Stock 2.3.6-4.5.141 with Locked Bootloader
Later i perform an upgrade from my phone to 2.3.6-4.5.145 (Moto Blur ID rerquired)
To end one more time in my first same version.
If you decided to do this IT'S ALL UNDER YOUR OWN RESPONSABILITY!!!
I'm just sharing my own experience!!!
Conclusion: It's posible Restock & Relock from Pudding Without Brick your MB860 Atrix 4G :good:
Saludos desde Tijuana B.C MX :laugh:
Any Gramatical Correction are welcome!, English it's not my natal Language!

klonic0 said:
Well i was needing revert my custom firmware and bootloader to stock (also relock bootloader)
but i was very afraid about you can revert uncloked bootloader if you do it with Pudding
http://forum.xda-developers.com/showthread.php?t=1136261
My atrix 4G (MB860) comes with the latest v4.5.145 (AT&T)
And I was running CF SuperLite_CM10_V8, with TWRP 2.6.3 Recovery
I decided to flash de SBF file running the risk of a brick, but i was reading this post
http://www.grupoandroid.com/topic/76554-downgrade-de-45145-a-141-y-unlock-bootloader/
If i get a soft-brick....
I use RSDLite 6.1.5 + MTK PATCH to flash
And 1ff-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-att-us-gas_na_olpsgbattspe_p012.sbf.gz as my flash file
And if you are reading this post it's because you allready have installed your MotoDrivers rigth?
(I do it from my Win 8 Computer, x64 system)
My Result? a MB860 Stock 2.3.6-4.5.141 with Locked Bootloader
Later i perform an upgrade from my phone to 2.3.6-4.5.145 (Moto Blur ID rerquired)
To end one more time in my first same version.
If you decided to do this IT'S ALL UNDER YOUR OWN RESPONSABILITY!!!
I'm just sharing my own experience!!!
Conclusion: It's posible Restock & Relock from Pudding Without Brick your MB860 Atrix 4G :good:
Saludos desde Tijuana B.C MX :laugh:
Any Gramatical Correction are welcome!, English it's not my natal Language!
Click to expand...
Click to collapse
Way late on this. Everybody knows how to return to stock.

palmbeach05 said:
Way late on this. Everybody knows how to return to stock.
Click to expand...
Click to collapse
Well... hehe :silly:

Stuck in the same boat! Please advise...
Many thanks klonic0 for your post, it has given me hope!
I am stuck in a similar situation with an AT&T Atrix 4G that has the v4.5.145 unlocked bootloader and absolutely refuses to flash back to the stock 1ff-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-att-us-gas_na_olpsgbattspe_p012.sbf image.
The phone experiences frequent SODs and drains its battery extremely quickly.
The Motorola RSD lite (with the MTK patch) keeps failing at "switching to BP Pass through mode".
(I have tried about 7 variations from windows xp through to Windows 8.1 on 32 and 64 bit machines.
After which I am back to square one, i.e. a "Failed to boot 1" error message on the top left corner of the phones screen, I then have to flash anyone of the following three sbf files to get the phone working again:
pudding.sbf or 4547-fix-try2.sbf or trololol-unlock234.sbf
Is there any hope to flash back this phone back to the stock image with a locked bootloader?

bevilz said:
Many thanks klonic0 for your post, it has given me hope!
I am stuck in a similar situation with an AT&T Atrix 4G that has the v4.5.145 unlocked bootloader and absolutely refuses to flash back to the stock 1ff-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-att-us-gas_na_olpsgbattspe_p012.sbf image.
The phone experiences frequent SODs and drains its battery extremely quickly.
The Motorola RSD lite (with the MTK patch) keeps failing at "switching to BP Pass through mode".
(I have tried about 7 variations from windows xp through to Windows 8.1 on 32 and 64 bit machines.
After which I am back to square one, i.e. a "Failed to boot 1" error message on the top left corner of the phones screen, I then have to flash anyone of the following three sbf files to get the phone working again:
pudding.sbf or 4547-fix-try2.sbf or trololol-unlock234.sbf
Is there any hope to flash back this phone back to the stock image with a locked bootloader?
Click to expand...
Click to collapse
Yes, it should be working. Did you factory reset? Did you look into what failed to boot 1 means?
Sent from my ATRIX HD using XDA Free mobile app

Update: No results yet...
palmbeach05 said:
Yes, it should be working. Did you factory reset? Did you look into what failed to boot 1 means?
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse
Hi Palmbeach05! Thank you for replying so quickly.
Yes I have factory reset the device before every attempt to flash the sbf using RSD Lite, and I have looked into the "failed to boot 1" error as well, it follows the information from this "quote" on the Atrix 4G GSMarena.com page 5:
"to all those people out there who own a motorola atrix 4g and have unlocked their bootloader 4.5.145 and are having sleep of death issues aka SOD where the phone does not wake up after a period of inactivity download moto software updater from motorola website and follow the on screen instructions moto software updater will download the stock 4.5.145 and automatically flash it and finally u will get rid of sleep of death issues and remember u will have to be in stock firmware the moto software update wont recognize your phone if u are on cyanogenmod word of advice if u are already on 4.5.145 never unlock the bootloader because there is no unlockable bootloader for 4.5.145 all the unlocked boootloaders are from previous versions so even though they unlock the phone there will be consequences like sod and random reboots on high temperatures so bottom line is u have to go back to stock many people will tell u to flash via rsd lite but trust me rsd lite is of no help as it wont be able to flash successfully because 4.5.145 sbf is not available and rsd cant downgrade so it will give an error message error switching phone to BP pass through mode but the moto software updater will be able to download the 4.5.145 sbf from motorola website and flash it automatically"​
Unfortunately I have had absolutely no luck with the Motorola software update software package either.

I realize this is an old thread, but I'm very interested in this and I couldn't find the right information.
Motorola has given me the run around because none of their links ever work anymore (like this one: https://forums.motorola.com/posts/9bae279371).
Is there any sort of official md5 checksum for this file? How do you know you're downloading something legit from 4shared?
Thanks so much.

Back from Repair - Fastboot Flash Mode (Not Secure) and "ENGINEERING"

Hi all,
so after I cracked my Screen I send my device to a service provicer to repair it. The device is back and the display is fine again.
Though there are certain concers on which I'd need advice. Service provider did not react to my E-Mail yet.
So my Style was bootloader unlocked before and had TWRP installed. Though never rooted. Now that the device is back, it seems that the bootloader is locked again and when I boot into Fastboot I see two entries which concern me:
1.)
AP Fastboot Flash Mode (Not Secure)
(in red)
2.)
Device is ENGINEERING
(in yellow)
As well, the IMEI number changed and my Storage doubled. 32 -> 64 gig (which is not bad though ). Not sure why that happened. Probably so much glue that they needed to exchange more.
Another consequence is, that I'm not able to unlock the bootloader again, which bothers me somewhat. I get the key from Motorola, but when I run the fastboot command it fails with a short display flash on the phone.
So, long story. Do you guys know if the two entries mentioned in Fastboot are problematic in some way? Are those keeping me from unlocking again? Can I fix those on my own if necessary?
Best regards
Simon

An Engineering Bootloader is supposed to be completely unlocked, even more so than regular "bootloader unlock" if the official Moto forums are to be believed, it cannot be changed to locked or unlocked (fails every time), but in the Moto G 3rd gen community here we have several users with an engineering bootloader status and they have very sporadic issues with ROMs. For example RR 5.7.2 works but 5.7.3 fails, CM13 older nightlies work but current ones fail, certain kernels work and others do not, it is very weird.
To my (limited) knowledge, this is the first Engineering bootloader seen on a X Style/Pure here, you are in uncharted waters so proceed with caution...

FYI... Due to the fact that several users have seen this in the Moto G community, and it's started showing up in the Moto X Pure community, I posted in the Lenovo forums for more information on this in this thread.
The response was quite clear from AlphaDog (Moto Sr Moderator):
The phones should not be showing Engineering. If you get a phone back this way, it was not flashed properly and needs to be reflashed - call customer service and make arrangements to have it reflashed.
Click to expand...
Click to collapse

If your storage doubled and IMEI changed, then one if two things happened. 1. They gave you another phone other than your own (very likely), or 2. They seriously borked it when they reinstalled the ROM (which would explain the ENGINEERING status).

aybarrap1 said:
If your storage doubled and IMEI changed, then one if two things happened. 1. They gave you another phone other than your own (very likely), or 2. They seriously borked it when they reinstalled the ROM (which would explain the ENGINEERING status).
Click to expand...
Click to collapse
Due to weird issues that Moto G have... I'm leaning towards #2, or both.
Sent from my Motorola XT1575 using XDA Labs

Thanks all for your responses. I'm very sorry for my late reply, gmail hid the subscription emails in some subfolder (=
So an indeed very weird issue. I can confirm that it is at least the original outer frame of my phone. I had one customized from Moto maker and it had some unique scratches So they probably f***** up installation / flash. I'll try to get back with that provider an see what they say about it.
The first response on my question WHY that is, and that I'm now unable to unlock my bootloader was:
"Why are you booting Fastboot instead of normal? And you loose warranty if you unlock!"
...which of course is neither an answer to one of my questions nor helpful in any way.

I also had sent my phone in for repair a few months ago (screen stopped responding to touch, they wouldn't fix it because root, replaced myself, very frustrating ordeal) and have a similar issue.
I don't have the same colored entries as you, but every single time I boot now it goes directly to the bootloader instead of starting up normally. This includes when I reboot while using the phone, as well as when specifically using the advanced reboot menu to go into recovery which basically makes the whole menu pointless.
Very annoying problem when you have to wait for the bootloader to startup and then press the button to get it to start.
Anyone have any ideas on how to fix it?
Sent from my XT1575 using XDA-Developers mobile app

black_valor said:
I also had sent my phone in for repair a few months ago (screen stopped responding to touch, they wouldn't fix it because root, replaced myself, very frustrating ordeal) and have a similar issue.
I don't have the same colored entries as you, but every single time I boot now it goes directly to the bootloader instead of starting up normally. This includes when I reboot while using the phone, as well as when specifically using the advanced reboot menu to go into recovery which basically makes the whole menu pointless.
Very annoying problem when you have to wait for the bootloader to startup and then press the button to get it to start.
Anyone have any ideas on how to fix it?
Click to expand...
Click to collapse
fastboot oem fb_mode_clear
Sent from my Motorola XT1575 using XDA Labs

hdyim said:
Hi all,
so after I cracked my Screen I send my device to a service provicer to repair it. The device is back and the display is fine again.
Though there are certain concers on which I'd need advice. Service provider did not react to my E-Mail yet.
So my Style was bootloader unlocked before and had TWRP installed. Though never rooted. Now that the device is back, it seems that the bootloader is locked again and when I boot into Fastboot I see two entries which concern me:
1.)
AP Fastboot Flash Mode (Not Secure)
(in red)
2.)
Device is ENGINEERING
(in yellow)
As well, the IMEI number changed and my Storage doubled. 32 -> 64 gig (which is not bad though ). Not sure why that happened. Probably so much glue that they needed to exchange more.
Another consequence is, that I'm not able to unlock the bootloader again, which bothers me somewhat. I get the key from Motorola, but when I run the fastboot command it fails with a short display flash on the phone.
So, long story. Do you guys know if the two entries mentioned in Fastboot are problematic in some way? Are those keeping me from unlocking again? Can I fix those on my own if necessary?
Best regards
Simon
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"
}
The two entries never gave me any problems I also have an engineering bootloader.
Sent from my XT1572 using XDA-Developers mobile app

[email protected] said:
The two entries never gave me any problems I also have an engineering bootloader.
Click to expand...
Click to collapse
It doesn't give you an problems because your still stock. Moto has officially said this shouldn't happen and anyone with this should contact customer support to get it flashed correctly.
Sent from my Motorola XT1575 using XDA Labs

acejavelin said:
It doesn't give you an problems because your still stock. Moto has officially said this shouldn't happen and anyone with this should contact customer support to get it flashed correctly.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
So then for me no need to worry.. Not planning to flash anything other then stock and as long it doesn't give any problems with rooting and flashing some mods I won't return it ...
Sent from my XT1572 using XDA-Developers mobile app

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