I have an HTC Aria and about 6 Months ago I let a friend attempt to Hack it. He gave up pretty fast and I didn't have any issues until the android 2.2 ROM Update came out for the phone.
The issues I am having is that the Phone thinks it is a Liberty something rather and not an HTC Aria. This is preventing me from doing the factory updates.
Any suggestions on how to restore my phone and OS to factory settings?
Thanks,
Ryan
rpkiel said:
I have an HTC Aria and about 6 Months ago I let a friend attempt to Hack it. He gave up pretty fast and I didn't have any issues until the android 2.2 ROM Update came out for the phone.
The issues I am having is that the Phone thinks it is a Liberty something rather and not an HTC Aria. This is preventing me from doing the factory updates.
Any suggestions on how to restore my phone and OS to factory settings?
Thanks,
Ryan
Click to expand...
Click to collapse
Ryan,
Please see the Aria Superthread. Instructions for multiple restorations are there.
rpkiel said:
I have an HTC Aria and about 6 Months ago I let a friend attempt to Hack it. He gave up pretty fast and I didn't have any issues until the android 2.2 ROM Update came out for the phone.
The issues I am having is that the Phone thinks it is a Liberty something rather and not an HTC Aria. This is preventing me from doing the factory updates.
Any suggestions on how to restore my phone and OS to factory settings?
Thanks,
Ryan
Click to expand...
Click to collapse
Also, the phone IS a Liberty. Thats the universal HTC name for it. Aria/Intruder/Gratia are just the consumer/branding names. All are technically the Liberty.
Related
I flashed a custom rom to an HTC ARIA. After working w/ it for a short period I realized it would work for the users needs. I odined back to stock then flashed Froyo 2.2. It works well except for one major issue. At the end of a phone call, the screen/phone seems to freeze. When the phone switches to "black screen mode" (during conversation) it doesn't switch back to screen on and the power button doesn't wake it up. The only way to wake the phone up is by removing the battery.
I've searched the web and XDA but I don't even know how to phrase this as a question!
tomween1 said:
I flashed a custom rom to an HTC ARIA. After working w/ it for a short period I realized it would work for the users needs. I odined back to stock then flashed Froyo 2.2. It works well except for one major issue. At the end of a phone call, the screen/phone seems to freeze. When the phone switches to "black screen mode" (during conversation) it doesn't switch back to screen on and the power button doesn't wake it up. The only way to wake the phone up is by removing the battery.
I've searched the web and XDA but I don't even know how to phrase this as a question!
Click to expand...
Click to collapse
So just to be clear, you now have a Aria that has the official HTC Froyo 2.2 ROM installed, correct? The symptom would point to faulty proximity sensor.
First thing I would try would be a hard reset. Here is a reference:
http://community.htc.com/na/htc-forums/android/f/96/t/3451.aspx
If the problem still exists, you may want to consider it a hardware problem and take it back to AT&T.
tpbklake said:
First thing I would try would be a hard reset. Here is a reference:
http://community.htc.com/na/htc-forums/android/f/96/t/3451.aspx
Click to expand...
Click to collapse
Yes it is the official HTC 2.2. This issue didn't exist prior to the install
tomween1 said:
Yes it is the official HTC 2.2. This issue didn't exist prior to the install
Click to expand...
Click to collapse
So have you tried a hard reset as suggested? If that didn't work, you might want to run the Froyo 2.2 RUU again and reflash the image.
Since it is an official AT&T update, you should be able to call AT&T and report the issue.
tpbklake said:
So have you tried a hard reset as suggested
Click to expand...
Click to collapse
No, sorry, could you run these steps by me?
tomween1 said:
No, sorry, could you run these steps by me?
Click to expand...
Click to collapse
I posted a link in my original response. Dude I'm trying to give you the benefit of the doubt, but I must admit some of the issues and questions you have been posting in the Aria forums almost sound like you are trolling...
tpbklake said:
I posted a link in my original response. Dude I'm trying to give you the benefit of the doubt, but I must admit some of the issues and questions you have been posting in the Aria forums almost sound like you are trolling...
Click to expand...
Click to collapse
Please stop w/ the "trolling" thing I am not! I am having legitimate issues. Thank you for the link, I did miss that.
I have completed the hard reset, this hasn't fixed the issue.
tomween1 said:
Please stop w/ the "trolling" thing I am not! I am having legitimate issues. Thank you for the link, I did miss that.
I have completed the hard reset, this hasn't fixed the issue.
Click to expand...
Click to collapse
OK, hard reset didn't work and since you are on the official AT&T Froyo update, you don't have a lot of options to try, since that version is unrootable at this time.
Option 1 is to re-run the Froyo 2.2 RUU update just to make sure you have a good flash.
Option 2 is to call AT&T and report the issue. Although the proximity sensor is hardware and it is acting like a hardware issue, it could well be a software issue with the new ROM.
tpbklake said:
OK, hard reset didn't work and since you are on the official AT&T Froyo update, you don't have a lot of options to try, since that version is unrootable at this time.
Option 1 is to re-run the Froyo 2.2 RUU update just to make sure you have a good flash.
Option 2 is to call AT&T and report the issue. Although the proximity sensor is hardware and it is acting like a hardware issue, it could well be a software issue with the new ROM.
Click to expand...
Click to collapse
OK before I go to AT&T w/ the problem, would I just run the HTC sync to upgrade to 2.2 again? Basically flashing 2.2 over itself?
tomween1 said:
OK before I go to AT&T w/ the problem, would I just run the HTC sync to upgrade to 2.2 again? Basically flashing 2.2 over itself?
Click to expand...
Click to collapse
Yes, you would be reflashing the 2.2 upgrade over itself.
tpbklake said:
Yes, you would be reflashing the 2.2 upgrade over itself.
Click to expand...
Click to collapse
I'll give that a try, thank you.
Ive just about had it with the resets like crazy ive had this tbolt for more then 30 days i know thats way pass the 14-day mark but im just curious would they let me exchange it out for a different android device just curious
Have you considered you have a bad device? Maybe you should exchange it first? (got another tb I mean).
I would say try and get a different thunderbolt. I don't know if they do this yet but back in the day when I was rocking the blackberry your. I had about 3 your replacements that were "bad" and finally offered me the bold. I think you need to go threw 3 device or more of the same and then they will let you get something else
Sent from my ADR6400L using Tapatalk
i was thinking about getting it replaced with another tbolt just fear i may get another in the same manner in which mine is in... ive did hard resets till i was blue in the face- pulled the battery tons of times... i want to love this device but just isnt flowing right
for me my motorola droid was the champ compared to this wish i didnt sell it now
Are you rooted? Did you flash any radios?
Sent from Verizon in Phoenix, AZ, running a rooted Thunderbolt, with Lightning Rom v3.3.1 / Adrynalyne 4.4.3
yes i was rooted at one time and yes i did flash the new radio but ive reverted back to out of box stock un-rooted with s-on stock kernel and radio -
Ive had mine a month, rooted and running bamf. No problems. Have 4g when im in 4g area. U may have a bad device
Sent from my ADR6400L using XDA App
cjmcmillion said:
yes i was rooted at one time and yes i did flash the new radio but ive reverted back to out of box stock un-rooted with s-on stock kernel and radio -
Click to expand...
Click to collapse
Have you experienced any more reboots?
Sent from Verizon in Phoenix, AZ, running a rooted Thunderbolt, with Lightning Rom v3.3.1 / Adrynalyne 4.4.3
Sounds like you just have a bad device. I'm rooted running BAMF 1.6 and the newest radio. I've never had a reboot.
Hello!
I got a new Thunderbolt a little over a week ago. I rooted it using Revolutionary v0.4pre4 and then flashed the newest versions of Imoseyon's leanKernel and CM7. It wasn't until afterwards that I attempted to make a phone call and discovered that Verizon couldn't authenticate my account. (Cause Code 97) Long story short, I ended up reverting back to stock Sense and getting a new authentication key after almost a week (the first tech I talked to didn't give me one). I would like to try CM7 and leanKernel again, but am extremely green with smartphones and am not sure how to diagnose which part of the process messed up my key. I really can't afford more downtime at the moment.
My question is: Could CM7 or leanKernel have caused my AKey problem? Has anyone else had the same experience with this ROM/kernel? (google only turns up one example of a CM7 user experiencing this problem)
I believe I heard it's possible for the phone to come that way from the store, and suspect rooting with Revolutionary could also have been the culprit. I would love to lay my fears to rest however (or confirm them I guess) before I give it another go.
Thank you guys in advance!
swod_woosh said:
Hello!
I got a new Thunderbolt a little over a week ago. I rooted it using Revolutionary v0.4pre4 and then flashed the newest versions of Imoseyon's leanKernel and CM7. It wasn't until afterwards that I attempted to make a phone call and discovered that Verizon couldn't authenticate my account. (Cause Code 97) Long story short, I ended up reverting back to stock Sense and getting a new authentication key after almost a week (the first tech I talked to didn't give me one). I would like to try CM7 and leanKernel again, but am extremely green with smartphones and am not sure how to diagnose which part of the process messed up my key. I really can't afford more downtime at the moment.
My question is: Could CM7 or leanKernel have caused my AKey problem? Has anyone else had the same experience with this ROM/kernel? (google only turns up one example of a CM7 user experiencing this problem)
I believe I heard it's possible for the phone to come that way from the store, and suspect rooting with Revolutionary could also have been the culprit. I would love to lay my fears to rest however (or confirm them I guess) before I give it another go.
Thank you guys in advance!
Click to expand...
Click to collapse
Learn ADB and use it to root. The easy way is not always the best way.
Sent from my Synergized Thunderbolt via XDA Premium App
Hey guys. Little new to the TBolt crew here.
I've been rooting for a bit. Did an HTC Hero, a DROID Eric, an Incredible... Now I've got a TBolt sitting here that I just rooted about an hour ago. It was running 4G just fine both before and after the root, but after installing a CM7 ROM (SFK's to be precise) I haven't seen 4G pop up since. I've tried a couple other CM7 roms, but nothing seems to make a difference - it only runs on 3G.
I was thinking it might be a radio problem, but admittedly I'm pretty novice with this stuff. I just flash what sounds interesting, and if it's not as stable as I'd like I find something else to flash. Does anyone have any ideas what's wrong? And what I can download to fix it?
EDIT: After giving up and deciding to go back to my backup of "stock" that I'd just made... now it's failing to properly back up. This wonderful error about data being corrupted with the only button available being "I'm Feeling Lucky" and still no 4G, only 3G. Now I'm at a complete loss.
I have a Nexus sitting next to me clearly connected to 4G just fine, so I know it's not a network issue. What the heck is going on here?
I'm sure you have, but never know... have you checked your wireless network settings?
Settings--Wireless & Networks--Mobile Networks--Network Mode.
Make sure LTE/CDMA is selected.
Sent from my ADR6400L using xda premium
most roms are built with a specific radio in mind i would try to flash one of the newer radios they work better drain less battery and are more compatible with rooted roms.
So, several months back, I rooted this phone. Then, an OTA came over and I stupidly installed it. BIG MISTAKE! Anyways, then, my wifi stopped working. I was instructed to find a sense rom and install it and that should take care of my wifi issue.
Well, after installing the Butterz rom (I forgot about this and just put the phone away since I got a Samsung now which is actually horrible) and after installing it, the problem still exists.
So, I was wondering if anyone had the original htc evo 3d rom that the phone came with. I wanted to install it from scratch and see if that takes care of the issue. If it does, I'll start using my evo 3d once again.
There is more than one stickied thread in here with exactly what you are asking for and other sites just for that.
www.shipped-roms.com/?category=android
http://d-h.st/users/mpgrimm2/?fld_id=6800#files
Sent from my dirty unicorn 3VO