• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Proposal/Theory for External SD storage solution on F6

orion2323 said:
out of the blue, after restarting, the hack went away,

when the same thing happened, phone rebooted after many play store updates and it went back to the original state,
Click to expand...
Before you redo the hack, try the flashing -fsck-ondemand.zip first. The card might have had a file system error or some file operation wasn't fully completed before a reboot. The zip simply attempts to fix the external ext4 partition. There should be no need to reapply the hack or recopy the files if the files are still there. You can read more about it in the post to which I've attached the zip file. Let me know if that works and we can go from there. Good luck.
 
Doing it right now
Lots of fixes taking place
Attempting to mount partition, Failed
No CSI structure available
Check Inodes . orphaned inode list fix

Free inodes count wrong....and many other things :)

This might take a while, it is a 55GB partition

Thanks for helping....always
 
Darn it
What an idiot I am
I removed the battery cover to inspect the microSD card
Your fix was running and I lifted the phone, the battery fell off and it won't boot now

....just wow
 
orion2323 said:
Your fix was running and I lifted the phone, the battery fell off and it won't boot now
Click to expand...
Hmm... your partition probably became mountable even though fsck didn't finish. But since the partition wasn't fully repaired, Android has trouble accessing data files. That's my guess anyway. If this is the case, power off the phone. Boot it without the SD. The phone should hopefully boot. Put the SD back in. Reboot to recovery and continue with fsck. No guarantee this would work though as I can't assess the damage. So again, good luck.
 
WarrantyVoider said:
Hmm... your partition probably became mountable even though fsck didn't finish. But since the partition wasn't fully repaired, Android has trouble accessing data files. That's my guess anyway. If this is the case, power off the phone. Boot it without the SD. The phone should hopefully boot. Put the SD back in. Reboot to recovery and continue with fsck. No guarantee this would work though as I can't assess the damage. So again, good luck.
Click to expand...

I almost couldn't get it to boot to recovery, took me a while, ran you file again, and it completed, saying changes were made, fixed many inodes ?
However, I'm stock on the carbon booting image for the past hour :(

I smell new rom installation :(
 
So the rom booted without the SD card fine, but now it can't with the SD after the partition was fsck'd? If so, some crucial data files on the SD were damaged. It might be possible to recover data and make the system bootable again by replacing those damaged files from a backup (or use the files from internal memory if you don't have a more recent backup). If you want to do that, I can try to think of a way to merge the folders. The other option is to save whatever app or system data you can find in that ext4 partition, start over, and then try to restore the saved data. Whether you want to go down either route is up to you. Anyway, just like a bad system drive on a PC, it's going to take some work to recover or to reinstall everything.
 
WarrantyVoider said:
So the rom booted without the SD card fine, but now it can't with the SD after the partition was fsck'd? If so, some crucial data files on the SD were damaged. It might be possible to recover data and make the system bootable again by replacing those damaged files from a backup (or use the files from internal memory if you don't have a more recent backup). If you want to do that, I can try to think of a way to merge the folders. The other option is to save whatever app or system data you can find in that ext4 partition, start over, and then try to restore the saved data. Whether you want to go down either route is up to you. Anyway, just like a bad system drive on a PC, it's going to take some work to recover or to reinstall everything.
Click to expand...

Thanks Man!

Maybe it's time to try out a new ROM after all :)
Maybe I'll go back to stock to gain bluetooth functionality

I always give myself, and *others* work on days off :)
 
So I went back to stock
I'm glad I made a backup of the original ROM back when I 1st rooted the phone
Wiped, restored my backup, did a factory reset and then applied your Storage Hack
It's android 4.1xxx but bluetooth works :)

Thanks for your help
 
So you're not trying to recover your data anymore? OK. Let me know if you still need my help. It's good to have backups in case something bad happens. Using this hack makes backup a less straightforward operation because now there are more data to deal with. I don't like the current way recovery makes full system backups because the backup archives take up a lot of space. I've been wanting to look into a way to do incremental backup, but other projects have higher priorities. Maybe some day. :)
 
Thanks...I didn't want to try and recover, it was just a matter of downloading all my apps again, settings and other stuff
With the carbon rom I had lost bluetooth, and had contemplated going back to stock, well, this pushed me
 
Last edited:
Hey warranty just a general question but what is a good read ahead value for an SD card I know it depends on card but in your experience what is a good value ... Or what app/s can I use to tune what should I be looking at what kind of results should I look for ???....thanks in advance man....
 
SantitasHeart said:
Hey warranty just a general question but what is a good read ahead value for an SD card I know it depends on card but in your experience what is a good value ... Or what app/s can I use to tune what should I be looking at what kind of results should I look for ???....thanks in advance man....
Click to expand...
Let me get link of my script... I have 7000 reahead values that works great... Make sure u have init.d support .
 
SantitasHeart said:
Hey warranty just a general question but what is a good read ahead value for an SD card I know it depends on card but in your experience what is a good value ... Or what app/s can I use to tune what should I be looking at what kind of results should I look for ???....thanks in advance man....
Click to expand...
I personally don't bother with it, so go with Krlypumaa's recommendation if that works for you. Larger readahead cache values can improve certain I/O access patterns, but it's a trade-off. I've seen some recommended values of 2048, 3072, or something like that, but that info was from a couple of years ago, so I don't know if they still apply to this generation of SD cards. I was planning to run some benchmarks. Since you've mentioned readahead, I'll consider doing that in the test.
 
Finally got around to doing the benchmark test. I didn't spend a lot of time on it, so I can't guarantee I didn't make mistakes. So treat the following as a bunch of numbers for amusement only. :)

Stock rom, Samsung EVO class-10 (orange/white), ext4, cfq (default with stock).
AndroBench macro test (unit=msec) with default settings.
First, three runs with default readahead value of 128 (kb) to get a sense of the variability.
Code: 
128k        run 1   run 2   run 3
Browser     73.25   83.5    86.5
Market     252.0   232.75  222.25
Camera     292.75  250.75  247.25
Camcorder  734.25  547.0   625.5
Then, one run of each value, keeping in mind the potential variability.
Code: 
    32k    64k    256k    512k   2048k   4096k
  83.25   77.25   77.75   88.0    85.0    90.0
  224.0  224.25  220.75  228.5   214.75  226.75
  222.5  216.0   226.75  221.0   216.75  214.75
  524.0  509.5   537.5   524.25  514.75  511.5
The differences don't seem to be big enough to draw a definitive conclusion.
Lastly, micro test (unit=MB/s) to get a sense of the two extremes.
Code: 
                   32k   4096k
Sequential read   39.77  39.86
Sequential write  21.71  27.43
Random read        9.01   8.76
Random write       1.47   1.28

Samsung EVO has a very good microcontroller, so perhaps the readahead cache value is more relevant for a slower card. Well, I'm not going to spend much time with this. I think for me, time would be better spent making other tweaks. ;)
 
Hey warranty recently got an l90 and was wondering what ifno would I need to change to get this to work for that phone is there something I should be looking for ??
 
SantitasHeart said:
Hey warranty recently got an l90 and was wondering what ifno would I need to change to get this to work for that phone is there something I should be looking for ??
Click to expand...
If the L90 has a custom recovery, make a backup of your rom and flash the zips. Then let me know if they work or if you run into problems. I believe the hack would work, but I won't make that promise.

If the L90 doesn't have a custom recovery (only rooted), it might still be possible, but it's riskier. The hack interrupts the booting process to mount the partition, so if something is not right, there's a possibility of soft-bricking. Fixing a boot problem requires some technical knowledge, so I wouldn't recommend doing it without a custom recovery unless you're familiar with low-level Android stuff.

Edit: by the way, the potential problems I'm talking about have to do with proper installation. Once the hack is installed correctly, it should function as you'd expect.
 
Last edited:
Hey man I was just about to install this on new phone but I forgot to mention that I'm currently on lollipop is that OK ?
 
Last edited:
I haven't personally tested the hack on Lollipop yet, so I am not sure. For a more technical discussion, you can read my previous reply (post #482). If I remember correctly, I've only got a report from someone with CM12 on L70. If you have a backup and can recover in case of problems, give it a try and let me know. And if the hack is not compatible and you want/need me to make it work with Lollipop, please provide me with some feedback and I can take a whack at it. Good luck.
 
You must log in or register to reply here.
Back
Top Bottom