Database Develop

CM7 problem or CWM ?

Hello first,
I wanted to yesterday, the new update of CM7 make up the v40 version.
Well but every time I get an error message when CWM, if I make a "Wipe Dalvik" do
Error message: "E: unknown volume for path (/ sd-ext) ".
and if I want to update the instalation, so on "choose from sdcard zip" then stands as an error message
Finding update package ...
Opening update pack ...
E: Can not open / sdcard/download/cm40.zip (bad) Installation aborted
I've really no idea which lies ahead. The updates before they all went without problems but now not any more why whatsoever.

Ignore the /sd-ext message, that's nothing.
My guess for the other error is that you just got a bad download.

I've downloaded twice and it came the same error. I've also tried to install the v39 and also did not work. And there is always the Android comes with a triangle where a !

Odd, that graphic sounds like the stock recovery, not Clockworkmod. What version are you using? I know 3.0.1.4 doesn't get on with CM7, but it should give an assert error, not that.

Okay the problem is removed. I've now downloaded the v41 and it worked. thanks again

do you have any idea how to back to optimus 2x official firmware?

clockworkmod, adb pull, or romdump
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/

Wipe & Flashing has no effect

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!

Huawei P10 Lite, TWRP Error 9, pls HALP

Hello everyone,
My phone is in what it seems to be erecovery loop, I tried flashing images via fastboot extracted from update.app file, didnt work at all.My phone is unlocked, I flashed twrp again and downloaded latest stockrom version for my country(asked a friend about it since he has the same phone), I put those 3 files on my usb and connected it to my phone.Opened it in twrp, when i try to flash update.zip i get Error 9.I tried pretty much anyting i could find on this forum and other sources from google, nothing rly seems to work and there isnt anything at all for error 9.Do u guys by any chanse know what is the problem here?
device: Huawei P10 Lite WAS-LX1C432B194 (latest version for my country, Serbia, Eu)
phone unlocked, twrp installed, can do fastboot commands
This is what i get when trying to flash that update.zip
Code:
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Formatting Cache using make_ext4fs...
Wiping data without wiping /data/media ...
Done.
Updating partition details...
...done
Installing zip file '/usbotg/update.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
mountencrypt: failed to mount /data: Success
script succeeded:resut was []
check_write_data_to_partition,write data error
[COLOR="Red"]E:unknown command [errno][/COLOR]
update_huawei_pkg_from_ota_zip: update package from
zip failed
[COLOR="red"]Updater process ended with ERROR: 9
Error installing zip file '/usbotg/update.zip'[/COLOR]
Updating partition details...
...done

There is already a thread for this problem: https://forum.xda-developers.com/mate-7/help/softbricked-device-fix-t3159742/page5

LwannaCM said:
There is already a thread for this problem: https://forum.xda-developers.com/mate-7/help/softbricked-device-fix-t3159742/page5
Click to expand...
Click to collapse
I already firgued it out, but tnx for the response.
I bought sd card(didnt have one), did dload method, since normal one approach didnt work i used force update approach(dload moved to sd card, power off, hold vol+ + vol- + power button and it installed) also i needed to flash stock recovery beforehand(so it removes twrp, used fastboot to do it, phone was unlocked, power off connect to PC via usb cable and hold down vol- right away, then flash it through fastboot), it cant do force update with twrp still installed.Once it was done i normally booted to stock rom, phone was no longer unlocked, now i unlocked it flashed twrp and rooted it, everything works just fine.Hope it helps some1 with the same problem.
source: https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097 , there is guide thing for both normal and force update

Thank for the help. It gives me a clue but I am still struggling as the force update approach get stuck at 5%. Thanks anyway.

Need help - Stuck on recovery screen - Hard brick ?

Hi guys !
I tried to install Lineage OS 17.1 on my Xperia Z3 compact and everything went well until I installed the openGapps (before reboot like tutorial said). I'm now stuck on the recovery screen where this message appears :
"Can't load Android system. Your data may be corrupt".
as well as the following error:
"E: Failed to bind mount /mtn/staging/emulated/media/0 to /storage/emulated: No such file directory"
I can "Try again" or "Factory Data reset" but neither option works! In both cases I'm stuck here again. I can't even turn off the phone or reboot via adb shell either since it is now recognized as "unauthorized".
I read a lot of topics but I have not find an answer.
Can it be an hard brick ? Please help. Thx

Try reinstalling stock ROM using Flashtool.

Moto X4 - Error 7 while trying to flash LineageOS

Good evening. I unlocked the bootloader on my Moto X4 and started following the installation guide on LineageOS's website to install. Everything was going smoothly, I ran the copy-partitions script and proceeded with wiping data and sideloading LOS. That's where problems occured. ADB on my PC echoed "total xfer: 1.00", but LOS Recovery gave me this :
Error applying update: 7 (ErrorCode: :kInstallDeviceOpenError)
E: Error in /sideload/package.zip (status 1).
I have no clue how to solve this. I've attached my recovery log, if it helps. Any help to get LOS running will be very appreciated!!!

recovery.log
recovery.log payton - pastebin -for Sharing Code and Text.
recovery.log payton - pastebin Paste can store text, source code or sensitive data for a set period of time.
paste-bin.xyz

UPDATE: I got progress using TWRP, I successfully flashed the LineageOS zip, but I only got a bootloop. People say to change slots and try again, but I didn't have any luck with that either.

Whenever I got a boot loop, I went back in to recovery and performed a factory reset, after rebooting, things worked normally.