Related
I thought since the cm5b4 thread is getting hard to navigate through that i would pull some helpful info out of it and make it in a seperate thread
I TAKE NO CREDIT FOR THE INFO BELOW, jerbarton should get credit for the procedure
As usual I'm not responsible for any problems you may encounter or broken phone, i also cant confirm if this works on any other rom's but cyans and there is no gurantee it will always work but here you go
EDIT:When updating to a new CM rom you WILL encounter a boot loop, simply run the steps below AGAIN during the loop cycle and then reboot the phone and it should work.
ALWAYS NANDROID!!
you will need to have an ext2 partition before this will work, i believe you can make one with the "partition" option in recovery
Code:
adb remount
adb push 04apps2sd /system/etc/init.d/
adb push e2fsck /system/xbin
adb shell
chmod 755 /system/xbin/e2fsck
chmod 755 /system/etc/init.d/04apps2sd
mkdir /system/sd
Downloads:
e2fsck: http://www.mediafire.com/?tzwwjyz2t2r
04apps2sd: http://www.mediafire.com/?mjjntmtmjmj
Attempted this, and I've never once tried doing apps2sd. I dl'ed the files to the root of my SD card after partitioning the SD card to ext2. After this was done, I went to my terminal emulator, but all I get from the commands are "adb: not found"
What am I doing wrong?
heroskyy said:
Attempted this, and I've never once tried doing apps2sd. I dl'ed the files to the root of my SD card after partitioning the SD card to ext2. After this was done, I went to my terminal emulator, but all I get from the commands are "adb: not found"
What am I doing wrong?
Click to expand...
Click to collapse
You have to get the android sdk kit on your computer and type in those commands from tools. Make sure those files are placed in your tools folder so it can find them(adb). Also need to hold down shift and right key to open up command in folder.
nonmindo said:
I thought since the cm5b4 thread is getting hard to navigate through that i would pull some helpful info out of it and make it in a seperate thread
I TAKE NO CREDIT FOR THE INFO BELOW, jerbarton should get credit for the procedure
AS usual I'm not responsible for any problems you may encounter or broken phone, i also cant confirm if this works on any other rom's but cyans and there is no gurantee it will always work but here you go
ALWAYS NANDROID!!
you will need to have an ext2 partition before this will work, i believe you can make one with the "partition" option in recovery
Code:
adb remount
adb push 04apps2sd /system/etc/init.d/
adb push e2fsck /system/xbin
adb shell
chmod 755 /system/xbin/e2fsck
chmod 755 /system/etc/init.d/04apps2sd
mkdir /system/sd
Downloads:
e2fsck: http://www.mediafire.com/?tzwwjyz2t2r
04apps2sd: http://www.mediafire.com/?mjjntmtmjmj
Click to expand...
Click to collapse
Thanks for putting this up but your crediting wrong person. First and foremost Cyanogen(his script pulled from rom) Second, dhanj was the first to post the script on here and the other guy added to it( the one your giving credit too.) Go back and read original post.
kamasi36 said:
You have to get the android sdk kit on your computer and type in those commands from tools. Make sure those files are placed in your tools folder so it can find them(adb). Also need to hold down shift and right key to open up command in folder.
Click to expand...
Click to collapse
awesome! thank you! Ive always been confused about that
heroskyy said:
awesome! thank you! Ive always been confused about that
Click to expand...
Click to collapse
Ha. me too man. You have to learn fast on here. They expect us to know all this stuff coming in the gate. Just holla back if you need some more help. I'm a noob too but managed to figure it out.
http://forum.xda-developers.com/showthread.php?t=532719
This might help you get started. make sure you get everything updated because this is kind of dated.
kamasi36 said:
Thanks for putting this up but your crediting wrong person. First and foremost Cyanogen(his script pulled from rom) Second, dhanj was the first to post the script on here and the other guy added to it( the one your giving credit too.) Go back and read original post.
Click to expand...
Click to collapse
Yeah cyanogen (especially) and dhanj should be credited more than me. I didn't really do anything but add on how I got it working for me.
One thing to mention, if cyanogen doesn't implement this officially in his ROM (and for most people it's probably not needed) you'll have to redo this procedure each time you flash/update so I'd suggest keeping the 2 files saved.
@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
In any case, I was also hesitant on starting a new thread about this because of the apps2sd, need or not to need discussion that's been going on. Anyway, I'm glad you did post this and glad that there are others asides from myself(kamasi, jerbarton, t0pgun & dscottjr81 that I know of!) who chose to get this up and running on their nexus one.
As for who get's credit, I certainly cannot take any credit for this because all I did was share information. The real credit goes to cyanogen and the great devs we have here on xda that made our toys even more enjoyable that it was stock.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3
dnanj said:
@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
In any case, I was also hesitant on starting a new thread about this because of the apps2sd, need or not to need discussion that's been going on. Anyway, I'm glad you did post this and glad that there are others asides from myself(kamasi, jerbarton, t0pgun & dscottjr81 that I know of!) who chose to get this up and running on their nexus one.
As for who get's credit, I certainly cannot take any credit for this because all I did was share information. The real credit goes to cyanogen and the great devs we have here on xda that made our toys even more enjoyable that it was stock.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3
Click to expand...
Click to collapse
Thanks dnanj. Just upgraded to ext. 3. apps2sd b4 now.
You betcha....as always, just sharing information whenever I can.
am i suppose to get a conformation in shell if the commands worked?
Ohal_yeah said:
am i suppose to get a conformation in shell if the commands worked?
Click to expand...
Click to collapse
When the commands complete, you should be brought back to the prompt where the shell awaits the next command.
I apologize for not looking deeper into who deserves credit here, thanks for those of you that do know!! I was simply just trying to make it easier to get the information to people that might want it...
as for the debate of needing a2sd or not, i was out of space right from the get-go because of all the apps i had on my mt3g...so to me i definitely need it out of the 1gb partition i made on my sd card i have .82 free now lol...
completed all steps but everything still saves to internal memory
JustinLoe said:
completed all steps but everything still saves to internal memory
Click to expand...
Click to collapse
a small glitch probably when you run the last command before adb reboot, it fails to create the directory as it exists, probably change the name to solve it, it happened to me once
dnanj said:
@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3
Click to expand...
Click to collapse
hi, what does the code has anything to do with app2sd? anyone cares to shed some lights to a newcomer?
TIA
jakontil said:
hi, what does the code has anything to do with app2sd? anyone cares to shed some lights to a newcomer?
TIA
Click to expand...
Click to collapse
ext3 is essentially a ext2 file system with journaling.
Click Here to read about ext3 and it's benefits over an ext2 fs. As to why ext2 over ext3 for apps2sd, since journaling improves reliability of the fs, that makes it more ideal than ext2.
it works great thanks!
hi dnanj
thanks for the link
sorry but im stuck here
C:\android-sdk-windows\tools>adb remount
remount succeeded
C:\android-sdk-windows\tools>adb push 04apps2sd /system/etc/init.d/
failed to copy '04apps2sd' to '/system/etc/init.d/': Is a directory
C:\android-sdk-windows\tools>
why does cmd show me this error can you help me out please..very much appreciated
I don't want to dual-boot, even, just have a nice "normal" Nookie Froyo install on eMMC. I've seen several allude to the fact that it worked for them but no reviews of how they did it. I've backed up my 2.1 install with Clockwork so I'm not really worried about that.
TIA.
It's quite simple actually. All you need is basic knowledge of adb.
All disclaimers apply, I'm not responsible for any damage. Just know that mine is running on internal partitions. And the SD does mount too!
Before doing anything, I would recommend applying a dd from your partitions to your pc.
With, for example on mmcblk0p1 (boot) adb: dd if=/dev/block/mmcblk0p1 of=boot.img
You should do that for each partition to be safe (0p1 to 0p8).
All the following commands can be execute one after one, the separations are only there to makes things a bit more clear.
Then,
Boot to a working Nookie (NF) with your uSD fresh from burning, without any google apps, and without any uSD damaged errors.
Empty your internal system and copy uSD system over, by doing:
- adb shell mount -o remount,rw /dev/block/mmcblk1 / (---there is a space after the 1---)
- adb shell
- mkdir tmpfolder
- mount /dev/block/mmcblk0p5 tmpfolder
- cd tmpfolder
- rm -r * (---note that there is space after the r---)
- cd ..
- cp -r system/* tmpfolder (---this will take a few minutes---)
- umount tmpfolder
Click to expand...
Click to collapse
Then, you need to boot push the attached files (bottom of post) except for the 2 vold files to your boot partition: mmcblk0p1. Unzip, copy content, not zip.
You could very well replace uImage with the new Quickie overclocked uImage for froyo (see dev thread).
To push attached files to boot, do:
- mount /dev/block/mmcblk0p1 tmpfolder
- exit
- adb push [folder-containing-4-attached-files-except-vold.fstab] tmpfolder
- adb shell
- umount tmpfolder
Click to expand...
Click to collapse
I would also recommend erasing all your data. But that's up to you, if you want to keep your data on it. In any case, you can revert back with the data.img you created above . So next part you could skip, haven't tried skipping personally:
Non mandatory, but you could do:
- mount /dev/block/mmcblk0p6 tmpfolder
- cd tmpfolder
- rm -r *
- cd ..
- umount tmpfolder
Click to expand...
Click to collapse
Then you need to push vold.fstab and vold.conf (unzip volds, copy content) to system/etc
Copy vold's to system/etc:
- mount /dev/block/mmcblk0p5 tmpfolder
- exit
- adb push [folder-with-vold's] tmpfolder/etc/
- adb shell
- umount tmpfolder
- rm -r tmpfolder
- exit
Click to expand...
Click to collapse
Then shut down, remove uSD, and boot.
Again, you can choose to push the Quickie uImage, I you prefer, but the accelerometer doesn't work with it at the moment. The 950 kernel does sometimes crash on boot, but once booted is quite stable.
I think that's all folks. I could have been a bit vague at some times, but this should work. And if you made your imgs as recommended, you're bullet proof.
To revert back to initial state with img files, you need to copy files to sdcard and then dd:
- adb shell mount -o remount,rw /dev/block/mmcblk1p1 sdcard
- adb push XXX.img sdcard (--could take a few minutes--)
- dd if=XXXX.img of=/dev/block/mmcblk0pX
Click to expand...
Click to collapse
Do that for each partition.
For those who don't feel up to the task, I could make a CWR flashable zip file of all this. The only thing is, CWR dosen't boot on Nookie just yet. So you couldn't restore with a zip after the change.
[Before doing anything, I would recommend applying a dd from your partitions to your pc.
With, for example on mmcblk0p1 (boot) adb: dd if=/dev/block/mmcblk0p1 of=boot.img
You should do that for each partition to be safe (0p1 to 0p8).
[/QUOTE]
I am a little confused here. What are the names of the 7 other partitions? Thanks, Great guide btw!
See here.
Do you see improved speed and touch response running nookie from emmc?
im getting a "No such file or directory" error after "adb push [folder-with-vold's] tmpfolder/etc"
I created the directory but now it looks like i am stuck at the landscape android splash screen on boot...
any ideas? I am attempting to redo the whole process again just incase i missed something.
Sorry, there's a slash after etc.
Make sure you've copied the systen files, with "ls" inside tmpfolder where you copied system. Should be a etc folder there.
Sam
to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.
FastCR said:
to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.
Click to expand...
Click to collapse
Thanks but I don't see how that comment adds anything here.
Looks like the issue is above commands copy the actual system folder (not the contents of the folder) To the root of the partition. ls shows the folder "system" not the contents including etc. They are inside the folder but if the partition is mounted as system then the folder is redundant. Will check copying the contents and see if that helps.
Once I get it working in will post back to let others know
**** in the first block of code replace
Code:
- cp -r system tmpfolder (---this will take a few minutes---)
with
Code:
- cp -r system[B]/*[/B] tmpfolder (---this will take a few minutes---)
many thanks!
FastCR said:
to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.
Click to expand...
Click to collapse
Why would you go out of your way to say that? It's not constructive. As a junior member with three posts and 0 thanks after a year and a half, sharpen your teeth here at XDA before you act like a big shot.
Right thanks. Changed it.
Has it worked for you?
Sent from my HTC Desire using XDA App
samuelhalff said:
You could very well replace uImage with the new Quickie overclocked uImage for froyo (see dev thread).
Click to expand...
Click to collapse
Are you certain on this part? Last I read in that thread, Froyo needs a different minimum kernel.
UPDATE: Nevermind, I missed this updated effort.
Homer
Well, last time I checked, my NC was running at 950 on froyo with setcpu.
Check the forum. There's a nookie version of quickie. Except accelerometer doesn't work..
First, huge thanks to the second poster - great guide! Can we sticky this?
Second, yes I know what dd does, etc, I've been working with Linux for about ten years . I just don't know the ins and outs of embedded devices yet.
samuelhalff said:
Right thanks. Changed it.
Has it worked for you?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
yeah i was up till 4am last night but got it working. first i tried to use my existing nf sd card... bad idea. would boot from emmc to the touch android screen to begin, but could not get past. i assume it was the issue on nookdevs because wifi was not enabled. so i removed the setupwizard.apk but somehow bricked and was unable to boot from emmc. so i took the following steps to get things working properly:
1. reimage boot and system from the stock 1.0.1 images and reset the nook to stock, didnt even touch. at the intro screen i just powered it off.
2. next i took a fresh nf sdcard and run steps from your post(with the correction to copy system contents)
3. from there i had a working nf from sdcard! i did my tweaks (google apps, market fix and button remapping from nookdevs froyo tips)
i might to put together a post with a more verbose set of instructions for a one stop froyo shop but if i do i will be sure to give you credit for your contribution.
thanks again!
Hi,
Second, yes I know what dd does, etc, I've been working with Linux for about ten years . I just don't know the ins and outs of embedded devices yet.
Click to expand...
Click to collapse
Well, that's a nice contrast. I've been working on Linux/Android for about 2 months now
I should have mentioned that the NF uSD Card must be a newly burnt image, without all the nookie tips added to it. Of course, your Google framework will crash if you port it without your data.
By the way, there's a nice trick to get past the numb android interface, simply touch every corner of the screen, starting with top left and going clockwise. You'll then be sent the your home screen, and from there you'll log on to google account again.
I think the best way of doing it would to create a flashable .zip, which I'll make tonight if I find the time and if people are really interested. But don't forget CWR dosen't work on nookie for the time being. The only way back would be through adb.
So, does anyone wish to have a flashable zip of this? Or will it be a waist of time?
Sam
samuelhalff said:
Hi,
Well, that's a nice contrast. I've been working on Linux/Android for about 2 months now
I should have mentioned that the NF uSD Card must be a newly burnt image, without all the nookie tips added to it. Of course, your Google framework will crash if you port it without your data.
By the way, there's a nice trick to get past the numb android interface, simply touch every corner of the screen, starting with top left and going clockwise. You'll then be sent the your home screen, and from there you'll log on to google account again.
I think the best way of doing it would to create a flashable .zip, which I'll make tonight if I find the time and if people are really interested. But don't forget CWR dosen't work on nookie for the time being. The only way back would be through adb.
So, does anyone wish to have a flashable zip of this? Or will it be a waist of time?
Sam
Click to expand...
Click to collapse
I would love a flashable .zip. I think many others would as well.
starkruzr said:
I would love a flashable .zip. I think many others would as well.
Click to expand...
Click to collapse
Can't wait for a flashable zip. Maybe even some cm7 release candidates would make me real happy.
Sent from Nooted NookColor using XDA App
For anyone actively working with and on the webtop portion of these phones, you'll have noticed that webtop suffers greatly from sluggish response. I decided to experiment and through that, managed to alleviate a large portion of my problems. By creating and enabling a swap partition, I gained a very noticeable increase in performance on my webtop.
1: Remove SD card from phone and mount onto a computer capable of formating as Linux Swap.
Linux machines can obviously do this with any partition manager.
Windows machines can do so with: Paragon Partition Manager
Mac: I'm not currently sure what tool can handle creating swap partitions.
2: Create Swap partition on SD Card. (I personally made mine 1.5 GB)
3: Put SD Card back into phone and boot fully into webtop.
4: In Synaptic, download Partitionmanager. (This is the only partition manager package I have found to do anything at all in the webtop. If anyone has any luck with others, please post what lead to your success.)
(Path Method):
5: Inside Partitionmanager, navigate to the swap partition of your SD card and take notice of the "Device:" line underneath the the bar Volumes bar.
6: If in gnome, Alt+F2 and type
Code:
gksudo gedit /etc/fstab
If in any other desktop environment, open a terminal and type
Code:
sudo gedit /etc/fstab
7: Append the following line to fstab replacing "<path>" with the value in the "Device:" line of partitionmanager:
Code:
<path> none swap sw 0 0
(UUID Method)
5: Inside either Webtop terminal or phone Terminal Emulator type:
Code:
su
blkid
Look for the line which contains
Code:
TYPE="swap"
.
Alongside "TYPE" should be a
Code:
UUID="xxxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx"
.
(If no "UUDI" is listed, take the path of the device from the same line and do the following replacing "<path>" with the path value from above.)
Code:
sudo mkswap <path>
6: If in gnome, Alt+F2 and type [code]gksudo gedit /etc/fstab
If in any other desktop environment, open a terminal and type
Code:
sudo gedit /etc/fstab
7: Append the following line to fstab replacing "<UUID>" with the value in the "UUID=" line of blkid:
Code:
UUID=<UUID> none swap sw 0 0
8: Reboot phone
9: Download Script Manager from the android market.
10: Download View attachment swap.sh.zip and unzip it to a directory of your SD Card where you won't erase it.
11: In Script Manager, navigate to the directory you placed the script and select "swap.sh".
12: Check:
Code:
"Run as root" and "Run at boot"
13: Click "Run"
14: Profit!
To see if it is working, open terminal emulator or a terminal window on either phone or webtop. Type the command "free". and take notice of the "Swap" line. It should tell you the partition size, amount used, and amount free.
Hope this helps someone.
**Tested Working Phones**
Motorola Droid Bionic
Motorola Milestone A854 (Nearly Identical to A855) {blkid is not compiled on this phone. /etc/fstab is non-existent. Easiest way of making the proper /etc/fstab is to partition the swap as the 2nd partition on the card and only have 2 partitions total. This will ensure that the path for the swap is "/dev/block/mmcblk0p2"}
Motorola Atrix 4G using faux123's 2.4beta (Several kernels for the Atrix 4G do not support swap. faux123's 2.4beta does, however) thanks nabicat
If anyone has any other phones that they can confirm working, PM me and I'll add them to the list. If anyone has a phone that requires any special steps, be sure to list the steps taken along with the PM.
*UPDATE!! 06/23/12*
I am currently running the ICS leak 2033 on my Bionic. Webtop is running ICS Tablet. For starters, even without swap space, this version of webtop runs smooth as butter. Swap space IS still capable, though, and does still improve performance. To those who are leery about having android instead of ubuntu for webtop, I challenge you to try it. Some will like it (I certainly do). Others will hate it.
One change that needs to be noted: ICS kernel doesn't support the -a tag on "swapon" instead of using "-a" you'll need to put the path in the command script instead. In my case, the script now reads "swapon /dev/block/mmcblk0p2". It still needs to be run as root. Webtop picks up immediately when you run the script, so no extra steps there. Chrome beta is sexual on webtop 3.0, btw.
Special Thanks:
Sogarth: Fantastic work with webtop2sd across multiple platforms. Opened monstrous doors for all of this.
tallnerd1985: Compiling a great guide for multiple steps of unlocking webtop
[mbm]: Fixing what Moto broke
Natronics: Providing the UUID solution in this guide
Very nice, I will have to test this out tomorrow. Webtop is working well minus some hiccups with Bluetooth mice not clicking properly and display.
But if I want to use this for Citrix receiver and OpenOffice, will definitely want to get this going.
hey bang, an easier way to find the UUID of the swap partition is to run blkid from terminal....it should actually list it as TYPE="swap".
Awesome thanks! I'll give this a try right now and report back!
Natronics said:
hey bang, an easier way to find the UUID of the swap partition is to run blkid from terminal....it should actually list it as TYPE="swap".
Click to expand...
Click to collapse
Very nice. I'll update the guide when I get a chance to reflect that. I'm guessing from either terminal emulator on phone and terminal in webtop?
I ran it on the webtop terminal. it showed the UUID with the quotations after the UUID. so I removed the quotations and entered the UUID into fstab.
---------- Post added at 05:40 PM ---------- Previous post was at 05:17 PM ----------
this is what it looks like in blkid:
/dev/block/mmcblk0p2: UUID="a0a11111-a94e-4fa1-ada0-69186b667b1e" TYPE="swap"
The UUID should look like this when you paste it in fstab:
UUID=a0a11111-a94e-4fa1-ada0-69186b667b1e
this is what the finished product looks like in fstab:
UUID=a0a11111-a94e-4fa1-ada0-69186b667b1e none swap sw 0 0
If you don't see a UUID when you do blkid...
get the location of the partition using blkid... mine was /dev/block/mmcblk0p2
then do a:
sudo mkswap /dev/block/mmcblk0p2
replace the /dev/block/mmcblk0p2 with your sdcards path if it is different than mine. That will set a UUID to the swap partition.
Just a note to those who aren't familiar with linux and/or UUIDs. YOUR actual UUID will be different. You'll have to actually run blkid in either the webtop terminal or terminal emulator (both work. run as super user).
UUID has benefits and drawbacks when compared with the device paths:
UUID values won't change unless the partition is destroyed and recreated. If it's moved around and/or resized, it'll remain the same.
Paths are easier to determine and remember for the less knowledgeable.
Thanks for clarifying the uuid being different for everyone. Forgot to mention that part.
Sent from my HTC Flyer P510e using XDA App
Oops, got distracted half way though. Anyways, works great! Noticeably snappier right away. Thank you so much for noticing this! Seems like Motorola should have had this on from the get go...
I have Paragon installed on my computer but I am still fuzzy on how to make this swap partition. Can anyone help me?
dB Zac said:
I have Paragon installed on my computer but I am still fuzzy on how to make this swap partition. Can anyone help me?
Click to expand...
Click to collapse
delete or resize the existing partition to create blank space. Make a new partition the size you want for swap. Choose "Linux Swap" as the partition type.
I couldn't find an option for swap partition. I made the space but couldn't get past that step
dB Zac said:
I couldn't find an option for swap partition. I made the space but couldn't get past that step
Click to expand...
Click to collapse
It's called "File System Type" or "Partition Type". It's the same option as where you'll find "FAT32" and "NTFS" file systems. You're looking for either "Linux Swap" or "Swap Space"
Banggugyangu said:
It's called "File System Type" or "Partition Type". It's the same option as where you'll find "FAT32" and "NTFS" file systems. You're looking for either "Linux Swap" or "Swap Space"
Click to expand...
Click to collapse
Man, that is weird. I found all those options but there is no option that says swap.....
Sent from my DROID BIONIC using Tapatalk
dB Zac said:
Man, that is weird. I found all those options but there is no option that says swap.....
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
I'm not using it myself, so I don't know for sure what options you have. Perhaps you can list them or post a screenshot of them so I can know more of what's going on?
NTFS, FAT16, FAT32 and none is all it offers
dB Zac said:
NTFS, FAT16, FAT32 and none is all it offers
Click to expand...
Click to collapse
Hmm that must be a limitation on the free version. You could always download a live CD of ubuntu and use GParted inside that to do the job.
Banggugyangu said:
Hmm that must be a limitation on the free version. You could always download a live CD of ubuntu and use GParted inside that to do the job.
Click to expand...
Click to collapse
confirmed. the free version did not have the "swap" partition options but the paid one does
If you paid for it, that's a little foolish, as downloading ubuntu is free and comes w/ GParted on the live CD.
Hey guys I have a question for you all about sd-cards
I sbf'd
Installed ota 5.7.894 (because of no true .906 sbf I won't flash it)
Regained root
Installed busybox 1.20 (figured newer might be better)
Installed safestrap (tweaked of course 1.08f)
Now
My phone see's the internal/external sd-cards fine and mounts/formats/explores just fine
My laptop also see's internal/external sd-cards just fine
However
Rootbrowser cannot see the sd-card
Safestrap cannot find /sdcard
But
Root explorer can see the internal and external just fine
I have tried sbfing several times to see if it will fix it
I have tried not installing the ota,changing versions of busybox ect..
Why can my phone see and work with the sd-cards just fine but programs cannot?
Because safestrap cannot see the sd-card I cannot create backups..
Any help is greatly appreciated
I think Rick#2 acknowledged this in the safestrap 1.08f thread and had this advice for those experiencing the error:
(For the record, this change almost worked for me - safestrap would now access my external sdcard (/sdcard), but when I would select a zip to flash, it would just take me back to the menu. I dropped a reply with my results in that thread.)
Rick#2 said:
While you're in Safestrap, either go into the console or "adb shell" into your phone. (Remember that for adb to work properly in the recovery your phone has to boot up with the USB cable already connected).
If you type:
Code:
ls -l /dev/block | grep mmcblk0
what output does it provide? For me, it spits out "mmcblk0" but... I'm pretty sure that for those that aren't able to mount their external sdcards it will say mmcblk0p1. In which case, the fix is easy; I'll be sure to update my package, obviously, but for those of you who want to try a little DIY, copy the file /systemorig/etc/safestrap/recovery.zip onto your computer and unzip it. Inside, there's be a file called /etc/recovery.fstab; edit this and change the line corresponding to /sdcard (It ought to be on line 3, or the second line of actual text) to the following:
Code:
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
Click to expand...
Click to collapse
At this point, after copying the recovery.fstab back to my phone, I assumed I had to correct the permissions of the file, so I did. If I am wrong, someone please let me know!
continuing his reply...
Doesn't really matter how many spaces you have between; ideally you'll just need to hit tab each time.
Hopefully this is what the issue was. I remembered changing that line because I was getting random error messages about my external /sdcard and since I didn't see /dev/block/mmcblk0p1 in my /dev/block directory I assumed I must have made a typo and changed it... here's one tiny example of how easy it is to completely bork these things. Multiply it by a million and you have kernel development...
Click to expand...
Click to collapse
That might work if it was just safestrap having the issue..but its not
Even cwm cannot backup the apps on the sd-card as it cannot see it as well..
But root explorer and the stock file browser can see the internal/external sd-cards
And write on them just fine..and even mount/unmount and format...arrrggggg
This is killin me
Hey!
I found this thread with fully compile-able code for android on most hardware platforms, I see it uses system level modifications to do its business, and would love to see it rolled into a magisk module. I regularly use external hard drives on my Pixel 2 XL for a plethora of reasons and really need legit exFat and NTFS support as I use flash kernel and I cant merge the code myself (my only machine couldn't handle the compiling). Anyway, If possible, making a ZIP that is universal and has the binaries for arm, arm64, and all x86 variants would be pretty great!
GitHub: https://github.com/Lurker00/Android-fs
XDA: https://forum.xda-developers.com/android/development/exfat-ntfs-fuse-drivers-easy-build-t3126413
I am not magisk-ninja so anyone who can help make this happen OR educate me in the process of doing so (and who can compile the above Git files for arm64 and send them to me) would be very much appreciated! I am willing to learn to help the community!
Over and out
thomasamas said:
Hey!
I found this thread with fully compile-able code for android on most hardware platforms, I see it uses system level modifications to do its business, and would love to see it rolled into a magisk module. I regularly use external hard drives on my Pixel 2 XL for a plethora of reasons and really need legit exFat and NTFS support as I use flash kernel and I cant merge the code myself (my only machine couldn't handle the compiling). Anyway, If possible, making a ZIP that is universal and has the binaries for arm, arm64, and all x86 variants would be pretty great!
GitHub: https://github.com/Lurker00/Android-fs
XDA: https://forum.xda-developers.com/android/development/exfat-ntfs-fuse-drivers-easy-build-t3126413
I am not magisk-ninja so anyone who can help make this happen OR educate me in the process of doing so (and who can compile the above Git files for arm64 and send them to me) would be very much appreciated! I am willing to learn to help the community!
Over and out
Click to expand...
Click to collapse
Hi. I just started working on this yesterday.
It seems like the perfect method to install additional filesystem support.
I am currently able to manually mount exfat or ntfs sdcard images on my phone (LG Aristo 2, Android 7).
However, a great deal has changed in how filesystem support is added to an existing kernel. Lurker00's code is for Android 4.4.2.
If you want to work together on it, I would be more than happy to do so. I will try to get together what I have so far in a post later today.
FYI, this is a TWRP installable .zip that has Lurker00's compiled binaries for arm64-v8a, armeabi-v7a, x86 and x86_64.
It also installs init.d scripts that supposedly support auto mounting of exFat and NTFS partitions. That part is not working for me, as I think it is setup for Android 5 and before. However the mount binaries work for manually mounting exFat or NTFS partitions.
Just install the .zip from TWRP.
https://forum.xda-developers.com/attachment.php?attachmentid=4600419&stc=1&d=1537390717
Hey! I just saw this, I can try my best but I was assuming it wouldn't be an android thing but rather a Linux/android kernel thing. Is there a way we can Abstract the mounting from android, solely into the kernel, basically leaving Android unaware that the introduced file system is not "officially supported"? I'm assuming FUSE can do this.
Edit: spelling.
tecknight said:
Hi. I just started working on this yesterday.
It seems like the perfect method to install additional filesystem support.
I am currently able to manually mount exfat or ntfs sdcard images on my phone (LG Aristo 2, Android 7).
However, a great deal has changed in how filesystem support is added to an existing kernel. Lurker00's code is for Android 4.4.2.
If you want to work together on it, I would be more than happy to do so. I will try to get together what I have so far in a post later today.
FYI, this is a TWRP installable .zip that has Lurker00's compiled binaries for arm64-v8a, armeabi-v7a, x86 and x86_64.
It also installs init.d scripts that supposedly support auto mounting of exFat and NTFS partitions. That part is not working for me, as I think it is setup for Android 5 and before. However the mount binaries work for manually mounting exFat or NTFS partitions.
Just install the .zip from TWRP.
https://forum.xda-developers.com/attachment.php?attachmentid=4600419&stc=1&d=1537390717
Click to expand...
Click to collapse
How exactly do you manually mount them? (your method)
Edit: also! I was thinking maybe this could become a kernel patch that I could alert kernel devs to? (see my above comment)
And... Thanks for all the hard work to get this going. Tell me how I can help!
thomasamas said:
How exactly do you manually mount them? (your method)
Edit: also! I was thinking maybe this could become a kernel patch that I could alert kernel devs to? (see my above comment)
And... Thanks for all the hard work to get this going. Tell me how I can help!
Click to expand...
Click to collapse
I installed the .zip file that I posted earlier using TWRP.
This installs these binaries to /system/xbin:
mount.exfat
mkfs.exfat
fsck.exfat
dumpexfat
exfatfsck
exfatlabel
mkexfatfs
mount.exfat-fuse
ntfs-3g
ntfsfix
probe
I then inserted an exFat formatted SDCard into my phone and Android told me the device was corrupt.
That is due to the fact that Android no longer uses probe to determine the filesystem of a device, it now uses a program called blkid.
I would like to figure out how to add a new supported filesystem type to blkid
In any event, I mounted my exFat sdcard by launching a shell from adb, running su to get root and then I created a folder named exfatsd in the /mnt folder. I then ran this command:
mount.exfat /dev/block/mmcblk1 /mnt/exfatsd
The mount succeeded and I was able to browse the sdcard from /mnt/exfatsd
When I typed mount to enumerate the mounts, this is the entry I saw for my sdcard:
/dev/block/mmcblk1 on /mnt/exfatsd type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
By the way, even as i was browsing the exfat sdcard, Android still had a notification up telling me that my sdcard was corrupt
Is there any legit documentation on blkid?
I haven't found any, but I haven't given up on this project either. I have been busy on a couple of other things lately, but I still would like to see this work.
Making progress on this on my LG cv1 ROMs
I just wanted to let you know that I now have exFAT and NTFS support working on my phone, even though the kernel does not have support for either filesystem..
I am mounting the Micro SD using a script that runs under Magisk from the:
post.fs.data.d folder
This folder contains scripts that are to run immediately after the /data filesystem is mounted.
My script is checking the Micro SD device using the blkid command.
The blkid command will indicate the type of filesystem residing on the device, even if the kernel won't mount it.
So I use the results from the blkid command to issue mount commands myself using the binaries created by lurker00.
Here is the script I am using, it is really quite short:
Code:
#!/system/bin/sh
#
# mount NTFS / exFAT
# 06/07/2019 by TecKnight
# This script checks the inserted Micro SD--
# If Micro SD is formatted exFAT or NTFS, it mounts it
sdcard_device=`blkid /dev/block/mmcblk1`
sdcard_part1=`blkid /dev/block/mmcblk1p1`
# Uncomment next 2 lines to troubleshoot
# echo $sdcard_device > /cache/sdcard_device.txt
# echo $sdcard_part1 > /cache/sdcard_part1.txt
# output from blkid command looks like this:
# /dev/block/mmcblk1p1: LABEL="e" UUID="CEDC-3F3A" TYPE="exfat"
# create mount point
mkdir /mnt/media_rw/extsd
# mount approriate filesystem if it resides on device directly
case "$sdcard_device" in
*exfat*) mount.exfat /dev/block/mmcblk1 /mnt/media_rw/extsd ;;
*ntfs*) ntfs-3g /dev/block/mmcblk1 /mnt/media_rw/extsd ;;
esac
# mount approriate filesystem if it resides on first partition of device
case "$sdcard_part1" in
*exfat*) mount.exfat /dev/block/mmcblk1p1 /mnt/media_rw/extsd ;;
*ntfs*) ntfs-3g /dev/block/mmcblk1p1 /mnt/media_rw/extsd ;;
esac
FYI: The reason I am checking /dev/block/mmcblk1 (the actual SD card itself) and dev/block/mmcblk1p1 (the first partition on the sdcard) is that depending on where the sdcard is formatted exFAT or NTFS, it could be on the disk itself or within a parrition. This way, I will catch it either way and mount it correctly.
I was thinking of creating a subroutine to cycle through the block devices to determine the sdcard device.
This would make it compatible with practically every device.
Then I could turn the whole thing into a Magisk module.
There are still 2 minor issues that I am having:
1. The phone still displays a notification about the sdcard being corrupt. You just have to clear the notification and it never reappears.
2. The mounted card is not identified as an external SD by android.
However, the exFAT or NTFS filesystem is mounted at /mnt/media_rw/extsd and is browseable and the filesystem is readable and writable.
Tell me what you think.
TWRP installable .zip to install NTFS/exFAT suport
OK, this is a installable .ZIP that will copy the binaries to /system/xbin and copy the mounting script to:
/data/adb/post-fs-data.d.
This should enable NTFS/exFAT support to most phones.
Requirements:
1. You must have Magisk installed
2. Your Micro SD''s device address must be:
/dev/block/mmcblk1. This is the case on most devices running Android 6 or higher.
If your Micro SD's device address is different, you can fix it by modifying:
/data/adb/post-fs-data.d/mount_ntfs_exfat.sh
replacing /dev/block/mmcblk1 with the device address of your external Micro SD.
Download the installer here:
https://forum.xda-developers.com/attachment.php?attachmentid=4773292&stc=1&d=1559992139
tecknight said:
OK, this is a installable .ZIP that will copy the binaries to /system/xbin and copy the mounting script to:
/data/adb/post-fs-data.d.
This should enable NTFS/exFAT support to most phones.
Requirements:
1. You must have Magisk installed
2. Your Micro SD''s device address must be:
/dev/block/mmcblk1. This is the case on most devices running Android 6 or higher.
If your Micro SD's device address is different, you can fix it by modifying:
/data/adb/post-fs-data.d/mount_ntfs_exfat.sh
replacing /dev/block/mmcblk1 with the device address of your external Micro SD.
Download the installer here:
https://forum.xda-developers.com/attachment.php?attachmentid=4773292&stc=1&d=1559992139
Click to expand...
Click to collapse
Hi,
I know this post isn't new, but I tried installing this zip file and it tells me that my bootloader in't unlocked even though I'm pretty sure it's unlocked,
any way around this?
rachelld said:
Hi,
I know this post isn't new, but I tried installing this zip file and it tells me that my bootloader in't unlocked even though I'm pretty sure it's unlocked,
any way around this?
Click to expand...
Click to collapse
Same here. Maybe the template is to old? Also could use this module.
aCIDsLAM said:
Same here. Maybe the template is to old? Also could use this module.
Click to expand...
Click to collapse
Try this one:
https://www.androidfilehost.com/?fid=4349826312261782012I removed the check for
ro.boot.bl_unlock_complete = true
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
rachelld said:
Hi,
I know this post isn't new, but I tried installing this zip file and it tells me that my bootloader in't unlocked even though I'm pretty sure it's unlocked,
any way around this?
Click to expand...
Click to collapse
Try this one:
https://www.androidfilehost.com/?fid...26312261782012
I removed the check for
ro.boot.bl_unlock_complete = true
I could flash it, using TWRP. In Magisk itself, it told me me, its no magisk module. Anyway. Thanks!
@thomasamas
@tecknight
Is this thread dead ?
Has these drivers been tested on Android 11 ?
I have a custom ROM and would like to use my SDCard with NTFS/exFAT but the ROM only supports FAT32.
KineSight said:
@thomasamas
@tecknight
Is this thread dead ?
Has these drivers been tested on Android 11 ?
I have a custom ROM and would like to use my SDCard with NTFS/exFAT but the ROM only supports FAT32.
Click to expand...
Click to collapse
+1
tecknight said:
TWRP installable .zip to install NTFS/exFAT suport
OK, this is a installable .ZIP that will copy the binaries to /system/xbin and copy the mounting script to:
/data/adb/post-fs-data.d.
This should enable NTFS/exFAT support to most phones.
Requirements:
1. You must have Magisk installed
2. Your Micro SD''s device address must be:
/dev/block/mmcblk1. This is the case on most devices running Android 6 or higher.
If your Micro SD's device address is different, you can fix it by modifying:
/data/adb/post-fs-data.d/mount_ntfs_exfat.sh
replacing /dev/block/mmcblk1 with the device address of your external Micro SD.
Download the installer here:
https://forum.xda-developers.com/attachment.php?attachmentid=4773292&stc=1&d=1559992139
Click to expand...
Click to collapse
Actually, this still works! Have tested this on A11 OctaviOS GSI. You still need to have Magisk installed, but you don't necessarily have to install this as a Magisk module.
Don't flash the .zip file from TWRP, it doesn't do anything (at least not for me). Just unzip everything in the .zip file into a folder. Then, take the files inside the xbin folder and put it into /system/xbin (as per instructions). Make sure those files have execute permissions. I just set the xbin folder with full execute permissions and apply to all child files in the folder, by using Root Explorer.
Next, do the same thing by taking the script and chuck that into /data/adb/post-fs-data.d. Again, give this script full execute permissions.
Reboot phone and voila, it should work! You should also see that the script is loaded and running in Magisk logs.
Oh and the reason why Magisk is required is because Magisk creates that "post-fs-data.d" folder after it is installed. If you put scripts into /data/adb/service.d or /data/adb/post-fs-data.d, they will automatically get executed by Magisk and run with superuser rights.
chaoscreater said:
Actually, this still works! Have tested this on A11 OctaviOS GSI. You still need to have Magisk installed, but you don't necessarily have to install this as a Magisk module.
Don't flash the .zip file from TWRP, it doesn't do anything (at least not for me). Just unzip everything in the .zip file into a folder. Then, take the files inside the xbin folder and put it into /system/xbin (as per instructions). Make sure those files have execute permissions. I just set the xbin folder with full execute permissions and apply to all child files in the folder, by using Root Explorer.
Next, do the same thing by taking the script and chuck that into /data/adb/post-fs-data.d. Again, give this script full execute permissions.
Reboot phone and voila, it should work! You should also see that the script is loaded and running in Magisk logs.
Oh and the reason why Magisk is required is because Magisk creates that "post-fs-data.d" folder after it is installed. If you put scripts into /data/adb/service.d or /data/adb/post-fs-data.d, they will automatically get executed by Magisk and run with superuser rights.
Click to expand...
Click to collapse
Hello, I did everything as you said and it worked normally, but now SELinux is turned off. This is normal?
i have same issue. But i cant find xbin folder
my device is Samsung M51 on custom os
I converted this twrp zip into a magisk module https://github.com/phhusson/treble_experimentations/files/8948418/ntfs-exfat-support.zip
Hi.
I'm using Ancient OS A13 and I can't access my SD Card.It asks for format and after formatting it still asks for format.
it still works on my pc and twrp recovery. Unfortunately, this fix isn't working. Also, there is not any xbin folder in system.
What should I Do?