Related
There is many of you that asks how to remove this and that preinstallaed apps in different ROM
When a developer put apps in system/app it can not be removed so easy.
But if you have RomManager or fakeflash´s update.zip there is a other way.
I have attached a zip fil that contains a ordinare ROM installation script that only contains delete and copy.
Download file and unzip on your computer and take a look in the folders
data/app
META-INF/com/google/android/update-script
system/app
If your only wish is to remove a systemapp
edit the file update-script (textfile)
and add line with the filename of what you want to remove:
(example)
delete SYSTEM:app/unwanted.apk
delete SYSTEM:app/unwanted.odex
If you want to install some apps put them in system/app for not installable
and data/app for apps that can be removed as usual
rezip folders and install zip with RomManager NO WIPE!!
cm6 azures you will get a error because not same structure for data/app
never mind just select reboot. Delete will work anyway.
Sometimes there will be .so files in system/libs too. They are little more difficult to know which to remove so that demands more knowledge of the app.
Use for instance Astro filemanager or Estrong to look in system/app for correct filename to delete
Script work even if *.odex not exist.
The fact that when you zip folders it will not be signed so file will not work with adb recovery
Googleapps filenames:
CarHomeGoogle.apk, CarHomeLauncher.apk, com.amazon.mp3.apk,
Facebook.apk, GenieWidget.apk, Gmail.apk, GoogleBackupTransport.apk,
GoogleCalendarSyncAdapter.apk, GoogleContactsSyncAdapter.apk,
GoogleFeedback.apk, GoogleGoggles.apk, GooglePartnerSetup.apk, GoogleQuickSearchBox.apk, GoogleServicesFramework.apk, googlevoice.apk,
HtcCopyright.apk, HtcEmailPolicy.apk, HtcSettings.apk, kickback.apk, LatinImeGoogle.apk, LatinImeTutorial.apk, Maps.apk, MarketUpdater.apk, MediaUploader.apk, NetworkLocation.apk, OneTimeInitializer.apk, PassionQuickOffice.apk, SetupWizard.apk, soundback.apk, Street.apk, Talk.apk, talkback.apk, Twitter.apk, Vending.apk, VoiceSearch.apk, YouTube.apk, QuickSearchBox.apk, Provision.apk
Other apps:
ADWLauncher.apk, Gallery3D.apk
but filename may be different depending of ROM
Mainpart must exist for using phone normally
Hope that this help to remove "non-removable" systemapps in future.
/Snakehult
Good guide.
via Legend using XDA-app
Thanks snakehult - great guide and very useful!!
snakehult said:
(example)
delete SYSTEM:app/unwanted.apk
delete SYSTEM:app/unwanted.odex
Click to expand...
Click to collapse
It may be worth explaining how people:
- can find out the name of the app they want to remove;
- how they know whether to add the suffix of *.apk or *.odex, or both;
Thanks again for your efforts!
c_man said:
Thanks snakehult - great guide and very useful!!
It may be worth explaining how people:
- can find out the name of the app they want to remove;
- how they know whether to add the suffix of *.apk or *.odex, or both;
Thanks again for your efforts!
Click to expand...
Click to collapse
Yes you can use some regular filemanager such Astro or Estrongs and look in system/app
Always delete both, script work even if odex file is missing
c_man said:
It may be worth explaining how people:
- can find out the name of the app they want to remove;
- how they know whether to add the suffix of *.apk or *.odex, or both;
Thanks again for your efforts!
Click to expand...
Click to collapse
cool guide!
anyway you have to detect the filename of the apps this way:
enter the recovery mode (in modaco-root-r4: recovery-windows.bat)
now type:
adb shell
mount -t yaffs2 /dev/block/mtdblock3 /system
ls -l /system/app
(this will give you the list of system apps, with space usage)
you have to delete both .apk and .odex files (the latter may not exist)
I use to delete the bigger ringtones too, the list is given by
ls -l /system/media/audio/ringtones
it is safe to delete, after you setup the google accounts (ie after first boot):
HTCSetup*
com.htc.Setup*
Stock*
HtcFoot*
NewsRead*
wow its working......thanks dude........
Uploaded with ImageShack.us
http://android.modaco.com/content/h...apps-from-the-htc-desire-with-adb-in-windows/
Simple guide from MoDaCo
That must be the hardest way to remove apps i guess Have you seen "modaco guide"? All you have to do is reboot your phone in to recovery mode and type 2-3 commands in ADB. Simple as that.
Thanks anyway for your efforts
Many way för same thing
But with a custom-made zipfile you always remove/install favourite apps without adb. And quick modify new ROM install.
Sent from my Legend using XDA App
Hello,
Good guide.
The Legend may be rooted to do this?
I am a newbie.
Thanks.
bobstar_fr said:
Hello,
Good guide.
The Legend may be rooted to do this?
I am a newbie.
Thanks.
Click to expand...
Click to collapse
As I see it, no use to do much in the dev forum without an rooted Phone
hey guys, thanks for bringing this up. i just tried modaco site method and i deleted stock and its widget only. the internal storage shot from 113 mb to 122 mb and ram from 42 to 134 mb !
what else can i delete
Learners Lisence said:
hey guys, thanks for bringing this up. i just tried modaco site method and i deleted stock and its widget only. the internal storage shot from 113 mb to 122 mb and ram from 42 to 134 mb !
what else can i delete
Click to expand...
Click to collapse
Just delete what you will never use and....no regret
thank you cryshop for your expert advise
i tried deleting Innovation.mp3 by this script -
adb-windows shell rm /system/media/audio/ringtones/Innovation.mp3
said file not found even though its listed.
whats my mistake ?
i will try snakehults method also but later.
thanks
im trying to use modaco's method but what is the green recovery menu?
i dont understand i go in fastboot then recovery and then?thank you
edit done im stupid
Learners Lisence said:
thank you cryshop for your expert advise
i tried deleting Innovation.mp3 by this script -
adb-windows shell rm /system/media/audio/ringtones/Innovation.mp3
said file not found even though its listed.
whats my mistake ?
i will try snakehults method also but later.
thanks
Click to expand...
Click to collapse
Hmm, did you forget a slash or a letter in the command? because I tried and I could actually delete it.
@kdma : install ROM Manager from the Market, and there is an option inside the app : Reboot into Recovery (easiest way to get into recovery mod)
I also deleted /system/etc/clock* and saved some space again
(of course I don't need Htc clock widgets)
cryshop said:
Hmm, did you forget a slash or a letter in the command? because I tried and I could actually delete it.
Click to expand...
Click to collapse
cryshop, i was typing in the wrong directory
Ps - snakehults's appfixer is real delight ! smooooth.
except that my winzip is a trial version and legend dont recognize winrar files.
I was wondering how i got such good figures for change in space and ram the first time. i havent since then. my legend just likes the rebooting involved coz i dont use task killers anymore. and maybe i deleted more than just stock the first time
Will this work with android 2.2 on Hero?
Hey I've been looking all over for something like this. I downloaded the zip, added the lines
delete SYSTEM:app/mms.apk
delete SYSTEM:app/mms.odex
delete SYSTEM:app/email.apk
delete SYSTEM:app/email.odex
and rezipped it.
I used Rom Manager and selected install rom from SD card. It rebooted, seemed to execute the zip. But the original email and mms apps are still installed. What am i doing wrong?
kdma said:
im trying to use modaco's method but what is the green recovery menu?
i dont understand i go in fastboot then recovery and then?thank you
edit done im stupid
Click to expand...
Click to collapse
The first thing you should do is download the required zip file from modaco (I'm a new user of xda and is not permitted to post outside links here. You may easily find that post "24/May r4 - HTC Legend rooting guide - Now with 1.31.x" in android.madaco.com)
I think many of us rooted the device followed the instructions of Paul. So that file might be already in your hands.
Fastboot and then recovery, as you have done before. Run Recovery-linux.sh (or Recovery-windows.bat, if you use Windows) in a terminal window - your device shall be at the green recovery screen.
Open another terminal window and enter:
./adb-linux shell mount /system
and then you can push, pull or rm file. For example,
./adb-linux shell rm /system/app/Calculator.apk
./adb-linux push abc.so /system/lib
--
I didn't notice you have already solved the problem, when I compiled this post. It is no longer useful.
Hey guys,
I have updated this thread with a script and files for those who are unsure of how to make this work. Its a quick script so don't expect much, reverse engineered to simply de-odex your phone fully.
You must have ADB added to your "Allow" list in Superuser.apk.
WARNING:
This can brick your phone if you do not do things properly. I have tested it on my phone and it worked flawlessly. Once again though, I was on a fresh install of 1.4.2.
INSTRUCTIONS:
-Download files here <-- Updated link
-Extract files to C:\
-Execute SevensDeodex1.1.bat
-Wait a few minutes
-Phone will reboot and take a while to start up
-Done
MANUAL INSTALL:
Navigate to extracted files through CMD or Shell
Type the following commands
adb.exe push 142system.tar.gz /data/local/tmp/
adb push bin/install_script.sh /data/local/tmp/install_script.sh
adb shell
Once in adb type:
su
cd /data/local/tmp
chmod 755 install_script.sh
./install_script.sh
Known issues:
-Photoeditor.apk deleted as de-odexing this was a problem. So what
Updates:
1.1 Updated to fix some issues with the bat file.
1.0 Original release
Special Thanks to: NFHimself for showing me the way
i know that ken was looking for a dump of /system and /data, did you or will you toss one at him seven?
i would, but i was working on some frameworks on 0.37 that i don't really want to leave unfinished
raybond25 said:
i know that ken was looking for a dump of /system and /data, did you or will you toss one at him seven?
i would, but i was working on some frameworks on 0.37 that i don't really want to leave unfinished
Click to expand...
Click to collapse
You want me to upload a framework dump?
Will that help, let me know exactly what you need and I'll try to help.
I found aout about that method too last night, I just deleted the photoeditor apk and odex file and it ran through the app deodex fine. When I tried to copy my framework files though adb shell refused to replace the files, even using the -f force command.
Yes... could someone throw me:
/system/
/data/
I know that's a lot... but that's what I'll need. Thanks guys. PM me if you need a private FTP server to upload it. If not, you can use Dropbox or Hotfile.com (I have a premium account).
http://db.tt/kdUycD1 just dumped that last night..might be a slow downlad though...raybond25 gave me the script for it since I've never done it hope its what you need
Sent from my MB860 using XDA Premium App
that was something that was needed, but after that it needed to be deodexed. I sent snake's dump to NFHimself and he deodexed it.
Deodexed system
raybond25 said:
that was something that was needed, but after that it needed to be deodexed. I sent snake's dump to NFHimself and he deodexed it.
Deodexed system
Click to expand...
Click to collapse
so with a deodex script we can deodex our system and framework?
Sent from my MB860 using XDA Premium App
SN4K3B1T3 said:
so with a deodex script we can deodex our system and framework?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
i'm not sure how NFH did it, you'd have to ask him about his method but that system has deodexed /app and /framework
i'm not sure if he plans on writing a script that will do this and releasing it or not, that deodex was mainly because kennpenn was looking for it.
but, yes it can be done.
Will upload deodex files now
any special tricks ive tried deodexing at least 4 times and it stops at 91 out of 134...pissed
yeah i got an error at core.odex
I agree there is no sense reinventing the wheel, I used dsixda's htc kitchen to do it, had a working folder for something else, simply replaced app and framework with the files from telstra and ran his script and selected deodex. He has bits in there specific to the Atrix, I noticed that when looking at the scripts to do my own version, didn't bother after since it was already done. No errors, and haven't had a problem in over a month so it's all good, it only needs to be done once per firmware.
My rule of thumb, don't run anything for your $$$ phone if you don't have source or can read the scripts yourself, especially if it hasn't been tested specifically on your phone. Don't be in a rush to execute some file or script unless it's from a family member you really like with lots of money.
Cheers!
NFHimself said:
I agree there is no sense reinventing the wheel, I used dsixda's htc kitchen to do it, had a working folder for something else, simply replaced app and framework with the files from telstra and ran his script and selected deodex. He has bits in there specific to the Atrix, I noticed that when looking at the scripts to do my own version, didn't bother after since it was already done. No errors, and haven't had a problem in over a month so it's all good, it only needs to be done once per firmware.
My rule of thumb, don't run anything for your $$$ phone if you don't have source or can read the scripts yourself, especially if it hasn't been tested specifically on your phone. Don't be in a rush to execute some file or script unless it's from a family member you really like with lots of money.
Cheers!
Click to expand...
Click to collapse
I've updated the OP and thread title.
Now includes a working script to deodex. Very simple and straight forward, no need to use any other tools and this should make it easier for all other users who are new at this.
Thanks for your help sir, you are a king amongst men!
Not a problem.
One thing about the script, Superuser.apk needs to know about the shell having root access, so once you root the phone, do an adb shell su command, accept the prompt from Superuser.apk, and you are good to go. I tossed some stuff into my root.bat (.sh) scripts to launch Superuser.apk and update it's database automatically, bit of a hack but worked the last 20 times I tried it.
NFHimself said:
Not a problem.
One thing about the script, Superuser.apk needs to know about the shell having root access, so once you root the phone, do an adb shell su command, accept the prompt from Superuser.apk, and you are good to go. I tossed some stuff into my root.bat (.sh) scripts to launch Superuser.apk and update it's database automatically, bit of a hack but worked the last 20 times I tried it.
Click to expand...
Click to collapse
ooooooooh you absolutely right.
Since I'm new at making scripts i'm going to simply just update the script so that the user has to put ACCEPT on the phone before running the rest of the commands you know, new vers coming now
I keep getting this error.. I took a screen shot of it.. Any ideas?
nate_benji said:
I keep getting this error.. I took a screen shot of it.. Any ideas?
Click to expand...
Click to collapse
easy. It means you do not have root access allowed with ADB.
If you're phone is not rooted, go to the link in my signature that shows you how to root.
If you have root and you know its working then you must do the following first:
Open up your command prompt - make sure to keep your phone's screen active and unlocked.
Type "adb shell"
Once you have $
type "su"
check your phone's screen, as you will be prompted to allow, or deny access.
Select "Allow"
Now you are set to go, execute the script again.
Let me know of your results
I just tried it on a fresh SBF flash and root, root confirmed working though adb shell. It pushes everything fine, but when it goes to execute the script the cmd window just closes.
EDIT: Managed to get a screen right before it closes. Not sure of the problem because root works in adb and titanium backup.
Open up CMD manually
then navigate to where the bat file is and run it.
Tell me what the output is please.
Also, you said Root is working through ADB.
Then try to do everything manually as such:
adb.exe push 142system.tar.gz /data/local/tmp/
adb push bin/install_script.sh /data/local/tmp/install_script.sh
adb shell
Once in adb type:
su
cd /data/local/tmp
chmod 755 install_script.sh
./install_script.sh
And there you go.
Here's an alternative way to gain more RAM and performance without odexing.
Get more RAM and faster responses by disabling verify-bytecode!
This process will usually give just as much as performance boost as odexing SYSTEM and USER app.
Click to expand...
Click to collapse
AS WITH ANY MODDING PROCEDURE/SCRIPTS FOR YOUR PHONE, THIS SCIPT ALSO COMES WITH NO WARRANTY. AUTHOR HOLDS NO RESPONSIBILITY FOR ANY DIRECT AND INDIRECT CONSEQUENCES OF RUNNING THIS SCRIPT. MAKE SURE YOU HAVE MADE A NAND BACKUP BEFORE PROCEEDING. MAKE SURE YOU HAVE AT LEAST 15% FREE ON /SYSTEM, THIS IS IMPORTANT BECAUSE IF YOU RUN OUT OF SPACE THINGS WILL GO BADLY WRONG..
Requires busybox.
If your system partition is almost full, have a look at http://forum.xda-developers.com/showthread.php?t=734236.
This script will *attempt* to odex all apks found at /system/app. Theming would be impossible once the ROM is odexed. Themes applied at the time of odexing will be preserved. If you plan on applying a theme, apply it before odexing. If you want to theme after odexing, you must deodex the ROM before theming. If you change themes often, odexing is not for you.
Quick Instructions for Windows:
Connect the phone with USB cable and enable USB debugging. (No wireless or Android Terminal shell)
Put the phone in airplane mode.
Download and extract the attached file and run odex.bat
Instructions for advanced users:
This attachment contains a folder called odex. Push that folder to data and set the permission of odex.sh to 4755. Mount system as r/w(could be done via adb remount system). Next, execute odex.sh. All of this should be done via USB using ADB shell. Do not use wireless adb or Android Terminal.
Advantages:
More free space in system partition.
Faster booting.
More free RAM(I was able to gain 20-30MB.)
Faster access to system apps.
Disadvantages:
Cannot be themed after odexing.
APK tweaks cannot be applied.
Might break some of the non-AOSP system apps such as Root Explorer if they are installed as system app.
Acknowledgments:
Only the odex.bat was created by me. Similar projects were done in past but most of the downloads are broken. So, I collected together different stuff from different places to put together this package.
adb.exe is from the RATC batch ROOT.
adb dlls are from Android SDK
odex.sh is from Paul O Brian from MoDaCo (pastebin.com/EZLWUdea)
zip, zipalign and dexopt-wrapper are from XDA (http://forum.xda-developers.com/showthread.php?t=734236)
Next aim: Odex for apps in data/app
Update:
I got 1017 on quadrant and 61.8fps on swiftdroid 2.0 M6 overclocked to 844MHz(offline mode with wifi on. No apps except system apps). It must be noted that sometimes odexed ROM performs slightly slower in benchmarks but the difference is very small. However, this does not mean their performance is lower. Odex means apps could load fast thereby making app switching, app loading really fast. And, it also reduces system RAM usage which means more apps could stay in memory making multi-tasking easier. Odexing is something like swap or compcache. Sacrifice something to gain something else. This is for some people who think odexing is useless. The drop in speed is so small that it cannot be noticed without a benchmark but the performance of the phone increases noticeably due to more space in dalvik and RAM.
Nice work.
Few remarks.
1) you need busybox installed for find
2) "busybox --install" defaults to /usr/bin (not available on android)
use "busybox --install ." when you cat-ed it to /system/xbin
Something seems not OK though with the odex.sh script?
Code:
Unable to create './Contacts.odex': File exists
zip warning: name not matched: classes.dex
zip error: Nothing to do! (./Contacts.apk)
Unable to open './Contacts.apk' as zip archive
failed on './Contacts.apk.new' - No such file or directory
Unable to create './VoiceSearch.odex': Permission denied
Unable to create './Music.odex': File exists
zip warning: name not matched: classes.dex
Cheers
Hmm, sorry, I just started to assume busybox is default since the two ROMs of concern(Joe's. Gingerbread and swiftdroid) had busybox.
Those apks are already odexed. You are on a partially odexed rom. Nothing to worry.
tweakradje said:
Nice work.
Few remarks.
1) you need busybox installed for find
2) "busybox --install" defaults to /usr/bin (not available on android)
use "busybox --install ." when you cat-ed it to /system/xbin
Something seems not OK though with the odex.sh script?
Code:
Unable to create './Contacts.odex': File exists
zip warning: name not matched: classes.dex
zip error: Nothing to do! (./Contacts.apk)
Unable to open './Contacts.apk' as zip archive
failed on './Contacts.apk.new' - No such file or directory
Unable to create './VoiceSearch.odex': Permission denied
Unable to create './Music.odex': File exists
zip warning: name not matched: classes.dex
Cheers
Click to expand...
Click to collapse
Sent from my GT540 using XDA App
i just applied a cm7 theme and the rom is still stable and the theme was applied after running the batch file
That depends on the theme. A theme that modifies odexed system apks will break things while an apk that modifies only the unodexed system apks will work. So, for most users, it would be safer to say that you shouldn't apply themes.
Sent from my GT540 using XDA App
First post has been updated.
Sent from my GT540 using XDA App
if you want to get even more ram odex your framework ... On my froyo with odexed framework i got 123mb ram with stock autokiller values This is only odexing system/app so you are able to theme your framework without problems ...
mikegapinski said:
if you want to get even more ram odex your framework ... On my froyo with odexed framework i got 123mb ram with stock autokiller values This is only odexing system/app so you are able to theme your framework without problems ...
Click to expand...
Click to collapse
I will try that. I was trying to odex data/apps. I odexed quadrant apk and saw a small gain of around 1% but it could be purely due to error or differences in conditions.
Framework isn't odexed doesn't mean all themes would work. Some themes modify other apks for more customizations. So, if you apply such a theme, it will break things. Better be safe than sorry. Saying that most themes would work, people might try to flash all themes thinking it won't break anything. It's just safer to deodex before theming. Of course, if you know what theme modify only framework and what theme modifies other apks, this shouldn't be a concern.
Update: odexing framework apk has reduced free memory to 60MB from previous 75MB
Might try add this into my app Root Toolbox if that's ok?
lukemovement1 said:
Might try add this into my app Root Toolbox if that's ok?
Click to expand...
Click to collapse
Hmm. You can but it's not a good idea. I tried odexing via terminal emulator but it fails.
Basically, this would not work if you try via root toolbox or rather it increases chances of being bricked. However, I noticed you had the scripts needed to flash an update.zip. If that's the case, you'll need to prepare an update.zip in real time and flash it via recovery.
http://forum.xda-developers.com/showthread.php?t=734236 This script moves the apps to SD and odexes. You will have to remove the appsupdate.sh and instead create an update.zip from odexed apps in sdcard. My script on the other hand, directly odexes without any user interaction.
On the other hand, I'd be glad to see this being simplified enough to pressing a button in root tool box. Only the bat script is mine. The rest are from other sources. I guess it shouldn't be a problem as long as you give credit to Paul O Brian from MoDaCo and the person who wrote deoxopt-wrapper.
And, btw, I noticed a small issue in your app. It has NO WARNINGS and NO CONFIRMATIONS! This is a real downer for an app like Root Toolbox which could brick your phone. You should ask for user confirmation whenever an user attempts to do a task that might brick your phone.
I am planning on adding the confirmation dialogs as soon as I can get back to my computer. For the odexing at runtime ill see if it works with app that don't have a GUI. If not ill do some kind of update.zip.
I'm on m6 and want to odex including framework how do I do this?
Sent from my GT540 using XDA App
Danzano said:
I'm on m6 and want to odex including framework how do I do this?
Sent from my GT540 using XDA App
Click to expand...
Click to collapse
Read start post.
And, to odex framework, you need to modify the line which says cd /system/app to cd /system/framework in odex.sh and go through same procedure.
I odexed framework but it made my ROM very unstable.
Hmmm maybe not such a good idea then
Sent from my GT540 using XDA App
this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
starting odexing...it might take a few minutes to finish...
this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
this process connot access the file because it is being used by another process...
your device is now odexed
is this right or is something wrong?
what way did you try and odex the rom?
the quick windows way
have you want to the system/app folder to see if any odex files there?
system/apps all apks no odex
try using script manager and set the script to run on boot to see if it work that way.
Here is what I have done for my personal webtop so far.
Download
To install:
Make a partition on a SDCard, formatted ext3, so that the first partition is FAT, second partition is EXT3.(2GB should be fine, YEMV)
Extract contents of osh2.tar.bz2 to this ext3 partition.
Make a backup of /osh/ubuntu.sh
Overwrite /osh/ubuntu.sh with the one on the root of the SDCard's EXT3 partition.
Backup your /data/home/adas folder.
Remove /data/home/adas, leaving just /data/home.
Reboot the phone.
You will need Linux to extract the tar properly and create the SDCard partitions.
You do not need to be unlocked or have a different kernel, you just need to replace ubuntu.sh, so rooted, temp root, whatever. I created everything from a stock Bell phone. Android 2.3.6. If anything doesn't work, just replace ubuntu.sh with the original file or just remove your sdcard.
Cheers!
edit: changed link
what has been modified:
fuse based smbnetfs installed, stock kernel can access windows shares and play video using motorola hd media center.
open office installed, gimp, some games
lxde set up, theme preconfigured.
No need for dependencies to be fixed or webtop to sd apps run, has zero errors and sudo apt-get dist-upgrade has completed without errors several times so adding extra sources and doing dist-upgrade won't cause errors.
Replaced firefox 7 with 8, rest is Bell webtop.
Been installing and playing with it for a while now, can't recall all the mods.
Yes, you can put the tarball on the phone and extract it to the sdcard that way, you just need to mount the partition. I keep a copy in internal memory to be able to restore when I install/uninstall something I shouldn't.
EDIT:
If you use xarchiver from another webtop to untar the archive, you may need more than 2GB.
Can you put the .tar file on the phone and extract there? I ask because I only have access to Windows machines. Creating the partitions on the sdcard is easy with MiniTool Partition on Windows.
I am can't downloading this file, webserver says: "This file is no longer available."
How has this webtop been modified?
Ramble via webtop:
My approach is to avoid established scripts for fixing dependencies and apps for moving webtop to sd card. Not that I have anything against those, but they were developed using ATT phones and might miss some compatibility with Bell.
One key difference for getting going from scratch is that I installed a standard armel busybox from the busybox site, that avoided a lot of errors when installing debs. Not sure where the busybox comes from in apps2sd but it is not as up to date and results in more errors with missing command line options.
I also didn't want to change/replace the contents of the phone too much so I could easily revert to stock, there is this ICS rumour..
This is what I did:
Starting off I updated the sources.list to be jaunty and just worked through the errors by installing debs manually. lxterminal was installed via deb and tomoyo was disabled by renaming the init and start files. Basically, I did a force install via deb file of some rootfs package contents, coreutils, cpio, dbus, dhcp, gpgv, grep, udev. All references to -mot versions were stripped of the -mot suffix so they could be more easily upgraded. I left the references to ~mot and -motorola in the versions of packages, not sure why, just did. Eventually I got to a place where synaptic was installed and I had no errors. Saved the state in a tarball and kept experimenting with installing things.
I really wanted a home folder elsewhere than /data/home but there are too many hard references to it in webtop for stability, I found a lot in scripts but I suspect they are in binaries as well. You can rbind once in webtop but you need it to have stuff in there during boot, not mix and match configs.
I tried an external hard drive, but there is a fundamental flaw in that logic, they only turn on once you open the lid of the lapdock, so you can't have boot files on it.
I copied the firefox-8.0 from ATT, deleted firefox-7, updated the soft links to point to the 8 version, redid profile.zip to have xda be the home page and adblock installed already, tossed in .xdg-bookmarks to add Network to pcmanfm. I originally had all the home folder stuff in profile.zip but some part of the scripts mess with settings and not everything was carrying over.
So, I did a tarball of my home dir's dot files and put it in /osh2/home/adas so when I do a factory reset and adas is wiped it restores my config. Tip: removing the entire adas folder gives you the same effect for webtop as a factory reset. Reboot and you are back to where you were.
I tried all the window managers, avant/awn anything is annoying when it shifts items left and right when an app opened or closed. I was able to have the stock awn working with a cairo menu, but it still shifted things left and right and was slow. I tried recompiling awn on the phone to get the option to just have launchers but there is this tendency for anything new you compile to require a new libc6. Xfce is cool, menu looked odd though, went with lxde, easy enough to switch if you want. Note: Compiz anything is a waste of time.
I have removed the stock webtop theme and replaced it with clearlooks and murrine window decoration. lxpanel is transparent via manual hack of the config file, the gui for changing things always sets alpha to 0, bug into the prefs app.
I could go on and on, but I like what I have done so far, thought I would pass it along. The main bit for me is not having to install a new kernel or wipe existing partitions, make a lot of phone mods, a pure stock phone can have a custom webtop, just needs to be rooted to copy one file over. Also, I like being able to watch tv shows on my lapdock, worth the price of admission right there for me.
Oh, size is around 1.4GB untarred, so it's a least a 2GB ext3 partition. I have an option in there for using mmcblk1p3 for var if you want to copy var over there formatted with smaller clusters. There are a few flags to control things, if you didn't want to remove your sdcard, touch /osh/no_osh2 and reboot the phone to disable. /osh/var_ownp enables the mounting and use of a third partition on the sdcard dedicated to /var. Use that one carefully, commit to it before installing a lot of things, having a mix and match could break the custom webtop.
Cheers!
Thanks for putting this up, I'd like to give it a try but am having difficulties, possibly cause i'm running Nochatrix (ATT 2.3.6).
When you say 'extract properly' to the EXT3 partition, what command would you use? Should extracting first then copying over work? Because I tried that, and it didn't!
Cheers
It has to be linux, either on the phone or on a pc so that tar -xvf will keep the ownership and file permissions.
VMware Player
CaelanT said:
Can you put the .tar file on the phone and extract there? I ask because I only have access to Windows machines. Creating the partitions on the sdcard is easy with MiniTool Partition on Windows.
Click to expand...
Click to collapse
Download VMware Player and the free copy of linux.. now you can run Linux.. :highfive:
https://my.vmware.com/web/vmware/evalcenter?p=player
NFHimself said:
... so that tar -xvf will keep the ownership and file permissions.
Click to expand...
Click to collapse
That's it, thanks. I was over-complicating things, putting in unnecessary arguments and trying to copy it over using -C. In the end I just copied the tar to the EXT3 and just unpacked it there.
Anyways, it works great! Everything ive quickly tried works nicely, openoffice, synaptic, Gnometris , etc, it's clean and quick, just what I was after.
can make a .zip CWM flashable file???
---------- Post added at 08:37 PM ---------- Previous post was at 08:37 PM ----------
jpinoy said:
Download VMware Player and the free copy of linux.. now you can run Linux.. :highfive:
https://my.vmware.com/web/vmware/evalcenter?p=player
Click to expand...
Click to collapse
where can i find Linux OS??
It work on stock 2.3.4?
It work on stock 2.3.4?
Click to expand...
Click to collapse
I haven't tested it, the webtop is from Bell's 2.3.6, probably not a large difference, but can't say for sure.
Can you make a CWM zip?
Click to expand...
Click to collapse
Yes, I can.
Cheers!
Chimpdaddy;[URL="tel:28700385" said:
28700385[/URL]]That's it, thanks. I was over-complicating things, putting in unnecessary arguments and trying to copy it over using -C. In the end I just copied the tar to the EXT3 and just unpacked it there.
Anyways, it works great! Everything ive quickly tried works nicely, openoffice, synaptic, Gnometris , etc, it's clean and quick, just what I was after.
Click to expand...
Click to collapse
Glad you like it!
Cheers!
I'd love to give this one a try. I'm using Webtop2SD right now. Can someone give a more detailed step-by-step instruction please?
Chimpdaddy;[URL="tel:28700385" said:
28700385[/URL]]That's it, thanks. I was over-complicating things, putting in unnecessary arguments and trying to copy it over using -C. In the end I just copied the tar to the EXT3 and just unpacked it there.
Anyways, it works great! Everything ive quickly tried works nicely, openoffice, synaptic, Gnometris , etc, it's clean and quick, just what I was after.
Click to expand...
Click to collapse
qaplus;[URL="tel:28824484" said:
28824484[/URL]]I'd love to give this one a try. I'm using Webtop2SD right now. Can someone give a more detailed step-by-step instruction please?
Click to expand...
Click to collapse
This does not use webtop2sd, so you would need to uninstall that first as it would likely cause problems.
Not sure how detailed you need instructions.
Cheers!
NFHimself said:
I haven't tested it, the webtop is from Bell's 2.3.6, probably not a large difference, but can't say for sure.
Yes, I can.
Cheers!
Click to expand...
Click to collapse
Thanks, but not seeing any zip on OP .....
I have limited experience with linux. What I got:
1. AT&T Atrix on 2.4.6.
2. Webtop2SD created ext3 partition on SD card.
What I plan to do:
1. Wipe ext3 partiion and copy the SimpleTop tar file to it
2. Log into Webtop ( boot from the Webtop partition from the internal sd card)
3. backup .sh and adas folder
4. untar simpletop in the ext3 partition
5. copy the new .sh file.
Will these steps work? I feel it's bit dangerous to do this on the phone. But how can I do this on a windows computer?
Thanks for any suggestions.
qaplus said:
I have limited experience with linux. What I got:
1. AT&T Atrix on 2.4.6.
2. Webtop2SD created ext3 partition on SD card.
What I plan to do:
1. Wipe ext3 partiion and copy the SimpleTop tar file to it
2. Log into Webtop ( boot from the Webtop partition from the internal sd card)
3. backup .sh and adas folder
4. untar simpletop in the ext3 partition
5. copy the new .sh file.
Will these steps work? I feel it's bit dangerous to do this on the phone. But how can I do this on a windows computer?
Thanks for any suggestions.
Click to expand...
Click to collapse
That is pretty much it. Just remember to be super user and include -p if using tar for backup. Tar -cvpjf /sdcard/ADAS.tar.bz2 . for example. Also, you don't want to be in webtop2sd mode if you are doing this but from a rooted webtop on the the phone itself. Or you could do it all from an adb shell.
Cheers!
Sent from my MB860 using xda premium
NFHimself said:
That is pretty much it. Just remember to be super user and include -p if using tar for backup. Tar -cvpjf /sdcard/ADAS.tar.bz2 . for example. Also, you don't want to be in webtop2sd mode if you are doing this but from a rooted webtop on the the phone itself. Or you could do it all from an adb shell.
Cheers!
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I haven't used adb before. Can you list the commands in adb to install this? Thanks.
qaplus said:
I haven't used adb before. Can you list the commands in adb to install this? Thanks.
Click to expand...
Click to collapse
ADB is just a way to get a remote shell going over usb, so the commands are linux shell commands.
I would do something like this:
(Blank ext3 partition on sdcard, second partition)
adb shell
$ shsu
# mkdir /mnt/asec/osh2
# mount -t ext3 /dev/block/mmcblk1p2 /mnt/asec/osh2
# cd /mnt/asec/osh2
# tar -xvf /sdcard/osh2.tar.bz2
# cp /osh/ubuntu.sh /sdcard/
# cp ubuntu.sh /osh/
# cd /data/home
# tar -cvpjf /sdcard/adas.tar.bz2 .
# rm -r /adas
# sync
# umount /mnt/asec/osh2
# reboot
Cheers!
Here's a quick guide on how I make my ROM's once I have everything I want in my setup.
Step 1: Backup system.img and boot.img.
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
reboot
If system.img gets around 3.4gb or higher it needs to under 2.1gb zipped to be flashable. If its not your going to have to zero out the free space so it will compress under 2.1gb's. If this is the case to go step 2.
Step 2: Zerofree the image by installing zerofree. Unzip the file attached here in Ubuntu 14+ and install it.
I created a folder on my desktop and called it zerofree and put the system.img inside it. Run this code:
cd Desktop
cd zerofree
zerofree -v system.img
Click to expand...
Click to collapse
It will zero out the system.img. Though its still might be the same size, don't worry as when you put it back in the zip it will compress way down.
Step 3: Add to ROM. Now add the system.img and boot.img to ROM-Flash.zip attached and your ready to go!
MicroMod777 said:
Here's a quick guide on how I make my ROM's once I have everything I want in my setup.
Step 1: Backup system.img and boot.img.
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
reboot
System.img will be around 3.4gb and once its put in a zip to flash needs to be under 2.1gb. If its not your going to have to zero out the free space so it will compress under 2.1gb's. If this is the case to go step 2.
Step 2: Zerofree the image by installing zerofree. Unzip the file attached here in Ubuntu 14+ and install it.
I created a folder on my desktop and called it zerofree and put the system.img inside it. Run this code:
It will zero out the system.img. Though its still might be the same size, don't worry as when you put it back in the zip it will compress way down.
Step 3: Add to ROM. Now add the system.img and boot.img to ROM-Flash.zip attached and your ready to go!
Click to expand...
Click to collapse
I think I already know the answer to this, but I want to be sure. Does this method make a flashable copy of just the ROM, not any personal stuff or apps you install from the store? I'd like to do this to flash my copy of a crdroid on another LG G2, but I don't want my personal stuff on it. I would just like it to be setup the way I have it now because I have removed a lot of things I don't need and made some changes to a few of the stock apps. It would be nice to be able to port those changes to another phone quickly and easily.
flyinjoe13 said:
I think I already know the answer to this, but I want to be sure. Does this method make a flashable copy of just the ROM, not any personal stuff or apps you install from the store? I'd like to do this to flash my copy of a crdroid on another LG G2, but I don't want my personal stuff on it. I would just like it to be setup the way I have it now because I have removed a lot of things I don't need and made some changes to a few of the stock apps. It would be nice to be able to port those changes to another phone quickly and easily.
Click to expand...
Click to collapse
This basically only saves whatever changes you make the system. For example, lets say you debloat a rom using Titanium backup removing system apps. Those changes will be made to the system.img.
MicroMod777 said:
This basically only saves whatever changes you make the system. For example, lets say you debloat a rom using Titanium backup removing system apps. Those changes will be made to the system.img.
Click to expand...
Click to collapse
That's what I thought and that's what I want. Thanks. Going to give this a shot right now.
Where does it place the two .img files when it's done? I can't find them on my sdcard or my computer. Nevermind. I tried this on another phone first just so I didn't screw up my daily phone in case I did something wrong. They were put on the internal storage instead of the sdcard.