I havent used my aria in almost a year now but decided to pull it out as a backup phone. I was rooted at one point but i think i did and ota update while i was rooted. Since I quit using the phone I formatted the sd card for it. I went to use the phone and it just boots up into recovery. I try installing Cm7 and a few other roms and they dont work. CM7 just sits on their loading screen the whole time. I looked at the HBoot screen and it says S-on. I cannot figure out how to get passed any of this at all. Is my phone pretty much done?
1) Use Revolutionary to obtain S-OFF. Follow all the directions from the site.
2) Use this method to install and/or update Clockworkmod Recovery. The latest version of CWM for Aria is here, though older versions should work fine also.
3) Flash ROM.
I know how to make it have s-off but those are applications for the computer and my phone wont connect to the computer since it only boots to recovery.
Sent from my Desire HD using XDA App
It looks like my usb port isn't working. My computer says it malfunctioned.
After the tenth time installing cm7 it started. I went back into recovery to install the Google apps but then it wouldn't start again. And now after another attempt at re installing it doesn't work.
Sent from my Desire HD using XDA App
What version of CWM do you have right now? Also, what is your HBOOT version? (if you can get to that screen)
Hboot says 0.57? Not sure if that's right and cwm is 2.5.0.1
Sent from my Desire HD using XDA App
Try installing the official AT&T 2.2.2 ROM using the alternative method that I've explained in this post: http://forum.xda-developers.com/showpost.php?p=18541475&postcount=145 . This method does not require using the USB connection at all so it might solve your problem.
It will overwrite CWM, but you can go through the S-OFF process to install CWM afterward.
The phone keeps aborting the installation of the Android 2.2.
Sent from my Desire HD using XDA App
pmariolo said:
The phone keeps aborting the installation of the Android 2.2.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Try using the RUU directly (while in fastboot).
pmariolo said:
The phone keeps aborting the installation of the Android 2.2.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Is there an error message?
Error message is can't open /sdcard/HTC_ aria....update.zip (bad)
Sent from my Desire HD using XDA App
Also I can't do anything in fastboot unless I'm doing it wrong.
Sent from my Desire HD using XDA App
pmariolo said:
Error message is can't open /sdcard/HTC_ aria....update.zip (bad)
Click to expand...
Click to collapse
You aren't following the directions from the post I linked to, please re-read them. You don't install the update through Clockworkmod.
Try this method as well as the method Theonew is telling you to do. One of them should work.
pmariolo said:
Also I can't do anything in fastboot unless I'm doing it wrong.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Download the RUU from here: http://www.htc.com/us/support/aria-att/downloads/ (link is under "HTC Aria ™ for AT&T Android 2.2 ROM Update | 02.25.2011"). After that, boot your device into fastboot, connect it to your PC and run the RUU.
Ohhh I got it. I'll try it in.a couple hours. I understand what it was saying I just for some reason wasn't doing it right.
Sent from my Desire HD using XDA App
Hey guys thanks a lot it worked!
Related
I have a MoPho with unlocked bootloader running 2.3.4 and everytime I try to flash back to my saved stock backup from any custom rom I keep getting an "error while flashing boot image" I tried to do an advanced restore and picked the files one at a time but I keep getting the same result. Can someone please help, thank you in advance...
Sent from my MB855 using xda app-developers app
Are you restoring using the same utility you did the nandroid backup with? Joker recovery vs twrp vs cwm recovery
Sent from my MB855 using Tapatalk 2
I created the back up using cwm and trying to restore through cwm...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
I created the back up using cwm and trying to restore through cwm...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Are you using a working recovery? Jokers? Twrp? Photon3? Or the ROM manager one? ROM manager version does not work.
Sent from my MB853 using XDA
As far as I know, I am using Clockworkmod Recovery v5.0.2.8. I've tried Rom Manager but I usually get an error while trying to perform a NANDroid backup...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
As far as I know, I am using Clockworkmod Recovery v5.0.2.8. I've tried Rom Manager but I usually get an error while trying to perform a NANDroid backup...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
as mentioned previously the ROM Manager one DOES NOT WORK. 5.0.2.8 DOES NOT WORK! you NEED to user Jokers, TWRP or the 5.0.2.7-photon3 recoveries ONLY. you can find the working recoveries on my site. choose which one suits you best! don't use Jokers V4 because it won't flash google apps properly.
http://www.motosunfire.com/clockworkmod-recovery/
Ok thanks a lot, I will try the two you just recommended...
Sent from my MB855 using xda app-developers app
OK I downloaded the TWRP recovery you had suggested, I backed up my current from but when I tried to restore a different from I keep getting an error "the process com.android.phone has stopped working" and I have no service now...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
OK I downloaded the TWRP recovery you had suggested, I backed up my current from but when I tried to restore a different from I keep getting an error "the process com.android.phone has stopped working" and I have no service now...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
alright? well that doesn't say alot? as you could be using any one of 20 different ROMs. which are you using?
na7q said:
alright? well that doesn't say alot? as you could be using any one of 20 different ROMs. which are you using?
Click to expand...
Click to collapse
I am running cm7, or rather was running cm7 coz now my phone is stuck in the boot loop limbo. Kept getting the error "com.android.phone stopped working" and I was unable to make or receive calls all day. So I thought relocking and unlocking the bootloader would do the trick but now I'm stuck on a rock and a hard place. Sssoooooo, do you have any tricks up your sleeves I could use, I would really appreciate it...
I've been able to run a hand full of fastboot commands to bring my phone back out of limbo, I am past the boot image and able to activate with the sprint network. Thank you all who took the liberty of viewing my post, I appreciate the help...
Stray2thaB said:
I am running cm7, or rather was running cm7 coz now my phone is stuck in the boot loop limbo. Kept getting the error "com.android.phone stopped working" and I was unable to make or receive calls all day. So I thought relocking and unlocking the bootloader would do the trick but now I'm stuck on a rock and a hard place. Sssoooooo, do you have any tricks up your sleeves I could use, I would really appreciate it...
Click to expand...
Click to collapse
Stray2thaB said:
I've been able to run a hand full of fastboot commands to bring my phone back out of limbo, I am past the boot image and able to activate with the sprint network. Thank you all who took the liberty of viewing my post, I appreciate the help...
Click to expand...
Click to collapse
hmmm... CDMA user? or GSM? i remember that bug being around in the very early builds of CM7. are you on the latest nightly or stable release?
i might also recommend changing some build prop info (which could be causing this?) to make sure it tells the radio to operate in the correct mode. gsm or cdma. if you look for ro.telophony.default_network=? the ? should be a 4 for CDMA or a 7 for GSM. change to your liking. then reboot. this was an issue in CM9 for the longest time and this is how it was resolved. it's possible it could be the same for CM7.
another option is to of course start over. wipe the cache,data,system partitions, possibly even twice. flash cm7. twice to be safe. then gapps. twice to be safe. then give it another shot.
other than that it might be a bad download or a bad build. so try another if it doesn't work. hope this helps you!
CDMA user, for now I am able to have my phone back on, but I will probably steer away from CM7 AND perhaps try CM10. All I keep finding is an unofficial release, is this the only one there is?
Sent from my MB855 using xda app-developers app
Stray2thaB said:
CDMA user, for now I am able to have my phone back on, but I will probably steer away from CM7 AND perhaps try CM10. All I keep finding is an unofficial release, is this the only one there is?
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
there will never be any officials releases unless somehow Motorola decides they want to give us drivers/source for ICS or JB. which is never. unless we get a leak.
I had some issues with various roms for unknown reasons, so I kept trying out new roms. Well the problem persisted, and as I was attempting to flash a new Rom, recovery just kind of failed. Whenever I attempt to enter recovery, a titled triangle with and exclamation mark and a droid figure pop up and I have to do a battery wipe. My phone still starts and runs, but I'm currently stuck on a problematic rom with no way of getting to recovery. I'm fairly new to all of this so I have no idea what's happening and I'm ultimately scared of attempting anything and messing up more. So any and all suggestions are beyond welcome.
FoxMarsden said:
I had some issues with various roms for unknown reasons, so I kept trying out new roms. Well the problem persisted, and as I was attempting to flash a new Rom, recovery just kind of failed. Whenever I attempt to enter recovery, a titled triangle with and exclamation mark and a droid figure pop up and I have to do a battery wipe. My phone still starts and runs, but I'm currently stuck on a problematic rom with no way of getting to recovery. I'm fairly new to all of this so I have no idea what's happening and I'm ultimately scared of attempting anything and messing up more. So any and all suggestions are beyond welcome.
Click to expand...
Click to collapse
Have you tried reinstalling CWM?? Or maybe using another recovery....
I had that to after updating to 236 first time had to install recovery couple times to get it to work.
Sent from my HTC One X+ using xda premium
Complication in my situation : I don't have a computer. I can get to one with the needed programs on it, but are you sure this will fix it?
I had that to after updating to 236 first time had to install recovery couple times to get it to work.<br />
<br />
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
So just install cwm multiple times..? Like install it, turn phone on, then install again if problem persists or isn't fixed immediately?
You're looking for some magical recipe that will 100% surely fix your phone. There isn't one. You will just have to play and be creative. You can report back here for more advice if needed.
FoxMarsden said:
So just install cwm multiple times..? Like install it, turn phone on, then install again if problem persists or isn't fixed immediately?
Click to expand...
Click to collapse
Like what ravilov mentioned, its more of a trial and error process and not a 100% quick fix. Not having a computer will make things much more difficult.
I'm not looking for a magic easy route, (though it'd be nice if there was one), I'm just asking for literally any advice on the situation.
Use the android sdk 'fastboot' command to push recovery to the device via USB. This should solve your issue with a borked recovery partition.
Sent from my MB860 using Tapatalk 2
Try ROM manager and install cwm with it free on market install it a few times it will work
Sent from my HTC One X+ using xda premium
markwoo said:
Try ROM manager and install cwm with it free on market install it a few times it will work
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
How do I install cwm on it? I have an idea but I don't want to mess up anymore than I already have
FoxMarsden said:
How do I install cwm on it? I have an idea but I don't want to mess up anymore than I already have
Click to expand...
Click to collapse
In rom manager just follow the prompts.
Sent from my MB860 using Tapatalk 2
jjwatmyself said:
In rom manager just follow the prompts.
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
Should I do Clockwork Mod Touch, or just cwm recovery?
FoxMarsden said:
Should I do Clockwork Mod Touch, or just cwm recovery?
Click to expand...
Click to collapse
No need for touch. If you ever damage your screen, touch recovery will make it impossible to use. Once you've flashed it with rom manager, you can download th3bill's recovery for Atrix and install over the top of it.
Sent from my MB860 using Tapatalk 2
Thanks man, I got it all fixed yesterday and everything is running fine. Thanks for all your help
So yesterday I tried flashing this tweak on my HTC One. Sadly it crashed my phone somehow and I ended up wiping the phone, and now it's telling me each time I reboot that it has no OS. I decided to try to flash stock Sense 5, but I realized I don't have a backup or anything. I've been trying to use Android File Transfer to make the OS available in recovery. Sadly it seems when it's on recovery I can't use file transferring. I would turn it on, but it won't boot any further than the "HTC Quietly Brilliant" loading screen.
Anyone have any ways I can get the OS back on the phone? Please help!
parkerfriend said:
So yesterday I tried flashing this tweak on my HTC One. Sadly it crashed my phone somehow and I ended up wiping the phone, and now it's telling me each time I reboot that it has no OS. I decided to try to flash stock Sense 5, but I realized I don't have a backup or anything. I've been trying to use Android File Transfer to make the OS available in recovery. Sadly it seems when it's on recovery I can't use file transferring. I would turn it on, but it won't boot any further than the "HTC Quietly Brilliant" loading screen.
Anyone have any ways I can get the OS back on the phone? Please help!
Click to expand...
Click to collapse
Are you using TWRP? Cause I've been wondering the same thing lately.
Sent from my HTC One using xda app-developers app
whitetiger_0603 said:
Are you using TWRP? Cause I've been wondering the same thing lately.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
So I figured out how to fix it- using adb I sent stock Sense back to my phone and flashed it, worked like a charm.
parkerfriend said:
So I figured out how to fix it- using adb I sent stock Sense back to my phone and flashed it, worked like a charm.
Click to expand...
Click to collapse
What command did you use?
Sent from my HTC One using xda app-developers app
whitetiger_0603 said:
What command did you use?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
adb push %PATH TO BE PUSHED% %PATH WHERE TO BE PUSHED%
Sent from my HTC One
GermanGuy said:
adb push %PATH TO BE PUSHED% %PATH WHERE TO BE PUSHED%
Sent from my HTC One
Click to expand...
Click to collapse
Haha thanks. I was dumb and didn't think of the command used in SuperCID until right before you posted this.
Sent from my HTC One using xda app-developers app
So I was flashing a unofficial CM9 on my phone and everything went without problems. But after the reboot I get a black screen after the HTC logo.
I can still go to fastboot menu and CWM. And factory reset didn't help.
Hopefully you can help me
You need to flash Kernel for CM on your phone to make it work. Read OP in the Rom Thread for instructions.
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
You need to flash Kernel for CM on your phone to make it work. Read OP in the Rom Thread for instructions.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
But now I have done a factory reset,I don't really need CM9 anymore,but it still gives a black screen,I just want only that away.
Flash a new rom.
oddoneout said:
Flash a new rom.
Click to expand...
Click to collapse
Is there then a way to connect my phone with usb to my PC? (Because my micro sd card slot on my pc is dead)
Use a usb cable...?
oddoneout said:
Use a usb cable...?
Click to expand...
Click to collapse
But my PC doesn't recognize the phone.
Install HTC drivers:
http://forum.xda-developers.com/showthread.php?t=2217396
oddoneout said:
Install HTC drivers:
http://forum.xda-developers.com/showthread.php?t=2217396
Click to expand...
Click to collapse
I already have them.
Then reinstall them.
Are you on Windows 8?
Also try a sd card mounting app such as Multi Mount
oddoneout said:
Then reinstall them.
Are you on Windows 8?
Click to expand...
Click to collapse
Yes I am
EDIT:It's hard to use apps when your phone is bricked...
Ok I found a way to flash the new rom but I have still the same problem. Everytime when the boots up I get the HTC logo with a sentence that says:
'This build is for development purposes only. Do not distribute outside of HTC without HTC's permission. Failure may lead to legal action' or something like that,it's going way to fast.
And after that I get the black screen,but there i can also use the button combination to go to the fastboot menu.
You need to install a sense kernel. Just choose one yourself or use stock kernel. The message about development purposes is normal, we all have it. Without S-Off we can't get it away.
dansou901 said:
The message about development purposes is normal, we all have it. Without S-Off we can't get it away.
Click to expand...
Click to collapse
Yes we can.... And I'm pretty sure you can change it to another animation (it was either in prototype or Fulmix kernel)
Sent from my HTC Desire X using Tapatalk
What you mean, is an additional splash screen shown after the HTC logo and before the boot animation...
And I don't need to wipe or flash another ROM? (I'm currently using Half Sense ROM now)
No, as long as you just install the right kernel, it should boot, but be sure to have the ROM installed correctly.
Today my DNA said the Wi-Fi was "turning on" and it just hangs there. It never actually turns on or connects to a wireless network. I have tried rebooting the phone, shutdown, using airplane mode, etc. Even did a factory reset and it's still doing the same thing.
I tried "WiFi fixer" from the Play Store, that didn't help either.
Phone has always been stock, no root.
Any suggestions?
Turn off fastboot and reboot. Then see if it works. If not only option might be to restore to factory settings.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
Turn off fastboot and reboot. Then see if it works. If not only option might be to restore to factory settings.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried turning off fast boot but I will try it again.
Already did a factory reset. I'm on the stock Android version as we speak.
Did you try performing an ruu of the current version you are on?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
Did you try performing an ruu of the current version you are on?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No I have not. I've yet to dive into Rooting and different ROMs on smartphones.
Got a link?
shortstop20 said:
No I have not. I've yet to dive into Rooting and different ROMs on smartphones.
Got a link?
Click to expand...
Click to collapse
The ruu won't root or put a custom rom on your phone. The ruu will erase your phone completely and put it back to the way it came out of the box on the stock rom. In your case it will be the newest update that's the ruu I suggest using. It's very easy to do just follow the instructions on the computer screen. Hopefully it can fix the issue if it doesn't it probably hardware related and if that's the case and your within your one year warranty try and get a replacement. But we can cross that bridge when we get there. For now get the newest ruu which is 3.0.6 I believe from here.
https://drive.google.com/file/d/0B32gqnbh2ZecYTlvV1dlZTVRS0E/preview?pli=1
That is the direct download link. The ruu needs to be run on a Windows computer I recommend Windows 7 and have the phones drivers installed for it to work properly.
This is the thread where it's located on xda.
http://forum.xda-developers.com/showthread.php?t=2612740
If you have any questions feel free to direct message me or reply within this thread.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
The ruu won't root or put a custom rom on your phone. The ruu will erase your phone completely and put it back to the way it came out of the box on the stock rom. In your case it will be the newest update that's the ruu I suggest using. It's very easy to do just follow the instructions on the computer screen. Hopefully it can fix the issue if it doesn't it probably hardware related and if that's the case and your within your one year warranty try and get a replacement. But we can cross that bridge when we get there. For now get the newest ruu which is 3.0.6 I believe from here.
https://drive.google.com/file/d/0B32gqnbh2ZecYTlvV1dlZTVRS0E/preview?pli=1
That is the direct download link. The ruu needs to be run on a Windows computer I recommend Windows 7 and have the phones drivers installed for it to work properly.
This is the thread where it's located on xda.
http://forum.xda-developers.com/showthread.php?t=2612740
If you have any questions feel free to direct message me or reply within this thread.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can't get the CLI commands to run. I installed the Android SDK. Is there something else I need to do? I'm in "Fastboot USB" mode.
shortstop20 said:
I can't get the CLI commands to run. I installed the Android SDK. Is there something else I need to do? I'm in "Fastboot USB" mode.
Click to expand...
Click to collapse
Is there a specific error that the ruu gives. I'm not familiar with what your referring to. Did you follow instructions in the thread I linked? Are your drivers installed for your phone?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
shortstop20 said:
I can't get the CLI commands to run. I installed the Android SDK. Is there something else I need to do? I'm in "Fastboot USB" mode.
Click to expand...
Click to collapse
Did you first try re flashing your kernel? Might be why your WiFi is sticking.
Sent from my HTC6525LVW using xda app-developers app
grimlocksmash said:
Did you first try re flashing your kernel? Might be why your WiFi is sticking.
Sent from my HTC6525LVW using xda app-developers app
Click to expand...
Click to collapse
Hey guys, after flashing the firmware and the RUU twice using the link provided the Wi Fi is working but it's still acting a little funky here and there. Earlier this morning, the phone rebooted when I tried to turn on Wi Fi. After it booted up, I was able to turn Wi Fi on/off several times and it worked perfectly.
Any chance that putting cyanogenmod or something on there would fix these intermittent glitches?
What would I do for a bootloader and root?
Newbie here, did some reading last night but there's so much.
If you look in the original development thread you will find it. Go to the website download the one for the DNA and then follow the guide. Once you achieve soff you need to flash a custom recovery. I recommend the twrp 2.6 beta it seems to work when flashing all the kit Kat roms I haven't tried 2.7 yet but if your feeling adventurous you can try that to. To flash a recovery you need to put your phone in fastboot and then use the command fastboot flash recovery and then you have your recovery on your phone. Then you can flash what you want. If you want to do this and need any help direct message me and I can help you out.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
If you look in the original development thread you will find it. Go to the website download the one for the DNA and then follow the guide. Once you achieve soff you need to flash a custom recovery. I recommend the twrp 2.6 beta it seems to work when flashing all the kit Kat roms I haven't tried 2.7 yet but if your feeling adventurous you can try that to. To flash a recovery you need to put your phone in fastboot and then use the command fastboot flash recovery and then you have your recovery on your phone. Then you can flash what you want. If you want to do this and need any help direct message me and I can help you out.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am trying to flash to the Sense 5 RUU to see if it corrects my Wi Fi issues but it's stuck at the following:
(bootloader) Read zipped android_info fail
What should I do?
shortstop20 said:
I am trying to flash to the Sense 5 RUU to see if it corrects my Wi Fi issues but it's stuck at the following:
(bootloader) Read zipped android_info fail
What should I do?
Click to expand...
Click to collapse
OK, I decided to take a chance and reboot the device. I'm back in fastboot mode so I'll try the RUU again.