So I don't know what has happened but I can't flash even a single custom rom. The problem occurs in TWRP as well as CWM. Also I am on the stock partition. Tried the modified partition too. The problem is still occuring no matter what I try. The following case is of SOKP. Every other rom also has the same problem. Even after trying it via adb the problem persists.
After I select the zip file in the recovery mode,the installation starts. After that, it says:
Patching system image unconditionally...
blkdiscard failed: Invalid argument
E : Error in/data/media/0/SOKP-L_5.1.1-LMY48B-R3-20150525-cancro.zip
(Status 7)
Installation aborted.
Have you checked whether your bootloader is locked or not (because of that damned MIUI MM)? Try sending through fastboot:
Code:
fastboot oem device-info
If the "Device unlocked" comes out as false, then unlock it first by sending through fastboot:
Code:
fastboot oem unlock
It'll wipe all the content of your phone though...
shivam0909 said:
So I don't know what has happened but I can't flash even a single custom rom. The problem occurs in TWRP as well as CWM. Also I am on the stock partition. Tried the modified partition too. The problem is still occuring no matter what I try. The following case is of SOKP. Every other rom also has the same problem. Even after trying it via adb the problem persists.
After I select the zip file in the recovery mode,the installation starts. After that, it says:
Patching system image unconditionally...
blkdiscard failed: Invalid argument
E : Error in/data/media/0/SOKP-L_5.1.1-LMY48B-R3-20150525-cancro.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Extend your partition first, you'll be fine then. There is manual tutorial in Mi3 General sub forum.
Related
Hi - I've started receiving a bunch of errors on my phone indicating a lot of processes are failing. The OS version is Android 4.1.2 Jelly bean. Have tried resetting app preferences after searching through a lot of forums but these problems still persisted. Factory reset didn't help either. I'm bootloader unlocked and rooted so thought I'd flash a new ROM via RSDLite. I am unable to do this either. I receive the error "Failed flashing process. 1/12 flash gpt "gpt_signed" -> Phone returned FAIL..". On the phone itself I see the following:
E: Can't read /dev/block/misc
(Bad file number)
E: Failed to get BOS sync msg from MISC
Fastboot Reason: Flash Failure
fastboot: max download size: 100Mb
USB connected
Getvar max-download-size
Downloading ...
Flashing gpt ...
E: re-partition failed: Device or resource busy
Fastboot command failed
Fastboot menu disabled
I fear this means I have a corrupted internal SD card so no way to fix... however I'm no expert on this. Any idea how to fix please?
Thanks,
U copy/pasted another forum post , ah well it works.
It is indeed that your phones memory is corrupted.
I maybe have a solution, but first i need to know what firmware u are using.
Hazou
Hi,
I have a problem with my Moto G 2014 XT1068 which is described in topic: forums.androidcentral.com/moto-g-2013/391289-something-seriously-wrong-my-moto-g.html#post3668518
I can't do these steps, because dialog window shows up all the time, and i cant go further.
I have disabled usb debugging option and can't disable ART runtime.
First of all "Factory" in bootloader doesn't work. Wipe and factory reset via stock recovery has no effect; old android remains, the same using TWRP:
"E:Unable to open 'cache/recovery/.version' but ends successfully
and PHilz.
I've tried to flash many roms using many recoveries( TWRP - few versions up to 2.8.5 because 2.8.6 has display flickering bug, few Philz, and few others that also flicker) and fastboot and msfastboot(both on linux).
When i flash via fastboot or mfastboot using xml.zip roms everything looks ok, there are no errors, but flashing has no effect - I have still old ROM with old issue.
When i flash via different recoveries always some errors appears. For example flashing latest CM 12.1 nightly
via TWRP i get:
"E:Error executing updater binary in zip '/sideload/package.zip'
or via stock recovery (ADB sideload) get:
"(...)
Verifying update package...
E:Failed to verify whole-file signature
E:signature verification failed
Installation aborted."
Partition erase in fastboot despite "OKAY" message in CLI has no effect. As i understand this should remove all files from partitions.
This problem showed up when i discharged battery to 0% and turned on the phone.
Have you any ideas what should i try more?
Thanks in advance.
Hi,
I've tried other things to back my phone to life, like turn on usb debugging or even delete files, all via adb shell in recovery, but it is impossible. In TWRP or PhilzTouch I remount partitions with rw privileges, it look like I'm able modifying files via vi and cat to check results but when remount one more time old files still exist, so it is like there is some buffer? (maybe some security lock?), when try rm -rf files it shows up that i can't delete because it read only... (but mount says rw). After remount partitions with rw privileges wipe /data in twrp ended successfully but has no effect.
Do you know why everything looks ok, but it is not? Of course android boots up but is useless and after few minutes phone turns off.
i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.
Sounds like you both have a failed eMMC. If that is the case, and I'm certain it is, there is nothing that can be done to "save" or "restore" your devices.
Sent from my XT1031
hi, maybe any1 has already found a solution?
dihcar said:
i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.
Click to expand...
Click to collapse
I have exactly the same issue with my XT1063. Reading a lot for a solution, traying all without success.
Hopping someone can help us!
hi, i recently installed twrp for my dora and attempting to repair phone from dead boot (maybe)
when i was trying to install custom rom , log says
failed to mount '/idd' invalid argument
failed to mount '/oem' invalid argument
failed to mount '/qns' invalid argument
and the "backup" part it says
Cache (0mb)
Diag (0mb)
OEM (0mb)
Qnovo (0mb)
tried to push manually via fastboot but failed
looking for flashable zip stock rom for this AU SOV33 is pretty hard to find since this phone wont go into flashmode
any solutions on this case?
if someone kindly shares some backup stock rom via twrp i would be so thankful
thanks
Greetings everyone,
I have a P20 Pro that was a long time ago under LineageOS 15. I've upgraded it to EMUI 9 out of curiosity a few months back, but I'm not happy with it and I would like to install LineageOS 16.
From TWRP, I'm trying to install the LineageOS 16 packages that I `adp push`'ed to `/sdcard`, but I get the following error:
Code:
...
Checking for Digest file...
E3000: This package expects the value "_a" for "ro.boot.slot_suffix"; this has value "".
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineage-16.0-20190728-nightly-charlotte-signed.zip'
I've tried with numerous LineageOS 16 packages (Latest signed official and a bunch of unofficial), they all give me the same error. I also tried with TWRP 3.2.2-0 with the same result. Anyone with a similar experience please?
Everything is unlocked on the phone (Both lines are RED on recovery).
Note that when I try to wipe using TWRP 3.2.2-0, I get errors that don't happen using 3.3.1-0:
Code:
Unable to wipe Cache.
Unable to wipe /cache.
I'm using ext4 for /cache, /data and /system.
[EDIT]What seems very odd is the fact that I'm actually able to flash LineageOS 15 (lineage-15.1-20181011_144350-UNOFFICIAL) but the phone gets stuck in a reboot loop afterward. Oh well, I'm without a phone [/EDIT]
Try the latest version of the recovery and install directly from twrp
The Restless Soul said:
Try the latest version of the recovery and install directly from twrp
Click to expand...
Click to collapse
Thanks for your help - but isn't it exactly what I'm doing already? I'm using TWRP 3.3.1-0 which is the latest, isn't it?
Bumpidy bumpidy
Anyone please?
Bump bump?
Anyone at all?
You have to delete two lines from updater script and guess what this is explained in lineage thread in dev section.
forever_lol said:
You have to delete two lines from updater script and guess what this is explained in lineage thread in dev section.
Click to expand...
Click to collapse
Thank you @forever_lol! I'm looking around and I can't figure out what the "dev section" is. The P20 install instructions are here: https://wiki.lineageos.org/devices/charlotte/install
In the package ZIP file, the only script I could find is `backuptool.sh` and I don't think it's related at all. I didn't find any README either... Any pointer where I can find this "dev section" please?
EDIT: I found this thread right here: https://forum.xda-developers.com/honor-view-10/development/rom-lineageos-16-0-t3876509/page12 and there's an occurrence of where this installer script is. I'll try tonight. Thanks!
doodloo said:
Thank you @forever_lol! I'm looking around and I can't figure out what the "dev section" is. The P20 install instructions are here: https://wiki.lineageos.org/devices/charlotte/install
In the package ZIP file, the only script I could find is `backuptool.sh` and I don't think it's related at all. I didn't find any README either... Any pointer where I can find this "dev section" please?
EDIT: I found this thread right here: https://forum.xda-developers.com/honor-view-10/development/rom-lineageos-16-0-t3876509/page12 and there's an occurrence of where this installer script is. I'll try tonight. Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=79401091&postcount=357
forever_lol said:
https://forum.xda-developers.com/showpost.php?p=79401091&postcount=357
Click to expand...
Click to collapse
Thanks @forever_lol,
I had to flash partitions manually from images extracted from Huawei's `update.app`:
Code:
fastboot flash cust cust.img
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
It seems like `vendor` fails at the 2nd sparse chunk... Not sure why. Message was:
Code:
fastboot flash vendor vendor.img
Sending sparse 'vendor.img' 1/2 (440380 KB) OKAY [ 11.642s]
Writing sparse 'vendor.img' 1/2 FAILED (remote: 'Command not allowed')
Finished. Total time: 11.663s
Now I'm seeing errors in TWRP when trying to format / flash:
Code:
Failed to mount '/cust' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/system' (Invalid argument)
Any idea?
Hey man, I just gave you the link from official lineage os thread for p20 pro (placed in development section called "roms, kernels... etc") i barely answered how to bypass installation error 7 on twrp. That's all. Not sure why you looked for help in other devices forum instead of searching lineage os thread thoroughly. No offence but i have no idea what you did to your device later.
Try this guide, it solves most problems I had.
https://depl0y.com/posts/P20-Pro-LineageOS-Guide/
I'm not the most knowledgeable about these sorts of things and I had tried to flash AOSP onto my phone (my mistake). It is now bricked in the most unique way and I've been stuck on multiple unbricking threads due to one or two issues.
A couple things to mention:
1.
For the explanation in this thread, https://forum.xda-developers.com/realme-x2-pro/help/bricked-realme-x2-pro-twrp-fastboot-t4038999, I had followed natedogg20050's explanation up until the point of checking the system is folder is empty. I'm not sure on how to do that. Regardless I have typed "rm -r system" and "mv system_root system" into the terminal. There are no returning messages, and not sure if it is meant to return anything.
I then proceeded to attempt to flash stock fastboot images with the issue of system.img and vendor.img saying "Invalid sparse file format at header magic" without a "Finished" message at the end.
Rebooting results in the phone saying "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it." error, and flashing vbmeta results in "fastboot: unknown option -- disable-verity".
2.
I had attempted to format data through twrp, with an error message returning with "Failed to mount '/data' (Device or resource busy)" and "Unable to mount storage". Similarly, attempting to flash the ozip results in "Patching firmware images...
mount: Failed to mount/dev/block/bootdevice/by-name/
userdate at /data: Device or resourse busy
script succeeded: result was [/data]
Updating partition details...
...done".
I have tried repairing the file system through twrp and it failed.
Trying to change file system to EXT2 results in "Unable to mount storage".
If anyone know the solution please help me. I'm at my wit's end here and exhausted nearly all the treads. Right now the best case scenario is that I missed a solution buried somewhere in there.
thread closed at the OP request