Database Info

[Q] H1X disaster (cant mount sd, bootloop, relocked, HELP!)

Hi,
I am a noob and this has been a complete disaster. I am a very new to this whole rooting, flashing, rom, etc. stuff and am not too farmiliar with many terms and actions and don't know how to do a lot of things. i have done something quite recently which i am afraid has bricked my phone.
-i unlocked bootloader and rooted my phone
-using cwm 5.8.2 i think..??
-tried to install a cyanogen mod 10 but kept getting stuck at cyanogen mod boot screen
-went into cwm cleared caches, dalvik caches, cleared data, etc.
-tried rebooting but kept getting stuck at the htc quietly brilliant boot screen
-went back into cwm but kept getting error E:cant mount/SD card when trying to do anything
-went into bootlaoder and tried to factory reset
-still stuck at htc quietly brilliant boot screen
-found another thread about using ruu..??
-typed into fastboot command window >fastboot oem lock >fastboot oem rebootRUU
-stuck at silver htc logo
-tried a ruu program, didn't seem to do anything
-rebooted, still stuck at htc quietly brilliant screen
-tried to go back into ccwm recovery but couldnt cause i think my bootloader is ***RELOCKED***
-in cmnd window, commands don't seem to work
-HELP!
also right now my bootloader says:
****TAMPERED*****
****RELOCKED ******
****security warning******
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
i don't know if this helps
wont let me flash or boot im cmnd window
still stuck at htc quietly brilliant boot screen when rebooted
I am completely clueless on what to do now. If possible, i would just completely like to reset everything and have a normal phone
Please, any help is appreciated!
Many thanks

Many things wronh here... Cwm...factory reset in bootloader which corrupted your sd storage... Fast rebootruu is a dangerous thing to type out there.... Just find the 2.20 ruu and run that and be done and format your sd with your computer

a box of kittens said:
Many things wronh here... Cwm...factory reset in bootloader which corrupted your sd storage... Fast rebootruu is a dangerous thing to type out there.... Just find the 2.20 ruu and run that and be done and format your sd with your computer
Click to expand...
Click to collapse
Thanks for replying. Just a couple more questions. How can I tell which ruu is mines, and where can i get it? also do i format through device manager, or computer devices, or something completely different?

Well, damn, boy. You don't have a brick, but you're very lucky not to after all that.
Sounds like what happened was using CWM (not really recommended for this phone, at least that release), then not flashing the boot.img in fastboot when you tried to install CM. You have to do that on your firmware unless you're s-off.
Once you relock, you have to ruu or unlock again. You can't flash anything from there.
This is the ruu you want, which is for 2.20.
http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
Once you're done with that, I recommend slowing down and doing a lot more reading before trying to mod your phone again.

Thanks you so much guys! i got my phone back to stock settings and everything seems to be going well so far.
I will definitely be sure to do some correct research before doing anything m unsure of
Thanks!

You should s-off before continuing. It will help with boot loops.

[Q]HTC sensation4G stuck on juopunutbear screen after S-OFF and bootloader is locked!

Hi Guys,
I am a first time poster on XDA and have already done my homework, reading other posts, regarding my problem. A similar post is here,http://forum.xda-developers.com/showthread.php?t=2284273, but the solution is not applicable to me.
So, I unlocked my HTC Sensation 4G, using HTC-DEV and it said unlock in the boot-loader. I followed this tutorial, http://forum.xda-developers.com/showthread.php?t=2182792
After I flashed recovery into my phone, I flashed both CVM and TWRP, it flashed fine but from the boot-loader I was not able to load my phone into recovery mode, so as to proceed to the step 3.
Then, I read somewhere that the phone needs to be S-OFF for that, so then I followed this tutorial to S-OFF my phone. http://forum.xda-developers.com/showthread.php?t=1870233
I was successfully able to gain S-OFF after the wire trick. Now the phone is stuck at the Juopunutbear Logo, with green arrow pointing down.
I went to the ControlBear troubleshooting guide and followed the steps under "ROM / Data Recovery".
ControlBear with -r and -f parameters say phone should boot normally now, but its again stuck there.
I also tried to flash my boot_backup.img as said there, but it fails
sending 'boot' (16384 KB)...
OKAY [ 3.441s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 3.757s
My phone bootloader specs are :
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.000
RADIO-11.23.3504.07_M2
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012
I cant unlock my phone again using HTC-DEV
Error : FAILED (remote: unlock token check failed)
Plus I cant flash the 4EXT recovery, its the sends the file but the
Error : FAILED (remote: not allowed)
I think I have to unlock it somehow and then I can flash 4EXT recovery.
I am using UBUNTU (LINUX).
Any help would be appreciated.
Thanks

You need to flash juopunutbear hboot.
For that check my soff guide.. Troubleshoot point #3 - flashing jb hboot section
Once done
Do the rom/data recovery section.. To get out of jb logo
Sent from my Nexus 7 using xda premium

ganeshp said:
You need to flash juopunutbear hboot.
For that check my soff guide.. Troubleshoot point #3 - flashing jb hboot section
Once done
Do the rom/data recovery section.. To get out of jb logo
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks Ganesh, you pin pointed the problem, I flashed juopunutbear hboot (by editing the CID, which is superID) and it says Juopunut Bear , instead of LOCKED now. Then, I followed the rom/data recovery section. Everything went well till step 5, means
ControlBear -r
ControlBear -f
fastboot flash boot boot_backup.img
fastboot flash recovery recovery_backup.img
Now, it says boot to Android, so I used reboot on the boot-loader screen but after rebooting its still the same screen with green arrow down.
But I can successfully send stuff to the device meaning flashing, how should I proceed now.
[EDIT] OK I flashed 4EXT recovery on my device, and I can reboot via recovery mode, so I am trying to make progress here, and I will check back if I am stuck again. Thanks
Thanks

vanbug said:
Thanks Ganesh, you pin pointed the problem, I flashed juopunutbear hboot (by editing the CID, which is superID) and it says Juopunut Bear , instead of LOCKED now. Then, I followed the rom/data recovery section. Everything went well till step 5, means
ControlBear -r
ControlBear -f
fastboot flash boot boot_backup.img
fastboot flash recovery recovery_backup.img
Now, it says boot to Android, so I used reboot on the boot-loader screen but after rebooting its still the same screen with green arrow down.
But I can successfully send stuff to the device meaning flashing, how should I proceed now.
Thanks
Click to expand...
Click to collapse
if you still have stucked there try to flash a custom rom from recovery
before flashing do a full wipe from recovery

rzr86 said:
if you still have stucked there try to flash a custom rom from recovery
before flashing do a full wipe from recovery
Click to expand...
Click to collapse
Thanks rzr86 and ganesh
I flashed 4EXT recovery and rebooted in recovery mode, then installed the latest firmwire 3.33 followed by Android Revolution HD with Sebastian Kernal.
Everything works fine now, thanks for the suggestions guys!!
Cheers

One XL no onger recognizes unlock.bin from HTC DEV

Good day everyone.
I relocked and installed stock RUU (4.0.3) on my Evita since I had that failing zip install though TWRP. It worked fine but when I tried to manually install the latest RUU (Android 4.1) it failed. Now I decided to unlock it again and start to flash custom ROMs, problem started.
1.) After flashing boot, recovery and custom rom (tried it with CM 10.1 and JellyBam), it would go only up to the boot image (HTC) and stay on there forever. Cleared everything that I could clear on the recovery and cleared fastboot cache.
What I did, relocked it again and tried running the stock RUU (through the computer) and shows error and won't complete.
2.) Now, phone no longer recognizes the Unlock_code.bin from HTC dev. I tried manually flashing it in fastboot and as well as using the All-in-one-tool for Evita, it would somehow show that it went through on both but looking at my phone, it stays: Relocked. Tried it with at least three unlock bin files to no avail.
3.) Other than that, turning the phone off and back on would go straight to bootloader. When I select Recovery, it would go back straight to fastboot mode. Tried to flash recoveries again, and would get this:
E:\Mobile Devices\sd-fix\Nocturnal_SD_FIX_EVITA\Nocturnal_SD_FIX_EVITA>fastboot
flash recovery openrecovery-twrp-2.5.0.0-evita.img
sending 'recovery' (7992 KB)... OKAY [ 2.140s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.871s
E:\Mobile Devices\sd-fix\Nocturnal_SD_FIX_EVITA\Nocturnal_SD_FIX_EVITA>fastboot
flash recovery openrecovery-twrp-2.2.0-evita.img
sending 'recovery' (7460 KB)... OKAY [ 1.692s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.370s
Now I'm stuck with a phone with no OS. Please help. I appreciate your time.
Here's my phone info.
AT&T HTC One X
S-ON
HBOOT - 2.14.0000

Getting a new code only requires fast boot. So just get a new unlock code.....
*edit*
Sorry I misread. This happened to me. Just simulate a battery pull by pressing and holding power and try again. Keep doing that over and over. Eventually, it will work.
Took me about 10-15 tries once.
Sent from my One X using xda app-developers app

Also try to lock the phone even if it tells you it is already locked.
fastboot oem lock
Do that prior to attempting the unlock after full power cycle. Sometimes that gets the device back on track, dont worry too much this issue is not exactly new and after a bit of dicking around the phone will unlock again.

Thanks for your responses!
Yeah, it did. After a number times requesting for unlock bins and re locking, finally it was unlocked.
Now I now have problem #1 from OP. It actually goes to HTC boot screen, stays there for a couple of seconds then reboot. It's been doing that in a loop. Flashed three different ROMs and three different versions of TWRP and phone still does the same thing.
Found my mainver to be 3.18 which I suspect have been changed when I attempted to run the 4.1 RUU (this was before I tried to unlock the bootloader). Downloaded the said RUU from two different sites just to be sure. None of those have worked.
So I found a thread here in XDA saying that this could be the reason why I couldn't boot any of these ROMs.
Any thoughts/help would be greatly appreciated.

Must not have read very much before trying to root if you don't know fastboot flash boot boot.Img
Sent from my One X using xda app-developers app

You're s-on so you need to flash the boot.img manually on hboot 2.14.
Retrieve the boot.img from the ROM zip and place it in your working directory on your pc.
Copy ROM to phone (if you haven't already done that).
Do a full wipe in recovery, then flash the ROM.
Reboot to the bootloader, connect phone to pc, make sure it says fastboot usb on your phone screen.
Open a command prompt in your working directory and issue the following command:
fastboot flash boot boot.img
Reboot the phone.
Enjoy.
Sent from my Evita

Typically bootloops are solved by
flashing recovery cwm or twrp.
wipe cache, data and system.
Manual install the boot.ing from rom you are installing.
Fastboot flash boot boot.img
Install your rom in recovery.
Hopefully all will work then
Sent from my HTC One XL using xda app-developers app

exad said:
Must not have read very much before trying to root if you don't know fastboot flash boot boot.Img
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
timmaaa said:
You're s-on so you need to flash the boot.img manually on hboot 2.14.
Retrieve the boot.img from the ROM zip and place it in your working directory on your pc.
Copy ROM to phone (if you haven't already done that).
Do a full wipe in recovery, then flash the ROM.
Reboot to the bootloader, connect phone to pc, make sure it says fastboot usb on your phone screen.
Open a command prompt in your working directory and issue the following command:
fastboot flash boot boot.img
Reboot the phone.
Enjoy.
Sent from my Evita
Click to expand...
Click to collapse
twistedddx said:
Typically bootloops are solved by
flashing recovery cwm or twrp.
wipe cache, data and system.
Manual install the boot.ing from rom you are installing.
Fastboot flash boot boot.img
Install your rom in recovery.
Hopefully all will work then
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
It's actually my fourth device. Did flash boot.img all the time. That's why it's kind of frustrating.

Any thoughts about damaged eMMC? Just hypothetical.
I don't know if it was a brick but I had an issue before where this HOXL didn't boot up after flashing a wrong kernel. Didn't even light up when plugged to power and had to re-flash the eMMC block using that WIP method. It went back to life.
Might need to try that again. Would that be possible? Still have to download live ubuntu, though. The one I used before got corrupted.
What I did so far:
-relock
-unlock
-erased fastboot cache
-flashed boot.img ( from the custom ROMs that I've tried )
-flashed twrp ( 3 versions )
-wiped every wipe option i could see
I already have tested at least 6 ROMs on this device with no issue with TWRP.
I had ViperXL installed before this happened. I wiped everything out and tried to flash the ATT Android 4.1 RUU and everything got screwed.
edit: i typed the capcha on the title box. lol

You're still s-on right?
Sent from my One X using xda app-developers app

exad said:
You're still s-on right?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yup!
Is there a way to s-off while you're on fastboot? Facepalm method requires it on booted android. So far can't see other procedures done through fastboot.

EjWilkes0121 said:
Yup!
Is there a way to s-off while you're on fastboot? Facepalm method requires it on booted android. So far can't see other procedures done through fastboot.
Click to expand...
Click to collapse
Get twrp running 2.3.3.1 and flash any sense Rom then s-off
Sent from my HTC One XL using xda premium

I'm going to try again once I get home from work.
Thanks for all your responses guys.

Done it all.
Relocked, intalled RUU - fail.
Unlocked, wiped everything, installed ROM, erased fastboot cache, flashed boot.img, erased fastboot cache - bootloop.
Tried using CWM and same thig happes - bootloops after flashing rom and boot.img
However, I just noticed something.
Whenever I get to flash a zip through recovery, process seems to just complete in no time. I have flashed multiple ROMs and one could really see progress shown on progress bar on both recovery flashing( CM10.1, JellyBam ) and through Aroma installer( CleanROM, ViperXL ).
When this problem started, entire process would initiate, pauses for few seconds then it completes. Can't see the progress bar move across.
I might be going out of topic here but I'm desperate in having this fixed.
Your thoughts and ideas means a lot.

Are there any roms you can boot?? How are you downloading the files? On a pc? Did the md5 match. Maybe the usb wire has a defect and screws the file upon transfer. Your have a really strange issue. I'll flash out of boredom and never had that happen, Even with roms that do nothing more than boot.
And your running twrp 2.3.3.1???
Sent from my HTC One XL using xda premium

I think the recovery is most likely at fault here.
Make sure it's twrp 2.3.3.1: http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Use a USB 2.0 port just to be safe.
check md5 omg so important!
Code:
fastboot erase recovery
fastboot flash recovery openrecovery-twrp-2.3.3.1-evita.img
fastboot erase cache
fastboot reboot bootloader
Select recovery
Check the md5 of the sense rom you downloaded
Extract boot.img from rom.
Transfer the rom zip to the phone.
wipe cache, dalvik, system and factory reset in recovery
install sense rom
reboot to bootloader
Code:
fastboot flash boot boot.img
fastboot reboot
Do all that and then tell me what happens.

Back to life!
A huge thanks to you guys! Big time! :victory:
It could be the recovery that screwed it up. Been trying TWRP 2.5 and TWRP 2.2 most of the time. I gave TWRP 2.6 a shot and that made a successful install. I flash ViperXL 3.2.7 + ElementalX 6.7 and phone's back to life!
One thing i noticed. After I S-Off'ed, phone's kind of jerky using normal use. One noticeable thing is the lock screen that doesn't respond after waking, takes 1-2 sec to respond when swiping the lock ring. Big prob for me, battery stuck at 77% even when charged or used heavily. Random reboots also happen. Maybe have to read the entire FacePalm S-Off thread this week. LoL. For now, back to S-On, phone works perfect.
Again, thanks so much for your help guys! Won't be missing any Thank button that you got. :laugh:

I found current sense roms work better with latest firmware so s-off ruu to 3.18 and then see how things run.
Sent from my HTC One X using xda app-developers app

Inspire 4g MAJOR Problem !

I am SO Freaking lost..... My problem is my phone will freez at the HTC splash screen, and the only things I can get into is bootloader and 4ext recovery. I can't flash any images they don't want to be flashed with the PD98img.zip I can't do anyting my phone is empty with no android os.. I am stuck. I can't seem to do much with fastboot with images either.

AlphaOmegaPrimus said:
I am SO Freaking lost..... My problem is my phone will freez at the HTC splash screen, and the only things I can get into is bootloader and 4ext recovery. I can't flash any images they don't want to be flashed with the PD98img.zip I can't do anyting my phone is empty with no android os.. I am stuck. I can't seem to do much with fastboot with images either.
Click to expand...
Click to collapse
can you give some background as what you did to get the phone into this state?

http://forum.xda-developers.com/showthread.php?t=1208507 I tried this to restore my phone thinking it would fix all my problems instead I must have messed something up, and now i'm pretty sure my phone is a paper weight. I managed to run fastboot oem rebootRUU and installed htc_inspire4g_att_RUU_3.20.502.52_US.exe but it hangs at white screen with HTC logo.

Did you try both flash packages?
Sent from my SAMSUNG-SGH-I527 using XDA Premium 4 mobile app

jzsidebott said:
Did you try both flash packages?
Sent from my SAMSUNG-SGH-I527 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm a NOOB, I have no idea what you mean by that. Sorry

AlphaOmegaPrimus said:
I'm a NOOB, I have no idea what you mean by that. Sorry
Click to expand...
Click to collapse
In the link you provided, on the first page, there were two seperate downloads, depending on when the phone was developed. "Download (restores to official Froyo 2.2.2) (315MB)" and also "Download (restores to official Gingerbread 2.3.3) (309MB)". Was just wondering which one you tried if any at all.

The only thing I can boot into is the 4ext Recovery Touch & hboot Can someone send me stock inspire 4g rom 4ext backup files they are *.tar files [email protected] Or [email protected]
Would that restore my system ?
the phone is
*** Unlocked ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0030
MICROP-0438
RADIO-26.17.14.11_M
eMMC-boot
If this helps
The 4ext Touch Recovery says under info
system ext3 549.2mb 504.9 free
data ext3 1.1gb 1.0 free
cache ext3 140.4mb 127.6 free
sdcard fat32 1.9gb 1.9 free

http://forum.xda-developers.com/showthread.php?t=1208507
4.Reboot to HBOOT: Shutdown completely (disconnect USB if connected and pull battery if necessary) then while holding down the VOL-DOWN key, press the POWER key for about half a second. The phone should boot into HBOOT, check the PD98IMG.zip for consistency, then prompt you to install. Select VOL-UP to install.
5.Once installed, HBOOT will prompt you to reboot by pressing the POWER button. Do this
I can get to step 4 and instead of flashing the PD98IMG.zip is says parsing and just goes back to hboot. I can't flash anything.

I have been making some MAJOR progress on my phone.. after messing around with a lot of fastboot commands, I found this with helped .. fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img if forces some images to boot.
Also the link I posted above only will work if my phone is relocked. I can't even make post in the Inspire 4G Android Development , because i'm "too new " to ask a question. But I managed to get his program to run again and I've noticed something. on step 7
7.Once successfully completed, the phone will automatically reboot to HBOOT and begin the process of installing the RUU. The only thing you have to do at this point is acknowledge the prompt to install by pressing VOL-UP. (Note: the RUU install may skip a couple of images during the install but this is normal.
IT FAILS to copy the RUU to the sdcard. and that's what has left my phone without an OS. I've also got the stock RUU htc_inspire4g_att_RUU_3.20.502.52_US.exe to run and complete But my phone hangs after the HTC logo..
So i'm headed in the right direction. Any ideas ???? ~ T

SO I've made a HUGE step in progress yesterday, I installed JellyTime rom and inspire mod and gapps. and forced the boot.img file to boot using fastboot -c "lge.kcal=0|0|0|x" boot boot.img it made the boot.img to run and start JellyTime. I've got android installed on the phone now. The only problem is I need to S-OFF so I can fastboot flash boot boot.img. It won't do it right now, As of now the phone will bootup and hang on the White HTC logo screen, Every attempt to S-OFF the phone has failed so far. Any Ideas ?

Your phone is bricked?
Try flashing this ROM
http://forum.xda-developers.com/showthread.php?t=996368

AlphaOmegaPrimus said:
SO I've made a HUGE step in progress yesterday, I installed JellyTime rom and inspire mod and gapps. and forced the boot.img file to boot using fastboot -c "lge.kcal=0|0|0|x" boot boot.img it made the boot.img to run and start JellyTime. I've got android installed on the phone now. The only problem is I need to S-OFF so I can fastboot flash boot boot.img. It won't do it right now, As of now the phone will bootup and hang on the White HTC logo screen, Every attempt to S-OFF the phone has failed so far. Any Ideas ?
Click to expand...
Click to collapse
You don't need S-Off to fastboot flash boot.img. Just an unlocked bootloader.
bayartiesto said:
Your phone is bricked?
Try flashing this ROM
http://forum.xda-developers.com/showthread.php?t=996368
Click to expand...
Click to collapse
This is not at all helpful. He is asking for boot.img or S-Off help. If he can't do that his ROM is irrelevant.

OMG. this is the worst place for help ever. I have Jelly time installed and I can get into it But only AFTER forcing the boot.img to boot. I CANNOT boot into jellytime by it's self normally. BECAUSE I cannot flash the boot.img file I get an error message. Because I need S-OFF to be off. right now it's on. Everything I've tried has failed.

AlphaOmegaPrimus said:
OMG. this is the worst place for help ever.
Click to expand...
Click to collapse
This is just about the worst way to start a post where you're asking for help.
AlphaOmegaPrimus said:
I have Jelly time installed and I can get into it But only AFTER forcing the boot.img to boot. I CANNOT boot into jellytime by it's self normally. BECAUSE I cannot flash the boot.img file I get an error message. Because I need S-OFF to be off. right now it's on. Everything I've tried has failed.
Click to expand...
Click to collapse
Did you even read what I wrote before??
bananagranola said:
You don't need S-Off to fastboot flash boot.img. Just an unlocked bootloader.
Click to expand...
Click to collapse
Also, you haven't told us what error message you get when you try to flash the boot.img. And is your bootloader unlocked??

AlphaOmegaPrimus said:
OMG. this is the worst place for help ever. I have Jelly time installed and I can get into it But only AFTER forcing the boot.img to boot. I CANNOT boot into jellytime by it's self normally. BECAUSE I cannot flash the boot.img file I get an error message. Because I need S-OFF to be off. right now it's on. Everything I've tried has failed.
Click to expand...
Click to collapse
What does forcing the boot.img means? there is no other way to flash a boot.img that in fastboot if you are S-ON. There is no need to be S-OFF to fastboot flash. In fact, having S-OFF is not enough to enable flash commands in fastboot (you actually need ENG S-OFF for that).
I suggest that you give detail information about the errors and what you are doing if you want to get helped.

Hello,
I have htc inspire. My phone was new sept 2011 and worked until july 2012. My phone was set to charge only and usb debug disable and was never rooted. One night I put the phone to charge and the next day it I turned it on but it never made past the white screen. I have tried to put the rom on sd card as PD98IMG. I tried RUU. The phone lists:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024 MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Apr 12 2011,00:55:45
When I try using RUU it gets stuck on reloading bootloader
When I try the PD98IMG method using a goldcard, it gets stuck:
parsing...[SD ZIP]
[1] BOOTLOADER -UPDATING
[2] BOOT
[3] RECOVERY
etc
Please help

Not sure but What helped me get past the HTC logo screen is just recovering the old Stock of the phone.
The link provided is to return back to old stock AT&T Roms.
http://forum.xda-developers.com/showthread.php?t=1385016
Boot your phone in Bootloader mode (PWR + VOL DOWN).
Run the RUU Installer.
For S-Off, Advanced Hack Kit (AAHK) was quite a big help to me.

My problem is I have s-on. Phone freezes when I try pd98img on sd goldcard. I can connect with fastboot but I am not sure how to use it. The phone was in charge only & usb debug off when it use to work.
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024 MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Apr 12 2011,00:55:45
Any help would be greatly appreciated

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

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?

CoolAndroid1 said:
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!
Click to expand...
Click to collapse
Hi,
What do you want to flash stock sense 6...??
greets

shivasrage said:
Hi,
What do you want to flash stock sense 6...??
greets
Click to expand...
Click to collapse
Hello,
Yes I would like to go back to Sense 6 or any stock firmware preferably 4.4.2
Thanks

CoolAndroid1 said:
Hello,
Yes I would like to go back to Sense 6 or any stock firmware preferably 4.4.2
Thanks
Click to expand...
Click to collapse
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

shivasrage said:
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
Click to expand...
Click to collapse
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

CoolAndroid1 said:
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
Click to expand...
Click to collapse
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

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

shivasrage said:
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
Click to expand...
Click to collapse
After i fix my drivers issue what can i do afterwards?

shivasrage said:
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
Click to expand...
Click to collapse
I can now do the fastboot command from CMD

CoolAndroid1 said:
After i fix my drivers issue what can i do afterwards?
Click to expand...
Click to collapse
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

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.

jollywhitefoot said:
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.
Click to expand...
Click to collapse
I cant unlock my bootloader as its relocked and fails, I cant install TWRP either

CoolAndroid1 said:
I cant unlock my bootloader as its relocked and fails, I cant install TWRP either
Click to expand...
Click to collapse
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)

jollywhitefoot said:
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)
Click to expand...
Click to collapse
Hello,
I did have the error code above but i used FUU to flash back to stock and all is fine now!!

CoolAndroid1 said:
Hello,
I did have the error code above but i used FUU to flash back to stock and all is fine now!!
Click to expand...
Click to collapse
Cool. Did you use fuu from here?
http://forum.xda-developers.com/showthread.php?t=2659109

jollywhitefoot said:
Cool. Did you use fuu from here?
http://forum.xda-developers.com/showthread.php?t=2659109
Click to expand...
Click to collapse
Yep! Windows 8 sucks with drivers and didn't work so had to switch to a different laptop!

CoolAndroid1 said:
Yep! Windows 8 sucks with drivers and didn't work so had to switch to a different laptop!
Click to expand...
Click to collapse
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.

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?

CoolAndroid1 said:
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?
Click to expand...
Click to collapse
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.

jollywhitefoot said:
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.
Click to expand...
Click to collapse
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?