[Q] HTC One Mini not booting up fully and no access to recovery

[CoolAndroid1]

Hello,

My phone was updating and crashed. The phone turns on but only the HTC logo appears and then goes to a black screen. I can't fastboot into the device as it is not recognised. I can't access TWRP recovery any more and goes to a downloading screen and then restarts again. While in the bootloader the phone shows the following:

***TAMPERED***
*** RELOCKED***
M4_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.19.0000
RADIO-1.22.40e.00.07
OpenDSP-v19.2.0268.0927
OS-1.31.401.1
eMMC-boot 1024MB
Aug 7 2013, 17:37:54.0

Please help me, any help greatly appreciated!

Update:

The phone is working and has an update but it can not update on the device, is there a way i can get the downloaded OTA file on to my PC?

 

[shivasrage]

Hello,

My phone was updating and crashed. The phone turns on but only the HTC logo appears and then goes to a black screen. I can't fastboot into the device as it is not recognised. I can't access TWRP recovery any more and goes to a downloading screen and then restarts again. While in the bootloader the phone shows the following:

***TAMPERED***
*** RELOCKED***
M4_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.19.0000
RADIO-1.22.40e.00.07
OpenDSP-v19.2.0268.0927
OS-1.31.401.1
eMMC-boot 1024MB
Aug 7 2013, 17:37:54.0

Please help me, any help greatly appreciated!

Hi,

What do you want to flash stock sense 6...??

greets

 

[CoolAndroid1]

Hi,

What do you want to flash stock sense 6...??

greets

Hello,

Yes I would like to go back to Sense 6 or any stock firmware preferably 4.4.2

Thanks

 

[shivasrage]

Hello,

Yes I would like to go back to Sense 6 or any stock firmware preferably 4.4.2

Thanks

Ok
First I recommend you to unlock your bootloader.
So if you are in bootloader and your device is not recognised I think it´s a driver issue.
If you allready checked it check it once more or update your tools (ADB, fastboot)
If nothing helps you could go to recovery and format your device (not only wipe format) should be clear that all data on device is lost.
Try different recoverys some people report that philz also works fine on M_4. (try install new rom option on philz).
DONT flash stock sense 6 ROM (wrong partition layout for this hboot) with this hboot rather take 5.5.
I´m sorry but without get connectet via ADB or fastboot I think there is no chance to get it working again.

greets

 

[CoolAndroid1]

Ok

So if you are in bootloader and your device is not recognised I think it´s a driver issue.
If you allready checked it check it once more or update your tools (ADB, fastboot)
If nothing helps you could go to recovery and format your device (not only wipe format) should be clear that all data on device is lost.
Try different recoverys some people report that philz also works fine on M_4. (try install new rom option on philz).
DONT flash stock sense 6 ROM (wrong partition layout for this hboot) with this hboot rather take 5.5.
With out get connectet via ADB or fastboot I think there is no chance to get it working again.
greets

I can not access recovery to wipe anything out, on bootloader if i choose to wipe it attempts to load recovery which goes into download mode. The device comes up as "Device failed emulation" on Windows 8

 

[shivasrage]

I can not access recovery to wipe anything out, on bootloader if i choose to wipe it attempts to load recovery which goes into download mode. The device comes up as "Device failed emulation" on Windows 8

Ok

I tell you in short terms:

If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.

You see all ends up with fastboot.

As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8

greets

 

[CoolAndroid1]

Ok, I will use a win 7 pc and let you know

 

[CoolAndroid1]

Ok

I tell you in short terms:

If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.

You see all ends up with fastboot.

As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8

greets

After i fix my drivers issue what can i do afterwards?

 

[CoolAndroid1]

Ok

I tell you in short terms:

If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.

You see all ends up with fastboot.

As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8

greets

I can now do the fastboot command from CMD

 

[shivasrage]

After i fix my drivers issue what can i do afterwards?

If you have a connection via fastboot you first have to decide what ROM you want, search for the matching firmware.

for example flash the latest firmware for M_4... 4.09.401.3 from here (new partition layout for e.g. sense 6):

https://docs.google.com/file/d/0BzCFBBNdXagdcEMybkdBME5iUE0/edit

After that flash TWRP 2.7.1.1 or philz and format all you have to try one of this recoverys should work.

Next push or sideload a ROM via adb I recommend you one them:

http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921

You can decide what you want rooted or not it doesn´t matter.

After installing with succsess try to reboot that´s it.

greets

 

[jollywhitefoot]

I encountered a similar issue when playing around with returning my device to stock. I flashed stock recovery, then re-locked my bootloader. What is the downloading screen you're seeing? Is it the stock recovery screen?

To fix, i had to change CID back to stock (for me that was, CWS__001)
Unlock bootloader again, using HTC unlock.bin (unlock.bin wouldn't work when i was on super cid)
Flash custom recovery TWRP 2.6.3.0 (I'm not sure if 2.7.1.1 works with the old partition layout, so i used this version until i had upgraded to hboot 2.22, then I flashed 2.7.1.1. This may be an unnecessary step, but it always worked for me)

Once twrp was working again...
Flash stock hboot 2.22 found in the dev section
Flash TWRP 2.7.1.1 (again, might be an unnecessary step)

Boot to recovery
From TWRP, adb push the sense 6 rom i wanted to flash (IC 3.07 in my case)
After the push completed, flash ROM and reboot and all was good

As you can see, the steps i took require that fastboot and adb drivers work flawlessly, especially when pushing ROM to the device using abd.

If any of this seems unfamiliar, then don't do these steps. Again, this is just what i did when i flashed stock recovery and re-locked bootloader with a ROM that wouldn't boot.

 

[CoolAndroid1]

I encountered a similar issue when playing around with returning my device to stock. I flashed stock recovery, then re-locked my bootloader. What is the downloading screen you're seeing? Is it the stock recovery screen?

To fix, i had to change CID back to stock (for me that was, CWS__001)
Unlock bootloader again, using HTC unlock.bin (unlock.bin wouldn't work when i was on super cid)
Flash custom recovery TWRP 2.6.3.0 (I'm not sure if 2.7.1.1 works with the old partition layout, so i used this version until i had upgraded to hboot 2.22, then I flashed 2.7.1.1. This may be an unnecessary step, but it always worked for me)

Once twrp was working again...
Flash stock hboot 2.22 found in the dev section
Flash TWRP 2.7.1.1 (again, might be an unnecessary step)

Boot to recovery
From TWRP, adb push the sense 6 rom i wanted to flash (IC 3.07 in my case)
After the push completed, flash ROM and reboot and all was good

As you can see, the steps i took require that fastboot and adb drivers work flawlessly, especially when pushing ROM to the device using abd.

If any of this seems unfamiliar, then don't do these steps. Again, this is just what i did when i flashed stock recovery and re-locked bootloader with a ROM that wouldn't boot.

I cant unlock my bootloader as its relocked and fails, I cant install TWRP either

 

[jollywhitefoot]

I cant unlock my bootloader as its relocked and fails, I cant install TWRP either

Did you get fastboot working yet? Does "fastboot devices" show your device? You can't do anything until fastboot works...but I imagine it worked at some point, since you unlocked and re-locked your device.

You can't install recovery because your bootloader is locked. And you can't unlock your bootloader until you change your CID back to whatever it was when you created the unlock.bin file on the HTC website.

Are you getting this error when you attempt to unlock?

FAILED (remote: unlock token check failed)

 

[CoolAndroid1]

Did you get fastboot working yet? Does "fastboot devices" show your device? You can't do anything until fastboot works...but I imagine it worked at some point, since you unlocked and re-locked your device.

You can't install recovery because your bootloader is locked. And you can't unlock your bootloader until you change your CID back to whatever it was when you created the unlock.bin file on the HTC website.

Are you getting this error when you attempt to unlock?

FAILED (remote: unlock token check failed)

Hello,

I did have the error code above but i used FUU to flash back to stock and all is fine now!!

 

[jollywhitefoot]

Hello,

I did have the error code above but i used FUU to flash back to stock and all is fine now!!

Cool. Did you use fuu from here?
http://forum.xda-developers.com/showthread.php?t=2659109

 

[CoolAndroid1]

Cool. Did you use fuu from here?
http://forum.xda-developers.com/showthread.php?t=2659109

Yep! Windows 8 sucks with drivers and didn't work so had to switch to a different laptop!

 

[jollywhitefoot]

Yep! Windows 8 sucks with drivers and didn't work so had to switch to a different laptop!

That's what i had to do when i first tried to root my phone. I was on Windows 7, but it was an old install and had all kinds of software on it that might have been preventing usb from working (iTunes, HTC Sync, some other random software, etc.) Sometimes, I would even have trouble connecting an external HD!

I ended up installing a clean copy of XP on an old computer that i now use strictly for flashing stuff to my phone.

 

[CoolAndroid1]

New problem

I have 4.3 on my HTC now and have received an update for 4.4.2, however when I try this it goes a quarter of the way then comes up with a red triangle and exclamation point. The device is still rooted somehow. Can you help me update?

 

[jollywhitefoot]

New problem

I have 4.3 on my HTC now and have received an update for 4.4.2, however when I try this it goes a quarter of the way then comes up with a red triangle and exclamation point. The device is still rooted somehow. Can you help me update?

I don't think OTA will work on unlocked/tampered device with custom recovery.I think you need to run ruu.exe if one is available for you to get 100% stock before OTA will work again.

 

[CoolAndroid1]

I don't think OTA will work on unlocked/tampered device with custom recovery.I think you need to run ruu.exe if one is available for you to get 100% stock before OTA will work again.

Hello,

I found an FUU for 4.4 Kitkat on the link you posted earlier, It does all the necessary actions with no failures and completes with a Congrats screen but the firmware is the same?