Database Users

Crippled G1 (Not Bricked) **SOLVED**

Hey guys.
I ran into some problems the other day installing a theme and after a reboot it was hanging on the Splash Screen T-Mobile G1 Screen. I thought I bricked my phone but I had the ENG SPL and someone suggested to reflash and start over with RC29 and reroot the phone. I did and it booted right up into the home screen like I just bought the phone. Now I was trying to flash the modified recovery partion but I noticed some stuff going wrong. Telnet was not downloading from the market, much less any of the apps. Telnet was neither installing from the browser nor downloading from the market. So i tried forwarding a port from my computer and connecting my G1 to Telnet via ADB from my computer which worked. I then flashed the modified recovery partition and after rebooting twice and going into the recovery utility it reads.
Android system recovery utility
E:Can't mount CACHE:recovery/command
Home+Back - reboot system now
Alt+L - toggle log text display
Alt+S - apply sdcard:update.zip
Alt+W - wipe data/factory reset
E:Can't mount CACHE:recovery/log
E:Can't mount CACHE:recovery/log
E:Can't mount CACHE:recovery/log
From this I cannot tell whether the modified recovery was flashed or not.
Now every time I try one of these options in the recovery utility, it always spit out another
E:Can't mount CACHE:recovery/log
The only thing that works is Alt+L which toggles the text but still gives me an error despite being the only option that works.
Am i screwed here or is there some way I can get my phone back on track and get it rooted and updated from RC29
NOTE: My phone still works but just in a watered down state where my phone doesn't download any apps at all
EDIT: Confirmed that I am now using test keys. It now reads:
Android system recovery utility
Using test keys.
E:Can't mount CACHE:recovery/command
Home+Back - reboot system now
Alt+L - toggle log text display
Alt+S - apply sdcard:update.zip
Alt+W - wipe data/factory reset
E:Can't mount CACHE:recovery/log
E:Can't mount CACHE:recovery/log
E:Can't mount CACHE:recovery/log
EDIT AGAIN: Here is a solution http://forum.xda-developers.com/showthread.php?p=3345258#post3345258

Just preform a whipe. I had the same issues last night.

I tried that I forgot to say too.
I can't do it in the recovery utility since it just pits out the same error everytime and when trying it from the phone itself from SD Card & Phone Storage it says something like "No reset performed because the System Clear service is not available.
Any other way from those two options to wipe my phone???

hmm I havent had this issue
just hang in there I know theres something with info or someone around who can help you. I wish i could though. good luck

I did the same (reflashed RC29) and got the same error. Thought, "Oh crap, now I've really done it." Turns out, I flashed JF 1.42 RC33 and the error went away. Of course, I was still able to download everything so it's not exactly the same issue. But the error message itself was the same. Have a backup from the outstanding Nandroid utility?

Well I do have some nandroid backups but flashing RC29 also restored the original bootloader so that means I'm not really able to flash those backups. I can't update to anything using the recovery utility so I don't know what my next move is.

Have you tried flashing rc29 again?

I hope this solves your problems. This is without the nandroid backup btw. If you dont care about backing up(or don't have astro/appsinstaller) what you have now, just skip to the *
I hope you either have appinstaller or Astro installed.
I would recommend using MyBackup, download it onto your sdcard from ur computer from http://www.mediafire.com/download.php?qmyztn0mndz. Use appinstaller/astro to install it from your SD, backup all your goodies. (for astro, the mybackup apk needs to be in backups/apps folder)
*Go back to RC29 (follow the steps here http://forum.xda-developers.com/showthread.php?t=442480)
Get hard SPL as suggested in that thread.
Install RC33/ADP1.1h (http://forum.xda-developers.com/showthread.php?t=475381)
Don't forget to upgrade your radio too (links in above thread)
Perform a wipe.
Boot to the home screen and check if everything works to your expectations. (Now is when you install Astro/appinstaller from the market)
Now install the engineering SPL.
Try instaling your nandroid backup.
NOTE: Next time you try a theme and find you are stuck at the splash screen, just reinstall the latest/greatest JF/personal image u were using.
Keep in mind themes for RC33 etc use more space so get rid of the ringtones & notifications from the system folder before installing most themes.
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm -r /system/media/audio/ringtones
rm -r /system/media/audio/notifications
Click to expand...
Click to collapse

Yes I have tried reflashing RC29 two times to no avail.
And MrBurrito I wish I was able to update my phone with any update.zip. packages but the recovery utility is not able to update with any of the packages. It just spits back out the error
E:Can't mount CACHE:recovery/log
I wish it was that easy to get it working
Any other suggestion for updating my phone without the recovery utility and fastboot?
Is there a partition called CACHE that may be causing the problem?

hey, not sure if this is any help or not but im wondering if you moved your cache to the sdcard so save room on the system memory? if so is your sdcard actually seated properly. I occasionally can't run my apps that i moved onto my sdcard cause the phone is not reading the sdcard. I take out the sdcard and reseat it and that usually does the trick. sometimes i have to reseat it 2 or 3 times before it will read. it's annoying when it happens. Other than that i'm sorry im a minnow in the ocean when it comes to linux stuff.
good luck with your phone.

Well I moved some of my cache's to my sdcard back when I had rooted RC30. Like browser, market, and a few more but I never tried moving my apps to the sdcard.

i moved everything but my cache to my sdcard. im wondering if something in the cache was moved that the phone needs but can't read cause of the sdcard not being seen. just a shot in the dark, but i've been in a place where i couldn't use my old wizard phone cause of a corrupt rom and can understand your frustration. you might try sending a private message to some of the more astute members like jesusfreke. I know he answers private messages as soon as he can and is very patient with newbs like me

I will try doing that but I'm still open to the community's answers.

I can now confirm that I am using the modified recovery.
But it is still giving the error. So it now looks like
Android system recovery utility
Using test keys
E:Can't mount CACHE:recovery/command
Home+Back - reboot system now
Alt+L - toggle log text display
Alt+S - apply sdcard:update.zip
Alt+W - wipe data/factory reset
E:Can't mount CACHE:recovery/log
E:Can't mount CACHE:recovery/log
E:Can't mount CACHE:recovery/log
I am also pretty sure the error given has to do something with the CACHE partition found in /dev/block/mtdblock4.
Every time i try to edit or modify a directory called /cache it tells me its a Read only file system

Well depending on all the signs I think there is something wrong with the cache of my phone. Market apps not downloading, Browser downloads not successfully downloading and the errors about Can't mount CACHE:recovery/log in the recovery utility. It also says says Read only file system whenever trying to do anything with a folder called /cache.
So if somebody has any suggestions on CACHE, I would appreciate it.
My last resort is a cache.img from anybody since mine seems to be corrupt or something since everytime i try to flash it from my NAND backup it keeps tell me there was an error reading the file.
If anybody has a NAND backup of cache.img file or if anybody backed up there /dev/mtd/mtd4 file from either RC29 or RC30. Preferably RC29. Please post. Thank You

the rooted .nbh
id look into flashing the nbh bassiclly treating the phone like a stock RC30, it sounds like your recovery stuff ain't playing well with others and that may reinstall all of the pooched apps and stuff.
I dunno but it don't sound good, but the rooted .nbh that freed the peeps trapped without root, uses the bootloader to re flash everything, im not an android expert but there is a holiday inn express just down the street...
bhang

I tried flashing both of the RC29 and RC30 DREAIMG.nbh to no avail either. I have to say it has to do with something the cache partition (mtdblock4). The only thing that does not get flashed when using the DREAIMG.nbh is the cache. That partition is a read only file system on my phone and I dont know how to change it to a read write so that the recovery and everything else can access it. Anybody knows how to???

i dont know what sort of console you have if any but the mount command if you can execute it will list the mounted filesystems and their current states (ro = read only rw = read/write) thats assuming you can type said command though, if you can through the output on here and i may be able to get cache writable

Here it is.
Code:
$ mount
rootfs / rootfs ro 0 0
tmpfs /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
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat rw,dirsync,nosuid,nodev,noexecuid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0
$

Okay guys i got it fixed. Thanks for all your help, especially DJ_Steve. The thing was having to mount the mtdblock4 partition (cache partition) and restarting in recovery and doing a wipe (which finally worked).
I did:
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /cache
Restart into recovery and wipe.
I think i did this before and it didnt work. O well it worked this time.
Now it shows.
Code:
$ mount
rootfs / rootfs ro 0 0
tmpfs /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
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat rw,dirsync,nosuid,nodev,noexecuid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0
$

[GUIDE] LogStructuredFileSystem SuperThread (nilfs2,f2fs)

Disclaimer, apply the following at your own risk, I plan to test most if not all of what I post but can't guarantee that you will not cause damage or lose data, and if you do I take no responsibility, that being said it is a simple adaption to current installations.
This is in no way (currently) a replacement for ext4 (or NAND), and shouldn't be seen as a replacement for NativeSD (I'm just piggybacking of their installation zips) compatibility across the board just isn't good enough yet.
Mark 1 - Nilfs2
Code:
Nilfs2 should be good as a replacement for lower class cards and may show a speed improvement on class 2/4 cards. If your installing on a fresh card and have the means to use nilfs2 then please try before/after using ext4 and report back your findings. Any requests for things currently using ext4 will be looked at to make them compatible with nilfs2 if possible.
[B]Partition creation[/B]
Currently only via a Linux OS, will try and trick a recovery to create a nilfs2 instead of ext but no promises
[I]Method 1. Terminal[/I][CODE]sudo apt-get install nilfs-tools
sudo mkfs -t nilfs2 /dev/sdc2
Changing sdc2 to the partition thats to be formatted, look in gparted to be sure your formatting the correct one
Method 2. Disk Utility
You can use Disk Utility from within a LinuxOS
Method 3. Gparted live
Partition creation should be possible using a gparted live usb or cd
Method 4. On device
Copy mkfs.nilfs2 binary to /system/xbin
duplicate fstab renaming to mtab
sudo mkfs.nilfs2 /dev/block/mmcblk0p2
ROM Modifications
Currently, starting with a NativeSD zip as a base only need to alter the install.sh and modify a few lines within the init (within /kernel/bootsd/initrd.gz)
INSTALL.SH
Code:
mount -t ext4 /dev/block/mmcblk0p2 /ext4p
change to
mount -t nilfs2 /dev/block/mmcblk0p2 /ext4p
INIT
Code:
mkdir -p /NativeSD
mount -t ext4 -o rw,noatime,nodiratime,barrier=0 /dev/block/mmcblk0p2 /NativeSD
change to
mkdir -p /NativeSD
mkdir -p /nilfs
mount -t nilfs2 /dev/block/mmcblk0p2 /nilfs
mount -t nilfs2 -o rw,noatime,nodiratime,barrier=0 /dev/block/mmcblk0p2 /NativeSD
ROM Installation
Installation confirmed working via CWM, and modified 4ext (recoverymod) (will need to test others)
After Install modifications
Download Nilfs2.zip from #2 , using a root browser or adb copy the system folder to / (thus adding the folders /files to /system). Then need to change permissions of /system/xbin/nilfs_cleanerd , /system/etc/nilfs_cleanerd.conf and /system/etc/init.d/04nilfs to 755 (permissions required will probably change at some point)
Backup
Backup of NILFS2 partition can be done by CWM but only if android is also in NAND as it needs to backup the whole system.
REQUEST: Help from any one who has experience with NiLFS2, and ideally people who have gotten the cleaner to run properly, I'm sure it ran correctly several times, but can't as yet recreate how I got it to work. Let me know if you think you can help [/COLOR][/B]
User Experience
Xylograph's user experience and benchmark NAND / EXT4 / NiLFS2
AnTuTu and Androbench benchmarks[/CODE]
F2FS
Code:
[SIZE="2"][B]Partition creation[/B]
[I][B]Linux only[/B][/I]
Download [URL="http://sourceforge.net/projects/f2fs-tools/"]f2fs tools[/URL] and extract,
cd into folder and run the following[CODE]autoreconf --install
sudo chmod +x configure
sudo ./configure
sudo make
sudo make install
Now you can format:
Code:
sudo umount /dev/sdd1
sudo mkfs.f2fs /dev/sdd1
[/SIZE][/CODE]
To do list
Tidy up the Aroma installer to say nilfs2 instead of ext
Modify a recovery (needed still???)
Modify installer to allow NAND/ext4/nilfs2 installation
Optimize init.d script
Optimize init mounts
Possible beneficial references from across the web
NiLFS website
Not sure if ext4 would have the same problem as ext2
Btrfs
Kernel updates??
Credits / Thanks
Unhelpful for the nilfs2 binaries
Xylograph and securecrt for NativeSD Installation method
ROM devs. (Updated as ROM diffs. added)
Xylograph for AOKP, PA, CyanX
Smokin901 for MIUI
Tytung for Nexus-HD2
Rick1995 for BareBones CM7
Kernel devs.
Securert
Tytung

NILFS2 SuperThread
Will fill this out in due course,
New setup, with sdcard partitions being FAT32 / EXT4 / ANY
requirement for different ROMs should be just the initrd and to change rom_name in a few files.
First change build is on post 34
Fyi. it would be relatively simple to change it to FAT32 / ANY / ANY so if you don't want an additional partition using two (fat32/nilfs2) shouldn't be a problem.
Attached is the different installer files, should be self explanitory, really just need the NAND_ANY_ANY one, but there you go.
NAND_ANY_ANY is the only one without included initrd.gz's, will eventually add a readme detailing what you need to change in the zip, for installing other ROMs and attach a list of initrd's for different roms and partition types / locations

ROM diff files attached, edit the files in the relevant NativeSD zips. And install via recovery.
Have modified securecrt's diff file for BBCM7 - although am having some issues wouldn't advise its use (yet) DON'T USE BBCM7
General
The nilfs2 mounts with the general mount script mount and not the mount.nilfs2.
Need reports on any settings that should help the system; for example noop seems to be the best i/o scheduler for me but have no confirmation from others
Attached Files
ROM 7zip files contain the different files from there corresponding NativeSD zip
All bins and .conf that I've found can be found in nilfs.7z
Nilfs2.zip contains the 3 files needed for the cleaner to work, just copy system over using a root browser and give the three file execution permission.
Init.d script
Original - confirmed working - just point to nilfs_cleanerd . If not already present add the following to /system/etc/init.d/ and chmod +x (or chmod 755) it via terminal/root explorer
Code:
#!/system/bin/sh
/system/xbin/nilfs_cleanerd
Currently trying the following - will probably be implemented within ramdisk at some point - adapted from unhelpful's user_init
Code:
#!/system/bin/sh
export PATH=$PATH:/system/xbin
exec >/system/nilfs2_mount.log
exec 2>&1
set -x
umount /nilfs
time mount -t nilfs2 -o noatime /dev/block/mmcblk0p2 /nilfs
nilfs_cleanerd -c /system/etc/nilfs_cleanerd.conf /dev/block/mmcblk0p2 /nilfs
Edit: files attached as ROM_NAME_initrd.gz need to just be renamed as initrd.gz

HypoTurtle said:
Current relevent files can be found here
Click to expand...
Click to collapse
Thx a lot, however would you be so kind to do the same with BareBoneCM7 NativeSD?
You haven't specified in the starting post how exactly lines should be modified in the init (within /kernel/bootsd/initrd.gz) and also install.sh...

Thanks for creating this thread, HypoTurtle!
Let the ideas start to flow
I'm sure nilfs2 will take over ext4 storage as prefered format once all details are ironed out and recoveries are updated to support it.
It's technically superior to other formats for any solid state memory device.
(BTW, I sent you a PM earlier)
I'm now running CyanMobileX with your nilfs2 binaries. It's just runs flawless!, speedy and I feel my data is very safe in case of any abrupt crash or power failure.

can some one make nilfs2 for this rom :victory:
http://forum.xda-developers.com/showthread.php?t=1681906

HypoTurtle said:
After Install modifications (needs clarification in terms of location)
Will tidy this up as they should/can be included in installation/flashable zip; but using adb/root browser copy the bins and .conf file into /system/xbin. And add a script to /system/etc/init.d initiating /system/xbin/nilfs_cleanerd. Then give the files execution permissions.
Click to expand...
Click to collapse
*.conf file into /system/xbin but not into /etc ?
One more notion: why not to put all these files from nilfs.7z into directories already inside ROM installation zip? (You advise to do it only after installation is complete)

ioy said:
*.conf file into /system/xbin but not into /etc ?
Click to expand...
Click to collapse
Yep, the .conf goes under "system/etc"

ioy said:
*.conf file into /system/xbin but not into /etc ?
One more notion: why not to put all these files from nilfs.7z into directories already inside ROM installation zip? (You advise to do it only after installation is complete)
Click to expand...
Click to collapse
Sorry yes, the default install location for the .conf would be in /etc (or /system/etc; same folder).
Integration of the binaries into the ROM is something I did state would be done eventually, but think that would also require digging through the zip to find where permissions are added and change those, and have had a bit of a hit and miss experience with the cleaner at the moment, want to make sure I have the permissions correct and it's working well before integration.
Kwag, could you make a post listing the benefits of nilfs2, as you know a lot more than I do.

HypoTurtle said:
Kwag, could you make a post listing the benefits of nilfs2, as you know a lot more than I do.
Click to expand...
Click to collapse
Already have
http://forum.xda-developers.com/showpost.php?p=31657498&postcount=716
Here's a copy:
Checksums
Immediate recovery after system crash (no fsck needed at all!)
Continuous (tailored) snapshots of the fs.
Those are benefits of nilfs over ext4. Ext4 has none of those!

no way to creat nilfs on ubuntu cause when i open termenal and command
mkfs -t nilfs2 /dev/sdb2
it give me Error: cannot open device: /dev/sdb2
so any ideas.....

seaman2k said:
no way to creat nilfs on ubuntu cause when i open termenal and command
mkfs -t nilfs2 /dev/sdb2
it give me Error: cannot open device: /dev/sdb2
so any ideas.....
Click to expand...
Click to collapse
sorry, might need sudo ; so sudo mkfs -t nilfs2 /dev/sdb2 failling that try formatting it to ext4 in gparted then try again.

Code:
[SIZE="2"]E/PackageManager( 1471): Couldn't create temp file for downloaded package file.
E/AndroidRuntime( 1471): *** FATAL EXCEPTION IN SYSTEM PROCESS: PackageManager
E/AndroidRuntime( 1471): java.lang.NullPointerException
E/AndroidRuntime( 1471): at com.android.server.PackageManagerService$FileInstallArgs.createCopyFile(PackageManagerService.java:5247)
E/AndroidRuntime( 1471): at com.android.server.PackageManagerService$FileInstallArgs.copyApk(PackageManagerService.java:5255)
E/AndroidRuntime( 1471): at com.android.server.PackageManagerService$InstallParams.handleStartCopy(PackageManagerService.java:5051)
E/AndroidRuntime( 1471): at com.android.server.PackageManagerService$HandlerParams.startCopy(PackageManagerService.java:4902)
E/AndroidRuntime( 1471): at com.android.server.PackageManagerService$PackageHandler.doHandleMessage(PackageManagerService.java:516)
E/AndroidRuntime( 1471): at com.android.server.PackageManagerService$PackageHandler.handleMessage(PackageManagerService.java:461)
E/AndroidRuntime( 1471): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1471): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 1471): at android.os.HandlerThread.run(HandlerThread.java:60)
E/AudioHardwareQSD( 1827): Cannot open /dev/audience_a1026 -1
E/HTC Acoustic( 1827): Update ADIE table ID 0
E/HTC Acoustic( 1827): Update ADIE table ID 2
E/HTC Acoustic( 1827): Update ADIE table ID 5
E/HTC Acoustic( 1827): Update ADIE table ID 7
E/HTC Acoustic( 1827): Update ADIE table ID 8
E/HTC Acoustic( 1827): Update ADIE table ID 10
E/HTC Acoustic( 1827): Update ADIE table ID 51
E/HTC Acoustic( 1827): Update ADIE table ID 53
E/HTC Acoustic( 1827): Fail to open /system/etc/TPA2018.csv -1.
E/SoundPool( 1844): error loading /system/media/audio/ui/Effect_Tick.ogg
E/SoundPool( 1844): error loading /system/media/audio/ui/KeypressStandard.ogg
E/SoundPool( 1844): error loading /system/media/audio/ui/KeypressSpacebar.ogg
E/SoundPool( 1844): error loading /system/media/audio/ui/KeypressDelete.ogg
E/SoundPool( 1844): error loading /system/media/audio/ui/KeypressReturn.ogg
E/GSM ( 1929): Wrong network type: 0
E/GSM ( 1929): Wrong network type: 0
E/GSM ( 1929): Wrong network type: 0
E/GSM ( 1929): Wrong network type: 0
E/GSM ( 1929): Wrong network type: 0
E/GSM ( 1929): Wrong network type: 0
E/GSM ( 1929): Wrong network type: 0
E/GSM ( 1929): Wrong network type: 0
E/NetworkLocationProvider( 1970): releaseCheckLocationLock: wake lock has already been released
E/WifiStateTracker( 1844): DHCP request failed: Timed out waiting for DHCP to finish
E/ConnectivityService( 1844): Attempt to connect to WIFI failed.[/SIZE]
logcat attached for BB7 when trying to install an app from the market, what happens is when downloading a app it downloads fine, but doesn't install, screen just turns off an app isn't installed. Haven't seen this posted elsewhere so may be nilfs2 related, anyone have any ideas.

HypoTurtle said:
logcat attached for BB7 when trying to install an app from the market, what happens is when downloading a app it downloads fine, but doesn't install, screen just turns off an app isn't installed. Haven't seen this posted elsewhere so may be nilfs2 related, anyone have any ideas.
Click to expand...
Click to collapse
Yeah I think I already mentioned it in the NativeSD thread.. it's because securecrt is using a method to share the '/root of your 'ext' partition/app' folder with all NativeSD roms, but that folder doesn't have the right permissions and so the whole system is failing..
This needs proper modifications in the updater script first just like the 'nilfs_cleanerd' stuff..

Xylograph said:
Yeah I think I already mentioned it in the NativeSD thread.. it's because securecrt is using a method to share the '/root of your 'ext' partition/app' folder with all NativeSD roms, but that folder doesn't have the right permissions and so the whole system is failing..
This needs proper modifications in the updater script first just like the 'nilfs_cleanerd' stuff..
Click to expand...
Click to collapse
Thanks just noticed that myself (the app folder in the root of the partition)

HypoTurtle said:
Thanks just noticed that myself (the app folder in the root of the partition)
Click to expand...
Click to collapse
I advise you to use the init script (ramdisk) structure found in my roms and leave the 'sharing data/app' folder aside untill it's properly inplemented

HypoTurtle said:
Code:
[SIZE="2"]E/PackageManager( 1471): Couldn't create temp file for downloaded package file.
E/AndroidRuntime( 1471): *** FATAL EXCEPTION IN SYSTEM PROCESS: PackageManager
E/AndroidRuntime( 1471): java.lang.NullPointerException
E/AndroidRuntime( 1471): at com.android.server.PackageManagerService$FileInstallArgs.createCopyFile(PackageManagerService.java:5247)
E/AndroidRuntime( 1471): at com.android.server.PackageManagerService$FileInstallArgs.copyApk(PackageManagerService.java:5255)
E/AndroidRuntime( 1471): at com.android.server.PackageManagerService$InstallParams.handleStartCopy(PackageManagerService.java:5051)
E/AndroidRuntime( 1471): at com.android.server.PackageManagerService$HandlerParams.startCopy(PackageManagerService.java:4902)
E/AndroidRuntime( 1471): at com.android.server.PackageManagerService$PackageHandler.doHandleMessage(PackageManagerService.java:516)
E/AndroidRuntime( 1471): at com.android.server.PackageManagerService$PackageHandler.handleMessage(PackageManagerService.java:461)
E/AndroidRuntime( 1471): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1471): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 1471): at android.os.HandlerThread.run(HandlerThread.java:60)
E/AudioHardwareQSD( 1827): Cannot open /dev/audience_a1026 -1
E/HTC Acoustic( 1827): Update ADIE table ID 0
E/HTC Acoustic( 1827): Update ADIE table ID 2
E/HTC Acoustic( 1827): Update ADIE table ID 5
E/HTC Acoustic( 1827): Update ADIE table ID 7
E/HTC Acoustic( 1827): Update ADIE table ID 8
E/HTC Acoustic( 1827): Update ADIE table ID 10
E/HTC Acoustic( 1827): Update ADIE table ID 51
E/HTC Acoustic( 1827): Update ADIE table ID 53
E/HTC Acoustic( 1827): Fail to open /system/etc/TPA2018.csv -1.
E/SoundPool( 1844): error loading /system/media/audio/ui/Effect_Tick.ogg
E/SoundPool( 1844): error loading /system/media/audio/ui/KeypressStandard.ogg
E/SoundPool( 1844): error loading /system/media/audio/ui/KeypressSpacebar.ogg
E/SoundPool( 1844): error loading /system/media/audio/ui/KeypressDelete.ogg
E/SoundPool( 1844): error loading /system/media/audio/ui/KeypressReturn.ogg
E/GSM ( 1929): Wrong network type: 0
E/GSM ( 1929): Wrong network type: 0
E/GSM ( 1929): Wrong network type: 0
E/GSM ( 1929): Wrong network type: 0
E/GSM ( 1929): Wrong network type: 0
E/GSM ( 1929): Wrong network type: 0
E/GSM ( 1929): Wrong network type: 0
E/GSM ( 1929): Wrong network type: 0
E/NetworkLocationProvider( 1970): releaseCheckLocationLock: wake lock has already been released
E/WifiStateTracker( 1844): DHCP request failed: Timed out waiting for DHCP to finish
E/ConnectivityService( 1844): Attempt to connect to WIFI failed.[/SIZE]
logcat attached for BB7 when trying to install an app from the market, what happens is when downloading a app it downloads fine, but doesn't install, screen just turns off an app isn't installed. Haven't seen this posted elsewhere so may be nilfs2 related, anyone have any ideas.
Click to expand...
Click to collapse
In the BB7 the same happened on Ext4, it had been reported many times even before NILFS-NativeSD idea arrived.

Xylograph said:
I advise you to use the init script (ramdisk) structure found in my roms and leave the 'sharing data/app' folder aside untill it's properly inplemented
Click to expand...
Click to collapse
Yeah thats the first thing I tried, but still not working correctly.
Other than removing the following from the init is there anything I've overlooked?
Code:
# create app data/app dir
mkdir -p /NativeSD/app
mkdir -p /data/app
mount --bind /NativeSD/app /data/app
if [ ! -d /data/.cache ];then
mkdir -m 0770 /data/.cache
chown 1000:2001 /data/.cache
fi
ln -s /data/.cache /cache
RecoveryMOD seems to run fine (Magldr - android on nand), and installs as expected.

HypoTurtle said:
Yeah thats the first thing I tried, but still not working correctly.
Other than removing the following from the init is there anything I've overlooked?
Code:
# create app data/app dir
mkdir -p /NativeSD/app
mkdir -p /data/app
mount --bind /NativeSD/app /data/app
if [ ! -d /data/.cache ];then
mkdir -m 0770 /data/.cache
chown 1000:2001 /data/.cache
fi
ln -s /data/.cache /cache
RecoveryMOD seems to run fine (Magldr - android on nand), and installs as expected.
Click to expand...
Click to collapse
Hmm.. have you compared the updater-script with for example the CyanMobile one ?
I also made an RecoveryMOD2 that will only mount the fat32, mmcblk0p2 and if available mmcblk0p3...

Xylograph said:
Hmm.. have you compared the updater-script with for example the CyanMobile one ?
I also made an RecoveryMOD2 that will only mount the fat32, mmcblk0p2 and if available mmcblk0p3...
Click to expand...
Click to collapse
Couldn't see anything relevant there, Could it be something in init.htcleo.rc? Have tried commenting everything at on fs, but still not fixed. There's also some mounts for squashfs files in init.rc (for modules and xbin) that seem redundant.

[Q] (Q) Failing backups and restore

I apologize if I've overlooked something simple here, but I am unable to restore my backups. I have swapped to PhilZ Advanced Touch CWM Recovery 6.0.3.7 newly posted in the Android Development Sub Forum.
I believe the error lies in that, for some reason, the external sd card is included in the data partition size calculation (I'm shooting in the dark here but when performing a backup it says needed free space is 21401 MB...I have a 16gb external sd card in the phone). The backups complete with CWM and only take up approx. 1500 MB.
When restoring any of the previously created backups, they all fail at the point of the /data partition. Is there some easy fix for this moving forward (maybe something simple I can change in one of the dumped backup files)? Something I need to reformat?
FWIW I had this problem of 21 GB backup size with TWRP 2.5 as well (yet TWRP fails because it does not continue without the necessary free space).
Any insight would be most appreciated!
Are the errors contained the log typical or do they point out something obvious that needs attention?
Thanks,
Joof
Here are the relevant pieces from the log of the backup being performed....not sure how to grab one from the failed restore and would prefer not to as I have to end up re-flashing the phone
------------------------
Starting recovery on Tue Oct 1 23:30:13 2013
(UTC)
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
CWM Advanced Edition 5
CWM Base version: v6.0.3.7
I:Build version: 5.15.0 - cm_xt907
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot (null) 0
2 /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system (null) 0
3 /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache (null) 0
4 /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata (null) -16384
5 /sdcard datamedia /dev/null (null) 0
6 /external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
7 /logo emmc /dev/block/platform/msm_sdcc.1/by-name/logo (null) 0
8 /modem ext4 /dev/block/platform/msm_sdcc.1/by-name/modem (null) 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 /preload during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:using /data/media/0 for /sdcard
Irocessing arguments.
I:Checking arguments.
Warning: No file_contexts
I:Warning: No file_contexts
I:device_recovery_start()
I:Cannot open /data/philz-touch/philz-touch_5.ini
I:nandroid_compression set to default (fast)
I:Cannot open /data/philz-touch/philz-touch_5.ini
I:nandroid_md5sum set to default (1)
I:Cannot open /data/philz-touch/philz-touch_5.ini
I:show_nandroid_size_progress set to default (1)
Command: "/sbin/recovery"
ro.boot.hardware=qcom
....
....
(REMOVED FOR BREVITY)
I:Checking for extendedcommand & OpenRecoveryScript...
I:Skipping execution of extendedcommand, file not found...
I:Skipping execution of OpenRecoveryScript, file not found...
I:ro.modversion=pa_scorpionmini-3.99-RC2-30SEP2013-084601
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard
I:Checking needed space for backup '/external_sd/clockworkmod/backup/2013-10-01.23.30.25_pa_scorpionmini-3.99-RC2-30SEP2'
E:Failed to find partition size '/boot'
I:/system backup size (stat)=430Mb
I:/cache backup size (stat)=105Mb
I:/data: tot size=4784Mb, free=3600Mb, backup size=21401Mb, used=21709Mb, media=308Mb
I:/external_sd/.android_secure backup size=0Mb
>> Free space: 6414Mb (42%)
>> Needed space: 21937Mb
>> Unknown partitions size (1): - /boot
>> Backing up /boot...
Backing up boot image...
Backup of boot image completed.
Volume not found! Skipping backup of /recovery...
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard
>> Backing up /system...
(APPS LISTED...REMOVED FOR BREVITY)
Backup of system completed.
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard
>> Backing up /data...
(REMOVED FOR BREVITY)
Backup of data completed.
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard
>> Backing up /external_sd/.android_secure...
Backup of .android_secure completed.
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard
>> Backing up /cache...
(REMOVED FOR BREVITY)
Backup of cache completed.
No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum...

Well fastboot flashing stock recovery and doing factory reset/data/cache wipe fixed it. I guess this is not a common issue but thought I'd share my remedy.
Sent from my XT907 using Tapatalk 2

Glad to hear you got your phone working. Just curious, are you now using Philz recovery?
Sent from my XT901 using Tapatalk 4

Thanks!
And Yes. Official philz touch.
I just got this device last week and unlocked the boot loader. I had some issues loading the AOKP 4.3 (boot loops and such even with doing 3x wipes of everything). I eventually had it running smoothly and decided to try the other offerings which is where I discovered this weird backup file size.
But a random post made today in the pacman ROM thread led me to try stock recovery.
Sent from my XT907 using Tapatalk 2

[Q] Have IMEI, SN, and I can backup /EFS. Still unable to mount /EFS (With CWM log)

Greetings,
Title says all, I'm posting the log from CWM.
I tried flashing lots of fw's. And this fix(http://forum.xda-developers.com/showthread.php?t=2507403)
before and after factory reset, removing battery between. Out of clues
Nothing seems to be working for me. Since I first flashed a ROM I could never get network/lockscreen back
Can anyone help me find whats happening with my device?
Starting recovery on Thu Jan 8 23:58:37 1970
framebuffer: fd 4 (1080 x 1920)
min_x_swipe_px=240,min_y_swipe_px=120
CWM-based Recovery v6.0.4.5
Compiled by Xiaolu(20131122)
rm: can't remove '/system/recovery-from-boot.p': No such file or directory
Swipe up/down to change selections.
Swipe to the right for enter.
Swipe to the left for back.
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 /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system 0
3 /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata 0
4 /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache 0
5 /efs ext4 /dev/block/platform/msm_sdcc.1/by-name/efs 0
6 /sdcard datamedia /dev/null 0
7 /external_sd auto /dev/block/mmcblk1 0
8 /storage/usbdisk1 auto /dev/block/sda 0
9 /storage/usbdisk2 auto /dev/block/sdb 0
10 /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 /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /preload during fstab generation!
I:Completed outputting fstab.
I:Connected to Vold..
I:110 0 sdcard /external_sd 0
I:110 0 sda /storage/usbdisk1 0
I:110 0 sdb /storage/usbdisk2 0
I:200 0 Volumes listed.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
...
...
...
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/efs on /efs failed: Invalid argument
W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/efs (File exists)
Error mounting /efs!
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/efs on /efs failed: Invalid argument
W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/efs (File exists)
Error mounting /efs!
I:using /data/media/0 for /sdcard.
Any clues?

Install busybox to get EFS back via CWM.
user @brockyneo had the same issue a few days ago, couldn't restore EFS until he installed busybox
http://forum.xda-developers.com/showthread.php?t=2546724&page=3
It may help with the lockscreen issue.

radicalisto said:
Install busybox to get EFS back via CWM.
user @brockyneo had the same issue a few days ago, couldn't restore EFS until he installed busybox
http://forum.xda-developers.com/showthread.php?t=2546724&page=3
It may help with the lockscreen issue.
Click to expand...
Click to collapse
Thanks a lot, I have asked brock for more detailed information about his solution. I hate messing with EFS, before I restore I want to make one more backup via terminal, I don't know exactly if he did the backup via terminal in his case.

I fixed my phone after one sad week of no networks! I'm so happy!
I used the batch script to restore my EFS via ODIN. and in CWM i was able to mouunt /efs.
Then I did a reset flashed clean ROM and it showed the SIM dialog and lockscreen started to work.
Thanks a lot!

Filesystem problems with /system, keeps remounting ro , filesystem errors common ?

Hey all, so I was making some new bootanimations and was about to try them out when I noticed that even after remounting /system rw and performing an operation, I was getting filesystem errors which caused it to remount ro (standard linux procedure to avoid data corruption.)
Here's the output while using adb shell while TWRP is running:
Code:
<2>[01-05 19:55:34.389] [0][51: bdi_writeback_w]EXT4-fs error (device sde13): ext4_mb_generate_buddy:757: group 27, block bitmap and bg descriptor inconsistent: 1 vs 65364 free clusters
<3>[01-05 19:55:34.389] [0][51: bdi_writeback_w]Aborting journal on device sde13-8.
<2>[01-05 19:55:34.389] [0][51: bdi_writeback_w]EXT4-fs (sde13): Remounting filesystem read-only
<2>[01-05 19:55:34.389] [0][51: bdi_writeback_w]EXT4-fs error (device sde13): ext4_mb_generate_buddy:757: group 28, block bitmap and bg descriptor inconsistent: 1 vs 43594 free clusters
<2>[01-05 19:55:34.389] [0][51: bdi_writeback_w]EXT4-fs error (device sde13): ext4_mb_generate_buddy:757: group 29, block bitmap and bg descriptor inconsistent: 16190 vs 49475 free clusters
<2>[01-05 19:55:34.389] [0][51: bdi_writeback_w]EXT4-fs error (device sde13): ext4_mb_generate_buddy:757: group 30, block bitmap and bg descriptor inconsistent: 32258 vs 20790 free clusters
So I rebooted back in to TWRP (it was semi-hung after the fs error) and ran `e2fsck /dev/block/sde13` and it found and fixed a few errors. My question is, has anyone else experienced this ? Is it fairly common or should I be considering a warranty return ?
I know with traditional HDDs and even SDDs, this can be an indication of a failing drive, or also from a power failure during a write operation on /system (I'm sure I've had a few.)
After my e2fsck, I was able to copy the bootanimation.zip in to place and it works fine (I'll post after I polish a bit). Hopefully I won't see it again, but I did want to reach out in case others were seeing this or had more experience about it's implications with this storage medium. Thanks!

EDIT: nevermind, misread issue