Related
Speedup your SD-Card reading Speed as follow steps:
1-Download and install "SD Tools" app that attached below and run to inform your sdcard write and read speed before applying speedup patch.
2-Download and install "Script Manager".
3-download "sdcardspeed.zip" file and Move "sdcardspeed.sh" file into your SD-Card.
4-Run "Script Manager" program and select "sdcardspeed.sh".
in opened page: fill the "Run as Root" and "Run at Boot" check boxes and Save!
5- Reboot the phone and after reboot "Allow" superuser!
6-Run again the "SD Tools" and compare your SD-Card speed after applying the patch.
Progress in your SD-Card speed is depend on your SD-Card Class.
Why not asking for SU after ReBoot!? (Here's explaing of the problem!): Thanks to GlossGhost
Lol, it really does something, Read: 4.5 MB/s
thanks good staff for my x10 i will test it later
the clock on the before shot shows that it was taken after the other
There's actually a new app called "SD increase " that will take care of the script for u
Sent from my X10i using XDA App
ermm... is there really a need to open a new thread when someone has already posted in our X10 General section where it should belong?
increase sdcard read/write speeds
anyway, good effort though...
GlossGhost said:
Lol, it really does something, Read: 4.5 MB/s
Click to expand...
Click to collapse
mine - 9.6 mb/s before
now is 10 mb/s
how to Allow SU after reboot?
microsd SU16G
cache set to 3072
before write 5.8 read 17.2
after write 6.5 read 26.1
Before 6.7
17.7
After 5.6
19.2
MicroSD SU08G
before
2.6
14.7
after
4.6
25.1
thanks
nonentity said:
ermm... is there really a need to open a new thread when someone has already posted in our X10 General section where it should belong?
increase sdcard read/write speeds
anyway, good effort though...
Click to expand...
Click to collapse
You can see downloads number of the thread
Why would my write speed go up but not my read speed? In fact my read is slower than the write!
Sent from my X10a using XDA App
great find!!
before write 1,2 read 12
after write 1,2 read 13,8
nice!!
my results WITHOUT the script:
1 - Write: 3.2 MB / s Read: 12.1 MB / s
2 - Write: 5.4 MB / s Read: 13.3 MB / s
3 - Write: 9.1 MB / s Read: 14.5 MB / s
4 - Write: 10.1 MB / s Read: 14.9 MB / s
5 - Write: 11.0 MB / s Read: 14.6 MB / s
6 - Write: 10.4 MB / s Read: 14.6 MB / s
Now with the script:
Firstly, the script did not do anything!
Message from GScript "sdcardspeed.sh: / system / bin / echo: not found"
this happens because I have echo in the xbin folder
After changing the file "read_ahead_kb" manually to 3072,
1 - Write: 9.9 MB / s Read: 32.6 MB / s
2 - Write: 10.3 MB / s Read: 29.8 MB / s
3 - Write: 10.3 MB / s Read: 30.3 MB / s
Conclusion,
first we need to make 3 or 4 tests without the script to get the real speeds, and secondly, only the reading speed increased (is already good enough).
Question: How does "read_ahead" could increase the writing speed?
Why not asking for SU after ReBoot!? (Here's explaing of the problem!)
memazy said:
mine - 9.6 mb/s before
now is 10 mb/s
how to Allow SU after reboot?
Click to expand...
Click to collapse
Okay, so I think everybody know's that when you turn on the phone, it's "Preparing SD Card" so the Script Manager is starting earlier than the sd card (i know the card is not starting but preparing). So the manager starts, and searches for the script, but there is NO sd card (because the sd card is preparing...) and what? Loading the script FAILS! That's why the manager don't ask for SuperUser permissions. That's why You have to move the "sdcardspeed.sh" to the INTERNAL MEMORY (I suggest moving it to the root folder of the INTERNAL MEMORY where are all the folders: system, sdcard.. etc) then you do all the instructions below.
Here's MY instructions:
1-Download and install "SD Tools" app that attached below and run to inform your sdcard write and read speed before applying speedup patch.
(attached @ first post!)
2-Download and install "Script Manager".
(attached @ first post!)
3-Download "sdcardspeed.zip" file and Move "sdcardspeed.sh" file into your SD-Card.
(attached @ first post!)
4-Use something like Root Explorer and move the "sdcardspeed.sh" file to the root folder of the INTERNAL MEMORY.
5-Run "Script Manager" search for the "sdcardspeed.sh" in the INTERNAL MEMORY not at the EXTERNAL MEMORY!" and select it.
6-In opened page: fill the "Run as Root" and "Run at Boot" check boxes and Save!
7- Reboot the phone and after reboot "Allow" superuser!
8-Run again the "SD Tools" and compare your SD-Card speed after applying the patch.
____________________________________________
That's from me
Nice one
Before:
5.9 and 15.5
After
9.6 and 46.8
Read speed increased by 3 times!!! Good one mate..
sony ericsson E10i (x10 mini)
To what cache/buffer size does this script increase the stock value?
My sd has the fastest speeds with 2048kb...
Does this work for 2.1?
I've changed the cache size manually with Root Explorer and I've seen a huge jump in my read and write speeds.
The only issue is that the change I made goes back to default when I reboot my phone.
I've seen other MODs but it required for me to have 2.2, which is why I'm asking.
vitas0y said:
Does this work for 2.1?
I've changed the cache size manually with Root Explorer and I've seen a huge jump in my read and write speeds.
The only issue is that the change I made goes back to default when I reboot my phone.
I've seen other MODs but it required for me to have 2.2, which is why I'm asking.
Click to expand...
Click to collapse
there's a guid in this thread
http://forum.xda-developers.com/showthread.php?t=1013554
before:
write : 4.0 mb/s
read : 11.9 mb/s
after:
write : 1.3 mb/s
read : 99.4 mb/s
something must be wrong... write speed 4x less and read speed 9x more
is there a possibility, both the stock Archos firmware to root and also with a boot menu such as OpenAOS to use.
Need to control both the floor on my A70H firmware with root right and as a second OS Debian Linux to the possibility of the software with a panoramic head Papywizard.
The Debian Linux I've done and it works flawlessly under OpenAOS, but unfortunately I have no right under Android Root.
Have also been tested UrukDroid, unfortunately, it works with the boot of an Alternative OS will not therefore have already contacted the developer of UrukDroid, unfortunately without positive result.
Sorry for my bad English.
Best regards
kwalter
Multiboot for OpenAOS works the same as Chulris Root but not for the last FW.
So if you want Root and Linux you have to downgrade the Archos to 2.3.81.
Ich you then boot through the Multiboot menu and select Android, you have root.
fzelle said:
Ich you then boot through the Multiboot menu and select Android, you have root.
Click to expand...
Click to collapse
Doesn't this also work with the latest firmware, because openaos multiboot uses unionfs to create an overlay over the archos firmware to give you read write access, su and superuser.apk.
I didn't upgrade, because of lack of time, it is still on my todo list.
Maurice
Do you think that your Kernel and InitRam is 100% compatible with the new FW?
P.S.: Any news on cm7?
Well there are only minor changes in the kernel from the latest firmware, so I guess it would be no problem to boot the new firmware with the openaos kernel.
However like I said I didn't try it myself yet, so that is why I asked if there are problems.
PS CM7:
For CM7 we have made good progress. However we have to wait until bubu has some time to finish the new unified multiboot menu for gen7 and gen8. In the mean time we are still improving CM7.
To get an impression on the progress just look at closed tickets and the commits on our git.
Maurice
openAOS A70H
hi,
can anyone help me?
i've created a ext4 partition on my A70H 250GB Harddisk with 50GB space.
On this partition i've put the Imagefiles for debian etc., what is the correct entry in menu.lst
to boot debian or other os from openAOS Bootmenu.
On Android over openAOS, fdisk say it is sda2.
When i put the following entry on Menu.lst it will not boot Debian etc. only Android boots correct:
Archos|ARCHOS|ARCHOS|/init|0
Debian|/dev/sda2|/rootfs.debian|/sbin/init|1
Angstrom|/dev/sda2|/rootfs.angstrom|/sbin/init|1
Gingerbread|/dev/sda2|/gingerbread.img|/init|0
or
Archos|ARCHOS|ARCHOS|/init|0
Debian|/dev/block/sda2|/rootfs.debian|/sbin/init|1
Angstrom|/dev/block/sda2|/rootfs.angstrom|/sbin/init|1
Gingerbread|/dev/block/sda2|/gingerbread.img|/init|0
What is the correct path to the second partition on openAOS Boottime??????
Sorry for my bad english.
Best regards
kwalter
It depends how your partition shows up in initramfs. To find out you could try serial debugging.
You can enable serial debugging in the boot menu by going to advanced menu and select Debugging then choose serial.
When your device is connected to your pc you can use minicom to get a shell on initramfs.
This is all explained http://dev.openaos.org/wiki/SettingUpMultiRootGen8#Debugging
In the initramfs shell you can see how your partition shows up by using "df" or looking at /dev etc.
However the way you want it doesn't work, you have to create a partition for each image file and unpack that image file on that partition. Partition booting is meant to get rid of image files.
Maurice
openAOS A70H
Hi,
sorry, but I do not understand.
If the image files I in the storage directory and the menu.lst like this I can change the whole boot without problems:
Archos | Archos | Archos | / init | 0
Debian | | / rootfs.img | / sbin / init | 1
Angstrom | | / angstrom.img | / sbin / init | 1
Gingerbread | | / gingerbread.img | / init | 0
Whether floor Archos firmware, Gingerbread, Angstrom or Debian, everything works 100%.
Unfortunately, I have 4GB but only for my Debian image since FAT file system.
Best Reagards
kwalter
You could change internal storage to ext3 to overcome the filesize problem.
However when you want to boot your image file from a different partition then you don't copy the image file to that partition, but you copy the contents of the image file to that partition. That is why you need a different partition for each image file.
In the multiboot menu we only loop mount image files from internal storage and not from other partitions. From other partitions they will be directly "booted" and not loop mounted first.
So what you can do is on your pc create a folder say /temp/mount/debian
Then you do the following:
Code:
$ sudo mount -o loop (path_to_where_your_archos_is_mounted)/rootfs.img /temp/mount/debian
This will mount your image file on the folder /temp/mount/debian
Then copy everything to your created partition on your archos using -rp option for recursive and preserve rights on the files.
Code:
$ sudo cp -rp /temp/mount/debian/* /(partition_on_your_archos)
After that adjust the menu.lst like you did before.
Maurice
Multiboot and root for A70H - Bluetooth
Hello at all,
so now I've finally managed to boot the Debian from a separate partition with openAOS.
But now comes the next problem, Bluetooth works
not more.
In the image it has worked reasonably clean, but once I
openAOS've installed boot menu does not work anymore.
Both the image and also on the partition, when I try to connect a Bluetooth device, gets out Blutooth.
(Only the devices, thats need a PIN for connection, all other devices are OK.)
Is there a solution?
Hope that someone can help me.
Best regards
kwalter
This is an idea to make the HD2 faster and fancy, I worked with Xylograph to make it more usable and easy to implement by common users.
Index
Post 1 Introduction
Post 2 ROMs, Scripts, Installer template for Devs by Xylograph
Post 3 Q&A
Introduction
We have SD ROMs for very long time, but I think most of the people should agree with me that the SD ROMs are slower than NAND ROMs. because the SD ROMs use system.ext4 and data.ext4 files to store all the ROM contant on the FAT partition, the IO access is the bottleneck.
My Class10 SD card has 10MB/s R/W speed, but the NAND flash R/W speed is only about 4MB/s. so if we can directly install the ROMs to SDCARD and boot from SDCARD we will get lots of benifits:
Faster Read/Write speed than NAND ROMs
Bigger data partition for user space (depends on how big the ext4 partition on SDCARD)
Install servel ROMs at the same time. and each ROM share the same space
Muilt-boot support, easy to switch between the ROMs been installed.
The NativeSD Rom is a new kind of ROM it needs an ext4 partition on your SDCARD.
This thread will tell you how to install a ROM to SDCARD and give some script templates for ROM Devs to make the ROM installer which can support install the ROM to NAND flash or SD/EXT4.
Install the ROM to SD/EXT4 will not effact the ROM(WM or Android) on NAND flash, NativeSD should support run from MAGLDR CLK or WM6.5(need test).
Important Notes:
Backup all the SDCARD content to PC before you create the ext4 partition on SDCARD.
Change Log:
05-09-2012 @2nd Post [05-09-2012] NativeSD Dual Installer v2 [nand/sdext][wip]
10-09-2012 Add NativeSD CM7 script template
13-09-2012 nativeSDMultiBoot Version4 Credits to datagr
20-09-2012 nativeSDMultiBoot Version5 Credits to datagr
26-09-2012 nativeSDMultiBoot Version6 Credits to datagr
30-10-2012 nativeSDMultiBoot Version9 Credits to datagr
30-10-2012 New initrd mod for NativeSD Credits to marco.palumbi
[05-09-2012] NativeSD Dual Installer v2 [nand/sdext][wip]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NativeSD Dual Installer v2
Keep in mind that this is a work in progress featuring a possibility to run a full nand rom on a SD-EXT partition..
Please check my current AOKP & PA jellybean ROMS or CM9ight ICS ROM for some 'NativeSD functionality' in action
Features:
Compatible with every bootloader and stock OS
Recovery package for users without Android on nand
Pre-Installation Requirements and recommendations:
HTC HD2 Phone
Sdcard with enough free space (performance may differ based on the quality of your card)
4EXT Recovery (Highly recommended)
Primary Fat32 partition and Primary EXT4 partition
Downloads : (Please do not mirror stuff)
Download 4EXT Recovery from here.
Pick the SD version if you would like to boot 4EXT Recovery from SD (unpack to your sdcard)
Pick the NAND version if you would like to flash the 4EXT Recovery on your NAND (flashable via recovery)
Users with non-working hardware keys can try the various touch recoveries I've ported , though I highly recommend 4EXT recovery..
Dual_Installer_v2_example.zip (only for advanced users, unpack the contents to your computer)
Contents :
4EXTRecoverySD for users with no or a different recovery on nand:
Code:
- Contains 4EXT Recovery ported for SD users.
- Unpack to the root of your sdcard
- Set your SD Boot to the Recovery folder or use clcad/haret to boot
4EXTRecoveryNAND for users who would like this recovery on nand:
Code:
- Contains 4EXT Recovery for android NAND users
- Flash it using DAF.exe (Magldr) cLK users can flash it using the HD2 toolkit
Dual Installer example Package (advanced users) :
Code:
- Contains an example (not flashable!) of how I use this for my roms.
- You can check all the stuff, folder structure and scripts.
- I've tried to make the updater-script and aroma-config 'easy to read'
- Placeholders with text on what to put where when porting stuff to NativeSD.
Installation Steps & Instructions:
Sdcard for NativeSD:
Code:
1. First make sure you have at least 1 Fat32 partition and 1 EXT4 partition on your sdcard
2. If you don't have these partitions ?? [B]backup your sdcard[/B][COLOR="Red"][B] , because everything will be wiped from your sdcard when you create partitions and format them ![/B][/COLOR]
3a Use the [URL="http://goo.im/devs/Xylograph/Various/Recoveries"]provided 4EXT recovery (NAND or SD version)[/URL] to create the partitions and format them.
3b If you rather use a computer for creating and formatting partitions keep in mind that both partitions [B]must[/B] be primary partitions (not logical)
4. The recommended size of your EXT4 partition is depending on how many roms and apps you are going to install.. 512M is the minimal size..
5. Restore/move the sdcard contents back to the Fat32 partition
6. (WP7 users) make sure the EXT4 partition is located @ /dev/block/mmcblk0p2
To check this mount your sd-ext partition in 4EXT recovery and use adb shell or QtADB shell and type [B]df[/B]
7. Your sdcard is now ready for NativeSD usage..
NativeSD Installation for Magldr NAND Android & WP7 users :
Code:
1. WP7 and SD users set your SD BOOT directory to the 'Recovery' folder by choosing '10.services' , '1. Bootsettings' , 3. AD SD Dir in the Magldr menu.
2. Boot into (NAND or SD) 4EXT recovery.
3. Flash the ROM.zip package and follow instructions
4. Set your SD BOOT directory to the 'NativeSD' folder after flashing the ROM (see step 1)
5. Boot into the ROM and have fun..
NativeSD Installation for cLK NAND Android users : (thanks clio94)
Code:
1. Copy the [URL="http://www.mediafire.com/?nhyausx0p5whu"]flash_bootv2.zip[/URL] to your sdcard.
2. Boot into cLK and make a sboot partition.Be aware that only clk from kokotas allows to make a sboot partition directly from device
3. Boot into recovery (4EXT recovery = recommended) and install rom by choosing sd-ext method
4. After installation finishes,dont reboot, but install flash_sbootv2.zip and then reboot to cLK
5. In cLK choose to boot from sboot and wait for the ROM to boot.
6. If you are stuck on the boot animation,try to wipe your ext partition and install the ROM again.
NativeSD Installation for Windows Mobile and other OS users :
Code:
1. Boot into recovery by executing the usual clcad and haret stuff inside the Recovery folder.
2. Flash the ROM.zip package and follow instructions
3. Reboot and boot the ROM by executing the usual clcad and haret stuff inside the NativeSD folder.
RMNET or PPP ??? summary :
Code:
- as of dual installer v2 you can choose your data connection during ROM installation
- For Magldr users I recommend using the RMNET connection
- For all other users I recommend using the PPP connection (default)
- PPP connection should work for all users !
Switch between different NativeSD ROMS ?
Code:
- If you want to use a previously installed/other NativeSD ROM ?
- Copy the contents of that roms folder found inside the NativeSD folder to the root of the NativeSD folder (overwriting the kernel+ramdisk)
- Boot to sd and that ROM will boot !
- Repeat the above steps when you want to switch again
- In the future we want to make the above steps easier and possible with either a 'gscript' or an 'android app'
Previous Roms (Examples) featuring NativeSD and Dual Installer :
Code:
- [URL="http://d-h.st/pFR"]PA_v1.992se_dual_installer_v2.zip[/URL] - [B][URL="http://tinyw.in/Xhft"]mirror[/URL][/B] (Flash via recovery) - md5: ce2138748c6b2cbc62848272acf92600
- [URL="http://d-h.st/p33"]AOKP_N2408se_dual_installer.zip (Magldr only!)[/URL] - [B][URL="http://tinyw.in/clMS"]mirror[/URL][/B] (Flash via recovery) - md5: 6a116ad3eebb0f92729af6954f0a9217
*** all flashing is at your own risk ! Always make backups in recovery and/or titanium backup ! ***
*** This is a NativeSD thread ! Please, Keep this thread NativeSD related and report issues with roms in the rom thread !!! ***
Thanks & Credits to : securecrt, Phoenix, clio94, LNE team and everybody I forgot !
Q&A
How is the NativeSD ROM work?
To boot the Android from SD card, the old SD ROMs mount the system.ext4 and data.ext4 before the init(rename to init.android) thread is start. I changed the initrd.gz to make it mount the ext4 partition before the android init.android start. here is the main code for the init script
Code:
echo "mount system and data partition on sdcard"
# change the rom_name TO PA MIUI CM7 will support
# to boot other system on SD/EXT4
# the system layout :
# /NativeSD/NexusHD2/
# /system
# /data
# /PA/
# /system
# /data
# /MIUI/
# /system
# /data
# /app
# the app dir is shared for all ROMs
#
# set the name of the rom to boot
rom_name="PA"
# mount the 1st (NativeSD) SD-EXT partition
mkdir -p /NativeSD
mount -t ext4 -o rw,noatime,nodiratime,barrier=0 /dev/block/mmcblk0p2 /NativeSD
# mount the system data app dir
mount --bind /NativeSD/$rom_name/system /system
mount --bind /NativeSD/$rom_name/data /data
# create app data/app dir
mkdir -p /NativeSD/app
mkdir -p /data/app
mount --bind /NativeSD/app /data/app
So for the ROM Devs should create new initrd.gz which is different with the NAND version, use different rom_name distinguish with others the whole templete is in 2nd post by Xylograph
How is the multi-boot works on NativeSD ROM?
Set the SD boot dir /sdcard/NativeSD in Magldr or CLK,the dir structure is
/sdcard/NativeSD/NexusHD2/zImage
/sdcard/NativeSD/NexusHD2/initrd.gz
/sdcard/NativeSD/PA/zImage
/sdcard/NativeSD/PA/initrd.gz
/sdcard/NativeSD/zImage
/sdcard/NativeSD/initrd.gz
The Magldr& CLK always read the /sdcard/NativeSD/zImage /sdcard/NativeSD/initrd.gz files to boot, so if you want to switch from PA to NexusHD2 just only need to copy the zImage & initrd.gz to the up layer dir, use the NativeSD ROM switch app made by datagr
How to convert the NAND ROM to NativeSD ROM?
HOWTO port NAND ROM to NATIVESD STEP-BY-STEP Credits to c1cl0n
This is for Devs and advanced users only. For example if we got the NAND version of the NexusHD2 extract the zip file and replace 2 files and add 1 file will finish the convert.
/kernel/boot/initrd.gz
the initrd.gz is similar with the SD ROMs but need to change the init script to mount the ext4 partition
/META-INF/com/google/android/updater-script
the updater-script is used for CWM to execute the install process; execute install.sh before copy the system content to the ext4, here is the sample code
Code:
package_extract_file("install.sh", "/tmp/install.sh");
set_perm(0,0, 0777, "/tmp/install.sh");
run_program("/tmp/install.sh");
show_progress(0.8, 80);
if file_getprop("/tmp/nfo.prop","NativeSD") == "true"
then
package_extract_dir("kernel/boot", "/boot");
package_extract_dir("kernel/boot", "/boot_dir");
package_extract_dir("system", "/system");
......
else
ui_print("can't find ext4 partition on your SDcard");
ui_print("install failed");
endif;
/install.sh
Code:
#!/sbin/sh
# Set the ROM name
ROM_NAME=NexusHD2
export ROM_NAME
mmcblk0p2=`ls /dev/block/mmcblk0p2`
# Mount the ext4 partition
if [ $mmcblk0p2 == "/dev/block/mmcblk0p2" ]
then
mkdir -p /ext4p
mkdir -p /sdcard/NativeSD/$ROM_NAME
mkdir -p /boot /boot_dir
mount -t ext4 /dev/block/mmcblk0p2 /ext4p
mkdir -p /ext4p/$ROM_NAME/system /ext4p/$ROM_NAME/data
mount --bind /ext4p/$ROM_NAME/system /system
mount --bind /ext4p/$ROM_NAME/data /data
mount --bind /sdcard/NativeSD/$ROM_NAME /boot
mount --bind /sdcard/NativeSD /boot_dir
#delete the old system
rm -rf /system/*
#clean the dalvik-cache
rm -rf /data/dalvik-cache/*
#all the dir has ready write some info for updater-script
echo "NativeSD=true" >> /tmp/nfo.prop
else
#no ext4 partition found
echo "NativeSD=false" >> /tmp/nfo.prop
fi
How to make ext4 partition on my SDCARD?
http://forum.xda-developers.com/showthread.php?p=31414628#post31414628
Spaqin said:
You just posted it, but I have a couple of questions - what is it really? How SD builds will be faster because of that? What can we expect? How will it work? Any details?
Click to expand...
Click to collapse
Securecrt will explain everything.. give the man some time to create the first post..
Expect the same/similar or even better performance compared to android on NAND with a descent SD card.
I will post an example ROM which I am working on so people can check it out @ 2nd post when I am done with it..
Spaqin said:
You just posted it, but I have a couple of questions - what is it really? How SD builds will be faster because of that? What can we expect? How will it work? Any details?
Click to expand...
Click to collapse
:laugh: Just be patient. I am updating the post.
Wow man! I can hardly wait!
securecrt said:
[coming soon] ...
This is an idea to make the HD2 more faster, I worked with Xylograph to make it more usable and easy to implement by common users.
Click to expand...
Click to collapse
Xylograph said:
Securecrt will explain everything.. give the man some time to create the first post..
Expect the same/similar or even better performance compared to android on NAND with a descent SD card.
I will post an example ROM which I am working on so people can check it out @ 2nd post when I am done with it..
Click to expand...
Click to collapse
Looking forward to trying this
Sent from my GT-I9100 using Tapatalk 2
Well everybody (especially sd rom users) waiting to test this stuff can already start by making sure they have an SD-EXT (EXT4 if possible) partition on their sd-card..
Make a big one for future use
Xylograph said:
Well everybody (especially sd rom users) waiting to test this stuff can already start by making sure they have an SD-EXT (EXT4 if possible) partition on their sd-card..
Make a big one for future use
Click to expand...
Click to collapse
ready - steady ...
dimdimdim said:
ready - steady ...
Click to expand...
Click to collapse
GO GO GO !!!
ext4 partition can be made from windows using minitool partition wizard home edition http://www.partitionwizard.com/download.html
I assume FAT32 partition should be first and ext4 partition second.
Robbie P said:
ext4 partition can be made from windows using minitool partition wizard home edition http://www.partitionwizard.com/download.html
I assume FAT32 partition should be first and ext4 partition second.
Click to expand...
Click to collapse
What size partition should I create?
I usually use partitions of 1 or 2 GB on 16 or 32 GB cards
hi..
my phone's hardware button (green button) is not working.. so i can not make any changes to magldr..
currently, my boot folder is set to ICS..
I was just wondering if its possible to edit the initrd.gz as mentioned in post 3 in such a way that it would reflect my folder (ICS) instead of NativeSD?
should i just replace all places which have NativeSD with my folder that is ICS? or is it just some specific places?
jjblaster3 said:
hi..
my phone's hardware button (green button) is not working.. so i can not make any changes to magldr..
currently, my boot folder is set to ICS..
I was just wondering if its possible to edit the initrd.gz as mentioned in post 3 in such a way that it would reflect my folder (ICS) instead of NativeSD?
should i just replace all places which have NativeSD with my folder that is ICS? or is it just some specific places?
Click to expand...
Click to collapse
I did not consider this case... let me think how to solve it.
Robbie P said:
ext4 partition can be made from windows using minitool partition wizard home edition http://www.partitionwizard.com/download.html
I assume FAT32 partition should be first and ext4 partition second.
Click to expand...
Click to collapse
Yes sir, or use recovery for partitioning your sdcard.. I recommend 4EXT recovery for the job.
aldai2 said:
What size partition should I create?
I usually use partitions of 1 or 2 GB on 16 or 32 GB cards
Click to expand...
Click to collapse
Depends on how many roms you are going to install...
I think 2 GB is a nice start.. especially when apps will be shared in future updates you won't have to install all apps over and over again.
securecrt said:
I did not consider this case... let me think how to solve it.
Click to expand...
Click to collapse
much appreciated friend, keeping my hopes up
Great work guys, have installed on a class 6, speed seems fine (personally I haven't found there to be any noticeable lag with SD builds).
Have just run some benchmarks; would attach if i could find a screenshot button. And will see how it performs for a day or two and report back before messing with it.
Just a suggestion, but with future builds are you considering adding an option to choose which ext to install to? So that you can have multiple sd-ext builds and/or a NAND build with a sd-ext and a separate sdext rom.
Likin' the installer as well, haven't used aroma too often, but you've customised this one and made it your own.
Nice Work.
Can't find screenshot, so. Using a class 6 card in:
Code:
System Test = 3398 ; SD card read/write = 13.6/8.0 MB/s
PassMark Performance = 816 ; Internal Storage read/write = 14.7/13.1 MB/s External Storage r/w = 15.1/8.27 MB/s
AnTuTu = 2741 (typical SDROM score) SD card r/w = 9.7/7.4 MB/s
jjblaster3 said:
hi..
my phone's hardware button (green button) is not working..
Click to expand...
Click to collapse
So besides changing the folder are you actually able to enter recovery without a working green key?
You'll need that 2
Xylograph said:
So besides changing the folder are you actually able to enter recovery without a working green key?
You'll need that 2
Click to expand...
Click to collapse
Couldn't he copy the files into the partition on the desktop? Using ubuntu for example, or while in a running nand build? Or would that be likely to cause issues?
Xylograph said:
So besides changing the folder are you actually able to enter recovery without a working green key?
You'll need that 2
Click to expand...
Click to collapse
well to b honest when i read on the first post that wm6.5 users and magldr users using wp7 in nand are also to be supported in the future, i never considered that recovery was a must.. guess i was wrong
I have a new external micro sd card for my ICS device (worked fine at first). I tried using the Paragon NTSF android app and evidently screwed my card up nice and hard. Here is what i can and cant do (connecting usb via 2 steps microsd->sd then sd->usb):
1. Windows 7 Disk Management sees the device (but device says something along the lines of no medium)
2. linux Disk Utility sees the device although under "capacity" it says "no medium found"
(when i try to format the device i get the error: "Error creating partition table: helper exited with exit code 1: cannot open /dev/sdb: No medium found")
3. linux command: [email protected]:~$ sudo dd if=/dev/zero of=/dev/sdb bs=512 count=1
dd: opening `/dev/sdb': No medium found
4. linux command:
Jan 26 17:47:56 adam-NC20-NB20 kernel: [ 596.153946] scsi4 : usb-storage 1-3:1.0
Jan 26 17:47:57 adam-NC20-NB20 kernel: [ 597.152949] scsi 4:0:0:0: Direct-Access Generic Storage Device 0.00 PQ: 0 ANSI: 2
Jan 26 17:47:57 adam-NC20-NB20 kernel: [ 597.161322] sd 4:0:0:0: Attached scsi generic sg1 type 0
Jan 26 17:47:57 adam-NC20-NB20 kernel: [ 597.162392] sd 4:0:0:0: [sdb] Attached SCSI removable disk
sudo fdisk 597.162392
(So it sees the device)
any help? Im very nub at linux. Also a nub at IT in general but hopefully i can fix my device.
(There is no data on the drive so im willing to try anything at all)
Reading around i came up with a hypothesis that i deleted some type of software that is needed for the hardware to work???
Have you tired inserting the card into another phone to format it? Which Linux distro are you using?
May be your partition table is gone. try something like partition magic and use repair drive option. Its better if you can use a micro SD card reader for this.
@weatheredeyec57
using lubutu and also ubuntu for the linux distros. tried multiple phones as well
@suki300me
why is a direct microsd reader better than going through micro to regular?
This is my first post, please bear with me if I'm asking an obvious question. I am trying to update my WinCE 6.0 sat nav to an Android OS (I believe my current version is known as S100 and (I think) I am upgrading to S150)
Here's what I have been supplied by the manufacturer of my sat nav:
SD Boot Fusing Tool
2 x BIN files to be fused to the SD card; SD-bl1-8k.bin and u-boot_sdboot.bin
A Panasonic SD card formatter
I have followed their rough instructions which are converted from Chinese:
1. Format SD card to FAT32 format performing complete erase
2. Add the 2 x BIN files to the tool for fusing to the SD card. This is where I am stuck.
I am receiving the following error message "Can't Read MBR Sector from Drive"
To confirm the SD card is not the issue I have swapped SD cards, run chkdsk /f against the drive and used the Rufus tool to obtain the following log output:
Deleting partitions...
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Partitioning (MBR)...
Closing existing volume...
Waiting for logical drive to reappear...
Formatting (FAT32)...
Using cluster size: 4096 bytes
Quick format was selected
Creating file system...
Format completed.
Writing master boot record...
Drive has a Zeroed Master Boot Record
Using Windows 7 MBR
Found volume GUID \\?\Volume{d9671328-5dee-11e5-825a-5442490c7ece}\
Successfully remounted Volume{d9671328-5dee-11e5-825a-5442490c7ece}\ on G:\
Found USB 2.0 device 'HSDPA MMC Storage USB Device' (1C9E:6061)
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 483, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x065A8C2D
Drive has a Windows 7 Master Boot Record
Partition 1:
Type: FAT32 LBA (0x0c)
Size: 3.7 GB (3979345920 bytes)
Start Sector: 2048, Boot: No, Recognized: Yes
Can anyone help me as I do not understand what the issue is. This is the first time I have attempted this type of thing.
Cheers
Chris
This is the error I am seeing:
66chrisscott99 said:
This is my first post, please bear with me if I'm asking an obvious question. I am trying to update my WinCE 6.0 sat nav to an Android OS (I believe my current version is known as S100 and (I think) I am upgrading to S150)
Here's what I have been supplied by the manufacturer of my sat nav:
SD Boot Fusing Tool
2 x BIN files to be fused to the SD card; SD-bl1-8k.bin and u-boot_sdboot.bin
A Panasonic SD card formatter
I have followed their rough instructions which are converted from Chinese:
1. Format SD card to FAT32 format performing complete erase
2. Add the 2 x BIN files to the tool for fusing to the SD card. This is where I am stuck.
I am receiving the following error message "Can't Read MBR Sector from Drive"
To confirm the SD card is not the issue I have swapped SD cards, run chkdsk /f against the drive and used the Rufus tool to obtain the following log output:
Deleting partitions...
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Partitioning (MBR)...
Closing existing volume...
Waiting for logical drive to reappear...
Formatting (FAT32)...
Using cluster size: 4096 bytes
Quick format was selected
Creating file system...
Format completed.
Writing master boot record...
Drive has a Zeroed Master Boot Record
Using Windows 7 MBR
Found volume GUID \\?\Volume{d9671328-5dee-11e5-825a-5442490c7ece}\
Successfully remounted Volume{d9671328-5dee-11e5-825a-5442490c7ece}\ on G:\
Found USB 2.0 device 'HSDPA MMC Storage USB Device' (1C9E:6061)
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 483, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x065A8C2D
Drive has a Windows 7 Master Boot Record
Partition 1:
Type: FAT32 LBA (0x0c)
Size: 3.7 GB (3979345920 bytes)
Start Sector: 2048, Boot: No, Recognized: Yes
Can anyone help me as I do not understand what the issue is. This is the first time I have attempted this type of thing.
Cheers
Chris
This is the error I am seeing:
Click to expand...
Click to collapse
Might help you to provide a pic of the unit itself. There are literally hundreds of these devices.
Sent from my SGH-I337M using Tapatalk
Flukester69 said:
Might help you to provide a pic of the unit itself. There are literally hundreds of these devices.
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
Good shout. Here it is:
m.alibaba.com/product/1447649060/ZESTECH-2-DIN-CAR-DVD-STEREO.html
And the spec:
m.alibaba.com/product/1447649060/ZESTECH-2-DIN-CAR-DVD-STEREO/specifications.html
Sorry, I'm too new to post urls ?
Sent from my D6603 using Tapatalk
Bump. Anyone? Ty
Sent from my D6603 using Tapatalk
Solved. It appears that you cannot write to that sector unless you run the application as an administrator
Sent from my D6603 using Tapatalk