Related
I have done extensive searching in general, Q&A, and development of this forum, as well as Sapphire and have not been able to find an answer to my problem. I have learned that your media files have a delay if you store them on your sd card and that this can be rectified by pushing the media files into your system memory. The /system/media/audio is a read only file and it won't let you push files. This is a simple fix by enabling the read/write of the phone using:
mount -w /system -o remount
From there you can push the files and no lag between calls and hearing the ringtone. Tada. This works perfectly on Cyanogen...The same cannot be said about Hero ROM's.
I have tried several Hero ROM's and I cannot get the read/write to be enabled on the phone when I type in the command. I noticed the first time that the media was located on the /data of the phone. So I changed the ADB command accordingly, and it did not work either. So I thought that it might be because of the location, so I flashed another Hero ROM where I knew the media was located on the /system of the phone. The same thing happened. Where I cannot get it to enable the write capability. I have tried this on several Hero ROM's and cannot figure out why I cannot get this to work.
Any insight is always appreciated, and an answer to this is always more than welcome. Thanks guys.
try
$su
#sh /system/bin/rwsystem
Click to expand...
Click to collapse
if that doesnt work
mount -o remount,rw /dev/mtd/mtdblock3 /system
Click to expand...
Click to collapse
make sure you have enough space on the partitions (type df into console)
I thought since the cm5b4 thread is getting hard to navigate through that i would pull some helpful info out of it and make it in a seperate thread
I TAKE NO CREDIT FOR THE INFO BELOW, jerbarton should get credit for the procedure
As usual I'm not responsible for any problems you may encounter or broken phone, i also cant confirm if this works on any other rom's but cyans and there is no gurantee it will always work but here you go
EDIT:When updating to a new CM rom you WILL encounter a boot loop, simply run the steps below AGAIN during the loop cycle and then reboot the phone and it should work.
ALWAYS NANDROID!!
you will need to have an ext2 partition before this will work, i believe you can make one with the "partition" option in recovery
Code:
adb remount
adb push 04apps2sd /system/etc/init.d/
adb push e2fsck /system/xbin
adb shell
chmod 755 /system/xbin/e2fsck
chmod 755 /system/etc/init.d/04apps2sd
mkdir /system/sd
Downloads:
e2fsck: http://www.mediafire.com/?tzwwjyz2t2r
04apps2sd: http://www.mediafire.com/?mjjntmtmjmj
Attempted this, and I've never once tried doing apps2sd. I dl'ed the files to the root of my SD card after partitioning the SD card to ext2. After this was done, I went to my terminal emulator, but all I get from the commands are "adb: not found"
What am I doing wrong?
heroskyy said:
Attempted this, and I've never once tried doing apps2sd. I dl'ed the files to the root of my SD card after partitioning the SD card to ext2. After this was done, I went to my terminal emulator, but all I get from the commands are "adb: not found"
What am I doing wrong?
Click to expand...
Click to collapse
You have to get the android sdk kit on your computer and type in those commands from tools. Make sure those files are placed in your tools folder so it can find them(adb). Also need to hold down shift and right key to open up command in folder.
nonmindo said:
I thought since the cm5b4 thread is getting hard to navigate through that i would pull some helpful info out of it and make it in a seperate thread
I TAKE NO CREDIT FOR THE INFO BELOW, jerbarton should get credit for the procedure
AS usual I'm not responsible for any problems you may encounter or broken phone, i also cant confirm if this works on any other rom's but cyans and there is no gurantee it will always work but here you go
ALWAYS NANDROID!!
you will need to have an ext2 partition before this will work, i believe you can make one with the "partition" option in recovery
Code:
adb remount
adb push 04apps2sd /system/etc/init.d/
adb push e2fsck /system/xbin
adb shell
chmod 755 /system/xbin/e2fsck
chmod 755 /system/etc/init.d/04apps2sd
mkdir /system/sd
Downloads:
e2fsck: http://www.mediafire.com/?tzwwjyz2t2r
04apps2sd: http://www.mediafire.com/?mjjntmtmjmj
Click to expand...
Click to collapse
Thanks for putting this up but your crediting wrong person. First and foremost Cyanogen(his script pulled from rom) Second, dhanj was the first to post the script on here and the other guy added to it( the one your giving credit too.) Go back and read original post.
kamasi36 said:
You have to get the android sdk kit on your computer and type in those commands from tools. Make sure those files are placed in your tools folder so it can find them(adb). Also need to hold down shift and right key to open up command in folder.
Click to expand...
Click to collapse
awesome! thank you! Ive always been confused about that
heroskyy said:
awesome! thank you! Ive always been confused about that
Click to expand...
Click to collapse
Ha. me too man. You have to learn fast on here. They expect us to know all this stuff coming in the gate. Just holla back if you need some more help. I'm a noob too but managed to figure it out.
http://forum.xda-developers.com/showthread.php?t=532719
This might help you get started. make sure you get everything updated because this is kind of dated.
kamasi36 said:
Thanks for putting this up but your crediting wrong person. First and foremost Cyanogen(his script pulled from rom) Second, dhanj was the first to post the script on here and the other guy added to it( the one your giving credit too.) Go back and read original post.
Click to expand...
Click to collapse
Yeah cyanogen (especially) and dhanj should be credited more than me. I didn't really do anything but add on how I got it working for me.
One thing to mention, if cyanogen doesn't implement this officially in his ROM (and for most people it's probably not needed) you'll have to redo this procedure each time you flash/update so I'd suggest keeping the 2 files saved.
@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
In any case, I was also hesitant on starting a new thread about this because of the apps2sd, need or not to need discussion that's been going on. Anyway, I'm glad you did post this and glad that there are others asides from myself(kamasi, jerbarton, t0pgun & dscottjr81 that I know of!) who chose to get this up and running on their nexus one.
As for who get's credit, I certainly cannot take any credit for this because all I did was share information. The real credit goes to cyanogen and the great devs we have here on xda that made our toys even more enjoyable that it was stock.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3
dnanj said:
@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
In any case, I was also hesitant on starting a new thread about this because of the apps2sd, need or not to need discussion that's been going on. Anyway, I'm glad you did post this and glad that there are others asides from myself(kamasi, jerbarton, t0pgun & dscottjr81 that I know of!) who chose to get this up and running on their nexus one.
As for who get's credit, I certainly cannot take any credit for this because all I did was share information. The real credit goes to cyanogen and the great devs we have here on xda that made our toys even more enjoyable that it was stock.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3
Click to expand...
Click to collapse
Thanks dnanj. Just upgraded to ext. 3. apps2sd b4 now.
You betcha....as always, just sharing information whenever I can.
am i suppose to get a conformation in shell if the commands worked?
Ohal_yeah said:
am i suppose to get a conformation in shell if the commands worked?
Click to expand...
Click to collapse
When the commands complete, you should be brought back to the prompt where the shell awaits the next command.
I apologize for not looking deeper into who deserves credit here, thanks for those of you that do know!! I was simply just trying to make it easier to get the information to people that might want it...
as for the debate of needing a2sd or not, i was out of space right from the get-go because of all the apps i had on my mt3g...so to me i definitely need it out of the 1gb partition i made on my sd card i have .82 free now lol...
completed all steps but everything still saves to internal memory
JustinLoe said:
completed all steps but everything still saves to internal memory
Click to expand...
Click to collapse
a small glitch probably when you run the last command before adb reboot, it fails to create the directory as it exists, probably change the name to solve it, it happened to me once
dnanj said:
@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3
Click to expand...
Click to collapse
hi, what does the code has anything to do with app2sd? anyone cares to shed some lights to a newcomer?
TIA
jakontil said:
hi, what does the code has anything to do with app2sd? anyone cares to shed some lights to a newcomer?
TIA
Click to expand...
Click to collapse
ext3 is essentially a ext2 file system with journaling.
Click Here to read about ext3 and it's benefits over an ext2 fs. As to why ext2 over ext3 for apps2sd, since journaling improves reliability of the fs, that makes it more ideal than ext2.
it works great thanks!
hi dnanj
thanks for the link
sorry but im stuck here
C:\android-sdk-windows\tools>adb remount
remount succeeded
C:\android-sdk-windows\tools>adb push 04apps2sd /system/etc/init.d/
failed to copy '04apps2sd' to '/system/etc/init.d/': Is a directory
C:\android-sdk-windows\tools>
why does cmd show me this error can you help me out please..very much appreciated
I have read the discussions about amoled screens not using battery on pixels which are meant to be black because it simply doesn't light anything up in the case. I was wondering if its possible for someone to make a Google talk app that is black with white text. Since that's my most used app I'd be interested in seeing if it makes any battery savings.
Sent from my Nexus One using XDA App
I could have sworn that it had a black background in the Eclair days... or at least on CM5.x Eclair. I could be mistaken, though.
Its been done, along with gvoice.
http://forum.xda-developers.com/showthread.php?t=821214
Waiting for Gmail.
Consider that you will not be able to update without uninstalling the modded version.
Wow that's brilliant..never even thought about that before
Sent from my Nexus One using XDA App
The app was problematic - not showing Mobile and Android contact status. I've updated it and attached the APK in the linked thread.
Attaching it here too.
adb push TalkMod_Mod.apk /system/app/Talk.apk
Jack_R1 said:
The app was problematic - not showing Mobile and Android contact status. I've updated it and attached the APK in the linked thread.
Attaching it here too.
adb push TalkMod_Mod.apk /system/app/Talk.apk
Click to expand...
Click to collapse
You mean you can't see if other people are on mobile or on android? Thanks for the update!
ksc6000 said:
You mean you can't see if other people are on mobile or on android? Thanks for the update!
Click to expand...
Click to collapse
I mean - before my update you couldn't see any of those. Not mobile and not Android. The watermarks just didn't show up near the contacts. Now you can see both.
Jack_R1 said:
I mean - before my update you couldn't see any of those. Not mobile and not Android. The watermarks just didn't show up near the contacts. Now you can see both.
Click to expand...
Click to collapse
Thanks, I really appreciate it. I'll push it when I get home.
Maybe you can help answer a problem I'm having, I have 2 nexus ones, one for Tmo and one for ATT. The ATT is just a backup in case I move to ATT someday, and it's like my wifi tablet lol.
Anyways, when I originally figured out how to push the talk apk to my TMo nexus one, it worked perfectly. However, when I pushed it to the ATT one, it looked like it worked fine, it showed that the 1032 kb were pushed (I'm just guessing the amount)...and I rebooted the phone...the google talk is still white :S....I did it again, and again it looked like it worked fine, but the google talk is still white! Any idea how to check to see what I'm doing wrong? The command I'm entering is fine..
The talk.apk is in my sdk tools folder..and the command I'm using is
adb push talk.apk /system/app/talk.apk
The command you're entering is wrong. Linux is case sensitive, so is Android. Copy the command I gave above EXACTLY. And you might be pushing the wrong file, since you don't have it named right.
Thanks,
I had just figured it out last night. I needed to capitalize the T in talk....however, now when I do
adb shell
cd /system/app
ls
I see in the files that there is a Talk.apk, and also a talk.apk. How do I remove the "talk.apk"?
adb pull talk.apk /c:/talk.apk ?
Pull doesn't remove, only copies to PC.
adb shell
cd /system/app
rm talk.apk
Once you execute "adb shell", you get to Linux shell. SH, specifically. Work with files and folders like you would in Linux.
Jack_R1 said:
The app was problematic - not showing Mobile and Android contact status. I've updated it and attached the APK in the linked thread.
Attaching it here too.
adb push TalkMod_Mod.apk /system/app/Talk.apk
Click to expand...
Click to collapse
Works fine. Thanks.
Any way to install this via terminal emulator?
I am running Enom's 2.14.1, and I have apps2ext enabled...
I tried to use the command "mount -o rw, remount -t yaffs2 /dev/block/mtdblock3 /system"
to remount via terminal emulator, but it says mounting remount on /dev/block/mtdblock3/system failed: Not a directory.
So I'm trying to figure out how to install these without the computer. I don't have root explorer but I'm not sure how it would work considering I have apps2ext enabled.
Any suggestions?
ksc6000 said:
Any way to install this via terminal emulator?
I am running Enom's 2.14.1, and I have apps2ext enabled...
I tried to use the command "mount -o rw, remount -t yaffs2 /dev/block/mtdblock3 /system"
to remount via terminal emulator, but it says mounting remount on /dev/block/mtdblock3/system failed: Not a directory.
So I'm trying to figure out how to install these without the computer. I don't have root explorer but I'm not sure how it would work considering I have apps2ext enabled.
Any suggestions?
Click to expand...
Click to collapse
Theres a space before "/system".
should work
1)mount as above
2)command: cp /sdcard/Talk_Mod.apk /system/app/Talk.apk
Thanks,
that gives me a new error though:
Code:
can't create '/system/app/Talk.apk': File exists
Got it!!
This command worked in terminal emulator to remount
Code:
mount -o rw,remount /system
Then I was able to do the cp /sdcard/Talk_Mod.apk /system/app/Talk.apk
Have tryd but it force close! :-(
bgx said:
Have tryd but it force close! :-(
Click to expand...
Click to collapse
Make sure you're running compatible version. This is for Froyo, you're running CM7 - not the same Gtalk.
Jack_R1 said:
The app was problematic - not showing Mobile and Android contact status. I've updated it and attached the APK in the linked thread.
Attaching it here too.
adb push TalkMod_Mod.apk /system/app/Talk.apk
Click to expand...
Click to collapse
this is for Froyo, correct? Do you happen to have a Gingerbread version?
No, I didn't make one. Try to look for various dark CM7 themes, you'll probably find it there.
I don't want to dual-boot, even, just have a nice "normal" Nookie Froyo install on eMMC. I've seen several allude to the fact that it worked for them but no reviews of how they did it. I've backed up my 2.1 install with Clockwork so I'm not really worried about that.
TIA.
It's quite simple actually. All you need is basic knowledge of adb.
All disclaimers apply, I'm not responsible for any damage. Just know that mine is running on internal partitions. And the SD does mount too!
Before doing anything, I would recommend applying a dd from your partitions to your pc.
With, for example on mmcblk0p1 (boot) adb: dd if=/dev/block/mmcblk0p1 of=boot.img
You should do that for each partition to be safe (0p1 to 0p8).
All the following commands can be execute one after one, the separations are only there to makes things a bit more clear.
Then,
Boot to a working Nookie (NF) with your uSD fresh from burning, without any google apps, and without any uSD damaged errors.
Empty your internal system and copy uSD system over, by doing:
- adb shell mount -o remount,rw /dev/block/mmcblk1 / (---there is a space after the 1---)
- adb shell
- mkdir tmpfolder
- mount /dev/block/mmcblk0p5 tmpfolder
- cd tmpfolder
- rm -r * (---note that there is space after the r---)
- cd ..
- cp -r system/* tmpfolder (---this will take a few minutes---)
- umount tmpfolder
Click to expand...
Click to collapse
Then, you need to boot push the attached files (bottom of post) except for the 2 vold files to your boot partition: mmcblk0p1. Unzip, copy content, not zip.
You could very well replace uImage with the new Quickie overclocked uImage for froyo (see dev thread).
To push attached files to boot, do:
- mount /dev/block/mmcblk0p1 tmpfolder
- exit
- adb push [folder-containing-4-attached-files-except-vold.fstab] tmpfolder
- adb shell
- umount tmpfolder
Click to expand...
Click to collapse
I would also recommend erasing all your data. But that's up to you, if you want to keep your data on it. In any case, you can revert back with the data.img you created above . So next part you could skip, haven't tried skipping personally:
Non mandatory, but you could do:
- mount /dev/block/mmcblk0p6 tmpfolder
- cd tmpfolder
- rm -r *
- cd ..
- umount tmpfolder
Click to expand...
Click to collapse
Then you need to push vold.fstab and vold.conf (unzip volds, copy content) to system/etc
Copy vold's to system/etc:
- mount /dev/block/mmcblk0p5 tmpfolder
- exit
- adb push [folder-with-vold's] tmpfolder/etc/
- adb shell
- umount tmpfolder
- rm -r tmpfolder
- exit
Click to expand...
Click to collapse
Then shut down, remove uSD, and boot.
Again, you can choose to push the Quickie uImage, I you prefer, but the accelerometer doesn't work with it at the moment. The 950 kernel does sometimes crash on boot, but once booted is quite stable.
I think that's all folks. I could have been a bit vague at some times, but this should work. And if you made your imgs as recommended, you're bullet proof.
To revert back to initial state with img files, you need to copy files to sdcard and then dd:
- adb shell mount -o remount,rw /dev/block/mmcblk1p1 sdcard
- adb push XXX.img sdcard (--could take a few minutes--)
- dd if=XXXX.img of=/dev/block/mmcblk0pX
Click to expand...
Click to collapse
Do that for each partition.
For those who don't feel up to the task, I could make a CWR flashable zip file of all this. The only thing is, CWR dosen't boot on Nookie just yet. So you couldn't restore with a zip after the change.
[Before doing anything, I would recommend applying a dd from your partitions to your pc.
With, for example on mmcblk0p1 (boot) adb: dd if=/dev/block/mmcblk0p1 of=boot.img
You should do that for each partition to be safe (0p1 to 0p8).
[/QUOTE]
I am a little confused here. What are the names of the 7 other partitions? Thanks, Great guide btw!
See here.
Do you see improved speed and touch response running nookie from emmc?
im getting a "No such file or directory" error after "adb push [folder-with-vold's] tmpfolder/etc"
I created the directory but now it looks like i am stuck at the landscape android splash screen on boot...
any ideas? I am attempting to redo the whole process again just incase i missed something.
Sorry, there's a slash after etc.
Make sure you've copied the systen files, with "ls" inside tmpfolder where you copied system. Should be a etc folder there.
Sam
to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.
FastCR said:
to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.
Click to expand...
Click to collapse
Thanks but I don't see how that comment adds anything here.
Looks like the issue is above commands copy the actual system folder (not the contents of the folder) To the root of the partition. ls shows the folder "system" not the contents including etc. They are inside the folder but if the partition is mounted as system then the folder is redundant. Will check copying the contents and see if that helps.
Once I get it working in will post back to let others know
**** in the first block of code replace
Code:
- cp -r system tmpfolder (---this will take a few minutes---)
with
Code:
- cp -r system[B]/*[/B] tmpfolder (---this will take a few minutes---)
many thanks!
FastCR said:
to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.
Click to expand...
Click to collapse
Why would you go out of your way to say that? It's not constructive. As a junior member with three posts and 0 thanks after a year and a half, sharpen your teeth here at XDA before you act like a big shot.
Right thanks. Changed it.
Has it worked for you?
Sent from my HTC Desire using XDA App
samuelhalff said:
You could very well replace uImage with the new Quickie overclocked uImage for froyo (see dev thread).
Click to expand...
Click to collapse
Are you certain on this part? Last I read in that thread, Froyo needs a different minimum kernel.
UPDATE: Nevermind, I missed this updated effort.
Homer
Well, last time I checked, my NC was running at 950 on froyo with setcpu.
Check the forum. There's a nookie version of quickie. Except accelerometer doesn't work..
First, huge thanks to the second poster - great guide! Can we sticky this?
Second, yes I know what dd does, etc, I've been working with Linux for about ten years . I just don't know the ins and outs of embedded devices yet.
samuelhalff said:
Right thanks. Changed it.
Has it worked for you?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
yeah i was up till 4am last night but got it working. first i tried to use my existing nf sd card... bad idea. would boot from emmc to the touch android screen to begin, but could not get past. i assume it was the issue on nookdevs because wifi was not enabled. so i removed the setupwizard.apk but somehow bricked and was unable to boot from emmc. so i took the following steps to get things working properly:
1. reimage boot and system from the stock 1.0.1 images and reset the nook to stock, didnt even touch. at the intro screen i just powered it off.
2. next i took a fresh nf sdcard and run steps from your post(with the correction to copy system contents)
3. from there i had a working nf from sdcard! i did my tweaks (google apps, market fix and button remapping from nookdevs froyo tips)
i might to put together a post with a more verbose set of instructions for a one stop froyo shop but if i do i will be sure to give you credit for your contribution.
thanks again!
Hi,
Second, yes I know what dd does, etc, I've been working with Linux for about ten years . I just don't know the ins and outs of embedded devices yet.
Click to expand...
Click to collapse
Well, that's a nice contrast. I've been working on Linux/Android for about 2 months now
I should have mentioned that the NF uSD Card must be a newly burnt image, without all the nookie tips added to it. Of course, your Google framework will crash if you port it without your data.
By the way, there's a nice trick to get past the numb android interface, simply touch every corner of the screen, starting with top left and going clockwise. You'll then be sent the your home screen, and from there you'll log on to google account again.
I think the best way of doing it would to create a flashable .zip, which I'll make tonight if I find the time and if people are really interested. But don't forget CWR dosen't work on nookie for the time being. The only way back would be through adb.
So, does anyone wish to have a flashable zip of this? Or will it be a waist of time?
Sam
samuelhalff said:
Hi,
Well, that's a nice contrast. I've been working on Linux/Android for about 2 months now
I should have mentioned that the NF uSD Card must be a newly burnt image, without all the nookie tips added to it. Of course, your Google framework will crash if you port it without your data.
By the way, there's a nice trick to get past the numb android interface, simply touch every corner of the screen, starting with top left and going clockwise. You'll then be sent the your home screen, and from there you'll log on to google account again.
I think the best way of doing it would to create a flashable .zip, which I'll make tonight if I find the time and if people are really interested. But don't forget CWR dosen't work on nookie for the time being. The only way back would be through adb.
So, does anyone wish to have a flashable zip of this? Or will it be a waist of time?
Sam
Click to expand...
Click to collapse
I would love a flashable .zip. I think many others would as well.
starkruzr said:
I would love a flashable .zip. I think many others would as well.
Click to expand...
Click to collapse
Can't wait for a flashable zip. Maybe even some cm7 release candidates would make me real happy.
Sent from Nooted NookColor using XDA App
I recently rooted my Nook color with Auto Nooter 2.12.25. It gave me the Google Market but it is the old one and it only displays 10 apps in portrait mode and some of the buttons have problems working. I read in a thread that the newer market fixes that and I downloaded an apk named com.android.vending02.apk but when I try to install it, the app manager doesn't have an install tab. I downloaded a 3rd party install manager and when I try to install it says that 'There is a problem parsing this package'.
I have read that people have installed the updated market but no one gives an explanation how. Does anyone know how do this? Thanks for your help.
Found solution
I found a solution.
Dont just post you found a solution, that helps no one. post what the solution was or atleast a link to the fix.
Good Call
I installed the APK at the top of this thread http://forum.xda-developers.com/showthread.php?t=872621 and then reset my NC and the new Market worked. Apparently, after reading through the thread, this method doesn't work for everyone. There are further instructions that may be of some use.
Now my market isn't working. After trying to install this and switch back both times when I open market it just disappears.
buffnutz1 said:
Now my market isn't working. After trying to install this and switch back both times when I open market it just disappears.
Click to expand...
Click to collapse
I had the same problem on my 1.1.0 NC rooted with Decad3nce's V1.1.0_r2 [01/29/2011] method (there's a huge long thread on that in the Development forum). I was dreading the possibility of having to wipe the machine and start over, but I just re-flashed the zip file, and everything's working fine again. Unfortunately, I'm still stuck with the old Market.
If you're feeling like you can handle cmd-line stuff, try this method out.
First download the attached newmarket.apk
open/connect adb
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
exit
adb pull /system/app/Vending.apk (notice the cap V, also this will get put into your platform-tools folder. Back it up!)
adb push pathtonewmarket.apk /system/app/Vending.apk
adb reboot
Once you've rebooted then go into settings->applications->manage->all
Find the market and clear the cache
Then find google services framework and clear the data then force quit
reboot once more
After that the new market should work just fine.
Thanks Woot! does this work on Froyo 0.6.7 too?
woot1524 said:
If you're feeling like you can handle cmd-line stuff, try this method out.
First download the attached newmarket.apk
open/connect adb
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
exit
adb pull /system/app/Vending.apk (notice the cap V, also this will get put into your platform-tools folder. Back it up!)
adb push pathtonewmarket.apk /system/app/Vending.apk
adb reboot
Once you've rebooted then go into settings->applications->manage->all
Find the market and clear the cache
Then find google services framework and clear the data then force quit
reboot once more
After that the new market should work just fine.
Click to expand...
Click to collapse
necroscopev said:
Thanks Woot! does this work on Froyo 0.6.7 too?
Click to expand...
Click to collapse
I can confim that it does, I used it my self to get the new market installed.
If you're booting off of an SD card and want to install the new market there. All you need to do is change one line.
FROM: mount -o remount,rw /dev/block/mmcblk0p5 /system (eMMC system partition)
TO: mount -o remount,rw /dev/block/mmcblk1p2 /system (SD-card system partition)