So my current situation is that I am romless, though I can boot into recovery(wipe and everything fine) but my external is also wiped.
My device seems to have a problem where whenever I mount it, windows cannot transfer new .zip roms as it always hangs at the 5% mark and never moves after that(reads an error after an hours or so). I've tried the nocturnal fix but that did not help.
I have tried relocking the bootloader but thr rogers RUU I've used here http://forums.team-nocturnal.com/showthread.php/1005-RUU-One-X-XL-LTE-RUU-s just hangs on sending...
Do you have the appropiate drivers?
---------- Post added at 04:04 AM ---------- Previous post was at 04:04 AM ----------
And what recovery are you on
Yes, I have all the appropriate drivers. The phone mount used to work but I must have not safely removed it and now it's like this :s
TWRP 2.4.1.0
Hmm. Think this I'd a job for inflated titan but try reformating your sd
Thanks, I'll try trying to factory reset the internal again.
a box of kittens said:
Hmm. Think this I'd a job for inflated titan but try reformating your sd
Click to expand...
Click to collapse
That's what I would do... Restart computer, format your SD card... Kind of sounds like you don't have the appropriate storage, so a SD wipe might help.. I'd hate to give you advice that will erase everything and potentially not correct the problem, but its a step you have to try to get a working phone.. Did you do any resets in bootloader? (White screen with skatin droids)
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
That's what I would do... Restart computer, format your SD card... Kind of sounds like you don't have the appropriate storage, so a SD wipe might help.. I'd hate to give you advice that will erase everything and potentially not correct the problem, but its a step you have to try to get a working phone.. Did you do any resets in bootloader? (White screen with skatin droids)
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Thanks for pitching in Titan, I did as instructed but this blasted thing still does not want to transfer files to the phone, always getting a stuck progress bar. Sigh* At this point in time I would not mind to wipe the whole phone if I had to, however I could not get RUU to work so maybe I'll just try it on a different pc and see if that works out.
And no, I cannot get to the classic bootloader menu, only the htc one. I used the nocturnal method to try and re-format my external but that doesnt seem to be working.
EDIT: Well a miracle occurred and I was able to get at least one .zip on my internal(but really all I did was change the usb port to the built in mobo one). Thanking those who pitched in.
Can't get to bootloader? I mean no disrespect man but your not doing it right... If your phone at least power cycles, you can get to bootloader. Did you press power+volume down till the lights blink and shuts off, hold for a second and release power button while keeping down the volume button?
Is the phone locked or unlocked?
EDIT: glad to see you have it worked out, I always find success with the main USB ports, I.e the back if the computer etc.
Any questions feel free to ask away, I don't mind trying to help one bit
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
Can't get to bootloader? I mean no disrespect man but your not doing it right... If your phone at least power cycles, you can get to bootloader. Did you press power+volume down till the lights blink and shuts off, hold for a second and release power button while keeping down the volume button?
Is the phone locked or unlocked?
EDIT: glad to see you have it worked out, I always find success with the main USB ports, I.e the back if the computer etc.
Any questions feel free to ask away, I don't mind trying to help one bit
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Oh whoops, misunderstood the question before I could get into bootloader of course!
Well since you offered, I flashed this rom http://forum.xda-developers.com/showthread.php?t=2130320 but when I boot into it, my touchscreen is unresponsive. Any incidents of this?
Since your phone was probably on 4.11 before the update and you can only flash sense 4+ roms until kernel source comes out
a box of kittens said:
Since your phone was probably on 4.11 before the update and you can only flash sense 4+ roms until kernel source comes out
Click to expand...
Click to collapse
Ah that's lame. Any foresight into that? Does HTC have to release that themselves?
protomanez said:
Ah that's lame. Any foresight into that? Does HTC have to release that themselves?
Click to expand...
Click to collapse
It should be released soon
Ah, kind of leaves me sour in the mouth but I can wait to get rid of sense entirely. Thanks again you guys.
Related
I TRIED THE HBOOT 2.2 ROOT GOT BRICKED AND USED THE FIX FROM "Monarky"
THANKS DUDE AND IT WORKED SO IVE PUT TOGETHER
A SHORTER FIX I ACTUALLY DID THE WORK MYSELF SO ALL YOU HAVE TO DO IS REPLACE THE ATTACHED FILE WITH THE ONE ON YOUR SD CARD
AND RELOAD BOOTLOADER AND IT SHOULD UNBRICK BUT ITS GOING TO SWITCH YOUR "PRI VERSION" BUT IT WORKS
ALL I ASK FOR IS A SIMPLE THANKS
FIX - http://www.megaupload.com/?d=2KA69REH
How are you defining "bricked?" What was your phone doing? What did the screen look like?
Tapa tapa tapa
mlin said:
How are you defining "bricked?" What was your phone doing? What did the screen look like?
Tapa tapa tapa
Click to expand...
Click to collapse
he was probably referring to being stuck at the RUU update screen
mlin said:
How are you defining "bricked?" What was your phone doing? What did the screen look like?
Tapa tapa tapa
Click to expand...
Click to collapse
s0xpan said:
he was probably referring to being stuck at the RUU update screen
Click to expand...
Click to collapse
well yea the red triangle
I haven't downloaded what you cooked up there, but if included radios or the wimax partition, you really need to warn people that they could lose 4G.
If you "brick" your phone, you should only use the RUU from Sprint to fix it. If the phone isn't recognized by the RUU, then extract the PC36IMG.zip from it and use the fastboot command line to flash.
-- Brian
That's not a brick. A brick is when your device will not do anything. Won't power on, won't even light up when you plug it in. There's nothing you can do with a true brick, that's why it's named that way.
If you can get into bootloader, you can recover your device.
clamknuckle said:
That's not a brick. A brick is when your device will not do anything. Won't power on, won't even light up when you plug it in. There's nothing you can do with a true brick, that's why it's named that way.
If you can get into bootloader, you can recover your device.
Click to expand...
Click to collapse
Not true. Here is a scenario for you...actually happened to my evo:
Your entire os gets erased, except bootloader. Your screen won't even come on, but the charge light comes on, and the computer sees the device. Fun part is, it does not even see it as android...it pops up as qualcomm. Ruu doesn't work. Pc36Img doesn't work. Trying to flash through fastboot doesn't work. Why? Because there are so many bad blocks in the memory that nothing will write (htc doesn't allow their handsets to skip bad blocks). So, you were mostly right, but there are exceptions to everything.
tejasrichard said:
Not true. Here is a scenario for you...actually happened to my evo:
Your entire os gets erased, except bootloader. Your screen won't even come on, but the charge light comes on, and the computer sees the device. Fun part is, it does not even see it as android...it pops up as qualcomm. Ruu doesn't work. Pc36Img doesn't work. Trying to flash through fastboot doesn't work. Why? Because there are so many bad blocks in the memory that nothing will write (htc doesn't allow their handsets to skip bad blocks). So, you were mostly right, but there are exceptions to everything.
Click to expand...
Click to collapse
So... as the man said, if you got it working then it wasn't really "bricked."
Tapa tapa tapa
tejasrichard said:
Not true. Here is a scenario for you...actually happened to my evo:
Your entire os gets erased, except bootloader. Your screen won't even come on, but the charge light comes on, and the computer sees the device. Fun part is, it does not even see it as android...it pops up as qualcomm. Ruu doesn't work. Pc36Img doesn't work. Trying to flash through fastboot doesn't work. Why? Because there are so many bad blocks in the memory that nothing will write (htc doesn't allow their handsets to skip bad blocks). So, you were mostly right, but there are exceptions to everything.
Click to expand...
Click to collapse
Nope, your wrong. Back when I used to mod PSPs, if you flashed a firmware incorrectly, you'd either get a semi-brick or a brick. A semi-brick is when you can't get into the OS, but you can access some sort of recovery menu/method. A brick is when it won't turn on at all or it will turn on but won't do anything (or freeze at splash screen).
mlin said:
So... as the man said, if you got it working then it wasn't really "bricked."
Tapa tapa tapa
Click to expand...
Click to collapse
Who said it was working?
I very clearly said that it wouldn't work, no matter what method was used. Please reread my original post. I don't think you understood what I said. Though you could get the phone into bootloader, the screen was not on. The only reason you would even know the phone was on was if you had it hooked up to your comp when you powered up. There was no method you could use that would allow anything to be written to the internal memory. There was a hardware problem with some of the evos, where in they have a TON off bad blocks. This prevented the os from being rewritten. I have meet a few other guys on xda who have the problem with bad blocks. So, how would you define this, if not as a brick? It wasn't hung up somewhere. It was totally unusable. After spending 2 hours on IRC, we decided it was totally unfixable. Took it to a sprint repair center the next day and, funny enough, they agreed. They couldn't even access it enough to tell that I had an unlocked bootloader. Yes, they replaced it.
tejasrichard said:
Who said it was working?
I very clearly said that it wouldn't work, no matter what method was used. Please reread my original post.
Click to expand...
Click to collapse
Ok, fair enough and my bad for misreading your post and I realize that I misread Clamknuckle's original post which is why I misinterpreted yours. SOmetimes I just gotta slow down a bit I guess.
mlin said:
Ok, fair enough and my bad for misreading your post and I realize that I misread Clamknuckle's original post which is why I misinterpreted yours. SOmetimes I just gotta slow down a bit I guess.
Click to expand...
Click to collapse
No big deal, man
The whole thing is pretty silly, anyway. My only point was you could be bricked and still have your charge light comer on. No hard feelings here.
Tejasrichard is right. I got one of the bad blocks phone, brand new too. I guess ill use it for a spare touchscreen
Bootup Problem
So I have an evo that when powered up only displays the startup white HTC EVO 4G screen for 5 sec....turns off for 3 or 4 sec then back on and same in a continuous loop. I can access regular android recovery with the white screen and androids on the bottom. When I choose recovery from the options on that page it does nothing but the white HTC EVO 4G screen boot looping over and over.
Things I have tried:
New SD Card
PC36IMG - tons of them from many methods
Flash a new recovery
The computer does recognize the phone but I can't find it anywhere?
Any help ?
PM me please.
clamknuckle said:
That's not a brick. A brick is when your device will not do anything. Won't power on, won't even light up when you plug it in. There's nothing you can do with a true brick, that's why it's named that way.
If you can get into bootloader, you can recover your device.
Click to expand...
Click to collapse
X2!.................
After trying this method my phone stills only boots to the white screen
I know we're going to get at least one person who says their phone is bricked. Here's how to unbrick it (links to stock rom/kernel, etc) for Virgin and Sprint versions:
http://www.howardforums.com/showthread.php/1691827-Intercept-free-stock-ROMs-and-apps!
You'll need to know how to install and patch SWUpdate for the Moment so it works for the Intercept. Not hard at all.
Did I miss something? How did we go from the EVO to the Moment/Intercept? Anyhow I'm having the same problem as whoisjlk in post #14. Please if anyone has a solution I would greatly appreciate it and even donate. PLEASE PLEASE PLEASE...thanks in advance.
Wow I guess I posted in the wrong section LOL.
Ok, I have an Evo that I would like to recover from the dark side.
I rooted my HTC EVO 4g using Unrevoked, it worked fine, then I decided to flash a new rom, followed all the steps and I backed up my stock and wipe data/factory reset and Davik, now my phone doesn't read the sd card.
Took the sd card out and did a FAT32 format (4 times already), downloaded the new zip to it and still not reading.'
Bought a couple different SD cards.
Can't do a restore because the sd card and is not recognized.
As soon as I check install zip from card it reads
ClockworkMod Recovery v2.5.0.1
E:Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)
(No such file or directory)
E:Can't mount /sdcard
Now I know Amon RA Recovery is way better.
I had S-OFF, after wipe all data have S-ON and don't know why.
This is what I tried:
All kinds of PC36IMG (Recoveries, ROMS, Unrevoked S on and S off)
ADB doesn't work.
Phone is not found, when try to update drivers using Windows 7 it says that Qualcomm-CDMA-Technologies-MSM driver is not found, but my other EVO and the ones that I rooted have no problems.
Phone boots into HBOOT and Recovery.
After opening HBOOT PC36IMG gets recognized but not updated.
In recovery when try to flash from SD has the message E: Can't blah blah
If I try to reboot the phone, it just goes to a black screen with a flashing LED or gets stock on white screen forever.
Any ideas?
I would like to fix it, already have a working phone, and I don't need this one, is just to put all the help together and maybe some one that has a similar problem can avoid all the troubles and follow a single post and not spend hours searching just to find the wrong answers.
Otherwise is going to be just for spare parts and that doesn't help many.
Thanks in advance.
If you have an idea, lets try it, PM or reply here.
SO yeah I decided to flash Miui lastnight and this happened clockworkmod wont load up for me to reflash or whipe, when I try to boot into clockwork htc logo comes up then slowly dies to black, though I can access hboot so what should i do?
I'm kinda new to this so step by step kinda thing would be great.
I have a video but I cant post it cause I'm too new.
TBRATCHER said:
SO yeah I decided to flash Miui lastnight and this happened clockworkmod wont load up for me to reflash or whipe, when I try to boot into clockwork htc logo comes up then slowly dies to black, though I can access hboot so what should i do?
I'm kinda new to this so step by step kinda thing would be great.
I have a video but I cant post it cause I'm too new.
Click to expand...
Click to collapse
it's not bricked.... power off the phone then press and hold the power key and the vol down key at the same time til you see the HBOOT screen. vol down until RECOVERY is highlited then press power. That will bring you into Recovery mode. now wipe data/factory reset... then wipe cache partition.. then go to advanced and wipe Dalvik Cache... go back to mounts and storage and format system...
after all that then go back to install zipfrom sdcard and reinstall miui that should do it
Im not going anywhere so I'll be here, let me know how you do
Ouch. That sucks. Don't worry though, there is hope.
What you will have to do is remove your SD card and download a stock RUU and it will flash in Bootloader. Unfortunately I believe it will unroot you. I am not positive on that though. I will post a link so you can be reading a little more about it, we helped a guy thru this the.other day, but he wasn't rooted. Should be the same process though. You'll want to wait until we know exactly what to do because this is your one shot before you got a fancy paperweight. I have to run to atnt for a minute. Start reading so you'll know a little more of what is going to go on, and hang tight. Someone else may step in before I'm back, but you can start familiarizing yourself with the process shortly.
This fellow was pricked during an OTA update. About the same steps will be taken...
http://forum.xda-developers.com/showthread.php?t=1222662
Tread lightly. I am gonna do my best to help, but I am not an expert. However I do feel confident that since Bootloader is all you can load that this is your fix. See ya soon.
Edit: I was under the impression your phone would not boot. Apologies...
Thanks for the feedback guys. Yes, hboot is all I have so I'm going to take it slow at this point, taking a look at the thread now.
TBRATCHER said:
Thanks for the feedback guys. Yes, hboot is all I have so I'm going to take it slow at this point, taking a look at the thread now.
Click to expand...
Click to collapse
I've gotten the same thing in the past when updating sense via HTC on a rooted rom lol.... it's most likely a bad flash sometimes you just have to reflash a rom but Im 99.9% sure it's not bricked
Like, you just had hboot when you tryed to boot into recovery it was just black? lol
TBRATCHER said:
Like, you just had hboot when you tryed to boot into recovery it was just black? lol
Click to expand...
Click to collapse
yeah the green HTC logo came up and faded black... i had to pull the battery out and put it back and hboot into recovery, once there I wiped everything and re flashed the rom and everything booted up just fine
Yeah, thats not the case here, i've done that multiple times and it remains the same.
search around on here for a stock rooted rom in PD98IMG.zip form There may be one inside the hack kit but cant remember. put it on your sdcard boot into bootloader by holding volume down and pressing power. let it search for the update. hit volume up to confirm update after it finds it. If you can access hboot your not bricked take a deep breath and relax
TBRATCHER said:
Yeah, thats not the case here, i've done that multiple times and it remains the same.
Click to expand...
Click to collapse
what program did you use to root ?
http://forum.xda-developers.com/showthread.php?t=961406
I have, should I just match the radio and flash it. If the file is corrupt it could for sure brick me. My question is how do you flash a rom from hboot? Cause I have the stock RUU from HTC Dev but I don't know how to go about doing that.
oxlong27 said:
search around on here for a stock rooted rom in PD98IMG.zip form There may be one inside the hack kit but cant remember. put it on your sdcard boot into bootloader by holding volume down and pressing power. let it search for the update. hit volume up to confirm update after it finds it. If you can access hboot your not bricked take a deep breath and relax
Click to expand...
Click to collapse
there ya go, that would have been my next step lol
TBRATCHER said:
I have, should I just match the radio and flash it. If the file is corrupt it could for sure brick me. My question is how do you flash a rom from hboot? Cause I have the stock RUU from HTC Dev but I don't know how to go about doing that.
Click to expand...
Click to collapse
you have a micro sd card reader on your computer ?
Here's a link to gb stock rooted. Look at post 4. Credit goes to gene for the file.
To flash you will need a way to transfer files to your SD card.
Download the file and rename to PD98IMG.zip. boot into hboot it will scan and ask you to apply the update.
If you can't transfer files try the ruu exe. Version you downloaded.
http://forum.xda-developers.com/showthread.php?t=1191949
Yeah I have a micro to regular SD, I'll give this a shot right now.
well looks like you guys got him heading in the right direction. but at any rate op feel free to pm me if further assistance is needed. good luck
Sent from my Inspire 4G using XDA Premium App
WIll do, thanks.
Got the dowload off gene, it's loading the zip in hboot now. I'll let you know how it goes.
Success! Thanks for your help everyone it is much appreciated.
I was one of the unlucky testers before Steve0007 closed the thread. Did anyone figure out how to save our Sensation after the bad flash? My phone does not light up or respond to any button presses but when plugged into the computer it is recognized as an "unrecognized device."
I guess this is the risk we run being early testers. Hopefully someone figures it out otherwise I've got myself very expensive paper weight.
I assume no two button rescue? And this should be in q/a or general
Can you get to the bootloader?
Sent from my Sensation using xda premium
what did he brick people's phones with what was it supposed to be?
Wrong section. And that happened to me when i got an hd2 and i bricked it. Luckily it was 2 days after i bought it so tmobile gave me another because they thought something was wrong with it. But next time please post in the right section. Thanks.
nba1341 said:
what did he brick people's phones with what was it supposed to be?
Click to expand...
Click to collapse
Its probably only a soft brick
Sent from my Sensation using xda premium
Thank god I didn't flash it, I just finished downloading it when people started reporting issues.
Anyway, I'm sure he didn't mean for it to happen. If you have a spare battery, have you tried putting that one in?
These things are usually flash at your own risk.
I would never flash a ruu, unless it's official it could cause problems.
Sent from my Sensation using Tapatalk
Also, if it doesnt work and if you have tmo. Tell them bs and they will get you one. Just some advice and please dont flame me.
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Yes as I said, this happened to me exactly when i had a tmo HD2 and flashed a european ruu and it was dead. I tried everything. You will have better luck to talk to your insurance company.
Have you got ADB installed on your pc? If not start downloading and installing it. I will find some links, in just a sec.
Edit:
New to ADB CLICK HER
More to set up path CLICK HERE
http://www.mediafire.com/?rrwi4f258lie1r7
Extract to system 32 or sysWOW64 (64bit)
Try 3 finger salute (VOL UP,VOL DOWN + POWER) with your phone plugged into pc and pc volume up see if it makes a sound like a device has connected.
Whats was this RUU anyway?
if you just need ADB you dont need all of the stuff above or to set up a path if its extracted to those folders
duychau said:
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Click to expand...
Click to collapse
This is excatly what happened to me.Computer wont see the phone though,so no adb fix can be applied.Mnn i'm so pissed as i dont have insurance.
usually blagging HTC will do the trick for a repair,dont mention XDA, ROOT, ICS or basically anything except your phone said update was available and the battery died
Click to expand...
Click to collapse
roflcopter is 10chars
duychau said:
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Click to expand...
Click to collapse
What does it recognize it as?
unrecognized usb device
Ok guys, it looks like the firmware that I posted to another thread from 3.06 bricked few devices. I have flashed it and it worked fine, so i tried again with the package i posted and indeed it is corrupted as it bricked also mine
My device does not respond, so I would think it is dead
I feel sorry for those who have bricked also theirs based on the package i posted.
I am closing my Rom thread and starting now my Rom developments will be for my own use. I will not publish anymore my work.
Again I feel sorry for those who have lost their devices.
Steve
ok so now his rom thread is closed. Why not keep it open and work together to help those with bricked devices attempt to restore them to a working state?
That way you keep your reputation rather than running away after bricking devices?
Arrrggghhhh,This could not have come at a worse time
nba1341 said:
ok so now his rom thread is closed. Why not keep it open and work together to help those with bricked devices attempt to restore them to a working state?
That way you keep your reputation rather than running away after bricking devices?
Click to expand...
Click to collapse
Because as far as I know no way to get them back
Tried installing a ROM, and being the noob that I am it was an International Rom. I used TeamWin. Can't post outside links because I'm new. The rom was IceColdJelly AOKP ROM from onexroot.com
I realize I was stupid. I just want out of this situation and I'll be really careful for now on. Is my HOX a lost cause? I bought it about 2 weeks ago (Really unlucky with the whole price drop...). And now, I've done this.
I get it, I've learned my lesson. XDA please help me out. How can I fix this brick? (If it is a brick? I'm assuming.)
Epsilon707 said:
Tried installing a ROM, and being the noob that I am it was an International Rom. I used TeamWin. Can't post outside links because I'm new. The rom was IceColdJelly AOKP ROM from onexroot.com
I realize I was stupid. I just want out of this situation and I'll be really careful for now on. Is my HOX a lost cause? I bought it about 2 weeks ago (Really unlucky with the whole price drop...). And now, I've done this.
I get it, I've learned my lesson. XDA please help me out. How can I fix this brick? (If it is a brick? I'm assuming.)
Click to expand...
Click to collapse
Yes, it's a brick, but there is a fix if you have access to a Linux computer and know what you're doing.
beaups said:
when the device is bricked (qhusb mode), after pushing and holding power for ~10 seconds - in linux shortly thereafter all of the partitions will enumerate and expose themselves to linux for about 5 seconds (you'll see sdX1, sdX3, sdX8, about 30 partitions alltogether). During that quick 5 seconds you can DD whatever you feel like back to those partitions.
.
This is how I've recovered bricks. Corrupt hboot --> Brick device. DD back correct hboot while in this mode --> unbricked
Click to expand...
Click to collapse
It successfully flashed? Than yes follow his directions only way out if it successfully flashed and your device is unresponsive
omario8484 said:
It successfully flashed? Than yes follow his directions only way out if it successfully flashed and your device is unresponsive
Click to expand...
Click to collapse
Good point, if you were on stock 2.20 before, it's not bricked, you just need to get back into recovery and flash something else.
bricked
iElvis said:
Good point, if you were on stock 2.20 before, it's not bricked, you just need to get back into recovery and flash something else.
Click to expand...
Click to collapse
It was stock 2.20. I bought the phone a week or two ago. HBOOT 1.14. But the phone still won't turn on?
Epsilon707 said:
It was stock 2.20. I bought the phone a week or two ago. HBOOT 1.14. But the phone still won't turn on?
Click to expand...
Click to collapse
Can your computer see it? Was it fully charged before?
Try plugging into the charger for a while. The battery in this phone has a weird tendency to suddenly lose all its charge.
iElvis said:
Can your computer see it? Was it fully charged before?
Try plugging into the charger for a while. The battery in this phone has a weird tendency to suddenly lose all its charge.
Click to expand...
Click to collapse
Computer cannot see it. Atleast constantly. My computer makes a noise like a drive was plugged in, then shortly after an error-like similar sound.
I'll try charging it for a few hours. Thanks!
Epsilon707 said:
Computer cannot see it. Atleast constantly. My computer makes a noise like a drive was plugged in, then shortly after an error-like similar sound.
Click to expand...
Click to collapse
That's not good. What does it look in explorer like when it shows up? Do you see QHSUSB anywhere?
The new hboots won't allow flashing of an incompatible Rom. Make sure you charge it for a while hold power button and volume down for a few seconds and see if capacitive buttons flash. If so, release power button but continue to hold volume down and see what happens
Sent from my HTC One XL using xda app-developers app
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Word of advice bro, don't flash anything what so ever from anywhere except xda. You'll be asking for trouble
Sent from my HTC One XL using xda app-developers app
iElvis said:
That's not good. What does it look in explorer like when it shows up? Do you see QHSUSB anywhere?
Click to expand...
Click to collapse
Nope. I'm running Windows by the way. I don't have access to a Linux computer right now, but I will later.
Epsilon707 said:
Nope. I'm running Windows by the way. I don't have access to a Linux computer right now, but I will later.
Click to expand...
Click to collapse
Okay, try what InflatedTitan suggested and see what happens.
InflatedTitan said:
The new hboots won't allow flashing of an incompatible Rom. Make sure you charge it for a while hold power button and volume down for a few seconds and see if capacitive buttons flash. If so, release power button but continue to hold volume down and see what happens
Sent from my HTC One XL using xda app-developers app
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Word of advice bro, don't flash anything what so ever from anywhere except xda. You'll be asking for trouble
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Zero response. I'll keep trying.
Epsilon707 said:
Zero response. I'll keep trying.
Click to expand...
Click to collapse
Let it charge for a few hours and try again.
Still no avail. Any other ideas?
I could really use some help. Anyone have an idea or a suggestion on what to do? I also don't suppose this is covered under my warranty
Okay, a couple of questions:
-Are you certain you were on 2.20? I ask because there have been cases of people buying One Xs recently and getting phones on 1.85.
-The phone is completely unresponsive despite being plugged into an outlet (not your computer) for a couple of hours?
iElvis said:
Okay, a couple of questions:
-Are you certain you were on 2.20? I ask because there have been cases of people buying One Xs recently and getting phones on 1.85.
-The phone is completely unresponsive despite being plugged into an outlet (not your computer) for a couple of hours?
Click to expand...
Click to collapse
Yes, I am certain. I remember checking it in the About Phone section of settings.
Completely unresponsive, but I'll keep trying.
Epsilon707 said:
Yes, I am certain. I remember checking it in the About Phone section of settings.
Completely unresponsive, but I'll keep trying.
Click to expand...
Click to collapse
Okay, one last thing. Open up Device Manager in Windows and expand the whole directory tree. Check "DVD/CD-ROM devices" in particular. Plug your phone in and see what happens.
If nothing happens at all, try leaving it plugged in overnight and see if anything is different. If it's still dead, it's bricked, whatever you did with it. Since it's new, you should be able to return it and get a new one.
Idk what to say if you were on 2.20 it should of failed the Rom flash...but it successfully flashed ?
omario8484 said:
Idk what to say if you were on 2.20 it should of failed the Rom flash...but it successfully flashed ?
Click to expand...
Click to collapse
I'm f'ing baffled myself mate.
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