Help, soft bricked my phone - HTC Aria Q&A, Help & Troubleshooting

I was trying to install this (knowmydroid [D0T] com/blog/enable-hw-acceleration-on-stock-cm7-browser) (Enabling H/W acceleration on my browser). I manually copied to the 2 files into system/lib and (studiply) overwrite the files without backing them up first. Now my phone doesn't boot past the HTC boot screen. I can still access the recovery menu. I just don't know what to do without ****ing it up anymore then I have.
I'm running CM7 if that is relevant information.

Just flash the original CM7 zip back on the phone (no need to wipe anything at all) and it should work OK again. But even before you do that, go ahead and make a backup through recovery so that you can undo any changes just in case.

Worked great, thanks man.

Related

Recovery woes

Okay so I recently got this phone more or less as a toy and have been playing with its hardware and software to get it up to par and usable. I've been very impressed by this thing. I ended up with Trackball optional recovery and CM7 Condemned running very well. I seen Gin-sen-tazz and decided to give it a whirl.
Booted into recovery, did a nandroid then wiped data cache and dalvik and then went to flash the rom. It wouldn't go, told me to do something via adb. So I went to restore the backup of cm7 and get a new download ( didnt verify any md5's )
The back up restore gave me the same sort of error, then told me to do something else via adb. I was pretty peved off at this point and went into rom manager and flashed cwr and made a back up of the fresh cm7 install via cwr, and then tried to install the rom via rom manager and then manually in cwr and it still failed.
I'm still downloading my second copy of the rom and I'll be reporting back, but is there any harm in having both recovery's? I really would prefer to run cwr but I have heard of a few bricks, how wide spread is the epidemic? Boot loader still pushes me into trackball optional recovery when selected.
Just kinda sucks that I have two recoveries and neither will work. I am not very new at the whole rom flashing thing but I am not an expert by any means, and have not yet taken the time to learn my adb skills which I know I should
Alright downloaded and put the new rom on the sd card, booted into trackball optional and it flashed just fine.
I also used cwr to back up cm7 and then restore cm7 just to see if that backup indeed worked, and it did. Now I'm concerned that I don't have a stock back up, I made one in trackball recovery but it wont restore... The only back up I have that's working is the cm7 one via cwr... what would you guys recommend i do?
If you decide you want to flash back to stock 2.1 at some point, there's a couple simple options.
Flashback21 will get you back to the latest OTA(March 2011)...unrooted completely stock 2.1.
http://forum.xda-developers.com/showthread.php?t=792026
This other also gives you the latest March 2011 unrooted stock OTA but leaves your custom recovery.
http://forum.xda-developers.com/showthread.php?t=984274
Dunno if this is what was going on, but the Nandroid restore in Amon_RA for the Eris (and derivatives including the trackball-free recovery, I presume) have a 30% battery charge requirement.
If your battery isn't charged above that level, you'll just get a cryptic message about running nandroid-mobile.sh from adb; it won't say "charge your battery, please".
It pays to read Amon_RA's original post, where he points out that you should always check the recovery log file - the exact reason that you could not run the restore operation is reported in that log file. Rather than complaining about an unknown problem on a forum, you would instead know exactly what the problem was.
You can get at the file ( /cache/recovery/log ) via adb while the same recovery session is running, or you can use the Amon_RA menus to copy it to your SD card for later review. It's just a plain text file. Every time you boot the recovery, it gets overwritten - so you need to either review it right away after a problem occurs, or save it to the SD card.
bftb0

[Q] Dead phone, stuck.

Hello,
I'm a happy user of cyanogenmod and have loved it since the day I got it. But as I updated to CM 7.1.0 Stable mod, I've had problems with my wireless. Whenever I try to turn it on, it responds with "Error" and doesn't turn on. I can't see any wireless networks either.
I tried something from cyanogenmods forum, but with no luck, it said I had to "Format system". As I tried to "Format system", it restarted and it's stuck at the "HTC" White screen. It shows the white screen everytime I try to start it. I'm able to get into HBOOT and recovery, but I'm unsure what to do. Have I really broken my phone?
Anything I can do to get it working again? I'd love if anybody could help me here, thank you.
I'm not very good at this, so I would be nice if somebody could guide me through this.
Ok, In your possition I bet you panic a little bit? Don't worry and stay calm
First of all, i don't know what other requirements you need other than to get the rom back into your phone ie swap partition, ext partition etc, so this help is to ONLY get a rom back into your formatted phone.
You said you can boot in recovery, this is a sure sign phone is not broken, do you have clockwork mod recovery?
If you have clockwork mod still in root folder of your sdcard, your halfway to fixing your issue, if no clockwork mod, search on XDA and get the clockwork mod recovery, it'll probably be called fake-flash and it will be a zip file, might be best to get version 5.0.2.0.
Next you will need a rom, download any one you like, be it cyanogen, Blayo's froyo, ogo's gingerbread etc.
If you've already got clockwork mod on your sdcard then best to take the sdcard out, put it in a card reader attached to the computer, copy the rom zip file to the sdcard, put it back in to the phone, load up clockwork mod via recovery on your phone then flash the rom from sdcard...
if no clockwork mod, then copy both clockwork and the rom to the sdcard clockwork must be named update.zip and in the root of the sdcard, put sdcard back in your phone then follow the same flashing procedure as before. You may need to wipe data and davlik cache before flashing.
I'm pretty new to android rooting & flashing and i've had a few scares myself, the one most important thing i've discovered is to have clockwork mod recovery in the root of the sdcard, and so long as you can boot into that, you pretty much can't go wrong, unless your S-OFF, then an inexperianced user can do damage.
The other thing of importance is to either have backups (done via clockwork mod) or a fresh rom to flash on the sdcard, backups are better though because that keep all your apps and stuff intact
Good Luck
OH F*** YEAH! It started now! ranger4740, I love you!
Thanks a lot for the help!
GuyFromDenmark said:
OH F*** YEAH! It started now! ranger4740, I love you!
Thanks a lot for the help!
Click to expand...
Click to collapse
I am very glad I could help you get your phone back up and running.
Have a look in this post my newbee tip for using Clockworkmod recovery's, it may help you for future reference. http://forum.xda-developers.com/showthread.php?t=1298680

[Q] Recovery Mode = Yellow Triangle

So I started by rooting with Shabby's AIO root. Worked fine.
Today I unlocked, following QBKing's instructional video. No errors.
Then I flashed TWRP using fastboot. No errors.
I'm able to boot, everything seems to work (except 4g of course), but when I boot into recovery, all I get is an android with a yellow triangle. What gives? Can anyone help?
try reflashing the recovery happened to me once when i flashed cwm.
it keeps happening to me no matter how many times i try to flash either one. I'm definitely rooted and unlocked but recovery just wont stick at all, all i ever get is the yellow triangle. Ive given up on it....
I have in my notes to delete "install-recovery.sh" in system/etc and reflash. Couldn't hurt.
jrebo said:
I have in my notes to delete "install-recovery.sh" in system/etc and reflash. Couldn't hurt.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=19650030&postcount=1
I think that the above post is correct, and also remember reading somewhere about it.
And I can do that from Root Explorer? I must admit I'm a little nervous - I'd better make a backup. You guys have done it too?
CharFalco said:
And I can do that from Root Explorer? I must admit I'm a little nervous - I'd better make a backup. You guys have done it too?
Click to expand...
Click to collapse
I would always do a backup in CWM or bootstrap before trying anything. I've never done this, but you could always try.
I don't currently have the ability to boot into CWM. I suppose I'll try to get into Bootstrap and make a nandroid, if that's possible - I haven't done any of this stuff since around this time last year on my Evo.
Use root explorer. another reason could be your not unlocked. Does your screen say unlocked when you boot?
Mine does say I'm unlocked, I've also deleted that .sh file after backing it up and still nothing. I don't want to go through the whole process of relocking my mopho to get it to work,, but I know that may help. I've done everything I could and read through every thread on it and still no go. I've definitely learned a lot though, lol. I've also figured out how to switch the internal memory sdcard with sdcard-ext to have your actual sdcard be internal. Good stuff, I love xda.
The current procedure seems to be:
moto-fastboot delete recovery
flash recovery
reboot
That gives it time to re-flash stock recovery during the reboot. What if you flashed the new recovery, yanked battery, went to recovery, then flashed CM7 (which apparently doesn't try to replace the stock recovery)?
I've got Bootstrap working. I'll be doing a Nandroid, then trying to rename install-recovery.sh later today. If that doesn't work - all I can do is go back to total stock, unroot, and restart the process. Life goes on.
Mine definitely says "Unlocked" at the top of the screen on boot - and I'm rooted (I can use Titanium Backup and Wifi Tether)
If it's an issue with the order of rooting and unlocking (I saw no error messages at any stage), can we get a warning placed in the pudding / MoPho FAQ thread please, spare someone else the trouble we're going through?
Seeing as I'm already unlocked and rooted via Penguin's AIO root- and backed up through Bootstrap, is there any harm in flashing the system.img used in QBKing77's video? Would that solve my problem and let a normal recovery stick?
Any idea if this would bork my phone? I don't have a backup - but I -do- want to be able to use CM and Miui (hate MotoBlur). If I'm already AIO rooted and QBking Unlocked, is there any harm to flashing system.img, then flashing recovery?
I am having the same issue on my photon. when i boot in to clockworks i see the android recovery, and when i try to select it the triangle pops up with the
android guy then i have to pull battery to restart phone still works thoe. Tom
Ebert
This worked on my Xoom. Suspect same/similar will work on Photon. Issue is that recent OTA's add files that overwrite custom recovery with stock recovery if you let the device boot (don't let it boot - or if you do, delete those files, then reflash).
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.
topeka_tom said:
I am having the same issue on my photon. when i boot in to clockworks i see the android recovery, and when i try to select it the triangle pops up with the
android guy then i have to pull battery to restart phone still works thoe. Tom
Ebert
Click to expand...
Click to collapse
I had the same issue then someone told me to root via Torpedo method. Did that and everything was smooth sailing from there.
Flash over Bootstrap?
With having bootsrap installed, could I use one of romracers CWM installers and flash over bootstrap? Has anyone tried this?
this is what i used. work great
http://forum.xda-developers.com/showthread.php?t=1250697
moonzbabysh, would you direct me to the thread that shows how to switch the internal and external memory around. I've got a 16gb card but can't put apps on it. Thanks.

[Q] Noob Issues

Yes I am new to rooting droids, but I am not illiterate in this subject. However, I am pregnant, and over emotional and possibly losing my mind because I can't get my phone to work. (Sounds like a noob issue right?!)
I have a droid 2, latest update, blahblah.
I rooted it, no problem, got good instructions from here, downloaded ROM manager, and Bootstrap. I downloaded Liquid Dream ROM. Flashed Clockwork, and rebooted. ROM seemed to download onto the device fine, finished rebooting and now it plays the Liquid Dream animation on start up over and over. Currently I am in reboot mode but I am stuck, I don't know where to go from here (because I am a noob, I know). So I'm hope full that someone with a lot more knowledge on this can help me out, so I don't totally lose my mind. Thanks for your time future person who helps me! (I hope)
did you wipe all the data/cache and davlik prior to installing a new rom. When ever changing roms, you need to clear out the old data.
go into fastboot, clear data/cache and under advance clear dalvik.
try that.
ChelseaLynn__ said:
Yes I am new to rooting droids, but I am not illiterate in this subject. However, I am pregnant, and over emotional and possibly losing my mind because I can't get my phone to work. (Sounds like a noob issue right?!)
I have a droid 2, latest update, blahblah.
I rooted it, no problem, got good instructions from here, downloaded ROM manager, and Bootstrap. I downloaded Liquid Dream ROM. Flashed Clockwork, and rebooted. ROM seemed to download onto the device fine, finished rebooting and now it plays the Liquid Dream animation on start up over and over. Currently I am in reboot mode but I am stuck, I don't know where to go from here (because I am a noob, I know). So I'm hope full that someone with a lot more knowledge on this can help me out, so I don't totally lose my mind. Thanks for your time future person who helps me! (I hope)
Click to expand...
Click to collapse
Well, something probably didnĀ“t upload ok. So, what you have to do know is: make sure the .zip file in the sdcard is not corrupted. In order to make sure of that, you can try to download it again (you will need an sdcard reader). Then, when you have already the .zip file in the sdcard, boot into recovery. From boot loop the best way is to boot the phone pressing power + volumen down, then choose recovery from the hboot menu. Once you are in the CWM recovery menu, do a wipe data / factory reset. wipe cache partion and format system.
When that is done, you are able to flash the zip file from install .zip from sdcard choice. That should work and get your cell back to life.
It might be Clockwork. There have been some issues with it. If none of the above suggestions work, try getting Amon Ra.
If ClockWorkMod does not work you can try flashing the 4EXT recovery...works smoothly at least in my Inspire 4G.

[Q] Nabi 2 brick-ish Stuck no touch input

Lost wifi again! was doing the normal backup and return to stock again to get the wifi back and it packed up on me, no longer accepting touch input. So I am stuck can't try to reload it, in the hope its software. right now its version 2.0.5 or something like that. Can't use the recovery since the touch is not working. Is there any working non-touch recoverys or is there a stock like firmware that can be loaded with out twrp touch. I still can fastboot flash the recoveries none work I have tried all the twrp version I could find.
I can plug a mouse in with a usbtg adapter but that is not useable in twrp.
I have opened it up to make sure a cable was not loose on the screen, and it was not dropped or broken in anyway.
Anyone who can hear my call HELP!
theskyisoutthere said:
Lost wifi again! was doing the normal backup and return to stock again to get the wifi back and it packed up on me, no longer accepting touch input. So I am stuck can't try to reload it, in the hope its software. right now its version 2.0.5 or something like that. Can't use the recovery since the touch is not working. Is there any working non-touch recoverys or is there a stock like firmware that can be loaded with out twrp touch. I still can fastboot flash the recoveries none work I have tried all the twrp version I could find.
I can plug a mouse in with a usbtg adapter but that is not useable in twrp.
I have opened it up to make sure a cable was not loose on the screen, and it was not dropped or broken in anyway.
Anyone who can hear my call HELP!
Click to expand...
Click to collapse
You can use open recovery script to still use TWRP without touch. So you are saying you have no touch in Android or TWRP right? What happened right before the touch stopped working?
attempted to unroot
aicjofs said:
You can use open recovery script to still use TWRP without touch. So you are saying you have no touch in Android or TWRP right? What happened right before the touch stopped working?
Click to expand...
Click to collapse
I attempted unroot as I have had to do before to get wifi back working. I did a wipe and restore the factory firmware then reset to do that whole wifi issue fix process and poof no more touch in either place but I can hook up a mouse in the android system. I can go in to twrp but the only twrp for this is touch. I am almost positive that my restore to factory backup was bad /corrupt because that's when it happened. Also the firmware verson also the apps and all were not removed so I am assuming it went bad doing the firmware. I don't care about loosing things. I have stock firmwares but can't load it. IF I had a non touch way to replace the firmware I think that would fix it all.
Anyideas how to push a firmware for that nabi 2 deal. or a place I can get the .win image to push it (if that would even work) I have a 19. something .win one but I tried to push it and it writes but does not apply it even after factory reset following that. Just stuck here now.
theskyisoutthere said:
I attempted unroot as I have had to do before to get wifi back working. I did a wipe and restore the factory firmware then reset to do that whole wifi issue fix process and poof no more touch in either place but I can hook up a mouse in the android system. I can go in to twrp but the only twrp for this is touch. I am almost positive that my restore to factory backup was bad /corrupt because that's when it happened. Also the firmware verson also the apps and all were not removed so I am assuming it went bad doing the firmware. I don't care about loosing things. I have stock firmwares but can't load it. IF I had a non touch way to replace the firmware I think that would fix it all.
Anyideas how to push a firmware for that nabi 2 deal. or a place I can get the .win image to push it (if that would even work) I have a 19. something .win one but I tried to push it and it writes but does not apply it even after factory reset following that. Just stuck here now.
Click to expand...
Click to collapse
If you have touch in Android install this https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager push your backup and use the program to make the open recovery script for you.
no touch anywhere. and no wifi!
Like I said no wifi and no touch at all anywhere So going online Iis a no go. I can use a mouse on the android system. Also I beleve my backup firmware is what caused the issue with the touch. Again this is a nabi 2 so now its been reset no file manager either access a apk from the sdcard if I could get the apk for that.
update
browser loaded the twrpmanager apk with that installed stock image now wifi works but no touch still what am I missing with the touch? Trying the stock update to see if that corrects anything I doubt it though
over post sorry
I know I am over posting on my own thread... sorry about that.
Had a thought. Since I am not great at describing what I need to accomplish here, try to work with me on this.
I need to just complete start over GO FOR BROKE format and push out the rom with adb How can I get started to do this and what do I need?
I feel that something in the touch input is not working based on some part of the rom is hosed. even tried the original recovery gives that android error icon thingy and I see nothing till she restarts nothing changes.
OK if you want to go for broke... You have to have an external SD card for this. TWRP must be installed
Hook Nabi up via USB can be in Android or TWRP
1) Download this: Nabi 2 stock
2) Unzip the NABI2STOCK.zip
3) Go here: http://forum.xda-developers.com/wiki/Fuhu_nabi_2
4) Grab either the 2.0.5 or 2.1.27 stock rom
5) Put the downloaded ROM zip in the "install" folder that was made in #2. Dont unzip, just download it straight to the install folder
6) Run 205.bat or 2127.bat depending on which ROM you chose.
The script will extract the ROM from the zip, copy the stock ROM to your external SD card, create an openrecoveryscript that will format system, format data, and restore Boot and System partition. Data will be left blank. This erases everything, except hidden partitions and recovery partition.
downloading will update when its done
downloading now will update when I run it. I hope things fixes it. as I have hosed it so far.
I get an error
I get an error
mkdir: can't create directory /external_sd card/twrp/backups/015d2a50211c1a19/abcdstock or something like says directory does not exist odd error it went thought its cycle and exited after that.
I do have an external sd card in it and it is working. did not know if that was an sd card error or what
no touch still
sadly no touch still.
Should I assume its hardware now? or do I have any hope its software?
The version and all changed so I know it did something but no touch
theskyisoutthere said:
sadly no touch still.
Should I assume its hardware now? or do I have any hope its software?
The version and all changed so I know it did something but no touch
Click to expand...
Click to collapse
It seems hardware now, but it is odd that touch went out when you were doing things to it. Still under warranty? Have you taken it apart and seen if anything is wrong?

Categories

Resources