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.
Related
tried to root my g1 today and came stuck, i downgrade android from 1.6 to 1.0, and the next step was to download telnet from the market, but i couldnt get the market to download.
i can see the apps in the market but it just wont download. can anyon help this is the walkthrough i was following http://forum.xda-developers.com/showthread.php?t=442480 , i got to step 6 in the Root your R29 or lower section.
please help
the rom i would like to put on is SuperCSDIv4, so any tips and advice would be good
well mate the rooting that work for me was
RC7-->manually update till i was able to bypass the signin screen then enable wifi (the os which i bypass was 1.5)then download linda file mannager from market/downloaded and install flash.apk and recovery-RA-dream-v1.5.1.img then followed the step as mentioned ...voola and as rooted
i recommand u to use 1-step rooting..it works and soo much easy
http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
and search for recovery-RA-dream-v.1.5.2.img
its the same i m using
try this
thanks jamb, i followed your route and it was much easier. thankyou
thanks jamb, i followed your route and it was much easier. thankyou
Your welcome mate
when i ran though the steps, i got to the end and everything was how it should be.
as id been messin with it foe ages i decided to end there, and i posted all was well abouve.
ive tried to install to roms today both never worked so i must be doinf something wrong.
heres what ive been doing.
empty sdcard, put the rom on it still zipped and renamed to 'update' . insert sd into G1 then boot via home ad power. when ! screen apears press 'alt L' then sellect wipe data followed be install update.zip. then reboot.
once rebooted im still with the original 1.5 .
when i do the wipe and update.zip to me it seems to quick (like 3 seconds for both).
any help peeps
just noticed that that whan i attemp the updat.zip it states update terminated so ive fond my problem ive also noticet that the spl didnt update, even thou it looked last night if all was ok????
going to run through the steps again and see if anything changes. il update later
hi jamb can you gice me a diect link to the spl you used please i thnk that is where im going wrong
here ya go mate
DANGERSPL
sheers jamb, i just keep getting the same msg once i try the update.zip
varifying update package.....
E:No signiture (5 files)
E:Varification failed
Instalation aborted
im at a loss now. any ideas???
What recovery are you using? the alt L thing makes me think you are still using stock.
If you are using RA you don't need to rename it to update.
im using recovery-RA-dream-v1.2.3.img
ihave just tried to use the one u are using but flashrec wouldnt see it, imreally at a loss now.
i just tried to install android stoc 1.0, so that i could start again but that to wouldnt install. so it looks like i may be stuck with 1.5 for now atleast.
edit- it wernt the one u have it was the recovery-RA-dream-v1.6.2.img i tried second
mate u have Uk model?right
just intall flashrec and 1.6.2 recovery image
start flashrec / in the box type something like
/sdcard/recovery-RA-dream-v1.6.2.img
then flash it dont interpt then process and u got root ...
note : put img file in the root(main) of ur sd card
thanks for your help jamb, but i seem to have damaed the boot loader somewhere on my rooting journey ,
i think i know where i done it as after post one, and before post two, i did (i think) get root and managed to flash superCSDIv14, (i got the custom spash with the android bot peeking from behind the A) but after the splash the phone just went black.
when i got your first post i decided to follow that post, i managed to flask android 1.0, then update to 1.5 then from that point i couldnt flash nothing, i even tried to flash back to 1.0 at one point.
last night i went to bed thinking that id be stuck with 1.5, but when i woke, i made the QTA upgrade msg on my phone so i ran it and now am back to where i started 1.6 (which is good cos google nav was released yesrerday)
as the OTA update worked all must not be broken so i decided to start again and tried to flash 1.0, it just faid so. my friend i am giving up, thank you for your time.
stephen.
its been two days now since i gave up on my root of the G1 and am starting to get the craving to start tinker with t againg, i dont want it to beat me.
can anyone outthere shed anylight on my plight. also give me some pointers.
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.
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.
OK folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!
You could try on another computer which doesn't run Vista
tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.
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..