Database Info

[SOLVED] Error formatting /data in ClockworkRecovery [Complete noob]

Hi guys, a little background :
I S-Off'd my Desire S a few weeks ago and installed/clicked gingerbread which i gather roots it?
One day my screen went blank randomly with just the notification bar showing up top. No buttons worked, couldn't turn it off etc.. so I did a battery pull. It then got stuck on the HTC screen, so I googled, tried clicking recovery/factory reset etc.. all while not really knowing what i was doing, but in the end it randomly loaded after a long wait.
Phew, or so I thought.
Now it constantly crashes, turns itself off, the camera doesn't work, force closes galore.. it's a mess. Figured the battery pull messed something up.
Searched a bit more and figured i should try and flash a ROM which might fix it and get it stable again.
Tried installing using 'download ROM' in Rommanager, it did all the installing and whatnot, but when it rebooted nothing had changed. Tried three times, same deal. Figure I should install a ROM via the SD card instead.
Found this forum and a relatively simple/safe guide :
I'm using the guide here : How to flash a perfect ROM.
http://forum.xda-developers.com/showthread.php?t=1257731
The Rom is MIUI.
However, I'm only on step 2 : Format data. (Formatting /system was fine)
Clockworkmod says Formatting /data for about 5 minutes, then : Error formatting /data.
Help!
A big thanks in advance.

Spare yourself a lot of troubles - use RUU and start fresh...
Sent from my HTC Desire S using XDA App

Could be a faulty eMMC chip on the phones motherboard, these tend to break after a few bad battery pulls?
If installing a new ROM on the phone wont work and you get data format problems I would do as posted above. If this doesnt work I would suggest a faulty eMMC chip.

amidabuddha said:
Spare yourself a lot of troubles - use RUU and start fresh...
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Is there a fairly easy to follow guide that includes every step on here?
According to the FAQ I might have a fried chip.. the e:Unable to mount errors.
Can I still save it with the RUU?
I'm clueless, and a fair few of the guides are not too noob friendly tbh, could you please point me in the direction of an easy to follow guide?
I wish I knew how deadly the battery pulls would be before hand, but when your phone is frozen and you can't power it off, it seems logical. Arrrghg.
Much appreciated.

wax_addict said:
Is there a fairly easy to follow guide that includes every step on here?
According to the FAQ I might have a fried chip.. the e:Unable to mount errors.
Can I still save it with the RUU?
I'm clueless, and a fair few of the guides are not too noob friendly tbh, could you please point me in the direction of an easy to follow guide?
I wish I knew how deadly the battery pulls would be before hand, but when your phone is frozen and you can't power it off, it seems logical. Arrrghg.
Much appreciated.
Click to expand...
Click to collapse
Since you still can boot into your system you are good.
Download the RUU that is right for you from here. Connect your phone to the PC and run the RUU.exe. It will hadle everything automatically. Then you will be back to Stock. To go back to custom ROM:
1) use Revolutionary
2) no need of Gingerbreak since you will flash a rooted ROM
3) flash custom ROM from recovery

amidabuddha said:
Since you still can boot into your system you are good.
Download the RUU that is right for you from here. Connect your phone to the PC and run the RUU.exe. It will hadle everything automatically. Then you will be back to Stock. To go back to custom ROM:
1) use Revolutionary
2) no need of Gingerbreak since you will flash a rooted ROM
3) flash custom ROM from recovery
Click to expand...
Click to collapse
Ok, I have the RUU downloaded.
Should I just connect the USB cable to the phone while it's in ClockworkMod, HBOOT, or does it not matter?
Soooo.. plug in USB cable, run the RUU file in Windows.. should work?
Cheers again.

wax_addict said:
Ok, I have the RUU downloaded.
Should I just connect the USB cable to the phone while it's in ClockworkMod, HBOOT, or does it not matter?
Soooo.. plug in USB cable, run the RUU file in Windows.. should work?
Cheers again.
Click to expand...
Click to collapse
Yep. If by any chance the RUU installer says that it cannot detect your device go to Settings -> Development - > enable USB Debugging on your phone

amidabuddha said:
Yep. If by any chance the RUU installer says that it cannot detect your device go to Settings -> Development - > enable USB Debugging on your phone
Click to expand...
Click to collapse
Cheers. Yep, I got no phone detected, check your USB cable etc.. / ERROR [170] USB CONNECTION ERROR
I can't get into the phone to go into settings and turn USB debugging on though As soon as I get it functioning to that degree I'm not using it for anything other than calls in case I break it again. sadly, I could have earlier before I tried flashing a new ROM. Hindsight eh?
All I can get is HBOOT/ClockworkMod.
Tried RUU with the HTC white screen on and also while in Clockwork Mod.
Anything else I could try?
Thanks.

Are you using windows?
If yes download HTC sync and instal it, could be a missing driver.
Swyped from my Desire S

wax_addict said:
Cheers. Yep, I got no phone detected, check your USB cable etc.. / ERROR [170] USB CONNECTION ERROR
I can't get into the phone to go into settings and turn USB debugging on though As soon as I get it functioning to that degree I'm not using it for anything other than calls in case I break it again. sadly, I could have earlier before I tried flashing a new ROM. Hindsight eh?
All I can get is HBOOT/ClockworkMod.
Tried RUU with the HTC white screen on and also while in Clockwork Mod.
Anything else I could try?
Thanks.
Click to expand...
Click to collapse
From the power menu in ClockworkMod reboot to bootloader (hboot) and with the volume key go to FASBOOT (then you should see "FASTBOOT USB"). Then run the RUU again. Let me know is it working please because I will leave my PC soon

amidabuddha said:
From the power menu in ClockworkMod reboot to bootloader (hboot) and with the volume key go to FASBOOT (then you should see "FASTBOOT USB"). Then run the RUU again. Let me know is it working please because I will leave my PC soon
Click to expand...
Click to collapse
It worked, can't thank you enough!!
Cheers all.

wax_addict said:
It worked, can't thank you enough!!
Cheers all.
Click to expand...
Click to collapse
Good to know
Congratulations!

great to read another XDA forum rescue complete successfully!
Please update post#1 (using Go advanced edit) and prefix the post title with [SOLVED] to indicate that the problem is resolved.

Tectas said:
Are you using windows?
If yes download HTC sync and instal it, could be a missing driver.
Swyped from my Desire S
Click to expand...
Click to collapse
Limited to 5 thanks a day but I'll come back, this definitely helped I'm sure, fairly certain the drivers were needed.

wax_addict said:
Limited to 5 thanks a day but I'll come back, this definitely helped I'm sure, fairly certain the drivers were needed.
Click to expand...
Click to collapse
If your intending on re-running revolutionary to S-OFF your device again then you must first de-install the program HTC SYNC from your PC, don't worry the drivers are left behind and there are all that you need.

This is already the 4th case that the "E: cannot open...." error is successfully solved. I am keeping track on all such posts constantly and in my opinion if we have some more evidences for solved errors of this kind it will be good to remove the "[solved]BRICKed: inside eMMC's dead..." thread to avoid stressing the users...
I think this is a mistake of a service technician that was too lazy to diagnose and just replaced the chip...and started a great panic in this forum

Could be true.
I personally think there where a few devices out there with an chip failure, but most of the reported faults where wrong classified and could have been solved other ways.
Maybe it would be good to write the conclusion at the overall section down, cause our device isn't the only affected.
Swyped from my Desire S

Tectas said:
Could be true.
I personally think there where a few devices out there with an chip failure, but most of the reported faults where wrong classified and could have been solved other ways.
Maybe it would be good to write the conclusion at the overall section down, cause our device isn't the only affected.
Swyped from my Desire S
Click to expand...
Click to collapse
I will write a "calming" thread besides the Guide that is in my signature or as a part of it, just waiting for more confirmations that generally the chip is not affected when there is an error. But it seems not much people are reading the guides they prefer to start a new thread...Anyway I have a friend that is working at a centre of a Mobile Operator for my country and according to him among the hundreds (!) Nokia's, Samsung's, etc., he got only one faulty HTC for repair for the last 2 years (and there is a practice to replace rather than repair as well)

amidabuddha said:
This is already the 4th case that the "E: cannot open...." error is successfully solved. I am keeping track on all such posts constantly and in my opinion if we have some more evidences for solved errors of this kind it will be good to remove the "[solved]BRICKed: inside eMMC's dead..." thread to avoid stressing the users...
I think this is a mistake of a service technician that was too lazy to diagnose and just replaced the chip...and started a great panic in this forum
Click to expand...
Click to collapse
Good point although hopefully any new user experiencing this problem for the first time will create a post in this forum and can get pointed in the right direction, or better still there's always the hope that they will look at the INDEX/GUIDES themselves and read some of the resources that have been made available for them to use.
Possibly create a list of most likely resolution strategies in a new thread so that they can be tried in order and I'll refer users to that in the section on eMMC issues at the bottom of the INDEX thread, where I've tried not to scare users into thinking that its all too late and its game over in the textual intro bit!

ben_pyett said:
...
Possibly create a list of most likely resolution strategies in a new thread ...
Click to expand...
Click to collapse
Yep. My "[GUIDE] Read this before going for eMMC replacement" is updated with the solutions that worked so far..

[Q] Inspire 4G BRICKED!!! Help!!!

I hope I am not posting where I am not supposed to, but I desperately need help. I am a noob and have managed to brick my inspire, or at least that's my guess. I can still get in to hboot, but when I select recovery, nothing happens. This all started after trying to use the htc boot unlocker. My screen shows the following when in hboot
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MIROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Dec 22 2011,14:28:19
I have tried loading the stock images using the PD98IMG.zip files that I have found throughout the site, but nothing seems to be working. Please help, or if you can point me to someone that can I would greatly appreciate it. I hate to be a pain, but I don't know what else to do.

dalton42503 said:
I hope I am not posting where I am not supposed to, but I desperately need help. I am a noob and have managed to brick my inspire, or at least that's my guess. I can still get in to hboot, but when I select recovery, nothing happens. This all started after trying to use the htc boot unlocker. My screen shows the following when in hboot
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MIROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Dec 22 2011,14:28:19
I have tried loading the stock images using the PD98IMG.zip files that I have found throughout the site, but nothing seems to be working. Please help, or if you can point me to someone that can I would greatly appreciate it. I hate to be a pain, but I don't know what else to do.
Click to expand...
Click to collapse
YOUR PHONE IS NOT BRICKED. The term bricked means that your phone is a useful as a brick, i.e. if you can get into HBOOT, it's not bricked.
Gotta ask though, why did you not use the Hack Kit as its the only reliable method to root, my advice to you sir is when this gets cleared up READ AND EDUCATE YOURSELF before you really do brick your phone.
If you have a SDcard reader, pop out the SDcard and place one of the PD98IMG stock ROMs on your SDcard. From here you can reboot into HBOOT with the sdcard in your phone and HBOOT should pick up the PD98IMG and flash a working stock ROM. From here, you can root with the Hack Kit...
This will help you, read it and do what the stock ROM option...if you can get into HBOOT

I have tried doing that, it says loading image, then parsing, then goes back to the hboot screen, it doesn't say press volume up to update or anything else as I have read in many other posts. Am I doing something wrong? As far as not using the hack kit, I didn't really stumble on that until after it was to late, sure wish I had found it in the first place. Guess if I could just get it back to factory, I would accept that doing this isn't for me and not mess with it again. I am good at following directions, but nothing I have tried seems to work.

dalton42503 said:
I have tried doing that, it says loading image, then parsing, then goes back to the hboot screen, it doesn't say press volume up to update or anything else as I have read in many other posts. Am I doing something wrong? As far as not using the hack kit, I didn't really stumble on that until after it was to late, sure wish I had found it in the first place. Guess if I could just get it back to factory, I would accept that doing this isn't for me and not mess with it again. I am good at following directions, but nothing I have tried seems to work.
Click to expand...
Click to collapse
is the file named exactly "PD98IMG.zip"..you may also want to check the hide extension option to be sure its not hiding the .zip because if it is and you renamed it to "PD98IMG.zip" with the hide extension on, the phone will read it as "PD98IMG.zip.zip" and you would get that error.
haha and yeah man, we've all been there...I don't want to discourage you man, rooting is such an awesome experience and the hack kit is a pretty straight forward process, if you do the research and take the time to understand what you're doing, but lets see if we can help you out here first. I had the same issue you're having when I tried to flash a radio (same PD98IMG method you're trying to use) and it turned out to be the hide extension issue.

I had also verified that as well, I went under tools, folder options, view tab, scrolled down to hide extensions for known file types and unchecked... And, everything was correct, just verified to be on the safe side.

dalton42503 said:
I had also verified that as well, I went under tools, folder options, view tab, scrolled down to hide extensions for known file types and unchecked... And, everything was correct, just verified to be on the safe side.
Click to expand...
Click to collapse
hmm, so its named PD98IMG.zip caps and everything? If its not working you m ay have to get a stock RUU and run it through fastboot..

This is why you should educate yourself first. You do not need to unlock the bootloader from the HTC dev site. Now you could flash the the stock ruu from the PC and then use the hack kit. Check the stickies in the Inspire general section for more help.
Sent from my HTC Inspire 4G using Tapatalk

I understand that I should have been a little more educated first now, but I thought I had everything in order, thats what thinking gets me... I have tried running the stock ruu, but it gives the following error.
ERROR[155]: UNKNOWN ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
I did notice the Image version the program shows is on the phone is 3.13.0.0, and it is trying to put 2.47.502.7 on the phone... Is this the problem? If so, whats the solution, I am so lost now its not even funny.... I apologize everyone.

dalton42503 said:
I understand that I should have been a little more educated first now, but I thought I had everything in order, thats what thinking gets me... I have tried running the stock ruu, but it gives the following error.
ERROR[155]: UNKNOWN ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
I did notice the Image version the program shows is on the phone is 3.13.0.0, and it is trying to put 2.47.502.7 on the phone... Is this the problem? If so, whats the solution, I am so lost now its not even funny.... I apologize everyone.
Click to expand...
Click to collapse
Dalton, lock your bootloader again. Boot into fastboot and plug the phone. You will see fastboot usb at the top. Then plug your phone and open cmd session. Once there type fastboot oem relock. Once that is done, try flashing the .exe file in the HTC site (original GB update), making sure that you have HTC Sync installed.
If that fails, then I would try using the HACK Kit to gain S-OFF and root. You will then be able to revert to stock or flash a custom rom...

Had a similar problem when using aahk my own fault and I took care of it. Long winded, so short of it, are you trying to install through
1. hboot or 2. on the computer using HTC rom update?
I ended up trying 2. But ended up using aahk to finish.
HTC update errored out and the recovery portion would not work, just in a boot loop on HTC logo
This was good news as aahk could take over on USB during that HTC green letters white background.
I'd suggest reading the effen manual run the tool to get it up and going, figure out what you want to do. I've used it to return to stock with s off before go back into roms.
So look at those options know what you want and then power on the phone USB connected and during HTC screen enter your number the kit should take over and give you what you asked it.
That should give you a working rom image.
--will'm
Sent from my Inspire 4G using XDA Premium HD app

willm98G97B said:
Had a similar problem when using aahk my own fault and I took care of it. Long winded, so short of it, are you trying to install through
1. hboot or 2. on the computer using HTC rom update?
I ended up trying 2. But ended up using aahk to finish.
HTC update errored out and the recovery portion would not work, just in a boot loop on HTC logo
This was good news as aahk could take over on USB during that HTC green letters white background.
I'd suggest reading the effen manual run the tool to get it up and going, figure out what you want to do. I've used it to return to stock with s off before go back into roms.
So look at those options know what you want and then power on the phone USB connected and during HTC screen enter your number the kit should take over and give you what you asked it.
That should give you a working rom image.
--will'm
Sent from my Inspire 4G using XDA Premium HD app
Click to expand...
Click to collapse
He won´t be able to use the Kit if the bootloader is unlocked. HE MUST RELOCK Bootloader...then run the Kit...It´s worth mentioning that...

True, never ran htc s unlock option.
Sent from my Inspire 4G using XDA Premium HD app

Thanks A MILLION!!!
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....

dalton42503 said:
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....
Click to expand...
Click to collapse
Glad you have it back....yeah you'd better read and make sure what are about to do it and of course what risks are involved before making a move....

Dalton,
I would suggest following glevitan's and willm's assertion of getting s-off and root to use custom roms. Custom roms are WAY better than anything HTC has to offer, and much easier to install, if you have an issue warranty wise, you can always return to stock. Just make sure you know how to flash correctly, search for it and you will find easy instructions, and if memory serves, a youtube video which helped me greatly.

dalton42503 said:
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....
Click to expand...
Click to collapse
Can you tell me the which firmware or send me a link.I have a same problem

If you are using AT&T branded cell then go to the htc.com site and in the support section of the inspire you will find it. Otherwise, you will find stock roms in the general section of this forum
Sent from my Inspire 4G using XDA

glevitan said:
If you are using AT&T branded cell then go to the htc.com site and in the support section of the inspire you will find it. Otherwise, you will find stock roms in the general section of this forum
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
I am having a bootloader error with stock ro.(error 140)
How can i fix it

ydnbngl said:
I am having a bootloader error with stock ro.(error 140)
How can i fix it
Click to expand...
Click to collapse
if you have unlocked the bootloader then relock it...then run it again.

glevitan said:
if you have unlocked the bootloader then relock it...then run it again.
Click to expand...
Click to collapse
It is relocked and ship s-on

[Q] HTC Aria will not boot if plugged in

EDIT: Wrong category, sorry. I'm new.
Rooted Aria/Liberty won't turn on if it's plugged in (wall charger or USB). The orange charging light is on and the screen is lit but black. The menu buttons do not turn on. I have to remove the battery after unplugging it for it to turn on.
The phone is rooted and the problem is consistent no matter what ROM I use. I believe it is a problem with the bootloader, but I'm not very advanced with these things.
I rooted the phone with Unrevoked and whenever I boot into recovery mode it says "Revolutionary CWM v4.0.1.4."
Any suggestions on how to make this problem go away? I know it's minor, but it is my mother's phone and every time I'm on the phone with her she complains about it.

The only way to fix a bootloader issue like this is to reflash the stock one, which you can accomplish by sourcing an HTC RUU (ROM Update Utility) for your Aria. This will flash everything back to stock so you'll lose everything, but it will fix these issues that tend to pop up occasionally
Good luck!

juzz86 said:
The only way to fix a bootloader issue like this is to reflash the stock one, which you can accomplish by sourcing an HTC RUU (ROM Update Utility) for your Aria. This will flash everything back to stock so you'll lose everything, but it will fix these issues that tend to pop up occasionally
Good luck!
Click to expand...
Click to collapse
I just did this and the problem is still occuring. I used the RUU on HTC's website that was the upgrade to 2.2. The process went without a hitch, but it did not do anything except change to the stock Froyo ROM. I checked and it was still Revolutionary's bootloader and the same HBOOT (6.02.1002).
I believe I read that Revolutionary is a protected bootloader and fairly difficult to remove, but I'm not sure. I've been researching this for 11 hours now. I've read a lot. >.< I'm up for a challenge, though, so if you or anyone else have instructions/link on how to replace it, I'll try.

ellaizee said:
I just did this and the problem is still occuring. I used the RUU on HTC's website that was the upgrade to 2.2. The process went without a hitch, but it did not do anything except change to the stock Froyo ROM. I checked and it was still Revolutionary's bootloader and the same HBOOT (6.02.1002).
I believe I read that Revolutionary is a protected bootloader and fairly difficult to remove, but I'm not sure. I've been researching this for 11 hours now. I've read a lot. >.< I'm up for a challenge, though, so if you or anyone else have instructions/link on how to replace it, I'll try.
Click to expand...
Click to collapse
Tried this one mate?

juzz86 said:
Tried this one mate?
Click to expand...
Click to collapse
I followed that and the only thing it did was change the top of the bootloader screen from "Revolutionary" to "AlphaRev Unlock." The hboot is still the same. The problem is still happening.
Is there a way to downgrade my hboot even though it is protected? Heck, I can't even turn S-ON because of that.
NOTE: The major problem I'm running into with all the forum posts I find is that they used megaupload to host their downloads and those links no longer work.

ellaizee said:
I followed that and the only thing it did was change the top of the bootloader screen from "Revolutionary" to "AlphaRev Unlock." The hboot is still the same. The problem is still happening.
Is there a way to downgrade my hboot even though it is protected? Heck, I can't even turn S-ON because of that.
NOTE: The major problem I'm running into with all the forum posts I find is that they used megaupload to host their downloads and those links no longer work.
Click to expand...
Click to collapse
Try flashing this recovery....it happened to my wife's Aria, that whenever the phone was charging off I couldn't turn it on until I pulled the battery...after flashing this everything returned to normal....hope it helps
http://forum.xda-developers.com/showthread.php?t=1025704

glevitan said:
Try flashing this recovery....it happened to my wife's Aria, that whenever the phone was charging off I couldn't turn it on until I pulled the battery...after flashing this everything returned to normal....hope it helps
http://forum.xda-developers.com/showthread.php?t=1025704
Click to expand...
Click to collapse
You are MAGICAL. Thank you so much! And thanks to juzz86 for the suggestions as well.
I used fastboot to flash the recovery and now it does the normal battery image when the phone is off and charging.

No problem. When that happened to me, I panicked but after a couple of google searches I came across that...glad you solved it.
Sent from my Inspire 4G using XDA

All of this mate/buddy calling makes me think women aren't a very common occurrence here. I guess I'll have to get used to it.

ellaizee said:
All of this mate/buddy calling makes me think women aren't a very common occurrence here. I guess I'll have to get used to it.
Click to expand...
Click to collapse
hahaha sorry for that. As u can see, I realised after writing it and erased it, but you probably saw it first.....

ellaizee said:
All of this mate/buddy calling makes me think women aren't a very common occurrence here. I guess I'll have to get used to it.
Click to expand...
Click to collapse
Sorry, no offence intended You'd be surprised how common mate/buddy is in Australia, even when ladies are involved.
In my defence, you can still be a mate or buddy as a female
Take care!

juzz86 said:
Sorry, no offence intended You'd be surprised how common mate/buddy is in Australia, even when ladies are involved.
In my defence, you can still be a mate or buddy as a female
Take care!
Click to expand...
Click to collapse
Even in UK they use mate a lot....but it is no defense for me...I am in Argentina... lol

[Solved] PLZ Help me out. stuck at loading screen

my htc one x is with rogers.
yesterday i unlocked my htc, and tried to root it by using the one click root tool
it said success but after rebooting , it stuck at the loading screen with security warning in red " this build is for development ......"
i tried to use ruu to flash PJ83IMG, but at the upgrade selection, it says my img version is 1.94, and the upgraded one is 1.73(or 1.83, i forgot)
i clicked upgrade anyway. i didn't work.
also i tried the ARUWIZARD, it didn't work as well.
plz help me , i just want to get this phone back to working.
any help would be appreciated.
thx for reading
forgot to say that i did relock it.

kongfutoufu said:
my htc one x is with rogers.
yesterday i unlocked my htc, and tried to root it by using the one click root tool
it said success but after rebooting , it stuck at the loading screen with security warning in red " this build is for development ......"
i tried to use ruu to flash PJ83IMG, but at the upgrade selection, it says my img version is 1.94, and the upgraded one is 1.73(or 1.83, i forgot)
i clicked upgrade anyway. i didn't work.
also i tried the ARUWIZARD, it didn't work as well.
plz help me , i just want to get this phone back to working.
any help would be appreciated.
thx for reading
forgot to say that i did relock it.
Click to expand...
Click to collapse
DId you use SuperCID? you should just try different ruu until one of them works. Did you try to get into recovery aka holding down the vol button when you power on?

drklazarus26 said:
DId you use SuperCID? you should just try different ruu until one of them works. Did you try to get into recovery aka holding down the vol button when you power on?
Click to expand...
Click to collapse
i dont know what is SuperCID so i guess i didn't use it.
recovery is the only thing that i can get into right now.
i tried factory reset. didn't work.
im quite new to android so i dont know too many things.
thx for reading and replying.

kongfutoufu said:
i dont know what is SuperCID so i guess i didn't use it.
recovery is the only thing that i can get into right now.
i tried factory reset. didn't work.
im quite new to android so i dont know too many things.
thx for reading and replying.
Click to expand...
Click to collapse
Well if you didnt that means you can only use an ruu for the image you currently have or any ruu after after that. im not to familiar with rogers ruu version numbers but like i said equal or great. I would go into recovery and and go into fastboot and try the ruu then. that should do the trick and you still need to be relocked but you said you did that already so good luck!

drklazarus26 said:
Well if you didnt that means you can only use an ruu for the image you currently have or any ruu after after that. im not to familiar with rogers ruu version numbers but like i said equal or great. I would go into recovery and and go into fastboot and try the ruu then. that should do the trick and you still need to be relocked but you said you did that already so good luck!
Click to expand...
Click to collapse
thx, but i still dont understand how to do it.
can u plz tell me the detail?
what files do i need ? or is there a thread that can help me through the process ?
btw, there is no equal or greater ruu, i searched it , found a few thread asking the same thing but no result.

kongfutoufu said:
thx, but i still dont understand how to do it.
can u plz tell me the detail?
what files do i need ? or is there a thread that can help me through the process ?
btw, there is no equal or greater ruu, i searched it , found a few thread asking the same thing but no result.
Click to expand...
Click to collapse
yeah it seems like you did take all steps. with changing your CID im not really sure what to do. illl be back if i find anything but right now im stuck. sorry man.

drklazarus26 said:
Yeah I was just looking around and I noticed there but only one ruu. this is a link to the ruu ROGER RUU. its an exe so basically hold the vol down button while you turn the power on. you should have a screen that says "fastboot", recovery and so on. select fastboot and connect to your computer. when it finishes installing the drivers and the phone says fastboot usb in red then run the ruu.
actually its not an exe. sorry i need to look it up myself
Click to expand...
Click to collapse
yeah, that is not an exe file. it's a zip file that should replace the rom.zip when u do the ruu (according to the posts online).
that's what i did. the thing is that when i did the ruu thing, my phone version is greater then the one u can find online. so it's not working this way. or maybe im not doing it right.
this phone is killing me right now.
thank u.

no one seems to have a good solution to this???

i just solved it.
it's quiet simple actually.
for ppl who may have the same problem as i did , this is what u need to do :
flash recovery, then go in to recovery mode, wipe everything, except the external storage, then install a new rom
simple...
yea , first of all , unlock ur device.
thx/.

Should change the title of post from [Q] to [solved] so that people know your all set and others that may find the info useful.
Sent from my Nocturnalized One XL using Forum Runner

[SOLVED] Flashing light, no screen...Help appreciated!

Hi All!
Recently i flashed TWRP and Cynogenmod 10.2.1 stable to my HTC Telestra One XL (evita)
I unlocked boot-loader
I successfully rooted
But I shut down once, and when i tried to boot, it got stuck in a boot-loop
Upon many retries, it suddenly wont turn on
when I charge it it only has a flashing red light but it wont even turn on, no screen not buttons; nothing!
And if I plug it in to my PC, the pc keeps sounding the USB Connected sound multiple times over a short period of 30 seconds to 2 minutes and then it gives off multiple shaky beeps
I hope this is enough info to let anyone help out!
Thank You in Advance
EDIT:
when connected to a pc it shows drivers is ready to use but tries to install QHUSB_DLOAD but fails and latest RUU does not detect
Thx again

What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita

timmaaa said:
What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita
Click to expand...
Click to collapse
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated

So does it power on at all?
Sent from my Evita

timmaaa said:
So does it power on at all?
Sent from my Evita
Click to expand...
Click to collapse
nope
when plugged in it only has a red LED that flashes once every once in a while and thats it
pc recognises it but wants to install qhusb_dload (as mentioned) and it just sais no driver found
i am researching and i found something called a "RIFF Box" but unsure if its worth it, plus i dont know where to jtag it (if its possible at all)
PS: hi from sydney!

Al-Dazzlez said:
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated
Click to expand...
Click to collapse
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.

It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita

Hi from Canada!... I just wanted to be part of the greetings.. :laugh:

exad said:
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.
Click to expand...
Click to collapse
he placed the cyanogen mod on the phones sd card, then he wiped sd card, after that he used the install function on twrp it gave him a message that his phone is not rooted and if he would like to root it, he accepted, then it rebooted into twrp, and he tried again to install, same message appeared and then he gave up and shut it down...(sorry for vague terms, please bear with me, still trying to learn the ropes of talking on this forum)

I gotta say, this is all very odd :/ How did he install anything if he wiped the SD card after copying it over? :/ hmmmm In any case, you CAN try he jet tool as per my last post before getting a jtag. You'll need a linux install or Bootable USB stick/CD/DVD though.

My guess is that the only thing he installed was SuperSU. That'd be why it booted straight back into TWRP.
Sent from my Evita

timmaaa said:
It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita
Click to expand...
Click to collapse
i researched..nothing..just some videos of people who do it (jtag)in the US and US only......
but still asking 'round the shops wont hurt i guess:laugh:
ill keep ya posted about using that tool you mentioned!
and exad; SUP!
and yeah.. it sounds weird to me too but i mainly play around with stuff like the galaxy series samsung's so the htc stuff is still new...and i have to admit...i am hating it so far.... but still experience cant hurt :laugh:

Hi guys!
im back
I JTAG'd the phone overseas, and it came back, surely enough, working, but now another problem arises,
the guy apparently unlocked the bootloader, S-Off, and installed CM with android 4.3.1. the phone boots, everything is well, but for times from 10 seconds to minutes of usage it just turns off, the Hboot shows
***tampered***
***relocked***
any idea wth is wrong with it now?
it does not reboot from power menu, and does not do anything really since I cant keep it on for more than a few minutes at most. I cannot keep it on long enough to unlock the bootlaoder anymore, and I cannot boot into TWRP (as the guy told me he put it on)
da hell do I Do now? any help appreciated

Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita

timmaaa said:
Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated

Al-Dazzlez said:
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated
Click to expand...
Click to collapse
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita

timmaaa said:
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita
Click to expand...
Click to collapse
I Just ran one, Unlocked bootloader, on Cm11 snapshot after re-root and all that crap done, should be alright now