ASUS Transformer -- Latest version of Revolver, using v22a of supercurios kernal, and the ice cream sandwich theme, v2.
I've searched and searched, bu haven't found a case similar to mine.
When trying to download and install or update apps, I always get a notification saying that there was "insufficient storage available".
I have over 3 gigs free on the Internal memory, and nearly 6 on my microsd card.
I've read about people wiping or deleting items in the dalvik cache, and I've read about clearing market data.
My problem is, some say that wiping the dalvik cache on custom roms can break them, requiring a new flash.
I also have another problem. Nearly 100% of the time, downloads fail in the stock browser. I'm not sure if they fail in other browsers, but frankly I don't care-- I haven't come across a single browser in the market that I actually like. Most aren't even worth the megabytes they eat up.
And I also can't get over the fact that one of androids nucest features of all times, the move apps to SD card function, is unavailable to me. This makes my 80 dollar high-speed microsd card that I bought specifically for fast application use useless.
What can I do about either issue? The app update and install and the storage issue is a priority for me.
I would be interested in what the output of 'df -hPa' is on your system (in the terminal).
Sent from my Transformer TF101 using Tapatalk
yup, i get that as well at times, it really is annoying however, a reboot normally always fixes it and a wiping of any and all caches (from recovery) will keep that problem from coming back for a long time. I always make backups (once a week) so that if I wipe the cache wrong or something, I can restore from the recovery backup I made. I havent had to reflash a rom yet (crosses fingers)
Spidey01 said:
I would be interested in what the output of 'df -hPa' is on your system (in the terminal).
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Spidey.. got this today driving me mad..
here is my output in terminal..
'df -hPa' = Filesystem 1k-blocks Used Available Use% Mounted on df: hPa: can't find mount point.
ok.. whats this telling me?
I have wiped cache's
un-installed a couple of big programs/games..
TB is reporting that I have the following..
System rom: 528MB(127MB Free)
Internal 13.3GB(8.51GB Free)
SD card 13.3GB(8.51GB Free)
settings/storage is showing..
12.43GB with 7.93GB free..
I undocked it, rebooted it..
pulled out the SDcard and tried to install..
but no joy..
looks like maybe a reinstall of the Rom, then slowly load things back in..
edits: looks like a mounting problem.. as the dock is not mounting usb1 for the external now..
will flash Blades kernel and see if it sets things right..
as the only difference in my set-up has been to flash Roachs kernel during the week..
a Kernel flash didn't fix it so am doing a full reset...
K..after a full Factory/data reset..
TB give me this now.. (Market loaded a few in.. but I stopped it.. )
System rom: 528MB(108MB Free)
Internal 13.3GB(9.08GB Free)
SD card 13.3GB(9.08GB Free)
settings/storage is showing..
12.43GB with 8.46GB free..
Will load TB backup back in and see if the problem starts again..
But If I have had this problem.. I am sure others will come across it..
as it seems I got a corrupted file somewhere in there,
will keep an eye on it and see if it happens again..
but for sure, there was a corrupt system file..
Anyone know which are the actual system files are called for the mounting operation?
**** happened again today..
after a clean install.. ran well yesterday..
this morning plugged in the USB Drive into the right USB and had a USB mouse in the left USB..
wonder if this is doing something to mount files?
Anyone know which are the actual system files are called for the mounting operation?
I might run with just the sdcard for the rest of the week shifting things on to it..
and see if I am getting a spike, hooking up with the usbdrive that is corrupting mounting files..
as this would seem like the problem.. its a western digital 500g portable that I am plugin and unpluggin
I modded the flash.cfg file in nvflash and increased my system partition from 512mb to 768mb. It works great. If anyone is interested in increasing their system partition size, I can post what I did to do it. You would need to backup your stuff as it wipes everything when you flash the new partitions.
romified said:
I modded the flash.cfg file in nvflash and increased my system partition from 512mb to 768mb. It works great. If anyone is interested in increasing their system partition size, I can post what I did to do it. You would need to backup your stuff as it wipes everything when you flash the new partitions.
Click to expand...
Click to collapse
I wouldn't mind knowing how.. incase I need to do it..
mine has settled this week as not been plugging/unplugging in the USB hard-drive..
so I have narrowed it down to this spike corrupting some files..
I have backed up the system/lib files incase I have to dump them back over top of corrupted ones.. as it will save a new Rom Flash..
as still not had time to narrow down the actual file or files needed for Mounting USB's in the Rom
If you could post here or PM.. would be grateful..
Basically you just use nvflash to flash a ROM, I flashed Prime since there was a nvflash version available.
All you have to do is edit the flash.cfg file in nvflash, and make the following change, and your system partition will go from 512mb to 768mb. I was trying to port a large ROM and kept running out of space, I made this change and never had a space issue since.
REMEMBER: nvflash will wipe all of your files and data, recovery and kernel as well. So make sure whatever you flash with nvflash is what you want in place. You can of course always reflash through regular CWM to any rom as well after using nvflash. You just need to flash something with nvflash to make the partition changes. And remember if you use nvflash in the future, if you do not edit the flash.cfg file per below, nvflash will partiton system back to 512mb when you use it.
It is only one line, so this is VERY easy. I have only tested this on a TF101-A1. I am not sure what the 32 GB (B1) models partition layout is like.
Open the flash.cfg file, and look for this (it started on line 93 of the flash.cfg I have):
Code:
[partition]
name=APP
id=9
type=data
allocation_policy=sequential
filesystem_type=basic
size=536870912
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=system.img
Change the "size=536870912" to "size=805306368" and save the file. The above section should now look like this :
Code:
[partition]
name=APP
id=9
type=data
allocation_policy=sequential
filesystem_type=basic
size=805306368
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=system.img
Now use nvflash as normal and your system partition will be 768mb.
I am not sure what the limit is on size or what else can be changed, so if you test, do so at your own risk, I have only changed system to 768mb. I think partition 16 is elastic and sizes based on space left over from other partitions (so this is where the extra space for system comes from), but I am not 100% sure on this yet. But do let us know if you do experiment as to what you learn
By the way, the "805306368" number is a number calculated based on bytes & cylinders (or something along those lines) :
1024 x 1024 (1048576) x size in mb = size used in above example
ie: 1048576 x 768 = 805306368
dgcruzing said:
'df -hPa' = Filesystem 1k-blocks Used Available Use% Mounted on df: hPa: can't find mount point.
Click to expand...
Click to collapse
Maybe a typo or damaged mount point? /system, /data, and /cache are what matters.
Code:
Thank you for using Better Terminal Emulator Pro
/ $ df --help
BusyBox v1.16.2androidbtep (2011-08-11 14:16:08 PDT) multi-call binary.
Usage: df [-Pkmhai] [-B SIZE] [FILESYSTEM]...
Print filesystem usage statistics
Options:
-P POSIX output format
-k 1024-byte blocks (default)
-m 1M-byte blocks
-h Human readable (e.g. 1K 243M 2G)
-a Show all filesystems
-i Inodes
-B SIZE Blocksize
/ $ df -Pha
Filesystem Size Used Available Capacity Mounted on
tmpfs 364.2M 32.0K 364.2M 0% /dev
devpts 0 0 0 0% /dev/pts
proc 0 0 0 0% /proc
sysfs 0 0 0 0% /sys
debugfs 0 0 0 0% /sys/kernel/debug
none 0 0 0 0% /acct
tmpfs 364.2M 0 364.2M 0% /mnt/asec
tmpfs 364.2M 0 364.2M 0% /mnt/obb
none 0 0 0 0% /dev/cpuctl
/dev/block/mmcblk0p1 503.9M 403.5M 100.5M 80% /system
/dev/block/mmcblk0p7 27.3G 4.1G 23.3G 15% /data
/dev/block/mmcblk0p2 512.8M 16.0M 496.8M 3% /cache
tmpfs 364.2M 0 364.2M 0% /Removable
/dev/fuse 27.3G 4.1G 23.3G 15% /mnt/sdcard
tmpfs 364.2M 32.0K 364.2M 0% /data/local/mnt/Linux/dev
devpts 0 0 0 0% /data/local/mnt/Linux/dev/pts
proc 0 0 0 0% /data/local/mnt/Linux/proc
sysfs 0 0 0 0% /data/local/mnt/Linux/sys
debugfs 0 0 0 0% /data/local/mnt/Linux/sys/kernel/debug
none 0 0 0 0% /data/local/mnt/Linux/acct
tmpfs 364.2M 0 364.2M 0% /data/local/mnt/Linux/mnt/asec
tmpfs 364.2M 0 364.2M 0% /data/local/mnt/Linux/mnt/obb
none 0 0 0 0% /data/local/mnt/Linux/dev/cpuctl
/dev/block/mmcblk0p1 503.9M 403.5M 100.5M 80% /data/local/mnt/Linux/system
/dev/block/mmcblk0p7 27.3G 4.1G 23.3G 15% /data/local/mnt/Linux/data
/dev/block/mmcblk0p2 512.8M 16.0M 496.8M 3% /data/local/mnt/Linux/cache
tmpfs 364.2M 0 364.2M 0% /data/local/mnt/Linux/Removable
/dev/fuse 27.3G 4.1G 23.3G 15% /data/local/mnt/Linux/mnt/sdcard
/ $
The other stuff you posted makes sense to me, as long as you have a 16GB TF and not a 32GB like mine.
The /data/local/mnt/Linux stuff is because of my Debian chroot, and the sdcard is really a cool hack they do for mounting /data/media correctly for Android. The mmcblk devices are the partitions on the internal memory, as far as I know at least.
Applications go in /data. Your /system partition can be touched by some things but you are not generally going to be stuffing apps in there when you go to the market. You can make an app a system app with some program I think but I wouldn't reccomend it for most apps without good reason.
As root, you can see for yourself with ls what is in the file system and see how Android does stuff, it's mostly self explanitory with some poking but not as obvious as people like me (or smarter people on the subject) might think.
Idk how the file system performance would be impacted here with regards to free space, I know FreeBSD with classic UFS2 / UFS2+SU on PCs will suffer heavy performance issues if the file system is tooooo full but now I'm talking Apples and Oranges. But I would be curious how increasing the /system partition would work for performance with the TF's specifics.
Sent from my Transformer TF101 using Tapatalk
Re: Transformer 16g system partition hack
Well after having it happen again to me today, I decided to bite the bullet and spend the night doing Romified's hack..(Thanks)
I nvflashed Prime 1.7 with the adjusted flash.cfg
As a note: using Notepad++ mine was on line 99
Will load it backup and see how we go..
Fingers crossed this will settle it down..
As said before.. once the problem starts.. even wiping programs off doesn't seem to store updates or allow installs of new programs, so it seems that only a good nflash is the way to go..
Will update as the week goes on..
Getting back to the hack..
it is interesting to get in to the Linux partition reading..
As the layout here seems to give us a bit of scope to play with..
I played safe and didn't push it this time..
but.. that's not to say that there couldn't be some decent discussion on
the actual need for so many partitions and their sizes..
This was the Terminal dump before the hack and with a flash of Prime 2.1/Blades latest Kernel.(As tried everything else before going ahead with the Nvflash hack)
Code:
/ # df -Pha
df -Pha
Filesystem Size Used Available Capacity Mounted on
tmpfs 364.2M 32.0K 364.2M 0% /dev
devpts 0 0 0 0% /dev/pts
proc 0 0 0 0% /proc
sysfs 0 0 0 0% /sys
debugfs 0 0 0 0% /sys/kernel/debug
none 0 0 0 0% /acct
tmpfs 364.2M 0 364.2M 0% /mnt/asec
tmpfs 364.2M 0 364.2M 0% /mnt/obb
none 0 0 0 0% /dev/cpuctl
/dev/block/mmcblk0p1 503.9M 403.5M 100.5M 80% /system
/dev/block/mmcblk0p7 12.4G 3.2G 9.2G 26% /data
/dev/block/mmcblk0p2 521.2M 9.1M 512.1M 2% /cache
tmpfs 364.2M 0 364.2M 0% /Removable
/dev/fuse 12.4G 3.2G 9.2G 26% /mnt/sdcard
/dev/block/vold/179:9
14.7G 3.9G 10.8G 27% /Removable/MicroSD
Will post back the new dump once got things loaded and settled..
romified said:
I modded the flash.cfg file in nvflash and increased my system partition from 512mb to 768mb. It works great. If anyone is interested in increasing their system partition size, I can post what I did to do it. You would need to backup your stuff as it wipes everything when you flash the new partitions.
Click to expand...
Click to collapse
This is pointless, /System is a ReadOnly filesystem.
well its back to the drawing board for me as it came back tonight..
after loading a small-iss program of 2meg from the market..
honest this is giving me the ****s..
as internal is showing 2.2g
system is 408mb of 504mb
this is the output on terminal with "df"
Code:
/ $ export PATH=/data/local/bin:$PATH
/ $ df -Pha
Filesystem Size Used Free Blksize
-Pha: No such file or directory
/ $ df
Filesystem Size Used Free Blksize
/dev 364M 32K 364M 4096
/mnt/asec 364M 0K 364M 4096
/mnt/obb 364M 0K 364M 4096
[COLOR="Red"]/system 503M 407M 96M 4096[/COLOR]
/data 12G 2G 9G 2048
/cache 521M 8M 512M 4096
/Removable 364M 0K 364M 4096
/mnt/sdcard 12G 2G 9G 2048
/R......./MicroSD 14G 4G 10G 8192
/ $
What is painful is I am clearing cache, going in and wiping programs
not only from market and also internally.. like in private data.. also apps out of system/apps
also wiped Market cache & Data..
but it doesnt seem to free up enough memory to allow even a 160k widget to download then download
an install from market..
Edit: Just did a test.. maybe its nothing to do with the actual Rom build..or Partitions but Market itself..
as I uninstalled a program downloaded from Market using another apps manager..
had a backup of it..
then re: installed it..via Root explorer.. installed no problems.. and is a 12meg program..
K.. will do a few more tests.. maybe its an unstall of market.. or a roll back..
dgcruzing said:
well its back to the drawing board for me as it came back tonight..
after loading a small-iss program of 2meg from the market..
honest this is giving me the ****s..
as internal is showing 2.2g
system is 408mb of 504mb
this is the output on terminal with "df"
/ $ export PATH=/data/local/bin:$PATH
/ $ df -Pha
Filesystem Size Used Free Blksize
-Pha: No such file or directory
/ $ df
Filesystem Size Used Free Blksize
/dev 364M 32K 364M 4096
/mnt/asec 364M 0K 364M 4096
/mnt/obb 364M 0K 364M 4096
/system 503M 407M 96M 4096
/data 12G 2G 9G 2048
/cache 521M 8M 512M 4096
/Removable 364M 0K 364M 4096
/mnt/sdcard 12G 2G 9G 2048
/R......./MicroSD 14G 4G 10G 8192
/ $
What is painful is I am clearing cache, going in and wiping programs
not only from market and also internally.. like in private data.. also apps out of system/apps
also wiped Market cache & Data..
but it doesnt seem to free up enough memory to allow even a 160k widget to download then download
an install from market..
Edit: Just did a test.. maybe its nothing to do with the actual Rom build..or Partitions but Market itself..
as I uninstalled a program downloaded from Market using another apps manager..
had a backup of it..
then re: installed it..via Root explorer.. installed no problems.. and is a 12meg program..
K.. will do a few more tests.. maybe its an unstall of market.. or a roll back..
Click to expand...
Click to collapse
try clearing the dalvik cache that may help you
Hi Stevie,
Yes..one of the first things I did..
But to no avail..
I see by your threads that you have a fair knowledge of how the partitions work and file structures work..
Would you know what are all the files associated with market and where all the directries are associated with it..?
I have found market.apk
Market update.apk
But where is market dropping the files you buy?
And market database filed?
At the moment, I am still leaning towards market doing something screwy to me..
As the test with
1:uninstall with root explorer
2:then a reinstall with TB
Proves that I can write to the partition.
But a..
1: uninstall 2 programs- with market
(Which in theory should free space)
2: reinstall 1 program- with market
Gives me the error again..
sent from yet another MikG HTC Evo
Just wondering how much room there is on the TF for apps? Just got one over the weekend...plus I use an N1 that has >200 MB...so from what I've read in this thread so far...seems that you can load up a butt load of apps on this tablet.
dgcruzing said:
Hi Stevie,
Yes..one of the first things I did..
But to no avail..
I see by your threads that you have a fair knowledge of how the partitions work and file structures work..
Would you know what are all the files associated with market and where all the directries are associated with it..?
I have got found market.apk
Market update.apk
But where is market dropping the files you buy?
And market database filed?
At the moment, I am still leaning towards market doing something screwy to me..
As the test with
1:uninstall with root explorer
2:then a reinstall with TB
Proves that I can write to the partition.
But a..
1: uninstall 2 programs- with market
(Which in theory should free space)
2: reinstall 1 program- with market
Gives me the error again..
sent from yet another MikG HTC Evo
Click to expand...
Click to collapse
It should download it to /cache then install it to /data nothing else
---------- Post added at 12:59 PM ---------- Previous post was at 12:58 PM ----------
SiNJiN76 said:
Just wondering how much room there is on the TF for apps? Just got one over the weekend...plus I use an N1 that has >200 MB...so from what I've read in this thread so far...seems that you can load up a butt load of apps on this tablet.
Click to expand...
Click to collapse
because /data and the emmc share the same partition, it is as much as you can store on your tablet, so 14ish GB on a 16GB device and 28ish GB on a 32GB device, unless of course you are running ubuntu in dual boot which shrinks the size of /data
lilstevie said:
It should download it to /cache then install it to /data nothing else
---------- Post added at 12:59 PM ---------- Previous post was at 12:58 PM ----------
because /data and the emmc share the same partition, it is as much as you can store on your tablet, so 14ish GB on a 16GB device and 28ish GB on a 32GB device, unless of course you are running ubuntu in dual boot which shrinks the size of /data
Click to expand...
Click to collapse
Yes, this is what I was figuring too.. that's why its frustrating me to be getting this error and leading me to believe that its a market problem..
I have already ruled out a space problem..
as time permits, I am going to wipe market off and try to install another version and see what happens..
This is why I am in the need of ALL files that point to and are called by market to wipe off it.. so that there are no rouge orphan files around..
Then of course going to have to hunt down a another copy to load in..
which I should be able to pull from one of the Roms..
as I dont want to use the one in Roach's Rom.. as this is the one that is maybe causing problems..(Via some unexplained help from Market update)
Note of course.. that I am not saying that it is anything to do with Roach's Rom and or files in it.. as I am still in the investigation stage of why I am getting the error..
dgcruzing said:
Yes, this is what I was figuring too.. that's why its frustrating me to be getting this error and leading me to believe that its a market problem..
I have already ruled out a space problem..
as time permits, I am going to wipe market off and try to install another version and see what happens..
This is why I am in the need of ALL files that point to and are called by market to wipe off it.. so that there are no rouge orphan files around..
Then of course going to have to hunt down a another copy to load in..
which I should be able to pull from one of the Roms..
as I dont want to use the one in Roach's Rom.. as this is the one that is maybe causing problems..(Via some unexplained help from Market update)
Note of course.. that I am not saying that it is anything to do with Roach's Rom and or files in it.. as I am still in the investigation stage of why I am getting the error..
Click to expand...
Click to collapse
is this on one rom? or has it happened to you on a few, and what rom are you running
lilstevie said:
is this on one rom? or has it happened to you on a few, and what rom are you running
Click to expand...
Click to collapse
Been on Roach's with C& B Kernel.. first time it happened swopped out to Blades Kernel..
Maybe its a Rom swop for a while to see if it settles..
might save the time spent on hunting down the problem..
Got a trip for a few weeks so don't want to be stressed with this on the road..
so got to get it settled in the next few days..
edit: going to run out of time.. as said on the road from Sunday..so decided to go a new Rom flash..
This is how it is looking like at the moment..
Code:
export PATH=/data/local/bin:$PATH:.
/ # export PATH=/data/local/bin:$PATH:.
/ # df
Filesystem Size Used Free Blksize
/dev 364M 32K 364M 4096
/mnt/asec 364M 0K 364M 4096
/mnt/obb 364M 0K 364M 4096
[COLOR="Red"]/system 755M 296M 459M 4096[/COLOR]
/data 12G 1G 10G 4096
/cache 521M 8M 512M 4096
/Removable 364M 0K 364M 4096
/mnt/sdcard 12G 1G 10G 4096
/Removable/MicroSD 14G 4G 9G 8192
/ #
interesting comparing it to the last one posted last night..
I have now got the full 755m in system as per nvflash..
as last one is only showing 503m with most of the same apps loaded back in..
I have done :
Mike1986 super wipe..
Then loaded in KRAKD rom..
Blue theme
Blades CptAwesome 12-07
let see how it goes..
Related
So all of my apps from the market aren't working. I have apps and cache to SD and the SD still seems to work (can still access pictures saved) so I'm not sure what's wrong.
Any app I try to open will force close immediately (or almost immediately). Stock apps still work though.
Not sure what went wrong, I didn't do anything new when this error occured.
Anyone have bright ideas on how to fix it?
I'm thinking the EXT2 partition might be corrupted, but if so, wouldn't more crashes happen with the browser and such, since I have cache to SD as well? I haven't had a chance to check yet on that though.
Extra info in case it helps:
$ busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 48.4M 0 48.4M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 67.5M 67.0M 516.0K 99% /system
/dev/block/loop0 1.5M 1.5M 0 100% /system/modules
/dev/block/loop1 3.1M 3.1M 0 100% /system/xbin
/dev/mmcblk0p2 220.3M 67.9M 141.0M 33% /system/sd
/dev/block/mtdblock5 74.8M 43.3M 31.5M 58% /data
/dev/block/mtdblock4 67.5M 2.2M 65.3M 3% /cache
/dev/block/mmcblk0p1 743.7M 419.2M 324.5M 56% /sdcard
I'll probably dig around for my Ubuntu live CD this weekend to check the partition. Hoping to find a solution before then.
Did you try to re-install the apps ? I fixed mine that way
Doing so works, but I have over 50 apps installed and would take a while, plus I would lose all of my settings and data. Is there any other method?
Thanks for the suggestion though. Hadn't thought of that one earlier.
I was trying to use the new Apps2SD method by Marcus and I seem to be running into a problem. When I try to remove the unionfs partition through either G-Parted or disk utility I cannot remove/format it.
As far as I'm aware unionfs is NOT supported in G-parted nor in Mac OS. I only have a 1GB FAT32 partition and the other 3GB seem to be lost. I searched the forums and Google but cannot find anything. Does anyone have any suggestions?
im not sure what are you trying to do, but you can repartition removing phone's sd card and plugin it into a computer. If you want to repartition / change partitions with you phone acting as sd card reader connected with usb, you will have to undo unionfs process before trying to repartition / make any changes to sdcard
that last can be acomplished removing /data/init.rc and /data/a2sd.sh and rebooting the phone.
if this doesnt help you, provide more info, like the output of "df" command.
What I'm trying to do is restart Marcus's unionfs Apps2SD by destroying the partitions so I can get a fresh start. I tried deleting the 2 files you told me about but that didn't work. Heres the output of df:
# busybox df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 49356 0 49356 0% /dev
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
/dev/block/mtdblock3 92160 60244 31916 65% /system
/dev/block/loop0 492 492 0 100% /system/modules
/dev/block/loop1 3524 3524 0 100% /system/xbin
/dev/block/mtdblock5 91904 23756 68148 26% /data
/dev/block/mtdblock4 30720 1160 29560 4% /cache
/dev/block//vold/179:1
991664 0 991664 0% /sdcard
Thanks!
Trying to get Dexter's native ext2 support working.
I pulled my SD card (8gb) and using GParted within Ubuntu, deleted my FAT32 partition, created 1st partition FAT32 ~7gb, 2nd partition ext2 (1gb), 3rd partition SWAP (64mb)
I understand that with Dexter's 1.1b, when the phne is booted with the card in, it should find the ext2 partition and proceed to move my apps to this partition.
Note, I also tried ext3 in the same partition configuration.
Under memory/sd card sotrage, phone is reading ~6.9GB as expected of the FAT32 partition.
Am I missing a step? Nothing ever gets moved from the phone to the card's ext2 partition.
ext2,3 problem on dexters rom
Sorry first post noob, hopefully im doing this right
I used mini tool partition wizard... i tried ext2 then ext3, made them logical and primary, with the swap partition. (do we need that swap ..i haven't tried it without it).
And the entire memory card wouldn't be recognised/mount at all when turning on the phone. I had to remove the partitions to be able to use the memory card in the normal manner.
is there another step? i was hoping all i had to do was make the partition and it would be done.
help!
did u guys set the ext partition to active?
I did not mark any partition active (none of the many guides on the net say anything about setting partition flags). My layout (per parted) looks like this:
Code:
Number Start End Size Type File system Flags
1 1049kB 6818MB 6817MB primary fat32
2 6818MB 7892MB 1074MB primary ext2
3 7892MB 7959MB 67.1MB primary linux-swap
Which matches every screenshot I have seen of parted/Gparted in any formatting guide.
I did find one that had fat32 marked as lba, but that makes no difference.
R-D said:
I understand that with Dexter's 1.1b, when the phne is booted with the card in, it should find the ext2 partition and proceed to move my apps to this partition.
Note, I also tried ext3 in the same partition configuration.
Click to expand...
Click to collapse
What is the output of "mount" after your phone boots up? Check if it is mounted already. If not try to mount it manually. At least we'll know if the issue is in phone recognizing the partitions.
I realised what i did wrong ..I tried to make the ext2 partition after I 'installed/flashed' dexters rom ...this messed everything up for me.
So I re-did the entire process but made my ext2 partition first. Now its allgood
Don't know if that helps
Sent from my XT720 using XDA App
kousik said:
What is the output of "mount" after your phone boots up? Check if it is mounted already. If not try to mount it manually. At least we'll know if the issue is in phone recognizing the partitions.
Click to expand...
Click to collapse
Here's the default mount output:
Code:
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock7 /system yaffs2 ro 0 0
/dev/block/mtdblock9 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock8 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock6 /cdrom yaffs2 rw 0 0
tmpfs /tmp tmpfs rw,size=2048k 0 0
tmpfs /skttmp tmpfs rw,size=2048k 0 0
/dev/block/mtdblock0 /pds yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock7 /system/lw yaffs2 ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
none /acct cgroup rw,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
tmpfs /tmp tmpfs rw,size=2048k 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,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:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,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,size=0k,mode=000 0 0
When I try and mount it manually, which device name is preferred? I found the partitions (1 = fat32, 2 = ext2, 3 = swap) as these names:
/dev/block/vold/179:1
/dev/block/mmcblk0p1
/dev/block/vold/179:2
/dev/block/mmcblk0p2
/dev/block/vold/179:3
/dev/block/mmcblk0p3
I can mount partition 1 manually referencing either device name, but when I try to mount partition 2 it says: mount: No such device
I know it is the right device because I can mount the fat32 partition.
Thanks for your help.
Edit: I saw in dateno1's script in the dev thread, he is doing insmod /system/lib/modules/ext2.ko before the mount, I do not have this module (I know he has it in his download package) but should I already have this in /system/lib/modules? Does this exist already for anyone else? Or am I guessing at the wrong thing?
R-D said:
I can mount partition 1 manually referencing either device name, but when I try to mount partition 2 it says: mount: No such device
I know it is the right device because I can mount the fat32 partition.
Edit: I saw in dateno1's script in the dev thread, he is doing insmod /system/lib/modules/ext2.ko before the mount, I do not have this module (I know he has it in his download package) but should I already have this in /system/lib/modules? Does this exist already for anyone else? Or am I guessing at the wrong thing?
Click to expand...
Click to collapse
"No such device" is indication that the kernel module is not loaded properly.
You may have to insmod ext2.ko yourself to get it to work. If you do not have the .ko files, you can download from http://dateno1.egloos.com/27191 yourself and copy to /system/lib/modules. Also you can see this thread http://forum.xda-developers.com/showthread.php?t=929871 for reference.
Okay, mystery solved!
I am missing these modules as I grabbed the "original" 1.1b update (1.1a-update.zip). This original file was missing these modules and had an incorrect overclock module.
I just re-downloaded 1.1b again, and found that if I look in the ZIP file, it has the missing modules I didnt initially get.
In speaking with Dexter, it seems that he updated the 1.1b (1.1a-update.zip) file twice, but kept the same file and version name. So the 1.1b everyone else is using, is newer than the 1.1b I downloaded, as I downloaded it right after it was first posted and missed the next update as it had the same filename.
Essentially, what amounted to 1.1c was also released as 1.1b ...
So lesson is, either redownload and apply the 1.1b update, or update to 1.2 (or newer as they come).
Thanks for your help.
Oh ! Confusing this 1.1a/b/c !
is it nid to do it manually? 1.1b did detect my ext2.. but in 1.2 did not detect.. i try put ext2 and ext4 ald..
Has anyone else run into a situation where your tablet has received a low space warning on your Transformer but you haven't installed/used a lot of space?
When I look at my storage break down I use about 400mb of media and 12GB+ of application. When I view by application there is no way that it's 12GB. So I installed DiskUsage and the "system data" is using 11GB on it's own. I am suspecting it some how related to system crashes but have not confirmed this. Anyone else?
I am having the same problem just different amount of space shown
I've been digging around in adb tonight trying to get to the bottom of this:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell df
Filesystem Size Used Free Blksize
/dev 364M 32K 364M 4096
/mnt/asec 364M 0K 364M 4096
/mnt/obb 364M 0K 364M 4096
/system 503M 340M 163M 4096
/data 13G 11G 1G 4096
/cache 521M 8M 512M 4096
/mnt/sdcard 13G 11G 1G 4096
I've been trying to get a good look into /data, but it's a system owned directory and you need root access to view some of the contents.
When I try to run:
adb shell ls /data
It responds:
opendir failed, Permission denied
Looks like I will have to root to continue the hunt, because I want to find the cause. The unfortunate thing is I need to revert my version back to 8.3.2.9 to be able to perform the root successfully. About to begin work on that now.
Is it when you are updating apps in the market and the app installation fails with a low space warning?
My Nexus S does that (with over 6gb available), then re-try the install and it works. Not sure where the issue is.
@tekkitan my big concern is:
Code:
/data 13G 11G 1G 4096
/mnt/sdcard 13G 11G 1G 4096
Because I've only used about 500MB's of space.
But you are correct I get the error trying to install from the market, and sometime if I delete some apps I can make enough room to install a new one.
There is a difference between 2.x and 3.x of android and how it allot's space for apps. In 2.x there is a partition that is limited size where you can install apps no matter the size of the onboard memory, unless you root and work around it. In 3.x they changed that and all free space can be used for apps.
So I can't perform the root tonight, I don't have a microSD card I can use to downgrade to 8.2.3.9. Will have to wait until tomorrow now.
wildbohr said:
@tekkitan my big concern is:
Code:
/data 13G 11G 1G 4096
/mnt/sdcard 13G 11G 1G 4096
Because I've only used about 500MB's of space.
But you are correct I get the error trying to install from the market, and sometime if I delete some apps I can make enough room to install a new one.
There is a difference between 2.x and 3.x of android and how it allot's space for apps. In 2.x there is a partition that is limited size where you can install apps no matter the size of the onboard memory, unless you root and work around it. In 3.x they changed that and all free space can be used for apps.
Click to expand...
Click to collapse
The Nexus S only has internal storage so it is similar.
Did you try just re-trying the download instead of removing apps? Like I said, if I just simply retry the isntallation/update, it works just fine.
I can't get imagine how apps could significantly impact the internal memory on a 16 or 32gb TF.
I've been loading apps on my Droid X internal 8gb memory with wild abandon for almost a year, and have only used up about 3gb. Tablet scaled apps might be somwhat larger, of course, but not that big.
Sent from my DROIDX using Tapatalk
Again I don't think it is a space issue. Just a bug with the Android Market.
Those of you who are trying to root the NEC Terrain, I've slapped together an ADB driver from the NEC NE-103T to help you out. Basically, I just modified the INF file. Really, we're supposed to use driver version number NA002 with the Terrain but I could only find NA001. It works though and you can get ADB shell etc. Despite the ADB access, I was unsuccessful at rooting the NEC Terrain with SuperOneClick and Root_with_Restore_by_Bin4ry etc. Hopefully, posting these drivers here will help someone else in cyberspace develop a feasible root method.
Here's what the zip file contains:
Obviously the modified ADB driver for NEC Terrain use
Not sure if this is correct but I also applied the ADB driver to the CDC Serial Driver and Windows didn't have a problem.
Here's what I need:
Root Method
Default Recovery Password - NEC password protected recovery mode. :-/
(Sigh), they weren't kidding when they said this phone was secure! I know this is not going to be a popular phone but dang it, I love blackberry keyboard-style Android phones and I really need a decent rooted phone to replace my aging Motorola Pro/Pro+.
tl;dr - I'm providing the missing drivers for the NEC Terrain. Someone please find a way to root it cause I've tried everything! Also, I'm looking for the default password to use Android Recovery 3e.
Hello, Is there anyway we can have help from other people to root this device?
I have tried with SuperOneclick also and with UnlockRoot and it didn't work.
Let me know. I am willing to do anything to make this work except of course stupid stuff.
Thanks Danik
Good news:
I found an exploit over here that gains a root shell (binary attached).
Bad news:
Unfortunately, even from there, running "mount -o remount,rw /system" fails.
Similarly, since /data is marked nosuid, you can't use any su command you install in there.
So...
I am able to remount / as rw and then drop an su command in /sbin. I also set up busybox in /data/local/tmp/xbin and mounted it over /system/xbin and included a link to /sbin/su in there. Of course, that gets overwritten on reboot but it's simple enough to do all this in a script and seems to be enough to get SuperSU and TiBu to run.
The next step is to figure out how to patch boot.img to disable ro.secure, etc. Extracting it should be easy now that we have root. We just need to find the right partition. There seem to be plenty of tools around for working with these images. Then we need someone brave enough to flash it back and try it.
Good news
This is good news...
One problem now, is that there is A LOT of partitions (+30).. It will take some time to get through them...
But it's a step in the right direction... great work...
/Martin
justDave said:
Good news:
I found an exploit over here that gains a root shell (binary attached).
Bad news:
Unfortunately, even from there, running "mount -o remount,rw /system" fails.
Similarly, since /data is marked nosuid, you can't use any su command you install in there.
So...
I am able to remount / as rw and then drop an su command in /sbin. I also set up busybox in /data/local/tmp/xbin and mounted it over /system/xbin and included a link to /sbin/su in there. Of course, that gets overwritten on reboot but it's simple enough to do all this in a script and seems to be enough to get SuperSU and TiBu to run.
The next step is to figure out how to patch boot.img to disable ro.secure, etc. Extracting it should be easy now that we have root. We just need to find the right partition. There seem to be plenty of tools around for working with these images. Then we need someone brave enough to flash it back and try it.
Click to expand...
Click to collapse
MrMEEE said:
This is good news...
One problem now, is that there is A LOT of partitions (+30).. It will take some time to get through them...
But it's a step in the right direction... great work...
/Martin
Click to expand...
Click to collapse
Look at 9 and 11.
justDave said:
Look at 9 and 11.
Click to expand...
Click to collapse
You are right.. There are some boot stuff (kernel and init's) on parts 9 and 11..
I have changed the ro.secure in the inits.. but I'm not able to reflash the two partitions..
I don't get any errors from dd, but got the following messages in dmesg:
<<mmc_write emmc lock write error 0x00097800 : 11
Besides from that, a lot of I/O errors.. so seems like the phone is EMMC locked as well..
hey folks, I managed to get an unlocked terrain. No joke, really unlocked! I just got it from ebay and I am using it on the Telus network in Canada. If it helps your effort to unlock it, let me know if there is any files or even the rom from this phone that you want to see. I just need instructions. On the side note, IMO, the phone is actually quite decent despite that it's running on slower CPU. It's more than capable of running all the most common apps on the market. My only problem is that the "system storage" only has 787M, while the "phone storage" has 4.34G. I can't install apps directly to the phone storage and that 787M is not enough for my use. It would be nice if I can re-partiion all the space and allocate all 4.5G to system.
Please let me know what I can do to help. Would love to see this phone root as well.
Cheers
MrMEEE said:
You are right.. There are some boot stuff (kernel and init's) on parts 9 and 11..
I have changed the ro.secure in the inits.. but I'm not able to reflash the two partitions..
I don't get any errors from dd, but got the following messages in dmesg:
<<mmc_write emmc lock write error 0x00097800 : 11
Besides from that, a lot of I/O errors.. so seems like the phone is EMMC locked as well..
Click to expand...
Click to collapse
Hey folks, so as I said in my previous post, my Terrain is unlocked, so I am just poking around and see if I can gain root to it. Looks like the ROM that my phone is using is the new one from NEC and maybe that's why it's already unlocked. Anyway, I need some help trying to root it. Looks like it's pretty lock down, I can't even access /data/local to put that run_root_shell in it, and so I put it to /sdcard but no good there neither, it won't let me run there.
[email protected]:/sdcard $ ls -la
ls -la
drwxrwxr-x system sdcard_rw 2014-04-29 23:50 .estrongs
drwxrwxr-x system sdcard_rw 1980-01-01 00:00 Android
drwxrwxr-x system sdcard_rw 2014-04-29 22:58 Download
drwxrwxr-x system sdcard_rw 1980-01-01 00:00 LOST.DIR
drwxrwxr-x system sdcard_rw 1980-01-01 00:00 Notifications
drwxrwxr-x system sdcard_rw 2014-04-29 23:49 backups
-rwxrwxr-x system sdcard_rw 89968 2013-12-06 08:54 run_root_shell
[email protected]:/sdcard $ ./run_root_shell
./run_root_shell
/system/bin/sh: ./run_root_shell: cannot execute - Permission denied
126|[email protected]:/sdcard $
Also, there aren't 30+ partitions anymore....or I could be looking at this wrong.
[email protected]:/ $ df
df
Filesystem Size Used Free Blksize
/dev 327M 76K 327M 4096
/mnt/asec 327M 0K 327M 4096
/mnt/obb 327M 0K 327M 4096
/system 1G 480M 558M 4096
/data 787M 347M 439M 4096
/persist 7M 4M 3M 4096
/cache 354M 24M 330M 4096
/tombstones 68M 4M 64M 4096
/firmware 127M 39M 88M 16384
/data/camera_socket 327M 0K 327M 4096
/data/secure/data 327M 0K 327M 4096
/mnt/sdcard 4G 3M 4G 32768
[email protected]:/ $
Any idea and help would be appreciated. And let me know if you need me to upload any files from it that can help people here to unlock theirs.
cheers
aluminumx said:
Hey folks, so as I said in my previous post, my Terrain is unlocked, so I am just poking around and see if I can gain root to it. Looks like the ROM that my phone is using is the new one from NEC and maybe that's why it's already unlocked. Anyway, I need some help trying to root it. Looks like it's pretty lock down, I can't even access /data/local to put that run_root_shell in it, and so I put it to /sdcard but no good there neither, it won't let me run there.
Click to expand...
Click to collapse
Same thing here, also unlocked device
Code:
[email protected]:/data/local $ ls
ls
opendir failed, Permission denied
Code:
mount
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
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
/dev/block/mmcblk0p12 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p15 /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p17 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
tmpfs /data/camera_socket tmpfs rw,relatime,mode=775,gid=1000 0 0
tmpfs /data/secure/data tmpfs rw,nosuid,relatime,mode=755,gid=1000 0 0
/dev/block/vold/179:14 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Forgive me for this slight OT-posting, but it's not that easy to find people with this device - let alone an unlocked one. I'm located in Germany and the device works just fine - except for the fact that neither WIFI tethering works nor syncing with Gmail App (although sync works once I connect to a WIFI Hotspot). Has anyone experienced something similar?
Have a look on my postings list or search for El Grande Partition List (if I remember that right ) by @E.V.A. there's tools for reading partition info
Bashing away at my HTC Desire C
Has anyone seen this yet? Do you think we can use it? http://i.imgur.com/TXKDpOI.png
Lets continue discussion in one thread!
http://forum.xda-developers.com/showthread.php?p=59514154#post59514154
I created a GitHub repo to collect information, also on how to disable apps (since thats as good as it gets for now).
I'm not sure how to install these drivers (it's not an executable so I've got no idea ). Where do I copy the files? to the ADB folder?