Database Users

Need help to restore Android to my new Axon 7

Hi guys
I decided to try and and unlock and root my phone as soon as I got it. But somewhere along the line things didn't go to plan, and I've got a phone with TWRP (3.0.2-b-b10) on it, and that's about it (stupidly I didn't do a back up as I'd not set anything up on the phone yet). I can still put it into Factory Test Mode, and run 'adb reboot edl' to put into a place where I can communicate with it using tenfar's tool.
First time out, everything seemed to go fine, but when I booted up the phone after running through the process, the wifi wasn't working. This meant I couldn't get through the first stage of phone set up (select language, then wifi, nothing I tried would get me beyond that, as I guess a phone without wifi isn't much use).
So I went back into wiped a few things, tried tenfar's tool again with no luck; wifi still no working. I followed the steps on here, but the ADB commands failed.
Code:
C:\Users\Stephen\AppData\Local\Android\sdk\platform-tools>adb shell dd if=/dev/z
ero of=/dev/block/bootdevice/by-name/modemst1 bs=16384
dd: /dev/block/bootdevice/by-name/modemst1: Permission denied
After some more messing, I wiped the OS (yeah, idiotic). Anyway, so I download Draken's boot and stock from another post, but when trying to flash them via TWRP, they failed. I downloaded them on mac, and copied them to a exFAT SD card. It complains about failed to mount /firmware and no MD5 file found, then I get:
Code:
Could not find 'META-INF/com/google/android/update-binary' in the zip file
And it finishes. Same with the stock file. So now I'm in the process of downloading the B20.zip from here in the hope there is something in there I can flash to get the OS back on the phone. any other suggestions?
Thanks in advance,
Sok

Had the same issue with rooting using Tenfar's tool. I used TWRP to flash a fresh B10 and start over. Send a PM if you need/want help.

Now I'm following the instructions here, and I keep getting the error:
Code:
Failed to mount '/firmware' (Invalid argument)
Then it tells me that the B20 zip file from Draken is corrupt.

Lineage OS 13 Port for BLU_Studio_XL_2

:good:
I have cm13 ported over from different Phone (Blu Life_Max) and booting.
already working
1. wifi
2. camera but not video camera
3. bluetooth audio
4. loud speaker audio
5. FM Radio
6. cell in sim1 and sim2 slot, but sim2 only gets H+ speed(5-10Mbps)
SIm1 gets 4G(LTE) speeds on test 50Mbps Both tests with freedomPop
known issue (mostly camera related)
1. videocamera causes camera crash
2. selfie-camera not available **Fixed with V6**
3. panarama shot crashes camera
4. NFC not able to turn on (stock rom did not have NFC, so this may not be possible to work) : next update may remove this **fixed in V5**
V7 -- Hassome permission changes in boot.img that were found in logcat, for "SMI"
still not working videocamera
To install:
1. Must be bootloader unlocked
.
How to Unlock Bootloader via Fastboot
1. Setup ADB and Fastboot on your PC.
2. Enable USB debugging and OEM Unlock on your Android device.
3. Connect your device to the PC with a USB cable.
4. Open a command window on your PC.
5. Boot your device into bootloader mode using the following command:
Code:
adb reboot bootloader
└ You may get a request to authorize USB debugging on the device, accept it.
6. Once your device is in bootloader mode, issue the following command to unlock bootloader:
Code:
fastboot oem unlock
You get a confirmation screen on your device. Press Volume Up button to highlight Yes and press Power button to select it.
This will begin bootloader unlocking process, which shouldn’t last more than couple of minutes.
7. Once bootloader is unlocked, your device will reboot into bootloader mode. You need to boot it into system now using the command below:
Code:
fastboot reboot
During reboot, your device will go through a factory reset and then finally boot into system.
2. Install included twrp(New kernel for recovery allows touchscreen to work)
***PRIOR RELEASES NEED TO USE LOPESTOM RECOVERY TO INSTALL***
Due to different moint point descriptions Future versions(If they come) will use block number moints to be compatible with both
******V-7-Block is compatible with both recoveries
1. make sure developer options is enabled
2. Reboot to bootloader
Code:
adb reboot bootloader
3. Test recovery works for your device
(example commands assume you have the vampirefo version of recovery downloaded to the desktop)
Code:
Fastboot boot Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
4. If recovery boots good, then return to bootloader and flash (commands work from in booted twrp)
These steps are what I find to be best order to prevent the stock rom from replacing the stock recovery on boot.
Code:
fastboot flash recovery Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
fastboot boot Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
adb wait-for-device
adb reboot recovery
3. If first install. do wipe and wipe system too. If Updating no wipe needed
Sources:
Rom not built for this device Built for Blu Life-Max --no thread to link, sorry
Rom uses the stock kernel, pulled from oem device (studio_XL_2)
keeping a git of files swapped to make rom work
https://github.com/mrmazakblu/BLU_Studio-XL-2_port_from_Life-Max
kernel source for recovery:
https://github.com/mrmazakblu/Blu_studio-XL_2_kernel_source
Other projects for Studio_XL_2:
Reserrection Remix Port
XDA:DevDB Information
blu-studio-xl-2, ROM for all devices (see above for details)
Contributors
mrmazak, Thanks to vampirefo --building donor rom
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: BLU-Studio-XL-2--BLU_S0270UU_V09_GENERIC
Based On: Lineage OS
Version Information
Status: Testing
Created 2017-10-30
Last Updated 2017-11-30

New TWPR kernel
Reserved

TWRP touchscreen
new kernel for TWRP allows touchscreen to work when recovery is flashed to device.
thanks to @vampirefo for finding a fix for Life-Max. Same fix worked here too.
New kernel is also put into @lopestom twrp.
Choose either one they both work.

Thanks for porting. I'm looking forward to testing it with my Studio XL2

killer13666 said:
I tried flashing it like you said and this is what happened....
Code:
Installing zip file '/external_sd/BLU_Studio-XL-2_port_from_Life-Max-V-7.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Update binary zip
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
Target: Blu Studio XL 2
Target: Blu Studio XL 2Check if system is already mounted
Check if system is already mountedcould not detect filesystem for /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system, assuming ext4could not detect filesystem for /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system at /system: No such file or directorymount: failed to mount /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system at /system: No such file or directoryRunning backup script for update installsabout to run program [/tmp/install/bin/backuptool.sh] with 2 args
Running backup script for update installs
run_program: child exited with status 127
unmount of /system failed; no such volumeChecking if Data is compatableunmount of /system failed; no such volume
Checking if Data is compatable
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
You have an installed system that isn't signed with this build's key, aborting...
run_program: child exited with status 124
script aborted: Can't install this package on top of incompatible data. Please try another package or run a factory reset
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
I:Install took 14 second(s).
Error installing zip file '/external_sd/BLU_Studio-XL-2_port_from_Life-Max-V-7.zip'
Updating partition details...
Click to expand...
Click to collapse
Do not know why you have failed to mount /system error could be because you have /system set to be read only.
In install directions it says need to wipe /data
and
also advanvance wipe /system
second error says imcompatable /data == this means you did not wipe data before installing.
Please continue here in the rom thread.

mrmazak said:
Do not know why you have failed to mount /system error could be because you have /system set to be read only.
In install directions it says need to wipe /data
and
also advanvance wipe /system
second error says imcompatable /data == this means you did not wipe data before installing.
Please continue here in the rom thread.
Click to expand...
Click to collapse
I figured out what the problem was. For some reason, the recovery image you supplied wasn't mounting the system partition properly. I used a different image and the ROM flashed perfectly

killer13666 said:
I figured out what the problem was. For some reason, the recovery image you supplied wasn't mounting the system partition properly. I used a different image and the ROM flashed perfectly
Click to expand...
Click to collapse
please let me know which one worked for you and which one did not.
I think I was using the one marked 3.1.1 (vampirefo) but now I am not sure.
I may do independet testing again on both, but would appreciate your input.
Just confirmed there is a problem with the combination of the update-binary used in these install zips and the vampirefo recovery. The fix can be either i use different update-binary file or you use lopestom recovery.
**EDIT**
Problem was with the my updateer-script. I put fixed install packages up.

Thanks for the port my version is v06.0.04.00_generic 16/06/2017
I have a unlocked phone from best buy
I keep seeing everyone say v09 mine has updated twice wondering if it will work on mine or if I need to update somehow

ahnuts72 said:
Thanks for the port my version is v06.0.04.00_generic 16/06/2017
I have a unlocked phone from best buy
I keep seeing everyone say v09 mine has updated twice wondering if it will work on mine or if I need to update somehow
Click to expand...
Click to collapse
I dont see any version of my stock OS that is similar to that number you have.
When I had stock installed, In the settings screen, about phone listed the build version as
Code:
BLU_S0270UU_V09_GENERIC
This port is for Blu_Studio_XL_2 make sure that is device you have.
If you look in the build.prop you will get more information about the device.
if you want to , you can pull the build.prop and post it , so I can see
Code:
adb pull /system/build.prop Desktop\build-prop.txt
then attach the file here.

According to the device in about phone mine is studio xl 2 and that was what the box said when I purchased the phone at best buy

And this one shows the version

And this one shows the version

Wrong pic

ahnuts72 said:
Wrong pic
Click to expand...
Click to collapse
The dates show it is a newer software than what I had, but this should still work, as long as you are still able to unlock the bootloader.

In the developer options I have a setting that says oem unlocking allow the bootloader to be unlocked will that work or will I have to still do it from adb

ahnuts72 said:
In the developer options I have a setting that says oem unlocking allow the bootloader to be unlocked will that work or will I have to still do it from adb
Click to expand...
Click to collapse
here is guide.
https://www.theandroidsoul.com/unlock-bootloader-via-fastboot-android/
the unlocking does do a complete wpe on the data part of the phone. so if you have pictures or music or any files you want to keep , make sure to copy first. Also to be safe , if you have external sdcard in , take it out before doing unlock
****
****
Must complete the unlock as the guide shows includeing the reboot, so stock recovery does its wipe, I t is important part of the unlock.
**
**
after unlocked,
to flash recovery, enable developer options again, enable usb debugging. authorize adb connection to your pc-
Code:
adb reboot bootloader
fastboot boot recovery.img
**recovery.img = "full path to the downloaded recovery"
**example if you downloaded the vampire based recovery and you downloaded to the desktop**
Code:
fastboot boot Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
after booted to recovery and it works return to bootloader and flash it to phone. I allways recomend this boot first method to verify it recovery works. You cant be certain every od will work on every device. Better safe than sorry.
select reboot menu from recovery and then select reboot bootloader.
Due to a securety measure android has (recovery-from-boot) when replacing recvoery to need to boot directly to new recovery to prevent the android system from replacing it with stock version. so I use the steps below
Code:
fastboot flash recovery Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
fastboot boot Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
adb wait-for-device
adb reboot recovery
.

Android 6 or 7, plus install questions
Hi, I have rooted several phones but the procedure keeps getting more difficult. I see the instructions for installing recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img but I am curious what is on this image .... will it be rooted and if so, what version of Android is bundled? Will the phone then support Xposed and Xprivacy?
From what I can determine, the video camera is not working with your most recent release, V8, is this correct?
Thank you for your assistance!

Donphillipe said:
Hi, I have rooted several phones but the procedure keeps getting more difficult. I see the instructions for installing recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img but I am curious what is on this image .... will it be rooted and if so, what version of Android is bundled? Will the phone then support Xposed and Xprivacy?
From what I can determine, the video camera is not working with your most recent release, V8, is this correct?
Thank you for your assistance!
Click to expand...
Click to collapse
LineageOS 13 is android 6
there is no V8 only upto V7
video recording does not work
Lineage has root built in. Enable it in developer options
I do not know about xposed I not use it
Donphillipe said:
" I see the instructions for installing recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img but I am curious what is on this image "
Click to expand...
Click to collapse
That image is TWRP recovery only
I have not been working on this anymore.
I have ported "better" Resurection rom based on android 7 , have been using it as a daily use phone for just over a month now
https://forum.xda-developers.com/android/development/-t3699638

I appreciate your patience with someone who only dabbles in this hobby. When you say that the install image is TWRP only, what exactly does this mean?
I know I have owned several BLU phones and each time I tried to install a high-end recovery tool in the past, the list of supported phones on the recovery software list would never include my BLU device, saying something to the order of the source needing to be recompiled (as I recall) or something to that order which never seemed to happen. So are there additional steps for getting the phone to the point it will take this image other than the steps you outlined for unlocking the boot loader? Or what do I need to be aware of?
Also, do you have a backup of the factory image available in case something goes wrong, with basic instructions on how to recover the phone back to the factory version? Or is there something I can install or do on this phone to create a backup copy on my own?
Again I am sorry to have to ask for what to some appears a simple procedure. I do appreciate your going to the effort when you have already contributed so much with your images. Thank you!

Donphillipe said:
I appreciate your patience with someone who only dabbles in this hobby. When you say that the install image is TWRP only, what exactly does this mean?
I know I have owned several BLU phones and each time I tried to install a high-end recovery tool in the past, the list of supported phones on the recovery software list would never include my BLU device, saying something to the order of the source needing to be recompiled (as I recall) or something to that order which never seemed to happen. So are there additional steps for getting the phone to the point it will take this image other than the steps you outlined for unlocking the boot loader? Or what do I need to be aware of?
Also, do you have a backup of the factory image available in case something goes wrong, with basic instructions on how to recover the phone back to the factory version? Or is there something I can install or do on this phone to create a backup copy on my own?
Again I am sorry to have to ask for what to some appears a simple procedure. I do appreciate your going to the effort when you have already contributed so much with your images. Thank you!
Click to expand...
Click to collapse
The recovery image (TWRP) works for this device.
Yes recovery images, just like android roms are specific to each different device. This one has been edited to work for Studio XL 2
The TWRP is a custum recovery needed to install the custom ROM
The steps are complete, you shouldn't need anything else (need adb and fastboot)
Yes stock recovery image is available. Installing back to stock recovery is same steps as installing custom recovery.
both can be done as described with fastboot. Or both can be installed using SPFT (smart phone flash tool)

A6000 Plus stuck on Bootloader

I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.

If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!

kamesh_kraken said:
I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.
Click to expand...
Click to collapse
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query

StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
I was like why didn't I try this before.
You know what happened? The boot process on "Command Prompt" screen went fine. I heard the unplugging the device and replugging the device sound very well. But during all these process it stays on Fastboot mode forever.
I have the latest TWRP loaded for temporary boot process. (3.2.1)
Besides from that
I was finally able to flash with QFIL tool. But still stucks at Lenovo POWERED BY android logo. QCom Downloader didn't work. But QFIL tool did work. I was able to finally come over the "sahara error" by quickly clicking "Download" button after connecting the cable. Then it flashed all the files. Then it finished downloading. But then if I try to switch it on, it wouldn't boot. Still stucks at the screen that I mentioned earlier.

StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry!
I tried it with Stock Recovery of A6000 (not plus). It booted into recovery.
Now, I can boot into TWRP. Looks like all the partitions are gone. How do I recover that?

StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?

kamesh_kraken said:
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?
Click to expand...
Click to collapse
Just flash a new ROM

StillrunsKK said:
Just flash a new ROM
Click to expand...
Click to collapse
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.

jameeljb6 said:
If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!
Click to expand...
Click to collapse
Haha. I know how to do that. Thing is, I can't boot into System or Recovery normally even if I flash via Fastboot. I can only boot to recovery by "fastboot boot recovery.img" Then in TWRP there, I can't flash any roms as it shows Failed to mount /system /data /cache all the time. Tried fixing with "repair file system" option in TWRP. Still doesn't work.

kamesh_kraken said:
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.
Click to expand...
Click to collapse
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?

StillrunsKK said:
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?
Click to expand...
Click to collapse
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5

kamesh_kraken said:
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5
Click to expand...
Click to collapse
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)

StillrunsKK said:
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)
Click to expand...
Click to collapse
The TWRP I mentioned 3.1.0 was obtained from RR forum only where dev mentions "F2FS" support. It does show the same error that I mentioned earlier. I did repair, resize, format, change file system. What ever I do, I always get the mount error on 3 partitions. Can't flash any ROMs either. Shows that error 7 and 6. I even deleted the assert line. It would only land me on error 6. I even googled and tried to get rid of that error. But after the error 6 or 7, it shows the same "mount failed".
Not my device. One of my client's. Received as not working.

TWRP won't boot

I am attempting to put lineageos on my new Mi A1, following the installation guide here https://wiki.lineageos.org/devices/tissot/install
I have previously installed lineage on my old Moto G LTE and a Samsung Galaxy S4 and have not run into issues.
I have unlocked the bootloader and all that but I can't get twrp to boot.
I boot into fastboot with
Code:
adb reboot bootloader
that works fine, then I
Code:
fastboot boot twrp-3.2.2-0-tissot.img
This seems to have no effect, other than my phone 'disconnecting' from the PC.
I get the following terminal output
Code:
./fastboot boot .\twrp-3.2.2-0-tissot.img
Downloading 'boot.img' OKAY [ 0.682s]
booting OKAY [ 0.623s]
Finished. Total time: 1.336s
However nothing happens on the phone, it still just has the fastboot logo on it.
At this point if I manually reboot (long-press power) it will reboot into stock rom.
If I manually reboot into recovery (long-press power+volume up) it will reboot into stock recovery
I have ensured my sytem tools are up to date, and tried the previous version of twrp, and there is no change.
I WAS able to get twrp to boot using the "Mi A1 Tool" i found here https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857
However I was not able to install lineage due to an error.
I did not copy the exact output but it was something along the lines of
error 7, kInstallDeviceOpenError
After this attempt, I reflashed the stock rom using Xiaomi tools, and am back to the beginning.
The phone is fully up-to-date with stock updates, Android 8.1, July security update.
Once again went through the bootloader unlocking, and everything, but have arrived at the same result.
Anyone have any ideas?
any help would be greatly appreciated!
Thanks!

Hey, could you try this TWRP made for Oreo? https://www.androidfilehost.com/?fid=818070582850498337 (thread: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472)
I've also had some issues booting TWRP, but running
Code:
fastboot oem unlock
was enough to boot it successfully (
Code:
fastboot boot recovery-3.2.1-2-oreo.img
)

Thank you!
dgadelha said:
Hey, could you try this TWRP made for Oreo? https://www.androidfilehost.com/?fid=818070582850498337 (thread: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472)
I've also had some issues booting TWRP, but running
Code:
fastboot oem unlock
was enough to boot it successfully (
Code:
fastboot boot recovery-3.2.1-2-oreo.img
)
Click to expand...
Click to collapse
This recovery image worked great, AND installed lineage, thank you very much.
However, I am now unable to get gapps working.
I was pointed to this changelog here https://lineageos.org/Changelog-19/ by a user in the lineage subreddit.
I rebooted from twrp into the lineage recovery, chose Apply Update -> Apply from ADB
On my PC I run
Code:
./adb sideload .\MindTheGapps-8.1.0-arm64-20180610_024023
.zip
and after a pause I get the output
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: No error
and sometimes I get
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: Connection reset by peer
What happens on the phone has been a little different each time I have attempted this.
It either pops up on screen that it is unable to verify the file, install anyway?, doing so doesn't work.
OR it is hung up on a progress bar screen, with the following log output, or a slight variation of it
Code:
Stopping adbd...
Now send the package you want to apply to the device with "adb sideload <filename>"...
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
E:error: 21 Restarting dbd... Installation aborted.
After many attempts of this, reflashing lineage, and trying again, it did miraculously start doing the transfer at one point. It got to 47% then failed again.

Can't you just install from recovery?
https://forum.xda-developers.com/mi-a1/development/rom-lineageos-15-1-t3757938

pidermin said:
This recovery image worked great, AND installed lineage, thank you very much.
However, I am now unable to get gapps working.
I was pointed to this changelog here https://lineageos.org/Changelog-19/ by a user in the lineage subreddit.
I rebooted from twrp into the lineage recovery, chose Apply Update -> Apply from ADB
On my PC I run
Code:
./adb sideload .\MindTheGapps-8.1.0-arm64-20180610_024023
.zip
and after a pause I get the output
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: No error
and sometimes I get
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: Connection reset by peer
What happens on the phone has been a little different each time I have attempted this.
It either pops up on screen that it is unable to verify the file, install anyway?, doing so doesn't work.
OR it is hung up on a progress bar screen, with the following log output, or a slight variation of it
Code:
Stopping adbd...
Now send the package you want to apply to the device with "adb sideload <filename>"...
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
E:error: 21 Restarting dbd... Installation aborted.
After many attempts of this, reflashing lineage, and trying again, it did miraculously start doing the transfer at one point. It got to 47% then failed again.
Click to expand...
Click to collapse
Hey,
Install GApps also at TWRP. Signature verification is failing most probably because the Lineage Recovery should be accepting only Lineage-signed ZIP files.
You can install TWRP in your current boot image (so you don't need to boot TWRP everytime through fastboot) with this ZIP: https://www.androidfilehost.com/?fid=746010030569959456 (yet, you need to boot to TWRP through fastboot so you can flash it, but no need to boot it manually after installing it). Notice that after every system update you may need to install TWRP again (same for Magisk), as boot images get replaced.
Also, if sideload fails, you can just do a
Code:
adb push filename.zip /sdcard/
then install the ZIP directly from the "Install" section on TWRP.
Thanks!

Thanks a lot!
I found and was able to follow this guide
https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
instead of the one on the lineageOS website, and I am up and running.
Thank you very much for your time!

Can't boot to recovery or fastboot
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt it just reboots normally. Any suggestions on what should I do Please?

Azan Qazi said:
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt. Any suggestions on what should I do.
Click to expand...
Click to collapse
Have you tried doing reboot in the OS and choosing Recovery option?

Azan Qazi said:
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt it just reboots normally. Any suggestions on what should I do Please?
Click to expand...
Click to collapse
TrueMS said:
Have you tried doing reboot in the OS and choosing Recovery option?
Click to expand...
Click to collapse
yes sir I did tried several times. But as I said above it simply reboots the system.

Problem flashig new roms: TWRP unable to mount Data/media/twrp/.twrps

Hello everybody!
To defeat planned obsolescence of my Zenfone 3 (ZE520KL) I've decided to root it and install an alternative ROM.
With much difficulty at the end I achive root it but I've a problem flashing roms.
- Unloked OK
- To flash and fix TWRP I used Magistik (without it TWRP starded only when phone was connected to pc)
Now Root Checker says my phone is rooter, Magistik is correctly installed and TWRP seems ok. So I felt in 90% of my challenge!
But…
When I try to flash a ROM in TWRP lots of red line appear…
Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details…
...done
Unable to mount storage
Successfully decrypted with default password.
Updating partition details
…..done
Unable to mount storage
Failed to mount '/data? (Invalid Argumetn)
Full SELinux support is present.
Unable to mount /data/media/twrp/.twrps
MTP Enabled
Installing zip file '/external_sd/PixelExperience_zenfone3_-9.0-20190823-1844-UNOFFICIAL.zip'
Checking for MD5 file…
Skipping MD5 check: no MD5 file found
Warnink: No file_context
E3004: This package is for device: Z017, ASUS_Z017_1D, ASUS_Z012D, ASUS_Z012DC, ASUZ_Z012S; this device is .
E:unknown command [log]
Update process ended with ERROR: 7
Error installing zip file '/external_sd/PixelExperience_zenfone3_-9.0-20190823-1844-UNOFFICIAL.zip'
Updating partition details…
...done
Unable to mount storage
Click to expand...
Click to collapse
The same thing happens with Lineage OS
In addition if I try to save the log I can't find it in the storage of the phone (really I don't know where it should be).
Maybe the Recovery [treble] proposed by Giovix92 can solve my problem?
Any other suggestion?
Thanks a lot to everybody!

twin-s said:
Hello everybody!
To defeat planned obsolescence of my Zenfone 3 (ZE520KL) I've decided to root it and install an alternative ROM.
With much difficulty at the end I achive root it but I've a problem flashing roms.
- Unloked OK
- To flash and fix TWRP I used Magistik (without it TWRP starded only when phone was connected to pc)
Now Root Checker says my phone is rooter, Magistik is correctly installed and TWRP seems ok. So I felt in 90% of my challenge!
But…
When I try to flash a ROM in TWRP lots of red line appear…
The same thing happens with Lineage OS
In addition if I try to save the log I can't find it in the storage of the phone (really I don't know where it should be).
Maybe the Recovery [treble] proposed by Giovix92 can solve my problem?
Any other suggestion?
Thanks a lot to everybody!
Click to expand...
Click to collapse
Might be due to encrypted partition.
Try
Code:
fastboot format userdata
in fastboot mode.
This will, as you might expect, wipe all your data. So be sure to backup first.
Also, the flashing error
Code:
E3004: This package is for device: Z017, ASUS_Z017_1D, ASUS_Z012D, ASUS_Z012DC, ASUZ_Z012S; this device is .
E:unknown command [log]
Update process ended with ERROR: 7
is from incompatible TWRP and ROM version. Are you using the latest TWRP?
As a last resort for the flashing error, try this https://forum.xda-developers.com/showthread.php?t=2522762

vaanish said:
Might be due to encrypted partition.
Try
Code:
fastboot format userdata
in fastboot mode.
This will, as you might expect, wipe all your data. So be sure to backup first.
Also, the flashing error
Code:
E3004: This package is for device: Z017, ASUS_Z017_1D, ASUS_Z012D, ASUS_Z012DC, ASUZ_Z012S; this device is .
E:unknown command [log]
Update process ended with ERROR: 7
is from incompatible TWRP and ROM version. Are you using the latest TWRP?
As a last resort for the flashing error, try this https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
Thank you vaanish!
I solved flashing an older versione of TWRP. The 3.3.1.
Now all is right!