EDIT 12/24/2014: Finally got back into my XDA account and finally updating this post with (hopefully) functionall links to the files I still have, Merry Christmas everyone!!
HI, found the misc development section so I'm putting all my findings on the Sharp FX Plus ADS1. Closest device I found that has cyanogenmod is the ZTE V9 (Theres a Z71 and some others also), I'm sure there are others but figure I'd post this in an appropriate spot incase anyone is curious. I'm attempting to get CyanogenMod of booting on this for a nice learning experience.
This phone has a Froyo 2.2.2 ROM, when "slimmed" or de-bloated the little thing is pretty snappy. Chainfire 3d Pro installed with no problems, ClockworkMod Recovery backups/restore work (updating to newer version doesnt "recognize" CWM installed, but older one allows reboot into recovery), Terminal and ADB dont give me any issues at all, logcat can be done from boot with the insecure boot.img. Hopefully this information is usefull to anyone curious.
Removed "links other information" - my old domain is not up.
Drivers:
-Sharp has them available from this site (for Windows/OSx)
Device:
Qualcomm MSM7x27 @ 600MHz
Adreno 200
512MB RAM, 512MB ROM (200-ish available to user).
Root:
-SuperOneClick 2.3.3 worked fine for me
ClockWorkMod Recovery:
-You should already be rooted before doing this.
-Made from the stock recovery.img processed on the CWM builder site. Its version 6.
-Only thing that doesnt work at the moment is mounting via USB mass storage. Aside from that, works like a charm.
-Download the files zip (attached to this post)
-Copy flash_image and the recovery.img of choice (stock is in root of archive, CWM folder contains the ClockWorkMod Recovery).
-Run these commands from terminal (on device or adb)
Code:
mount -o remount,exec /dev/block/vold/179:1 /sdcard
cd /sdcard
./flash_image recovery /sdcard/recovery.img
reboot
{
"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"
}
System Dump:
-I can try and make a "stock ROM" flashable zip, but I'll need a stock dump from a rooted ADS1. I only have the modified "stock ROM".
LINKS NOW AT DEV-HOST
Modified ROMS:
Stock 2.2.2 based (google apps pre-installed)
ADS1-2.2.2 test-acemod4x
CM6 Z71 port
CM6.1.2-ADS1 Z71 test-port
modded google apps for the CM6 port ONLY
Other info:
-output of mount
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mtdblock1 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock9 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock7 /persist yaffs2 rw,nosuid,nodev,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/mtdblock3 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /fotaup yaffs2 rw,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0712,dmask=0700,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0712,dmask=0700,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.keramidas.TitaniumBackup-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.adobe.reader-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.aol.mobile.aim-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
-output of cat /proc/mtd
Code:
$ cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00040000 "boot"
mtd1: 0a500000 00040000 "system"
mtd2: 00100000 00040000 "splash"
mtd3: 02800000 00040000 "cache"
mtd4: 00080000 00040000 "fota_state"
mtd5: 02100000 00040000 "fota_up"
mtd6: 00080000 00040000 "misc"
mtd7: 00280000 00040000 "persist"
mtd8: 00500000 00040000 "recovery"
mtd9: 0bcc0000 00040000 "userdata"
-Also BOARD_KERNEL_ stuff (when breaking the original kernel down)
Code:
BOARD_KERNEL_CMDLINE mem=458M console=ttyMSM2 androidboot.hardware=qcom
BOARD_KERNEL_BASE 13600000
BOARD_PAGE_SIZE 4096
Was stuck for a while trying to repack a insecure kernel, few "bricks" (thank goodness for CWM's backups lol).
Got it to work and boot! Its still the same original boot.img but I was able to repack it with ro.secure=0 and other changes to the default.prop (enabled adb, debugging etc..)
Heres a link with info on it, and heres the files (in zip this time) incase anyone wants to test.
Basically (if anyone wants to try this insecure.boot.img) for test (make sure you have CWM and a Nandroid backup first) - Phone should already be rooted (SuperOneClick 2.3.3), ADB Debugging on (I used a ADB shell to do this, you should be able to run the commands from the terminal on the device itself)
Open the archive, copy the flash_image (if you havent from the CWM Install), also copy the insecure.boot.img over to the sdcard (you can alsio do this with the original boot.img to restore)
Code:
su
mount -o remount,exec /dev/block/vold/179:1 /sdcard
cd /sdcard
flash_image boot insecure.boot.img
reboot
All goes well, the phone should reboot normally. MInes took a little longer on initial booting, but it went through using that boot.img and the stock rom.
Now onto the next hurdle (getting CyanogenMod to compile) - The problem I was having before was using a version of mkbootimg that did not support the --pagesize option.
I'll try repacking the zImage that was built into a CM7 ramdisk and see if I can get past the "Sharp" screen and try to boot..
If anyone has any thoughts on the subject it would be greatly appreciated, back to the terminal I go
CM6 Booted
Well, went back to trying to see what would "boot" in this phone. My attempt to port CM6 to this ADS1 is somewhat successful!!!!
Currently botted into a modified Z71 CM6 ROm, using the insecure.boot.img I repacked for the Sharp ADS1.
Compared the system structures side by side and added the ADS1 bits (also for the surf_keyboard and other stuff).
Removed Z71 specific files, made a hybrid build.prop with the ADS1 changes.
Result: Boots!! Pretty Usable!!!
Still Broken:
-No camera/camcorder (checking the libcamera files)
-WiFi
-keyboard backlight
-some keyboard buttons (@ key, everything else is good - onscreen and swype are in from stock rom)
Works:
-battery charging (even switches to the sharp charging screen when its off but plugged in)
-radio - H+ on the status bar, data, sync, sms, etc.. (havent tried MMS yet)
-bluetooth - enables fine, just need something to pair with
-boots (initial boot takes a while as it does its firstrun thing, reboots are very fast)
-sound works
-graphics seem smooth as butter (going through the UI, etc..)
-touchscreen
-qwerty keyboard
-screen rotation works
-CM6 gapps work
Anyways, I'm kinda excited that atleast CM6 booting and (aside from the broken stuff) somewhat usable! I'll attatch the logcat I made with adb as it booted, did some testing, etc.. Incase anyone wants to see.
CyanogenMod 6 ROM testing Updates.. (SO FAR SO GOOD!!)
(I accidentally posted this in the General thread I had, and it wouldnt let me delete it - so I put the information in this as its under the Misc Development section)
Update on "porting" CM6 for the Commtiva Z71 to the Sharp ADS1.
Not Working:
-WiFi - logcat shows an error when loading the libra.ko seems to load librasdioif.ko fine however
-Camera - logcat shows problem loading liboemcamera.so (using the ADS1 libs and Camera.apk)
-3d Acceleration - works, but has some hiccups (so it still needs *some* work - importing some Adreno200 EGL libs over improved greatly so far)
-USB Mounting - havent gotten to this yet, still working on WiFI/Camerea. ADB however works flawlessly (push, pull, reboot, lolcat/logcat, etc..)
[email protected] Key and SYM on physical keyboard arent mapped correctly (going to see if I can poll the keys and figure that out) also the Camera physical button does not map.
Working:
-Calls (speaker also, mute, normal, etc..)
-Data (uploaded my wordpress post from the device, market sync works, etc..)
-SMS/MMS
-SDCARD (can be browsed internally, SD-Ext for app2sd works, no USB Mounting yet)
-Bluetooth
-Audio
-Keyboard Backlight+Sensors (properly shuts off when screen is slid closed)
-Deep Sleep seems to be working (battery life seems to be decent, still gotta work other bugs out)
-Rotation sensor (open keyboard, screen rotates for you also)
-Auto brightness sensor looks to be working normally (even turns keyboard backlighting off it seems)
http://acebox.info/2012/07/sharp-fx-plus-ads1-z71-cm6-test-rom/
I'm a little stumped on the WiFi + Camera issue, both roms (CM6-Z71 and ADS1-Stock) are running similar Kernels, and the version of Froyo is almost identical; CM6-Z71 Is actually 2.2.1 and ADS1 is 2.2.2 as I recieved it (CyanogenMod runs sooo much better ).
wifi libs (in /system/lib/modules):
Code:
libra.ko
librasdio.ko
modules.dep.bb
If anyone has some time to help or atleast offer some insight, I can repost the stock dumps, nand backups, kernel, ramdisk, logcats - and even a cwm zip I've made for flashing a "slimmed" version of the stock 2.2.2 Froyo as well as any "working" version of the CM6 "port" I'm attempting). I've been comparing logcats from the stock rom and this to see what can possibly be stopping wifi/camera working..
The CM6 ROM IS EXPERIMENTAL AND NOT A DAILY DRIVER AT ALL - (I wouldnt consider it untill WiFI, Camera, etc.. are functional. It is usable - even updated my wordpress post from the device with screenshots, hower it is still an Development Work In Progress).
If anyone is feeling brave (or wants to help test), I've uploaded the CWM zips I used (experimental) onto my site (linked in this post). FLASH CLOCKWORKMOD RECOVERY AND DO A NAND BACKUP FIRST!! Then go nuts flashing away lol. Hope someone finds this usefull.
PS. THIS IS NOT A DAILY DRIVER ROM, ONLY FOR TESTING!
Info/ROM links - current ones posted here towards the bottom (so I only have to update one set of links lol)
WiFi partially working
UPDATE:
Got wifi working, test release here more information here. I fixed a few things in the ramdisk and updater-script. Now to get the camera/video and USB mounting working (ADB is fully functional, push/pull/logcat/lolcat work).
Also the original Swype, Weather, SMS and Email widgets work. For the market, flash the CM6 20110501 MDPI gapps package from here (its persistent between full wipes, use a NAND backup to return to clean install, workingo n a updater-script that fully wipes and removes all traces of GAPPS (doesnt seem to currently).
Shots of About Phone and Storage (theres some room I think)
UPDATE (EGL and Camera fixed!) - Notes on swapping libs between roms
Saw a nice way of using readelf and it helped getting a lot of things sorted out.
Basically made a shell script and but it into my ~/bin folder and used that to manually check dependencies of the libraries. checked them and made sure they matched, flashed the phone and now its almost 100%!
I believe replacing libc.so from the CM6's /system/lib with the ads1 broke adb logcat - adb shell works, push/pull work fine. Gallery3d is now VERY smooth, Camera works fine now (tested snaps, etc..)
so, to recap lol..
STILL BROKEN:
-USB Mass Storage (going to check ramdisk)
-adb logcat/lolcat (cannot link executable since fixing EGL)
-Need to check GPS (noticed I've been checking with WiFI only)
WORKS:
-Phone/Data
-SMS/MMS
-WiFI/Bluetooth
-Camera/Video
-EGL smooth
-SD Internal mounting/browsing (SD-Ext also for APP2SD)
-CyanogenMod 6 settings
-ADWLauncher Settings
-Sharp Widgets (SMS/Email)
-Gapps (use the CM6 MDPI version)
-Slide out Keyboard (still going to look at the @, Sym and Camera button mappings)
-Keyboard Backlight (with light sensor adjusting)
-Rotation Sensor
I'll post a link to an updated version soon if anyone wants to test, just sorting out a few small things - progress is progress! Hopefully have USB mounting working.
test version cm6-z71 port beta1
Got the ROM somewhat stable, EGL seems to be working VERY smoothly (tracked back dependencies) and Camera/Video work (using CM6 camera apk, going to test with the Froyo/Sharp camera apk).
Link to test here - more information here.
Hope this is helpful to anyone testing.
Updated Ext3 ClockWorkMod - CyanogenMod 6.1.2 USB test.
Updated the ClockWorkMod Recovery from the builder site (generated using a dump of the stock.img)
Now it formats /sd-ext as Ext3 and not Ext4 (more info here). Also included the stock recovery image and tools.
Also got a test version of the CM6.1.2 port (more info here) - USB mass storage should work, no Google Apps (can be downloaded seperately - get CyanogenMod 6 MDPI version).
BUGS/TODO:
-Looking at a hardware keyboard "glitch" - Sym key brings up the "Select Input Method" menu (vs the Symbol menu). The @(AT) key also is unresponsive, using KeyTest.apk - shows as picking up #215 - but its not doing anything.
-Need to test the GPS
-Need to test Bluetooth pairing more
-Checking issue with init.d automounting sd-ext (running /system/etc/init.d/05mountsd works)
-If ADW Launcher stays stuck in Portrait mode (wont rotate), uncheck System Persistent from the ADW System options if its checked in and having problems.
DOWNLOADS:
CWM-EXT3-TEST (unpack to your SDCARD)
CM6.1.2-ADS1-B4a2 (flash with CWM, backup and data wipe prior to testing)
Notes on building CyanogenMod from source possibly..
Noticed when I got my initial zip back from the CM builder site, it had a device tree for the ads1. There isnt any "vendor" specific one matching, however I'm playing with one mocked from the Z71 tree (as they seem oddly similar).
I've already contacted Sharp about the sources, but not sure if I'm asking correctly . Maybe they'll respond. I was also asking about if they would have some kind of update.zip for the phone, theres a few other members that have "bricked" phones - a Sharp signed update.zip would work nicely for the stock recovery (unless theres another method)
However, just incase - testing this for a "proprietary mock up" to see if anything can work lol
-compared the extracted-files from the z71, removed the ones the ads1 did not have.
-ran a recursive diff between the bin, lib, etc folders between a Z71 cm6 rom (which I've based my test) and a system dump I made of the ADS1.
-added missing files for now (some might be for the Sharp UI Launcher)
-extract files works, copies the requested files off the phone (I've got a blend of a few ads1 froyo bits ontop of z71 cm6 atm)
-testing the local_manifest.xml to get it to work, experimenting
Still missing rild and libaudio sources (as well as some other ones I noticed in the Z71 tree) - going to experiment building a Froyo rom from source, using existing rild/audio libraries. Not entirely sure what I'm doing (as there is no real support for this device at all), just proceeding carefully and examining the surroundings as best as I can lol.
Z71-CM7.2.0 boots (needs work, but its something!)
Tested with a Z71 CM7 port that uses a similar kernel version to whats available for the ads1..
http://acebox.info/2012/07/sharp-fx-plus-ads1-cm7-test/
Hi Amaury,
I have been reading your posting these days. I am a new android device user, and I just bought a Sharp ADS1 to replace my old phone.
I would like to know which software did you use to root the ADS1, Can "SuperOncClick" root it?
And, do you have a back-up file of the original Stock ROM? or Can the "ClockwordMod" do the back-up for the original ROM?
Also, do you think it's possible to upgrade the Android 2.2 to Android 3.0 or even 4.0, 4.1 for this device?
This cell phone seems very nice and well functioned, but not many users or developers discuss about it.
Thanks for your answer and posting.
wisesoar said:
Hi Amaury,
I have been reading your posting these days. I am a new android device user, and I just bought a Sharp ADS1 to replace my old phone.
I would like to know which software did you use to root the ADS1, Can "SuperOncClick" root it?
And, do you have a back-up file of the original Stock ROM? or Can the "ClockwordMod" do the back-up for the original ROM?
Also, do you think it's possible to upgrade the Android 2.2 to Android 3.0 or even 4.0, 4.1 for this device?
This cell phone seems very nice and well functioned, but not many users or developers discuss about it.
Thanks for your answer and posting.
Click to expand...
Click to collapse
Hi, SuperOneClick 2.3.3 did the trick for me.
Unfortunately, dont have a backup of the stock system, The Clockworkmod custom recovery can backup the entire phone state to your sdcard, and you can restore the entire phone back to that exact state. Also if you can get a stock dump (all stock apps), let me know - I can probably try making a "flash to stock" cwm zip for it.
I'm not sure but think Sharp would have to release sources for the device? Or find sources that would be compatible with this device. Its pretty similar to a Commtiva Z71 as far as I can tell. I'd like to eventually try CM9 booting on this, so started with getting CM6/Froyo to work first - and found the Z71 worked with few modifications.
I found a Z71 Gingerbread 2.3.7 CM7.2 rom runs a similar 2.6.32.x kernel that boots (with modification) and somewhat works (no network, local/audio/touch/keyboard works). Would be nice to see something newer than froyo on this phone, so I'm posting whatever info on it while learning things in the process.
EDIT:
Not sure if Sharp will update the phone to Gingerbread, they havent released a update.zip for restoring the stock Froyo image yet. The device can definitely run Gingerbread, I'm playing with Z71 libs on a hybrid ROM that boots and (aside from phone/data/wifi/networking and screen timeout issue) runs rather quickly and smooth. I've been trying to contact Sharp about this device, but havent heard back yet. Guess I'm asking the wrong questions lol.
Kernel notes revisited
UPDATE: re-uploaded what was built with the modules for testing (previously only uploaded zImages)
Added some notes when I tried building the kernel incase anyone's interested - here. I've uploaded a test mock up of a device/vendor tree. The kernel config off the device as well as some test kernels (zImage only) built from the cm-kernel source. android-msm-2.6.35-unified and android-msm-2.6.33-ds
The device tree actually came from the ClockWorkMod builder site iirc, modded with some Z71 bits (to make the vendor side). Hopefully this helps anyone testing, as I havent had time to play with source building much (working on fixing bugs in the CM6 test port).
Updated ROMs (Froyo based)
DISCLAIMER: These are testing roms, they work pretty well for me - but always backup before flashing anything. Not responsible if sliding open the keyboard rips the fabric of time. WIth that out of the way...
I've uploaded 2 roms for the Sharp FX Plus (ADS1) - one is based off the stock 2.2.2 (Holo launcher, init,d, etc..) second rom is an updated version of the Z71 port I've been playing with (more on those here)
Downloads:
stock-based 2.2.2-acemod4
cm6.1.2-port-beta7
modified/slimmed google apps package
Found a user setting up official cyanogenmod support, thanks to rnorris. The github repo for the sharp fx plus ads1 is at.. more information here
https://github.com/rnorris97/sharp-ads1
I also set one up for testing unofficial device and vendor trees out for the ADS1
https://github.com/acebox/sharp_ads1_device_vendor_test
Good times for the little droid!!
Sent from my cm10-A500 using xda app-developers app
GPL Source?
Well, found out Sharp sold all rights to the FX Plus ADS1 to PCD Phones. In an email back form Sharp they refered me to asking PCD Phones about the source - PCD referred me back to Sharp. I've forwarded my emails from Sharp's support stating to ask PCD in hopes that they'll reply.
Hopefully they'll know something about the 2.6.32.9-perf kernel sources, that would definitely help with developing Android for this device from source.
More information on that here
AmauryRR said:
Well, found out Sharp sold all rights to the FX Plus ADS1 to PCD Phones. In an email back form Sharp they refered me to asking PCD Phones about the source - PCD referred me back to Sharp. I've forwarded my emails from Sharp's support stating to ask PCD in hopes that they'll reply.
Hopefully they'll know something about the 2.6.32.9-perf kernel sources, that would definitely help with developing Android for this device from source.
More information on that here
Click to expand...
Click to collapse
Any news? I'm interested in this phone.
deofavente said:
Any news? I'm interested in this phone.
Click to expand...
Click to collapse
Unfortunately none, I've been trying to get some information from either Sharp or PCD Phones on the modified kernel source and no dice. They were pointing to eachother, and being very helpful unfortunately.
It is a nice phone, and I would like to see what can be done from source vs porting roms. Definitely still some potential for the lil slider droid!
Hopefully something pops up, I've been moving around so if something pops up I'll dust mines off and get back to playing with it.
Rom Download Link ALL BROKEN....
i'm Try to download stock moded rom and cm6 rom.but download link all Broken...
all link broken please some upload sharp ads1 room and als its procedure to flash my phone have booting problem not starting sharp logo and restart i make the hardreset but still same problem.........
Related
I Was Helping another member get a rom working for the 6.35 radio sapphire and thought I'd look into making cm7 run better on our new radio magics, I've had it compiling for a long time now but it was slow and laggy and several things were broken. So I concentrated on DietGingerbread.
Well I succeeded this weekend at making it run ok and everything is working as it does on any other cm7 phone install.
It has my 710 kernel with 245/528 as default. (updated kernel, added 352000 to cpu freq table)
You must have 1.76.2007 spl
You should have 6.35.16.19 radio
cwm-carz-v4.0.1.4-0820-recovery, RA's hero recovery on sapphire does not work
install the rom
install gapps (optional)
Custom MTD explained below. (optional)
________
New Sept 30
Fixed merge issue in frameworks/base, fixes settings for lockscreen and a few other quirks
2.3.7 now
cm-7.1.0-09302011-6355Sapphire
________
New Sept 28
Latest cm7 source, a few changes, unlock bubbles are nice
New kernel with many changes, it has great battery life again, only 3% drop overnight now, 40 hours 35 minutes on battery and I have 18% left still, no problems over a weeks use.
Gapps package has the new market now, the old one auto updated to the new one every time for me anyways
Everything is on Andriodspin now, nice fast servers
cm-7.1.0-09262011-6355Sapphire (I didn't wipe and it works perfectly, your mileage my vary)
--------------
Aug 20
2.3.5, CM teams updates merged and tested
New kernel
Updated power profile (not sure if it affects battery or not)
Incall ui off by default, you can enable in settings
Off animation is not on by default anymore, you can turn it on in settings (it's still buggy for me anyways, I need to rewrite the code so it isn't using gles2.0)
Led settings are back (not that a lot of you noticed it gone lol, I didn't notice either)
Many tweaks for more speed, mostly in ADW
Fast enough now that I don't even overclock at all now
I forgot to add, I fixed gles1.1, neocore now works
Finally, here is the update!
cm-7.1.0-08202011-6355Sapphire-signed
This is the gapps you should use, the minimal package that way all is updated and current from the market
gapps-gb-20110613-signed.zip
*Optional*
This is the newest recovery, 4.0.1.4,(in fastboot usb mode: fastboot flash recovery cwm-carz-v4.0.1.4-0820-recovery.img )
cwm-carz-v4.0.1.4-0820-recovery (unzip and use the fastboot binary in the zip to flash, you can not flash the zip from recovery!)
--------------
New July 10 (fixed)
This is the version I have in a post in this thread (over 350 downloads and only one issue so far)
Updated kernel with camera speed improvement (not in the previously posted rom, I'll post an update package for you guys)
Fixed audio issue after taking pictures
Recovery 4.0.0.5
Rom:
CyanogenCARZ-7.1.0-07102011-6355Sapphire-signed (todays build downloaded and tested)
gpsshim replacement for wake issue http://www.multiupload.com/DKOFY5UNR3
Kernel: (update zip for those already running the july version)(not needed for above rom)
carz-2.6.34.4-07072011-signed
Google apps:
gapps_mdpi_gb_20110613_S(go to market and update)
Recovery: (fixes a wipe issue)
carz-clockworkmod-v4.0.0.5-recovery
--------------
June 21
Updated to latest cm/aosp sources, new kernel with updated usb and audio, fastest version yet. Also 4.0.0.2 recovery is working great so far.
Testing reports are good, wipe if you have issues.
CyanogenCARZ-7.1.0-06192011-6355Sapphire-signed
Carz-Clockworkmod-4.0.0.2-recovery
gapps_mdpi_gb_20110307_S
--------------
June 08
A very stable and fast release so far
New kernel with updated usb, tethering and debug notification working now
New recovery (optional)
I did not wipe but I was coming from builds that were only 1 day old, If in doubt wipe and format system.
on off animations may or may not work for you, still looking into it
cm-CyanogenCARZ-7.1.0-06062011-6355Sapphire-signed
This is not needed for anything but testing for you guys, tethering involved rom changes also.
carz-2.6.34.2-06052011-signed (flashable zip with new kernel and modules)(modules are sqf)
Recovery coming, v3.2.0....
--------------
May 23
Many updates from both the cm team and aosp (close to RC I think)
Smoother and more responsive
Updated kernel
If you have any boot issues you have to fully wipe and format system from recovery
update-cm-CyanogenCARZ-7.1.0-05232011-6355Sapphire
MD5SUM: cf815615f72cf5df900e2f8f73b57c5d
Clockworkmod-Carz-recovery-v3.1.0.1-05-23-2011.zip (newest recovery compiled with rom)
--------------
May 14 Consider this a Nightly
No wipe update if coming from may 08 version
update-cm-CyanogenCARZ-7.1.0-05142011-6355Sapphire
p
md5sum 8f3fda6dbb4b47ac3098ab28b3f29181
--------------
May 08 Stable
Sorry about the wait, I had real life work to do, also several things quit working with the cm7.1.0, 2.3.4 update, it's all good now I believe and seems much faster, This is on a clean install without custom mtd that I tested.
update-cm-CyanogenCARZ-7.1.0-05092011-6355Sapphire for mtd use, everything else is the same as the version below
update-cm-CyanogenCARZ-7.1.0-05072011-6355Sapphire
MD5SUM 137e6ec97d0498c5097bce4e42bfe102
I also started compiling clockworkmods recovery with the rom for our devices, it has all the options plus a few I've never seen before.
Clockworkmod-Carz-recovery-v3.0.2.8-05-04-2011
It's a zip with the recovery and the fastboot binary, unzip, cd to directory and:
Code:
fastboot flash recovery Clockworkmod-Carz-recovery-v3.0.2.8-05-04-2011.img
--------------
April 24
You must wipe all for this release, I used google to save settings and apps before wiping and then used it to restore everything, works now on mtd also.
If you use seo's 2.0 recovery (as I do) you have to use fastboot to erase system, as the recovery does not. (I'm looking in to fixing it)
Code:
fastboot erase system -w
Cyanogen-CARZ-7-6355sapphire-signed
Here is a new boot mtd flasher for custom MTD, I fixed cm7 so it doesn't bind data/local/download to cache/download anymore, market fixed for good on MTD
DGB-boot-v1.5.8-CustomMTD_S
(I will have a newer compile out later today with a few changes like the kernel)
--------------
Cyanogen-7-RC4-6355Sapphire
MD5SUM
Cyanogen-7-RC4-6355Sapphire-MTD
--------------
Cyanogen-7-RC3-6355Sapphire
CM7 RC3 carz v03.27.2001.2-MTD
--------------
gapps
Limited support as I'm only pulling in cm teams changes. Enjoy! Big props to all of Cyanogenmods team.
For market to work on AutoMTD for now, open terminal
on phone
Code:
su
cp -a /dev/cache/download /cache
on comp
Code:
adb shell
su
cp -a /dev/cache/download /cache
New Nightlies
--------------
update-cm-CyanogenCARZ-7-04062011-2-NIGHTLY-DS-signed.zip
MD5SUM f005d14bd708403ff92dafba475837ff
update-cm-CyanogenCARZ-7-04062011-2-NIGHTLY-DS-signed-AutoMTD.zip
MD5SUM ce91ba7861de46e9e52bd12c8d39ecb9
I have no long movies, please check and see if they work now
--------------
update-cm-CyanogenCARZ-7-04022011-NIGHTLY-DS-signed.zip
MD5SUM
update-cm-CyanogenCARZ-7-04022011-NIGHTLY-DS-signed-AutoMTD.zip
MD5SUM
--------------
update-cm-Carz2-Cyan-7-04012011-NIGHTLY-signed.zip
MD5SUM
update-cm-Carz2-Cyan-7-04012011-NIGHTLY-signed-AutoMTD.zip
--------------
update-cm-Carz2-Cyan-7-03302011-NIGHTLY-signed.zip
MD5SUM
update-cm-Carz2-Cyan-7-03302011-NIGHTLY-signed-AutoMTD.zip
MD5SUM
Custom MTD: Please know what you are doing here, read and then read some more.
first before anything run this either in term or using adb (only "df" in term)
Code:
adb shell df
you should get something like this
Code:
[email protected]:~/androidgb/system$ adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98096 32 98064 0% /dev
tmpfs 98096 0 98096 0% /mnt/asec
tmpfs 98096 0 98096 0% /mnt/obb
/dev/block/mtdblock3 174080 [COLOR="Red"]139540[/COLOR] 34540 80% /system
/dev/block/mtdblock5 169728 19832 149896 12% /data
/dev/block/mtdblock4 133120 39968 93152 30% /cache
/dev/block/loop0 1024 1024 0 100% /system/lib/modules
/dev/block/loop1 4352 4352 0 100% /system/xbin
/dev/block/mmcblk0p2 468331 8226 435120 2% /sd-ext
/dev/block/vold/179:1
7216340 7148400 67940 99% /mnt/sdcard
/dev/block/vold/179:1
7216340 7148400 67940 99% /mnt/secure/asec
look at "/dev/block/mtdblock3 174080 139540 34540 80% /system"
I used "mtd 140 3" in my mtdpartmap.txt
Download DGB-recovery-v1.5.8-CustomMTD_S.zip
These instructions are from firerats thread (recommended reading material) modified a little for my use.
Install Instructions:
Download DGB-recovery-v1.5.8-CustomMTD_S.zip
Create mtdpartmap.txt and put on /sdcard/ (use 140 3) see configuration above or in Firerats thread < recomended
reboot to recovery
nandbackup
wipe (I also "fastboot erase system -w" )
flash DGB-recovery-v1.5.8-CustomMTD_S.zip
reboot to recovery ( reboot and hold Home )
wipe again
Flash any of my custom MTD roms
reboot
Click to expand...
Click to collapse
For market to work on AutoMTD for now, open terminal
on phone
Code:
su
cp -a /dev/cache/download /cache
on comp
Code:
adb shell
su
cp -a /dev/cache/download /cache
The above is what I did and I'm running fine right now,
Below is with 130 3 mtdpartmap, I trimmed some stuff out
Code:
[email protected]:~/androidgb/system$ adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98096 32 98064 0% /dev
tmpfs 98096 0 98096 0% /mnt/asec
tmpfs 98096 0 98096 0% /mnt/obb
/dev/block/mtdblock3 133120 131772 1348 99% /system
/dev/block/mtdblock5 340736 83740 256996 25% /data
/dev/block/loop0 1024 1024 0 100% /system/lib/modules
/dev/block/mmcblk0p2 468331 10053 433293 2% /sd-ext
/dev/block/mmcblk0p2 468331 10053 433293 2% /cache
/dev/block/mtdblock4 3072 780 2292 25% /dev/cache
/dev/block/vold/179:1
7216340 7138144 78196 99% /mnt/sdcard
/dev/block/vold/179:1
7216340 7138144 78196 99% /mnt/secure/asec
169 > 340 on data
Great job!
Thank you for all your effort. I will test it right away.
May i get your permission to post this ROM in other forum? With all the credits and with a link to these thread. Only for promoting purpose.
Unkjcr said:
Thank you for all your effort. I will test it right away.
May i get your permission to post this ROM in other forum? With all the credits and with a link to these thread. Only for promoting purpose.
Click to expand...
Click to collapse
Sure but can you wait till it gets tested out a little bit first?
carz12 said:
Sure but can you wait till it gets tested out a little bit first?
Click to expand...
Click to collapse
Sure! I was thinking in testing the ROM first before doing that. Thanks
Awesome, downloading asap
Hi Carz,
Do i need to change my SPL and recovery?
Dexreyes said:
Hi Carz,
Do i need to change my SPL and recovery?
Click to expand...
Click to collapse
Not if it's what is in your sig.
carz12 said:
Not if it's what is in your sig.
Click to expand...
Click to collapse
Thanks Carz, I'm downloading it right now, will test this, looks promising!
So far it works as any other GB ROM out there. But with 2 differences for now: It doesn´t support App2SD (i really hope you enable this feature) and... it´s faster than the others! Great job Carz!
Unkjcr said:
So far it works as any other GB ROM out there. But with 2 differences for now: It doesn´t support App2SD (i really hope you enable this feature) and... it´s faster than the others! Great job Carz!
Click to expand...
Click to collapse
Have you turned on jit yet?
Sent from my Dream/Sapphire using XDA App
i got install error, status 7 when installing this rom. Please look into this.
hellokittyr said:
i got install error, status 7 when installing this rom. Please look into this.
Click to expand...
Click to collapse
Do you have 1.76.2007 spl?
Sent from my Dream/Sapphire using XDA App
Unkjcr said:
So far it works as any other GB ROM out there. But with 2 differences for now: It doesn´t support App2SD (i really hope you enable this feature) and... it´s faster than the others! Great job Carz!
Click to expand...
Click to collapse
It supports apps2sd (native) and supports app2ext if I add the script
Sent from my Dream/Sapphire using XDA App
thx carz, testing it right now...
Just installed, replacing GBRider, so far so good, very speedy, everything seems to work.
Excellent work carz, as usual!
---
Update: seems I spoke too fast, the root portion seems to have a problem. SuperUser/Titanium don't work (exception with 'failed running exec() on SU' appear in the log
Reset your phone - it helped me -
carz - rom is very fast like 4 GB2.3 - one qestion, how about battery drain?
[email protected] said:
Just installed, replacing GBRider, so far so good, very speedy, everything seems to work.
Excellent work carz, as usual!
---
Update: seems I spoke too fast, the root portion seems to have a problem. SuperUser/Titanium don't work (exception with 'failed running exec() on SU' appear in the log
Click to expand...
Click to collapse
So far so good, are there any plans on a MTD friendly version?
orange_24 said:
Reset your phone - it helped me -
carz - rom is very fast like 4 GB2.3 - one qestion, how about battery drain?
Click to expand...
Click to collapse
Em, could you specify what do you mean by 'reset' ? Wiping? Rebooting?
I started with a wipe, and rebooted since... Didn't help.
install Completed but reboot to recovery ?
I assume no liability for any damage to your phone!
You can use my complete rom or parts of it to make your own rom. Only post a small thanks on your owm thread.
Big thanks to: iaio72, spear1403, tgzw, Quarx, Simondo, ein1002, santimanuel, epsylon3 and ...
Language support for final 4.0 --> da, de, el, en, es, fi, fr, hr, hu, id, it, nb, nl, pl, pt, pt-BR, sv, th, ti, vi, zh_CH, zh_TW + arabic* and ru*
MS2Ginger 4.0
- based on 4.5.2-109-DHT-25 - Android 2.3.6 blur lite rom
- support for Defy, Defy+, Milestone 2, Bravo
- MS2Ginger4 can used as 2nd-system (tested on GB kernel only) !! system image file have to be >= 350 MB
- multibootmanger app by royale1223
- new bootmenu 1.1.8, CWM 5.0.5/6, multiboot big thanks to m11kkaa
- 2 way to boot the rom: normal and via 2nd-init (default)
- new reboot option form cm7.2 --> trigger: all keys at the same time vol- , vol+ , power (only tested on Defy)
- disabled blurhome rotation
- button backlight can set from 10-100 % via build.prop
- mmcfix from CM7
- CPU settings default safe 30/300 38/600 {48/800} 58/1000
- Camera will work on SOC and Bayer camera (green* and red)
- better camera support for bayer camera
- new 720p record* and play (Milestone 2 - Android 2.3.6 files)
- 720p record in m4v (h264 can be enabled via build.prop)
- Milestone 2 froyo camara app for SOC camera (fixed green strips)
- BlurHome from Milestone 2 - 2.3.6 (no widget updating bug)
- Battery min. 2-5 mA/h
- no wifi, apn, vpn bugs
- wifi channels 12, 13, 14 enabled
- bootmenu + cwm (vsel4/clk4 added) "did not work for SOC camera with greenbreadMOD"
- bootmenu with Stable, Custom, Stock-Recovery
- call record libs
- init.d support
- zipalign at boot
- ramscript
- backlight button fix for Defy with bayer camera (can removed via optional patch)
- deepsleep support
- max 10 finger multitouch
- support for farsi-arabic, hebrew (thanks to MMarv)
- CyanogenMod-settings not finished (alpha) - sorry, will try to fix it if i have more time.
(* via greenbreadmod for MS2Ginger4.0 and if you never flashed a Android 2.3.6 full sbf with bl7)
(* 720p record only for Bayer camera Defy and Milestone 2)
Download: ROM, BlurApps, Greenbread: (MS2Ginger4.0.zip, BlurApps-MS2Ginger4.zip,Milestone2patchMS2Ginger4.0withbaseband.zip )
Mirror 1 (google)
Mirror 2 (Dev-Host)
More information for BlurApps --> LINK
Soft-sim-unlock for MS2Ginger 4.0
based on Dabb guide: http://forum.xda-developers.com/showthread.php?t=1447950
Install View attachment 1129769 via CWM.
If you like MS2Ginger feel free to donate! Donations will be used to purchase a Defy with SOC camera (green lens)
Bugs and problems Reporting: http://code.google.com/p/ms2ginger/issues/list?can=1&q
- wifi bug like all 2.3.6 Motorola roms http://forum.xda-developers.com/showthread.php?t=1502817
(fixed, disable unlimited lease time for IP adress on your rooter)
Timeline:
19.06.12 - MS2Ginger 4.0 released
05.02.12 - MS2Ginger 3.0 released
Patch and updates for current release
none for MS2Ginger 4.0
HOW to INSTALL:
To begin:
Put the Nandroid backup folder MS2Ginger on the SDCard in this folder: /sdcard/clockworkmod/backup
Put "Milestone2patchMS2Ginger4.0withbaseband.zip" to the root of your sdcard
Put "Milestone2-GB-kernel-update.zip*" to the root of your sdcard (only if you have a froyo kernel)
-------------------------------------------------------
Root your Milestone 2 and Install BOOTMENU - CWM for Milestone 2
REBOOT
run 2nd-init (voldown on blue LED)
Go to "Recovery"
Go to "Latest or Stable or Custom Recovery"
"wipe data and cache"
Go to "Backup and Restore"
Go to "Advance Restore"
Select "MS2Ginger4.0"
"restore system"
Go to "install zip from sdcard"
select and install "Milestone2patchMS2Ginger4.0withbaseband.zip"
"Install "Milestone2-GB-kernel-update.zip" via install zip" (only if you have froyo kernel)
reboot
Booting up can take a while, max is about 10 minutes.
Team:
- walter79
- spear1403 (theming)
- santiemanuel
- Defy red lens tests spear1403
- Defy greens lens tests luciferps and Cristi_10
- Defy plus tests Dollo73 and free2live
- Milestone 2 tests Carolinux and Motodoido
Translation Team: (each language max. 4 person) View attachment 806172
Brazillian Portuguese: pupiloalpha , Cassinander , filipeazev
Bulgarian Auris 1.6 vvt-i
Farsi: MMarv
Hungarian: szabof1 , balika01
Polish: yackoo , szacuken , Antszej
Serbian: atomskasarma
Spanish espaciosalter20
Spanish-Argentina YaPeL
walter79 said:
Welcome.
The idea:
Defy is running Milestone 2 Android 2.2.2 ROMs. (DACH retail based)
So maybe we could make a working Gingerbread for Milestone 2.
- Defy has rooted only Android 2.3.4 /system nandroid-backup http://forum.xda-developers.com/showpost.php?p=14793844&postcount=8
- it is also possible to run 2nd-init on milestone 2
- read this (Defy 2nd-int + froyo kernel + Gingerbread-system working) http://forum.xda-developers.com/showthread.php?t=1130656
- i think it could be possible to get gingerbread working on milestone 2
- basband should be change with original milestone 2 files
- /lib/hw/ from milestone 2 needed
- kernel from milestone 2
- fix for camera
Whats your opinion?
Click to expand...
Click to collapse
I'm sorry to kill your optimism, but we are unable to flash onto /system for now. Big files at least..
Did clockworkmod not work?
http://www.gamaze.com/blog/2010/11/installing-clockworkmod-recovery-on-motorola-milestone-2/
walter79 said:
Did clockworkmod not work?
http://www.gamaze.com/blog/2010/11/installing-clockworkmod-recovery-on-motorola-milestone-2/
Click to expand...
Click to collapse
It works, it's just that.. it doesn't flash big update.zip's, which overwrite the whole system. Problem could be caused by us not having a recovery build specifically for our devices.
But nandroid backup works, or?
Mikevhl said:
It works, it's just that.. it doesn't flash big update.zip's, which overwrite the whole system. Problem could be caused by us not having a recovery build specifically for our devices.
Click to expand...
Click to collapse
So build one: https://github.com/koush/Droid2Bootstrap
Edit: Check this out "use an update.zip that waits a bit longer for the system to settle then unmounts tmp and remounts /"
dangpzanco said:
So build one: https://github.com/koush/Droid2Bootstrap
Edit: Check this out "use an update.zip that waits a bit longer for the system to settle then unmounts tmp and remounts /"
Click to expand...
Click to collapse
Nice. Will try to get a clean nandroid backup of my /system, unyaffs it and create my own update.zip formatting /system and using this trick to see if I it works.
r2beta0 said:
Nice. Will try to get a clean nandroid backup of my /system, unyaffs it and create my own update.zip formatting /system and using this trick to see if I it works.
Click to expand...
Click to collapse
Lol, I think it's a lucky shot finding this...
Sent from my Milestone 2 XDA App
Hey, what happens if I flash Defy's SBF on M2? Besides other problems is it possible to enter bootloader mode and flash another sbf, or it will corrupt the device?
I didn't, but I saw it was a prerequisite for the Rom posted here, so if there's theorical trouble, then I won't try.
Also I found out that Droid 2 bootloader image has the same first and last bytes as M2 (but different check sums), and Defy's is little different.
dangpzanco said:
Hey, what happens if I flash Defy's SBF on M2? Besides other problems is it possible to enter bootloader mode and flash another sbf, or it will corrupt the device?
I didn't, but I saw it was a prerequisite for the Rom posted here, so if there's theorical trouble, then I won't try.
Also I found out that Droid 2 bootloader image has the same first and last bytes as M2 (but different check sums), and Defy's is little different.
Click to expand...
Click to collapse
Did not work.
dangpzanco said:
Hey, what happens if I flash Defy's SBF on M2? Besides other problems is it possible to enter bootloader mode and flash another sbf, or it will corrupt the device?
I didn't, but I saw it was a prerequisite for the Rom posted here, so if there's theorical trouble, then I won't try.
Also I found out that Droid 2 bootloader image has the same first and last bytes as M2 (but different check sums), and Defy's is little different.
Click to expand...
Click to collapse
I don't think RSD Lite will allow you to do that. Even if it does, I don't think it's a good idea since it may replace your bootloader potentially bricking your phone.
r2beta0 said:
I don't think RSD Lite will allow you to do that. Even if it does, I don't think it's a good idea since it may replace your bootloader potentially bricking your phone.
Click to expand...
Click to collapse
Yeah, I thought about that bricking stuff... (maybe linux/mac sbf_flash would flash it)
Did the "update.zip that unmount tmp and remounts /" work?
Sent from my Milestone 2 XDA App
dangpzanco said:
Yeah, I thought about that bricking stuff... (maybe linux/mac sbf_flash would flash it)
Did the "update.zip that unmount tmp and remounts /" work?
Sent from my Milestone 2 XDA App
Click to expand...
Click to collapse
Not yet, still working on it on my free time. Unfortunately 'free time' is a scarce resource
Maybe if you point the update-script to another script:
Code:
#!/system/bin/sh
#This was in Apex 1.4.1 /etc/init.rc folder (wait for system to settle?)
sleep 24s
#unmount tmp
busybox umount /tmp
#remount /
busybox mount -o remount -rw -t rootfs /
Will it work?
dangpzanco said:
Maybe if you point the update-script to another script:
Code:
#!/system/bin/sh
#This was in Apex 1.4.1 /etc/init.rc folder (wait for system to settle?)
sleep 24s
#unmount tmp
busybox umount /tmp
#remount /
busybox mount -o remount -rw -t rootfs /
Will it work?
Click to expand...
Click to collapse
First attempt failed. I had some problems formatting /system partition. The only way I could get it to format was through Recovery Menu. Maybe the problem is reformatting the system. The command mount("MTD", "system", "/system") also doesn't work. I'm starting to think that Motorola messed with the file system. Will try again using delete_recursive instead of format.
There is any d2 / d2g rom based on GB?
With all the problems developers were facing lately, I guess motorola add the same "weird" protections in m2 2.2 to GB d2 rom
It's very hard to make a custom ROM with all these protections and without knowing what happens when phone tries to boot. All we get is the damned M logo and no info at all. Without some output from the phone everything we can do is guessing.
I was reading that new fission roms based on GB (for d2), were facing the "motorola logo" stuck problem. That´s why the developer gave up.
But, like you say, there is no way to know if it´s the same problem.
I have no knowledge at all on android platform. I´d stuck on winmo 6.
If you need some testing, I can try, there is nothing more I can offer
Second attempt failed. It may have nothing to do with format or system file. I'm really clueless Jut the M logo again. Maybe the /system protection checks for some date/time on some random file? Will reflash with RSD and 'touch' everything in /system to see if the damned thing still boots.
Did you compare the hash of apex files to the moto original files?
Kogan Agora 10" 8GB Tablet - Powered by Android ICS!
kogan.com/au/buy/10-inch-tablet-pc-android-8gb/
Hi All, thought I'd put this here for anyone having trouble with this device.
had it a few weeks, accidentally let the battery drain.
Charged it up tried to boot, but unfortunately it was stuck in a boot loop.
Kogan support didnt even get back to me,
in order to solve, I followed the eken a90 steps to recover:
futeko.com/navpage/support.php#ekena90
(same device rebranded)
hope that helps someone out there having the same issues.
I also tried a number of different firmwares with little succes - touchscreen refuses to work ie:
slatedroid.com/topic/33373-rom-cm9-nightlies/
Guessing at this stage you haven't herd back from Kogan?
I killed boot but have managed to install a October 2012 dated firmware to it via LiveSuite.exe. The only problem I have found is the wifi wont turn on. I'm going to try the version on the site you posted tonight.
I've just sent a request through asking for a link to their Kogan branded firmware. Doesn't really matter but I may want to revert back at some stage.
Have you had any success with Cyanogen MOD? I'm going to have a go at installing it tonight but not sure what recovery to go for.
Cheers,
Brian
I am in need of a stock firmware, a backup rom or a good compatibility patch that works with cm9 or cm10 that has working wifi.
Kogan's reply to my email.was that they did not have access to the original firmware. Less than helpful and it took 2 weeks to get that answer.
Kogan Agora 10" tablet
I've had the same issue with my Kogan Agora 10" tablet - had a boot-loop issue and followed the above instructions to flash my tablet.
The flashing worked fine and the tablet is up and running again, but, the wireless will not turn on. (like the issue stated above).
I'm wondering how you got on... did you find a way to get the wireless to turn on?
Is there a newer flash version or a patch that gets the wireless going?
I'd really appreciate some help with this (thanks for the help so far ... got the tablet up and going)
Chrys
I've got one of these too - the 16GB version (KATBL10A16DA)
I have attempted to flash clockworkmod recovery to the device without success (Says the update installed OK, but it always boots to the standard recovery).
At the moment I just want to get it rooted - not so concerned about a new ROM at the moment. The stock one is not all that bad.
Mine seems to be missing the english dictionary, so I need access to the system folder to put one in.
hybiepoo
I have used Tasselhof root script for AllWinnerA10 perfectly for rooting, dont use super one click it wont root properly. As for clockworkmod I had the same problem, this was solved after i rooted the tablet first ( not sure if it needs to be rooted first but it worked )
If you could take a backup with clockworkmod after it is all setup and post a link that would be awsome as my tablet had the bootloop issue before i could make my backup and now im without wifi which sucks and kogan will not give a firmware link.
hope all this helps
Thanks wvusrj, that root worked fine after adding the drivers.
Now my dictionary is also fixed after using the files in this thread:
http://forum.xda-developers.com/showthread.php?t=1498006
Clockwork mod is still showing an unsupported device. Did you manually install clockwork recovery or do it through the app?
If you installed manually, did you use it from an A10 device, same as the root thing, or some other way?
For Clockwork mod you will have to install it through the original recovery. Look for cwm_recovery_6.0.1.2_a10.zip or cwm-20120615.zip. I can not remember the exact process but this should get you started in the right direction. You wont be able to install it from in the android os it has to be in the original recovery.[/I][/I]
Ok, I could not get the recovery to install using quite a few methods, and I could not get a dump of my recovery image either, just in case I broke something.
I managed to manually install a recovery image and back up my own first, but now my device won't boot. I just see the android mascot in the middle of the screen and it goes no further.
The strange thing is - I did manage to get it into the new recovery once, but after rebooting it now seems busted.
This is what I did. You need root access.
To backup my boot and recovery partitions:
- Using either a terminal emulator, or adb shell: cat /cache/recovery/last_log
Look for a list of partitions, something like this:
Code:
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/nandc (null) 0
2 /system ext4 /dev/block/nandd (null) 0
3 /data ext4 /dev/block/nande (null) 0
4 /misc emmc /dev/block/nandf (null) 0
5 /recovery ext4 /dev/block/nandg (null) 0
6 /cache ext4 /dev/block/nandh (null) 0
7 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/nandj 0
To backup recovery and boot to your sd card:
dd if=/dev/block/nandg of=/sdcard/recovery.img
dd if=/dev/block/nandc of=/sdcard/boot.img
I won't post how I flashed recovery yet unless I can fix my issues.
Ok, so something I did stopped the device from booting into recovery, or the OS.
Unfortunately, I had to flash the software from the EKEN website, which means I don't have the original ROM any more either.
Wifi won't turn on for me either - obviously it needs a different driver. Pretty useless tablet now isn't it? :/
Right. I have managed to get a recovery working.
Please use cwm-20120615.zip.
https://www.dropbox.com/s/6ce36p1z4ofpevn/cwm-20120615.zip
Unzip the recovery image, and copy recovery.img to your internal or external sd card.
Start adb.exe
A link to a working adb for our devices is here:
https://www.dropbox.com/s/22oqm507i...ild.Prop,_&_Tweaks_Script_-_AllWinner_A10.rar
Extract it, open a cmd prompt in the extracted dir.
If you used external sd, use the following command:
Code:
cat /mnt/extsd/recovery.img > /dev/block/nandg
If you used internal sd, use the following command:
Code:
cat /sdcard/recovery.img > /dev/block/nandg
Once the image is uploaded, we need to boot to recovery.
Code:
adb shell "echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1 conv=sync; sync; reboot"
Once it's booted into recovery, use the volume buttons to move down to backup and restore.
Use the power button to select the backup option.
After you have backed up, zip the contents of the backup, and put it on a dropbox somewhere so those of us that have lost the Kogan firmware can try a restore
NOTE:
You may want to do a backup first, then copy the backup to your PC.
Restore to factory defaults so none of your personal stuff is in the backup that you put online.
Then you can restore your original backup afterwards.
---------- Post added at 10:21 AM ---------- Previous post was at 10:12 AM ----------
If somebody on a stock ROM could also run the following command in ADB, that would be handy for us to work out what's missing for the wireless device.
Code:
adb shell lsmod
This will list the modules (drivers) currently loaded.
Here is the output from the ROM I'm using:
Code:
Script - AllWinner A10>adb shell lsmod
bma250 6806 0 - Live 0xbf0b1000
rtl8150 8910 0 - Live 0xbf0aa000
mcs7830 6557 0 - Live 0xbf0a4000
qf9700 8513 0 - Live 0xbf09d000
asix 22500 0 - Live 0xbf092000
usbnet 23745 3 mcs7830,qf9700,asix, Live 0xbf086000
mma7660 5671 0 - Live 0xbf07c000
sun4i_vibrator 2278 0 - Live 0xbf078000
sun4i_csi0 26905 0 - Live 0xbf06d000
gc0308 14208 1 - Live 0xbf065000
gt2005 16234 1 - Live 0xbf05d000
videobuf_dma_contig 5659 1 sun4i_csi0, Live 0xbf058000
videobuf_core 18067 2 sun4i_csi0,videobuf_dma_contig, Live 0xbf04e000
ft5x_ts 45249 0 - Live 0xbf03e000
mali 130083 8 - Live 0xbf011000
ump 42006 9 mali, Live 0xbf000000
I have installed CM10 to my device and then installed the 907c_compatability_1.2.0.zip patch.
The patch got the touch screen working, but I still can't turn on WIFI.
On top of this, there is also an SD card issue that I need to resolve.
I'm sure WIFI would be fixed by adding one of the other zips... just need to work out which one.
This is what I see when I try to enable wifi.
Code:
<7>[ 5235.303542] ##########rtw_suspend_lock_init ###########
<6>[ 5235.309607] usbcore: registered new interface driver rtl8192cu
<7>[ 5235.453172] sw_usb_enable_hcd: usbc_num = 2
<7>[ 5235.457459] WRN:L872(drivers/usb/host/ehci_sun4i.c):ERR: not support sw_us
b_enable_ehci
<7>[ 5235.465517] WRN:L806(drivers/usb/host/ohci_sun4i.c):ERR: not support sw_us
b_enable_ohci
<7>[ 5235.480158] rtl8188eu driver version=v4.1.1_4235.20120606
<7>[ 5235.485568] build time: Aug 15 2012 09:39:59
<7>[ 5235.489835] ##########rtw_suspend_lock_init ###########
<6>[ 5235.495935] usbcore: registered new interface driver rtl8188eu
<7>[ 5239.913418] +rtw_drv_halt
<7>[ 5239.916057] ##########rtw_suspend_lock_uninit###########
<6>[ 5239.921582] usbcore: deregistering interface driver rtl8192cu
<7>[ 5239.928223] -rtw_drv_halt
<7>[ 5239.930913] sw_usb_disable_hcd: usbc_num = 2
<7>[ 5239.935183] WRN:L819(drivers/usb/host/ehci_sun4i.c):ERR: not support sw_us
b_disable_ehci
<7>[ 5239.943308] WRN:L753(drivers/usb/host/ohci_sun4i.c):ERR: not support sw_us
b_disable_ohci
Not sure if it means we're using the wrong driver or what.... if we can get someone to run the lsmod on the original firmware, we should be able to see which hardware it's using.
I must have tried a dozen ROMs now... none of them will allow me to enable wifi.
Final update for tonight.
I definitely believe this is a driver issue. Most of these clone tablets (there are heaps of them) seem to use the realtek 8188 range of devices, and those drivers are included in all the ROMs. This one does not use a realtek.
This is the chip that we need to identify:
{
"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"
}
It's very small, but it seems to read
iNet i10
T0C601C
1226
Finally some good news. I've found a ROM that works.
It's currently uploading to my dropbox at home, so I'll post a link this afternoon.
Now we might be able to work out which drivers are required, and get them included in the CM9 and/or the CM10 ROMs.
Damn there is an issue with this ROM too. Changes are not saved during reboot for some reason.
It might be an issue with partitions - it might be writing changes to a partition that is wiped every boot.
Anyway, I'm going to try and get some drivers included in one of the CM ROMs.
Ok, this ROM is not perfect either. It resets after every reboot, so no changes are saved. Must be an issue with partitions I think.
At least it contains the right drivers. Feel free to test with it.
https://www.dropbox.com/s/2py7exhuljdqw26/930i.zip
hybiepoo said:
Final update for tonight.
I definitely believe this is a driver issue. Most of these clone tablets (there are heaps of them) seem to use the realtek 8188 range of devices, and those drivers are included in all the ROMs. This one does not use a realtek.
This is the chip that we need to identify:
It's very small, but it seems to read
iNet i10
T0C601C
1226
Click to expand...
Click to collapse
Same as on mine. Imagine this would be the same with all Kogan devices. Would be good to find another clone for their image.
hybiepoo said:
Ok, this ROM is not perfect either. It resets after every reboot, so no changes are saved. Must be an issue with partitions I think.
At least it contains the right drivers. Feel free to test with it.
https://www.dropbox.com/s/2py7exhuljdqw26/930i.zip
Click to expand...
Click to collapse
I'll give this a try tonight if I have a spare few minutes.
Cheers for sharing.
I also did a bit of serching based on the revision of the board.
I found this Kraun KT.A1
I have also read a forum talking about another version of the tablet posting and someone having the same issues with CM10 that we have.
Soo... The firmware posted on the site linked may bring wifi back. As long as it has English.. This is a Italian release tablet.
Ok, re-imaging without format seems to have fixed it, and all my changes are there. Weird.
I have a feeling that when I installed busybox it screwed with the storage.
So at least we have a ROM that works!
Hey Guys,
mkasick released in his thread a fix for the mounting problems in Android >= 4.2.
Description of the issue:
mkasick said:
Android >= 4.2 breaks Dalvik-apps that mount file systems to be shared with other apps. This includes CifsManager, Mount Manager, essentially anything that mounts cifs shares, FUSE file sytems, etc. The symptom is that the mounted contents appear fine to app that peforms the mount operation (assuming the app itself provides the ability to browse the contents), but every other app only sees an empty directory at the mount point.
Click to expand...
Click to collapse
As I said - mkasick released a solution - so I compiled my own kernel. Now we can again easy mount cifs and others! All old apps should work. Only limitation: the mount point needs to be outside of /storage (and also /mnt/sdcard/). Fix for this: Mount within /data/media/0 -- android will redirect the mount so you can access the mounted-files from this folders.
The kernel is a "stock kernel" and also includes:
mkasick Patch
Built-In cifs, md4, utf8, nfs, f2fs (Since V17)
kexec hardboot patch (The full patch, allows boot as host and as guest)
As Modules: .ko: snd-usb-audio and all of its devices (Installed, but not modprobe'd since V17)
[Since V16/Android 5.0.2] Fix for baseband_xmm_power wakelock on tilapia (see Hints and Bugs since V16 / Android 5.0 / Lollipop ; for Android 4.4.4 see this post)
mkasick recommends in his thread to patch dalavik, but for the stock-roms it is easier to patch the kernel.
Known Bugs:
Since Android 5.0.X/V16: SELinux is now blocking the access of cifs/nfs even in read. Also nfs isn't loaded at boot time anymore. For more information look below.
Since Android 4.4.X: There is a known bug with mounting cifs (you can't write). The solution is (try at your own risk) here. If you want to do this workaround at boot-time, you can flash the zip linked here.
With SuperSU >= 1.50 && < 1.65 the mounted folders are empty. Please update! (For more Info see hide-box "SuperSU Information" below)
Hints and Bugs since V16 / Android 5.0 / Lollipop:
SELinux, cifs and nfs
SELinux is since Android 5.0 "more" enforced. Because of that, even the read on nfs / cifs isn't working anymore without disabling selinux by "setenforce permissive" as root. Be careful, disabling selinux is an security hole. USB is still working with selinux at enforcing.
Because of the same reason the nfs and sound modules are not loaded at boot anymore. Because I don't want to mess around with selinux at boot time, you can modprobe them yourself, if you need it. Run the following commands as root to use nfs / sound modules (a installed busybox is required):
Activate sound modules:
Code:
busybox modprobe snd-usb-audio
Activate NFS File System:
Code:
busybox modprobe nfs
Workaround for baseband_xmm_power wakelock
Some people have massive issues with tegra3 + cellular devices with the baseband_xmm_power wakelock. The wakelock drains all the battery. With V16 I included a possible fix for this. The fix is based on the work of jfmcbrayer and Sgt. Meow. By default, the fix isn't active and the kernel uses the stock behaviour.
If you want to disable the wakelock entirely, you can flash this zip: CWM_activate_baseband_xmm_power_wakelock_workaround_vorcers_rev2.zip
I used this this workaround for some time with Android 4.4.4 and I had no issues. Well, I did not test the mobile data... Please tell me, if something isn't working (And the workaround is active). I just wanted to get rid of that battery drain. I was on flight mode all time.
Technical:
The workaround is enabled by echoing a number into a baseband_xmm_power module parameters:
Code:
echo 0 > /sys/module/baseband_xmm_power/parameters/bb_timeout
Possible Values:
< 0 - disable workaround, stock behaviour [Default (-1)]
= 0 - disable the baseband_xmm_power wakelock completely
> 0 - how long the wakelock can stay active, every time the wakelock is triggered, in 10ths of a second. Meaning: Value 5 = 500 ms, 10 = 1 second, 20 = 2 seconds....
You find the patch I used in the actual Patchset. (Included since Android 5.0.2)
Downloads
(Kernels since v8 are only tested by me for the 3G version (tilapia) - but should also work with wifi (grouper).)
The flash of the kernel shouldn't break anything, but I recommend to backup your system.
Download-Links for grouper and tilapia:
Android 5.1: Kernel: Grouper: boot-grouper-vorcers-gf5d7b8b-v18.zip ; Tilapia: boot-tilapia-vorcers-gf5d7b8b-v18.zip
Android 5.0.2: Kernel: Grouper: boot-grouper-vorcers-g6ff7a51-v16.zip ; Tilapia: boot-tilapia-vorcers-g6ff7a51-v16.zip
Android 4.4.4: Kernel: Grouper: boot-grouper-vorcers-g1e42d16-v13.zip ; Tilapia: boot-tilapia-vorcers-g1e42d16-v13.zip
In V11 the kernel modules are placed in /data instead of /system. If you are upgrade from < V11 and you want to delete the modules in /system, you can delete the folder "/system/vorcers_kernelmodules" manually, or you use this CWM-Zip to delete.
Download-Links only for grouper: (try on tilapia at your own risk)
Android 4.3: Kernel: boot-grouper-vorcers-g1e8b3d8-v7.zip Kernelmodules: integrated
Android 4.2.2: Kernel: boot-grouper-vorcers-g05b777c-v4.zip Kernelmodules: kernelmodules-vorcers-g05b777c-v2.zip
Extra-Links:
My Repository for this Kernel (also contains old versions): https://www.mediafire.com/folder/j9iocde4l20c7/Kernel
Stock-Kernels: https://www.mediafire.com/folder/d3mj3k3v61jzu/Stock Kernels
A zip which contains the Patches and modifications I made: https://www.mediafire.com/folder/kvdmcsl16x0ox/Sources
Integration wishes for new kernelmodules to support new hardware are always welcome (you will get .ko's for my kernel)
Have a lot of fun!
Sources:
http://forum.xda-developers.com/showthread.php?t=2106480 (Mount fix)
http://forum.xda-developers.com/showthread.php?t=2104706 (Hardboot patch)
http://source.android.com/source/building-kernels.html
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://nek0s.blogspot.de/2012/12/nexus-7-ramdisk.html
Changelog:
Android 5.1: gf5d7b8b-v18 (2015/04/10)
- Switched to gf5d7b8b / android-tegra3-grouper-3.1-lollipop-mr1
- Build-In nfs
- Disabled Module auto loading for snd-usb modules -- are still installed
- Added f2fs Filesystem, untested, standard is ext4
Android 5.0.2: g6ff7a51-v16 (2015/01/31)
- Switched to g1e42d16 / android-tegra3-grouper-3.1-lollipop-release
- Added Workaround for the baseband_xmm_power wakelock on tilapia (Please see "Hints and Bugs since V16 / Android 5.0 / Lollipop" for more information)
- NFS and Sound Modules are not loaded anymore by default but can loaded manual via "busybox modprobe nfs" / "busybox modprobe snd-usb-audio".
Android 4.4.4: g1e42d16-v13 (2014/06/06)
- Switched to g1e42d16 / android-tegra3-grouper-3.1-kitkat-mr2
Android 4.4.3: g4776c68-v12 (2014/06/03)
- Updated Grouper and Tilapia ramdisks for Android 4.4.3.
Android 4.4.2: g4776c68-v11 (2014/01/11)
- To save space in /system, the kernel-modules had been moved from /system/vorcers_kernelmodules to /data/vorcers_kernelmodules.
If you want to delete the modules in /system, you can use this zip: CWM_delete_system_vorcers_kernelmodules.zip
- Nothing else is new
Android 4.4.2: g4776c68-v10 (2013/12/11)
- Updated Kernel Config and Ramdisks. (Both changed in Android 4.4.2/KOT49H)
Android 4.4: g4776c68-v9 (2013/12/10)
- Created separate files for grouper and tilapia (their ramdisk differ, kernel not)
Android 4.4: g4776c68-v8 (2013/12/07)
- Switched to Android 4.4: g4776c68 ; KRT16O (?) ; android-tegra3-grouper-3.1-kitkat-mr1 KRT16S is gee1a0b2 / (?)(?) android-tegra3-grouper-3.1-kitkat-mr0 (?)(?)
Android 4.3: g1e8b3d8-v7 (2013/09/01)
- Modules Support for Android 4.3
- Packed all modules inside zip...
- I go back to the old version scheme and only count up the numbers...
Android 4.3: g1e8b3d8-v6 (2013/07/29)
- Forgot somehow UTF8
- Really added /proc/config.gz
Android 4.3: g1e8b3d8-v5-km-v4 (2013/07/25)
- Switched to Android 4.3: g1e8b3d8 ; jwr66v ; android-tegra3-grouper-3.1-jb-mr2
- This kernel has also: /proc/config.gz and an loadable module support (Stock has not)
- I also provided the patchset I used for Android 4.3
Android 4.2.2: g05b777c-v4-km-v2 (2013/02/19)
v4-Kernel (boot-grouper-vorcers-g05b777c-v4.zip):
- Switched to different version schema: boot-grouper-vorcers-<android-kernel-hash>-v<count of changes of kernel (overall)> ; For the kernelmodules it is: kernelmodules-vorcers-<android-kernel-hash>-v<count of changes of kernel-modules (overall)>. This means for you: if the number is higher, there is something new Version-Number at Changelog: <android-kernel-hash>-v<count of changes of kernel (overall)> -km-v<count of changes of kernel-modules (overall)>
- Added init.d (/system/etc/init.d/) support to the kernel/init.rc. If the directory exists, the scripts inside the directory get run via "run-parts" from busybox. This means: The script need to be runable (+x) and mustn't have an file-extension.
- Removed the mount of /mounts out of init.rc (is now in an script called by init.rc)
v2-Kernelmodules (kernelmodules-vorcers-g05b777c-v2.zip):
- Made a CWM flashable package which autoloads the modules in my kernel.
Android 4.2.1: v3 - boot-grouper-4.2.2-vorcers-v3.zip : (2013/02/15)
- Switched to Android 4.2.2 - Kernel, jdq39, g05b777c, android-tegra3-grouper-3.1-jb-mr1.1
- Added Modules for OTG-USB-Sound (see kernelmodules*.zip)
Android 4.2.0: v2 (2013/01/19)
- I added a tmpfs mount for /mounts, so you don't need to do "mount -o remount rw /" and create your inital-mountpoint yourself. /mounts is writeable by all apps. (done in init.rc)
Android 4.2.0: v1 (2013/01/19)
- inital release
SuperSU Information:
Information for SuperSU Users
It seemed that SuperSU >= 1.50 && < 1.65 doesn't work correctly with this kernel. Well, the Version 1.65 seems to work again (The folders where empty after mount). The SuperSU Version 1.45 worked the best. If you want to use 1.45, you can download the old Flashable-Version here: http://download.chainfire.eu/343/SuperSU/UPDATE-SuperSU-v1.45.zip.
As I said, the version 1.65 seems to work again. It maybe can happen, that the folders gets empty, after some time. This has been noticed with Version 1.60. But 1.65 not (yet).
If you still have problems with the empty folders on my kernel, you should try superuser by koush.
koush's superuser is opensource and is the same as in cyanogenmod. And with that, the mount-technique is working without bugs: https://play.google.com/store/apps/details?id=com.koushikdutta.superuser
Some gimmick: One"click"mount-Shell-Script
Because I want to get rid of stickmount, I written a little shell-script to mount all connected devices. It is very similar to stickmount, but it supports: ext, fat32, ntfs. Well, ntfs only, if you provide the path to an ntfs-3g binary. (In the variable NTFS_BINARY) I used in the script the paragon-ntfs binary. Just install the Paragon-App.
Download V2.2: http://www.mediafire.com/download/rjmsdt06cf0cp6b/oneclickmountv22.sh.gz
Download V3: http://www.mediafire.com/download/xppx2m3awcf3oq3/oneclickmount-v3-20130221172223.tar.gz
glimmling created a tasker apk for this script. I but it still bases on v11 of the script.
from v3 on, ocm needs -m parameter. If you want the old behavior, use "-m auto"
from v3 on, ocm also mounts /dev/block/sdX partitons (e.g. /dev/block/sda), but only if my script can use a busybox with blkid with TYPE output. (I provided one)
I added in v3 an fstab-like future usable with -f <file> see my example.
Please be careful with the new v3. I works, but I would call it "beta"...
You can't run ocm >= v3 inside /mnt/sdcard. All files (except for ocm.fstab and ocm-library) need the x right. Copy the files too /data/local/, "chmod 777 *" them and run ocm from /data/local.
example for ocm.fstab.
syntax:
Code:
<device> <mountpoint> <fs-type> <options>
example:
It is is very importent that the options seperated by one space!
Code:
//192.168.100.1/username username cifs username=<username>,password=password,ro
192.168.100.1:/home/username nfs nfs nolock,ro
/dev/sda1 sda1 ntfs
Thanks to:
mkasick - for the patch
farhanito - for the basic code in the .zip
glimmling - for the tasker apk's running the One"click"mount-Shell-Script
jfmcbrayer / Sgt. Meow - for the baseband_xmm_power wakelock workaround
Hi and thanks for this!
I'm a Linux noob and have some questions.
If I understand it correctly, I don't need Stickmount anymore with your kernel. Do I need to mount an usb stick in the terminal or is there a way to automate this with tasker for example?
What is the correct mount command syntax?
The old way to mount a network share with cifs manager in 4.1.2 I used this guide with external modules:
http://forum.xda-developers.com/showpost.php?p=29055478&postcount=10
Can you please show an example configuration for Cifs Manager, when I use your kernel?
Many thanks!
You still can use stickmount. You will see no difference, because stickmount uses the old "debuggerd" method. (Well, I did not test stickmount with the new fix, but it should work...)
For cifs:
I already included cifs in my kernel. You don't need to load them anymore. You can now easy use cifs manager, if you are mounting under /mounts (with the v2 of my kernel)
Here an screenshot of an configuration I use with CifsManager:
{
"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"
}
It is only important, to use a path in /mounts/. As I tested, CifsManager automatically creates the mount-point inside /mounts/.
It is possible, that applications which doesn't support browsing in file system, can't access /mounts. But some provide an option to the start directory or something like that (OfficeSuite for example) the directory just need to be set to /mounts. This is the reason, why stickmount uses an mountpoint inside /mnt/sdcard ... I am using OI Filemanager. It is a quite nice application. It also supports starting apps with the selected file.
I hope, I could help you.
AW: [KERNEL][WIFI][4.2.X] Included "Fix for empty app-mounted directories"
Thank you.
Cifs is working for me now, but I want to get rid of stickmount.
Since android 4.2.x I always get empty folders with stickmount, even with the latest version. I want to replace it with a new method. But I don't know the mount command and the device name to mount a standard usb-stick.
mount [devicename?] /mounts/usb ???
EDIT: I replaced stickmount with usb otg helper http://forum.xda-developers.com/showthread.php?t=1588940. Now I can see the files of a mounted usb-stick in every app, no more empty folders.
Gesendet von meinem Nexus 7 mit Tapatalk 2
Ah. I forgot USB-OTG helper. Well, with this app, the mounting of devices already worked without the fix. It also uses the "debuggerd" workaround like stickmount. You will need the kernel-fix only for mounting cifs.
I stay at my new oneclickmount-shellscript, because I want to know what the applications do ^^ I don't trust stickmount and usb-otg-helper...
AW: [KERNEL][WIFI][4.2.X] Included "Fix for empty app-mounted directories"
Can you please share your script?
Gesendet von meinem Nexus 7 mit Tapatalk 2
Look in the first post, I attached it there
Re: [KERNEL][WIFI][4.2.X] Included "Fix for empty app-mounted directories"
Thanks vorcers,
Here is flashable zip of v2
http://www.mediafire.com/download.php?gnn4n5p8plhdkv8
Md5= 0394f49ae911ec7a2d7cf845c5916fb6
Hope you can figure out the /storage problem
Every other kernel should implement this fix
Sent from my Nexus 7 using Tapatalk 2
This is a great! Question, since the mount point needs to be outside of /storage and /mnt/sdcard does that mean I can not use this to mount app data? ex. gameloft, etc (using Directory Bind)
It would be really awesome if a fix or hack to this issue (empty directories if app is not launched before mounting) could be found without requiring a kernel patch.
I tried the debuggerd method supposedly used by StickMount and found that it didn't work: app still sees empty mount if its process is started after mount.
Btw, app sees mounts if its process is started before because mounts are propagated in that case. They are just not inherited on process creation due to how zygote spawn app processes and initializes their mounts.
I never understood how hacking debuggerd could work to fix this issue as this is not much different to me than running a shell script invoking adb shell in loopback mode (requires root), since debuggerd and adbd run with identical priviledges:
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
adb connect localhost
adb shell mount ....
I've found a workaround that involves hijaking the obb directory by mounting whatever you want over /mnt/shell/emulated/obb. This directory is systematically bind mounted by the Zygote process in <external storage root>/Android/obb (see source code) when it spawns an app's process
Unfortunately this hack is not very usable because it has the side effect that any app expecting its data in the obb directory will not find it. And you can only mount one filesystem here.
Conclusion: with the new 4.2 multiuser support, Google made miserable all apps dealing with mounting.
Re: [KERNEL][WIFI][4.2.X] Included "Fix for empty app-mounted directories"
I havent tried this kernel yet, but it might appear by simply set the mount point to /data/media/0/MOUNTNAME
Might appear in storage that way.
worked for me using sshfsandroid mounting the pc harddrive over the wifi.
EDIT: I just flashed this kernel and its working the way I said. THANKS A BUNCH.:thumbup:
Sent from my Transformer TF101 using Tapatalk HD
Half-OT: Did someone tested with the new fix the superuser-function in non-primary accounts?
----------------------------------
farhanito said:
Thanks vorcers,
Here is flashable zip of v2
http://www.mediafire.com/download.php?gnn4n5p8plhdkv8
Md5= 0394f49ae911ec7a2d7cf845c5916fb6
Hope you can figure out the /storage problem
Every other kernel should implement this fix
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Very nice, If you don't object, I would use your zip in the future as base and would only offer .zip's.
Doncabezon said:
This is a great! Question, since the mount point needs to be outside of /storage and /mnt/sdcard does that mean I can not use this to mount app data? ex. gameloft, etc (using Directory Bind)
Click to expand...
Click to collapse
As mkasick said in his patch, also fixing the /storage/ folder, can cause other problems:
mkasick in his patch said:
Unfortunately bind mounts from outside /storage may retain the recursive-shared property (bug?). This means any additional namespace-specific bind mounts (e.g., /storage/emulated/0/Android/obb) will also appear, shared in all namespaces, at their respective source paths (e.g., /mnt/shell/emulated/0/Android/obb), possibly leading to hundreds of /proc/mounts-visible bind mounts. As a workaround, mark /mnt/shell/emulated also as recursive-slave so that subsequent bind mounts are confined to their namespaces.
Click to expand...
Click to collapse
To "fix" the /storage problem, only 6 lines of the patch need to be removed. But it also can break the multiuser-feature. I will test it in the next days.
bubbleguuum said:
It would be really awesome if a fix or hack to this issue (empty directories if app is not launched before mounting) could be found without requiring a kernel patch.
Click to expand...
Click to collapse
As an alternative (which is not really an alternative...) is to use the dalavik patch. But I think the Kernel-Patch is easy for stock.
Anyway, I think there will never be a 100% solution without patching. Only Google can solve this problem, by changing their multiuser architecture... (Or they mark by stock the root folder as non-slave, but that wouldn't fix the /storage problem...)
Re: [KERNEL][WIFI][4.2.X] Included "Fix for empty app-mounted directories"
What if I don't need multiuser support. Don't care much if it becomes broke, since my son has a kindle and my wife dare not touch my tablet save for playing Temple Run Brave
Sent from my Nexus 7 using xda premium
Re: [KERNEL][WIFI][4.2.X] Included "Fix for empty app-mounted directories"
vorcers said:
----------------------------------
Very nice, If you don't object, I would use your zip in the future as base and would only offer .zip's.
Click to expand...
Click to collapse
Of course, no problem
Sent from my Nexus 7 using Tapatalk 2
Thank you so much for that kernel! That is exactly what I have been looking for!
I added .zip's and released a new oneclickmount.sh version. :highfive:
Re: [KERNEL][WIFI][4.2.X] Included "Fix for empty app-mounted directories"
YayYouFixedIt said:
I havent tried this kernel yet, but it might appear by simply set the mount point to /data/media/0/MOUNTNAME
Might appear in storage that way.
worked for me using sshfsandroid mounting the pc harddrive over the wifi.
EDIT: I just flashed this kernel and its working the way I said. THANKS A BUNCH.:thumbup:
Sent from my Transformer TF101 using Tapatalk HD
Click to expand...
Click to collapse
So using this method, directory bind works?
Sent from my Nexus 7 using xda premium
Re: [KERNEL][WIFI][4.2.X] Included "Fix for empty app-mounted directories"
Actually it did seem too. No idea why. Both on the n7 and tf101 for sshfsandroid only.
But eventully I just made it mount to /Removable/pcharddrivefoldermountpointnamelong examplee and that was OK for me too. Ssomone mentioned it can be mounted anywhere outside storageed
EDIT: only using this kernel and I am using dirty aokp2.8 ATM.
I just checked again and the bind works as /data/media/0/PC which wouldnbe good if you want to download directly from dolphin into the PC.
vorcers said:
I added .zip's and released a new oneclickmount.sh version. :highfive:
Click to expand...
Click to collapse
Just wanted to give a HUGE THANKS for compiling your kernel and making it available, to farhanito for the flashable zip, and of course to mkasick for the concept
CIFS Manager works like a charm, and DeaDBeeF Player can see my shares, so me=HAPPY!
Nice to be on 4.2.1 now.
Y'all rule :highfive:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I'll just add that Mount Manager also works like a charm, automounting under /mounts whatever shares you define.
I created a new oneclickmount version, with some bug-fixes.
http://forum.xda-developers.com/attachment.php?attachmentid=1690089&d=1359582536
They appeared if you use more then one device at the nexus parallel. It simply only mounted one device.
I also set the standard-mountpoint to /data/media/0/mounts. With that, we can use our files also in /mnt/sdcard. :highfive: (Android re-directs it...)
This also works for bind's. I could bind /mounts/ to /data/media/0/mounts . It also works... Maybe someone helps that for using some games.
A lot of users around here like to try out different kinds of ROMs on their devices. It is advisable though, to always keep a backup of a stable (usually stock) ROM on your SD card. The truth is that it is very time-consuming to have to backup and restore ROMs in recovery just to boot to a new ROM for a few hours, run some tests and then go back to the stable one. It is also true that AOSP based ROMs may not support special features of certain devices (e.g. 3D displays and cameras or FM tuners), so a stock-based ROM must always be handy in case you need those features. This is why Dual-Boot can be useful. It allows people to switch between two ROMs almost as quickly as a simple reboot.
I have followed these guidelines to create Dual-Boot on four different phones and I suppose that the same method can be used for any phone.
The idea is to keep any stable ROM as primary and install an AOSP-based JB (4.1) or newer ROM on the SD-card.
WARNING: If you are not familiar with the way Android works, you can easily brick your device by flashing the wrong partition. I won't assume responsibility if you do and I can't offer support since I cannot possibly own all the devices this guide may be applicable to. If you don't fully understand these guidelines, then stay away. If you still want to try, remember, you are on your own! Questions, suggestions and remarks should be properly posted in the thread for everyone to read. Take no ofense, I will not reply to PMs.
Click to expand...
Click to collapse
Prerequisites:
A) You need to fully unlock your device (Root, Bootloader unlock, S-Off or whatever else your device has that may prevent you from flashing partitions).
B) You need to find a suitable way to unpack and repack your boot.img. Different ways are available for different devices. I can only suggest those that I have tested for mine.
C) You need to have a working updated busybox.
D) A ROM zip file to install onto the SD card. This ROM must NOT be using Aroma Installer.
Steps:
1. First you need to figure out the locations and sizes of your system, data, cache and boot partitions (you can use Partition Table from Play Store).
2. Create three additional partitions at the end of your SD card with the sizes you found. You can either use AParted on your phone or MiniTool and a card adapter on your PC. The partitions must be all primary and formatted to ext4.
(HINT1: If you use AParted, you probably want go hit "Decline" on the agreement, otherwise it will install adware junk)
(HINT2: You may want to create a larger Data partition, so that you have more space to install apps)
(HINT3: If you can convert ZIPs using DBootRecovery from 2nd post, then do it and jump to step 7)
3. Now you have to unzip the ROM file you want to install, browse to /META-INF/com/google/android, find the updater-script and edit all lines that contain mmcblk0ps (where s is your internal system partition number) to mmcblk1p2 (your new SD-system partition). Some ROM zips (like MIUI) also install stuff to the data partition, so be careful and change the respective lines from mmcblk1pd (where d is the number of your internal data partition) to mmcblk1p3.
4. You also need to unpack the boot.img, find the fstab.nick in the ramdisk (nick is the nickname of your device) and edit the sysyem, data and cache mountpoints to /dev/block/mmcblk1p2, 3 and 4 accordingly.
In some ROMs, the fstab. file plays no important role. In this case you must search inside files ending in .rc in the RamDisk for lines that have to do with the system, data and cache partitions. For example, in HTC One SV stock-based ROMs, you must change [email protected] with /dev/block/mmcblk1p2. Data and cache also follow this pattern.
5. If you need to flash GApps, then you must also modify that updater-script by changing the line run_program("/sbin/busybox","mount","/system"); into mount("ext4","EMMC","/dev/block/mmcblk1p2","/system");
Any other add-on you may want to flash must first be edited as described in steps 4 & 5.
6. Pack and zip everything back and reboot to recovery.
7. Make a backup of your current ROM and flash your modified zip(s).
When you reboot, your device should load your secondary ROM.
To switch back to the primary ROM you need to reflash your primary kernel (from the backup you took). Use dd if=path/backup.boot.img of=/dev/block/mmcblk0pb (where b is your boot partition) and reboot.
To boot back to your secondary ROM, just use the above command to flash the boot.img extracted from your modified ROM.zip. This process can now be done automatically using SwitchROM.sh from 2nd post
If you don't like scripts or terminal commands, another way to flash your boot images is Flashify.
If for any reason your 2nd ROM doesn't boot (e.g you haven't found the right method to pack your boot.img), you can advanced-restore just your primary boot.img from your backup in recovery. This way you'll be able to boot back to your primary ROM which is otherwise unaffected by the procedure.
In order to complete step 4, these links may be a good start:
i) These tools by Modding.MyMind work on my HTC.
ii) These ones by michfood work on my HTC but only unpack my LG boot.img
iii) and this one by berni987654321 packs my LG boot.img (download dualboot_tool.zip at the end of 1st post).
Don't forget to hit "Thanks" on those pages too.
Important:
- Be extra careful if your secondary ROM supports OTA updates which are applied through recovery. Only download but NEVER apply them before you tweak the zips as described above. Otherwise they will overwrite your primary ROM!
- Actually, every zip you want to flash to your secondary ROM must be edited first, otherwise it will flash to your primary.
- You can only use your regular custom recovery to flash edited zips to your secondary partitions. You can't use it to backup, restore or wipe them. Those functions will only affect the primary ROM. For this reason, I have created the DBoot Recovery script. For more info, read on to the second post.
Special thanks to @berni987654321 from whom I learned almost everything there is to know about Dual-Boot. This guide is based on his work.
DBoot Recovery Tools
Here are the scripts I promised.
Initial Setup
1. In order to use the scripts, you need to have partitioned your SD card the way I described in the previous post.
2. Download the zip from the link at the end of this post, unzip it and copy the DualBoot folder to the root of your SD card.
3. Install Script Manager from Play Store
4. Install (or update) Busybox
Inside the Dual Boot folder you will find two scripts and some more folders. Please do not change anything there. Just use ScriptManager to run the scripts. Their usage is explained below.
DBootRecovery.sh
Purpose: Manage your secondary ROM.
This tool is designed to run on the primary ROM, but some major functions are also available on the secondary.
1st run
Open ScriptManager, browse to the DualBoot folder and tap on DBootRecovery.sh. At the top of the screen that follows, select the first two icons (Fav and SU). I also prefer to enable the Wklock icon (it has to be enabled in settings first). Then you can hit Run.
When you run the script for the first time, it will try to read the /proc/emmc file (if it exists on your system) in order to determine your normal partitions. If the file exists, it will present you the data, so you can accept or reject them. If it doesn't exist, it will ask you to enter your partition numbers manually. In both cases, the data will be exported to a new file (part.ini) in the DualBoot folder and you will not be asked again.
The main screen
The top two lines are important. After a selection you made completes and returns to the main screen, the first two lines will inform you of its success or if any errors occurred.
Main menu
1. Backup ROM2
This option will create a backup of your secondary ROM. It will actually create images of your secondary system (mmcblk1p2) and data (mmcblk1p3) partitions. Those two will be saved in the backup folder inside DualBoot. Be careful, a new backup will overwrite the old one. If you want to keep an old backup, make sure you move or rename it.
2. Restore ROM2
This option will flash the images you took with option 1 back to their respective secondary partitions. It will only be available while you are on your primary ROM (you don't really expect to flash a partition while it's being used).
3. Convert ZIPs
This tool wil automatically do all the edits described in the 1st post to all ZIPs it can find in the OriginalZIPs folder. It is based on @Modding.MyMind's binaries [point (i) in 1st post]. If they don't work for you, you will see an error message. The original ZIPs will be kept intact and the edited ones will be created in the DBootZIPs folder. It is not certain that it will function equally well on all devices/ROMs, so before you flash your edited ZIPs, please check that they were edited correctly. This tool will NOT flash ZIPs. It will only convert them, so they can be flashed as secondary ROMs using your regular custom recovery. The tool will also put boot2.img in the img folder for use with the Switch ROM function. If you are on your primary ROM, it will also backup your current boot partition into a boot1.img in the img folder.
4. Advanced options
After selecting this, you will be taken to another menu where you can find more options. Most of them are not available while on your secondary ROM.
9. Switch ROM
This does the same as the individual SwitchROM.sh script. Read below.
0. Exit
I have decided not to explain this option.
Advanced menu
1. Wipe System2
2. Wipe Data2
3. Wipe Cache2
4. Wipe Dalvik2
These options just do to the secondary ROM what their name implies. They will only be available while on your primary ROM. If you want to factory-reset your secondary ROM, just wipe your Data2 and Cache2. When you flash new addons, it is advised to wipe Cache2 and Dalvik2. You can also wipe everything if you want to clean-install a completely new ROM.
5. Update binaries
Whenever Modding.MyMind updates his binaries, download and put them in your DualBoot/bin folder. Then, use this option to update existing binaries in your /system/bin folder.
0. Main Menu
Returns to the previous menu
SwitchROM.sh
The name is self-explanatory. This tool can only function if it finds the files boot1.img and boot2.img inside the DualBoot/img folder. These files will be automatically generated when you convert a ROM zip (using option 3). Alternatively, if you know what you are doing, you can create and put them there yourself.
Tap it in Script Manager and again select the first two icons (Fav and SU) and Run. It will automatically detect the current ROM, flash the boot image of the other one and prompt you to reboot. Use your Power-Menu and reboot your device. Your device will now boot to the other ROM.
In previous versions of this script for the LG Optimus 3D, I had included a reboot command. The reason why I am not using it any more is that the device would turn off abruptly and not "shutdown" the way it does when selecting it from the Power-Menu.
DOWNLOAD:
Get the latest version from here.
TROUBLESHOOTING:
If, while converting a zip, the script gives you an error that yourboot.img is incompatible, then either you have an encrypted header, or you have a truly incompatible boot.img! In any case, visit [Without PC] Unpack, Edit, Repack boot.img to read how to deal with encrypted headers, or to download the latest boot_manipulation.zip
Changelog:
13.03.2014 Initial upload of ZipEditor and SwitchROM.
17.03.2014 Updated ZipEditor to support the conversion of HTC-OneSV ROMs (AOSP and Stock based). Thanks to Modding.MyMind for assisting.
23.03.2014 First upload of DBootRecovery. The ZipEditor is now contained in it. If you are wondering about the v3.0, previous versions were device specific (only for the LG-P920). This is the first one for use on any Android.
21.06.2014 Version 3.1: Added support for the new LG P920 KitKat ROM. Fixed a bug where Dalvik2 cache would not be properly wiped. Changed a few minor details for better script operation.
Very insightful bro. Thanks for the share. I will definitely try this out. This may be my motivation to work on my Port Rom again. Was getting tired of wiping, flashing, wiping, flashing.... Was a nuisance and I unfortunately only have one device for my current model. This will be really useful to me in the future. Huge thanks again for letting me know about this thread.
Sent from my C525c using Tapatalk
Hey, getting ready to do this now with a 2gig. Using it as a test run lol. Anyways, to confirm, you leave the first part as is, meaning, fat 32, but add three additional parts to make a total of four partitions within the sdcard. So for example, part 1 (fat32), part 2-4 (ext4) which those would be the system, data, and cache. I'm confident that is how it is done, but wanted to clarify. Will do it now and check back for a reply later lol. Meanwhile, this has also given me a couple of dev ideas
Sent from my C525c using Tapatalk
Aww snap! Lol
Modding.MyMind said:
Hey, getting ready to do this now with a 2gig. Using it as a test run lol. Anyways, to confirm, you leave the first part as is, meaning, fat 32, but add three additional parts to make a total of four partitions within the sdcard. So for example, part 1 (fat32), part 2-4 (ext4) which those would be the system, data, and cache. I'm confident that is how it is done, but wanted to clarify. Will do it now and check back for a reply later lol. Meanwhile, this has also given me a couple of dev ideas
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Trust your confidence. You are right!
If you have a large card and use MiniTool, you can "shrink" your main partition to make room for the additional three. This way it won't be wiped.
Sent from the 3rd dimension!
dreccon said:
Trust your confidence. You are right!
Sent from the 3rd dimension!
Click to expand...
Click to collapse
Outstanding, just finished partitioning it. Will tackle the boot.img now.
Sent from my C525c using Tapatalk
One additional piece of info. Be extra careful if your secondary ROM supports OTA updates which are applied from recovery. Only download but NEVER apply them before you tweak the zips. Otherwise they will overwrite your primary ROM!
Sent from the 3rd dimension!
dreccon said:
One additional piece of info. Be extra careful if your secondary ROM supports OTA updates which are applied from recovery. Only download but NEVER apply them before you tweak the zips. Otherwise they will overwrite your primary ROM!
Sent from the 3rd dimension!
Click to expand...
Click to collapse
Not unless I make a change with the recovery lol
Anyways, I am still messing with my boot.img the fstab file for my device doesn't contain a list of mount points.
This is really the only thing it has as far as partitions are listed:
Code:
userdata/dataext4noatime,nosuid,nodev,noauto_da_alloc,discardencryptable=extra
Sent from my C525c using Tapatalk
Here's HTC OneSV K2_CL recovery.fstab
# mount pointfstypedevice[device2]
/boot emmc/dev/block/mmcblk0p20
/cacheext4/dev/block/mmcblk0p36
/dataext4/dev/block/mmcblk0p37
/devlogext4/dev/block/mmcblk0p25
/miscemmc/dev/block/mmcblk0p22
/int_sdvfat/dev/block/mmcblk0p38
/recoveryemmc/dev/block/mmcblk0p21
/sdcardvfat/dev/block/mmcblk1p1 /dev/block/mmcblk1
/systemext4/dev/block/mmcblk0p35
russellvone said:
Here's recovery.fstab
# mount pointfstypedevice[device2]
/boot emmc/dev/block/mmcblk0p20
/cacheext4/dev/block/mmcblk0p36
/dataext4/dev/block/mmcblk0p37
/devlogext4/dev/block/mmcblk0p25
/miscemmc/dev/block/mmcblk0p22
/int_sdvfat/dev/block/mmcblk0p38
/recoveryemmc/dev/block/mmcblk0p21
/sdcardvfat/dev/block/mmcblk1p1 /dev/block/mmcblk1
/systemext4/dev/block/mmcblk0p35
Click to expand...
Click to collapse
Thanks bro, i was actually trying to remember where that file was at haha.
Sent from my C525c using Tapatalk
And the fstab.k2cl is found in the source code, I'm not sure it's in the finished boot.img
russellvone said:
And the fstab.k2cl is found in the source code, I'm not sure it's in the finished boot.img
Click to expand...
Click to collapse
It is in the boot.img, I just ended up having a blonde moment when looking for the fstab recovery file haha. I knew it would have the correct info for me.
@Modding.MyMind
Could you post the fstab.k2cl in text form here please sir
russellvone said:
@Modding.MyMind
Could you post the fstab.k2cl in text form here please sir
Click to expand...
Click to collapse
Here you go. That is all of it lol
Code:
# Android fstab file.
#
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
userdata/dataext4noatime,nosuid,nodev,noauto_da_alloc,discardencryptable=extra
Sent from my C525c using Tapatalk
Is this from a JB or KK ROM?
Sent from the 3rd dimension!
dreccon said:
Is this from a JB or KK ROM?
Sent from the 3rd dimension!
Click to expand...
Click to collapse
JB 4.1.2
Sent from my C525c using Tapatalk
Then you might want to look for the mountpoints in the init.rc file also in the ramdisk.
Sent from the 3rd dimension!
dreccon said:
Then you might want to look for the mountpoints in the init.rc file also in the ramdisk.
Sent from the 3rd dimension!
Click to expand...
Click to collapse
Already snooping around lol
Sent from my C525c using Tapatalk
K2_CL info (I am wondering if I just apply the needed info to that fstab file if whether or not it will accept and read it)
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/timer_group cgroup rw,relatime,timer_slack 0 0
/dev/block/mmcblk0p35 /system ext4 ro,relatime,data=ordered 0 0
/dev/block/mmcblk0p37 /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p36 /cache ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk0p25 /devlog ext4 rw,nosuid,nodev,noatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p32 /carrier ext4 rw,nosuid,nodev,noatime,grpid,data=ordered 0 0
/dev/block/mmcblk0p16 /firmware_radio vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p17 /firmware_q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:38 /storage/sdcard0 vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0202,dmask=0202,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro,discard 0 0
/dev/block/vold/179:38 /mnt/secure/asec vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0202,dmask=0202,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro,discard 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:65 /storage/sdcard0/ext_sd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Sent from my C525c using Tapatalk