For 1.6 use the patched Version from this thread -> http://forum.xda-developers.com/showthread.php?t=645286&highlight=market
put the Vending-Tattoo-patched.apk on your sdcard.
enter commandshell
Code:
adb shell
su
mount -o rw,remount /dev/block/mtdblock0 /system
cat /system/app/Vending.apk > /sdcard/Vending.org.apk
rm /system/app/Vending.apk
cat /sdcard/Vending-Tattoo-patched.apk > /system/app/Vending.apk
For 2.1 put the attached Version on your sdcard
enter commandshell
Code:
adb shell
su
mount -o rw,remount /dev/block/mtdblock0 /system
cat /system/app/Vending.apk > /sdcard/Vending.org.apk
rm /system/app/Vending.apk
rm /system/app/MarketUpdater.apk
rm -r /data/data/com.android.vending
cat /sdcard/Vending.inteks.2.1.apk > /system/app/Vending.apk
have fun
inteks
Yup, just tried it on my rooted X10mini, and it works - I can now see apps that didn't show up in the original market app
Hmmm, I tried to install this patch. Now I have no market at all on my phone. (yes I did reboot). Where did I slip up? Astro shows that the file is in the /system/app folder but it doesn't show up as a launchable app. If I click on it in astro it gives me the option to install it but if I try to do that I get an error message.
These are roughly the steps I used:
Backed up the original market to my sdcard [ busybox cp /system/app/Vending.apk /sdcard ]
Deleted the original market [ rm /system/app/Vending.apk ]
Copied the patched Vending-Tattoo-blah.apk to my SD card
(in the shell again) copied the patched vending apk to /system/app/
Make sure the original Vending app isn't open, and that you're "su"'d as root when you delete and copy
You don't need to rename the patched file back to Vending.apk - it works fine if it's left with the name from the Zip (this also makes it easier to remember that you are using a patched version!)
ok. i've done it, too. and it works fine ;o)
so it worked for me
put the Vending-Tattoo-patched.apk on your sdcard.
enter commandshell
Code:
adb shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
cat /system/app/Vending.apk > /sdcard/Vending.org.apk
rm /system/app/Vending.apk
cat /sdcard/Vending-Tattoo-patched.apk > /system/app/Vending.apk
have fun
inteks
ps: i will edit the 1. post as TUT ;-)
Works a treat on X10 Mini Pro. Nice to have all the apps back.
Works fine on my x10 mini pro
but before I can use the patched marked, I needed to change the system language to English(American) and re-accepting ToS of the market. After that I changed the language back to german.
Really appreciate the tut inteks. Everything works now. Happy, happy
Can someone suggest an app to search for, so we can tell if it's working or not?
I'm currently trying to get hold of SwitchPro, but it doesn't seem to show up, even with the patched Market app. :s
spatuluk said:
Can someone suggest an app to search for, so we can tell if it's working or not?
I'm currently trying to get hold of SwitchPro, but it doesn't seem to show up, even with the patched Market app. :s
Click to expand...
Click to collapse
of course, you may search for "financisto"
Cool - I found that app.
I think SwitchPro might be having market issues.. The Android Market really is a pile of buggy junk!
Where can I find this Vending-Tattoo-patched.apk file?
george_russos said:
Where can I find this Vending-Tattoo-patched.apk file?
Click to expand...
Click to collapse
It's in the post linked into by the first post in this thread
http://forum.xda-developers.com/attachment.php?attachmentid=292944&d=1268421305
Thanks!!!!
It works perfectly on my x10 mini.
Yeah it's all up and running fine here
crashes into force close for me when I try to download anything, any ideas? I didn't use adb, I used root explorer to install it, do I need to use adb?
Sent from my E10i using XDA App
thats an issue with this patch. one dirty fix is to download an app and as soon as it will try to install, you'll see force close screen. at this point, force close market, and (i dont know if we can do it in x10 mini yet) browse to "/cache" folder (folder "cache" in "root") using any file manager. there you'll see an apk file, thats the file you've just downloaded. click-install it
crashes for me as soon as it starts to download, no chance to get far enough to install, literally market crashes as it initialises the download
have tried going back to the original vending apk but now that crashes trying to initialise a download too, not good
Sent from my E10i using XDA App
Related
Get superuser whitelist. I pulled mine off a rooted Galaxy Tab:
Code:
linux$ adb pull /system/app/Superuser.apk
linux$ adb pull /system/bin/su
From a machine with ADB working, and communicating with your Nook:
Install Superuser.apk, and copy the su binary to /data/local:
Code:
linux$ adb install Superuser.apk
linux$ adb push su /data/local/
Shell into the Nook, remount the system partition read/write, and install the su utility to /system/bin:
Code:
linux$ adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
#
reboot Nook Color to get Superuser to show up in "extras." Now, you can get root from inside the Better Terminal Emulator Pro shell.
Thanks for the info. Just a quick note that on Cyanogenmod 6.1 RC2 (Nexus One), the su binary is actualy at /system/xbin/su rather than /system/bin/su
hharte said:
Get superuser whitelist. I pulled mine off a rooted Galaxy Tab:
Code:
linux$ adb pull /system/app/Superuser.apk
linux$ adb pull /system/bin/su
From a machine with ADB working, and communicating with your Nook:
Install Superuser.apk, and copy the su binary to /data/local:
Code:
linux$ adb install Superuser.apk
linux$ adb push su /data/local/
Shell into the Nook, remount the system partition read/write, and install the su utility to /system/bin:
Code:
linux$ adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
#
reboot Nook Color to get Superuser to show up in "extras." Now, you can get root from inside the Better Terminal Emulator Pro shell.
Click to expand...
Click to collapse
Thank you, very useful instruction!
Couple of questions though:
1. Any public repo where the working in NC Superuser.apk could be downloaded from? Not everyone out of NC owners owns Galaxy Tab.
2. More elaboration on "whitelist", please
3. If possible, show some example why someone might need this. I'd rather try to edit build.prop: pixel density, whatever, plus changing stock system Droid Sans into, say, much more beautifil Segoe WP. But it's just me though.
Thank you
aludal said:
Thank you, very useful instruction!
Couple of questions though:
1. Any public repo where the working in NC Superuser.apk could be downloaded from? Not everyone out of NC owners owns Galaxy Tab.
2. More elaboration on "whitelist", please
3. If possible, show some example why someone might need this. I'd rather try to edit build.prop: pixel density, whatever, plus changing stock system Droid Sans into, say, much more beautifil Segoe WP. But it's just me though.
Thank you
Click to expand...
Click to collapse
For #3, somebody may want to replace system fonts to support other languages than English. I have done that to Android 2.1 phones too.
aludal said:
Thank you, very useful instruction!
Couple of questions though:
1. Any public repo where the working in NC Superuser.apk could be downloaded from? Not everyone out of NC owners owns Galaxy Tab.
Thank you
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/showthread.php?t=665974
hharte said:
Get superuser whitelist. I pulled mine off a rooted Galaxy Tab:
linux$ adb pull /system/bin/su
Click to expand...
Click to collapse
Thanks Man, this was the part i didn't get and it's working now
PTzero said:
Here you go: http://forum.xda-developers.com/showthread.php?t=665974
Click to expand...
Click to collapse
So I installed this version of the Superuser apk but it seems to be an old version (2.0.3) with the ninja icon.
The latest version is 2.3.6.1 but I can't seem to get it to install (INSTALL_FAILED_UPDATE_INCOMPATIBLE).
Which is the latest version of Superuser apk that works with nC that has the 'Android Skull and Crossbones' icon and does anyone have the apk?
califrag said:
So I installed this version of the Superuser apk but it seems to be an old version (2.0.3) with the ninja icon.
The latest version is 2.3.6.1 but I can't seem to get it to install (INSTALL_FAILED_UPDATE_INCOMPATIBLE).
Which is the latest version of Superuser apk that works with nC that has the 'Android Skull and Crossbones' icon and does anyone have the apk?
Click to expand...
Click to collapse
That's odd. I was able to install 2.3.6.1 with no problem. I pulled it the apk off my Nexus One.
dark79 said:
That's odd. I was able to install 2.3.6.1 with no problem. I pulled it the apk off my Nexus One.
Click to expand...
Click to collapse
Could you pull and post your Superuser apk and your /system/bin/su file? I don't have a nexus one and when I tried using the Superuser apk and su file from the cyanogen 6.0 Nexus ROM it didn't seem to work either
EDIT:
Nevermind I got it working using the files attached (latest version 2.3.6.1)
(from here: http://forum.xda-developers.com/showthread.php?t=682828)
I also noticed that it had to grant itself Superuser permissions when I hit the "settings" tab. Under the settings tab I also noticed my 'su' version was 'original' and there was an update available which changed it to version '2.3.1-ef'. Not sure if this needs to be done for it to work right or not but thought I should mention it.
Will this work on just linux or windows?
You can do it on windows using ADB
califrag said:
Could you pull and post your Superuser apk and your /system/bin/su file? I don't have a nexus one and when I tried using the Superuser apk and su file from the cyanogen 6.0 Nexus ROM it didn't seem to work either
EDIT:
Nevermind I got it working using the files attached (latest version 2.3.6.1)
(from here: http://forum.xda-developers.com/showthread.php?t=682828)
I also noticed that it had to grant itself Superuser permissions when I hit the "settings" tab. Under the settings tab I also noticed my 'su' version was 'original' and there was an update available which changed it to version '2.3.1-ef'. Not sure if this needs to be done for it to work right or not but thought I should mention it.
Click to expand...
Click to collapse
What did you do to get this? I tried installing using ADB and Android Commander. I get the same error that says INCOMPATIBLE. This is the only program giving me issues.
sminker said:
What did you do to get this? I tried installing using ADB and Android Commander. I get the same error that says INCOMPATIBLE. This is the only program giving me issues.
Click to expand...
Click to collapse
Make sure to download the 'eclair\froyo' version.
this is the file im using
su-2.3.6.1-ef-signed
i did have it installed once and uninstalled, but now i cant reinstall it
sminker said:
this is the file im using
su-2.3.6.1-ef-signed
i did have it installed once and uninstalled, but now i cant reinstall it
Click to expand...
Click to collapse
use adb shell and go into /data/data and do an 'ls'
remove any directory there that looks like 'com.noshofou'
i was able to use z4root to get it installed
when I do:
cat /data/local/su > su
I get:
Cannot create su: remote access failed
Is there a Windows tutorial for how to install Super User on the NC or an apk that does the same thing?
Is there any advantage to put the binary into xbin versus bin
discourse said:
Is there a Windows tutorial for how to install Super User on the NC or an apk that does the same thing?
Click to expand...
Click to collapse
I would like a windows walkthrough also
WARNING: I've added this to my script and for some reason it has an adverse effect on the "n" button and Lock Screen if used BEFORE you complete the SetupWizard !!!
WARNING: Again BE WARNED if you do this mod before you finish the setup wizard you will loose the functionality of your "n" button and Lock Screen !!!
I have a feeling poster before me copied and pasted this from somewhere because notice how in his first sentence he says "Phone.apk and TelephonyProvider.apk" but then his script says "Mms.apk"....what happened to Phone.apk because there is no Mms.apk in the system folder on any Nook I have. So below is the corrected script and also this entire process in done in dos instead of in adb;
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Phone.apk /system/app/Phone.OLD
adb shell mv /system/app/TelephonyProvider.apk /system/app/TelephonyProvider.OLD
adb reboot
There is no adverse effect from doing this & it's confirmed after while in NookTools there is no Cell Standy service running.
Download [REMOVAL]
Want to undo this process?
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Phone.OLD /system/app/Phone.apk
adb shell mv /system/app/TelephonyProvider.OLD /system/app/TelephonyProvider.apk
adb reboot
Download [UNDO REMOVAL]
thanks, just got my NC yesterday, and already updated/rooted + done this hack
xmas_spirit said:
thanks, just got my NC yesterday, and already updated/rooted + done this hack
Click to expand...
Click to collapse
Run my script too from the other post?
xboxexpert said:
Run my script too from the other post?
Click to expand...
Click to collapse
No, I just manually entered commands in adb shell
xboxexpert said:
I have a feeling poster before me copied and pasted this from somewhere because notice how in his first sentence he says "Phone.apk and TelephonyProvider.apk" but then his script says "Mms.apk"....what happened to Phone.apk because there is no Mms.apk in the system folder
Click to expand...
Click to collapse
90% of the internet are sites posting info from other sites. Be glad he didn't slap on some ads.
I'm new here, but trying to learn.
Your code is:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Phone.apk /system/app/Phone.OLD
adb shell mv /system/app/TelephonyProvider.apk /system/app/TelephonyProvider.OLD
adb reboot
would it make sense to add:
adb shell mount -o remount,ro /dev/block/mmcblk0p5 /system
before the reboot? Or does that get done automatically upon reboot? I assume it is bad to leave it rw and not reset it to ro?
Thanks for this, I ran 'most' of your other script.
Auto-nooter, your script, adw launcher and it is coming along nicely. Still debating remapping the volume keys to back/menu...
DC_Rob said:
I'm new here, but trying to learn.
Your code is:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Phone.apk /system/app/Phone.OLD
adb shell mv /system/app/TelephonyProvider.apk /system/app/TelephonyProvider.OLD
adb reboot
would it make sense to add:
adb shell mount -o remount,ro /dev/block/mmcblk0p5 /system
before the reboot? Or does that get done automatically upon reboot? I assume it is bad to leave it rw and not reset it to ro?
Thanks for this, I ran 'most' of your other script.
Auto-nooter, your script, adw launcher and it is coming along nicely. Still debating remapping the volume keys to back/menu...
Click to expand...
Click to collapse
yes, the system partition goes back to RO after a reboot
Can this be done using terminal emulator
Sent from my PC36100 using XDA App
Ben74 said:
yes, the system partition goes back to RO after a reboot
Click to expand...
Click to collapse
Great, now I know. I write code for a living so, I try to be tidy....
Thanks
worked perfectly, thanks.......
midnightmaraude said:
Can this be done using terminal emulator
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Just use Root Explorer; rename those two files to anything else and reboot. Really, you could just remove them, renaming is just a precaution.
Thanks for this, makes the nook even better!
Mike
sent from my nookcolor using the xda app
Just to play devil's advocate, does anyone know if it's really improving battery life, rather than just no longer reporting cell standby under battery use details?
wvcachi said:
Just to play devil's advocate, does anyone know if it's really improving battery life, rather than just no longer reporting cell standby under battery use details?
Click to expand...
Click to collapse
I wondered that, but I also have no reason to run unused services so it can't hurt.
wvcachi said:
Just to play devil's advocate, does anyone know if it's really improving battery life, rather than just no longer reporting cell standby under battery use details?
Click to expand...
Click to collapse
I've been playing angry birds for 30 minutes and only lost 4% battery life. Seems to be awesome.
ummmmmm where is the script
ADB commands are only in OP lol
Therefore you need adb
No such file or directory?
I keep getting an error message stating the following:
"failed on '/system/app/phone.apk' - No such file or directory"
If I navigate to that file using Astro File Manager I can see the files, so I can't figure out what I'm missing here.
Salt72 said:
I keep getting an error message stating the following:
"failed on '/system/app/phone.apk' - No such file or directory"
If I navigate to that file using Astro File Manager I can see the files, so I can't figure out what I'm missing here.
Click to expand...
Click to collapse
Try capitalizing the file names.
Not to beat a dead horse, but this can easily be done in Root Explorer. All you're doing is renaming two files.
Not to be a cheapskate, but is there a free version of Root Explorer or a similar app that will do the same?
No
try Astro or Linda, thats free but ads supported
I'm running void, and I need to make some space in /system.
In particular I'm interested in those apps which get updated in the market, but are installed using the "gapps" module:
- gmail (com.google.android.gm-1.apk)
- youtube (com.google.android.youtube-1.apk)
- google search (com.google.android.googlequicksearchbox-1.apk)
- maps (com.google.android.apps.maps-1.apk)
- market (Vending.apk)
Can I remove them on /system/app? They are already in /data/apps it shouldn't be a problem. Thanks
This has been asked a lot of times before, but anyway:
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm *appname*.apk
The real answer of my question is: yes you can safely remove from /system/app all applications that you will find on market.
I tested it yesterday with success
Yeah, but my reply was a verbose version of "yes" Sorry, didn't get it right.
Titanum backup can remove all of those, and its included in one of the void packages... or maybe its already in the void rom. I cant remember which one at the top of my head. But even if you download the free one from market place with ads, it'll still do the job
You really should leave the filesystem they way you found it (read only). I would recommend that you append the above steps with:
Code:
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
It more than likely will be fine without it and on the next reboot it will mount as read only, but proper procedure is to put it back as read only when you're finished with it.
U can use Titaniumbackup to remove them or Root explorer(seach in market).
Sent from my LG-P500 using XDA Premium App
cannot edit build.prop. i get an error when trying to edit it with es file explorer (there was an error when trying to save this file.)
any help? ive edited it before, but i dont know how. im pretty sure i did it this way but im not sure why its not saving properly this time.
running calk+clemsyn rom/kernel combo.
thanks!
Copy it to another folder edit the copy and then move the edited file in the correct folder.
tried that already, didnt work. got another error
I use Root Explorer to do any editing.
Any other suggestions? I'd rather not have to pay for it
joshtb86 said:
cannot edit build.prop. i get an error when trying to edit it with es file explorer (there was an error when trying to save this file.)
any help? ive edited it before, but i dont know how. im pretty sure i did it this way but im not sure why its not saving properly this time.
running calk+clemsyn rom/kernel combo.
thanks!
Click to expand...
Click to collapse
If the build.prop you want to edit is in /system, then you'll have to mount /system read-write before you can modify any files there:
Code:
$ su [I]Become superuser. Prompt will change to '#'.[/I]
# /system/xbin/mount -w -o remount /system
[I]Edit the file[/I]
# /system/xbin/mount -r -o remount /system
You must have the Superuser app from Market and busybox installed on the gTablet for the commands to work. If you can't edit the file in ES File Explorer because of permission errors, copy the file into /mnt/sdcard via the command line, edit it there (or on the PC after removing the card), then move it back into place in /system and restore the old permissions:
Code:
$ cp /system/build.prop /mnt/sdcard/.
[I]a) The build.prop file in /mnt/sdcard should be editable now in ES File Explorer.
Edit the file, then do:
OR
b) Unmount the SD card via Settings > Storage, then remove the SD card and
edit the file elsewhere. Plug it back in, and, after it mounts do:[/I]
$ su
# /system/xbin/mount -w -o remount /system
# /system/xbin/mv /mnt/sdcard/build.prop /system/build.prop
# chown root.root /system/build.prop
# chmod 644 /system/build.prop
# /system/xbin/mount -r -o remount /system
All this is much easier through adb if you have that setup.
Note: Do not type the prompts--the '$' and '#' characters--in; they're just there to tell you what the Terminal screen should look like.
joshtb86 said:
Any other suggestions? I'd rather not have to pay for it
Click to expand...
Click to collapse
Did you have ES file explorer in Root mode?
In Es file explorer
Settings->Root Options -> both boxes checked, (HiAPK mode for first box)
I usually copy the file to sdcard and modify it, get ES explorer in root mode and copy it back. Do a backup before, in case you mess it up.
I usually use a terminal in su mode for editiing/copying, but that might not be needed.
cbay said:
Did you have ES file explorer in Root mode?
In Es file explorer
Settings->Root Options -> both boxes checked, (HiAPK mode for first box)
I usually copy the file to sdcard and modify it, get ES explorer in root mode and copy it back. Do a backup before, in case you mess it up.
I usually use a terminal in su mode for editiing/copying, but that might not be needed.
Click to expand...
Click to collapse
if i use CM Mod, i cant see any files. if i use HiAPK, all the files have -rw and a lot of stuff before it and i cant read anything, but it does mount. CW had problems mounting the drive. im gonna try out the terminal commands
rajeevvp said:
If the build.prop you want to edit is in /system, then you'll have to mount /system read-write before you can modify any files there:
Code:
$ su [I]Become superuser. Prompt will change to '#'.[/I]
# /system/xbin/mount -w -o remount /system
[I]Edit the file[/I]
# /system/xbin/mount -r -o remount /system
You must have the Superuser app from Market and busybox installed on the gTablet for the commands to work. If you can't edit the file in ES File Explorer because of permission errors, copy the file into /mnt/sdcard via the command line, edit it there (or on the PC after removing the card), then move it back into place in /system and restore the old permissions:
Code:
$ cp /system/build.prop /mnt/sdcard/.
[I]a) The build.prop file in /mnt/sdcard should be editable now in ES File Explorer.
Edit the file, then do:
OR
b) Unmount the SD card via Settings > Storage, then remove the SD card and
edit the file elsewhere. Plug it back in, and, after it mounts do:[/I]
$ su
# /system/xbin/mount -w -o remount /system
# mv /mnt/sdcard/build.prop /system/build.prop
# chown root.root /system/build.prop
# chmod 644 /system/build.prop
# /system/xbin/mount -r -o remount /system
All this is much easier through adb if you have that setup.
Note: Do not type the prompts--the '$' and '#' characters--in; they're just there to tell you what the Terminal screen should look like.
Click to expand...
Click to collapse
when i tried the mv command to move it back, i still got errors in moving it and was not able to
joshtb86 said:
when i tried the mv command to move it back, i still got errors in moving it and was not able to
Click to expand...
Click to collapse
Try
Code:
/system/xbin/mv /mnt/sdcard/build.prop /system/build.prop
instead of plain 'mv'. The default Android mv command is idiotically implemented. (See this post if you're interested in the details):
http://forum.xda-developers.com/showpost.php?p=13956585&postcount=4
Using 'cp' command instead of 'mv' should also work; this way, you'll also have a backup of build.prop in /mnt/sdcard/.
rajeevvp said:
Try
Code:
/system/xbin/mv /mnt/sdcard/build.prop /system/build.prop
instead of plain 'mv'. The default Android mv command is idiotically implemented. (See this post if you're interested in the details):
http://forum.xda-developers.com/showpost.php?p=13956585&postcount=4
Using 'cp' command instead of 'mv' should also work; this way, you'll also have a backup of build.prop in /mnt/sdcard/.
Click to expand...
Click to collapse
thanks so much again. i finally got it to work, but i just wanted to get netflix to work, and it still doesnt. after all that work. ugh.
JoTeC said:
I use Root Explorer to do any editing.
Click to expand...
Click to collapse
Thanks, I tried two other applications and they didn't work. Was able to edit with Root Explorer. didnt fix the Netflix playback. Bummer.
***** changing the Nexus S to HTC Vision and samsung to HTC did the trick.
Root explorer will work, and is a great app. Worht the money.
Also, ADB from a PC will work as well. Just install the android sdk and use ADB.
From windows cmd prompts the commands are just adb remount (to remount as root) then "adb pull /system/build.prop" (this will pull it to the sdk platform-tools folder that adb.exe is in) and then edit to your hearts delite.
"adb push build.prop /system/build.prop" to send it back.
I was able to use ES File System by unchecking the Mount File System option in the Root options menu and then rechecking it. I imagine that it forced a remount of the file system in a writable mode.
This worked on our nabi big tab hd24
We now have true multiuser, where everyone has their own login, files, emails, bookmarks, web history, etc; as it should be.
I first did a factory reset, then installed kingo root, then another reset, did the build prop edit this suggested (es file explorer did not work) but build prop editor did....
We now have the nabi big tab hd 24 running as our primary desktop workstation computer...
No we just wish for a room update to be made available with the latest version of Android.
4.4.2 is getting old, and as is common little manufacturer long term support...
Okay, we discovered that having the Webtop over HDMI breaks the OTA update.
So to update you're going to have to undo that mod, and possibly any others.
If you backed up your original files great, go restore them, clear the dalvik-cache and you're fine.
Otherwise, use the attached files and these steps to recover:
Credit: _unknown for the original posted instructions I'm using as a template
Please let me know if there are any adjustments that need to be made to the code, as I'm pulling this from memory and had stored the backups on my phone and was restoring from there.
Requirements:
Be rooted
Be able to work with adb
First, unpack the attached zip-file.
Go into the correct directory for your version.
Now run (in a terminal)
Code:
# I use /data/tmp as the storage location, you can also use /sdcard/
adb push DockService.apk /data/tmp
adb push PortalApp.apk /data/tmp
adb push DockService.odex /data/tmp
adb push PortalApp.odex /data/tmp
adb shell
# you are now in the phone shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
# you could mv these files to backups if you intend on doing the mod
# again after the update
rm /system/app/DockService.*
rm /system/app/PortalApp.*
rm /data/dalvik-cache/*DockService* /data/dalvik-cache/*PortalApp*
# move the files from /data/tmp to /system/app
mv /data/tmp/DockService.* /system/app/
mv /data/tmp/PortalApp.* /system/app/
reboot
NOTE: This zip will not in any way help you to obtain root! You must be rooted prior to attempting to apply this patch, or it will not work!
pksublime said:
Okay, we discovered that having the Webtop over HDMI breaks the OTA update.
So to update you're going to have to undo that mod, and possibly any others.
If you backed up your original files great, go restore them, clear the dalvik-cache and you're fine.
Otherwise, use the attached files and these steps to recover:
Credit: _unknown for the original posted instructions I'm using as a template
Please let me know if there are any adjustments that need to be made to the code, as I'm pulling this from memory and had stored the backups on my phone and was restoring from there.
Requirements:
Be rooted
Be able to work with adb
First, unpack the attached zip-file.
Go into the correct directory for your version.
Now run (in a terminal)
Code:
# I use /data/tmp as the storage location, you can also use /sdcard/
adb push DockService.apk /data/tmp
adb push PortalApp.apk /data/tmp
adb push DockService.odex /data/tmp
adb push PortalApp.odex /data/tmp
adb shell
# you are now in the phone shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
# you could mv these files to backups if you intend on doing the mod
# again after the update
rm /system/app/DockService.*
rm /system/app/PortalApp.*
rm /data/dalvik-cache/*DockService* /data/dalvik-cache/*PortalApp*
# move the files from /data/tmp to /system/app
mv /data/tmp/DockService.* /system/app/
mv /data/tmp/PortalApp.* /system/app/
reboot
NOTE: This zip will not in any way help you to obtain root! You must be rooted prior to attempting to apply this patch, or it will not work!
Click to expand...
Click to collapse
mv /data/tmp/PortalApp.* /system/app/
# mv /data/tmp/DockService.* /system/app/
mv /data/tmp/DockService.* /system/app/
failed on '/data/tmp/DockService.apk' - Cross-device lin
# mv /data/tmp/PortalApp.* /system/app/
mv /data/tmp/PortalApp.* /system/app/
failed on '/data/tmp/PortalApp.apk' - Cross-device link
Okay working on it...
try using cp instead of mv
Thank you. Will do this tonight
cp worked instead of mv
was able to update, thankyou.
lcpl said:
cp worked instead of mv
Click to expand...
Click to collapse
thanks, i updated the instructions
at least the important part was getting the files up for people, most can figure it out from there
Has anyone that has updated to the newer OTA version been able to re-hack the Webtop / HDMI output using the original method?
Thanks!
alohajeff said:
Has anyone that has updated to the newer OTA version been able to re-hack the Webtop / HDMI output using the original method?
Thanks!
Click to expand...
Click to collapse
You rave to re-root after the update, but yeah, it's the same thing.
Haven't got that far yet, I'm just starting.
Give me a bit and I'll tell you how it went.
Update 1:
Installed the update with out a hitch, save for a line of code
"rm /data/dalvik-cache/*DockService* /data/dalvik-cache/*PortalApp*"
I had to change to
"rm /data/dalvik-cache/*.*"
The dalvik chache is rebuilt at the next reboot, so there isn't much harm wiping the whole thing.
And Yeah, i had to change that the "mv" to"cp"
Update 2:
Rooted just fine using :/showthread.php?t=1217416
Update 3:
Followed : /showthread.php?t=1199443
But as of again, I changed
"rm /data/dalvik-cache/*DockService* /data/dalvik-cache/*PortalApp*"
to
"rm /data/dalvik-cache/*.*"
and
"mv" to"cp"
Works just as well as before. Even with 9/12's update
I had some trouble before, but It looks like I just had to re apply the hack one again. It's all good now. Dockless webtop on the latest OTA.
It's not working for me for the 10/12 update. Any ideas? Do the odex files have to be renamed to .bak?
Airwolf79 said:
It's not working for me for the 10/12 update. Any ideas? Do the odex files have to be renamed to .bak?
Click to expand...
Click to collapse
Yes.
Sent from my MB855 using Tapatalk
John Kotches said:
Yes.
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
So what is the easiest way to go about this? Do I have to rename them before I push, or once they're installed?