Database Info

HTC One Mini (M4_U4) Softbricked, OEM not unlocked, USB debug not enabled, bootloop

Hi all,
My HTC One Mini crashed one month after warranty (Boo!). I can get to the FASTBOOT and BOOTLOADER screen and select options. However, the Factory reset and recovery just cause a vibration and get be back to FASTBOOT menu. The phone is *** LOCKED ***.
After a few false starts on linux and mac machines, I've installed WinDroid Toolkit v3.1 on Windows 7. I have gotten the Token ID and used it to get an Unlock_code.bin via email from the HTC developers website (Cannot link as newb). However, when I follow the instructions in WinDroid it recommends that newer devices require "Enable OEM Unlock" to be set:
I cannot do this now. I continue but when it says a menu will appear on the phone, the menu does not and the phone remains in *** LOCKED *** state. I tried continuing with step 2 "Flashing a TWRP" but it does nothing.
TL;DR Am I screwed with having previously unlocked OEM on my HTC One Mini, now that it is soft-bricked?

I'm not that good at this stuff, but managed to get mine unlocked and a recovery on it via this link
sadly mine still has a problem in that it's now stuck in a boot loop, so don't use Oneclickroot as I did in my post here
hopefully you will get yours to work ok, but when you get to instruction 17 you may find that HTC website is quite fussy with the code you copy/paste
when you copy the Identifier block into Notepad or whatever, ensure you don't get any leading blank spaces before you submit it to HTC.
this excerpt from mine had blank spaces where I have inserted red X's, but it worked with them removed and HTC then emailed me the Unlock_code.bin file
XX<<<< Identifier Token Start >>>>
XX36ADF279412BE14D5002935236B24913
XXetc
XXetc
XX<<<<< Identifier Token End >>>>>
I hope this is of some use mate
---------- Post added at 02:39 PM ---------- Previous post was at 02:26 PM ----------
sorry,
lost the plot on my first reply and forget about the OEM unlock bit ...
to get that OEM unlock bit you would normally
first Enable Developer Modeon your phone by Launching the Settings Application -
Scroll Down and Tap on About Phone(or About Device) - Locate the Build Number Section - Tap on the Build Number Option 7 Times -
Go Back to the Main Settings Page - Scroll Down and Tap on Developer Options and it's found there
but given that you are in is bad a place as me in that we cannot get a bootup, I'm afraid I can't offer any more info,
but it's worth knowing anyway in case you do get booted up

Hi, i have the same issue, but a little different.
My phone was in a box for like 2 months, and then i decide to turn it on again, and i faced the same problem as the OP, but my One Mini is UNLOCKED, and i can't lock it again because i get an error in ADB. I try to enter on recovery (and flashed three differents recoveries without sucess), and reboot in bootloader, then try to factory reset, and reboot bootloader again. It don't do anything, only turn on when i plug the usb and enter in bootloader but no more than that. i've try to flash a RUU too, but it give me the error 171. i tried too the method with the rubber band pressing the power button to cause a reboot loop and get enough charge to launch the system but nothing, i don't see any results. I'm one step closer to give up, please help, i tried everything and nothing has worked for me. If need more information don't doubt on asking me. I really appreciate any help you can provide.

I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen

carkev said:
I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen
Click to expand...
Click to collapse
i don't need to press vol down and power together, the phone enter in bootloader once you plug the usb cable. it do that alone.
This is what i get
C:\adb>adb devices
List of devices attached
C:\adb>
the phone is recognized by HTC Sync manager but i can't see it in ADB.

a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here

carkev said:
a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
Click to expand...
Click to collapse
Hahaha, i know, i have the replacement here, i'll change it once i solve this problem.
carkev said:
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here
Click to expand...
Click to collapse
2. I will leave you down here exactly what i get when i type "adb devices" (with an attached image)
3. i have installed the latest HTC drivers, and i tried connecting my phone to front an rear usb ports, both of them. No results.
4. Down here i'll leave you an attached image of what i get when i try to install a recovery by typing "fastboot flash recovery recovery.img" (i changed the name to recovery.img of course) and the phone seems installing the recovery in fastboot but it gave me that error in adb and when i try to enter in recovery it reboots on bootloader.

your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here

carkev said:
your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here
Click to expand...
Click to collapse
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers

Little Snevil said:
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers
Click to expand...
Click to collapse
Hello guys, I've been following this thread and I'm having same issue. Adb does not sees my phone.
Fastboot does, but when I run ruu , it disconnects and give error 171
Tried usb 2 instead of 3.nothing.
I also think it's the drivers, but I can't seem to find the correct one for this phone. Any help is appreciated

my phone only starts in bootloader it have s-on and i cant use the toolkit cause usb debugging isnt active
adb writes waiting for device
can anyone help me?

Help - Bricked (accidentally locked bootloader with TWRP installed)

It was late and I was cleaning up my old OP5T, getting it ready to sell. I thought I had plugged in my OP5T, but I still had my OP6 plugged in when I ran "fastboot oem lock". Now it won't boot and I can't unlock it (I'm assuming because I can't get into the OS and "enable OEM unlocking" anymore).
Is there anything I can do?

try using search next time because its already been talked abput here https://forum.xda-developers.com/oneplus-6/help/relock-bootloader-t3798135

Actually, I DID read that. I didn't just roll off the cabbage truck. If you have time to post snippy replies (I also searched YOUR post history), then maybe you can point out where in that thread the answer to my question is. I could see if there was a thread where this specifically happened, or if it had been talked about over and over, but I couldn't find one. You do know this is a fairly new device, right? TBH, you're just being rude. To count on someone to hit the right search terms for a single thread where the info exists is just asinine.
1) I have not seen anyone with this situation on the OP6 yet
2) The OP5T had an unbrick tool
3) Most phones have a way to restore the OS to factory
If it can't be restored without calling OnePlus, then why not just say so? I'll answer for you, it's because you actually enjoy replying in such a manner. Grow up.

Have you tried the mega unbrick guide?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051

Flapjack said:
It was late and I was cleaning up my old OP5T, getting it ready to sell. I thought I had plugged in my OP5T, but I still had my OP6 plugged in when I ran "fastboot oem lock". Now it won't boot and I can't unlock it (I'm assuming because I can't get into the OS and "enable OEM unlocking" anymore).
Is there anything I can do?
Click to expand...
Click to collapse
I don't think relocking your bootloader will disable the "enable OEM unlock" toggle in the OS. You may just be able to unlock your bootloader as normal again. You should be able to use the fastboot recovery method to restore your OS.

[email protected] said:
Have you tried the mega unbrick guide?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Click to expand...
Click to collapse
I did, but I got the "software image does not exist" error. Does it matter whether I downloaded the 5.13 or 5.15 vesion?
mikex8593 said:
I don't think relocking your bootloader will disable the "enable OEM unlock" toggle in the OS. You may just be able to unlock your bootloader as normal again. You should be able to use the fastboot recovery method to restore your OS.
Click to expand...
Click to collapse
I tried several times. It throws the following error, which when searched for, always seemed to be someone forgetting to enable OEM unlocking in settings:
Code:
FAILED (remote: oem unlock is not allowed)

Success! I was able to get it to work with the drivers from this post. No other drivers worked. I also forced the COM port to the first available (in my case, COM1) vs the one it popped up on. Until I did that, I would just get a huge list of ports that had no device attached. Once I had it on COM1, it was the only device that showed up in the list. The first time after that, I got a "Sahara Communication Failed" error, but it went away after rebooting the phone back into EDL mode again.
Thanks for the help!

Flapjack said:
Success! I was able to get it to work with the drivers from this post. No other drivers worked. I also forced the COM port to the first available (in my case, COM1) vs the one it popped up on. Until I did that, I would just get a huge list of ports that had no device attached. Once I had it on COM1, it was the only device that showed up in the list. The first time after that, I got a "Sahara Communication Failed" error, but it went away after rebooting the phone back into EDL mode again.
Thanks for the help!
Click to expand...
Click to collapse
Hi buddy,
I tired to relock the bootloader and success in that but the phone stuck at fastboot mode, neither restarting to system nor to anything. Kindly help me if i can flash the stock rom in locked bootloader is so how.
THanks in adv

Did you try msm download tool ?

My OnePlus was bricked and it's bootloader is locked too, I have tried most of the steps like msm and those Bat files etc. But error is coming
"Remote : Flashing is not allowed in locked state"
Even tried that all in one tool that also can't unlock my bootloader
Now plz someone show me steps it will be a great help

I can't find my LG Velvet 5G LM-G900UM on ADB

I enabled USB debugging on my device, but I still can't find it. Please help.

I have the same issue.

Plug in phone in "charging only" mode.

It seems that my ohone was not setup properly. It works now.

t1moc said:
It seems that my ohone was not setup properly. It works now.
Click to expand...
Click to collapse
Please have you unlock your bootloader? Can you share with me your eng abl file? Please

I've tried until I get tired. I could not do it. Nor can I update it manually via LGUP. A bloody error appears. I can't unlock the bootloader. I went through a wizard in these things and I literally saw when the pop-up window of the recognition of the bootloader and its ADB appeared, but it did not continue because I could not pay the exorbitant amount that it asked me. And I do have an AT&T device the LM-G900UM. I have it on Android 10 and it failed to update it outside the region.

rcascoherrera said:
I've tried until I get tired. I could not do it. Nor can I update it manually via LGUP. A bloody error appears. I can't unlock the bootloader. I went through a wizard in these things and I literally saw when the pop-up window of the recognition of the bootloader and its ADB appeared, but it did not continue because I could not pay the exorbitant amount that it asked me. And I do have an AT&T device the LM-G900UM. I have it on Android 10 and it failed to update it outside the region.
Click to expand...
Click to collapse
Did you ever came right. I need firehose file lg velvet 5g

Question Hidden oem unlock

I upgraded to android 12. Oem unlock is not visible. I went back to android 11 and it still doesn't show. help

hhhhhhhhheeelllpp

And i search on recovery mode tap bootloader but i see black screen

is there no one to answer on huge xda? interesting

I think you can just use the official OEM unlock too app to one-step unlock the BL....

asus bootloader unlock tool apk. I tried maybe 20 times and it didn't work
yurishouse said:
I think you can just use the official OEM unlock too app to one-step unlock the BL....
Click to expand...
Click to collapse

I did not understand anything.
OEM unlock does not visible in developer options. I cannot enter the bootloader in the recovery menu. asus unlock tool.apk doesn't work.
i regret buying an asus phone

Robocop36 said:
I did not understand anything.
OEM unlock does not visible in developer options. I cannot enter the bootloader in the recovery menu. asus unlock tool.apk doesn't work.
i regret buying an asus phone
Click to expand...
Click to collapse
This device does not have OEM unlock. Contact ASUS to try and resolve the issue with the unlock app but I suspect you have a converted phone that is getting rejected by the ASUS side. Attempting too fix it yourself will involve amending some device parameters, I think someone has added some notes somewhere on the forums here..

I made a comment on asus zentalk. I've been waiting for a week, no answer. There are 20 moderators, but one person is not responding. a disgraceful place.
Hey man i went to the internet cafe yesterday to install raw firmware. I downloaded win10 asus qualcom usb drivers , downloaded usb minimal android sdk, pressed the volume up power button, the computer did not see my phone on the start screen, I tried many times and it didn't work.
The computer sees the phone without entering the start screen. I even copied 40 movies to the phone. but every time I press the volume up/power button the computer does not see the phone when the start screen comes up.

Andrologic said:
This device does not have OEM unlock. Contact ASUS to try and resolve the issue with the unlock app but I suspect you have a converted phone that is getting rejected by the ASUS side. Attempting too fix it yourself will involve amending some device parameters, I think someone has added some notes somewhere on the forums here..
Click to expand...
Click to collapse
If I try this, will the computer see my phone on the start screen?
ASUS Android Bootloader Interface Drivers Download for Windows 10, 8.1, 7, Vista, XP
Download the latest drivers for your ASUS Android Bootloader Interface to keep your Computer up-to-date.
www.driverscape.com

hhhhhhhheeeeeellppppp

It had HTC, Samsung, Xiaomi. I switched to ASUS. maybe my version is cn but the chinese changed it to ww! I didn't know it was like this i wouldn't have bought this phone had I known.

How do I get out of this job? I risk losing imei and more. maybe my device will be hard bricked. Flashing raw software takes a lot of effort. first of all, my computer doesn't see my device on the start screen, I couldn't even take a step. I unlocked the bootloader hundreds of times on my previous phones. I rooted hundreds of times , I installed custom roms hundreds of times,. but I could not progress even one step on the Asus phone.

Robocop36 said:
If I try this, will the computer see my phone on the start screen?
ASUS Android Bootloader Interface Drivers Download for Windows 10, 8.1, 7, Vista, XP
Download the latest drivers for your ASUS Android Bootloader Interface to keep your Computer up-to-date.
www.driverscape.com
Click to expand...
Click to collapse
Suggest using the orginal Andrid driver directly from Google. There is no specific ASUS drivers needed for this device although the one in your link may work too. And yes, you do need to sort out your driver before you can flash from PC to the device with Fastboot commands.

Andrologic said:
Suggest using the orginal Andrid driver directly from Google. There is no specific ASUS drivers needed for this device although the one in your link may work too. And yes, you do need to sort out your driver before you can flash from PC to the device with Fastboot commands.
Click to expand...
Click to collapse
Ok

Hi, your device seems to be a converted chinese version (with Tencent Games on the back) so you need to use this method to spoof the region if your phone and force the bootloader unlock: https://forum.xda-developers.com/t/...the-bootloader-of-your-rog-phone5-5s.4371255/

Saying and complaining ain't gonna help you out.
Lost people don't wanna reply as this is covered many times and can be found with search option on this forum.
Anyway his is relevant info for you :
1: The usb c port needed to use to flash etc in bootloader mode is on the side, NOT the bottom one.
2 : if option 1 this Still not working add device manual in driver section of computer, then is driver problem.
3: adb drivers/software/map with adb commands etc needs to be present on computer, or commands will not be executed correctly and give error.
4: of you have a Chinese phone CN FW that is flashed with the WW firmware, you will get problems, only way to solve this is to use correct firmware on device and upgrade.
This is also covered in a big topic on this forum.
5: of you need to go to a internet cafe do to flashing and install firmware, and you had Samsung xaomi etc and can't work this out yourself or Ith search option, o ask myself if you should mess with the phone in the first place,
When it goes wrong, it is bad phone, crap etc.... While it is user error. No hard feelings.
Hope you know enough now and get it fixed
Sending from Rog 5 ultimate android12 fw ww91 unlocked and rooted.

Read this : https://forum.xda-developers.com/t/...the-bootloader-of-your-rog-phone5-5s.4371255/

1: i was plugging it into the bottom usb c port not the side usb c port I'll try it when I have free time. thank you all so much

Help- Mi Unlock Tool not working properly on PC

Hi guys,
I'm trying to unlock my Poco F3's bootloader. I'm doing good on the phone's part (enabling oem unlocking, usb debugging and connecting account and device), but on the PC side, not so much. When I try to use the Mi Unlock tool on my PC, there's 2 types of errors occurring, which depend on the Mi Unlock Tool version I'm using (I've tried several of them just to try to get them to work). The errors are:
1. After I log in to the Mi Unlock Tool, In Chinese text It says this: (attached screenshot)
I translated It, and the result was "You do not appear to be connected to the Internet Please refresh and try connecting to the network Tap to refresh"
2. The second error I am getting on the other version of the Mi unlock tool which is "Couldn't get Info[-1 Unknown error. Try again later". (Screenshot attached)
For context, I am using ADB setup 1.4.3 with the Mi Unlock tool, on Windows 11. I've tried downloading other Mi Unlock tool versions to see If it fixes the problem, but I get the one of the above 2 errors everytime. I've also tried using the XiaomToolsV2 to download any missing drivers, but nothing has changed. Send help pls.

Did you do this?
Spoiler: MiUnlock
Check that the firewall does not block the application, create a rule if necessary.
Put the Miflash folder at the root of the disk, run as administrator.

NOSS8 said:
Did you do this?
Spoiler: MiUnlock
View attachment 5881305
Check that the firewall does not block the application, create a rule if necessary.
Put the Miflash folder at the root of the disk, run as administrator.
Click to expand...
Click to collapse
thank you for replying, meanwhile while I was waiting I thought of giving it a try my bros pc (its newer and has much better processing capabilities). And magically for some reason it turned out pretty smooth, till the phone not connected page. I even got a popup to use the latest version of the unlock tool which I didn't get on my PC.
Now the problem here is that my PC doesn't recognize it. So to fix that I tried XiaomiToolV2 (so it can help the PC identify my device, as I saw ppl doing it on YouTube). though luckily XiaomiToolV2 managed to identify my device, but the problem I'm stuck at is the USB port. Ah, It got fixed after I reset the Pc after downloading the recommended firmware by XiaomiToolV2.
Just figured It out, the main reason for those errors is due to the filtering on my Wi-Fi my bro set up. It most probably was blocking the Mi Unlock Tool from properly communicating with the Internet. Somehow, my brother always uses a VPN (proton to be specific) on his PC at all times. I don't. So the first time I tried to setup the Unlock Tools on his VPNed PC, It went pretty smoothly than It did on my PC. Then I had tor restart it to install XiaomiToolV2 firmware. After I did that, I was getting the same error I was on my PC. Then I re-connected the VPN (as it was disconnected due to restart) and restarted the Mi Unlock Tool, and voila. magik.
Now the problem I'm stuck at is that I have to wait 166 more hours to be able to unlock It, as I connected my Mi account just 2 hours ago. I wasn't aware that the 168 hours timer starts from when I connect my acc, (my dumass thought the timer starts when you first bootup the phone after purchasing ). So there's that..
I was writing this reply while I was in the process, so the sequence you see in the first 2 paragraphs is me trying random stuff one after another. Sorry for the long post, and thank you for commenting/helping.
For people coming to this thread in the future looking for a solution to the same error ("Couldn't get Info[-1 Unknown error. Try again later") try using a VPN, it should fix the problem.

Alright, you solved the problem.
Xiaomi official tool is Mi Unlock not XiaomiToolV2.
Recommended to use a Usb2 port.

Yeah, thanks. I used the XiaomiToolV2 just so I can get the official tool to recognize my phone which It wasn't doing earlier