[Q] error installing Liberated 2.2.2 - HTC Aria Q&A, Help & Troubleshooting

Well, I really did try searching for this before posting, but didn't see anyting with several variations on the search.
I have a Rooted Aria 2.1 "stock" with Clockwork Recovery, i think from using unrevoked3 awhile back.
Read up about Liberated 2.2.2 http://forum.xda-developers.com/showthread.php?t=970272 - and decided to try just installing it over the old stock ROM, since others seemed to have success. Did several backups using different apps, such as Titanium Backup, BackupEverything, and also did the NAND backup from clockwork.
Rebooted into recovery. Cleared Dalvik. Cleared cache. Installed from SDcard: the default name of the liberated .zip file, hoxnet_liberated_aria_liberated_final.zip. It ran through several lines of progress:
-- Installing: SDCARD:hoxnet_aria_liberated_final.zip
Finding update package...
Opening update package...
Installing update...
Aria Liberated HFR006b.
With hoxnet_kernel_006b.
Formatting "system" ...
Unpacking new files...
Symlinks and permissions...
E:Error in /sdcard/hoxnet_aria_liberated_final.zip
(Status 0)
Installation aborted.
...so I waited a few seconds, making sure it was really "done", then just tried again, just picking the .zip file again from the sdcard in the clockwork recovery menu, same as before, but now it is just frozen at "Formatting "system" ..."
Suggestions?

Usually when I've seen error messages like that, it turned out that the zip file was corrupt. I suggest re-downloading the zip file and trying it again.
If you know how to check the MD5 sum, check that. The correct sum is listed next to the Liberated 2.2.2 download link.

Don't really have a way of checking the md5, so I guess I'll redownload. Just wanted to make sure this didn't brick my phone. It's still frozen at "Formatting system..." but I can try removing battery to restart it.
...after a long, long reboot and loading time on the ATT white screen, the phone was totally normal back into 2.1 stock. I guess nothing was actually changed during the failed flash attempt. Redownloaded Liberated 2.2.2 by Gene as well as attn1's Liberated 2.2, and CM7... will try them in that sequence, but I'd prefer to stick with the 2.2.2 as it seems from other posters to be most stable and functional.
I don't like bloatware, but can remove it just fine on my own using Ti Backup's method. I mainly want to move apps to the SD card.

Woot! I am Liberated %)

i wish i can use the liberated rom cant flash due to different cwm version

lokodoe said:
i wish i can use the liberated rom cant flash due to different cwm version
Click to expand...
Click to collapse
You should be able to install the Liberated 2.2.2 final version in CWM 5. I'm talking about the version here: http://forum.xda-developers.com/showthread.php?t=970272
The CWM 2 requirement was only necessary for older releases.

Related

[Q] Unable to root update.zip in recovery mode.

I rooted many times before and this is the first time i ran into this problem.
In recovery mode it says E:Can't open /sdcard/update.zip (no such file or directory). I even tried the one click root/unroot program to no avail.
I think the problem started when i was on Bionix 1.4w/Jacs OC/UV/Voodoo kernel and JI5 modem. I decided i want to upgrade to JI6 from bionix 1.5. I did the disable-lagfix in the voodoo folder, restarted my phone and check with terminal and typed mount to see if it was disabled which it was.
Now here is what started giving me problems. After the voodoo was disabled i notice a whole bunch of my apps including the market, clockwork recovery, titanium back up, setcpu and all rooted programs was missing. So before i decided to upgrade to bionix 1.5. I removed the disable-lagfix and rebooted my phone. When the phone was rebooted the missing apps are still missing.
Next thing i decided to do was restore my phone back to stock rom following the steps in the bionix 1.5 thread, which requires flashing it w/ eugene froyo rom then flashing it again w/ stock vibrant 2.1 rom.
Now since im on the stock 2.1 rom i havent been able to root my phone either doing it the manual way or using one click root/unroot program. PLEASE HELP me find a solution
that happened to me once, I just went through the option to flash a zip file and browsed for the file and it worked instead of doing the update.zip option
Yeah, I dont have that option to flash because I cant get rooted.
I figured it out. Close thread please.

[Q] Samsung Screen only...Red Clockwork not coming up!

I thought I had this down and well, I guess not....
I had a great running Superclean v2.6 nonvoodoo running on my DL09 and I did a factory reset from inside the settings. I was trying to setup my Google account so my Google Voice would work right. I had made a backup using red Clockwork so I thought I'd be okay. The phone rebooted and hung on the Samsung screen.
I've been able to Odin the new cwm-recovery-ALL.tar to the phone but it still hangs. I tried using the old version CWMrecovery.tar and it boots in the factory recovery (2e) and won't allow me to apply the update.zip file since it can't mount the drive.
Um, is there a way out? I thought I saw a tar file for the DL09 and that would take me back to stock and then I could install the red recovery and restore my back up. Any help would be appreciated. Thanks!
Error in factory recovery (2e):
E:Can't mount /dev/block/vold/179:9
Can't mount SDCARD:update.zip
Installation aborted.
You can flash to EB01 with all the stuff in this post:
http://forum.xda-developers.com/showthread.php?t=977493
Thanks! I think I found another route, but your solution looked good.
I used Odin and put the cwm-recovery-ALL.tar on after having put CWMrecovery.tar (the older version) and it started into red. I applied the update.zip and installed cwm-recovery-ALL.zip and then am now in the process of restoring my backup. Whew! That was close.
*EDIT*
So, that didn't actually work. When I tried to restore with RED Clockwork it froze during the restore. It specifically froze on restoring the "tegra_flash_image". I even tried using the DL09_stock.zip and that didn't work either. I used the method you recommended and it worked very well. In fact If I need to go back to stock this method seemed the fastest and most straightforward. Thanks again.
For those who read this later. I then installed my ROM choice, which is non voodoo Superclean v2.6 after doing everything listed here http://forum.xda-developers.com/showthread.php?t=977493 and it was much cleaner than what I had originally.

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

Bell Atrix failed 2.2->2.3.4 update.

I'm a Canadian Bell user.
I've been using Android 2.2, rooted, with a little OEM bloat removed (ashphalt demo etc.). The phone decided to update to the OTA 2.3, and bricked. I flashed to OLYEM_U4_2.1.1_SIGNED_UCAOLYPORTFR_P014_A004_M001_HWolympus_1g_1FF.sbf A Bell firmware it seems, though not quite the same as the original.
Which seems to work (I have no internet, but it seems I can call/text, it'll do for I came across http://forum.xda-developers.com/showthread.php?t=1195922&page=14
I then attempted to use Bell GB 2.3.4, so I rooted, installed ROM MANAGER, unlocked the bootloader, flashed tenfar's CWM, pulled the SIM, but kept the MicroSD in (the ROM is on the MicroSD) and then attempted to flash the 2.3.4 Bell GB leak.
First time,
...
Updating BP...
Updating System...
assert failed: package_extract_file("system.img". "/internal/app.bin")
E:Errpr in sdcard/Bell-2.3.4.zip
(Status 7)
Instalation aborted.
So, I reflashed , rooted. etc. and tried again, and it froze this time at Updating BP...
Third times the charm right? aborted at the same stage as the first time.
Can someone please just call me a idiot and tell me I'm missing something silly? I read that someone else had the same error, but it worked the second try for them.
ok so first the 2.1.1 rom is the retail france rom not bell (thus why you didn't have any internet as your apns wouldn't be loaded)
I would try putting the file on the internal memory and flashing it again
I assume the cwm you have is this one http://forum.xda-developers.com/showthread.php?t=1138541
y2whisper said:
ok so first the 2.1.1 rom is the retail france rom not bell (thus why you didn't have any internet as your apns wouldn't be loaded)
I would try putting the file on the internal memory and flashing it again
I assume the cwm you have is this one http://forum.xda-developers.com/showthread.php?t=1138541
Click to expand...
Click to collapse
I can't remember how I found it to be honest, but thank you very much for informing me. Yes, that is the CWM I have.
I will try again right away.
OP, I am slightly puzzled. You were running the stock Bell 2.2 and it decided to update to 2.3 ?? The official Bell update is out ?
Travis Beane said:
I'm a Canadian Bell user.
I've been using Android 2.2, rooted, with a little OEM bloat removed (ashphalt demo etc.). The phone decided to update to the OTA 2.3, and bricked. I flashed to OLYEM_U4_2.1.1_SIGNED_UCAOLYPORTFR_P014_A004_M001_HWolympus_1g_1FF.sbf A Bell firmware it seems, though not quite the same as the original.
Which seems to work (I have no internet, but it seems I can call/text, it'll do for I came across http://forum.xda-developers.com/showthread.php?t=1195922&page=14
I then attempted to use Bell GB 2.3.4, so I rooted, installed ROM MANAGER, unlocked the bootloader, flashed tenfar's CWM, pulled the SIM, but kept the MicroSD in (the ROM is on the MicroSD) and then attempted to flash the 2.3.4 Bell GB leak.
First time,
...
Updating BP...
Updating System...
assert failed: package_extract_file("system.img". "/internal/app.bin")
E:Errpr in sdcard/Bell-2.3.4.zip
(Status 7)
Instalation aborted.
So, I reflashed , rooted. etc. and tried again, and it froze this time at Updating BP...
Third times the charm right? aborted at the same stage as the first time.
Can someone please just call me a idiot and tell me I'm missing something silly? I read that someone else had the same error, but it worked the second try for them.
Click to expand...
Click to collapse
You don't flash it with recovery you flash it with RSD Lite. It's a .sbf file not a zip file There's a billion threads on this already
mobileweasel said:
OP, I am slightly puzzled. You were running the stock Bell 2.2 and it decided to update to 2.3 ?? The official Bell update is out ?
Click to expand...
Click to collapse
Not quite sure about that, though I do know Bell wanted me to update my phone when I already had 2.2, and I must've accepted at some point, bricking my phone.
Now I'm racking my head over this, I've meticulously gone through the procedure, and I don't know what's wrong.
Flash the French 2.2 SBF
Root
Unlock bootloader
Install CWM (tried Tenfar's and another by romracer)
Install 2.3.4.zip (from both external and internal memory)
Still get the same error message at the end.
shadowskorch said:
You don't flash it with recovery you flash it with RSD Lite. It's a .sbf file not a zip file There's a billion threads on this already
Click to expand...
Click to collapse
I flashed the SBF with RSDlite, and izip from CWM.
could have been the 2.2.2 update.
have you tried to re-download the file? wondering the if the system.img file got damaged some how.
you shouldn't need to flash the french rom again (outside of just to have a device that boots)
EDIT
clear your data as well
This is what i did and not a single problem
Pt1 http://www.youtube.com/watch?v=jPQzZOj0-BA
Pt 2 http://www.youtube.com/user/TheSmokingAndroid#p/u/4/BYM-YeSH22o
Pt 3 http://www.youtube.com/user/TheSmokingAndroid#p/u/3/CwJGetPHlzE
Pt 4 http://www.youtube.com/watch?v=IcgvglaXLyM
Pt 5 http://www.youtube.com/watch?v=CzFhKFeTBuM
I am on bell and running this rom http://forum.xda-developers.com/showthread.php?t=1206767
I am on the international kernel for GB(INTL mbr_d00 original Kernel Version)
from here
http://forum.xda-developers.com/showthread.php?t=1156040&highlight=INTERNATIONAL+USERS+%28Based+on+ATT+4591+Source%29+}+posted+by+Faux123+%2C+the+d00+with+the+1.1+overclock+kernel
As for losing your data and not your phone/text. Did you punch in your apn addresses and ports for bell?
Settings-wireless and networks-Mobile networks-add apn
http://forum.xda-developers.com/showthread.php?p=13607746#post13607746
i got this problem fixed by placing in ext sdcard instead of internal memory.
Thank you very much Spuzzum. That was exactly what I needed. Though I must say, going from the stock Bell rom to a modified Alien rom is quite the change. Motorola was nice enough to save my contacts and google my calender events.
Sent from my MB860 using Tapatalk
Edit:
I can't actually seem to differ from what I did and what the instructional video showed, other than loading a different ROM.
I still can't seem to access 2G from my phone though. Not like I need it when I'm in the city, but I'd prefer to use it when I'm out of the city and have to go several days without a charge.
Same problem
hi Guys.. I am having the same problem. I flashed the french SBF now multiple times, rooted, installed Tenfar's recovery and then tried to recover using either the bell 2.2.2 or bell 2.3.4 and both give me error while using recovery. The errror is assert failed , installation aborted. I also had my bootloader unlocked but that didnt help either. Any help will be greatly appreciated.
Bell atrix issues
hey, so when i try to update my phone throws an error saying i dont have "qik.apk" in my system folder. i had this issue before with the random bloat demos the atrix comes packed with, i was able to add the demos to the system folder using su in the terminal and putting the .apk files that i found on the internet into the folder. but for some reason i do not have super user rights anymore (even though the super user app is still installed)
is there any way to fix this so i can update my phone?

[Q] Cant restore stock backups with CWM or TWRP

So im still pretty new to this, but im pretty technical so I pick up on this stuff pretty quick. When I first started getting into this stuff I was using CWM as I saw it used most often around the forums. After getting root and unlocking I backed up my stock rom, and then tried to restore it just to test, and it failed. I tried a few times, with different settings, and it failed everytime, so I pretty much had no choice but to go to custom roms at this point. After switching to TWRP 2.6.3, and messing around with a few CM7.2 and CM9 roms, I decided to flash the 4.5.141 sbf (came from 4.5.145), which bricked me untill i flashed the pudding file again, then flashed a 4.5.145 update fruitcake, so i was back to where I was. Backed up the stock rom again with TWRP, wiped everything just in case that was the problem before, and it still failed when I attempted to restore. Again tried different settings, restoring from the SD card, from the internal, mounted and unmounted partitions. Nothing. I flashed CM9, backed up, and it restored flawlessly. Reflashed 4.5.141, pudding, and 4.5.145 update again, repeated the backup and restore. Fail.
All partitions restore except the system partition. No errors are given in the dialog box. The last line of text is "Restoring system..." However, looking through the log, I find this at the bottom;
Code:
==> tar_extract_regfile(t=0x139110, realname="/system//etc/spellchecker/pt_BR.dic")
==> extracting: /system//etc/spellchecker/pt_BR.dic (file size 4581228 bytes)
FAILED RESTORE OF FILE i: /system//etc/spellchecker/pt_BR.dic
E:Unable to extract tar archive '/sdcard/TWRP/BACKUPS/TA20708E1R/4.5.145_Stock/system.ext3.win'
I:extractTarFork() process ended with ERROR=255
Whats the problem here? I flashed CM9 and it backed up and restored without a flaw. Why is it just the stock roms that are failing me?
BUMP
No ideas from anybody?
Iirc, thete was an issue oreventing the correct decompression of system. On the international fruitcake thread this is discussed.
I had that trouble also, but since the stick rom is a piece of crap, just deleted the backup and installed other roms hehe
Enviado desde mi MB860 usando Tapatalk 2

Categories

Resources