New Market (2.2.11) on Nookie Froyo 0.6.6
Update 2/7/2011: Updated for Nooke Froyo 0.6.6. Please READ THE NOTES.
There are 2 methods: Pushing to existing system (just Market) and pushing to new system (all gapps, working Market & Youtube especially)
Notes:
You should exercise caution and make sure you match the case exactly as I have posted. For example, if you push vending.apk instead of Vending.apk, you'll still see the old one, etc. You may also be ignoring a failure message when you copy/paste a command. Report any failure messages.
There are now two sections: Updating and install of Market, and Fresh NookieFroyo/Fresh Market.
Method 1: You have an existing, older market, and you use SD Nookie Froyo. I will note that I started from a format of my SD card, and a fresh image. Report if you used an upgraded NF.
Steps to installing:
1. Download Vending_2_2_11.zip from below
2. Extract Vending_2_2_11.apk to somewhere on your computer. Note the location (eg C:\users\name\blabla\Vending_2_2_11.apk) as yours will be different.
3. Open up a command/termal
4. Use ADB as usual, and run the following commands:
Code:
adb shell
# mount –o remount,rw /dev/block/mmcblk1p2 /system
(should get a confirmation, it will say exactly what you entered)
# exit
adb push C:\users\name\blabla\Vending_2_2_11.apk /system/app/Vending.apk
5. Now, open Settings --> Applications --> Manage Applications --> All --> Market
6. Clear *cache*, and then Force stop
7. Press back
8. Select Google Services Framework
9. Clear *data*, and then Force Stop
10. Reboot
11. Open market
12. Insert credentials & accept agreement (if needed)
13. *Confirm new market. If you don't have it, stop here.
14. Download something
15. ??? Profit!
Method 2: You just installed Nookie Froyo, you use the SD card version, and you have no gapps.
***EXPERIMENTAL. Gnomes ahead!***
What I have done here is I have taken the nookie devs gapps zip, and changed out the market & youtube apks for known working apks.
1. Download nookie-froyo-gapps-20110207 from here:
(mirror 1 (likely dead) http://rapidshare.com/files/446788041/nookie-froyo-gapps-20110207.zip )
(mirror 2 http://rapidshare.com/files/446835767/nookie-froyo-gapps-20110207.zip )
(mirror 3 http://www.multiupload.com/RFP7W72EVS )
(mirror 4 http://www.multiupload.com/72F253U21B)
2. Unzip. Note the location (C:\Users\name\blabla\nookie-froyo-gapps-20110207)
3. Open up a command/terminal
Code:
adb shell
#mount -o remount,rw /dev/block/mmcblk1p2 /system
(should get a confirmation, it will say exactly what you entered)
# exit
adb push C:\users\name\PathToUnzippedGoogleApps\system system/
(should see each file push individually, followed by ## pushed successfully)
adb reboot
4. Open market
5. Enter credentials, accept eula
6. Download something, report success/failure of method 2.
7. ??? Profit? Thank me?
If it "freezes" at a loading screen, you may need to reboot.
Credit to the folks at XDA who have done this before on other devices. I just tried it and it worked. Also credit to http://aliwaqas.info/download-and-install-new-android-market-version-2-2-11-guide/ for the vending 2.2.11 apk
General Questions
How to get ADB or Nook Color ADB Drivers
http://nookdevs.com/NookColor_USB_ADB
I installed ADB & Drivers, but it isn't working!!!
Make sure that "USB Debugging" is enabled under Settings > Applications > Development > USB Debugging (check)
I can't see "x" app, or all apps
You need to change your build.prop
http://nookdevs.com/NookColor:_Nookie_Froyo_Tips#Access_Protected_market_apps
Neither method worked! Can't download apps. (after trying a reboot)
Please answer the following:
What version of Nookie Froyo (v.#x.#y.#z)
What type of Nooke Froyo (SD card, eMMC)
Which method (one or two)
Post a log of the commands you typed, and the output. Screenshots or copy/paste work best.
I tried it using rootEx since my ADB wasn't installed on a different PC. It did not work once adding to system/app or installing with r/w.
Worked Using ADB
I tried it with ADB, and it worked. Now Need for Speed Shift shows up. I tried everything before, but could not get it to show.
mattphoner said:
I tried it using rootEx since my ADB wasn't installed on a different PC. It did not work once adding to system/app or installing with r/w.
Click to expand...
Click to collapse
So double checking here:
/system was mounted R/W
you copied it in as Vending.apk (NOT Vending_2_2_11.apk)
you rebooted
And you still have the old market (with the gray bar)?
Tried again over ADB, that worked!! Not sure if RootEx is the way to go or not.
Anyone know if this will work on regular (nootered) 2.1?
Installed via Root Explorer, and it worked for me. Here's what I did:
Renamed it to: Vending.apk
Mounted System as R/W
Copied Vending.apk to: /System/app/
Rebooted NC then installed Vending.apk from /System/app/
Tested and working.
I tried installing it before rebooting and it just said that it didn't install.
JESTERDEV: on Froyo or 2.1?
sent from my nook color using XDA App
JesterDev said:
Installed via Root Explorer, and it worked for me. Here's what I did:
Renamed it to: Vending.apk
Mounted System as R/W
Copied Vending.apk to: /System/app/
Rebooted NC then installed Vending.apk from /System/app/
Tested and working.
I tried installing it before rebooting and it just said that it didn't install.
Click to expand...
Click to collapse
Maybe this is where I went wrong. I tried installing it BEFORE rebooting, not after.
I am unable to install from either method, RootExplorer or ADB.
With ADB everything went fine, but after reboot I had no Market installed. I checked the system directory, and the apk file was there, but trying to do anything with it resulted in "Unable to Parse Package" errors.
I tried manually with RootExplorer as well, and received the same errors.
EDIT: I even loaded my backup from RomManager to see if that would allow me to try again, but I am still receiving the same errors. Once again the ADB push method works fine to get the file in as Vending.apk in RW mode to system, but then upon reboot there is no market installed anymore.
The apk file is in the system/app directory, but it's not installed for some reason. Any attempt to do so results in the parse errors.
Not working on 2.1.
I haven't been willing to root my nook because all of my school books are on there. Just been using Nookie on SD. I'll update the OP later with some updated directions based on additional feedback tonight. Plus, I need to write a "from stock" tutorial that would be nice to have on the wiki.
Especially curious to know about it working on 2.1. Keep the feedback on that coming please
cybertimber2007 said:
I haven't been willing to root my nook because all of my school books are on there. Just been using Nookie on SD. I'll update the OP later with some updated directions based on additional feedback tonight. Plus, I need to write a "from stock" tutorial that would be nice to have on the wiki.
Especially curious to know about it working on 2.1. Keep the feedback on that coming please
Click to expand...
Click to collapse
You can keep your school books when you root the device. Just sayin'
Sent from my Nooted friend...
Tried to download something from the Market this morning, and it will not let me. I don't remember the exact error, but I will post when I get home. It worked just fine yesterday.
@hetzbh, Froyo.
JesterDev said:
Tried to download something from the Market this morning, and it will not let me. I don't remember the exact error, but I will post when I get home. It worked just fine yesterday.
@hetzbh, Froyo.
Click to expand...
Click to collapse
Not having a problem here. Anyone else?
Obviously there is something I'm doing wrong... I tried installing the new market with ADB and nothing happened...
What options do I have to install this correctly?
I didn't get any errors in ADB while installing
hetzbh said:
JESTERDEV: on Froyo or 2.1?
sent from my nook color using XDA App
Click to expand...
Click to collapse
no the it doesnt work on 2.1... but the 2.2.7 market works on the 2.1 system
djkns said:
no the it doesnt work on 2.1... but the 2.2.7 market works on the 2.1 system
Click to expand...
Click to collapse
Heh, funny. 'Cause originally I was going to post 2.2.7, but the IRC chat informed me that 2.2.11 was available. Did you use the same directions, but with the 2.2.7 vending instead of 2.2.11? I wouldn't mind posting that up there for 2.1 users.
bassrebel said:
Obviously there is something I'm doing wrong... I tried installing the new market with ADB and nothing happened...
What options do I have to install this correctly?
I didn't get any errors in ADB while installing
Click to expand...
Click to collapse
What exactly did you do, what happened (I guess you still have a gray top-bar market), did you reboot, and are you on Nookie Froyo?
Note that unlike most apks, you don't "install" (adb install <file>). You just push the file (adb push /system/app/Vending.apk). Also, there is case sensitivity. vending.apk and Vending.apk are two different files in *nix.
cybertimber2007 said:
What exactly did you do, what happened (I guess you still have a gray top-bar market), did you reboot, and are you on Nookie Froyo?
Note that unlike most apks, you don't "install" (adb install <file>). You just push the file (adb push /system/app/Vending.apk). Also, there is case sensitivity. vending.apk and Vending.apk are two different files in *nix.
Click to expand...
Click to collapse
Well... i booted froyo... then i installed the adb on my computer, opened superuser and followed the instructions, i didnt see an error msg, but when i try to check i dont see qmny market in my apps
Related
I didn't see a thread for this anywhere and it's not included in the rooting documentation so i figured I'd make one.
This will allow you to install apk files directly from the device, no need to adb them over. Just get the apk from the web or whatever source you want and install. Of course this is all assuming you have completed the current root process and have adb access already.
Thanks to godsfilth for finding these directions for the origninal nook.
1. Open a command prompt and navigate to your sdk tools folder
2. Run the following commands
Code:
C:\android-sdk-windows\tools>adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
C:\android-sdk-windows\tools>sqlite3 settings.db
sqlite> update secure set value=1 where name='install_non_market_apps';
sqlite> .q
C:\android-sdk-windows\tools>adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
3. Reboot
4. Install apps from NC without ADB.
You might have to restart your homescreen for the apps to show up, but i've had sucess with every app i've tried that is known working on the NC.
This was done on a Windows 7 x64 machine, although i'm sure it's the same or similiar for Linux and MUC OSx.
Also, sqlite3.exe was already in my sdk tools folder, if it's not for you then you can download from here.
Yep, and you can ADB install a file manager app, then just use the file manager to install anything else, from the SD card.
Bimboy said:
Yep, and you can ADB install a file manager app, then just use the file manager to install anything else, from the SD card.
Click to expand...
Click to collapse
So...the nook doesn't stop apps from deing installed if Iinstall them manger astro file Manger?
What is the command in sqllite to see if the db entry has been changed?
I copied & pasted your commands and after a reboot still get "Can't install downloaded apk"
I did the same - even adapted the commands because the folder name wasn't the same, etc.
However, I'm trying to use SlideMe to install APKs and it keeps coming up with "Install Blocked" - any ideas?
sudermatt said:
So...the nook doesn't stop apps from deing installed if Iinstall them manger astro file Manger?
Click to expand...
Click to collapse
Once you enable this it will allow you to install the apps, it doesn't have anything to do with astro per se. You can just use astro to navigate to apks stored on your sd card. I use estrongs file manager myself and have installed apks from my sd card, dropbox and downloads from dolphin browser hd.
I'm getting the same error as everyone else.
I made the edits per your first post and pushed the file back to the NC. Then I rebooted. Placed an apk in the NC and tried to open it using Root Explorer. I try to install it and I get the "Installation of donwload apks is not supported" error.
barrosd12 said:
I did the same - even adapted the commands because the folder name wasn't the same, etc.
However, I'm trying to use SlideMe to install APKs and it keeps coming up with "Install Blocked" - any ideas?
Click to expand...
Click to collapse
Slideme works perfect for me so you did something wrong. Not sure what though, I would just redo it.
lovelacer said:
What is the command in sqllite to see if the db entry has been changed?
I copied & pasted your commands and after a reboot still get "Can't install downloaded apk"
Click to expand...
Click to collapse
just use
Code:
sqlite3 settings.db ".dump"
and then scroll down and look for INSERT INTO "secure" VALUES(4,'install_non_market_apps','1'); you want a 1 there at the end.
barrosd12 said:
I did the same - even adapted the commands because the folder name wasn't the same, etc.
However, I'm trying to use SlideMe to install APKs and it keeps coming up with "Install Blocked" - any ideas?
Click to expand...
Click to collapse
look in your tools folder for the settings.db file and check the modified by time and make sure the change you are making is made.
To clarify if there's a misunderstanding the path info and text before the > in the commands is just what you would see in your command prompt. the actual commands are after the >. These are the actual commands.
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db
update secure set value=1 where name='install_non_market_apps';
.q
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
What command did you have to alter?
also, maybe try
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
to push... I didn't have any problem with the other command and both appear to work for me.
Oh none, your commands worked awesomely, I just had to yank the folder designations that were there, which you've now done for everyone, so thanks!
I think it might be a problem somewhere else, I'm re-doing everything right now, I'll let everyone know
Ran these commands again with the additional adb push and still no dice. I checked to see that the db entry had been updated and it correctly has the install non market apps set to 1. I'm using root explorer as well I'll try estrongs as you have. Thanks for the help.
lovelacer said:
Ran these commands again with the additional adb push and still no dice. I checked to see that the db entry had been updated and it correctly has the install non market apps set to 1. I'm using root explorer as well I'll try estrongs as you have. Thanks for the help.
Click to expand...
Click to collapse
Confirmed now that SlideMe is not the issue - the settings are all correct on the PC, I can't confirm these settings for the NC. I tried re-adb-pushing and still no cigar here either. I'm getting app rejections from any source, downloaded on the NC and the SD card. Any idea what could be wrong?
Ok, definitely isolated the problem now.
I pull the settings from the NC, modify them, and everything works great, then it refuses to push it back, but says it succeeds, or something to this effect, because whenever I pull the file back from the NC, it says value=0
barrosd12 said:
Confirmed now that SlideMe is not the issue - the settings are all correct on the PC, I can't confirm these settings for the NC. I tried re-adb-pushing and still no cigar here either. I'm getting app rejections from any source, downloaded on the NC and the SD card. Any idea what could be wrong?
Click to expand...
Click to collapse
Not sure, I've got it working using this method on 3 different NCs myself. The only thing i can think of is that i had already installed estrongs file manager and a few other games before doing it. Maybe try using adb to install estrongs or astro and see if it will let you then.
estrongs i'm using: www mediafire com ?sxw6adfzvyp250m
astro: www mediafire com ?05scsbrnx2wfw4v
Novaglarion said:
Not sure, I've got it working using this method on 3 different NCs myself. The only thing i can think of is that i had already installed estrongs file manager and a few other games before doing it. Maybe try using adb to install estrongs or astro and see if it will let you then.
estrongs i'm using: www mediafire com ?sxw6adfzvyp250m
astro: www mediafire com ?05scsbrnx2wfw4v
Click to expand...
Click to collapse
Thanks for the file links - I'll give them a try, I really think the problem though is that the NC keeps resetting the value I push back for the non-market apps. I have no idea why it's doing this...
barrosd12 said:
Thanks for the file links - I'll give them a try, I really think the problem though is that the NC keeps resetting the value I push back for the non-market apps. I have no idea why it's doing this...
Click to expand...
Click to collapse
try pulling it back right after pushing the modified one, before rebooting, and see if it's even pushing correctly at all. If it is then being reset on reboot i don't know what the issue is.
Novaglarion, I am not able to do it either.
When you say "reboot", is that the same as power off and on?
boret said:
Novaglarion, I am not able to do it either.
When you say "reboot", is that the same as power off and on?
Click to expand...
Click to collapse
yes, the same.
make sure you're pushing the modified db file to /data/data/com.android.providers.settings/databases not to /data/data/com.android.providers.settings
it needs to be in the databases folder so it overwrites the original
bular211 said:
make sure you're pushing the modified db file to /data/data/com.android.providers.settings/databases not to /data/data/com.android.providers.settings
it needs to be in the databases folder so it overwrites the original
Click to expand...
Click to collapse
DAMN YOU!!!! such a simple thing and i missed it! You are correct. I'll update the original commands. Thanks for the good catch there.
Theres a new version of the Swype beta that is IMMENSELY better than the preloaded swype that comes with the atrix, it literally fixes all the annoying things of the older Swype versions:
http://beta.swype.com/
Swype 3.x beta works with the method below!
Process:
1) Use Root Explorer/Terminal/ADB to backup and then delete Swype.apk from /system/app and libSwypecore.so from /System/lib
2) Download the installer from https://beta.swype.com/android/get/ (on your phone)
3) Use installer to login and install latest version of swype
After your first phone reboot, if you are experiencing Swype Force closes after installing the latest swype, uninstall swype from your phone and then reinstall it; it should no longer force close after reboot.
If you are still experiencing force crashing after reinstall, try wiping your dalvik cache within CWM. Thanks Dudeman Broguy.
If you want to get in the latest beta, sign up over here. Registrations are open right now, hurry before they close them again!
Thanks to playin4sheezy for figuring this out: post #12
yes, i have been using it all day and it looks and feels great! if you have sideloading enabled, when you start the install it will ask to over write the current one.
graemegb said:
yes, i have been using it all day and it looks and feels great! if you have sideloading enabled, when you start the install it will ask to over write the current one.
Click to expand...
Click to collapse
Im trying to use the installer and it tells me to disable swype, and you cant disable the built in one. Can you pm me the apk?
Yea, I get to the point where it says "Licensing Swype, please wait...." and it doesn't get past that.
You need to go into /system/app and move Swype.apk to a backup folder on /mnt/sdcard
Then go into /system/lib and do the same for libSwypeCore.so
Give it a reboot and then try to install the beta. It worked for me
How did you move the apk, it wont allow me to do so
playin4sheezy said:
You need to go into /system/app and move Swype.apk to a backup folder on /mnt/sdcard
Then go into /system/lib and do the same for libSwypeCore.so
Give it a reboot and then try to install the beta. It worked for me
Click to expand...
Click to collapse
woo nice! thanks that worked for me! no more stupid tip window!
Krshaw18 said:
How did you move the apk, it wont allow me to do so
Click to expand...
Click to collapse
you have to use root explorer (and be rooted) or you could use terminal/adb (still have to be rooted)
Sorry for the noob questions! Move it completely? or make a back up of it? and also any apps out there like root explorer but free ?
I tried the above steps but the libswypecore is still in the system folder when i move it as it is read only...
Krshaw18 said:
Sorry for the noob questions! Move it completely? or make a back up of it? and also any apps out there like root explorer but free ?
Click to expand...
Click to collapse
If youre rooted, root explorer is worth the money. You have to move Swype.apk completely, and make sure its not there after moving or the install wont work.
Make sure if you are in Root Explorer that you click the R/W button at the top to make the system folder Read/Write access. Then long press the files and click move and goto sdcard and make a folder named "whatever you want" then click paste..
Or you could do this using adb with Atrix plugged into the computer:
goto command prompt
type the following:
adb shell
su
mkdir /mnt/sdcard/swype_backup
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /system/app/Swype.apk /mnt/sdcard/swype_backup
cp /system/lib/libSwypeCore.so /mnt/sdcard/swype_backup
rm /system/app/Swype.apk
rm /system/lib/libSwypeCore.so
Hopefully this gets you going
playin4sheezy said:
Make sure if you are in Root Explorer that you click the R/W button at the top to make the system folder Read/Write access. Then long press the files and click move and goto sdcard and make a folder named "whatever you want" then click paste..
Or you could do this using adb with Atrix plugged into the computer:
goto command prompt
type the following:
adb shell
su
mkdir /mnt/sdcard/swype_backup
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /system/app/Swype.apk /mnt/sdcard/swype_backup
cp /system/lib/libSwypeCore.so /mnt/sdcard/swype_backup
rm /system/app/Swype.apk
rm /system/lib/libSwypeCore.so
Hopefully this gets you going
Click to expand...
Click to collapse
Thanks a bunch!
Wont let me delete
Sent from my Atrix 4G using XDA App
joshuajoshua said:
Wont let me delete
Sent from my Atrix 4G using XDA App
Click to expand...
Click to collapse
Is your phone rooted? If so, then when you typed su in adb shell(not terminal) did it ask you for superuser permission? If so, then you should make sure and accept it.
If your phone is not rooted, then I don't think your gonna get this working
Sent from my MB860 using XDA App
I didnt need to move/delete libSwypeCore.so and the install worked fine.
andy2na said:
I didnt need to move/delete libSwypeCore.so and the install worked fine.
Click to expand...
Click to collapse
Ok. Be aware that I've had previous issues with swype after few days of use because I didn't remove that file
Sent from my MB860 using XDA App
I would suggest someone testing that you can in fact put it back to the stock setup. Mine somehow got deleted when i first got the phone, and it doesn't come back, factory reset or otherwise.
cegna09 said:
I would suggest someone testing that you can in fact put it back to the stock setup. Mine somehow got deleted when i first got the phone, and it doesn't come back, factory reset or otherwise.
Click to expand...
Click to collapse
i have been messing with swype for the last few days
i can guarentte you that if u installed / mounted a messed up version of swype (WVGA with a language pack in my case), you can just use put the backup stock swype back on /system/app and it'll be fine again
i get an error on sign-in into the installer, says device id dont match. any ideas?
EDIT: I had to log into mySwype and remove my old phone (nexus one) and then now it works!
Does anyone have the APK for the AT&T Hotspot App (WISPr46_Android22_signed.apk)? This is the one thing I miss most about the FR008 ROM - having the Aria automatically connect to AT&T hotspots. I know I can use the web form, but it's a pain in the rear.
Thanks in advance.
Brainded said:
Does anyone have the APK for the AT&T Hotspot App (WISPr46_Android22_signed.apk)? This is the one thing I miss most about the FR008 ROM - having the Aria automatically connect to AT&T hotspots. I know I can use the web form, but it's a pain in the rear.
Thanks in advance.
Click to expand...
Click to collapse
Go to this thread and download one of the rooted AT&T ROMs, unzip it and pull the apk out.
Found the APK in the most recent 2.2.2 ROM from Gene Poole. Pulled it out and copied it to the Aria. "Application not installed". Oh well. Thanks though!
Brainded said:
Found the APK in the most recent 2.2.2 ROM from Gene Poole. Pulled it out and copied it to the Aria. "Application not installed". Oh well. Thanks though!
Click to expand...
Click to collapse
How did you copy it to the phone? If you boot into recovery and mount /system as Read/Write, then you should be able to type "adb push [name of hotspot].apk /system/app.
I just ran Astro to browse to the APK, then let its app manager do its thing. Being a novice, I appreciate the more detailed instructions. I'll give that a try if I can follow that.
tpbklake said:
How did you copy it to the phone? If you boot into recovery and mount /system as Read/Write, then you should be able to type "adb push [name of hotspot].apk /system/app.
Click to expand...
Click to collapse
Brainded said:
I just ran Astro to browse to the APK, then let its app manager do its thing. Being a novice, I appreciate the more detailed instructions. I'll give that a try if I can follow that.
Click to expand...
Click to collapse
Assuming you have the adb tools installed on your PC (you probably do if you have rooted your phone):
1. Reboot the phone into ClockworkMod recovery. Make sure you do not have the USB cable connected at this point.
2. Select the "mounts and storage" option.
3. Select the "mount /system" option.
4. On your PC open a command window and set your working directory to your "adb\tools" directory.
5. Plug your phone into the USB cable.
6. In the command window type "adb devices". It should respond to with your device name.
7. Copy the WISPr46_Android22_signed.apk to the adb\tools directory.
8. In the command window type: adb push WISPr46_Android22_signed.apk /system/app
9. On the phone select "unmount /system"
10. Unplug the phone.
11. Reboot the phone.
I needed to install the tools, but after that everything went smoothly. However, I don't see the process running, and the icon does not exist. There is an .ODEX file for this package as well; do I need to do anything with that? Or do anything special after the phone rebooted?
Brainded said:
I needed to install the tools, but after that everything went smoothly. However, I don't see the process running, and the icon does not exist. There is an .ODEX file for this package as well; do I need to do anything with that? Or do anything special after the phone rebooted?
Click to expand...
Click to collapse
Yes you need to push the ODEX file too. That is probably why you got "Application not installed" the first time when you tried it through Astro.
Still no love. I pushed both files over, followed the instructions, and it does not appear to be there. Also tried using Astro again just for good measure (with the ODEX file in the same location as the APK), same message. I guess this package just will not install on this ROM.
I appreciate the help - if nothing else I've learned a lot about how the system works!
I'm looking at potentially flashing Gene Poole's 2.2.2 ROM over FR008 anyway, which should put this app back in place in the process, so we'll see.
Thanks again!
Update to this thread:
After upgrading my phone to the latest 2.2.2 ROM from Gene Poole (hoxnet 005b) I was able to successfully install this app using the method described above. The 005b ROM does not include the APK anymore though, so if you want this you'll need to snag it from an older ROM.
Greetings everyone!
New *registered* user here! I've been frantically sifting through post after post on the forums all night hoping to get some help with an issue I am having on my Vibrant.
Goal:
Remove some bloatware ONLY, not looking to install any ROMs or modify the phone too much...just clean some annoying apps and icons off.
Phone Information:
Model SGH-T959
Firmware 2.2
Baseband T959UVKB5
Kernel 2.6.32.9
Build FROYO.UVKB5
I currently have the latest version of Java, Android SDK, and SuperOneClick installed.
Install directory of AndroidSDK:
C:\AndroidSDK
My method of failure:
Open SuperOneClick, Click "Root"
Start, Run, "CMD"
cd c:\AndroidSDK\tools
adb shell
mount -o rw,remount /dev/block/st19/system
This is where it fails and I run into an endless loop of it telling me the proper usage of the "mount" command. I thought I had it at one point but when I typed: rm /system/AmazonMp3.apk all it did was tell me that it was a read-only file and that it couldn't be deleted.
Can someone help lead me in the right direction of what I am doing wrong? I rooted and removed all bloatware about a year ago but I just did an upgrade through MiniKies to the latest version of firmware and I can't seem to remember the process I went through that long ago to get it done right.
I apologize for possibly asking a question that has been asked numerous times but I just couldn't seem to get the wording right to get any helpful results in the search of the forums. Thank you so much for the time in reading this and the future help if any can be provided. Have a great night!!!
It looks like you are in the wrong directory. Open a command prompt in
C:\AndroidSDK\platform-tools
Open the platform tools folder. Click on a blank space > hold down the shift key > hit right click > select open command window here. Then enter the commands:
adb devices "to check if your device is connected. also make sure usb debugging is enabled on your phone.
adb remount
adb shell
su
mount -o remount,rw -t rfs /dev/stl5 /system
rm -r /system/app/[AppName].apk
If you want a list of all your /system/apps enter this command
cd /system/app
ls *.apk
This is much easier if you download rom toolbox from the market. All you do is go to /system/app and delete whatever bloatware you dont want.
BUT BE EXTREMELY CAREFUL WHEN DELETING SYSTEM APPS. ONLY DELETE WHAT YOU KNOW IS BLOATWARE OTHERWISE YOU WILL GET FC'S
good luck
Would I still need to follow the steps prior to that and use SuperOneClick to root the device or do I just skip that process and go straight to the cmd prompt?
Also, I followed a tutorial I found for installing the Android SDK that informed me to copy all the files from android-tools to the tools directory and use that instead but I don't know what the use in that is except for maybe a smaller directory name?
EDIT: I tried what you said with and with using SuperOneClick prior to the procedure and the cmd prompt displayed the following text:
*opened cmd promt in C:\AndroidSDK\tools (no files in platform-tools anymore)*
adb devices (it found my device connected)
adb remount (adb remount: no such file or directory exists)
The adb shell and su commands works fine BUT I still hit the endless loop of it trying to explain to me the "usage" of the mount command.
I will look into Rom toolbox as I'm trying to figure this out as well. Thank you.
I strongly recommend you download root explorer or some similar root browser app. Of course though your phone must be rooted. Just try rom toolbox. It has its own root browser within the app along with other useful features. This is probably the easiest way to uninstall the bloatware in your case since you are having issues with adb.
Sent from my Galaxy Nexus using XDA
Thank you!
Okay, I have the suggested "rom toolbox" downloaded from the market and I will try to use that but SuperOneClick does not root the phone deep enough for rom toolbox to see the phone as rooted so...will the "updated.zip" method work for this instead?
I haven't tried it before but I am willing to give it a go if you think it's the best method. If this is the method you recommend, would you happen to have a link to the most recent or atleast most trusted updated.zip rooting method?
CScrivener said:
Thank you!
Okay, I have the suggested "rom toolbox" downloaded from the market and I will try to use that but SuperOneClick does not root the phone deep enough for rom toolbox to see the phone as rooted so...will the "updated.zip" method work for this instead?
I haven't tried it before but I am willing to give it a go if you think it's the best method. If this is the method you recommend, would you happen to have a link to the most recent or atleast most trusted updated.zip rooting method?
Click to expand...
Click to collapse
You can try rooting your phone using this toolbox.
http://forum.xda-developers.com/showthread.php?t=954509
If that does not work for you i will try and find the link to the "one click root program" i use all the time.
Here is an excellent guide to root.
http://forum.xda-developers.com/showthread.php?t=849028
Sent from my Galaxy Nexus using XDA
Here is the program i use. Just remember to have usb debugging enabled on your phone. It really cant get any easier than this.
http://forum.xda-developers.com/showthread.php?t=739300
Sent from my Galaxy Nexus using XDA
So I downloaded the one click program you suggested and the program itself seems to bee pretty straight forward.
I connected phone to computer with debugging on. Opened program and hit one click root. It started doing it's thing...phone rebooted and went into recovery. I started to follow instructions up until I got to where it said install packages. When I clicked it, the phone said installation failed no such file our directory exists.
The phone is looking for the updated.zip file but none exists in the one click folder. There is a root.zip and an unroot.zip...do I need to rename one of them to proceed???
Thank you so much for all the help so far, I feel like I'm so close but just not there yet. You have been an incredible help!
Sent from my SGH-T959 using XDA
CScrivener said:
The phone is looking for the updated.zip file but none exists in the one click folder. There is a root.zip and an unroot.zip...do I need to rename one of them to proceed???
Click to expand...
Click to collapse
The way (Stock) Recovery works is if you are not "Install from SD" then it will look for the file labeled Update.zip. So you can rename only the Root.zip to Update.zip and make sure that is the only thing on your internal SD labeled that or with .zip Put the unroot.zip in a folder for now. Then try again.
Alright, will give that a try when I get home. I thought I read that the program copied the update.zip file to the phone during it's process so I didn't want to do anything to work against that. I will rename one of the files, copy it to the phone and give the one click root another shot. Thank you!
Sent from my SGH-T959 using XDA
CScrivener said:
Alright, will give that a try when I get home. I thought I read that the program copied the update.zip file to the phone during it's process so I didn't want to do anything to work against that. I will rename one of the files, copy it to the phone and give the one click root another shot. Thank you!
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
There is no need to rename anything. The program does it all for you. Play close attention to the first screen (green one) if it says update.zip copied successfully it will then reboot your phone to stock recovery. Once you are in stock recovery all you do is click reinstall packages. Keep clicking reinstall packages even if it reboots the first time. To prove my point mount your phone to your pc and check to see if the update.zip is copied onto the root of your into storage. If not well copy the update.zip from the last guide i suggested from above.
Also check to see if the superuser app is installed on your phone. The program also installs that along with the update.zip. If you have superuser then go to the market download rom manager so you could download CWM.
Sent from my Galaxy Nexus using XDA
Alright, so I tried it again once I got home. Didn't work BUT I did see that update.zip was installed into my phone. The sig verification failed, which means I need to change recovery versions to the one that skips sig verification correct?
I'll go search the forums for that since I remember seeing that a little while ago but that is the correct path I need to take at this point in time am I right?
Thank you so much! Big big help!
You can pull the CWR from my signature. Same as before. Put it on your internal labeled update.zip, boot into recovery and and scroll down to Reinstall Packages. Hit it. It will cycle and probably come back to stock recovery. Hit Reinstall Packages again and the stock recovery will go from blue to green (CWR).
Side note, probably from there you will be able to install the Superuser update.zip. Just go to Install from SD card and find it and hit it. The reboot. Might not but the CWR instructions above shoudl work for you.
Well I changed the recovery version using the file from http://forum.xda-developers.com/showthread.php?t=833423 and then used the OneClickRoot and was able to get the update installed (I think). The phone booted up normally, I noticed that SU Permissions was installed so I figure I am rooted correct? WRONG. Rom toolbox says I am not. Is there another way to verify? Should I reinstall Rom toolbox incase it's just bugging out on me?
So I tried using Rom Manager too. Looks as tho SU is not installed correctly, will have to try again I guess.
Cannot install CWR, tried and the recovery text stays blue even after 14 times of reinstalling packages...
This phone will be sent flying across the room sometime tonight I'm guessing. About to erase the entire thing and try starting from scratch again. (Start from Eclair and work my way up maybe)
If you are willing to start from Eclair it would be soooo much easier that all this stuff.
Odin to stock, flash CWR from my signature, go from blue to green and then flash Fishman's Bionix and you are good to go. Simple and way easier than all this mess. Just download Fish's and put it on you SD card somewhere you'll remember. Once in green recovery just scroll to that ROM and flash it per OP.
We've just been trying to Root you since on your OP you said you didn't want to flash a custom ROM.
Well...I'm still trying to avoid flashing Roms (I've upgraded through MiniKies and that's it).
I've only been trying to root just to clean bloatware off but it seems that I must be lacking the technical skills to follow instrcutions properly....nothing is cooperating and even after following all steps nothing wants to work like it should.
Grrrr! One last try to get CWR working before I lose my mind and need to take a break/walk away for a bit.
Ok, so I'm currently back to stock Eclair (ew!!) and about to boot to recovery to install CWR. Wish me luck on that one....
Wooo, CWR up and running! Now I just have to work on a flash maybe or whatever steps were suggested next...I might try the ROM you suggested.
The ROM gets placed on external sdcard and installed from within CWR correct?
Do most ROMs remove bloatware and useless apps?
Yes and are pre-Rooted. Put the ROM.zip on either card. I have a folder that I use. Boot into recovery and get green recovery back. Go to install from SD, find the ROM and flash it per the OP instructions.
Bloat free, pre-Rooted and usually has Voodoo so you can get Voodoo Sound from the market and have a sonic ear-gasm.
Just wanted to say thanks for all the help! I installed the suggested ROM last night and I am very happy with the results thus far. It was alot easier than I thought it would be. Flashing a ROM was MUCH more simpler than the root only decision. Thank you again!
I saw a post in this thread about getting the promotional space on AT&T S4 without flashing TMobile roms. I gave it a try, and it worked just fine. So I thought of sharing the files with you. I pulled them out of a deodexed TMobile rom.
Download the attached file. You need to push Dropbox.apk and DropboxOOBE.apk into system/app and fix permission. Then you need to push com.dropboxpartner into system/framework and again fix permission.
Then, you need to modify the build.prop using a root explorer. Find the following lines and modify them as follow:
ro.product.model=SGH-M919
ro.product.name=jfltetmo
ro.product.device=jfltetmo
Reboot your device, open the Dropbox app, and log in with your existing account, or create a new account. You will receive an email, and after fulfilling 5 of the 7 tasks, you will receive the 48 GB promotional space. After fulfilling the tasks, you can restore your build.prop to its original state.
Attached Files:
http://d-h.st/fZJ
smnfriend said:
I saw a post in this thread about getting the promotional space on AT&T S4 without flashing TMobile roms. I gave it a try, and it worked just fine. So I thought of sharing the files with you. I pulled them out of a deodexed TMobile rom.
Download the attached file. You need to push Dropbox.apk and DropboxOOBE.apk into system/app and fix permission. Then you need to push com.dropboxpartner into system/framework and again fix permission.
Then, you need to modify the build.prop using a root explorer. Find the following lines and modify them as follow:
ro.product.model=SGH-M919
ro.product.name=jfltetmo
ro.product.device=jfltetmo
Reboot your device, open the Dropbox app, and log in with your existing account, or create a new account. You will receive an email, and after fulfilling 5 of the 7 tasks, you will receive the 48 GB promotional space. After fulfilling the tasks, you can restore your build.prop to its original state.
Attached Files:
http://d-h.st/fZJ
Click to expand...
Click to collapse
Worked great for me, thanks! I already had 12GB and had completed the 5 Getting Started steps long ago. When I signed into the DropBox app and got it setup, I suddenly had 60GB for 24months and an email from DropBox.
Here's the instructions I followed:
Cleared cache of, cleared data of, and uninstalled the DropBox app I already had.
Reminder: backup your build.prop
I ended up using this build.prop Editor. When you open it, use the menu key to make a backup before touching anything. Then scroll through and make the changes prescribed in the OP.
Downloaded the file attached in OP.
Extracted files using my computer to my internal sdcard. Possible to do this with apps on your phone (various file explorers or unzip programs), but I found it easier to just do it over USB/MTP.
Fired up ADB Shell - could also use a terminal emulator from the device, but do not use the "stop" command below if you are using an emulator on the device.
Performed the following commands (after running "adb shell" from a command line on the computer):
Code:
$ su
# mount -o rw,remount /system
# stop
# cp /sdcard/Dropbox.apk /system/app
# cp /sdcard/DropboxOOBE.apk /system/app
# cp /sdcard/com.dropboxpartner.jar /system/framework
# reboot recovery
Device rebooted into TWRP, where I used the Advanced menu to Fix Permissions.
Rebooted back into the System like normal.
Opened the DropBox app and signed in. Setup the camera sync again of course (awesome feature).
Checked my mail - Woot.
Used the build.prop editor to restore my build.prop
Closed the build.prop editor and re-opened. For some reason after restoring the backup, the restored changes were not reflected until I restarted the editor. Whatever, but it worked.
Worked for me:thumbup: Thanks! Now what to do after the two year promo period ends...
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I'm already up to 50GB on doing something like this before. I'm not sure if it'll work again but I'll give it a whirl sometime today. Will report back if I find myself up to 98GB.
Perfectly working.
Followed general instructions (used FX root explorer instead of Android Terminal for dropping apks in designated locations) and this worked just fine without a hitch. I appreciate the straightforward and simple instructions.
All I did was flash Wicked (T-Mobile ROM) then KTOONSEZ touchjizz kernel. After getting my free dropbox space, I flashed back.
Sent from my SGH-I337 using xda premium
lol same here with GOLD3N3Y3 rom; any non-ATT rom works if you DL and activate it. i have my own server so im letting everyone in my family use it for our stuff.
Slade8525 said:
lol same here with GOLD3N3Y3 rom; any non-ATT rom works if you DL and activate it. i have my own server so im letting everyone in my family use it for our stuff.
Click to expand...
Click to collapse
i can confirm that this works on vzw.
Thanks, worked great on my VZW S4.
Aou said:
Worked great for me, thanks! I already had 12GB and had completed the 5 Getting Started steps long ago. When I signed into the DropBox app and got it setup, I suddenly had 60GB for 24months and an email from DropBox.
Here's the instructions I followed:
Cleared cache of, cleared data of, and uninstalled the DropBox app I already had.
Reminder: backup your build.prop
I ended up using this build.prop Editor. When you open it, use the menu key to make a backup before touching anything. Then scroll through and make the changes prescribed in the OP.
Downloaded the file attached in OP.
Extracted files using my computer to my internal sdcard. Possible to do this with apps on your phone (various file explorers or unzip programs), but I found it easier to just do it over USB/MTP.
Fired up ADB Shell - could also use a terminal emulator from the device...
Performed the following commands:
Code:
$ su
# mount -o rw,remount /system
# stop
# cp /sdcard/Dropbox.apk /system/app
# cp /sdcard/DropboxOOBE.apk /system/app
# cp /sdcard/com.dropboxpartner.jar /system/framework
# reboot recovery
Device rebooted into TWRP, where I used the Advanced menu to Fix Permissions.
Rebooted back into the System like normal.
Opened the DropBox app and signed in. Setup the camera sync again of course (awesome feature).
Checked my mail - Woot.
Used the build.prop editor to restore my build.prop
Closed the build.prop editor and re-opened. For some reason after restoring the backup, the restored changes were not reflected until I restarted the editor. Whatever, but it worked.
Click to expand...
Click to collapse
Using terminal emulator, after using #stop, device screen goes black... what do I do, just wait?
Cinosinu said:
Using terminal emulator, after using #stop, device screen goes black... what do I do, just wait?
Click to expand...
Click to collapse
You need to do it from your computer terminal/shell using adb shell command through the USB, not using a terminal emulator on the device. Stop does exactly what it says, it stops the device from running I think , or maybe just pauses.
You should be able to copy the files without stop though, it's probably riskier, and then you need to use reboot. You just need to copy the files into the right locations and then fix the permissions.
Cinosinu said:
Using terminal emulator, after using #stop, device screen goes black... what do I do, just wait?
Click to expand...
Click to collapse
These are linux commands. Stop, stops your device, and you cannot use it unless you reboot it. You can punch in the commands through your computer (this way, you need to install android sdk. Then, open the installed folder, and go to sdk\platform-tools. Here, you should hold shift, right click and select "open command window here", and punch the commands). Also, you can simply use a root explorer, and manually move the files to their folders and fix permissions
Just pull the battery and reboot. It happened to me also.
Sent from my SGH-M919 using xda premium
smnfriend said:
Also, you can simply use a root explorer, and manually move the files to their folders and fix permissions
Click to expand...
Click to collapse
What does this mean? I have ES fie explorer, trying to move the files I get a rewrite error. Do i need to fix the permissions first? What is the adb command?
thanks
I got it!!! :victory:
Why didn't someone tell me you must use the command 'ADB Shell' to start?
I'm no expert with ADB obviously. Knew it was something trivial. Hope someone else finds my comment helpful. :highfive:
Thank you OP and all! XDA rocks!
Thanks for pointing these things out. Yes, "stop" should only be used if doing this from an ADB shell. I've updated my instructions a tad bit to reflect this.
How can i do this for multiple accounts? I logged out and in and no luck.
Sent from my SGH-M919 using xda premium
kalparker said:
How can i do this for multiple accounts? I logged out and in and no luck.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
did you do a factory reset, re-install of your ROM, then the steps again? that may help by giving you a different device ID (you may have had this warning before in TiBU), which i'm guessing DB is looking for to limit 1 upgrade per device ID.
-rf
xrabbitfootx said:
did you do a factory reset, re-install of your ROM, then the steps again? that may help by giving you a different device ID (you may have had this warning before in TiBU), which i'm guessing DB is looking for to limit 1 upgrade per device ID.
-rf
Click to expand...
Click to collapse
That might work. In TiBu, I have the option to create a new, random device ID - might be a Pro feature only. Check your menu key, and near the bottom you can Manager your Device ID...
I would advise a nandroid backup first - this may screw up some of your other accounts, including Google. I've personally never tried it, but I would imagine it could cause some amount of chaos.
thanks!