EXFAT support for RN2 on MIUI 8 - Redmi Note 2 General

If you want to read/write your big microSD (64-128gb), on MIUI, but don't wanna format it to FAT32, there is way to do it:
1. You must have instaled init.d support on your device.
If you don't know how, just install sMIUI rom, from rom kitchen:
http://smiui.net/index.php/rom-kitchen/rom-kitchen-features/?codename=hermes&d_version=5.0&d_img=redminote2&realname=RedMi+Note+2
Or you can install only kernel (boot image ) with included init.d and busybox from:
http://smiui.net/index.php/mod-download/?mod=pboot&device=hermes
Both includes busybox, so you don't need step 2.
2. Install busybox (google play)
3. Go to
http://forum.xda-developers.com/android/development/mod-exfat-ntfs-support-mediatek-mt6753-t3304866
and download exfat-ntfs-patch-mtk.zip
4. Copy exfat-ntfs-patch-mtk.zip to your phone, restart in recovery (TWRP), and flash it.
If you get screen without systemui and backscreen picture, just reboot in recovery and make wipe ONLY cache and dalvik/art cache.
All credits to @dr_root.

I tried it on my RN2, but i got a problem. For some reason it gets mounted under root account and therefor none-root apps don't have access.
I guess it's a SuperSU related problem, but i didn't found a way to fix it.

What MIUI version you run?
I run it only on eu.multi roms, without any single problem.

I tested it with sMIUI 6.7.28.
When i check with DiskInfo it says: SD Card mounted as root

pp23 said:
I tested it with sMIUI 6.7.28.
When i check with DiskInfo it says: SD Card mounted as root
Click to expand...
Click to collapse
Strange, my first try was with sMIUI (earlier version), and it was OK.
Try to install now ONLY sMIUI kernel for your version, restart, and then instal patch.

I think the problem is SuperSU and it's namespace separation. I can mount it correctly via android terminal with su --mount-master option, but i can't that to work with the init file.

pp23 said:
I think the problem is SuperSU and it's namespace separation. I can mount it correctly via android terminal with su --mount-master option, but i can't that to work with the init file.
Click to expand...
Click to collapse
Did you check settings>additional settings>privacy>unknown sources BEFORE flashing patch.
After patching, you must have file exfat-ntfs in folder /system/etc/init.d, with 755 permissions (-rwxr-xr-x).
And busybox in /system/xbin...

I have both with correct permissions. If not i would guess it would not be executed at all, instead just being mounted under root account only. I really think it's SuperSU namespace separation for mount points, since it works with --mount-master option. Changing/Deactivating the namespace separation in SU has no effect, it's still mounted as root. And this kind of behavior is exactly what namespace separation does.
And i know from a similar problem that i had this mounting problem started with SuperSU there too, as long as MIUI dev had it's own root it worked without a problem.

pp23 said:
I have both with correct permissions. If not i would guess it would not be executed at all, instead just being mounted under root account only. I really think it's SuperSU namespace separation for mount points, since it works with --mount-master option. Changing/Deactivating the namespace separation in SU has no effect, it's still mounted as root. And this kind of behavior is exactly what namespace separation does.
And i know from a similar problem that i had this mounting problem started with SuperSU there too, as long as MIUI dev had it's own root it worked without a problem.
Click to expand...
Click to collapse
Sorry,
since I have no problem with using my SDcard, I didn't check it before with Diskinfo... Yes, I have same SD Card mounted as root, but my device/apks use it with unlimited acces on LP rules.
Any app have right to r/w on SDcard, but only in extSD0/Android/data/yourapk folder.
MIUI file manager works properly (r/w) anywhere, but my favorite is Mixplorer, again, with no any limits.
But real problem is enabling documents in settings>installed apps, that cause black homescreen... and because this problem, apks can't acces other places on SD for eg. saving data.
Like I said, I have no problem on any xiaomi.eu_multi rom with sMIUI patchedboot.img.

Yay. I got it working. I had additionally to just add "su --mount-master -c " to the mount commands also to add before mounting "su 0 setenforce Permissive" and after "su 0 setenforce Enforcing" . I also added "allow_other" to the mount options just to make sure.
Now everything works again as before. (Still mounted as root but working)

pp23 said:
Yay. I got it working. I had additionally to just add "su --mount-master -c " to the mount commands also to add before mounting "su 0 setenforce Permissive" and after "su 0 setenforce Enforcing" . I also added "allow_other" to the mount options just to make sure.
Now everything works again as before. (Still mounted as root but working)
Click to expand...
Click to collapse
Glad to solve

the init.d link is dead,
anybody willing to refresh or upload it here?

21667 said:
the init.d link is dead,
anybody willing to refresh or upload it here?
Click to expand...
Click to collapse
Boot images with init.d:
http://smiui.net/index.php/mod-download/?mod=pboot&device=hermes

I don't know whether it's a coincidence or not but since installing this mod with the sMiui rom, my USB port doesn't work as well as it did.
I'm having problems connecting to my PC with most of my USB cables whereas previously I had no problems whatsoever. It will no longer charge using my Aukey 5-socket wall charger with ANY cable in any socket whereas previously it always charged. The Aukey has a QC 2.0 socket and it always appeared to charge very quickly using this port. I can only get it to charge using the original Xiaomi charger but only with one or two of my cables.
My wife has an identical phone with an sMiui rom without the mod and without the modded sMiui bootloader and it has none of these problems.
I've deleted the init.d script and installed the latest sMiui rom without the modded bootloader but neither has resolved these problems.
Can anyone suggest what else I might try to eliminate any other cause rather than a hardware fault ?

fourlans said:
I don't know whether it's a coincidence or not but since installing this mod with the sMiui rom, my USB port doesn't work as well as it did.
I'm having problems connecting to my PC with most of my USB cables whereas previously I had no problems whatsoever. It will no longer charge using my Aukey 5-socket wall charger with ANY cable in any socket whereas previously it always charged. The Aukey has a QC 2.0 socket and it always appeared to charge very quickly using this port. I can only get it to charge using the original Xiaomi charger but only with one or two of my cables.
My wife has an identical phone with an sMiui rom without the mod and without the modded sMiui bootloader and it has none of these problems.
I've deleted the init.d script and installed the latest sMiui rom without the modded bootloader but neither has resolved these problems.
Can anyone suggest what else I might try to eliminate any other cause rather than a hardware fault ?
Click to expand...
Click to collapse
sMiui rom contain sMiui modded kernel (boot.img-not bootloader, noone touch your bootloader). So there is no difference between your and your wife's device, after flashing sMiui rom.
To test device, try to flash other rom, eg. some weekly from xiaomi.eu, or CM12.1.
To be sure, before flashing rom, make standard wipe (data/cache/dalvik), and format data (save data from internal mem. before).
I have zero real problems with several versions of weekly (with modded sMiui kernel+exfat mod) and sMiui (only exfat mod) roms.

maxx_hr said:
if you want to read/write your big microsd (64-128gb), on miui, but don't wanna format it to fat32, there is way to do it:
1. You must have instaled init.d support on your device.
If you don't know how, just install smiui rom, from rom kitchen:
http://smiui.net/index.php/rom-kitchen/rom-kitchen-features/?codename=hermes&d_version=5.0&d_img=redminote2&realname=redmi+note+2
or you can install only kernel (boot image ) with included init.d and busybox from:
http://smiui.net/index.php/mod-download/?mod=pboot&device=hermes
both includes busybox, so you don't need step 2.
2. Install busybox (google play)
3. Go to
http://forum.xda-developers.com/android/development/mod-exfat-ntfs-support-mediatek-mt6753-t3304866
and download exfat-ntfs-patch-mtk.zip
4. Copy exfat-ntfs-patch-mtk.zip to your phone, restart in recovery (twrp), and flash it.
If you get screen without systemui and backscreen picture, just reboot in recovery and make wipe only cache and dalvik/art cache.
All credits to @dr_root.
Click to expand...
Click to collapse
it's mandatory to replace your current system/etc/permissions/platform.xml
with the one i provided
only that way your exfat/ntfs formated sd card will be mounted correctly and will be r/w
and all apps will not have a single problem
no need for commands via terminal emulator this way!
Cheers

maxx_hr said:
sMiui rom contain sMiui modded kernel (boot.img-not bootloader, noone touch your bootloader). So there is no difference between your and your wife's device, after flashing sMiui rom.
To test device, try to flash other rom, eg. some weekly from xiaomi.eu, or CM12.1.
To be sure, before flashing rom, make standard wipe (data/cache/dalvik), and format data (save data from internal mem. before).
I have zero real problems with several versions of weekly (with modded sMiui kernel+exfat mod) and sMiui (only exfat mod) roms.
Click to expand...
Click to collapse
Thanks for your explanation and your suggested solutions. Unfortunately, none of them worked. Can you suggest anything else before I contact my supplier regarding a repair to my phone ?

fourlans said:
Thanks for your explanation and your suggested solutions. Unfortunately, none of them worked. Can you suggest anything else before I contact my supplier regarding a repair to my phone ?
Click to expand...
Click to collapse
hey mate try fasboot flashing latest global rom found on en.miui.com
REMEBER to use command FLASH ALL
backup personal things before trying

dissidius said:
hey mate try fasboot flashing latest global rom found on en.miui.com
REMEBER to use command FLASH ALL
backup personal things before trying
Click to expand...
Click to collapse
I wasn't quite sure how to flash the global rom using the 'FLASH ALL' option of FASTBOOT so I flashed it via TWRP after a factory reset.
Are these 2 methods equivalent ?
Still having problems with the USB socket after flashing this rom.
Thanks for your suggestion.

fourlans said:
I wasn't quite sure how to flash the global rom using the 'FLASH ALL' option of FASTBOOT so I flashed it via TWRP after a factory reset.
Are these 2 methods equivalent ?
Still having problems with the USB socket after flashing this rom.
Thanks for your suggestion.
Click to expand...
Click to collapse
no they are not equivalent!
so try fasboot flashing!

Related

[Q] CM7 - stucked on tattoo boot screen

Hello,
After rooting my Tattoo, I installed ROM manager and flashed the clockworkMod Recovery 3.0.0.6 (for tattoo/click).
When I install the rom cyanogenmod 7 RC1 or RC2 (I try CM7 nightlybuild 19 as well) via clockworkmod, he said that the rom is successfully installed but when I launch the ROM, the ROM stucked on the tattoo boot screen (not on the CM7 boot screen, I never saw the CM7 boot screen).
Any idea to resolve my problem?
Thanks
Stuck for how long? About 2 minutes it is ok and then the CM boot logo come up.
First boot takes a long time.
Did you wipe your device before flashing CM ROM? If not do so in recovery menu. (wipe all, factory setting, clear cache etc...)
Same here. At first when i got boot screen, i thought i blew it, but it took few minutes to urn up...
it happened twice to me. Wipe cache at first ... if it doesn't boot, wipe all.
Good luck!
I wipe all before every flash.
I flash the rom "update-cm-7.0.0-RC2-click-signed.zip" and after the gapps "gapps-gb-20110307-signed.zip".
On my screen, I saw only "TATTOO". , I waited during 10 minutes...
charlesdg said:
I wipe all before every flash.
I flash the rom "update-cm-7.0.0-RC2-click-signed.zip" and after the gapps "gapps-gb-20110307-signed.zip".
On my screen, I saw only "TATTOO". , I waited during 10 minutes...
Click to expand...
Click to collapse
try other rom file. and don't install gap yet. I had been there too.
I tried the rom "FroYo AOSP(2.2.2_r1) for Tattoo v0.3 released" and it works!
How can I install cyanogenmod 7? which rom can I use from cyanogenmod 7?
I tried repeating installation 6 times then it worked. I think install isn't clean. try again.
with which rom?
Try latest cyanogen rom rc - and here you will find all the info.
It's really great, try it.
charlesdg said:
I wipe all before every flash.
I flash the rom "update-cm-7.0.0-RC2-click-signed.zip" and after the gapps "gapps-gb-20110307-signed.zip".
On my screen, I saw only "TATTOO". , I waited during 10 minutes...
Click to expand...
Click to collapse
I have the same problem. Today I've tried the RC3 without being able to boot it, stuck at Tattoo logo. Doing a logcat I see many "DEBUG" row. The previous nightly build 31 boot correctly but after a while hang and sometime the system reboot itself. The nFinityGB 0.92 and previous, despite being CyanogenMod based, runs correctly. I've not been able to figure why I have so many problem with a rom that for most people is rock solid.
Please let me know if nFinityGB rom works correctly.
Have had success booting RC2.2 & RC3
I have had no problems flashing or booting Cyanogen 7 RC2.2 and RC3, using Rom Manager from Android market.
The problem seems to be solved in RC3, but the default cpu speed is too high to boot without getting some instability. At the third try I've been able to get into cpu settings to lower the maximum speed to 615 MHz. Now it works without stabilty issues.
Hey guys someone please help me out...even im stuck with the same problem....
Boot LOOPs continuously... i dont find any solution to this... phone isnt working atol and if i want to get back to the stock rom it says "USB CCONNECTION ERROR" so im really in a bad situation here....
guess have to travel to college without music (
I try the CM7 RC4 and the rom is bootlooping when I launch it! :-s
I went back on the CM6 :-(
charlesdg said:
I try the CM7 RC4 and the rom is bootlooping when I launch it! :-s
I went back on the CM6 :-(
Click to expand...
Click to collapse
If you feel dare, you can use this little init script that i've created for personal use. It sets a maximum cpu frequency of 528MHz in the early boot phase, allowing the phone to be stable. Once the phone booted, you can change the cpu speed using the CM Settings menu.
To place it in the correct directory, you must use adb.
- Just download it somewhere in your computer
- rename it removing the .txt extension (the resulting name will be 02slowdown)
- normally flash the CyanogenMod rom and do not reboot
- connect the usb cable between the phone and the computer
- mount the /system partition using the Clockwork storage and mounts menu
- copy the script in the /system partition with the command
Code:
adb push 02slowdown /system/etc/init.d/
- change the script owner with
Code:
adb shell chown root:shell /system/etc/init.d/02slowdown
- change the permissions with
Code:
adb shell chmod 750 /system/etc/init.d/02slowdown
- reboot and cross your finger
Now the phone should boot regularly without getting nasty FC
Hope this will help someone.
There is another way to apply this workaround: you can open the zipped rom with 7zip or something like that and put the "02slowdown" script in the /system/etc/init.d subdirectory of the archive. I used this method to flash the cm7 stable version.
my first reboot took a bit longer too. I just waited and voilá. Droid skater and CM7 installed.
lupp0l0 said:
If you feel dare, you can use this little init script that i've created for personal use. It sets a maximum cpu frequency of 528MHz in the early boot phase, allowing the phone to be stable. Once the phone booted, you can change the cpu speed using the CM Settings menu.
To place it in the correct directory, you must use adb.
- Just download it somewhere in your computer
- rename it removing the .txt extension (the resulting name will be 02slowdown)
- normally flash the CyanogenMod rom and do not reboot
- connect the usb cable between the phone and the computer
- mount the /system partition using the Clockwork storage and mounts menu
- copy the script in the /system partition with the command
Code:
adb push 02slowdown /system/etc/init.d/
- change the script owner with
Code:
adb shell chown root:shell /system/etc/init.d/02slowdown
- change the permissions with
Code:
adb shell chmod 750 /system/etc/init.d/02slowdown
- reboot and cross your finger
Now the phone should boot regularly without getting nasty FC
Hope this will help someone.
Click to expand...
Click to collapse
Thanks man! It works for the rom CM7 stable mod
charlesdg said:
Thanks man! It works for the rom CM7 stable mod
Click to expand...
Click to collapse
I'm glad to be useful!
There is another way to apply this workaround: you can open the zipped rom with 7zip or something like that and put the "02slowdown" script in the system/etc/init.d subdirectory of the archive. I used this method to flash the cm7 stable version.
Sent from my HTC click using XDA App
lupp0l0 said:
I'm glad to be useful!
There is another way to apply this workaround: you can open the zipped rom with 7zip or something like that and put the "02slowdown" script in the system/etc/init.d subdirectory of the archive. I used this method to flash the cm7 stable version.
Sent from my HTC click using XDA App
Click to expand...
Click to collapse
If I don't, every times I launch cm7, I have to do the manipulation (with adb) explain above?

[Release] Clockwork Recovery Port. Latest release V4 fixes graphical issues

I take no responsibility for any harm that comes to your phone as a result of applying this mod.
I suggest people start using genokolar's version instead, available here: http://forum.xda-developers.com/showthread.php?t=1067490
Clockwork Recovery port based on Koush's 3.0.2.8 source.
Available here: http://www.multiupload.com/DQGL84P3A5
Source available on my github: https://github.com/stockwell/u8800-clockwork-recovery-port (bit messy.. will do a cleanup when I have the time)
BIG THANKS TO 357546 for creating the new kernel!!
v4 Notes:
- Now using 357546's kernel with fixed framebuffer driver capable of RGB565!
- Seems to be fully functional aside from rom manager integration
- Some small cleanups in init scripts and sbin
Detailed Installation:
- Ensure that there are no Huawei rom updates on your SD-Card in the dload folder and unplug the phone from your computer
- Boot to bootloader mode by pressing the up and down volume keys and pressing the power button. This will show a plain violet/purple screen.
- Connect the phone to your computer. In windows it will automatically mount one mass storage device which corresponds to the /cust_backup folder on your phone. If your OS supports EXT3 it will mount multiple devices, look for the one with an images directory and this is the device to use.
- In the images directory rename recovery.img to something else (ie. recovery.bak) and then copy the new recovery image in its place.
- Unmount the mass storage device to ensure all cached writes are completed and then disconnect from the computer. Exit bootloader mode by pulling out the battery.
You now have the clockwork recovery installed. Boot to recovery by holding the volume up and power buttons to turn the phone on.
wow！
hope for a perfect recovery!
Any feedback on this?
Sent from my u8800 using XDA App
good news！！！
seems that the32bpp mode is a big problem
hope to see changes!!!
Good stuff man, thanks for the work you're doing.
good job bro
Thanks for the support! I've got an issue though, I've applied the recovery but when I press the vol buttons and power I am taken to the purple screen instead of the green recovery menu. V2 worked fine though......not sure if anyone else is having the same issue?
VolUP+VolDown+Power=Purple screen
VolUp+Power=Recovery screen
Got it, thanks!
Sent from my u8800 using XDA App
tested, backup ok, wifi ok
thanks for your work, tested V4, backup ok, wifi is working fine, so far no problem
wmi543 said:
thanks for your work, tested, use lastest clockmod rom manager 4.0, backup ok, wifi is working fine, so far no problem
Click to expand...
Click to collapse
Hey, just a question on that topic - I goto 'Backup Current ROM' and it asks me to install clockmod recovery, and asks to verify what model of phone; obviously u8800 isn't an option on the list.
So.... Aroo? Sorry if I'm missing something obvious
actually you don't need to install rom manager
just follow the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1043232
Yep, so just skip using the app entirely. Got it
What's the difference between this and Reckas recovery?
blup1 said:
What's the difference between this and Reckas recovery?
Click to expand...
Click to collapse
That would be v2 of my recovery port actually. As stated this version fixes usb mass storage mounting and implements off-mode charging.
made a backup without problem.. thx..
blup1 said:
What's the difference between this and Reckas recovery?
Click to expand...
Click to collapse
I mentioned in mine that it was Stockwells, maybe I didn't make this clear. Sorry about that in that case.
Either way I better get this up on my site to be mirrored
http://www.apksmash.com/x5/recovery.img
New version uploaded
When you are in recovery after the last step which says so, are you just suppose to take the first option "reboot system now"?
Sorry, completely beginner with these kinds of stuff.
Edit: I guess I should choose backup and restore> backup but when i do so it says "Can't mount SD-card"
I have serious problem by finding the bootloader drivers! The driver update is failing all the time? Do some of you have the driver folder you can give me?
THX!
blup1 said:
When you are in recovery after the last step which says so, are you just suppose to take the first option "reboot system now"?
Edit: I guess I should choose backup and restore> backup but when i do so it says "Can't mount SD-card"
Click to expand...
Click to collapse
Feel free to just have a poke around and see what it can do. At the moment the only really useful thing is backup and restore.
I'm not sure why it won't mount the sd. I should mention that it does not use the internal 'sd-card' so you'll get that error if you don't have an external sd-card inserted.
Playron said:
I have serious problem by finding the bootloader drivers! The driver update is failing all the time? Do some of you have the driver folder you can give me?
THX!
Click to expand...
Click to collapse
I didn't think that drivers were needed, it should just come up with the mass storage device. From what I remember there are two other devices that windows detects but cannot find drivers for, but don't stress about that as it's not needed. Try it again and see how it goes, it may have mounted but you were stressing about the drivers so missed that it was working.

exFAT and NTFS drivers for Lenovo Yoga Tablet 2 - a solution!

I own Lenovo Yoga Tablet 2 830L, firmware "upgraded" to 830LC, rooted. I've tested the provided solution only on it, though it should work on other models, and maybe even on other devices.
I've built exFAT and ntfs-3g drivers from the most resent sources, and made a shell script, to auto-mount a microSD at the system start. Root and SuperSU are required. Currently, the installation is manual. The project is here:
https://github.com/Lurker00/Android-fs/releases
Please read the description I've written, at least "How to mount?" section, and, of course, the disclaimer.
Edit: Now it has a CWM/TWRP installation zip for easy use!
Lurker0 said:
I own Lenovo Yoga Tablet 2 830L, firmware "upgraded" to 830LC, rooted. I've tested the provided solution only on it, though it should work on other models, and maybe even on other devices.
I've built exFAT and ntfs-3g drivers from the most resent sources, and made a shell script, to auto-mount a microSD at the system start. Root and SuperSU are required. Currently, the installation is manual. The project is here:
https://github.com/Lurker00/Android-fs/releases
Please read the description I've written, at least "How to mount?" section, and, of course, the disclaimer.
Click to expand...
Click to collapse
Thanks a lot for putting effort into this! I haven't tried it yet, but I'd suggest to create an app/APK which installs the files necessary and which features some buttons for mounting and unmounting. A CWM package is not such a good idea due to the fact that we have only temporary CWM and hence installing would still be a bit painful. This app could be something like a Yoga tablet 2 toolkit, which could maybe even include my sharpness fix
I've created CWM/TWRP installation zip with exFAT and NTFS drivers, and mounting script. It can be downloaded from here:
https://github.com/Lurker00/Android-fs/releases
Now, if you have rooted your Lenovo Yoga Tablet 2 (any screen size), and have SuperSU installed, just download UPDATE-android-fs-1.0.1-install.zip, install the same way, and start using exFAT (strongly recommended!) or NTFS (not recommended!) microSD.
To safely unmount for hot unplug, use Android settings. For mount after hot plug, better to reboot your tablet.
Note: the microSD file system is checked before mounting, and, if errors are found, it is mounted as read-only. So, if you find out that you can't write to the microSD, safely remove it and check (allowing to fix errors) it under Windows. It is strongly recommended to check and fix under Windows, because both exFAT and NTFS are produced by Microsoft, and no open source software is able to correct the file system errors correctly!
I have Yoga Tablet 2 8''. But the installation zip contains binary files for a number of platforms, and may work on other Lenovo Android devices. Being manually installed, the drivers are confirmed to work on:
Lenovo Vibe Z2 Pro
Lenovo Vibe Z2
Lenovo S90
so I see no a reason why they will not work being installed via recovery console.
I almost thought my Yoga 2-850F is broken as it was impossible to mount or format any micro SD card. Even when I tried formatting the card with my android phone using various file systems (i.e. exfat, ext4 etc.), I would always get an error. Finally, just flashing the zip did the trick. Thanks for the script!
I've updated the drivers to version 1.0.2:
1. One more supolicy rule added to the mounting script. Without it, unmount from Android Settings didn't work.
I didn't put per-platform binaries this time, because the recovery zip contains them all.
I'm sorry for so frequent updates, but
exFAT/NTFS fuse drivers binaries for Android v1.0.3
The problem is that the original exFAT driver was designed to update the file system only at unmount events, but the current Android never unmounts microSD mounted not by Android's vold process Meaning, file system corruption may happen on a reboot or power off.
Version 1.0.2 partially addresses that issue, and is stable enough. Only freshly created directories can be damaged by a reboot, and only if there were no any file operations after that, i.e. a rare case. Version 1.0.3 ensures that the file system is kept consistent almost always. It can be damaged only by removing microSD card during write operation.
Nevertheless, I plan to make at least one more release, to keep microSD clean, when there are no pending writes. Also, I'd try to improve the write performance compared to 1.0.3, without a penalty of the file system consistency.
I just have released
exFAT/NTFS fuse drivers binaries for Android v1.0.4
and I can say I'm quite satisfied with both performance and robustness of the resulting exFAT driver (no changes were made to ntfs-3g). So, I believe, it is the final build for a while.
Worked perfect.
Tested and working perfect:
Tablet: Lenovo Yoga Tablet 2 Pro Android 4.4
Micro SD: Lexar 128GB (633x) Formatted to exFAT
I flashed it via temp recovery and did a reboot from recovery. Then shut down the tablet and put the exFAT card in. Booted up and not so much as a whisper. The system recognised and mounted the card without any problems.
Thanks again for your hard work.
Now to find a custom ROM. I think I've got more chance of finding rocking horse s**t than a ROM for my tablet though
Hello,
Thanks fort the work.
I have got a lenovo yoga tab 2 1050F updated tout lollipop and rooted.
Can you tell US if it is works with both KitKat ans lollipop?
Can you détail the installing methode?
Thanks in advance.
Kalachnikos said:
Hello,
Thanks fort the work.
I have got a lenovo yoga tab 2 1050F updated tout lollipop and rooted.
Can you tell US if it is works with both KitKat ans lollipop?
Can you détail the installing methode?
Thanks in advance.
Click to expand...
Click to collapse
I didn't upgrade to Lollipop myself, and I don't want to.
The driver and the mounting script are reported to work under Lollipop, but, for auto-mount on boot, they rely on /system/etc/install-recovery.sh script modified by SuperSU to launch with required privileges on system boot, which is not the case for Lollipop. It works flawlessly under Kitkat though.
You can find the detailed instructions at the github place from the link above. It's as easy as to root.
Hi,
Should this work on the Tab 2 A10-70, which has ARMv8 (Cortex-A53, MT8165 chipset)?
Looking for a sustainable solution to get exFAT working on that Lenovo device, it's a real let down it doesn't by default...
Many thanks !
You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.
Lurker0 said:
You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.
Click to expand...
Click to collapse
I'm still on kit-kat, and rooted. I've yet to install CWM/TWRP though, so that's the first step. I'm pretty limited on tech skills so that might be an issue, but I'll see how it goes ; if it's a simple zip flash then great, otherwise things may get too out of hands
If/when I get around to testing, I'll keep you posted - but in the meantime many thanks for the work on this!
Thank you for your work. It works with exfat microsd 64 go sandisk and my lenovo 1050F tablet under lollipop.
I don't know how android system works, sorry for newbie questions
I try to have my external SD mounted in R/W at launch time.
In superSU, i change the following parameter : activate su on starting to enable but it does not work.
I have read that /system/etc/install-recovery.sh is executed by super-su. I can see at the end of this shell /system/etc/install-recovery-2.sh is called but it does not mount the SD in R/W...
Any help is appreciated! Thank you.
Unfortunately, Lollipop has more protection, and it launches install-recovery.sh in a very restricted environment, not enough for the mounting script to work properly. And I don't know a way to launch my script at the boot time with required privileges under Lollipop. One of the reasons I don't want to "upgrade" my 830LC to 5.0.1!
I have a Lenovo yoga tablet 2 830LC, upgraded to Lollipop 5.0.1 recently. There are no proper root guides for the Lollipop version anywhere on the forum, and since I'm interested in rooting my device and also be able to write to the external sd card, I request you to guide me on this. I'm sorry if this isn't the proper thread for my request but would be appreciated much.
zach181 said:
Worked perfect.
Tested and working perfect:
Tablet: Lenovo Yoga Tablet 2 Pro Android 4.4
Micro SD: Lexar 128GB (633x) Formatted to exFAT
I flashed it via temp recovery and did a reboot from recovery. Then shut down the tablet and put the exFAT card in. Booted up and not so much as a whisper. The system recognised and mounted the card without any problems.
Thanks again for your hard work.
Now to find a custom ROM. I think I've got more chance of finding rocking horse s**t than a ROM for my tablet though
Click to expand...
Click to collapse
Hi.. i hv rooted and in that process flashed supersu thru temp recovery twrp... now iam not sure how to activate again twrp... any advise...thanks
Same way you did it when rooted. It is launched one time only.
mmlbbntr said:
Should this work on the Tab 2 A10-70, which has ARMv8 (Cortex-A53, MT8165 chipset)?
Looking for a sustainable solution to get exFAT working on that Lenovo device, it's a real let down it doesn't by default...
Click to expand...
Click to collapse
Yeah, it's a shame that Lenovo hasn't included exFAT support.
Read on...
Lurker0 said:
You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.
Click to expand...
Click to collapse
I love you, man! :good:
I just got your drivers to work on a Lenovo Tab 2 A10-70F running Android 5.0.1.
Yes, the install-recovery-2.sh mounting script doesn't work there, because it runs in a restrictive security context on Lollipop, if I've understood it correctly.
I flashed your update zip, noticed that it didn't work, then searched for some other options. I thought about init.d, but that isn't supported on this tablet either.
However, SuperSU, which I've already been using, offers a "su.d" mechanism, similar to init.d, and I used that to get it to run!
One needs to have SuperSU and busybox installed, and flash your update zip with a custom recovery (this one works for the Tab 2 A10-70, F & L).
Then create /system/su.d directory and move the /system/etc/install-recovery-2.sh script there. It can be named anything, I renamed it "/system/su.d/00mount_exfat_ntfs.sh".
I'm not too sure about the permissions, I used 755 for both the directory and the script.
In the SuperSU settings (accessible in the SuperSU app), the option "mount namespace separation" must be disabled.
I have a 64GB SanDisk Ultra microSDXC card, but for some reason it wouldn't want to work with exFAT on this tablet at first.
/dev/block/mmcblk1p1 did not show up while the card was inserted, only /dev/block/mmcblk1.
I formatted the card with NTFS, and that worked. I changed it back to exFAT, and then it finally did show up. Weird.
Anyway, would you recommend exFAT or NTFS, Lurker0?
I've used this card with NTFS on an older tablet, and it was rock solid, which I can't say about my experience with exFAT.
One minor caveat: the card isn't automatically mounted on insertion. Mounting requires another execution of the mounting script, either by rebooting or running "su -c /system/su.d/00mount_exfat_ntfs.sh".
Is there any way to make that automatic?
Thanks again.
Tzul said:
However, SuperSU, which I've already been using, offers a "su.d" mechanism, similar to init.d, and I used that to get it to run!
Click to expand...
Click to collapse
Thank you for finding! I'll read more and try to update my package.
Tzul said:
Anyway, would you recommend exFAT or NTFS, Lurker0?
Click to expand...
Click to collapse
NTFS is not flash-friendly, so I believe exFAT is better.
Tzul said:
Is there any way to make that automatic?
Click to expand...
Click to collapse
It requires to write an application to watch for system mount events and run that script. I'm lazy to do it

[ROM][Lollipop][Omni 5.1.1] P5wifi (DISCONTINUED)

Hi all, here I wish to continue porting OmniROM from the P4/P4wifi over to our device the P5/P5wifi.
*Please note that this is simply a port of an already built rom. It was not built from source therefore anything that you may find to be broken will more than likely remain broken until it is fixed in the parent ROM.
-Many thanks to the builder of this rom @AAccount. His hard work made this ROM possible. :good:
-Thanks to @jolinnard whose kernel is being used in these ROMs. :good:
*On first boot the keyboard will not be showing. The fix is simple. Go to settings>Language & Input. Tap on Current Keyboard and flip the toggle next to Hardware. The keyboard should now be fine.
Working:
Everything works on the P5 AFAIK
Not working:
SELinux---------Need a recovery that supports it.
To those looking forward to a P5 3G rom then please note that there will not be one any time soon. AAccount has stopped building for the p4 3g so that means we don't have a 3g rom to port anymore. So unless AAccount starts porting for the p4 again there won't be a P5 rom.
Flash Instructions
Wipe data, system, cache, dalvik if coming from another ROM. If ugrading to a newer build then a simple Dalvik and cache wipe will do
Flash the ROM zip
Flash GAPPs (Thanks to @jolinnard)
Flash SuperSU
Reboot and enjoy
Original ROM thread
Credits
@AAccount - for the ROM
@jolinnard - For the kernel
@decatf - for his work on the p4 kernel which is used here that delivers great performance
If you helped out and I missed you in the credits then send me a PM and you will be credited
This port has been discontinued!!
"See why
Hey! Maybe some day I will back to Omni. I'm planning to erase my Gtab of Google stuff and enjoy a clean Android experience.
jolinnard said:
Hey! Maybe some day I will back to Omni. I'm planning to erase my Gtab of Google stuff and enjoy a clean Android experience.
Click to expand...
Click to collapse
@L3Ron ,i will give it a try.
@jolinnard
If you want to port or start with omni source? Nice to See your work for our Tab 8.9.
jolinnard said:
Hey! Maybe some day I will back to Omni. I'm planning to erase my Gtab of Google stuff and enjoy a clean Android experience.
Click to expand...
Click to collapse
Awesome!! Erased my internal sdcard by accident last week. Luckily I have the same files on my Nexus 9 so I was saved. This port works great for me. Should I even port for the P5? AAccount stopped building for the p4 as of May 23. Reason being that 3G doesn't work but oddly enough it does work on the P5 using our modified KK kernel and your data_on script.
bierma32 said:
@L3R0N ,i will give it a try.
Click to expand...
Click to collapse
Great. Tell me how it works for you.
L3R0N said:
Great. Tell me how it works for you.
Click to expand...
Click to collapse
Installed the Rom with out problems, i done a clean install and wipe / Format system / data / cache and dalvik.
I looks smooth and battery are good, it goes into deepsleep without battery consum.
Onliest Problem is i can not connet with wifi to a network. I can See all avaible network ,but no connection.
bierma32 said:
Installed the Rom with out problems, i done a clean install and wipe / Format system / data / cache and dalvik.
I looks smooth and battery are good, it goes into deepsleep without battery consum.
Onliest Problem is i can not connet with wifi to a network. I can See all avaible network ,but no connection.
Click to expand...
Click to collapse
Did you try with advanced wifi configuration? Try not use dhcp to assign wifi. Use a fixed ip. I had the same issue and that was the solution.
?
Enviado desde mi LG-D855
julen163 said:
Did you try with advanced wifi configuration? Try not use dhcp to assign wifi. Use a fixed ip. I had the same issue and that was the solution.
?
Enviado desde mi LG-D855
Click to expand...
Click to collapse
I tried different setting at the advanced configuration of WLAN settings with out success.
bierma32 said:
I tried different setting at the advanced configuration of WLAN settings with out success.
Click to expand...
Click to collapse
I have no such problems. My WiFi connects just fine. Try turning airplane mode on for a moment then turn it back off and try connecting again. Could it be the kernel? I'll p.m you a kernel to try and see if it fixes anything later on. Any logs?
OP has been updated with links to the new build released by AAccount today. According to him there were no major changes, just the usual Omni sync.
thanks for the unexpected gift! unfortunately i have problems with the zip package, it can't be opened/flashed, redownloaded 4-5 times from pc and tablet, same, checked the MD5 and it matches...am i the only one having troubles with it?
chemicalbuz said:
thanks for the unexpected gift! unfortunately i have problems with the zip package, it can't be opened/flashed, redownloaded 4-5 times from pc and tablet, same, checked the MD5 and it matches...am i the only one having troubles with it?
Click to expand...
Click to collapse
Nope same overhere.
Made a backup but transferred it to pc so I've got a problem! TWRP and no flashable zip on the internal sd...
Edit: used the sideload option with ADB and used the omni-5.1.1-20150706-p5wifi-HOMEMADE ROM
Got also problems with the WiFi connection. My network uses 192.168.2.xx range
chemicalbuz said:
thanks for the unexpected gift! unfortunately i have problems with the zip package, it can't be opened/flashed, redownloaded 4-5 times from pc and tablet, same, checked the MD5 and it matches...am i the only one having troubles with it?
Click to expand...
Click to collapse
No you are not the only one. This was reported to me earlier today by another user. I'm in the process of uploading a new zip to androidfilehost and another to mega. They will be up soon.
Nonomen said:
Nope same overhere.
Made a backup but transferred it to pc so I've got a problem! TWRP and no flashable zip on the internal sd...
Click to expand...
Click to collapse
I'm sorry to hear that. You can use adb to push a zip file to your sdcard for installation.
Use this command
Code:
adb push romname.zip sdcard
Or you could use sideload to install one as well. in twrp go to advanced then select adb sideload and connect your tab to your pc. Open up windows command prompt and type
Code:
adb sideload romname.zip
This should get a rom installed to your tab.
File has been re-uploaded. It opens fine now and should work fine.
L3R0N said:
File has been re-uploaded. It opens fine now and should work fine.
Click to expand...
Click to collapse
tnx for the quick answer. I've been able to sideload your first rom but it has lot of fc when installing or updating the apps from the playstore. Setting cpu to 1.2 had no result.
I will try your new uploaded file tomorrow.
Nonomen said:
tnx for the quick answer. I've been able to sideload your first rom but it has lot of fc when installing or updating the apps from the playstore. Setting cpu to 1.2 had no result.
I will try your new uploaded file tomorrow.
Click to expand...
Click to collapse
I have absolutely no problems with the ROM. No force closes or anything. Can you try a clean install of the 0716 build and see if it fixes anything?
Just before your re-upload I installed aosp-5.1.1-p5wifi-20150513. (Jollinnard). This ROM runs better than the UltraPlus I had before.
What are the advantages of your ROM over Jollinard's?
Nonomen said:
Just before your re-upload I installed aosp-5.1.1-p5wifi-20150513. (Jollinnard). This ROM runs better than the UltraPlus I had before.
What are the advantages of your ROM over Jollinard's?
Click to expand...
Click to collapse
There aren't any huge differences but here are a few notable changes
1) Ability to change battery icon
2) Battery color changes based on charge level
3) Pre rooted
4) Performance settings app included
5) Omniswitch recent
And a few others nothing big. IMO I prefer the browser in the omnirom over the aosp browser and the omni keyboard over the Google keyboard in the aosp ROM. But that's personal preference. Try both and pick a side *twix ad*
how i can use this rom for the p5 ?
thanks
4rch0 said:
how i can use this rom for the p5 ?
thanks
Click to expand...
Click to collapse
Edit the updater script and at the top where you see p5wifi simply delete the "WiFi" part so only p5 remains. Save the file put it back into the ROM zip and flash. Or you could simply flash the p5wifi recovery and you'll no longer have to worry about editing the script.
For future ROMs I think I'll remove the assert lines in the updater script so nobody else will have to worry about them.

HELP! Recommendations for Samsung Galaxy Tab 10.1" SM-P580?

I have a Samsung Galaxy Tab 10.1" SM-P580 and started working to root it so I could install more apps using a micro SD card. It was a long time ago with Android 7 or so and a while back I thought I would upgrade so I tried upgrading it to Android 11 and Lineage 18.1 and bare bones Google apps. This has been only partially successfully as the system runs but I cannot install any apps at all and have been unable to make any further progress. So I am looking to go back to the drawing board here. What recommendations do you have with regard to what to use that will allow me to install more apps? Thank you very much!
JR1979 said:
I have a Samsung Galaxy Tab 10.1" SM-P580 and started working to root it so I could install more apps using a micro SD card. It was a long time ago with Android 7 or so and a while back I thought I would upgrade so I tried upgrading it to Android 11 and Lineage 18.1 and bare bones Google apps. This has been only partially successfully as the system runs but I cannot install any apps at all and have been unable to make any further progress. So I am looking to go back to the drawing board here. What recommendations do you have with regard to what to use that will allow me to install more apps? Thank you very much!
Click to expand...
Click to collapse
I assume you got the basic stuff out of the way - unlocked bootloader, installed TWRP, etc.
Did you install a Gapps package?
If you prefer something more vanilla, without the LineageOS customizations, you can try an Android GSI, which is like turning your device into a Pixel tablet. Check out my guide here.
JR1979 said:
I have a Samsung Galaxy Tab 10.1" SM-P580 and started working to root it so I could install more apps using a micro SD card. It was a long time ago with Android 7 or so and a while back I thought I would upgrade so I tried upgrading it to Android 11 and Lineage 18.1 and bare bones Google apps. This has been only partially successfully as the system runs but I cannot install any apps at all and have been unable to make any further progress. So I am looking to go back to the drawing board here. What recommendations do you have with regard to what to use that will allow me to install more apps? Thank you very much!
Click to expand...
Click to collapse
There are differences between Android 7,8,9 and now, especially eg.the use of sd-cards and permissions for users in general. Maybe you have to check such things as "Allow Installing apps from unknown ressources" in Settings, or you ckeck magisk modules that could help.
abagm said:
There are differences between Android 7,8,9 and now, especially eg.the use of sd-cards and permissions for users in general. Maybe you have to check such things as "Allow Installing apps from unknown ressources" in Settings, or you ckeck magisk modules that could help.
Click to expand...
Click to collapse
Thanks for the input. I have it upgraded to Android 11. Yhe unknown resources shouldn't matter AFAIK, in this case, as I am only trying to install via Play Store. I was trying to work with Magisk - I have it installed. I was going to try the ExSD module but I haven't been able to add it.
V0latyle said:
I assume you got the basic stuff out of the way - unlocked bootloader, installed TWRP, etc.
Did you install a Gapps package?
If you prefer something more vanilla, without the LineageOS customizations, you can try an Android GSI, which is like turning your device into a Pixel tablet. Check out my guide here.
Click to expand...
Click to collapse
Thank you. I will look into that. I will look into what the differences are between that and LineageOS. Question: will the pen/stylus work under this configuration? Thank you again.
JR1979 said:
Thank you. I will look into that. I will look into what the differences are between that and LineageOS. Question: will the pen/stylus work under this configuration? Thank you again.
Click to expand...
Click to collapse
In theory, yes - because GSIs are meant to be used with the stock kernel, and the system image doesn't have to have any specific hardware support.
LineageOS is built from AOSP, with added tweaks and customizations. I used it for a while, but grew tired of the Magisk issues I was having (PHH builds have built in SuperSU) so I just went straight vanilla with GMS.
So I looked at your guide and decided to give it a shot. With Multidisabler, when I tried pushing that to the tablet with sideload, it failed. I have also been unable to move system.img to the tablet. I'm at a loss. I know I am missing something here but just can't figure out what I am doing wrong. I just want to get this tablet up and running with Android and being able to use the 400GB SD card.
Thanks.
JR1979 said:
So I looked at your guide and decided to give it a shot. With Multidisabler, when I tried pushing that to the tablet with sideload, it failed. I have also been unable to move system.img to the tablet. I'm at a loss. I know I am missing something here but just can't figure out what I am doing wrong. I just want to get this tablet up and running with Android and being able to use the 400GB SD card.
Thanks.
Click to expand...
Click to collapse
Does MTP work for you in TWRP? ADB sideload is only for installing zips from your computer; the correct command to send files to device storage is adb push. Still, if you're able to get storage access over USB in TWRP just move the files that way because it's simpler.
I'm honestly not sure if the multidisabler is necessary when using custom firmware or GSIs. I think most likely not.
V0latyle said:
Does MTP work for you in TWRP? ADB sideload is only for installing zips from your computer; the correct command to send files to device storage is adb push. Still, if you're able to get storage access over USB in TWRP just move the files that way because it's simpler.
I'm honestly not sure if the multidisabler is necessary when using custom firmware or GSIs. I think most likely not.
Click to expand...
Click to collapse
Sorry - I just saw this response from you. So MTP is enabled but my laptop was unable to see the tablet. I connected the SD card to my laptop and placed the system.img file on it and then dropped the SD card back into the tablet. I was able to see it in the File Manager. As you said to, I wiped /system and flashed the system.img file. It showed "[IMAGE FLASH COMPLETED]". But when I went to reboot from the main TWRP menu, it said there was no OS installed and asked if I was sure if I wanted to reboot. So I took a gamble and selected Reboot and System again. And I guess I lost on the gamble. It now just loops on the "Samsung Galaxy Tab A with S Pen" splash screen. Well, game over... for tonight.
JR1979 said:
Sorry - I just saw this response from you. So MTP is enabled but my laptop was unable to see the tablet. I connected the SD card to my laptop and placed the system.img file on it and then dropped the SD card back into the tablet. I was able to see it in the File Manager. As you said to, I wiped /system and flashed the system.img file. It showed "[IMAGE FLASH COMPLETED]". But when I went to reboot from the main TWRP menu, it said there was no OS installed and asked if I was sure if I wanted to reboot. So I took a gamble and selected Reboot and System again. And I guess I lost on the gamble. It now just loops on the "Samsung Galaxy Tab A with S Pen" splash screen. Well, game over... for tonight.
Click to expand...
Click to collapse
Don't worry about the No OS warning, I get the same thing on my Tab A after installing a GSI.
You formatted data, yes?
You did NOT wipe /boot or /product I hope?
Something I noticed with the LineageOS GSIs is that the securized ones bootlooped, and I had to flash one of the pre-rooted builds. Can you link the image you tried to flash?
As a test to ensure a GSI runs properly, download one of the Android Developer Preview GSIs and try installing that. Let me know how it goes.
I didn't wipe /boot or /product.
I did format data.
I used the system.img from the aosp_arm64-exp-T2B2.221216.006-9443277-e508d63f.zip file on this page, from the Android Developer Preview GSIs: https://developer.android.com/topic/generic-system-image/releases
I'm guessing I didn't select the right build ?
Thanks again!
JR1979 said:
I didn't wipe /boot or /product.
I did format data.
I used the system.img from the aosp_arm64-exp-T2B2.221216.006-9443277-e508d63f.zip file on this page, from the Android Developer Preview GSIs: https://developer.android.com/topic/generic-system-image/releases
I'm guessing I didn't select the right build ?
Thanks again!
Click to expand...
Click to collapse
I also just tried the system.img from gsi_gms_arm64-exp-T2B2.221216.006-9443277-12a8e193.zip file. I get the same results - the splash screen loop.
JR1979 said:
I also just tried the system.img from gsi_gms_arm64-exp-T2B2.221216.006-9443277-12a8e193.zip file. I get the same results - the splash screen loop.
Click to expand...
Click to collapse
And so I tried the system.img files from the 2 zip files that are in the Android 13 (stable) folder:
aosp_arm64-exp-TP1A.220624.014-8819323-996da050.zip
gsi_gms_arm64-exp-TP1A.220624.014-8819323-8a77fef1.zip
Neither of these work. I still get the splash screen boot loop.
One thing I noticed is when I wipe system, it shows:
========================================
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Failed to mount '/system_root' (Invalid argument)
Formatting system using mke2fs...
Done.
Updating partition details...
...done
=========================================
It's almost tablet frisbee time.

Categories

Resources