I have vivo v3 phone running android 5.1.1. lollipop.
I installed twrp by ADB in my phone.When I install the magisk14 zip file by twrp, it fails.They show error unpack boot img failed.
Help me plz..
Related
i am trying to install a custom rom on my Liquid acer S100
so i installed malez custom recovery 0.6.2 (the easy installer method)
i can boot to the recovery menu but everything i try to do fails
whenever i select anything it says aborted
flash aborted
wipe aborted
POWER OFF aborted
even Coppy recovery.log to sdcard aborted
please help my phone is useless that way
i am now using 2.2 rom which i flashed using a .bin flashtool. its even slower than my old 2.1 which i cant restore right now
btw, i rooted it visa superoneclick
and i think it was successful cuz i can use root explorer r/w mode
at the last step of installation (after OS boot)
i see this message at the adb log
rm failed -for read-only file system
is that whats causing the problem ??
hsn.ahmed said:
i am trying to install a custom rom on my Liquid acer S100
so i installed malez custom recovery 0.6.2 (the easy installer method)
i can boot to the recovery menu but everything i try to do fails
whenever i select anything it says aborted
flash aborted
wipe aborted
POWER OFF aborted
even Coppy recovery.log to sdcard aborted
please help my phone is useless that way
i am now using 2.2 rom which i flashed using a .bin flashtool. its even slower than my old 2.1 which i cant restore right now
btw, i rooted it visa superoneclick
and i think it was successful cuz i can use root explorer r/w mode
at the last step of installation (after OS boot)
i see this message at the adb log
rm failed -for read-only file system
is that whats causing the problem ??
Click to expand...
Click to collapse
Try factory resetting and than the exe recovery and root from within recovery. It took me 2 times to get it working error free.
Sent from my SGH-I997 using XDA Premium App
-I cant get malez recovery to work on my brother phone. after install acer liquid drivers and all dat. phone conect to pc, mount sdcard but nothing happens
Hi,
I'm having a problem trying to flash roms. I have both ViperOne and Android Revolution pushed onto /sdcard.
They show up when I press install on TWRP but after I slide to install, it fails. It shows the following:
Updating partition details...
E: Unable to open zip file.
Error flashing zip '/sdcard/viperone.zip'
Updating partition details...
This is on TWRP v2.7.1.1
Any ideas on what do would be appreciated.
Please note I can't get into normal android system and its currently stuck on a cyanogenmod bootloop.
steliosxvi said:
Hi,
I'm having a problem trying to flash roms. I have both ViperOne and Android Revolution pushed onto /sdcard.
They show up when I press install on TWRP but after I slide to install, it fails. It shows the following:
Updating partition details...
E: Unable to open zip file.
Error flashing zip '/sdcard/viperone.zip'
Updating partition details...
This is on TWRP v2.7.1.1
Any ideas on what do would be appreciated.
Please note I can't get into normal android system and its currently stuck on a cyanogenmod bootloop.
Click to expand...
Click to collapse
use twrp 2.6.3.3 to flash arhd.
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-botloader
then try to flash arhd or viper again
also check your roms MD5 before flashing them
Hi,
Here a brief of my phone
ZTE Blade Q Lux
Android 5.0.2
MSM8916
Installed exposed
Try to flash sdk21, all version but encounter error failed to update, file corrupted
Then I tried copy manually to root/system and root/meta-inf
Xposed detected SDK v80 installed but not activated
Checked the log but log error
What should I do? Please assist me
Thanks
Here what shown when flashing the SDK 21 v80 ARM
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Update failed, package corrupt
installation aborted
Lex-ON said:
Here what shown when flashing the SDK 21 v80 ARM
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Update failed, package corrupt
installation aborted
Click to expand...
Click to collapse
Use a recovery that allows disabling signature verification, for example TWRP.
TWRP Manager 3.0.0 on playstore? I tried it, there are no option to disable signsture. Or I'm doing it wrong. If there's a specific link to download or use it, highly appreciated
Thanks
Lex-ON said:
TWRP Manager 3.0.0 on playstore? I tried it, there are no option to disable signsture. Or I'm doing it wrong. If there's a specific link to download or use it, highly appreciated
Thanks
Click to expand...
Click to collapse
TWRP Manager only downloads the TWRP for your device (if any is available). You have to flash it either manually by using ADB or use an app like ROM Installer or Flashify. Best way is via ADB. If you don't know how to do this, search for "your device name TWRP ADB flash"
orville87 said:
TWRP Manager only downloads the TWRP for your device (if any is available). You have to flash it either manually by using ADB or use an app like ROM Installer or Flashify. Best way is via ADB. If you don't know how to do this, search for "your device name TWRP ADB flash"
Click to expand...
Click to collapse
Checked it. the stock ROM I downloaded from ZTE.com does not contain *.bin files. is it able to use adb flash? I was unable to do so
attached the file contents
I'm trying to install the ZIP file for the framework by flashing in recovery but it always says signature verification failed installation aborted. That's in both TWRP and CWM mode. My device is an Acer Iconia One 10 running on Android 5.1.1 and the zip file is xposed-v86-sdk22-arm64.zip any thoughts on how to solve this problem?
Hi
I am trying to install magisk 16.7 on my doogee s60 Lite android 7.0 phone. Sticking to v16 in hope google pay works.
I have unlocked bootloader in dev options, restarted into phone's native recovery mode, selected apply update from sd card, selected magisk zip file but after verification install aborted.
So I chose update from adb, which got me into bootloader, prompt now send the package
connected phone to windows 7 machine with drivers installed
adb devices
-> started successfully
typed adb sideload magisk-v16.7.zip/
and here is the response:
->sideload connection failed: no devices found
How to fix that?
You either fastboot flash the boot image that you first patch through the Magisk Manager, or you flash the Magisk zip in a custom recovery. Using the stock recovery or adb sideload won't work.