Database Develop

Unable to update CM13

Hello guys, i was trying to update my CM 13 today and it didn't work. It made the download but once in the recovery, nothing happened :S i'm trying to understand why and i hope some of you know of this.
By the way, my TWRP version is the 2.8.7.0 if it helps..

ugh...Can't really understand what happened
You installed via OTA/cm updater? meaning you downloaded with your phone
Just download the zip directly and flash it with twrp
You'll also need to re-flash gapps unless you're using TWRP 3.0.0

Make sure that you have not installed any additional mods which alters system partition (kernels, soundmods etc.) If not, easiest solution would be to dirtyflash new one or clean install.

Same problem here.
405. CM13. TWRP 3.0.0. Merged SD card with internal storage.
In Recovery I can see folder structure but no files. I know its because of SD-encryption but I hoped I could at least see files in internal storage to update. Hope there's a solution soon. Does anyone have a workaround?
Gesendet von meinem LG-D405 mit Tapatalk

Filesystem of sdcard mount point
What is your /sdcard mount point filesystem? Mine is 'auto' (Maybe that might be causing the problem?) , and you can check by going into TWRP -> Wipe -> sdcard -> Repair or Change File System

Thank you for your answer. I checked that quickly, but couldn't find the option 'repair or change filesystem' without actually wiping the storage... I'll check again later if there's more time.

I found and changed the option from exFAT to ext4. All folders on the SD were lost in TWRP. Changed back to exFAT: couldn't see them either..

When using adopted storage (i.e. formatting external SD and using it as internal storage), then /sdcard in Android becomes /emmc in TWRP. At least it's what I see here using TWRP 3.0.0 Dark Blue.
From what I've looked, all internal storage is used only for app and app data once I started using adopted storage, so the only way I can think of using internal storage in TWRP to flash anything is either sideloading or using MTP in TWRP.

I managed updating through sideload.
1. Connect your phone to your computer via USB
2. Activate sideload in TWRP (advanced)
3. In platform-tools folder press Shift+right click to open commandline
4. If your device is connected properly ('adb devices') you can sideload zips (in platformfolder) via the command 'adb sideload filename.zip'
5. Restart device. Note: It took a few minutes for all apps to appear in the appdrawer again.
Thank you all for your help! I will looks after the folder emmc, but as I see no files, just folders anywhere, I am not that hopeful. But at least it works now

kreativpause said:
I managed updating through sideload.
1. Connect your phone to your computer via USB
2. Activate sideload in TWRP (advanced)
3. In platform-tools folder press Shift+right click to open commandline
4. If your device is connected properly ('adb devices') you can sideload zips (in platformfolder) via the command 'adb sideload filename.zip'
5. Restart device. Note: It took a few minutes for all apps to appear in the appdrawer again.
Thank you all for your help! I will looks after the folder emmc, but as I see no files, just folders anywhere, I am not that hopeful. But at least it works now
Click to expand...
Click to collapse
What did you wipe prior to your sideload? I want to do a wipe and fresh install of gapps and cm13, but I am afraid I could soft brick my phone.

I chose both. Dalvik and the other option ( I believe cache). No issues.

kreativpause said:
I chose both. Dalvik and the other option ( I believe cache). No issues.
Click to expand...
Click to collapse
Mine gets stuck at "detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" then it just reboots to TWRP again. Sideload says "
serving: 'cm-13.0-20160322-NIGHTLY-w7.zip' (~0%) * failed to read command: No error". Did you wipe system before you sideloaded?

I did not wipe anything beforehand.

Internal memory does not show on PC

Hello everybody,
I am in desperate need for help.
Received my OP3T yesterday and followed the instructions to flash Sultan's CM13 ROM, unlocking bootloader, running "fastboot OEM unlock", deleting data and system partitions, attempting to flash TWRP and even using the SuperSu root afterwards.
I now have an issue where the internal memory of the phone does not show up on PC. It does not show when I am running CM13, and does not show when I'm in the TWRP recovery menu.
- Using the mount feature in TWRP does not work.
- All my file systems are currently set to ext4.
- USB debugging is on, off course.
- Tried accessing internal memory on a different PC, and still doesn't show.
I've tried completely deleting all the partitions, re-flashed TWRP and re-flashed CM13. Also tried re-flashing the original recovery and the original OxygenOS rom.
As a result, I can only access the TWRP recovery now. I have no way to copy the CM13 zip file or any other file to the internal memory.
Anyone know what's going on?

to see internal storage in TWRP you need to enter the password you definied as android login.
to see internal storage on pc go to "Settings/developer options/usb configuration and use again "file transfer" (i hope this is the english word for "dateiübertragung")

TWRP Internal storage unable to Mount (internal 0mb) redmi note 4 (mido)

There is an akward situation, whenever i try to go into TWRP for flash any zip aur img file , TWRP does not show any such file. It is 100% sure that i transfer the flasheable zip file to the mido. But TWRP does not show. It shows 0mb internal storage. And i tried to wipe delvik cashe data system but it gives a message and error in red color that data not mount.
So for this i just formate the phone by twrp... It get easly formate by typing YES and delete all the internal storage, after that i can wipe all the stuff under advanced wipe by selecting all the options system data delvik cashe.... Etc.
After doing this i just power off the phone by twrp, and again boot the phone into twrp recovery by pressing volume up+ power button
And then twrp shows 52 gb aprx internal , so i transfer the custom rom zip file and gapps zip to the phone using computer.
After that i had flash the rom and reboot the phone into system..
The phone get started and work awsome.
Now after an hour latter , i had again reboot the device to recovery ... To flash magisk manager ... Guys i am shoked the internal storage shows 0 mb instead of actual memory.
Again does not shows any zip file, img file.
So i have to follow all the steps that i performed before formate the phone and reboot to recovery then transfer magisk and then flash it.
The problem is why twrp again and again shows 0mb error ...
So i also flash the miui using fastboot method (clear all) clean flash, then flash the twrp after that flash the custom rom.
After flashing rom , Now again reboot to recovery it shows 0 mb internal and data unable to mount.
Twrp fix temporary not permanent.
Please tell me if you find any solution for this for permanant fix twrp 0 mb error....

dheerajsinghal said:
Please tell me if you find any solution for this for permanant fix twrp 0 mb error....
Click to expand...
Click to collapse
Wrong section here.
https://forum.xda-developers.com/redmi-note-4

Hi! actually i had similar issue after restoring all partitions (not just boot data and system, but all the 10 or more partitons) on my redmi 4x. i couldnt mount the data partition it got corrupted somehow. I couldnt format it in twrp too. Reflashing everything in my flash solved the problem, just dont forget to NOT choose the option with RELOCK, or you will lock the bootloader.

Help! Tried to install custom rom and now internal storage is encrypted

So i tried to install a custom rom, now my storage is encrypted and i can't install apps or anything on my device.
I unlocked the bootloader, install twrp, it didn't ask me for a password however. I then did advanced wipe, system data cache.
I then couldn't copy anything to my internal storage, so reflashed miui using miflash tool.
My device is working fine, but when plugged in, all the folders on my internal storage come up as random numbers and letters (which i assume means its encrypted). I have tried downloading something via chrome and it says "sd card not found".
I really hope someone can help me.
Thanks!

Hi ! Do you can resolve your problem ?
I'm not expert but I think reboot to Twrp and format your data . Advanced format data yes and flash your Rom. But I don't no if you do to flash the DM Verity Encryption remover before flash your Rom ?
Stay for expert help you..

ha2ell said:
So i tried to install a custom rom, now my storage is encrypted and i can't install apps or anything on my device.
I unlocked the bootloader, install twrp, it didn't ask me for a password however. I then did advanced wipe, system data cache.
I then couldn't copy anything to my internal storage, so reflashed miui using miflash tool.
My device is working fine, but when plugged in, all the folders on my internal storage come up as random numbers and letters (which i assume means its encrypted). I have tried downloading something via chrome and it says "sd card not found".
I really hope someone can help me.
Thanks!
Click to expand...
Click to collapse
I faced similar issue when flashing custom rom.
I did some research and found out that, I have to wipe data first, reboot to fastboot (in TWRP). Boot into TWRP again using DOS shell prompt.
In this way, your phone will not be encrypted, allowing file transfer and flash from TWRP.
Hope it helps.

Hi, I managed to fix it by flashing the latest miui fastboot ROM again using mi flash tool, and then restoring a backup of my system from Google drive and miui when setting up the phone. I think I will try to flash a ROM again at some point. What do you mean by DOS shell prompt? Thanks

You need flash Forced Encryption Disabler to remove encryption of the folders. In TWRP, flash zip and reboot to recovery.
This is link to download. https://androidfilehost.com/?fid=3700668719832238534

ha2ell said:
Hi, I managed to fix it by flashing the latest miui fastboot ROM again using mi flash tool, and then restoring a backup of my system from Google drive and miui when setting up the phone. I think I will try to flash a ROM again at some point. What do you mean by DOS shell prompt? Thanks
Click to expand...
Click to collapse
im facing the same problem now. the files are all jumbled up letters, do i need to format the device before using mi flash tool?

Many errors when wiping cache partition in TWRP

Hello,
As stated in the titled I have tried to root my OP 3T and it horribly wrong. First I got the error message telling me it couldn't mount my /system partition. I googled how to fix it and discovered that I had to wipe the partition as it might be corrupt. Just to be sure that it was indeed corrupt. The size was stated as 2913MB but the used space was stated as 1728265MB. I therefor wiped it and tried to boot. Now I couldn't boot into Oxygen OS...The only thing i can boot into was fastboot and recovery. I then tried to install the LineageOS and it worked. I can finally boot to a OS. However when going in the recovery again and wiping the cache I get a slew of errors. Almost all of them are "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)". There is also one other error: "Unable to mount storage"
How do I fix this?

uptivuptiz said:
First I got the error message telling me it couldn't mount my /system partition.
I therefor wiped it and tried to boot. Now I couldn't boot into Oxygen OS...
Click to expand...
Click to collapse
System partition is the OS. So from that fact, it should now be obvious that wiping system (and therefore wiping the OS) will result in not being able to boot to OS.
Not being able to mount system is a little odd. What version TWRP? Current version is typically recommended (currently 3.2.3-1).
You can try in TWRP Wipe section, the "Format data" button. This will often fix corruption issues with data partition (format is not the same as wipe), although I'm not sure how the system partition was affected.

redpoint73 said:
System partition is the OS. So from that fact, it should now be obvious that wiping system (and therefore wiping the OS) will result in not being able to boot to OS.
Not being able to mount system is a little odd. What version TWRP? Current version is typically recommended (currently 3.2.3-1).
You can try in TWRP Wipe section, the "Format data" button. This will often fix corruption issues with data partition (format is not the same as wipe), although I'm not sure how the system partition was affected.
Click to expand...
Click to collapse
I'm using TWRP 3.2.3-1. I tried to format with the "Format data". It seems that I still can't install the OxygenOS. Also the error "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)" still accurs.
I'm still able to install and run LineageOS.

uptivuptiz said:
I'm using TWRP 3.2.3-1. I tried to format with the "Format data". It seems that I still can't install the OxygenOS. Also the error "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)" still accurs.
I'm still able to install and run LineageOS.
Click to expand...
Click to collapse
Formatting with 3.2.3-1 will remove the encryption footer. It's basically the only build of TWRP you DO NOT want to use! 3.2.3-10 is the latest but that won't reinstate your encryption footer. My advice is this. Flash TWRP 3.2.3-0, format at least /system, /data and /cache from the Wipe/Advanced screen and then Wipe everything for good measure.
Make sure you are in front of your PC when you do this. Back up everything to PC first as formatting will delete everything from Internal Storage. Make sure you have all your Install zips ready to go on your PC. Whn you're done formatting and wiping you can copy the install zips back to Internal Storage and flash OOS full Zip (or Custom ROM).

Dirk said:
Formatting with 3.2.3-1 will remove the encryption footer. It's basically the only build of TWRP you DO NOT want to use! 3.2.3-10 is the latest but that won't reinstate your encryption footer. My advice is this. Flash TWRP 3.2.3-0, format at least /system, /data and /cache from the Wipe/Advanced screen and then Wipe everything for good measure.
Make sure you are in front of your PC when you do this. Back up everything to PC first as formatting will delete everything from Internal Storage. Make sure you have all your Install zips ready to go on your PC. Whn you're done formatting and wiping you can copy the install zips back to Internal Storage and flash OOS full Zip (or Custom ROM).
Click to expand...
Click to collapse
Thanks! I will try that when i get time tomorrow. There will come an update.

uptivuptiz said:
Thanks! I will try that when i get time tomorrow. There will come an update.
Click to expand...
Click to collapse
Let me know.
Remember to reboot Recovery once you have 3.2.3-0 installed so that your format operations are carried out with that version.

Dirk said:
Let me know.
Remember to reboot Recovery once you have 3.2.3-0 installed so that your format operations are carried out with that version.
Click to expand...
Click to collapse
I have now downgraded TWRP to version 3.2.3-0 and wiped everything. I didn't backup as I don't have anything on there because it's not my main device. After wiping I tried installing OOS again and this time I get the same "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)" error and now it cant mount the /system partiton again

uptivuptiz said:
I have now downgraded TWRP to version 3.2.3-0 and wiped everything. I didn't backup as I don't have anything on there because it's not my main device. After wiping I tried installing OOS again and this time I get the same "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)" error and now it cant mount the /system partiton again
Click to expand...
Click to collapse
You're not just wiping, You're formatting. Select each of the partitions (Cache/Data/System) and format in each case. (I recommend EXT4 for Data)

Dirk said:
You're not just wiping, You're formatting. Select each of the partitions (Cache/Data/System) and format in each case. (I recommend EXT4 for Data)
Click to expand...
Click to collapse
Ok. I tried to format all the partitions with EXT4 and tried to install OOS again with a adb sideload. This didn't work and I got an error "adb sideload cannot read 'OnePlus3TOxygen.zip'". So I tried installing it with a OTG adapter and a USB inside TWRP and it worked. OOS is running and working! Thanks for the help
Now I'm just curios as to why I can't sideload...

uptivuptiz said:
Ok. I tried to format all the partitions with EXT4 and tried to install OOS again with a adb sideload. This didn't work and I got an error "adb sideload cannot read 'OnePlus3TOxygen.zip'". So I tried installing it with a OTG adapter and a USB inside TWRP and it worked. OOS is running and working! Thanks for the help
Now I'm just curios as to why I can't sideload...
Click to expand...
Click to collapse
A few possibilities:
1) OnePlus3TOxygen.zip of course isn't the name of the file as downloaded, so i assume you renamed it to something more sensible before trying to sideload? Do you have 'Hide Extensions of known filetypes' selected in Windows Explorer? Could it be that what you ended up with was 'OnePlus3TOxygen.zip.zip', which of course wouldn't work if you were trying to sideload 'OnePlus3TOxygen.zip'?
2) You didn't move your download to your platform-tools folder in adb?
3) You didn't open a CMD window in your platform-tools folder?
Anyway, good that you're back on your feet.

Dirk said:
A few possibilities:
1) OnePlus3TOxygen.zip of course isn't the name of the file as downloaded, so i assume you renamed it to something more sensible before trying to sideload? Do you have 'Hide Extensions of known filetypes' selected in Windows Explorer? Could it be that what you ended up with was 'OnePlus3TOxygen.zip.zip', which of course wouldn't work if you were trying to sideload 'OnePlus3TOxygen.zip'?
2) You didn't move your download to your platform-tools folder in adb?
3) You didn't open a CMD window in your platform-tools folder?
Anyway, good that you're back on your feet.
Click to expand...
Click to collapse
Here's what I did:
Moved the zip file to the platform-tools folder.
Kept the stock name of the zip file.
opened CMD window in platform-tools folder.
I still get the error.

uptivuptiz said:
Here's what I did:
Moved the zip file to the platform-tools folder.
Kept the stock name of the zip file.
opened CMD window in platform-tools folder.
I still get the error.
Click to expand...
Click to collapse
You wouldn't be the first. It's a common issue. You know you can just move the zip to Internal Storage and flash it with TWRP? The Recovery is MTP enabled. Useful to know for future reference. :good: