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.
Related
Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
Anyways, the message of succesfull wipe appeared (and internal storage was in fact wiped). I don't know if I should worry (everything works fine after installing CM.12.1 nightly 08/06). The previous firmware installed was OxygenOs (I had a remote session thinking they would accept a RMA but they instead installed Oxygen with the latest drivers ). Every time I try to wipe that partition again I get the same message (but it gets wiped).
Thanks for your help and sorry for my english!
trionic said:
Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
Anyways, the message of succesfull wipe appeared (and internal storage was in fact wiped). I don't know if I should worry (everything works fine after installing CM.12.1 nightly 08/06). The previous firmware installed was OxygenOs (I had a remote session thinking they would accept a RMA but they instead installed Oxygen with the latest drivers ). Every time I try to wipe that partition again I get the same message (but it gets wiped).
Thanks for your help and sorry for my english!
Click to expand...
Click to collapse
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards
Are you using latest 2.8.6.0/2.8.6.1?
davebugyi said:
Are you using latest 2.8.6.0/2.8.6.1?
Click to expand...
Click to collapse
real_pac said:
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards
Click to expand...
Click to collapse
I am using 2.8.6.1 (latest version). Unfortunately twrp doesn't allow me to repair / format that partition.
Thanks you both for your response
trionic said:
I am using 2.8.6.1 (last version). Unfortunately twrp doesn't allow me to repair / format that partition.
Thanks you both for your response
Click to expand...
Click to collapse
You're welcome but please don't a new thread write in the specific thread..
please reinstall twrp via playstore flashable zip or just flash the recovery img via adb or any oneplus one toolkit regards
real_pac said:
You're welcome but please don't a new thread write in the specific thread..
please reinstall twrp via playstore flashable zip or just flash the recovery img via adb or any oneplus one toolkit regards
Click to expand...
Click to collapse
I installed again with TWRP Manager and everything works perfectly now (no error message). Thanks again
trionic said:
Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
[...]
Click to expand...
Click to collapse
I faced this error once on twrp 2.8.6.1 a week ago. I wanted to restore my nandroid and the error repeatedly happened while restoring data-partition. I then booted the system and deleted some files from internal storage (which was about half full at the time the error occurred). Afterwards I rebooted to twrp and could successfully restore my complete nandroid. It's a bit shocking if you face this error when restoring a nandroid, because the restore process wipes the data partition first and then begins the restore.
real_pac said:
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards
Click to expand...
Click to collapse
That tip worked for me (i9192), I just install the last TWRP (I think this is not needed) and wipe /Data with ext4, wipe again to F2FS and restore, thank you.
@lost101 I need help with my XT1034. I can't push any files to my phone! When I push a file (like a 250 MB file) It says it finished in 5 seconds, which is a bit unusual. I checked in the file manager in TWRP, and it says the file is only 10 MB. Later inspecting I found out my /data /cache and /sdcard were corrupted! I think I was able to fix /data and /cache, but I can't format /sdcard :crying: I used the mkfs.f2fs command in TWRP Terminal and I was able to fix /data and /cache (I think). But I can't format /sdcard! And If you are wondering how they got corrupted, I believe I had a bad TWRP and when formatting, I think TWRP corrupted them. Looks like Dalvik Cache wasn't affected. Recovery and Bootloader working, ADB and Fastboot is also working. But when I try to check the file system in internal storage, it says "invalid partition," every other partition I checked worked. BTW I'm using TWRP 2.8.7.0 NO-THEME.
/sdcard is emulated by using files in /data/media. You can't format it.
I tried flashing gpt.bin to see if that would do anything but it looks like it didn't have any effect
@lost101 should be tagged now
TWRP > Wipe > Format Data > Yes
@lost101 It says E:Unknown MTP message type: 1
RedKill3r said:
@lost101 It says E:Unknown MTP message type: 1
Click to expand...
Click to collapse
Ignore that, everyone gets it. It means nothing.
@lost101 I still can't push files. The file pushes, but then it gets cut off and says it finished. This is where the problem is. and ADB Sideload isn't working either. I have Motorola Drivers installed.
RedKill3r said:
@lost101 I still can't push files. The file pushes, but then it gets cut off and says it finished. This is where the problem is. and ADB Sideload isn't working either. I have Motorola Drivers installed.
Click to expand...
Click to collapse
Try a different USB cable.
@lost101 FIXED IT!!!!!! My Drivers got corrupted, installing new drivers fixed it. I'm very sorry for wasting your time lost, I am truly sorry. Thank you for replying though.
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 #
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.
I searched for an answer and noticed it's a common issue. I am trying to flash a kernel on to my already flashed rom. I was wondering if there is a more current fix. More importantly, how can this be avoided in the future. Thank you guys!
Its caused by a bug/error with either the filesystem or encryption.
Did you wipe data after flashing the new ROM? Data from stock usually doesn't work with custom ROMs.
Do you have a PIN/password on Android?
Are you using the latest build of TWRP?
Press the menu button at the bottom of the screen in TWRP and post what the error message is in the red text.
It's caused by no root access
djhulk2 said:
It's caused by no root access
Click to expand...
Click to collapse
Something is probably wrong with the data partition. TWRP should always have root access.
Try in TWRP:
Wipe > Format Data > Slide to format
This will erase the data partition, so backup everything to a PC in Android first if needed. It should allow TWRP to mount /data again.
KemikalElite said:
Something is probably wrong with the data partition. TWRP should always have root access.
Try in TWRP:
Wipe > Format Data > Slide to format
This will erase the data partition, so backup everything to a PC in Android first if needed. It should allow TWRP to mount /data again.
Click to expand...
Click to collapse
I've debated on doing this. I'm not worried about losing pictures texts etc as they're backed up.
I read that it essentially leaves the device with no OS. If that's wrong please let me know!
I have found that if I choose Slot A and reboot system it reboots me in to TWRP. If I choose Slot B it runs the OS like normal (except I still have issues using Facebook and it's services).
The ROM works and I can perform all the custom mods on it. I just want to flash a kernel and the problem persists. 0 mb in storage.
It's trial and error at this point. Fail fast fail forward. I have another phone I can use but I love the OnePlus. Any help will be appreciated!
https://andi34.github.io/faq/faq_twrp.html
I'm not willing to risk it until I know how to get the custom ROM on to the storage to flash it.
Yes formating by typing in yes will wipe it all,everything including pictures, with no rom on it at all. If u choose to do that, don't close twrp. Instead you should be able mount after wards, once mounted transfer the magisk zip, twrp, and your custom rom(has to be 1.5gb not 200mb through magisk). Flash magesik, install ram disk twrp, install rom. That was a method I've done before but if u want to keep everything there is other way
fastboot boot twrp.img, that command boots twrp if u have it or don't, installing to ram disk makes it permant...this boot command is just a one time thing each time. It's what I do when new firmware update, I loose root but I regain it each time
Never heard of formating data removing the OS, that would be if you wipe the system and normal wipe is like a factory data reset and therefore will not wipe your phone of the OS
djhulk2 said:
Yes formating by typing in yes will wipe it all,everything including pictures, with no rom on it at all. If u choose to do that, don't close twrp. Instead you should be able mount after wards, once mounted transfer the magisk zip, twrp, and your custom rom(has to be 1.5gb not 200mb through magisk). Flash magesik, install ram disk twrp, install rom. That was a method I've done before but if u want to keep everything there is other way
fastboot boot twrp.img, that command boots twrp if u have it or don't, installing to ram disk makes it permant...this boot command is just a one time thing each time. It's what I do when new firmware update, I loose root but I regain it each time
Click to expand...
Click to collapse
I attempted to format. It said
"failed to mount /data (device or resource busy)
"unable to mount storage"
Try this in recovery, sometimes its known to work.
Wipe > Advanced Wipe > Check Data and press Repair or Change File System > Change File System > Change it to EXT2.
Repeat the same process selecting Ext4
Wipe > Advanced Wipe > Check Data and press Repair or Change File System > Change File System > Change it to back to EXT4.
Try formatting data after this.
drey4211 said:
I attempted to format. It said
"failed to mount /data (device or resource busy)
"unable to mount storage"
Click to expand...
Click to collapse
Since you dont care about the data on the phone I would just do 1 of 2 things. 1st I would reflash twrp on to you phone if that doesn't work then I would just grab the fastboot ROM and just flash your phone back to full stock reroot and install twrp from scratch. I would not try to start repairing partitions. I wouldn't want to worry about screwing up the EFS partition
Well in an update, I formatted the
Storage and now I'm stuck in bootloader screen. It's unlocked but I'm having a hard time flashing a ROM through adb.
I use the twrp version 3.3.1-2
Best would be to just use fast command to boot it
But it should be under wipe/format data/then type in yes
That was what I was trying to have you avoid. If your can boot to fastboot download the fastboot ROM I told you to and run the flash-all.bat file. If your on 9.5.8 make sure you use the fastboot ROM of the same version. Do not flash azip of a different version firmware like 9.5.7.
It happens to me any time I'm in twrp and flash a rom then reflash twrp. It doesn't matter if I flash Magisk or not the issue always happens. What I do is use a USB C flash drive and plug it in when I want to flash/backup a rom. This way I can always access it. After flashing any rom then booting I'm always able to access my internal storage again. It seems like a bug in twrp.
The strange part is when this bug happens your files are encrypted in a 0 folder but you can still copy from your PC to your internal storage while in twrp.
I essentially soft bricked my device. Called OnePlus and they got me up and running. That's awesome that they have that service!
Are you removing all security? Pattern, pin and fingerprints? Are you decrypted? Never had an issue with flashing a ROM causing these issues which is why I'm asking. Something you've done at some point is causing this
I'm not sure what that was. Ironically enough I am now stuck in TWRP boot loop. Hopefully I can figure this out otherwise I have to call oneplus again.
I will admit I may not know everything but it's trial and error. I don't have anyone to really teach me this so I try to read the forums and learn. You guys have been great!
ajsmsg78 said:
It happens to me any time I'm in twrp and flash a rom then reflash twrp. It doesn't matter if I flash Magisk or not the issue always happens. What I do is use a USB C flash drive and plug it in when I want to flash/backup a rom. This way I can always access it. After flashing any rom then booting I'm always able to access my internal storage again. It seems like a bug in twrp.
The strange part is when this bug happens your files are encrypted in a 0 folder but you can still copy from your PC to your internal storage while in twrp.
Click to expand...
Click to collapse
I've the same issue.. did you find a fix? So annoying