clockwork recovery line 12 error? - Vibrant Q&A, Help & Troubleshooting

okay so i still need some help with the following::
-- Movi_check Start..!!
checksum confirmation need_checksum[1301305579]
MBR_ChkSum in header : 4.1
MBR checksum : EC0063A432AFDBA2B104C3F0DF52FE3D
MRB Checksum Error
Movinand Checksum Confirmation Fail
-- movi_checking done!...
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC
Error has to do with clockwork recovery, been searching around on this thread and there are a few people with this issue and havent found a solution. I was able to boot up to clockwork recovery by placing and a update.zip on my sd card. I would boot up into stock recovery, and install update packages, the clockwork recovery package would be my update package. Once into recovery I wipe and try flashing another rom, NO LUCK!!! line 12 error!!! Can someone please walk me out of this mess! Or give me some advice on what to do?

Related

Solution for Failed OTA Update (due to removed apps)

I wanted to write this "guide" for all the others that may be experiencing issues such as myself and others that I've talked to and helped. It was quite a learning experience and one of those "wow, I totally screwed myself" moments, to say the least lol.
There have been quite a few posts by others that outline how to update your rooted phone with the OTA but I wanted to put it down a bit more step by step with some extra information for those that thought it might be a good idea to just DELETE some apps from the /system/app patition (myself, included) without taking a full system backup using CWM, etc. I do NOT believe that a Titanium backup is sufficient if you choose to delete the application afterwards (as I see no evidence that the [required] .odex files are part of the TiBu backups)
Due to all the requests (here is my RAZR /system/app dump):
Pre-OTA: http://bit.ly/vwkbDw
Post-OTA: http://bit.ly/rZdQgC
So here we go...
1. Settings -> About Phone -> System Updates -> "Download Now"
2. Once downloaded, choose "Install Later" (important!)
3. Open up ES File Explorer or Root Explorer or you can even use adb to shell into the system (not recommended unless you're really good at this)
4. Browse to the /cache directory
5. Copy the two files named "Blur_Version.6.11.744.XT912.Verizon.en.US.crc" and "Blur_Version.6.11.744.XT912.Verizon.en.US.zip" to the /sdcard-ext location (NOT /sdcard)
6. Download and Install (from the Market) "OTA RootKeeper"
7. Run OTA Rootkeeper and select "Protect Root" (this will preserve files and links to the root application after the update). You CAN still choose to re-root using DoomLord/Zerg method but this is a LOT easier
8.You can choose to backup your apps via TiBu if you want to be extra cautious should something go wrong (but not required).
9. Power OFF the device. Then enter Motorola Recovery mode (Hold Vol+ and Vol- and Power). Click Vol- to highlight Recovery Mode and Click Vol+ to select it. Wait for the Triangle and exclamation point and then press both Vol buttons at the same time
10. Choose to "apply update from sdcard" by using the the Vol+ or Vol- to highlight and the Power Button to select
11. Choose the update file using the same method as step 10
12. Let it run and do it's thing...here's where the problems can start. If you have no problems you can skip to step 18
13. If you receive a "Status 7" error message it is probably complaining about checksum mismatch of the file that is ALSO listed in that output. This can also happen if the file is missing
14. Record the first 4 characters of the TWO checksums that it lists (this is important, do not forget) AND the filename (usually /system/app/<somename.apk> /system/app/<somename.odex>
Having these checksums will help you locate which file you need to get you back to "good" standing. The first value indicates the SHA1 checksum of the UPDATED file (POST OTA patching) while the second value indicates the SHA1 checksum of the older file (PRE OTA patching). There are quite a few resources on these forums where people have provided their "system dump".
You can also find this information after an unsuccessful install in the /cache/recovery/last_log directory on your phone - for those that use the install method from within the Android OS (Automatic OTA Install)
15. Download one or more of these "system dumps" and extract the file named in the error. Copy it to your sdcard and then use Root Explorer or Astro to copy it to the /system/app location (you might need to make it R/W on /system/app)
15A. For the advanced users:
You can save some guess work and get the sha1 value using a utility (windows/linux) to compare the strings with what was in the error message.
IF the checksums match you might as well copy over the corresponding .odex/.apk file as well.
IF the checksums do NOT match, you might as well scrap that "system dump" and download another one (and pray)
15B. IF you are unable to locate an original razr file that matches your criteria you can also take a stab and ask someone to send you their POST-OTA file(s) that you are missing. You can also compare the SHA1 checksum OR just try and see if it works. The installer will continue forward if it detects either the CORRECT old or new file already in place (*whew*)
16. Then return to step 9. Continue steps 9-15 until the update goes through.
18. Reboot after the update is complete
19. Verify the update was successful by following step 1 (there are other ways to see the version as well)
20. Re-run OTA RootKepper and select the option to "Restore Root"
21. Disconnect any USB cable to the phone and reboot. Verify root works properly (SetCPU, TiBu, SuperUser App, etc)
IF you are unable to regain root via Step 20, then you can always use the method that you previously used to RE-root your phone (Zert/DoomLord utility)
22. FREEEEEZE your apps from now on. (at least until there is an SBF). Stop deleting anything that isn't on your sdcard-ext partition
I hope that helps some folks out. I had about 8 files to replace and it seemed that there was never a "system dump" that had all of them. I helped one user by providing just ONE file that he accidentally deleted. In turn, after the update he provided me with both (updated) files that I needed. Win-Win!
I have my old and my NEW "system-dump" files so don't hesitate to ask me for them. If I receive enough requests I will end up putting them on one of the mediafire/megaupload places. A few other places to get the system dumps are from some of the ROMS provided for the US RAZR (i had some files match from the RAZRX 1.0 ROM)
If you noticed that I skipped number 17 then you were paying close enough attention ;-)
It worked, thank you.
Sent from my DROID RAZR using xda premium
great write up
droidony--droidforums
I cant find any dump links that are active. My problem is with the settings.apk. can anyone help?
Found one dump and no match.
When I looked in my cache thingy there wasn't anything there. Am I missing something or looking in the wrong spot?
I originally needed the maps odex file (as that was what was showing up in the log but I had it on my phone I must have done something as to how it disappeared) which i got from your download well one thing had lead to another with all these zips of the update and this is where I am at now. I guess I will stop here until I get better direction on what to do now. I am not sure if it is better or worse than before. This is the current log of where I am. If you know where to go from here please let me know. Thanks!
Parsing the directoryd_name: 3-0:1.0
Parsing the directoryd_name: 2-1
Parsing the directoryd_name: 2-1:1.0
Finding update package...
I:Update location: /cache/Blur_Version.6.11.744.XT912.Verizon.en.US.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing NV updater extensions
installing omapdevtype updater extension
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Verifying current system...
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to stat "/data/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop", "88b14d106c1935ebf67d34285a6840e9fc4a77da", "84e1256862a5723b93d38b6135ce947e97a39504")
assert failed: apply_patch_check("/system/build.prop", "88b14d106c1935ebf67d34285a6840e9fc4a77da", "84e1256862a5723b93d38b6135ce947e97a39504")
E:Error in /cache/Blur_Version.6.11.744.XT912.Verizon.en.US.zip
(Status 7)
Installation aborted.
-------------------------------------------------------------------------------------
update: I tried to install the 744 copy that was on the sd card and this is the error it gave me. The above is the error it gives me directly from the ota download and update.
-- Install /sdcard/download ...
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing NV updater extensions
installing omapdevtype updater extension
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Failed to mount /dev/block/mmcblk1p20 on /system: Device or resource busy
mtd mount of system failed: Device or resource busy
script aborted: assert failed: mount("ext3", "MTD", "system", "/system")
assert failed: mount("ext3", "MTD", "system", "/system")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
I:Set boot command ""
elyhlapetina said:
When I looked in my cache thingy there wasn't anything there. Am I missing something or looking in the wrong spot?
Click to expand...
Click to collapse
Same here. No files there.
elyhlapetina said:
When I looked in my cache thingy there wasn't anything there. Am I missing something or looking in the wrong spot?
Click to expand...
Click to collapse
Oaklands said:
Same here. No files there.
Click to expand...
Click to collapse
If you don't have root enabled you won't be able to view the folder contents. SO, if you used the OTA RootKeeper app and temporarily removed root, you will need to back into that application and restore root...
Viewing the last_log in the /cache/recovery location isn't needed, if you do the manual installation using the Motorola Recovery. The same error messages appear in the yellow text after the update fails and before you reboot the phone.
branshaw09 said:
I cant find any dump links that are active. My problem is with the settings.apk. can anyone help?
Found one dump and no match.
Click to expand...
Click to collapse
Branshaw, did you take a look at my two download options listed in my original post? Settings.apk SHOULD be in there. You can also try grabbing one from one of the few ROMS that are out for the RAZR - i suggest trying to pull the apk from the RAZRX 1.0 ROM
kb3awq said:
I originally needed the maps odex file (as that was what was showing up in the log but I had it on my phone I must have done something as to how it disappeared) which i got from your download well one thing had lead to another with all these zips of the update and this is where I am at now. I guess I will stop here until I get better direction on what to do now. I am not sure if it is better or worse than before. This is the current log of where I am. If you know where to go from here please let me know. Thanks!
Parsing the directoryd_name: 3-0:1.0
Parsing the directoryd_name: 2-1
Parsing the directoryd_name: 2-1:1.0
Finding update package...
I:Update location: /cache/Blur_Version.6.11.744.XT912.Verizon.en.US.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing NV updater extensions
installing omapdevtype updater extension
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Verifying current system...
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to stat "/data/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop", "88b14d106c1935ebf67d34285a6840e9fc4a77da", "84e1256862a5723b93d38b6135ce947e97a39504")
assert failed: apply_patch_check("/system/build.prop", "88b14d106c1935ebf67d34285a6840e9fc4a77da", "84e1256862a5723b93d38b6135ce947e97a39504")
E:Error in /cache/Blur_Version.6.11.744.XT912.Verizon.en.US.zip
(Status 7)
Installation aborted.
-------------------------------------------------------------------------------------
update: I tried to install the 744 copy that was on the sd card and this is the error it gave me. The above is the error it gives me directly from the ota download and update.
-- Install /sdcard/download ...
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing NV updater extensions
installing omapdevtype updater extension
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Failed to mount /dev/block/mmcblk1p20 on /system: Device or resource busy
mtd mount of system failed: Device or resource busy
script aborted: assert failed: mount("ext3", "MTD", "system", "/system")
assert failed: mount("ext3", "MTD", "system", "/system")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
I:Set boot command ""
Click to expand...
Click to collapse
It sounds like you ran something on your phone that may have adjusted settings in the build.prop file (supercharger, jakebitesmod, etc). I can try and give you a copy of mine when I get home tonight, but hopefully someone else in here would be kind enough to attach it to a post on this thread.
it worked!!
thank you so much it worked perfected
Great solution, but what if I just have to restore an app (Facebook Authenticator in this case) I'm already Post-OTA, deleted it by accident, any help please? been scratching my brain for days. TIBU just hangs when I try to restore it.
jerkwad said:
It sounds like you ran something on your phone that may have adjusted settings in the build.prop file (supercharger, jakebitesmod, etc). I can try and give you a copy of mine when I get home tonight, but hopefully someone else in here would be kind enough to attach it to a post on this thread.
Click to expand...
Click to collapse
Actually I haven't ran anything extra just copied the map codex in with the others and the pre and post update on here gives signature verification error lie the other couple I tried from droid forums from the other guy who had a zip for a solution which was a stock root zip. This is amazing my Droid 1 could flash anything etc. And I was trying to be a stock good boy with this phone except root.
can someone please help me on what to do now. after i got to trying to install the update i recieved the status 7
this is what my phone said
assert failed: apply_patchcheck("system/app/livewallpappers.apk", "37db550d10330f4e0bcf0efb60a86b62f7598a4a3", "d3686011083bcb1b46cb9d1702b1788bf5772e37")
E:error in /tmp/sideload/package.zip
(status 7)
Installation aborted
So I took a look at what was missing, and it doesn't match with the directions you gave. Atleast I don't think it does.
here's what i got:
--Install /sdcard/Android Dev Update ...
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/preinstall/KnowYourDevice/Motorola_XT912_BatterySave.3gp",
5faf882a9f143c2e45a264aad9c067233a43be8b", "6bcc903965d9cd3862f5c5a5760e129d36b07cf5")
E:Error in /tmp/sideload/package.zip
(status 7)
Installation aborted.
I didn't, myself, remove or freez any apps.
jerkwad said:
Branshaw, did you take a look at my two download options listed in my original post? Settings.apk SHOULD be in there. You can also try grabbing one from one of the few ROMS that are out for the RAZR - i suggest trying to pull the apk from the RAZRX 1.0 ROM
Click to expand...
Click to collapse
I am trying to download your pre ota file now. The settings.apk md5sum in razrx ROM fine match my error report
I have the same problem. Im rooted and use astro file manager and nothing is in cache.
Sent from my DROID RAZR using xda premium
I have same issue with guidedtours.odex
checksum first 4 are
64d7
1c18
5bb6 & 5cc1
Sent from my DROID RAZR using xda premium
95ea and b39c for gmail.odex any info greatly appreciated.
HDW

[HELP] Bricked LG L70 D325 when Trying Install Custom ROM

1. Unlocking Bootloader taken from here (Success)
2. Installing SuperSU, BusyBox Installer
3. Downloading the CM12 from here
4. boot to recovery mode to install the Custom ROM. first I do wipe data, then install the ROM. when Installing, there are no error code or notifications so I assumed it's installed. I try to install the Gapps, but failed, so I skipped it. when I reboot my phone, suddenly I got messages on the left top of screen says :
[840] fastboot_init()
[840] Error: allocating memory for ssd buffer
[860] USB init ept @ 0x7ad0000
[860] udc_start()
------------------------------------------------
DOWNLOAD MODE
------------------------------------------------
Loading ......
Press the Volume Up key until you see the download screen
[530] fastboot_init()
[530] Error: allocating memory for ssd buffer
[550] USB init ept @ 0x7ad0000
[570] udc_start()
[680] -- reset --
[680] -- portchange --
[720] -- reset --
[720] --portchange --
I've tried so many ways to restore it. from Laf Multi Tools, using fastboot device (my device won't detect in PC, even in my friend's laptop), etc and still no luck. can someone please help me?

[Q] Recovery errors

Hello,
I have just compiled TWRP for my phone, but I got a lots of error, when I booted into the recovery.
I can't see sd card or internal storage when I want to flash something..
There are lots of errors like
"E: invalid block device on '/dev/block/bootdevice/by-name/system........"
" ', 'ext4', 59
E : invalid block device.."
How to fix that?

Q: 14.1-Lineage with Magisk 16.0/16.3 - unable to flash

Hi,
i'm trying to install Magisk on my I9100, but i fails with error like (this was during the try to patch lineage boot.img within 14.1 with magiskmanager and lineage-su)
Code:
- Device platform: arm
- Extracting files
- Patch boot/ramdisk image: /dev/block/mmcblk0p5
- Unpacking boot image
MagiskBoot v16.3(1630) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
! Unable to unpack boot image
Failed!
! Installation failed
When flashing it the regular way from TWRP (3.1.0-0) i get a similar sounding error (Error 1).
I also tried the latest unofficial 3.2.1-0., but got the same error.
The PIT is changed to 1,5gb System and 6 GB Data.

[Recovery] [ANE-LX] Recovery and Erecovery stuck and challanged flashing LOS

Hi there
I had some problems booting into Recovery and ERecovery. It would always stay endless in the Warning screen where it says that the Device is unlocked.
I run into it because of TWRP not Formating Data properly.
https://dl.twrp.me/anne/
twrp-3.5.1_9-0-anne.img14.6M 2021-03-13 15:27:54 ESTtwrp-3.5.0_9-0-anne.img13.2M 2020-12-27 21:03:29 EST
​This Versions get stuck at:​
Code:
Formatting Data using mkfs.f2fs...
Done
After it beeing stuck I could usually reach erecovery and wipe . But at one point it wouldn't work and I couldn't reacht the two and also couldn't stop the device from endless starting after shutting down.
I tried to flash several images from this one: https://androidhost.ru/1nfK
After flashing odm.img I could access the reflashed Stock Recovery and E-Recovery.
Update: Erasing Data with fastboot also works.
Note: It would show Google instead of Huawei at startup and in fastboot FRP:Unlocked doesn't show anymore after flashing odm.img
Else:​To reach erecovery or twrp recovery I retried often to hold power and volume up when the device is turned off. It then vibrates two times when it works. I hat sometimes to try for 10 Minutes to reach one of the to.
I unlocked with PotatoNV. The phone can be opened quite comfortable with a straight package plastic like from a cabel or electric device and a hairdrier.
Update: I can actually not format Data with any of these TWRPs. This was working before flashing the odm or maybe an other image.
twrp-3.5.1_9-0-anne.img14.6M 2021-03-13 15:27:54 ESTtwrp-3.5.0_9-0-anne.img13.2M 2020-12-27 21:03:29 ESTtwrp-3.4.0-1-anne.img13.2M 2020-09-26 14:58:13 EDTtwrp-3.4.0-0-anne.img13.2M 2020-08-21 17:03:57 EDT
I could format with adb shell:
anne:/etc # mkfs.f2fs /dev/block/mmcblk0pXX
F2FS-tools: mkfs.f2fs Ver: 1.10.0 (2018-01-30)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Label =
Info: Trim is enabled
Info: No support kernel version!
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 106086400 (51800 MB)
Info: zone aligned segment0 blkaddr: 512
Info: [/dev/block/mmcblk0p57] Discarding device
Info: Secure Discarded 0 MB
Info: Overprovision ratio = 0.880%
Info: Overprovision segments = 459 (GC reserved = 235)
Info: format successful
benaep said:
I can actually not format Data with any of these TWRPs.
Click to expand...
Click to collapse
Yes, you have installed wrong TWRP (version 3.4.0.x and 3.5.0.x is not fully compatible with our device and it's strongly NOT recommended do 'wipe data' runnig stock ROM , it may brick the phone).
Use recommended TWRP:
Recommended and tested TWRP Recovery
EMUI 8 Stock ROMs: 3.2.1-0 by pretoriano80 (with data decryption on Android 8 ) https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw EMUI 8 Custom ROMs: 3.2.1.0 by Catuva21...
forum.xda-developers.com
-Alf- said:
Yes, you have installed wrong TWRP (version 3.4.0.x and 3.5.0.x is not fully compatible with our device and it's strongly NOT recommended do 'wipe data' runnig stock ROM , it may brick the phone).
Use recommended TWRP:
Recommended and tested TWRP Recovery
EMUI 8 Stock ROMs: 3.2.1-0 by pretoriano80 (with data decryption on Android 8 ) https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw EMUI 8 Custom ROMs: 3.2.1.0 by Catuva21...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the direction Alf. So for the Newest Linage OS build that would be:
Pie Custom ROMs:
3.4.0-0-emui9_eR
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
right?
benaep said:
Thanks for the direction Alf. So for the Newest Linage OS build that would be:
Pie Custom ROMs:
3.4.0-0-emui9_eR
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
right?
Click to expand...
Click to collapse
If you want to flash LOS from TWRP (idk why, but it's your choice), use 3.2.1 by pretoriano80 (wiping etc.) After installing custom ROM, you can replace 3.2.1. with 3.4.0.0-emui9_eR.
-Alf- said:
If you want to flash LOS from TWRP (idk why, but it's your choice), use 3.2.1 by pretoriano80 (wiping etc.) After installing custom ROM, you can replace 3.2.1. with 3.4.0.0-emui9_eR.
Click to expand...
Click to collapse
Hi Alf
Thanks for the reply. Very gratefull for this. I'm trying since Weeks to get this running.
I just want a phone with minimal Google. I had /e/ but I didn't find a build and back in the days linage would be fine.
You think there is something which makes more sense?
benaep said:
I just want a phone with minimal Google
Click to expand...
Click to collapse
Then install "v" variant , e.g.
LOS 17.1-unoff.
https://sourceforge.net/projects/treblerom/files/LOSQ/2020.10.17/losq-v224-201017-arm64-bvN.img.xz/download
LOS 18.1-unoff.
https://sourceforge.net/projects/treblerom/files/LiR/2021.03.18/lir-v302-210318-arm64-bvZ.img.xz/download
and install opengapps - pico, nano, micro... , what suits you.
-Alf- said:
Then install "v" variant , e.g.
LOS 17.1-unoff.
https://sourceforge.net/projects/treblerom/files/LOSQ/2020.10.17/losq-v224-201017-arm64-bvN.img.xz/download
LOS 18.1-unoff.
https://sourceforge.net/projects/treblerom/files/LiR/2021.03.18/lir-v302-210318-arm64-bvZ.img.xz/download
and install opengapps - pico, nano, micro... , what suits you.
Click to expand...
Click to collapse
Yo Alf
Thanks for the Links to the Image files. I would never have found them myself. I tried now a few hours to make them run.
Formating and Wiping works with 3.2.1 by pretoriano80
I tried both images, but am not shure. I get an invalid zip file error when I copy it on the device. Sideload doesn't work. No connection or Success or Success 00.00 X.
I make it a zip on linux with --> unxz --> img2simg --> Create Zip Directory wit xarchiver.
I tried different combinations of this. First I forgot about simg and just made a zip out of the img.
Code:
/tmp/recovery.log: 1 f...57322 bytes in 0.010s)
~ >>> adb sideload /home/bni/Downloads/losq17.zip
adb: failed to read command: Success
~ >>> adb sideload /home/bni/Downloads/losq17.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
~ >>> adb pull /tmp/recovery.log /home/bni/Downloads/recovery.log
/tmp/recovery.log: 1 f...59228 bytes in 0.007s)
Code:
~ # twrp install /image/LOS17_SIMG.zip
Installing zip file '/image/LOS17_SIMG.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
Invalid zip file format!
Error installing zip file '/image/LOS17_SIMG.zip'
Done processing script file
benaep said:
I get an invalid zip file error when I copy it on the device.
Click to expand...
Click to collapse
Of course, it is not a flashable .zip file.
You have to install it as image file, unpack .zip package, transfer exctracted .img file to the SD card. In TWRP go to Install , select Install image, choose lineage .img file , mark "system image" and flash.
If you need to do a factory reset , first replace TWRP with stock recovery and perform factory reset in recovery.
Or, flash Lineage.img in fastboot,without TWRP, wipes, errors etc. (make sure to have the stock recovery flash) - https://forum.xda-developers.com/t/losq-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543

Categories

Resources