I get this error whenever I try and flash the latest update. Any way to fix it.
You made changes to your /system/ replace LatinIME.apk with the stock one.
You probably installed the LG G3 keyboard or something.
This is the stock one for the TWRP keyboard.
Try flashing http://forum.xda-developers.com/oneplus-one/general/xnph33r-ota-modified-updater-script-t2855052 instead
Thanks.
Related
I have a rooted stock Sensation. I have heard that to update to the latest firmware, I need to flash the stock recovery P58img file (or whatever it is called) and then revert back to the clockwork mod recovery. As we all know, trying to apply the firmware update with the clockwork mod recovery prevents the update from even attempting to install.
I downloaded the stock p58 file someone kindly provided me and tried the update, but it always freezes 1/3 of the way through the update and I have to pull the battery to restore it to normal.
Does anybody have an idea why this is happening? I read most of the update thread, but I didn't see the solution unless I missed it.
Listerine said:
I have a rooted stock Sensation. I have heard that to update to the latest firmware, I need to flash the stock recovery P58img file (or whatever it is called) and then revert back to the clockwork mod recovery. As we all know, trying to apply the firmware update with the clockwork mod recovery prevents the update from even attempting to install.
I downloaded the stock p58 file someone kindly provided me and tried the update, but it always freezes 1/3 of the way through the update and I have to pull the battery to restore it to normal.
Does anybody have an idea why this is happening? I read most of the update thread, but I didn't see the solution unless I missed it.
Click to expand...
Click to collapse
You haven't provided any real details.
PG58IMG.zip can be used to update a multitude of things on the phone, Recovery, Radio, Firmware.
Can I ask why you want to update the Firmware and what you expect to get out of the update ?
There is a thread on a cut down update (no HBOOT Update) from the latest RUU, is that what you're referring to ? http://forum.xda-developers.com/showthread.php?t=1385439
I have also read that installing the latest RUU (with the firmware update) changes the HBOOT which can affect how it's then used.
You need to ask for more in details
gol_n_dal said:
You haven't provided any real details.
PG58IMG.zip can be used to update a multitude of things on the phone, Recovery, Radio, Firmware.
Can I ask why you want to update the Firmware and what you expect to get out of the update ?
There is a thread on a cut down update (no HBOOT Update) from the latest RUU, is that what you're referring to ? http://forum.xda-developers.com/showthread.php?t=1385439
I have also read that installing the latest RUU (with the firmware update) changes the HBOOT which can affect how it's then used.
Click to expand...
Click to collapse
Sorry. so the pg58img I used was a stock recovery file. I had heard using that would allow me to install the update, but after flashing it during the installation of the update it failed.
I wanted to install the firmware because I had read that it improved system performance and reduced bugs.
I saw the update that you were referring to, but the thread mentioned how after updating there would be no visual changes or any indicators to let me know that the firmware had actually updated, and I didn't like that aspect of it.
All the forums that I could find are talking about updating from a stock rom to the ODEX rom. I am wondering if i need to update my bootloader if i am upgrading to the asus rom.
I have TWRP 2.4.1.0 and i am on the ASUS stock ics update 30. I have downloaded the ASUS stock firmware V10.6.1.14.8 which stores the 4.2.1 rom. If i do a wipe on everything from TWRP then mount and install the rom from an external sd card, will I brick my device without doing the same bootloader update that is done for the ODEX rom. Correct me if I am wrong but I believe that the firmware package comes with the bootloader needed for the rom.
data90 said:
All the forums that I could find are talking about updating from a stock rom to the ODEX rom. I am wondering if i need to update my bootloader if i am upgrading to the asus rom.
I have TWRP 2.4.1.0 and i am on the ASUS stock ics update 26. I have downloaded the ASUS stock firmware V10.6.1.14.8 which stores the 4.2.1 rom. If i do a wipe on everything from TWRP then mount and install the rom from an external sd card, will I brick my device without doing the same bootloader update that is done for the ODEX rom. Correct me if I am wrong but I believe that the firmware package comes with the bootloader needed for the rom.
Click to expand...
Click to collapse
Before you update to the latest firmware, I would recommend that you use NVFlash as a backup for recovering if you brick your device. You can find the information here: http://forum.xda-developers.com/showthread.php?t=1901479
If you update the latest Asus firmware, V10.6.1.14.8, it will also update your bootloader with the latest version. Good luck.
Thank you for the idea of NVFlash but unfortunately I have one too many updates to utilize that wonderful software. If I was able to use it, then I would have dove in head first and then informed the populace of my findings. So lets see if I give my self a ~$450 paper weight.
data90 said:
All the forums that I could find are talking about updating from a stock rom to the ODEX rom. I am wondering if i need to update my bootloader if i am upgrading to the asus rom.
I have TWRP 2.4.1.0 and i am on the ASUS stock ics update 30. I have downloaded the ASUS stock firmware V10.6.1.14.8 which stores the 4.2.1 rom. If i do a wipe on everything from TWRP then mount and install the rom from an external sd card, will I brick my device without doing the same bootloader update that is done for the ODEX rom. Correct me if I am wrong but I believe that the firmware package comes with the bootloader needed for the rom.
Click to expand...
Click to collapse
You are correct. The Asus firmware has the correct bootloader, recovery and rom. If you flash it from TWRP it will install the stock recovery. So you loose TWRP and root too. You're basically back to a stock system, except you're unlocked.
berndblb said:
You are correct. The Asus firmware has the correct bootloader, recovery and rom. If you flash it from TWRP it will install the stock recovery. So you loose TWRP and root too. You're basically back to a stock system, except you're unlocked.
Click to expand...
Click to collapse
When I went to flash the firmware from twrp it kept failing. (and i accidentally wiped the os from the device) So I flashed ics back onto it and then tried upgrading again from the stock recovery, but i kept getting the dead android. I also got the device to recognize that there was an update zip on the device so that it would send it into an updating state by itself, but that also produced the android with the caution sign.
Any ideas?
data90 said:
When I went to flash the firmware from twrp it kept failing. (and i accidentally wiped the os from the device) So I flashed ics back onto it and then tried upgrading again from the stock recovery, but i kept getting the dead android. I also got the device to recognize that there was an update zip on the device so that it would send it into an updating state by itself, but that also produced the android with the caution sign.
Any ideas?
Click to expand...
Click to collapse
There are a lot things that could be wrong. However, most likely are: 1. A wrong signed firmware, for example you have a US bootloader but you try to update with WW firmware. 2. You have a currupted zip file. 3. You forgot to unzip it once because there is a zip inside the other zip file. If non of the above are applied to you, you could try this.
1. Copy a second zip file to your Root directory on your Internal SD
2. Reboot your device
3. After rebooted, you should see the notification on your lower right corner with the new update
4. Just click on the updated notification and follow the instructions as it walk you through the updated precesses.
Please report back. If it does not work, you need to rename your second zip file and use the stock recovery to update the firmware. There is a link some where on this website will walk you through the processes. Good luck.
LetMeKnow said:
There are a lot things that could be wrong. However, most likely are: 1. A wrong signed firmware, for example you have a US bootloader but you try to update with WW firmware. 2. You have a currupted zip file. 3. You forgot to unzip it once because there is a zip inside the other zip file. If non of the above are applied to you, you could try this.
1. Copy a second zip file to your Root directory on your Internal SD
2. Reboot your device
3. After rebooted, you should see the notification on your lower right corner with the new update
4. Just click on the updated notification and follow the instructions as it walk you through the updated precesses.
Please report back. If it does not work, you need to rename your second zip file and use the stock recovery to update the firmware. There is a link some where on this website will walk you through the processes. Good luck.
Click to expand...
Click to collapse
I second LetMeKnow.
Download the firmware again unzip it once and put it into the root of your microSD card. The card should be formatted as FAT32.
If the recovery does not automatically recognize it, rename the file to EP201_768_SDUPDATE.zip.
As far as I can see you are on the .30 ICS so nvflash won't work for you.
Looked through both dev subsections and can not find an offical release of CM11S before the 4.4.4 OTA update. Was wondering if anyone knows where it can be downloaded to go back to before the update. Thank you.
This is the zip i used to flash trough stock recovery.
Its the official 25R version signed by CM
http://dist01.slc.cyngn.com/factory/...con-signed.zip
Note : When i flashed this over the 30o update my trebuchet crashed all the time to fix this simply factory reset after update !
In an attempt to stop anyone else from making a "pls halp me" thread I decided to make one myself.
Before I go further let me reiterate the importance of regular backups. Before you do anything, make a full backup of your device in a usable state^. This serves as somewhere you can revert to if you accidentally tap something that screws everything up.
^ - If you're trying to recover from what appears to be a softbrick you should start by flashing and/or booting into recovery or fastboot at least.
Being overly excited about finally getting Lollipop (I don't check for updates often) I immediately went and installed the first update available OTA, forgetting that I had for some reason refused to update my E8 since unboxing it. I've since successfully updated from 1.09 to 2.33 (Kit Kat 4.4.2 to Lollipop 5.0) and installed the Xposed Framework, here's some issues I ran into and what I did to solve them.
PROBLEM: Update takes you to your custom recovery mode without doing anything else.
Having already rooted and installing TWRP the OTA update failed, only taking me to TWRP's recovery screen instead of performing the update.
SOLUTION: Flash the stock recovery.img extracted from the downloaded .zip update in the Downloads folder on the Internal Storage
You can probably find the OTA/RUU update .zip you need from this thread or let your E8 check and download the update .zip which you can then find in the Download folder on the Internal Storage. Transfer it to your PC and extract recovery.img from 'firmware.zip' in the update .zip file. Using fastboot, flash the extracted stock recovery image and reboot. You can now restart the update which will properly complete. Once your phone has booted back up into Lollipop and completed the update you should flash back your custom recovery of choice using fastboot.
PROBLEM: ROOT LOST AFTER UPDATE
This shouldn't be a surprise. OTA updates will unroot your device.
SOLUTION: Install SuperSU in recovery, NOT Play Store.
Download the latest SuperSU installable .zip and copy it to your phone. Boot into recovery and install.
My E8 is a single-sim M8sX but I believe these steps should work with any other variant.
I get this message when I try to flash the new CM12 snapshot on my HTC One M8, SlimROM 4.4.4, with TWRP v.2.8.1.0. When I tried it, I actually had to use an RUU on my phone to get it working again. How do I fix this (not the broken phone, I fixed that).
I've looked into similar threads, and one says I need to update my TWRP, but I can't, because anything above TWRP 2.8.1 doesn't work on KitKat 4.4.4, and I have no idea how I would update my phone past that, since that's what I'm trying to do...
darthnix said:
... anything above TWRP 2.8.1 doesn't work on KitKat 4.4.4, and I have no idea how I would update my phone past that, since that's what I'm trying to do...
Click to expand...
Click to collapse
I'm not so sure this is true. IF there's a point at which twrp is too new to flash a kit Kat Rom then you probably don't have to go back much further than 2.6 or so. If you're looking to get to a newer Rom then I would greatly recommend flashing the 5.0.1 ruu from dottat (to make sure you're on the latest official firmware) and then flashing the latest twrp followed by any one of the great lollipop roms out there.