[Q] TWRP: AutoRec: cant flash roms - AT&T LG G2

ive had this phone for a year and a half. i used ioroot, and autorec, and whenever i try to flash, its fails. how can i flash roms without fully restoring my phone back to jelly bean? (going back to rom version d80010d)
Current Version
Android: 4.4.2 Kitkat
ROM version: Stock D80020k
TWRP: 2.7.0.0
EDIT: i forgot to mention that i have the d800 variant.

1. re-download the rom, to make sure you don't have a corrupt download
2. what message is it saying when "fails to flash".........Ex. Does it say something like "error executing update binary"
3. You can adb sideload the rom (and push) (which will most like not work since twrp can't do it normally)

Related

[Q] Do you need ROM Manager to flash ICS 4.0.3?

Hey this is my first time posting - I have a rooted Rogers Samsung Captivate i897 that I upgraded to Gingerbread 2.3.4 in November (with an AT&T based ROM). I am trying to upgrade the firmware to the new ICS 4.0.3 that is now available for this model as I am looking for something new.
So, I did some research and followed the directions that were posted (got ROM Manager, downloaded nightly .zip files & GApps). I then tried to back up my ROM using ROM manager (didn't work but thats OK I have the ROM file on my PC). And did the factory restore/cache wipe and tried to flash the .zip files from my SD and it didn't work.
Here is what it says when I try to flash:
"E: failed to verify whole-file signature"
"E: signature verification failed"
Question 1) What could be causing this error?
Question 2) Should I try to flash a stock ROM first before attempting to flash ICS?
Question 3) do I really need to use ROM Manager?? Is there another method available (flashing from PC from Odin)?
I am hesitant about doing this on the fly because when I updated to Gingerbread in November I had a good scare with my phone - soft bricked it, fixed that, and then got it stuck in a boot loop, then had issues with boot logo conflict between Rogers a AT&T. I was out of a phone for about a day working madly to fix it. I would like to avoid it again at all cost.
Phone Information:
Firmware Version: 2.3.4
Baseband Version: I897UCKH3
Kernel Version: 2.6.35.7-I897UCKH3-CL461307
Build Number: GINGERBREAD.UCKH3
Please help I appreciate it!!

[Q] Can't install ROMs

Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Download latest recovery from http://forum.xda-developers.com/nexus-s/development/crespo-philz-touch-t2284670
Then try to flash the ROM. It seems your recovery is very old.
gunlok said:
Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Click to expand...
Click to collapse
gunlok said:
Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Click to expand...
Click to collapse
@smit.sanghavi is right.
You need KitKat compatible Recovery. Update your recovery and then try to flash the ROM.
K guys, wanted to try all you said, but there's another problem.
I discovered my nexus isn't rooted. Bootloader unlocked, but any root checker says its unrooted (of course it was before...). So I'm trying to reroot it but when im connecting my phone via usb in bootloader windows 7 doesn't recognize the device. When the phone is connected in recovery or in normal usb debugging mode it recognizes it as adb android, looks good to me. I go back to booloader and i get "Windows has stopped this device because it has reported problems. (Code 43)" in Devices.
Installed the drivers on few different ways.
So.... what now ?
UPDATE: solved

Error Status 7 (device name doesn't match) in Custom Rec when trying to install zips

Hello! Recently purchased a used (but like new) S Relay off of Ebay. It came with 4.1.2 already installed.
Basically let me tell you a brief backstory: I started off by installing Custom Recovery (CWM PhilZ 6.07) using ODIN and backing a NANDroid Backup. Then flashed KitKat CM 11 from CWM (wanted to try it out but didn't like it more than Jellybean). So I restored my backup via custom recovery.
Then I tried unlocking the sim network from T-mobile so I can use this phone when I travel abroad (using the method in http://forum.xda-developers.com/showthread.php?t=2255892 ). But apparently I found this doesn't work except on the stock Ice Cream Sandwich rom. So I flashed the LH1 stock rom using ODIN. Then I did the unlock method and it appeared successful. (it recognized an AT&T sim I have without asking for an unlock code)
So long story short, I used the custom recovery again to restore to my stock version of 4.1.2 Jellybean. But my baseband version is still LH1. I want to update it to UVMA2. I tried using a zip to update it from LH1 to UVMA2. But it always fails and aborts. It gives me Error Status 7. Which from google apparently means the device name doesn't match the one on the zip package.
I also try installing other minor packages. Which all incur the same error 7. So I'm not really sure if I'm just a really stupid beginner. Or if I've messed something up when I went to Kitkat and back. Or perhaps when I downgraded to 4.0 to unlock the network....
I tried using this ( http://forum.xda-developers.com/showthread.php?t=2302599 ) guide to fix the packages by removing the initial device name check. Yet it still fails/aborts before trying to install.
Any help or insights for this beginner would be greatly appreciated, thank you
Edit: The device name should be "apexqtmo" apparently...
Was able to flash to UVBMC5 baseband. Is that perhaps the latest version? It appears to be one of the most recent from google.

Unable to get OTA Updates installed on TWRP - Need to go back to stock recovery

Hi All,
Background:
Installed TWRP recovery to downgrade to KitKat from Android ver 5.0.2 / COS 12.0 YNg1TAS17L
( I guess the changes in lollipop made me to do so).
But after installing TWRP, for some reason or other I did nothing and now the issue is the OTA are not getting installed. From other similar thread I know that we can download the OTA zip and install through TWRP and I am not looking to get into that...as I am giving this device to my family.
Help Required:
1) Is there a way to uninstall TWRP and go back to stock recovery without losing any data?
( Is it as simple as flashing recovery image from the Stock ROM?)
2) Using the OnePlus tool kit can we flash the stock ROM which will also restore the stock recovery?
(If so is it possible to flash the latest ROM 5.1.1 or CM12.1)
I just need guidance here with steps on what will be the best and safe approach without frying up my device.
Please suggest
droidfry said:
Hi All,
Background:
Installed TWRP recovery to downgrade to KitKat from Android ver 5.0.2 / COS 12.0 YNg1TAS17L
( I guess the changes in lollipop made me to do so).
But after installing TWRP, for some reason or other I did nothing and now the issue is the OTA are not getting installed. From other similar thread I know that we can download the OTA zip and install through TWRP and I am not looking to get into that...as I am giving this device to my family.
Help Required:
1) Is there a way to uninstall TWRP and go back to stock recovery without losing any data?
( Is it as simple as flashing recovery image from the Stock ROM?)
2) Using the OnePlus tool kit can we flash the stock ROM which will also restore the stock recovery?
(If so is it possible to flash the latest ROM 5.1.1 or CM12.1)
I just need guidance here with steps on what will be the best and safe approach without frying up my device.
Please suggest
Click to expand...
Click to collapse
Numerous other threads on the same subject... I don't understand why you are not ready to flash the OTA through TWRP but you are through stock recovery... It's the same thing... Don't use toolkit, they are the ones, in 99% of the cases, that "fry" your phone... As soon as TWRP is installed no OTA will automatically, you will have to flash them manually.

Soft Brick -> Stock Firmware -> TWRP -> Custom ROM -> Bootloop

Hey, so i formatted the boot partition by accident today and could not boot anymore.
I was on a 5.1.1 Custom ROM before that. So i googled a bit and found a fix by flashing the Stock Firmware. Downloaded a 4.4.4 Stock Firmware here (RETAIL-DE) and flashed it using the commands here (as described in 3b). The second command failed with "Preflash validation failed". I believe thats because i had bootloader version 4.1.19 already and its not possible to flash an older one over that.
After that i could boot the phone again into the Stock Android 4.4.4. So i wanted to go back to an Lollipop or Marshmallow ROM. Using fastboot i flashed the latest TWRP Recovery and used it to flash a Custom ROM. I've tried several ROMs but every ROM results in an bootloop. Also tried using TWRP 2.6.0.0 and 2.7.0.0, but it didnt change sth.
I hope someone can help me solving this issue. Thanks.
You should probably full-flash the latest original Motorola firmware (GPE 5.1 or stock 5.0.2) before putting TWRP and custom roms based on Android L or M.

Categories

Resources