Hi!
I've been getting an unholy amount of PM's asking for help. I would kindly like to redirect all of you Windows users to Viper Matrix Wireless' useful little tool: http://forum.xda-developers.com/showthread.php?t=824154
For those of us that love installing apps and tinkering around with Android on our HD2's, 256MB of "Device" memory simply isn't enough! This fix will increase the size of the data.img file so that there will be more free space available when it's mounted. This is especially beneficial for users running on Android 2.1! See the attached picture!
Download the data.img file corresponding to your build or resize your own by using the instructions at the bottom of this post.
1GB userdata.img for shubCRAFT CM6/Froyo/Themed RC1.1!
http://cid-1dff7e1df294438f.office....ta.img for shubCRAFT CM6FroyoThemed RC1.1.rar
http://dl.dropbox.com/u/7684410/xda...ta.img for shubCRAFT CM6FroyoThemed RC1.1.rar (mirror)
http://www.vbnfiles.com/xda/birkoffsjunk/1GB userdata.img for shubCRAFT CM6FroyoThemed RC1.1.rar Thanks to birkoffsjunk for the high speed mirror!
1GB data.img for mattc Leo + Froyo w/Sense RC1.2!
http://cid-1dff7e1df294438f.office....ers/1GB data.img for mattcFroyoWSenseRC1.2.7z
http://dl.dropbox.com/u/7684410/xda-developers/1GB data.img for mattcFroyoWSenseRC1.2.7z (mirror)
http://www.vbnfiles.com/xda/birkoffsjunk/1GB data.img for mattcFroyoWSenseRC1.2.7z Thanks to birkoffsjunk for the high speed mirror!
512MB data.img v1.1 for DarkStone's Desire v5!
http://cid-1dff7e1df294438f.office....B data.img^_v1.1 for darkstone^_desire^_v5.7z
http://dl.dropbox.com/u/7684410/xda-developers/512MB data.img_v1.1 for darkstone_desire_v5.7z (mirror)
http://www.vbnfiles.com/xda/birkoffsjunk/512MB data.img_v1.1 for darkstone_desire_v5.7z Thanks to birkoffsjunk for the high speed mirror!
512MB data.img for dan1j3l's Froyo v1 (w/o Sense)!
http://cid-1dff7e1df294438f.office....s/512MB data.img for dan1j3l-LeoFroyo-1.0.rar
http://dl.dropbox.com/u/7684410/xda-developers/512MB data.img for dan1j3l-LeoFroyo-1.0.rar (mirror)
http://www.vbnfiles.com/xda/birkoffsjunk/512MB data.img for dan1j3l-LeoFroyo-1.0.7z Thanks to birkoffsjunk for the high speed mirror!
1GB data.img v1.1 for DarkStone's Froyo v1!
http://cid-1dff7e1df294438f.office....ata.img^_v1.1 for darkstone^_HD2Froyo^_v1.rar
http://dl.dropbox.com/u/7684410/xda-developers/1GB data.img_v1.1 for darkstone_HD2Froyo_v1.rar (mirror)
http://www.vbnfiles.com/xda/birkoffsjunk/1GB data.img_v1.1 for darkstone_HD2Froyo_v1.rar Thanks to birkoffsjunk for the high speed mirror!
1GB data.img v1 for DarkStone's Froyo v1!
http://cid-1dff7e1df294438f.office..../1GB data.img for darkstone^_HD2Froyo^_v1.rar
http://dl.dropbox.com/u/7684410/xda-developers/1GB data.img for darkstone_HD2Froyo_v1.rar (mirror)
http://www.vbnfiles.com/xda/birkoffsjunk/1GB data.img for darkstone_HD2Froyo_v1.7z Thanks to birkoffsjunk for the high speed mirror!
1GB data.img v1 for DarkStone's Desire v5!
http://cid-1dff7e1df294438f.office....rs/1GB data.img for darkstone^_desire^_v5.rar
http://dl.dropbox.com/u/7684410/xda-developers/1GB data.img for darkstone_desire_v5.rar (mirror)
http://www.vbnfiles.com/xda/birkoffsjunk/1GB data.img for darkstone_desire_v5.7z Thanks to birkoffsjunk for the high speed mirror!
NOTE: It's best to reformat (or delete ALL your Android files) from your card before replacing the file. Alternatively, manually modify your data.img file using the instructions below.
Changelog
02/08/2010 - Added 1GB userdata.img for shubCRAFT CM6/Froyo/Themed RC1.1
02/08/2010 - mirrors added
29/07/2010 - Added 1GB data.img for mattc Froyo w/Sense RC1.2
29/07/2010 - v1.1 for Desire v5 fixes looping boot animation, screenshot: IMG_4331.jpg
29/07/2010 - Added 512MB data.img for dan1j3l-LeoFroyo-1.0
28/07/2010 - v1.1 fixes carrier issues for Froyo v1, Desire v5 unaffected
28/07/2010 - Added 1GB data.img v1 mods for DarkStone's Desire v5 and Froyo v1, screenshot:
{
"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"
}
-----------------------------------------------OR-------------------------------------------------
Manually edit data.img if you want a different size or use a different build!
I wrote this tutorial using a European HD2, 8GB microSD card, DarkStone's Froyo_v1 and a laptop running Ubuntu 10.04, your experience may vary.
Requirements:
Desktop/Laptop running some form of Linux.
IMPORTANT NOTE: Both, a PC and a Mac, can resize the .img file but not modify (specifically - run resize2fs) the ext2 file system that Android uses. I was in a hurry to post the resizing instructions and didn't fully test the procedure on a PC. Currently, this procedure is only possible on a Linux based operating system. I apologize if your time was wasted.
data.img file
HD2, microSD card, microUSB cable etc, etc (you might be better off using a card reader)
--------------------------------------------(Running Linux)----------------------------------------------
Procedure:
1. UnZip Android or your present data.img file to your Home Folder. Or a folder of your liking (or even on your memory card!), just remember to cd before you do the following:
2. Open Terminal and Copy&Paste (Ctrl+C, Ctrl+Shift+V) this:
Code:
dd if=/dev/zero bs=1M count=XXX >> data.img
where XXX is the amount, in MB, by which data.img should be increased by.
My filesize started out as 256MB and I wanted a total of 512MB. That would mean I needed a extra 256MB, so I executed this:
Code:
dd if=/dev/zero bs=1M count=256 >> data.img
3. Run a file system check and file system resizer
Code:
e2fsck -f data.img
resize2fs data.img
e2fsck -f data.img
if prompted, press "y" for "yes"
4. Copy all of the Android files onto your SD card, put it into your phone, and run CLRCAD.exe and HARET.exe!
-----------------------------------------------TIPS!-------------------------------------------------
Don't know how to cd?
If you're running a modern build of Linux you can just mount your SD card (phone or cardreader), open File Browser and paste "dd if=/dev/zero bs=1M count=XXX >> " into your open Terminal. This way you can just drag and drop the file into Terminal rather than typing out the file location!
Mounting:
If you're switching between builds and need to copy more than just your apps (apps are easily backed up by ASTRO File Manager - found on the Android Market), mount your data.img file and copy/backup the relevant data before moving on!
Linux:
Code:
mount -o loop data.img /mnt/data
you can put your apps into the AndroidApps folder before booting for them to be auto-installed
---------------------------------------------------------------------------------------------------------------------
EDIT:
added screenshot
added modded data.img for non-Linux users
added modded data.img for non-Linux users for desire v5 too!
put files at the top of the post
added changelog
added mirrors
added instructions for PC
Noice! I was exactly thinking about this since I started trying out Android on HD2 couple of days ago.
Might backup my data.img and give this method a go.
This is awesome!
Please can chefs cook this into their builds....
My biggest problem (other than no USB and no bluetooth) is this space limitation.
Well done you!
GG
info moved to first post...
works beautifully!!!
Thank you
How would you fancy doing each version as testers for us, as some people on here dont use Linux?? and is there a way you can provide a screen shot showing the phone running android with more storage?
any changes to extend a used img. file?!
also sofar my linux knowing is this command:
dd if=/dev/zero bs=1M count=256 >> data.img
just writes zeros to the end of the data.img...
shouldn't this work with a used file too?
another idea (can't try because mac osx didn know the resize2fs commands..)
dd if=/blabla/data.img bs=1M count=512 > data_new.img ?!
so it just copies the hole data.img in a new file ...
holy COW great work you clever little bunny lol, maybe you should message the devs see if they wanna add this to there work
futureshock said:
dd if=/dev/zero bs=1M count=256 >> data.img
just writes zeros to the end of the data.img...
shouldn't this work with a used file too?
Click to expand...
Click to collapse
I was thinking that too...
I tried it at least 3 times, but Android still displayed 0.00 MB free memory (heh heh, i know )
Maybe because the system registers the size of the mount after the initial boot and never bothers checking it?!?
any change to extend the img inside android?!
maybe there are also the commands built in the linux kernel?
futureshock said:
any change to extend the img inside android?!
maybe there are also the commands built in the linux kernel?
Click to expand...
Click to collapse
I doubt it since the file is mounted and no longer appears as a .img file to the system
But a good idea nonetheless. If it were possible, I would be kicking myself for missing this!
was just thinking will it still work for us that dont use an 8gig card??? because thats what you have will it be looking for 8gig or is it just gonna use a gig from any card??
Demon_man said:
was just thinking will it still work for us that dont use an 8gig card??? because thats what you have will it be looking for 8gig or is it just gonna use a gig from any card??
Click to expand...
Click to collapse
I don't think so.
You will need at least a 2GB card if you want to use the .img file I posted (since the file itself takes up 1GB)
If you want, I could also make a 512MB one!
Kev007 said:
I doubt it since the file is mounted and no longer appears as a .img file to the system
But a good idea nonetheless. If it were possible, I would be kicking myself for missing this!
Click to expand...
Click to collapse
ok... no resize2fs in linux kernel... tried it ...
maybe it could be built in while running.. .but this is far beyond my knowledge...
i tried all now todo this on mac... but no changes to extend the ext2(3) FS... no tool found.. got it to mount but no way to resize...
for now i'm looking at a virt. linux machine... but didn't found something usable with vmtools installed to get directory sharing ...
futureshock said:
for now i'm looking at a virt. linux machine... but didn't found something usable with vmtools installed to get directory sharing ...
Click to expand...
Click to collapse
You could use a Ubuntu Live CD, it boots Linux and lets you use it without installing anything
but why the had work when I've just uploaded the file you've been trying to create?
still on desire v5
and i want to keep my files!
futureshock said:
still on desire v5
and i want to keep my files!
Click to expand...
Click to collapse
since you said you could mount it, why not copy and paste your files into the data.img for desire v5
I can't guarantee that it'll work...but it's worth the try. amirite?
Kev007 said:
since you said you could mount it, why not copy and paste your files into the data.img for desire v5 (which i'm about to upload)
I can't guarantee that it'll work...but it's worth the try. amirite?
Click to expand...
Click to collapse
uhm ;D good question at all...
will try this...
also just strugeling around with the ubuntu live cd ...
This is awesome, thanks!
I had a problem everytime I have used Android it has known I was on Virgin UK but when I use this updated image it thinks im on T-mobile
and if you want it here is a torrent for the update you made
Related
FlintFire_v1.0
Based on latest official stock firmware Android 2.2.2
FEATURES:
1)TJ Styles OC'd Kernel
2).Darktremor Apps2SD 2.7.5.3 beta 4(requires that you have ext2 or ext3 partition on your SD card; exact procedure to create one is described in installation procedure.)
3) Fully deodexed and zipalligned apps and framework.
4) Rooted.
5) Installed BusyBox with support for init.d scripts
6) Replaced stock boot animation with custom animation
8)Support for OpenVPN(not tested) and CIFS.
9)Removed some stock apps and updated Gapps.
8)Updated Documents to go and Maps to 5.9 with worldwide navigation.
9)Added a init.d script and tweaks to build.prop(Increased screen density and possible increase in net speed)
10)Repalced stock Launcher and File Manager.
11)Added the V6 SuperCharger Script(Just go to terminal and type: superc)
Firmware should also work with compatible devices such as: Cherry Mobile Superion, Commtiva Linx N700, Olivepad VT-100, Spice MI700, and Camangi FM600 but I don't have these devices, so I cannot verify. As always make a backup before installing any custom firmwares.
Requrements:
Clockworkmod Recovery from here
Installation:
1)Create a backup using Clockworkmod Recovery.
2)If you dont have a A2SD EXT2 partition follow the first part of the instructions from here
3)Download the ROM and store it in the root of your SD Card.
4)Reboot into recovery mode,wipe data and cache and install the ROM.
Migrate from stock or another build:
1)Make backup of your phone using Titanium Backup (select all user applications).
2)Copy all files and folders from SD card to local folder on your computer.
3)Install Clockwork Recovery Partition, create partition on SD card and install ROM as described in installation guide.
4)Copy all files and folders from local folder on your computer back to SD card.
5)Restore applications using Titanium Backup and reboot your phone.
Download:
Code:
http://dl.dropbox.com/u/21654931/FlintFire_v1.0.zip
Credits:
TJStyle for his OC'd kernel and kernel source.
hucqim80 for his recovery
dsixda for his kitchen
Darktremor for his excellent Apps2d
zeppelinrox for his V6_Supercharger
Brut.all for his hacked version of Google Maps
Screenshots:
{
"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"
}
Changelog:
v1.0
Initial Release
one question
hi
is ext4 ok as i have ext4 on my SD and is see u have mentioned that we need ext3
haree said:
hi
is ext4 ok as i have ext4 on my SD and is see u have mentioned that we need ext3
Click to expand...
Click to collapse
ext4 should work but you wont be able to backup your SD-EXT using clockworkmod recovery.
First backup your apps using titatinum backup,boot into recovery mode=>mounts and storage=>format sd-ext.This will format your partition to ext2.
then restart and restore your apps.
googlehome said:
ext4 should work but you wont be able to backup your SD-EXT using clockworkmod recovery.
First backup your apps using titatinum backup,boot into recovery mode=>mounts and storage=>format sd-ext.This will format your partition to ext2.
then restart and restore your apps.
Click to expand...
Click to collapse
hi
do i need to bakup my SD card to my PC before i do this as give below
First backup your apps using titatinum backup,boot into recovery mode=>mounts and storage=>format sd-ext.This will format your partition to ext2.
i just have a Ext4 done via CWM and as of now app2sd works im using amalgamations rom right now
what u have mentioned is a little new to me
haree said:
hi
i just have a Ext4 done via CWM and as of now app2sd works im using amalgamations rom right now
what u have mentioned is a little new to me
Click to expand...
Click to collapse
If you made your partition using CWM then it is ext2 and not ext4 .
Please check your partition type by connecting your device to your PC and opening a partition manager which recognizes ext partitions.you will see that your SD Card is split into 2 partitions
FAT32 and EXT2.(You dont need to check if you trust my word )
You can safely use my ROM because your are using EXT2 and not EXT4.
whaaat... 1512 in quadrant... impressive
googlehome said:
If you made your partition using CWM then it is ext2 and not ext4 .
Please check your partition type by connecting your device to your PC and opening a partition manager which recognizes ext partitions.you will see that your SD Card is split into 2 partitions
FAT32 and EXT2.(You dont need to check if you trust my word )
You can safely use my ROM because your are using EXT2 and not EXT4.
Click to expand...
Click to collapse
hi
1.i trust ur words 100% man
2.im lazy to do all that checking i do have ur rom downloaded ill use it and keep u posted
thanks buddy for ur kind reply
Edit : i tried ur rom and it was good.but as i need the original keyboard and could not get it to work on ur ROM i went back to
amalgamation 1.3 ROM thanks
Which languages are included?
Sent from my ViewPad7 using XDA App
GHome, tell me how to get 1500 in quadrant score
wazzzuuuup2 said:
GHome, tell me how to get 1500 in quadrant score
Click to expand...
Click to collapse
Convert your partion to EXT3.:
open terminal emulator and type:
>su
>a2sd convert-ext3
Use the data2sd feature:
>su
>a2sd datasd
No German language, only English, Vietnamese, ...?
Vcrone said:
No German language, only English, Vietnamese, ...?
Click to expand...
Click to collapse
dont ill include more languages in my next update
googlehome said:
Convert your partion to EXT3.:
open terminal emulator and type:
>su
>a2sd convert-ext3
Click to expand...
Click to collapse
After I did that my tablet rebooted and was unable to boot. Guess it's stupid to try to convert the ext2 partition when it is in use? Well how do I do it then?
googlehome said:
Convert your partion to EXT3.:
open terminal emulator and type:
>su
>a2sd convert-ext3
Use the data2sd feature:
>su
>a2sd datasd
Click to expand...
Click to collapse
it doesnt work... my quadrant score still stuck <1000 and even worst....
High quadrant score in the screen-shots is based on high CPU and high IO score so I would guess these tweaks would be highly dependent on sd card speed to get higher scores unless there is some swapping to ram going on to "fake" these IO speeds. I've read something about that while checking out data2sd > http://forum.xda-developers.com/showthread.php?t=852219
@googlehome: What brand and type of sd card are you using ? I'm very curious because I'm looking for the best one possible for our device.
Amalgation said:
High quadrant score in the screen-shots is based on high CPU and high IO score so I would guess these tweaks would be highly dependent on sd card speed to get higher scores unless there is some swapping to ram going on to "fake" these IO speeds. I've read something about that while checking out data2sd > http://forum.xda-developers.com/showthread.php?t=852219
@googlehome: What brand and type of sd card are you using ? I'm very curious because I'm looking for the best one possible for our device.
Click to expand...
Click to collapse
Im using a class 2 (not the best)16gb SD Card.You can create an ext3 partition with gparted from your PC.Im using ext3 currently
Thank you every much googlehome. Thank you. Thank you.
But i'm still can't play youtube HQ.
sorry for my weak english...
By the way, Wi-Fi is not working on my device with this ROM, just like it's not working with Amalgation's EUViewPad. It is, however, working with CleanViewPad ROM. I have HWVer 103.
Some of my impressions.
Wifi works on my Viewpad 7 HWV 1.03. Tle launcher is notably slower than the stock one. There is no email application and I don't know how to send and receive emails. It is not good as emails are very basic tablet function for me.
I am really courious how to "revive" icons from Dock "thrown" in the recycle bin?
Everything else is OK. One of my Quadrant scores was 1045.
hi guys here is BACKTRACK 5 on HTC Flyer
most of the work was done by anantshri, i have only modified it slightly so that it will works properly on HTC Flyer... dont forget to thank him!
i will try n keep it short and simple... this is running in chroot environment and doesnt boot as a separate OS... it can be accessed through shell or via a VNC client..
for more details u can read the original thread at X10 sub-forums...
[DEV] BACKTRACK 5 on Xperia X10 chroot
if u dont know what Backtrack is read this: http://bit.ly/z23em2
[ Screenshots ]
on startup (shell):
{
"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"
}
in GUI:
BT5 on tablet:
[ Requirements ]
rooted device
Some apps from Android Market:
Android Terminal Emulator
androidVNC
[optional] highly recomended keyboard: Hacker's Keyboard
7zip (for PC), for extracting the files
around 3.3 GB free on external sdcard (/sdcard/ext_sd/)
[ How To : File Setup ]
u need to do this only once
download the files from the links provided in this thread
extract the files using 7zip to a temporary folder (needs 3.3GB free on that drive)
connect ur device to PC and mount USB storage
create a folder named 'bt' (without quotes) in the root of ur external sdcard and copy the bt.img in that folder
also place the file bt5_flyer_shell_scripts_v1.zip in root of sdcard, this file has to be flashed via recovery
once u verify that the above is correct then un-mount usb storage
reboot into recovery and flash the file bt5_flyer_shell_scripts_v1.zip stored in root of sdcard
once ur phone reboots into OS just check the /sdcard/ext_sd/bt folder
final directory structure should look like this:
/sdcard/ext_sd/bt/bt
/sdcard/ext_sd/bt/bt.img
/sdcard/ext_sd/bt/installbt.sh
/sdcard/ext_sd/bt/startbt
/sdcard/ext_sd/bt/stopbt
once u verify that the above is correct then u can proceed
[ How To : Launch BT ]
start Terminal Emulator app on ur device and enter the following commands step by step (accept/allow any SuperUser request/popup that u may receive)
su
cd /sdcard/ext_sd/bt
sh installbt.sh
startbt
bt
now u are in BackTrack5 shell
to launch GUI (vncserver) enter the following command
ui
now note the number N shown localhost:N
e.g. as u can see from the above image that "New 'X' desktop is localhost:1", so N=1
the vncserver is running at (5900 + N, N=1 ; so server port is 5901)
now launch androidVNC app on phone and fill in the detials as follows
Nick : bt
Address : 127.0.0.1
Port : 5901
Password : 12345678
Username : <leave it blank>
Color Format : 24-bit color (4 bpp)
inside vnc window select input mode (i personally recommend the following)
TouchPad (here your screen works like a big touchpad use it to navigate mouse.)
and then press connect... now u are in BackTrack GUI!
if u want to exit/close BT5 then u need to follow these steps:
close the androidVNC app (Menu -> Disconnect)
go back into Terminal Emulator app and enter the following commands
u should be at this shell [email protected]:~#
killui
exit
now u will get back to this shell> #
now enter the following commands to stop bt and exit
stopbt
exit
exit
u can now exit the Terminal Emulator app
i would also recommend that u reboot ur phone
[ Important Info ]
root password is 12345678
[ Download Links ]
update.zip package containing shell scripts, busybox (which gets installed to temporary location) [to be flashed via recovery]
this will not disturb/conflict with busybox of ur ROM/CF-Root kernel
bt5_flyer_shell_scripts_v1.zip (~800KB)
main bt.img
there are two sets of files... for those who dont have a very stable connection i have provided small 50MB (x 10) packages while for others who have a stable connection i have provided 250MB (x 2) packages... both contain the same file bt.img but for the convenience of users i have created these two sets... if u have already downloaded one set u do not need the other set...
KINDLY DO NOT MIRROR OUR FILES
SET 1
these links are 7zip archives split into 50mb files, u will need to download the following:
total size: 486MB
bt.7z.001 (50 MB)
bt.7z.002 (50 MB)
bt.7z.003 (50 MB)
bt.7z.004 (50 MB)
bt.7z.005 (50 MB)
bt.7z.006 (50 MB)
bt.7z.007 (50 MB)
bt.7z.008 (50 MB)
bt.7z.009 (50 MB)
bt.7z.010 (36 MB)
md5 hashes:
Code:
bt.7z.001 f19e769bf42b44867c8bb1d9bb9c5d44
bt.7z.002 a4dd26a98d2c6925d871fb108fb5fadb
bt.7z.003 ecca5a5d72c449117b1d3dbc23aeb1a2
bt.7z.004 8ad487a01e4d149f0247ad9288201f32
bt.7z.005 adab9cb3778cd8ac89ccc0e21997c3d7
bt.7z.006 ba6a28de70a1115dc316f45cea508215
bt.7z.007 f59757e891631607e1a35abadb231b3b
bt.7z.008 cdb8c28a1fbd03657bb42e8d69f0600b
bt.7z.009 426d892f872679e3d53d0ebb0376e138
bt.7z.010 c7d2957bc65340d967b9dd3646d7cb39
i am also uploading a different set where-in the files are split into 250MB parts... but that upload is taking time
OR
SET 2
these links are 7zip archives split into 250mb files, u will need to download the following:
total size: 486MB
part1
part2
md5 hashes:
Code:
bt.7z.001 fea6299bfa1677bd344d478108d458b2
bt.7z.002 b3897170d1f05dd0fb812fd092411203
ENJOY!
reserved for later
Nice job! Will this also work on GB?
AidenM said:
Nice job! Will this also work on GB?
Click to expand...
Click to collapse
yups should work irrespective of android OS version
DooMLoRD said:
yups should work irrespective of android OS version
Click to expand...
Click to collapse
Cool beans trying it out now
I was just wishing someone would port Linux to the flyer the other day, and here it is, like magic. I'm glad we have you as a dev, you always seem to think outside the box. I'm kinda sad it came at the end of my break, but I will definitely be giving this a try next time I have some spare time. Thanks!
Sent from my mobile typewriter with tapatalk
thx
Works fine on GB flyer
Very Nice........
First, I would like to show me appreciation for this nice piece of art!
Second, would it be ok if I copied the script files manually on me rooted device instead of flashing it ?
Thanks again.........
jaguaralani said:
Very Nice........
First, I would like to show me appreciation for this nice piece of art!
Second, would it be ok if I copied the script files manually on me rooted device instead of flashing it ?
Thanks again.........
Click to expand...
Click to collapse
I recommend that u should flash them via recovery...
Sent from my HTC Flyer P510e using XDA App
So, I can't open the second part of the two 250mg files. It tells me it can't be opened as an archive. The first part works.
devator22 said:
So, I can't open the second part of the two 250mg files. It tells me it can't be opened as an archive. The first part works.
Click to expand...
Click to collapse
Bump?
Sent from my mobile typewriter with tapatalk
devator22 said:
Bump?
Sent from my mobile typewriter with tapatalk
Click to expand...
Click to collapse
second part cant be seperately opened...
open the first file and it will open all further parts
DooMLoRD said:
second part cant be seperately opened...
open the first file and it will open all further parts
Click to expand...
Click to collapse
Oh, okay. Thanks for the answer, I was about ready to give up.
Sent from my mobile typewriter with tapatalk
Thanks a lot! I've edited the scripts a bit and managed to run this from internal sd card (my ext_sd is just 2GB). It's all working fine, when I'll get home from work I will try to find out how usefull this can be
PS: Never thrust a bit.ly link, it's almost always a lmgtfy link
Thanks for all the info I got everything setup and working. Can we put the wifi into monitor mode? Not really sure where to go from here. Thanks.
cmantis said:
Thanks for all the info I got everything setup and working. Can we put the wifi into monitor mode? Not really sure where to go from here. Thanks.
Click to expand...
Click to collapse
Nope, no driver support.
It's in the kernel
barry99705 said:
Nope, no driver support.
Click to expand...
Click to collapse
The AOSP kernel is currently dev'ing, and monitor mode is possible for the View/Flyer as they use a very common chip (Broadcomm 5823) The information for this chip is on xda, but I don't have time to search it, will edit later.
how i can use virtual/hacker keyboard with GB? i got an empty bar in GB when in HC is fixed. how i can keyboard appear? send text function is a bit annoying
Anything new about the monitor mode???
doctorlirio said:
Anything new about the monitor mode???
Click to expand...
Click to collapse
Does HDMI output not work wheil runing BT5?
Hi Guys,
I have successfully unpack, edit init.rc & repack but it doesn't boot !
The way to unpack MTK series was actually found by the guys at mobileuncle over a year ago ! I've subscribe to their forum but no reply...
Below is the translated version.
PHP:
MTK boot is different from the other android system. To extract, delete the
first 512 bytes of data, using Winhex. Find the location 800 to 9F0, delete it
& save it. Then you can unpack using the command below.
split_bootimg.pl boot.img
split_bootimg.pl boot.img
Page size: 2048 (0x00000800)
Kernel size: 1388548 (0x00153004)
Ramdisk size: 141518 (0x000228ce)
Second size: 0 (0x00000000)
Board the name:
Command line: no_console_suspend = 1
Writing as boot.img, the kernel ... the complete.
Writing as boot.img, ramdisk.gz ... the complete.
Unpack the ramdisk command as follows:
mkdir ramdisk
% cd ramdisk
% gzip -dc ../boot.img-ramdisk.gz | cpio -i
% cd ..
Any help is greatly appreciated !
--------------------------------------
Added on Oct 17, 2012 WARNING : MEDIATEK SMART PHONE FLASH TOOL
i've seen far too many times that fellow xda member make this same mistake over & over again, including myself...
{
"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"
}
So pls pls people, don't use SP Flash Tool & download ROM not meant for your phone, it will brick it & there is no way to revive it back ! After you have download wrong PRELOADER, your phone will be completely dead, cannot power on, no charging, no recovery, no USB vcom detection & you can say
to it...
Here is the WARNING again :
NEVER DOWNLOAD ROM NOT MEANT FOR YOUR PHONE. IT WILL BRICK IT !
yuweng said:
Hi Guys,
I have successfully unpack, edit init.rc & repack but it doesn't boot !
The way to unpack MTK series was actually found by the guys at mobileuncle over a year ago ! I've subscribe to their forum but no reply...
Below is the translated version.
PHP:
MTK boot is different from the other android system. To extract, delete the
first 512 bytes of data, using Winhex. Find the location 800 to 9F0, delete it
& save it. Then you can unpack using the command below.
split_bootimg.pl boot.img
split_bootimg.pl boot.img
Page size: 2048 (0x00000800)
Kernel size: 1388548 (0x00153004)
Ramdisk size: 141518 (0x000228ce)
Second size: 0 (0x00000000)
Board the name:
Command line: no_console_suspend = 1
Writing as boot.img, the kernel ... the complete.
Writing as boot.img, ramdisk.gz ... the complete.
Unpack the ramdisk command as follows:
mkdir ramdisk
% cd ramdisk
% gzip -dc ../boot.img-ramdisk.gz | cpio -i
% cd ..
Any help is greatly appreciated !
Click to expand...
Click to collapse
hey yuweng thanks a lot !! you have given me a clue on how to unpack boot.img on MTK65xx.........can you post that mobile uncle website link for extracting boot.img for our phones ?? Thanks in advance !!
I'll be with you all the way it we reach success of flashing the modified boot.img !!!
Please reply !!
Hello balamu96m,
You can download the tools from Dark Tremor's site & refer to the How-to. There is no tools listed at mobileuncle thread there however all tools can be found here at XDA & one of them is this
In fact, there are quite alot of how-to posted here at XDA, all you have to do is search for the correct key word.
Update, been trying for about a month now & it turns out MT65xx doesn't support ext2 partition; thats why my phone went into boot loop ! Bruno Martins has given me some tips, so have to learn how to port ext2.ko
What platform are you using, Windows (Cygwin) / Linux / Mac OS X ? Another great way to start is using this tool
Ciao...
Hey yuweng,
thanks for the reply !! But first of all, what is the size of the 'boot.img' of your MTK mobile and also what is the normal size of a boot.img ?
I'm asking this because my 'boot.img' is 6.00 MB !! I removed the header and also completed splitting the 'no_header' file into kernel and ramdisk.gz. After splitting, the size of ramdisk.gz is around 2.9 MB. When i g-unzip ramdisk.gz, it says that unzip is complete and also says that it removed some bad sectors of that file. The remaining that i get is only 590 K.
So when i complete repacking into boot.img, its size becomes 2.9 MB.
Did i commit any mistake ??
Please help me !!
Did you successfully unpack and repack it ??
I mainly use Cygwin and also have Ubuntu.
Please reply !!
Hi bala,
Opps, i didn't select 'receive email notification of new replies'; sorry for the late response...
As for your question, that is normal. If you open up your Hex Editor, you will notice whole lot of FF after the offset 002937F0; that is what taking up the spaces.
7-zip your boot.img & upload so that i can compare it & see what are the differences with mine !
Rgds,
Same problem here dude!! Didn't use email notifications!
okay......here is link 4 my 'boot.img' : http://www.mediafire.com/?giq9c384eshvhq7
hope get a solution soon !
thanks in advance !!!!!
Hey guys, I have decided to make my MT65xx unpack / repack scripts public. You can find the thread here.
Any question, feel free to ask, but please use that thread.
Dear Bruno,
Thank you so much for sharing your unpack/ repack scripts. You have open up a whole new world of possibility for our MT65xx android smartphone
Particularly for MT6573, with casacristo's ext2.ko, we can now port DT_a2sd, Ad2sdx, Data2ext & much much more...
Once again, thank you, Master ShiFu Bruno & Master ShiFu casacristo ...
As mention by Bruno, please use his newly started thread for questions & answers on how to use it...
Did u try ur hands on other scripts?
Sent from my Android using Tapatalk 2
Hello ckethan,
Can you be more specific ?
Anyway, talking about scripts, i've tried DT_a2sd, its amazing ! i've just push it to the max with over 200 games + apps; on a max of 2GB ext2 partition !
There is another amazing scripts, the Super Charger V6
Go ahead & tried it...
Kudos to the developers...
Ciao...
Wow can u help me set this script ?
And how is the speed of dt_a2sd compared to ad2sdx?
Sent from my Android using Tapatalk 2
i've only tried DT_a2sd so far, it worked the first time upon setup ! As for the others, i'm having trouble with it...so i can't comment on the speed...
However, one thing i can confirm is to use the fastest possible micro sd. i'm using sandisk mobile ultra & its superb compare to my old 16GB Class 2. Can't wait for the new samsung UHS-1 which claim 80MB/s transfer rate...
As for maximum space saving, DT_a2sd is still the best, it moves everything to the sd-ext with the command 'a2sd cachesd' & your internal memory will increase back to default, like no apps has been installed to your phone !
Upload your boot.img & i'll take a look at it, pls make sure it is MT6573 with kernel 2.6.35.7 or else i can't help you much...
I have the boot.img edited for ext2 and all .. what class n card do u recommend?
Sent from my Android using Tapatalk 2
i have attached mine boot.img,recovery.img
mine kernel is 2.6.35.7
and board is mtk6573
hello bindassdost,
Pls check ur pm & reply...
yuweng said:
Upload your boot.img & i'll take a look at it, pls make sure it is MT6573 with kernel 2.6.35.7 or else i can't help you much...
Click to expand...
Click to collapse
Yuweng bro,
For mtk6516 running 2.2, we don't need to make any changes in the boot.img also don't need ext2.ko.....is this true??
I am asking because, only in gingerbread, init.rc must be modded to run init.d scripts at boot (i believe!!).....
Thanks in advance!!
yeoh macha bala bro...,
been busy with field work; AFAIK, DT_a2sd uses ext2,3 or 4 to 'trick' android thinking that the ext partition is internal memory...
branded froyo android phone, most do support ext partition, thats why they can use DT_a2sd...on top of that, they don't need to mod init.rc because its already there...they also have native android apps2sd on later build...
As for MT6516, AFAIK, there is no ext2,3,4.ko exist so DT_a2sd will not work on it and its CPU is slow...but you can always try with casacristo's ext2.ko & see if it works... ( i don't have a MT6516 phone so i can't test it out )
Ciao...
yuweng said:
yeoh macha bala bro...,
been busy with field work; AFAIK, DT_a2sd uses ext2,3 or 4 to 'trick' android thinking that the ext partition is internal memory...
branded froyo android phone, most do support ext partition, thats why they can use DT_a2sd...on top of that, they don't need to mod init.rc because its already there...they also have native android apps2sd on later build...
As for MT6516, AFAIK, there is no ext2,3,4.ko exist so DT_a2sd will not work on it and its CPU is slow...but you can always try with casacristo's ext2.ko & see if it works... ( i don't have a MT6516 phone so i can't test it out )
Ciao...
Click to expand...
Click to collapse
Thanks for the reply bro!! I'll try it and tell you!!!
yuweng said:
Hi Guys,
I have successfully unpack, edit init.rc & repack but it doesn't boot !
The way to unpack MTK series was actually found by the guys at mobileuncle over a year ago ! I've subscribe to their forum but no reply...
Below is the translated version.
PHP:
MTK boot is different from the other android system. To extract, delete the
first 512 bytes of data, using Winhex. Find the location 800 to 9F0, delete it
& save it. Then you can unpack using the command below.
split_bootimg.pl boot.img
split_bootimg.pl boot.img
Page size: 2048 (0x00000800)
Kernel size: 1388548 (0x00153004)
Ramdisk size: 141518 (0x000228ce)
Second size: 0 (0x00000000)
Board the name:
Command line: no_console_suspend = 1
Writing as boot.img, the kernel ... the complete.
Writing as boot.img, ramdisk.gz ... the complete.
Unpack the ramdisk command as follows:
mkdir ramdisk
% cd ramdisk
% gzip -dc ../boot.img-ramdisk.gz | cpio -i
% cd ..
Any help is greatly appreciated !
Click to expand...
Click to collapse
As a newbie,finally I found a place where I can reply.I have been reading your thread but I cannot view the pdf instructions hosted on mediafire,due to GFW or some thing.Can you please send me the material in below thread by email.
http://forum.xda-developers.com/showthread.php?t=1923764
I think it might be the hope for me to root my MTK 6573 based Motorola XT390.
Thank you so much.
mediafire & myself is located outside of the GFW so nothing is block...
i presume its ur browser problem where i purposely use this feature for fellow xda member to 'view' it first & when they find it useful then just remove the view/ from the link & it will bring you to the download page...
That tut i made is specifically for MT6575/ 77 & a few of the steps are totally different so you can't use it...
However, i've updated the tut & attach it here just for you...
it has a mix response so hopefully it does work for you... :fingers-crossed:
And pls read the WARNING at the first post...
In fact, i have updated all my thread with that warning so hopefully nobody make that same mistake ever again...
{
"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"
}
Please OP remove my old post about Ubuntu on Tab 3...
T3buntu (Had to call it something...)
Disclaimer:
What you do with this information is up to you. If your device breaks while trying anything in here you do that at your own risc.
I cant be held responsible for anything that happens to your device.
Everything in here was tested on a Samsung Galaxy Tab3 10.1(5210) if you try anything in here on any other device thats up to you.
Most of the work is made by the Linux on Android team i have just tested and fixed some stuff.
The image is ext2, x86 but im working on a ext4, AMD64 image.
”Changelog”
1. Replaced lxde with KDE Plasma
2. Added entryś in etc/fstab for int/ext SdCards
3. Edited bootscript from the Linux on Android team so that the SdCards in the Tab is correcly mounted and works with fstab.
4. Installed "missing" packages to minimize errors.
Works:
Wifi
Battery indicator
Int/Ext SdCard
Most of the stuff in Ubuntu.
Issues:
Leftpanel is black
Slow startup, but can be fixed. I will add that later.
Some apps dont work if you start them as root.
Couldnt make jpg work as wallpaper so using png at the moment.
Rotation isnt setup since we cant use xrandr to rotate the screen..
Not tested:
GPS
ToDo
Streamline startup
Add init.d support on the Tab
Tweaking were ever possible.
Fix sound
Now for the fun stuff.
Installation:
1. Root your device. I used this Guide.
2. Install Busybox.
3. Install Linux on Android.
4. Install a VNC client of your shoice, i preferr Jump Desktop free.
5. Copy bootscript.sh to /data/data/com.zpwebsites.linuxonandroid/files/ overwrite the old file.
6. Unpack and Copy the t3buntuv1.2_20131216.img to a place of your choosing on either internal or external sdcard.
7. Make a Linux on Android widget and point it to the img file you copied in 6.
OBS !! This image is preconfigured with the user ubuntu and psw t3buntu..
8. Now click on the LOA widget you made in 7 and let linux ”bootup”
9. In your VNC client connect to localhost.
DONE ! Your now in Ubuntu..
If you want more screenspace you can uncomment
# service call activity 42 s16 com.android.systemui
In bootscript.sh this will remove the android panel. The problem with this at the moment is that to
get it back you have to restart the Tab becourse the ´am´ command to get it back ”Seg faults” on
my tab and i havnt figured out why yet.
Consider this image as alpha...
OBS !! The image file is BIG 1.4GB compressed and 4GB decompressed. Will try and make it smaller not sure how the Linux on Android team made there images so small...
LINK to imagefile
LINK to bootscript
Credits
Linux on Android team
The one that made the scripts from the start. Not sure who made them...
How about a link to get 3. Linux on Android.
I know I'm top lazy to Google.
Sent from my GT-P5210 using XDA Premium HD app
Awesome! Glad to see something! And having Ubuntu is a very cool os to have! Good work and thank you!
Sent from my SCH-I605 using xda app-developers app
Added links to Linux on Android and Busybox in first post.
Nice, but there are a few things...
The bootscript.sh contains one little, but crucial error.
At line 172, character 44, you forgot one space, which makes the mount procedure unusable:
Code:
$bbox mount -o bind /storage/extSdCard $mnt/extSdCard
Which should be:
Code:
$bbox mount -o bind /storage/extSdCard $mnt/extSdCard
Without this (for me) it failes while it's starting up.
And, another thing, my tablet reboots at the moment I have to run VNC to start the X server, even though I'm not doing or touching anything.
After reboot it doesn't start up t3buntu either.
But, very good work !!
And yes, I do have Samsung Galaxy Tab 3 10.1 GT-P5210...
RubenStauttener;48606882]Nice, but there are a few things...
The bootscript.sh contains one little, but crucial error.
At line 172, character 44, you forgot one space, which makes the mount procedure unusable:
Code:
$bbox mount -o bind /storage/extSdCard $mnt/extSdCard
Which should be:
Code:
$bbox mount -o bind /storage/extSdCard $mnt/extSdCard
Without this (for me) it failes while it's starting up.
Havnt noticed any problems here but i have added the space and updated the script since both versions works for me.
And, another thing, my tablet reboots at the moment I have to run VNC to start the X server, even though I'm not doing or touching anything.
After reboot it doesn't start up t3buntu either.
Does it reboot during script execution ? It do sound like a mem issue. Do you have widgets and such running in android ?
You can try with enabling the swapfile in bootscript.sh .
But, very good work !!
And yes, I do have Samsung Galaxy Tab 3 10.1 GT-P5210...
I've got the terminal up and running fine. But I can't VNC into it. What settings are you using for you VNC viewer?
How about native graphic support using libhybris? Or since this device use PowerVR SGX 544, is native X11 possible? Reference: https://wiki.archlinux.org/index.php/Intel_GMA3600
EDIT: https://github.com/trevd/android_kernel_samsung_santos10/tree/cm-10.2/drivers/staging/mrst/pvr and https://github.com/thomas001/cedarview-drm/tree/master/staging/cdv/pvr looks similar
Thanks for sharing but it's not working
VNC: autentification failed !
Jump Desktop: It ask a password, and I don't have this password !
Sent from Gallifrey using TARDIS
Nonta72 said:
Thanks for sharing but it's not working
VNC: autentification failed !
Jump Desktop: It ask a password, and I don't have this password !
Sent from Gallifrey using TARDIS
Click to expand...
Click to collapse
Test password: ubuntu
When run script say mnt error =/
zorrigas said:
Test password: ubuntu
When run script say mnt error =/
Click to expand...
Click to collapse
Thanks, but I already solved it :good:
Sent from my GT-5210 powered by AmatROM HD
Hi, I posted a question in the Q&A forum (them 10 posts), but I guess it really belongs here.
Tried this on my TWRP rooted UANB4 stock rom P5210, stock kernel. And I get the following with your script and image:
Code:
[email protected]:/ $
[email protected]:/ $ cd /storage/extSdCard/Img
[email protected]:/storage/extSdCard/Img $ su
[email protected]:/storage/extSdCard/Img # sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /storage/extSdCard/Img/t3buntuv1.2_20131216.img
Checking loop device... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Invalid argument
Error: Unable to mount the loop device!
1|[email protected]:/storage/extSdCard/Img #
Line : $bbox mount -t ext2 /dev/block/loop255 $mnt
Do I tell busybox to overwrite the mount command?
Otherwise, excellent work, cant wait till I have it running.
*EDIT*
Turns out I just had to copy the image again, I guess my first transfer got cut off.
Totally works, thx
hey. i noticed that the last update was in April of 2014. i was wondering if there was any updates on this.
getting linux on my tablit was the #1 reason i chose to root my GT-P5210 in the first place.
Homage said:
hey. i noticed that the last update was in April of 2014. i was wondering if there was any updates on this.
getting linux on my tablit was the #1 reason i chose to root my GT-P5210 in the first place.
Click to expand...
Click to collapse
I did not try this one. I bet itworks in VNC as it tell us. Instead i did
http://forum.xda-developers.com/showpost.php?p=58175673&postcount=54
I guess I can say it work aceptable in VNC mode, definitly work nice in comand mode. I been working in a native solution but it is a hard bone for my teeth. Look in the general area.
Download link is down
I would like to run Ubuntu on my Tab 3 but the link doesn't work. Could some upload a working link please?
Hi Guys,
Anyona has this .sh script and the t3buntuv1.2_20131216.img file? if you send me im hosting and distributing free as i live i want to use for my home automatization.
THX
G
jorgen_gustavsson said:
Please OP remove my old post about Ubuntu on Tab 3...
T3buntu (Had to call it something...)
Disclaimer:
What you do with this information is up to you. If your device breaks while trying anything in here you do that at your own risc.
I cant be held responsible for anything that happens to your device.
Everything in here was tested on a Samsung Galaxy Tab3 10.1(5210) if you try anything in here on any other device thats up to you.
Most of the work is made by the Linux on Android team i have just tested and fixed some stuff.
The image is ext2, x86 but im working on a ext4, AMD64 image.
”Changelog”
1. Replaced lxde with KDE Plasma
2. Added entryś in etc/fstab for int/ext SdCards
3. Edited bootscript from the Linux on Android team so that the SdCards in the Tab is correcly mounted and works with fstab.
4. Installed "missing" packages to minimize errors.
Works:
Wifi
Battery indicator
Int/Ext SdCard
Most of the stuff in Ubuntu.
Issues:
Leftpanel is black
Slow startup, but can be fixed. I will add that later.
Some apps dont work if you start them as root.
Couldnt make jpg work as wallpaper so using png at the moment.
Rotation isnt setup since we cant use xrandr to rotate the screen..
Not tested:
GPS
ToDo
Streamline startup
Add init.d support on the Tab
Tweaking were ever possible.
Fix sound
Now for the fun stuff.
Installation:
1. Root your device. I used this Guide.
2. Install Busybox.
3. Install Linux on Android.
4. Install a VNC client of your choice, i preferr Jump Desktop free.
5. Copy bootscript.sh to /data/data/com.zpwebsites.linuxonandroid/files/ overwrite the old file.
6. Unpack and Copy the t3buntuv1.2_20131216.img to a place of your choosing on either internal or external sdcard.
7. Make a Linux on Android widget and point it to the img file you copied in 6.
OBS !! This image is preconfigured with the user ubuntu and psw t3buntu..
8. Now click on the LOA widget you made in 7 and let linux ”bootup”
9. In your VNC client connect to localhost.
DONE ! Your now in Ubuntu..
If you want more screenspace you can uncomment
# service call activity 42 s16 com.android.systemui
In bootscript.sh this will remove the android panel. The problem with this at the moment is that to
get it back you have to restart the Tab becourse the ´am´ command to get it back ”Seg faults” on
my tab and i havnt figured out why yet.
Consider this image as alpha...
OBS !! The image file is BIG 1.4GB compressed and 4GB decompressed. Will try and make it smaller not sure how the Linux on Android team made there images so small...
LINK to imagefile <===== this URL broken
LINK to bootscript <===== this URL broken
Credits
Linux on Android team
The one that made the scripts from the start. Not sure who made them...
Click to expand...
Click to collapse
OS2SD for any rom
As I see there is many P500 users interested to put their ROM to sd card, so I'm providing this tutorial how to make any rom bootable from sd.
Requirements:
Linux or cygwin for Windows
Boot.img tools
Modified updater-script
Modified fstab
Correctly partitioned sdcard (Guide)
TWRP-OS2SD or TWRP-MULTI
Steps:
Replace updater-script in your's ROM zip with provided. It will probably work with all kitkat based roms. If not the idea is mounting /system on sd card so change all "mount("yaffs2", "MTD", "system", "/system");" lines with "mount("ext4", "EMMC", "/dev/block/mmcblk0p2", "/system");" in original updater-script
Extract bootimg-tools.zip and paste boot.img from your rom in same foder
Open terminal or cygwin, locate folder with boot.img tools and type "./extractboot boot.img"
This will create out folder. Replace fstab.p500 and init.qcom.rc in out/ramdisk with provided (they might need rework on older roms)
In terminal type "./packboot"
Now rename boot_new.img to boot.img and pase it to rom zip
Flash rom zip with one of provided TWRP versions
should probably work back thru 4.0 but froyo/gingerbread init won't mount any sd partitions before boot is completed.
just curious, why this partition layout?
I used p2 for /data until wiping it by accident several times swapping my sd to a phone with pre-os2sd recovery.
of course, I've modded my own os2sd partition map several times now experimenting, and the order doesn't seem to matter.
and i was wondering, could you post your twrp modifications for internal/os2sd hybrid? i had one kinda working but it was glitchy.
I used this configuration to keep swap working if enabled, because default is p3. Also p4 for /data because it not used by anything else, so it's safe. I think you are right, order doesn't impact performance. Will send you config of twrp then be on pc.
Sent from my LG-P500 using xda premium
HardLight said:
I used this configuration to keep swap working if enabled, because default is p3. Also p4 for /data because it not used by anything else, so it's safe. I think you are right, order doesn't impact performance. Will send you config of twrp then be on pc.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I'm not seeing any other ROMs of this style floating around.
The only reason I didn't leave p3 for swap is that it wasn't being used yet when I started with the os2sd stuff. I tried sticking it on p2 (instead of the stubby sd-ext I had there to satisfy the odd this-or-that which demanded sd-ext,) and that worked ok, but I hadn't set sd-swap as a default in any builds.
since you're building similar stuff now, maybe I'll drift mine into your partition map in the interest of some sort of unification. and I'd like to match up the twrps, too.
especially if the sd-swap is working well on the p500.
everybody who's been dealing with my versions for any length of time now since it came out in February, is used to having to upgrade recovery and deal with incompatible backups from earlier releases anyway.
thanks for your contributions.
Thank You
HardLight said:
OS2SD for any rom
As I see there is many P500 users interested to put their ROM to sd card, so I'm providing this tutorial how to make any rom bootable from sd.
Requirements:
Linux or cygwin for Windows
Boot.img tools
Modified updater-script
Modified fstab
Correctly partitioned sdcard (Guide)
TWRP-OS2SD or TWRP-MULTI
Steps:
Replace updater-script in your's ROM zip with provided. It will probably work with all kitkat based roms. If not the idea is mounting /system on sd card so change all "mount("yaffs2", "MTD", "system", "/system");" lines with "mount("ext4", "EMMC", "/dev/block/mmcblk0p2", "/system");" in original updater-script
Extract bootimg-tools.zip and paste boot.img from your rom in same foder
Open terminal or cygwin, locate folder with boot.img tools and type "./extractboot boot.img"
This will create out folder. Replace fstab.p500 and init.qcom.rc in out/ramdisk with provided (they might need rework on older roms)
In terminal type "./packboot"
Now rename boot_new.img to boot.img and pase it to rom zip
Flash rom zip with one of provided TWRP versions
Click to expand...
Click to collapse
Thank You for posting the guide as requested. Awesome, now I will try to make some ROMs bootable in sdcard, and try them in my phone.
bigsupersquid said:
should probably work back thru 4.0 but froyo/gingerbread init won't mount any sd partitions before boot is completed.
Click to expand...
Click to collapse
i think that you are wrong
i have a gingerbread installed on SD (and kitkat CM11 by mukulsoni on internal)
i used Multirom manager 5.1 by arnab321 based on work by Tassadar
http://forum.xda-developers.com/showthread.php?t=1828151
HardLight: can you make this procedure work like the one in Multirom ?
it allows me to have GB and KitKat installed at the same time, both are bootebel using the same recovery and im only a boot away from moving from one to the oder
danielboro said:
i think that you are wrong
i have a gingerbread installed on SD (and kitkat CM11 by mukulsoni on internal)
i used Multirom manager 5.1 by arnab321 based on work by Tassadar
http://forum.xda-developers.com/showthread.php?t=1828151
HardLight: can you make this procedure work like the one in Multirom ?
it allows me to have GB and KitKat installed at the same time, both are bootebel using the same recovery and im only a boot away from moving from one to the oder
Click to expand...
Click to collapse
multirom has preinit of its own, runs before GB init, and uses busybox to mount sd folders. It also mods init.rc to not mount the MTD partitions.
it would have to be recoded because, among other things, init.rc doesn't mount the filesystems anymore, it's moved to init.qcom.rc or init.device.rc (init.p500.rc or init.thunderc.rc in the current OS2SD versions.)
to use OS2SD like multirom, it would have to bind-mount folders or filesystem images from the card instead of mounting partitions directly, unless android can 'see' more than 4 card partitions now. It used to be limited to 4 back in GB.
Plus unless kexec is working every OS installed has to work with the kernel in the boot.img for tasssadar's original code (the app you're using is reflashing a new boot.img every time you change OS's, which will eventually trash your boot NAND memory,)
bigsupersquid said:
multirom has preinit of its own, runs before GB init, and uses busybox to mount sd folders. It also mods init.rc to not mount the MTD partitions.
it would have to be recoded because, among other things, init.rc doesn't mount the filesystems anymore, it's moved to init.qcom.rc or init.device.rc (init.p500.rc or init.thunderc.rc in the current OS2SD versions.)
to use OS2SD like multirom, it would have to bind-mount folders or filesystem images from the card instead of mounting partitions directly, unless android can 'see' more than 4 card partitions now. It used to be limited to 4 back in GB.
Plus unless kexec is working every OS installed has to work with the kernel in the boot.img for tasssadar's original code (the app you're using is reflashing a new boot.img every time you change OS's, which will eventually trash your boot NAND memory,)
Click to expand...
Click to collapse
ill start at the end
flashing boot is no worse then flashing a new rom but its less work and less time
i like GB for the speed and batt use but from time to time i need to run ting that wont work on GB(at list not on the 1 i chose after trying ~12 rom`s)
having kitkat installed and using multirom to change is faster
so, any chance of implementing the bind-mount option?
prite please
:fingers-crossed:
danielboro said:
ill start at the end
flashing boot is no worse then flashing a new rom but its less work and less time
i like GB for the speed and batt use but from time to time i need to run ting that wont work on GB(at list not on the 1 i chose after trying ~12 rom`s)
having kitkat installed and using multirom to change is faster
so, any chance of implementing the bind-mount option?
prite please
:fingers-crossed:
Click to expand...
Click to collapse
Just install your GB rom to internal memory and cm11 OS2SD to sd card, then make two flashable zips (or backups) of both roms boot.img and flash them respectively to rom you want to boot. Just keep in mind that GB won't be able to use sd-ext, because it's os2sd system partition.
Sent from my LG-P500 using xda premium
HardLight said:
Just keep in mind that GB won't be able to use sd-ext,
Click to expand...
Click to collapse
this is way i was hoping for the mount-bind
at the moment GB is on P2, swap on P3 and kitkat uses P4 as /sd-ext
i have some limited knowledge, ill try to see if i can do something wen ill have the time
any pointer on how i can use mount-bind ?
all the work on developing the p500 helps extend it life
thanks
p.s.
what is the MULTI in TWRP-MULTI?
danielboro said:
this is way i was hoping for the mount-bind
at the moment GB is on P2, swap on P3 and kitkat uses P4 as /sd-ext
i have some limited knowledge, ill try to see if i can do something wen ill have the time
any pointer on how i can use mount-bind ?
all the work on developing the p500 helps extend it life
thanks
p.s.
what is the MULTI in TWRP-MULTI?
Click to expand...
Click to collapse
the multi can flash os2sd & normal rom, so you have not to change between recoveries
ThAnKs
Thanks alot for this guide.....
have anyone tried it on an ICS rom ?
getting this error using cygwin
{
"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"
}
maybe it doesnt work with cygwin , i am trying to make genetICS 9.1.6 OS2SD compatible ..
nomancoolboy said:
getting this error using cygwin
maybe it doesnt work with cygwin , i am trying to make genetICS 9.1.6 OS2SD compatible ..
Click to expand...
Click to collapse
For starters , you need Perl installed for that script.
Second, ics don't use fstab, you'll have to change init.rc
And maybe even recompile init with a delay inside, like on GB.
otherwise init may not mount the card partitions.
The easy way to run ICS from card is tasssadar's multirom. You can find the thread buried in this forum.
I'm using HardLight's GenetICS 9.1.7 with the OS2SD mod. It's the most stable and smoothest with long battery life and 1.5GB in the data partition for my apps. Also successfully made it with Hephappy's ICS Plus simply modifying the updater-script inside the zip and search the mounting points in the 'init.rc' and 'init.qcom.rc', then just have to modify the lines following the first post.
Greetings from Costa Rica!
Enviado desde mi LG-P500 usando Tapatalk
@HardLight
This is twrp-multi, renamed to boot.img. I have previously extracted recovery images this way using apktool.
[email protected]:~/bootimg-tools$ ./extractboot boot.img
Page size: 2048 (0x00000800)
Kernel size: 2803424 (0x002ac6e0)
Ramdisk size: 2294087 (0x00230147)
Second size: 0 (0x00000000)
Board name:
Command line: mem=471M console=ttyMSM2,115200n8 androidboot.hardware=p500 no_console_suspend
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
gzip: ../../boot.img-ramdisk.gz: not in gzip format
cpio: premature end of archive
Any other tools needed to make this work? (ubuntu 14.04)
manu3193 said:
I'm using HardLight's GenetICS 9.1.7 with the OS2SD mod. It's the most stable and smoothest with long battery life and 1.5GB in the data partition for my apps. Also successfully made it with Hephappy's ICS Plus simply modifying the updater-script inside the zip and search the mounting points in the 'init.rc' and 'init.qcom.rc', then just have to modify the lines following the first post.
Greetings from Costa Rica!
Enviado desde mi LG-P500 usando Tapatalk
Click to expand...
Click to collapse
Can you share the modified files to be replaced in the rom.
hi all - thanks for these instructions. I tried to apply these to cm-9.1.5-GenetICS-Final-P500+gapps.zip and cm-9.1.7-GenetICS-HardLight-p500.zip.
In those roms I had to update the updater-script (I had to remove the format command otherwise the install would fail - but i figured that should be ok since the ext4 partition can be formatted externally - if i remember to do it).
I also updated the init.rc in the (mount mtd partitions section), but no updates to the init.qcom.rc
Each time I try to install a ROM, the device gets stuck at the LG boot logo.
I get the same problem with those zip's installing from TWRP MULTI's "Internal" mode. So I suspect something else is wrong...
interestingly, the only zip I can install successfully is the cm11.0.0-20160101-os2sd-ext4-p500.zip. Works like a charm, just dies in a matter of hours with Wifi on.
eldamobo said:
hi all - thanks for these instructions. I tried to apply these to cm-9.1.5-GenetICS-Final-P500+gapps.zip and cm-9.1.7-GenetICS-HardLight-p500.zip.
In those roms I had to update the updater-script (I had to remove the format command otherwise the install would fail - but i figured that should be ok since the ext4 partition can be formatted externally - if i remember to do it).
I also updated the init.rc in the (mount mtd partitions section), but no updates to the init.qcom.rc
Each time I try to install a ROM, the device gets stuck at the LG boot logo.
I get the same problem with those zip's installing from TWRP MULTI's "Internal" mode. So I suspect something else is wrong...
interestingly, the only zip I can install successfully is the cm11.0.0-20160101-os2sd-ext4-p500.zip. Works like a charm, just dies in a matter of hours with Wifi on.
Click to expand...
Click to collapse
roms not built for kernel swapped system/userdata (kitkat only built this way, and not older kitkat versions) will flash to the wrong partition and won't boot.
change your updater-script to switch system and userdata for older roms to flash correctly with the twrp-multi in internal mode.