Database Info

[Q] (Q) Urgent: My Xoom stuck at booting screen

Hello everyone,
I just received an MZ604 Xoom from my friend, current OS is 4.0.3, and I want to upgrade it to 4.1. However, when I tried to root my device by Tiamat Kernel 1.3.1, after typing in cmd "fastboot flash boot boot.img", it's ok. Then I entered "fastboot reboot", the tablet just frozen at boot screen. Here is what I have tried so far and got no result:
- Try to restart it by holding power off and volume up
- Try to turn of completely by holding power off button (it didn't turn off)
- Factory reset from recovery mode
Can you guys help me on this, I'm a newbie to this stuff. Thank you very much!!!!!!!
In addition, my tablet was brought at Singapore, no there is no official upgrade to 4.1 ...

Can you get into fastboot mode? Volume down and power with your xoom off. If you can we can fastboot your xoom back to stock and start over from scratch. Is it a us version?

dfib1 said:
Can you get into fastboot mode? Volume down and power with your xoom off. If you can we can fastboot your xoom back to stock and start over from scratch.
Click to expand...
Click to collapse
I cannot even turn off my tablet, but I can enter fastboot mode by pressing Power + volumn up, then wait 2 sec and press volumn down to select. But I already factory reset it in recovery mode, problem still persists :crying:

ADICpanasonic said:
I cannot even turn off my tablet, but I can enter fastboot mode by pressing Power + volumn up, then wait 2 sec and press volumn down to select. But I already factory reset it in recovery mode, problem still persists :crying:
Click to expand...
Click to collapse
follow the steps here to install adb on your pc ADB one click it is a one click method
create and folder on your pc c:\xoom
download this file xoom wifi restore and unzip it into the folder you created.
click on the xoom_restore.bat
follow the on screen instructions.
try and reboot your xoom
let me know how you made out
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
Your xoom will be back to stock out of the box. I know it sucks to start over but you should be running.

dfib1 said:
follow the steps here to install adb on your pc it is a one click method
create and folder on your pc c:\xoom
download this fileand unzip it into the folder you created.
click on the xoom_restore.bat
follow the on screen instructions.
try and reboot your xoom
let me know how you made out
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
Your xoom will be back to stock out of the box. I know it sucks to start over but you should be running.
Click to expand...
Click to collapse
I enter "adb devices" in cmd and it gave me 16 digit number, so I guess I don't have to install adb again?
And by the way, follow your instruction mean my tablet will go back to android 3.0?

dfib1 said:
follow the steps here to install adb on your pc ] it is a one click method
create and folder on your pc c:\xoom
download this file and unzip it into the folder you created.
click on the xoom_restore.bat
follow the on screen instructions.
try and reboot your xoom
let me know how you made out
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
Your xoom will be back to stock out of the box. I know it sucks to start over but you should be running.
Click to expand...
Click to collapse
Thank you very much!! It works!!!!

[Q] Non-stop bootloop...

Hello,
Yesterday, I tried to flash my moto g to install cyanogenmod 11 with cwm recovery.
But after the installation, bootloop with the little blue head.
I want to flash it again but the phone is not recognized by my pc, and I installed the drivers...
So I can't install a new rom, and I have no backups.
HELP !

Burned-Z said:
Hello,
Yesterday, I tried to flash my moto g to install cyanogenmod 11 with cwm recovery.
But after the installation, bootloop with the little blue head.
I want to flash it again but the phone is not recognized by my pc, and I installed the drivers...
So I can't install a new rom, and I have no backups.
HELP !
Click to expand...
Click to collapse
Pres power for 2min should be turn off. Then try power and volume down to enter the fastboot. If you succeed, then download the proper stock rom for your device from http://sbf.droid-developers.org/phone.php?device=14 then follow this guide to recover the phone http://forum.xda-developers.com/showthread.php?t=2542219
If you cant enter fastboot then i really don't know. Then It should be done by side loading the rom, but have no experience with that. regards

bobrda said:
Pres power for 2min should be turn off. Then try power and volume down to enter the fastboot. If you succeed, then download the proper stock rom for your device from http://sbf.droid-developers.org/phone.php?device=14 then follow this guide to recover the phone http://forum.xda-developers.com/showthread.php?t=2542219
If you cant enter fastboot then i really don't know. Then It should be done by side loading the rom, but have no experience with that. regards
Click to expand...
Click to collapse
Already tried, in the cmd.exe it's written " < waiting for device > " when I type the commands...
It's not taken by the warranty ?

sideload method for phone http://forum.xda-developers.com/showpost.php?p=51601244
---------- Post added at 12:56 PM ---------- Previous post was at 12:53 PM ----------
Burned-Z said:
Already tried, in the cmd.exe it's written " < waiting for device > " when I type the commands...
It's not taken by the warranty ?
Click to expand...
Click to collapse
Don't know for warranty. Try to instal GPE rom or some other. it should be past. I have had a problem with German rom, but with GB rom i succeed. I have a 1032 version

bobrda said:
sideload method for phone http://forum.xda-developers.com/showpost.php?p=51601244
---------- Post added at 12:56 PM ---------- Previous post was at 12:53 PM ----------
Don't know for warranty. Try to instal GPE rom or some other. it should be past. I have had a problem with German rom, but with GB rom i succeed. I have a 1032 version
Click to expand...
Click to collapse
I can't install any rom, my device isn't recognized by my PC

Burned-Z said:
I can't install any rom, my device isn't recognized by my PC
Click to expand...
Click to collapse
really don't know that. try to reinstall Motorola drivers, or adb. Try another usb on computer..

bobrda said:
really don't know that. try to reinstall Motorola drivers, or adb. Try another usb on computer..
Click to expand...
Click to collapse
Only "Motorola MTP Device" is recognized, but I can't click it.

Here the screen shot. Where its saying XT 1032 it is a power up phone. Where it say adb interference it is in fasboot mode. regards

bobrda said:
really don't know that. try to reinstall Motorola drivers, or adb. Try another usb on computer..
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g/general/unbrick-method-t2794271

eg0097 said:
http://forum.xda-developers.com/moto-g/general/unbrick-method-t2794271
Click to expand...
Click to collapse
Thnks for this. I put it in the bookmarks if there would be a necessary :good:

[Resolved] One Plus 3 OxygenOs 3.2.2 Installation failed

Hi, I have been using One plus 3 for a week now. Today I received new update 3.2.2 After downloading it, started the update. However after some time, the installation window is saying "Installation failed" with only reboot option given. I am really confused right now. Note : This phone is Chinese variant and was given OxygenOS while purchasing. Any help regarding this would be much appreciated.

farhan37 said:
Hi, I have been using One plus 3 for a week now. Today I received new update 3.2.2 After downloading it, started the update. However after some time, the installation window is saying "Installation failed" with only reboot option given. I am really confused right now. Note : This phone is Chinese variant and was given OxygenOS while purchasing. Any help regarding this would be much appreciated.
Click to expand...
Click to collapse
Same issue. i thought it may be a security with my unlocked bootloader so i reflashed stock recovery and relocked the bootloader. Still failed.
Trying adb sideload now. Will let you know if it works
---------- Post added at 07:04 AM ---------- Previous post was at 07:01 AM ----------
mayerlench said:
Same issue. i thought it may be a security with my unlocked bootloader so i reflashed stock recovery and relocked the bootloader. Still failed.
Trying adb sideload now. Will let you know if it works
Click to expand...
Click to collapse
Success!! Adb sideload the full oxygenos 3.2.2 full rom(1.3gb) and youll be up and running.
Let me know if you need help.

mayerlench said:
Same issue. i thought it may be a security with my unlocked bootloader so i reflashed stock recovery and relocked the bootloader. Still failed.
Trying adb sideload now. Will let you know if it works
---------- Post added at 07:04 AM ---------- Previous post was at 07:01 AM ----------
Success!! Adb sideload the full oxygenos 3.2.2 full rom(1.3gb) and youll be up and running.
Let me know if you need help.
Click to expand...
Click to collapse
Thats great ! However, I am newbie to these things ! Could you please suggest a step by step guide for the procedure ? Thanks a lot in advance.

farhan37 said:
Thats great ! However, I am newbie to these things ! Could you please suggest a step by step guide for the procedure ? Thanks a lot in advance.
Click to expand...
Click to collapse
First you need adb on your computer.
1. Download the ADB For Windows from here :- https://drive.google.com/open?id=0B0...VB1elljU2NPR0k
2. Run the .exe file downloaded from above as Administrator.
3. Press 'Y' every time the installer asks.
4. Continue Driver Installation.
Now,ADB and Fastboot have been installed on your PC. Great
1. Now, go to settings>aboutphone>click buildnumber 10 times to activate developer options.
2. Settings>developer options>enable usb debugging
3. Dowbload the update to your pc fron here: https://mega.nz/#!o4EhnCDZ!lG3IrVdAc6ceIbSLQRRvOzZrzGhL-DObCg0oBtncgDc
4. Connect phone to pc. and boot phone into recovery by powering down phone and booting back up while holding volume down and power button. Using volume buttons navigate to recovery. Use power button as select.
Now go to advanced and click the adb option while in recovery mode.
5. Open command prompt on your pc. Type "adb sideload (Update file zip)".
Type without the quotes and the update zip file is the big file you downloaded, just drag and drop it onto the command prompt window without the parentheses obviously.
Hopefully this helps
let me know if you need more help

Sony Xperia E5 F3311 [Root][Guide][Twrp]

After a lot of struggles, we've finally managed to root the Sony Xperia E5.
If you own this device and would like to root it, this thread will guide you through the process.
Requirements:
-You must have the correct drivers installed!
You can't proceed without them as the adb interface won't recognize your device.
-The modified boot.img for 37.0.A.2.156 which you can download here
-The modified boot.img for 37.0.A.2.248 which you can download here
-Twrp recovery which you can download here
-The adb interface, google it.
-Your bootloader must be unlocked via the Sony official method. If you can't find the E5 in the list, you can use the code of the E4g.
-Supersu 2.79 zip which you can download here
-An equal kernel (boot.img) to your desired firmware version. 37.0.A.2.156+37.0.A.2.156 or 37.0.A.2.248+37.0.A.2.248.
-The no-verity encryption fix (optional): (link to be added)
-30 minutes of your time.
I'm not responsible for any possible damage caused to your phone, even though it most likely won't go wrong if you follow the instructions carefully.
I can, however, provide support if your device is stuck in a bootloop.
I won't reply to questions, of which the answers are already mentioned in this thread.
YOU MUST MAKE SURE YOU'VE DOWNLOADED THE KERNEL THAT IS MEANT FOR YOUR SPECIFIC FIRMWARE VERSION!
IF THE TWO AREN'T EQUAL, YOU'LL HARD BRICK YOUR DEVICE AND YOU'LL HAVE TO AGREE THAT I WON'T BE HELD RESPONSIBLE!
Instructions:
1. Unlock your bootloader, check out Sony's website to see how.
2. Check whether the boot unlock succeeded or not.
To do so, you can open your dialer and type *#*#7378423#*#* .
A screen will appear, tap on service info and go to configuration.
Check the rooting status:
*If it says 'bootloader unlock allowed=yes' it means your bootloader is still locked.
*If it says 'bootloader unlocked=yes' it means your bootloader is unlocked.
3. Install the correct drivers for your device, Sony adb+fastboot etc.
4. Go to the root directory of your adb folder, location depending of where you installed it.
Hold Shift and right click to show a menu.
In that menu there should be an option called 'open command prompt here', click on it and it should start adb.
5. Make sure to enable usb debugging on your device.
6. Connect your phone to your computer and type this command in adb:
Code:
adb devices
If your device shows up, it means adb recognized your device and you may proceed.
If it doesn't show up you have to double check your installed drivers in device manager.
7. Type
Code:
adb reboot bootloader
to reboot the device to fastboot.
8. Now you'll have to flash the kernel and recovery.
Put both of the files into the root directory of the adb folder and rename them to boot.img and recovery.img, type
Code:
fastboot flash boot boot.img
to flash the kernel and type
Code:
fastboot flash recovery recovery.img
to flash the recovery.
9. Unplug your device and boot into twrp by pressing the power+volume down buttons. Keep holding the volume down button and release the power button quickly.
10. When you're in twrp, head to 'wipe'->'advanced wipe'->'(user)data partition'.
This step is optional, but recommended to avoid problems with encryption.
Update: the forced encryption has proven to bring limitations and issues to the recovery and system.
The updated steps are now mandatory!
11. Now head to 'install', browse to the directory in which you saved the supersu zip file and flash/install it.
12. Flash the latest version of the encryption fixed no-verity-opt-encrypt zip file, which can be downloaded from here
At first I made my own fix zip file, but I lost it and lot's of other projects, so the above file is a workaround.
13. If the installation succeeds, you may reboot your device.
Please be patient, the first boot may take a while.
It will reboot during the initialization, so don't panic and think it's a bootloop, cause it simply isn't.
I hope this has helped people with rooting their Sony Xperia E5.
I'm here if you need support, unless it's something dumb and/or already mentioned.
UPDATE APRIL 2018
A new modified kernel is available for the latest firmware 37.0.A.2.248!
The rooting process is the same as written above, but instead of flashing the older kernel and firmware, you'll have to flash the new ones.
Be warned, you cannot flash any newer kernel on an older firmware version and the other way around!
The kernel and firmware versions always have to be equal, no exceptions.
An advantage of flashing the newer kernel is that it should support Magisk, while the previous one didn't.
If you want to root your device with Magisk, or install both Magisk and Supersu, the rooting instructions will differ.
You can find new instructions here: (Link to the thread to be added!)
~A special thanks to rrvuhpg and Tu_Angel

Thank you a lot! It worked and now I have my E5 rooted:good::good:

How is the camera quality after unlocking bootloader ?

Tried it last night and it works. Thank you!

wardonz said:
How is the camera quality after unlocking bootloader ?
Click to expand...
Click to collapse
It's exactly the same, the camera works well in all resolutions, video recording seems to be fine too.

Hello, Im stuck in the process of unlock bootloader, im doing all step by step but i couldnt resolve this error:
Code:
C:\Users\Cristian\AppData\Local\Android\Sdk\platform-tools>fastboot devices
RQ3001L5W7 fastboot
C:\Users\Cristian\AppData\Local\Android\Sdk\platform-tools>fastboot -i 0x0fce oe
m unlock 0xA55381B959C2CA7B
...
FAILED (remote: Command not allowed)
finished. total time: 0.029s
Help, Thank you.

CrStN224 said:
Hello, Im stuck in the process of unlock bootloader, im doing all step by step but i couldnt resolve this error:
Code:
C:\Users\Cristian\AppData\Local\Android\Sdk\platform-tools>fastboot devices
RQ3001L5W7 fastboot
C:\Users\Cristian\AppData\Local\Android\Sdk\platform-tools>fastboot -i 0x0fce oe
m unlock 0xA55381B959C2CA7B
...
FAILED (remote: Command not allowed)
finished. total time: 0.029s
Help, Thank you.
Click to expand...
Click to collapse
You must enable oem unlocking in developer options.
To do this you'll have to go to settings, tap on about device and tap build number 5 times in a row.
This will enable the developer options on your device.
Now go to the developer options in settings and make sure oem unlocking is checked.
Now try to unlock the bootloader again.
It should work now, but if it doesn't, you'll have to check your drivers.

It worked perfectly, I had to restore everything because my phone turned on with fabric presets, but the technology saved me, my phone automatically did a backup this morning. Thanks!

CrStN224 said:
It worked perfectly, I had to restore everything because my phone turned on with fabric presets, but the technology saved me, my phone automatically did a backup this morning. Thanks!
Click to expand...
Click to collapse
Unlocking the bootloader always deletes all your data, I'm glad you've made a backup.
So did you manage to root it?

Well, right now im officially Rooted, but unsucesfully... My device is detected by Root Checker like a rooted device, but I dont know why some apps dont recoignize it. I have two apps what works with root:
- The first one ask me for root permissions but says dont detect root...
- The another app dont ask me and dont recoignize it...
But that everything looks fine, i dont know whats the issue.

CrStN224 said:
Well, right now im officially Rooted, but unsucesfully... My device is detected by Root Checker like a rooted device, but I dont know why some apps dont recoignize it. I have two apps what works with root:
- The first one ask me for root permissions but says dont detect root...
- The another app dont ask me and dont recoignize it...
But that everything looks fine, i dont know whats the issue.
Click to expand...
Click to collapse
That's odd, do you see the supersu app in your app drawer?
If not, install it from the play store and within the app update the su binary.
Also make sure that in supsersu settings, superuser is enabled and that mount namespace seperation is disabled.
Let me know if that worked out with you

I confirm you thats all ok, i dont know how to resolve the issue...

CrStN224 said:
Well, right now im officially Rooted, but unsucesfully... My device is detected by Root Checker like a rooted device, but I dont know why some apps dont recoignize it. I have two apps what works with root:
- The first one ask me for root permissions but says dont detect root...
- The another app dont ask me and dont recoignize it...
But that everything looks fine, i dont know whats the issue.
Click to expand...
Click to collapse
Hi, if you use Magisk try to disable build in Busybox and install it from Playstore app. It solve the problem on some devices.

OK, I downloaded Magisk and Busybox, I wish I have all the requirements for use any root app! I will reply again if Im done, Thank you!
---------- Post added at 09:30 PM ---------- Previous post was at 09:23 PM ----------
Okay, it works at least, but the apps "CIH" and "No-frills CPU Control" doesnt work for me.
---------- Post added at 09:30 PM ---------- Previous post was at 09:30 PM ----------
Okay, it works at least, but the apps "CIH" and "No-frills CPU Control" doesnt work for me.

CrStN224 said:
OK, I downloaded Magisk and Busybox, I wish I have all the requirements for use any root app! I will reply again if Im done, Thank you!
---------- Post added at 09:30 PM ---------- Previous post was at 09:23 PM ----------
Okay, it works at least, but the apps "CIH" and "No-frills CPU Control" doesnt work for me.
---------- Post added at 09:30 PM ---------- Previous post was at 09:30 PM ----------
Okay, it works at least, but the apps "CIH" and "No-frills CPU Control" doesnt work for me.
Click to expand...
Click to collapse
No-frills cpu control didn't work on mine either, I replaced it with kernel adiutor.
Besides, you can tweak a lot more in it than in no-frills

mrmarvin_16 said:
-The modified boot.img which you can download here-link
....
~A special thanks to rrvuhpg for the kernel
Click to expand...
Click to collapse
Hello.
Why do we need to flash modified kernel?
Isn't recovery just enough for installing supersu zip onto system partition?

freedom74 said:
Hello.
Why do we need to flash modified kernel?
Isn't recovery just enough for installing supersu zip onto system partition?
Click to expand...
Click to collapse
Flashing only the recovery will result into a bootloop.
As this is a newer device, some kernel patches are required due to dm-verity, bootcheck, etc.
Also make sure to first flash the kernel and then the kernel afterwards to finish the rooting process successfully.
Good luck.

Please! Need Help Fast
Need Help !!! I'm stucked at point 8. After i typed in comand 7. my phone goes into fastboot okay... but then i got two Problems: First one is that i didnt really understand where to put the two files you named.
Second one is that after i typed in command 8. the cmd says >waiting for device< and i can't type in anything anymore.
while my second problem my phone is in fastboot: the blue light in the left top corner is on and the screen is on and has the color black. please help me fast THANK YOU !!!

Wlans Theme said:
Need Help !!! I'm stucked at point 8. After i typed in comand 7. my phone goes into fastboot okay... but then i got two Problems: First one is that i didnt really understand where to put the two files you named.
Second one is that after i typed in command 8. the cmd says >waiting for device< and i can't type in anything anymore.
while my second problem my phone is in fastboot: the blue light in the left top corner is on and the screen is on and has the color black. please help me fast THANK YOU !!!
Click to expand...
Click to collapse
You haven't done anything wrong so far.
The two downloaded files must be placed in your adb folder
You must rename the kernel into boot.img and the recovery into recovery.img
Try to then re-enter the commands of step 8.
If it still says waiting for device it means you'll need to check if you have the proper drivers installed in device manager.
If you really want to turn your device off for now, you can long press the volume up+volume down+power buttons at the same time so your device will turn itself off.

I need help
After unlocking the bootloader, I can`t restore the backup.

Relock bootloader

Follow some step
1. go to developer option and tick OEM unlocking.
if your enable to tick this format your device than go to developer option and tick this
2.reboot your device to bootloader mode.
3. i am using ""fastboot oem lock".
4.download your software version ruu.
5.Flash with SD card method in download mode wait for 4 to 5 minut.
6.After flashing complete reboot your device.
Now you see your bootloader Relock .
Sorry for bad english.

Tried you solution still doesn't work, OEM unlock is grayed out

neitin said:
Tried you solution still doesn't work, OEM unlock is grayed out
Click to expand...
Click to collapse
Do one thing flash with any custom ROM with wipe your data and now chek OEM unlock .
if you have nandriod backup restore than chek it.

shubham puri4488 said:
Do one thing flash with any custom ROM with wipe your data and now chek OEM unlock .
if you have nandriod backup restore than chek it.
Click to expand...
Click to collapse
Thanks I installed custom rom, and wiped data and flashed RUU in download mode to lock bootloader.

neitin said:
Thanks I installed custom rom, and wiped data and flashed RUU in download mode to lock bootloader.
Click to expand...
Click to collapse
I have tried this process and it does not seem to work.
1. Install custom ROM
2. Ensure OEM Unlock is ticked in Developer Options
3. Reboot to Download Mode
4. fastboot oem lock
5. Flash stock RUU
6. Reboot
Can you please advise correct process?
Cheers

Flashing RUU does NOT relock the bootloader !
IF OEM UNLOCK IS GREYED OUT, it's unlocked already ! It doesent matter for what we are addressing.
1. Make sure to remove micro sd cards, or you CANNOT relock !!!<-----
2. FOLLOW STEP 1.
3. make sure USB DEBUGGING is ENABLED.
4. Boot into DOWNLOAD mode, and only download mode will work. Hold POWER +VOLUME DOWN or type, "adb reboot download" from fastboot directory.
5. Type, "fastboot oem lock" and a screen should pop up asking if you want to lock the phone, select YES or NO with the volume button and press power button to confirm choice.
If you want to unlock again you need to reflash the unlock token.
Usually, the culprit is the micro sd card as I found out. I also had relock trouble and tried a bunch of incorrect steps in other posts. I even got in touch with HTC special projects, but I figured it out and told them what I did.
---------- Post added at 01:10 AM ---------- Previous post was at 01:09 AM ----------
neitin said:
Thanks I installed custom rom, and wiped data and flashed RUU in download mode to lock bootloader.
Click to expand...
Click to collapse
flashing RUU doesn't relock the bootloader, I can take a video showing that is false.
---------- Post added at 01:12 AM ---------- Previous post was at 01:10 AM ----------
gohnjorry said:
I have tried this process and it does not seem to work.
1. Install custom ROM
2. Ensure OEM Unlock is ticked in Developer Options
3. Reboot to Download Mode
4. fastboot oem lock
5. Flash stock RUU
6. Reboot
Can you please advise correct process?
Cheers
Click to expand...
Click to collapse
Follow my post and see if that works, I too had relock troubles, it was the micro SD card !
---------- Post added at 01:12 AM ---------- Previous post was at 01:12 AM ----------
gohnjorry said:
I have tried this process and it does not seem to work.
1. Install custom ROM
2. Ensure OEM Unlock is ticked in Developer Options
3. Reboot to Download Mode
4. fastboot oem lock
5. Flash stock RUU
6. Reboot
Can you please advise correct process?
Cheers
Click to expand...
Click to collapse
Follow my post and see if that works, I too had relock troubles, it was the micro SD card ! If you have probs let me know, I'll try to help you.

According to the procedure RELOCK
It was documented.
Where is RUU for U-3u?
Help me.

So when I have normally STOCK oreo with no normally working over the air update but oem unlocked (previously tried many custom roms) there is no way to lock oem without again reinstall ruu with full wipe (I don't want loose my data but want to use nfc android pay and it can be used only with locked oem)?

royalcrown said:
Flashing RUU does NOT relock the bootloader !
IF OEM UNLOCK IS GREYED OUT, it's unlocked already ! It doesent matter for what we are addressing.
1. Make sure to remove micro sd cards, or you CANNOT relock !!!<-----
2. FOLLOW STEP 1.
3. make sure USB DEBUGGING is ENABLED.
4. Boot into DOWNLOAD mode, and only download mode will work. Hold POWER +VOLUME DOWN or type, "adb reboot download" from fastboot directory.
5. Type, "fastboot oem lock" and a screen should pop up asking if you want to lock the phone, select YES or NO with the volume button and press power button to confirm choice.
If you want to unlock again you need to reflash the unlock token.
Usually, the culprit is the micro sd card as I found out. I also had relock trouble and tried a bunch of incorrect steps in other posts. I even got in touch with HTC special projects, but I figured it out and told them what I did.
---------- Post added at 01:10 AM ---------- Previous post was at 01:09 AM ----------
flashing RUU doesn't relock the bootloader, I can take a video showing that is false.
---------- Post added at 01:12 AM ---------- Previous post was at 01:10 AM ----------
Follow my post and see if that works, I too had relock troubles, it was the micro SD card !
---------- Post added at 01:12 AM ---------- Previous post was at 01:12 AM ----------
Follow my post and see if that works, I too had relock troubles, it was the micro SD card ! If you have probs let me know, I'll try to help you.
Click to expand...
Click to collapse
Well I did this process and now when the phone boots, the phone is encrypted and I'm not able to decrypt even though I enter the correct PIN. Before it boot to the where you enter your PIN, the message I get before it boots up is "Your device has loaded a different operating system". Please help.

mauiblue said:
Well I did this process and now when the phone boots, the phone is encrypted and I'm not able to decrypt even though I enter the correct PIN. Before it boot to the where you enter your PIN, the message I get before it boots up is "Your device has loaded a different operating system". Please help.
Click to expand...
Click to collapse
Download mode, flash stock firmware (same version as what was on it before it was modified/corrupt) via sdcard method. All data will be lost.

See this thread too:
https://forum.xda-developers.com/u11/help/sprint-version-bricked-t3823545
It should be a total reset and therefore should not ask you for a pin as far as I know.

A couple issues I have come across in trying to recover and revive my phone. First, I am not able to find the stock OS that the phone has (2.42.617.6) I am able to find this one (2.42.617.7). I just hate to send the phone back to HTC and have them charge me up to $200 to unbrick my phone. But it is what it is...

royalcrown said:
Flashing RUU does NOT relock the bootloader !
IF OEM UNLOCK IS GREYED OUT, it's unlocked already ! It doesent matter for what we are addressing.
1. Make sure to remove micro sd cards, or you CANNOT relock !!!<-----
2. FOLLOW STEP 1.
3. make sure USB DEBUGGING is ENABLED.
4. Boot into DOWNLOAD mode, and only download mode will work. Hold POWER +VOLUME DOWN or type, "adb reboot download" from fastboot directory.
5. Type, "fastboot oem lock" and a screen should pop up asking if you want to lock the phone, select YES or NO with the volume button and press power button to confirm choice.
If you want to unlock again you need to reflash the unlock token.
Usually, the culprit is the micro sd card as I found out. I also had relock trouble and tried a bunch of incorrect steps in other posts. I even got in touch with HTC special projects, but I figured it out and told them what I did.
---------- Post added at 01:10 AM ---------- Previous post was at 01:09 AM ----------
flashing RUU doesn't relock the bootloader, I can take a video showing that is false.
---------- Post added at 01:12 AM ---------- Previous post was at 01:10 AM ----------
Follow my post and see if that works, I too had relock troubles, it was the micro SD card !
---------- Post added at 01:12 AM ---------- Previous post was at 01:12 AM ----------
Follow my post and see if that works, I too had relock troubles, it was the micro SD card ! If you have probs let me know, I'll try to help you.
Click to expand...
Click to collapse
I relocked my u11 with the Sdcard in, I flash stock ruu first & do a factory reset first, make sure USB debugging is enabled after flashing via Sdcard method, I also never have a problem using 125gb Sdcard ,which some say you doesn't work, I've done this on EU software, I don't always use the exact same version is 2.33.401. The prefix after doesn't matter, it's a slight down grade but same mid & cid, this worked for me on u11 & u11 + , I only get oem grayed out when debugging not enabled

jab5555 said:
I relocked my u11 with the Sdcard in, I flash stock ruu first & do a factory reset first, make sure USB debugging is enabled after flashing via Sdcard method, I also never have a problem using 125gb Sdcard ,which some say you doesn't work, I've done this on EU software, I don't always use the exact same version is 2.33.401. The prefix after doesn't matter, it's a slight down grade but same mid & cid, this worked for me on u11 & u11 + , I only get oem grayed out when debugging not enabled
Click to expand...
Click to collapse
Maybe the EU software is a bit different, my HTC U11 was the Sprint version (USA) and removing the card was the only way it would ever re lock. I have since upgraded to the Note 8. Not getting 8.1 through my carrier was a factor, as was wanting to try Samsung Gear VR. I enjoyed my U11 immensely.