Hi All
I've posted this on the CM forums, but I thought I would get better help here
Link to the original post in the CM forums -> http://forum.cyanogenmod.com/topic/22941-nandroid-backup-freezes-on-clockworkmod-never-completes/
So I was flashing the final version of Cyanogenmod (7.0.2.1) last week and I thought I'd back up my device before doing it - Since CWM3 always gave me an issue, I'm currently on Amon_RA 2.2.1 (I think that's the version)
Turns out, that Nandroid just freezes when it is backing up a file in sd-ext
It's called #10956 (yes, including the quotes)
Just struck an idea that I could just go to Root Explorer and delete that file (knowing the consequences could be catastrophic)
So I kick started Root Explorer and mounted my device as Read/Write
I went to /sd-ext/lost+found and I saw that the file #10956 was 3076.00 GB - Yes, that is GB - But the file could never be deleted
I'm assuming that the file is corrupt and that's causing my Nandroid backups to freeze and never complete.
Any way how I could get rid of this file? Ofcourse, I'll be going into Amon_RA recovery and performing a backup before deleting that file
Any help would be appreciated
Thanks!
[edit: I have a 8GB class 10 Transcend MicroSDHC. Amon_RA never failed a Nandroid backup for me. It's only Clockworkmod - I've tried the older versions of CWM, and the backup never finishes. I'm forced to use Amon_RA instead]
Note:
I've tried sticking the SDCard on my Windows 7 box, but since /sd-ext is a partition instead of a folder, I cannot even see that partition
I had partitioned my card with CWM3.x - This was way back when I was on CM7 RC1 or RC2. However after partitioning, Nandroid never froze, so I'm assuming that stuff went wrong sometime later
I understand that a lot of folks are having issues with CWM3.x and are using older versions or using Amon_RA - My question is how do I get rid of that file "#10956" from the /sd-ext/lost+found directory? Since I think deleting that file might cause some issues in the future, but atleast my Nandroid will finish
[EDIT] - Uploaded 2 attachments from Root Explorer
chetanthaker said:
Hi All
I've posted this on the CM forums, but I thought I would get better help here
Link to the original post in the CM forums -> http://forum.cyanogenmod.com/topic/22941-nandroid-backup-freezes-on-clockworkmod-never-completes/
So I was flashing the final version of Cyanogenmod (7.0.2.1) last week and I thought I'd back up my device before doing it - Since CWM3 always gave me an issue, I'm currently on Amon_RA 2.2.1 (I think that's the version)
Turns out, that Nandroid just freezes when it is backing up a file in sd-ext
It's called #10956 (yes, including the quotes)
Just struck an idea that I could just go to Root Explorer and delete that file (knowing the consequences could be catastrophic)
So I kick started Root Explorer and mounted my device as Read/Write
I went to /sd-ext/lost+found and I saw that the file #10956 was 3076.00 GB - Yes, that is GB - But the file could never be deleted
I'm assuming that the file is corrupt and that's causing my Nandroid backups to freeze and never complete.
Any way how I could get rid of this file? Ofcourse, I'll be going into Amon_RA recovery and performing a backup before deleting that file
Any help would be appreciated
Thanks!
[edit: I have a 8GB class 10 Transcend MicroSDHC. Amon_RA never failed a Nandroid backup for me. It's only Clockworkmod - I've tried the older versions of CWM, and the backup never finishes. I'm forced to use Amon_RA instead]
Note:
I've tried sticking the SDCard on my Windows 7 box, but since /sd-ext is a partition instead of a folder, I cannot even see that partition
I had partitioned my card with CWM3.x - This was way back when I was on CM7 RC1 or RC2. However after partitioning, Nandroid never froze, so I'm assuming that stuff went wrong sometime later
I understand that a lot of folks are having issues with CWM3.x and are using older versions or using Amon_RA - My question is how do I get rid of that file "#10956" from the /sd-ext/lost+found directory? Since I think deleting that file might cause some issues in the future, but atleast my Nandroid will finish
[EDIT] - Uploaded 2 attachments from Root Explorer
Click to expand...
Click to collapse
Either UFS explorer (not free, but works great) or
DiskInternals Linux Reader (free, but i've never used it http://www.diskinternals.com/linux-reader/)
Either one of these should get you access to the EXT partition via your card reader/windows pc.
You could also just connect your phone to Linux PC, and mount USB - it'll also mount EXT partition to the Linux PC, and you'll be able to use Linux disk tools on it.
Connect your phone to a computer with linux, then you see both partitions when you mount. It's easy to get it running with a LiveUSB setup like this #2 here http://www.ubuntu.com/download/ubuntu/download
The Window$ DiskInternals Ext2/3/4 trial could also be enough to let you delete the file.
Hi,
This is my first android device, so am pretty much a newbie for android.
Have created this mod to mount external SD card partition as internal partition.
I took pointers from a lot of threads on xda forums to get this working, so I feel bound to share it.
Note: Have only tested it with Android 4.1.
(I'm not responsible for any Damage to your phone. Use at your own risk.)
Note: This will likely result in data loss. Backup!
Required :
1. Root Access
2. init.d support click here
3. Root Browser click here
4. SManager click here
5. An sd card (duh!) (with class 10 SD cards preferable)
6. Some way to partition your SD Card (like MiniTool Partition Manager)
Install instructions:
1. Create two ‘fat32’ partitions on SD card(EDIT: PS: both partitions should be Primary). Your first partition will be mounted as normal extSd card, and your second partition will be mounted as internal SD Card for your apps. (I partitioned my 64GB(10^9 bytes) sd card with ~16 GB 1st partition and ~42 GB 2nd partition)
2. Copy and paste “mountSd” to etc/init.d folder. (If you don’t have such a folder, means you lack init.d support. click here and follow instructions to enable it) This script creates another mount point called ‘sdcard2’ and mounts current internal sd card there. It also tries to mount second partition to ‘sdcard0’ location, but seems to fail some times (as fat32 is not natively supported linux partition it seems, but could be wrong), so step 3 is required.
3. Copy ‘mountSdFailSafe.txt’ to your phone’s ‘/data’ folder. Now with ‘SManager’, register this file as script with ‘su’ and ‘boot’ selected. (click and hold script -> in context menu click ‘Open As..’ -> ‘Script/Executable’ -> Is Script = true, select ‘su’ and ‘boot’ buttons)
4. Restart.
This should do it. Once restarted, second partition will be shown as internal memory.
Note:
You will lose all app data and other app related customizations. You may be able to restore it by simply copy pasting ‘Android’ folder from ‘/storage/sdcard2’ to ‘/storage/sdcard0’. This has not been tested by me but should work theoretically (as I started with a blank phone, and so did not need to back up my app data). Or you could use Titanium Backup.
Some Issues that occur due to this mod:
I have been using this mod since the past 2 weeks, and the phone is quite stable with this mod.
The only issue I have faced is that when connected to PC (Windows 8) through USB, ‘My Computer’ keeps crashing unless and until you disconnect the phone. Otherwise it seems to be working fine. To circumvent this issue I have been using Samba to share files between PC and my phone.
Please share how it works out for you guys.
Other Notes:
I tried to get this working with ext4 partition, which has a +ves that it will not require step ‘3’ of install instructions and supports file sizes >4GB, but there are loads of permission issues happening, which I could not solve.
(Thought of setting “set GID” bit and then finding and adding all users to root group but failed. Also tried to set owner group ‘sdcard_rw’ without much success. May be someone who knows linux better may know how to solve this, Could not find much help on the forums as it seems others are facing a similar problem see more)
Thanks to:
For basic idea (PS: do not use the given method exactly as you will end up in a boot loop. For some reason, ‘sdcard1’ mount point has to be mounted by system only and can’t be mounted any other way, it seems.)
http://forum.xda-developers.com/showthread.php?t=2180733
Edit:
Simplified installation if you do not care for easy accessibility to your orig internal memory:
Use this video tutorial by ashwin123:
The only exceptions are that, you need to partition your card,
and you have to use the file 'mountSdFailSafe.txt' instead of the file in the package mentioned by him.
Nice
Waiting for someone to test it n confirm it successfully works
Still here
N!geR -> E!ch0
NisJ said:
Hi,
This is my first android device, so am pretty much a newbie for android.
Have created this mod to mount external SD card partition as internal partition.
I took pointers from a lot of threads on xda forums to get this working, so I feel bound to share it.
Note: Have only tested it with Android 4.1.
(I'm not responsible for any Damage to your phone. Use at your own risk.)
Note: This will likely result in data loss. Backup!
Required :
1. Root Access
2. init.d support click here
3. Root Browser click here
4. SManager click here
5. An sd card (duh!) (with class 10 SD cards preferable)
6. Some way to partition your SD Card (like MiniTool Partition Manager)
Install instructions:
1. Create two ‘fat32’ partitions on SD card. Your first partition will be mounted as normal extSd card, and your second partition will be mounted as internal SD Card for your apps. (I partitioned my 64GB(10^9 bytes) sd card with ~16 GB 1st partition and ~42 GB 2nd partition)
2. Copy and paste “mountSd” to etc/init.d folder. (If you don’t have such a folder, means you lack init.d support. click here and follow instructions to enable it) This script creates another mount point called ‘sdcard2’ and mounts current internal sd card there. It also tries to mount second partition to ‘sdcard0’ location, but seems to fail some times (as fat32 is not natively supported linux partition it seems, but could be wrong), so step 3 is required.
3. Copy ‘mountSdFailSafe.txt’ to your phone’s ‘/data’ folder. Now with ‘SManager’, register this file as script with ‘su’ and ‘boot’ selected. (click and hold script -> in context menu click ‘Open As..’ -> ‘Script/Executable’ -> Is Script = true, select ‘su’ and ‘boot’ buttons)
4. Restart.
This should do it. Once restarted, second partition will be shown as internal memory.
Note:
You will lose all app data and other app related customizations. You may be able to restore it by simply copy pasting ‘Android’ folder from ‘/storage/sdcard2’ to ‘/storage/sdcard0’. This has not been tested by me but should work theoretically (as I started with a blank phone, and so did not need to back up my app data). Or you could use Titanium Backup.
Some Issues that occur due to this mod:
I have been using this mod since the past 2 weeks, and the phone is quite stable with this mod.
The only issue I have faced is that when connected to PC (Windows 8) through USB, ‘My Computer’ keeps crashing unless and until you disconnect the phone. Otherwise it seems to be working fine. To circumvent this issue I have been using Samba to share files between PC and my phone.
Please share how it works out for you guys.
Other Notes:
I tried to get this working with ext4 partition, which has a +ves that it will not require step ‘3’ of install instructions and supports file sizes >4GB, but there are loads of permission issues happening, which I could not solve.
(Thought of setting “set GID” bit and then finding and adding all users to root group but failed. Also tried to set owner group ‘sdcard_rw’ without much success. May be someone who knows linux better may know how to solve this, Could not find much help on the forums as it seems others are facing a similar problem see more)
Thanks to:
For basic idea (PS: do not use the given method exactly as you will end up in a boot loop. For some reason, ‘sdcard1’ mount point has to be mounted by system only and can’t be mounted any other way, it seems.)
http://forum.xda-developers.com/showthread.php?t=2180733
Click to expand...
Click to collapse
Am interested to try this but before I do, just wanted to check when you say data is lost, is it due to the lost of the original /data partition? Or just due to the sd card's partition?
What's the outcome when this is done, I mean do we have two data partitions one from the original phone's memory and another with the sdcard? And in the settings menu, will we get to choose to send apps over to sd? Thanks
grim_ripper said:
Am interested to try this but before I do, just wanted to check when you say data is lost, is it due to the lost of the original /data partition? Or just due to the sd card's partition?
What's the outcome when this is done, I mean do we have two data partitions one from the original phone's memory and another with the sdcard? And in the settings menu, will we get to choose to send apps over to sd? Thanks
Click to expand...
Click to collapse
Your application data will be lost in a way, as orig internal sd card will be mounted to 'sdcard2' mount point(newly created). All your app data will be installed to your memory card's second partition, which is now the new internal sdcard. To access your orig data, you will have to go to it through a file manager, and apps or media scanner will not be able to access this memory any more.
The scripts provided will not format your internal memory.
Still apk files, dalvik cache etc, will still take up your original internal memory's space.
Partitioning your sd card will probably format it as well unless you take special precaution (ie. through shrink volume).
Hope it makes sense...?
NisJ said:
Your application data will be lost in a way, as orig internal sd card will be mounted to 'sdcard2' mount point(newly created). All your app data will be installed to your memory card's second partition, which is now the new internal sdcard. To access your orig data, you will have to go to it through a file manager, and apps or media scanner will not be able to access this memory any more.
The scripts provided will not format your internal memory.
Still apk files, dalvik cache etc, will still take up your original internal memory's space.
Partitioning your sd card will probably format it as well unless you take special precaution (ie. through shrink volume).
Hope it makes sense...?
Click to expand...
Click to collapse
It makes sense, just am confused on how the system will still recognize the original storage when the sd card's storage is supposingly replacing it. Could you post a screen shot of your storage from settings?
grim_ripper said:
It makes sense, just am confused on how the system will still recognize the original storage when the sd card's storage is supposingly replacing it. Could you post a screen shot of your storage from settings?
Click to expand...
Click to collapse
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...
NisJ said:
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...
Click to expand...
Click to collapse
Can u do a tutorial video how to install this script bro?
Cuz the installation steps r bit complicated
Still here
N!geR -> E!ch0
NisJ said:
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...
Click to expand...
Click to collapse
Phone keeps rebooting now, couldn't copy it to /etc/init.d
I think it has something to do with having data running in the background, now I don't know what to do with my phone
EDIT: Ok, manage to recover from the reboot state, had to deny root access to my file explorer. I think the reboot was caused when I set permission to write for /system. Anyway, everytime I keep trying to copy to /etc/init.d, I get a permission denied so am not sure what I should do now.
grim_ripper said:
Phone keeps rebooting now, couldn't copy it to /etc/init.d
I think it has something to do with having data running in the background, now I don't know what to do with my phone
EDIT: Ok, manage to recover from the reboot state, had to deny root access to my file explorer. I think the reboot was caused when I set permission to write for /system. Anyway, everytime I keep trying to copy to /etc/init.d, I get a permission denied so am not sure what I should do now.
Click to expand...
Click to collapse
When ever you copy something to init.d it will reboot, or does it go into boot loop?
To check if it worked correctly, see if new mount point storage/sdcard2 was created..
EDIT: If it worked correctly, then you could move to next step.
else you could also skip it, and goto the next step of SManager, but in that case you will lose access to your original internal storage as it wont be mounted to sdcard2.
E!ch0 said:
Can u do a tutorial video how to install this script bro?
Cuz the installation steps r bit complicated
Still here
N!geR -> E!ch0
Click to expand...
Click to collapse
Creating a video will take time at least til sat... prob more.
Will see if I can create a simplified install instructions once i reach home.
NisJ said:
When ever you copy something to init.d it will reboot, or does it go into boot loop?
To check if it worked correctly, see if new mount point storage/sdcard2 was created..
EDIT: If it worked correctly, then you could move to next step.
else you could also skip it, and goto the next step of SManager, but in that case you will lose access to your original internal storage as it wont be mounted to sdcard2.
Click to expand...
Click to collapse
What happens is that everytime I try to mount /system as writable, it reboots and hence I can't copy either files to their designated location
EDIT: Also, now everytime I reboot, there's a popup that says USB connectivity has stopped, and if I go under settings->storage, settings fc. I'm thinking this has something to do with two partitions on the sd card so I hope it all goes away when this works or I revert back to as it was.
EDIT 2: So I managed to get all the files to the appropriate place using terminal and managed to get the script to run at boot. Alas, the phone doesn't detect my sdcard at all now and still throws the USB connectivity error at boot. Once I removed the sdcard, everything works alright. Also, I figured the solution to the reboot (haven't tested it yet as I wanted to resolve my sdcard first):
http://forum.xda-developers.com/showthread.php?t=2317432
EDIT 3: Got the reboot solve, but the sdcard can't be read and I tried plugging it into my other phone, the first partition is only read. I can't get minitool to even find the 2nd partition. I am thinking I need to get a card reader to plug it into my laptop. Anyway, I went through your script and open the log file it used, says that there's an invalid argument for mount. Any idea?
Final Edit: Got it working! I had to re-partition my sdcard and made both partitions primary so maybe you might want to add that in OP as MiniTool by default selected the 2nd partition as logical
grim_ripper said:
What happens is that everytime I try to mount /system as writable, it reboots and hence I can't copy either files to their designated location
EDIT: Also, now everytime I reboot, there's a popup that says USB connectivity has stopped, and if I go under settings->storage, settings fc. I'm thinking this has something to do with two partitions on the sd card so I hope it all goes away when this works or I revert back to as it was.
EDIT 2: So I managed to get all the files to the appropriate place using terminal and managed to get the script to run at boot. Alas, the phone doesn't detect my sdcard at all now and still throws the USB connectivity error at boot. Once I removed the sdcard, everything works alright. Also, I figured the solution to the reboot (haven't tested it yet as I wanted to resolve my sdcard first):
http://forum.xda-developers.com/showthread.php?t=2317432
EDIT 3: Got the reboot solve, but the sdcard can't be read and I tried plugging it into my other phone, the first partition is only read. I can't get minitool to even find the 2nd partition. I am thinking I need to get a card reader to plug it into my laptop. Anyway, I went through your script and open the log file it used, says that there's an invalid argument for mount. Any idea?
Click to expand...
Click to collapse
Why are you trying to mount /system as rw?
for getting init.d support you just have to download the apk from mentioned thread and install it, and then fallow instruction in app.
you can mount root as rw with the foll command if you want, and that is exactly what is done in he scripts as well if you will check:
Code:
mount -o remount,rw /
also to check if partition is created on sd card, type the command:
Code:
blkid
and see if
Code:
/dev/block/vold/179:34
is listed
if not post the output and i'll see what i can do.
grim_ripper said:
Final Edit: Got it working! I had to re-partition my sdcard and made both partitions primary so maybe you might want to add that in OP as MiniTool by default selected the 2nd partition as logical
Click to expand...
Click to collapse
EDIT: Correct, you need both the partitions to be primary. got out of my mind when posting the tutorial.
NisJ said:
Why are you trying to mount /system as rw?
for getting init.d support you just have to download the apk from mentioned thread and install it, and then fallow instruction in app.
you can mount root as rw with the foll command if you want, and that is exactly what is done in he scripts as well if you will check:
Code:
mount -o remount,rw /
also to check if partition is created on sd card, type the command:
Code:
blkid
and see if
Code:
/dev/block/vold/179:34
is listed
if not post the output and i'll see what i can do.
EDIT: Correct, you need both the partitions to be primary. got out of my mind when posting the tutorial.
Click to expand...
Click to collapse
For whatever reason, my /etc folder is actually a link from /system/etc
Could you post a way to revert back? I think my apps are acting all funny now and just want to revert back to before. Thanks!
grim_ripper said:
Could you post a way to revert back? I think my apps are acting all funny now and just want to revert back to before. Thanks!
Click to expand...
Click to collapse
The apps are behaving funny because you have lost their data as I had warned in the original post.
To fix do either of the foll:
1. reinstall app, and start fresh.
or
2. restore from Titanium backup if you had created...
or
3. copy paste 'Android' folder from sdcard2 if it is created to 'sdcard0'
To remove and revert, just delete the files from int.d, and stop scheduling it in SManger.
Note: to un schedule it from smanager, you first have to remove memory card, un schedule and then put in your memory card (this is coz when phone boots up, it is in standard way, with 8gb internal but, after script is executed SManager looses its data too.
How complicated will it be to make this compatible with 4.2.2?
grim_ripper said:
How complicated will it be to make this compatible with 4.2.2?
Click to expand...
Click to collapse
Ideally should be possible, unless something has changed majorly, but I haven't tried it, as am waiting for OTA update. If it is not forth coming in 2-3 weeks, may be tempted to flash nordic rom and try.
NisJ said:
Ideally should be possible, unless something has changed majorly, but I haven't tried it, as am waiting for OTA update. If it is not forth coming in 2-3 weeks, may be tempted to flash nordic rom and try.
Click to expand...
Click to collapse
I did try but nothing happened, am guessing it has permission issues or something on those lines
grim_ripper said:
I did try but nothing happened, am guessing it has permission issues or something on those lines
Click to expand...
Click to collapse
Could you be more specific? Like system restarts etc...
Else in terminal try out what I Gave in post no 12 and give me what the output is for both the commands in the terminal.
Note: execute them with super user credentials.
Thanks
NisJ said:
Could you be more specific? Like system restarts etc...
Else in terminal try out what I Gave in post no 12 and give me what the output is for both the commands in the terminal.
Note: execute them with super user credentials.
Thanks
Click to expand...
Click to collapse
on the 4.2.2 update, it doesnt recognize the second partition even if it is formatted to primary and set to active. there r definitely some updates done in that field and plus i cant get the init.d rights on the phone as the test.log file is absent in the data folder..no matter what i do i just cant get it straight with the present procedure. please try it on 4.2 and there r more frequent updates on the nordiac then the local version. so i decided to flash it rather than waiting for ota update
I just upgraded my HTC One (from stock rooted 4.1.2) by flashing to stock rooted 4.3. Unfortunately, I didn't realize the file system changed and that I needed to copy my SD card data (including of course titanium backups) to external storage and move it back after the upgrade.
I understand I can use Root Explorer to do the move, but is there a more robust and easier way to do this? Is there any way to access the data through the PC with something friendlier then adb (e.g.windows file explorer)? I did create a nandroid before I flashed. Should I just flash back, move the data, and reflash the update?
Why do you need to move it to external storage then back again? Don't you just move it within the phone? I know you want something friendlier than adb, but honestly one command you cut and paste into the shell window and it's done within seconds.
Or download a file Explorer in the phone and move them manually.
Sent from my HTC One using Tapatalk 4
Thank you both for your replies.
I went down the adb route. A little more complicated than I thought it would be. I had to, of course, update adb and along the way I got driver conflicts. Then I was left with deciding which folders needed to move, which should stay, and which were just old cruft.
It seems the directories legacy, obb, as well as hidden file .htc_layout_version should stay (as well as, of course, "0"). I kept .aid.bak as well, mostly because I have no cluse what that file is. Most everything else was cruft or "obvious" user files that got moved.
Al I have left in \data\media\ are the directories 0, clockworkmod, legacy, obb, and the file .htc_layout_version and .aid.bak. I hope I didn't screw anything up.
Seems my base configuration is using more space then before I migrated (roughly 11gb without the clockworkmod backups).
Really pulling my hair out over this issue. I installed the latest version of the GPE Lollipop 5.0.1 ROM that can be found in the Development section on my HK One M8, clean flash and everything with the .zip located at the root of my internal storage, and now when I boot up, I can't access any of my files. I have no pictures, no music, no download folder, etc. When I try to locate my files in ES File Explorer, nothing comes up, and when I plug my phone into my desktop, the only folder I have is "Ringtones". I've read a couple posts that suggest using TWRP to format the entire storage, but I have no external SD card to install a ROM from. Added to this, when I choose "Mount" in TWRP and plug into the desktop, nothing happens. USB OTG isn't even an option that I can select, it just sits there and never actually checks the checkbox. This never happened while I was using digitalhigh's GPE ROM (the one in the Verizon development section), and I'm just at a complete loss right now. Any assistance would be greatly appreciated, thanks.
Edit: Strangely enough, when I use TWRP'S file browser, even when choosing to flash a .zip file, I can see everything there, all my files right where I left them, all the folders still intact.
getinnocuous said:
Really pulling my hair out over this issue. I installed the latest version of the GPE Lollipop 5.0.1 ROM that can be found in the Development section on my HK One M8, clean flash and everything with the .zip located at the root of my internal storage, and now when I boot up, I can't access any of my files. I have no pictures, no music, no download folder, etc. When I try to locate my files in ES File Explorer, nothing comes up, and when I plug my phone into my desktop, the only folder I have is "Ringtones". I've read a couple posts that suggest using TWRP to format the entire storage, but I have no external SD card to install a ROM from. Added to this, when I choose "Mount" in TWRP and plug into the desktop, nothing happens. USB OTG isn't even an option that I can select, it just sits there and never actually checks the checkbox. This never happened while I was using digitalhigh's GPE ROM (the one in the Verizon development section), and I'm just at a complete loss right now. Any assistance would be greatly appreciated, thanks.
Edit: Strangely enough, when I use TWRP'S file browser, even when choosing to flash a .zip file, I can see everything there, all my files right where I left them, all the folders still intact.
Click to expand...
Click to collapse
I have the same exact issue right now. I happened just as you described it; flashing the 5.0.1 GPE ROM. I CAN get into the storage, however, when I mount my phone to my computer through TWRP. A BIG problem, however, is that I can't copy any files into the phone. I get a "File size limit exceeded" message.
I did some digging here and on other forums and it would SEEM that something happened during the ROM flash that completely changed the file system. Where it used to be FAT32 (I think), it now says "Generic Hierarchical." This particular file system apparently only has a file limit of 4 gigs. Anything above that and it won't accept it.
I'm currently trying to find a way to fix this but I've got nothing. I can't even flash a new ROM or anything because I'm locked out of my phone's storage.
getinnocuous said:
Really pulling my hair out over this issue. I installed the latest version of the GPE Lollipop 5.0.1 ROM that can be found in the Development section on my HK One M8, clean flash and everything with the .zip located at the root of my internal storage, and now when I boot up, I can't access any of my files. I have no pictures, no music, no download folder, etc. When I try to locate my files in ES File Explorer, nothing comes up, and when I plug my phone into my desktop, the only folder I have is "Ringtones". I've read a couple posts that suggest using TWRP to format the entire storage, but I have no external SD card to install a ROM from. Added to this, when I choose "Mount" in TWRP and plug into the desktop, nothing happens. USB OTG isn't even an option that I can select, it just sits there and never actually checks the checkbox. This never happened while I was using digitalhigh's GPE ROM (the one in the Verizon development section), and I'm just at a complete loss right now. Any assistance would be greatly appreciated, thanks.
Edit: Strangely enough, when I use TWRP'S file browser, even when choosing to flash a .zip file, I can see everything there, all my files right where I left them, all the folders still intact.
Click to expand...
Click to collapse
Sorry if I am replying too late, but I ended up in this same boat and this was the top result for what I was searching for on Google and the symptoms were exactly the same, I could see my files on TWRP but it seems like internal storage wasn't being mounted when booting into the rom. What I ended up doing was using TWRP's File Manager (under Advanced menu) to copy the contents of the internal storage to my external sd card. After that I did an advanced wipe and included internal storage (which seems to format it) and finally internal storage became available when booted into a rom again, and I didn't even have to sacrifice my files.
My Workaround/Fix
Although I don't own an HTC One, I encountered the same problem after flashing a ported ROM to a BLU Studio-G. So I'm sharing my Workaround/Fix: Reboot to recovery (TWRP in my case); Make a backup of the current ROM; Recovery will create another folder inside the original TWRP/Backup folder; After the backup completes, hit 'Restore' and make a note of the location of that folder; return to main menu and reboot.
I used Root Explorer but I imagine other competent File Managers can be used: Now move the other backup folders to the new location in the TWRP/Backup folder and that should solve the problem. All backup folders will again be available to be restored in Recovery. :good::victory: Hope this helps someone else before having to purchasing a wig