Input Script into Startup - Nexus One Q&A, Help & Troubleshooting

So I recently came across a script at Modaco Forums that allows me to light up the capacitive buttons while using the Desire Port. I was wondering if there was a way for me to implement that into the ROM without having to go to GScript everytime. I have Dsxdsi's ROM Kitchen installed so I'm thinking I could use that. I just don't know where the file would go.
I attached the file that contains the script. And this is the thread I got it from.
http://android.modaco.com/content/g...ble-capacitive-buttons-for-nexus-desire-roms/

add a shortcut to your homescreen directly to the script, voila.
though it would be nice to have this on bootup..

That's what I mean.

/system/etc/init.d/
Rename the script to have numbers in the beginning, or just link it in 20userinit.

Depending on what 20userinit you've got (system/etc/init.d/) some look to the sd card for a script called userinit.sh and executes it if it exists.
Load up userinit.sh on your sd card with whatever you like (using #!/system/bin.sh) and go wild. It's a great way to set everything up that you need... especially after you've just installed a new build (mine restores all my settings before I even get to the home screen - bliss). It runs in a root context so if you copy or create files or directories you'll need to chmod as necessary.

add a shortcut to your homescreen directly to the script, voila
Click to expand...
Click to collapse
Out of curiousity, how do you do that with a script? I use GScript but it doesn't work right with some of my scripts and would love to hear of any alternatives.
-------------------------------------
Sent from a device of some sort.

Related

creating personalized roms

my question is this, say for example I have my phone setup just as I like with the theme of my choosing, htc music app instead of the stock android app in the cyanogen mod. i would like to be able to create a rom from this setup that I could then just load on my phone as oppsed to loading a cm mod, then installing music player, then installing the theme. before the flaming begins, i tried the search to no avail. i am aware of how to sign the zip and all of that. just a point in the right direction would be MUCH appreciated.
Its something I would like to be able to do as well. According to Haykuros twitter hes going to be making a video about android rom cooking soon so that should help
jholt0130 said:
my question is this, say for example I have my phone setup just as I like with the theme of my choosing, htc music app instead of the stock android app in the cyanogen mod. i would like to be able to create a rom from this setup that I could then just load on my phone as oppsed to loading a cm mod, then installing music player, then installing the theme. before the flaming begins, i tried the search to no avail. i am aware of how to sign the zip and all of that. just a point in the right direction would be MUCH appreciated.
Click to expand...
Click to collapse
This should've gone in the Q&A section. Will probably get locked soon.
But in response to your question, I guess you could grab the CM rom, then grab the theme you use and overwrite the files in the rom, and then overwrite the music app with the HTC music. Resign and you got your update.zip customized how you want it.
xidominicanoix said:
This should've gone in the Q&A section. Will probably get locked soon.
But in response to your question, I guess you could grab the CM rom, then grab the theme you use and overwrite the files in the rom, and then overwrite the music app with the HTC music. Resign and you got your update.zip customized how you want it.
Click to expand...
Click to collapse
Thanks for the help and my apologies for the wrong section
how do you resign it?
joey3002 said:
how do you resign it?
Click to expand...
Click to collapse
by searching.
Stericson said:
Automatic version!
Do not use this to sign APK files in Vista or windows 7! It will cause your theme to loop phones when placed on a device. Only use this to sign update files if your using those O/S's
Note, this will not work if your SDK or the path that you place this in has any spaces in the dir name!
An Example of this is c:\users\Nikki and Stephen\sdk\tools
Try to put the SDK and the contents of the zip in a dir where the names are all together and not like the one above.
I have made a batch file that will automate the entire process of setting up to use the signing tool made by JF. This batch file will set the CLASSPATH, set the PATH, install the registries, and will even allow you to sign files manually if you wish. I plan on building onto this batch file to include other things. However, for the moment, it will only include what you see here.
In order to use this you should have downloaded the sdk already. Simply extract all of the files into the tools dir of your sdk, and run autosign.bat follow the instructions and go through the options one by one, starting with 1 working through 4. You can however, put the contents of this zip anywhere on your computer and it will work. It is just better to put them into the tools dir of your SDK. Especially for the consideration of future versions.
Autosign .zip: http://www.fightforthepits.com/Androidstuff/signing.zip
Want to set up the signing tool manually?
Here is the link for the signing tool: Http://www.FightForthePits.com/testsign(2).zip
Before using this you need to know how to set this up:
Now you will need to add the tools dir of your sdk to the environment variable CLASSPATH.
FOR XP:
Right click on My Computer click properties, then choose the tab that says advanced.
Click the button that says environmental variables.
Go to system variables find the one that says CLASSPATH
double click it
go to the end of variable value.
There should be a semicolon ; at the end, type in the path to the testsign.jar located in the tools directory of your SDK
for example the path to my testsign.jar was c:\sdk\android-sdk-windows-1.0_r1\tools\testsign.jar
If CLASSPATH is not in your system variables then create it.
Secondly, Find the system variable called PATH and add to the end of it, the full path to your sdk directory.
For example, mine was c:\sdk\android-sdk-windows-1.0_r2\tools
FOR VISTA:
Open a cmd prompt.
Replace THEEXACTPATHTO-TESTSIGN with the path to the dir that holds the file testsign.jar.
Type:
echo %CLASSPATH%
If it is returns %CLASSPATH%
Type the following:
set CLASSPATH=THEXACTPATHTO-TESTSIGN\testsign.jar
If it comes back with something else then
Type the following:
set CLASSPATH=%CLASSPATH%;.;THEXACTPATHTO-TESTSIGN\testsign.jar
For Example, when I type this it looks like:
set CLASSPATH=%CLASSPATH%;.;c:\Android\SDK\tools\tests ign.jar
To set the PATH
Replace THEEXACTPATHTO-SDK with the path to the tools dir of your SDK.
Now type:
set PATH=%PATH%;.;THEXACTPATHTO-SDK\tools
For example, when I type this out it looks like this:
path-%PATH%;.;c:\Android\SDK\tools
Now through doing this you have done two things, first off you have made the resigning process extremely easy, secondly you will not have to cd to the tools dir of the sdk to use adb or any other tool in the sdk.
Signing the Files:
Now right click the reg file that you extracted and choose to install it, or merge.
Now, right click an apk, do you see an option that says ResignApk? That's how you will resign your .apks and .zips.
When you choose it a cmd window should open for a few seconds and then close. the file you signed will be overwritten with the new resigned file.
If you find the right click menu not working for some reason you can type the following in cmd to sign your files: java testsign whateverfiletosign
Click to expand...
Click to collapse
.apk's not showing up after flash in resigned .zip
Ok, so I've created a ROM to my liking. All the .apk's I normally use and got rid of the ones I don't. My problem is after I customized the ROM and flashed it none of the .apk's I added showed up. The only ones that showed up were the paid apps. I never opened the .apk's and made changes. I assume I don't need to change them to .zip resign and back to apk. Do I? I am using Windows 7 though and am able to resign no problem. Thanks to anyone who replies.

[Android] Dr. NoMoRootfs! or How I learned to stop worrying and love the extra space

Everything needs to go in /sdcard/andboot
FILES YOU NEED:
the nbh flashed to your phone
an sd card with the andboot folder at the top level
an androidinstall.tar file plopped into the andboot folder
thats it
then just hold down volume up or dpad center or the middle of your touchscreen when booting and go through the menu to choose where to put things and then install the system. (for those without a dpad, pretend the touchscreen is a giant dpad)
if you're doing it with haret, extract basefiles to your sd, plop the androidinstall.tar into the same folder, and boot, hold down volume up (camera on kaiser/polaris) just like the nand people (but don't pick nand to store the files, it won't work)
---------
all the files
basefiles for the haret folks out there
Grab the nbh files for your device. Only difference between eclair and non-eclair is that eclair is set up to use the newer hw3d driver, non-eclair is set to use the older one (for donut/cupcake)
These do not use rootfs. They remove it completely and free up that extra space in your nand for a bigger, cleaner system.
They also have my new menu-based installer! Yay! Just hold-down volume-up or dpad center or the middle of your touchscreen
THIS WON'T WORK WITH ANY OF THE OLDER SYSTEMS! THE SYSTEM MUST INCORPORATE THE APPROPRIATE FILES FROM ROOTFS (and the rom cooks will let you know when theirs is ready)
The first system to use this is based on eclair 2.1 with working sleep and audio
Here's my tattoo system for this method
FYI Craig & I spent a lot of time on these!!!
How to create a build
How to make your build work with this
So it actually isn't that hard.
Extract your sqsh to a folder somewhere, so you have, say /android/system
Mount/extract whichever rootfs worked best with your system somewhere else, say /android/rootfs
Code:
cp -a /android/rootfs/init.etc/* /android/system/etc
cp /android/rootfs/lib/donut/* /android/system/lib
cp /android/rootfs/lib/modules/* /android/system/lib/modules
cp /android/rootfs/lib/hw/* /android/system/lib/hw
cp /android/rootfs/init.cfg/init.donut.rc /android/system/sysinit.rc
You'll need to modify the sysinit.rc a bit, as in the rootfs some things are commented out that shouldn't be, and it references a few things in /bin or /etc that aren't there anymore.
Also, don't forget to uncomment the line near the top of sysinit.rc that creates a symlink from /system/etc to /etc
Once you are done, just do this to create the installer:
Code:
cd /android
tar cvf androidinstall.tar system
Soon, I may upload some packs for making the process easier, with updated sysinit.rc's for each system type. If I have time, we'll see...
Note, you can update the contents of the .tar file from windows/izarc/winrar/etc and it'll still work. you don't need to keep messing about with linux anymore if you don't want to
How to update things
How to create an update pack
Since not everyone gets things right the first time, and we keep getting updates, the rootfs made it easy to install updates without downloading the whole system again.
Well now anyone can create an update pack
just create a tar file called androidupdate.tar, make sure it has everything in a /system folder with whatever files you want, drop it into /sdcard/andboot and reboot holding down volume-up (camera on kaiser/polaris). Choose the update option and you should be good to go.
If things get wonky when you try to boot up, give the fix permissions option a shot in the installer, if it still fails, try wiping the dalvik cache, that can fix things up too.
About the installer
I ripped it off from here, but put about 6 or 7 solid hours into getting it to fit and react with the keys/screen
May be new
rootfs
may be new
better eclair support
---
with android development this fast for "yomama so old" phone, who knows what future holds?
sshark said:
May be new
rootfs
may be new
better eclair support
---
with android development this fast for "yomama so old" phone, who knows what future holds?
Click to expand...
Click to collapse
whats a rootfs hahaha
Might be something called "Code Name Ginger"....or our tame racing car driver, we call the Stig.
nabicat said:
Might be something called "Code Name Ginger"....or our tame racing car driver, we call the Stig.
Click to expand...
Click to collapse
what the..... that was random
Holy cow.. like there's nothing even in this thread and it's already filling up..
I think I know what it is..
Vilord ported Dalvik from 2.5 which now includes native support for HW accel for MSM7500..
jesus.
Do we still need to have three partitions on the card? Or would one FAT32 partition be sufficient?
@vilord:
is everything needed for the rootfsless nbh in the git? I would like to test this with ´my kaiser
This works for Polaris? Really thanks!
the bootenv git should have everything needed for this. I haven't tested on my polaris yet, but it should "just work" on polaris and kaiser as long as martin's method to drop the active key into /proc works on all hardware.
What happens to the .conf files?
What about /media ?
Thanks for all of your efforts
conf files are no longer used from the sd card.
If the cook put things in the right places, there should be a /system/etc/userinit.conf that gets parsed during android boot, but it is up to the cook to not screw that up.
This way is a lot cleaner, but it does a LOT less handholding for lazy cooks.
the upside is that it is *very* easy for anybody to fix a broken androidinstall by just piecing together what needs to change into an androidupdate.tar
/media is still used if it is on your SD card, but there's enough space and things are fast enough that media files should be included in /system now
This is a HUGE development for rom devs.
I will be honest in saying I've been having a hard time not hitting the 90MB cap with my next Warm Donut release.
Infact, I spent 4 hours yesterday de-odexing and compressing the classes.dex back into the jars and apks to save space.
With this new method this gives us ALOT more space. I applaud you for doing this. It breaks alot of the current builds but at the same time gives us a ton more flexibility for future.
And what I really like from this is it removes the confusion and headaches on configuration, giving the power to the ROM dev to include the necessary settings.
Question though. Different phones (Vogue, Polaris, Kaiser) may require different configurations. In the past it was a simple "just use this conf with this phone"
Thanks again
so when running from haret - getting an error about looking for a system file, I have all the files in andboot folder, any ideas on what I'm missing.
Know what would be really nice? In the setup, the ability to change LCD_Density and resolution.
This would eliminate the confusion users may have in editing the build.prop and rom files to change these values.
I guess the ROM devs could distribute separate files/tars for each res/density but that gets redundant if you know what I mean.
I'm using haret, but I dont see any option to choose to install not to nand, i get into the installer and it says install system so i click that but then it just goes through installation and fails. How do i choose to install to sd card?

Block OTA (Beginners guide?)

adb shell, sqllite, build prop...Any other non-tech major people around here a little lost?
I'm rooted. I don't want the new update. I can follow directions but would be more comfortable if some basic instruction were written. Treat me like I'm 10.
It looks like the best way to do this is as follows:
"From this thread:
http://forum.xda-developers.com/showthread.php?t=874871
Attached is a working sqlite3 binary.
Copy it to /system/bin
(I transfered it to my SD, then used rootexplorer (mount R/W) to copy into /system/bin))
you will now be able to edit sqlite databases on the nook itself.
--------------------------------------------------------------------------------
Attached Files sqlite3.7z (11.9 KB, 56 views)
--------------------------------------------------------------------------------
In your terminal:
$ adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
$ sqlite3 devicemanager.db
sqlite> update registry set value='manual' where name='com.bn.device.fota.mode';
sqlite> .q
$ adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
$ adb reboot
"
Do I unzip the attached binary and paste that into the location or the .zip as a whole? What do I use as a terminal?
I've been flashing my DROID since day one but the NC development circle has been far from entry level user-friendly. Any help would be appreciated.
you can do it on windows too.
1) pull/get/copy the.db file from your phone to your pc
2) update the database file using sqlitebrowser. I.e run the sql command "update ......". Close sqlitebrowser.
3)push/put/copy the updated .db file to the same location overwriting the original.
britoso said:
you can do it on windows too.
1) pull/get/copy the.db file from your phone to your pc
2) update the database file using sqlitebrowser. I.e run the sql command "update ......". Close sqlitebrowser.
3)push/put/copy the updated .db file to the same location overwriting the original.
Click to expand...
Click to collapse
Progress. However...
I got SQLite on my PC. I found the devicemanager file on my NC, pasted it to my SD card for transfer over to my PC for editing. I trasnferred the file over to my PC for editing. I open SQLite but have no idea how to use it.
I just did this today using sqlite editor only!!! Its a GUI so it real simple to use.
1.Install the apk
2.reboot
3.go to extras and launch sqlite editor
4.allow it, give it the permision it needs
5.look for DeviceManagerService
6.click on devicemanager.db
7.click on registry
8.look for _id 7, name>>>> "com.bn.device.fota.mode"
9.scroll to the right and click and hold value field "auto", until a little pop up shows and select edit field
10. Change the value from auto to manual
11. Save
Done!!!
If you need the apk here is a link I just made
?d=LTSQDZ65 for megaupload (sure u guys can piece it together!)
Let me know if it helped anyone!
Yes, we totally need another thread on this. I must note that pushing the build.prop in my thread and my two Nook Colors have not updated. Dunno about this method or others. Caveat emptor!
This is exactly what I was looking for. Thank you. Very simple.
Sent from my NC using XDA App
Thanks for breaking it down for us, nookme.
Do we need to do this if we are operating from an SD bootable Froyo or CM7 ROM?
tablo said:
Thanks for breaking it down for us, nookme.
Do we need to do this if we are operating from an SD bootable Froyo or CM7 ROM?
Click to expand...
Click to collapse
In theory it should work for both, whether its a soft root mod or simply a bootable sd card that emulates froyo... It's a matter of just having root access and changing a registry setting on the device itself. Hope this shines some light! happy rooting ppl
Not noobie enough for me, sigh
So, if I have followed these directions from an earlier post have I messed something up? Not blocked updates at all? I don't understand the directions in this thread. What happens if I don't block the update? There must be a lot of people like me who had the technical skills to manage the root process but don't understand all of your coded instructions. I read in another thread that I should do a Titanium backup. How does that help after an update? Will market aps that have already been downloaded still work? Will everything revert to stock? Could someone explain what we should expect? Thanks!
To disable OTA (over the air) updates:
Change the name of this file: otacerts.zip to anything else
To do this, get root explorer ($3) from the market
Run root explorer
Go to etc/security/otacerts.zip
Hit the little mount button near the top to change r/w to r/o
Rename the file otacerts.zip to otacerts.zip_DISABLED_OTA_UPDATES
Hit the little mount button again to change r/o back to r/w
Droiddict said:
So, if I have followed these directions from an earlier post have I messed something up? Not blocked updates at all? I don't understand the directions in this thread. What happens if I don't block the update? There must be a lot of people like me who had the technical skills to manage the root process but don't understand all of your coded instructions. I read in another thread that I should do a Titanium backup. How does that help after an update? Will market aps that have already been downloaded still work? Will everything revert to stock? Could someone explain what we should expect? Thanks!
To disable OTA (over the air) updates:
Change the name of this file: otacerts.zip to anything else
To do this, get root explorer ($3) from the market
Run root explorer
Go to etc/security/otacerts.zip
Hit the little mount button near the top to change r/w to r/o
Rename the file otacerts.zip to otacerts.zip_DISABLED_OTA_UPDATES
Hit the little mount button again to change r/o back to r/w
Click to expand...
Click to collapse
If you read this >> http://forum.xda-developers.com/showthread.php?t=1007551
you will see that the sqlite method is used by many and is the simplest way too, again this is a GUI, so no shell command line... How can this be difficult??
Just follow my steps... it works
I have had nothing but problems with my rooted NOOK Color due to B&N auto updates. I followed your instructions and now I hope my problems are resolved and my NOOK Color will never update again.
Thank you

[GUIDE] Create your own Soft-MODs

USING DSIXDA's KITCHEN TO CREATE YOUR OWN SOFT-MODs
(THIS IS MY FIRST BIG TUTORIAL, SO PLEASE CO-OPERATE AND HELP ME MAKING THIS GUIDE BETTER!!)
DsiXDA has created an excellent Kitchen for 'cooking' custom ROMs. So first THANKS goes to DsiXDA.
READ THIS BEFORE PROCEEDING:
Click to expand...
Click to collapse
For Kitchen to get working you need a Linux environment. My choice is go for Ubuntu 10.04 / 10.10 (I won't recommend 11.xx as Unity spoils the 'Cooking' experience). You should have a little bit of experience with Ubuntu. You can do it on Windows too. Install Ubuntu inside VirtualBox. I won't recommend using cygwin as it may reduce the performance.
Click to expand...
Click to collapse
GIVE CREDITS TO THE ORIGINAL DEVELOPER
I. Setup the Kitchen:
Download DsiXDA's Kitchen at https://github.com/dsixda/Android-Kitchen/archives/master. Download the 0.179 version
Get an 'original' ROM (not soft-modded). The ROM that I used in this tutorial is Pebe's CyanogenMod 7
Get JDK. It's necessary. Execute the following command in Terminal:
sudo apt-get install openjdk-7-jdk
When asked for password, enter the one which you use for logging in.
For 64-bit system, you need the ia32-libs ( sudo apt-get install ia32-libs )
Extract the contents of the dsiXDA's kitchen to a folder, say kitchen, in your Home folder (for convenience). Just inside the kitchen folder there should be the ./menu file
Open Terminal. Browse to your kitchen directory
cd ./kitchen
source ./menu
It should open up the Kitchen Menu
This is the basic setup of your Kitchen. Now move up to the next big step.
II. Actual ROM:
Copy the ROM (in my case, it is cm7_v2.zip (pebe's CM7)) and paste it in the original_update folder
Execute Kitchen (Step 5 from I). Select option '1. Setup working folder from ROM'. Another menu appears, hit ENTER. It'll show up the available ROMs list. It should display at least one ROM. In my case it was "(1) cm7_v2.zip". Enter selection number: 1. Hit ENTER. It'll prompt for changing the name, leave it, no need. Hit ENTER. It'll start extracting the ROM. In my case, it found the updater-script. It'll ask to convert the script into update-script. We want update-script at the moment, so just hit ENTER. It should say 'Finished setting the working folder!'. Hit ENTER. You'll be back to Menu.
The Menu shows various options like 'Adding Root permissions, installing busybox, etc'. You can play with them. As most of the ROMs have Root and Busybox installed, we don't need any of these features.
Now comes a bit advanced part. Select ADVANCED OPTIONS. There are various options like Deodex files, add Nano text editor, signing APKs, etc. I'll explain each of them:
Deodex: Merges ODEX and APK together. However, it's applicable for ODEXed ROMS (mostly Stock 2.1) only. Neither of GB and FroYo versions are ODEXed. So you can skip this step.
Add task killer tweak: It's a good alternative to Supercharger script. Only thing is, it isn't as versatile as Supercharger script. Leave this if you don't know anything about Task killer values like FOREGROUND APP, BACKGROUND APP, etc
Add data/app functionality: Suppose you've come across a situation that the system size reaches almost 150 MB (standard for GT540) and still you want to add some more apps, then this tweak is for you. It adds the /data/app folder. You can place apps in this folder. These apps will be directlty installed in the /data partition thus eliminating the 150MB limit.
Add Bash: Adds command-line completion in Terminal commands. Install if you want. Not needed.
Add Apps2SD: This is much primitive type of Apps2SD in which you have to create an ext partition on your SD card. Not recommended. Link2SD (app) is much better.
Add busybox run-parts: This tweak is most important one. I enables the startup scripts option, that means, scripts placed in /etc/init.d folder will get executed during the booting process. Recommended for Stock and AOSP ROMs only.
Add custom boot animation: If you want to add a custom boot animation to your ROM, then you need this. Select this option. It'll ask you to proceed, hit ENTER. A folder /data/local will be created inside the WORKING_xxxxxxx_xxxxxxx folder. Place your bootanimation.zip in that folder. Google some nice boot animations or if you want to create your own boot animations, Despotovski brothers had made a 'Boot Animation maker', check it here http://forum.xda-developers.com/showthread.php?t=1234611
Rest all tweaks are not required for now
III. Something's Cooking!
There will be a folder named something like WORKING_xxxxx_xxxxxxxx in your kitchen folder. Open it up. It contains the actual system, boot.img file, data directory etc.
The best feature of DsiXDA is that you can easily 'browse' the system.
Open the system folder. Here you can see the apps, etc, lib, usr, etc folders.
Adding / Removing Apps: Open the apps folder. You'll see APKs of all the system apps. Try removing some apps. You can remove Dev tools, pre-installed CM themes or any other app. Add your own apps. Copy-paste your apps here. If their filenames have spaces in them (like Root Explorer.apk) remove these spaces (like RootExplorer.apk). You can also use the /data folder for adding more apps.
Adding some other stuff: The /etc folder has a lot of cool stuff too. The apns-conf.xml file contains the APNs. System can auto-detect the APN according to your carrier. I got an apns-conf.xml file which contains a huge list of APNs. Just replace the existing file.
Adding Fonts: Pick your favorite font (I like Ubuntu). Grab the .ttf file of that font. Open /fonts folder. Remove the existing DroidSans.ttf file. Copy-paste your font file in it and rename it to DroidSans.ttf.
IV. Final Steps:
Open the kitchen menu. Advanced Options → Sign all APKs
Back to main menu. '9. Check update-script for errors'.
'6. Zipalign all APKs'
'99. Build ROM'. If it shows warning regarding BOOT-EXTRACTED folder exists, select y (remove BOOT-EXTRACTED).
Select a build option → 1. Interactive Mode
Would you like to Zipalign → n (we already did that before)
It'll start making update.zip.
Add updater-script to your ROM → y (We want compatibility with ClockworkMod)
Proceed with the change → y
Sign your ROM → y
Change the name → n
Once you're back to main menu, select Exit (x)
Your ROM is located in OUTPUT_ZIP folder (It'll be a zip file)
Copy this zip file on your SD card. Reboot into Recovery. Select 'Install zip from SD card', select the ZIP file.
Reboot. See if everything works properly.
I KNOW THERE MIGHT BE ZILLIONS OF ERRORS IN THIS GUIDE. IF YOU'RE STUCK AT SOME POINT OR CANNOT UNDERSTAND SOMETHING, TELL ME. I'LL TRY TO MAKE THIS GUIDE MORE EASIER TO UNDERSTAND.
THIS IS A BASIC SOFT-MODDING GUIDE. I'M DOING SOME INVESTIGATION REGARDING THEMING AND BUILD.PROP TWEAKS. I'LL BE ADDING THESE SECTIONS LATER.
WOW nice work making this TUT!!
Nice Work!
thanks!!
gonna try this out sometime
There is a search feature guys this was posted about like half a year ago
I tried the kitchen its not that great all you can do is zipalign change some options and re package
TBH androidboss you probably could do more using terminal and root explorer
Sent from my tf101 using xda premium 1.54Ghz
Guys! Before Soft-Modding please ask the Devs first. They worked and took up free time for those roms and they would like a thanks.
Danzano said:
There is a search feature guys this was posted about like half a year ago
I tried the kitchen its not that great all you can do is zipalign change some options and re package
TBH androidboss you probably could do more using terminal and root explorer
Sent from my tf101 using xda premium 1.54Ghz
Click to expand...
Click to collapse
really i should try one day!
with credits and thanks!!
Algud if you need tips or want a hand customizn give me a shout hell if you wana use enigma and just cretic it to you're liking be my guest
Sent from my tf101 using xda premium 1.54Ghz
Danzano said:
Algud if you need tips or want a hand customizn give me a shout hell if you wana use enigma and just cretic it to you're liking be my guest
Sent from my tf101 using xda premium 1.54Ghz
Click to expand...
Click to collapse
yeah thanx bro!!
i will try and make one during this weekend
once i get my phone fixed..
i will pm you if i need help with something about the
soft-mod!!
All good
Sent from my tf101 using xda premium 1.54Ghz
Danzano said:
All good
Sent from my tf101 using xda premium 1.54Ghz
Click to expand...
Click to collapse
pm' ed u!!
soz its a bit long!
I'll be writing the "Theming using UOT Kitchen" tutorial tonight
tejasdj12 said:
I'll be writing the "Theming using UOT Kitchen" tutorial tonight
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=18934516#post18934516
you can base on this if u want

[WEBTOP][Bell][Mod] SimpleTop 07/05/2012

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!

Categories

Resources