Related
This is early, hacky, and built from the work of the guys on the Vibrant forums: http://forum.xda-developers.com/showthread.php?t=739647
anomalous3 figured out that "there was only one thing running as root that could safely be replaced; the boot logo player. So, all this does is replace the boot logo player with a script that calls userinit.sh from /data/local and then calls the (now renamed) bootlogo player for those of you who want that nifty startup screen"
What this does is allows the phone to mount an ext3 partition on boot so we can have a lag fix on JP3. I'm getting 1610 on quadrant and it's pretty stable. Please someone improve this!! shaunm89 and I just hacked this together from other's work.
Directions:
1.) Create an EXT3 partition on your external SD card of 2gb. It should be the second partition after the fat32 partition
2.) Flash Modaco's pre-rooted JP3 through Odin: http://android.modaco.com/content/s...insecure-boot-clockworkmod-recovery-for-odin/
3.) Boot the phone up. Open market and install Root Explorer (costs $) and Busybox. Update busybox
4.) Download these files: http://www.megaupload.com/?d=ONGUDAIJ
Copy them across to the SD card. Move playlogos1 and playlogosnow to /system/bin. Move userinit.sh to /data/local. Use root explorer to set permissions read (all 3) write (user only) execute (all 3). 0755 for those who know linux. You can use adb to push if you wanna get fancy.
5.) Reboot. Use root explorer to see if /sd-ext exists, and if so, whether /sd-ext/data and /sd-ext/dalvik-cache exist. If so it worked! If not, reboot again and then check.
That's it. Maybe someone can package this into an update.zip, maybe someone can take it and make it more stable and even faster (ext4 for example)
great! hope we could find an easier way
Sent from my GT-I9000
Is it a must to get the pre-rooted version of firmware? However using the original SP3 then root by myself?
On the other hand, I think I will modify your init.rc as I would rather to do all the moving by myself
Great job, hope we can get EXT4 soon.
In step 4, " Move userinit.sh to /local/data" should be data/local. Quadrant benchmark 1700.
seems like the script is calling busybox, but is it necessary to use root explorer. Could one substitute root explorer with adb?
I assume root explorer is just to do things adb can do, but locally on the device instead of attached via USB.
I tried this and it and i can see sd-ext and the subfolders but is this all we need to do?
is /data/data linked to the sdcard?
I am asking because i tried to reboot the phone without the sdcard in it and i can still see all my apps and everything is working fine.
Thoughts?
Also there is an error in section 4 of your instructions. there is no /local/data, it is /data/local.
Also playlogos1 and playlogosnow files needs to be renamed with a capital P for this to work.
No need to install root explorer if you can use adb to push the files. I just wasn't sure how to use adb to push to those directories.
I fixed the other mistake, thanks
This is not ideal but gets the job done. I'm hoping you guys can make it better!
Are you able to download anything from the market after doing this?
My market is just stuck on "starting download" and that's it.
clubtech said:
Are you able to download anything from the market after doing this?
My market is just stuck on "starting download" and that's it.
Click to expand...
Click to collapse
Protected apps don't show but i've been able to get all my other purchased and free apps installed and running fine.
Strange.
I'll flash again and try again.
Yea i don't know.
The market will download some and won't others.
Also my Quadrant test is getting stuck at 3/4 stage of the I/O test so it might be my SDCard which sucks.
I used a 16GB SanDik class 4 card.
clubtech said:
Yea i don't know.
The market will download some and won't others.
Also my Quadrant test is getting stuck at 3/4 stage of the I/O test so it might be my SDCard which sucks.
I used a 16GB SanDik class 4 card.
Click to expand...
Click to collapse
sandisk are one of the best cards you can get, kingston are known to get stuck at this stage, are you sure you don't have a fake sandisk card?
anyway if you leave it running after about 10 minutes quadrant will finish and still give you a massive score of over 1500.. just shows how reliable the quadrant scores are .
does it mean that quadrant is good but speed isnt?
Tried this fix on my JP3 but no luck. I don't get these folders.
Maybe it must be MoDaCo?
If I manually execute the script I get these folders, but after reboot they are gone.
Pretty new to this maybe I'm doing something wrong?
drygmasken said:
Tried this fix on my JP3 but no luck. I don't get these folders.
Maybe it must be MoDaCo?
If I manually execute the script I get these folders, but after reboot they are gone.
Pretty new to this maybe I'm doing something wrong?
Click to expand...
Click to collapse
Ok, did it from scratch today. Format, flashed MoDaCo prerooted JP3 and everything. Stilll I don't get this to work (
Please, any ideas?
Finally got it to run faster with this fix, thanks for sharing!
drygmasken said:
Ok, did it from scratch today. Format, flashed MoDaCo prerooted JP3 and everything. Stilll I don't get this to work (
Please, any ideas?
Click to expand...
Click to collapse
Also happened to me initially. /sd-ext won't show up or if it does, it doesn't contain the correct folders though it is listed when you run 'mount'. Laggy with Quadrant result at 975.
So, went back and reformatted SD w/Fat32 then EXT3, cleared cache/data, re-flashed Modaco's JP3, installed the latest Busybox, copied files per OP and I finally got it working after a couple of re-boots (3, i think). It is running smooth so far w/quadrant 1622. GPS seems to be getting locks on SATs quickly but you still can't get to LBSTest via the keypad. Still can't write to the external sd when mounted/shared to PC.
Also tried JAC's work (see this thread: [KERNEL/RECOVERY] Vibrant EXT2/3/4 with init.d support) since it has the nifty feature allowing user to put startup scripts on boot up. I flashed his kernel but i got stuck on the 'Vibrant' boot screen. anyways, will give it another try later.
titovic said:
Also happened to me initially. /sd-ext won't show up or if it does, it doesn't contain the correct folders though it is listed when you run 'mount'. Laggy with Quadrant result at 975.
So, went back and reformatted SD w/Fat32 then EXT3, cleared cache/data, re-flashed Modaco's JP3, installed the latest Busybox, copied files per OP and I finally got it working after a couple of re-boots (3, i think). It is running smooth so far w/quadrant 1622. GPS seems to be getting locks on SATs quickly but you still can't get to LBSTest via the keypad. Still can't write to the external sd when mounted/shared to PC.
Also tried JAC's work (see this thread: [KERNEL/RECOVERY] Vibrant EXT2/3/4 with init.d support) since it has the nifty feature allowing user to put startup scripts on boot up. I flashed his kernel but i got stuck on the 'Vibrant' boot screen. anyways, will give it another try later.
Click to expand...
Click to collapse
Which method do you use for making the ext3? I made my on my hero using Amon RA could that be a problem?
drygmasken said:
Which method do you use for making the ext3? I made my on my hero using Amon RA could that be a problem?
Click to expand...
Click to collapse
I used GParted Live CD as Paragon fails to format my AData card and sorry but I am not familiar with AMON RA.
1646 thanks, very fast!
Sent from my GT-I9000 using XDA App
Would this procedure work for ext4 partitioned SD Card?
Hi everyone. This is my first (compilation) tutorial that I decided to make after reading a lot of tuts and not having them work for me until last night. Just to clarify, I'm running a MarvelC Wildfire S on a Sense-based ROM. Here are the steps to prep your phone for INT2EXT based off of multiple tutorials. Also, if you're on a stock/stock-based ROM, I recommend doing a factory reset of your phone before following these steps just to keep things clean.
In order to use INT2EXT, your phone must have:
1. d.init support
2. ext2/3/4 support
It must also be permanently rooted.
Credits: http://forum.xda-developers.com/showthread.php?t=1432459
Step 1: Preparing your SD card
Important Notes:
N1. If you are running a stock or stock-based ROM (i.e. using a stock kernel), your ROM only supports FAT32 and Ext2 for the second partition. DO NOT FORMAT YOUR SECOND PARTITION TO EXT4.
N2. You must be rooted (tutorial not included - plenty of working tutorials in this section).
N3. Do not mount your phone to follow these steps; use a microSD card reader.
Tools:
- Computer
- MicroSD adapter/reader
- Minitool Partition Pro Home Edition (http://www.partitionwizard.com/download.html)
Make sure you read the important notes above before proceeding. If you have, proceed:
1. Boot up Windows.
2. Insert your MicroSD card into the adapter and attach the adapter to your computer.
3. Make a folder on your computer to back up the contents of your SD card.
4. Install Minitool Partition Pro Home Edition.
5. Run the Partition Wizard.
6. Look for your SD card along the bottom and find the FAT32 partition.
7. Right-click it and choose "Move/Resize Partition."
8. Change the value of the partition size until your "unallocated/free space" is around 750 - 1000 MB (this is how much internal memory I recommend)
9. Click OK.
10. Find the unallocated space on the new drive map, right-click on it, and click "Create."
11. Click "Yes" on the warning that pops up.
12. Choose Ext2, Ext3, or Ext4. Stock/stock-based ROM users, choose Ext2. I recommend Ext2 just to be safe for all other ROM users, in case your kernel doesn't support it. If you know for sure that your ROM supports Ext4, then Ext4 is fine as well.
13. Make sure it is a Primary Partition, not Logical.
14. Click OK.
15. Click the Apply button on the top left corner of the window.
16. Choose "Yes" to continue.
Let it finish. Then, step 1 is complete.
Credits: http://forum.xda-developers.com/showthread.php?t=1933849
Step 2: Adding init.d Support
Tools:
- BusyBox app (make sure you use the normal install, NOT smart install)
- Terminal Emulator (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Term-init from Ryuinferno (http://www.androidfilehost.com/?fid=9390169635556426791)
1. Download Term-init.
2. Install BusyBox from Google Market/Play Store.
3. Install Terminal Emulator from Google Market/Play Store.
4. Place Term-init at the root of your SD card.
5. Launch Terminal Emulator.
6. Type: su
7. Grant SuperUser access if prompted.
8. Type: sh/sdcard/term-init.sh
9. Follow the on-screen instructions from the script that is run.
To check if it worked, reboot your phone twice and browse to your /data/ folder (using an app such as Root Browser or ES File Explorer). If it's working, you should find a Test.log in there. Congratulations, you now have init.d support and you're ready to set up INT2EXT.
Credits: http://forum.xda-developers.com/showthread.php?t=1716124
Step 3: Flashing INT2EXT(+)
Requirements:
- init.d support
- sd-ext partition (ext2/3/4)
- 100 MB of internal memory for every 500 MB of external memory
Tools (choose ONE):
- INT2EXT: http://d-h.st/Fvz
- INT2EXT+ (recommended): http://d-h.st/Otj
NOTE: If you already have a A2SD/D2EXT/INT2EXT/M2SD script, you will need to remove it completely.
1. Download your chosen script above.
2. Place it at the root of your SD card.
3. Reboot into CWM (Recovery).
4. Select "Install zip from sd card"
5. Select "Choose zip from sd card"
6. Select "CronMod-****_signed"
7. Let the script run.
8. Select "Mounts and Storage" directory.
9. Select "format/sd-ext"
10. Reboot.
You should have INT2EXT on your system now (check your internal memory to make sure). If you have any problems or questions, look in the threads given at the credits before asking here. Also, here are a few other great tutorials on flashing INT2EXT if you can't get it to work following mine:
- http://forum.xda-developers.com/showthread.php?t=2223190
- http://forum.xda-developers.com/showthread.php?t=1490607
A friend of mine has the Wildfire S and asked me to do something about the low storage. I will try this tutorial in a few days and I hope it will work It seems harder to do INT2EXT on that phone than it is on my old Desire ^^
Thank you!
It's not working for me. I ha a Galaxy Ace GT-S5830i running Ace-I-Sure 12.0 ROM. Can you help me to finally extend the internal memory? Pleease!
...100% working trick !! Thanks a lot man
Does this work with Android 4.2? I have some read-only problems described here: http://forum.xda-developers.com/showthread.php?t=2522679
I am getting status 0 error...I followed all the steps... And tried all scripts .... still i am getting status 0 error ...
Please help ..
geniusrehan said:
I am getting status 0 error...I followed all the steps... And tried all scripts .... still i am getting status 0 error ...
Please help ..
Click to expand...
Click to collapse
8. Type: sh/sdcard/term-init.sh
8. Type: sh /sdcard/term-init.sh ..... ... You must type in this way :good:
invesadm said:
8. Type: sh/sdcard/term-init.sh
8. Type: sh /sdcard/term-init.sh ..... ... You must type in this way :good:
Click to expand...
Click to collapse
I guess no problem with the init.d script? Because I already make it work in terminal. This command is just to run the term-init.sh.
And i made it worked already.
The problem is with the script i guess. I read here in comments someone also complains about status 0 error.
Thanks for the tutorial!
I know this is an old thread. But I had to resurrect my wife's old HTC WFS to use while one of our phones needed to be repaired. I couldn't find a good stable ROM to run. Ran through your tutorial and it was just fine.
I did run into a "System UIDs Inconsistent" error after the last step and ended up doing a factory reset and all was well! Tried a few other steps before that like "fix permissions" and clearing caches etc. but in the end needed a full factory reset.
Great job! Love that we can got back to these threads!
Thanks thanks thanks!
RTNetwork
Stuck in bootloop after doing the term-init.sh
what to do :?
Problem with buttons and wifi
This trick works for me great, but my hardware buttons (home, context-menu, back and search) are not working good. Also my wifi cant find any network. Can someone help me with these issues please ?
I found the most easiest way, no need to make unit.d by yourself.
So here the step
1. Flash this Rom http://forum.xda-developers.com/showthread.php?t=2143410
2. Make SD card partition ext 2 with your CWM recovery. I choose 1024 mb
3. Flash cronmod file just like this tutorial tell you.
4. Reboot, and now you have internal storage about 800-900 mb.
That's it
trying to install stock rom with extra internal memory
my device: UNLOCKED
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-0451
RADIO-7.57.39.10M
CWM 6.0.5.3
4GB flash disk 2.6gbfat32-1gbext2-128swap primary all
also tried ext3
tried all ways but couldnt make
with all INT2EXT ,INT2EXT+,INT2EXT4,INT2EXT4+ formating format/sd-ext or without format/sd-ext
i can increase memory with cronmod+marvellous rom but couldnt achieved with stock rom
what can i do pllss help
Scherby007 said:
This trick works for me great, but my hardware buttons (home, context-menu, back and search) are not working good. Also my wifi cant find any network. Can someone help me with these issues please ?
Click to expand...
Click to collapse
I have same problem, please help?
I have a new T-Mobile Note 2. I installed TWRP and SuperSU using the toolkit. I then used Root Browser and deleted a bunch of apps ("bloatware", I thought), and apparently removed too much, as the phone no longer boots android.
I downloaded the two Tweaked 2.4.1 Rom files, checked Md5sums, OK, and coped same to external SD card. I did the recommended wipes using TWRP. Thereafter, also using TWRP, BasicInstall finishes with success, but the Tweaked.2.4.1.UVBMD1.073113.zip install fails with "E: Unable to open zip file". Then I try to reboot, and get a message "your phone does not appear to be rooted", and take the option "Install SuperSU? That also fails.
I think maybe I can't install Tweaked.2.4.1.UVBMD1.073113.zip because the phone isn''t rooted? Is that right? But I can't figure out how to root the phone either. I'm stuck in a loop. Recommendations to fix appreciated.
Thx, Gus
gus_zernial said:
I have a new T-Mobile Note 2. I installed TWRP and SuperSU using the toolkit. I then used Root Browser and deleted a bunch of apps ("bloatware", I thought), and apparently removed too much, as the phone no longer boots android.
I downloaded the two Tweaked 2.4.1 Rom files, checked Md5sums, OK, and coped same to external SD card. I did the recommended wipes using TWRP. Thereafter, also using TWRP, BasicInstall finishes with success, but the Tweaked.2.4.1.UVBMD1.073113.zip install fails with "E: Unable to open zip file". Then I try to reboot, and get a message "your phone does not appear to be rooted", and take the option "Install SuperSU? That also fails.
I think maybe I can't install Tweaked.2.4.1.UVBMD1.073113.zip because the phone isn''t rooted? Is that right? But I can't figure out how to root the phone either. I'm stuck in a loop. Recommendations to fix appreciated.
Thx, Gus
Click to expand...
Click to collapse
If you got an unable to open zip file error - even though the md5s check out the only thing I can think of is the zip has become corrupted somehow. Did you check the md5 on a computer and move the file over? Might be worth checking it on the phone (you can use the terminal interface in twrp fwiw - just use the md5sum command).
Bottom line recommendation - try to copy the full zip over to the sdcard again. Also, just to sate my curiosity - did you wipe /system before flashing?
RE: Stuck
dwitherell said:
If you got an unable to open zip file error - even though the md5s check out the only thing I can think of is the zip has become corrupted somehow. Did you check the md5 on a computer and move the file over? Might be worth checking it on the phone (you can use the terminal interface in twrp fwiw - just use the md5sum command).
Bottom line recommendation - try to copy the full zip over to the sdcard again. Also, just to sate my curiosity - did you wipe /system before flashing?
Click to expand...
Click to collapse
I did recopy the two Tweaked .zip files to the sdcart - repeated attempt to install on phone, same problems.
I also unzipped the two Tweaked files on linux, and although I don't know exactly what I'm supposed to see, there's no errors and a bunch of directories and files that generally look reasonable
I think I did wipe /system on the phone before flashing - could that be my problem? Also, when I go into terminal mode in TWRP on the phone, I get a hang at "Updating partition details"
Is it possible I've accidentally deleted the unzip program on the phone?
Is there stuff I could/should do from an adb shell on my PC through a USB hookup to the phone?
thx, Gus
You could flash stock rom with odin and start over.
Tweaked Out
gus_zernial said:
I did recopy the two Tweaked .zip files to the sdcart - repeated attempt to install on phone, same problems.
I also unzipped the two Tweaked files on linux, and although I don't know exactly what I'm supposed to see, there's no errors and a bunch of directories and files that generally look reasonable
I think I did wipe /system on the phone before flashing - could that be my problem? Also, when I go into terminal mode in TWRP on the phone, I get a hang at "Updating partition details"
Is it possible I've accidentally deleted the unzip program on the phone?
Is there stuff I could/should do from an adb shell on my PC through a USB hookup to the phone?
thx, Gus
Click to expand...
Click to collapse
Hmm... maybe reflash recovery? That's very strange - especially if the first zip worked fine and the second had the issues...
rail205 said:
You could flash stock rom with odin and start over.
Tweaked Out
Click to expand...
Click to collapse
I wish I could! But when I try that it hangs at "Waiting for USB debugging to be enabled". And that's even if the phone is booted into download mode.
Gus
Odin back to stock. Twrp started failing everything I tried to flash also. That's why I stopped using it. But you need to Odin to stock
Sent from my SGH-T889 using xda premium
[SOLVED] Stuck ...
dwitherell said:
Hmm... maybe reflash recovery? That's very strange - especially if the first zip worked fine and the second had the issues...
Click to expand...
Click to collapse
Finally got it working. dwitherell was more or less right about the problem. Here's my steps: 1) did a low-level format on the external sda card 2) recopied the two Tweaked zip files onto the external sda card 3) Cheked md5sums for both files on the external sda card 4) ainstalled from TWRP, as before. BUT - this time it worked.
I'm guessing either the external sda card or one of the zip files was corrupted - as dwitherell had suggested. Thanks to him and other forum members for helping out.
Gus
Hi,
Sorry, newbie here.
I rooted my c1905 4.3 with towelroot.
Worked fine.
Then tried this swap method for internal and external memory
There is already a script to swap internal with external memory. i just made it to work at boot without SManager
This is just for the stock ROM!!
how to install:
1.remove SManager if u already have it
2.flash the zip in recovery OR edit the files like i did
what i did:
place the script in system/etc/init.d (script is not mine. credits to whoever made it )
edited init.qcom.post_boot.sh and added the line sh /system/etc/init.d/ext2sd
this will execute the script post boot.
any script can be executed using this method , so it kinda provides init.d support to stock ROMS
Click to expand...
Click to collapse
My phone rebooted (don't ask me why, I don't know) and now all my apps have stopped working (except google play and google chrome).
Can't acces my file browser anymore to delete changes made, and when connected to pc it only shows my sd-card contents.
UPDATE: Chrome and play store also stopped
Help?
Flasg a stock android ftf through flashtool
Wouldn't know how to do that.
But fixed it by rebooting without my sd card inserted. And then undo all the changes made.
But thanx for the reply
Oetsjie said:
Wouldn't know how to do that.
But fixed it by rebooting without my sd card inserted. And then undo all the changes made.
But thanx for the reply
Click to expand...
Click to collapse
Well, in the future, if you mess up badly, and/or get a soft brick, be sure to take a look at this thread: http://forum.xda-developers.com/showthread.php?t=2697277
Issue:
When using Open Camera, ES File Explorer or Amaze file explorer files are created with zero bytes. i.e. Copying a file will create a 0 byte file or if file storage location set to the SDCard, the Open Camera app will fail to record video or take pictures.
Initially write operations on the SDCard did seem to work for a while (recorded one video before fail using Open Camera and copied files across without errors).
All operations are fine on internal memory.
There is no issue using the built-in file manager and camera apps. Will update as I check though other apps affected by this.
Setup:
The phone was on MIUI 9, then updated to the MIUI 10 OTA update (from beginning of Oct2018):
GLOBAL Version 10.0.1.0 (OEDMIFH)
Android 8.1.0 OPMI.171019.019
Kernel 4.4.78-pref-ge3e6edb
I then performed a factory reset from the boot recovery before installing everything from my previous phone. I didn't try MIUI 9 with an SDCard.
System Apps and Apps up to date.
I then started with the SDCard (128GB Class 10) cleanly formatted on PC, FAT32, and then when inserted into the phone formatted again. Looked for option to mount as Internal Storage, but noted that this isn’t available on this device (probably for the best), and no obvious option for encryption???
Troubleshooting:
Initially I thought, OK failed SDCard (this was before I found built-in apps worked OK). So I removed the card formatted it and checked using a test program to write/verify the whole card and it checked out OK. Still same issues back in the phone.
Next I pulled SDCard from another phone and tried that, and I get the very same issues. Thinking less likely it is a failed SDCard now, perhaps it is a hardware issue with the phone. Although it did write some files before.
After reading a few places, mention of an issue on MIUI 9 but this was fixed in later update. The steps don't match with anything in MIUI 10.
There is also mention of a bug with Android Orio which is similar, where apps need Storage permissions. Checked and I'd given the apps this permission and I had.
Following this, I tried the standard apps (Camera and File Manager) and discovered that these wrote files without errors (using the very same files which fail before/after on the other apps). Right so looking less like a hardware issue (hopefully!).
For ES Explorer, first time you write to the SDCard you have to select the SDCard root (“Please choose the root directory (XXXX-XXXX) of ext-SDCard…”). In this step, the SDCARD is referred to as BOOT and ES Explorer mounts it with the ID of SDCARD. The internal memory is mounted as /storage/emulated/0 and the SDCard as /storage/XXXX-XXXX/.
Additional testing with the apps, has shown that the data is actually written by ES Explorer since the 0 byte file shown in ES Explorer after a copy, is the correct size and opens from the standard file manager. This is further confirmed when performing a reboot or remount of the SDCard, ES Explorer then reads the file as it should… Any file copied/moved by the standard file manager is shown and works correctly, even from ES Explorer.
I get just the same behaviour with alternative file explorers such as Amaze. Also I think many of the other apps suffer from the same issue since they can't open the 0byte photo or video until there is a remount/reboot.
With regards to Open Camera, this has the option to Use Storage Access Framework, which I think I had to enable for it to select the SDCard for storage (otherwise I think it returned a “serious error” when a few seconds into recording). I suspect something similar is happening on this app, but perhaps not consistently. As mentioned before, the first time I noticed a problem was after it had recorded a video (which was fine) and the next one I recorded was 0 bytes. The fact that it recorded without complaining, in retrospect, suggests to me that it was only reporting 0 bytes for the file (and if I’d remounted the card I would have the video OK) – since it’d have to been writing the data somewhere.
So it may be that the issue isn't writing to the SDCard, but correctly reading the data afterwards without remounting the SDCard (or reboot).
I've noticed there is a new version of MIUI 10 released yesterday, so may pick that up to see if it magically solves things (nothing mentioned on change log).
Questions:
Anyone else experienced anything similar? Ans: Apparently yes, it is a "feature", aren't we lucky.
Am I missing some special setting? Ans: No.
Any thoughts on what the issue could be or if there is a fix? Ans: It can be fixed using root magisk.
Are your mount points similar/different? Ans: Guessing not and isn't related to the problem.
Did you do a factory reset after update (one possibility is that whatever made it work in MIUI 9 remained for most people if they didn't factory reset)? Ans: Not the cause of the problem.
Thanks
meltwater.
i thought i was the only one with zero bytes files. and when you transfer them back- all good
The only way I could find an alternative solution was to install "ExSDCard Access Enabler" module in magisk.
Then point the direction to /mnt/media-rw/XXXX-XXXX/* and you can carry on as usual.
But this only works for apps that allow you to enter or select a path where you can enter the directory path by typing or open a gui to browse to this directory.
Or a file manager such as Root explorer, just go back back back to / directory and go to /mnt and you'll find the folder from there.
Apps such as OpenCamera when selecting the save path you can manually either enter this path or choose to use the Android framework to go to this folder.
But if the app only has an option to "save to external sd card" it assumes the sdcard is mounted to /storage/XXXX-XXXX/* with write permissions.
A bit of a shame..but I don't use any apps that asks for this permission so I can live with it.
I like to mention that this behavior is the same on Treble roms too, Pie or Oreo.
dvijetrecine said:
i thought i was the only one with zero bytes files. and when you transfer them back- all good
Click to expand...
Click to collapse
Awesome, helps to know it isn't something terminal. Will update if I manage to get to the bottom of it.
SUPERUSER said:
The only way I could find an alternative solution was to install "ExSDCard Access Enabler" module in magisk.
Then point the direction to /mnt/media-rw/XXXX-XXXX/* and you can carry on as usual.
But this only works for apps that allow you to enter or select a path where you can enter the directory path by typing or open a gui to browse to this directory.
Or a file manager such as Root explorer, just go back back back to / directory and go to /mnt and you'll find the folder from there.
Apps such as OpenCamera when selecting the save path you can manually either enter this path or choose to use the Android framework to go to this folder.
But if the app only has an option to "save to external sd card" it assumes the sdcard is mounted to /storage/XXXX-XXXX/* with write permissions.
A bit of a shame..but I don't use any apps that asks for this permission so I can live with it.
I like to mention that this behavior is the same on Treble roms too, Pie or Oreo.
Click to expand...
Click to collapse
Interesting, not come across it before, very odd behavior. Very glad I don't have to throw the card or return the phone.
I've seen magisk mentioned elsewhere, shall look into it. Does that require root? How easy is the Mi Max 3 to root? That sounds like that should be enough to make it work.
Also thanks for pointing out it is on other roms too, saves chasing down a fix through that. I assume then it does it on MIUI 9 too.
Thanks!
meltwater said:
Awesome, helps to know it isn't something terminal. Will update if I manage to get to the bottom of it.
Interesting, not come across it before, very odd behavior. Very glad I don't have to throw the card or return the phone.
I've seen magisk mentioned elsewhere, shall look into it. Does that require root? How easy is the Mi Max 3 to root? That sounds like that should be enough to make it work.
Also thanks for pointing out it is on other roms too, saves chasing down a fix through that. I assume then it does it on MIUI 9 too.
Thanks!
Click to expand...
Click to collapse
Magisk is the new "supersu" standard when it comes to root.
So it is the root per say. Yes you need root. But you root your phone by installing Magisk, its kind of a multi-tool.
You need to unlock your bootloader, if not already unlocked if you bought it that way like I did from Tradingshenzhen.
It will say Unlocked on the bootloader mi splash screen when you turn the phone on if the bootloader is unlocked.
And then you need to properly flash TWRP. Other than that you can stay on stock rom and use Magisk
Magisk thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
ExSDCard Write Access Enabler module thread https://forum.xda-developers.com/apps/magisk/module-exsdcard-write-access-enabler-t3670428
I see something I did not see before.
In the thread OP mentions:
Since the v3.3 ZIP version, a feature has been added especially for Oreo (Android 8) users, on this Android version, several special permissions can be used by any app.
For exemple, theses specials permissions are used to get access to reading logs, managing the power of the device.
If you want to use this special feature, you just have to follow theses easy steps:
- creating a simple file named "ExSDCard_Oreo_apps" in the module path, so: /sbin/.core/img/ExSDCard/ExSDCard_Oreo_apps (remove any extension).
- Write all the apps package names that require a special permissions, one by line, for exemple:
Click to expand...
Click to collapse
So with this you can apparently create custom rules for apps that don't support selecting the external SD card path.
Maybe you should look in to that and experiment
This bug happened across android 8.0 in various brand.
Since I familiars with ES File Explorer, I solved by root the phone, convert ES File Explorer into System app via Titanium Backup, then everything work perfectly fine. No more 0 bytes copy file.
ES File Explorer still work even I un-root my phone by uninstall Magisk.
If you're really not want to root your phone or any other reason. Just copy file that you want then restart your phone. Copied file will now become usable file.
My bootloader isn't unlocked and for now I'd rather avoid rooting my phone (may well do so later).
Good to know there are work-arounds, and that my device hardware is ok.
Will have an experiment and see if I can live with it until I have a go at rooting. Even if I do the temp fix of ES explorer.
Thanks for the info and tips.
Same **** for me. 1 year to solve this stupid bug and they dont have fix this **** yet
Say thanks to xiaomi[emoji108][emoji867]
Enviado desde mi MI MAX 3 mediante Tapatalk
Hmm i'm getting an SD card tomm for my Mix Max 3, i use the Asus File Manager. I wonder if that problem happnes with other file manager apps. Tried the Samsung Evo and another one and that 0byte bug there. No bueno.
Wmateria said:
Hmm i'm getting an SD card tomm for my Mix Max 3, i use the Asus File Manager. I wonder if that problem happnes with other file manager apps. Tried the Samsung Evo and another one and that 0byte bug there. No bueno.
Click to expand...
Click to collapse
Yep, looks like it is a solid bug. For now, I'm living with it and use the space I have on internal memory to transfer data to before using a System file manager to transfer to SDcard.
Been trying some app development and now found the "Install via USB" bug.
Again can work around it, but it does spoil debugging with Android Studio.
There are certainly some odd bugs on this phone, I suspect down to Xiaomi going "off plan".
meltwater said:
Issue:
When using Open Camera, ES File Explorer or Amaze file explorer files are created with zero bytes. i.e. Copying a file will create a 0 byte file or if file storage location set to the SDCard, the Open Camera app will fail to record video or take pictures.
Initially write operations on the SDCard did seem to work for a while (recorded one video before fail using Open Camera and copied files across without errors).
All operations are fine on internal memory.
There is no issue using the built-in file manager and camera apps. Will update as I check though other apps affected by this.
Setup:
The phone was on MIUI 9, then updated to the MIUI 10 OTA update (from beginning of Oct2018):
GLOBAL Version 10.0.1.0 (OEDMIFH)
Android 8.1.0 OPMI.171019.019
Kernel 4.4.78-pref-ge3e6edb
I then performed a factory reset from the boot recovery before installing everything from my previous phone. I didn't try MIUI 9 with an SDCard.
System Apps and Apps up to date.
I then started with the SDCard (128GB Class 10) cleanly formatted on PC, FAT32, and then when inserted into the phone formatted again. Looked for option to mount as Internal Storage, but noted that this isn’t available on this device (probably for the best), and no obvious option for encryption???
Troubleshooting:
Initially I thought, OK failed SDCard (this was before I found built-in apps worked OK). So I removed the card formatted it and checked using a test program to write/verify the whole card and it checked out OK. Still same issues back in the phone.
Next I pulled SDCard from another phone and tried that, and I get the very same issues. Thinking less likely it is a failed SDCard now, perhaps it is a hardware issue with the phone. Although it did write some files before.
After reading a few places, mention of an issue on MIUI 9 but this was fixed in later update. The steps don't match with anything in MIUI 10.
There is also mention of a bug with Android Orio which is similar, where apps need Storage permissions. Checked and I'd given the apps this permission and I had.
Following this, I tried the standard apps (Camera and File Manager) and discovered that these wrote files without errors (using the very same files which fail before/after on the other apps). Right so looking less like a hardware issue (hopefully!).
For ES Explorer, first time you write to the SDCard you have to select the SDCard root (“Please choose the root directory (XXXX-XXXX) of ext-SDCard…”). In this step, the SDCARD is referred to as BOOT and ES Explorer mounts it with the ID of SDCARD. The internal memory is mounted as /storage/emulated/0 and the SDCard as /storage/XXXX-XXXX/.
Additional testing with the apps, has shown that the data is actually written by ES Explorer since the 0 byte file shown in ES Explorer after a copy, is the correct size and opens from the standard file manager. This is further confirmed when performing a reboot or remount of the SDCard, ES Explorer then reads the file as it should… Any file copied/moved by the standard file manager is shown and works correctly, even from ES Explorer.
I get just the same behaviour with alternative file explorers such as Amaze. Also I think many of the other apps suffer from the same issue since they can't open the 0byte photo or video until there is a remount/reboot.
With regards to Open Camera, this has the option to Use Storage Access Framework, which I think I had to enable for it to select the SDCard for storage (otherwise I think it returned a “serious error” when a few seconds into recording). I suspect something similar is happening on this app, but perhaps not consistently. As mentioned before, the first time I noticed a problem was after it had recorded a video (which was fine) and the next one I recorded was 0 bytes. The fact that it recorded without complaining, in retrospect, suggests to me that it was only reporting 0 bytes for the file (and if I’d remounted the card I would have the video OK) – since it’d have to been writing the data somewhere.
So it may be that the issue isn't writing to the SDCard, but correctly reading the data afterwards without remounting the SDCard (or reboot).
I've noticed there is a new version of MIUI 10 released yesterday, so may pick that up to see if it magically solves things (nothing mentioned on change log).
Questions:
Anyone else experienced anything similar?
Am I missing some special setting?
Any thoughts on what the issue could be or if there is a fix?
Are your mount points simlar/different?
Did you do a factory reset after update (one possibility is that whatever made it work in MIUI 9 remained for most people if they didn't factory reset)?
Thanks
meltwater.
Click to expand...
Click to collapse
no need for this post. erased.
I want know why xiaomi dont fix this ****?
Think that mi max 3 will die with this bug. Never buy a xiaomi phone more
jorgeepelos said:
I want know why xiaomi dont fix this ****?
Think that mi max 3 will die with this bug. Never buy a xiaomi phone more
Click to expand...
Click to collapse
Get a Mi Mix 2S
Wmateria said:
Get a Mi Mix 2S
Click to expand...
Click to collapse
Phone with 3 month since release and they dont solve bugs and i have to buy more expensive phones?
All xiaomi phones its ****, policies, comunity,software and bugs that the dont solve
And People like you its the problem=sh it comunity guys that likes get fuked the ass by xiaomi[emoji108][emoji6]
Enviado desde mi MI MAX 3 mediante Tapatalk
jorgeepelos said:
Phone with 3 month since release and they dont solve bugs and i have to buy more expensive phones?
All xiaomi phones its ****, policies, comunity,software and bugs that the dont solve
And People like you its the problem=sh it comunity guys that likes get fuked the ass by xiaomi[emoji108][emoji6]
Enviado desde mi MI MAX 3 mediante Tapatalk[/QUOTE.
It's people like you who make the community bad when you out your hatred in the forums or is not knowledgeable enough because main post talks about THIRD PARTY FILE MANAGER APPS not 1ST PARTY Xiaomi File Manger APP and thinks it's the end of the world on here and the Xiaomi forums. And trust me there is plenty of you people around pushing Devs and OP here by complaining when other people already stated the fact many times on a thread, and trust me, I hardly take offense. "Read", it works.
Click to expand...
Click to collapse