Database Info

[Q] Asus Unlock Tool says device unlocked, but it actually is not

Hi there,
I have a TF300T which I am trying to unlock. I downloaded the Asus APK file, and initially it did not work. After a bit of troubleshooting I was able to get it to work by registering my device on the Asus website.
However, even though the application ran, the bootloader is not unlocked.
Code:
C:\Program Files\android_sdk\sdk\platform-tools>fastboot -i 0x0b05 getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 015d15b51c0c0e04
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
[B][COLOR="Red"](bootloader) unlocked: no[/COLOR][/B]
(bootloader) uart-on: yes
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.104s
Each time I run the Unlocking application from Asus, I get a toast message saying "Device is unlocked". I take this to mean that the APK has detected somehow that the bootloader is unlocked and doesn't attempt to unlock the device.
I tried using an older version of the Unlock tool (Version 7 instead of 8) but it's the same problem.
Has anyone had this issue before? Any ideas?

CatalystNZ said:
Hi there,
I have a TF300T which I am trying to unlock. I downloaded the Asus APK file, and initially it did not work. After a bit of troubleshooting I was able to get it to work by registering my device on the Asus website.
However, even though the application ran, the bootloader is not unlocked.
Code:
C:\Program Files\android_sdk\sdk\platform-tools>fastboot -i 0x0b05 getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 015d15b51c0c0e04
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
[B][COLOR="Red"](bootloader) unlocked: no[/COLOR][/B]
(bootloader) uart-on: yes
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.104s
Each time I run the Unlocking application from Asus, I get a toast message saying "Device is unlocked". I take this to mean that the APK has detected somehow that the bootloader is unlocked and doesn't attempt to unlock the device.
I tried using an older version of the Unlock tool (Version 7 instead of 8) but it's the same problem.
Has anyone had this issue before? Any ideas?
Click to expand...
Click to collapse
I'm not home, if no one helps you by time I get home I will. But I believe there's a modified apk or an apk not from Asus here on the forums for unlocking the boot loader. That's what I used when I unlocked my tf300t, not the one from Asus.
Edit. I just saw you said you used v7 and 8, don't remember if it's needed but is USB debugging on?
Sent from my LG-P769 using Tapatalk

I can't find any tools other than the official Asus one

CatalystNZ said:
I can't find any tools other than the official Asus one
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2094746&page=1
Try that toolkit
Sent from my LG-P769 using Tapatalk

I tried the toolkit, all it does is install the official Asus Unlock app... which as before, tells me that it has worked, however it does not actually unlock the device

CatalystNZ said:
I tried the toolkit, all it does is install the official Asus Unlock app... which as before, tells me that it has worked, however it does not actually unlock the device
Click to expand...
Click to collapse
After some quick reading, if I understood correctly some people weren't able to unlock till a day or 2 later, and the Asus registration was suspected to be the issue like it takes a day or something to register in their system. Wait till tomorrow if you can and try again and if it still doesn't work I'll see what else I can find.
Sent from my LG-P769 using Tapatalk

When you boot up your device does it say Your device is unlocked in the top left? If it does, then it actually is unlocked.
Sent from my GS3 on 4.4 KitKat using Tapatalk 4

Actually fastboot doesn't see our bootloader status, so only hint is "device is unlocked" line during boot.

No, unfortunately I do not see the message when booting up. And all attempts to flash an unsigned Recovery image fail with the message
Code:
C:\Program Files\android_sdk\sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery.img
sending 'recovery' (6890 KB)...
OKAY [ 2.666s]
writing 'recovery'...
[COLOR="Red"][B]FAILED (remote: (InvalidState))[/B][/COLOR]
finished. total time: 5.215s
I have tried flashing TWRP, and have tried a couple of versions intended for 4.2, none have worked, all with the same error.
My suspicion is that the Unlock tool only works one time per device. Mine failed during the initial unlock and now my device is flagged as unlocked on the Asus servers and cannot be unlocked again. This makes sense, otherwise people could spoof/change their device serial number and a cracked version of the Unlock tool could be made which would not void your warranty on the Asus side.
I feel like my only hope is to contact Asus, however I don't feel hopeful about that. This is the sort of thing which makes me not recommend Asus.
If they just unlocked the bootloader, without the need to phone home, it would be a lot better.

Well I contacted Asus 24 hours ago... still nothing back from their Email support.
The Unlock tool is giving now me a different error now, which is different than the usual "Device is unlocked" message from before.
The message is "An unknown error occurs...". From what I understand, this happens if the Serial Number is not in their Database, or if their server is down.. or if there is a local network problem.
I will keep trying it periodically.

First Asus response today
Hi, we're very glad to help you. For this issue, I have emailed your problem to our BU(technical department) in Taipei,I will give you the answer as soon as I receive it and I have written down your checking number.
So sorry for waiting and causing your inconvenience.
If you not get any reply from asus within 48 hours, please feel free to contact us again.
Sorry for the inconvenience.
Click to expand...
Click to collapse
I tried to run the unlock tool, and it worked this time!
So in summary, use the vip.asus.com support site to email Asus if this happens to you!

CatalystNZ said:
First Asus response today
I tried to run the unlock tool, and it worked this time!
So in summary, use the vip.asus.com support site to email Asus if this happens to you!
Click to expand...
Click to collapse
Hi guys,
I have resolved.
I confirm that the reburbished tablet isn't right registered on Taipei Asus's server.
You must contact your Asus country support and ask to update this serve with your right serial number.
My italian support good ask me a screenshot but after they help me without problem.
The day after you can unlock the tablet.
Have a good enjoy with your unlocked tablet

device tracker is down
I want to use the device tracker excuse since my last 3 vip support tickets got denied /closed with no resolution over a year ago but now the device tracker website has been phased out. Any advice? Help! I won't give up.

diesburg said:
http://forum.xda-developers.com/showthread.php?t=2094746&page=1
Try that toolkit
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
Thanks sir, you saved so much time, that root kit worked like charm, as ASUS is not providing "Unlocker apk" download.

[LGUS996] How To Unlock the Bootloader

Thank you everyone who reached out the LG to express their interest in having the LGUS996 LG V20 be unlockable. LG has now provided a way, via their own website, to request an unlock key (unlock.bin) for the LGUS996 model of the V20. This unlock key can be used to unlock the bootloader.
*THIS WILL WIPE ALL YOUR DATA AND FACTORY RESET YOUR PHONE*
SKU Status
Only LGUS996.USA of LGUS996 (V20) for the US open market
LGUS996USATN - Unlocked (Supported)
LGUS996TNUCL - US Cellular (Not Supported)
You can find the steps and details on unlocking the bootloader here: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
While it does not, at the time of this post, state that the LGUS996 V20 is supported, I can confirm that the LGUS996 has been added the request page and that I have personally unlocked the bootloader on my LGUS996.
Code:
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
LGUS996XXX device
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>fastboot devices
LGUS996XXX fastboot
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x4d000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xced000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x180000000
(bootloader) serialno:LGUS996XXX
(bootloader) kernel:lk
(bootloader) product:MSM8996
[B](bootloader) unlocked:no[/B]
all:
finished. total time: 0.211s
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.039s]
writing 'unlock'...
(bootloader) Erasing userdata and cache
(bootloader) Bootloader Unlock key flash Success
OKAY [ 1.951s]
finished. total time: 1.990s
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x4d000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xced000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x180000000
(bootloader) serialno:LGUS996XXX
(bootloader) kernel:lk
(bootloader) product:MSM8996
[B](bootloader) unlocked:yes[/B]
all:
finished. total time: 0.210s
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>fastboot reboot

I have tried this method in my v20 and the site says my phone is not yet supported. Are there 2 different lg us996 models?

falloon19 said:
I have tried this method in my v20 and the site says my phone is not yet supported. Are there 2 different lg us996 models?
Click to expand...
Click to collapse
Did you purchase the US996 from US Cellular? The SKU on my V20 box is LGUS996USATN and was purchased unlocked from Amazon. There have been suspicions that the US Cellular version is actually different even though it seems to have the same US996 versioning.

Yeah I got my us996 at us cellular. I was sure wondering that myself. Should have just ordered online but thought I could get a deal instead of paying full price

Worked like a charm on mine!! THANKS!!

wyvernwaddell said:
Worked like a charm on mine!! THANKS!!
Click to expand...
Click to collapse
Did you purchase yours online as well?

falloon19 said:
Did you purchase yours online as well?
Click to expand...
Click to collapse
Purchased straight from LG-the carrier unlocked version. Fingerprint reader still works! YAY! Off to see if TWRP is out there yet...and supersu.
.

wyvernwaddell said:
Purchased straight from LG-the carrier unlocked version.
Click to expand...
Click to collapse
Hmm guess redshorty4 is probably right. Don't know why they would brand the phone the same model then

falloon19 said:
Hmm guess redshorty4 is probably right. Don't know why they would brand the phone the same model then
Click to expand...
Click to collapse
If you happen to have the box for your phone, what does the SKU say on it?

redshorty4 said:
If you happen to have the box for your phone, what does the SKU say on it?
Click to expand...
Click to collapse
sku is LGUS996USATN
---------- Post added at 11:17 PM ---------- Previous post was at 10:41 PM ----------
Anyone know if SuperSU for the 918 will work with the 996? I'm not even gonna try TWRP until I'm sure we have a working one...

redshorty4 said:
If you happen to have the box for your phone, what does the SKU say on it?
Click to expand...
Click to collapse
SKU is LG-US996TN UCL
---------- Post added at 05:39 AM ---------- Previous post was at 05:23 AM ----------
I did notice also on the lg bootloader unlock that my imei # is one digit shorter than required a well

falloon19 said:
SKU is LG-US996TN UCL
---------- Post added at 05:39 AM ---------- Previous post was at 05:23 AM ----------
I did notice also on the lg bootloader unlock that my imei # is one digit shorter than required a well
Click to expand...
Click to collapse
Unfortunate to say your model may not be supported due to the fact it was purchased from a carrier. I imagine your model is locked to US Cellular and they won't allow their model to be bootloader unlocked just like Sprint/AT&T/Verizon.

whoa awesome. amazon unlocked here, so I'll try this maybe in a few weeks...once it's confirmed we've got absolute root and twrp and whatnot. very cool!
Sent from my LG V20 US996

Now here is a question:
Can dirty cow method be used on US996 bootloader unlocked?

Thanks for the update.

Unlocked Bootloader LGUS996USATN
Works perfect
Cheers

I guess once this is done and the bootloader is unlocked and the phone is rooted, that Android Pay will not work? That ia the way it is with my Note 4.
Also, and the process be reversed on the V20?

FAUguy said:
I guess once this is done and the bootloader is unlocked and the phone is rooted, that Android Pay will not work? That ia the way it is with my Note 4.
Also, and the process be reversed on the V20?
Click to expand...
Click to collapse
Android pay will not work and according to LG you cannot reverse the process.
Cheers

mingkee said:
Now here is a question:
Can dirty cow method be used on US996 bootloader unlocked?
Click to expand...
Click to collapse
Shouldn't need it, if it's an officially unlockable device it should have fastboot flash enabled.
You should be able to just download https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-0-us996.img and do:
Code:
fastboot flash twrp-3.0.2-0-us996.img
And if that works, you're pretty much safe from ever bricking.

jcadduono said:
Shouldn't need it, if it's an officially unlockable device it should have fastboot flash enabled.
You should be able to just download https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-0-us996.img and do:
Code:
fastboot flash twrp-3.0.2-0-us996.img
And if that works, you're pretty much safe from ever bricking.
Click to expand...
Click to collapse
So after we install TWRP do we just flash SuperSU 2.78 via TWRP to root the US996? Also would I change twrp-3.0.2-0-us996.img to recovery.img before I flash it?
Cheers

HTC U11 please help!!!!

First to admit I did something stupid. I am looking for anyone to help me.
Long story short I think I have locked my bootloader. I dont know if i have the stock bootloader or twrp.
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) version-main: 2.31.617.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711021119
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
all:
finished. total time: 0.005s
I cant get into the twrp bootloader menu and I tried to use the RRU from htc to reload my phone. I get a 155 error. I tried to unlock the bootloader again with the htc ulock_code.bin error message
sending 'unlocktoken' (0 KB)...
OKAY [ 1.001s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.199s
I am at a loss on what to do. Am I screwed? I am within the htc 30 day window but dont think they will accept my phone.

skinny1439 said:
First to admit I did something stupid. I am looking for anyone to help me.
Long story short I think I have locked my bootloader. I dont know if i have the stock bootloader or twrp.
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) serialno: FA79G0500641
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 358182081003810
(bootloader) version-main: 2.31.617.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711021119
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
(bootloader) cid: BS_US001
all:
finished. total time: 0.005s
I cant get into the twrp bootloader menu and I tried to use the RRU from htc to reload my phone. I get a 155 error. I tried to unlock the bootloader again with the htc ulock_code.bin error message
sending 'unlocktoken' (0 KB)...
OKAY [ 1.001s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.199s
I am at a loss on what to do. Am I screwed? I am within the htc 30 day window but dont think they will accept my phone.
Click to expand...
Click to collapse
Delete your SN and Imei.
Wysłane z mojego HTC U11 przy użyciu Tapatalka

skinny1439 said:
First to admit I did something stupid. I am looking for anyone to help me.
Long story short I think I have locked my bootloader. I dont know if i have the stock bootloader or twrp.
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) version-main: 2.31.617.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711021119
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
all:
finished. total time: 0.005s
I cant get into the twrp bootloader menu and I tried to use the RRU from htc to reload my phone. I get a 155 error. I tried to unlock the bootloader again with the htc ulock_code.bin error message
sending 'unlocktoken' (0 KB)...
OKAY [ 1.001s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.199s
I am at a loss on what to do. Am I screwed? I am within the htc 30 day window but dont think they will accept my phone.
Click to expand...
Click to collapse
Skip again the bootloader unlocking procedure via htcdev
HTC U11 & Tapatalk

linar10 said:
Skip again the bootloader unlocking procedure via htcdev
Delete imei and serialno
HTC U11 & Tapatalk
Click to expand...
Click to collapse
Thanks I was able to unlock the bootloader via the htc dev. I just had to redownload the unlock key.

HTC u11 fails to boot.
skinny1439 said:
Thanks I was able to unlock the bootloader via the htc dev. I just had to redownload the unlock key.
Click to expand...
Click to collapse
I have a new problem.
I will start at the beginning. I was running stock htc oreo. I really wanted to install viperu 1.7. I assumed that I needed to reinstall nougat. I attemped to use the htc ruu to roll back. This failed. I booted into twrp and performed a wipe and restore to a known good nougat backup. When I rebooted the device started to boot gets past the htc logo and the shuts off. Thinking that something failed I rebooted into twrp and attempted to reinstall a stock zip. This fails to install. I wiped again and installed viperu 1.7 everything installs properly per the viper install guide. When the phone reboots it starts to install the apps. It finishes but shuts off. I connected it to a charger and booted the phone and attempted to boot but shuts off.
Can someone please tell me what I have done wrong and how to fix it.
thanks in advance.

Without s-off, the older ruu will not work. Probably older rom on newer firmware may not work. Download stock backup 2.xx.xxx.x and restore in twrp and do not forget full wipe before restoring backup
HTC U11 & Tapatalk

linar10 said:
Without s-off, the older ruu will not work. Probably older rom on newer firmware may not work. Download stock backup 2.xx.xxx.x and restore in twrp and do not forget full wipe before restoring backup
HTC U11 & Tapatalk
Click to expand...
Click to collapse
Do you have a stock backup 2.xx.xxx.x or know where I can get one. I looked online but they dont have 2.x on the list.
My phone is 2PZC50000 BS_US001 WHL (Single SIM) US Unlocked.

RUU and backup
https://forum.xda-developers.com/showthread.php?p=74694695
HTC U11 & Tapatalk

IT works again!!
linar10 said:
RUU and backup
https://forum.xda-developers.com/showthread.php?p=74694695
HTC U11 & Tapatalk
Click to expand...
Click to collapse
You saved me. I am extremely grateful of your knowledge. I thought I flushed 700 buck down the drain.
Whats the best way to revert back to nougat so I can flash to viperu 1.7. Right now I am on 2.31.617.2 from the backup you sent me to in the link. I do need to root the phone but have not attempted yet. I was planning to root the phone at the same time as installing viperu. Much thanks again.

skinny1439 said:
You saved me. I am extremely grateful of your knowledge. I thought I flushed 700 buck down the drain.
Whats the best way to revert back to nougat so I can flash to viperu 1.7. Right now I am on 2.31.617.2 from the backup you sent me to in the link. I do need to root the phone but have not attempted yet. I was planning to root the phone at the same time as installing viperu. Much thanks again.
Click to expand...
Click to collapse
Can't roll back to 7.1.1 yet. You need to be S-Off and Sunshine isn't fully working on Oreo at this time.
But there is a ViperU Oreo Rom available now. If you want, to just flash it and sick with 8.0.

linar10 said:
RUU and backup
https://forum.xda-developers.com/showthread.php?p=74694695
HTC U11 & Tapatalk
Click to expand...
Click to collapse
You're the man.

henslo said:
Can't roll back to 7.1.1 yet. You need to be S-Off and Sunshine isn't fully working on Oreo at this time.
But there is a ViperU Oreo Rom available now. If you want, to just flash it and sick with 8.0.
Click to expand...
Click to collapse
Thanks for all your help. I really appreciate it!

skinny1439 said:
Thanks for all your help. I really appreciate it!
Click to expand...
Click to collapse
The viper rom for oreo doesn't really work right yet and they're working on it. I'm using stock with magisk beta 14.5. Substratum works a bit too.

Stuck in bootloader when update to OREO.

My HTC U11 always stuck in bootloader saying I use an unauthorized software everytime I update to Android Oreo ( official OTA update).
Even if I use RUU to 8.0.
The only thing I can boot my phone is when I use Nougat Rom. Even Costum Rom not helping. It;s very weird that I cannot update to 8.0.
I try leedroid Rom, also same, got back to Bootloader. So I need to reflash the 7.1.1 Rom to enable to boot.
My phone is S-Off with Bootloader Unlocked.
When I try to relock bootloader it will say something like
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ -0.000s]
finished. total time: -0.000s
In the Menu is greyed out saying bootloader already unlock.
Thanks in advance for any help.

sing2x said:
My HTC U11 always stuck in bootloader saying I use an unauthorized software everytime I update to Android Oreo ( official OTA update).
Even if I use RUU to 8.0.
The only thing I can boot my phone is when I use Nougat Rom. Even Costum Rom not helping. It;s very weird that I cannot update to 8.0.
I try leedroid Rom, also same, got back to Bootloader. So I need to reflash the 7.1.1 Rom to enable to boot.
My phone is S-Off with Bootloader Unlocked.
When I try to relock bootloader it will say something like
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ -0.000s]
finished. total time: -0.000s
In the Menu is greyed out saying bootloader already unlock.
Thanks in advance for any help.
Click to expand...
Click to collapse
Am output of a
Code:
fastboot getvar all
might show us some more, to help you with that very problem. Don't forget to delete your IMEI and SN though.
Tell us which RUU you are using that causes this very problem as well.
Sent from my HTC U12+ using XDA Labs

(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1562400000
(bootloader) serialno: FA76T1802xxx
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 990007230168xxx
(bootloader) version-main: 1.28.617.6
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-001791N-1709131257
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
(bootloader) cid: BS_US001
all:
finished. total time: 0.016s

Any RUU, any costum Rom based on Android 8.0 give me error.
Other than that, all 7.1.1 Roms / RUU boots just fine.
It's Sprint Unit , S-Off , and change to BS-US001
return to sprint Rom also no use.
I can receive OTA no problem.
After OTA to 8.0 stuck in Bootloader again saying same error.

sing2x said:
Any RUU, any costum Rom based on Android 8.0 give me error.
Other than that, all 7.1.1 Roms / RUU boots just fine.
It's Sprint Unit , S-Off , and change to BS-US001
return to sprint Rom also no use.
I can receive OTA no problem.
After OTA to 8.0 stuck in Bootloader again saying same error.
Click to expand...
Click to collapse
Well that's it actually. The device only accepts CDMA sprint updates. So it would have to be rebranded and RUU'd back to Sprint to receive updates again. But are you really using an HTC U11? The fastboot command mentions a slot which in general only applies to Treble enabled devices.
Sent from my HTC U12+ using XDA Labs

Ruu back to sprint. Also cannot upgrade to 8.0. Even on OTA update. Yes its U11.

Any help ? it only works with 7.0 Rom. I try almost everything.

Pattern lock (factory defaults / official 3.34.401.1 flash)

Hi all,
Maybe someone could push me in the right direction here. I unlocked my HTC U11 and went searching for a good CFW with MHL support. Sadly many don't have decent MHL support, thanks Google! I went into recovery steps, locked the bootloader and flashed official 3.34.401.1 rom. That went fine, but now the phone is stuck at the pattern screen.
Phone works fine, but the pattern is not set by me, almost as if the stock firmware has some secret pattern. It won't ask me to setup my google account and factory defaults doesn't fix the issue.
Current rom file: 2PZCIMG_OCEAN_UHL_P90_SENSE10GP_MR_HTC_Europe_3.34.401.1_Radio_8998-200321-1905141529_release_signed.zip
Device info:
(bootloader) kernel: lk
(bootloader) product: htc_ocnuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560000000
(bootloader) serialno: xxxx
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: xxxx
(bootloader) version-main: 3.34.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-200321-1905141529
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC10000
(bootloader) cid: HTC__034
Thanks in advance!

ristodesign said:
Device info:
(bootloader) kernel: lk
(bootloader) product: htc_ocnuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560000000
(bootloader) serialno: xxxx
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: xxxx
(bootloader) version-main: 3.34.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-200321-1905141529
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC10000
(bootloader) cid: HTC__034
Click to expand...
Click to collapse
To the one/those answering:
How can one have 0 slots?
That's odd, isn't it? I mean there are a/b partitioned devices and 'a' partioned devices out there.
So the slot-count is either 2 (a/b) or 1 (a).
To @ristodesign: Before flashing you had no pattern? And you did a factory data reset with your recovery?

Hi, yes. I tested LineageOS and Goole PixelExperience, but should have known there was no MHL support. Then I tried Viper and LeeDroid, but those didn't enable Wifi somehow.
Then decided to get back to the stock ROM provided by Ziand: https://androidfilehost.com/?fid=1899786940962575313
Locked the bootloader and renamed the rom file to 2PZCIMG.zip so I could restore from booting in download. File was accepted and everything went back to normal. Got a welcome screen, was forced to enable wifi, then suddenly some pattern lock, which does not give any option to escape. Perviously used patterns are certainly not working.
Factory reset does not clear the pattern lock. Which makes me quite unique I guess. ;-)

ristodesign said:
Hi, yes. I tested LineageOS and Goole PixelExperience, but should have known there was no MHL support. Then I tried Viper and LeeDroid, but those didn't enable Wifi somehow.
Then decided to get back to the stock ROM provided by Ziand: https://androidfilehost.com/?fid=1899786940962575313
Locked the bootloader and renamed the rom file to 2PZCIMG.zip so I could restore from booting in download. File was accepted and everything went back to normal. Got a welcome screen, was forced to enable wifi, then suddenly some pattern lock, which does not give any option to escape. Perviously used patterns are certainly not working.
Factory reset does not clear the pattern lock. Which makes me quite unique I guess. ;-)
Click to expand...
Click to collapse
Maybe you can try to boot twrp and see if it asks to decrypt?
The thing is: Passwords, pins, patterns etc. should be stored in the userdata partition. If you wipe this partition, the pattern should be gone.
However, if you manage to boot twrp and to have the userdata partition decrypted (go to /data and see if those entries aren't "randomized" letters), we should be able to delete this manually.
Else I'd like to know whether that pattern has been coded into the update zip you applied... Don't know how to accomplish that, however. But I'll see if I figure out something for the case twrp doesn't work.

You could also try another file like this one from here: https://htcstockrom.com/htc-u11

Will try to get trwp back on the device. It was removed and USB debugging probably disabled.
I did try the rom at https://htcstockrom.com/htc-u11 , after all those Visual C++ x86/x64 fixes it finally worked to start, but at the end it wouldn't accept to downgrade 3.34.401.1 to 2.42.617.7.

ristodesign said:
Will try to get trwp back on the device. It was removed and USB debugging probably disabled.
I did try the rom at https://htcstockrom.com/htc-u11 , after all those Visual C++ x86/x64 fixes it finally worked to start, but at the end it wouldn't accept to downgrade 3.34.401.1 to 2.42.617.7.
Click to expand...
Click to collapse
I see.
You only need to boot twrp temporarily, no need to flash it. Just do:
Code:
fastboot boot twrp.img
EDIT: What if you reflash LineageOS and then the older firmware mentioned above?
LineageOS should allow downgrades.

Good idea, i tried with this result:
downloading 'boot.img'...
OKAY [2.4sec]
booting...
(Then it stops)
Phone screen shows:
Flash image succes
Start downloading (1/1)
It stops there.

ristodesign said:
Good idea, i tried with this result:
downloading 'boot.img'...
OKAY [2.4sec]
booting...
(Then it stops)
Phone screen shows:
Flash image succes
Start downloading (1/1)
It stops there.
Click to expand...
Click to collapse
Oh, well...
That's strange... Then go for the method you already know.
What did you do earlier to flash twrp? Same command but "flash boot"?
EDIT:
I think you flashed it using
Code:
fastboot flash recovery twrp.img
right?
If so, maybe you can boot it somehow similar like this:
Code:
fastboot boot recovery twrp.img
.

Earlier I had to unlock the phone with the HTC Dev website. I created an Unlock_code.bin file. But if I try to flash now it will not accept.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 1.002s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
So USB debugging and the OEM lock seems to have set to default by flashing the stock rom.

ristodesign said:
Earlier I had to unlock the phone with the HTC Dev website. I created an Unlock_code.bin file. But if I try to flash now it will not accept.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 1.002s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
So USB debugging and the OEM lock seems to have set to default by flashing the stock rom.
Click to expand...
Click to collapse
If you do
Code:
fastboot getvar all
do you get something like this?:
(bootloader) unlocked:yes
Click to expand...
Click to collapse

Nope, it does not. When I try to flash it states that the bootloader is locked. The phone screen shows:
HTC download mode
*** RELOCKED ***
*** PRODUCTION ***
htc_ocnuhl PVT S-ON
yada yada yada... ;-)

ristodesign said:
Nope, it does not. When I try to flash it states that the bootloader is locked. The phone screen shows:
HTC download mode
*** RELOCKED ***
*** PRODUCTION ***
htc_ocnuhl PVT S-ON
yada yada yada... ;-)
Click to expand...
Click to collapse
Well, maybe you should research how to unlock an relocked bootloader.
I heard that some bootloader won't unlock again after relocking, which is why I never relocked my devices bootloader...

Hehe, yes it might be not too smart but it was the fastest solution as I could not find a working MHL CFW. I'll give my kids some money if they can find the pattern lol.