Related
Here's the deal, I flashed a clockwork port for the kindle fire that I made. It was 100% useless as of now because of the one hardware button that we have to work with. I sent Koush a message on twitter asking if there is a possibility to have a long press and quick/short press differentiate between scrolling down and actually selecting the item on the menu but he hasn't gotten back to me yet but I'm sure he's working on it
Very good news! Hopefully something comes of this. I want to look at the code for TWRP 2.0 and see if that can be ported over to the fire, its touch control.
Sent from my Kindle Fire
you got partition table for fire yet ? i am looking for boot partition
cat /proc/mounts....
Code:
# cat /proc/mounts
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
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
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/splash /dropbox ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/vold/179:12 /mnt/sdcard 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
/dev/block/vold/179:12 /mnt/secure/asec 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
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
#
cat /proc/partitions
Code:
# cat /proc/partitions
major minor #blocks name
179 0 7553024 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 196608 mmcblk0p4
179 5 16384 mmcblk0p5
179 6 65536 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 524288 mmcblk0p9
179 10 1164288 mmcblk0p10
179 11 262144 mmcblk0p11
179 12 5254144 mmcblk0p12
#
cat /proc/filesystems
Code:
# cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev devtmpfs
nodev binfmt_misc
nodev debugfs
nodev sockfs
nodev usbfs
nodev pipefs
nodev anon_inodefs
nodev rpc_pipefs
nodev devpts
ext3
ext2
ext4
nodev ramfs
vfat
msdos
nodev nfs
nodev nfs4
#
ls /dev/block/platform/mmci-omap-hs.1/by-name
Code:
# ls /dev/block/platform/mmci-omap-hs.1/by-name
media
cache
userdata
system
splash
boot
backup
recovery
dfs
dkernel
bootloader
xloader
#
Probably doesn't help. But I guess it was worth a shot. I'm not sure what the partitions are mapped to. :/
using root explorer i can tell that
/dev/block/platform/mmci-omap-hs.1/by-name/boot
is symlinked to
/dev/block/platform/mmci-omap-hs.1/mmcblk0p7
so if you wanted to mount boot
you could type
mount -o rw,remount /boot
i believe..
well i did a dd if= from the phone to the sdcard, but now we can just grab the boot.img from the update on amazon's site
Can you post pictures? This is the main reason I am not trading my fire for a nook.
http://i.imgur.com/9zWTk.jpg just gettings rid of those error messages now. had the wrong filesystem for /cache
I love you.screw the nook.
Wow JackpotCalvin! How were you able to flash the clockwork recovery? Also are you still able to load your KF as normal?
really nice work
another way to mount things as is done in the init.rc:
mount [email protected]/system system
so for rw..."mount -o rw,remount -t ext4 [email protected] /system"
anyway mounts are as follows:
backup -> mmcblk0p6
boot -> mmcblk0p7
bootloader ->mmcblk0p2
cache -> mmcblk0p11
dfs -> mmcblk0p4
dkernel -> mmcblk0p3
media -> mmcblk0p12
recovery -> mmcblk0p5
splash -> mmcblk0p8
system -> mmcblk0p9
userdata -> mmcblk0p10
xloader -> mmcblk0p1
well we're at a bit of a road block as of right now as we have no way to navigate through the menu, we can just press OK and reboot the kindle. also, pressing reboot now does not start the device normally, it just reboots into clockwork. i'm looking for the flag that the OS puts in /cache or /data to trigger a recovery reboot because pressing reboot now does not remove that flag so it will continue to reboot into clockwork unless you do a little hackery to put the stock recovery back on it and then reboot it into the stock recovery and make it fail the signature verification this fluke update.zip i made. we need to find a way to make a fail safe to reboot into recovery as well in case when we start roming, something goes wrong
Do you think something like this might work?
https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en
JackpotClavin said:
when we start roming,
Click to expand...
Click to collapse
Emphasis mine. I can't wait. Great work so far, this seems to be going a lot faster than I imagined at first. I wish I had the programming chops to become a dev, instead i just look on from the sidelines, and maybe monetarily support projects when and where I can.
Awesome work guys. I've got the Nook Tablet but thought I'd pop over to see how it's going. Again, awesome work.
Sent from my Nook Tablet using Tapatalk
littleemp said:
Do you think something like this might work?
https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en
Click to expand...
Click to collapse
The official clockword mod does not support the fire yet... if that's what you're asking. That is what OP is trying to do.
JackpotClavin said:
Here's the deal, I flashed a clockwork port for the kindle fire that I made. It was 100% useless as of now because of the one hardware button that we have to work with. I sent Koush a message on twitter asking if there is a possibility to have a long press and quick/short press differentiate between scrolling down and actually selecting the item on the menu but he hasn't gotten back to me yet but I'm sure he's working on it
Click to expand...
Click to collapse
How did you boot into recovery?
well i've just made a clockwork backup of my current system. i believe ive found a way that we can manage to "navigate" through the menu, even though it's a real pain in the ass to do
JackpotClavin said:
well i've just made a clockwork backup of my current system. i believe ive found a way that we can manage to "navigate" through the menu, even though it's a real pain in the ass to do
Click to expand...
Click to collapse
Sounds like we may have to be connected to our PC to run the commands...??
Hello. I need help with backing up my /efs folder. I tried different methods and none seemed to work.
Phone: GT-S5660 Gio
Network Lock [OFF]
Network Subset Lock [OFF]
SP Lock [OFF]
CP Lock [OFF]
Android: 2.3.3
PDA : S5660XXKPO
PHONE : S5660XXKPA
CSC : S5660OXFKP5
Lurking the forums I tried different methods with no luck:
C:\sdk>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ su
su
# tar zcvf /sdcard/efs-backup.tar.gz /efs
tar zcvf /sdcard/efs-backup.tar.gz /efs
tar: not found
# exit
exit
$ exit
exit
=======================
C:\sdk>adb shell
$ su
su
# busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
tar: /efs: No such file or directory
tar: error exit delayed from previous errors
# cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
/dev/block/stl3: Invalid argument
# exit
exit
$ exit
exit
This method creates efs_dev-block-stl3.img (0 bytes) and efs-backup.tar.gz (29 bytes)
=======================
EFS Pro
Checking Device Connection... Device Connected!
Restarting ADB Server... Okay!
Checking ROOT Access... Device Has ROOT Permissions!
Backing Up Device's '/efs' Folder, Please Wait...
Creating EFS Backup TAR Archive... EFS Backup Failed!
Operation Finished!
With the ISO option the program freezes.
=======================
C:\sdk>adb shell
$ su
su
# dd if=/dev/block/stl4 of=/sdcard/efs.rfs
dd if=/dev/block/stl4 of=/sdcard/efs.rfs
/dev/block/stl4: cannot open for read: Invalid argument
# exit
exit
$ exit
exit
=======================
I also tried this:
mount
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
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
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioch
arset=utf8 0 0
/dev/stl12 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=u
tf8 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,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,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=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.sportstracklive.stopwatch-1 vfat ro,dirsync,nosuid
,nodev,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.speedsoftware.rootexplorer-1 vfat ro,dirsync,nosui
d,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859
-1,shortname=mixed,utf8,errors=remount-ro 0 0
$
=======================
With Root Explorer I am unable to find the /efs
Sorry for the long post, but what am I missing?
Best regards, V a L y O.
STOP!
The first rule with the Gio is not to mess with the EFS partition if you don't know what you're doing.
It is located in stl5, but you very much risk corrupting it solely by mounting and reading it.
Corruption in this case means a bricked phone or a blank IMEI, which means no phone service.
Either backup bml5, or work in recovery mode.
Thank you for the replay.
I know that messing with the stl5 can brick the phone. Well, that already happened once when I used Odin to flash a wrong 2.3.5 version. Lucky for me, It was repaired under warranty.
That's why I want to make a backup to the system files.
bml5 is backed up. Is it enough to fix the phone in case I brick it again?
Best regards, V a L y O.
now my phone have blank imei
but, i still can use it for sms, call & internet
is anyone here know how to restore it?
lucky, in indonesian imei is not requirement for gettiong mobile service service
phiexz said:
now my phone have blank imei
but, i still can use it for sms, call & internet
is anyone here know how to restore it?
lucky, in indonesian imei is not requirement for gettiong mobile service service
Click to expand...
Click to collapse
Same here! I live in the Netherlands and also have a blank IMEI(IMEI is 000000000000) but still evrything works except swype install because it requires an IMEI number. Somebody know how to fix it? maybe to use somebody elses IMEI? with /efs restore or is there an way to import my own IMEI in somebody elses /efs backup?
Hi, guys!
I've tried rooting my DesireZ using "Downgrading guide from gingerbread to froyo" (link was destroyed by forum rules)
It is really clear and easy to do guide. But I ran into a problem because I can't make a root backup after gaining Temporary root on HTC DESIRE Z (2.42.405.2). When fixsu.sh ends I am starting "Root check basic" app and it has show me the result is OK. Then I starts MyBackupPro. The first time it shows me new menu item with root operations, but after that it refusing do anything instead of message "There is no properly root access". Titanium Backup behaves in the same way: it properly starts, but does not work with system applications. The only step in the guide I have missed is "Changing version number", but I think the problem is not the case, is it true? Could you tell me please, what may be a reason?
I really fear to begin change the ROM before to have full backup...
Try a full power off. turn the phone off, pull the battery out for a minute, then turn it back on and retry the temp-root.
Sometimes the 'fastboot' feature of sense roms messes with the temp-root.
-Nipqer
Nipqer said:
Try a full power off. turn the phone off, pull the battery out for a minute, then turn it back on and retry the temp-root.
Sometimes the 'fastboot' feature of sense roms messes with the temp-root.
-Nipqer
Click to expand...
Click to collapse
unfortunately, did not help.
Here is log after I turned device:
C:\Documents and Settings\htc>adb devices
List of devices attached
HT0BHRT01025 device
C:\Documents and Settings\htc>adb shell
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 800
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Potential exploit area found at address fbb52000:1000.
Exploiting device...
C:\Documents and Settings\htc>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./fixsu.sh
./fixsu.sh
# cat /system/etc/passwd
cat /system/etc/passwd
root::0:0:root:/data/local:/system/bin/sh !!ROOT is really getting!
# cat /system/etc/passwd
cat /system/etc/passwd
keychar xV4 9 0 0 0 # !!After MyBackup Pro start
#
I think the problem is the destruction of the memory area, where exploit works.
Maybe there are other ideas?
Hi everyone,
After about 12 hours of research and no solution here is my question regarding my T999.
For about 2 days I've been unable to flash any roms or recoveries. I currently run CM11 nightlies and was updating fine since the first CM11 nightlies until this problem. I originally thought I had lost root, but that didn't turn out to be the case. I've been unable to boot into recovery and everytime I try to do so I'm taken to what I think is the stock recovery (Android with turning gears on its back) even though I have CWM installed and set up. As a result, CM11 01/01 auto installs and I never see the recovery menu options.
Furthermore, every time I attempt to connect to my PC to flash with ODIN I get an "Samsung Mobile USB MODEM failed" error from Windows 7 (64bit). Here's what I've tried so far,
1- Re-downloaded and installed Samsung drivers (about 3 times). Installed from KIES once and just drivers twice.
2- Tried pushing recovery through ADB but get a "-1" error at the end of the process. (Seems like a permission error)
3- Tried reflashing recovery with ROM and Goo Manager but it takes me back to the aforementioned stock recovery.
4- Tried to flash using Heimdall but also get errors.
At ODIN MODE my T999 reads,
PRODUCT NAME:SGH-T999
CUSTOM BINARY DOWNLOAD: Yes (1 count)
CURRENT BINARY: Custom
SYSTEM STATUS: None
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWREV: 1
I'm aware of these posts, but find my issue to be different since Windows is not installing appropriate drivers.
http://forum.xda-developers.com/showthread.php?t=2541437
http://forum.xda-developers.com/showthread.php?t=2221279
Any insights would be appreciated,
Cheers
Did you put the phone in download before connecting to Windows ? Download mode drivers for Windows are slightly different from what Kies has. In addition, you have to install those drivers before you start Odin. So best close it before you plug in.
Sometimes you may have to restart windows after installing the Download Mode Drivers.
Perseus71 said:
Did you put the phone in download before connecting to Windows ? Download mode drivers for Windows are slightly different from what Kies has. In addition, you have to install those drivers before you start Odin. So best close it before you plug in.
Sometimes you may have to restart windows after installing the Download Mode Drivers.
Click to expand...
Click to collapse
Hi Perseus,
Sorry I didn't state that. I thought it would be assumed. Yes, definitely put into download mode with debug enabled before connecting it. It tries to install it as a "MSM8960" and Samsung Mobile USB Modem always fails to install... here's a screenshot of my device manager and driver install.
Cheers,
Pictures are huge, so please click on the links!
http://www.image-share.com/upload/2392/209.jpg
http://www.image-share.com/upload/2392/210.jpg
In that case find the original ADB Drivers. They are not from Samsung. Once the errors are resolved, your problem will likely go away.
Perseus71 said:
In that case find the original ADB Drivers. They are not from Samsung. Once the errors are resolved, your problem will likely go away.
Click to expand...
Click to collapse
Thanks Perseus,
I already had the original ADB drivers. I play around with Eclipse quite often so I try to keep my SDK files updated. Here's an update though. I was able to re-flash CWM 6.0.5 recovery in download mode using Heimdall and now Custom Binary reads 2 in ODIN Mode. Though Heimdall frontend recognizes my device and flashes successfully, it never really loads CWM. Just jumps straight into an auto-install of my current rom (CM11 01/01).
Here's the recovery log under /cache/recovery. Thank you for your insight!
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Tue Dec 31 19:37:48 2013
framebuffer: fd 4 (720 x 1280)
ClockworkMod Recovery v6.0.4.3
recovery filesystem table
=========================
0 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot 0
1 /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery 0
2 /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache 0
3 /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system 0
4 /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata -16384
5 /storage/sdcard1 auto /devices/platform/msm_sdcc.3/mmc_host/mmc1 0
6 /storage/usbdisk0 auto /devices/platform/msm_hsusb_host/usb 0
7 /tmp ramdisk ramdisk 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!
I:Completed outputting fstab.
I:Connected to Vold..
I:110 0 sdcard /storage/sdcard1 1
I:110 0 sda /storage/usbdisk0 0
I:200 0 Volumes listed.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.boot.hardware=qcom
ro.boot.debug_level=0x4f4c
ro.boot.cp_debug_level=0x55FF
ro.boot.emmc_checksum=3
ro.boot.warranty_bit=1
ro.boot.bootloader=T999UVUEMJC
ro.boot.nvdata_backup=0
ro.boot.boot_recovery=1
ro.boot.batt_check_recovery=1
ro.boot.emmc=true
ro.boot.serialno=761bc55c
ro.boot.baseband=msm
ro.serialno=761bc55c
ro.bootmode=unknown
ro.baseband=msm
ro.bootloader=T999UVUEMJC
ro.hardware=qcom
ro.revision=16
ro.emmc=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=JLS36G
ro.build.display.id=cm_d2tmo-userdebug 4.3 JLS36G 0c51335b75 test-keys
ro.build.version.incremental=0c51335b75
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3
ro.build.date=Sun Oct 6 04:26:36 PDT 2013
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=hudson
ro.build.host=koushik-lion
ro.build.tags=test-keys
ro.product.model=SGH-T999
ro.product.brand=samsung
ro.product.name=d2uc
ro.product.device=d2tmo
ro.product.board=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
ro.build.product=d2tmo
ro.build.description=d2uc-user 4.1.2 JZO54K T999UVDMD5 release-keys
ro.build.fingerprint=samsung/d2uc/d2att:4.1.2/JZO54K/T999UVDMD5:user/release-keys
ro.build.characteristics=default
ro.cm.device=d2tmo
rild.libargs=-d /dev/smd0
telephony.lteOnGsmDevice=1
ro.telephony.default_network=9
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.sf.lcd_density=320
ro.hwui.text_cache_width=2048
ro.vendor.extension_library=/system/lib/libqc-opt.so
ro.ril.hsxpa=1
ro.ril.gprsclass=10
persist.radio.add_power_save=1
persist.radio.snapshot_disabled=1
com.qc.hardware=true
persist.radio.apm_sim_not_pwdn=1
ro.ril.transmitpower=true
ro.opengles.version=131072
persist.audio.vr.enable=false
persist.audio.speaker.location=high
persist.timed.enable=true
ro.emmc.sdcard.partition=17
ro.use_data_netmgrd=true
persist.data_netmgrd_nint=16
lpa.decode=true
rild.libpath=/system/lib/libril-qc-qmi-1.so
ril.subscription.types=NV,RUIM
ro.ril.svdo=true
ro.cdma.subscribe_on_ruim_ready=true
persist.radio.no_wait_for_card=0
media.aac_51_output_enabled=true
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
persist.audio.fluence.mode=endfire
persis
Cheers,
Can you try Odin Mobile and TWRP ?
Hey Perseus,
Thanks for working with me through this. I had forgot to m mentioned that I had tried ODIN Mobile already. Decided to try again and it didn't work. I went back to cache/recovery/ and saw a command for with rw permissions. Here's what it said
boot-recovery
--update_package=/sdcard/0/cmupdater/cm-11-20140101-NIGHTLY-d2tmo.zip
Simply backed up the file and erased the file, rebooted into recovery and voilà, it worked.
Your patience is appreciated!
Cheers
Sent from my SGH-T999 using XDA Premium 4 mobile app
Glad it all worked.
Hi @all,
haven't found any definite answer to this unsing the search function.
Is there any image out there supporting the HDD version of the 80G9 tablet? Except the official image of course.
Installed the lastest 4.4.2 developer image, now I know what the H-Model is (No "H" model support)... otherwise working great so far.
Thanks for your answers!
martinwag said:
Hi @all,
haven't found any definite answer to this unsing the search function.
Is there any image out there supporting the HDD version of the 80G9 tablet? Except the official image of course.
Installed the lastest 4.4.2 developer image, now I know what the H-Model is (No "H" model support)... otherwise working great so far.
Thanks for your answers!
Click to expand...
Click to collapse
It's really confusing...
[URL="http://forum.xda-developers.com/showpost.php?p=50137500&postcount=61" @[email protected][/URL] has reported that it works... I really don't know whats going wrong...
@[email protected]: Can you give a statement, if the harddisk storage works for you?
Quallenauge said:
It's really confusing...
[URL="http://forum.xda-developers.com/showpost.php?p=50137500&postcount=61" @[email protected][/URL] has reported that it works... I really don't know whats going wrong...
@[email protected]: Can you give a statement, if the harddisk storage works for you?
Click to expand...
Click to collapse
Yes, but I could only install till version 23_01_2014-21_52_56 yet.
And I need to mount it manually e.g. via 'adb shell':
[email protected]:/ # mount /dev/block/platform/omap/usbhs_omap/sdb1 /storage/sdcard1/
[email protected] said:
Yes, but I could only install till version 23_01_2014-21_52_56 yet.
And I need to mount it manually e.g. via 'adb shell':
[email protected]:/ # mount /dev/block/platform/omap/usbhs_omap/sdb1 /storage/sdcard1/
Click to expand...
Click to collapse
Can you please adapt the fstab file "/fstab.archosa101hboard" to this location?
Code:
[STRIKE]/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1/1-1.1/1-1.1:1.0/ auto auto defaults voldmanaged=sdcard1:auto[/STRIKE]
[B]/dev/block/platform/omap/usbhs_omap/sdb1 auto auto defaults voldmanaged=sdcard1:auto[/B]
/devices/platform/omap/musb-omap2430/musb-hdrc/usb2/2-1/2-1:1.0 auto auto defaults voldmanaged=usbdisk:auto
/dev/block/zram0
And see if it helps? (Maybe you can play with the old path definition; does it exist? Maybe this is sufficient:
Code:
/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/
)
Hint: Don't forget to unlock the device in order to modify the system file:
Code:
adb shell mount -o remount,rw /
Actually I am not used to writing in those forum systems, so my original try to answer is now blocked
---------- Post added at 01:10 AM ---------- Previous post was at 12:59 AM ----------
I try without any quotes and just a very short version:
Actually I forgot that I had a mini card reader and sdcard in the 3G USB plugged in, without this card it is in fact sda1
---------- Post added at 01:22 AM ---------- Previous post was at 01:10 AM ----------
... Nevertheless it didn't worked, so I searched and found fstab.archosa101hboard is not really in use and I changed init.archosa101hboard.rc first.
---------- Post added at 01:27 AM ---------- Previous post was at 01:22 AM ----------
please try a grep fstab.archosa init* to find that always the sboard fstab files are mounted
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Don't know if this can be useful information for you in init.archosa.*board.rc files, but I found in init.rc this import line via ${ro.hardware}:
import /init.${ro.hardware}.rc
back to the harddisk:
still not knowing why it didn't work I changed fstab.archosa101hboard to double-check my fix above is okay:
#/devices/platform/omap/omap_hsmmc.0 auto auto defaults voldmanaged=sdcard1:auto
#/dev/block/platform/omap/usbhs_omap/sda1 auto auto defaults voldmanaged=sdcard1:auto
/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2
/devices/platform/omap/musb-omap2430/musb-hdrc/usb2/2-1/2-1:1.0 auto auto defaults voldmanaged=usbdisk:auto
/dev/block/zram0 none swap defaults zramsize=134217728
Okay I got the right file, as after reboot I got it mounted:
[email protected]:/ # df
Filesystem Size Used Free Blksize
...
/storage/sdcard1 231.0G 187.5M 230.9G 4096
...
I do not understand "voldmanaged=sdcard1:auto", so I need to stop here and wait for your further support.
I have already played around a lot also with the information from android source website, which I cannot link here (new user)
[email protected] said:
Actually I am not used to writing in those forum systems, so my original try to answer is now blocked
---------- Post added at 01:10 AM ---------- Previous post was at 12:59 AM ----------
I try without any quotes and just a very short version:
Actually I forgot that I had a mini card reader and sdcard in the 3G USB plugged in, without this card it is in fact sda1
---------- Post added at 01:22 AM ---------- Previous post was at 01:10 AM ----------
... Nevertheless it didn't worked, so I searched and found fstab.archosa101hboard is not really in use and I changed init.archosa101hboard.rc first.
---------- Post added at 01:27 AM ---------- Previous post was at 01:22 AM ----------
please try a grep fstab.archosa init* to find that always the sboard fstab files are mounted
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Don't know if this can be useful information for you in init.archosa.*board.rc files, but I found in init.rc this import line via ${ro.hardware}:
import /init.${ro.hardware}.rc
Click to expand...
Click to collapse
Thanks for your report ! The fstab is loaded on specific archos model init file.
Code:
on fs
# mount partitions
mount rawfs /dev/block/mmcblk0p1 /mnt/rawfs
mount_all /fstab.archosa101hboard
swapon_all /fstab.archosa101hboard
This init file is loaded on top at the init.archos_init.rc file. The ${ro.hardware} reflects the model property. You can verify this with
Code:
adb shell getprop ro.hardware
.
Then the correct fstab should loaded.
please try a grep fstab.archosa init* to find that always the s board fstab files are mounted
Click to expand...
Click to collapse
PS: Which version do you use? I had a fix a few weeks ago (Correct fstab file name for non a80s devices.) which is used in newer releases.
back to the harddisk:
still not knowing why it didn't work I changed fstab.archosa101hboard to double-check my fix above is okay:
#/devices/platform/omap/omap_hsmmc.0 auto auto defaults voldmanaged=sdcard1:auto
#/dev/block/platform/omap/usbhs_omap/sda1 auto auto defaults voldmanaged=sdcard1:auto
/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2
/devices/platform/omap/musb-omap2430/musb-hdrc/usb2/2-1/2-1:1.0 auto auto defaults voldmanaged=usbdisk:auto
/dev/block/zram0 none swap defaults zramsize=134217728
Okay I got the right file, as after reboot I got it mounted:
[email protected]:/ # df
Filesystem Size Used Free Blksize
...
/storage/sdcard1 231.0G 187.5M 230.9G 4096
...
I do not understand "voldmanaged=sdcard1:auto", so I need to stop here and wait for your further support.
I have already played around a lot also with the information from android source website, which I cannot link here (new user)
Click to expand...
Click to collapse
The output of the df command is ok. Please check if it is possible to use the following:
Code:
/dev/block/platform/omap/usbhs_omap/sda1 auto auto defaults voldmanaged=sdcard1:auto
. The destination mount point is determined from the vold daemon, which starts the appropriate "sdcard" daemon.
Thank you all for your answers!
Great, the HDD is already avaliable in /dev/block/platform/omap/usbhs_omap/sda1... Why didn't I just do a find * | grep sda ...
I'm at the point where [email protected] is now, only difference is that I'm using the 80h files instead of the 101h ones.
- enable write on /
Code:
busybox mount -o remount,rw /
- edit fstab.archosa80hboard
Code:
#/devices/platform/omap/omap_hsmmc.0 auto auto defaults voldmanaged=sdcard1:auto #original
#/dev/block/platform/omap/usbhs_omap/sda1 auto auto defaults voldmanaged=sdcard1:auto #as suggested, doesn't work
/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2 #works
- edit init.archosa80hboard.rc
Code:
#mount partitions
mount rawfs /dev/block/mmcblk0p1 /mnt/rawfs #as is
mount_all /fstab.archosa80hboard #replace s with h
swapon_all /fstab.archosa80hboard #replace s with h
I'm using Image 12_02_2014-20_55_45.7z, which was current last weekend at least
Maybe this has been reported before, but 12_02_2014-20_55_45.7z don't boot on my tab.
I get nothing, but a black screen and the green LED - not even the Archos logo or a logcat
Latest running version is 23_01_2014-21_52_56
[email protected] said:
Maybe this has been reported before, but 12_02_2014-20_55_45.7z don't boot on my tab.
I get nothing, but a black screen and the green LED - not even the Archos logo or a logcat
Latest running version is 23_01_2014-21_52_56
Click to expand...
Click to collapse
That's weird.... I get this behavior in case I'm flash via SDE and when I choose "Flash kernel and initramfs" the USB drive is mounted on my PC.
When I copy the two files to the destination, sometimes I forget to unmount the removable storage drive and choose "continue" (or something like this) on the tablet. Then the incomplete kernel/initramfs files are written to the internal ssd which causes the black screen on start.
Can you please check if this was also the case?
[email protected] said:
Maybe this has been reported before, but 12_02_2014-20_55_45.7z don't boot on my tab.
I get nothing, but a black screen and the green LED - not even the Archos logo or a logcat
Latest running version is 23_01_2014-21_52_56
Click to expand...
Click to collapse
If I don't open a terminal and sudo sync before disconnecting the usb cable it happens most of the time for me.
stevemp said:
If I don't open a terminal and sudo sync before disconnecting the usb cable it happens most of the time for me.
Click to expand...
Click to collapse
Quallenauge said:
That's weird.... I get this behavior in case I'm flash via SDE and when I choose "Flash kernel and initramfs" the USB drive is mounted on my PC.
When I copy the two files to the destination, sometimes I forget to unmount the removable storage drive and choose "continue" (or something like this) on the tablet. Then the incomplete kernel/initramfs files are written to the internal ssd which causes the black screen on start.
Can you please check if this was also the case?
Click to expand...
Click to collapse
Thank you for the suggestions, so I could find out a bit what is actually my problem:
I did in fact not disconnecting the USB cable before rebooting.
This was never a problem for the old versions - may be you could add this to your installation instructions if really necessary:
Quallenauge said:
- reboot into SDE menu and under Developer Edition Mernu , Flash Kernel and Initramfs : copy zImage and initramfs.cpio.lzo on the new driver that appears on desktop/laptop
- Wait for reboot your devices : after reboot you can see Android prepares the system for a while .....be patient !
Click to expand...
Click to collapse
Nevertheless the device immediately stops (freeze) also directly when I later plug in the USB cable and further after a short time it shows again a black screen and the green LED. I have also tested to connect an OTG cable adapter and it also directly stops (with and without a mouse). Sometimes after plugging off the cable the device automatically reboots.
I switched the 3g dongle on to test the other USB port with a mouse, but no lights - it doesn't work either.
I have no time for testing now and for the rest of the week, I'll check next week for requested logs or a new version fixing it. :fingers-crossed:
Cheers!
[email protected] said:
Thank you for the suggestions, so I could find out a bit what is actually my problem:
I did in fact not disconnecting the USB cable before rebooting.
This was never a problem for the old versions - may be you could add this to your installation instructions if really necessary:
Click to expand...
Click to collapse
Sorry, I meant something different :angel: You can leave the USB cable plugged into the device. I mean, you have to eject (sign off,...) the drive removable in windows / linux after you finish the file transfer to the device (both when you copy the kernel+initramfs and also when updating the archos.ext4.update file). This way the data is synced on the device (to avoid corrupted data).
[email protected] said:
Nevertheless the device immediately stops (freeze) also directly when I later plug in the USB cable and further after a short time it shows again a black screen and the green LED. I have also tested to connect an OTG cable adapter and it also directly stops (with and without a mouse). Sometimes after plugging off the cable the device automatically reboots.
I switched the 3g dongle on to test the other USB port with a mouse, but no lights - it doesn't work either.
I have no time for testing now and for the rest of the week, I'll check next week for requested logs or a new version fixing it. :fingers-crossed:
Cheers!
Click to expand...
Click to collapse
Does at least the archos screen appear before the screen goes black?
Quallenauge said:
Sorry, I meant something different :angel: You can leave the USB cable plugged into the device. I mean, you have to eject (sign off,...) the drive removable in windows / linux after you finish the file transfer to the device (both when you copy the kernel+initramfs and also when updating the archos.ext4.update file). This way the data is synced on the device (to avoid corrupted data).
Does at least the archos screen appear before the screen goes black?
Click to expand...
Click to collapse
Actually I am using linux and I follow exactly your process with sync and umount ... and I was used to leaving the USB cable plugged into the device, but starting with CM 11.0 from 11_02_2014-23_03_07 the tablet was not booting and the archos screen did not appear any more.
I saw that you classified the kernel "Important: Highly experimental!" and "No "H" model support", so I thought just "bad luck" and went back to the old version. (and I bought a sony xperia tablet s)
stevemp wrote "before disconnecting the usb cable", so I tried also without the cable and it boots. Later I realized that I cannot use the micro USB plug at all, because the tablet directly freeze when I connect anything to it. (No problem with power, as the H model has a separated power plug)
May be I didn't explained it well: It always freeze: either before booting or/and also during booting or/and also after booting in normal operating: just plug it in -> directly freeze.
I have no idea what happens and how it can be analyzed.
This happens not when I run CM 11.0 version from 23_01_2014-21_52_56, so I do not believe in a hardware bug.
[email protected] said:
Actually I am using linux and I follow exactly your process with sync and umount ... and I was used to leaving the USB cable plugged into the device, but starting with CM 11.0 from 11_02_2014-23_03_07 the tablet was not booting and the archos screen did not appear any more.
I saw that you classified the kernel "Important: Highly experimental!" and "No "H" model support", so I thought just "bad luck" and went back to the old version. (and I bought a sony xperia tablet s)
stevemp wrote "before disconnecting the usb cable", so I tried also without the cable and it boots. Later I realized that I cannot use the micro USB plug at all, because the tablet directly freeze when I connect anything to it. (No problem with power, as the H model has a separated power plug)
May be I didn't explained it well: It always freeze: either before booting or/and also during booting or/and also after booting in normal operating: just plug it in -> directly freeze.
I have no idea what happens and how it can be analyzed.
This happens not when I run CM 11.0 version from 23_01_2014-21_52_56, so I do not believe in a hardware bug.
Click to expand...
Click to collapse
Thanks for your explanation! Now it's clear for me, the update process was done correctly.
Sadly, I updated the kernel since the 23_01_2014-21_52_56, so I think this is a kernel bug, which affects the JMicron USB SATA controller :-/
Sadly only a few people has a serial cable connected to their *H devices, so we don't have an easy way to track down this issue.
I see a light chance to get the boot log. I can send you a archive where you can test the kernel from your existing installation.
If you have time for some experiments, let me know.
Quallenauge said:
Thanks for your explanation! Now it's clear for me, the update process was done correctly.
Sadly, I updated the kernel since the 23_01_2014-21_52_56, so I think this is a kernel bug, which affects the JMicron USB SATA controller :-/
Sadly only a few people has a serial cable connected to their *H devices, so we don't have an easy way to track down this issue.
I see a light chance to get the boot log. I can send you a archive where you can test the kernel from your existing installation.
If you have time for some experiments, let me know.
Click to expand...
Click to collapse
Yeah, I can test it, but I think not before Monday next week.
Quallenauge said:
I had a fix a few weeks ago (Correct fstab file name for non a80s devices.) which is used in newer releases.
Click to expand...
Click to collapse
Sorry your fix does not really correct all:
Code:
localhost / # grep fstab.archosa init*
init.archosa101[B]h[/B]board.rc: mount_all /fstab.archosa101[B]s[/B]board
init.archosa101[B]h[/B]board.rc: swapon_all /fstab.archosa101[B]s[/B]board
...
After fixing this I have also tested a bit changing the fstab.archosa101hboard.rc file, as your described, but I couldn't get the hard disk mounted with the voldmanaged=sdcard1:auto setting.
Only this line automatically mount it:
Code:
/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2
I also wonder about a link (/sys/class/block/sda1) which has no correct target:
Code:
localhost / # find / -name sda1 2>/dev/null
/sys/class/block/sda1
/dev/block/sda1
/dev/block/platform/omap/usbhs_omap/sda1
localhost / # ls -l /sys/class/block/sda1 /dev/block/sda1 /dev/block/platform/omap/usbhs_omap/sda1
lrwxrwxrwx 1 root root 15 Mar 7 00:16 /dev/block/platform/omap/usbhs_omap/sda1 -> /dev/block/sda1
brw------- 1 root root 8, 1 Mar 7 00:16 /dev/block/sda1
lrwxrwxrwx 1 root root 0 Mar 7 00:22 /sys/class/block/sda1 -> ../../devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1/1-1.1/1-1.1:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
/sys/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1/1-1.1 does not exist, just
/sys/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1/1-1:1.0
Code:
localhost / # ls -l /sys/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1
drwxr-xr-x 4 root root 0 Mar 7 00:22 1-1:1.0
-rw-r--r-- 1 root root 4096 Mar 7 00:22 authorized
-rw-r--r-- 1 root root 4096 Mar 7 00:22 avoid_reset_quirk
-rw-r--r-- 1 root root 4096 Mar 7 00:22 bConfigurationValue
-r--r--r-- 1 root root 4096 Mar 7 00:22 bDeviceClass
-r--r--r-- 1 root root 4096 Mar 7 00:22 bDeviceProtocol
-r--r--r-- 1 root root 4096 Mar 7 00:22 bDeviceSubClass
-r--r--r-- 1 root root 4096 Mar 7 00:22 bMaxPacketSize0
-r--r--r-- 1 root root 4096 Mar 7 00:22 bMaxPower
-r--r--r-- 1 root root 4096 Mar 7 00:22 bNumConfigurations
-r--r--r-- 1 root root 4096 Mar 7 00:22 bNumInterfaces
-r--r--r-- 1 root root 4096 Mar 7 00:22 bcdDevice
-r--r--r-- 1 root root 4096 Mar 7 00:22 bmAttributes
-r--r--r-- 1 root root 4096 Mar 7 00:22 busnum
-r--r--r-- 1 root root 4096 Mar 7 00:22 configuration
-r--r--r-- 1 root root 65553 Mar 7 00:22 descriptors
-r--r--r-- 1 root root 4096 Mar 7 00:22 dev
-r--r--r-- 1 root root 4096 Mar 7 00:22 devnum
-r--r--r-- 1 root root 4096 Mar 7 00:22 devpath
lrwxrwxrwx 1 root root 0 Mar 7 00:22 driver -> ../../../../../../../bus/usb/drivers/usb
drwxr-xr-x 3 root root 0 Mar 7 00:22 ep_00
-r--r--r-- 1 root root 4096 Mar 7 00:22 idProduct
-r--r--r-- 1 root root 4096 Mar 7 00:22 idVendor
-r--r--r-- 1 root root 4096 Mar 7 00:22 maxchild
drwxr-xr-x 2 root root 0 Mar 7 00:22 power
-r--r--r-- 1 root root 4096 Mar 7 00:22 quirks
--w------- 1 root root 4096 Mar 7 00:22 remove
-r--r--r-- 1 root root 4096 Mar 7 00:22 speed
lrwxrwxrwx 1 root root 0 Mar 7 00:22 subsystem -> ../../../../../../../bus/usb
-rw-r--r-- 1 root root 4096 Mar 7 00:22 uevent
-r--r--r-- 1 root root 4096 Mar 7 00:22 urbnum
drwxr-xr-x 3 root root 0 Mar 7 00:22 usb_device
-r--r--r-- 1 root root 4096 Mar 7 00:22 version
localhost / # ls -l /sys/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1:1.0
-r--r--r-- 1 root root 4096 Mar 7 00:22 bAlternateSetting
-r--r--r-- 1 root root 4096 Mar 7 00:22 bInterfaceClass
-r--r--r-- 1 root root 4096 Mar 7 00:22 bInterfaceNumber
-r--r--r-- 1 root root 4096 Mar 7 00:22 bInterfaceProtocol
-r--r--r-- 1 root root 4096 Mar 7 00:22 bInterfaceSubClass
-r--r--r-- 1 root root 4096 Mar 7 00:22 bNumEndpoints
lrwxrwxrwx 1 root root 0 Mar 7 00:22 driver -> ../../../../../../../../bus/usb/drivers/hub
drwxr-xr-x 3 root root 0 Mar 7 00:22 ep_81
-r--r--r-- 1 root root 4096 Mar 7 00:22 modalias
drwxr-xr-x 2 root root 0 Mar 7 00:22 power
lrwxrwxrwx 1 root root 0 Mar 7 00:22 subsystem -> ../../../../../../../../bus/usb
-r--r--r-- 1 root root 4096 Mar 7 00:22 supports_autosuspend
-rw-r--r-- 1 root root 4096 Mar 7 00:22 uevent
I've also played around a little bit, but without any further progress...
- tried to just mount hdd over whatever is on /storage/sdcard0 -> doesn't work as sdcard0 is a link to Storage/emulated/legacy which itself is again a link to /mnt/shell/emulated/0 and apps seem to use that. Mounting on top of /mnt/shell/emulated/0 also doesn't work for some reason unknown to me :crying:
- had a look at vold configuration file in /system/etc/vold.A80H.fstab (in the case of my A80), but I don't even know if that file is interpreted at some time. Changing the faulty hdd path in there had no effect whatsoever.
I'm back to one of the rooted Archos Images, as I want to actually use the thing again I don't think there is a way to dual boot to do some further investigations?
Hi @Quallenauge,
(I don't know if I can talk about it here but it has a relation with the latest kernel update you've done) With your last update, I have a little problem : Indeed my Internal storage is recognized as an external SDcard when I use the file explorer and also I don't have access to the contents of my Internal storage in my computer.
Thank you in advance.
Hi again,
I could actually manage to use the HD for apps and data. It was easier than expected, but still a hack and need some tuning. So don't blame me if it doesn't run on your device.
Okay here is what I have done:
(I use Ubuntu and don't know how to do it on Windows or iOS)
a) Reset and format the device and the HD to start with a clean environment. (Don't forget to save your data somewhere outside)
b) Download and extract @Quallenauge 's CM11 ROM 09_03_2014-12_04_52
c) Mount the archos.ext4.update file
d) Fix the init.archosa101hboard.rc (init.archosa80hboard.rc) file to get the correct file loaded fstab.archosa101hboard (fstab.archosa80hboard.rc)
-> Just seach for 101s (80s) and change to 101h (80h)
e) Change fstab.archosa101hboard (fstab.archosa80hboard.rc) to use the HD for /data:
Code:
#/dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,barrier=1 wait
#/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 nosuid,nodev,barrier=1 wait,check
#/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 noatime,nosuid,nodev,barrier=1,discard,noauto_da_alloc,journal_async_commit wait,check,encryptable=footer
#/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 noatime,nosuid,nodev,barrier=1,discard,noauto_da_alloc,journal_async_commit wait,check
# mount rawfs /dev/block/mmcblk0p1 /mnt/rawfs
# mount ext4 /dev/block/mmcblk0p2 /mnt/system noatime nosuid noexec
# mount ext4 /dev/block/mmcblk0p4 /data noatime nosuid
#/dev/block/mmcblk0p1 /mnt/rawfs rawfs
/dev/block/mmcblk0p2 /mnt/system ext4 noatime,nosuid,noexec wait
#/dev/block/mmcblk0p4 /data ext4 noatime,nosuid wait,check,encryptable=footer
/dev/block/platform/omap/usbhs_omap/sda1 /data ext4 defaults 0 2
/devices/platform/omap/omap_hsmmc.0 auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/omap/musb-omap2430/musb-hdrc/usb2/2-1/2-1:1.0 auto auto defaults voldmanaged=usbdisk:auto
#/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2
/dev/block/zram0 none swap defaults zramsize=134217728
f) Unmount the archos.ext4.update file
g) Install as usual
My impressions:
- I could install all (!) my apps :laugh:
- I have still only 512 MB RAM, so e.g. Adblock Plus be stopped when Chrome is running. I have installed Greenify, which helps a bit. Need more investigation. Any thoughts are welcome!
- Booting takes a bit longer
- As the HD is used to falling quick back in sleep mode and it cannot cache all needed files, it takes some extra time to open an app or switch to one of the other screens.
- Don't know what to do with /dev/block/mmcblk0p4 - Can we use it for caching the HD or as swap device?
- After some time sleeping, the device need to reboot by long pressing on/off (I think that is in discussion in the main [ROM] [4.4.2] CyanogenMod 11.0 thread)
- Not tested yet, but activating the 3g dongle for USB memory would change the HD partiion from sda1 to sdb1, so wouldn't run. Maybe copying the HD to a SD card would be nice to have.
- Battery time: Don't know, as it is always plugged in
At the end I think it is the best ROM for this poor device - so thanks again @Quallenauge
[email protected] said:
Hi again,
I could actually manage to use the HD for apps and data. It was easier than expected, but still a hack and need some tuning. So don't blame me if it doesn't run on your device.
Okay here is what I have done:
(I use Ubuntu and don't know how to do it on Windows or iOS)
a) Reset and format the device and the HD to start with a clean environment. (Don't forget to save your data somewhere outside)
b) Download and extract @Quallenauge 's CM11 ROM 09_03_2014-12_04_52
c) Mount the archos.ext4.update file
d) Fix the init.archosa101hboard.rc (init.archosa80hboard.rc) file to get the correct file loaded fstab.archosa101hboard (fstab.archosa80hboard.rc)
-> Just seach for 101s (80s) and change to 101h (80h)
e) Change fstab.archosa101hboard (fstab.archosa80hboard.rc) to use the HD for /data:
Code:
#/dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,barrier=1 wait
#/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 nosuid,nodev,barrier=1 wait,check
#/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 noatime,nosuid,nodev,barrier=1,discard,noauto_da_alloc,journal_async_commit wait,check,encryptable=footer
#/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 noatime,nosuid,nodev,barrier=1,discard,noauto_da_alloc,journal_async_commit wait,check
# mount rawfs /dev/block/mmcblk0p1 /mnt/rawfs
# mount ext4 /dev/block/mmcblk0p2 /mnt/system noatime nosuid noexec
# mount ext4 /dev/block/mmcblk0p4 /data noatime nosuid
#/dev/block/mmcblk0p1 /mnt/rawfs rawfs
/dev/block/mmcblk0p2 /mnt/system ext4 noatime,nosuid,noexec wait
#/dev/block/mmcblk0p4 /data ext4 noatime,nosuid wait,check,encryptable=footer
/dev/block/platform/omap/usbhs_omap/sda1 /data ext4 defaults 0 2
/devices/platform/omap/omap_hsmmc.0 auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/omap/musb-omap2430/musb-hdrc/usb2/2-1/2-1:1.0 auto auto defaults voldmanaged=usbdisk:auto
#/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2
/dev/block/zram0 none swap defaults zramsize=134217728
f) Unmount the archos.ext4.update file
g) Install as usual
My impressions:
- I could install all (!) my apps :laugh:
- I have still only 512 MB RAM, so e.g. Adblock Plus be stopped when Chrome is running. I have installed Greenify, which helps a bit. Need more investigation. Any thoughts are welcome!
- Booting takes a bit longer
- As the HD is used to falling quick back in sleep mode and it cannot cache all needed files, it takes some extra time to open an app or switch to one of the other screens.
- Don't know what to do with /dev/block/mmcblk0p4 - Can we use it for caching the HD or as swap device?
- After some time sleeping, the device need to reboot by long pressing on/off (I think that is in discussion in the main [ROM] [4.4.2] CyanogenMod 11.0 thread)
- Not tested yet, but activating the 3g dongle for USB memory would change the HD partiion from sda1 to sdb1, so wouldn't run. Maybe copying the HD to a SD card would be nice to have.
- Battery time: Don't know, as it is always plugged in
At the end I think it is the best ROM for this poor device - so thanks again @Quallenauge
Click to expand...
Click to collapse
Nice work [email protected] I'm glad someone is still trying to bring this tablet to the present. Let me know if you need a tester. I have a 80 G9 Turbo 250GB.