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.
Related
i was trying to root down to rc29 and everytime i do i get an error, when it says BOOT it fails. thus leading to the whole update to fail. everytime i turn on my g1 it goes straight to bootloader
any help ? i already reformated my memory card and download a RC29 again and still no luck !
if i return this to tmobile thru warrenty exchange, will it count as out of warrenty ?
jayizzbakk said:
i was trying to root down to rc29 and everytime i do i get an error, when it says BOOT it fails. thus leading to the whole update to fail. everytime i turn on my g1 it goes straight to bootloader
any help ? i already reformated my memory card and download a RC29 again and still no luck !
if i return this to tmobile thru warrenty exchange, will it count as out of warrenty ?
Click to expand...
Click to collapse
Did you put the DREAIMG.NBH file onto your SD card?
Make sure you extracted everything if you downloaded it by zip file. Once you do that, you'll find the .NBH file in there.
Also wrong section
Well, if you go to Bootloader, I'm sure you don't have a Brick. Brick means it stays at the G1 Screen and doesn't do anything else.
yeah i did, i always downgrade no problem, this was a exchange so i had to re root and now its giving me this message
G1BRICKED said:
Well, if you go to Bootloader, I'm sure you don't have a Brick. Brick means it stays at the G1 Screen and doesn't do anything else.
Click to expand...
Click to collapse
ironic its your name lol
but yeah thats what i thought..but everytime i try and get this error what else can i do ! RC29 is like the safe house, if thats broken then what lol
Well, I thought I was bricked before too but naah. The nice people here made fun of me for a day, and then started helping me. Try Flashing a different RC?
G1BRICKED said:
Well, I thought I was bricked before too but naah. The nice people here made fun of me for a day, and then started helping me. Try Flashing a different RC?
Click to expand...
Click to collapse
hmm like the rc8? europe version? what other rc's are out there?
i redownload rc29 and reformatted just to be sure and i still had the error, is this the first time a problem like this occured? i looked around and no one has the same problem
RC33. Google it man, it's Android for Nas-sake! Yeahh haha, did you see the irony in that? Nas, your location is Queens, New York. Hahahahahahahha lmaooo. I am hilarious.
ahaha yeah, i live 5 bus stops away from queens bridge actually. im in astoria. and i cant get into recovery, when my phone turns on it goes straight to bootloader no splash screen. i thought i cpuld only flash the DREAHIMG.nbh only (which is what i have/tried)
Shiz I though RC33 was... wth. Wow. You kids now a days, messing with an old geezer like me. Loll. Uhmm. Yeaah. Hahaha, I think I'm gonna go before you break you're phone. So no Splashs. Well den we know you don;t have any water damage. LOL I AM COMEDY. Naah uhmms, well you usually don't get Splashes when you go into FastBoot and BootLoader. Try, doing, idk. Damn it people, help two playas out. I'm stupid and can;t even use ADB properly, and this guys stuck with BootLoader. I was afraid to Boot into FastBoot yesterday, help us!
LOL yeah man im stuck, i just got this replacement today! i called in for a replacement AGAIN but im afraid they will say this one is tampered with/out of warrenty since its doing it
http://android-dls.com/wiki/index.php?title=OTA_Updates
It could be a stuck Camera button also. That would call for a replacement.
i read that somewhere but i doubt it cause even if it was the update wouldnt fail at BOOT. i tried actually holding out the camera buttom while powering..same thing.
Probably because when you hold the Camera button, that's what boots you into BootLoader. And don't forget, when you start the update, you can't press any buttons. So if the camera button is being held, then you will go straight to BootLoader. When you start the Update, the Camera button will be pressed, and you won't be able to finish the Update.
hmm that is also true but what i dont get is why it wpuld say FAIL at the boot part (the check off list after you flash dreahimg.nbh
this happened to me while I was rooting my brother's phone a while back. What I did was redownload the .nbh and put that on the sd card and when i started it again it downgraded no problem. but for this you're gonna need a microSD reader or another device you can pop the sd into so you can put the .nbh on it because you can't access it through the G1 at this state.
yeah i use a sdcard reader always. i redownloaded and re formated! still same issue....hmmm
you're formatting to FAT32 right?
idk maybe try downloading it from a different source.
It sounds like the exact same thing that happened to me, I downloaded the DREAIMG.nbh from a different place than I got the one I had previously to get it right
hmmm alright will try that, i got mine off megaupload link that was posted in the rooting tutorial
try the one in Cyanogen's tutorial, I think that's the one I used
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
My Galaxy S3 will not respond to any combination of button presses, and the device is identified as QHSUSB_DLOAD in Device Manager. If I take out the battery and plug it in, the light turns red for ~10 seconds, and then turns off. (Device Manager is refreshed at this time, but still reads it out as QHSUSB_DLOAD). It does not respond to home+power+vol down or up.
To get to this result, I had booted into recovery mode in order to install a new ROM, but the installation failed. I chose the reboot option and this is how I ended up. Looking back, I probably should've restored the device prior to booting...
x04a said:
My Galaxy S3 will not respond to any combination of button presses, and the device is identified as QHSUSB_DLOAD in Device Manager. If I take out the battery and plug it in, the light turns red for ~10 seconds, and then turns off. (Device Manager is refreshed at this time, but still reads it out as QHSUSB_DLOAD). It does not respond to home+power+vol down or up.
To get to this result, I had booted into recovery mode in order to install a new ROM, but the installation failed. I chose the reboot option and this is how I ended up. Looking back, I probably should've restored the device prior to booting...
Click to expand...
Click to collapse
You most likely need to go into Odin mode and flash back to stock using Odin. Just follow the steps in this guide:
http://forum.xda-developers.com/showthread.php?t=1762709
Also, dumb question, but is your battery dead? I know I had this problem coming from a completely dead battery once, took a bunch of tries to get it to start charging and turn back on. But I wasn't coming off of a bad flash, of course.
dontsayeta said:
You most likely need to go into Odin mode and flash back to stock using Odin. Just follow the steps in this guide:
http://forum.xda-developers.com/showthread.php?t=1762709
Also, dumb question, but is your battery dead? I know I had this problem coming from a completely dead battery once, took a bunch of tries to get it to start charging and turn back on. But I wasn't coming off of a bad flash, of course.
Click to expand...
Click to collapse
The battery was at ~60% when I was flashing.
ALSO: I can't get into ODIN mode as the device doesn't respond to any type of button combination.
Deleted.
dontsayeta said:
Ok. I don't know what steps you have taken so far, but do a battery pull and then try to get into Odin mode.
Click to expand...
Click to collapse
I don't know if you read the OP or not but I did in fact already do what you stated. It does not work. I have: Battery pull+attach to USB, Battery pull+battery back in. Neither work to get back into ODIN mode.
Yeah, sorry, I did read that right after my post, but I couldn't go back and edit it fast enough because I have these new user restrictions on my account.
dontsayeta said:
Yeah, sorry, I did read that right after my post, but I couldn't go back and edit it fast enough because I have these new user restrictions on my account.
Click to expand...
Click to collapse
I understand, I have the same restriction. However, I think that the device is simply bricked and cannot be recovered. If no solution is posted then I will be heading to the VZW store tomorrow I suppose.
x04a said:
My Galaxy S3 will not respond to any combination of button presses, and the device is identified as QHSUSB_DLOAD in Device Manager. If I take out the battery and plug it in, the light turns red for ~10 seconds, and then turns off. (Device Manager is refreshed at this time, but still reads it out as QHSUSB_DLOAD). It does not respond to home+power+vol down or up.
To get to this result, I had booted into recovery mode in order to install a new ROM, but the installation failed. I chose the reboot option and this is how I ended up. Looking back, I probably should've restored the device prior to booting...
Click to expand...
Click to collapse
Your phone is hard bricked. I'm gonna guess you were flashing a non Verizon ROM, probably an international.
The only fix at this point is a JTAG service. Also, unfortunately you would not have been able to restore before leaving recovery anyways. I'll try to find the popular website people use for that service.
Sent from my SGS3 running Eclipse 2.1 build 4
Yep, sounds like you flashed a ROM not made for the Verizon S3. Be a little more careful next time.
Check out mobile tech videos for a JTAG.
Zalithian said:
Yep, sounds like you flashed a ROM not made for the Verizon S3. Be a little more careful next time.
Check out mobile tech videos for a JTAG.
Click to expand...
Click to collapse
Thanks I couldn't remember the site.
Sent from my SGS3 running Eclipse 2.1 build 4
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
josh995 said:
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
Click to expand...
Click to collapse
Probably just google about flashing roms, find a youtube video and follow instructions. Wonder if a lot of videos don't have a warning, or if people ignore it.
josh995 said:
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
Click to expand...
Click to collapse
I'm just an idiot, and jumped the gun on this flash.
josh995 said:
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
Click to expand...
Click to collapse
Well, back in the days before quadcore... the roms that were made for the international HTC Desire HD also worked on the us version the HTC Inspire 4G. . . I fell right into the pitfall after getting used to that.
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.
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