Database Info

(SOLVED) [Q] [HELP] Motorola NOOB! Mount point information for XT925?

Hi there, I seem to have messed up my mounting partitions while trying to deodex Stock JB Central Europe. I basically used xultimate to pull the files and deodex then tried using adb shell to mount the system partition and copy them over. After I rebooted the phone, it would get stuck on unlocked bootloader warning or on the motorola logo. I hard reset into recovery and restored a nandroid backup and once booted into android found so many folders under the Storage folder such as "asec", "obb", rfs0" and so on. Now, when I try to wipe dalvik-cache in recovery, i get the following error: "E: unknown volume for path [/sd-ext]". Also, when i try flashing custom rom's and reboot, it gets stuck on the unlocked bootloader warning and wont load - while in recovery after flashing, i also get another error something like this: "E: cant load /cache/recovery.log" or similar. I also sometimes have issues mounting system, cache partitions, data and internal storage, all depending on which custom recovery i am using. I read on another site that downgrading to ics might solve mounting problems so I forced a downgrade to ics but that didnt work either and am still on ics.
Is there a way to restore the partitions correctly or are they stuck this way? Would mounting and remounting solve this problem? Any help would be much appreciated and would very much appreciate it if someone could upload their mount point info so i could use to try and fix it.
Many thanks in advance.
EDIT: Managed to flash Slim Bean 4.3 Official using OUDHS recovery without wiping cache and dalvik-cache at first. After reboot, it would bootloop so went to recovery and wiped cache and dalvik-cache then it worked. Still no sd-ext and some apps can't write or backup to external memory such as Go Backup & Restore Pro so what remains is to mount/unmount the partitions correctly.

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.

Disable encryption protection?

Hi Guys
Im having trouble flashing new Roms to my S7. When I enter TWRP recovery, it shows my device as 0MB and it doesnt picK up any files. I looked into this and read that Encryption should be disabled on the handset. I followed instructions to do this and noticed that there is no option for Encryption Protection. Its not there!
I disabled any passwords and Pin numbers to erase decryption and it still didnt work!
last resort was to try a factory reset and the device restarted to recovery and failed as TWRP recovery cant find any mounted devices due to the encryption crap.
Any help appreciated.
Chris

scientificharmony said:
Hi Guys
Im having trouble flashing new Roms to my S7. When I enter TWRP recovery, it shows my device as 0MB and it doesnt picK up any files. I looked into this and read that Encryption should be disabled on the handset. I followed instructions to do this and noticed that there is no option for Encryption Protection. Its not there!
I disabled any passwords and Pin numbers to erase decryption and it still didnt work!
last resort was to try a factory reset and the device restarted to recovery and failed as TWRP recovery cant find any mounted devices due to the encryption crap.
Any help appreciated.
Chris
Click to expand...
Click to collapse
Hi mate
Seems like you did not format your data partition during TWRP installation.........
Try flashing your custom rom from the External SD card......your data partition has all your app , files , passwords, photos...there is still a chance that there it may be a incompatibility issue between your apps and the new rom....that is why they recommend a factory reset when flashing a new custom rom

MAX 404 said:
Hi mate
Seems like you did not format your data partition during TWRP installation.........
Try flashing your custom rom from the External SD card......your data partition has all your app , files , passwords, photos...there is still a chance that there it may be a incompatibility issue between your apps and the new rom....that is why they recommend a factory reset when flashing a new custom rom
Click to expand...
Click to collapse
hi mate
thanks for your reply. I dont have an external SD card
Is there any other way of sorting this? I am downloading a stock rom as we speak.

scientificharmony said:
hi mate
thanks for your reply. I dont have an external SD card
Is there any other way of sorting this? I am downloading a stock rom as we speak.
Click to expand...
Click to collapse
Hi
TWRP can not handle Samsung encryption . if you wish to use TWRP and have access to the Data partition ( internal SD card) you need to format it so the encryption is disabled ( you lose all your apps , data and user configuration AKA factory reset) , you can have TWRP and data encryption but mods and roms have to be flashed from external memories also you will not have available MTP in recovery or factory reset from it.
There is no way to disable data encryption without format data.....

Ok, I got a friends SD card and placed the Rom on there. I can now see the Rom but the trouble is, TWRP wont let me wipe Dalvik / data / system / cache as it wont mount the storage....
can I still apply the ROM?

Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all of your data.

scientificharmony said:
Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all of your data.
Click to expand...
Click to collapse
That is why I point it out " factory reset is recommended when flashing custom rom" if you wish to flash a custom rom you will have to format your data partition and flash the data verify file........

MAX 404 said:
That is why I point it out " factory reset is recommended when flashing custom rom" if you wish to flash a custom rom you will have to format your data partition and flash the data verify file........
Click to expand...
Click to collapse
I have tried to format/wipe data. TWRP keeps saying it failed as it cant mount the storage.
I tried flashing the stock rom via odin and it also failed as it goes to recovery to wipe data and it fails again as it cant mount storage.

scientificharmony said:
I have tried to format/wipe data. TWRP keeps saying it failed as it cant mount the storage.
I tried flashing the stock rom via odin and it also failed as it goes to recovery to wipe data and it fails again as it cant mount storage.
Click to expand...
Click to collapse
How did you flash the stock rom...which files did you use?
Wipe data is not enough you have to Wipe / FORMAT DATA and type yes....

1 To get rid of encryption, go to "wipe", format data (TWRP) (keyboard will pop up) then type "yes" and format it, then reboot to recovery
2. After flashing this, hit wipe, full wipe (this will clean all internal memory and your data will be lost
3 you can test if encryption is still enabled, if TWRP shows error about not mounting data your phone is still encrypted
Sent from my SM-G930F using XDA-Developers mobile app

Josh Smith10 said:
1 To get rid of encryption, go to "wipe", format data (TWRP) (keyboard will pop up) then type "yes" and format it, then reboot to recovery
2. After flashing this, hit wipe, full wipe (this will clean all internal memory and your data will be lost
3 you can test if encryption is still enabled, if TWRP shows error about not mounting data your phone is still encrypted
Sent from my SM-G930F using XDA-Developers mobile app
Click to expand...
Click to collapse
What version of TWRP are you guys using and what version Super SU?

Delete

[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.

0 mb in TWRP internal storage

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