Last week, my colleagues and I received free HTC Magic/Sapphire/ION devices from Google for attending their developer event in Yokohama. I'm currently using it on the NTT DoCoMo network, and my colleague is using it with SoftBank here in Japan. The devices are very nice
I noticed that the hboot displayed on my device is 1.33.3005. Has anyone seen this version before? From reading the posts here, it seems newer than what others have. It seems quite locked down, for example I cannot flash unsigned roms or replace the splash image.
I successfully loaded Haykuro's latest signed HTC-flavor rom on the device, and it runs quite well (he did a nice job!). However, I was wondering if there is any other SPL available I could flash on the device to try unsigned roms or to try flashing the partitions directly?
Also, if anyone is interested in getting Japanese keyboard support on their device, I may be able to extract the Japanese IME keyboard from here
Best Regards,
J. Maurice
EDIT: Entire Japan OS nandroid dump
Article: Installing Japanese IME on Android
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Its the newest SPL we´ve seen here on XDA....
Hi, can you upload your rom so anyone who interest might help you.
Let me double-check. The correct way to dump my ROM as I guess from reading these forums is:
1) Use fastboot to load recovery.img
2) Run a nandroid backup - I assume this will copy OS as well as data?
3) Make an archives of the files saved in /tmp/nandroid/
Is this correct?
Here is one of the devices running the HTC image:
And here is the original OS that came with the devices, I assume made by Google:
Yes, steps are right.
jmaurice said:
Hello everyone, this is my first post on these forums.
Last week, my colleagues and I received free HTC Magic devices aka Sapphire aka ION from Google for attending their developer event in Yokohama. I am using it on the NTT DoCoMo network, and my colleague is using it with SoftBank here in Japan. The devices are very nice
I noticed that the hboot displayed on my device is 1.33.3005. Has anyone seen this version before? From reading the posts here, it seems newer than what others have. It seems quite locked down, for example I cannot flash unsigned roms or replace the splash image.
I successfully loaded Haykuro's latest signed HTC-flavor rom on the device, and it runs quite well (he did a nice job!). However, I was wondering if there is any other SPL available I could flash on the device to try unsigned roms or to try flashing the partitions directly?
Also, if anyone is interested in getting Japanese keyboard support on their device, the backup I made of my original ROM with Japanese IME keyboard may be useful to extract it from
Best Regards,
J. Maurice
Click to expand...
Click to collapse
Japanese IME keyboard
I want it~~also the Japanese lang pack
Okay, give me a few days to get it copied it off and uploaded somewhere.
A little busy now that the work week has started.
EDIT: Download it here.
what's Haykuro's latest signed HTC-flavor rom ???
wassss said:
what's Haykuro's latest signed HTC-flavor rom ???
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=3835311&postcount=1
jmaurice said:
http://forum.xda-developers.com/showpost.php?p=3835311&postcount=1
Click to expand...
Click to collapse
ah ok, sorry
I took a brand new HTC Magic out of the box from Google Japan and did a nandroid dump. It's never even been turned on, so it should be a good image of the original OS for Japan.
Download it here. Please let me know if you extract anything useful from this and post in this thread.
I will also look at extracting the Japanese IME keyboard from this later, which I know many people besides myself are interested in
jmaurice said:
Okay, give me a few days to get it copied it off and uploaded somewhere.
A little busy now that the work week has started.
Click to expand...
Click to collapse
Thank you ~~
jmaurice said:
I took a brand new HTC Magic out of the box from Google Japan and did a nandroid dump. It's never even been turned on, so it should be a good image of the original OS for Japan.
Download it here. Please let me know if you extract anything useful from this and post in this thread.
I will also look at extracting the Japanese IME keyboard from this later, which I know many people besides myself are interested in
Click to expand...
Click to collapse
how can i install this?!?
if it's a nandroid backup i cannot use the NORMAL method of the update.zip to the sd card right?!?
iWnnIME working as a standalone
This method is now obsolete, grab the update.zip made by jashsu on page 3.
After some digging around, I was able to get iWnnIME working on my G1. Wasn't sure where to post it, but figured since I got it from jmaurice's dump, this would be the best place. I would think the steps would be identical on a Sapphire, but I don't have one so there's no way for me to tell. Report back if it works! I'll do my best to help troubleshoot but I'm not an expert by any stretch so just keep that in mind. This is pretty much one of those "Here's how I did it, it works for me, and if it doesn't for you, then, well.. I dunno."
Just copypasting with some minor edits from my blog:
Things you will need:
1. The ROM dump, graciously uploaded by jmaurice
2. A computer running some flavor of *nix (OSX + xcode kit works too, it's what I used)
3. unyaffs
4. The android dev environment, namely adb. Although this probably isn't *required*; you could potentially do everything after unyaffs-ing by copying the requisite files to the sd card and copying via the terminal emulator.
Some notes before getting started:
-A problem you may run into is lack of space on the /system partition. I'm currently using one of the Rogers Dream ROMs and I had to delete the HTC_CIME.apk to free up enough space to copy all the files over (there are quite a few). Depending on which version of Android you are running, this may not be a problem at all, or it may be a major obstacle; YMMV. Deleting HTC_CIME is as easy as rm -r HTC_CIME.apk from the shell and rebooting. No ill side effects other than not being able to use that particular IME, but I don't have a need for Chinese input so it was a non-issue.
-Didn't need to fix any permissions, just copied and it worked
-I'm writing this mostly from memory and it's a bunch of pseudocode, definitely not a "step-by-step" guide. If you don't know what you are doing then you should probably stop now.
-If you mess up your phone I am not responsible, proceed at your own risk. You know the drill.
Now the walkthrough:
1. Get all of the above things, and compile unyaffs for your box with gcc and all that jazz
2. unyaffs data.img and system.img
3. There are only 2 things we need from data.img. First is the jp.co.omronsoft.iwnnime folder in /data/data, copy it to the same location on your phone (make sure to preserve the subfolder structure). There is also a [email protected]@[email protected] in the dalvik-cache folder, copy that over too.
4. Now for the fun part with the multitude of files needed from system.img. I'm a total nub when it comes to this stuff, so not all of these may be required. All I know is that they are all referenced by entries in some of the lib files so for completeness I copied them all over. It may be possible to omit some to save space but it's beyond my ability to tell. First, the files in the /system/lib folder:
libiwnn.so
lib_dic.conf.so
lib_dic_e.conf.so
libEnjcon.so
libEnjemailuri.so
libEnjlearn.so
libEnjlearnL.so
libEnjlearnM.so
libEnjrel.so
libEnjyomi.so
libkaomoji_kihon.so
libkaomoji_tyukyu.so
libnjaddress.so
libnjcon.so
libnjemoji.so
libnjexyomi.so
libnjexyomi_new.so
libnjexyomi_re.so
libnjfzk.so
libnjname.so
libnjtan.so
libnjubase1.so
libnjubase2.so
Copy these to /system/lib
5. Now take DroidSansJapanese.ttf from /system/fonts and copy that over to the same folder on your phone.
6. And finally, copy over iWnnIME.apk to your sd card and run it to install it.
7. Go to your locale settings and you should have a nice new iWnnIME to use.
The only limitation I have experienced with the IME is that it doesn't seem to play too well in landscape mode. It works, but sometimes it gets a little confused. This appears to be limitation of the software though, and not a result of using it on the Dream platform. Even romaji input works a charm using the hardware keyboard on the G1, although it suffers from some of the same issues described above.
Credit goes out to jmaurice for providing the ROM dump, and to the great community at xda for the wealth of info that allowed even a nub like me to be able to pull something like this off.
Feel free to skip over this rant unless you are planning on selling this
/rant on
And last but not least, it has come to my attention that there are certain companies out there that have been and will continue to make commercial profits off of the hard work done by the fine folks here on xda, particularly in the realm of selling mobiles in the United States that have been reflashed with Japanese firmwares or other localized apps. What I've done isn't anything amazing compared to what people like Haykuro have done, but I can say with confidence that there are a few companies out there that I can think of off the top of my head that will certainly jump on this and start pawning it off to less savvy customers as their own work. It might not be much, but as a contributor I'm proud of my work, and all I can say is that hacking these ROMs as a hobbyist is one thing, but when I see this method commercialized there will be some people at Omron that won't be too happy.
/rant off
Cool! I'm very happy that you were not only able to get it working, but you posted documentation for others to follow.
Since I'm currently running the HTC flavor software on my phone (not the one I posted here), I will use your instructions to try and get iWnnIME working on my phone with this image when I have time later and report back how it goes or any trouble along the way.
I wish I had the time to do this myself, but I'm busy hacking Android for other reasons for the company I work for. Anyway, I'm glad we were able to join efforts and now Japanese IME is available to everyone because of it. Good teamwork bro
just put system.img, boot.img and data.img into tools folder in your sdk and
put this in your dos window
fastboot erase system -w
fastboot erase boot
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
it worked good for me but all in chinese language, I don't understand chinese
very lite firmware, I prefer vodafone firmware
wassss said:
it worked good for me but all in chinese language, I don't understand chinese
very lite firmware, I prefer vodafone firmware
Click to expand...
Click to collapse
This is Japanese, not Chinese.
Google developed this OS for a very small run of phones that were given away for free (maybe 1000 phones or so) for use of development of Android apps, so this OS is minimal and not meant for daily use.
The only cool thing about this OS is the Japanese support, which hasn't been available for Android until now. The font and IME are particularly cool here, perhaps some locale settings, but not much else.
My intent was for others to extract anything they want from this OS, and pack it into other cool custom OS images, since it probably won't be posted here otherwise.
jmaurice said:
This is Japanese, not Chinese.
Google developed this OS for a very small run of phones that were given away for free (maybe 1000 phones or so) for use of development of Android apps, so this OS is minimal and not meant for daily use.
The only cool thing about this OS is the Japanese support, which hasn't been available for Android until now. The font and IME are particularly cool here, perhaps some locale settings, but not much else.
My intent was for others to extract anything they want from this OS, and pack it into other cool custom OS images, since it probably won't be posted here otherwise.
Click to expand...
Click to collapse
japanese or chinese it's same for me ...
ok ?
Thanks to iamerror for figuring out what files iWnnIME needs to run properly. Here is a simple pre-packaged installation guide how to get Japanese IME on your Android device.
Download the iWnnIME Japanese IME application and extract it so that you have the iWnnIME directory in your SDK tools directory.
Then do:
Code:
adb remount
adb push iWnnIME/jp.co.omronsoft.iwnnime /data/data/
adb push iWnnIME/[email protected]@[email protected] /data/dalvik-cache/
adb push iWnnIME/libiwnn.so /system/lib/
adb push iWnnIME/lib_dic.conf.so /system/lib/
adb push iWnnIME/lib_dic_e.conf.so /system/lib/
adb push iWnnIME/libEnjcon.so /system/lib/
adb push iWnnIME/libEnjemailuri.so /system/lib/
adb push iWnnIME/libEnjlearn.so /system/lib/
adb push iWnnIME/libEnjlearnL.so /system/lib/
adb push iWnnIME/libEnjlearnM.so /system/lib/
adb push iWnnIME/libEnjrel.so /system/lib/
adb push iWnnIME/libEnjyomi.so /system/lib/
adb push iWnnIME/libkaomoji_kihon.so /system/lib/
adb push iWnnIME/libkaomoji_tyukyu.so /system/lib/
adb push iWnnIME/libnjaddress.so /system/lib/
adb push iWnnIME/libnjcon.so /system/lib/
adb push iWnnIME/libnjemoji.so /system/lib/
adb push iWnnIME/libnjexyomi.so /system/lib/
adb push iWnnIME/libnjexyomi_new.so /system/lib/
adb push iWnnIME/libnjexyomi_re.so /system/lib/
adb push iWnnIME/libnjfzk.so /system/lib/
adb push iWnnIME/libnjname.so /system/lib/
adb push iWnnIME/libnjtan.so /system/lib/
adb push iWnnIME/libnjubase1.so /system/lib/
adb push iWnnIME/libnjubase2.so /system/lib/
adb push iWnnIME/DroidSansJapanese.ttf /system/fonts/
adb install iWnnIME/iWnnIME.apk
After installation, go to Settings -> Locale & Text and you should have an options to enable and configure the "iWnn IME".
Open any text input screen, and hold your finger on a text input screen for 3 seconds until the "select text input" dialog appears, and you can select the iWnnIME option.
Initially, the T9 screen will appear, but now to switch to qwerty, hold down the bottom left "文字" key for 3 seconds, and you can switch to the full-size keyboard.
Enjoy typing with native Japanese IME on Android !
Related
Hello all, I just completed an app I'd like to share with you all.
It's called Search2Play, it lets you play and pause your music by pressing a button on your device. On most devices, it is the search key. Currently, the Nexus & MyTouch 3G both use the Search key, whereas the Droid uses the Camera key. If you have physical keys (i.e. Droid, MT3G, G1, etc) then it will work when the phone is locked, but if you have capacitive keys (Nexus, Moment, Eris, Incredible, etc) then the screen must be on (lockscreen works, and fully unlocked of course).
It is available on the market under the name "Search2Play (Root Required)". It's totally free.
It requires root permissions to install. It also requires that you have a version of BusyBox that supports the "cp" command. Only Droid users probably have to worry about the busybox version, as most other custom ROMs have that already. Droid users, I recommend CyanogenMod for Droid or Bugless Beast as I know both of them have the right version.
It does not run in the background or install a service, just makes some changes to a few files on the /system partition.
The UI is very simple, just two buttons and some text explaining the app. Once you hit install, it will ask for permission to use root, you must hit accept or the app won't serve its purpose
The other button, "Restore", lets you remove the mod and go back to stock settings, where the search button brings up search, etc.
Supported Devices:
Nexus
Spica
Hero (GSM & CDMA)
Galaxy S devices (all US variants and probably the i9000 as well. It's not tested)
MyTouch 3G
Droid 1 (I've been told DX & D2 work as well, though I'm not sure how :?)
Evo (must be NAND unlocked or S-OFF)
Desire (must be NAND unlocked or S-OFF)
Free Version on Market:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Or click this from your device: Search2Play Free
See the Market to view a screenshot. Please give me some feedback. Thanks! Hope you enjoy the app :
FOR DEVICE REQUESTS SEE POST #3
Changelog:
1.4.1 thru 2.1:
Add support for Evo, GSM Hero, CDMA Hero, & Samsung Spica (thanks to Aasheet Kumar for the files I needed for Spica support!)
1.4:
Fixed rare root checking bug on some Droid ROMs, and maybe some Nexus ROMs too
1.6+ only now, sorry, it's not like any device this works for isn't updated to at least 1.6
1.3:
Now checks if the SD card is present on launch instead of just crashing if it's not there
Cleaned things up more
Merged some code between the donate & free versions
Better checks to see if it can be installed
1.2.5:
FINALLY stopped it from causing buttons to stop working. Checks for compatibility, and throws an error if it detects it can't run.
1.2:
Droid support!!
More should fix a few FC issues some people have seen. Let me know if you have problems.
1.1.2:
Fixes the not restoring bug
1.1.1:
Failed attempt at fixing the not restoring bug.
1.1:
Support for low res devices.
Now works with MT3G! Since it has a hard search key, it will even work when the phone is locked
Deletes files from SD card once done installing.
Cleaned up more code.
1.0.1:
Sets system back to Read-Only once finished installing
Cleaned up some code, if you have FCs let me know.
1.0:
Base release
If you want to request support for your device here's what I need. Note that your device must be able to be rooted and the system partition must be able to get read/write access from userspace. I.E. any Desire or Evo or any other recent HTC device with a NAND lock will not work, unless it has been NAND unlocked with an S-OFF bootloader, like via Unrevoked.. If your device has all that, get this info and send me an email at [email protected]
Run the command "adb shell mount" and tell me the output. I don't need the whole thing, just the line referring to the system partition. I.E. "/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)" is the line on the Nexus, it should be similar to that.
Then, run "adb shell getprop" and tell me the 1-4 lines related to the keyboard, like hw.keyboards.*.devname and tell me those lines. I.E the Nexus returns "mahimahi-keypad". Yours should be similar.
Finally, run "adb shell ls /system/usr/keylayout/". It should return a list of files all ending in ".kl"
Remember the keypad name from step 2? Good
There should be a ".kl" file matching that name (like mahimahi-keypad.kl). Pull that file with "adb pull /system/usr/keylayout/keypadname.kl directory" with directory being the folder you want to pull the file to and keypad name being the name from step 2.
Zip that file, and then send it to me please.
That should be it, if you have any questions or problems with this list hit me up on GTalk or email me. [email protected] for both GTalk & email.
Dear geniusdog
I just tried out your app.
I installed it, run it, pressed the install button, allowed root access and rebooted mynexus one. But after that reboot, my sell doesn't react on anypressed buttons anymore. I can only use the touchscreen...
I also tried to restore in your app, but there appeared a window saying that the app is not responding anymore.
How can I manually restore it? Is there a command or some files, I can edit?
Thanks for your help
bayoffire said:
Dear geniusdog
I just tried out your app.
I installed it, run it, pressed the install button, allowed root access and rebooted mynexus one. But after that reboot, my sell doesn't react on anypressed buttons anymore. I can only use the touchscreen...
I also tried to restore in your app, but there appeared a window saying that the app is not responding anymore.
How can I manually restore it? Is there a command or some files, I can edit?
Thanks for your help
Click to expand...
Click to collapse
Sorry for the issue. I have uploaded a new version of both apps that should fix the problem. If you can download the app and install it again, otherwise, PM me & I will give you manual instructions to restore it.
Also, just some technical details, the problem was caused because I had set it to create the directory on the start of the application. After that I removed it once you clicked the button & the install was finished. Because of that, if you clicked restore after install, it would fail to find the directory and then proceed to FC. Sorry for the trouble
Droid Support!!!!
Help!!!!!
I have installed V1.0.4, but my touch keys(back, Menu, Home and Search) don't work.
Then I have tried to restore it, but it's failed.
How could I fix it? Thanks.
My Rom is 2.1-update1 rooted.
hahabear said:
Help!!!!!
I have installed V1.0.4, but my touch keys(back, Menu, Home and Search) don't work.
Then I have tried to restore it, but it's failed.
How could I fix it? Thanks.
My Rom is 2.1-update1 rooted.
Click to expand...
Click to collapse
Hmm I dont have this issue, how does it fail? Does it just freeze, or does it FC, or does it say it finishes then do nothing? Also, what ROM, CM? Enomther? Please let me know so I can work on this.
Also, to fix it, download the attached file, & run the following commands (you must have ADB set up):
adb remount
adb shell rm /system/usr/keylayout/mahimahi-keypad.kl
adb push *path to downloaded file* /system/usr/keylayout/mahimahi-keypad.kl
Or you can just reflash your ROM, either way you'll get the same thing.
My phone is Nexus one.
My rom is Official v2.1-updated1.
When I execute the command as your indication.
"adb shell rm /system/usr/keylayout/mahimahi-keypad.kl"
rm failed for /system/usr/keylayout/mahimahi-keypad.kl, No such file or directory
What's wrong? And thank you for your quick reply.
hahabear said:
My phone is Nexus one.
My rom is Official v2.1-updated1.
When I execute the command as your indication.
"adb shell rm /system/usr/keylayout/mahimahi-keypad.kl"
rm failed for /system/usr/keylayout/mahimahi-keypad.kl, No such file or directory
What's wrong? And thank you for your quick reply.
Click to expand...
Click to collapse
Ok excellent that answers the second part of my question its failing to copy the file back over after deleting the original on certain ROMs.
You can just skip that step and go on to the "adb push" step. Also, can you run the command "adb shell cp" and tell me the output?
bingo! Thanks for your help. It's resolved.
On the other hand, I could get the mod.kl from SD Card, push again, Search2play will work, is that right?
hahabear said:
bingo! Thanks for your help. It's resolved.
On the other hand, I could get the mod.kl from SD Card, push again, Search2play will work, is that right?
Click to expand...
Click to collapse
Yes, but can you tell me what it says if you run the command "adb shell cp"
That will tell me if the issue is with the version of BusyBox on some ROMs.
Geniusdog254 said:
Yes, but can you tell me what it says if you run the command "adb shell cp"
That will tell me if the issue is with the version of BusyBox on some ROMs.
Click to expand...
Click to collapse
C:\N1root>adb shell cp
cp: not found
My god!!! It means there is not cp command in my phone?
hahabear said:
C:\N1root>adb shell cp
cp: not found
My god!!! It means there is not cp command in my phone?
Click to expand...
Click to collapse
Yeah exactly lol. Not sure if that was sarcasm or what, but thats what is causing the FC's and the failures some people are getting. And theres not a damn thing I can do about it.
I would recommend installing the CyanogenMod ROM, since it is fast, adds extra features, and supports cp Then the app will work just fine
Anyway. Thanks for your help. You are so kind. I will try new ROM later. And I will support your work. cu.
hahabear said:
Anyway. Thanks for your help. You are so kind. I will try new ROM later. And I will support your work. cu.
Click to expand...
Click to collapse
Thanks you very much for your support. Glad I could help you, if you have any other problems please email me, email listed in the market
Donate version now just to support me, added support for all devices to free version.
Please donate!
1.3 version uploaded
See changelog.
Any updates on newer phones?
KaliKot said:
Any updates on newer phones?
Click to expand...
Click to collapse
I can make it work for any phone without a NAND lock. Any requests?
I need to do the Galaxy S series, but the only one I can test is the Epic and I'm not sure if the others have different mount tables or not. Desire still has NAND lock so I can't do it. Not sure about Droid2/X. Just email/Twitter/PM me or post here with a request. I'll get back to you.
This is the stock Droid2 System and Framework files deodexed and zip aligned. This first of two packages that contains my Black (HTC) Status Bar Theme that looks like this. The next package will be the stock Droid2 deodexed and zip aliagned with stock status bar.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
( Picture from my Droid2 Theme for Droid 1. Status bar is exactly the same. Too lazy to update pic )
It contains all original Droid2 files so if you have renamed or removed files it will replace them. This includes all Droid2 widgets and bloatware. If you have removed or renamed files then you can rename or remove the files from the app folder you placed on your memory card so you do not have to go back after install to clean up.
A couple of apk files have been modified so the status icon matches status bar better. I still need to fix up a few more apk files and will post them as an update.zip file.
I will have a update.zip file soon so it can be installed with clockwork. If you would like to test it for me please message me to let me know.
Root Privilege:
You must have Root Access to install the files.
Check this thread and this thread on how to root your phone.
ADB:
You also need to have The Android SDK installed so you can use adb commands.
Clockwork Recovery:
Download from Android Market or check here and make donation after you download.
Download:
Droid2 Deodexed Black Status Bar Command Line Install
Droid2 Deodexed Stock Status Bar Command Line Install
Install Instructions - Recommended Method - Command Line:
Prep
Download the archive from above, extract file to your compter. Place app and framework folders from archive on the root of your sd card (/sdcard/app /sdcard/framework).
Make sure your phone is plugged into the USB cable and PC Mode is selected and that you have debugging enalbed on the phone application settings.
Open DOS prompt and type the following commands or paste them at the DOS prompt.
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/app/* /system/app/
cp /sdcard/framework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Install Instructions - Clockwork:
Coming Soon!
After reboot it will take a few minutes too boot up so be patient. Your phone has not hung on boot unless the droid eye stops moving.
Launcherpro:
Download themed LauncherPro 0.7.9.0 here.
Extract the com.fede.launcher.apk file and place on root of SD Card.
Make sure your phone is in PC Mode and Debugging is enalbed in Applications settings on phone.
Open command prompt on pc and type following commands.
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/com.fede.launcher.apk /system/app/
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Looking forward to the clockwork package. This is the mod I've been waiting for.
wsfanatic said:
Looking forward to the clockwork package. This is the mod I've been waiting for.
Click to expand...
Click to collapse
Go with the command line for now. Having adb will be better in the long run and have to figure out how to write a script for update.zip to delete all the odex files when installing from clockwork.
If I've already deodexed, would I still need the script to remove the *.odex files?
I think its worth noting that your phone needs to be in PC Mode when plugging it in, with debugging on. If your in mass storage, it won't work because adb won't be able to access the sdcard while its mounted on the computer. These commands should also work via Android Terminal, although I imagine it's easier copying and pasting with a mouse and keyboard.
I know this may be obvious to some, but when you have people not knowing what they're doing in the first place, they assume that certain instructions were omitted intentionally.
Natty_lite said:
I think its worth noting that your phone needs to be in PC Mode when plugging it in, with debugging on. If your in mass storage, it won't work because adb won't be able to access the sdcard while its mounted on the computer. These commands should also work via Android Terminal, although I imagine it's easier copying and pasting with a mouse and keyboard.
I know this may be obvious to some, but when you have people not knowing what they're doing in the first place, they assume that certain instructions were omitted intentionally.
Click to expand...
Click to collapse
Thanks! It's there under the install instructions.
Natty_lite said:
These commands should also work via Android Terminal, although I imagine it's easier copying and pasting with a mouse and keyboard.
.
Click to expand...
Click to collapse
It isn't a good idea to try installing system files from the phone especially in terminal when there is a "stop" command because this will hault the GUI and the system so you'd be stuck.
Please stick to ADB for this at least. A strong suggestion.
newk8600 said:
It isn't a good idea to try installing system files from the phone especially in terminal when there is a "stop" command because this will hault the GUI and the system so you'd be stuck.
Please stick to ADB for this at least. A strong suggestion.
Click to expand...
Click to collapse
I was just going to suggest that too...
-----------
LauncherPro has been updated to 0.7.9.0 Check bottom of first post for download link and install instructions.
MotoBoy said:
I was just going to suggest that too...
Click to expand...
Click to collapse
LOL great minds think alike!
newk8600 said:
It isn't a good idea to try installing system files from the phone especially in terminal when there is a "stop" command because this will hault the GUI and the system so you'd be stuck.
Please stick to ADB for this at least. A strong suggestion.
Click to expand...
Click to collapse
You're right. I didn't think about that. I'll make sure I remember that for future reference. Thank God I used ADB
MotoBoy said:
Thanks! It's there under the install instructions.
Click to expand...
Click to collapse
No problem at all. Very clean work. I'm running the black status bar on my phone as we speak.
Natty_lite said:
You're right. I didn't think about that. I'll make sure I remember that for future reference. Thank God I used ADB
No problem at all. Very clean work. I'm running the black status bar on my phone as we speak.
Click to expand...
Click to collapse
Cool...so I take it that theme install went well.
MotoBoy said:
Cool...so I take it that theme install went well.
Click to expand...
Click to collapse
Yep, thanks to you. I had issues getting the Deodex tool to work properly on my W7 64 bit machine. This file made life easier.
Someone just upped a D1 theme in the Theme and Apps subforum. Shouldn't I be able to replace the .apks from your file with those? (I'm trying to get the stock Android icons back for browser, music, dialer, sms, and calendar)
Natty_lite said:
Yep, thanks to you. I had issues getting the Deodex tool to work properly on my W7 64 bit machine. This file made life easier.
Someone just upped a D1 theme in the Theme and Apps subforum. Shouldn't I be able to replace the .apks from your file with those? (I'm trying to get the stock Android icons back for browser, music, dialer, sms, and calendar)
Click to expand...
Click to collapse
That should work...
Would this work if I have already installed a custom rom? Or would it mess things up?
Thanks!
-John
What exactly is theme in the launcherpro? Sorry to have to ask but couldn't the image be provided for the app drawer from the screenshot? Thanks for the great work!
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/app/* /system/app/
cp /sdcard/framework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Questions:
1. Could you explain the Mount line?
2. When you "rm" the odex files what happens. I mean have you done something to the associated .apx files?
If not, does that mean I could just use these commands and remove my .odex files and I would be what is called deodex'ed?
3. What is the benefit of de oxed' ing?
I am keeping an text file with abd instructions for different categories and do not understand some of the commands like the mount line that is the same in most of the procedures.
I have been googleing around trying to find a tutorial or lesson plan for adb and keep bookmarks on sites I find. Most of the info on the net that I find, you can get by typing adb help. That is fine, except it does not really explain what the commands mean or do.
Understand you are busy man, so if you do not have time for this, I'll understand. I am retired and have nothing else to do. Ha!
This is probably more information than you wanted to know, but you seem to be interested in learning so...
chrstdvd said:
Questions:
1. Could you explain the Mount line?
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
Click to expand...
Click to collapse
This line mounts the /system partition in read-write instead of the default read-only. In linux, hardware has special device files that are housed in the /dev/ directory. These devices get "mounted" for use to a mount point which usually has a nice, human-readable name. In this case, "/system". The "-t ext3" part defines the file system type. Typical linux file systems are ext2 and ext3. Winblows file systems are things like FAT32 and NTFS.
So, the command spelled out is something like this: remount in read-write mode the block device at "/dev/block/mmcblk1p21" to the mount point "/system" using the file system type "ext3".
2. When you "rm" the odex files what happens. I mean have you done something to the associated .apx files?
Click to expand...
Click to collapse
Yes something has been done. Deodexing is a lengthy process that, in part, converts the .odex files back to .dex files and reincorporates that data back into the associated .apk file. This is necessary for theme creation and some other kinds of development. The .odex files tend to prevent modification of .apk's, which is required for things like themes. The default .apk's are also signed zip files with a signature to prevent against tampering. In other words, although you can rename an .apk to .zip and extract it, you can't decompress an .apk, modify its contents (change an image or icon, for example) and then recompress without some consequences. Deodexing removes the signature stuff, making it far easier for developers to get at the guts of the content within the .apks.
If not, does that mean I could just use these commands and remove my .odex files and I would be what is called deodex'ed?
Click to expand...
Click to collapse
No. Simply removing the .odex files without replacing the .apk's with modified (deodexed) versions would leave you with non-functioning applications. The .odex files contain code that has been removed from the .apk files by developers in an effort to compress data and speed up the initial boot process.
Basically, when you phone boots for the first time, a lot of information is being decompressed into the /data directory for easy, quick access. The .odex files help streamline this process. With their data reincorporated into the .apk's, booting takes longer, but the benefits, like themes and other fixes that probably won't ever be available to non-deodexed phones, usually far outweigh the drawbacks.
3. What is the benefit of de oxed' ing?
Click to expand...
Click to collapse
For now, the ability to install custom themes is the main benefit. However, community developers are often able to provide fixes to problems on deodexed phones that the official devs will not, like the HTC Hero's stock lock screen issues.
If you're interested in learning more about adb, you will probably want to swan dive into some linux documentation. Without a linux background, the adb stuff will seem pretty foreign. I'd include links to some sources, but I'm new here and that's been restricted.
Stephan_ said:
What exactly is theme in the launcherpro? Sorry to have to ask but couldn't the image be provided for the app drawer from the screenshot? Thanks for the great work!
Click to expand...
Click to collapse
All that is themed in launcher pro are the icons when you long home press the home screen. So Shortcuts, Widgets, Folders and Wallpapers are using the same icons as Blur Home. Also the people and phone icons have been replaced to match the blur icons when you are using the default icons.
goliathvt said:
This is probably more information than you wanted to know, but you seem to be interested in learning so...
This line mounts the /system partition in read-write instead of the default read-only. In linux, hardware has special device files that are housed in the /dev/ directory. These devices get "mounted" for use to a mount point which usually has a nice, human-readable name. In this case, "/system". The "-t ext3" part defines the file system type. Typical linux file systems are ext2 and ext3. Winblows file systems are things like FAT32 and NTFS.
So, the command spelled out is something like this: remount in read-write mode the block device at "/dev/block/mmcblk1p21" to the mount point "/system" using the file system type "ext3".
Yes something has been done. Deodexing is a lengthy process that, in part, converts the .odex files back to .dex files and reincorporates that data back into the associated .apk file. This is necessary for theme creation and some other kinds of development. The .odex files tend to prevent modification of .apk's, which is required for things like themes. The default .apk's are also signed zip files with a signature to prevent against tampering. In other words, although you can rename an .apk to .zip and extract it, you can't decompress an .apk, modify its contents (change an image or icon, for example) and then recompress without some consequences. Deodexing removes the signature stuff, making it far easier for developers to get at the guts of the content within the .apks.
No. Simply removing the .odex files without replacing the .apk's with modified (deodexed) versions would leave you with non-functioning applications. The .odex files contain code that has been removed from the .apk files by developers in an effort to compress data and speed up the initial boot process.
Basically, when you phone boots for the first time, a lot of information is being decompressed into the /data directory for easy, quick access. The .odex files help streamline this process. With their data reincorporated into the .apk's, booting takes longer, but the benefits, like themes and other fixes that probably won't ever be available to non-deodexed phones, usually far outweigh the drawbacks.
For now, the ability to install custom themes is the main benefit. However, community developers are often able to provide fixes to problems on deodexed phones that the official devs will not, like the HTC Hero's stock lock screen issues.
If you're interested in learning more about adb, you will probably want to swan dive into some linux documentation. Without a linux background, the adb stuff will seem pretty foreign. I'd include links to some sources, but I'm new here and that's been restricted.
Click to expand...
Click to collapse
He took the words right out of my mouth
Thanks!
Thank you so much for the info. Linux huh, guess I will dive right in. My background is Basic, FORTRAN, COBAL AND Visual Basic for Apps (Excel only). I quit trying to keep up with Visual Basic because Object Oriented Programming was really starting to irritate me. I was fairly good in DOS back in the day. These adb commands remind me of DOS, so hopefully I will catch on and understand.
At least in the olden days you got a manual to explain the commands with some examples.
Anyway, Thank you. I will start Googleinh Linux.
Found this site and I am in pig heaven. Thanks again, things are starting to make sense, from the "old days perspective".
http://www.linux-tutorial.info/
This all started out as an experiment to get my nandroid system.img file running in the adb emulator. Well sadly I haven't been able to do that (yet) but I have found something useful. I've Seen several people all over asking how to get a working marketplace app in 2.2 on the adb emulator. After a lot of researching (and trial and error) I've managed to get one. Here are the steps I've taken. (Steps 5 and 6 optional, you can just use the included build.prop if you prefer)
1) Create an avd running 2.2 (froyo,plenty of places explain how to do this so I won't)
2) Download the file (attached below, root files included)
3) Unzip to a location that's easy to remember and find.
4) Load your emulated phone (allow it to load fully)
5) enter this command in a command prompt/terminal window (make sure you "cd" to the directory where you extracted the files)
Code:
adb pull /system/build.prop
6) Remove or comment "ro.config.nocheckin=yes" (no quotes, might be able to just change it to "no" but I haven't tried it that way)
7) enter these commands
Winblows (I mean windows)
Code:
adb remount
adb push build.prop /system/build.prop
adb install GoogleServicesFramework.apk
adb install Vending.apk
adb install Gmail.apk (optional but sometimes signing in here lets the market sign in)
adb shell rm /system/app/SdkSetup.apk
Linux
Code:
adb remount
adb push ./build.prop /system/build.prop
adb install ./GoogleServicesFramework.apk
adb install ./Vending.apk
adb install ./Gmail.apk
adb shell rm /system/app/SdkSetup.apk
8) Sign in. If it works you're done if not reboot and try again, sometimes it takes 3 or 4 reboots to set. If your emulated phone has a data signal from your computer (you'll see a 3G and network icon in the notification area) just wait for it to sign in. The cancel button should grey out within a minute. If it says it can't connect restart the emulator and try again, be patient.
There is a known bug that not all apps show up in the marketplace. I'm not sure why so if someone here knows how to fix that by all means leave a post and let me know. If I see it I'll add it to the first post (provided it works of course )
Edit: Working on getting root on the emulator (just for the hell of it). So far I have su in the xbin directory and superuser.apk installed. Not 100% sure what else I need to do to get the su requests to go through though, I'll probably PM a more experienced member and post back when I have more. Got root? I do (got it working.) Here are the steps you need to take.
Rooting the standard android image on the emulator
1) Open a command prompt (cd to the directoy where you extracted the files)
2) enter these commands
Code:
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock03 /system
adb push su /system/xbin/su
adb shell chmod 06755 /system
adb shell chmod 06755 /system/xbin/su
adb install superuser.apk
That's it! You now have a rooted, market-enabled android emulator.
New! N00b-friendly method
1) create your avd
2) download the emulator files archive attached to this post
3) extract somewhere easy to find
4) open command prompt/terminal and cd to the extracted location
5) start your avd
6) Run your script (windows.bat or linux.sh)
7) sign into market and enjoy root!
Note:
You may have to chmod su again upon restarting the emulator.
To get root back simply run the re-root script for your OS (bat for windows,sh for linux)
To install busybox simply run the re-root script, it will automatically install if you're using the script to install on a new avd.
Post 2
[reserved for updates, explanations, pictures, present/future tweaks in progress, etc]
Pictures:
Superuser list,Marketplace (I like solitaire><), Terminal with su permissions, and re-rooted Terminal
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tweaks:
1: root (done!)
2: busybox (done!)
Wow nice....
Thank you the root resets after reboot, working on making it stick but its not hard to do it again, just start with the "-wipe-data" command and redo the root, market works after reboot though. Still working on getting a dumped system.img to boot, ill post that in its own thread when i get it. Glad you like this.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App
Edit: see first post on how to get root back,no data-wipe!
so cool!! Good job man!
Thanks ^_^ let me know if you find any problems that I haven't already mentioned and I'll see if I can fix them or if they're just an emulator quirk.
Sorry for the double post but I wanted to let you all know busybox is now included! Installation can be performed through scripts (included in the "Emulator Files.rar" archive) or manually. If you wish to do it manually simply open the script in a text editor to see what's going on and enter the commands in a command prompt/terminal window.
I'm not able to make this work, not with a toolkit downloaded yesterday anyway.
Pulling of build.prop works, but pushing fails with a directory related error.
"adb shell" followed by "cd /system" and "ls -l" gives a list of files that does not include build.prop, neither as a file nor as a directory.
"ls -l build.prop" works though, and lists a file with 0644 permissions.
Install of all apks different from Gmail fails, with an error that says that those apks are already installed. Uninstalling them through adb doesn't work, netting instead a simple generic error.
Does anyone know whether I'm doing something wrong or Google has modified the emulator images so to render the Market workaround unusable? If so, where could I download an earlier version of the 2.2 system image?
Many thanks
Rocco
I actually had this issue as well. Try re-making the avd, worked for me. You could also try running the scripts to install, might work. If it doesnt post back and ill post the system.img from my sdk.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App
I have the same problem as ropi. Remade the avd several times with different properties, still no go.
I would really appreciate it if someone could upload a fully set-up avd somewhere.
I'll try again late this afternoon (I'm on CEST). Hope it works. If not, I'd be happy too if some kind soul would upload a link to a working avd
Thanks for the kind help
Rocco
I have no idea why people are having so many problems :/. I had the problem and once I remade the avd it went away. Try starting with the -partition-size 96 option and see if that helps. If not here are the files, just extract to your avd directory, it has the ini and img files you need and it's already setup. Just run re-root to get root back and sign into market and you're good to go.
http://hotfile.com/dl/79959332/3efbade/froyo-avd.rar.html
Edit: I just downloaded the latest revision and everything seems to be working fine :/ As I've said before try starting with -partition-size 96 and also try using the scripts I've provided. That should fix the issues, but if it doesn't there's always the hotfile link I've provided (or if you're just lazy lol)
Edit 2: also,just thought of this, make sure before you push the build.prop you adb remount. Pulling will work fine without doing that but pushing won't. No one said if they had done this and still received the errors so I'm trying to cover all bases. If remount fails try the adb shell mount command posted on the first page.
Thanks dbzfanatic, that avd worked great.
Glad it worked for ya. Let us know how everything works.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App
A lot of apps can not be found in the Market ... I cannot find Lookout....
Yeah, I've mentioned that,firs post. It's a known bug. Nothing I can do to fix it at the moment. You could download the apk on your phone then pull it then install it in the emulator. Bit of a roundabout way of doing things but it's all we can do on the emulator for the time being, at least from what I know.
Ok after a bit of poking around (sorry it took so long) I found out a bit about the market. It seems it's not just your region that it uses to show apps but things like your carrier, presence/absence of a SIM card, Android version, etc. It uses the filters to choose which apps to show and which to exclude (not showing an American user Japanese apps, not showing someone on Verizon T-Mobile apps, etc) so this explains part of the problem. I also found out that the SIM card and IMEI numbers were(are?) hard-coded into the emulator binary, changing these may allow us to see a few more apps. I looked through the binary file a bit and didn't find anything but I'll look more closely in a bit (new job, yay <- read as "groan"). I don't know how to emulate or spoof a carrier so that will still cut us back on some of the apps being seen. If anyone knows how to do this please post here and let us know! It would also be beneficial if a user who has already modified their IMEI and SIM numbers in the emulator to compare the apps list to the one you see in the standard, non-modded emulator binary and let us know if there is a difference or not. The more apps we can see in the marketplace the better!
Just wanted to confirm that I've tried Market Enabler a few days ago and it doesn't seem to work.
Alright thanks for the feedback. Ill keep working on it.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App
Despite several tries, I've so far been unsuccessful in using this method to install the marketplace on a 2.2 avd. Many thanks for having provided ready-made avds, then!
I've been able to install marketplace on the Galaxy Tab images provided by Samsung, though!
Keep up the good work
IMPORTANT INFO
First I gotta give a shoutout to KellyLewis3985 because he's helped so much with modding the script to need less work for install, run faster, and have more programs work.
NEEDED!
Must Be ROOTED
1. Busybox (Preferrably the most updated version).
2. Superuser.
3. Android SDK (With knowledge on how to use it).
4. AndroidVNC (Search exactly that in the market. It will say "Android VNC Viewer").
5. Terminal Emulator (Also available in the market).
6. Patience when working with this.
UPDATE!!
Thanks to the persistance of urboy4mbx, we now know a little more information to get it working. While both KellyLewis3985 and myself were running custom ROMS, we didn't think about testing it for the stock build. So due to urboy4mbx's will to get this installed, we now know you MUST have a custom ROM installed. There's probably ways to get it to work on the stock build, but it's going to take a little more work. For now, make sure you have a custom ROM, download, and install the files, and if we got our scripts right, it should boot right up for you.
DOWNLOAD FILE!
NOTE: When you download this zip, you will need to extract it, and inside the extracted folder will be the folder "sdcard", DO NOT!! Place this entire folder in your "ubuntu" folder, simply open it and copy all the files from it to your "ubuntu" folder on your sd card.
Download File...
Ubuntu: Epic Edition v1.2 <---These are the files you will need to run Ubuntu. It will come with "bootlinux", "fsrw", "mountonly", "ubuntu.img", "ubuntu.sh", and "unionfs".
INSTRUCTIONS!
Options For Transferring Files To Phone
First Option...
Your first option of course is the easiest. Simply connect your phone to the computer, and mount your sd card. Once on the sd card, you are going to create a new folder labeled "ubuntu". Open this folder and transfer all the files from the downloaded zip file into this folder. After you have transferred the files to your "ubuntu" folder on the sd card, unmount the sd card, but leave the phone plugged in.
Second Option...
Your second option is "adb push". Here is the command for "adb push" if you cant, or don't feel like mounting your sd card.
First you need to create your destination folder. Do so with this set of commands.
cd C:/sdk/tools (Of course you might have your sdk folder in a different location, just cd to that location)
adb shell
su
cd /sdcard/
mkdir ubuntu
exit
Now you should be back at "C:/sdk/tools", or wherever you have your sdk folder located. Next, you push the files to your folder. In order to push the files, you first need to open the zip folder, and copy all the files into your tools subfolder in the sdk folder. Then push the files with this set of commands.
adb push bootlinux /sdcard/ubuntu
adb push fsrw /sdcard/ubuntu
adb push mountonly /sdcard/ubuntu
adb push ubuntu.sh /sdcard/ubuntu
adb push unionfs /sdcard/ubuntu
adb push ubuntu.img /sdcard/ubuntu
The "ubuntu.img" file may take a little longer, as it is the largest file that needs to be transferred.
NOTE: You cannot have your sd card mounted to use adb. You must be unmounted.
INSTALLATION
1. Ok, first thing you have to do is make sure you're still cd'd to "C:/sdk/tools". Now you need to type "adb shell". You will then most likely be prompted with the symbol "$". To continue, type "su" and the symbol should then change to a "#". NOTE!!!! After adb shell, YOU MUST TYPE "su", or the program will not boot!!!
2. Next you are going to cd into the Ubuntu folder on your sd card. (cd /sdcard/ubuntu) Once in, you're going to type the command "sh ./ubuntu.sh".
After that runs through, the next thing you're going to enter is "bootlinux". Once you get the prompt "[email protected]" you have successfully installed ubuntu on the Epic.
With this new update, there is no need to install any other files, as we have added them into the image file for you so it should do so automatically. If you have issues, let us know and we will try to fix it.
PREPARING YOUR VNC TO LOAD UBUNTU!
NOTE: There is no need to type this into your adb shell. This is for information purposes only, i've displayed the code and it's position at the bottom of this post along with screen shots to show you what it should look like.
With our new update, it's a lot easier to get everything up and running, but we don't have the capability of storing the vnc server to start every time we start up ubuntu, as it was causing issues. Until we get this issue fixed, you have to start the vnc server like this:
rm -rf /tmp/.X*
export USER=root
vncserver -geometry 1280x800 (Or whatever you would like your resolution to be. We have found this to be the nicest so far.)
Ok, at this point, everything should be set up to run.
NOTE: After the initial install of ubuntu on your phone, when you want to get it to start again, all you have to do is go into the terminal emulator, first type "su" to give it superuser permissions, then type "bootlinux", it will run through it's script and give you the "[email protected]" prompt. After you get that prompt, simply type the "rm -rf /tmp/.X*", "export USER=root", and "vncserver -geometry 1280x800" prompts and you can then start vnc again.
All the info you need for vnc will be as follows.
Nickname: "root"
Password: "ubuntu" (This is a set password, so it will be the same for everyone.)
Address: "localhost"
Port: "5901"
Change Log
Version 1.2
-Modified to make it ext4 compatible.
-Modified img to make it a little faster and more stable.
That's really all I had to do for this version, as it was working before.
Version 1.1
-Modified the scripts to run smoother, faster and use less memory while running.
-Added some custom wallpapers.
-Mozilla Firefox now works.
-Modified scripts to make Ubuntu more interactive.
-Modified the .img to install everything needed instead of you having to do it.
Issues
-Firefox randomly closes. Just reopen and restore.
-After using the vncserver Ubuntu doesn't truly shutdown without a reboot. Fix in progress.
-When wanting to start Ubuntu, after initial install, you have to go into the terminal emulator and type "su", then "bootlinux", allow that to complete giving you the "[email protected]" prompt. Then type "rm -rf /tmp/.X*", "export USER=root", and "vncserver -geometry 1280x800" to start the vnc server. After that you can go right into vnc and start Ubuntu up. We ARE currently working on a fix for this issue.
If you have any issues please post. Your input helps us make this better for you.
Here's a couple tricks we picked up.
1. You can use the arrow pad on your keyboard to direct the mouse.
2. If you long press on the screen and keep your finger on it, you can slide the mouse with your finger.
3. Long press on something, is a left click.
4. Double tap on something, is a right click.
5. To get symbols to appear, such as "-", you have to HOLD the function key while hitting the symbol.
And i'm sure there's more, but there's a couple for now.
After the installation and the first time you setup the vncserver. You have to use this command everytime to start the vncserver again.
rm -rf /tmp/.X*
export USER=root
vncserver -geometry 1280x800
New links.
Ubuntu
http://db.tt/4z8uDst
New Scripts.
http://db.tt/lDjNNQn
Were working on a fix for this.
Here is the latest update. I dont know if its going to work for everyone. I suggest creating a folder inside the ubuntu folder to put the scripts you have in. Unzip this and replace the scripts in the ubuntu folder.
Please make a backup.
If you have any issues please post. Your input helps us make this better for you.
Yeah I'm on this as soon as I leave buffalo wild wings.
Sent from my SPH-D700 using XDA App
going to sleep soon for school in the morning, also will try tomorrow. naaao this is epic!
Since this is a full operating system, what are the chances or installing silverlight and being able to stream netflix?
Sent by a little green robot
As Of Right Now, The Internet Is Having Issues On This One, But Kellylewis And I Have Already Scripted Another Version Of Ubuntu And It Is Internet Compatible . We're Running It Now To Get The Bugs Worked Out And Will Have It Up Soon. After That, You Can Try To Download Whatever You Want, Considering It's An OS, And See If It Works... I Have Not Tested Downloading Anything.
The New Ubuntu Will Come As A Update, So Install This One The Way I've Instructed, And The Update Will Simply Replace The Files. The New One Is Faster, Internet Compatible, And Nicer Looking All Together. This One Still Works, But Please Be Patient For The Update. Thanks Everyone.
No matter what I do Im stuck here...
Also, If You Change The Port And It Says "VNC Cannot Connect" Or Something Like That, Back Out To The Terminal Emulator, And Hit "Exit" And "bootubuntu" Again And Change The "localhost" Number Again. Whatever The "localhost" Number, Change The Port Number To Match. Ex: "localhost:4" > "5904", "localhost:7" "5907".
Click to expand...
Click to collapse
I get "VNC connection failed!" on any port.
TIA for any help! thanks.
First, Exit From The Terminal Emulator, And Open It Back Up. Type "su" Then "Bootubuntu" Without Any Other Commands. It Should Boot It Up Still And Then When You Get The Localhost Prompt, Type "Exit" And "Bootubuntu" Again. This Time It Should Come Up Localhost:2 ...As Long As You Copied My Code, It Should Have Put The VNC Server In The Boot File So When Ubuntu Was Booted Up, It Would Automatically Start The Server. Anyways, When You Get "localhost:2" Change Your Port To 5902. Do That And Let Me Know What Happens.
Why Do You Type Like This? It's Really Annoying!
infamousjax said:
Why Do You Type Like This? It's Really Annoying!
Click to expand...
Click to collapse
Because That's How I Type... You Aren't Required To Look At This Thread, So If It Bothers You, Just Hit The Back Button. Otherwise, How I Type Should Be Of No Importance, So If You Want Ubuntu, Run The Script To Get It And You'll Never Have To Worry About How I Type Ever Again. It's Completely Up To You.
most excellent. hooks up without a glitch or a hangup or anything!
is lxde the only desktop you have used? would other replacement desktops work? im not saying lets throw gnome on there...but i wonder how it would run...takes a minute to get used to but runs like a champ!
so could this really the first step and getting the phone to fastboot into a ubuntu partition?
newkidd said:
most excellent. hooks up without a glitch or a hangup or anything!
is lxde the only desktop you have used? would other replacement desktops work? im not saying lets throw gnome on there...but i wonder how it would run...takes a minute to get used to but runs like a champ!
so could this really the first step and getting the phone to fastboot into a ubuntu partition?
Click to expand...
Click to collapse
If you like this one YOUR gonna love the next one. Its so much faster and looks amazing.
infamousjax said:
Why Do You Type Like This? It's Really Annoying!
Click to expand...
Click to collapse
Why would you come in to someones thread that has worked hard to give to the community and bash them? It makes no sense unless your jealous of him. Go whine about something else somewhere else. Thank you and have a nice day.
Here Are Some Screen Shots From The Next Ubuntu Version We're Working On ...Isn't It Gorgeous??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Give Us Some Feedback And Let Us Know What You Think
This guy mr im going to bed. Lol wait until you see what im doing.
Sent from my SGH-T959 using XDA App
I figured for all the skeptics I would put a bad pick up of the next update. Especially when it says drocap2 in it.
Sent from my SGH-T959 using XDA App
KellyLewis3985 said:
Why would you come in to someones thread that has worked hard to give to the community and bash them? It makes no sense unless your jealous of him. Go whine about something else somewhere else. Thank you and have a nice day.
Click to expand...
Click to collapse
SERIOUSLY? THAT IS NOT BASHING HIM. WHEN PEOPLE YELL AND SCREAM BY TYPING IN ALL CAPS IT IS JUST AS ANNOYING, DON'T YOU AGREE? HE WAS JUST POINTING OUT THAT TYPING THE WAY HE DOES IS A PAIN IN THE ASS TO READ. IF YOU CAN'T UNDERSTAND THAT THEN YOU MAY BE RETARDED. JUST LIKE PEOPLE WHO TYPE IN ALL CAPS. THANK YOU.
Sent from my SPH-D700 using XDA App
KellyLewis3985 said:
Why would you come in to someones thread that has worked hard to give to the community and bash them?
Click to expand...
Click to collapse
Because it legitimately detracts from the quality of an otherwise fine thread.
Also, it would be helpful if the landscape screenshots could be rotated so the text is right-side up. Thanks!
Just a noob question before I start... This only runs after you've booted it from the terminal emulator? As in your phone is still running all its original phone software (and by this I don't mean stock software, just phone software in general, custom or otherwise) and this is something you can boot on top of that? Maybe my terminology is wrong here, but that's at least how it appeared to work to me and I just wanted to check! Thanks!
wjsmaggle said:
Just a noob question before I start... This only runs after you've booted it from the terminal emulator? As in your phone is still running all its original phone software (and by this I don't mean stock software, just phone software in general, custom or otherwise) and this is something you can boot on top of that? Maybe my terminology is wrong here, but that's at least how it appeared to work to me and I just wanted to check! Thanks!
Click to expand...
Click to collapse
yeah it pretty much runs as a virtual machine on top of android...i only tested it and everything but android is always running...it grabs data and internet from the phones 3g/4g connection.
[Background]
A few users have gotten Transformers with Android 2.2 installed with diagnostic tools included. So far there have been 3 confirmed users who have gotten these units.
These units are shipped rooted from Asus
Unfortunately, t0dbld has confirmed that the sbk is locked on these devices
[Photos]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[System Dump]
System Archive:
http://db.tt/p3p14Ez
MD5 for Archive:
http://db.tt/DWpL8U7
Or
85c584c6f425fbd6ab111b9f73251fe0
[Reference Thread]
http://forum.xda-developers.com/showthread.php?t=1054120
[Credits]
mmsson - Took time to provide system dump
t0dbld - Helping with users with 2.2 TF and confirming sbk is locked
Welshiren - Currently taking his time to provide more details on his 2.2 TF
*I did not create the system dump or the photographs, and i take no credit for it
Placeholder For Later Or For Important Temporary Information
The MD5 link might be broken.
FYI it should be:
85c584c6f425fbd6ab111b9f73251fe0
Roach2010 said:
The MD5 link points to the system dump.
FYI it should be:
85c584c6f425fbd6ab111b9f73251fe0
Click to expand...
Click to collapse
Yup just realized that lol, corrected the link, thanks
Just some findings i found that i thought where interesting
in \system\lib\hw\wlan\ there are specific broadcom files
bcm4329.ko
fw_bcm4329.bin
fw_bcm4329_apsta.bin
fw_bcm4329_mfg.bin
The Broadcom 4329 supports FM according to specs
http://www.broadcom.com/products/Blu...utions/BCM4329
and look what i found in the app folder
FMTesttool.apk
Interesting...
The FMTesttool.apk wont run for me
I dont know if it is a honeycomb issue or a issue with it being disable in the Broadcom bin files
One user told me when he ran it it displayed radio frequencies but everything was in Chinese, and there was no audio output or any type of RF noise coming from the TF
Do any of these users have root access, a system dump is nice but we could use alot more than that.. we need to see if there partitions are hidden etc we need to see if they have an available partition map or at least a blkid command, next we should dd these partitions etc, the best we could gain from this is to see if the partitions still match up the same as in hc builds and than know where to look to unlock our devices
t0dbld said:
Do any of these users have root access, a system dump is nice but we could use alot more than that.. we need to see if there partitions are hidden etc we need to see if they have an available partition map or at least a blkid command, next we should dd these partitions etc, the best we could gain from this is to see if the partitions still match up the same as in hc builds and than know where to look to unlock our devices
Click to expand...
Click to collapse
I am unsure since the 3 known users who have gotten these units seem to be regular end users, the dump that was acquired was done through a walkthrough by another member on xda from what i was told
If you want to contact welshiron and walk him through the steps in doing a dd image of the partitions and go over any other things you want to know about the device
(dont know if he is familiar with linux, maybe have him do it through a live CD if he is up to it, or maybe use Cygwin to run DD if it even supports it)
Im still an Android noob so i cant really help him too much
If he is the trusting type he might let someone remote in via teamviewer, logmein, etc. lol
Anyways, my theory is these are shipping mistakes because of the limited supply, and once supply increases we may never see any of these test units again
You Dont need linux for a DD, we need root and that is all, also if they are on 2.2 and linux kernel .32 than super one click should work for a quick root and unroot when done. after than we need to get them to open an adb shell,
C:\ adb shell
$ su
# blkid
this will get us some output that we can go on from there also there maybe be a partition map on the tab... i wont get mine till tuesday so i can only guess on where it is . either way we would want to start dd the partitions he has or tha came up for example from the same adb shell with su
C:\ adb shell
$ su
# dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1.img
t0dbld said:
You Dont need linux for a DD, we need root and that is all, also if they are on 2.2 and linux kernel .32 than super one click should work for a quick root and unroot when done. after than we need to get them to open an adb shell,
C:\ adb shell
$ su
# blkid
this will get us some output that we can go on from there also there maybe be a partition map on the tab... i wont get mine till tuesday so i can only guess on where it is . either way we would want to start dd the partitions he has or tha came up for example from the same adb shell with su
C:\ adb shell
$ su
# dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1.img
Click to expand...
Click to collapse
Didnt know dd was built into android shell, thats cool
Can you contact him and walk him through it, i contacted asking him if he ever used ADB before, haven't gotten a response yet
SlimDan22 said:
Just some findings i found that i thought where interesting
in \system\lib\hw\wlan\ there are specific broadcom files
bcm4329.ko
fw_bcm4329.bin
fw_bcm4329_apsta.bin
fw_bcm4329_mfg.bin
The Broadcom 4329 supports FM according to specs
http://www.broadcom.com/products/Blu...utions/BCM4329
and look what i found in the app folder
FMTesttool.apk
Interesting...
The FMTesttool.apk wont run for me
I dont know if it is a honeycomb issue or a issue with it being disable in the Broadcom bin files
One user told me when he ran it it displayed radio frequencies but everything was in Chinese, and there was no audio output or any type of RF noise coming from the TF
Click to expand...
Click to collapse
new roms have the same bcm4329 files, look in /system/vendor in any rom (prime for example).
and lol i'm stupid, dd is the obvious answer for the boot.img.
We could theoretically make a cool testing rom with that.
also, if a wipe/factory reset got rid of testing apps, that means they were in /data, so we need a dump of that too, almost for sure. you see, i've never had a factory reset that so much as TOUCHED system partition, so if the apps disappeared after a reset, they were in data, not /system.
Hi!
Sorry if it has been posted already .
There is another guy who has received a 2.2 TF, and he cannot post in this thread.
I beg any master please go to this link (look in the pages 19 and 20) and help this man before he returns his TF tomorrow. Maybe there is still time to get something useful.
http://forum.xda-developers.com/showthread.php?t=1054120&page=20
Regards.
CalvinH said:
Hi!
Sorry if it has been posted already .
There is another guy who has received a 2.2 TF, and he cannot post in this thread.
I beg any master please go to this link (look in the pages 19 and 20) and help this man before he returns his TF tomorrow. Maybe there is still time to get something useful.
http://forum.xda-developers.com/showthread.php?t=1054120&page=20
Regards.
Click to expand...
Click to collapse
Are you talking about mmsson, if so he already returned it, he is the one who provided the partial system dump
But if you are talking about welshiron then i am in contact with him, it seems that no one has contacted him yet which is disappointing, i am trying my best to help him but i am not as experienced as other users in the community
Im working on showing how how to check for root
Yes I was talking about welshiron.
Thank you for your efforts. I would like to be able to do something by myself, but can't do much (well, apart from annoy you really expert guys by posting here and there).
Good luck.
Regards.
what exactly are the advantages of a 2.2 dump? will you be able to make older apps work?
I wonder if they have a different bootloader.. Is the partition layout the same? Thats a different tegrastats than my gtab.. Has anyone confirmed that this rom is not already rooted.. certainly seems like it would be. I really hope I get one of these treats.
Update:
The dev units do have root access!, welshiron has confirmed it and was able to run the su command to enable root privileges via adb
i need help from other experienced members here, i am going to have him run the blkid command, but after that i am unable to reliably walk him through and dumps through dd, due to lack of experience
I seem to have permission to post here now, how do I run the blkid command and what will that tell us?
Just a reminder, Android and Linux are alien to me so I will need help with the syntax
welshiron said:
I seem to have permission to post here now, how do I run the blkid command and what will that tell us?
Just a reminder, Android and Linux are alien to me so I will need help with the syntax
Click to expand...
Click to collapse
Im not sure either, i cant run it on my rooted phone with cyanogen
Im really surprised there is not a lot of activity or help, maybe its a slow day lol
I'm no expert but on my Desire I do this...
Download Mini ADB.
Have mine if ya need Link!
Run the Runme.Bat file
In the pop-up box type: adb shell
when it gets a console type: blkid
EDIT: Just in case it wasn't obvious, connect your Transformer to PC with USB and enable USB Debugging.
EDIT2: I think it's possible you will need to push Busybox to your device.