Related
Hello Again, I have found a few threads with the same issue but something in the middle is different, this has happened on my Nexus 5 before, and it pissed me off because i never got it resolved.
I want to convert my HTC One M8 ATT to GPE later today, but first i'm on sense with NvROM.
The ROM isn't the issue since it's been working fine for a 2 weeks now, here is the story.
What i did-
Recovery (Wanted to try out CarbonROM)
Flashed LiquidSmooths kernel ontop of Carbon, got "Unfortunately phone has stopped".
Went to recovery again to attempt to flash liquidsmooth only.
E: Unable to mount /data
E: Unable to mount /system
E: Unable to mount /cache
E: Unable to mount /sdcard
E: Wiping /data /system /cache failed!
Now, i rebooted and those errors are non existent i can flash again.
But on LiquidSmooth , The Gallery can not find my Pictures.
The Music app can not find the music anymore.
Whenever i use a File Manager , magically my files are still there.
Anybody got ideas on this one? Thanks.
>Pics related<
Try to connect the phone to a PC, and use Device Manager to format the internal memory. Backup any personal data first, if needed (and if possible).
I've heard that , that causes the eMMc or internal storage to go into Read Only mode?
anyone correct me when i`m totally wrong here.
hasn't this something to do with the so called fused location of your sd-card ?
On my phone the locations of the sdcard is shown different then when i locate them trough recovery or shell.
In android the location is something like: /root/storage/sdcard (internal memory)
the real location in my case was shown in recovery as: /root/storage/emulated/0/
And i think because i had previously installed a cm11 based rom and kernel.
And when i completely wiped my phone for a newly rom, afterwards i still had all my data on my phone, because it didn't wipe the /emulated/0 location.
so all the files are still found with a file manager because the two location i mentioned before are fused. But your apps still has the old location in his settings somewhere..
You can try to do a media rescan so your phone search for new media.... But i believe that is also done when you reboot your phone.
I had that happen to me and I was able to fix it by using the "Format" option in TWRP recovery. That, of course, wipes everything on the device but everything will be mounted correctly and properly again.
Guys, I ended up fixing it.
TWRP format fixes it but i needed a backup. Also first attempt at formatting it on TWRP had issues. E:Can't format , E: Data isn't mounted.
Ended up just going ahead and doing the Google Play Edition Conversion and that fixed the whole issue, Thanks for your time!
@TarekElsakka @djmarkd @redpoint73
i4GS said:
Guys, I ended up fixing it.
TWRP format fixes it but i needed a backup. Also first attempt at formatting it on TWRP had issues. E:Can't format , E: Data isn't mounted.
Ended up just going ahead and doing the Google Play Edition Conversion and that fixed the whole issue, Thanks for your time!
@TarekElsakka @djmarkd @redpoint73
Click to expand...
Click to collapse
so wait, aren't you going to tell us what you mean by it fixed the whole issue? were you able to back up the data first?
I'm having a slightly different (maybe similar) issue.. my at&T m8 was working fine on insertcoin (previously viper/venom) and i decided to try a very stock AT&T debloated rom.
forgot to flash the firmware first, so booted into fastboot, and was going to do that.. but it wouldn't work, gave me an error..
booted back into recovery (TWRP 2.7.0.2) and my internal storage WILL NOT MOUNT. hence, nothing works... I can see microSD files, I can attempt to flash things ,but, due to the internal "sd" (not my microsd, just using old fashioned android terminology) not mounting, every operation fails. interestingly, I can mount / (root partition) and it has the correct structure, and even some vestiges of my files.. when i say mount, i mean in recovery on the device.. not on a computer via USB.
any ideas? i'm stuck
I know i can probably format the /media/data blahblah partition (the internal storage) but I have very important photographs of my best friend's wedding and my children's recent visit to their grandparents'.. so i really really want to restore those files.. I do this kind of thing (file forensics) on OSX, windows, and some linux drives, all the time at work.. I just don't know how to access the storage on an android phone, in order to run the forensics scans etc.
thanks!!
sneef said:
so wait, aren't you going to tell us what you mean by it fixed the whole issue? were you able to back up the data first?
I'm having a slightly different (maybe similar) issue.. my at&T m8 was working fine on insertcoin (previously viper/venom) and i decided to try a very stock AT&T debloated rom.
forgot to flash the firmware first, so booted into fastboot, and was going to do that.. but it wouldn't work, gave me an error..
booted back into recovery (TWRP 2.7.0.2) and my internal storage WILL NOT MOUNT. hence, nothing works... I can see microSD files, I can attempt to flash things ,but, due to the internal "sd" (not my microsd, just using old fashioned android terminology) not mounting, every operation fails. interestingly, I can mount / (root partition) and it has the correct structure, and even some vestiges of my files.. when i say mount, i mean in recovery on the device.. not on a computer via USB.
any ideas? i'm stuck
I know i can probably format the /media/data blahblah partition (the internal storage) but I have very important photographs of my best friend's wedding and my children's recent visit to their grandparents'.. so i really really want to restore those files.. I do this kind of thing (file forensics) on OSX, windows, and some linux drives, all the time at work.. I just don't know how to access the storage on an android phone, in order to run the forensics scans etc.
thanks!!
Click to expand...
Click to collapse
Sorry, but what i did was different, and MIGHT factory reset your internal storage, i can't verify 100%.
You can do two things,
Either flash the RUU
for 4.4.3 STOCK HTC [ATT]
or Flash Google Play edition RUU and revert back to sense which will fix it too.
SENSE: http://forum.xda-developers.com/showthread.php?t=2733523
GPE: http://forum.xda-developers.com/showthread.php?t=2708589
Prior to today, I had not installed TWRP or rooted my T310 device. I believed I followed the instructions to root my device correctly (found here). Going through TWRP, I rebooted the system to install the Superuser package. I then rebooted the system, loaded up TWRP, and began to do a system wipe (followed instructions found here) to prep the flash of the rom and gapps.
I selected the following partitions to wipe: Dalvik cache, system, data and data. The instructions werent clear, so I checked both 'data' boxes.
After the wipe executed, I went to flash the rom and GAPPS I loaded to the internal sd card aaaaand... there were no .zip files. Crap. I went to reboot TWRP and it alerted me that my device does not appear to be rooted. Double crap. Not panicking, I went to mount and tried to see if I could mount the internet SD card to my device. Nothing. Windows now shows a 'Samsung_Android' device but it is listed under 'unspecified'. Reloading the drivers have done no good.
I'm guessing SuperUSer was never installed correctly *or* I did something during the reset.
I, of course, did not perform a backup prior to all of these. I have rooted my devices multiple times and it was always a breeze so why backup now? Weell...
So now I'm sitting here with a nonSU device, with no OS, no backup, and I'm unable to connect my device to Windows. Outside of loading a rom from an external SD Card, what options do I have?
jaredmac11 said:
Prior to today, I had not installed TWRP or rooted my T310 device. I believed I followed the instructions to root my device correctly (found here). Going through TWRP, I rebooted the system to install the Superuser package. I then rebooted the system, loaded up TWRP, and began to do a system wipe (followed instructions found here) to prep the flash of the rom and gapps.
I selected the following partitions to wipe: Dalvik cache, system, data and data. The instructions werent clear, so I checked both 'data' boxes.
After the wipe executed, I went to flash the rom and GAPPS I loaded to the internal sd card aaaaand... there were no .zip files. Crap. I went to reboot TWRP and it alerted me that my device does not appear to be rooted. Double crap. Not panicking, I went to mount and tried to see if I could mount the internet SD card to my device. Nothing. Windows now shows a 'Samsung_Android' device but it is listed under 'unspecified'. Reloading the drivers have done no good.
I'm guessing SuperUSer was never installed correctly *or* I did something during the reset.
I, of course, did not perform a backup prior to all of these. I have rooted my devices multiple times and it was always a breeze so why backup now? Weell...
So now I'm sitting here with a nonSU device, with no OS, no backup, and I'm unable to connect my device to Windows. Outside of loading a rom from an external SD Card, what options do I have?
Click to expand...
Click to collapse
You can either download the whole firmware and use Odin to flash or get adb setup and push a rom zip to the internal card using adb.
Sent from my SM-N900V using Tapatalk
hi,
you will need a microsd card 32gb and properly formatted that comes with a card reader for your pc.
download your rom and get it onto the card, insert the card into your device
boot to twrp, and flash,
now, if twrp still spits the no os message at you, which is an issue with twrp,
you next need to go to your wipe options, select advanced and do a full data format/wipe,
NOT SYSTEM, DATA. meaning /data and /data/media. when that completes you should be sorted
but expect your initial boot of the new rom to take a little longer.
never wipe system with twrp. the rom's updater-script will manage that function.
m
Thank you both. I lost my SD cards and card reader in a move so while that orders, I will attempt to utilize ADB. I'm pretty green but I'm certain there are guides out there..
moonbutt74 said:
hi,
you will need a microsd card 32gb and properly formatted that comes with a card reader for your pc.
download your rom and get it onto the card, insert the card into your device
boot to twrp, and flash,
now, if twrp still spits the no os message at you, which is an issue with twrp,
you next need to go to your wipe options, select advanced and do a full data format/wipe,
NOT SYSTEM, DATA. meaning /data and /data/media. when that completes you should be sorted
but expect your initial boot of the new rom to take a little longer.
never wipe system with twrp. the rom's updater-script will manage that function.
m
Click to expand...
Click to collapse
I'm having a hell of a time getting the rom to install from the SD card. I believe I am not formatting the card correctly. Is there a guide on how to do so? I have a primary partition in SD in FAT32 and the other partition as EXT4 but no luck. Any help is appreciated.
jaredmac11 said:
I'm having a hell of a time getting the rom to install from the SD card. I believe I am not formatting the card correctly. Is there a guide on how to do so? I have a primary partition in SD in FAT32 and the other partition as EXT4 but no luck. Any help is appreciated.
Click to expand...
Click to collapse
hi,
your external sdcard should be formatted as single partition fat32 unaligned,
if you running windows, use bootice, look it up
On linux , gparted may give you issues, if so, on debian at least there is another better utility
though the name escapes me at the moment, disk manager i think.
m
moonbutt74 said:
hi,
your external sdcard should be formatted as single partition fat32 unaligned,
if you running windows, use bootice, look it up
On linux , gparted may give you issues, if so, on debian at least there is another better utility
though the name escapes me at the moment, disk manager i think.
m
Click to expand...
Click to collapse
Well I was able to find a good stock firmware download, flashed that via Odin and I'm back to square 1. I am going to forego the external SD route. Perhaps too technical for me or some other hang up is abound but I am leaving that method alone for now. Thank you for your help : )
HELLO, and thanks for reading me, so today i made the jump and wanted to upgrade stock rom of my xperia S, to the marshmallow rom via rtwp.
so i unlocked the bootloader proprely,but while merging the partitions 14 and 15 to increase the volume, i think something went wrong, after that i managed to continue the process and pushed the rom, i even got the loading screen witch ended ( of course ) by "encryption unsuccessful" and looploading.
inside the twrp i see that the sd card is 0 mb and cannot be accessed or wiped or formatted, i always have lot of errors :
cant't mount /data ( no such device ).
unable to mount storage.
unable to wipe /sdcard.
unable te recreate and sec-folder.
i tried many tricks but nothing is happening, so i flashed again to rtwp and its loopbooting to it, even the rom is lost and adb shell doesnt recognize the device.
fastboot is actually the only thing have access to.
please i need help, i'm desperate !
lotfix said:
HELLO, and thanks for reading me, so today i made the jump and wanted to upgrade stock rom of my xperia S, to the marshmallow rom via rtwp.
so i unlocked the bootloader proprely,but while merging the partitions 14 and 15 to increase the volume, i think something went wrong, after that i managed to continue the process and pushed the rom, i even got the loading screen witch ended ( of course ) by "encryption unsuccessful" and looploading.
inside the twrp i see that the sd card is 0 mb and cannot be accessed or wiped or formatted, i always have lot of errors :
cant't mount /data ( no such device ).
unable to mount storage.
unable to wipe /sdcard.
unable te recreate and sec-folder.
i tried many tricks but nothing is happening, so i flashed again to rtwp and its loopbooting to it, even the rom is lost and adb shell doesnt recognize the device.
fastboot is actually the only thing have access to.
please i need help, i'm desperate !
Click to expand...
Click to collapse
Do you know about adb sideload?it can help you in this case.
Check your partition if you merged p14 n 15 correctly or not.
Convert data and cache to ext4 and again return to f2fs.
without merging p14 and p15 the marshmallow rom can boot but you can only use 2 gb as data.
The MM requires
System as ext4
cache and data as f2fs.
so check if you done this.
ok, just figured out where the error was after merging the 2 partitions i skipped the last step after writing partition
mkfs.f2fs -r 16384 /dev/block/mmcblk0p14
that's because i followed another tutorial rather than xda ! so basically MY FALT !
but to restore my phone the only method that worked is to use flashtool and go back with original tft !!
after following the "right" tutorail everything went fine ! and i have a mooth brand new phone on marshmallow :laugh:
lotfix said:
HELLO, and thanks for reading me, so today i made the jump and wanted to upgrade stock rom of my xperia S, to the marshmallow rom via rtwp.
so i unlocked the bootloader proprely,but while merging the partitions 14 and 15 to increase the volume, i think something went wrong, after that i managed to continue the process and pushed the rom, i even got the loading screen witch ended ( of course ) by "encryption unsuccessful" and looploading.
inside the twrp i see that the sd card is 0 mb and cannot be accessed or wiped or formatted, i always have lot of errors :
cant't mount /data ( no such device ).
unable to mount storage.
unable to wipe /sdcard.
unable te recreate and sec-folder.
i tried many tricks but nothing is happening, so i flashed again to rtwp and its loopbooting to it, even the rom is lost and adb shell doesnt recognize the device.
fastboot is actually the only thing have access to.
please i need help, i'm desperate !
Click to expand...
Click to collapse
I encountered this issue more than once
The 1st time I managed to fix it by Emma the xperia official flashtool and returned to stock
The 2nd time I just flashed doomlord. Kernel with CWM booted to cwm wiped data and internal and then reflashed twrp and all was good with our errors..
I think it's something with twrp having trouble updating to the new partition table. I hope this works for u
I have the same problem, and after recovering to stock with emma I still cant see my SD card, not even on the computer. No internal storage for my Xperia S, it shows its empty.
What to do?
Hello I encounter the same problem while I try to flash to 7.1.2 from 6.0 . Sd card is 0 mb. Is there anyway to fix this ? I cant even flash stock rom any more uploaded some
I was running oos based nougat custom rom with blu spark recovery. Then flashed official ob1, didnt like it, wiped cache/data/system and reinstalled my old oos nougat rom (audax 4.7.6). Now i get the above mentioned message..
Things i tried:
- addionally wipe internal storage and media (installed rom via adb sideload then)
- reformat system/cache/date with ext4
I googled the error and for most people (threads werent particularly concerning the op5t however) it seems that just wiping data and reinstalling the rom did the trick. Not for me though..
What can i do now?
Solution: reformating the data partition with ext4 is not enough. I had to format to FAT and right after that again to ext4, reboot to system and boom, it worked!
PS: i wonder what data is on the internal storage partition that i deleted? I didnt have any data on the phone, i just wonder.. It isnt somehow crucial to the phone?!
I think the decryption key is somehow embedded into the internal storage as wiping /data does not delete the PIN/pattern. Might be a hidden partition or something similar that is not wiped when wiping /data as long as it is ext4.
Your data is gone. It failed to completely encrypt and now there's nothing that can be done. Format /data as ext4 and let it try encrypting again
I have the same problem exactly. Can you explain in steps you have installed then format or how?
I have the same problem exactly. Can you explain in steps you have installed then format or how?
Click to expand...
Click to collapse
I had the exact same problem. But it is an easy fix but does require wiping your internal storage.
So the save way of doing this would be:
1. Backup all your data by going to TWRP or your ROM if that still works. Plug in an USB cable and use MTP or the adb pull command to backup your data
2. Reflash OB1 with no root (like Magisk of SuperSU) if you have TWRP. This will cause you to have the stock recovery again. I also recommend to do a clean flash (Wiping system and data before flashing the rom).
3. Download the rollback build from Oneplus [HERE] and copy this to the internal storage.
4. Boot into the stock recovery flash the rollback build. THIS STEP WILL WIPE YOUR INTERNAL STORAGE.
5. Now you have OxygenOS 4.7.5. Download OxygenOS 4.7.6 Incremental Update [HERE]
6. Go back to the Stock recovery and flash the incremental 4.7.6 zip.
7. You have the latest version now. So boot to fastboot reflash TWRP and flash SuperSU or Magisk in TWRP to regain root
Guys I did a fail, i had OB3 installed, and I wanted to try RR so I wiped system and when I tried to install I have seen error 7 saying its for dumpling not for oenplus5t.
So I restored.... But instead restoring OB3 I have restored stock Nougat rom -.- I have even stock recovery now, what is the best way to fix it?
Can i change to FAT and stay and dont go back to ex4 again?
Hi i don't know if u r reading this but if you are please help me cause I'm so lost and confused over this since yesterday...
so 2 days ago my phone started lagging and hanging and freezing until i realized i have got this issue with data encryption
i have a rooted sony z2 with TWRP Custom recovery
first i didn't know it was with data encryption failure so i literally factory reset and installed all my apps and data again and again!!! after every time my phone started to lag !!
after one whole day of trying everything i finally realized its actually with the data encryption and i should change my ex4 to something else... so here again i wiped the phone and changed to ex3 and installed and all my data and apps all over again
but after a couple hours...same problem again.....
im literally so tired of not knowing what to do ! my head hurts so much due this ugh....
i havent changed to FAT from ex3 so im wondering if it will finally solve my problem permanently if i change to FAT ??
And if it did can i just keep it on FAT forever ?
Please guide me thanks ...!
Lasersdude said:
I was running oos based nougat custom rom with blu spark recovery. Then flashed official ob1, didnt like it, wiped cache/data/system and reinstalled my old oos nougat rom (audax 4.7.6). Now i get the above mentioned message..
Things i tried:
- addionally wipe internal storage and media (installed rom via adb sideload then)
- reformat system/cache/date with ext4
I googled the error and for most people (threads werent particularly concerning the op5t however) it seems that just wiping data and reinstalling the rom did the trick. Not for me though..
What can i do now?
Solution: reformating the data partition with ext4 is not enough. I had to format to FAT and right after that again to ext4, reboot to system and boom, it worked!
PS: i wonder what data is on the internal storage partition that i deleted? I didnt have any data on the phone, i just wonder.. It isnt somehow crucial to the phone?!
Click to expand...
Click to collapse
Finally. Thank you so much!
Hello, some time ago i posted something about my bricked phone, i did it again but not so badly.
So basically i tried to flash a GSI, and i kind of succeeded, the Phone starts and it asks me to put the password to start android, when i put it works but it says that the password i put was correct but the data was corrupt, i can go to TWRP and go in the files of an SD Card i have but, i cannot put anything in my internal storage via pc but luckily i have a chromebook, it also doesn't transfer to the internal storage, i tried to connect to my pc multiple times but it didn't work, so i want to know if i can re-install the Stock Rom via sd card with the help of my chromebook (it has 4gb)
If you are coming from Stock to GSI, you may encounter this encryption problem. The easiest way is to flash stock recovery after flashing GSI. Then boot, and when it asks you to enter password, and it fails, it tells you to reboot and the stock recovery will format your internal storage (TWRP can't).
If you want to get back to stock, just flash some stock firmware in fastboot (wiping data)
TWRP actually CAN format encrypted storage. It justs happens it won't work at the first try. You have to format two to three times, and on each format you need to reboot to TWRP until you format again and the red letters (errors) stops appearing. I do this all the time with 64-bit Treble TWRP and has never failed after doing this process.