Recent content by UnicycleWheelie

the kept the SN the same but the IMEI changed (on the back sticker)

I had to contact HTC via the help chat. and they walked me through all the "try this" and nothing still went into BL. so they had me ship it in, and I got it fix for free. took about a 11days...it sounded like there is a problem/fault with this phone.

if you don't care about your data, just run the RUU.exe for you device, but make sure you install the drivers from HTC first.

can you point me to the AT&T RUU Thank you

HTC One Mini (AT&T) (bootloader) version: 0.5 (bootloader) version-bootloader: 2.19.0000 (bootloader) version-baseband: N/A (bootloader) version-cpld: None (bootloader) version-microp: None (bootloader) version-main: 1.32.502.3 (bootloader) version-misc: PVT SHIP S-ON (bootloader) serialno...

To unlock the bootloader do you need adb or only fastboot...because this phone takes the htcdev unlockcode.bin but the phone just stays in bootloader. when you do fastboot devices it shows up but when you do adb devices there is nothing.

flash TWRP for your phone, then test to see if the RECOVERY mode works by selecting the ‘RECOVERY’ option. your phone should boot into TWRP Recovery mode now and this means that the install has been successfully completed. Select ‘Reboot’ from the TWRP Recovery options and wait until your phone...

can you get into fastboot

so is it stuck on this screen/recovery

yeah and you should have a loading bar under that then it will reboot once done with the HTC logo

you will need to let them know more about your phone unless you are s-off

maybe someone else can add but look for an RUU (.exe file) for your device, but since the os is blank IDK what RUU you would need. since on my att htc one mini has an os - 1.32.502.3

When I turn it on it goes strigh to boot loader, in hboot/bootloader, I go to recovery and hit the power button, it vibrates and shoes an all white screen with the 3 androids in the middle, then goes to fastboot I asked her what happened to the phone before this problem happened. and this is...

C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools> adb devices * daemon not running. starting it now on port 5037 * * daemon started successfully * List of devices attached C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools> adb...

https://www.youtube.com/watch?v=XZDuXmy4buY