Related
Hi all,
It is the stock XXJVK (Gingerbread) internet browser modified to open more than 4 windows.
Actually you can visit up to 16 different web site at the same time but you'll probably miss memory before
Note:
Once you reach the 8th windows, continue to press the "new button" and it will open an extra new window even thought that the counter will not display more than 8
For those who remain in froyo,see my thread for XWJS8:
[MOD] increased Stock XWJS8 browser limit
to install :
-copy the apk to your sdcard
-Delete the old Browser.apk in /system/app
-Place the new Browser.apk in there
Note:
Don't forget to be superuser and to mount the partition as read-write :
for stock kernel :
$su
#mount -o remount,rw /dev/block/system /system
#cp /sdcard/Browser.apk /system/app/Browser.apk
#exit
$exit
for CF-ROOT kernel, (thanks to ramad)
su
stop (phone will freeze, that's OK just move on)
busybox mount -o remount,rw /dev/block/system /system
cp /sdcard/Browser.apk /system/app/Browser.apk
exit
exit
adb reboot
Eric,
in Sri lanka.
Thanks, just what i have been looking for
Nice work thanks!
Sent from my GT-I9000 using XDA App
Thanks man. needed this. But for me the line with /dev/block/system i had to remove that. Then it worked.
Jobiza said:
Thanks man. needed this. But for me the line with /dev/block/system i had to remove that. Then it worked.
Click to expand...
Click to collapse
Hi,
Do you mean you did not use the whole line (mount....) ?
So , your /system partition could permanently be mounted as read write.
Are you using any tools or specific rom ?
Eric ,
in Sri Lanka.
will this going to work wirh jpx rom also ??
thx
Sent from my GT-I9000 using Tapatalk
claustrox said:
will this going to work wirh jpx rom also ??
thx
No I've tried gingerbread browsers on earlier roms before ... they don't work.
There are plenty of extra window modded browsers that do tho. The author of this thread made a js8 version I believe that will work
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Stock XXJVK, Voodoo GB hack Kernel, JVE GB Modem
thank you man !
can this also be done by using the root explorer app?
tried the adb method but it doesnt work for me
Have done it word for word like the method above for cf root but not working, phone does connect and reboot at the end but still have the 4 windows
Jobiza said:
Thanks man. needed this. But for me the line with /dev/block/system i had to remove that. Then it worked.
Click to expand...
Click to collapse
Had to do this to make it work
thanks
hey eric...thanks your exellent work....im also sri lankan.. keep it up bro......
I have a question is there the UserAgent hack in this one?
If not please add it to your version
Cool, good job man!
This is a new Gingerbread Sense rom Please make a nandroid backup before Flashing, just incase you don't like it, so you wont hate me.
http://www.multiupload.com/1KQA36UXS0 - V 2 Gingerbreadeddebain.ext2.zip
http://www.multiupload.com/FEO9PZLOCP - DEBIAN squeeze, working for your eris, web, and basic setup openoffice works on this, I uninstalled for space, but just about anything that works on a desktop works on this img. Follow instructions below.
Made for 3 partitions, Fat32, ext2, swap.
To use this rom correctly you must partition your sdcard as follows:
adb shell
parted /dev/block/mmcblk0
print
Click to expand...
Click to collapse
remove any partitions
Code:
rm1
rm2
rm3
rm4
rm5
Click to expand...
Click to collapse
now create new partitions these partitions should be as so, for sense or 2.1, or gingerbread roms fat32 ext2 swap file is the order, for froyo I believe it is swap ext2 fat32, but I have not tried a froyo rom yet.
16GB sdcard, change for your correct card amount
Code:
mkpartfs primary fat32 0 11500MB
mkpartfs primary ext2 11500MB 15500MB
mkpartfs primary linux-swap 152500MB 15900MB
Click to expand...
Click to collapse
CPU clocked at 748 mhz, any higher you will freeze your phone
WORKING
DEBIAN linux mount in terminal use pocketcloud free,or android-vnc to connect.
FLASH 10.1( WORKING )
make &recieve calls
camera video
market
sms
mms
gps
navigation
widgets
sensors
search
skins
scenes
voice
wi fi
friendstream
twitter
NOT WORKING
wi fi hotspot no drivers
softkey lights (with backlight version)
A few notes:
1. IF YOU HAVE ANY PERMISSION ERRORS i.e the camera not saving images to sdcard, you have to unmount your sdcard and remount it.
2. If you don't have an ext2 or a swap partition, everything will be ok, but if you do make sure they are in the correct order, because on boot the sdcard is mounted
3. there are a few custom commands in the terminal,
Code:
bash free, term, linux, nano, swapon, swapscriptv2, swap-off, swapon50, swapon60, swapon70, swapon80, swapon90, bootscriptv2, bootswap90,bootswap80,bootswap70, mountsd, umountsd, mountsd2pc, umountsd2pc, linuxloop
[QUOTE][COLOR=red]4. This rom first boot is close to 10 minutes, be patient it will pay off.[/COLOR][/QUOTE]
[QUOTE]To use bash it is a good idea to add this to the terminal emulator's initial command just below PATH
[CODE]su -c bash
[/QUOTE]
That sets the terminal up to use bash, this will allow you to use your tracball to scroll threw old commands.
3. To chroot into linux, it is very easy if you dont have the linux, To use this debian.img download the debain.img from above and push to sdcard. /sdcard/debain.img
busybox mount -o rw,remount /
mkdir /sdcard/debain
mount -o rw,loop -t ext2 /sdcard/debain.img /sdcard/debian
dd if=/sdcard/debain of=/mnt/linux
Click to expand...
Click to collapse
this will take some time several hours maybe. use a file manager to check your progress.
Once the copy is complete, than you can open the terminal and type
Code:
linux
this should put you into a localhost:#
once in local host type:
nano /etc/init.android/rc_enter.sh
Click to expand...
Click to collapse
now add this to the file
vncserver -kill :1
rm -r tmp
mkdir tmp
cd tmp
mkdir .X11-unix
cd ..
vncserver
Click to expand...
Click to collapse
To connect to vncserver use any vncserver app and use the following info:
username: localhost
password: android
host: localhost
port: 5901
Click to expand...
Click to collapse
the new debian.img is roughly 2.5 gigs so I would make enough room on your ext2 partition for 2.5 gigs at least, if you have any problems let me know
here is a link to an old thread of 2 versions of linux, NEITHER of these are the debian.img I have and am working on. these two are just incase you want to try to play around.
you will need to know a little about linux to get them running, but they will work. http://forum.xda-developers.com/showthread.php?t=823564
I forgot to add custom cpu settings, but it can stand up to 748mhz, that is what mine is clocked at.
Things that need fixing or tweaks wanted, please help as follows:
Download Apps2SD Free to use apps on sdcard, made by AZSoft Technology.
/system folder has only 13 megs after fresh install
currently I have a data/apps/ but data/apps is mounted as sdcard/data/apps
so the phone thinks data/apps is my external sdcard memory
would like to link a few apps into the system settings If you would like to help on this rom and become part of the new team please private message.
Compiled from Google source:
http://www.mydroidworld.com/forums/htc-droid-eris/1234-android-2-1-htc-eris-leaked.html
free apps from market on phone:
quickboot
pocketcloud
terminal emulator
File manager (android open source code)
http://www.multiupload.com/6K1O736M29 - Gingerbreadeddebian v 1 - Plain (old)
you say wifi hotspot isn't working.
was that ever even a feature available for the eris?
never has worked besides an app, the only reason I say isnt working is because there is an app that works, for wifi tether, and wpasupplicant should be able to handle wifi hotspot, we just need to go threw a few files and rewrite the code. If someone has the hear they can do this, or an nother way that would make me happy would be just to change the link, for settings wifi hotspots to wifi tether app
either way I would like a more perminant way to use wifi tether make it look native
hows debian run? and which version is it?
THE SENSING VERSION IS AN ARMV STABLE VERSION, WITH VNCSERVER, AND ICEWEASEL, JUST RUN LINUX BOOT IN TERMINAL AND CONNECT TO SENSING WITH:
User:android
Localhost
Pass:android
5901
Everythingworks connects to internet, the image I posted was me searching XDA forums with it
Sent from my HTC(ERIS) CLOAKED Vision using XDA App
Does that say flash 10.1 is working...?
Yep, finaly added link for download, now adding the debain.img soon
This Rom looks just another one on here.
Sent from my...
The looks isn't what makes this Rom, its what u don't see that makes this Rom .This Rom is SENSE, any Rom that is sense will look the same, unless we change the launcher or how it looks. If you want to theme the Rom or join the team let me know, lots to work on.
Sent from my HTC Vision (cloaked-Eris running Gingerbrededdebain)using XDA App
PFongemie said:
This Rom looks just another one on here.
Sent from my...
Click to expand...
Click to collapse
GPL requires links to the source for all Rom's or Apps posted on XDA... What source is this Rom from?
Google code, and my updates added info in original post
Sent from my HTC Vision (cloaked Eris Gingerbreadeddebain using XDA App
mjgdroid said:
Google code, and my updates added info in original post
Sent from my HTC Vision (cloaked Eris Gingerbreadeddebain using XDA
Deleted should have sent a pm
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
ORIGINALY POSTED BY ITHINKTOHILYOFMYSELF TAZZ
Dude don't lie.. u used my Rom I've pulled it apart.. just thank me .. u could have asked tho. U need my boot img I had to edit it. Also u used my build prop and update script stop Ur lies
Sent from my ADR6400L using XDA Premium App
__________________
Please help control the Human population: spay or neuter your humans.
Click to expand...
Click to collapse
Dont think that highly of yourself. I didnt use any of your rom, ACTUALY I tested your rom and your ROM SUCKS, you dont have half of the lib files I have in my rom, also I did try your boot.img for the softkeyboard, BUT IT DID NOT WORK. IT FROZE MY PHONE. I WAS GOING TO THANK YOU IF THE BOOT.img worked but it did not however. update script was provided by autosigner wow you are a lamer!
OH ya and my build.prop, I edited using the thread on how to trick flash10.1 to run on android armv6 so you are wrong there too here is my build.prop for the world to see:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=HCL31
ro.build.display.id=GRJ22
ro.build.version.incremental=eng.kmobs.20110510.000606
ro.build.version.sdk=11
ro.build.version.codename=REL
ro.build.version.release=3.1
ro.build.date=Thurs Sept 3 10 00:06:35 PDT 2011
ro.build.date.utc=0
ro.build.type=user
ro.build.user=localhost
ro.build.host=localhost
ro.build.tags=test-keys
ro.product.model=HTC Vision
ro.product.brand=verizon
ro.product.name=HTC Vision
ro.product.device=desirec
ro.product.board=desirec
ro.product.cpu.abi=armeabi-v6j
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7k
# ro.build.product is obsolete; use ro.product.device
ro.build.product=Vision
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=HoneyCombed-Linux
ro.build.fingerprint=google/soju/crespo:2.3.1/GRH78/85442:user/release-keys
ro.product.version=HoneyCombed-Linux
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
#
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.hsxpa=2
ro.ril.hsupa.category=5
ro.ril.enable.a52=1
ro.ril.enable.a53=1
ro.ril.def.agps.mode=2
ro.ril.def.agps.feature=1
ro.ril.gprsclass=10
#
wifi.interface=tiwlan0
#
windowsmgr.support_rotation_270=true
#
debug.sf.hw=1
ro.product.multi_touch_enabled=true
# Increase value for jpg decode capability
ro.media.dec.jpeg.memcap=10000000
# Screen Resolution
ro.sf.lcd_density=160
# Dalvik Tweaks
dalvik.vm.execution-mode=int:jit
dalvik.vm.heapsize=32m
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# Compcache Settings
ro.compcache.default=26
# Tweaks
persist.sys.use_dithering=0
ro.telephony.call_ring.delay=1000
windowsmgr.max_events_per_sec=60
wifi.supplicant_scan_interval=90
mot.proximity.delay=150
# OpenGL Settings
ro.opengles.version=165537
# Network Settings
ro.telephony.default_network=4
ro.com.google.clientidbase=android-htc-rev
ro.cdma.home.operator.alpha=Verizon
ro.com.google.locationfeatures=1
ro.cdma.home.operator.numeric=310012
ro.cdma.homesystem=128,64
ro.cdma.data_retry_config=default_randomization=960000,960000,960000,960000,960000
#
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
#
settings.display.autobacklight=1
# SD Storage insert notification sound
persist.service.mount.playsnd=0
# Additional Build Properties
ro.setupwizard.enable_bypass=1
net.bt.name=Android
ro.config.sync=yes
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.setupwizard.mode=OPTIONAL
# Rommanger Info
## NOT SET UP YET
ro.rommanager.developerid=Mike
ro.modversion=HoneyCombed-Linux
# Hardware Info
ro.product.processor=528MHz
ro.product.ram=288MB
ro.product.display_resolution=3.2 inch HVGA resolution
ro.product.main_camera=5M
ro.product.front_camera=NA
ro.product.wifi = 802.11 b/g
ro.product.bluetooth=BRF6300
Click to expand...
Click to collapse
BRING BACK KAOS
mjgdroid said:
ORIGINALY POSTED BY ITHINKTOHILYOFMYSELF TAZZ
Dont think that highly of yourself retard. I didnt use any of your rom, ACTUALY I tested your rom and your ROM SUCKS, you dont have half of the lib files I have in my rom, also I did try your boot.img for the softkeyboard, BUT IT DID NOT WORK. IT FROZE MY PHONE. I WAS GOING TO THANK YOU IF THE BOOT.img worked but it did not however. update script was provided by autosigner wow you are a lamer!
BRING BACK KAOS
Click to expand...
Click to collapse
First off .. Ur wrong and on Tuesday I will show u ok? No need for name calling dude.. u did use mine but its kool man I really don't care...u needed to edit the boot Img mind telling how u did it ? U have to copy ..I'm not gonna resort to name calling like u bro
Sent from my ADR6400L using XDA Premium App
mjgdroid said:
ORIGINALY POSTED BY ITHINKTOHILYOFMYSELF TAZZ
Dont think that highly of yourself retard. I didnt use any of your rom, ACTUALY I tested your rom and your ROM SUCKS, you dont have half of the lib files I have in my rom, also I did try your boot.img for the softkeyboard, BUT IT DID NOT WORK. IT FROZE MY PHONE. I WAS GOING TO THANK YOU IF THE BOOT.img worked but it did not however. update script was provided by autosigner wow you are a lamer!
BRING BACK KAOS
Click to expand...
Click to collapse
U need to read the GPL license here... Links to sources used for Rom's and Apps have to be posted in the OP. This is an open source forum, therefore sources need to have links for others to share in. I'm assuming since the source link isn't posted, this rom is a clone of someone else's and therefore doesn't belong up here. Given your response to the dev, that just confirms it.
Bringing Kaos back to the Eris community? Why, so you have some new source code to use? Dude, just post the source link and everything will be totally fine... If it's a clone, atleast give credit and discuss it with the Dev...
Wpw just the kind of thing I want to read in a PUBLIC FORUM. This seems like a PRIVATE issue and I am sure a lot of folks would appreciate it if y'all kept it that way.
tazzpatriot said:
First off .. Ur wrong and on Tuesday I will show u ok? No need for name calling dude.. u did use mine but its kool man I really don't care...u needed to edit the boot Img mind telling how u did it ? U have to copy ..I'm not gonna resort to name calling like u bro
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
You know there were people before you that could create roms, there are people after you can will create more roms, yours is not the best, and you try to say that it is.
I was kind enough to not tell people all you do is put a luancher on an old build of froyo, and call it a new rom, like your IPHONE ROM, and the reason I can say this is, because about a year ago I posted the windows7.apk. This post stopped you from creating " a new rom" even though it was no new rom, just an old foryo with a new windows7.apk. Talk about taking peoples work and making it yours.
mjgdroid said:
You know there were people before you that could create roms, there are people after you can will create more roms, yours is not the best, and you try to say that it is.
I was kind enough to not tell people all you do is put a luancher on an old build of froyo, and call it a new rom, like your IPHONE ROM, and the reason I can say this is, because about a year ago I posted the windows7.apk. This post stopped you from creating " a new rom" even though it was no new rom, just an old foryo with a new windows7.apk. Talk about taking peoples work and making it yours.
Click to expand...
Click to collapse
Dude I can. Count how many ways that statement is wrong Windows ? but I'm done. Not gonna argue with u peace
Just one more thing and ill never speak about it again
U should remove system/etc/ init.d/ 40data2text from Ur update script.
I REMOVED IT FROM MY ROM..lol that's y its not in Ur folder
Now if u wish to continue pm me not here if in my thread
Sent from my ADR6400L using XDA Premium App
I'm getting really confused here Lol
Sent from my ADR6300
http://forum.xda-developers.com/showthread.php?t=755526
Sent from my ADR6300
I could not find any binaries of the MTD-Utils (a set of useful tools when dealing with flash devices; see http://www.linux-mtd.infradead.org/index.html) for Android so I compiled some Android binaries from the source (http://git.infradead.org/mtd-utils.git).
My main interest was to get the two programs 'nanddump' and 'nandwrite' running on Android which must be used instead of 'dd' when creating images of nand partitions and restoring partitions from these images, because dd does not handle the bad blocks on the nand correctly which could lead to corrupted data.
With these two tools more flexible backup/recovery tools can be implemented since a backup/recovery can be made for every partition available on the device, even those which do not have a readable filesystem, for example the bootloader. Also, for partitions which include a filesystem, but hide some extra data outside that filesystem, this hidden data will also be included in the backup. These raw nand partition images can be tar'd or zip'd to reduce the size of the backup files.
Download: http://www.multiupload.com/5GJLEJNR8M
I do not accept donations, however if you want to make my life easier and thank me for my efforts, please think about signing up for a free SpiderOak account using this refer-a-friend link https://spideroak.com/download/referral/b89974e492728fa6a246880f0b7cbcd5. It is just like Dropbox except you can get up to 50GB of free space and they have a true zero-knowledge policy.
Thanks. I am trying to dump the system partition and restore it to another Android Mobile. Any Hints ? Thanks.
kkkelvinkk said:
Thanks. I am trying to dump the system partition and restore it to another Android Mobile. Any Hints ? Thanks.
Click to expand...
Click to collapse
Dump from one device wont work on other, if they are very similar it has few chances of booting but else it'ld brick if you dont be safe!
Actually, I want to remove some system app and then install other app, and make all configuration. After that, I want to clone this configuration to other mobile device with same model. Do you have any suggestions ?
Thanks.
kkkelvinkk said:
Actually, I want to remove some system app and then install other app, and make all configuration. After that, I want to clone this configuration to other mobile device with same model. Do you have any suggestions ?
Thanks.
Click to expand...
Click to collapse
Ok so you got a phone (model a) and you wanna remove sumtin frm /system/app n add sumtin back n then let some user having the same model a use it
Get root
Install root explorer or any root file explorer
Allow su permissions
Navigate to /system/app and do what you wanted
Then you can dump the /system partition
Kindly give some more info of your device - will help more
And yes also paste the output of "mount" command
I think I can only give more information about the phone after I back to my office.
Actually, I am using System App Remover to remove the System App. It does the job.
Wow can I dump and restore the system partition ? I have tried to use dd command, but it fails. May be nanddump will help, but I cannot find the documentation how to use it. Please help. Thanks.
Is there any way to have nanddump directly send the image to a PC that is running recv_image? I'd like to use nanddump on my Galaxy Nexus, but since it is lacking an SD card, it would seem like writing the nanddump image to the nand would just destroy any possibility of obtaining a clean nand image.
I found a way using netcat...
From host machine in one console window:
Code:
adb.exe forward tcp:5555 tcp:5555
adb.exe shell
# nanddump [options] /dev/mtd/mtd0 | nc -l -p 5555
From host machine in a second console window
Code:
nc 127.0.0.1 5555 > flashdump.bin
So how does nanddump compare with Nandroid, which uses mkyaffs2image to create .img files?
So does n e one a mirror for this??? Multiupload is no good n e more...
Sent from my Hellfire Kindle using xda premium
da-pharoah said:
So does n e one a mirror for this??? Multiupload is no good n e more...
Sent from my Hellfire Kindle using xda premium
Click to expand...
Click to collapse
Per my request, stericson kindly built nanddump and nandwrite into his version of busybox. If you still want Ezekeels's pack, I might still have it around here somewhere.
Maximilian Mary said:
Per my request, stericson kindly built nanddump and nandwrite into his version of busybox. If you still want Ezekeels's pack, I might still have it around here somewhere.
Click to expand...
Click to collapse
Yes please and thank you..
Sent from my Hellfire Kindle using xda premium
da-pharoah said:
Yes please and thank you..
Sent from my Hellfire Kindle using xda premium
Click to expand...
Click to collapse
Nope. I dug through my sdcard and the backups on my computer, and I do not still have it. If you want to contact the OP directly, he is @ezekeel666 on twitter.
Maximilian Mary said:
Nope. I dug through my sdcard and the backups on my computer, and I do not still have it. If you want to contact the OP directly, he is @ezekeel666 on twitter.
Click to expand...
Click to collapse
dirty... and nope also.. I PM'd him and he informed me he deleted all his backups on this....
also try compile, but it hard for me.
all link dead. please, upload mtdutil again.
so I saw that you updated your github!! thanks! now lets see if I can get this sorted and btw if I end up using anything no worries I will give you full credit as usual! Thanks again!
mtd ultil for android
ok guys...
1st: sorry for reviving this topic ...
2nd:here ara the binaries for android: http://goo.gl/eJ8mX
3rd and most importanto to me:
If I do a nandread mtd7 > mtd7.img (in my case the /misc partition) I can do a nandwrite mtd7.img > /dev/mtd/mtd7 without any data corruption ?
I have a lot of backups of many partition except this /misc that in freaking me!
So. Is this a reliablbe backup/restore system ? can I do it with all mtd partition ?
* I tested nandread in qcom msm_7x27 device running android 2.3.6.
shaunco said:
I found a way using netcat...
From host machine in one console window:
Code:
adb.exe forward tcp:5555 tcp:5555
adb.exe shell
# nanddump [options] /dev/mtd/mtd0 | nc -l -p 5555
From host machine in a second console window
Code:
nc 127.0.0.1 5555 > flashdump.bin
Click to expand...
Click to collapse
Or just:
adb shell "nanddump -f - /dev/mtd/mtd0" > mtd0.img
-f - outputs to stdout
Excude the partial OT, but are there any similar tools for MMC flash storage?
Hi there,
I just found catherall's thread on [how to boot CM 7.1 from the external SD card][0] on a Desire Z/G2 with the infamously fried eMMC.
I used his instructions to boot CM 7.2 (the last stable version for the Vision); since the above thread ends with a dangling question on how to update the system to be booted, I thought I'd document my efforts.
anonymousthing said:
anybody know what system.img format he is using?
Click to expand...
Click to collapse
It's just an ext4 file system:
Code:
$ file system.img
system.img: Linux rev 1.0 ext4 filesystem data, UUID=b4db3ed8-7d52-46a0-85fb-46fb67c5e837 (needs journal recovery) (extents) (huge files)
$ adb shell
~ # mount | grep system
/dev/block/loop0 on /tmp/boot.img-ramdisk/system type ext4 (rw,nodev,noatime,nodiratime,nouser_xattr,commit=19,barrier=0,data=ordered)
Disclaimer: On the original image, `file` actually identifies the FS as a `mounted or unclean` ext2; it's definitely an ext4 with journaling, though. Accordingly a `mount -t ext2` will fail with a `wrong fs type`.
You can create a new one with
Code:
$ dd if=/dev/zero of=system.img bs=4k count=64000
$ /sbin/mkfs.ext4 system.img
# mount -o loop -t ext4 system.img /media/new_sys
anonymousthing said:
I have tried making my own system.img from the rom but it does not work
Click to expand...
Click to collapse
This is potentially due to missing binaries:
Code:
$ diff -r /media/orig_sys update-cm-7.1.0-vision-signed/system | head -n 5
Only in /media/orig_sys/bin: cat
Only in /media/orig_sys/bin: cmp
Only in /media/orig_sys/bin: date
Only in /media/orig_sys/bin: dd
Only in /media/orig_sys/bin: dmesg
If you download a version of CM, at least the `toolbox` and the `busybox` binaries will be missing from the `system/bin` and `system/xbin` directories respectively. I couldn't be bothered to check for up-to-date versions but just copied the ones provided by catherall before copying over the new CM version:
Code:
# cp -r /media/orig_sys/bin /media/orig_sys/xbin /media/new_sys
# cp -r cm-7.2.0-vision/system/* /media/new_sys
This will obviously update all the files that come with CM 7.2 and just keep what's not included in the box.
While you're at it, you might want to add up-to-date gapps:
Code:
# cp -r gapps-gb-20131214-signed/system/* /media/new_sys
This gives you a booting CM 7.2. Just replace the `system.img` that comes with catherall's `.zip` with the one you just created and off you go
Unpleasant issue: Booting from SD seems to require a specifically prepared kernel, so the `boot.img` that comes with a different ROM/CM version won't work. So until someone finds out how to prepare a kernel for booting from SD, you will have to continue to boot the one provided by catherall. However, the WIFI driver has not been compiled into the kernel but lives in a separate kernel module in `/system/lib/modules/bcm4329.ko`. Which we (by copying over the `/system` dir from the CM 7.2 build) replaced with a version incompatible with the old kernel we have to boot. So if you intend to boot through `fastboot` and use WIFI (and why wouldn't you? ;P), we will have to put the old kernel module back:
Code:
# cp /media/orig_sys/lib/modules/bcm4329.ko /media/new_sys/lib/modules/
Weirdly enough, in the CM 7.2 version I downloaded, the permissions for the `dhcpd-run-hooks` script were broken, so I at least needed to fix those too:
Code:
# chmod 550 /media/new_sys/etc/dhcpd/dhcpd-run-hooks
So, `umount` your pristine new `system.img`, move it to your SD card and boot into CM 7.2.
HTH
D.
PS I naively tried to create a larger 1 GB `data.img`, copying over the content from the existing one, but the phone didn't boot with that one. I might have made a mistake (was rather late at that point -.- and I didn't investigate any further), but it seems like the size of the partitions may be hardcoded somewhere. If someone has any additional information, please let me know Thx!
PPS If anyone ([MENTION]@catherall[/MENTION]? ;P) knows anything about the kernel issue, I'd be highly interested
PPPS After creating this account (to be fair, I've been profiting from this community since the old Windows Mobile days), I was informed that as an account noob, I obviously didn't have anything to contribute to this community and was ordered to place my undoubtedly profane question (which certainly had been answered may times before, I was only too lazy/dumb to search) outside the elite developer forums [/rage]. Maybe one of the Mods can stitch the [original thread][0] and this st0pid workaround back together again? :/ Thanks!
[0]: http://forum.xda-developers.com/showthread.php?t=1572924
I didn't see anything about how to convert to f2fs for the nexus 6 so I thought i'd write something up as somebody requested me to do this.
What are the benefits of using f2fs over ext4?
I could list pros and cons, but I strongly encourage you to do your own research on the matter.
Should I do this
If you want to at your own risk
Pre-requisites
You need a recovery that supports f2fs in kernel and has the f2fs tools. Dhacker20 has provided one (TWRP 2.8.5.0) here: https://twitter.com/dhacker29/status/568070387306766336
You will need a kernel that supports f2fs for /cache and /data (Obviously I recommend Zen Kernel, but there are some others. Zen has the newest f2fs from upstream, while others may not)
ONLY YOU ARE RESPONSIBLE FOR YOUR DATA. IT IS YOUR RESPONSIBILITY TO UNDERSTAND THE RISKS AND YOUR RESPONSIBILITY TO BACKUP YOUR DATA
How-To
1.) Back up everything you care about to your PC (everything will be erased, including sdcard)
2.) Install a kernel that supports f2fs. Get the boot.img and do "fastboot flash boot boot.img" in bootloader (Like Zen)
3.) Install the recovery with f2fs support (fastboot flash recovery twrp-recvery-f2fs.img)
4.) In TWRP, go to Wipe
5.) Do a full wipe by swiping right
6.) Go to Wipe -> Advanced Wipe
7.) Choose /cache
8.) Choose "Change Filesystem"
9.) Pick f2fs, proceed
10.) Do the same thing for /data
11.) While still in recovery, plug phone into PC and do this:
Code:
# adb shell
# mount -o rw /system
# cp /sbin/fsck.f2fs /system/bin/
# cp /sbin/mkfs.f2fs /system/bin/
# chmod a+x /system/bin/*f2fs*
12.) Reboot and you are done.
Reserved
Is adb shell in terminal app
jiv101 said:
Is adb shell in terminal app
Click to expand...
Click to collapse
No adb is part of the android SDK platform-tools
I did this a while ago (except for step 12), and I remember something happening, which caused my data partition to become corrupted. I tried to format the partition again using ext3 or whatever the default is and that ended up giving me a soft brick. I had to restore the factory software. I have read things of where it does improve R/W speeds but I don't know if it's worth the hassle of possibly losing everything at the drop of a hat if you flash ROMs often.
RSVP..
Thanks for the information on F2FS well needed..!
brando56894 said:
I did this a while ago (except for step 12), and I remember something happening, which caused my data partition to become corrupted. I tried to format the partition again using ext3 or whatever the default is and that ended up giving me a soft brick. I had to restore the factory software. I have read things of where it does improve R/W speeds but I don't know if it's worth the hassle of possibly losing everything at the drop of a hat if you flash ROMs often.
Click to expand...
Click to collapse
The last step is a huge component of the whole process. If the rom doesn't have f2fs-tools in by default (most don't have fsck.f2fs/mkfs.f2fs) you will not have standard integrity checking every time you boot like you do on ext4. If you do the last step you will get integrity checking every time you bootup.
Also, since f2fs is a relatively young file system it can do harm to revert to older versions of the file system. For example, zen kernel has the newest f2fs which was updated last about 2 days ago. If you go on stock kernel you will find an f2fs that is 1+ year old. There may be a compatibility issue between these two where if you flash different roms (which almost always bundle a kernel)/kernels you will almost certainly have an issue.
But that's all part of the risk with using a relatively young file system. I do not understate the risks of data corruption in doing something like this - but anybody who is doing this and has significant worry should take precautions is backing up all their important files.
bbedward said:
The last step is a huge component of the whole process. If the rom doesn't have f2fs-tools in by default (most don't have fsck.f2fs/mkfs.f2fs) you will not have standard integrity checking every time you boot like you do on ext4. If you do the last step you will get integrity checking every time you bootup.
Also, since f2fs is a relatively young file system it can do harm to revert to older versions of the file system. For example, zen kernel has the newest f2fs which was updated last about 2 days ago. If you go on stock kernel you will find an f2fs that is 1+ year old. There may be a compatibility issue between these two where if you flash different roms (which almost always bundle a kernel)/kernels you will almost certainly have an issue.
But that's all part of the risk with using a relatively young file system. I do not understate the risks of data corruption in doing something like this - but anybody who is doing this and has significant worry should take precautions is backing up all their important files.
Click to expand...
Click to collapse
Is there any sort of confirmations when you are doing the last steps? I see this when I do them and I'm not sure if it has actually done the last steps.
C:\Development\platform-tools>adb shell
~ # ←[6nmount -o rw /system
mount -o rw /system
~ # ←[6ncp /sbin/fsck.f2fs /system/bin/
cp /sbin/fsck.f2fs /system/bin/
~ # ←[6ncp /sbin/mkfs.f2fs /system/bin/
cp /sbin/mkfs.f2fs /system/bin/
~ # ←[6nchmod a+x /system/bin/*f2fs*
chmod a+x /system/bin/*f2fs*
~ # ←[6n
C:\Development\platform-tools>
lobrau said:
Is there any sort of confirmations when you are doing the last steps? I see this when I do them and I'm not sure if it has actually done the last steps.
C:\Development\platform-tools>adb shell
~ # ←[6nmount -o rw /system
mount -o rw /system
~ # ←[6ncp /sbin/fsck.f2fs /system/bin/
cp /sbin/fsck.f2fs /system/bin/
~ # ←[6ncp /sbin/mkfs.f2fs /system/bin/
cp /sbin/mkfs.f2fs /system/bin/
~ # ←[6nchmod a+x /system/bin/*f2fs*
chmod a+x /system/bin/*f2fs*
~ # ←[6n
C:\Development\platform-tools>
Click to expand...
Click to collapse
That's about it, you can type exit to get out of adb shell or just close it.
On your device you can make sure f2fs took by simply typing "mount" in terminal emulator. You should see you data and cache reads f2fs now.
lobrau said:
Is there any sort of confirmations when you are doing the last steps? I see this when I do them and I'm not sure if it has actually done the last steps.
C:\Development\platform-tools>adb shell
~ # ←[6nmount -o rw /system
mount -o rw /system
~ # ←[6ncp /sbin/fsck.f2fs /system/bin/
cp /sbin/fsck.f2fs /system/bin/
~ # ←[6ncp /sbin/mkfs.f2fs /system/bin/
cp /sbin/mkfs.f2fs /system/bin/
~ # ←[6nchmod a+x /system/bin/*f2fs*
chmod a+x /system/bin/*f2fs*
~ # ←[6n
C:\Development\platform-tools>
Click to expand...
Click to collapse
Nope, it will only inform you if something went wrong (like file not found) of it all went through with no error it worked.
After you bootup you can verify it worked by typing "mount" in adb shell or terminal emulator. It should say f2fs on /data and /cache. Also in something like root Explorer if you navigate to /system/bin you should see the files you copied (fsck.f2fs and mkfs.f2fs)
bbedward said:
Nope, it will only inform you if something went wrong (like file not found) of it all went through with no error it worked.
After you bootup you can verify it worked by typing "mount" in adb shell or terminal emulator. It should say f2fs on /data and /cache. Also in something like root Explorer if you navigate to /system/bin you should see the files you copied (fsck.f2fs and mkfs.f2fs)
Click to expand...
Click to collapse
Perfect thanks for the quick response looked like it worked. Just out of curiosity is there any reason to format system to f2fs or does it end up causing issues, or just no changes in use?
lobrau said:
Perfect thanks for the quick response looked like it worked. Just out of curiosity is there any reason to format system to f2fs or does it end up causing issues, or just no changes in use?
Click to expand...
Click to collapse
I've tested it partly in testing the newest f2fs Zen merges as well as just general f2fs testing before.
It seems like writes are a bit faster, especially sql stuff. I've seen some grossly huge benchmark differences on other devices - on the n6 I've seen improvements but nothing astronomical like those benchmarks portrayed (I presume the 200% increase in write performance they showed is not accurate regardless) .
Recovery
So currently I'm on a 5.1 stock based rom (sinless) and TWRP 2.8.6
HAve Downloaded the latest Zen Kernel, and am downloading the latest 5.1 Benzo Rom.
Am I going to have issues rolling back to a 2.8.5 recovery - does 2.8.5 support 5.1 based roms?
shaitan667 said:
So currently I'm on a 5.1 stock based rom (sinless) and TWRP 2.8.6
HAve Downloaded the latest Zen Kernel, and am downloading the latest 5.1 Benzo Rom.
Am I going to have issues rolling back to a 2.8.5 recovery - does 2.8.5 support 5.1 based roms?
Click to expand...
Click to collapse
Yea it's compatible. There isn't a 2.8.6 with f2fs support yet that I know if and I haven't had the time to make one myself, but the 2.8.5 one works just fine.
@bbedward
I didn’t know any about the part 11 (I mean I convert mine to F2FS before I read this) so I’m wondering I’m gonna face any problem or not?
And also if have to do it, can I do it now or I have to wipe everything and then do it (cause changing partition to F2FS will clean everything)
Also I’m on your kernel.
dany20mh said:
@bbedward
I didn’t know any about the part 11 (I mean I convert mine to F2FS before I read this) so I’m wondering I’m gonna face any problem or not?
And also if have to do it, can I do it now or I have to wipe everything and then do it (cause changing partition to F2FS will clean everything)
Also I’m on your kernel.
Click to expand...
Click to collapse
Every time you boot your phone, it automatically runs fsck (for ext4 on stock). Essentially it's an automatic integrity check and repair.
So if it finds issues at boot up in the file system, it will tend to fix them automatically. If you look at boot up logs currently you will probably see something like "/system/bin/fsck.f2fs not found skipping integrity check"
You don't have to wipe everything though, you can just install the tools now.
I'm almost happy I posted this now hopefully it saves a few filesystems for folks who didn't do it completely.
---
When you see a kernel say f2fs compatible it means:
- f2fs is built into the kernel or a module is provided
- It's ramdisk's fstab allows for mounting of partitions as f2fs. On zen - it supports /data and /cache
When you see a rom say f2fs compatible it means:
- They have an f2fs-compatible kernel included
- They have the f2fs tools in the rom (As step 11 does)
This is why I say in the title this is "Any Rom" compatible as it will work on any rom, while on other devices you may see "Rom x, rom y, and rom z are the only known roms to be fully compatible." If you just do it this way it doesn't matter because it'll make any rom compatible with f2fs.
@bbedward this worked perfectly! But I just want to confirm that it switches back to ext4 after flashing a new ROM? After wiping and doing a clean flash it seems I'm not booting in f2fs anymore.
Am I doing something wrong or will I have to do this every time I clean flash?
Thanks again for the tutorial!
philsfan said:
@bbedward this worked perfectly! But I just want to confirm that it switches back to ext4 after flashing a new ROM? After wiping and doing a clean flash it seems I'm not booting in f2fs anymore.
Am I doing something wrong or will I have to do this every time I clean flash?
Thanks again for the tutorial!
Click to expand...
Click to collapse
I think most likely when you flashed a rom it overwrote your f2fs kernel, which caused it to reformat to ext4 when you booted it up.
Whenever you flash a rom you will need to flash f2fs-kernel right afterwards, and re-copy the tools (step 11) if the rom doesnt have them already in order to keep f2fs.
bbedward said:
I think most likely when you flashed a rom it overwrote your f2fs kernel, which caused it to reformat to ext4 when you booted it up.
Whenever you flash a rom you will need to flash f2fs-kernel right afterwards, and re-copy the tools (step 11) if the rom doesnt have them already in order to keep f2fs.
Click to expand...
Click to collapse
Thanks for responding so soon!
So I did flash zen9 (so good BTW) immediately after but I didn't repeat step 11 again. So that means Chroma doesn't have the necessary files for f2fs, good to know!
Edit: @bbedward does that mean I don't have to reformat again? Just do step 11?
Edit 2: entered step 11 in recovery and now i'm back to f2fs thanks again!
bbedward said:
The last step is a huge component of the whole process. If the rom doesn't have f2fs-tools in by default (most don't have fsck.f2fs/mkfs.f2fs) you will not have standard integrity checking every time you boot like you do on ext4. If you do the last step you will get integrity checking every time you bootup.
Also, since f2fs is a relatively young file system it can do harm to revert to older versions of the file system. For example, zen kernel has the newest f2fs which was updated last about 2 days ago. If you go on stock kernel you will find an f2fs that is 1+ year old. There may be a compatibility issue between these two where if you flash different roms (which almost always bundle a kernel)/kernels you will almost certainly have an issue.
But that's all part of the risk with using a relatively young file system. I do not understate the risks of data corruption in doing something like this - but anybody who is doing this and has significant worry should take precautions is backing up all their important files.
Click to expand...
Click to collapse
That was probably it! It was just a pain because this is the first phone that I've had in a while that doesn't have an SD card, I had a nandroid, but it doesn't do any good if you can't access your data partition Hahaha I have now taken to uploading my nandroids to Google Drive or putting them on my pc just in case that happens.