[Q] T-mobile LG G2 TWRP won't install CM11 ROM - T-Mobile LG G2

Hi Guys,
Urgent issue. I rooted the device using Kingo, installed TWRP and then transferred the zip for the CM11 nightly and the gapps. I confirmed the nightly was for the D801 model which is T-mobile and the version of the G2 I have. Like a fool I forgot to backup my previous rom and TWRP says:
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11-20140208-NIGHTLY-d801.zip'
Error flashing zip '/sdcard/cm-11-20140208-NIGHTLY-d801.zip'
Updating partition details
And there's a red ominous 'Failed' at the bottom of the prompt. Please help, I have no idea what to do, I'm a noob at this. Help is greatly appreciated, thank you!
Regards

mysticgohan_92 said:
Hi Guys,
Urgent issue. I rooted the device using Kingo, installed TWRP and then transferred the zip for the CM11 nightly and the gapps. I confirmed the nightly was for the D801 model which is T-mobile and the version of the G2 I have. Like a fool I forgot to backup my previous rom and TWRP says:
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11-20140208-NIGHTLY-d801.zip'
Error flashing zip '/sdcard/cm-11-20140208-NIGHTLY-d801.zip'
Updating partition details
And there's a red ominous 'Failed' at the bottom of the prompt. Please help, I have no idea what to do, I'm a noob at this. Help is greatly appreciated, thank you!
Regards
Click to expand...
Click to collapse
Can you restore the phone and boot back up? If so, replace TWRP with Philz Touch CWM. I had trouble flashing kit kat rom with TWRP too. But Philz Touch recovery seems to works just fine and it also has the option with restore a backup from TWRP too.

super114 said:
Can you restore the phone and boot back up? If so, replace TWRP with Philz Touch CWM. I had trouble flashing kit kat rom with TWRP too. But Philz Touch recovery seems to works just fine and it also has the option with restore a backup from TWRP too.
Click to expand...
Click to collapse
Hi, thanks for your reply. I have resolved all issues. Turns out you need TWRP 2.6.3.5 to flash any CM11 nightlies. Also was using Windows 8.1 so the adb drivers were not straightforward to install to use adb push. I pushed and installed TWRP 2.6.3.5 and then flashed CM11 and she works like a dream!

Related

[Q] stuck on TWRP 2.5.0.0 + cannot install cm11

lets get down to business,
I'm currently running CM10.2.0 with TWRP 2.5.0.0 as recovery, I recently tried updating to latest CM11 M4 snapshot but received the following error:
"error executing updater binary"
I read that i need to update recovery (2.6.3.0 latest) but encountered a roadblock.
I downloaded the .img to internal memory in root directory and used the terminal emulator as per TWRP instructions, rebooted into recovery but it still showed 2.5.0.0. I then tried using ADB but ran into the same issue
I've thought about using CWM but when I install ROM toolbox it says only tf200 is officially supported.
lastly tried Goomanager but it gave me an error saying recovery not found.
any thoughts on this?
any ideas would be appreciated
ok, tried a different version of TWRP (4.2 as opposed to JB) and it worked though cm11 still wont flash
n00b1c1d3 said:
ok, tried a different version of TWRP (4.2 as opposed to JB) and it worked though cm11 still wont flash
Click to expand...
Click to collapse
What is your bootloader version is it 10.1.6.27.x
The last digit really does not matter...
If so you need this recovery here http://forum.xda-developers.com/showthread.php?t=2691886
Let me know if I can help you with anything else..
Thx Josh
ended up using that method and all went well.
thanks

ROM installation problems

I've been flashing ROMs, recoveries etc for years on every android device I've had, from Samsung to nexus, HTC. Everything. This is my first Motorola and I'm having a lot of problems.
Unlocked the boot loader, flashed TWRP but wouldn't backup my stock ROM so put on Pholz recovery and it wouldn't backup either.
Tried to install C-Rom after the usual wipes and just sticks at boot screen. Tried Tweakone ROM I think its called and same problem.
Any ideas? I have the XT1032
I know about restoring to factory but what I'm asking is, is there anything specific I'm doing wrong? I'm quite an experienced flasher. Research is showing me how to recover the phone but what's gonna stop it happening again
Sent from my Nexus 5 using Tapatalk
A lot of users report issues not being able to flash rom's on 4.4.2 kitkat.
A fix is to downgrade to 4.3, then flash roms.
I dont know why. I bought my device upgraded to 4.4.2 already, and i can flash roms with no issues.
Search the forum for the topic and you will find the info you need.
Roshi69 said:
I've been flashing ROMs, recoveries etc for years on every android device I've had, from Samsung to nexus, HTC. Everything. This is my first Motorola and I'm having a lot of problems.
Unlocked the boot loader, flashed TWRP but wouldn't backup my stock ROM so put on Pholz recovery and it wouldn't backup either.
Tried to install C-Rom after the usual wipes and just sticks at boot screen. Tried Tweakone ROM I think its called and same problem.
Any ideas? I have the XT1032
I know about restoring to factory but what I'm asking is, is there anything specific I'm doing wrong? I'm quite an experienced flasher. Research is showing me how to recover the phone but what's gonna stop it happening again
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It wont backup saying what error?
Twrp just said 'failed' in red writing after the data backup I think. And philz touch said something along the lines of Not being able to write a file into the \clockworkmod folder.
I bought the device with 4.4.2 on it and followed the guides after reading up about the problems etc but TWRP 2.7.0.0 had a lot of reports that everything was working on it so went ahead with it
Sent from my Nexus 5 using Tapatalk
Ya that's strange because philz works great for me. Do you have a USB otg to try an external backup?
Sent from my XT1032 using Tapatalk
I got the phone booted again by following a guide and flashing a stock rom.
Installed Philz recovery again and still getting the backup error. it says: E: Error while backing up boot image!
So understandably i am now scared to flash another rom in case i get a boot loop again.
*update* Strangely i flashed TWRP via CWM, rebooted into TWRP 2.7.0.0 and performed a backup successfully.
Roshi69 said:
I got the phone booted again by following a guide and flashing a stock rom.
Installed Philz recovery again and still getting the backup error. it says: E: Error while backing up boot image!
So understandably i am now scared to flash another rom in case i get a boot loop again.
*update* Strangely i flashed TWRP via CWM, rebooted into TWRP 2.7.0.0 and performed a backup successfully.
Click to expand...
Click to collapse
Why dont you use Clockwork mod recovery for flashing Rom. I have flashed 10 Roms with that and all are backed up with out any problems. TWRP has no official support for moto g, and instead of all that why don't you try Cyanogenmod ?
(sorry if my english is not perfect)
Hello,
I have exactly the same problem with my XT1032.
Bootloader unlocked, CWM (6.0.4.7) successfully installed and backup done with no issues.
But custom roms won't load...
CM11 is stuck at "bootloader unlocked warning screen" and SlimKat is stuck at slimkat logo.
I never had such problems on my Nexus..
Please help me, I don't know what's going on
TheSkweed said:
I have exactly the same problem with my XT1032.
Bootloader unlocked, CWM (6.0.4.7) successfully installed and backup done with no issues.
But custom roms won't load...
CM11 is stuck at "bootloader unlocked warning screen" and SlimKat is stuck at slimkat logo.
Click to expand...
Click to collapse
Same here. It may be possible to downgrade to 4.3 (see here), but would it then be possible to flash a 4.4.2-based custom ROM ? I'm not sure.
Heres the steps I took.
*******Before device was stuck at bootloop*******
1. Bought phone (XT1032)
2. unlocked boot loader
3. Rooted
4. Flashed Philz Recovery (wouldn't backup rom)
5. Flashed TWRP and CWM with same issue.
6. Flashed 2 ROMs to try it (TweakyOne + C-Rom, Both wouldn't boot. and tried on all recoveries.
********Steps after being stuck at bootloop*******
1. Followed this amazing guide here (https://www.youtube.com/watch?v=laU6NQ0LxR0)
2. Set up the stock ROM again
3. Flashed TWRP 2.7.0.0 via Fastboot
4. Backup worked successfully
5. installed CM11 and setup successfully
6. installed Lego rom just to assure myself (currently running this ROM)
I know this is no solution at all but just wanted to share my steps to see what maybe fixed my phone. possibly the stock 4.2.2 rom I flashed was the solution. Maybe the original factory ROM that came on the phone was the issue?

[Q] unable to flash anyrom after kitkat port

Hi there,
I flashed a KitKat port to test it. However, I decided to go back to Cyanogenmod since it didn't work very well.
However, any ROM that I try to flash appears this error:
format() expects 5 args, got 3
E: Error in /storage/sdcard0/cm-7.2.0-p500.zip
(Status 7)
Installation aborted
what can I do to fix this? thanks
Athosbr99 said:
Hi there,
I flashed a KitKat port to test it. However, I decided to go back to Cyanogenmod since it didn't work very well.
However, any ROM that I try to flash appears this error:
format() expects 5 args, got 3
E: Error in /storage/sdcard0/cm-7.2.0-p500.zip
(Status 7)
Installation aborted
what can I do to fix this? thanks
Click to expand...
Click to collapse
To flash that KitKat, you had to place a newer CWM or TWRP recovery version.
To flash cm-7.2, you need to go back to the older recovery!
For KitKat ROMs a recovery equivalent to 6.0.4.5 or newer is required to flash. The newer recoveries are capable of flashing CM 10.2 to CM11. All older Android versions will require the use of an older recovery, pre 6.0.4.5, such as CWM 5.0.2.7 Touch by vivekkalady.
Dovidhalevi said:
To flash that KitKat, you had to place a newer CWM or TWRP recovery version.
To flash cm-7.2, you need to go back to the older recovery!
Click to expand...
Click to collapse
shinobisoft said:
For KitKat ROMs a recovery equivalent to 6.0.4.5 or newer is required to flash. The newer recoveries are capable of flashing CM 10.2 to CM11. All older Android versions will require the use of an older recovery, pre 6.0.4.5, such as CWM 5.0.2.7 Touch by vivekkalady.
Click to expand...
Click to collapse
nice to know that. I will try later
In other subject, I tried other kitkat roms and they gave me that same error. the only one that worked was Omega. is there any reason to that?
Athosbr99 said:
nice to know that. I will try later
In other subject, I tried other kitkat roms and they gave me that same error. the only one that worked was Omega. is there any reason to that?
Click to expand...
Click to collapse
Sorry, I honestly can't say. I no longer use this device so I've been out of the loop for some time now.
Also having same problem
Can't Flash anyother rom after kitkat port.
plz help me.
Thanks
DevG said:
Can't Flash anyother rom after kitkat port.
plz help me.
Thanks
Click to expand...
Click to collapse
Have you installed any custom kernel?
I am also faced this problem and solved by flashing stock rom with KDZ

Problems flashing KatKiss 5.1_030c ROM

I am running an Asus TF101 B90 tablet. I have just rooted and installed KatKiss 4.4.4_036. I am using ClockworkMod v 3.2.0.1 roach2010-tf101-r1 for recovery. This appears to work fine. I have tried the defined step,s both before and after flashing the 4.4.4 ROM, to flash the 5.1 ROM without success. I have tried this with both a full wipe and without. The results are always the same. After it starts the install the system gives me the following error messages:
Set_metadata_recursive: some changes failed
E:Error in /sdcard/KatKiss-5.1_030.zip
(Status 7)
Installation aborted
I have the same issue with KatKiss-5.1_030c.zip. Yesterday was the first time I rooted an android device. Any recommendations on what and how I need to change things so I can move to Lollipop? Thanks.
John
jdwbmc said:
I am running an Asus TF101 B90 tablet. I have just rooted and installed KatKiss 4.4.4_036. I am using ClockworkMod v 3.2.0.1 roach2010-tf101-r1 for recovery. This appears to work fine. I have tried the defined step,s both before and after flashing the 4.4.4 ROM, to flash the 5.1 ROM without success. I have tried this with both a full wipe and without. The results are always the same. After it starts the install the system gives me the following error messages:
Set_metadata_recursive: some changes failed
E:Error in /sdcard/KatKiss-5.1_030.zip
(Status 7)
Installation aborted
I have the same issue with KatKiss-5.1_030c.zip. Yesterday was the first time I rooted an android device. Any recommendations on what and how I need to change things so I can move to Lollipop? Thanks.
John
Click to expand...
Click to collapse
You need to install a recent recovery
See the link in the 1st post of the rom installation instructions
Thanks!
timduru said:
You need to install a recent recovery
See the link in the 1st post of the rom installation instructions
Click to expand...
Click to collapse
Tim,
First of all thanks so much for your work keeping the ASUS TF101 alive and working! It means a great deal. I did flash the TWRP 2.8.1 recovery system. That worked fine. I was then able to flash the KatKiss-5.1_030c ROM. I am now running Lollipop 5.1.1! Two questions. I ran Root Checker Basic. It can no longer validate that I am rooted, though it could when I ran 4.4.4. Is this to be expected or is there something I need to fix? Secondly, Lollipop seems a bit slower than 4.4.4. Is this to be expected or is there something I need to change to up performance? Thanks.
John

Latest TWRP not working

Hello guys,
I have a p5113 tablet that i have been having trouble with. I have tried flashing like 5 different roms and they all boot loop. I think its because I am using an old recovery (Device Specific TWRP 3.0.0-0) the problem is only the old recoveries are working for me. When i flash the latest common TWRP (3.0.3-0) Wiping gets stuck at updating partition details, it wont install any roms it stays at "detected filesystem ext4", and if I try to reset the tablet through TWRP menu it wont do anything. When I use the old recoveries it flashes and wipes fine. When i flash stock rom through odin, the system works fine. I have tried different versions of the latest twrp but to no avail. Thank you in advance for your help.
EDIT: I finally have a custom rom working on this tablet, it is Dhollmen stock 4.2.2 with GT-P5110_PhilZ-Touch-Recovery_6.59.2. recovery, device specific TWRP 3.0.0-0 would give me error 7. Im very happy but I would like to get Marshmallow on this tablet if anyone can help with that.
Install the 3.0.3-0 common TWRP, then try to format data (Wipe ->Format Data-> type yes). Reboot recovery once and then perform a wipe of all partitions (Wipe->Advanced Wipe-> select everything). If you get stuck at "updating partition details..." just wait. It could take as long as five minutes some times to get unstuck.
This is the link for the thread of Slim6, the mm rom I recommend by Andi:
https://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-slim6-t3414798/page1
And this is an aosp mm rom also by Andi, try it if above fails
http://builds.unlegacy-android.org/aosp-6.0
Flash both with TWRP 3.0.3-0
If problems continue, post the recovery log (you can find it after reboot at /cache/recovery/ )
landetta said:
Hello guys,
I have a p5113 tablet that i have been having trouble with. I have tried flashing like 5 different roms and they all boot loop. I think its because I am using an old recovery (Device Specific TWRP 3.0.0-0) the problem is only the old recoveries are working for me. When i flash the latest common TWRP (3.0.3-0) Wiping gets stuck at updating partition details, it wont install any roms it stays at "detected filesystem ext4", and if I try to reset the tablet through TWRP menu it wont do anything. When I use the old recoveries it flashes and wipes fine. When i flash stock rom through odin, the system works fine. I have tried different versions of the latest twrp but to no avail. Thank you in advance for your help.
EDIT: I finally have a custom rom working on this tablet, it is Dhollmen stock 4.2.2 with GT-P5110_PhilZ-Touch-Recovery_6.59.2. recovery, device specific TWRP 3.0.0-0 would give me error 7. Im very happy but I would like to get Marshmallow on this tablet if anyone can help with that.
Click to expand...
Click to collapse
have you used the twrp on the http://andi34.github.io/ website? and roms compiled before 3/22/16 dont flash with common twrp when I updated twrp I had downloaded the zip and went into twrp to flash it I havent used a pc at all to install twrp and root . so I just put the zip on my sd card and it updated it did you update twrp with odin?
Thank you for your reply,
Yes I used the recoveries from Android Andi, and yes I have installed recoveries in zip form through recovery and Odin. Unfortunately neither have worked. I did use the latest recoveries when I tried to install the newer roms but it just gets stuck, I can't even make nandroid backups it also gets stuck with the newer recoveries.
Edit:
@ john99ap Sorry i just got home, I tried what you said but it just got stuck at both wipes, I waited 10 mins but a no-go. I found the logs, I couldn't paste them in here because it exceeded character length so I put it in pastebin. I didn't know which log to use so I am giving you the ones that I think are more relevant
Log:
pastebin/gpWgBEm7
Last_log:
pastebin/12uLYgwS
Last_log.10
pastebin/asePpLBa
Thank you guys again for your help!
landetta said:
Log:
pastebin/gpWgBEm7
Last_log:
pastebin/12uLYgwS
Last_log.10
pastebin/asePpLBa
Thank you guys again for your help!
Click to expand...
Click to collapse
I can't find anything in these logs
I need the log in which you try to install the zip file.
Try this:
-Install TWRP 3.0.3-0 (if it's not already there)
-Reboot and delete all recovery logs you can find
-Install the zip without doing anything else before or after so that the log is as clean as possible
-Post any log you find
PS: you could upload logs in your reply by hitting the button with a stapler on the bottom left corner
Thanks for your reply, sorry about the old logs, here are the new ones like you requested. Hopefully you find something in these new ones. Thanks again for all your help BTW I don't have any staples in my advanced reply so I had to use Pastebin again sorry. I think its because of my low post count.
pastebin/UcntGLTZ
pastebin/Fq8V7WUf
PS: Not even the reboot button works on 3.0.3-0.
Sorry but I can't find anything in these logs either. Maybe it's my fault since I 'm not an expert
At your first post you said device specific twrp gives you error 7. This is caused by a safety check in which your recovery checks if your device is compatible with the rom. In your case, it must be a mistake of the recovery (I had the same issue with my p3110 device specific twrp). So you could just remove the safety check.
Here's how to do it:
- Go to the zip you want to install and find the file /META-INF/com/google/android/updater-script
-Edit it with a text editor and remove the first line (it begins with asserts and ends at the first semicolon)
-Install the zip
Good luck!
john99ap said:
Sorry but I can't find anything in these logs either. Maybe it's my fault since I 'm not an expert
At your first post you said device specific twrp gives you error 7. This is caused by a safety check in which your recovery checks if your device is compatible with the rom. In your case, it must be a mistake of the recovery (I had the same issue with my p3110 device specific twrp). So you could just remove the safety check.
Here's how to do it:
- Go to the zip you want to install and find the file /META-INF/com/google/android/updater-script
-Edit it with a text editor and remove the first line (it begins with asserts and ends at the first semicolon)
-Install the zip
Good luck!
Click to expand...
Click to collapse
Awe thanks anyways dude, I really appreciate you trying. One last thing, on Andi's website he say that device specific 3.0.0-0 recovery should work to flash the latest roms. If anyone can confirm this maybe I can get the new roms working on it. Thanks again for all your help john99ap :good:

Categories

Resources