Database Info

Error updating CM13, and others.

Hi, i have the next versions:
CyanogenMod: 13.0-20161004-NIGHTLY-osprey
Kernel: 3.10.49-MPI24.107-56-g09ff0d1
And when trying to install the 1009-NIGHTLY update i get an error without a log in the cianogenmod recovery. When I try to "Apply update" and then "Choose from emulated", it shows the next message:
"E:failed to mount /data (Invalid argument)
Installation aborted"
Then, i go to see the recovery logs, but it blanks and shows the main menu again.
Why do I want to update to the latest version, having 5 days of difference with the installed version?
Because I'm having repeatedly bugs with the Firefox browser, can't update Telegram, can't connect via Bluetooth to the most of the devices, can't update the binaries of SuperSU, and other minor errors.
Which could be the cause of some of this problems?
Sorry for my poor english, Saludos!

Download the latest nightly and before installing wipe the /system /dalvik cache and /cache partition, just be aware that you will need to reflash your gaps package.

Henriquefeira said:
Download the latest nightly and before installing wipe the /system /dalvik cache and /cache partition, just be aware that you will need to reflash your gaps package.
Click to expand...
Click to collapse
Just did what you said, wiped /cache and /system partition, and when the phone reboots it stays in the Motorola logo. Seems that I can't load the installer using USB, because there is no ROM installed.
The good news are that I have access to emulated.
What am I doing wrong?

Gonzon said:
Just did what you said, wiped /cache and /system partition, and when the phone reboots it stays in the Motorola logo. Seems that I can't load the installer using USB, because there is no ROM installed.
The good news are that I have access to emulated.
What am I doing wrong?
Click to expand...
Click to collapse
You wiped your entire internal storage? If not then there is an issue with your internal storage. I once had a similar issue to this, where my phone would keep wiping it's internal storage and crash a lot, the solution was to reflash the stock ROM. Sorry for the inconvenience that I caused to you

Just as a side question, did anyone got AICP nightlies .zip stuck at extracting image to /system? I tried clean install (wipe /system, /data, /cache and dalvik) but its just stuck there. Tried multiple nightlies. Tried deleting Android and .android_secure folders in both external and internal storage. I haven't tried wiping internal storage yet (I will do it ASAP). Any tips will be great. Thanks
Broadcasted from Zeta Reticuli

Henriquefeira said:
You wiped your entire internal storage? If not then there is an issue with your internal storage. I once had a similar issue to this, where my phone would keep wiping it's internal storage and crash a lot, the solution was to reflash the stock ROM. Sorry for the inconvenience that I caused to you
Click to expand...
Click to collapse
I still don't know why cm installs a recovery that it is unstable and with less tools than TWRP. I believe that they should use at least the code of TWRP.
No problem Henriquefeira, everything has it's solution. Besize, your help was too much better than silence in this post. Now, I have to focus on try to enter to the internal storage and flash the update I have.
For that, I'm using fastboot in linux. But I don't know too much about using it. Next, I'll show you the messages that the terminal sent me:
Code:
[email protected]:~$ fastboot -p xxxxxxxxxx flash /data/media /home/imperial/Android2/cmupdater/cm-13.0-20161009-NIGHTLY-osprey.zip
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 91972855 is not a multiple of the block size 4096
fastboot: /build/android-tools-hIu7Bj/android-tools-4.2.2+git20130529/core/libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
Abortado
Do you know what it means?

Gonzon said:
I still don't know why cm installs a recovery that it is unstable and with less tools than TWRP. I believe that they should use at least the code of TWRP.
No problem Henriquefeira, everything has it's solution. Besize, your help was too much better than silence in this post. Now, I have to focus on try to enter to the internal storage and flash the update I have.
For that, I'm using fastboot in linux. But I don't know too much about using it. Next, I'll show you the messages that the terminal sent me:
Do you know what it means?
Click to expand...
Click to collapse
You can't flash the zip of a ROM via fastboot, follow this tutorial >goo.gl/JfRzZu and on the next time avoid installing the CM bundled recovery

Solved.
I flashed vía fastboot a stable twrp, then after a lot of errors and strange things i was able to flash the ROM.
Thanks a lot for your help.
I was seeing a bricked phone already jajaja.

Can't flash anything through recovery. (failed to mount "/cpefs" (Invalid Response)

Can't flash anything through recovery. (failed to mount "/cpefs" (Invalid Response)
I recently got this phone and I've been trying to install a custom rom, however, I can't seem to do anything while using TWRP. For some reason the file explorer shows no files and no /storage folder. It also says that the /system partition weights 0MB. I've already tried formatting the /data partition from EXT4 to extFAT, but it won't let me because it cannot mount the "/cpefs" partition, which I've been unable to find any information about.
I can flash the stock firmware trough ODIN, and I can flash the recovery. The internal storage works fine, but nothing shows up when I open TWRP.
I've tried formatting the data partition, repairing it, changing the partition format, wiping, installing a custom rom, installing superSU. But it won't allow me to do any of those things. Either "/data" can't be mounted, or "/cpefs" can't be mounted while formatting /data.

Cepillado said:
I recently got this phone and I've been trying to install a custom rom, however, I can't seem to do anything while using TWRP. For some reason the file explorer shows no files and no /storage folder. It also says that the /system partition weights 0MB. I've already tried formatting the /data partition from EXT4 to extFAT, but it won't let me because it cannot mount the "/cpefs" partition, which I've been unable to find any information about.
I can flash the stock firmware trough ODIN, and I can flash the recovery. The internal storage works fine, but nothing shows up when I open TWRP.
I've tried formatting the data partition, repairing it, changing the partition format, wiping, installing a custom rom, installing superSU. But it won't allow me to do any of those things. Either "/data" can't be mounted, or "/cpefs" can't be mounted while formatting /data.
Click to expand...
Click to collapse
Which phone you're using?
J7 Pro?
Secondly make sure to enable OEM unlock options from the stock ROM's Developer option!
Thirdly check the recovery patches etc of the desired recovery's webiste (you're using) and flash it through the recovery if you're facing the problem!
It'll work, mostly some users said they fixed this by the above mentioned step!
If no luck, maybe someone will sort it out for ya, soon! :laugh:
Good Luck! :good:

sosukeaizen said:
Which phone you're using?
J7 Pro?
Secondly make sure to enable OEM unlock options from the stock ROM's Developer option!
Thirdly check the recovery patches etc of the desired recovery's webiste (you're using) and flash it through the recovery if you're facing the problem!
It'll work, mostly some users said they fixed this by the above mentioned step!
If no luck, maybe someone will sort it out for ya, soon! :laugh:
Good Luck! :good:
Click to expand...
Click to collapse
Thanks for your reply. The model of the phone is SM-J710MN. The OEM unlock option is enabled, otherwise I wouldn't be able to flash the recovery. I am trying to use TWRP. Where would I find a recovery patch for this model?. Everything works fine in the recovery, but it won't let me wipe/format/repair or change ANY partition. It can't mount anything, and the error that I see the most often is that it cannot mount the /cpefs partition.

Cepillado said:
Thanks for your reply. The model of the phone is SM-J710MN. The OEM unlock option is enabled, otherwise I wouldn't be able to flash the recovery. I am trying to use TWRP. Where would I find a recovery patch for this model?. Everything works fine in the recovery, but it won't let me wipe/format/repair or change ANY partition. It can't mount anything, and the error that I see the most often is that it cannot mount the /cpefs partition.
Click to expand...
Click to collapse
try flashing a lower version of the same frimware you've already installed e.g if the latest is nougat 7.1.1 with the recent security update, try flashing with another nougat version that is lower to the recent one's security patch #

[A510] Can't mount /data on any recovery

Hi,
I wanted to reset my 510 to a fresh 4.4.4 install. So I decided to "restore to factory settings" within the android system settings menu.
kitkat CM12 4.4.4 by shreps was working fine before, I just wanted to get rid of the data in order to give the tablet away.
now I'm stuck with a soft bricked device, it seems:
- when starting the tablet, the CM screen shows, but freezes after a while
- flashing any CM version in CWM 6..0.5 by shreps shows a "error: can't mount /data"
- wipe cache / data shows the same error
- wipe dalvik cache doesn't seem to respond in any way
- I reflashed CWM 6.0.5 using fastboot flash recovery, but to no success..
what options do I have now? can I format and remount the /data partition via ADB? do I need to go to stock?if, so, how?
Thanks for your ideas!

ok, via
fastboot -w -v
i could reformat the data partition somehow.
I still got an
E:unknown volume for path [/sd-ext]
error, but it continued and works for now.

huedrant said:
ok, via
fastboot -w -v
i could reformat the data partition somehow.
I still got an
E:unknown volume for path [/sd-ext]
error, but it continued and works for now.
Click to expand...
Click to collapse
Glad you dot it going.
I just pulled my 701 out of retirement (broke my Sony z2 screen trying to change my battery) so taking a look in here.
The data format has always been a bit twitchy, but I run the latest version of TWRP for KK. I remember bricking my original Data partition wiping it because some bozo used the wrong partition info making the original recovery for JB. Exchanged the tab.
I recall the bootloader version had to match what version of the ROM you installed (JB, KK, etc), and maybe the recovery also (can't remember). Latest TWRP for KK seems to work for me as I installed Pac Rom before I retired it. TWRP Ver 2.7.1.0
As with the "Path to ext SD", that's always been there if I recall. Just means you have to install a ROM from internal memory. Although my TWRP seems to mount it fine.
But I will say, feels like I've entered the dark ages again.

May be someone can help may be the bootloader is locked, doesn't boot installed Lineage and it's bricked

I have bought an gt-n8010, which has lineage os installed, but doesn't boot (just splash screen).
So i tried odin to flash the stock rom, but it failed any writing process on the device. In Download mode there is some info written:
ODIN MODE
PRODUCT NAME: GT-N8010
CURRENT BINARY: Custom
SYSTEM STATUS: Official (What does it mean? Does it mean the Bootloader is locked and the device is bricked?)
RP SWREV: A2
But twrp (2.8.7.0 or so) is/was installed, so i booted into recovery and tried to install other custom roms, but it also failed. "Can't state /data/media".
The File Manager in TWRP shows /data but couldn't enter /data/media.
I remounted /data as RW (at least i thought first, that i did) and the file manager could show me /data/media and i thought i was sucessfull.
But the ROM i had, didn't want to install (it thought this was the wrong hardware) and the /data folder was still mounted Readonly (/cache too).
I loaded another ROM, but that needed a newer TWRP.
So i tried flashing TWRP through TWRP and failed. Tried with Odin and Failed. Tried with the DD command within TWRP and failed.
I realised /cache and /data were still mounted read only (and i assume that this is the same problem in Download Mode when trying to flash with Odin)
So, has anyone any suggestion why i can't get /data and /cache mounted in RW mode and has a solution?
Or are these just symtoms of a locked bootloader.
Finally i got it mounted rw (both Cache and and data) und could copy a file to the /data/media folder, by umount and then mount manually.
Still i either need to upgrade twrp or get a ROM which works with twrp v2.8.7.0, so any suggestions? May be dd with the right /dev/blk.... instead of "dd if=/external_sd/twrp.img of=/dev/block/platform/dw_mmc/by-name/RECOVERY" (fails with writing with I/O Error) may work. But i don´t know which one it is.

Pauleberber said:
I realised /cache and /data were still mounted read only (and i assume that this is the same problem in Download Mode when trying to flash with Odin)
Click to expand...
Click to collapse
I would try to flash a recent TWRP from in the download mode and see if this works.
If there's still the old TWRP after the flash than your eMMC is locked and needs to get replaced.

Is there any other possibility to flash from Download Mode except from Odin3 which i already tried. (Adb doesn´t seem to work detects no devices, fastboot neither).
And why does twrp mount /cache und /data read only on start up?
I also thought that something may be locked, but finally i could mount it RW in twrp by mounting it manually by using umount and mount with tha same options except rw instat of ro.

Pauleberber said:
Is there any other possibility to flash from Download Mode except from Odin3 which i already tried. (Adb doesn´t seem to work detects no devices, fastboot neither).
Click to expand...
Click to collapse
Sure, you could use heimdall (linux). But Odin 3.09 should work fine for example.
Does it even detect your device?

Yes it detects the device, it connects to the device but it seems it can´t write anything. I´ll post a screenshot later.

Is my OP 7Pro permanently broken?

I have an OP 7Pro (GM1917) that was working fine for a long time with OOS 10.3.8.
I hadn't done an upgrade for a long time, and so recently, I did an upgrade to OOS 11.0.5.1.GM21AA. After doing that, my device is unusable, and I fear that there might be something broken or damaged that causes firmware or storage to no longer function properly. All of the explanatory details follow, and please read all of that. What I'm wondering is whether the device is now permanently hosed, or perhaps if there is some way for me to fix it. Here are all of the details:
After the upgrade, my device went into a permanent boot loop when trying to boot to System.
I then did fastboot boot twrp-3.6.0_11-0-guacamole.img, and it indeed put me into TWRP. However, the /data partition is inaccessible. Whenever I try to format /data, I consistently get these messages:
Code:
Failed to mount /data (Invalid argument)
Unable to recreate /data/media folder.
Unable to mount storage
Unable to mount /data/media/TWRP/.twrps
Unable to wipe data
I go back to the bootloader and connect to my PC, and I then run these commands:
Code:
fastboot erase userdata
fastboot format:ext4 userdata
These commands successfully run with no error messages. I then go back into TWRP, but /data is still inaccessible, and I get the same error messages that I listed above when trying to format /data .
I then tried to decrypt /data, but when I do so, it asks for a password, and I have no idea what password to give. I never used any password on the device in the past. I am not allowed to decrypt /data without a password.
So, I decided to use the MsmDownloadTool to reflash my device back to OOS 10.3.8. This works fine with a different GM1917 device that I have (but which I never tried flashing to OOS 11). However, with this particular device, after going into EDL mode, I am told that I am "Connected", but a couple seconds later it gives me the "Sahara Connection Failed" message. I have double-, triple-, and quadruple-checked the device drivers, and it indeed is showing that the "Qualcomm qds 9008" driver is properly installed and active. Furthermore, as I mentioned, I have no problem using MsmDownloadTool on that PC with another GM1917 device.
I went further: I extracted payload.bin from the OOS 11.0.5.1.GM21AA installation bundle, and I extracted all of the *.img files. I flashed boot.img via fastboot and retried everything that I mentioned above, but nothing has changed.
I then went and flashed all of the *.img files. However, still nothing has changed.
When reflashing the set of all *.img files, in some cases, I was told that the file is critical and cannot be reflashed. I then ran these two commands ...
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
... but in both cases, I was told that the device is already unlocked. Trying to reflash all of the *.img files again gave me the same results: i.e., some got flashed, and others were not flashed due to being "Critical".
Also, some of the items I flashed were said to be "sparse" and their flashes were flagged with warnings, but as far as I can tell, they seem to have been flashed anyway.
Do these problems with /data and EDL and everything else mean that my device is somehow permanently damaged? Or are there perhaps one or more additional things that I can try in order to restore it to some sort of working state?
Thank you in advance for any thoughts or ideas.

This has been fixed.
I had forgotten that in the past, I was trying the OrangeFox dual-boot recovery on this device, and it had repartitioned /data.
I fixed this by booting into OrangeFox recovery via fastboot, and then using its adb sideload facility to flash that recovery. OrangeFox's adb sideload mechanism offers options to the user for repartitioning and rebuilding /data. I utilized those options and set /data back to "Stock", and after that, /data was accessible again.
At this point, I flashed OOS 10.3.8, and then flashed the appropriate TWRP and Magisk, now, my device is back up and running in that OOS version.
The EDL problem continues, but given that my device is now usable again, I am not overly concerned about this MsmDownloadTool issue at the moment. In my spare time, I'll continue to look into that.
All's well that ends well!

I think I also have the same issue but the good thing with mine is my device is still working..but every time I access storage via twrp it give me a 0mb or in accessible data no matter if I enter my password to decrypt data. Until now I just leave it as is for I haven't found any solution

I have the same issue but I can't boot at all. I'm only limited to twrp and fastboot. I was previously running 11.0.3 with Magisk and a Magisk module called xXx_nolimit, downloaded the OTA update and went to reboot to recovery before being prompted for a pattern passcode (I hadn't set any fingerprint or password) so I rebooted into twrp and clicked fix bootloader. Now as I reboot it just boots back into twrp.
I'm also getting these same messages:
Failed to mount /data (Invalid argument)
Unable to recreate /data/media folder.
Unable to mount storage
Unable to mount /data/media/TWRP/.twrps
I'm currently running apbf to bruteforce the pattern passcode that I never set in hopes to decrypt my phone. Not even sure it will work though as I don't have FBE user 0 mounted? I have my dad's phone which basically has the exact setup as mine but I didn't update it yet. Anyway to use partition or parts data from his phone to fix mine? I really don't want to wipe my /data or /userdata as it's been a while since I backed anything up.
Edit:
All I have in my /data folder is:
/data/india
/data/recovery
/data/reserve

The edl issue happended to me too and I just needed to use another msmdownloadtool version.