Database Develop

Bricked XT1072

Hi Guys,
I stupidly did not realise my device (XT1072) was a different slightly different model to the moto g 2014.
I unlocked the bootloader and installed TWRP, then tried to install Cyanogenmod 12.1, this failed giving an error "Error executing updater binary in zip" Which I guess is due to it being a different model, right? After receiving this error I did some googling and found on a few sites that I should wipe data, system, cache & dalvik cache to resolve this. I did this and tried to flash it again, with the same error. Now my phone is stuck on the "warning bootloader unlocked screen" I can boot into fastboot mode, but is there any official Motorola images for my device anywhere? I have had a look online and cant find anything. :crying:
Any help would be much appreciated.
Thanks

Format system is completely wipe previous android version,
You need a custom ROM (I'm assuming you have custom recovery for your device model)
Or fastboot a original image for you're device

Hi
ohmygoddude said:
Hi Guys,
I stupidly did not realise my device (XT1072) was a different slightly different model to the moto g 2014.
I unlocked the bootloader and installed TWRP, then tried to install Cyanogenmod 12.1, this failed giving an error "Error executing updater binary in zip" Which I guess is due to it being a different model, right? After receiving this error I did some googling and found on a few sites that I should wipe data, system, cache & dalvik cache to resolve this. I did this and tried to flash it again, with the same error. Now my phone is stuck on the "warning bootloader unlocked screen" I can boot into fastboot mode, but is there any official Motorola images for my device anywhere? I have had a look online and cant find anything. :crying:
Any help would be much appreciated.
Thanks
Click to expand...
Click to collapse
Hi,
I am facing exactly the same problem here. Could you please let me know if you find any solution!!! please
Thanks

omarhowlader said:
Hi,
I am facing exactly the same problem here. Could you please let me know if you find any solution!!! please
Thanks
Click to expand...
Click to collapse
You might want to take a look at this thread: http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303

omarhowlader said:
Hi,
I am facing exactly the same problem here. Could you please let me know if you find any solution!!! please
Thanks
Click to expand...
Click to collapse
Hi,
I too faced this issue. I've seen this error mostly with the Team Win Recoveries(TWRP). Switch to philiz recovery touch.

Still no luck
kishorebvs said:
Hi,
I too faced this issue. I've seen this error mostly with the Team Win Recoveries(TWRP). Switch to philiz recovery touch.
Click to expand...
Click to collapse
Hi,
Thank you for your reply. I also tried with CWM_Touch_Titan_v2 recovery image. But when I tried to flash the stock rom RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml using mfastboot method, it shows on the phone screen "image too large".
As you have faced the same problem, would you be kind enough to give a step by step instruction to solve the issue. My phone is just stuck to unlocked bootloader warning screen for days.
My phone is Moto g XT1072 4G LTE.
Your help could save my days...
Thanks.

omarhowlader said:
Hi,
Thank you for your reply. I also tried with CWM_Touch_Titan_v2 recovery image. But when I tried to flash the stock rom RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml using mfastboot method, it shows on the phone screen "image too large".
As you have faced the same problem, would you be kind enough to give a step by step instruction to solve the issue. My phone is just stuck to unlocked bootloader warning screen for days.
My phone is Moto g XT1072 4G LTE.
Your help could save my days...
Thanks.
Click to expand...
Click to collapse
Why are u flashing an xml file? XML files are not rom files
The link provided above by mic_he has step by step instructions to restore phone back to stock
Your phone is not bricked. You deleted your system so there is no os to boot. The link should restore you back to stock

mic_he said:
You might want to take a look at this thread: http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
Click to expand...
Click to collapse
Thank you,
I have tried those instruction earlier. when I enter "mfastboot flash bootloader bootloader.img" is says "Bootloader preflash validation failed" and when I enter "mfastboot flash system system.img_sparsechunk.0" onthe phone screen is says "Image too large". After going through all the steps when I reboot, it does not ever get past unlocked bootloader warning screen.
I really do not know which other option to try??
---------- Post added at 07:30 PM ---------- Previous post was at 07:26 PM ----------
Moto G User said:
Why are u flashing an xml file? XML files are not rom files
The link provided above by mic_he has step by step instructions to restore phone back to stock
Your phone is not bricked. You deleted your system so there is no os to boot. The link should restore you back to stock
Click to expand...
Click to collapse
I could not find any zip file of the stock rom. I downloaded the stock rom from that link but I am having error as i posted earlier.
Thanks

ohmygoddude said:
Hi Guys,
I stupidly did not realise my device (XT1072) was a different slightly different model to the moto g 2014.
I unlocked the bootloader and installed TWRP, then tried to install Cyanogenmod 12.1, this failed giving an error "Error executing updater binary in zip" Which I guess is due to it being a different model, right? After receiving this error I did some googling and found on a few sites that I should wipe data, system, cache & dalvik cache to resolve this. I did this and tried to flash it again, with the same error. Now my phone is stuck on the "warning bootloader unlocked screen" I can boot into fastboot mode, but is there any official Motorola images for my device anywhere? I have had a look online and cant find anything. :crying:
Any help would be much appreciated.
Thanks
Click to expand...
Click to collapse
Unmounting system before flashing usually stops that problem. What I like to do is wipe data, system, cache & dalvik then reboot to recovery before flashing the rom.
Sent from my GT-P5210 using Tapatalk

could you solve the problem with the XT1072?
hello sir! could you solve the problem with thw XT1072? Can you give me some instructions? cheers

It works!!!!! I could restore my system back with these steps!
Here´s the info
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
I followed the steps and when I was triyng to Flash each of the partitions in sequence using mfastboot get an error
I get an error with one of the files, (don´t remember now but I think was with the mfastboot flash logo logo.bin line
This give me an error, try to fix it and i couldn´t so I continue with the other files in the order listed and when the process was finished the phone was working again!!!!

Enter twrp recovery
Wipe system data cache dalvik
Put any rom like cm in microsd card or usb
And flash it using twrp

ohmygoddude said:
Hi Guys,
I stupidly did not realise my device (XT1072) was a different slightly different model to the moto g 2014.
I unlocked the bootloader and installed TWRP, then tried to install Cyanogenmod 12.1, this failed giving an error "Error executing updater binary in zip" Which I guess is due to it being a different model, right? After receiving this error I did some googling and found on a few sites that I should wipe data, system, cache & dalvik cache to resolve this. I did this and tried to flash it again, with the same error. Now my phone is stuck on the "warning bootloader unlocked screen" I can boot into fastboot mode, but is there any official Motorola images for my device anywhere? I have had a look online and cant find anything. :crying:
Any help would be much appreciated.
Thanks
Click to expand...
Click to collapse
Hi, I have facing this problem too on my XT1063. My phone do boot to system but all the app are getting FCs, so I decided to flash another ROM like usual and All of this give me that "Error executing updater binary in zip", so I trie to wipe AND format all partition from TWRP and FASTBOOT with no success. Via Fastboot says: "File system type raw not supported." So I cant change to a new ROM, I cannot even flash other recovery....
So if you guys find a solution of this problem very users like me will be very thankful.

"Device failed verification" error on boot?

Flashed the M preview two days ago, working completely fine. I rebooted the phone for some reason, and there was an error right after the Google screen stating "Your device has failed verification and may not work properly"
I know people have been getting this, but I haven't seen anything on how to get rid of it. The phone still boots and operates fine after the message started popping up, but its a bit annoying. I thought if I just formatted all the partitions on my phone that would go away. Apparently not. After formatting in TWRP, I wanted to see if that would pop up even after I wiped everything, and it does.
Does anybody know how to get rid of this error?

RealROGWaffle said:
Flashed the M preview two days ago, working completely fine. I rebooted the phone for some reason, and there was an error right after the Google screen stating "Your device has failed verification and may not work properly"
I know people have been getting this, but I haven't seen anything on how to get rid of it. The phone still boots and operates fine after the message started popping up, but its a bit annoying. I thought if I just formatted all the partitions on my phone that would go away. Apparently not. After formatting in TWRP, I wanted to see if that would pop up even after I wiped everything, and it does.
Does anybody know how to get rid of this error?
Click to expand...
Click to collapse
its a normal m error. flash a custom kernel to get rid of it. despair has one, elite has another, and there are more out there.

RealROGWaffle said:
Flashed the M preview two days ago, working completely fine. I rebooted the phone for some reason, and there was an error right after the Google screen stating "Your device has failed verification and may not work properly"
I know people have been getting this, but I haven't seen anything on how to get rid of it. The phone still boots and operates fine after the message started popping up, but its a bit annoying. I thought if I just formatted all the partitions on my phone that would go away. Apparently not. After formatting in TWRP, I wanted to see if that would pop up even after I wiped everything, and it does.
Does anybody know how to get rid of this error?
Click to expand...
Click to collapse
This error is often a result of system/bootloader mismatch. Do you have 5.1.1 with M bootloader?

simms22 said:
its a normal m error. flash a custom kernel to get rid of it. despair has one, elite has another, and there are more out there.
Click to expand...
Click to collapse
Awesome, thank you very much.

cam30era said:
This error is often a result of system/bootloader mismatch. Do you have 5.1.1 with M bootloader?
Click to expand...
Click to collapse
Nope, running M with the M bootloader.

Did you flash TWRP recovery or the M (factory) recovery?
If TWRP, did you allow it to try and flash SU?
I didn't have that error until flashing TWRP and allowing it to try and root upon exiting TWRP.
I was a able to clear it by flashing a different kernel, booting to TWRP, and wiping caches (I didn't do a Factory Reset).

jasoraso said:
Did you flash TWRP recovery or the M (factory) recovery?
If TWRP, did you allow it to try and flash SU?
I didn't have that error until flashing TWRP and allowing it to try and root upon exiting TWRP.
I was a able to clear it by flashing a different kernel, booting to TWRP, and wiping caches (I didn't do a Factory Reset).
Click to expand...
Click to collapse
everyone who flashed m without a separate kernel got that error. its a m thing for now.

my phone wont boot up after it flashes that.. dont know what to do..

dave2metz said:
my phone wont boot up after it flashes that.. dont know what to do..
Click to expand...
Click to collapse
what did you flash? .img files or via twrp flashable zip? did you flash the bootloader? you have to or it won't ever boot.

simms22 said:
what did you flash? .img files or via twrp flashable zip? did you flash the bootloader? you have to or it won't ever boot.
Click to expand...
Click to collapse
My device keeps flashing as well. I fastboot .img files

I only had this error when I flashed twrp. When I was stock M and no twrp didn't have this issue

md1008 said:
I only had this error when I flashed twrp. When I was stock M and no twrp didn't have this issue
Click to expand...
Click to collapse
Same... flashing twrp kills my M install. Say's it's booting but all I get is a black screen.

Now it's my turn to join. Any fixes for those that won't boot up at all? I think I may have a brick. How did you get out of this?

sbrownla said:
Now it's my turn to join. Any fixes for those that won't boot up at all? I think I may have a brick. How did you get out of this?
Click to expand...
Click to collapse
you have to flash the m bootloader before flashing m, or it will never boot up.

How to flash Android M, TWRP, & SuperSU with out getting red corrupt triangle @ boot?

How to flash Android M, TWRP, & SuperSU with out getting red corrupt triangle @ boot?
Is there a method to flash Android M with TWRP and supersu that will work with out giving the red triangle stating the device is corrupt at boot?
Thanks

I wonder the same thing. I tried to get rid of the red triange but it's impossible. I've tried a full wipe and flash everything from stock but no dice.
Also i'm unable to boot to recovery. It just freezes... Same thing if I flash back the 5.1.1 image. TWRP is working though.
Any ideas?

Does anyone have a solution to get rid of the triangle WITHOUT twrp or root? I flashed TWRP to see if I could install a custom HOSTS file and the message started popping up on boot, but even after reflashing everything from the official M image and wiping data and cache it still pops up. Any suggestions? o_o

Did you flash userdata too? Tried factory reset on top?

pszyman said:
Did you flash userdata too? Tried factory reset on top?
Click to expand...
Click to collapse
I formatted userdata because I have a 64GB device and the userdata image included is for 32GB. this is what I did without the file names because I'm mobile:
Code:
Fastboot flash bootloader mboot.img
Fastboot reboot-bootloader
Fastboot flash mradio.img
Fastboot flash system msystem.img
Fastboot flash boot mboot.img
Fastboot flash recovery mrecovery.img
Fastboot format userdata
Fastboot format cache
And then I booted and got the device corrupt message. I did all of that a few times to make sure I didn't miss anything and I have no idea what it's detecting as modified. I haven't tried factory resetting from the device itself, I figured formatting userdata would be enough but ill try that tomorrow unless anyone has other ideas.

I had this same issue today too after I flashed twrp. The only way to resolve it was to flash stock and unroot using nexus toolkit to a lollipop stock image. In time I'm sure it will be a smoother process to go to android m with twrp and root, but until then, I'm sticking with lollipop.
Sent from my Nexus 6 using Tapatalk

530farm said:
Is there a method to flash Android M with TWRP and supersu that will work with out giving the red triangle stating the device is corrupt at boot?
Thanks
Click to expand...
Click to collapse
Experienced this too, until I found this article that shows different TWRP, SuperSU, etc versions.
http://wccftech.com/root-nexus-6-android-60-mra58k-marshmallow/
I flashed it without the errors.
Hope it works for you. After a few minutes of Marshmallow I went back to Fusion 6.0 which was a bit more features based on CM12.1. I just got the Shamu yesterday coming from OnePlusOne running SultanXDA's CM CAF.

Well, the issue is this corrupted message stays even after the full stock reinstall. Some say it went away after the factory reset but returned back after a while later, after spontaneous reboot or so.

thanks the dispair kernel worked with twrp 2.8.7.1 and su 2.49 beta.
now i have no more corrupt and i am rooted and not encrypted
thanks

What I've done to get back to stock was - flash clean image and next factory reset. No corrupted message. So far so good.

I believe to get rid of it...you will have to lock and unlock bootloader again...which will factory reset in the process. Hopefully someone finds a workaround for a factory reset...I am going to continue to run it with the error message until someone does. I dont want to factory reset. The message doesnt cause any issues to my knowledge...its just a warning to the user.

dansoh said:
Experienced this too, until I found this article that shows different TWRP, SuperSU, etc versions.
http://wccftech.com/root-nexus-6-android-60-mra58k-marshmallow/
I flashed it without the errors.
Hope it works for you. After a few minutes of Marshmallow I went back to Fusion 6.0 which was a bit more features based on CM12.1. I just got the Shamu yesterday coming from OnePlusOne running SultanXDA's CM CAF.
Click to expand...
Click to collapse
kidhudi said:
thanks the dispair kernel worked with twrp 2.8.7.1 and su 2.49 beta.
now i have no more corrupt and i am rooted and not encrypted
thanks
Click to expand...
Click to collapse
I have confirmed this works. I had the "Device is Corrupt" message non-stop. Basically go to that link and download all the stuff.
Have TWRP install.
From TWRP install the Despair.R20.6.Shamu.zip
then flash BETA-SuperSU-v2.49.zip.
Reboot
PRESTO, Device Corrupt is GONE
I had tried Despair.M.CFS.R31.2.Shamu.UBER.zip and UPDATE-SuperSU-v2.46.zip before, which did not eliminate the Device is Corrupt Message

inspiron41 said:
I have confirmed this works. I had the "Device is Corrupt" message non-stop. Basically go to that link and download all the stuff.
Have TWRP install.
From TWRP install the Despair.R20.6.Shamu.zip
then flash BETA-SuperSU-v2.49.zip.
Reboot
PRESTO, Device Corrupt is GONE
I had tried Despair.M.CFS.R31.2.Shamu.UBER.zip and UPDATE-SuperSU-v2.46.zip before, which did not eliminate the Device is Corrupt Message
Click to expand...
Click to collapse
Which one makes the message go away though, the kernel or supersu? Or both? I wasn't looking to root my phone so at this point I'm just trying to get the message to go away lol
EDIT: Can confirm it's kernel related, just flashed a lollipop kernel and the message vanished but of course it bootlooped Lol.

I flashed the kernel from here http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958 and it went away.

PhantomGamers said:
Which one makes the message go away though, the kernel or supersu? Or both? I wasn't looking to root my phone so at this point I'm just trying to get the message to go away lol
EDIT: Can confirm it's kernel related, just flashed a lollipop kernel and the message vanished but of course it bootlooped Lol.
Click to expand...
Click to collapse
Custom kernels that have the flag edited out will will get rid of the Corrupt message.

djkinetic said:
Custom kernels that have the flag edited out will will get rid of the Corrupt message.
Click to expand...
Click to collapse
I guess I'll have to resort to that if factory resetting doesn't fix it, sucks though cuz I would have been happy with stock.

asus memo pad 7 (me176cx) "unable to mount /factory"

Hello, i have a bricked asus memo pad 7 (me176cx), when i try to install the factory firmware (UL-K013-WW-12.10.1.33-user.zip) the cwm and the twrp2 give me a error "unable to mount /factory" and i can't install the rom.
How can i fix that?
Thanks
PD: sorry for my caveman english (?)

kitsunezero said:
Hello, i have a bricked asus memo pad 7 (me176cx), when i try to install the factory firmware (UL-K013-WW-12.10.1.33-user.zip) the cwm and the twrp2 give me a error "unable to mount /factory" and i can't install the rom.
How can i fix that?
Thanks
PD: sorry for my caveman english (?)
Click to expand...
Click to collapse
Hello,
I have reported this thread to be moved to right Q&A inorder to get expertise help
-Vatsal

I never had to mount those partitions when installing that ROM when I bricked mine. I just wiped all caches and installed from zip. Are you doing this?

paulgiro said:
I never had to mount those partitions when installing that ROM when I bricked mine. I just wiped all caches and installed from zip. Are you doing this?
Click to expand...
Click to collapse
I'm a idiot http://forum.xda-developers.com/memo-pad-7/general/5-0-brick-solution-asus-memo-pad-7-t3134814,
I didn't read this "This package is for "K013" devices; this is a "K013_1"." I was bricked for a week because of a random device "name change?" Well here are the steps I took to make a flashable lollipop that wouldnt brick me. What you are doing here is telling the script that does the update that it does not need to verify your tablet model since it is wrong anyways.
Now i follow the steps and my tablet is boot, i'm waiting.
EDIT: Still bricked, now i can enter in fastboot mode but when i power on the tablet, after the logo, the screen is black

I have the same problem and can't find any solution yet :crying::crying:

sidane12 said:
I have the same problem and can't find any solution yet :crying::crying:
Click to expand...
Click to collapse
i can install the original firmware, but now still bricked with the same error

kitsunezero said:
i can install the original firmware, but now still bricked with the same error
Click to expand...
Click to collapse
try to format all partitions and shutdown, then boot into bootloader and load temp recovery and reflash .33 then boot android normally if still doesnt work, then reinstall once more but without wiping any partitions, if it decides to boot to bootanimation but its stuck there you need to simply make a reboot and then it should boot.

Ruben Craveiro said:
try to format all partitions and shutdown, then boot into bootloader and load temp recovery and reflash .33 then boot android normally if still doesnt work, then reinstall once more but without wiping any partitions, if it decides to boot to bootanimation but its stuck there you need to simply make a reboot and then it should boot.
Click to expand...
Click to collapse
how can i do that? can you make a tutorial please ><?

kitsunezero said:
how can i do that? can you make a tutorial please ><?
Click to expand...
Click to collapse
Load temp recovery select wipe, advanced wipe, format all, reboot to bootloader, load temp recovery, install, reboot normally, if it boots but its on bootloop just make another rebokt and itshould boot

Need help with Me176c, fastboot.... 123# screen

My Asus memo pad 7 is stuck on fastboot.... 123# screen. I've tried temporary recovery and had success installation with lineage-14.1 but nothing changed. Please help. Thanks.

Did you have Lollipop installed before?
Also, do I understand it correctly that you're able to get into the temp recovery session?

Yes lollipop was installed and rooted long time ago, after the issue I decided to put it away. I did loads after that though, so I don't think lollipop is still there.
It was first at boot screen, got this fastboot... 123# after I flashed a fastboot image. Flashed loads of recoveries, systems and boot images before and after the fastboot issue.
Hope this helps you understand the state it's in. Thanks for replying.

MJMJ7 said:
Yes lollipop was installed and rooted long time ago, after the issue I decided to put it away. I did loads after that though, so I don't think lollipop is still there.
It was first at boot screen, got this fastboot... 123# after I flashed a fastboot image. Flashed loads of recoveries, systems and boot images before and after the fastboot issue.
Hope this helps you understand the state it's in. Thanks for replying.
Click to expand...
Click to collapse
If the tablet boots into the screen with the 3 fastboot lines you are in DNX mode, which means you've likely messed up your bootloader. To restore the bootloader, follow the steps outlined in https://forum.xda-developers.com/showpost.php?p=73672837&postcount=5
If everything works, you should get to a second Fastboot screen with NORMAL BOOT etc. From there you can either start the temporary TWRP recovery session (see https://forum.xda-developers.com/showpost.php?p=73673438&postcount=7) to flash the Lollipop package you've downloaded earlier (UL-K013-WW-12.10.1.36-user.zip) or flash LineageOS.
If you want to flash LineageOS you need to unlock your bootloader. Download https://www.androidfilehost.com/?fid=312978532265362065, take the ESP.img from the ZIP and download https://github.com/me176c-dev/devic...recovery-3.1.1-20171119-UNOFFICIAL-me176c.img. Then run:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20171119-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20171119-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD).

I will try these steps and update you. Thank you very much.

O yes! It worked. Tablet is now back in operation on lineageos. Going and get Gapps now. Thanks a lot lambdadroid

I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.

lambdadroid said:
If the tablet boots into the screen with the 3 fastboot lines you are in DNX mode, which means you've likely messed up your bootloader. To restore the bootloader, follow the steps outlined in https://forum.xda-developers.com/showpost.php?p=73672837&postcount=5
If everything works, you should get to a second Fastboot screen with NORMAL BOOT etc. From there you can either start the temporary TWRP recovery session (see https://forum.xda-developers.com/showpost.php?p=73673438&postcount=7) to flash the Lollipop package you've downloaded earlier (UL-K013-WW-12.10.1.36-user.zip) or flash LineageOS.
If you want to flash LineageOS you need to unlock your bootloader. Download https://www.androidfilehost.com/?fid=312978532265362065, take the ESP.img from the ZIP and download https://github.com/me176c-dev/devic...recovery-3.1.1-20171119-UNOFFICIAL-me176c.img. Then run:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20171119-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20171119-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD).
Click to expand...
Click to collapse
I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.

MJMJ7 said:
I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.
Click to expand...
Click to collapse
No need to reply twice.
Please clarify: What exactly is failing? The LineageOS ZIP or the OpenGApps ZIP? Do you get an error during installation or does it never finish the boot after installation?
Things you can try: Check TWRP log for errors (usually marked red if you click the bottom right button in TWRP). Try a factory reset in TWRP.

lambdadroid said:
No need to reply twice.
Please clarify: What exactly is failing? The LineageOS ZIP or the OpenGApps ZIP? Do you get an error during installation or does it never finish the boot after installation?
Things you can try: Check TWRP log for errors (usually marked red if you click the bottom right button in TWRP). Try a factory reset in TWRP.
Click to expand...
Click to collapse
Just thought you wouldn't be notified if I don't quote.
The gapps file is giving an error and failing, the lineageOS just stalls and never complete the installation.
I will try again now.....

patching system image unconditionally....
This is going on and on, about 10% left to complete but it never does. LineageOS installation.
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/0-System zips/
Asus Memo pad 7 K013/gapps 7.1.zip'
And that's what I'm getting from the gapps installation.
Installation failed.

Got the Gapps to install, had to choose x86 version. Still no improvement from lineage.

MJMJ7 said:
patching system image unconditionally....
This is going on and on, about 10% left to complete but it never does. LineageOS installation.
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/0-System zips/
Asus Memo pad 7 K013/gapps 7.1.zip'
And that's what I'm getting from the gapps installation.
Installation failed.
Click to expand...
Click to collapse
Maybe the file wasn't downloaded/copied properly. Enable ZIP file signature verification in the TWRP settings and flash the LineageOS package again. Does it print "Zip signature verified successfully"?

lambdadroid said:
Maybe the file wasn't downloaded/copied properly. Enable ZIP file signature verification in the TWRP settings and flash the LineageOS package again. Does it print "Zip signature verified successfully"?
Click to expand...
Click to collapse
Did it again with another copy and enabled the verification and all came out successfully. Thanks for your help.:good: