Hello, I have a Acer Liquid E, I tried to update the 2.2 OS from the .ca website to my 2.1 (this is a dutch version), but it gave an error.
I now can't boot my cellphone and when I try to update again it always says installation aborted and a code (something like getprop(ro.build.display.id)
If i boot my phone i get random colours and then it just freezes on the Acer loading screen with the android robots.
Can I fix this, can I send it for warranty, or did i just messed up my cellphone?
Thanks.
You might still be able to recover from this situation. Try installing the Malez recovery tool if you dont already have it. http://code.google.com/p/acer-liquid-malez-recovery/wiki/howToInstall
Then flash to a safe ROM (preferably your actual ROM) using an update.zip through Malez. You can find update.zips for most ROMs around these and other forums.
Updating using the Acer Download Tool and BIN files doesn't work unless your actually in OS mode (which your not, since your not getting past the acer androids screen). Malez should still work though.
Related
Hello everyone,
i really thank all the people who are investing lots of time on this site to help others. I have found myself many solutions to many issues in many of my phones.
now i have a new issue and I have not benn able to find a solution. maybe its hidden in the forums, if you know it, please send my a link.
issue:
got a g1 from the US, using it in EU.
if I turn it on, shows the G1 logo folowed by the recovery(android system recovery uitility)
It doesnt matter if I do something else, it allways comes the screen.
Tried several upgrades but it allways tells me:
Install form sdcard...
Finding...
Opening...
Verifying...
E:No signature (XXX files)
E:Verification failed
Installation aborted.
on top of the recovery there is a message:
E: can't open /cache/recovery/command --> to this i found several solutions, but all require a running g1... this is not the case.
Also the "back+power" wont load the defaults, it doesnt matter what i do.. wont do anything.
PS: SD is an 8Gb class 6 which was working on my old G1, fresh formated
any clues?
most appreciated!
Luis
I almost forgot to mention..
Power + Cam, fastloader wont work, wont load.. also found a solution having a working G1.. again.. this is not the case. I got the phone yesterday and should be working, it looks rather soft-bricked
A hint might be to post this in the Dream Q & A Section before you get battered for posting in the Dev section....
many thanks! Q&A should have been!
any ideas to solve my problem? thanks
E:No signature (XXX files)
E:Verification failed
is due to the ROM not being signed.
if you want to get into bootloader to flash nandroid backups
use
adb reboot bootloader
Click to expand...
Click to collapse
Hi B-man007,
thanks.. is there a way to use ADB if the phone has no OS? and if its not recognized by PC... ? found solutions about how to use it.. IF the phone is running. please let me know if i am missing something here. cheers!
any other solutions?
if the roms that i tried are not signed.. could you suggest me one which is?
tried from original ones to cooked.. same responce. i even tried 30 to 33.. to see waht happens, it started but showed me again an error message, it would make sense if the installed rom would have been 30. i was just trying around.
any links to a very old android which is signed? to keep on trying.. cheers!
Since you have a US G1, flash the RC29 DREAIMG.nbh to get to Android 1.0
ADB can be used in recovery since there is a kernel being used. You need to install the drivers for it to work
no cannt do.. driver for win7 x64 are not te be found and the update from RC29 not possible. i cannt access the booloader to install images ;(
tried several signed updates and roms, allways the same crap!
any other idea? thanks!
The adb drivers for vista x64 should work just fine. If you can't get into bootloader by holding Cam+Power
you will need adb to actually boot into the bootloader to flash the RC image
so.. many tests .. same situation
ADB works if the device is conected. it could be recognized if the bootload is on OR if android is running.
none of this works for me.
i cannt access anything but the android recovery, believe that the old user saved recovery on SDcard and send me the phone w/o it... E:/can't access recovery.. blah
i am getting really angry with the phone and the seller.. damm eVay
Ok, so here is the scoop:
I was in the middle of trying to root and upgrade my Rogers acer liquid e to v 2.2, but I messed something up and I can't finish.
I installed malez with no problems. Then, when I went to upgrade to lcr, I saw that it said I first needed to install 4.002.14.EMEA.GEN1. I downloaded that as well and spent an hour trying to install it through malez, which I think now I've realized I'm suppose to install using Acer Download Tool.
Problem is, before I learned this I tried installing LCR-F 2.0 without having installed 4.002.14.EMEA.GEN1. It said it "installed" correctly, but then when I tried to boot normally it hung at the robot flash screen, without the eyes blinking (I read they are suppose to blink). With this being an issue, I learned about the Acer Download Tool and have been trying to use it to install 4.002.14.EMEA.GEN1. It identifies the device, and prosesses the Nv ID. Then, when trying to process the DMSS DL Hex file, it jams up every time around 91000/137056 and gives me a "The write timed out" error. I don't know what to do at this point.
If you have any advice on what to do next, please let me know. I'd really like to have my phone working in some form at least...
Thanks much
Note2: I did try updating with the stock 2.2 firmware the supposedly doesn't work if you have malez installed. Is it possible that broke it?
UPDATE: Realized I could install the stock 2.1 fido firmware on the device through malez. tried installing that, it said it was sucessful, but its been on the multi-robot acer loading page for 5+ minutes now. Also tried with rogers, same issue.
I am sick to my stomach. I tried to update my WIND version of the G2X to the T-Mobile V21E_00.kdz to get the newer baseband installed but it caused my phone to get stuck at "S/W upgrade Please wait while upgrading..." and the V21E_00.kdz
file I downloaded is corrupted (I've downloaded a few from various sources). I did do the NVFlash recovery and installed ClockworkMod Recovery before I did that but nothing I've tried, and I've tried virtually everything to resurrect my LG-P999 phone, worked. Various flashers I've used stop at extracting the V21E_00.kdz because it is corrupted. The normal LG update tool that is used for the T-Mobile G2X doesn't work for the WIND Mobile phone version because it detects that it isn't a T-Mobile phone and won't install the update and won't do an emergency repair. This phone can't be returned to WIND or LG because the upgrade I tried is "unauthorized" and they won't help.
Does anyone here know where I can get a good copy of V21E_00.kdz which will fully extract and, if you do, please post the link to it.
Is your phone the T mobile version?
Sent from my LG-P990 using XDA App
Why don't you ask here:
http://forum.xda-developers.com/forumdisplay.php?f=1114
Your phone is a p999 if I understood correctly.
I think you should use nvflash to restore a proper system, it always work. Ask in p999 forums.
corrupted kdz
Core Memory said:
I am sick to my stomach. I tried to update my WIND version of the G2X to the T-Mobile V21E_00.kdz to get the newer baseband installed but it caused my phone to get stuck at "S/W upgrade Please wait while upgrading..." and the V21E_00.kdz
file I downloaded is corrupted (I've downloaded a few from various sources). I did do the NVFlash recovery and installed ClockworkMod Recovery before I did that but nothing I've tried, and I've tried virtually everything to resurrect my LG-P999 phone, worked. Various flashers I've used stop at extracting the V21E_00.kdz because it is corrupted. The normal LG update tool that is used for the T-Mobile G2X doesn't work for the WIND Mobile phone version because it detects that it isn't a T-Mobile phone and won't install the update and won't do an emergency repair. This phone can't be returned to WIND or LG because the upgrade I tried is "unauthorized" and they won't help.
Does anyone here know where I can get a good copy of V21E_00.kdz which will fully extract and, if you do, please post the link to it.
Click to expand...
Click to collapse
Hi Core Memory, I don't know if you finally got an answer to your problem, but I got stock in similar situation, T-Mobile G2X that no longer boot after doing a LG update,
tried the various ClockworkMod Recovery, nvflash, root, nandroid, img, fixes,
but ended with that procedure as last resort, which failed with the various files I tried. same corrupted error message while extracting...
In my case, the error message was misleading,
I finally notice that the file I tried were containing a space: 'P999 V21E_00.kdz' apparently those kind of tool can be picky, I just try removing the space in the name P999_V21E_00.kdz
My guess was right, I restarted the procedure and everything went fine,
the phone is now up and running, using Gingerbread (2.3.4 I think)
hope this can help,
Jonathan
jhoude said:
Hi Core Memory, I don't know if you finally got an answer to your problem, but I got stock in similar situation, T-Mobile G2X that no longer boot after doing a LG update,
tried the various ClockworkMod Recovery, nvflash, root, nandroid, img, fixes,
but ended with that procedure as last resort, which failed with the various files I tried. same corrupted error message while extracting...
In my case, the error message was misleading,
I finally notice that the file I tried were containing a space: 'P999 V21E_00.kdz' apparently those kind of tool can be picky, I just try removing the space in the name P999_V21E_00.kdz
My guess was right, I restarted the procedure and everything went fine,
the phone is now up and running, using Gingerbread (2.3.4 I think)
hope this can help,
Jonathan
Click to expand...
Click to collapse
Thanks for your help.
I did get the problem solved a long time ago and have learned a lot since those early days of owning the G2X. The V21E kdz file installs Gingerbread 2.3.3.
So for awhile I used a droid as my main phone and I flashed countless different roms on it. One day though it just went kaput on me, the led flash started flashing on and off whenever I tried to reboot it and I could not access anything including recovery or boot loader. Eventually the battery died and it would not charge again.
I recently was messing around with it and was able to revive it, would not boot up still but was able to get in the boot loader and eventually sbf it. The battery still wont charge(normally) which tells me at least one issue still exists with hardware. Other than that the phone works fine now on android 2.0. The problem is that I cannot upgrade it to anything higher than that.
The only .sbf I could get to both load and boot up successfully was esd20 anything else would just boot loop indefinitely, after rooting that and trying to go from there anything else also boot looped. I installed every recovery I know of from clockwork to spr to that rzr mod of it but none could flash without the same results(restoring a nandroid of that esd20 still worked though). I've tried different kernels as well to no avail. The first steps I did were an exact procedure that I had done before on the same phone successfully with a 2.2 sbf but now it just wont work.
I don't know if there could be some hardware issue causing these problems though I cannot fathom how when one firmware still works and would appreciate any insight that anyone has as to what may be the problem. Was planning on giving the phone to a young family member to play games on as soon as I managed to boot it back up but I don't want to deal with the compatibility issues with such an old version of android.
OK, this post might be long. Feel free to skim. I just want to let people know everything that I've done.
So, my VS980 was rooted and I was trying to install a new ROM. I was going to try out Cloudy G2, but the installation routine only gave me international variants to choose from. I picked one anyway and my phone has been hosed since. I didn't have any download mode or recovery or anything.
I was able to get download mode back by extracting part of the firmware out with the LG Firmware Extractor and flashing that through fastboot. So, that part worked. I have download mode. I was going to try to restore my 24A firmware with a KDZ file and the old LG flash tool v 1.8.1 (the one where you put the ADB interface on COM41, and you use the updated megaunlock.dll, etc), but that no longer works for me. It keeps giving me the "failed previous load" error. I can't find a fix for that.
So, I've been trying to flash it (or firmware 26) with the LG Flash Tool 2014 (the one where you pick "Republic of Korea"). That will only get to between 25 and 49%, and then crash with an unknown error.
In between trying that option, I found instructions for extracting all of the bits out of the firmware and then flashing them to the phone partitions one by one. That seemed to work except I kept getting a security error on bootup. The only fix I found for that was to flash with the first flash tool I mentioned. Ugh.
The last time I rooted my phone and ran a custom ROM, my desktop USBs couldn't communicate with my phone very well, but my laptop could. This time not even the laptop's working. I even bought a new USB addon card (I needed it anyway, the USB3 ports on this suck). That seemed to get the computer to see the phone better, but it didn't solve my problems.
Can anyone help with this? I've scoured tons of directions already.
Thank you for any help
Wackman
A little bit of progress
So, I finally got the older flash tool v 1.8.1 to start working. I've almost got it to flash the stock .TOT file (the KDZ file keeps giving me the "failed previous load" error). Now, I've kinda hit a new roadblock.
I think I mentioned that I got into this mess by trying to flash the CloudyG2 ROM, but that it's for international variants. When the flash tool tries to flash the firmware for the VS980, it thinks I have an F320S, and says wrong phone. Anyone know a way around this? I still only have access to download mode. No fastboot, no recovery, no ADB.
any luck? I bricked my G2 last night and I'm trying the flashtool to get back to stock 27A right now. Did you update your C++ library? I read somewhere that that can cause issues with flashtool..