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
Related
Hi all, I am sorry if this is already posted or answered but I spent all day yesterday searching and reading and cannot find the answer.
I have 2 Htc sensations that I messed up some how and would be very grateful if you could help me with them.
Phone 1 has been rooted for a long time and in preparation for ICS I flashed T-mobil: Download 3.32 from here
http://forum.xda-developers.com/showthread.php?t=1459767
and now the phone works but it will randomly reboot. I have wiped the cache, delvak cache and battery stats.
I am completely lost please help.
Phone 2 I think I may have messed up real bad here is what I did to it.
I rotted it from here
http://forum.xda-developers.com/showthread.php?t=1192300
I got to step 2 sub step 6 and now it continuously reboots it starts with the white screen with HTC on it then goes to another white screen that says HTC Quietly brilliant for a second and repeats.
Please help me yes I am a noob and grateful for any help.
Wow that was a fun ride (not really) it appears I did not flash the PG58IMG file correctly, after I flashed it correctly I got Insert Coin installed and so far it seems that they both are working. only time will tell.
Thanks anyway guys.
A.J.
If you are trying to install the latest firmware and having the HTC log restart problem. Try to super wipe on the recovery and install first the 3.12 firmware.
HTH
Did you install supercid after root?
Sent from my HTC Sensation 4G using xda premium
Both phones are working fine but I have a new question, I can not get the voice dialer to work ie I long press the button on my plantronics bt and say call tom.
I have tried vlingo from the market and this fix
http://forum.xda-developers.com/showthread.php?t=1133246
but nothing has worked. is it just not working in Insert Coin rom?
Did I just brick my phone?
I tried to flash the 1.17 firmware and the last step failed, now it wont boot at all just a black screen the only thing it will do is the charge lite will come on bit it stays on after I unplug it.
which of the 2 phones you are talking about?
In a previous post you said that problem was solved, now what?
Also, it would be better to know what your bootloader says and what you were attempting to do before black screen.
area1509 said:
Did I just brick my phone?
I tried to flash the 1.17 firmware and the last step failed, now it wont boot at all just a black screen the only thing it will do is the charge lite will come on bit it stays on after I unplug it.
Click to expand...
Click to collapse
Sounds like a brick to me, but since the problem is unclear, it's possible to fix. I wish I could help but I don't understand your issue to be honest!
I had 3.32 on it with Insert Coin ICS and thought I have 2 so might as well restore one to factory setting that's when I tried to flash the 1.17 and it never started again.
T-Mobile HTC Sensation 4G
The other one is working so I am not messing with it.
I had the same thing happen to me and it was over for the phone. Took it in to tomo and told them it died and after I charged it and went to turn it on, bam, went black and never came back. They never got it to work either and replaced it for me
You mean 1.17 is the hboot?
In this case you installed a hboot for GB while on ICS rom. Obviously it won't work.
If you want to downgrade to GB you can try to run a GB RUU while in bootloader - fastboot usb (if you can still reach it)
kualmente said:
You mean 1.17 is the hboot?
In this case you installed a hboot for GB while on ICS rom. Obviously it won't work.
If you want to downgrade to GB you can try to run a GB RUU while in bootloader - fastboot usb (if you can still reach it)
Click to expand...
Click to collapse
He was in the process of going back to gb and that's 1 of the steps. U have to flash a gb firmware to go back to it from ics. I've done it countless times with no issues.
mugetsu666 said:
He was in the process of going back to gb and that's 1 of the steps. U have to flash a gb firmware to go back to it from ics. I've done it countless times with no issues.
Click to expand...
Click to collapse
Oh yes I have made many times too buf, if he changed firmware without changing rom obviously get stuck, and this seems happening to him.
No what's happened to him is what happened to me. It's like it gets fried or something. The screen goes black and u can't turn it on or get into bootloader. Tmobile told me when it happened it was dead and got me a new 1
kualmente said:
Oh yes I have made many times too buf, if he changed firmware without changing rom obviously get stuck, and this seems happening to him.
Click to expand...
Click to collapse
Yes you got it I will try to get it replaced. Wish me luck.
Thank you guys so much.
area1509 said:
Yes you got it I will try to get it replaced. Wish me luck.
Thank you guys so much.
Click to expand...
Click to collapse
Good luck mate. Just let us know if it worked
Folks, I wouldn't call myself a n00b in flashing phones--I've been flashing ROMs since my HTC Wing so I feel like I have a decent amount of experience under my belt. But this Sensation...
From the start, performing S-OFF was tricky in itself, particularly with the paperclip trick. Miraculously, it worked after the third try. Flashing ROMs was a whole different monster. Even with 4ext, I could only flash THREE ROMs from the huge collection in the Development forum. And I honestly don't even know why--I kept on getting Error 0 for every build I tried to load. It was only through luck or magic that I was able to flash HyperNonsense, a MIUI build, and another one that I don't remember. Upgraded 4ext to latest version: nope. Changed SD card: nope. Different sequences of superwipe/no superwipe, clear dalvik, etc.: nope. I'm using HyperNonsense for now since it's pretty legit, but even then, I'm getting reboots all over the place. Stock kernel or different kernels--doesn't matter. I have a hunch it has to do with the bottom row of capacitive buttons running so hot.
Oh well, just holding out for the One X+ on T-Mobile or the next Nexus device. Just wanted to let out my despair and frustration. Thanks, guys. :good:
Long live the HD2. :silly:
Have you tried not using superwipe and using factory reset/wipe from 4ext recovery instead? Never had a problem with that.
Also I've never had to use the wire trick to have S-OFF. Gained it back when I was running GB, and still have it. Even after flashing OTA updates.
Sent from my HTC Sensation using xda developers app
nuron said:
Folks, I wouldn't call myself a n00b in flashing phones--I've been flashing ROMs since my HTC Wing so I feel like I have a decent amount of experience under my belt. But this Sensation...
From the start, performing S-OFF was tricky in itself, particularly with the paperclip trick. Miraculously, it worked after the third try. Flashing ROMs was a whole different monster. Even with 4ext, I could only flash THREE ROMs from the huge collection in the Development forum. And I honestly don't even know why--I kept on getting Error 0 for every build I tried to load. It was only through luck or magic that I was able to flash HyperNonsense, a MIUI build, and another one that I don't remember. Upgraded 4ext to latest version: nope. Changed SD card: nope. Different sequences of superwipe/no superwipe, clear dalvik, etc.: nope. I'm using HyperNonsense for now since it's pretty legit, but even then, I'm getting reboots all over the place. Stock kernel or different kernels--doesn't matter. I have a hunch it has to do with the bottom row of capacitive buttons running so hot.
Oh well, just holding out for the One X+ on T-Mobile or the next Nexus device. Just wanted to let out my despair and frustration. Thanks, guys. :good:
Long live the HD2. :silly:
Click to expand...
Click to collapse
It has nothing todo with the capacitive buttons running hot. Have you tried a different recovery like CWM because this seems like a recovery issue. As a side note, try disabling signature verification in 4EXT or better still, attempt to flash a ROM with aroma installer in and then save the aroma log and post it here
nuron said:
Folks, I wouldn't call myself a n00b in flashing phones--I've been flashing ROMs since my HTC Wing so I feel like I have a decent amount of experience under my belt. But this Sensation...
From the start, performing S-OFF was tricky in itself, particularly with the paperclip trick. Miraculously, it worked after the third try. Flashing ROMs was a whole different monster. Even with 4ext, I could only flash THREE ROMs from the huge collection in the Development forum. And I honestly don't even know why--I kept on getting Error 0 for every build I tried to load. It was only through luck or magic that I was able to flash HyperNonsense, a MIUI build, and another one that I don't remember. Upgraded 4ext to latest version: nope. Changed SD card: nope. Different sequences of superwipe/no superwipe, clear dalvik, etc.: nope. I'm using HyperNonsense for now since it's pretty legit, but even then, I'm getting reboots all over the place. Stock kernel or different kernels--doesn't matter. I have a hunch it has to do with the bottom row of capacitive buttons running so hot.
Oh well, just holding out for the One X+ on T-Mobile or the next Nexus device. Just wanted to let out my despair and frustration. Thanks, guys. :good:
Long live the HD2. :silly:
Click to expand...
Click to collapse
Post combat time. *Puts on Armor*
The wire trick is only necessary if you got screwed out of every other S-OFF method. I used Revolutionary and got S-OFF the day I rooted it. As for your ROM issues, that's pretty odd and unheard of to me. Try to flash one of those error 0 ROMs and Dump your recovery.log here after the flash, I'll look at it. As for the capacitive buttons, it's not the buttons running hot, but the fact that the CPU is literally right behind it. It doesn't run hot for me unless I start a game, and even that varies by ROM. Never gets hot on CM9. HyperNonSense 3.3 always runs hot though, no matter what. hyperNonSense 2.7 was the best :/
Anyway send in the recovery log, I'll try help you with that. PM me as well because I won't remember this thread after 5 minutes.
Thanks very much for all of your replies. I think I'll start with removing 4ext and run regular CWM. How would I go about uninstalling 4ext?
Hypernonsense always reboots for me
Sent from my Sensation using xda premium
nuron said:
Thanks very much for all of your replies. I think I'll start with removing 4ext and run regular CWM. How would I go about uninstalling 4ext?
Click to expand...
Click to collapse
just flash over it. Are you sure you're doing everything right? Have the right firmware for the right roms? Sounds like you're missing something
se1000 said:
just flash over it. Are you sure you're doing everything right? Have the right firmware for the right roms? Sounds like you're missing something
Click to expand...
Click to collapse
Seems like I am. I'm S-OFFed, and before 3.33 FW was required, I wasn't on it. When the cooks started requiring it, I flashed it. How important is Super CID? Will that cause an Error 0?
nuron said:
Seems like I am. I'm S-OFFed, and before 3.33 FW was required, I wasn't on it. When the cooks started requiring it, I flashed it. How important is Super CID? Will that cause an Error 0?
Click to expand...
Click to collapse
Your problem may be that you flashed the wrong FW for your CID - that is why superCID is important because it allows you to flash any variation of the firmware you like (you will have seen there are about 10+ variations of the 3.33 firmware)
So maybe try superCID (its really easy) then reflash the radio
fredcorp6 said:
Your problem may be that you flashed the wrong FW for your CID - that is why superCID is important because it allows you to flash any variation of the firmware you like (you will have seen there are about 10+ variations of the 3.33 firmware)
So maybe try superCID (its really easy) then reflash the radio
Click to expand...
Click to collapse
Yep, this.
It takes a couple of seconds to do, and is super easy.
Like fredcorp6 said, SuperCID will allow you to flash any RUU or firmware from any region.
Sent from my CM9 Stable Sensation using XDA Premium
Alright, so I just performed Super CID and was looking at this thread:
http://forum.xda-developers.com/showthread.php?t=1459767&highlight=3+33
I just flash 3.33 Universal?
nuron said:
Alright, so I just performed Super CID and was looking at this thread:
http://forum.xda-developers.com/showthread.php?t=1459767&highlight=3+33
I just flash 3.33 Universal?
Click to expand...
Click to collapse
I recommend 3.32 fw, flash in fastboot or bootloader can't remember which lol. I don't see any reason for 3.33 fw and 3.33 u can't do fastboot commands
Sent from my Sensation using xda app-developers app
nuron said:
Folks, I wouldn't call myself a n00b in flashing phones--I've been flashing ROMs since my HTC Wing so I feel like I have a decent amount of experience under my belt. But this Sensation...
Click to expand...
Click to collapse
Ever installed linux on a d-box2 (famous settop-box of a german pay-tv provider, anno 1999)? No? Well, shut up, with this thing you're SO happy seeing "u-boot" in the display and having it boot from your tftp server, which of course only works with a properly configured arpd and a dhcpd that speaks the ancient "bootp" ...
Haha, no offense For me, sensation was a piece of cake, didn't even need any hardware hacks, just a nice tool called "revolutionary"
Zirias said:
Ever installed linux on a d-box2 (famous settop-box of a german pay-tv provider, anno 1999)? No? Well, shut up, with this thing you're SO happy seeing "u-boot" in the display and having it boot from your tftp server, which of course only works with a properly configured arpd and a dhcpd that speaks the ancient "bootp" ...
Haha, no offense For me, sensation was a piece of cake, didn't even need any hardware hacks, just a nice tool called "revolutionary"
Click to expand...
Click to collapse
Shut up. No one cares about you. This isn't a one-up contest. With that kind of supposed knowledge, you should be helping others. But nope, you instead add nothing to the thread.
Thanks everyone for all the help so far. uml, I'll flash 3.32 and get back to you.
GazaIan said:
Post combat time. *Puts on Armor*
The wire trick is only necessary if you got screwed out of every other S-OFF method. I used Revolutionary and got S-OFF the day I rooted it. As for your ROM issues, that's pretty odd and unheard of to me. Try to flash one of those error 0 ROMs and Dump your recovery.log here after the flash, I'll look at it. As for the capacitive buttons, it's not the buttons running hot, but the fact that the CPU is literally right behind it. It doesn't run hot for me unless I start a game, and even that varies by ROM. Never gets hot on CM9. HyperNonSense 3.3 always runs hot though, no matter what. hyperNonSense 2.7 was the best :/
Anyway send in the recovery log, I'll try help you with that. PM me as well because I won't remember this thread after 5 minutes.
Click to expand...
Click to collapse
True! i never had to use paperclip to S-OFF mine. Both the official HTC method (on HTC website) AND the non-official method here on XDA worked for me to S-OFF my sensation.
I didn't mind the paperclip method too much. I think I needed to do it because my HBOOT was of a different version than the regular easy-to-root versions.
nuron said:
Just wanted to let out my despair and frustration.
Click to expand...
Click to collapse
nuron said:
Shut up. No one cares about you. This isn't a one-up contest. With that kind of supposed knowledge, you should be helping others. But nope, you instead add nothing to the thread.
Click to expand...
Click to collapse
So ... what actual "addition" were you hoping for? I don't think you'd start a thread like this if you didn't kind of enjoy the "hard way" you obviously took
btw -- whole point was to contradict your title by example, just to say: there are worse, much worse
Don't you understand that the Sensation is one of the most aggravating devices ever FOR ME?
This thread could be useful for other XDA members if they run into the same problems that I did and are searching for solutions. But instead, they have to to read through your useless posts. This clutters up the whole thread and detracts from all the members who have helped with a response and possible solution.
Leave.
nuron said:
Don't you understand that the Sensation is one of the most aggravating devices ever FOR ME?
This thread could be useful for other XDA members if they run into the same problems that I did and are searching for solutions. But instead, they have to to read through your useless posts. This clutters up the whole thread and detracts from all the members who have helped with a response and possible solution.
Leave.
Click to expand...
Click to collapse
There are a LOT of useful threads with lots of useful info here. This isn't one of them. Just re-read your original post and stop being such a moron, thanks.
wow, no ****, Sherlock. But I couldn't find an answer so that's why I created this thread. Thanks for not helping. And thanks for cluttering up this thread. Don't start calling others a moron without evaluating yourself first.
I've been running CM9 for a few weeks now, but have decided that I want to get S-Off and open the phone's capability up some more... Anyway, I'm on a MT4GS:
HBOOT 1.45.0013
Nov 21 2011 build
Tried flashing this https://www.cx.com/mycx/share/O2W61....00_11.16.3504.20_2_release_245247_signed.zip
from weekendsr2short's mirror page (http://forum.xda-developers.com/showthread.php?t=1878329) of Blue6ix's stuff...(i tried autoflashing from the bootload/fastboot screen)
anyway, it loads up like it is going to actaully flash, but nothing changes on the Bootloader screen. The phone is unlocked via HTC's tool and is rooted. Any help is greatly appreciated! Please lemme know if any more info is needed.
Josh
more to it than flashing an hboot
read up on THIS
SurfRodder said:
I've been running CM9 for a few weeks now, but have decided that I want to get S-Off and open the phone's capability up some more... Anyway, I'm on a MT4GS:
HBOOT 1.45.0013
Nov 21 2011 build
Tried flashing this https://www.cx.com/mycx/share/O2W61....00_11.16.3504.20_2_release_245247_signed.zip
from weekendsr2short's mirror page (http://forum.xda-developers.com/showthread.php?t=1878329) of Blue6ix's stuff...(i tried autoflashing from the bootload/fastboot screen)
anyway, it loads up like it is going to actaully flash, but nothing changes on the Bootloader screen. The phone is unlocked via HTC's tool and is rooted. Any help is greatly appreciated! Please lemme know if any more info is needed.
Josh
Click to expand...
Click to collapse
If you're rooted, install a stock-based ROM and then use juopunutbear.
blackknightavalon said:
If you're rooted, install a stock-based ROM and then use juopunutbear.
Click to expand...
Click to collapse
OK, that's what I was hoping to do. I noticed in the JB instructions that it said I must be a stock RUU not a custom ROM or something to that effect. I am on CWM 5.Something so a rom flash is NP. Any recommended ROMs? I.e One that worked for you? I tried the wire trick about 100 times over the course of an hour or so(on cm9.1), but then reread the bit shout the rom again.
Thanks for all the responses so far!
Any stock based ROM will do. I went with MikTouch myself and it worked like a charm! (on the 4th try so be patient....)
demkantor said:
more to it than flashing an hboot
read up on THIS
Click to expand...
Click to collapse
Thanks, after reading that thread <again> it linked me the this http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24
Which I have Also already read,but noticed this time that I cannot be unlocked via HTC and still flash pg59imgs... so im off to relock, if the stock rom method doesn't work...
WeekendsR2Short said:
Any stock based ROM will do. I went with MikTouch myself and it worked like a charm! (on the 4th try so be patient....)
Click to expand...
Click to collapse
Awesome, thanks brotha
well, one down, one to go. I have my phone all dialed in...now its time to fix my wife's... Thanks again Gents! (& Ladies, as applicable!)
edit: well, hers is done now... I ended up using another SD card, the original one I tried was kinda old, but the newer one I normally use worked on the 2nd try... didnt lose any data either... her sd card on the other hand was toasted and needed to be reformated... anyway, both phones are now S-Off!!
SurfRodder said:
well, one down, one to go. I have my phone all dialed in...now its time to fix my wife's... Thanks again Gents! (& Ladies, as applicable!)
edit: well, hers is done now... I ended up using another SD card, the original one I tried was kinda old, but the newer one I normally use worked on the 2nd try... didnt lose any data either... her sd card on the other hand was toasted and needed to be reformated... anyway, both phones are now S-Off!!
Click to expand...
Click to collapse
Man, that's GREAT! Once you knew HOW, the process was nothing for you. That's a far cry from most. Way to go!
WeekendsR2Short said:
Man, that's GREAT! Once you knew HOW, the process was nothing for you. That's a far cry from most. Way to go!
Click to expand...
Click to collapse
yeah, Ive been running root since my MT3G way back when...couldnt stand how laggy that thing was with all the bloat... wasnt even that great with CM6 but still night and day better than stock (=hooked on rooting). then upgraded to the MT4g and now this thing... was fairly concerned about all the extra hoops but wouldve just chosen another platform had I borked it...glad I didnt, saved me some funds!
On a related note, what radios are you guys running? Are there any issues between the GB radios and ICS ones? Im assuming so, but with the custom ROMs/kernels anything should be able to be overcome I'm hoping... I know I def. had issues on CM7 -> CM9 on the reg. 4G when swapping radios...
I don't generally swap my radios around since there are only two that I'm aware of. But I DID find that the new one (when I replaced my phone) seemed to lock a signal a bit quicker but for me the original radio gets MUCH better phone reception. Depends on your phone I suppose.
(you'll be glad you went with this phone though. basically a Sensation with a keyboard)
WeekendsR2Short said:
I don't generally swap my radios around since there are only two that I'm aware of. But I DID find that the new one (when I replaced my phone) seemed to lock a signal a bit quicker but for me the original radio gets MUCH better phone reception. Depends on your phone I suppose.
(you'll be glad you went with this phone though. basically a Sensation with a keyboard)
Click to expand...
Click to collapse
cool, I just flashed the older one today... been having really crappy recption on campus lately (esp. since switching from the MT4G) better reception is what I'd rather have... ill give this one a week or so and see if I think its any better... I like the phone a lot already... i still use the soft keyboard from time to time as I forget the other one is there, but it comes in really handy on certain sites...
Hello guys, I've been lurking the forums for hours trying to find a thread with an issue close to mine, and this is the closest I got. I followed all the necessary steps on the first page, but the problem I'm having is when I try to flash the PG59IMG.zip file, it says "Loading... PG59IMG.zip", but then it says "Checking....PG59IMG.zip" and afterwards it says "Wrong zipped image!" Any ideas what it could mean? I just want to get it back to stock. Any help is greatly appreciated.
THIS MAY HELP YOU
Thanks for the link. It said I need to relock the phone in order to flash the image, but when i type "fastboot oem lock" into command prompt, I get a message saying 'fastboot' is not recognized as an internal or external command, inoperable program or batch file." I'm guessing this means my fastboot wasn't set up correctly, but I don't know where to go from here. As always, thanks again for any help or advice.
The third post in this thread
http://forum.xda-developers.com/showthread.php?p=27796375
It was made for the g2 so don't use the drivers in it, but it will at least give you an idea of what to do
Sent from my HTC Vision using xda premium
Hanenbow said:
Thanks for the link. It said I need to relock the phone in order to flash the image, but when i type "fastboot oem lock" into command prompt, I get a message saying 'fastboot' is not recognized as an internal or external command, inoperable program or batch file." I'm guessing this means my fastboot wasn't set up correctly, but I don't know where to go from here. As always, thanks again for any help or advice.
Click to expand...
Click to collapse
Does fastboot work like this
./fastboot oem lock
On my PC some of my fastboot commands need that.
Sent from my Freaked out JellyBean
Thanks so much for your help guys. I followed the instructions on the pathing link, and the phone is currently flashing the image. I'll post a final time once I can confirm everything is fine.
So I have used TMOUS rom for ALONG time and recently decided to switch to use Cyanogen being a fan of it form other platforms.
While on the TMOUS rom I had 4g connectivity in my area about 90% of the time with the occasional drop into 3g here and there. It always displayed a 4g image in the top.
When I switched to Cyanogen that pretty much stoped. It always says 3g and is slow as hell. every once in awhile it will say H+ but not for long. MOST of the time it is constantly switching between 3g/4g/edge then shutting off.
Now im not sure if its a rom problem or not, but its making me want to switch back to a TMOUS rom.
Any suggestions would be great!
Edit: Just for clairification, I am S-On
I have this problem as well. I even ran the ruu back to stock and it is still happening. Please and thank you!
cp101 said:
I have this problem as well. I even ran the ruu back to stock and it is still happening. Please and thank you!
Click to expand...
Click to collapse
Damn, this scares me.... any solution anyone?
I'm thinking it might be a hardware error at this point. I might just "lose my phone" or just flash to stock and return it, this is preposterous.
cp101 said:
I'm thinking it might be a hardware error at this point. I might just "lose my phone" or just flash to stock and return it, this is preposterous.
Click to expand...
Click to collapse
Unfortunately, it doesn't seem to be a hardware problem
I have been trolling the net for weeks but have not found a solution yet.
I've posted in threads here but no solution.....
My issues started when I went to CM ROM - I used to have great 4g all the time before I went to custom rom (I was on stock TMO US) .. Now no matter what I do, I am not able to get 4G again.... it's really irritating...
I've tried a bunch of custom ROMS.. I am on 1.13 HBOOT and S-ON .. .. CID = HTC__001 (originally my CID was stock TMO US CID whatever that is but now its not that.. I don't wan to run RUU because I don't have TMO US CID and dont want to brick my phone)
You can set your CID back easily with the All in One ToolKit found here.http://www.hasoon2000.info/getdownload.php?file=One%20S/One_S_All-In-One_Kit_v4.0.rar
That is not the problem, unfortunately. It just doesn't make much sense, whatever the problem is; and especially considering after a full RUU restock. That has always fixed whatever mess I have created in the past.
This rom should fix your problem. Dont forget to clear storage from bootloader. It will erase everything thoug. And follow the steps under show contents link.
http://forum.xda-developers.com/showthread.php?t=2250573
cp101 said:
You can set your CID back easily with the All in One ToolKit found here.http://www.hasoon2000.info/getdownload.php?file=One%20S/One_S_All-In-One_Kit_v4.0.rar
That is not the problem, unfortunately. It just doesn't make much sense, whatever the problem is; and especially considering after a full RUU restock. That has always fixed whatever mess I have created in the past.
Click to expand...
Click to collapse
I not sure if its a CID problem. The only thing I ever did was upgrade to the newest Hboot and load in the CM rom. even going back to the TMOUS rom does not fix the problem.
Its so bad, and never on 4g that im considering getting a new phone.
bnd10706 said:
I not sure if its a CID problem. The only thing I ever did was upgrade to the newest Hboot and load in the CM rom. even going back to the TMOUS rom does not fix the problem.
Its so bad, and never on 4g that im considering getting a new phone.
Click to expand...
Click to collapse
I'm in the same boat, friend. I've tried literally everything suggested, I'm just wondering what exactly happened in the flashing of the Maximus rom. The worst part being is that I GET 3g/H and then it drops back to E. It's so strange. The only thing I've not done is contact Tmobile about it, and i highly doubt that they would throttle my bandwidth without contacting me in some form or fashion.
cp101 said:
I'm in the same boat, friend. I've tried literally everything suggested, I'm just wondering what exactly happened in the flashing of the Maximus rom. The worst part being is that I GET 3g/H and then it drops back to E. It's so strange. The only thing I've not done is contact Tmobile about it, and i highly doubt that they would throttle my bandwidth without contacting me in some form or fashion.
Click to expand...
Click to collapse
my phone is still under warrenty. Im wondering if i am able to revert back to stock without them knowing if I can get a phone replacement.
From what I've read, it's doable; even with an unlocked phone. But I'd really like to know what in the dev's source code made this happen... it's a bit ridiculous.
jenenser83 said:
This rom should fix your problem. Dont forget to clear storage from bootloader. It will erase everything thoug. And follow the steps under show contents link.
http://forum.xda-developers.com/showthread.php?t=2250573
Click to expand...
Click to collapse
I just wanted to say, that I did this and it worked!
I did this the first time, but i just flashed the rom with a full wipe.
This time what I did was go into TWRP and erased everything....and I mean everything except TWRP.
After that i flashed the rom and boot.img and everything works great. 4g all the time again!
Sucks that im back on an older version of jellybean, but oh well
bnd10706 said:
I just wanted to say, that I did this and it worked!
I did this the first time, but i just flashed the rom with a full wipe.
This time what I did was go into TWRP and erased everything....and I mean everything except TWRP.
After that i flashed the rom and boot.img and everything works great. 4g all the time again!
Sucks that im back on an older version of jellybean, but oh well
Click to expand...
Click to collapse
Can you take me through the steps you took to achieve all of this? Thanks.
cp101 said:
Can you take me through the steps you took to achieve all of this? Thanks.
Click to expand...
Click to collapse
So what I did first was go into TWRP and selected wipe. Inside wipe i selected EVERYTHING, every little box. Then Wiped it.
This left nothing on the phone but the recovery. I then loaded on SuperSU from TWRP. I download the stock TMOUS rom that was posted earlier in this post.
In TWRP I mounted it and hooked it to computer and transfered the rom over.
Once the rom was on I did the install of the rom.
I rebooted the rom into bootloader.
Once in bootloader i put it into fastboot.
I had previous extracted the boot.img from the rom.
I sent the boot.img over via fastboot which restarted the phone.
Once it got all started up. No issues. I am on 4g 99% of the time now.
Im thinking the issue was definatly based in the CM rom.
Since this worked I wanted to test things out since my phone was pretty much stripped of everything.
I tried out Viper rom and a couple of other non CM based roms, and I have had no issues.
IM back on teh TMOUS rom though. Wifi calling will win over when i go overseas.
Thanks, but it did not work for me. It is a hardware issue on mine. Thanks again
cp101 said:
Thanks, but it did not work for me. It is a hardware issue on mine. Thanks again
Click to expand...
Click to collapse
Must be.
I did find something out though doing all my research. Did you ever at any point update the radio? TMobile uses some frequencies that some companies dont use.
It is my understanding that some of these roms are packed with radios that are generic and thus ment for multi carriers.
Not sure if thats your issue, but might want to look into.
Its nice being back on 4g though.
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