Related
I love the speed of Cyan's Rom, but I hate the HTC camera. Video is always choppy. I don't think I had this problem with the default camera.
Is it possible to swap the cameras?
bittermormon said:
I love the speed of Cyan's Rom, but I hate the HTC camera. Video is always choppy. I don't think I had this problem with the default camera.
Is it possible to swap the cameras?
Click to expand...
Click to collapse
ADB commands to switch out the .apk's of the camera and camcorder with the "default" camera from another build (most likely JF's because that's all Google)
lukekirstein said:
ADB commands to switch out the .apk's of the camera and camcorder with the "default" camera from another build (most likely JF's because that's all Google)
Click to expand...
Click to collapse
ummm, thanks for the reply, but did you mean to list the ADB commands? have playd a little with this in the past but haven't had any luck, so any help would be appreciated. As for now I think I am going to reformat to ext2 and play with Haykuro's Ion r1 for a day or 2.
if you ALREADY HAVE the camera.apk you want to install...then good. IF NOT, go download JF1.51 and pretty sure it will have the Google version camera.apk...MAKE A NANDROID BACKUP BEFORE YOU BEGIN!! I AM NOT RESPONSIBLE FOR ACCIDENTS! This is a simple procedure, so please pay attention and do this carefully, Its not my fault if your phone gets bricked. That being said, i have done this more than once and never bricked my phone. THAT being said, I CANNOT GUARANTEE YOU THE SAME RESULTS, SO PLEASE! PLEASE! BACKUP YOUR DEVICE AND YOUR DATA BEFORE ATTEMPTING THIS!
First go into terminal on your device and type:
Code:
su
mount -o rw,remount -t yaffs2, /dev/block/mtdblock3 /system
rm /system/app/camera.apk
rm /system/app/HTCAlbum.apk
this removes the HTC versions from your phone. Then just go ahead and push the google version camera.apk. The adb commands are:
Code:
adb push /exact/path/to/your/camera.apk /system/app
remember, DO NOT type "/exact/path/to..." replace this line with the path on your computer where you have the camera.apk, for example,
/Desktop/Android/camera.apk is where mine would be...
then thats it. FYI, the HTC version has a separate gallery, the HTCAlbum.apk...THE GOOGLE VERSION DOES NOT HAVE A SEPARATE .APK FOR THE GALLERY. once you have pushed to google camera.apk you SHOULD have the camera and gallery and all...Good Luck!
-BMFC
bmfc187 said:
MAKE A NANDROID BACKUP BEFORE YOU BEGIN!!
Click to expand...
Click to collapse
Where's the fun in that??
bmfc187 said:
FYI, the HTC version has a separate gallery, the HTCAlbum.apk...THE GOOGLE VERSION DOES NOT HAVE A SEPARATE .APK FOR THE GALLERY.
Click to expand...
Click to collapse
I think that's what threw me off in the first place. Thanks for the help, I think I'll give it a shot after I get sick of Ion.
bittermormon said:
Where's the fun in that??
Click to expand...
Click to collapse
If you mess up sometimes you're screwed
bmfc187 said:
once you have pushed to google camera.apk you SHOULD have the camera and gallery and all...Good Luck!
-BMFC
Click to expand...
Click to collapse
Ok so here's the problem I have had in the past, and am still having. I backed up and remover the HTC CAmera and HTCAlbum, but even after I push Camera.apk from JF's ROM, it doesn't show up. No Camera and no Gallery.
Having the same problems. I'd also like to restore the stock camera application, but after replacing the apk and so files from the JF1.51 build (and rebooting), neither Camera nor Gallery appears in the app drawer.
Any thoughts?
rogers dream
hi!
does anyone know if this procedure will work fine on a Rogers Dream? Should replacing the apk files work okay?
Thanks!
silvrhat
silvrhat7 said:
hi!
does anyone know if this procedure will work fine on a Rogers Dream? Should replacing the apk files work okay?
Thanks!
silvrhat
Click to expand...
Click to collapse
Nandroid Backup, do it and if it fails just restore backup. There's no reason it shouldn't.
I'm running Cyan 4.0.2 and I'm trying to push the camera.apk from the rooted T-Mobile builds and when I push the files and try to install the apk it says it can't be installed on this phone. Do I need to push the .odex files also? Another thing, what are the commands for console to delete the data/data files for the htc stuff?
Anyone know why I can't push the stock camera to cyan 4.0.2?
How are you going about it? Are you using console or are you trying to use the package installer?
Copy the old camera file from an old rom. I found one with the JF1.5 build.
mount /dev/block/mtdblock5 /data
mount /dev/block/mmcblk0p1 /sdcard
rm -r /data/app_s/HTCCamera.apk
rm -r /data/app_s/HTCCamera.odex
mv /sdcard/Camera.apk /data/app_s
This will delete the HTC camera and put the old one back. The ODEX file should be created once the .apk file installs. Hope this helps!
it says HTCCamera.apk couldn't be found
What rom are you using?
EDIT: Try this -- Using Cyan4.0.1 (I assumed that you were using JacxHeroski1.5r2..my bad!)
[cpde]mount /dev/block/mtdblock3 /system
mount /dev/block/mmcblk0p1 /sdcard
rm -r /system/app/Camera.apk
rm -r /system/app/Camera.odex
mv /sdcard/Camera.apk /system/app[/code]
I'm using 4.0.2 (pretty much the same as 4.0.1) but shouldn't I have to remove the gallery.apk also? What about the folders in /data/data? Should I remove those too?
I'm looking at the file structure and can't find there is a /data/data. As far as the gallery you shouldn't need to (didn't realize that it was updated.) But if you'd like to push that it would be:
Code:
mount /dev/block/mtdblock5 /data
mount /dev/block/mmcblk0p1 /sdcard
rm -r /system/app/HTCCamera.apk
rm -r /system/app/HTCCamera.odex (may or not be there)
mv /sdcard/Camera.apk /system/app
I've been looking and cannot find anything regarding a Gallery/Album.apk. But it should be able to use the Gallery that's already installed. Let me know how it goes.
ThR1LL said:
I'm running Cyan 4.0.2 and I'm trying to push the camera.apk from the rooted T-Mobile builds and when I push the files and try to install the apk it says it can't be installed on this phone. Do I need to push the .odex files also? Another thing, what are the commands for console to delete the data/data files for the htc stuff?
Click to expand...
Click to collapse
They're folders i believe.
Try "rmdir foldername"
bmfc187 said:
if you ALREADY HAVE the camera.apk you want to install...then good. IF NOT, go download JF1.51 and pretty sure it will have the Google version camera.apk...MAKE A NANDROID BACKUP BEFORE YOU BEGIN!! I AM NOT RESPONSIBLE FOR ACCIDENTS! This is a simple procedure, so please pay attention and do this carefully, Its not my fault if your phone gets bricked. That being said, i have done this more than once and never bricked my phone. THAT being said, I CANNOT GUARANTEE YOU THE SAME RESULTS, SO PLEASE! PLEASE! BACKUP YOUR DEVICE AND YOUR DATA BEFORE ATTEMPTING THIS!
First go into terminal on your device and type:
Code:
su
mount -o rw,remount -t yaffs2, /dev/block/mtdblock3 /system
rm -r /system/app/camera.apk
rm -r /system/app/HTCAlbum.apk
this removes the HTC versions from your phone. Then just go ahead and push the google version camera.apk. The adb commands are:
Code:
adb push /exact/path/to/your/camera.apk /system/app
remember, DO NOT type "/exact/path/to..." replace this line with the path on your computer where you have the camera.apk, for example,
/Desktop/Android/camera.apk is where mine would be...
then thats it. FYI, the HTC version has a separate gallery, the HTCAlbum.apk...THE GOOGLE VERSION DOES NOT HAVE A SEPARATE .APK FOR THE GALLERY. once you have pushed to google camera.apk you SHOULD have the camera and gallery and all...Good Luck!
-BMFC
Click to expand...
Click to collapse
This is what I tried to do at first but it kinda failed
nolimit78 said:
I'm looking at the file structure and can't find there is a /data/data. As far as the gallery you shouldn't need to (didn't realize that it was updated.)
I've been looking and cannot find anything regarding a Gallery/Album.apk. But it should be able to use the Gallery that's already installed. Let me know how it goes.
Click to expand...
Click to collapse
i think i figured out the data command its like
Code:
rm -r /data/data/com.android.camera
rm -r /data/data/com.htc.album
or something like that
I tried searching for this type of install and couldn't find it. After re-flashing cyanogen 5.0.7 stable, I lost my 3d gallery again. I'm at work right now and don't have access to ADB so I had to figure out how to install this on-the-go, without having double galleries. These instructions can be used in terminal emulator without a system reboot. Make sure to download the attached gallery.apk and place it on the root of your sd card.
Code:
1. su (allows root permission)
2. mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system (make the system folder writeable)
3. rm /system/app/Gallery.apk (removes system Gallery)
4. cat /sdcard/Gallery.apk > /system/app/Gallery.apk (copies 3D Gallery to system)
5. enjoy
Help!!!
Permisson denied (are you root?)
yes i am... why doesn't it work?
s.aldrete said:
Permisson denied (are you root?)
yes i am... why doesn't it work?
Click to expand...
Click to collapse
before entering the above commands, try first entering "su", then when you see the # symbol enter in the above command.
so it may look like this, not sure if will work but you can try it:
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# rm /system/app/Gallery.apk
# cat /sdcard/Gallery.apk > /system/app/Gallery.apk
NguyenHuu said:
before entering the above commands, try first entering "su", then when you see the # symbol enter in the above command.
so it may look like this, not sure if will work but you can try it:
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# rm /system/app/Gallery.apk
# cat /sdcard/Gallery.apk > /system/app/Gallery.apk
Click to expand...
Click to collapse
Thanks for helping. I just added that step in the original post. I forgot all about it...
Can we use something like linda to install this and keep both galleries?
Yes you can have both galleries if you install using Astro or Linda but you'll get 2 identical galleries and thus arousing identification problems.
pziv2 said:
Yes you can have both galleries if you install using Astro or Linda but you'll get 2 identical galleries and thus arousing identification problems.
Click to expand...
Click to collapse
What do you mean by identification problems?
thank you man finally a simple way to push apps without using adb interface (that **** is hard when you have no idea what to do)
FatBoyExtraordinaire said:
What do you mean by identification problems?
Click to expand...
Click to collapse
on your device it will show two "Gallery" icons/apps. You wont be able to tell which is which because the 3D one wasnt modded and renamed. So you dont have for example seperate "Gallery" and "3D Gallery" labels, you just have two "Gallery" icons. hope that makes sense. if you look around the forums, you can rip out the modded 3D gallery from one of the roms so it can run side by side with the stock gallery and be properly labeled. maybe rip it out of one of cyanogen's old roms when he had them both before he removed the 3d one.
NguyenHuu said:
on your device it will show two "Gallery" icons/apps. You wont be able to tell which is which because the 3D one wasnt modded and renamed. So you dont have for example seperate "Gallery" and "3D Gallery" labels, you just have two "Gallery" icons. hope that makes sense. if you look around the forums, you can rip out the modded 3D gallery from one of the roms so it can run side by side with the stock gallery and be properly labeled. maybe rip it out of one of cyanogen's old roms when he had them both before he removed the 3d one.
Click to expand...
Click to collapse
I understand what you mean now, thanks for the explanation. Quick question though since I'm kind of novice at certain things, when you say rip out the modded one, is it as simple as opening up the zip, finding the app, taking it out, and then using Linda or such to install it beside the original? And do you know which test version it was when Cyan stopped using the 3d gallery? Thanks in advance.
Edit: I took the apk from Superbad, but it still had the same icon, do you know a specific rom that has a modded icon?
Edit #2: Nevermind, I was able to find 2 different icon-ed versions. Now just a matter of deciding which one I like most.
FatBoyExtraordinaire said:
Edit #2: Nevermind, I was able to find 2 different icon-ed versions. Now just a matter of deciding which one I like most.
Click to expand...
Click to collapse
Dude, can you possibly post the rom/s you took the iconed version/s from, or post the apk's on here as im interested in this myself.
Thanks
Trauma
yay! Thanks a lot! Works marvelously. Now if only somebody were to be able to speed it up, all my dreams would be fulfilled.
traumatism said:
Dude, can you possibly post the rom/s you took the iconed version/s from, or post the apk's on here as im interested in this myself.
Thanks
Trauma
Click to expand...
Click to collapse
No problem, I got it from right here: http://forum.cyanogenmod.com/index.php?/topic/145-gallery-3d-working-version/page__p__1398#entry1398
Just grab the gallery3d zip, take the apk out of it, and just use linda or astro to install. That's what I did.
FatBoyExtraordinaire said:
No problem, I got it from right here: http://forum.cyanogenmod.com/index.php?/topic/145-gallery-3d-working-version/page__p__1398#entry1398
Just grab the gallery3d zip, take the apk out of it, and just use linda or astro to install. That's what I did.
Click to expand...
Click to collapse
nice one dude thanks for that.
makes things easier if lots of images are in a folder
traumatism said:
nice one dude thanks for that.
makes things easier if lots of images are in a folder
Click to expand...
Click to collapse
Not a problem, glad I could help. I actually find the 3d gallery to be faster than the legacy one for me. I have 1200 images on my phone ( I pretty much site ripped G1-Walls and put it on my SD ) and after the initial boot when it creates its thumbs and other cache files, it flies for me. Plus it looks so damn good!
NP
...glad I could contribute to the android movement. F*** iPhone!
SG_Shadow said:
...glad I could contribute to the android movement. F*** iPhone!
Click to expand...
Click to collapse
Hell yeah!!
For those of you having trouble seeing protected apps, I modified our fingerprint in the build.prop. What this does is spoofs the market into thinking its seeing a Droid 2 (with Froyo) It worked for me, let me know if it does for you.
1. Put build.prop into your AndroidSDK\TOOLS folder
2. Connect via USB.
3. CD (Navigate) in CMD to your tools folder
Mount your /system (adb remount) works for me
Copy and paste this
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
To test if you need this before you push the build.prop fix, search the market for Us Bank. If only 2 or 3 show up, you are not getting the full market. After this fix, you should see 10 items listed when you search for Us Bank.
Hope this helps.
2.2 Market Fix Build.Prop -- WITH STAGEFRIGHT=TRUE
This can also be done via Root Explorer.
Edit: Here is a "clean" build.prop for those of you who do not want the stagefright fix (which breaks video playback) Sorry, I was not aware it did that. Thank you.
Non Stagefright Build.prop -- WITH STAGEFRIGHT=FALSE
For everyone flipping out about Birdmans tweet and you want the stock build.prop, here ya go
Stock Build.prop -- WITH NOTHING! STOCK!
You only need the stock one if you ever plan on doing a factory reset. But, you also cant do a factory reset if you have removed or renamed apps so I feel that should be mentioned. If you've done any modding and you are planning on upgrading, your best bet is to always use the SBF anyway. I dont think birdman realizes the panic he sets in with one little tweet. Factory resets suck anyway. But then again... "you decide..."
Thanks to Jcase for giving me the original idea way back when. I just basically applied his Eris Market Fix to work with our phones.
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Found a fix
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Zaphod-Beeblebrox said:
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Click to expand...
Click to collapse
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
elkniwcire said:
i must say i take no responsibility if this causes problems but this worked for me. Do a search in the market for "eris market fix." it was designed for the eris but works just fine on my droid x. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but i assume most everyone on froyo already is rooted.
Click to expand...
Click to collapse
yes this worked for me aswell thank you
Yes this method definitely works. I have market working now and can search for protected apps etc.
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.
I just used the root explorer meathod and now it wont boot.
I downloaded the file.
renamed my build.prob to build.prob/bak
placed the new build.prob in the system folder
rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back
Edit Delete Post: Im just retarted haha .prop not .prob :/
Could you plz give us some details on doing this with root explorer. Thanks
Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.
LexusBrian400 said:
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
Click to expand...
Click to collapse
LexusBrian400 said:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
Click to expand...
Click to collapse
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.
While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.
Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?
As for the Eris file, I did download that and all seems to be OK right now.
Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?
Yes, it requires an edit to a file that you can only be edited when rooted
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
This works for me...thanks!
OP has been updated with original build.prop
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
will2live said:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
Click to expand...
Click to collapse
Just use the non-stagefright one.
Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop
Use the =false version for better stability.
Thanks for the reply.
Hi guys.
I know that the z4mod can successfully patch a Tab kernel, without any problems (I did it myself, flashed it, and ran it just fine for a few days).
But when I tried to run one of the zip files to switch the file system, everything went nuts and I had to reflash my Tab from scratch.
So I did a little investigating, and as far as I can tell, all that needs to be done to make the whole thing successful is to modify the script in the zip file to correct the mount point names (as they are different from the SGS).
So if anyone around here knows anything about this sort of business, please take a look at it and let me/us all know, cuz it would be GREAT to get z4mod working on the Tab.
Here's the web site if anyone's interested;
http://www.sgscompilebox.dreamhosters.com/
Hi, did you tell ryanZA what results you got? I'm sure he'll be interested to help.
However, thank you for trying, I was about to do the same.
Noob question. What's the benefit of running ext2/3 for the internal partitions versus rfs?
knightnz said:
Noob question. What's the benefit of running ext2/3 for the internal partitions versus rfs?
Click to expand...
Click to collapse
RFS is Samsung's partition format (FAT + journal) that is supposed to be better for flash devices. Apparently it is not so good, and very laggy. Therefore people are switching partitions to ext2/3 or moving and linking stuff to SD card with ext2/3 or jffs2 partition.
jeebspawnshop said:
So I did a little investigating, and as far as I can tell, all that needs to be done to make the whole thing successful is to modify the script in the zip file to correct the mount point names (as they are different from the SGS).
Click to expand...
Click to collapse
Could you explain how you came to that conclusion ?
I was not able to locate my mount points to compare with what you did observe, but i guess we should start with that, then ask ryanZA his thought about what you've found.
Fyi: http://forum.xda-developers.com/showthread.php?p=9629477#post9629477
doloop said:
Could you explain how you came to that conclusion ?
I was not able to locate my mount points to compare with what you did observe, but i guess we should start with that, then ask ryanZA his thought about what you've found.
Click to expand...
Click to collapse
It has been tested by many Galaxy S users. Go to their forum and you will know
evermick said:
It has been tested by many Galaxy S users. Go to their forum and you will know
Click to expand...
Click to collapse
I'm really newb on linux, but i've read a little since last post.
What if we:
1 - dump mount list from a working SGT (terminal or adb shell -> mount ?)
2 - apply Z4mod then SGT won't boot (i assume it creates /etc/.fstab)
3 - edit /etc/fstab to match the dump in step 1
But, how do we read/write /etc/fstab once the sgt is locked ? using some kind of update.zip, or is there some shell service we could connect to, even if some mounts aren't in the right place ?
Unfortunately, everything I could contribute to this idea was in my first post. I know absolutely nothing about Android development, sadly...
But after reading what Deodexed said about volumes not mounting properly during recovery (he's the guy trying to get CWM to work for our Tabs) it seems that maybe that's the reason that z4mod may not work... If the volumes aren't mounted correctly, it can't convert the filesystems.
Maybe what doloop said might work? I hope so. An SGT running on ext2 would rock the socks off anything else out there. God I want it
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