Database Develop

chkdsk on Android?

Bad day today. Why? Because this morning I decided to try out one of the Eclair roms before leaving for work. I flashed it, tried it and then looked at the time. After noticing that I had only 15 minutes before having to be at work I decided that it was time to lock up my computer and take off... but first... I need to restore back to a stable rom. So I restarted my phone and using switchrom I recieved an error of some kind. Not a big deal because anytime I flash a new rom I do a switchrom -s, bart backup AND nandroid+ext backup. Then everyday I use a bat script to automatically mount my sdcard and back it up to my pc just in case I need to format my card and restore everything later. Which brings me to the point of this thread. I was able to restore CM-4.2.8.1 but it was booting VERY slowly (about 15 minutes) and I noticed that it still said "Checking for errors" in the status bar. I left my phone on the charger and checked it later and it said that my sdcard was damaged. I have absolutely NO computer access and my phone is running WAAAYYYY to sluggish to use. So I just turned it off and put my sim in my old Tilt phone and used that for the day.
So... throughout the ENTIRE day I was going through Android withdrawls. I needed my G1. It was killing me.
So my question/idea is, is there a way to do a chkdsk on the fat partition of from the recovery menu or from terminal? I did a little searching and came up with something called dosfsck. And I looked in the /system/bin/ directory and saw something called fsck_msdos. Can we use this to repair the errors that the system finds on the sdcard? If the OS can scan and detect errors, then why can't we have an option to fix them? Instead of having to use a computer at home or the office.
Any thoughts? Thanks.

Binary100100 said:
I was no longer the Hero.I needed my hero. I needed to be rescued.Times were changing people changed, things got hard for me .
Any thoughts to rescue my savior ???
Click to expand...
Click to collapse
The thing is that is part of the windows OS, i know cause i use it to check for errors on my HDD or SD cards time-time. Im not sure if linux or distro or whatever its called has that feature avail.
Oh and i had that prob before where it was devastatingly sluggish.

Ace42 said:
The thing is that is part of the windows OS, i know cause i use it to check for errors on my HDD or SD cards time-time. Im not sure if linux or distro or whatever its called has that feature avail.
Oh and i had that prob before where it was devastatingly sluggish.
Click to expand...
Click to collapse
Uhhhh... is that a paraphrased version of what I said in the quote? LOL.
Here... I found this: http://linux.die.net/man/8/fsck.vfat
I don't see why it can't be implimented somehow into a recovery.img to avoid future problems. It'll basically be like e2fsck but for fat.

Binary100100 said:
Uhhhh... is that a paraphrased version of what I said in the quote? LOL.
Here... I found this: http://linux.die.net/man/8/fsck.vfat
I don't see why it can't be implimented somehow into a recovery.img to avoid future problems. It'll basically be like e2fsck but for fat.
Click to expand...
Click to collapse
Oops sorry about that, didnt think anyone would notice.
Maybe you should check that up with Amon_RA?
I usually use my SD reader to check for errors before i flash a rom.

Ace42 said:
Oops sorry about that, didnt think anyone would notice.
Maybe you should check that up with Amon_RA?
I usually use my SD reader to check for errors before i flash a rom.
Click to expand...
Click to collapse
Yeah I guess I'll do just that.
I did find this too:
http://www.netmite.com/android/mydroid/donut/external/dosfstools/doc/README.dosfsck
So it looks like someone had the idea already. I wonder why it's never been implemented.

Binary100100 said:
Yeah I guess I'll do just that.
I did find this too:
http://www.netmite.com/android/mydroid/donut/external/dosfstools/doc/README.dosfsck
So it looks like someone had the idea already. I wonder why it's never been implemented.
Click to expand...
Click to collapse
The fat32 probably does get corrupted, sometimes i get the sd isnt inserted error.

Ace42 said:
The fat32 probably does get corrupted, sometimes i get the sd isnt inserted error.
Click to expand...
Click to collapse
I never get that but whatever is wrong with my sdcard it must be major because my pc is still trying to recover it after an hour later.

Binary100100 said:
I never get that but whatever is wrong with my sdcard it must be major because my pc is still trying to recover it after an hour later.
Click to expand...
Click to collapse
Copy the files to your pc, then erase the partition via console.Then do the error check again. I think its having trouble since you have a lot of files on your sd that must be zip or maybe you have a .img

Ace42 said:
Copy the files to your pc, then erase the partition via console.Then do the error check again. I think its having trouble since you have a lot of files on your sd that must be zip or maybe you have a .img
Click to expand...
Click to collapse
I think it was Vista. I never should have used the error check option in the disk properties menu. I just tried it again using dos (chkdsk f: /R) so it actually tells me what it's doing. The error checking tool in vista is just like the defrag tool. You have absolutely no idea what's going on or how much longer it's going to take. Sucks.

Binary100100 said:
I think it was Vista. I never should have used the error check option in the disk properties menu. I just tried it again using dos (chkdsk f: /R) so it actually tells me what it's doing. The error checking tool in vista is just like the defrag tool. You have absolutely no idea what's going on or how much longer it's going to take. Sucks.
Click to expand...
Click to collapse
I upgraded to 7
But i did like vista because of the HW support and eye-candy. I do wonder what its checking while it does that though.

New to Android or NAND?

I'm no longer keeping up with NAND on the vogue. So if anyone would like to keep me informed and email me or post me on any changes with NAND, ill be happy to add the news on the first post. The lock up issue with NAND has been fixed!
This is simply for any noobs or others who are having issues with Android and NAND.
IMPORTANT!!!
FOR VOGUE USERS ONLY
I am not responsible for any bricked or messed up devices. By continuing you are agreeing to my simple rule.
MY SIMPLE RULE: I owe you nothing.
I will help you through the way though if you bricked or need any sort of help.
How-to Video up NOW!!!
http://www.youtube.com/watch?v=3gTkJkOc7m4
​
First off, What is NAND?
To keep it simple...its your phones internal memory. Up untill recently we (Vogue Users) had to run Android off our SD cards using HARET. But thats another story.
What are the benefits of running from NAND? (based on what I have seen)
-Runs faster
-Longer Battery life
-faster boot up
-can be faster to put together.
-Easier to connect your vogue with android to your pc and sync
-Much more convenient.
So how do I start?
STEP1:
The Build
First you need to find a Build that is usable with NAND. Most Hero builds at this moment are not. Here are some links:
Donut 1.6
http://forum.xda-developers.com/showthread.php?t=591104
Hero
http://forum.xda-developers.com/showthread.php?t=603028
Cupcake 1.5
Method 1 from http://forum.xda-developers.com/showthread.php?t=593786
DO NOT DOWNLOAD ANYTHING JUST YET! I WILL TELL YOU WHEN A GOOD TIME WOULD BE
You may want to consider reading the rest...
STEP2:
Base Files (Most builds will supply these)
For all builds (Except the Link in Cupcake "instructions are givin in the download.) you will need a basic set of base files. The link below contains the 3 basic empty files for all builds and Systems.
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/Androidstuff.rar
IF
You are using Hero make sure you download hero.user.conf too:
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/hero.user.conf
-create a new folder called conf
-and place hero.user.conf in your new folder.
STEP3:
Rootfs
After you have the Base files you will need a rootfs. Depending on your Build, you may need a different type then the one I am going to supply you. Most builds will supply you with one. This one is DZO's rootfs.
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/rootfs.img
STEP4:
Prepare
-You need to clean out your storage on your SD. Make sure you delete everything.
-Create a file called android on your desktop.
-Download the base files, unzip, open folder, and place all 3 in your android folder
-Download the rootfs and place them in your android folder. Make sure you either download DZO's or the one your Build provides.
-Download a System.img. When you download a System most likely it will have a different name such as system-hero-123.img. You need to rename it system. So it should look like system.img . Then place it in your android folder.
-If you are using Hero place your conf folder in your android folder.
-Depending on your Build (mostly Hero) you may also need a Data file. The build you select should supply one. Download it and place it in your Android Folder
STEP5
Placing
Open up your android folder of all your collected files and select all, copy, and paste into your empty SD card.
STEP6
Unlocking
If you have never flashed a ROM before than you don't have HardSPL installed. So unlock your phone with...
http://forum.ppcgeeks.com/showthread.php?t=20370
Make sure you follow the forums directions.
STEP7
Method
Method1: The way I do it.
Download ROMUpdateUtility.rar
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/ROMUpdateUtility.rar
Extract to a newfolder
Download a kernel with your screen size
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
Don't know your screen size...check this out
http://forum.xda-developers.com/showthread.php?t=544906
After you have have gotten the kernel:
rename it to RUU_signed and place it in the ROMUpdateUtility folder you created.
NOW you need to plug your phone into your computer. Establish active sync. And run ROMUpdateUtility.
-Follow the Instructions on the screen.
Method 2 and 3 can be found here:
http://forum.xda-developers.com/showthread.php?t=593786
This also shows my method...but a little less detail. You can also find many other helpful things there.
If you fail OR think your bricked your phone.
You will need to download one of these depending on your carrier...Make sure you download the shipped gps rom. (If you are Verizon skip down)
http://forum.ppcgeeks.com/showthread.php?p=191607
Than you will put your phone in boot mode. Hold the Camera and Power button. While holding both of them...get a pen or something small and hit the little restart button on the bottom of your phone. You may have to hold it for like a second.
-you will see three color bars on your phone
-plug your phone into your computer
-run the backup
After your phone is all back to normal. Make sure you run internet explore on your phone. It will enable you to get data.
For Verizon follow the instructions here.
http://wiki.ppchaven.com/index.php?title=Pocket_PC_WIki:FIX_VERIZON_GPS
That is about it. I'm sure I forgot some stuff and will add on to this. Make sure you donate to the Devs for all their hard work.
DZO
http://forum.xda-developers.com/showthread.php?t=593786
jamezelle
http://forum.xda-developers.com/showthread.php?t=603028
plemen
http://forum.xda-developers.com/showthread.php?t=591104
vilord
http://forum.xda-developers.com/showthread.php?t=523692
They deserve it.

thank you this was very helpful

inphin1ty said:
thank you this was very helpful
Click to expand...
Click to collapse
No problem...

yea here is the md5sum: 9b08971e7f23619b6a9a4db9d52d857a

jamezelle said:
yea here is the md5sum: 9b08971e7f23619b6a9a4db9d52d857a
Click to expand...
Click to collapse
Whats that?

staud8469 said:
What are the benefits of running from NAND? (based on what I have seen)
1 Runs faster
2 Longer Battery life
3 faster boot up
4 can be faster to put together.
5 Easier to connect your vogue with android to your pc and sync
6 Much more convenient.
Click to expand...
Click to collapse
great thread. I've run both from nand and sdcard. i have not messed with ext2 on the sdcard.
I agree with 3 for sure. I would also add that there is a deep gratification in wiping win mo off the sdcard
6 is debatable, depends on which conveniences you want. changing lcd.density, changing resolution are all much faster running from the sdcard - no flashing or messing with build.prop, just edit default.txt and reboot (aside - if you have a non-sdhc card you can flash on the fly from the sdcard, but changing lcd.density still requires pulling and pushing files from the system, which is not as easy as changing the default.txt). also more convenient to back-up or revert to a data.img when running from sdcard. definitely booting straight into android is convenient, as is the new mass storage on boot method, as well as having a re-writable system (which you also have using ext2).
1 and 2, I honestly have not noted a significant difference in battery life. With a fast sdcard, I don't think there is a significant difference in speed either - dzo has said this in one of the non-vogue forums as well. i have not tried any sense builds from the sdcard though, and that's where you would notice the greatest difference in speed if there is any.
4 I agree with in general.
I think running from the nand is a huge advance, and great for everyone to try. but, running from the sdcard is still a decent way to use android. choosing between the two comes down to choosing which conveniences suit your usage style the most.
One last thing - please add vilord to your donate links (his google ion on vogue thread), he has been instrumental in developing the ril and advancing android on the vogue. srwalter also deserves mention for his reverse engineering of the libgps.so to bring gps first to cupcake and now to donut as well. jamezelle, plemen, mssmison, zenulator, enatefox, f00bar (no specific order) have all worked hard porting roms and working on things like compcache, swap, modem, etc, which has all been invaluable (zenulator and mssmison deserve special credit for spearheading the porting business). however the gruntwork of porting to the vogue has been done mainly by dzo who brought us the kernel and initial ril and now nand (he's just frickin amazing, he singlehandedly got the first functioning port to the vogue and others helped from there), then vilord who took the ril and really refined it. I guess suffice to say, there have been a lot of people involved along the way, thanks to all of them.

when i try to run android from both nand and haret i always get an error about not being able to mount sd card. does this mean i need to reformat the card? if so how do i do this?

Barogi44 said:
when i try to run android from both nand and haret i always get an error about not being able to mount sd card. does this mean i need to reformat the card? if so how do i do this?
Click to expand...
Click to collapse
When do you get this error? During linux kernel bootup?

Verizon users.
I just update a fix for Verizon users. Shows you how to get GPS too!

Also...there will be a video up soon. It seems that there are so many people having issues. So I will create a video from start to finish. Will be posted up late tonight/ tomorrow morning.

staud8469 said:
When do you get this error? During linux kernel bootup?
Click to expand...
Click to collapse
Yea.. i think i may need a new sd card. Can android boot from a 4gb card or is 2 the max?

Barogi44 said:
Yea.. i think i may need a new sd card. Can android boot from a 4gb card or is 2 the max?
Click to expand...
Click to collapse
i running with a 8gig PNY sdcard
it could theoretically run off of a 512, but you would be a little cramped on space
i guess android doesnt like some of them

so really it doesn't matter how big the card is? do they all have to be formatted to fat32?

Barogi44 said:
so really it doesn't matter how big the card is? do they all have to be formatted to fat32?
Click to expand...
Click to collapse
short answer, yes.

Hey guys...I will try my best to get that video up today. I am about to start recording it.

Am I correct in assuming that step 4-b is create a FOLDER name android on the desktop?
Can I delete those files from the SD when flashing is done?
THANK YOU for the N00B instruction, works great.

stopthebus said:
Am I correct in assuming that step 4-b is create a FOLDER name android on the desktop?
Can I delete those files from the SD when flashing is done?
THANK YOU for the N00B instruction, works great.
Click to expand...
Click to collapse
Yes that is correct, as for deleting the files...I would assume you could. But im not sure. Maybe they are still needed on boot. Never hurts to try though.

im not getting access to the internet after i flashed, am i suppose to edit anything?
im running the donut flash on my sprint vogue.

gigermunit said:
im not getting access to the internet after i flashed, am i suppose to edit anything?
im running the donut flash on my sprint vogue.
Click to expand...
Click to collapse
Wait...NVM you want data to work right?

If you are using donut...try to restart your phone one time. After it boots back up you should see a 3g symbol appear on the notification bar.
If that does not work...go to your apps and open modem. Click once on disconnect and then once more. Then click connect.
Tell me if that works...

Getting rid of PKG's

I understand that the solution to this question may already exist in the forums, however, I did check high and low for it, and was unable to locate one.
Here goes:
I like (as I'm sure others do) to install apps2sd, something I'm able to do thanks to the actively-rooted and cyanogen-modded N1 that I use.
Unfortunately, the actual *install* files *themselves* from all Market-downloaded apps seem to remain in the phone's internal memory, clogging up preciously limited space. How do I get rid of these install files? I tried using a file manager to go into the mnt/asec directory to get rid of *.pkg's, but these seem to be uninstall-protected (I'm not even sure if I'm making a mistake from the get-go in trying to purge the *.pkg's), so I'm kind of back to the drawing board on this one.
Any help on this would be pretty invaluable folks.
Thanks,
Eli

If you've installed a lot, your dalvik cache will grow pretty big. That's found in /data/dalvik-cache.

Thanks Rusty - but my /data dir is completely empty (unless there are invisible folders; if there are, who you know how I can make them visible?).
Best,
Eli

You need SU access to view /data, make sure what you're using to browse it supports that.

Ahh, thanks Rusty - will do that

Your DATA folder is inaccessible, unless you use Root Explorer or other file explorer with root privileges (ES Explorer, for example - but it doesn't work with all ROMs).
There are no PKGs. There are APKs. And you're wrong in your assumption that they aren't used. This is no PC, this is Android, forget what you used to know, you need to learn again. APKs are the actual applications being ran, without them you can't execute anything, and using old Apps2SD, AKA Apps2EXT, you can move your /data/data to SD (EXT partition) and /data/dalvik-cache to /cache. CM doesn't support Apps2EXT, but it can be easily installed and used, following the guide in DarkTremor's thread. Read Wiki in my sig, it'll point you in the right direction. You can start by reading FAQ, question 9.

seekingandroid said:
I understand that the solution to this question may already exist in the forums, however, I did check high and low for it, and was unable to locate one.
Here goes:
I like (as I'm sure others do) to install apps2sd, something I'm able to do thanks to the actively-rooted and cyanogen-modded N1 that I use.
Unfortunately, the actual *install* files *themselves* from all Market-downloaded apps seem to remain in the phone's internal memory, clogging up preciously limited space. How do I get rid of these install files? I tried using a file manager to go into the mnt/asec directory to get rid of *.pkg's, but these seem to be uninstall-protected (I'm not even sure if I'm making a mistake from the get-go in trying to purge the *.pkg's), so I'm kind of back to the drawing board on this one.
Any help on this would be pretty invaluable folks.
Thanks,
Eli
Click to expand...
Click to collapse
1) The .apk isn't the install file it _is_ the application. The are no "install only" parts to an android app
2) Anything on /mnt/asec is already on your sdcard using froyo-style a2sd
3) .so files in /data/data/xxx/lib and /data/dalvik-cache are the primary causes of full /data partitions

[webtop] webtop2sd discussion (currently version 2.0.1)

Note: Please keep this thread restricted to Atrix-specific and general issues. Threads for other devices are referenced at the top of the main webtop2sd thread.
Discuss webtop2sd here (the other thread will be kept clean for announcements, FAQs, etc.).
Before you report an issue:
Make sure it's not on the Known Issues list first!.
Basic debugging, since these are going to be questions I ask anyways:
If you hit problems with the Android webtop2sd application, you'll need to tell me the error, and give me the last few lines of adb logcat. Run this adb command, which will filter out most of the unimportant lines:
adb logcat ActivityManager:i AndroidRuntime:i webtop2sd:i *:s
Are you actually booting from your SD card? You can find this out by checking the Diagnostics tab in webtop2sd, under "Currently mounted webtops". If mmcblk1p12 isn't listed, you're not booted from your SD card. If this is the case, report what ROM you're running from.
Is the webtop configurator application showing, but not running successfully? If so, plug your device into your dock and run a terminal (either locally or adbWireless + adb shell) and run the following:
su
/usr/bin/sudo -H -u adas bash
export DISPLAY=:0
python /usr/local/bin/webtop-configurator.pyc
I'll need whatever output shows up.

great! thanks for making it so much easier.
haven't actually tested it b/c i sort of figured out how to do that a few days back, but still need to manually install it.
maybe i'll test your app next time i decide to reinstall my ubuntu.
btw, which script are you using to mount /osh? for me only /data/logging.sh works (it's safer anyway).

I suspect that what I'm doing isn't rocket science by any means. But, what I do seem to be pretty good at is packaging semi-complex things up for people into a manageable form with a fairly solid level of reliability. You couldn't imagine the things I'm happy that I managed to accomplish with this app, because they're so... quirky.
Anyways, I've been using /system/bin/mountosh since the beginning. I need to tweak the copy I'm using right now, since my goals have expanded beyond what I initially wrote it for. On the other hand, it'll mean that I can separate out my "personal" Ubuntu versus my "debugging" one, and that should be quite helpful.

These advances with linux customization in webtop have turned me on to Ubuntu in general. I just dumped windows xp on my desktop server and now run ubuntu super OS and studio. This takes a phone to a new level. Thanks OP!

i would love to try this out but i'm on a mac.. can you partition through disk utility?

I would complain that you beat me to it, my initial post here, except it looks like what you created is way more advanced and polished than anything I could do.
I will check it out right now. Oops, i see it is only a shell at the moment. Well I am very eager to try it.
A few questions then:
1. I assume this is similar to your last mod, in that you have just moved the Motorola environment onto the SD card, no chroot or other tricks?
2. Is the dependency problem better? Are we able to replace the motorola packages?
3. Are we still stuck with jaunty or is there a possibility to upgrade to a supported version of ubuntu?

I know this might seem like a useless question (installing regardless), but your previous work was based off the 1.5.7 firmware, would this app be supported/functional on the current 1.8.3 firmware?
Oh, and...
Thank you!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! XD
-djazin

Yes I believe the most important questions here are:
1 - which version will it work for? .83? .57? or just up to .52?
2 - If the Ubuntu version could be upgraded to, say, 11? Probably not, but hey...
Regardless, your work is the only reason why I'm buying myself a lapdock and replacing my netbook, so thank you very much for this hobby of yours =)

Looks great, thanks for the hard work

Sweet!! I just bought a 32 GB card the other day. Happy Fathers day to me.
Looks like no sleep week.

n1ckr0th said:
i would love to try this out but i'm on a mac.. can you partition through disk utility?
Click to expand...
Click to collapse
Possibly; I'm not sure. At least one person I talked to said that it should be possible via command line utilities, but I'm not the best person to ask about this particular issue, not having convenient access to Mac OS X...
krkeegan said:
I would complain that you beat me to it, my initial post here, except it looks like what you created is way more advanced and polished than anything I could do.
I will check it out right now. Oops, i see it is only a shell at the moment. Well I am very eager to try it.
A few questions then:
1. I assume this is similar to your last mod, in that you have just moved the Motorola environment onto the SD card, no chroot or other tricks?
2. Is the dependency problem better? Are we able to replace the motorola packages?
3. Are we still stuck with jaunty or is there a possibility to upgrade to a supported version of ubuntu?
Click to expand...
Click to collapse
Heh. I've actually been planning this for over a month, after some pointers from eval- - I had a rough version running, but I wanted to make something that users would be able to take advantage of easily. Oddly, it's the UI that's been the difficult part - actually having it do stuff is (relatively speaking) the easy part.
1. Yes, this is moving the Motorola environment to the SD card. Nothing special otherwise.
2. Not really - nothing's changed on that front. I'll be tweaking some of the package states on the filesystem to make upgrades less liable to completely blow up, but if we want to keep some of the niceties that Motorola added, I'll need to port those changes forward (which I have no particular problem with doing).
3. We're stuck with Jaunty for now. Unfortunately, it looks like information I had previously in regards to a version upgrade for Ubuntu don't apply to our phone, so I'll likely start working on an upgrade to 10.04 LTS after this stabilizes.
Djazin said:
I know this might seem like a useless question (installing regardless), but your previous work was based off the 1.5.7 firmware, would this app be supported/functional on the current 1.8.3 firmware?
Click to expand...
Click to collapse
Viamonte said:
Yes I believe the most important questions here are:
1 - which version will it work for? .83? .57? or just up to .52?
2 - If the Ubuntu version could be upgraded to, say, 11? Probably not, but hey...
Click to expand...
Click to collapse
This is the fun part. Since this is an Android application and not a script, this part should work with any version. I'm currently running 4.1.57 on my phone (I never did get around to upgrading), but once I verify it works there properly, I'll be upgrading to 4.1.83 and testing there as well. There are no issues that I'm aware of that would prevent this first application from running, and the second application (the Python/Gtk one I have planned) should be able to handle any differences between the various ROMs out there.
And the Ubuntu version upgrade question, I answered just above this.

everything is greyed out when i try to use the app..

Epic Sogarth
The ui looks nice though can't wait to test it on 1.8.3 been on 1.5.7 with v2 awhile now updated to 1.8.3 installed the app played with the setting everything looks sweet cant wait for the go ahead XD wouldnt mind testing anything.
-Djazin

dicksteele said:
Sweet!! I just bought a 32 GB card the other day. Happy Fathers day to me.
Looks like no sleep week.
Click to expand...
Click to collapse
32g class 10 has proven to fail on the atrix
it corrupts. Lets hope you didn't spend the extra money for the class 10

n1ckr0th said:
everything is greyed out when i try to use the app..
Click to expand...
Click to collapse
Greyed out? I know that the "Go!" and "Uninstall" buttons tell you that it's not implemented yet, but nothing should be grayed out?

PAulyhoffman said:
32g class 10 has proven to fail on the atrix
it corrupts. Lets hope you didn't spend the extra money for the class 10
Click to expand...
Click to collapse
That's good to know. Luckily they were out of 10's, and I got a four. Already formatted 16 GB fat32 the rest ext3.

Sogarth said:
Greyed out? I know that the "Go!" and "Uninstall" buttons tell you that it's not implemented yet, but nothing should be grayed out?
Click to expand...
Click to collapse
Now that I really look at it mine is also. So I'm guessing that's due to 1.83, or GladiAtrix. That's what I'm using.
I'll post a screenshot if you need.
I could go to stock 1.57 upgrade to 1.83 but not until tomorrow night

Thanks for the answers, Sogarth. And congratulations on your gift man, because your sum of intelligence and dedication sure is one. I'll be installing this on my Atrix as soon as it has been stabilized (and, well, actually made useful xD)

I am on Gingerblur 4.5 only things greyed out are Partitioning section, both 'Device to partition' and 'Webtop partition size' items if "Partition ext. storage" is not selected. Also under "Locations" 'Delete filesystem file' is grey if 'Source webtop' is set to 'internal storage'.
All of these being grey makes sense if you read what they are doing......

_Dennis_ said:
I am on Gingerblur 4.5 only things greyed out are Partitioning section, both 'Device to partition' and 'Webtop partition size' items if "Partition ext. storage" is not selected. Also under "Locations" 'Delete filesystem file' is grey if 'Source webtop' is set to 'internal storage'.
All of these being grey makes sense if you read what they are doing......
Click to expand...
Click to collapse
Unchecking the Partition ext. storage option "ungreyed" the Locations options and Advanced options. Didn't think about doing that since that was one of the goals of this app.
Since I manually partitioned already I should have thought of that.

7310 bootsamsung.qmg and bootsamsungloop.qmg

I am trying to find the stock 7310 boot animation files: bootsamsung.qmg and bootsamsungloop qmg files from the 7310. Please.
Thanks,

you need to have root... then go to system->media and there they are... enjoy

JU57FL1P said:
you need to have root... then go to system->media and there they are... enjoy
Click to expand...
Click to collapse
Thanks for replying. I knew I should have given more information, darn it! I have a rooted i957 LTE that has a really ugly Telus boot screen, Since I don't plan on using this tab for data with AT&T or Telus, I'd like to just get a Samsung (or a generic android) boot animation. I've found some other boot animations in different forums, but I thought that the 7310 would be my best bet because the resolution should be correct without any tweaking. I've seen people posting links to boot files in the past and was hoping someone could do the same with the 7310. Thanks again for your reply.

http://forum.xda-developers.com/showthread.php?t=1648314
but you have to download the rom file, put it in there and then flash the rom with the modified .zip inside it (DON'T EXTRACT THE ROM ZIP FILE)

JU57FL1P said:
http://forum.xda-developers.com/showthread.php?t=1648314
but you have to download the rom file, put it in there and then flash the rom with the modified .zip inside it (DON'T EXTRACT THE ROM ZIP FILE)
Click to expand...
Click to collapse
Here's the situation. I am using the DannoRom_2xx. His Rom has the two qmg files in question located in system>media. I have tried replacing those files with other qmg animation files and they don't seem to want to be replaced. Do I need to replace the files in the ROM and then re-flash the ROM? Actually, I did accomplish part of what I wanted to do (although I'm not sure how I did it.) I did get rid of the Telus screen so now I just have a black screen while my tab is booting. Obviously this is not an urgent problem, I'm just determined to figure out how to do this. It was much easier using zip files on the Nook Color last year. Thanks for trying to help.

heliosue said:
Here's the situation. I am using the DannoRom_2xx. His Rom has the two qmg files in question located in system>media. I have tried replacing those files with other qmg animation files and they don't seem to want to be replaced.
Click to expand...
Click to collapse
How did you try to replace them?
The /system file-system is mounted read-only. It needs to be re-mounted read-write before you can modify it. And then re-mounted read-only in the interest of safety.

boscorama said:
How did you try to replace them?
The /system file-system is mounted read-only. It needs to be re-mounted read-write before you can modify it. And then re-mounted read-only in the interest of safety.
Click to expand...
Click to collapse
Even after setting system permissions to R/W, this is the message I get when I try to move or replace those QMG files that are located in system.
Thanks,

heliosue said:
Even after setting system permissions to R/W, this is the message I get when I try to move or replace those QMG files that are located in system.
Click to expand...
Click to collapse
Hmmm. There is another explanation (other than not being rooted, which you already seem to be).
Is the /system/media a distinct file-system? Or a symlink?
(I don't believe the i957 is that different, though)
What does the mount or df command say?
And 'ls -ld /system/media' ?
Also, have you tried doing the mv/cp using adb?

boscorama said:
Hmmm. There is another explanation (other than not being rooted, which you already seem to be).
Is the /system/media a distinct file-system? Or a symlink?
(I don't believe the i957 is that different, though)
What does the mount or df command say?
And 'ls -ld /system/media' ?
Also, have you tried doing the mv/cp using adb?
Click to expand...
Click to collapse
Okay, I surrender! I am not afraid to admit that I am apparently in over my head. I just wanted to replace the current QMG files with some others,and it looks like I have ventured into, what is for me, unchartered territory. I have used ADB in the past, but I don't think I know enough to be really comfortable with it. Samsung's proprietary animation files are way beyond my ability to deal with. I'll be following this thread to see if someone out there who is much more knowledgeable than I, comes up with a procedure that I can understand and actually implement.
Thanks to any and all who have tried to help me solve this problem.

heliosue said:
I'll be following this thread to see if someone out there who is much more knowledgeable than I, comes up with a procedure that I can understand and actually implement.
Click to expand...
Click to collapse
Really? Wow. OK.
I will note that this is your thread and this is xda-developers, not Samsung user support.
Sitting back and waiting to have the solution spoon-fed to you while someone is trying to help you is not exactly the way to endear yourself to the community.

boscorama said:
Really? Wow. OK.
I will note that this is your thread and this is xda-developers, not Samsung user support.
Sitting back and waiting to have the solution spoon-fed to you while someone is trying to help you is not exactly the way to endear yourself to the community.
Click to expand...
Click to collapse
Easy for you to say. Sorry if this offends. Please tell me what I should do in this circumstance. Your most recent response is way over my head. I gave as much information that I could come up with. Other than that, what would you have me do. Should I pretend that I know what you are talking about, or should I acknowledge that this thread has moved beyond my ability to understand. I was hoping to find someone with some recognition of the problems I was dealing with. Obviously not something you have experienced for yourself. I tried everything that was suggested until I got to this last post which made absolutely no sense to me. Of course I can google until the cows come home, and I probably will, trying to figure out what all of the references you made actually mean. I really am sorry if I led anyone to believe that I knew and understood more than I do. I come from the earlier XDA threads for the Nook Color which was a very special place for all of us newcomers who were so excited about learning what we could do. It has been all too obvious that those Nook Color forums were the not the norm. I have managed to work my through a few other android products: the touchpad, the nexus s, and the galaxy 7.7. All rooted with help fro XDA. The 8.9 doesn't seem to have the same interest and dedication that some of the other forums have. Sorry to have been a distraction.

heliosue said:
Please tell me what I should do in this circumstance. Your most recent response is way over my head.
Click to expand...
Click to collapse
If you'd simply said ^^^^ this ^^^^ before, I'd have said:
"Download a terminal app from the store and run the commands I mentioned before."
and then I wouldn't have thrown away the update.zip I had prepared for you.

I need help and i'm not giving up... lol
boscorama said:
Really? Wow. OK.
I will note that this is your thread and this is xda-developers, not Samsung user support.
Sitting back and waiting to have the solution spoon-fed to you while someone is trying to help you is not exactly the way to endear yourself to the community.
Click to expand...
Click to collapse
ok so i'm having the same problem as this guy.... except i want my stock bootanimation changed. the animation is labeled bootsamsung.qmg, i have rooted my samsung galaxy s3 and my samsung galaxy tab 2 but both have same file type.... have done lots of research and still have not found out why when i root does not change bootanimation to a zip.... i have root explorer and it shows the same in both devices. Any help would be great. I really appreciate all the help with the rooting i have had just from reading xda threads.

BillyBigRoot said:
ok so i'm having the same problem as this guy.... except i want my stock bootanimation changed. the animation is labeled bootsamsung.qmg, i have rooted my samsung galaxy s3 and my samsung galaxy tab 2 but both have same file type.... have done lots of research and still have not found out why when i root does not change bootanimation to a zip.... i have root explorer and it shows the same in both devices. Any help would be great. I really appreciate all the help with the rooting i have had just from reading xda threads.
Click to expand...
Click to collapse
Hello there!
It seems that you can get new QMG files by following this tutorial:
http://forum.xda-developers.com/showthread.php?t=2189934
It says shutdown but it's actually for both